An abnormality prompting method and device of a timing message

Abstract

This specification provides a method and apparatus for providing abnormal prompts for timed messages, applied to a first client device of a communication application. The method includes: acquiring a timed message sending task, wherein the timed message sending task defines a target session, a target time point, and target content; the timed message sending task instructs the communication application to send the target content to the target session at the target time point, with the local user corresponding to the first client device as the sender; and if it is determined that the timed message sending task cannot be executed before the target time point arrives, a corresponding prompt message is sent to the local user.

Description

Technical Field

[0001] This specification relates to the field of communication technology, and in particular to a method and apparatus for providing abnormal notifications for timed messages. Background Technology

[0002] When users communicate using communication applications, they often encounter scenarios where they need to send messages to a specific session at a specific time, which limits communication efficiency. In related technologies, the client device of such communication applications can typically send specified content to a specified session at a specified time by creating a scheduled message sending task. When the specified time arrives, the specified content can be sent to the specified session without user intervention, thereby expanding the user's communication methods and improving communication efficiency.

[0003] However, if the aforementioned scheduled message sending task fails to execute for any reason, the client device will not provide feedback to the user, making it difficult for the user to determine whether the scheduled message sending task has been successfully executed, thus reducing communication efficiency. Summary of the Invention

[0004] To overcome the problems existing in related technologies, this specification provides a method and apparatus for providing abnormal prompts for timed messages.

[0005] Specifically, this specification is implemented through the following technical solution:

[0006] According to a first aspect of the embodiments of this specification, an abnormal notification method for a timed message is provided, applied to a first client device of a communication application, comprising:

[0007] A scheduled message sending task is obtained. The scheduled message sending task defines a target session, a target time point, and a target content. The scheduled message sending task is used to instruct the communication application to send the target content to the target session at the target time point, with the local user corresponding to the first client device as the sender.

[0008] If it is determined that the timed message sending task cannot be executed before the target time point is reached, a corresponding prompt message is sent to the local user.

[0009] According to a second aspect of the embodiments of this specification, an abnormal notification method for a timed message is provided, applied to a server device of a communication application, comprising:

[0010] A scheduled message sending task is obtained. The scheduled message sending task defines a target session, a target time point, and target content. The scheduled message sending task is used to instruct the communication application to send the target content to the target session at the target time point, with the target user corresponding to the first client device as the sender.

[0011] If it is determined that the timed message sending task cannot be executed before the target time point is reached, a corresponding prompt message is sent to the target user.

[0012] According to a third aspect of the embodiments of this specification, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first or second aspect.

[0013] According to a fourth aspect of the embodiments of this specification, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the method described in the first or second aspect.

[0014] According to a fifth aspect of the embodiments of this specification, a computer program is provided that, when executed by a processor, implements the steps of the method as described in the first aspect.

[0015] In the technical solution provided in this specification, by acquiring a timed message sending task, and if it is determined that the timed message sending task cannot be executed before the corresponding target time point, a corresponding prompt message is sent to the local user, thereby ensuring that the user can promptly confirm the executable status of the task and improving communication efficiency.

[0016] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this instruction manual. Attached Figure Description

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

[0018] Figure 1 This is a schematic diagram of a timed message sending interface shown in an exemplary embodiment of this specification;

[0019] Figure 2 This is a schematic diagram of the architecture of an abnormal notification system for timed messages, as illustrated in an exemplary embodiment of this specification.

[0020] Figure 3 This is a flowchart illustrating an exemplary embodiment of an error notification method for a timed message.

[0021] Figures 4a to 4f This is a schematic diagram of a multi-platform timed message sending interface, as illustrated in an exemplary embodiment of this specification.

[0022] Figure 5 This is a schematic diagram of a theme configuration interface shown in an exemplary embodiment of this specification;

[0023] Figures 6a-6c This specification illustrates an exemplary embodiment of a configuration that associates a set of facial expression images with keywords.

[0024] Interface diagram;

[0025] Figure 7 This is a flowchart illustrating another method for displaying anomalies in a timed message, as shown in an exemplary embodiment of this specification.

[0026] Figure 8 This is a schematic structural diagram of an electronic device shown in an exemplary embodiment of this specification;

[0027] Figure 9 This is a schematic diagram illustrating the structure of an abnormality notification device for a timed message, as shown in an exemplary embodiment of this specification; 5 Figure 10 This is a schematic diagram illustrating the structure of another timed message exception notification device according to an exemplary embodiment of this specification. Detailed Implementation

[0028] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The exemplary embodiments described below...

[0029] The embodiments described herein do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification.

[0030] It should be noted that in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification. In some other embodiments, the methods may include more or fewer steps than those described in this specification. Furthermore, a single step described in this specification may be broken down into multiple steps in other embodiments; and multiple steps described in this specification may be combined into a single step in other embodiments. It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0031] 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 manual are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0032] When users communicate using communication applications, they often encounter scenarios where they need to send messages to a specific session at a specific time, thus limiting communication efficiency. In related technologies, the client device of such communication applications can typically send specified content to a specified session at a specified time by creating a scheduled message sending task. When the specified time arrives, the specified content can be sent to the specified session without user intervention, thereby expanding the user's communication methods and improving communication efficiency. The following section will combine... Figure 1 The above-mentioned timed message sending interface will be described. Figure 1 This is a schematic diagram of a timed message sending interface shown in an exemplary embodiment of this specification, such as... Figure 1 As shown, suppose user A wants to send a timed message to session 101 named "X" via a client device of a communication application. The content of the timed message is media data entered by user A in the timed message content input box 102, and the time at which the timed message is sent to session 101 is the time data entered by user A in the time input box 1033. When user A clicks the confirm send button 1032, the aforementioned media data will be sent to session 101 at the time corresponding to the aforementioned time data. Of course, user A can also cancel the above process midway by clicking the cancel send button 131.

[0033] However, if the aforementioned scheduled message sending task fails to execute for any reason, the client device will not report this situation to user A, making it difficult for user A to determine whether the scheduled message sending task was successfully executed, resulting in reduced communication efficiency.

[0034] In view of this, this specification provides an abnormal notification scheme for timed messages to solve the problems existing in related technologies. The following is a detailed description in conjunction with the accompanying drawings.

[0035] Figure 2 This is an exemplary embodiment of the present specification illustrating the architecture of an abnormal notification system for timed messages. The architecture may include a server 21, a network 22, and several electronic devices, such as a mobile phone 23 and a PC 24.

[0036] Server 21 can be deployed on a physical server containing a standalone host, or it can be deployed on a virtual server (such as a cloud server) hosted in a host cluster. Server 21 can run a server-side program with an exception timed message notification function, thereby working in conjunction with the client-side program to provide users with corresponding exception timed message notification services. More specifically, the server-side program with the exception timed message notification function can be the server-side program corresponding to an instant messaging application, and the exception timed message notification function refers to sending a corresponding notification message to the user when it is determined that the scheduled message sending task cannot be executed before the corresponding target time point.

[0037] The network 22 for interaction between the mobile phone 23, the PC (Personal Computer) 24, and the server 21 can include various types of wired or wireless networks. In one embodiment, the network can include the Public Switched Telephone Network (PSTN) and the Internet.

[0038] The electronic device can be a mobile phone 23, PC 24, or wearable device (such as a smartwatch or smart glasses) with a communication application installed; this specification does not limit this. The electronic device can run a client-side program with an abnormal timed message notification function, thereby cooperating with the server to provide the user with the corresponding search application service. More specifically, the client-side program with the abnormal timed message notification function can be a client-side program corresponding to an instant messaging application, and the abnormal timed message notification filtering function can refer to sending a corresponding notification message to the corresponding user when it is determined that the timed message sending task cannot be executed before the corresponding target time point. Because by obtaining the timed message sending task and sending a corresponding notification message to the local user when it is determined that the timed message sending task cannot be executed before the corresponding target time point, it ensures that the user can promptly confirm the executable status of the task, thus improving communication efficiency.

[0039] Figure 3 This is a flowchart illustrating an exemplary embodiment of a timed message exception notification method. This method can be applied to a first client device and may specifically include the following steps:

[0040] Step 302: Obtain a scheduled message sending task. The scheduled message sending task defines a target session, a target time point, and target content. The scheduled message sending task is used to instruct the communication application to send the target content to the target session at the target time point, with the local user corresponding to the first client device as the sender.

[0041] When a user using the first client device wishes to send the target content for the target session at the target time, this can be achieved by executing a pre-created scheduled message sending task. This scheduled message sending task can be obtained by reading a pre-created scheduled message sending task, which is either pre-created by the user or created by another user (e.g., an administrator within the same organization) for all members of the organization; alternatively, the scheduled message sending task can be obtained by direct creation.

[0042] In one embodiment, the first client device can acquire the input content generated by the local user in any session's interface, and, if it is determined that the local user has selected timed sending as the sending method, further determine the time point selected by the local user, and then create the timed message sending task by taking any session as the target session, the input content as the target content, and the selected time point as the target time point. For example... Figure 4aThe aforementioned first client device uses the content "Please change the date in the schedule to Friday" entered by the user in a certain session into input box 401 as the target content of a timed message, and uses the time point determined by the time point selection component 402 as the target time point of the timed message as "June 2nd, 15:00". Of course, if... Figure 4b As shown, after the user successfully sets the above target content and the above target time point, and clicks the corresponding confirm and send button (i.e., Figure 4a After clicking the "OK" button, the corresponding message panel 403 to be sent can be displayed in the conversation interface of any session. The user can also click the "Edit" button 4031 in the message panel 403 to modify the target content "Change the date in the schedule to Friday" and the target time "June 2, 15:00".

[0043] When the aforementioned local user has multiple corresponding scheduled message sending tasks for different sessions, this manual can centrally display these multiple scheduled message sending tasks. For example... Figure 4c As shown, the first client device can display a task management interface 404, which is used to uniformly display timed message sending tasks sent by the local user. Those skilled in the art will understand that since the multiple timed message sending tasks may correspond to multiple sessions, the task management interface 404 can be divided into a "current session" interface for displaying timed message sending tasks corresponding to the current session, and a "all sessions" interface for displaying all timed message sending tasks, based on the session corresponding to the timed message sending task, thereby improving the efficiency of users querying established timed message sending tasks.

[0044] As mentioned earlier, the first client device can be either a mobile phone or a PC. Figure 4d and Figure 4e As shown, input box 405 and Figure 4a The input box 401 and the time point selection component 406 in the middle Figure 4a The technical effect of the timing selection component 402 is basically the same as that of the other components, so it will not be described again in this manual.

[0045] Step 304: If it is determined that the timed message sending task cannot be executed before the target time point is reached, a corresponding prompt message is sent to the local user.

[0046] The above-mentioned situations where the scheduled message sending task cannot be executed can be combined with Figure 4fThe description includes any of the following situations: the user on the local end is muted in the target session (i.e., the reason why message 409 cannot be sent), the target session is disbanded (i.e., the reason why message 408 cannot be sent), the target message is a group message with a unique reminder message for the target user (e.g., containing @ + the target user's username) and the target user leaves the target session (i.e., the reason why message 410 cannot be sent), the target message is a unique message for the target user and the target user's identity information changes (i.e., the reason why message 407 cannot be sent; specifically, when the target content contains confidential information and the target user has left their original organization, then the target content is sensitive information for the target user), and the user on the local end leaves the target session. This specification does not limit these situations.

[0047] In one embodiment, when the timed message sending task is successfully executed, the first client device can add a completion status identifier to the timed message sending task to indicate that the task has been completed. The completion status identifier can be represented based on, for example, 0 or 1 byte bits, and this specification does not limit it in this way.

[0048] When the aforementioned scheduled message sending task fails, secondary operations can be performed on it. For example, in response to the editing command triggered by the local user for any scheduled message sending task, the target session, target time point, and / or target content in any scheduled message sending task can be modified; or in response to the exception confirmation command triggered by the local user for any scheduled message sending task, a completion status flag indicating task completion can be added to any scheduled message sending task. This ensures that the local user can understand and decide on the subsequent handling of failed tasks.

[0049] In addition to the aforementioned timed messages, the first client device can also send a silent message to the second client device that will not attract the attention of the receiver.

[0050] In one embodiment, the first client device can obtain a mute message generated for the second client device, wherein the mute message carries a mute identifier, and then send the mute message to the server, which forwards it to the second client device. The mute identifier can be used to instruct the second client device to avoid triggering the corresponding reception prompt after receiving the mute message, thus satisfying the user's need for "their messages not to disturb the recipient." Furthermore, if the server has an associated third-party push notification system, the mute identifier can also be used to instruct the server to avoid forwarding the mute message to the third-party push notification system, which also prevents the third-party push notification system from disrupting the user's needs. It is worth noting that the mute message can be sent to the target session as a timed message, and this specification does not impose any limitations on this.

[0051] This manual provides a solution that can help each organization configure the theme scheme for the chat interface of its members, such as... Figure 5 As shown, the above theme scheme includes, but is not limited to: the appearance style of the conversation interface 501 (e.g., background color), the appearance style of related components (e.g., the selection color and background color of the navigation bar 502), the font style of the message 503 in the conversation interface (e.g., font, font size, etc.) and the style of the message box 504. This specification does not limit these aspects.

[0052] In one embodiment, the first client device can obtain a corresponding theme scheme based on the target organization to which the local user belongs. This theme scheme is configured uniformly by the target organization for all its members, and is applied to the session interface corresponding to the session associated with the theme scheme, thereby highlighting the target organization's philosophy or culture. The theme scheme can be configured to require the first client device to implement it, or it can be partially implemented by the local user as needed; this specification does not impose any limitations on this.

[0053] The following is combined Figures 6a-6c This section explains how to display a set of emoji images based on keywords in a message. Figures 6a-6c This is a schematic diagram illustrating an exemplary embodiment of the configuration interface for the association between a collection of facial expression images and keywords.

[0054] In one embodiment, the first client device can acquire any message from the session interface, which corresponds to a session related to the target organization to which the user belongs. Based on the correspondence between the unified set of emoticons and keywords configured by the target organization, if it is determined that the content of any message contains a target keyword corresponding to the target emoticon set, then the target emoticon set is displayed in the session interface. This also facilitates highlighting the target organization's philosophy or culture.

[0055] exist Figure 6a In the table composed of keywords 601 and emoticon image sets 602, each row represents a pair of keywords and emoticon image sets. This correspondence can be modified and its availability switched using the edit button 6031. Furthermore, the corresponding correspondence can be deleted by clicking the delete button 6032, or a new correspondence can be added by clicking the relationship add button 604. The keywords 601 can also be completely customized by the user, such as "Congratulations on the transaction," "Order completed," or "Next order." Both the edit button 6031 and the relationship add button 604 can point to... Figure 6b The interface is described in this manual, but this manual does not impose any restrictions on it.

[0056] exist Figure 6b In this context, the aforementioned set of emoticons can be obtained by users through local uploads or network links, or determined from the officially preset icons. Specifically, such as... Figure 6c As shown, the above set of emoji images can contain, for example, 5 types of icons, and each icon can be repeated.

[0057] Figure 7 This is a flowchart illustrating another method for displaying an exception in a timed message, as shown in an exemplary embodiment of this specification. This method can be applied to a server-side device and may specifically include the following steps:

[0058] Step 702: Obtain a scheduled message sending task. The scheduled message sending task defines a target session, a target time point, and target content. The scheduled message sending task is used to instruct the communication application to send the target content to the target session at the target time point, with the target user corresponding to the first client device as the sender.

[0059] In one embodiment, obtaining the timed message sending task includes: reading an existing timed message sending task, which was pre-created by the target user or other users; or, creating the timed message sending task.

[0060] In one embodiment, creating the timed message sending task includes: acquiring input content generated by the target user in any session's interface; if it is determined that the target user selected timed sending as the sending method, further determining the time point selected by the target user; and creating the timed message sending task by taking the any session as the target session, the input content as the target content, and the selected time point as the target time point.

[0061] In one embodiment, the situation in which the timed message sending task cannot be executed includes any of the following:

[0062] The target user is muted in the target session;

[0063] The target session was dissolved;

[0064] The target message is a group message with a unique reminder message for the target user, and the target user has exited the target session;

[0065] The target message is a separate message for the target user, and the target user's identity information has changed;

[0066] The target user exits the target session.

[0067] Step 704: If it is determined that the timed message sending task cannot be executed before the target time point is reached, a corresponding prompt message is sent to the target user.

[0068] In one embodiment, the method further includes: if the timed message sending task is successfully executed, adding a completion status identifier to the timed message sending task to indicate that the task has been completed.

[0069] In one embodiment, the method further includes at least one of the following: in response to an editing instruction triggered by the target user for any timed message sending task, modifying the target session, target time point, and / or target content in the any timed message sending task; in response to an exception confirmation instruction triggered by the target user for any timed message sending task, adding a completion status identifier to the any timed message sending task to characterize task completion.

[0070] In one embodiment, the method further includes: obtaining a mute message generated for a second client device, the mute message carrying a mute identifier; forwarding the mute message to the second client device, the mute identifier being used to instruct the second client device to avoid triggering a corresponding receiving prompt after receiving the mute message; wherein, if the server has an associated third-party message push system, the mute identifier is also used to instruct the server to avoid forwarding the mute message to the third-party message push system.

[0071] Figure 8 This is a schematic structural diagram of an electronic device according to an exemplary embodiment. Please refer to... Figure 8 At the hardware level, the electronic device includes a processor 801, a network interface 802, memory 803, non-volatile memory 804, and an internal bus 805, and may also include other necessary hardware. One or more embodiments of this specification can be implemented in software, such as the processor 801 reading the corresponding computer program from the non-volatile memory 804 into memory 803 and then running it. Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0072] Figure 9 This is a schematic diagram illustrating the structure of an abnormal notification device for a timed message, as shown in an exemplary embodiment of this specification. Please refer to... Figure 9 This device can be used as a first client device for communication applications, and the device includes:

[0073] The task acquisition unit 901 is used to acquire a timed message sending task. The timed message sending task defines a target session, a target time point and a target content. The timed message sending task is used to instruct the communication application to send the target content to the target session at the target time point with the local user corresponding to the first client device as the sender.

[0074] The task error notification unit 902 is used to send a corresponding notification message to the local user if it is determined that the timed message sending task cannot be executed before the target time point is reached.

[0075] Optionally, the task acquisition unit 901 is specifically used for:

[0076] Read the pre-created timed message sending task, which was pre-created by the local user or other users; or...

[0077] Create the scheduled message sending task.

[0078] Optionally, the task acquisition unit 901 is specifically used for:

[0079] Obtain the input content generated by the local user in any session's interface;

[0080] If it is determined that the sending method selected by the local user is timed sending, the time point selected by the local user is further determined;

[0081] The scheduled message sending task is created by taking any of the sessions as the target session, the input content as the target content, and the selected time point as the target time point.

[0082] Optionally, the device further includes:

[0083] The task success notification unit 903 is used to add a completion status identifier to the timed message sending task to indicate that the task has been completed when the timed message sending task is successfully executed.

[0084] Optionally, the situation in which the scheduled message sending task cannot be executed includes any of the following:

[0085] The user on this end is muted in the target session;

[0086] The target session was dissolved;

[0087] The target message is a group message with a unique reminder message for the target user, and the target user has exited the target session;

[0088] The target message is a separate message for the target user, and the target user's identity information has changed;

[0089] The user on this end exits the target session.

[0090] Optionally, the device further includes:

[0091] The task management interface display unit 904 is used to display the task management interface, which is used to uniformly display the timed message sending tasks with the local user as the sender.

[0092] Optionally, the device further includes at least one of the following:

[0093] The first task processing unit 905 is used to respond to the editing instruction triggered by the local user for any timed message sending task, and modify the target session, target time point and / or target content in the any timed message sending task;

[0094] The second task processing unit 906 is used to add a completion status identifier to any timed message sending task to indicate task completion in response to an exception confirmation instruction triggered by the local user for any timed message sending task.

[0095] Optionally, the device further includes:

[0096] The mute message sending unit 907 is used to obtain a mute message generated for the second client device, the mute message carrying a mute identifier;

[0097] The mute message is sent to the server, which then forwards it to the second client device. The mute flag is used to instruct the second client device to avoid triggering the corresponding receiving prompt after receiving the mute message.

[0098] In cases where the server has an associated third-party message push system, the mute flag is also used to instruct the server to avoid forwarding the mute message to the third-party message push system.

[0099] Optionally, the device further includes:

[0100] The theme scheme configuration unit 908 obtains the corresponding theme scheme according to the target organization to which the local user belongs. The theme scheme is configured uniformly for all members of the organization by the target organization. The theme scheme includes at least one of the following: the appearance style of the conversation interface, the appearance style of related components, the font style of messages in the conversation interface, and the message box style.

[0101] The theme scheme is applied to the session interface corresponding to the session associated with the theme scheme.

[0102] Optionally, the device further includes:

[0103] The emoticon image collection display unit 909 is used to obtain any message in the conversation interface, the conversation interface being a conversation related to the target organization to which the local user is located;

[0104] Based on the correspondence between the unified set of emoticons and keywords configured by the target organization, if it is determined that the content of any message contains a target keyword corresponding to the target set of emoticons, then the target set of emoticons is displayed in the conversation interface.

[0105] Figure 10 This is a schematic diagram illustrating the structure of another timed message exception notification device according to an exemplary embodiment of this specification. Please refer to... Figure 10 This device can be applied to server-side equipment for communication applications, and the device includes:

[0106] The task acquisition unit 1001 is used to acquire a timed message sending task. The timed message sending task defines a target session, a target time point and a target content. The timed message sending task is used to instruct the communication application to send the target content to the target session at the target time point with the target user corresponding to the first client device as the sender.

[0107] The task error notification unit 1002 is used to send a corresponding notification message to the target user if it is determined that the timed message sending task cannot be executed before the target time point is reached.

[0108] Optionally, the task acquisition unit 1001 is specifically used for:

[0109] Read the pre-created timed message sending task, which was pre-created by the target user or other users; or...

[0110] Create the scheduled message sending task.

[0111] Optionally, the task acquisition unit 1001 is specifically used for:

[0112] Obtain the input content generated by the target user in any session's interface;

[0113] If it is determined that the target user has selected timed sending as the sending method, the time point selected by the target user will be further determined.

[0114] The scheduled message sending task is created by taking any of the sessions as the target session, the input content as the target content, and the selected time point as the target time point.

[0115] Optionally, the device further includes:

[0116] The task success notification unit 1003 is used to add a completion status identifier to the timed message sending task to indicate that the task has been completed when the timed message sending task is successfully executed.

[0117] Optionally, the situation in which the scheduled message sending task cannot be executed includes any of the following:

[0118] The target user is muted in the target session;

[0119] The target session was dissolved;

[0120] The target message is a group message with a unique reminder message for the target user, and the target user has exited the target session;

[0121] The target message is a separate message for the target user, and the target user's identity information has changed;

[0122] The target user exits the target session.

[0123] Optionally, the device further includes at least one of the following:

[0124] The first task processing unit 1004 is used to modify the target session, target time point and / or target content in any timed message sending task in response to the editing instruction triggered by the target user for any timed message sending task.

[0125] The second task processing unit 1005 is used to add a completion status identifier to any timed message sending task in response to an exception confirmation instruction triggered by the target user for any timed message sending task, to indicate that the task has been completed.

[0126] Optionally, the device further includes:

[0127] The mute message sending unit 1006 is used to obtain a mute message generated for the second client device, the mute message carrying a mute identifier;

[0128] The mute message is forwarded to the second client device, and the mute flag is used to instruct the second client device to avoid triggering the corresponding receiving prompt after receiving the mute message;

[0129] In cases where the server has an associated third-party message push system, the mute flag is also used to instruct the server to avoid forwarding the mute message to the third-party message push system.

[0130] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0131] In a typical configuration, a computer device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0132] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0133] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0134] The computer-readable medium (or computer-readable storage medium) described above or in any other form may store computer instructions that, when executed by a processor, implement one or more of the embodiments described above, thereby realizing the technical solutions of this specification.

[0135] This specification also provides a computer program that, when executed by a processor, implements one or more of the embodiments described above, thereby achieving the technical solutions of this specification. This computer program may be specifically recorded on the computer-readable medium described above or in any other form, and this specification does not impose any limitations on this.

[0136] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0137] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.

[0138] The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of this specification. The singular forms “a,” “the,” and “the” as used in this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0139] It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0140] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

Claims

1. A method of abnormity notification of a timing message, characterized by, The first client device used in communication applications includes: A scheduled message sending task is obtained. The scheduled message sending task defines a target session, a target time point, and a target content. The scheduled message sending task is used to instruct the communication application to send the target content to the target session at the target time point, with the local user corresponding to the first client device as the sender. If it is determined that the timed message sending task cannot be executed before the target time point is reached, a corresponding prompt message is sent to the local user. The method further includes: Obtain a mute message generated for the second client device, the mute message carrying a mute identifier; The mute message is sent to the server, which then forwards it to the second client device. The mute flag is used to instruct the second client device to avoid triggering the corresponding receiving prompt after receiving the mute message. The scheduled message sending task cannot be executed under any of the following circumstances: The user on this end is muted in the target session; The target session was dissolved; The timed message is a group message with a separate reminder message for the target user, and the target user has exited the target session; The timed message is a separate message for the target user, and the target user's identity information has changed; The user on this end exits the target session.

2. The method of claim 1, wherein, The task of obtaining and sending timed messages includes: Read the pre-created timed message sending task, which was pre-created by the local user or other users; or... Create the scheduled message sending task.

3. The method of claim 2, wherein, Creating the scheduled message sending task includes: Obtain the input content generated by the local user in any session's interface; If it is determined that the sending method selected by the local user is timed sending, the time point selected by the local user is further determined; The scheduled message sending task is created by taking any of the sessions as the target session, the input content as the target content, and the selected time point as the target time point.

4. The method of claim 1, wherein, Also includes: If the scheduled message sending task is successfully executed, a completion status flag is added to the scheduled message sending task to indicate that the task has been completed.

5. The method of claim 1, wherein, Also includes: The task management interface is used to uniformly display timed message sending tasks with the local user as the sender.

6. The method of claim 1, wherein, It also includes at least one of the following: In response to the editing command triggered by the local user for any timed message sending task, modify the target session, target time point and / or target content in any timed message sending task; In response to the local user's exception confirmation command for any timed message sending task, a completion status identifier is added to the timed message sending task to indicate that the task has been completed.

7. The method of claim 1, wherein, If the server has an associated third-party push notification system, the mute flag is also used to instruct the server to avoid forwarding the mute message to the third-party push notification system.

8. The method of claim 1, wherein, Also includes: The corresponding theme scheme is obtained based on the target organization to which the local user belongs. The theme scheme is configured uniformly for all members of the organization by the target organization. The theme scheme includes at least one of the following: the appearance style of the conversation interface, the appearance style of related components, the font style of messages in the conversation interface, and the message box style. The theme scheme is applied to the session interface corresponding to the session associated with the theme scheme.

9. The method of claim 1, wherein, Also includes: Get any message from the conversation interface, which corresponds to a conversation related to the target organization to which the local user belongs; Based on the correspondence between the unified set of emoticons and keywords configured by the target organization, if it is determined that the content of any message contains a target keyword corresponding to the target set of emoticons, then the target set of emoticons is displayed in the conversation interface.

10. A method for providing an error notification for a timed message, characterized in that, Server-side equipment used in communication applications includes: A scheduled message sending task is obtained. The scheduled message sending task defines a target session, a target time point, and target content. The scheduled message sending task is used to instruct the communication application to send the target content to the target session at the target time point, with the target user corresponding to the first client device as the sender. If it is determined that the timed message sending task cannot be executed before the target time point is reached, a corresponding prompt message is sent to the target user. The method further includes: Obtain a mute message generated for the second client device, the mute message carrying a mute identifier; The mute message is forwarded to the second client device, and the mute flag is used to instruct the second client device to avoid triggering the corresponding receiving prompt after receiving the mute message; The scheduled message sending task cannot be executed under any of the following circumstances: The user on this end is muted in the target session; The target session was dissolved; The timed message is a group message with a separate reminder message for the target user, and the target user has exited the target session; The timed message is a separate message for the target user, and the target user's identity information has changed; The user on this end exits the target session.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 10.

12. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method as described in any one of claims 1 to 10.

Images