Message processing method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention discloses a message processing method and device, equipment, a storage medium and a program product, and the method comprises the steps: obtaining a target no-disturbing time period corresponding to a target session to which a current to-be-pushed message belongs based on a mapping relation between a session and a no-disturbing time period, the mapping relation comprises a plurality of sessions and a no-disturbing time period corresponding to each session in the plurality of sessions; if the current time point is not in the target no-disturbing time period, pushing the to-be-pushed message; and if the current time point is within the target no-disturbing time period, not pushing the to-be-pushed message. According to the technical scheme provided by the embodiment of the invention, the push message can be subjected to session-level non-disturbing management, and the flexibility and accuracy of message push can be improved.

Description

Technical Field

[0001] This application relates to the fields of computer and communication technology, and more specifically, to message processing methods, message processing apparatus, electronic devices, computer-readable storage media, and computer program products. Background Technology

[0002] With the continuous development and improvement of smart terminal functions, the number of applications installed and running on smart terminals is increasing, leading to a surge in push notifications. However, excessively frequent or numerous push notifications can significantly degrade the user experience for message recipients. Therefore, managing push notifications is a pressing issue that needs to be addressed. Summary of the Invention

[0003] The embodiments of this application provide a message processing method, a message processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product, which can perform session-level do-not-disturb management of push messages, thereby improving the flexibility and accuracy of message push.

[0004] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0005] According to one aspect of the embodiments of this application, this application provides a message processing method, the method comprising:

[0006] Based on the mapping relationship between sessions and do-not-disturb time periods, the target do-not-disturb time period corresponding to the target session to which the current message to be pushed belongs is obtained; wherein, the mapping relationship includes multiple sessions and the do-not-disturb time period corresponding to each of the multiple sessions;

[0007] If it is detected that the current time point is not within the target do-not-disturb time period, then the message to be pushed will be pushed.

[0008] If the current time point is detected to be within the target do-not-disturb time period, the message to be pushed will not be pushed.

[0009] According to one aspect of the embodiments of this application, an embodiment of this application provides a message processing apparatus, the apparatus comprising a detection unit, a first push unit, and a second push unit, wherein:

[0010] The detection unit is used to obtain the target do-not-disturb time period corresponding to the target session to which the current message to be pushed belongs, based on the mapping relationship between sessions and do-not-disturb time periods; wherein, the mapping relationship includes multiple sessions and the do-not-disturb time period corresponding to each of the multiple sessions;

[0011] The first push unit is used to push the message to be pushed if the current time is not within the target do-not-disturb time period;

[0012] The second push unit is configured not to push the message to be pushed if the current time point is within the target do-not-disturb time period.

[0013] In one embodiment, based on the aforementioned scheme, before obtaining the target do-not-disturb time period corresponding to the target session to which the current push message belongs based on the mapping relationship between the session and the do-not-disturb time period, the detection unit may further be used to: obtain the session identifier of the selected session in response to the session selection operation; obtain the do-not-disturb time period corresponding to the selected session in response to the time information editing operation of the selected session; and obtain the mapping relationship between the selected session and the obtained do-not-disturb time period based on the session identifier and the obtained do-not-disturb time period.

[0014] In one embodiment, based on the aforementioned scheme, when the detection unit obtains the do-not-disturb time period corresponding to the selected session in response to the time information editing operation for the selected session, it can specifically be used to: generate the do-not-disturb time period corresponding to the selected session in response to the start time point and end time point entered in the time information editing interface; wherein, the generated do-not-disturb time period starts from the current time point and ends at the input time point; or, generate the do-not-disturb time period corresponding to the selected session in response to the end time point entered in the time information editing interface; or, in response to the start time point entered in the time information editing interface, use the input start time point as the start time point of the do-not-disturb time period corresponding to the selected session.

[0015] In one embodiment, based on the aforementioned scheme, when the detection unit obtains the do-not-disturb time period corresponding to the selected session in response to an information editing operation for the selected session, it can specifically be used to: display a time information editing interface, which includes a recommended do-not-disturb time period obtained based on the historical do-not-disturb time period corresponding to the selected session; and obtain the do-not-disturb time period corresponding to the selected session in response to a trigger operation for the recommended do-not-disturb time period.

[0016] In one embodiment, based on the aforementioned scheme, when the detection unit obtains the mapping relationship between the selected session and the obtained do-not-disturb time period based on the session identifier and the obtained do-not-disturb time period, it can specifically be used to: detect the mapping relationship between the currently stored session and the do-not-disturb time period based on the session identifier, and obtain a relationship detection result; if the relationship detection result indicates that there is a target mapping relationship containing the session identifier, then update the do-not-disturb time period in the target mapping relationship to the obtained do-not-disturb time period; if the relationship detection result indicates that there is no target mapping relationship containing the session identifier, then map the session identifier to the obtained do-not-disturb time period to obtain the mapping relationship between the selected session and the obtained do-not-disturb time period.

[0017] In one embodiment, based on the aforementioned scheme, the detection unit can also be used to: if the current time point is not within the target do-not-disturb time period, obtain the termination time point contained in the target do-not-disturb time period; if the current time point reaches the termination time point, delete the mapping relationship containing the target do-not-disturb time period.

[0018] In one embodiment, based on the aforementioned scheme, the detection unit can also be used to: periodically traverse the mapping relationship between sessions and do-not-disturb time periods, obtain the termination time point included in the do-not-disturb time period in the currently traversed mapping relationship; if the current time point reaches the termination time point, delete the currently traversed mapping relationship.

[0019] In one embodiment, based on the aforementioned scheme, the second push unit can further be used to: if it is detected that the current time point has reached the end time point included in the target do-not-disturb time period, then obtain messages that the target session has not pushed during the target do-not-disturb time period; generate a prompt message based on the obtained messages, wherein the message length of the prompt message is less than the message length of the obtained messages; and push the prompt message.

[0020] In one embodiment, based on the aforementioned scheme, when the second push unit does not push the message to be pushed, it can be specifically used to: if the target session contains multiple session objects, and among the multiple session objects there is a target session object with a session priority greater than a preset priority, then obtain the session object to which the message to be pushed is sent; if the obtained session object does not match the target session object, then do not push the message to be pushed; if the obtained session object matches the target session object, then push the message to be pushed.

[0021] In one embodiment, based on the aforementioned scheme, when the second push unit does not push the message to be pushed, it can specifically be used to: perform information importance detection on the message to be pushed and obtain information detection results; if the information detection results indicate that the message to be pushed does not contain information with an importance greater than a preset importance threshold, then the message to be pushed is not pushed; if the information detection results indicate that the message to be pushed contains information with an importance greater than a preset importance threshold, then the message to be pushed is not pushed.

[0022] In one embodiment, based on the aforementioned scheme, after the second push unit states that if the current time point is within the target do-not-disturb time period, then it will not push the message to be pushed, it is further configured to: push the message to be pushed if the current time point reaches the end time point included in the target do-not-disturb time period.

[0023] According to one aspect of the embodiments of this application, an electronic device is provided, including one or more processors; and a storage device for storing one or more computer programs, which, when executed by the one or more processors, cause the electronic device to implement the message processing method as described above.

[0024] According to one aspect of the embodiments of this application, the embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor of an electronic device, causes the electronic device to perform the message processing method as described above.

[0025] According to one aspect of the embodiments of this application, the present application provides a computer program product, including a computer program stored in a computer-readable storage medium, wherein a processor of an electronic device reads from the computer-readable storage medium and executes the computer program, causing the electronic device to perform the message processing method as described above.

[0026] In the technical solution provided by the embodiments of this application, by mapping the relationship between sessions and do-not-disturb time periods, corresponding do-not-disturb time periods can be set for sessions. This allows for precise control over when messages generated in a session can be pushed and when they cannot, improving the flexibility and accuracy of setting do-not-disturb time periods and facilitating precise control of message pushes based on these time periods. Furthermore, by detecting whether the current time point is within the target do-not-disturb time period to select whether to push the message, messages within the do-not-disturb time period will not be pushed to the user. This effectively reduces the frequency and number of messages pushed to the user from various sessions, thus avoiding message overload. It achieves session-level do-not-disturb management of pushed messages, improving the flexibility and accuracy of message pushes and enhancing the user experience.

[0027] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0028] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0029] Figure 1 This is a schematic diagram of the structure of a message processing system provided in an embodiment of this application;

[0030] Figure 2 This is a flowchart illustrating a message processing method provided in an embodiment of this application;

[0031] Figure 3 This is a flowchart illustrating another message processing method provided in an embodiment of this application;

[0032] Figure 4 This is a schematic diagram of a time information editing interface provided in an embodiment of this application;

[0033] Figure 5 This is a schematic diagram of a do-not-disturb message setting process provided in an embodiment of this application;

[0034] Figure 6 This is a schematic diagram of a message push process provided in an embodiment of this application;

[0035] Figure 7 This is a schematic diagram of a lazy deletion process for non-disturbing information provided in an embodiment of this application;

[0036] Figure 8 This is a schematic diagram of a process for periodically deleting Do Not Disturb messages provided in an embodiment of this application;

[0037] Figure 9 This is a structural block diagram of a message processing apparatus illustrated in an exemplary embodiment of this application;

[0038] Figure 10 This is a schematic diagram of the structure of a computer system suitable for implementing the electronic devices of the present application embodiments. Detailed Implementation

[0039] 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 embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0040] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0041] The flowcharts shown in the accompanying diagrams are merely illustrative and do not necessarily include all content and operations, nor do they necessarily have to be executed in the described order. For example, some operations may be broken down, while others may be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0042] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0043] It should also be noted that "multiple" as mentioned in this application refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0044] As the functions of smart terminals continue to develop and improve, the number of applications installed and running on smart terminals is increasing, and the number of push messages is also growing. However, pushing messages too frequently or in too many quantities to the terminal user can cause some annoyance and reduce the user experience.

[0045] Based on this, this application provides a message processing scheme that establishes a mapping relationship between sessions and do-not-disturb time periods, so that the target do-not-disturb time period corresponding to the target session to which the message to be pushed belongs can be queried; then, by detecting whether the current time point is within the target do-not-disturb time period, it is selected whether to push the message to be pushed.

[0046] Specifically, if the current time is not detected within the target do-not-disturb period, the aforementioned pending push messages can be pushed; if the current time is detected within the target do-not-disturb period, the aforementioned pending push messages will not be pushed. Furthermore, a session can specifically be an application session, which is the primary source of application messages. A session can contain one or more session objects.

[0047] Therefore, this solution establishes a mapping relationship between sessions and do-not-disturb time periods, allowing for the setting of specific do-not-disturb time periods for each session. This enables precise control over when messages generated within a session can be pushed and when they cannot, improving the flexibility and accuracy of do-not-disturb settings. Furthermore, by detecting whether the current time falls within the target do-not-disturb time period and then deciding whether to push messages, messages within the do-not-disturb time period are prevented from being pushed to the user. This effectively reduces the frequency and number of messages pushed to the user, achieving session-level do-not-disturb management of push messages, thereby improving the flexibility and accuracy of message push and ultimately enhancing the user experience.

[0048] Based on the above message processing scheme, this application provides a message processing system, which can be found in [reference needed]. Figure 1 , Figure 1The message processing system shown may include terminal devices 101 and servers 102. The number of terminal devices 101 and servers 102 may be one or more. A communication connection is established between any terminal device and any server. For example, terminal device 101 may include any one or more of smartphones, tablets, laptops, desktop computers, smart voice interaction devices, smart home appliances, in-vehicle terminals, aircraft, and smart wearable devices. Terminal device 101 may have various business clients installed, such as social networking clients, game clients, live streaming clients, shopping clients, interactive experience clients, and map clients. Server 102 may be a server or server cluster providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. Any terminal device 101 and any server 102 may communicate directly or indirectly via wired or wireless communication; this application does not impose any limitations on this.

[0049] In some embodiments, the above message processing method may be performed solely by Figure 1 The terminal device 101 in the message processing system executes the following process: Based on the mapping relationship between sessions and do-not-disturb time periods, the terminal device 101 obtains the do-not-disturb time period corresponding to the session to which the message to be pushed belongs. Then, if the terminal device 101 detects that the current time is not within the obtained do-not-disturb time period, it can push the message to be pushed; if the terminal device 101 detects that the current time is within the obtained do-not-disturb time period, it will not push the message to be pushed.

[0050] In other embodiments, the above message processing method may also be performed solely by... Figure 1 The message processing system shown in the diagram is executed by server 102. The specific execution process may include: server 102 obtaining the do-not-disturb time period corresponding to the session to which the message to be pushed belongs, based on the mapping relationship between sessions and do-not-disturb time periods. Then, if server 102 detects that the current time is not within the obtained do-not-disturb time period, server 102 can send the message to be pushed carrying a push tag to terminal device 101, so that terminal device 101 pushes the message to be pushed; if server 102 detects that the current time is within the obtained do-not-disturb time period, server 102 can send the message to be pushed carrying a non-push tag to terminal device 101, so that terminal device 101 does not push the message to be pushed.

[0051] In some other embodiments, the message processing method described above can run in a message processing system, which may include terminal devices and servers. Specifically, the message processing method described above can be... Figure 1 The message processing system shown is jointly implemented by terminal device 101 and server 102. Specifically, terminal device 101 receives a message to be pushed from server 102. Based on the mapping relationship between sessions and do-not-disturb time periods, terminal device 101 obtains the do-not-disturb time period corresponding to the session to which the received message belongs. Then, if terminal device 101 detects that the current time is not within the obtained do-not-disturb time period, it can push the message; if terminal device 101 detects that the current time is within the obtained do-not-disturb time period, it will not push the message.

[0052] It should be noted that the embodiments of this application can be applied to various application scenarios that require message push, including but not limited to games, cloud technology, artificial intelligence (AI), smart cities, smart transportation, assisted driving and other application scenarios. It can also be used to push messages to various applications such as instant messaging applications, social media applications, game applications, live streaming applications, shopping applications and so on. There is no limitation on this.

[0053] It should be noted that in the specific implementation of this application, if the session data, do-not-disturb time period and other related data or information involve the object, when the embodiments of this application are applied to specific products or technologies, the permission or consent of the object is required, and the collection, use and processing of related data or information must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0054] The following details the various implementation details of the technical solutions in the embodiments of this application:

[0055] like Figure 2 As shown, Figure 2 This is a flowchart illustrating a message processing method according to an embodiment of this application. This method can be applied to... Figure 1 The message processing system shown can be executed by a terminal device or a server, or by both a terminal device and a server. In this embodiment, the method is described as being executed by a terminal device. The message processing method may include steps S201 to S203, which are described in detail below:

[0056] S201. Based on the mapping relationship between sessions and do-not-disturb time periods, obtain the target do-not-disturb time period corresponding to the target session to which the current message to be pushed belongs.

[0057] In this embodiment, the mapping relationship includes multiple sessions and a do-not-disturb time period corresponding to each session. Sessions are the primary source of application messages; specifically, a session can be an in-app session, and a session can contain one or more session objects. For example, for social applications, it's necessary to push chat messages generated in chat sessions established with social friends; for shopping applications, it's necessary to push shopping messages generated in communication sessions established with merchants; for live streaming applications, a live room containing viewers and the host can be considered a session, and it may be necessary to push messages sent by the host or other viewers; for social applications, a session can also be established between the public account followed by the user and the user, and the public account needs to push some tweets, etc.

[0058] In addition, the do-not-disturb period is a time period. Specifically, the do-not-disturb period for a conversation can be a short period of time, such as 10 minutes, 9 to 10 pm, etc.; or it can be a long period of time, such as 1 day, 1 week, after 12 midnight tonight, etc.

[0059] In one embodiment, the mapping relationship between a session and a do-not-disturb period can be obtained by mapping the session identifier to a do-not-disturb period (such as a field representing a do-not-disturb period).

[0060] Specifically, the mapping relationship between sessions and do-not-disturb periods can be set manually or by terminal devices or servers in the message processing system, and is not limited here.

[0061] Optionally, a do-not-disturb time period can be set for each session based on at least one of the following information: the click frequency of each session in the application, historical click time points, the interface dwell time of each session, and the dwell time.

[0062] S202. If the current time is not within the target do-not-disturb time period, then push the message to be pushed.

[0063] In this application embodiment, the specific method for determining whether the current time point is within the do-not-disturb period may include: obtaining the start time point and end time point of the target do-not-disturb period; if the current time point reaches the start time point but does not reach the end time point, then it is determined that the current time point is within the target do-not-disturb period; if the current time point does not reach the start time point, or the current time point reaches the end time point, then it is determined that the current time point is not within the target do-not-disturb period.

[0064] In one embodiment, message push processing may include prompting an object to view the message. Specifically, a message notification for the message to be pushed may be generated and then output. For example, the push process for the message to be pushed may include at least one of the following: displaying the message to be pushed or a message notification for the message to be pushed on the lock screen; displaying the message to be pushed or a message notification for the message to be pushed in the message notification bar; displaying the message to be pushed or a message notification for the message to be pushed in the application interface; or increasing the number of unread messages in the icon area of ​​the application to which the message to be pushed belongs.

[0065] S203. If the current time is within the target do-not-disturb time period, then no push notifications will be sent.

[0066] In the embodiments of this application, the non-push processing of messages may include not providing notifications for the messages, or including the messages in the conversation. For example, the non-push processing of messages to be pushed may specifically include displaying a red dot indicating the presence of unread messages in the display area of ​​the conversation to which the message to be pushed belongs, not displaying the conversation to which the message to be pushed belongs, or only displaying the message to be pushed in the conversation interface of the conversation to which the message to be pushed belongs, etc., and is not limited thereto.

[0067] In one embodiment, step S201 mentions that a session may contain multiple session objects, such as in a group chat. In a group chat scenario, it is possible that most messages sent by session objects are unimportant to the user, but messages sent by certain session objects are important to the user, such as those from superiors or relatives.

[0068] Therefore, to ensure that users receive messages sent by important session objects in a timely manner and further improve the user experience, session priorities can be set for session objects. Specifically, the handling of not pushing messages can include: if the target session contains multiple session objects, and among these multiple session objects there is a target session object with a session priority greater than the preset priority, then the session object to which the message to be pushed is obtained; if the obtained session object does not match the target session object, then the message to be pushed is not pushed; if the obtained session object matches the target session object, then the message to be pushed is pushed.

[0069] The session priority can be set manually or by the terminal device or server in the message processing system; no limitation is made here.

[0070] In one embodiment, the reason why an object is used to set a session to Do Not Disturb is often because the session object in the session has sent too many unimportant messages, or the object needs a moment of peace and quiet; but this does not mean that the object wants to miss important messages in the session.

[0071] Therefore, in order to ensure that users receive important messages in a timely manner and further improve the user experience, the specific handling of not pushing messages can also include: performing information importance detection on the message to be pushed and obtaining the information detection result; if the information detection result indicates that the message to be pushed does not contain information with an importance greater than a preset importance threshold, then the message to be pushed will not be pushed; if the information detection result indicates that the message to be pushed contains information with an importance greater than a preset importance threshold, then the message to be pushed will be pushed.

[0072] The information importance detection may include detecting whether the message contains specified characters, or whether the semantics of the message matches the semantics of specified text, etc., which are not limited here. Accordingly, if the message contains specified characters or matches the semantics of specified text, its importance will increase. In addition, the preset importance threshold, specified characters, and specified text can be set manually or by the terminal devices or servers in the message processing system, which are not limited here.

[0073] In one embodiment, considering that not pushing messages that were not pushed during the do-not-disturb period after the corresponding do-not-disturb period has passed might cause users to miss messages, after step S203, if it is determined that the current time has reached the end time point included in the target do-not-disturb period, the message to be pushed can be pushed. Optionally, the message to be pushed may not be pushed even if the current time point has reached the end time point included in the target do-not-disturb period.

[0074] In one embodiment, considering that pushing all messages that were not pushed during the do-not-disturb period of the session at once after the do-not-disturb period has passed, the user needs to receive too many messages in a short period of time, which will also affect the user's experience.

[0075] Therefore, after detecting that the current time has reached the end time of the do-not-disturb period corresponding to any session, it is possible to retrieve any messages that were not pushed during the corresponding do-not-disturb period for that session; then, a notification message is generated based on the retrieved messages, wherein the message length of the notification message is shorter than the message length of the retrieved messages; finally, the notification message is pushed. It should be noted that the end time of the do-not-disturb period includes both cases where the current time is the end time and cases where the current time has exceeded the end time.

[0076] This involves performing semantic analysis on the acquired messages to obtain a summary text, which is then used as a prompt message. Optionally, when multiple messages are acquired, the summary texts corresponding to each message can be concatenated to obtain the prompt message, ensuring that the length of the prompt message is less than the total length of all acquired messages.

[0077] Specifically, by organizing messages that are not pushed during the do-not-disturb period into more concise notifications, users can quickly understand the message content without feeling annoyed, which helps improve the user experience. At the same time, it also helps users check these messages in a timely manner, thereby effectively preventing users from missing messages and further enhancing the user experience.

[0078] In this embodiment, by establishing a mapping relationship between sessions and do-not-disturb time periods, corresponding do-not-disturb time periods can be set for sessions. This allows for precise control over when messages generated within a session can be pushed and when they cannot, improving the flexibility and accuracy of setting do-not-disturb time periods and facilitating precise control of message pushes based on these periods. Furthermore, by subsequently detecting whether the current time point is within the target do-not-disturb time period to select whether to push the message, messages within the do-not-disturb time period will not be pushed to the user. This effectively reduces the frequency and number of messages pushed to the user, achieving session-level do-not-disturb management of push messages, which improves the flexibility and accuracy of message pushes and ultimately enhances the user experience.

[0079] In one embodiment of this application, another message processing method is provided, which can be applied to Figure 1 The message processing system shown can be executed by a terminal device or a server, or by both. In this embodiment, the method is described using an example of execution by a terminal device. Figure 3 As shown, a flowchart illustrating another message processing method is presented. Figure 2 The method shown is an extension of the one presented.

[0080] The specific steps S301 to S306 are detailed below:

[0081] S301. In response to a selection operation for a session, obtain the session identifier of the selected session.

[0082] In this embodiment, the session identifier is used to uniquely identify a session. The session identifier can be a session name, session number, etc., and is not limited here. The selection operation for a session can specifically be a click operation, confirmation operation, trigger operation, etc., on the session or session information settings interface, and is not limited here.

[0083] S302. In response to the time information editing operation for the selected session, obtain the do-not-disturb time period corresponding to the selected session.

[0084] In this embodiment, the time information editing operation may include at least one of editing the start time point and editing the end time point. Specifically, the editing operation may include at least one of operations such as selection, modification, addition, and deletion.

[0085] Optionally, the process of obtaining the do-not-disturb time period may specifically include: generating the do-not-disturb time period corresponding to the selected session in response to the start time point and end time point entered in the time information editing interface; wherein, the input start time point is the start time point of the generated do-not-disturb time period, and the input end time point is the end time point of the generated do-not-disturb time period.

[0086] Alternatively, in response to the end time entered in the time information editing interface, a do-not-disturb period corresponding to the selected session is generated. The generated do-not-disturb period begins at the current time and ends at the entered time. The current time is the start time of the generated do-not-disturb period, and the entered end time is the end time of the generated do-not-disturb period.

[0087] Alternatively, in response to the start time entered in the time information editing interface, the entered start time is used as the start time of the Do Not Disturb period corresponding to the selected session. Here, the entered start time is the start time of the Do Not Disturb period, and there is no end time within the Do Not Disturb period. In other words, the Do Not Disturb period obtained in this way represents all time after the entered start time.

[0088] In one embodiment, to facilitate users in quickly setting a do-not-disturb period, a recommended do-not-disturb period can be displayed so that users can quickly complete the do-not-disturb period setting by directly selecting the recommended do-not-disturb period.

[0089] The recommended do-not-disturb time period can be obtained based on the historical do-not-disturb time periods corresponding to the selected conversation. For example, if the user has set a do-not-disturb time period of 1 hour for the history of the conversation, then the 1 hour after the current time can be set as the do-not-disturb time period. Or, if the user usually sets a do-not-disturb time period of 13:00 to 14:00 for the conversation around 10:00 every day, then when the user opens the time information editing interface of the conversation around 10:00, the time period of 13:00 to 14:00 can be displayed as the recommended do-not-disturb time period.

[0090] Therefore, the terminal device can also display a time information editing interface, which includes a recommended time period for do-not-disturb; then, the terminal device can respond to the trigger operation for the recommended time period for do-not-disturb to obtain the do-not-disturb time period corresponding to the selected session.

[0091] For example, please see the appendix. Figure 4 The diagram illustrates a time information editing interface. After selecting a session using the object selection function, one can enter... Figure 4 The conversation information interface 401 is shown. At this time, the user can select the "Do Not Disturb" option in the conversation information interface 401 to set the messages generated in the selected conversation to be in a do-not-disturb state from the current time point; or select the "Conversation Break" option in the conversation information interface 401 to enter the time information editing interface 402.

[0092] like Figure 4 As shown, the time information editing interface 402 includes a start time editing area, an end time editing area, and a recommended time area. Users can set only the start time; for example, setting the start time to 15:00 will include the period after 15:00. Users can also set only the end time; for example, setting the end time to 14:00 will include the period from the current time (assuming 8:00) to 14:00. Users can also set both the start and end times.

[0093] Users can also select a time period from the recommended time range as the Do Not Disturb period. For example, if a user selects 1 hour, the period from 8:00 (the current time) to 9:00 will be the Do Not Disturb period; if a user selects "9:00-9:30", the period from 9:00 to 9:30 will be the Do Not Disturb period. Finally, after the user completes the setting of the Do Not Disturb period, they can select the "Confirm" button in time information editing interface 402 to confirm the setting.

[0094] S303. Based on the session identifier and the obtained do-not-disturb time period, obtain the mapping relationship between the selected session and the obtained do-not-disturb time period.

[0095] In this embodiment, the session identifier can be mapped to the acquired do-not-disturb time period to obtain the mapping relationship between the selected session and the acquired do-not-disturb time period. Specifically, the mapping relationship between the session identifier and the acquired do-not-disturb time period can be established by associating the session identifier with a time field used to represent the acquired do-not-disturb time period.

[0096] Optionally, to ensure the effectiveness and security of storage, avoid errors caused by interference from other operations or information, and facilitate the retrieval and updating of mapping relationships, the mapping relationships can be stored in persistent storage media such as databases.

[0097] In one embodiment, considering that the mapping relationship between sessions and historically set do-not-disturb time periods may already be stored, if the mapping relationship between the session and the new do-not-disturb time period is also stored, although the two mapping relationships should be based on the new do-not-disturb time period, the two mapping relationships may lead to incorrect judgments on whether to push messages generated in the session.

[0098] Therefore, based on the session identifier, the mapping relationship between the currently stored session and the do-not-disturb time period can be detected to obtain the relationship detection result. If the relationship detection result indicates that there is a target mapping relationship containing the session identifier, the do-not-disturb time period in the target mapping relationship is updated to the obtained do-not-disturb time period. If the relationship detection result indicates that there is no target mapping relationship containing the session identifier, the session identifier is mapped to the obtained do-not-disturb time period to obtain the mapping relationship between the selected session and the obtained do-not-disturb time period.

[0099] For details, please see the appendix. Figure 5 This illustrates a schematic diagram of the Do Not Disturb settings process. For example... Figure 5As shown in step 501, the object can select a specific session from the session list, which can be a session about other objects or groups, and set a do-not-disturb period for the selected session. After the object confirms the setting, as shown in step 502, the session thread managing the sessions in the terminal device can read the do-not-disturb information corresponding to the selected session from the storage medium (including a session ID and a field indicating the do-not-disturb period, equivalent to a mapping relationship between sessions and do-not-disturb period). Then, as shown in steps 503 to 506, if the session thread does not read the do-not-disturb information corresponding to the session, the do-not-disturb period set by the object is stored as the do-not-disturb information corresponding to the session in the storage medium; if the session thread reads the do-not-disturb information corresponding to the session, the do-not-disturb information corresponding to the session is updated based on the do-not-disturb period set by the object. The do-not-disturb information corresponding to the session can contain a session ID and a do-not-disturb period, so the update process can specifically be to update the do-not-disturb period contained in the do-not-disturb information to the do-not-disturb period set by the object.

[0100] S304. Based on the mapping relationship between sessions and do-not-disturb time periods, obtain the target do-not-disturb time period corresponding to the target session to which the current message to be pushed belongs.

[0101] In this application embodiment, the specific implementation of step S304 can be found in the specific implementation of step S201, and will not be repeated here.

[0102] S305. If the current time is not within the target do-not-disturb time period, push the message to be pushed.

[0103] In this embodiment of the application, when faced with a large number of sessions, if invalid session information is not deleted, too much data will be stored, resulting in session information storage bloat, which in turn affects the effectiveness of storage and system performance.

[0104] Therefore, considering the mapping relationship between the session and the do-not-disturb period, once the end time of the do-not-disturb period is reached at the current time, it will no longer have the effect of preventing push notifications of messages generated in the session, which means that the information is essentially invalid.

[0105] Therefore, to ensure the effectiveness of storage and system performance, if the current time point is not within the target do-not-disturb time period, the end time point contained in the target do-not-disturb time period can be obtained; if the current time point reaches the end time point, the mapping relationship containing the target do-not-disturb time period can be deleted.

[0106] The step of obtaining the termination time point included in the target do-not-disturb period can be performed after the step of pushing the message to be pushed, or it can be performed simultaneously with the step of pushing the message to be pushed.

[0107] Specifically, the reason why the current time point is not within the target "Do Not Disturb" period mainly includes two situations: one is that the current time point has not reached the start time point included in the target "Do Not Disturb" period, and the other is that the current time point has reached or exceeded the end time point included in the target "Do Not Disturb" period. The first situation indicates that the target "Do Not Disturb" period has not yet taken effect, and it will still be needed for subsequent detection and judgment, so the mapping relationship containing the target "Do Not Disturb" period cannot be deleted in this case. The second situation indicates that the target "Do Not Disturb" period has expired, and it will no longer be used for subsequent detection and judgment, so the mapping relationship containing the target "Do Not Disturb" period can be deleted in this case.

[0108] Furthermore, this method, which determines whether to push messages generated by a session based on the corresponding do-not-disturb period, and then determines whether to delete the mapping relationship for that session based on the current time and the end time of the do-not-disturb period, is a more lazy deletion method compared to directly checking whether the current time has reached the end time of the do-not-disturb period. This lazy deletion method can avoid the waste of computing resources caused by frequently checking whether the current time has reached the end time of the do-not-disturb period, and can also further avoid the pressure on system performance caused by frequently initiating deletion operations, which is conducive to improving system performance.

[0109] Optionally, the mapping relationship between sessions and do-not-disturb time periods can be periodically traversed to obtain the end time point included in the do-not-disturb time period in the currently traversed mapping relationship; if the current time point reaches the end time point, the currently traversed mapping relationship is deleted.

[0110] Optionally, the mapping relationship between sessions and do-not-disturb time periods can be traversed periodically to obtain the end time point included in the do-not-disturb time period in the currently traversed mapping relationship; if the current time point reaches the end time point, the currently traversed mapping relationship is deleted. Optionally, if it is detected that the current time point has reached the end time point in the do-not-disturb time period corresponding to any session, the mapping relationship for that session is deleted.

[0111] Furthermore, the aforementioned lazy deletion method can be combined with periodic or irregular deletion methods to promptly delete stored mapping relationships.

[0112] Furthermore, the specific implementation of step S305 can be found in the specific implementation of step S202, and will not be repeated here.

[0113] S306. If the current time is within the target do-not-disturb time period, then no push notifications will be sent.

[0114] In the embodiments of this application, the specific implementation of step S306 can be found in the specific implementation of step S203, and will not be repeated here.

[0115] For specific implementation details, please refer to the appendix. Figure 6 This illustrates a message push process. Figure 6 As shown in steps 601 to 602, after the push system detects the session message to be pushed, it can obtain the do-not-disturb information contained in the session information. The do-not-disturb information may include the session ID and a field indicating the do-not-disturb time period.

[0116] Subsequently, as shown in steps 603 to 605, the push system can further compare the do-not-disturb time period included in the do-not-disturb information with the current time. If the current time reaches the start time of the do-not-disturb time period but not the end time, it indicates that the current time is within the do-not-disturb time period, and therefore the detected conversation messages are not pushed. If the current time does not reach the start time of the do-not-disturb time period, or reaches the end time of the do-not-disturb time period, it indicates that the current time is not within the do-not-disturb time period, and therefore the detected conversation messages are pushed; wherein, the push system can push the conversation messages to the target based on the content of the conversation messages.

[0117] Step 305 mentions that after determining the end time of the do-not-disturb period, to ensure storage effectiveness and system performance, the corresponding mapping relationship can be deleted. For practical applications, please refer to the appendix. Figure 7 The diagram illustrates a process for lazy deletion of Do Not Disturb messages. As shown in steps 701 to 704, after the push system detects session message A, it obtains the Do Not Disturb information for the session to which session message A belongs; after detecting that the current time point is within the Do Not Disturb time period corresponding to the session based on the obtained Do Not Disturb information, it does not push session message A.

[0118] After this, the do-not-disturb information for the session to which session message A belongs remains stored in the storage medium until session message B generated in that session is received. As shown in steps 705 to 709, after the push system detects session message B, it obtains the do-not-disturb information for the session to which session message B belongs. If, based on the obtained do-not-disturb information, the system detects that the current time is not within the do-not-disturb time period corresponding to the session and has exceeded the end time of the do-not-disturb time period, the push system can determine that the do-not-disturb information for the session has expired. Then, the push system sends a message to the cleanup information thread indicating that the do-not-disturb information for the session has expired and needs to be deleted, thereby triggering the cleanup information thread to delete the do-not-disturb information for the session from the storage medium.

[0119] Furthermore, step S305 mentions that the mapping between sessions and do-not-disturb periods can be periodically deleted. For practical applications, please refer to the appendix. Figure 8 This diagram illustrates a process for periodically deleting Do Not Disturb messages. As shown in steps 801-802, a timer in the terminal device initiates a daily task to delete expired messages. The message cleanup thread responds to this task by reading the Do Not Disturb messages for all sessions. Then, as shown in steps 803-805, the message cleanup thread iterates through and checks the Do Not Disturb time periods for all sessions. It determines whether the Do Not Disturb messages for each session have expired by checking if the current time exceeds the end time of the Do Not Disturb time period for each session. If it does, the messages are expired; otherwise, they are not. The message cleanup thread then deletes the expired Do Not Disturb messages from the storage medium, thereby updating the Do Not Disturb messages stored in the storage medium.

[0120] In this embodiment, by responding to selection operations and time information editing operations, the user can set precise do-not-disturb time periods according to their needs through interaction with the terminal device. This prevents the user from being disturbed by specific messages during specific time periods, thereby precisely controlling the timing of message pushes. Furthermore, by setting do-not-disturb time periods for a conversation, and subsequently determining whether to push a message based on the current time and the do-not-disturb time period, this embodiment achieves conversation-level message noise reduction during message pushes. This personalized, conversation-level message noise reduction mechanism avoids message overload, reduces the pressure on the user to receive messages, and improves the user experience. It also reduces resource consumption on the terminal and in terms of memory, helping to prevent system crashes.

[0121] Furthermore, in this embodiment, expired do-not-disturb time period-related mapping relationships can be promptly deleted using lazy deletion, periodic deletion, etc., which can prevent invalid information about the session from occupying storage space, thereby solving the problem of personal session information storage expansion. At the same time, the lazy deletion mechanism avoids frequent deletion operations, which is beneficial to improving system performance, while the periodic deletion mechanism can periodically clean up expired information, which is beneficial to maintaining storage effectiveness and improving system performance.

[0122] In summary, the message denoising solution at the session granularity proposed in this application prioritizes personalized message denoising, precise push control, storage optimization, and adaptability, and can provide users with better message management and user experience.

[0123] This application describes an apparatus embodiment that can be used to execute the message processing method described above. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the message processing method described above.

[0124] This application provides a message processing device, such as... Figure 9 As shown, the device includes a detection unit 901, an acquisition unit 902, and a storage unit 903, wherein:

[0125] The detection unit 901 is used to obtain the target do-not-disturb time period corresponding to the target session to which the current message to be pushed belongs, based on the mapping relationship between sessions and do-not-disturb time periods; wherein, the mapping relationship includes multiple sessions and the do-not-disturb time period corresponding to each of the multiple sessions;

[0126] The first push unit 902 is used to push a message to be pushed if it is detected that the current time point is not within the target do-not-disturb time period.

[0127] The second push unit 903 is used to not push the message to be pushed if it is detected that the current time point is within the target do-not-disturb time period.

[0128] In one embodiment of this application, based on the aforementioned scheme, before obtaining the target do-not-disturb time period corresponding to the target session to which the current push message belongs based on the mapping relationship between the session and the do-not-disturb time period, the detection unit 901 may further be used to: obtain the session identifier of the selected session in response to the session selection operation; obtain the do-not-disturb time period corresponding to the selected session in response to the time information editing operation of the selected session; and obtain the mapping relationship between the selected session and the obtained do-not-disturb time period based on the session identifier and the obtained do-not-disturb time period.

[0129] In one embodiment of this application, based on the aforementioned scheme, when the detection unit 901 obtains the do-not-disturb time period corresponding to the selected session in response to the time information editing operation for the selected session, it can specifically be used to: generate the do-not-disturb time period corresponding to the selected session in response to the start time point and end time point entered in the time information editing interface; or, generate the do-not-disturb time period corresponding to the selected session in response to the end time point entered in the time information editing interface; wherein, the generated do-not-disturb time period starts from the current time point and ends at the entered time point; or, in response to the start time point entered in the time information editing interface, use the entered start time point as the start time point of the do-not-disturb time period corresponding to the selected session.

[0130] In one embodiment of this application, based on the aforementioned scheme, when the detection unit 901 obtains the do-not-disturb time period corresponding to the selected session in response to an information editing operation for the selected session, it can specifically be used to: display a time information editing interface, which includes a recommended do-not-disturb time period obtained based on the historical do-not-disturb time period corresponding to the selected session; and obtain the do-not-disturb time period corresponding to the selected session in response to a trigger operation for the recommended do-not-disturb time period.

[0131] In one embodiment of this application, based on the aforementioned scheme, when the detection unit 901 obtains the mapping relationship between the selected session and the obtained do-not-disturb time period based on the session identifier and the obtained do-not-disturb time period, it can specifically be used to: detect the mapping relationship between the currently stored session and the do-not-disturb time period based on the session identifier, and obtain a relationship detection result; if the relationship detection result indicates that there is a target mapping relationship containing the session identifier, then update the do-not-disturb time period in the target mapping relationship to the obtained do-not-disturb time period; if the relationship detection result indicates that there is no target mapping relationship containing the session identifier, then map the session identifier to the obtained do-not-disturb time period to obtain the mapping relationship between the selected session and the obtained do-not-disturb time period.

[0132] In one embodiment of this application, based on the foregoing scheme, the detection unit 901 can also be used to: if the current time point is not within the target do-not-disturb time period, obtain the termination time point contained in the target do-not-disturb time period; if the current time point reaches the termination time point, delete the mapping relationship containing the target do-not-disturb time period.

[0133] In one embodiment of this application, based on the foregoing scheme, the detection unit 901 can also be used to: periodically traverse the mapping relationship between sessions and do-not-disturb time periods, obtain the termination time point included in the do-not-disturb time period in the currently traversed mapping relationship; if the current time point reaches the termination time point, delete the currently traversed mapping relationship.

[0134] In one embodiment of this application, based on the foregoing scheme, the second push unit 903 can also be used to: if it is detected that the current time point has reached the end time point included in the target do-not-disturb time period, then obtain messages that the target session has not pushed during the target do-not-disturb time period; generate a prompt message based on the obtained messages, wherein the message length of the prompt message is less than the message length of the obtained messages; and push the prompt message.

[0135] In one embodiment of this application, based on the aforementioned scheme, when the second push unit 903 does not push the message to be pushed, it can be specifically used to: if the target session contains multiple session objects, and among the multiple session objects there is a target session object with a session priority greater than a preset priority, then obtain the session object to which the message to be pushed is sent; if the obtained session object does not match the target session object, then do not push the message to be pushed; if the obtained session object matches the target session object, then push the message to be pushed.

[0136] In one embodiment of this application, based on the aforementioned scheme, when the second push unit 903 does not push the message to be pushed, it can specifically be used to: perform information importance detection on the message to be pushed and obtain information detection results; if the information detection results indicate that the message to be pushed does not contain information with an importance greater than a preset importance threshold, then the message to be pushed is not pushed; if the information detection results indicate that the message to be pushed contains information with an importance greater than a preset importance threshold, then the message to be pushed is not pushed.

[0137] In one embodiment of this application, based on the aforementioned scheme, after the second push unit 903 states that if the current time point is within the target do-not-disturb time period, then the message to be pushed will not be pushed, it can also be used to: push the message to be pushed if the current time point reaches the end time point included in the target do-not-disturb time period.

[0138] It should be noted that the apparatus provided in the above embodiments and the method provided in the above embodiments belong to the same concept, and the specific way in which each module and unit performs operations has been described in detail in the method embodiments, and will not be repeated here.

[0139] The apparatus provided in the above embodiments can be located within a terminal device or a server. The apparatus provided in this application establishes a mapping relationship between sessions and do-not-disturb time periods, allowing for the setting of corresponding do-not-disturb time periods for sessions. This enables precise control over when messages generated in a session can be pushed and when they cannot, improving the flexibility and accuracy of setting do-not-disturb time periods and facilitating precise control of message pushes based on these periods. Furthermore, by detecting whether the current time point is within the target do-not-disturb time period to select whether to push the message, messages within the do-not-disturb time period are not pushed to the user. This effectively reduces the frequency and number of messages pushed to the user, achieving session-level do-not-disturb management of push messages, improving the flexibility and accuracy of message pushes, and ultimately enhancing the user experience.

[0140] Embodiments of this application also provide an electronic device, including one or more processors and a storage device, wherein the storage device is used to store one or more computer programs, which, when executed by one or more processors, cause the electronic device to implement the message processing method described above.

[0141] Figure 10 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown.

[0142] It should be noted that, Figure 10 The computer system 1000 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0143] like Figure 10 As shown, the computer system 1000 includes a central processing unit (CPU) 1001, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on a program stored in read-only memory (ROM) 1002 or a program loaded from storage portion 1008 into random access memory (RAM) 1003. The RAM 1003 also stores various programs and data required for system operation. The CPU 1001, ROM 1002, and RAM 1003 are interconnected via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0144] In some embodiments, the following components are connected to the I / O interface 1005: an input section 1006 including a keyboard, mouse, etc.; an output section 1007 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 1010 as needed so that computer programs read from it can be installed into the storage section 1008 as needed.

[0145] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as a computer program. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1009, and / or installed from removable medium 1011. When the computer program is executed by processor (CPU) 1001, it performs various functions defined in the system of this application.

[0146] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory, flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

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

[0148] The units or modules described in the embodiments of this application can be implemented in software or hardware, and can also be located in a processor. The names of these units or modules do not necessarily limit the specific unit or module itself.

[0149] Another aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned message processing method. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not assembled into the electronic device.

[0150] Another aspect of this application provides a computer program product comprising a computer program stored in a computer-readable storage medium. A processor of an electronic device reads the computer program from the computer-readable storage medium and executes the computer program, causing the electronic device to perform the message processing method as described above in the various embodiments.

[0151] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0152] Other embodiments of this application will readily conceive of by considering the specification and practicing the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0153] The above content is merely a preferred exemplary embodiment of this application and is not intended to limit the implementation of this application. Those skilled in the art can easily make corresponding modifications or alterations based on the main concept and spirit of this application. Therefore, the scope of protection of this application should be determined by the scope of protection claimed in the claims.

Claims

1. A message processing method, characterized in that, include: Based on the mapping relationship between sessions and do-not-disturb time periods, the target do-not-disturb time period corresponding to the target session to which the current message to be pushed belongs is obtained; wherein, the mapping relationship includes multiple sessions and the do-not-disturb time period corresponding to each of the multiple sessions; If the current time is not within the target do-not-disturb time period, then the message to be pushed will be sent. If the current time is within the target do-not-disturb period, the message to be pushed will not be pushed.

2. The method according to claim 1, characterized in that, Before obtaining the target do-not-disturb time period corresponding to the target session to which the current push message belongs based on the mapping relationship between the session and the do-not-disturb time period, the method further includes: In response to a selection operation for a session, obtain the session identifier of the selected session; In response to the time information editing operation for the selected session, obtain the do-not-disturb time period corresponding to the selected session; Based on the session identifier and the obtained do-not-disturb time period, a mapping relationship between the selected session and the obtained do-not-disturb time period is obtained.

3. The method according to claim 2, characterized in that, The step of responding to the time information editing operation for the selected session and obtaining the do-not-disturb time period corresponding to the selected session includes: In response to the start and end times entered in the time information editing interface, generate the do-not-disturb time period corresponding to the selected session; Alternatively, in response to the end time point entered in the time information editing interface, a do-not-disturb period corresponding to the selected session is generated; wherein, the generated do-not-disturb period starts from the current time point and ends at the entered time point; Alternatively, in response to the start time point entered in the time information editing interface, the entered start time point is used as the start time point of the do-not-disturb time period corresponding to the selected session.

4. The method according to claim 2, characterized in that, The step of responding to the time information editing operation for the selected session and obtaining the do-not-disturb time period corresponding to the selected session includes: The time information editing interface is displayed, which includes a recommended time period for do-not-disturb based on the historical do-not-disturb time period corresponding to the selected session; In response to the trigger operation for the recommended do-not-disturb time period, the do-not-disturb time period corresponding to the selected session is obtained.

5. The method according to claim 2, characterized in that, The step of obtaining the mapping relationship between the selected session and the obtained do-not-disturb time period based on the session identifier includes: Based on the session identifier, the mapping relationship between the currently stored session and the do-not-disturb time period is detected to obtain the relationship detection result; If the relationship detection result indicates the existence of a target mapping relationship containing the session identifier, then the do-not-disturb time period in the target mapping relationship is updated to the obtained do-not-disturb time period; If the relationship detection result indicates that there is no target mapping relationship containing the session identifier, then the session identifier is mapped to the obtained do-not-disturb time period to obtain the mapping relationship between the selected session and the obtained do-not-disturb time period.

6. The method according to claim 1, characterized in that, The method further includes: If it is detected that the current time point is not within the target do-not-disturb time period, then the end time point contained in the target do-not-disturb time period is obtained; If the current time point reaches the termination time point, then delete the mapping relationship containing the target do-not-disturb time period.

7. The method according to claim 1, characterized in that, The method further includes: Periodically traverse the mapping relationship between sessions and do-not-disturb time periods, and obtain the end time point included in the do-not-disturb time period in the currently traversed mapping relationship; If the current time point reaches the termination time point, then the mapping relationship of the current traversal is deleted.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: If the current time point is detected to have reached the end time point contained in the target do-not-disturb time period, then the messages that were not pushed to the target session during the target do-not-disturb time period are obtained. A prompt message is generated based on the obtained message, and the message length of the prompt message is less than the message length of the obtained message; The notification message is pushed out.

9. The method according to any one of claims 1 to 7, characterized in that, The statement that the message to be pushed is not pushed includes: If the target session contains multiple session objects, and among the multiple session objects there is a target session object with a session priority greater than a preset priority, then the session object to which the push message is to be sent is obtained; If the obtained session object does not match the target session object, the message to be pushed will not be pushed.

10. The method according to any one of claims 1 to 7, characterized in that, The statement that the message to be pushed is not pushed includes: The message to be pushed is subjected to information importance detection to obtain the information detection result; If the information detection result indicates that the message to be pushed does not contain information with an importance greater than a preset importance threshold, then the message to be pushed will not be pushed.

11. The method according to any one of claims 1 to 7, characterized in that, After stating that if the current time point is within the target do-not-disturb time period, the method will not push the message to be pushed, the method further includes: If the current time reaches the end time point included in the target do-not-disturb period, then the message to be pushed will be sent.

12. A message processing device, characterized in that, The device includes a detection unit, a first push unit, and a second push unit, wherein: The detection unit is used to obtain the target do-not-disturb time period corresponding to the target session to which the current message to be pushed belongs, based on the mapping relationship between sessions and do-not-disturb time periods; wherein, the mapping relationship includes multiple sessions and the do-not-disturb time period corresponding to each of the multiple sessions; The first push unit is used to push the message to be pushed if the current time is not within the target do-not-disturb time period; The second push unit is configured to not push the message to be pushed if the current time point is within the target do-not-disturb time period.

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

14. An electronic device, characterized in that, include: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the one or more processors to implement the message processing method as described in any one of claims 1 to 11.

15. A computer program product, characterized in that, The computer program product includes a computer program adapted to be loaded by a processor and executed as any one of claims 1 to 11.

Images