Message notification methods, apparatus, computer devices, and computer-readable storage media
By identifying the managed object in the session group and receiving its confirmation information, a notification message is sent directly to the session group, which solves the problem of editing errors of the managed object and improves the efficiency of notification and the timeliness of status confirmation.
Patent Information
- Application Number
- CN202111143904.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-09-28
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2041-09-28
AI Technical Summary
In a conversation group, the managed object is prone to editing errors and is inefficient when sending notification messages, and cannot promptly confirm the status of the message being sent.
By receiving the notification message from the first client, determining the managed object based on the attribute information of the session group, sending the notification message to the second client of the managed object, and sending the target notification message to the session group after receiving the confirmation message, the editing steps of the managed object are reduced.
It improves the efficiency of group notification messages, reduces editing errors, and ensures timely confirmation of message delivery status.
Smart Images

Figure CN115878339B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, specifically to a message notification method, apparatus, computer device, and computer-readable storage medium. Background Technology
[0002] With the development of instant messaging technology, messages can be sent to members of a conversation group, eliminating the need to send individual messages to each member and reducing communication costs. However, when a member not in the group needs a notification message from the group, or needs to send a notification message to a specific member within the group, the usual approach is to first notify the group member, who then sends the message to the group through the group's chat window. This process is prone to errors such as misediting the notification message or forgetting to send it, resulting in low message notification efficiency. Summary of the Invention
[0003] This application provides a message notification method, apparatus, computer device, and computer-readable storage medium, which can improve the efficiency of notifying messages to session groups.
[0004] This application provides a message notification method, including:
[0005] The system receives a pending notification message sent by a first client of a first object. The pending notification message indicates a pending notification session group and pending notification content. The session group includes at least two objects. The accounts of the at least two objects include a first object account belonging to a first message system and a second object account belonging to a second message system. The object account of the first object belongs to the first message system.
[0006] The management object of the session group is determined based on the attribute information of the session group, and the object account of the management object belongs to the first message system;
[0007] The notification message is sent to the second client corresponding to the managed object based on the object account of the managed object.
[0008] Receive confirmation information from the second client in response to the pending notification message;
[0009] Based on the confirmation message, a target notification message is sent to the object in the session group. The content of the target notification message includes the content to be notified, and the target notification message is sent to the managed object.
[0010] Accordingly, embodiments of this application also provide a message notification device, including:
[0011] The first receiving unit is used to receive a notification message sent by the first client of the first object. The notification message indicates the session group to be notified and the content to be notified. The session group includes at least two objects. The accounts of the at least two objects include a first object account belonging to the first message system and a second object account belonging to the second message system. The object account of the first object belongs to the first message system.
[0012] An object determination unit is used to determine the management object of the session group based on the attribute information of the session group, wherein the object account of the management object belongs to the first message system;
[0013] The first sending unit is used to send the notification message to the second client corresponding to the managed object according to the object account of the managed object;
[0014] The second receiving unit is used to receive the sending confirmation information triggered by the second client in response to the notification message;
[0015] The second sending unit is used to send a target notification message to an object in the session group according to the sending confirmation information. The content of the target notification message includes the content to be notified, and the target object of the target notification message is the managed object.
[0016] Accordingly, this application also provides a computer device including a memory and a processor; the memory stores a computer program, and the processor is used to run the computer program in the memory to execute any of the message notification methods provided in this application.
[0017] Accordingly, embodiments of this application also provide a computer-readable storage medium for storing a computer program, which is loaded by a processor to execute any of the message notification methods provided in embodiments of this application.
[0018] This application embodiment receives a pending notification message sent by a first client of a first object. The pending notification message indicates the session group to be notified and the content to be notified. The session group includes at least two objects, and the accounts of the at least two objects include a first object account belonging to a first message system and a second object account belonging to a second message system. The object account of the first object belongs to the first message system. The management object of the session group is determined according to the attribute information of the session group, and the object account of the management object belongs to the first message system. The pending notification message is sent to the second client corresponding to the management object according to the object account of the management object. The sending confirmation information triggered by the second client for the pending notification message is received. The target notification message is sent to the objects in the session group according to the sending confirmation information. The content of the target notification message includes the pending notification content, and the sending object of the target notification message is the management object. This scheme sends the pending notification message to the management object of the session group, and sends the target notification message to the session group based on the sending confirmation information of the management object for the pending notification message. This eliminates the need for the management object to edit the notification message and send it to the session group, which can reduce the editing errors that may occur during the editing process of the management object. Moreover, the sending confirmation information sent by the management object can confirm that the management object has sent the notification message, thereby improving the efficiency of sending notification messages to the group session. Attached Figure Description
[0019] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0020] Figure 1 This is a scenario diagram of the message notification method provided in the embodiments of this application;
[0021] Figure 2 This is a flowchart of the message notification method provided in the embodiments of this application;
[0022] Figure 3 This is another flowchart of the message notification method provided in the embodiments of this application;
[0023] Figure 4 This is a schematic diagram of the message notification interface provided in an embodiment of this application;
[0024] Figure 5 This is a schematic diagram of the sending range selection interface provided in an embodiment of this application;
[0025] Figure 6 This is a schematic diagram of the message notification interface provided in an embodiment of this application;
[0026] Figure 7 This is a schematic diagram of the target notification message display interface provided in an embodiment of this application;
[0027] Figure 8 This is a schematic diagram of the message status interface provided in an embodiment of this application;
[0028] Figure 9 This is a schematic diagram of a message notification device provided in an embodiment of this application;
[0029] Figure 10 This is a schematic diagram of the structure of the computer device provided in the embodiments of this application. Detailed Implementation
[0030] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0031] This application provides a message notification method, apparatus, computer device, and computer-readable storage medium. The message notification apparatus can be integrated into a computer device, which may be a server or a terminal, etc.
[0032] The terminal may include mobile phones, wearable smart devices, tablets, laptops, personal computers (PCs), and in-vehicle computers, etc.
[0033] The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.
[0034] For example, such as Figure 1 As shown, the first client is logged into the object account of the first object. The first client can display a message notification page. In response to selection and input operations on the message notification page, the first client generates a pending notification message indicating the session group and the content to be notified, and sends the pending notification message to the server. The server receives the pending notification message, determines the management object of the session group based on the attribute information of the session group indicated by the pending notification message, and sends the pending notification message to the second client corresponding to the management object.
[0035] The second client logs in to the object account that manages the objects. The second client displays the received pending notification message, responds to the sending confirmation operation for the pending notification message, and sends the sending confirmation information to the server. The server sends the target notification message to the objects in the session group based on the received sending confirmation information.
[0036] The third client logs in with the second object. The third client displays the received target notification message, responds to the confirmation operation for the target notification message, and sends notification confirmation information to the server. The server generates notification status information for the pending notification message based on the received notification confirmation information, and generates sending status information for the pending notification message based on the sending confirmation information. The server then sends the notification status information and sending status information to the first client.
[0037] This solution sends the notification message to the management object of the session group. Based on the confirmation information of the management object regarding the notification message, the target notification message is sent to the session group. This eliminates the need for the management object to edit the notification message and send it to the session group, reducing editing errors that may occur during the editing process. Furthermore, the first object can obtain the sending status information and notification status information of the message to be sent, thus improving the efficiency of notifying the group session.
[0038] Among them, the object account of the first object corresponds to the first message system, the object account of the managed object corresponds to the first message system, the object account of the second object corresponds to the second message system, the first message system and the second message system are heterogeneous systems, and the first message system and the second message system correspond to different account types.
[0039] Among them, the first object and the management object are related. For example, the first object and the management object can belong to the same organizational structure. The organizational structure can be a whole formed by at least one object in a certain structure. Members in the organizational structure can communicate within the organizational structure through the client (first client and second client) corresponding to the first message system. Members in the organizational structure can query other members in the organizational structure and communicate with them through the client.
[0040] A conversation group can be a combination of at least two objects, and the corresponding object accounts included in the conversation group can belong to either the first message system or the second message system.
[0041] The first client and the second client can be the same client or different clients.
[0042] The following sections provide detailed descriptions of each example. It should be noted that the order in which the embodiments are described is not intended to limit the preferred order of the embodiments.
[0043] This embodiment will be described from the perspective of a message notification device, which can be integrated into a server. This application embodiment provides a message notification method, such as... Figure 2 As shown, the specific process of this message notification method can be as follows:
[0044] 101. Receive a pending notification message sent by the first client of the first object. The pending notification message indicates the session group to be notified and the content to be notified. The session group includes at least two objects. The accounts of the at least two objects include the first object account belonging to the first message system and the second object account belonging to the second message system. The object account of the first object belongs to the first message system.
[0045] The notification message can indicate the conversation group to be notified, and can also include the notification content that the first object wants to send to the conversation group. The notification content can include text content, image content, video content, or audio content, etc.
[0046] For example, the first client can log in with the object account of the first object. When the user performs an operation on the user interface displayed on the first client (such as clicking, double-clicking, or long-pressing), the first client is triggered to send a notification message to the server. For example, when the user clicks on any message displayed on the first client, the first client generates a notification message based on that message and sends it to the server.
[0047] The server receives the pending notification message sent by the first client and determines the pending notification session group and the pending notification content based on the pending notification message.
[0048] The session group to be notified can be a pre-set session group or can be determined based on the user's selection. That is, in one embodiment, the step "receiving the notification message sent by the first client of the first object" may specifically include:
[0049] Receive message notification requests sent by the first client of the first object;
[0050] Based on the message notification request, determine the candidate session group that matches the first object;
[0051] Send a candidate session group to the first client of the first object;
[0052] Receive the first client response from the first object, which is a pending notification message triggered by the selection operation of the candidate session group.
[0053] For example, the first client may display the user interface corresponding to the notification message, respond to the user's trigger operation on a specified control on the user interface, or respond to a trigger operation on a certain message on the user interface, and send a message notification request to the server carrying the object account of the first object.
[0054] After receiving the message notification request, the server determines the object permissions of the first object based on the object account, retrieves candidate session groups matching the object permissions, and sends the candidate session groups to the first client of the first object. The first client displays the received candidate session groups and responds to the selection operation for the candidate session groups, generating a notification message indicating the selected session group.
[0055] For example, an object with the identity of principal can be set to send notification messages to all class groups in the school, and an object with the identity of grade leader can send notification messages to the classes in the grade it is responsible for. When a message notification request is received from an object with the identity of principal, the session groups managed by the school teachers are obtained as candidate session groups.
[0056] Different objects correspond to different candidate session groups, which can improve the flexibility of message notification. Objects cannot send notification messages to session groups that do not correspond to permissions, thus improving the reliability of message notification.
[0057] Optionally, the first client responds to the user's operation on a specified control on the user interface, displays a message input area and the corresponding candidate session group, responds to the selection operation of the candidate session group, and generates a notification message for the selected session group based on the message entered by the user in the message input area.
[0058] Optionally, the user can also select the message confirmation method for the notification message through the user interface displayed on the first client, such as no confirmation required, click confirmation, or signature confirmation. That is, after step "receiving the notification message sent by the first client of the first object", the message notification method may further include:
[0059] Determine the message confirmation method for the message to be notified based on the message attribute information;
[0060] Generate the corresponding target notification message based on the message confirmation method.
[0061] For example, the message confirmation method of the message to be notified can be determined based on the message attribute information, and a target notification message corresponding to the message confirmation method can be generated. If the message confirmation method is "no confirmation required", the content to be notified of the message to be notified can be used as the target notification message. If the message confirmation method is "click confirmation", a target notification message containing a click control can be generated based on the content to be notified. If the message confirmation method is "signature confirmation", a target notification message containing a signature area can be generated accordingly.
[0062] You can set appropriate message confirmation methods for pending notifications based on the needs of the scenario. For example, important pending notifications can be set to require click confirmation or signature confirmation. Based on the notification confirmation information corresponding to the message confirmation method, you can then obtain the viewing status of pending notifications by the objects in the conversation group.
[0063] 102. Determine the management object of the conversation group based on the attribute information of the conversation group. The object account of the management object belongs to the First Message System.
[0064] The attribute information can be information about the nature of the session group, such as the number of group members, the object identifier of the managed object, and the group name. The object identifier can be the object account or other information that can uniquely identify the managed object.
[0065] For example, the server could query the session group in a database or blockchain, and determine the management object of the session group based on the object identifier of the management object in the session group's attribute information.
[0066] 103. Send the notification message to the second client corresponding to the managed object based on the object account of the managed object.
[0067] For example, the server could obtain the object account of the managed object and send the notification message to the second client corresponding to the managed object based on the object account.
[0068] Optionally, corresponding event information can be generated based on different management objects. The event information may include the name of the first object that sent the message to be notified, the session group managed by the management object, and other information. A notification message is generated based on the event information and the content to be notified of the message to be notified. For example, the notification message received by the management object of the session group Class 1, Grade 1 may be: "Object B (corresponding to the first object) has assigned you to send the following notification message to the Class 1, Grade 1 session group: xxx (content to be notified)".
[0069] 104. Receive confirmation information from the second client in response to the pending notification message.
[0070] Among them, the confirmation information can manage the information that the object determines to send a notification message to the session group.
[0071] For example, the second client can display the received notification message on the user interface, respond to the user's confirmation operation for the notification message, send confirmation information, and the server can receive the confirmation information sent by the second client.
[0072] 105. Send a target notification message to the objects in the session group based on the confirmation message. The target notification message includes the content to be notified, and the target notification message is sent to the managed object.
[0073] For example, when a confirmation message is received, a target notification message can be generated in a preset message format based on the content to be notified in the message to be notified. For example, the target notification message can be generated as a sub-application (e.g., a mini-program), and the management object can be used as the sending object to send the sub-application corresponding to the target notification message to the conversation group. Alternatively, the target notification message can be generated as a group announcement and displayed in the group announcement.
[0074] Optionally, the target notification message may also include information such as the sending time.
[0075] After a third client containing an object in a session group receives a target notification message, the user can view the target notification message through the third client and confirm that the target notification message has been viewed. When the server receives a notification confirmation message sent by the third client, it can confirm that the target notification message has been viewed. That is, in one embodiment, the message notification method may further include:
[0076] Receive notification confirmation information triggered by a third client in response to a target notification message. The third client is the client where the second object in the session group is located. The object account of the second object in the session group belongs to the second message system.
[0077] Generate notification status information for the pending notification message in the session group based on the notification confirmation information.
[0078] Send notification status information of the pending notification message to the first client of the first object.
[0079] The third client can be a client corresponding to the second messaging system.
[0080] The notification confirmation information can include various forms of information, such as images, characters, or instructions. The content of the notification confirmation information is related to the notification confirmation method.
[0081] The notification status information may include information about whether the message to be notified has been viewed by objects in the session group, such as the number of people who have viewed it, the number of people who have not viewed it, the objects that have viewed it, and the objects that have not viewed it.
[0082] For example, a third client might receive and display the target notification message. Users can view the message and perform a confirmation operation based on the corresponding confirmation method, such as clicking or signing, to indicate that they have viewed the message. The third client, logged into with the second object's account, responds to the confirmation operation for the notification message, triggering the sending of confirmation information to the server. If the confirmation method is signature confirmation, the confirmation information sent by the third client to the server will be an image containing the signature. If the confirmation method is click confirmation, the confirmation information sent by the third client to the server may include corresponding instructions or requests.
[0083] The server receives a notification confirmation message from a third client. Based on the confirmation message, it can identify the second object that has performed the confirmation operation on the target notification message. Based on the second object that has performed the confirmation operation, it generates notification status information for the message to be notified and sends the notification status information to the first client. The first client can view the number of people who have viewed the message to be notified (number of people who have viewed it) and the object (object that has viewed it).
[0084] Optionally, based on the objects in the session group and the second object that performed the confirmation operation for the target notification message, the object that did not perform the confirmation operation for the target notification message can be determined. Based on the second object that has viewed the message to be notified and the object that has not viewed the message to be notified, notification status information is generated and sent to the first client of the first object. The first client can view the number of people who have viewed the message and the number of people who have not viewed the message, as well as the corresponding objects.
[0085] By monitoring the notification status information, you can know the notification status of the pending message in the conversation group. Timely notifications can be made to take action based on the notification status information to ensure that all participants in the conversation group have viewed the pending message and avoid problems caused by not seeing the pending message.
[0086] When the notification confirmation information includes a confirmation image, the content of the confirmation image can be used for identification, improving the reliability of notification message delivery. Specifically, the step "generating notification status information of the message to be notified in the session group based on the notification confirmation information" can include:
[0087] The identity information of the confirmed image is obtained by performing identity verification on the confirmed image;
[0088] The identity information is matched with the object information corresponding to the object to be notified, and the matching result is obtained.
[0089] If the matching result is a successful match, the notification status information of the message to be notified in the session group is determined based on the object to be notified in the notification confirmation message and the objects in the session group.
[0090] Among them, identity information recognition can be the recognition of identity information contained in the confirmation image, such as the recognition of facial information or text information in the confirmation image.
[0091] The object information can be information corresponding to an object in the session group. For example, it can be an image containing a face of an object in the session group, or facial information, real name, etc.
[0092] For example, if the message confirmation method is facial recognition confirmation, the user can use a third-party client to activate the camera to capture a confirmation image containing a face, or upload a confirmation image containing a face. Facial recognition is then performed on the confirmation image to obtain the facial information contained within it. This facial information is compared with the facial information of a pre-set second object. If they match, the matching result is "match successful"; otherwise, it is "match unsuccessful." If the match is successful, notification status information for the pending notification message is generated based on the notification confirmation information. If the match fails, it indicates an error in confirming the target notification message, and the notification confirmation information is not processed.
[0093] Optionally, if the message confirmation method is signature confirmation, the obtained message confirmation information can be a confirmation image containing a signature, and the corresponding identified identity information can include text information. That is, the step "identity information recognition of the confirmation image to obtain the identity information of the confirmation image" can specifically include:
[0094] Text features are extracted from the confirmed image to obtain the text feature information contained in the confirmed image;
[0095] The text information contained in the image is determined based on text feature information.
[0096] For example, the text features in the confirmation image can be extracted using optical character recognition (OCR) technology to obtain the text feature information contained in the confirmation image. Based on the text feature information, the text information contained in the confirmation image can be determined, that is, the signature information in the confirmation image can be obtained.
[0097] The signature information contained in the confirmation image is compared with the signature information of the pre-stored object to be reminded. If they match, the match is successful; otherwise, the match is unsuccessful.
[0098] In addition, the confirmation image can be compared with a preset image containing the signature to verify if the handwriting matches. This can be achieved using a neural network model, which will not be elaborated upon here. Verifying the confirmation information prevents erroneous operations from triggering the confirmation message and thus avoiding situations where the object is not alerted.
[0099] After the first client receives the notification status information of the message to be notified, it can view the objects to be reminded that have not yet triggered notification confirmation information through the first client, and can also trigger the sending of reminder messages to the objects to be reminded through the first client. That is, in one embodiment, the message notification method further includes:
[0100] The first client receives the message notification information triggered by the first object for the object to be reminded;
[0101] Send a target notification message to the recipient based on the message reminder information.
[0102] For example, after the first client receives the notification status message, it can display the corresponding user interface based on the notification status message, respond to the operation of the user interface to trigger message system information, and the server can send the target notification message to the object to be reminded according to the message reminder information.
[0103] Message notification trigger conditions can also be set. When the message notification trigger conditions are met, the target notification message is automatically resent to objects that have not viewed the message to be notified, thereby improving the efficiency of message notification. That is, in one embodiment, after obtaining the notification status information of the message to be notified, the message notification method may further include:
[0104] Determine the message notification trigger conditions based on message attribute information;
[0105] Based on the notification status information of the message to be notified, the objects to be reminded in the session group are determined. The objects to be reminded are those in the session group that have not triggered notification confirmation information for the target notification message.
[0106] If the current conditions meet the message notification trigger conditions, a target notification message will be sent to the recipient to be notified.
[0107] Among them, message attribute information can be information about the characteristics of the message to be notified, and message attribute information can include the message reminder trigger conditions of the message to be notified.
[0108] The message notification triggering condition can be related to time or quantity. For example, the message notification triggering condition can be a specified time, or when the number of objects that have not viewed the target notification message reaches a threshold.
[0109] For example, the message reminder triggering conditions of the target notification message can be determined based on the message attribute information, and the objects in the session group that have not viewed the target notification message can be determined based on the notification status information, that is, the objects that have not triggered notification confirmation information for the target notification message through a third client.
[0110] If the message trigger condition for the target notification is 21:00 today, then the target notification message will be sent to the recipient at 21:00. Optionally, the target notification message can be sent to the recipient through the management object, or it can be sent through the management assistant corresponding to the management object. The management assistant can be a virtual object corresponding to the management object, used to assist the management object in managing the session group. The management assistant does not need to log in to the client through the object's account. When the object is called the management object in the session group, a corresponding management assistant is generated.
[0111] Optionally, in addition to sending the target notification message to the recipient, a reminder message can also be sent to the recipient. The reminder message can be used to remind the recipient to check the target notification message. For example, the reminder message could be: "Please check the group notifications".
[0112] The targeted notification message can be sent to the recipient through a conversation group, or it can be sent directly to the recipient. In one embodiment, the step "sending the targeted notification message to the recipient" may specifically include:
[0113] If there is a relationship between the managed object and the object to be reminded, then the target notification message is sent to the object to be reminded through the managed object;
[0114] If there is no association between the managed object and the object to be reminded, a target notification message is sent to the object to be reminded through the session group. The target notification message is sent to the managed object.
[0115] The relationship can include the communication relationship between the managed object and the object to be reminded. For example, the managed object and the object to be reminded are friends. The object to be reminded can be an object in the contact list of the managed object, and the managed object can be an object in the contact list of the object to be reminded.
[0116] For example, if there is a relationship between the managed object and the object to be reminded, the managed object will send a target notification message to the object to be reminded based on the relationship. If there is no relationship between the managed object and the object to be reminded, the managed object cannot directly send a target notification message to the object to be reminded based on the relationship; instead, the managed object can send a target notification message to the object to be reminded through a session group.
[0117] In one embodiment, in addition to tracking the viewing status of target notification messages by second objects in the session group, the system can also track the sending status of pending notification messages by managed objects. This allows for understanding the sending and notification status information of pending notification messages, facilitating reminders to managed objects that have not sent pending notification messages and to objects that have not viewed target notification messages, thereby improving message notification efficiency. The message notification method may further include:
[0118] Based on the confirmation message triggered by the second client, determine the sent session group for the target notification message that has been sent;
[0119] Based on the sent session groups, determine at least two session groups to be sent, which are the groups that have not yet sent the target notification message;
[0120] Based on the sent session groups and the pending session groups, generate the sending status information corresponding to the notification messages;
[0121] Send the sending status information to the first client of the first object.
[0122] For example, the server can determine the session groups that have sent the target notification message based on the sent confirmation message, i.e., the sent session groups. Based on the sent session groups, it can determine the pending session groups that have not yet sent the target notification message. Based on the sent session groups and the pending session groups, it can generate the sending status information of the notification message to be sent.
[0123] The server sends status information to the first client of the first object. The first client can display the status information and the user can determine the session group that has not sent the target notification message based on the displayed content.
[0124] The first client can send a preset reminder message to the management object of the pending session group based on the user's operation, so as to remind the management object to trigger a confirmation request based on the second client for the notification message. That is, the message notification method may also include:
[0125] The first client receiving the first object receives a notification reminder message triggered by the pending session group in the sending status information;
[0126] Based on the notification reminder information, a preset reminder message is sent to the second client corresponding to the management object of the session group to be sent.
[0127] For example, after receiving the sending status information, the first client displays the corresponding user interface based on the sending status information, responds to operations related to the pending session group in the user interface, and triggers a notification reminder. The server, based on the received notification reminder, can send a preset reminder message to the second client managing the pending session group.
[0128] The preset reminder message can be a pending notification message or other messages, such as: "There is still a group notification that has not been sent. Please confirm."
[0129] As can be seen from the above, in this embodiment of the application, the server receives a pending notification message sent by a first client of a first object. The pending notification message indicates the session group to be notified and the content to be notified. The session group includes at least two objects, and the accounts of the at least two objects include a first object account belonging to a first message system and a second object account belonging to a second message system. The object account of the first object belongs to the first message system. The server determines the management object of the session group based on the attribute information of the session group. The object account of the management object belongs to the first message system. The server sends the pending notification message to the second client corresponding to the management object based on the object account of the management object. The server receives a sending confirmation message triggered by the second client in response to the pending notification message. The method involves sending a target notification message to an object in the session group based on the confirmation information sent by the management object. The target notification message includes the content to be notified. The target notification message is sent to the management object in the session group. This method sends the message to be notified to the management object in the session group, and then sends the target notification message to the session group based on the confirmation information sent by the management object for the message to be notified. This eliminates the need for the management object to edit the notification message and send it to the session group, which can reduce editing errors during the process of editing the notification message by the management object. Furthermore, the confirmation information sent by the management object can confirm that the management object has sent the notification message, thus improving the efficiency of sending notification messages to the group session.
[0130] Based on the above embodiments, the following examples will provide further detailed explanations.
[0131] This embodiment will describe a message notification system applied to a home-school communication scenario. Specifically, the message notification system may include a server, a first client, a second client, and a third client.
[0132] This application provides a message notification method, such as... Figure 3 As shown, the specific process of this message notification method can be as follows:
[0133] 201. The first client displays the message notification interface, responds to the operation on the message notification page, and sends the pending notification message to the server.
[0134] The message notification interface can be a user interface used to edit pending notification messages and trigger the sending of pending notification messages.
[0135] For example, specifically it can be like this Figure 4 As shown, the message notification interface displayed on the first client may include an input area for the content to be notified, a control for selecting the notification confirmation method, a control for setting the message reminder trigger conditions, and a control for selecting the sending range. Users can edit the content to be notified in the input area and enter the sending range selection interface by clicking the sending range selection control. Figure 5 The sending range selection interface is shown.
[0136] Once the content to be notified is edited, and the notification confirmation method, message reminder triggering conditions, and sending scope are all determined, you can click the "Send" control. The first client responds to this operation, generates a notification message indicating the content to be notified, the session group to be notified, the notification confirmation method, and the message reminder triggering conditions, and sends the notification message to the server.
[0137] 202. The server determines the management object of each session group based on the attribute information of the session group.
[0138] For example, the server could query the session group in a database or blockchain, and determine the management object of the session group based on the object identifier of the management object in the session group's attribute information.
[0139] 203. The server sends the notification message to the second client corresponding to the managed object based on the object account of the managed object.
[0140] For example, the server can generate corresponding event information based on different managed objects. The event information may include the name of the first object that sent the notification message, the session group managed by the managed object, and other information. A notification message is generated based on the event information and the notification content of the notification message.
[0141] 204. The second client sends a notification based on the received pending notification message.
[0142] For example, specifically it could be like this Figure 6 As shown in Figure 601, the second client can display an unread message in the message list as a reminder, and the user can click on the unread message to view it. Figure 6The message card shown in Figure 602 can include event information. For example, the notification message received by the administrator of the conversation group "Grade 1 Class 1" could be: "Object B (corresponding to the first object) has assigned you to send the following notification message to Grade 1 Class 1 and others (conversation group): xxx (content to be notified)". The user can click the "Send" control on the page (send confirmation operation) to confirm sending the notification message, and can also click... Figure 6 View the notification details of the message card shown in Message Card 602, such as... Figure 6 The notification details shown in section 603 can be used to select the session groups to be notified to the managed object. Users can select the session groups to be notified and send notification messages to the selected session groups.
[0143] 205. The second client sends a confirmation message to the server based on the confirmation operation for the message to be notified.
[0144] The second client responds to the user's confirmation of sending the notification message by sending confirmation information to the server.
[0145] 206. Based on the received confirmation message, the server sends the target notification message to the third client in the session group where the second object is located.
[0146] For example, when a confirmation message is received, a target notification message can be generated in a preset message format based on the content to be notified in the message to be notified. For example, the target notification message can be generated in the form of a mini-program, with the managed object as the sending object, and the mini-program corresponding to the target notification message can be sent to the conversation group. The target notification message can also include the sending time.
[0147] 207. The third client responds to the notification confirmation operation for the target notification message by sending notification confirmation information to the server.
[0148] For example, specifically, it could be that a third client receives a target notification message, such as... Figure 7 As shown, users can click on the mini-program to view the details of the target notification message and perform a notification confirmation operation on the target notification message.
[0149] The third client responds to the notification message by sending a confirmation message to the server.
[0150] 208. The server generates the sending status information and notification status information of the message to be notified based on the sending confirmation information and notification confirmation information, respectively.
[0151] For example, the server might receive a notification confirmation from a third client. Based on this confirmation, it can identify the second entity that has confirmed the target notification message. Based on this second entity, it generates notification status information for the pending notification message and sends this information to the first client. The first client can then view the number of people who have viewed the message (number of views) and the objects that have viewed it. Alternatively, based on the objects in the session group and the second entity that confirmed the target notification message, it can identify the objects that have not confirmed the message. Finally, it generates notification status information based on the second entities that have viewed the message and the objects that have not viewed it.
[0152] 209. The server will send status information and notification status information to the first client.
[0153] For example, specifically, notification status information could be sent to the first client of the first object. The first client could then view the number of people who have viewed the notification and the number of people who haven't, as well as the corresponding objects. Figure 8 As shown, the first client can display the sending status information of each pending notification message based on the notification status information. Users can remind the managed object to send pending notification messages by clicking the "Remind Send Notification" control, or remind the second object to check the target notification message by clicking the "Remind Confirmation" control.
[0154] 210. If the current conditions meet the message notification trigger conditions, the server will send a target notification message to the recipient.
[0155] For example, the message reminder triggering conditions of the target notification message can be determined based on the message attribute information of the message to be notified, and the objects in the session group that have not viewed the target notification message, i.e., the objects to be reminded that have not triggered notification confirmation information for the target notification message through a third client, can be determined based on the notification status information.
[0156] If the message triggering condition for the target notification message is 21:00 today, then at 21:00, the target notification message will be sent to the target object through the management assistant corresponding to the managed object.
[0157] For example, such as Figure 7 As shown, in addition to sending target notification messages to the recipients to be reminded, reminder messages can also be sent to the recipients to be reminded. Reminder messages can be used to remind the recipients to check the target notification messages. For example, a reminder message could be: "Please check the group notifications," etc.
[0158] As can be seen from the above, in this embodiment of the application, the first client displays a message notification interface, responds to the operation on the message notification page, and sends a message to be notified to the server. The server determines the management object of each session group based on the attribute information of the session group. The server sends the message to be notified to the second client corresponding to the management object based on the object account of the management object. The second client provides a reminder based on the received message to be notified. The second client sends a confirmation message to the server based on the confirmation message. The server sends the target notification message to the third client where the second object in the session group is located through the session group based on the received confirmation message. The third client responds to the confirmation message to the server and sends a confirmation message to the server. The server generates the sending status information and notification status information of the message to be notified based on the confirmation message and the notification confirmation information, respectively. The server sends the sending status information and the notification status information to the first client. If the current conditions meet the message reminder triggering conditions, the server sends the target notification message to the object to be reminded. This solution sends the notification message to the management object of the session group. Based on the confirmation information of the management object regarding the notification message, the target notification message is sent to the session group. This eliminates the need for the management object to edit the notification message and send it to the session group, reducing editing errors that may occur during the editing process. Furthermore, the first object can obtain the sending status information and notification status information of the message to be sent, thus improving the efficiency of notifying the group session.
[0159] To facilitate better implementation of the message notification method provided in the embodiments of this application, a message notification device is also provided in one embodiment. The meanings of the terms used are the same as in the message notification method described above, and specific implementation details can be found in the description of the method embodiments.
[0160] This notification device can be integrated into a computer device, such as... Figure 9 As shown, the message notification device may include: a first receiving unit 301, a target determination unit 302, a first sending unit 303, a second receiving unit 304, and a second sending unit 305, as detailed below:
[0161] (1) First receiving unit 301: used to receive a notification message sent by the first client of the first object. The notification message indicates the session group to be notified and the content to be notified. The session group includes at least two objects. The accounts of the at least two objects include the first object account belonging to the first message system and the second object account belonging to the second message system. The object account of the first object belongs to the first message system.
[0162] Optionally, the first receiving unit 301 includes a request receiving subunit, a group determination subunit, a sending subunit, and a message receiving subunit, specifically:
[0163] Request receiving subunit: used to receive message notification requests sent by the first client of the first object;
[0164] Group Determination Subunit: Used to determine the candidate session group that matches the first object based on the message notification request;
[0165] Sending subunit: Used to send the candidate session group to the first client of the first object;
[0166] Message receiving subunit: Used to receive the first client response of the first object, which is a pending notification message triggered by the selection operation of the candidate session group.
[0167] Optionally, the message notification device may further include a method determination unit and a message generation unit, specifically:
[0168] Method determination unit: used to determine the message acknowledgment method for the message to be notified based on message attribute information;
[0169] Message generation unit: used to generate corresponding target notification messages based on message confirmation methods.
[0170] (2) Object determination unit 302: used to determine the management object of the session group based on the attribute information of the session group. The object account of the management object belongs to the first message system.
[0171] (3) First sending unit 303: used to send the notification message to the second client corresponding to the managed object according to the object account of the managed object.
[0172] (4) Second receiving unit 304: used to receive the sending confirmation information triggered by the second client in response to the notification message.
[0173] (5) Second sending unit 305: used to send a target notification message to an object in the session group according to the sending confirmation information. The content of the target notification message includes the content to be notified, and the target object to which the target notification message is sent is the management object.
[0174] Optionally, the message notification device may further include a method information receiving unit, an information confirmation unit, and an information sending unit, specifically:
[0175] Information receiving unit: used to receive notification confirmation information triggered by a third client in response to a target notification message. The third client is the client where the second object in the session group is located, and the object account of the second object in the session group belongs to the second message system.
[0176] Information confirmation unit: used to generate notification status information of the message to be notified in the session group based on the notification confirmation information.
[0177] Information sending unit: Used to send notification status information of the pending notification message to the first client of the first object.
[0178] Optionally, the information confirmation unit may include an identification subunit, a matching subunit, and a status determination subunit, specifically:
[0179] Recognition Subunit: Used to identify the identity information of the confirmed image and obtain the identity information of the confirmed image;
[0180] Matching subunit: Used to match identity information with the object information corresponding to the object to be notified, and obtain the matching result;
[0181] Status determination subunit: If the matching result is a successful match, it determines the notification status information of the message to be notified in the session group based on the object to be notified in the notification confirmation message and the objects in the session group.
[0182] Optionally, the recognition subunit may include an extraction module and a text information determination module, specifically:
[0183] Extraction module: Used to extract text features from the confirmation image to obtain the text feature information contained in the confirmation image;
[0184] Text information determination module: used to determine the text information contained in the confirmation image based on text feature information.
[0185] Optionally, the message notification device may further include a reminder information receiving unit and a first message sending unit, specifically:
[0186] Reminder Information Receiving Unit: Used to receive message reminder information triggered by the first client of the first object for the object to be reminded;
[0187] First message sending unit: used to send target notification messages to the recipient based on message reminder information.
[0188] Optionally, the message notification device may further include a condition determination unit, a reminder recipient determination unit, and a second message sending unit, specifically:
[0189] Condition determination unit: used to determine the message notification triggering conditions of the target notification message based on message attribute information;
[0190] The reminder object determination unit is used to determine the reminder object in the session group based on the notification status information of the message to be notified. The reminder object is the object in the session group that has not triggered a notification confirmation message for the target notification message.
[0191] The second message sending unit is used to send a target notification message to the object to be reminded if the current conditions meet the message reminder triggering conditions.
[0192] Optionally, the second message sending unit may include the first message sending subunit and the second message sending subunit, specifically:
[0193] First message sending subunit: used to send a target notification message to the object to be reminded through the management object if there is a relationship between the managed object and the object to be reminded;
[0194] The second message sending subunit is used to send a target notification message to the object to be reminded through a session group if there is no association between the managed object and the object to be reminded. The target notification message is sent to the managed object.
[0195] Optionally, the message notification device may further include a first group determination unit, a second group determination unit, a status information generation unit, and a status information sending unit, specifically:
[0196] First group determination unit: used to determine the sent session group of the sent target notification message based on the sending confirmation information triggered by the second client;
[0197] Second group determination unit: used to determine the session group to be sent from at least two session groups based on the sent session groups, the session group to be sent being the group that has not sent the target notification message;
[0198] Status information generation unit: used to generate sending status information corresponding to the message to be notified based on the sent session group and the session group to be sent;
[0199] Status information sending unit: used to send sending status information to the first client of the first object.
[0200] Optionally, the message notification device may also include a status information receiving unit and a reminder message sending unit, specifically:
[0201] Status information receiving unit: used to receive notification and reminder information triggered by the pending session group in the status information sent by the first client of the first object;
[0202] Reminder Message Sending Unit: Used to send preset reminder messages to the second client corresponding to the management object of the session group to be sent, based on the notification reminder information.
[0203] As can be seen from the above, the message notification device in this application embodiment receives a pending notification message sent by a first client of a first object through a first receiving unit 301. The pending notification message indicates the session group to be notified and the content to be notified. The session group includes at least two objects, and the accounts of the at least two objects include a first object account belonging to a first message system and a second object account belonging to a second message system. The object account of the first object belongs to the first message system. The object determination unit 302 determines the management object of the session group based on the attribute information of the session group. The object account of the management object belongs to the first message system. The pending notification message is sent to the second client corresponding to the management object by the first sending unit 303 according to the object account of the management object. The second receiving unit 304 receives the pending notification message from the second client. The system receives a confirmation message triggered by the notification message. Finally, the second sending unit 305 sends the target notification message to the objects in the session group based on the confirmation message. The target notification message includes the content to be notified, and the recipient of the target notification message is the management object. This solution sends the notification message to the management object in the session group, and then sends the target notification message to the session group based on the confirmation message sent by the management object for the notification message. This eliminates the need for the management object to edit the notification message and send it to the session group, reducing editing errors during the process. Furthermore, the confirmation message sent by the management object confirms that the management object has sent the notification message, improving the efficiency of sending notification messages to the group session.
[0204] This application also provides a computer device, which can be a terminal or a server, such as... Figure 10 As shown, it illustrates a structural schematic diagram of the computer device involved in the embodiments of this application, specifically:
[0205] The computer device may include components such as a processor 1001 with one or more processing cores, a memory 1002 with one or more computer-readable storage media, a power supply 1003, and an input unit 1004. Those skilled in the art will understand that... Figure 10 The computer device structure shown does not constitute a limitation on the computer device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:
[0206] The processor 1001 is the control center of the computer device. It connects various parts of the computer device via various interfaces and lines, and performs various functions and processes data by running or executing software programs and / or modules stored in the memory 1002, and by calling data stored in the memory 1002, thereby providing overall monitoring of the computer device. Optionally, the processor 1001 may include one or more processing cores; preferably, the processor 1001 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and computer programs, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 1001.
[0207] The memory 1002 can be used to store software programs and modules. The processor 1001 executes various functional applications and data processing by running the software programs and modules stored in the memory 1002. The memory 1002 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, computer programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 1002 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 1002 may also include a memory controller to provide the processor 1001 with access to the memory 1002.
[0208] The computer equipment also includes a power supply 1003 that supplies power to the various components. Preferably, the power supply 1003 can be logically connected to the processor 1001 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 1003 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.
[0209] The computer device may also include an input unit 1004, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
[0210] Although not shown, the computer device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 1001 in the computer device loads the executable files corresponding to the processes of one or more computer programs into the memory 1002 according to the following instructions, and the processor 1001 runs the computer programs stored in the memory 1002 to realize various functions, as follows:
[0211] The first client of the first object receives a pending notification message, which indicates the pending notification session group and the pending notification content. The session group includes at least two objects, and the accounts of the at least two objects include the first object account belonging to the first message system and the second object account belonging to the second message system. The object account of the first object belongs to the first message system.
[0212] The management object of the conversation group is determined based on the attribute information of the conversation group, and the object account of the management object belongs to the First Message System;
[0213] The notification message will be sent to the second client corresponding to the managed object based on the object account of the managed object.
[0214] Receive confirmation information from the second client in response to the pending notification message; based on the confirmation information, send a target notification message to the object in the session group. The target notification message includes the pending notification content, and the target notification message is sent to the managed object.
[0215] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.
[0216] As can be seen from the above, the computer device in this application embodiment can receive a pending notification message sent by a first client of a first object. The pending notification message indicates the session group to be notified and the content to be notified. The session group includes at least two objects, and the accounts of the at least two objects include a first object account belonging to a first message system and a second object account belonging to a second message system. The object account of the first object belongs to the first message system. The device can determine the management object of the session group based on the attribute information of the session group, and the object account of the management object belongs to the first message system. The device can send the pending notification message to the second client corresponding to the management object based on the object account of the management object. The device can receive a sending confirmation triggered by the second client in response to the pending notification message. The method involves sending a target notification message to an object in the session group based on the confirmation information sent by the management object. The target notification message includes the content to be notified. The target notification message is sent to the management object in the session group. This method sends the message to be notified to the management object in the session group, and then sends the target notification message to the session group based on the confirmation information sent by the management object for the message to be notified. This eliminates the need for the management object to edit the notification message and send it to the session group, which can reduce editing errors that may occur during the editing process of the management object. Furthermore, the confirmation information sent by the management object can confirm that the management object has sent the notification message, thus improving the efficiency of sending notification messages to the group session.
[0217] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations of the above embodiments.
[0218] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by a computer program, or by a computer program controlling related hardware. The computer program can be stored in a computer-readable storage medium and loaded and executed by a processor.
[0219] Therefore, embodiments of this application provide a computer-readable storage medium storing a computer program that can be loaded by a processor to execute any of the message notification methods provided in embodiments of this application.
[0220] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.
[0221] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.
[0222] Since the computer program stored in the computer-readable storage medium can execute any of the message notification methods provided in the embodiments of this application, it can achieve the beneficial effects that any of the message notification methods provided in the embodiments of this application can achieve, as detailed in the preceding embodiments, and will not be repeated here.
[0223] The foregoing has provided a detailed description of a message notification method, apparatus, computer device, and computer-readable storage medium provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A message notification method, characterized in that, Applied to servers, including: The system receives a pending notification message sent by a first client of a first object. The pending notification message indicates a pending notification session group and pending notification content. The session group includes at least two objects. The accounts of the at least two objects include a first object account belonging to a first message system and a second object account belonging to a second message system. The object account of the first object belongs to the first message system. The management object of the session group is determined based on the attribute information of the session group, and the object account of the management object belongs to the first message system; The notification message is sent to the second client corresponding to the managed object based on the object account of the managed object. Receive confirmation information from the second client in response to the pending notification message; Based on the confirmation information, the server sends a target notification message to the objects in the session group, with the managed object as the sending object. The content of the target notification message includes the content to be notified. Receive notification confirmation information triggered by a third client in response to the target notification message, wherein the third client is the client of the second object in the session group, and the object account of the second object in the session group belongs to the second message system; Generate notification status information of the message to be notified in the session group based on the notification confirmation information; The notification status information of the pending notification message is sent to the first client of the first object.
2. The method according to claim 1, characterized in that, The message to be notified includes message attribute information, and the method further includes: Determine the message notification triggering conditions for the target notification message based on the message attribute information; Based on the notification status information of the message to be notified, the objects to be reminded in the session group are determined. The objects to be reminded are those in the session group that have not triggered notification confirmation information for the target notification message. If the current conditions meet the message notification trigger conditions, then the target notification message is sent to the object to be notified.
3. The method according to claim 2, characterized in that, Sending the target notification message to the recipient includes: If there is a relationship between the managed object and the object to be reminded, the target notification message is sent to the object to be reminded through the managed object based on the relationship. If there is no association between the managed object and the object to be reminded, the target notification message is sent to the object to be reminded through the session group, and the target notification message is sent to the managed object.
4. The method according to claim 2, characterized in that, After receiving the notification message sent by the first client of the first object, the method further includes: The message confirmation method for the message to be notified is determined based on the message attribute information. A corresponding target notification message is generated based on the aforementioned message confirmation method.
5. The method according to claim 1, characterized in that, The notification confirmation information includes a confirmation image, and the step of generating notification status information for the message to be notified in the session group based on the notification confirmation information includes: The identity information of the confirmed image is obtained by performing identity information recognition on the confirmed image; The identity information is matched with the object information corresponding to the object to be notified, and the matching result is obtained; If the matching result is a successful match, then the notification status information of the message to be notified in the session group is generated based on the notification confirmation information.
6. The method according to claim 5, characterized in that, The identity information includes text information. The process of recognizing the identity information of the confirmed image to obtain the identity information of the confirmed image includes: Text feature extraction is performed on the confirmation image to obtain the text feature information contained in the confirmation image; The text information contained in the confirmation image is determined based on the text feature information.
7. The method according to claim 1, characterized in that, The notification status information includes objects to be reminded that have not triggered notification confirmation information for the target notification message, and the method further includes: The first client receives a message notification triggered by the first object for the object to be reminded. The target notification message is sent to the recipient based on the message reminder information.
8. The method according to claim 1, characterized in that, The session groups include at least two session groups, and the method further includes: Based on the confirmation message triggered by the second client, determine the sent session group that has sent the target notification message; Based on the sent session groups, determine the session groups to be sent from the at least two session groups, wherein the session groups to be sent are the groups that have not sent the target notification message; Based on the sent session groups and the pending session groups, generate the sending status information corresponding to the message to be notified; The sending status information is sent to the first client of the first object.
9. The method according to claim 8, characterized in that, The method further includes: The first client receiving the first object receives a notification reminder message triggered by the pending session group in the sending status information; A preset reminder message is sent to the second client corresponding to the management object of the session group to be sent, based on the notification reminder information.
10. The method according to any one of claims 1-9, characterized in that, The pending notification message sent by the first client receiving the first object includes: Receive message notification requests sent by the first client of the first object; Based on the message notification request, determine the candidate session group that matches the first object; Send the candidate session group to the first client of the first object; Receive the first client response from the first object, which is a pending notification message triggered by the selection operation of the candidate session group.
11. A message notification device, characterized in that, include: The first receiving unit is used to receive a notification message sent by the first client of the first object. The notification message indicates the session group to be notified and the content to be notified. The session group includes at least two objects. The accounts of the at least two objects include a first object account belonging to the first message system and a second object account belonging to the second message system. The object account of the first object belongs to the first message system. An object determination unit is used to determine the management object of the session group based on the attribute information of the session group, wherein the object account of the management object belongs to the first message system; The first sending unit is used to send the notification message to the second client corresponding to the managed object according to the object account of the managed object; The second receiving unit is used to receive the sending confirmation information triggered by the second client in response to the notification message; The second sending unit is configured to send a target notification message to objects in the session group based on the sending confirmation information, with the managed object as the sending object. The content of the target notification message includes the content to be notified. The information receiving unit is used to receive notification confirmation information triggered by a third client in response to the target notification message. The third client is the client where the second object in the session group is located, and the object account of the second object in the session group belongs to the second message system. The information confirmation unit is used to generate notification status information of the message to be notified in the session group based on the notification confirmation information; The information sending unit is used to send the notification status information of the message to be notified to the first client of the first object.
12. A computer device, characterized in that, It includes a memory and a processor; the memory stores a computer program, and the processor is used to run the computer program in the memory to perform the message notification method according to any one of claims 1 to 10.
13. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which is loaded by a processor to perform the message notification method according to any one of claims 1 to 10.
14. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the message notification method according to any one of claims 1 to 10.
Citation Information
Patent Citations
Content publishing method and device
CN109995581A
Message interaction method and device, storage medium and electronic equipment
CN111880887A
