Message management method, terminal, electronic device and readable storage medium

Abstract

The application discloses a message management method, a terminal, an electronic device and a readable storage medium, and belongs to the technical field of information processing. The message management method provided by the application comprises the following steps: displaying at least one message type identifier and at least one notification message of a message type indicated by each message type identifier; receiving a first input of a user on a first message type identifier in the at least one message type identifier; and in response to the first input, performing notification message processing on the at least one notification message of the message type indicated by the first message type identifier. The notification message processing comprises any one of the following: message clearing processing and message reminding processing.

Description

Technical Field

[0001] This application belongs to the field of information processing technology, specifically relating to a message management method, a terminal, an electronic device, and a readable storage medium. Background Technology

[0002] Typically, if a user wants to control an electronic device to perform management operations on multiple notification messages in the notification bar, such as wanting to control the electronic device to clear multiple notification messages in the notification bar, the user needs to first find each notification message one by one in the notification bar, and then perform operations on each notification message one by one to control the electronic device to clear each notification message.

[0003] However, since users may need a considerable amount of time to find each notification message in the notification bar and need to make multiple inputs to control the electronic device to perform management operations on each notification message, the user's operation is cumbersome and time-consuming in the process of controlling the electronic device to perform management operations on multiple notification messages in the notification bar. As a result, the user operation efficiency of notification message management is low. Summary of the Invention

[0004] The purpose of this application is to provide a message management method, terminal, electronic device, and readable storage medium that can improve the user operation efficiency of notification message management.

[0005] In a first aspect, embodiments of this application provide a message management method, the method comprising: displaying at least one message type identifier and at least one notification message of a message type indicated by each message type identifier; receiving a first input from a user on a first message type identifier among the at least one message type identifiers; and, in response to the first input, performing notification message processing on at least one notification message of the message type indicated by the first message type identifier. The notification message processing includes any one of the following: message clearing processing and message reminder processing.

[0006] Secondly, embodiments of this application provide a terminal, comprising: a display module for displaying at least one message type identifier and at least one notification message of the message type indicated by each message type identifier; a receiving module for receiving a first input from a user to a first message type identifier among the at least one message type identifiers displayed by the display module; and a processing module for performing notification message processing on at least one notification message of the message type indicated by the first message type identifier in response to the first input received by the receiving module. The notification message processing includes any one of the following: message clearing processing and message reminder processing.

[0007] Thirdly, embodiments of this application provide an electronic device including a processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0008] Fourthly, embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0009] Fifthly, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the steps of the method described in the first aspect.

[0010] In a sixth aspect, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the steps of the method described in the first aspect.

[0011] In this embodiment, the electronic device can first display at least one message type identifier and at least one notification message of the message type indicated by each message type identifier. Then, based on the user's first input to the first message type identifier among the at least one message type identifiers, notification message processing is performed on the at least one notification message of the message type indicated by the first message type identifier. This notification message processing includes at least one of message clearing processing and message reminder processing. Since the electronic device can categorize notification messages by displaying message type identifiers indicating message types, users can batch manage at least one notification message of any message type by inputting any message type identifier. This avoids the tedious process of searching for each notification message one by one from a large number of notification messages, thereby simplifying user operations for notification message management and improving user efficiency. Attached Figure Description

[0012] Figure 1 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0013] Figure 2 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0014] Figure 3 These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0015] Figure 4A These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0016] Figure 4B These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0017] Figure 5A These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0018] Figure 5B These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0019] Figure 6 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0020] Figure 7 These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0021] Figure 8 These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0022] Figure 9A These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0023] Figure 9B These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0024] Figure 10A These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0025] Figure 10B These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0026] Figure 11 These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0027] Figure 12 These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0028] Figure 13 These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0029] Figure 14 These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0030] Figure 15 These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0031] Figure 16These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0032] Figure 17 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0033] Figure 18A These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0034] Figure 18B These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0035] Figure 19A These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0036] Figure 19B These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0037] Figure 20 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0038] Figure 21A These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0039] Figure 21B These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0040] Figure 22 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0041] Figure 23 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0042] Figure 24A These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0043] Figure 24B These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0044] Figure 24C This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0045] Figure 25 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0046] Figure 26 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0047] Figure 27 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0048] Figure 28A These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0049] Figure 28B These are schematic diagrams of the interface of a mobile phone provided in some embodiments of this application;

[0050] Figure 28C This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0051] Figure 29 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0052] Figure 30 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0053] Figure 31 This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0054] Figure 32A This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0055] Figure 32B This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0056] Figure 32C This is a flowchart illustrating a message management method provided in some embodiments of this application;

[0057] Figure 33 These are schematic diagrams of the terminal structure provided in some embodiments of this application;

[0058] Figure 34 These are schematic diagrams of the hardware structure of electronic devices provided in some embodiments of this application;

[0059] Figure 35 These are schematic diagrams of the hardware structure of electronic devices provided in some embodiments of this application. Detailed Implementation

[0060] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0061] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class, without limiting the number of objects; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship. The identifiers in this application are text, symbols, images, etc., used to indicate information, and can use controls or other containers as carriers for displaying information, including but not limited to text identifiers, symbol identifiers, and image identifiers.

[0062] The terminology used in the embodiments of this application will be explained below.

[0063] 1. Push Program

[0064] Typically, push notification programs are applications installed on electronic devices that have push notification capabilities. In practical applications, these push notification programs include, but are not limited to, shopping push notification programs, payment push notification programs, navigation push notification programs, video push notification programs, and system push notification programs.

[0065] Among them, shopping-related push notifications include, but are not limited to, online retail platforms, direct-supply platforms, overseas goods purchasing platforms, and second-hand goods trading platforms; payment-related push notifications include, but are not limited to, the official applications of major banks and third-party payment platforms; navigation-related push notifications include, but are not limited to, map applications and food delivery applications; video-related push notifications include, but are not limited to, short video applications and online video playback platforms; and system-related push notifications include, but are not limited to, system browsers, system video software, system music software, app stores, and theme stores.

[0066] 2. Notification messages

[0067] Typically, when the aforementioned push notification program is installed on an electronic device, the program can recommend content to the user in the form of a notification message. The electronic device can then receive the notification message pushed by the program and output a reminder message to alert the user that the notification message has been received. The received notification message will also be displayed in the notification message display interface.

[0068] Notification messages can be categorized into at least one of the following message types based on their content: "Promotion" message type, "Reminder" message type, "Payment" message type, "Movies & TV" message type, "Navigation" message type, "Food Delivery" message type, "Important" message type, and "Regular" message type.

[0069] The message management method, terminal, electronic device, and readable storage medium provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0070] The message management method provided in this application can be applied to scenarios where users manage notification messages.

[0071] Typically, users install multiple push notification apps on their electronic devices, and each app sends notification messages to the device. This can result in multiple notification messages appearing on the notification display screen.

[0072] In one scenario, suppose a user wants to control an electronic device to clear certain notification messages. The user would first search for each notification message from the displayed list, then swipe right on one of those notifications to reveal a "clear" control, and then click the control to clear that notification. This process is repeated multiple times to clear all notifications. However, because it can take a considerable amount of time for the user to find each notification and requires multiple inputs to clear it, the process is cumbersome and time-consuming.

[0073] However, in some embodiments of this application, the electronic device categorizes the notification messages in the notification message display interface and displays at least one message type identifier and at least one notification message of the message type indicated by each message type identifier. In this way, the user can perform batch clearing of at least one notification message of any message type by entering any message type identifier once. Therefore, the tedious operation process of searching for each notification message one by one from a large number of notification messages is avoided, thereby simplifying the user operation of notification message management and improving the user operation efficiency of notification message management.

[0074] In another scenario, suppose a user wants to control an electronic device to send reminders for certain notifications. The user would first search for each notification from the displayed list, then tap on one of those notifications to display the push notification interface. They would then set a reminder time for that notification, repeating this process multiple times. However, because it might take a considerable amount of time for the user to find each notification and requires multiple inputs, controlling the device to send reminders for each notification is cumbersome and time-consuming.

[0075] However, in some embodiments of this application, the electronic device categorizes the notification messages in the notification message display interface and displays at least one message type identifier and at least one notification message of the message type indicated by each message type identifier. In this way, the user can perform batch reminder processing for at least one notification message of any message type by entering any message type identifier once. Therefore, it avoids the tedious operation process of the user searching for each notification message one by one from a large number of notification messages, thereby simplifying the user operation of notification message management and improving the user operation efficiency of notification message management.

[0076] The message management method provided in this application can be executed by a terminal, an electronic device, or a functional module or entity within an electronic device. This application uses an electronic device executing the message management method as an example to illustrate the message management method provided in this application.

[0077] Figure 1 A flowchart illustrating a message management method provided in an embodiment of this application is shown. Figure 1 As shown, the message management method provided in this application embodiment may include the following steps 101 to 103.

[0078] Step 101: The electronic device displays at least one message type identifier and at least one notification message of the message type indicated by each message type identifier.

[0079] In some embodiments of this application, the aforementioned at least one message type identifier may specifically include at least one of the following: type name, type icon, etc. For example, at least one message type identifier may include: "Reminder" message type name, "Promotion" message type name, and "Important" message type name, etc.

[0080] In one scenario, when the "Optimize Notification Bar Messages" function is enabled on an electronic device, if the number of notification messages in the notification message display interface is greater than or equal to a first quantity threshold, the electronic device can first determine at least one message type based on the message content of the notification messages in the notification message display interface, and generate a message type identifier for each message type. Thus, the electronic device can display at least one message type identifier and at least two first notification messages in the notification message display interface.

[0081] Specifically, the notification message display interface can be a notification bar interface or a negative one screen. It should be noted that the desktop of an electronic device includes at least one desktop page. Each desktop page can hold multiple program icons and desktop widgets. The first desktop page is the main screen, and the negative one screen is a page added to the left of the main screen to display some shortcut function icons and other information. That is, it is an interface displayed after swiping left on the main screen.

[0082] The first quantity threshold can be a user-preset threshold, and can be any integer value within a first quantity threshold range, specifically [1, 100]. For example, the first quantity threshold can be 5.

[0083] Optionally, the electronic device can input the message content of the notification message in the notification message display interface into the message type recognition model to obtain at least one message type output by the message type recognition model. This message type recognition model can be a model downloaded by the electronic device from a server, or a model pre-trained by the electronic device.

[0084] Specifically, the aforementioned message type identification model can be a text classification model, which can be any of the following: Text Convolutional Neural Networks (TextCNN) model, Deep Convolutional Neural Network (DCNN) model, Region Convolutional Neural Networks (RCNN) model, etc.

[0085] It should be noted that the description of the training message type recognition model for electronic devices can be found in the specific descriptions in related technologies, and will not be repeated here in the embodiments of this application.

[0086] In another scenario, when the "Optimize Notification Bar Messages" function is enabled on the electronic device, if the device receives user input in the notification message display interface, such as long press input, left swipe input, right swipe input, etc., the electronic device can first determine at least one message type based on the message content of the notification message in the notification message display interface, and generate a message type identifier based on each message type. Thus, the electronic device can display at least one message type identifier and at least two first notification messages in the notification message display interface.

[0087] In some embodiments of this application, step 101 described above can be implemented by step 101a as follows.

[0088] Step 101a: The electronic device displays at least one message type label and at least one message card.

[0089] In this embodiment of the application, each message type label includes a message type name, each message card corresponds to a notification message, and each message card displays a message summary of a notification message of a certain message type.

[0090] It should be noted that for each message type label in at least one message type label, a message type label can be understood as a specific implementation of "a message type identifier", for example... Figure 3 The labels shown are "Reminder" message type label 11, "Promotion" message type label 15, and "Important" message type label 19. For each message card in at least one message card, a message card can specifically be a card component with a card-like appearance, used to display a message summary of a notification message, so that the user can obtain the content of the notification message by viewing the message card, for example... Figure 3 The message cards 12, 13, and 14 shown are examples of this. In this embodiment, the card component is an interface component used for information output in the Android system. The card component can display text information, controls, etc., from any application.

[0091] Thus, since electronic devices can display the message type name of each message type identifier and the message summary information of each notification message of the message type indicated by each message type name, users can determine the location of a specific notification message they need by each message type name, and accurately find that specific notification message based on the message summary information displayed at that location, without having to view all notification messages one by one. Therefore, the time spent by users searching for the notification message they need can be reduced.

[0092] The following two different examples illustrate a specific scheme for an electronic device to display at least one message type identifier and at least one notification message of the message type indicated by each message type identifier.

[0093] Example 1

[0094] In some embodiments of this application, combined with Figure 1 ,like Figure 2 As shown, step 101 can be implemented in detail through steps 101b and 101c below.

[0095] Step 101b: The electronic device displays a first message type identifier in the first display area of ​​the notification message display interface, and displays at least one notification message of the first message type indicated by the first message type identifier in the adjacent display area of ​​the first display area.

[0096] In some embodiments of this application, the first display area mentioned above may specifically be a blank display area in the notification message display interface.

[0097] In some embodiments of this application, the notification message display interface includes multiple display areas, each display area being a blank display area in the notification message display interface. Each display area displays one of the above-mentioned at least one message type identifiers, and in the adjacent display areas of each display area, at least one notification message of the message type indicated by a message type identifier is displayed.

[0098] In some embodiments of this application, the aforementioned first message type identifier may specifically include at least one of the following: type name, type icon, etc.

[0099] It should be noted that the "adjacent display area of ​​the first display area" mentioned above can be understood as the display area within the preset range of the first display area.

[0100] In some embodiments of this application, the electronic device may display at least a portion of notification messages of a first message type, indicated by a first message type identifier, in an adjacent display area of ​​the first display area. It is understood that the aforementioned at least one notification message may be: all or part of the notification messages of the first message type.

[0101] In some embodiments of this application, the electronic device can display at least one notification message of the first message type in adjacent display areas of the first display area, either in a tiled display mode or a stacked display mode. It should be noted that the aforementioned "tiled display mode" can be understood as: at least one notification message of the first message type is located in different display positions in adjacent display areas of the first display area, and each notification message does not overlap, for example... Figure 5A As shown, the electronic device displays message cards 16, 17, and 18 in a tiled display manner. The aforementioned "layered display manner" can be understood as follows: at least one notification message of the first message type can be located in the same display position in the first display area, and each notification message at least partially overlaps, with each notification message having a different display layer, for example... Figure 3 As shown, the electronic device displays message cards 12, 13, and 14 in a stacked display manner. This display hierarchy can be the hierarchy of notification messages displayed by the electronic device; when at least one notification message overlaps, the notification message with the higher display hierarchy can obscure the notification message with the lower display hierarchy.

[0102] Optionally, if the number of at least one notification message of the first message type is less than the second quantity threshold, the electronic device may display at least one notification message of the first message type in a tiled display manner; if the number of at least one notification message of the first message type is greater than or equal to the second quantity threshold, the electronic device may display at least one notification message of the first message type in a stacked display manner.

[0103] The second quantity threshold can be a user-preset threshold, and can be any integer value within a range of second quantity thresholds, specifically [1, 100]. For example, the second quantity threshold can be 2.

[0104] Step 101c: If at least one message type identifier also includes a second message type identifier, the electronic device displays the second message type identifier in the second display area of ​​the notification message display interface, and displays at least one notification message of the second message type indicated by the second message type identifier in the adjacent display area of ​​the second display area.

[0105] It can be understood that the second display area mentioned above is the same as the display area in the at least one of the above display areas.

[0106] In some embodiments of this application, the aforementioned second message type identifier may specifically include at least one of the following: type name, type icon, etc.

[0107] In this embodiment of the application, when at least one message type identifier also includes a third message type identifier, the electronic device can display the third message type identifier in the third display area of ​​the notification message display interface, and display at least one notification message of the third message type indicated by the third message type identifier in the adjacent display area of ​​the third display area. Specifically, the third message type identifier may include at least one of the following: type name, type icon, etc.

[0108] For example, let's take a mobile phone as an example. Assume message types can include "reminder" message types, "promotion" message types, and "important" message types, such as... Figure 3 As shown, the mobile phone can display a "reminder" message type identifier in the first display area of ​​the notification message display interface 10, for example... Figure 3 The "Reminder" message type label 11 includes the message type name "Reminder" for notification messages of the "Reminder" message type. In an adjacent display area of ​​the first display area, at least one notification message card of the "Reminder" message type indicated by the "Reminder" message type label 11 is displayed, for example... Figure 3The notification display interface 10 includes message cards 12, 13, and 14. Message card 12 displays a message summary of a notification message of the "Reminder" message type: "Tomorrow's weather forecast: Tomorrow's weather in Shenzhen is sunny, temperature 12℃, humidity 1%." Message card 13 displays a message summary of another notification message of the "Reminder" message type, and message card 14 displays a message summary of yet another notification message of the "Reminder" message type. In the second display area of ​​the notification message display interface 10, a "Promotion" message type identifier is displayed, such as "Promotion" message type label 15. This "Promotion" message type label 15 includes the message type name "Promotion" for notification messages of the "Promotion" message type. In the adjacent display area of ​​the second display area, at least one notification message of the "Promotion" message type indicated by "Promotion" message type label 15 is displayed, such as message cards 16, 17, and 18. Message card 16 displays a message summary of a notification message of the "Promotion" message type: "Treasure Mall Limited-Time Special Offer, Please Pay Attention." The message card 17 displays a message summary of another notification message of the "Promotion" message type, and the message card 18 displays a message summary of yet another notification message of the "Promotion" message type. Additionally, in the third display area of ​​the notification message display interface 10, an "Important" message type identifier is displayed, such as an "Important" message type label 19. This "Important" message type label 19 includes the message type name "Important" for the notification message. In the adjacent display area of ​​this third display area, at least one notification message of the "Important" message type indicated by the "Important" message type label 19 is displayed, such as message card 20, message card 21, and message card 22. Message card 20 displays a message summary of an "Important" message message, "SMS verification code: 010586," message card 21 displays a message summary of another "Important" message message, and message card 22 displays a message summary of yet another "Important" message message.

[0109] Thus, since the electronic device can display each message type identifier in each display area of ​​the notification message display interface, and display at least one notification message of the message type indicated by each message type identifier in the adjacent display areas of each display area, the user can clearly determine each notification message of the message type indicated by each message type identifier, and accurately determine a certain message type identifier required by the user. Therefore, the user can control the electronic device to accurately manage the notification messages of a certain message type identifier required by the user in batches.

[0110] In some embodiments of this application, step 101a above can be specifically implemented by step 101a1 below.

[0111] Step 101a1: The electronic device displays a first message type identifier in the first display area of ​​the notification message display interface, and displays at least two notification messages of the first message type in a stacked display manner in the adjacent display areas of the first display area.

[0112] In this embodiment of the application, the display level of the notification message and the receiving time of the notification message are positively correlated in the above at least two notification messages.

[0113] It is understood that at least two notification messages of the first message type mentioned above can be located in the same display area, and these at least two notification messages can at least partially overlap. The notification message received earlier has a higher display hierarchy.

[0114] For example, combined with Figure 3The electronic device can display message cards 12, 13, and 14 in a stacked display manner. The notification message corresponding to message card 12 is received earlier than the notification message corresponding to message card 13, and the notification message corresponding to message card 13 is received earlier than the notification message corresponding to message card 14. Therefore, the display level of message card 12 is higher than that of message card 13, and the display level of message card 13 is higher than that of message card 14. That is, message card 12 can cover 90% or more of the card area of ​​message card 13, and message card 13 can cover 90% or more of the card area of ​​message card 14. Furthermore, the electronic device can display message cards 16, 17, and 18 in a stacked display manner. The notification message corresponding to message card 16 is received earlier than the notification message corresponding to message card 17, and the notification message corresponding to message card 17 is received earlier than the notification message corresponding to message card 18. Therefore, the display level of message card 16 is higher than that of message card 17, and the display level of message card 17 is higher than that of message card 18. That is, message card 16 can cover 90% or more of the card area of ​​message card 17, and message card 17 can cover 90% or more of the card area of ​​message card 18. Furthermore, the electronic device can display message cards 20, 21, and 22 in a stacked display manner. The notification message corresponding to message card 20 is received earlier than the notification message corresponding to message card 21, and the notification message corresponding to message card 21 is received earlier than the notification message corresponding to message card 22. Therefore, the display level of message card 20 is higher than that of message card 21, and the display level of message card 21 is higher than that of message card 22. That is, message card 20 can cover 90% or more of the card area of ​​message card 21, and message card 21 can cover 90% or more of the card area of ​​message card 22.

[0115] Thus, since the electronic device can display at least two notification messages of the first message type in a stacked display manner in adjacent display areas of the first display area, the display space of the notification message display interface can be saved, so that more message type identifiers and notification messages can be displayed in the notification message display interface.

[0116] Of course, after the electronic device displays the identifiers of each message type in each display area of ​​the notification message display interface, and displays at least two notification messages of each message type in the adjacent display areas of each display area, the user can also control the electronic device to perform different operations on the notification messages, as illustrated below.

[0117] In some embodiments of this application, after step 101a1 above, the message management method provided in the embodiments of this application may further include steps 201 to 202 as described below.

[0118] Step 201: The electronic device receives a second input from the user for at least two notification messages.

[0119] In one scenario, after an electronic device displays message type identifiers in various display areas of the notification message display interface and displays at least two notification messages of each message type in adjacent display areas of each display area, a user may not be interested in a certain notification message. In this case, the user may need to control the electronic device to clear that particular notification message, so the user can make a second input to the at least two notification messages to which that particular notification message belongs.

[0120] In another scenario, after the electronic device displays the message type identifiers in each display area of ​​the notification message display interface and displays at least two notification messages of each message type in the adjacent display areas of each display area, the user may have already clearly viewed the message content of a certain notification message. In this case, the user may need to control the electronic device to clear that notification message, so the user can make a second input to the at least two notification messages to which that notification message belongs.

[0121] In some embodiments of this application, the second input described above is used to control the electronic device to clear the notification message selected by the user.

[0122] In some embodiments of this application, the aforementioned second input may include, but is not limited to: touch input by the user in the input method interface, or voice commands input by the user, or specific gestures input by the user through a touch device such as a finger or stylus, or other feasible inputs. The specific input can be determined according to actual usage needs, and this application embodiment does not limit it. Among them, the aforementioned specific gestures can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure recognition gesture, a long-press gesture, an area change gesture, a double-press gesture, or a double-click gesture; the click input in the embodiments of this application can be a single-click input, a double-click input, or any number of clicks, and can also be a long-press input or a short-press input.

[0123] Step 202: In response to the second input, the electronic device clears the notification message with the highest display level from at least two notification messages.

[0124] In some embodiments of this application, after the electronic device clears the notification message with the highest display level among at least two notification messages, the electronic device can increase the display level of each notification message in at least one notification message. Here, the at least one notification message refers to the notification message other than the notification message with the highest display level displayed before user input, among the at least two notification messages.

[0125] For example, combined with Figure 3 ,like Figure 4A As shown, users can Figure 4A The user can perform a second input on any message card in the message list, for example, by swiping right on message card 16, so that the electronic device can respond to the user's right swipe input by clearing the notification message indicated by message card 16. Figure 4B As shown, after the user swipes right to input, the phone can clear the notification message indicated by message card 16, that is, cancel the display of message card 16 and delete the notification message indicated by message card 16 from the cache space of the electronic device, while maintaining the display of message cards 17 and 18, and raising the display level of message cards 17 and 18. After adjustment, the display level of message card 17 is higher than the display level of message card 18.

[0126] Thus, since users can clearly view the entire content of the highest-level notification message among the at least two notification messages, the electronic device, after receiving a second input from the user regarding the at least two notification messages, can determine that the user may need to clear the notification message that has already been clearly viewed and clear the notification message directly without requiring user input. Therefore, the operation of clearing notification messages can be simplified and time-consuming.

[0127] In some embodiments of this application, after step 101a above, the message management method provided in this application may further include steps 203 and 204 as described below.

[0128] Step 203: The electronic device receives a third input from the user for at least one notification message of the first message type.

[0129] In one scenario, after an electronic device displays various message type identifiers in different display areas of the notification message display interface, and displays at least two notification messages of each message type in adjacent display areas of each display area, the user may need to view each notification message of the first message type, thus allowing the user to make a third input on at least one notification message of the first message type.

[0130] In another scenario, after the electronic device displays each message type identifier in each display area of ​​the notification message display interface, and displays at least two notification messages of each message type in adjacent display areas of each display area, the user may need to perform an operation on a notification message of the first message type, thus allowing the user to make a third input on at least one notification message of the first message type.

[0131] In some embodiments of this application, the third input described above is used to control the electronic device to display all notification messages of the message type indicated by the message type identifier selected by the user.

[0132] In some embodiments of this application, the aforementioned third input may include, but is not limited to: touch input by the user in the input method interface, or voice commands input by the user, or specific gestures input by the user through a touch device such as a finger or stylus, or other feasible inputs. The specific input can be determined according to actual usage needs, and this application embodiment does not limit it. Among them, the aforementioned specific gestures can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure recognition gesture, a long-press gesture, an area change gesture, a double-press gesture, or a double-click gesture; the click input in the embodiments of this application can be a single-click input, a double-click input, or any number of clicks, and can also be a long-press input or a short-press input.

[0133] Step 204: In response to the third input, the electronic device displays all notification messages of the first message type in the notification message display interface.

[0134] In some embodiments of this application, the electronic device can update at least one message type identifier and at least one notification message of the message type indicated by each message type identifier to all notification messages of the first message type. The electronic device can then display all notification messages of the first message type in a tiled display manner.

[0135] For example, combined with Figure 3 ,like Figure 5A As shown, users can perform third-party input on message cards 16, 17, and 18, which are "Promotion" message type indicated by label 15, such as moving two fingers away from the input field, so that the phone can display message cards 16, 17, and 18. Figure 5B As shown, after the user moves two fingers away from the input field, the electronic device updates the display content of the notification message display interface 10 to only display the "Promotion" message type label 15, and displays message cards 16, 17 and 18 in a tiled display mode. Message card 16 displays the message summary information of a notification message of the "Promotion" message type: "Treasure Mall Limited-Time Special Offer: The product you are interested in has been reduced in price, come and grab it!" Message card 17 displays the message summary information of another notification message of the "Promotion" message type: "Wonder Mall: You have a red envelope to spend. The red envelope has been sent to your wallet. Click to view it!" Message card 18 displays the message summary information of yet another notification message of the "Promotion" message type: "Treasure Mall Headline: Come and participate in the flash sale!"

[0136] Thus, when a user requests to view all notification messages of the first message type, the user can make a third input on at least one notification message of the first message type, so that the electronic device can directly display all notification messages of the first message type without the user having to make multiple inputs. Therefore, the user operation of notification message management can be simplified and the user operation efficiency of notification message management can be improved.

[0137] Example 2

[0138] In some embodiments of this application, the aforementioned at least one message type identifier includes a first message type identifier, a second message type identifier, and a third message type identifier; the first message type identifier indicates a first message type, the second message type identifier indicates a second message type, and the third message type identifier indicates a third message type. Optionally, in combination with... Figure 1 ,like Figure 6 As shown, step 101 above can be implemented through step 101d below.

[0139] Step 101d: The electronic device displays a first message type identifier, a second message type identifier, and a third message type identifier in the identifier display area of ​​the notification message display interface. In the first sub-area of ​​the message display area in the notification message display interface, at least one notification message of the first message type is displayed. In the second and third sub-areas adjacent to the first sub-area, program icons of at least one push program that pushes the notification message of the second message type and program icons of at least one push program that pushes the notification message of the third message type are displayed respectively.

[0140] In this embodiment, the input selection may include, but is not limited to: touch input by the user in the input method interface, or voice commands input by the user, or specific gestures input by the user through a touch device such as a finger or stylus, or other feasible inputs. The specific input can be determined according to actual usage needs, and this embodiment does not limit it. The aforementioned specific gestures can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture. The click input in this embodiment can be a single-click input, a double-tap input, or any number of clicks, and can also be a long-press input or a short-press input.

[0141] In some embodiments of this application, the aforementioned identifier display area may specifically be a blank display area in the notification message display interface. The aforementioned first sub-region may be an adjacent display area of ​​the identifier display area.

[0142] In some embodiments of this application, the electronic device may display a first message type identifier, a second message type identifier, and a third message type identifier in an identifier display area according to a first direction, and in a second sub-area and a third sub-area adjacent to the first sub-area, respectively, program icons of at least one push notification program pushing notification messages of the second message type and program icons of at least one push notification program pushing notification messages of the third message type. The first direction may be a direction from one edge line of the electronic device's display screen to another non-adjacent edge line, for example, from the left edge line to the right edge line, or from the top edge line to the bottom edge line.

[0143] For example, such as Figure 7 As shown, the phone can display the identifier in the notification message display interface 10, for example... Figure 7 In the left-hand area, following a vertical direction from the top edge to the bottom edge, the first, second, and third message type identifiers are displayed. For example, "Reminder" message type label 23, "Promotion" message type label 24, and "Important" message type label 25 are displayed. The "Reminder" message type label 23 includes the message type name "Reminder," the "Promotion" message type label 24 includes the message type name "Promotion," and the "Important" message type label 25 includes the message type name "Important." In the first sub-area of ​​the message display area in the notification message display interface 10, at least one message card for the "Reminder" message type label 23 is displayed, such as message card 26, message card 27, and message card 28. These message cards 26, 27, and 28 are arranged vertically. Card 26 displays a message summary of a notification message of the "Reminder" type: "Weather: Tomorrow's weather forecast: Shenzhen will be sunny tomorrow, with a temperature of 12°C and humidity of 1%." Card 27 displays another notification message of the "Reminder" type: "Itinerary planning: Tomorrow's itinerary: From 8:00 to 10:00, I will go to the city park." Card 28 displays yet another notification message of the "Reminder" type: "Itinerary planning: Today's itinerary: From 1:00 to 18:00, I will go to the Central Building." In the second and third sub-areas adjacent to the first sub-area, program icons for at least one push notification program that pushes "Promotion" type notification messages and at least one push notification program that pushes "Important" type notification messages are displayed, such as program icons 29 and 30 for pushing "Promotion" type notification messages and program icon 31 for pushing "Important" type notification messages.

[0144] For example, such as Figure 8 As shown, the phone can display the identifier in the notification message display interface 10, for example... Figure 8 In the central area, following a horizontal direction from the left edge to the right edge, the first message type identifier, the second message type identifier, and the third message type identifier are displayed. For example, "Reminder" message type label 32, "Promotion" message type label 33, and "Important" message type label 34 are displayed. The "Reminder" message type label 32 includes the message type name "Reminder" for notification messages of the "Reminder" message type. The "Promotion" message type label 33 includes the message type name "Promotion" for notification messages of the "Promotion" message type. The "Important" message type label 34 includes the message type name "Important" for notification messages of the "Important" message type. In the first sub-area of ​​the message display area in the notification message display interface 10, at least one message card of the "Reminder" message type label 32 is displayed, such as message card 35, message card 36, and message card 37. These message cards 35, 36, and 37 are arranged horizontally. Card 35 displays a message summary of a notification message of the "Reminder" type: "Weather: Tomorrow's weather forecast: Shenzhen will be sunny tomorrow, with a temperature of 12°C and humidity of 1%." Card 36 displays another notification message of the "Reminder" type: "Itinerary planning: Tomorrow's itinerary: From 8:00 to 10:00, I will go to the city park." Card 37 displays yet another notification message of the "Reminder" type: "Itinerary planning: Today's itinerary: From 1:00 to 18:00, I will go to the Central Building." In the second and third sub-areas adjacent to the first sub-area, program icons for at least one push notification program that pushes "Promotion" type notification messages and at least one push notification program that pushes "Important" type notification messages are displayed, such as program icons 38 and 39 for at least one push notification program that pushes "Promotion" type notification messages and program icon 40 for at least one push notification program that pushes "Important" type notification messages.

[0145] Thus, since the electronic device can display at least one message type identifier in one display area of ​​the message display interface, display at least one notification message with one message type identifier in another display area, and display the program icon of at least one push notification message with other message type identifiers in yet another display area, the user can clearly determine whether the user needs a specific notification message among the at least one notification message with one message type identifier, and whether the user needs a specific notification message among the notification messages with other message type identifiers, without the user needing to control the electronic device to open the push notification program and check the notification messages one by one. Therefore, the user's operation can be simplified in the process of searching for the desired notification message, and the time consumption can be reduced.

[0146] In some embodiments of this application, after step 101 above, the notification message management method provided in this application may further include steps 301 and 302 as described below.

[0147] Step 301: When the electronic device receives the user's selection input for the second message type identifier, it updates the display content of the first sub-area to at least one notification message of the second message type, and updates the display content of the second sub-area to the program icon of at least one push program that pushes the notification message of the first message type.

[0148] In one scenario, when a user needs to find a certain notification message, if the notification message of the first message type indicated by the first message type identifier does not exist, the user can select and input a second message type identifier so that the electronic device can update the display content of the first sub-area to at least one notification message of the second message type, and update the display content of the second sub-area to the program icon of at least one push program that pushed the notification message of the first message type.

[0149] In another scenario, when a user needs to view at least one notification message of the second message type indicated by the second message type identifier, the user can select the second message type identifier so that the electronic device can update the display content of the first sub-area to at least one notification message of the second message type, and update the display content of the second sub-area to the program icon of at least one push program that pushed the notification message of the first message type.

[0150] In this embodiment, the input is selected to switch the display notification message.

[0151] In some embodiments of this application, the input selection may include, but is not limited to: touch input by the user in the input method interface, or voice commands input by the user, or specific gestures input by the user through a touch device such as a finger or stylus, or other feasible inputs. The specific input can be determined according to actual usage needs, and this application embodiment does not limit it. Among them, the aforementioned specific gestures can be any one of the following: single-click gesture, swipe gesture, drag gesture, pressure recognition gesture, long-press gesture, area change gesture, double-press gesture, and double-click gesture; the click input in the embodiments of this application can be single-click input, double-click input, or any number of clicks, and can also be long-press input or short-press input.

[0152] For example, combined with Figure 7 ,like Figure 9A As shown, users can select and input information for the "Promotion" message type label 24, for example, by clicking to switch the displayed notification messages on the phone. Figure 9B As shown, after the user makes a selection input, the mobile phone can update the display content of the first sub-area to a message card of at least one notification message of the "Promotion" message type, such as message card 41, message card 42, and message card 43. Message cards 41, 42, and 43 are arranged vertically. Message card 41 displays the message summary information of a notification message of the "Reminder" message type, "Weather Tomorrow's Weather Forecast: Tomorrow's weather in Shenzhen is sunny, temperature 12℃, humidity 1%". Message card 42 displays the message summary information of another notification message of the "Reminder" message type, "Itinerary Planning Tomorrow's Itinerary: Tomorrow from 8:00 to 10:00, going to the city park". Message card 43 displays the message summary information of yet another notification message of the "Reminder" message type, "Itinerary Planning Today's Itinerary: Today from 1:00 to 18:00, going to the Central Building". The display content of the second sub-area is updated to the app icon of at least one push notification of the "Reminder" message type, such as app icon 44 and app icon 45.

[0153] For example, combined with Figure 8 ,like Figure 10A As shown, users can select and input information for the "Promotion" message type label 33, for example, by clicking to switch the displayed notification messages on the phone. Figure 10BAs shown, after the user makes a selection input, the mobile phone can update the display content of the first sub-area to a message card of at least one notification message of the "Promotion" message type, such as message card 46, message card 47, and message card 48. Message cards 46, 47, and 48 are arranged horizontally. Message card 46 displays the message summary information of a notification message of the "Promotion" message type, "Treasure Mall Limited-Time Special Offer: The items you are interested in have been reduced in price, come and grab them!" Message card 47 displays the message summary information of another notification message of the "Promotion" message type, "Wonder Mall: You have a red envelope to spend. The red envelope has been sent to your wallet. Click to view it!" Message card 48 displays the message summary information of yet another notification message of the "Promotion" message type, "Treasure Mall Headlines: Come and participate in the flash sale!" The mobile phone can also update the display content of the second sub-area to the program icon of at least one push notification message of the "Reminder" message type, such as program icon 49 and program icon 50.

[0154] Step 302: When the electronic device receives the user's selection input for the third message type identifier, it updates the display content of the first sub-area to at least one notification message of the third message type, and updates the display content of the third sub-area to the program icon of at least one push program that pushes the notification message of the first message type.

[0155] It should be noted that for the explanation of the selection input, please refer to the specific description in step 301, which will not be repeated here in the embodiments of this application.

[0156] Thus, since the electronic device can display at least one notification message of different message types in the first sub-area based on the user's selection input, and display the program icon of at least one push notification program of different message types in the adjacent area of ​​the first sub-area, the user can clearly determine whether there is a notification message of the user's needs among the at least one notification message of the currently displayed message type, and determine whether there is a notification message of the user's needs among the notification messages identified by other message types.

[0157] Of course, since some notification messages may have inaccurate message types, users can directly control their electronic devices to reset the message types of those notification messages. Examples will be given below.

[0158] In some embodiments of this application, after step 101 above, the message management method provided in this application may further include steps 401 and 402 as described below.

[0159] Step 401: The electronic device receives a notification message indicated by a first message type identifier and a fifth input of a second message type identifier from at least one message type identifier.

[0160] In one scenario, if a user finds that the message type of a notification message is inaccurate, the user can provide a fifth input: the notification message and the correct message type identifier.

[0161] In another scenario, where a user needs to set the message type of a notification message to the user's desired message type, the user can provide a fifth input for that notification message and the accurate message type identifier.

[0162] In some embodiments of this application, the fifth input described above is used to control the electronic device to reset the message type of the notification message.

[0163] In some embodiments of this application, the aforementioned fifth input may include, but is not limited to: touch input by the user in the input method interface, or voice commands input by the user, or specific gestures input by the user through a touch device such as a finger or stylus, or other feasible inputs. The specific input can be determined according to actual usage needs, and this application embodiment does not limit it. Among them, the aforementioned specific gestures can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure recognition gesture, a long-press gesture, an area change gesture, a double-press gesture, or a double-click gesture; the click input in the embodiments of this application can be a single-click input, a double-click input, or any number of clicks, and can also be a long-press input or a short-press input.

[0164] In one possible implementation of this application, the message summary information of all notification messages indicated by the first message type identifier in at least one of the aforementioned message type identifiers is displayed on the message card. Optionally, step 401 can be specifically implemented by step 401a or step 401b described below.

[0165] Step 401a: The electronic device receives a drag input from the user who drags a message card of a notification message indicated by a first message type identifier in at least one message type identifier onto a second message type identifier.

[0166] For example, combined with Figure 3 ,like Figure 11 As shown, users can drag a message card of a notification message indicated by the "Reminder" message type label 11 to the "Promotion" message type label 15, for example, drag message card 12 to the "Promotion" message type label 15.

[0167] For example, combined with Figure 7 ,like Figure 12As shown, users can drag a message card of a notification message indicated by the "Reminder" message type label 23 to the "Promotion" message type label 24, for example, drag message card 26 to the "Promotion" message type label 24.

[0168] Step 401b: The electronic device receives touch input from the user for a message card and a second message type identifier of a notification message indicated by a first message type identifier in at least one message type identifier.

[0169] In some embodiments of this application, the touch input described above can be a single click or a click input of a preset number of times.

[0170] For example, combined with Figure 3 ,like Figure 13 As shown, users can use touch input to input the message card of a notification message indicated by the "Reminder" message type label 11, for example, by double-tapping the message card 12, and then use touch input to input the "Promotion" message type label 15, for example, by clicking the "Promotion" message type label 15.

[0171] For example, combined with Figure 7 ,like Figure 14 As shown, users can use touch input to input messages of a notification message indicated by the "Reminder" message type label 23, such as double-tapping message card 26, and then use touch input to input messages of the "Promotion" message type label 24, such as single-tapping message card 24.

[0172] Thus, it can be seen that since users can control electronic devices to set the message type of the notification message selected by the fifth input to the second message type indicated by the second message type identifier through different inputs, the flexibility of user input can be improved.

[0173] Step 402: In response to the fifth input, the electronic device sets the message type of the notification message selected by the fifth input to the second message type indicated by the second message type identifier, and updates the notification message selected by the fifth input to the message display area corresponding to the second message type identifier.

[0174] In some embodiments of this application, when at least one notification message of the second message type indicated by the second message type identifier is displayed in the second display area of ​​the notification message display interface, the electronic device can update the notification message selected by the fifth input to the adjacent display area of ​​the second display area.

[0175] For example, combined with Figure 11 and Figure 13 After the user makes a fifth input to message card 12 and "promotion" message type label 15, such as Figure 15 As shown, the electronic device can display the message card 12 in an adjacent display area of ​​the second display area.

[0176] In some embodiments of this application, when at least one notification message of the second message type indicated by the second message type identifier is displayed in the first sub-area of ​​the notification message display interface, the electronic device can update the notification message selected by the fifth input to the first sub-area.

[0177] For example, combined with Figure 12 and Figure 14 After the user makes a fifth input on message card 26 and the "Promotion" message type label 24, such as Figure 16 As shown, in the case where the electronic device displays a message card of at least one notification message of the "promotion" message type in the first sub-area, the first sub-area includes message card 26.

[0178] Thus, since the electronic device can directly set the message type of a notification message to the second message type based on the user's fifth input of the first message type identifier and the second message type identifier, and display the notification message in the message display area corresponding to the second message type identifier, without requiring the user to make multiple inputs, the user's input during the process of resetting the message type of the notification message can be simplified and the time consumption can be reduced.

[0179] Step 102: The electronic device receives a first input from the user for a first message type identifier in at least one message type identifier.

[0180] In this embodiment of the application, the first input is used to select the message type identifier of the user's needs and the notification message processing of the needs.

[0181] In some embodiments of this application, the aforementioned first input may include one input or multiple sub-inputs. The aforementioned one input or each sub-input may include, but is not limited to: touch input by the user in the input method interface, or voice commands input by the user, or specific gestures input by the user through a touch device such as a finger or stylus, or other feasible inputs. The specific input can be determined according to actual usage needs, and this application embodiment does not limit it. The aforementioned specific gestures may be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture. The click input in this application embodiment may be a single-click input, a double-tap input, or any number of clicks, and may also be a long-press input or a short-press input.

[0182] Step 103: In response to the first input, the electronic device performs notification message processing on at least one notification message of the message type indicated by the first message type identifier.

[0183] In some embodiments of this application, the electronic device may first determine the notification message processing based on the first input, and then perform notification message processing on at least one notification message of the message type indicated by the first message type identifier.

[0184] Optionally, if the first input includes a single input, the electronic device can determine the notification message processing based on the input type of that single input. For example, if the single input is a swipe input, the electronic device can determine that the notification message processing is message clearing processing; if the single input is a double-tap input, the electronic device can determine that the notification message processing is message alert processing.

[0185] Optionally, when the first input includes multiple sub-inputs, the electronic device may first display at least one control based on a sub-input of the user for the first message type identifier, with each control corresponding to a different processing method, and then determine the processing method corresponding to a certain control as a notification message processing method based on another sub-input of the user for a certain control.

[0186] In this embodiment of the application, the above notification message processing includes any one of the following: message clearing processing and message reminder processing.

[0187] In some embodiments of this application, the message clearing process includes at least one of the following: timed message clearing, batch clearing by importance, and clearing by message type identifier. The message reminder process includes at least one of the following: time-based scheduled reminders and application-based scheduled reminders.

[0188] Therefore, since message clearing can be divided into at least one of the following methods: scheduled message clearing, batch clearing by importance, and clearing by message type, users can choose the clearing method according to their different needs, so that electronic devices can clear the notification messages according to the user's requirements. Similarly, message reminders can be divided into at least one of the following methods: scheduled reminders by time and scheduled reminders by application, so users can choose the reminder method according to their different needs, so that electronic devices can remind users of the notification messages according to their requirements.

[0189] This application provides a message management method. An electronic device can first display at least one message type identifier and at least one notification message of the message type indicated by each message type identifier. Then, based on a user's first input to a first message type identifier among the at least one message type identifiers, notification message processing is performed on at least one notification message of the message type indicated by the first message type identifier. This notification message processing includes at least one of message clearing processing and message reminder processing. Since the electronic device can categorize notification messages by displaying message type identifiers indicating message types, users can batch manage at least one notification message of any message type by inputting any message type identifier. This avoids the tedious process of searching for each notification message one by one from a large number of notification messages, thereby simplifying user operations for notification message management and improving user efficiency.

[0190] The following will use notification message processing as an example to illustrate the specific scheme for an electronic device to perform notification message processing on at least one notification message of the message type indicated by the first message type identifier.

[0191] Example 3

[0192] In some embodiments of this application, the notification message processing described above includes message clearing processing, which includes clearing processing based on message type identifier. Optionally, in conjunction with... Figure 1 ,like Figure 17 As shown, step 103 above can be specifically implemented through step 103a below.

[0193] Step 103a: In response to the first input, the electronic device clears all notification messages of the message type indicated by the first message type identifier, and maintains the display of all notification messages of the message type indicated by all message type identifiers other than the first message type identifier.

[0194] In one example, if the user does not care about notification messages of the message type indicated by the first message type identifier, the user can directly make a first input to the first message type identifier so that the electronic device can clear all notification messages of the message type indicated by the first message type identifier and maintain the display of all notification messages of the message type indicated by all message type identifiers other than the first message type identifier.

[0195] For example, combined with Figure 3 ,like Figure 18AAs shown, the user can make a first input to the "Promotion" message type label 15, such as by long-pressing, so that the electronic device can perform message clearing processing on all notification messages of the "Promotion" message type indicated by the "Promotion" message type label 15, such as... Figure 18B As shown, after the user makes the first input, the electronic device can directly clear all notification messages of the "promotion" message type indicated by the "promotion" message type identifier 15 from the notification message interface 10, that is, delete all notification messages of the "promotion" message type indicated by the "promotion" message type identifier 15 from the cache space of the electronic device, and cancel the display of message cards 16, 17 and 18, while maintaining the display of message cards 12, 13, 14, 20, 21 and 22.

[0196] For example, combined with Figure 7 ,like Figure 19A As shown, the user can make a first input to the "Promotion" message type label 24, such as by swiping left, so that the electronic device can perform message clearing processing on all notification messages of the "Promotion" message type indicated by the "Promotion" message type label 24, such as... Figure 19B As shown, after the user makes the first input, the electronic device can directly clear all notification messages of the "promotion" message type indicated by the "promotion" message type label 24 from the notification message display interface 10, that is, delete all notification messages of the "promotion" message type indicated by the "promotion" message type label 24 from the cache space of the electronic device, and cancel the display of message cards 41, 42, 43 and the "promotion" message type label 24, while maintaining the display of message cards 26, 27 and 28, that is, maintaining the display of message cards of at least one notification message of the "reminder" message type.

[0197] Thus, since the electronic device can clear all notification messages of the message type indicated by the first message type identifier based on a single input from the user, and maintain the display of all notification messages of the message type indicated by all message type identifiers other than the first message type identifier, it can clear the notification messages that the user needs to clear and retain the notification messages that the user does not need to clear, without requiring the user to perform multiple operations to control the electronic device to clear the notification messages that the user needs to clear one by one. Therefore, the time spent clearing the notification messages that the user needs to clear can be reduced.

[0198] Example 4

[0199] In some embodiments of this application, the notification message processing includes message clearing processing, which includes batch clearing processing based on importance; the at least one message type identifier includes a first message type identifier and a second message type identifier, wherein the first message type identifier indicates an important message type, and the second message type identifier indicates a normal message type. Optionally, in combination with... Figure 1 ,like Figure 20 As shown, before “perform notification message processing on at least one notification message of the message type indicated by the first message type identifier” in step 103 above, the message management method provided in this application embodiment further includes the following steps 501 and 502, and the above step 103 can be specifically implemented by the following step 103b.

[0200] Step 501: The electronic device responds to the first input and displays the message clearing control.

[0201] Step 502: The electronic device receives the user's fourth input to the message clearing control.

[0202] In some embodiments of this application, the fourth input described above is used to control the electronic device to clear notification messages in batches.

[0203] In some embodiments of this application, the aforementioned fourth input may include, but is not limited to: touch input by the user in the input method interface, or voice commands input by the user, or specific gestures input by the user through a touch device such as a finger or stylus, or other feasible inputs. The specific input can be determined according to actual usage needs, and this application embodiment does not limit it. Among them, the aforementioned specific gestures can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure recognition gesture, a long-press gesture, an area change gesture, a double-press gesture, or a double-click gesture; the click input in the embodiments of this application can be a single-click input, a double-click input, or any number of clicks, and can also be a long-press input or a short-press input.

[0204] For example, combined with Figure 3 ,like Figure 21A As shown, the user can make the first input on the "Important" message type label 19, such as by clicking the input button, so that the electronic device can display the message clearing control, such as... Figure 21B As shown, after the user makes the first input, the electronic device can display the "Clear Unimportant Messages" control 51, so that the user can make a fourth input to the "Clear Unimportant Messages" control 51.

[0205] Step 103b: In response to the fourth input, the electronic device clears all notification messages of the message type indicated by the second message type identifier, and maintains the display of all notification messages of the message type indicated by the first message type identifier.

[0206] For example, combined with Figure 21B ,like Figure 22 As shown, after the user makes a fourth input to the "Clear Unimportant Messages" control 51, the electronic device can clear all notification messages of the message type indicated by the "Reminder" message type label 11 and the "Promotion" message type label 15, and maintain the display of all notification messages of the "Important" message type indicated by the "Important" message type label 19. That is, it deletes all notification messages of the "Promotion" message type indicated by the "Reminder" message type label 11 and all notification messages of the "Promotion" message type indicated by the "Promotion" message type label 15 from the cache space of the electronic device, and maintains the display of message cards 20, 21 and 22.

[0207] Thus, since electronic devices can clear all notification messages of the normal message type with a single input from the user to the message clearing control, without requiring multiple inputs from the user, the user's input can be simplified and time-consuming in the process of clearing notification messages that the user does not need.

[0208] Example 5

[0209] In some embodiments of this application, the notification message processing includes message clearing processing, which includes timed message clearing processing. Optionally, in conjunction with... Figure 1 ,like Figure 23 As shown, before “perform notification message processing on at least one notification message of the message type indicated by the first message type identifier” in step 103 above, the message management method provided in this application embodiment further includes the following steps 601 and 602, and the above step 103 can be specifically implemented by the following step 103c.

[0210] Step 601: The electronic device responds to the first input and displays the timer duration setting control.

[0211] It is understandable that in this example, the first input may include multiple sub-inputs.

[0212] In this embodiment of the application, the aforementioned timer duration setting control is used to input the duration.

[0213] For example, combined with Figure 7 ,like Figure 24A As shown, the user can make a sub-input on the "Promotion" message type label 24, for example, by double-clicking the sub-input, so that the electronic device can display the "Function Options" interface 52, such as... Figure 24B As shown, the "Function Options" interface 52 includes an "Auto Clear" control 53, a "Time-Based Reminder" control 54, and an "Application-Based Reminder" control 55, allowing the user to make another sub-input to the "Auto Clear" control 53, such as... Figure 24C As shown, this allows the electronic device to display the timing duration setting control 56.

[0214] Step 602: The electronic device receives the duration entered by the user in the timer duration setting control.

[0215] Step 103c: After the duration specified by the user's input time in the timer duration setting control, clear all unread notification messages of the message type indicated by the first message type identifier, or clear all notification messages of the message type indicated by the first message type identifier.

[0216] For example, combined with Figure 24C ,like Figure 25 As shown, at 11:00, the user can enter a duration of "2 hours" in the timed duration setting control 56, so that the electronic device can clear all unread notification messages of the "Promotion" message type indicated by the "Promotion" message type label 24, or clear all notification messages of the "Promotion" message type indicated by the "Promotion" message type label 24, starting 2 hours after 11:00, i.e., at 13:00.

[0217] For example, combined with Figure 24C ,like Figure 26 As shown, the user can enter a duration of "4 hours" in the timed duration setting control 56 at 8:00, so that the electronic device can clear all unread notification messages of the "Promotion" message type indicated by the "Promotion" message type label 24, or clear all notification messages of the "Promotion" message type indicated by the "Promotion" message type label 24, 4 hours after 8:00, i.e., at 12:00.

[0218] Thus, since the electronic device can display a timeout duration setting control, allowing users to customize the time for clearing at least a portion of all notification messages of the message type indicated by the first message type identifier, the electronic device can automatically clear at least a portion of all notification messages of the message type indicated by the first message type identifier after the duration specified by the user in the timeout duration setting control. Therefore, the user-defined time for clearing notification messages is realized, making the time for clearing notification messages more flexible.

[0219] Example 6

[0220] In some embodiments of this application, the notification message processing described above includes message reminder processing, which includes time-based scheduled reminder processing. Optionally, in conjunction with... Figure 1 ,like Figure 27As shown, before “perform notification message processing on at least one notification message of the message type indicated by the first message type identifier” in step 103 above, the message management method provided in this application embodiment further includes the following steps 701 and 702, and the above step 103 can be specifically implemented by the following step 103d.

[0221] Step 701: The electronic device responds to the first input and displays the appointment time setting control.

[0222] It is understood that in this embodiment, the first input includes multiple sub-inputs.

[0223] In this embodiment, the time setting control is used to input the time.

[0224] For example, combined with Figure 7 ,like Figure 28A As shown, the user can make a sub-input on the "Promotion" message type label 24, such as by double-clicking, so that the electronic device can display the "Function Options" interface 57, such as... Figure 28B As shown, the "Function Options" interface 57 includes an "Auto Clear" control 58, a "Time-Based Reminder" control 59, and an "Application-Based Reminder" control 60, allowing the user to make another sub-input to the "Auto Clear" control 59, such as... Figure 28C As shown, this allows the electronic device to display the appointment time setting control 61.

[0225] Step 702: The electronic device receives the time point entered by the user in the appointment time setting control.

[0226] Step 103d: When the system time matches the time point, the electronic device outputs reminder information for all notification messages of the message type indicated by the first message type identifier.

[0227] It should be noted that "matching" in the embodiments of this application can be understood as: identical, or the difference between the two is less than or equal to a preset difference.

[0228] In some embodiments of this application, when the system time matches the time point, the electronic device may display a reminder message of all notification messages of the message type indicated by the first message type identifier, or play a first prompt voice, which is used to prompt all notification messages of the message type indicated by the first message type identifier.

[0229] For example, combined with Figure 28C ,like Figure 29As shown, the user can enter the time "14:30" in the appointment time setting control 61 so that the electronic device can output reminder information of all notification messages of the "promotion" message type indicated by the "promotion" message type label 24 when the system time is "14:30".

[0230] For example, combined with Figure 28C ,like Figure 30 As shown, the user can enter the time "18:00" in the appointment time setting control 61 so that the electronic device can output reminder information of all notification messages of the "promotion" message type indicated by the "promotion" message type label 24 when the system time is "18:00".

[0231] Thus, since electronic devices can display a scheduled time setting control, allowing users to customize the time of all notification messages of the message type indicated by the first message type identifier according to their needs, and when the system time of the electronic device matches the user-defined time, the electronic device can automatically output the prompt information of all notification messages of the message type indicated by the first message type identifier. Therefore, it realizes the user's ability to customize the reminder time of notification messages, making the way notification messages are reminded more flexible.

[0232] Example 7

[0233] In some embodiments of this application, the notification message processing described above includes message reminder processing, which includes application-based scheduled reminder processing. Optionally, in conjunction with... Figure 1 ,like Figure 31 As shown, before “perform notification message processing on at least one notification message of the message type indicated by the first message type identifier” in step 103 above, the message management method provided in this application embodiment further includes the following steps 801 and 802, and the above step 103 can be specifically implemented by the following step 103e.

[0234] Step 801: The electronic device displays at least one application identifier.

[0235] In this embodiment of the application, each application identifier is used to indicate a push program, and the at least one application identifier indicates a push program that pushes a notification message of the message type indicated by a first message type identifier.

[0236] It is understood that in this embodiment, the first input includes multiple sub-inputs.

[0237] For example, combined with Figure 7 ,like Figure 32AAs shown, the user can make a sub-input on the "Promotion" message type label 24, such as by double-clicking, so that the electronic device can display the "Function Options" interface 62, such as... Figure 32B As shown, the "Function Options" interface 62 includes an "Auto Clear" control 63, a "Remind by Time" control 64, and a "Remind by Application" control 65, allowing the user to make another sub-input to the "Remind by Application" control 65, such as... Figure 32C As shown, this allows the electronic device to display at least one application identifier, such as application identifier 66, application identifier 67, and application identifier 68.

[0238] Step 802: The electronic device receives the user's selection input for one of the at least one application identifiers.

[0239] Step 103e: When the push notification program indicated by the selected application identifier is running, the electronic device outputs a reminder message of the notification message pushed by the push notification program indicated by the selected application identifier among all notification messages of the message type indicated by the first message type identifier.

[0240] For example, combined with Figure 32C Users can select and input application identifier 66 so that when the electronic device runs the push program indicated by application identifier 66, the electronic device can output reminder messages of all notification messages of the "promotion" message type pushed by the push program.

[0241] Thus, since electronic devices can display at least one application identifier, allowing users to select the application identifier of the push notification program that needs to be reminded again, the electronic device can, while the push notification program is running, select the notification message pushed by the push notification program indicated by the selected application identifier from all notification messages of the message type indicated by the first message type identifier. Therefore, it is possible to enable users to customize the push notification program that reminds them of the notification message again, making the notification message reminder method more flexible.

[0242] The message management method provided in this application can be executed by a terminal. This application uses the execution of the message management method by a terminal as an example to illustrate the terminal provided in this application.

[0243] Figure 33 A schematic diagram of a possible structure of the terminal involved in an embodiment of this application is shown. For example... Figure 33As shown, terminal 50 may include: a display module 51, configured to display at least one message type identifier and at least one notification message of the message type indicated by each message type identifier; a receiving module 52, configured to receive a first input from a user regarding a first message type identifier among the at least one message type identifiers displayed by the display module 51; and a processing module 53, configured to perform notification message processing on at least one notification message of the message type indicated by the first message type identifier in response to the first input received by the receiving module 52. The notification message processing may include any one of the following: message clearing processing or message reminder processing.

[0244] This application provides a terminal that can classify notification messages by displaying message type identifiers indicating the message type. This allows users to batch manage at least one notification message of any message type by inputting any message type identifier, avoiding the tedious process of searching for each notification message one by one from a large number of notification messages. This simplifies user operations for notification message management and improves user efficiency for notification message management.

[0245] In one possible implementation, the display module 51 is specifically configured to display a first message type identifier in a first display area of ​​the notification message display interface, and display at least one notification message of the first message type indicated by the first message type identifier in an adjacent display area of ​​the first display area; and if at least one message type identifier also includes a second message type identifier, display a second message type identifier in a second display area of ​​the notification message display interface, and display at least one notification message of the second message type indicated by the second message type identifier in an adjacent display area of ​​the second display area.

[0246] In one possible implementation, the display module 51 is specifically used to display at least two notification messages of the first message type in a stacked display manner in adjacent display areas of the first display area. The display level of the notification messages is positively correlated with the reception time of the notification messages.

[0247] In one possible implementation, the receiving module 52 is further configured to receive a second input from the user regarding the at least two notification messages after displaying them in a stacked manner in an adjacent display area of ​​the first display area. The processing module 53 is further configured to, in response to the second input received by the receiving module 52, clear the notification message with the highest display level among the at least two notification messages.

[0248] In one possible implementation, the receiving module 52 is further configured to, after displaying at least one notification message of the first message type indicated by the first message type identifier in an adjacent display area of ​​the first display area, receive a third input from the user regarding at least one notification message of the first message type. The display module 51 is further configured to, in response to the third input received by the receiving module 52, display all notification messages of the first message type in the notification message display interface.

[0249] In one possible implementation, the at least one message type identifier includes a first message type identifier, a second message type identifier, and a third message type identifier; the first message type identifier indicates a first message type, the second message type identifier indicates a second message type, and the third message type identifier indicates a third message type. The display module 51 is specifically configured to display the first message type identifier, the second message type identifier, and the third message type identifier in the identifier display area of ​​the notification message display interface; display at least one notification message of the first message type in a first sub-area of ​​the message display area of ​​the notification message display interface; and display the program icons of at least one push program that pushes the notification message of the second message type and the program icons of at least one push program that pushes the notification message of the third message type in the second and third sub-areas adjacent to the first sub-area, respectively.

[0250] In one possible implementation, the display module 51 is specifically configured to, after displaying at least one message type identifier and at least one notification message of the message type indicated by each message type identifier, upon receiving user input for selecting a second message type identifier, update the display content of the first sub-area to at least one notification message of the second message type and update the display content of the second sub-area to the program icon of at least one push notification program that pushes the notification message of the first message type; and upon receiving user input for selecting a third message type identifier, update the display content of the first sub-area to at least one notification message of the third message type and update the display content of the third sub-area to the program icon of at least one push notification program that pushes the notification message of the first message type.

[0251] In one possible implementation, the message clearing process includes at least one of the following: timed message clearing, batch clearing by importance, and clearing by message type identifier; the message reminder process includes at least one of the following: time-based scheduled reminder and application-based scheduled reminder.

[0252] In one possible implementation, the notification message processing includes message clearing processing, which includes clearing processing based on message type identifier. Specifically, the processing module 53 is used to clear all notification messages of the message type indicated by the first message type identifier, and to maintain the display of all notification messages of the message type indicated by at least one message type identifier other than the first message type identifier.

[0253] In one possible implementation, the notification message processing includes message clearing processing, which includes batch clearing processing based on importance; the at least one message type identifier includes a first message type identifier and a second message type identifier, wherein the first message type identifier indicates an important message type, and the second message type identifier indicates a normal message type. The receiving module 52 is further configured to receive a fourth input from the user to the message clearing control. The processing module 53 is further configured to, in response to the fourth input received by the receiving module 52, clear all notification messages of the message type indicated by the second message type identifier, and maintain the display of all notification messages of the message type indicated by the first message type identifier.

[0254] In one possible implementation, the notification message processing includes message clearing processing, which includes timed message clearing processing. The display module 51 is further configured to display a timed duration setting control before the processing module 53 performs notification message processing on at least one notification message of the message type indicated by the first message type identifier. The receiving module 52 is further configured to receive the duration input by the user in the timed duration setting control displayed by the display module 51. Specifically, the processing module 53 is configured to, after the receiving module 52 receives the duration from the time input by the user in the timed duration setting control, clear unread notification messages of all notification messages of the message type indicated by the first message type identifier, or clear all notification messages of the message type indicated by the first message type identifier.

[0255] In one possible implementation, the notification message processing includes message reminder processing, which includes time-based appointment reminder processing. The display module 51 is further configured to display an appointment time setting control before the processing module 53 performs notification message processing on at least one notification message of the message type indicated by the first message type identifier. The receiving module 52 is further configured to receive the time point entered by the user in the appointment time setting control displayed by the display module 51. Specifically, the processing module 53 is configured to output reminder information for all notification messages of the message type indicated by the first message type identifier when the system time matches the time point received by the receiving module 52.

[0256] In one possible implementation, the notification message processing includes message reminder processing, which includes application-based scheduled reminder processing. The display module 51 is further configured to display at least one application identifier before the processing module 53 performs notification message processing on at least one notification message of the message type indicated by the first message type identifier; the application identifier is used to indicate a push notification program, and the at least one application identifier indicates a push notification program that pushes notification messages of the message type indicated by the first message type identifier. The receiving module 52 is further configured to receive user selection input for one of the at least one application identifier displayed by the display module 51. Specifically, the processing module 53 is configured to, when the push notification program indicated by the application identifier selected by the receiving module 52 is running, output a reminder message for the notification message pushed by the push notification program indicated by the application identifier selected by the user among all notification messages of the message type indicated by the first message type identifier.

[0257] In one possible implementation, the receiving module 52 is further configured to receive a fifth input from the user regarding a notification message indicated by a first message type identifier and a second message type identifier, after the display module 51 displays at least one message type identifier and at least one notification message of the message type indicated by each message type identifier. The processing module 53 is further configured to, in response to the fifth input received by the receiving module 52, set the message type of the notification message selected by the fifth input to the second message type indicated by the second message type identifier, and update the notification message selected by the fifth input to the message display area corresponding to the second message type identifier.

[0258] In one possible implementation, message summary information of all notification messages indicated by the first message type identifier in the at least one message type identifier is displayed on the message card. Specifically, the receiving module 52 is configured to receive drag input from the user dragging the message card of a notification message indicated by the first message type identifier in the at least one message type identifier onto the second message type identifier; or, to receive touch input from the user on the message card of a notification message indicated by the first message type identifier in the at least one message type identifier and the second message type identifier.

[0259] In one possible implementation, the display module 51 is specifically used to display at least one message type label and at least one message card. Each message type label includes a message type name, each message card corresponds to a notification message, and each message card displays a message summary of a notification message of a specific message type.

[0260] The terminal in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television set (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the scope of the terminal.

[0261] The terminal in this application embodiment can be a device with an operating system. The operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system.

[0262] The terminal provided in this application embodiment can achieve... Figures 1 to 3 To avoid repetition, the various processes implemented in the method embodiment 2 will not be described again here.

[0263] In some embodiments of this application, such as Figure 34 As shown, this application embodiment also provides an electronic device 60, including a processor 61 and a memory 62. The memory 62 stores a program or instructions that can run on the processor 61. When the program or instructions are executed by the processor 61, they implement the various process steps of the above message management method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0264] It should be noted that the electronic devices in the embodiments of this application include the aforementioned mobile electronic devices and non-mobile electronic devices.

[0265] Figure 35 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application.

[0266] The electronic device 100 includes, but is not limited to, components such as: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0267] Those skilled in the art will understand that the electronic device 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 35 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0268] The display unit 106 is used to display at least one message type identifier and at least one notification message of the message type indicated by each message type identifier.

[0269] User input unit 107 is used to receive a first input from a user for a first message type identifier in at least one message type identifier.

[0270] Processor 110 is configured to perform notification message processing on at least one notification message of a message type indicated by a first message type identifier in response to a first input.

[0271] The aforementioned notification message processing includes any one of the following: message clearing processing and message reminder processing.

[0272] This application provides an electronic device that can classify notification messages by displaying message type identifiers indicating the message type. This allows users to batch manage at least one notification message of any message type by inputting any message type identifier, avoiding the tedious process of searching for each notification message one by one from a large number of notification messages. This simplifies user operations for notification message management and improves user efficiency for notification message management.

[0273] In some embodiments of this application, the display unit 106 is specifically configured to display a first message type identifier in a first display area of ​​the notification message display interface, and display at least one notification message of the first message type indicated by the first message type identifier in an adjacent display area of ​​the first display area; and if at least one message type identifier also includes a second message type identifier, display a second message type identifier in a second display area of ​​the notification message display interface, and display at least one notification message of the second message type indicated by the second message type identifier in an adjacent display area of ​​the second display area.

[0274] In some embodiments of this application, the display unit 106 is specifically used to display at least two notification messages of the first message type in a stacked display manner in an adjacent display area of ​​the first display area.

[0275] Among these, in at least two of the aforementioned notification messages, the display level of the notification message and the time of receipt of the notification message are positively correlated.

[0276] In some embodiments of this application, the user input unit 107 is also configured to receive a second input from the user for at least two notification messages.

[0277] The processor 110 is also configured to, in response to the second input, clear the notification message with the highest display level among at least two notification messages.

[0278] In some embodiments of this application, the user input unit 107 is further configured to receive a third input from the user for at least one notification message of the first message type.

[0279] The processor 110 is also configured to, in response to a third input, display all notification messages of the first message type in the notification message display interface.

[0280] In some embodiments of this application, the aforementioned at least one message type identifier includes a first message type identifier, a second message type identifier, and a third message type identifier; the first message type identifier indicates a first message type, the second message type identifier indicates a second message type, and the third message type identifier indicates a third message type.

[0281] The display unit 106 is specifically used to display a first message type identifier, a second message type identifier, and a third message type identifier in the identifier display area of ​​the notification message display interface; to display at least one notification message of the first message type in the first sub-area of ​​the message display area of ​​the notification message display interface; and to display program icons of at least one push program that pushes the notification message of the second message type and at least one push program that pushes the notification message of the third message type in the second sub-area and the third sub-area adjacent to the first sub-area, respectively.

[0282] In some embodiments of this application, the processor 110 is further configured to, upon receiving user input for selecting a second message type identifier, update the display content of the first sub-area to at least one notification message of the second message type and update the display content of the second sub-area to the program icon of at least one push notification program that pushes the notification message of the first message type; and upon receiving user input for selecting a third message type identifier, update the display content of the first sub-area to at least one notification message of the third message type and update the display content of the third sub-area to the program icon of at least one push notification program that pushes the notification message of the first message type.

[0283] In some embodiments of this application, the notification message processing described above includes message clearing processing, which includes message type identifier clearing processing.

[0284] The processor 110 is specifically configured to clear all notification messages of the message type indicated by the first message type identifier, and maintain the display of all notification messages of the message type indicated by at least one message type identifier other than the first message type identifier.

[0285] In some embodiments of this application, the notification message processing includes message clearing processing, which includes batch clearing processing based on importance; the at least one message type identifier includes a first message type identifier and a second message type identifier, wherein the first message type identifier indicates an important message type and the second message type identifier indicates a normal message type.

[0286] The user input unit 107 is also used to receive a fourth input from the user to the message clearing control.

[0287] The processor 110 is also configured to, in response to the fourth input, clear all notification messages of the message type indicated by the second message type identifier, and maintain the display of all notification messages of the message type indicated by the first message type identifier.

[0288] In some embodiments of this application, the notification message processing includes message clearing processing, which includes timed message clearing processing.

[0289] Display unit 106 is also used to display timer duration setting controls.

[0290] The user input unit 107 is also used to receive the duration entered by the user in the timed duration setting control.

[0291] The processor 110 is specifically configured to, after a certain period of time following the input time in the timer duration setting control, clear unread notification messages of all notification messages of the message type indicated by the first message type identifier, or clear all notification messages of the message type indicated by the first message type identifier.

[0292] In some embodiments of this application, the notification message processing described above includes message reminder processing, which includes time-based scheduled reminder processing.

[0293] Display unit 106 is also used to display the reservation time setting control.

[0294] The user input unit 107 is also used to receive the time point entered by the user in the appointment time setting control.

[0295] The processor 110 is specifically used to output reminder information for all notification messages of the message type indicated by the first message type identifier when the system time matches the time point.

[0296] In some embodiments of this application, the notification message processing described above includes message reminder processing, which includes application-based scheduled reminder processing.

[0297] The display unit 106 is also configured to display at least one application identifier; the application identifier is used to indicate a push program, the at least one application identifier indicating a push program that pushes a notification message of the message type indicated by a first message type identifier.

[0298] User input unit 107 is also configured to receive user input for selecting one of the application identifiers from at least one application identifier.

[0299] The processor 110 is specifically configured to, when the push notification program indicated by the selected application identifier is running, output a reminder message of the notification message pushed by the push notification program indicated by the selected application identifier among all notification messages of the message type indicated by the first message type identifier.

[0300] In some embodiments of this application, the user input unit 107 is further configured to receive a notification message indicated by a first message type identifier and a fifth input from a second message type identifier in at least one message type identifier.

[0301] The processor 110 is also configured to, in response to the fifth input, set the message type of the notification message selected by the fifth input to the second message type indicated by the second message type identifier, and update the notification message selected by the fifth input to the message display area corresponding to the second message type identifier.

[0302] In some embodiments of this application, the message summary information of all notification messages indicated by the first message type identifier in at least one of the above-mentioned message type identifiers is displayed on the message card.

[0303] The user input unit 107 is specifically configured to receive drag input from a user dragging a message card of a notification message indicated by a first message type identifier in at least one message type identifier onto a second message type identifier; or, to receive touch input from a user on a message card of a notification message indicated by a first message type identifier in at least one message type identifier and a second message type identifier.

[0304] In some embodiments of this application, the display unit 106 is specifically used to display at least one message type label and at least one message card.

[0305] Each message type label includes a message type name, each message card corresponds to a notification message, and each message card displays a message summary of a notification message of a certain message type.

[0306] It should be understood that, in this embodiment, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes at least one of a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0307] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 109 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM). The memory 109 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0308] Processor 110 may include one or more processing units; optionally, processor 110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0309] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described message management method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0310] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0311] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above message management method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0312] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0313] This application provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the message management method embodiment described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0314] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0315] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0316] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A message management method, characterized in that, The method includes: Display at least one message type identifier and at least one notification message of the message type indicated by each message type identifier; Receive a first input from the user for a first message type identifier among the at least one message type identifiers; In response to the first input, perform notification message processing on at least one notification message of the message type indicated by the first message type identifier; The notification message processing includes any one of the following: message clearing processing, message reminder processing; The at least one message type identifier includes a first message type identifier, a second message type identifier, and a third message type identifier; the first message type identifier indicates a first message type, the second message type identifier indicates a second message type, and the third message type identifier indicates a third message type. The at least one notification message displaying at least one message type identifier and the message type indicated by each message type identifier includes: In the identifier display area of ​​the notification message display interface, the first message type identifier, the second message type identifier, and the third message type identifier are displayed. In the first sub-area of ​​the message display area of ​​the notification message display interface, at least one notification message of the first message type is displayed. In the second and third sub-areas adjacent to the first sub-area, the program icons of at least one push program that pushes the notification message of the second message type and the program icons of at least one push program that pushes the notification message of the third message type are displayed respectively. Upon receiving a user's selection input for the second message type identifier, the display content of the first sub-area is updated to at least one notification message of the second message type, and the display content of the second sub-area is updated to the program icon of at least one push notification program that pushes the notification message of the first message type; Upon receiving user input selecting the third message type identifier, the display content of the first sub-area is updated to at least one notification message of the third message type, and the display content of the third sub-area is updated to the program icon of at least one push notification program that pushed the first message type notification message.

2. The method according to claim 1, characterized in that, The at least one notification message displaying at least one message type identifier and the message type indicated by each message type identifier includes: In the first display area of ​​the notification message display interface, the first message type identifier is displayed, and in the adjacent display area of ​​the first display area, at least one notification message of the first message type indicated by the first message type identifier is displayed; If the at least one message type identifier also includes a second message type identifier, the second message type identifier is displayed in the second display area of ​​the notification message display interface, and at least one notification message of the second message type indicated by the second message type identifier is displayed in the adjacent display area of ​​the second display area.

3. The method according to claim 2, characterized in that, The step of displaying at least one notification message of the first message type indicated by the first message type identifier in an adjacent display area of ​​the first display area includes: In the adjacent display areas of the first display area, at least two notification messages of the first message type are displayed in a stacked display manner; Among the at least two notification messages, the display level of the notification message and the reception time of the notification message are positively correlated.

4. The method according to claim 3, characterized in that, After displaying at least two notification messages of the first message type in a stacked display manner in adjacent display areas of the first display area, the method further includes: Receive a second input from the user regarding the at least two notification messages; In response to the second input, the notification message with the highest display level among the at least two notification messages is cleared.

5. The method according to claim 2, characterized in that, After displaying at least one notification message of the first message type indicated by the first message type identifier in an adjacent display area of ​​the first display area, the method further includes: Receive a third input from the user for at least one notification message of the first message type; In response to the third input, all notification messages of the first message type are displayed in the notification message display interface.

6. The method according to claim 1, characterized in that, The message clearing process includes at least one of the following: timed message clearing process, batch clearing process based on importance, and clearing process based on message type identifier; The message notification processing includes at least one of the following: time-based scheduled notification processing and application-based scheduled notification processing.

7. The method according to claim 6, characterized in that, The notification message processing includes the message clearing process, which includes clearing process based on the message type identifier. The step of performing notification message processing on at least one notification message of the message type indicated by the first message type identifier includes: Clear all notification messages of the message type indicated by the first message type identifier, and maintain the display of all notification messages of the message types indicated by all message type identifiers other than the first message type identifier among the at least one message type identifier.

8. The method according to claim 6, characterized in that, The notification message processing includes the message clearing process, which includes the batch clearing process based on importance; the at least one message type identifier includes a first message type identifier and a second message type identifier, wherein the first message type identifier indicates an important message type and the second message type identifier indicates a normal message type; The method further includes: Receive the user's fourth input to the message clearing control; In response to the fourth input, all notification messages of the message type indicated by the second message type identifier are cleared, while the display of all notification messages of the message type indicated by the first message type identifier is maintained.

9. The method according to claim 6, characterized in that, The notification message processing includes the message clearing process, which includes the timed message clearing process. Before performing notification message processing on at least one notification message of the message type indicated by the first message type identifier, the method further includes: Displays the timer duration setting control; Receive the duration input by the user in the timer duration setting control; The step of performing notification message processing on at least one notification message of the message type indicated by the first message type identifier includes: After the specified duration starting from the time entered by the user in the timed duration setting control, clear all unread notification messages of the message type indicated by the first message type identifier, or clear all notification messages of the message type indicated by the first message type identifier.

10. The method according to claim 6, characterized in that, The notification message processing includes the message reminder processing, and the message reminder processing includes the time-based scheduled reminder processing; Before performing notification message processing on at least one notification message of the message type indicated by the first message type identifier, the method further includes: Displays the reservation time setting control; Receive the time point entered by the user in the appointment time setting control; The step of performing notification message processing on at least one notification message of the message type indicated by the first message type identifier includes: If the system time matches the stated time, output reminder information for all notification messages of the message type indicated by the first message type identifier.

11. The method according to claim 6, characterized in that, The notification message processing includes the message reminder processing, and the message reminder processing includes the application-based scheduled reminder processing; Before performing notification message processing on at least one notification message of the message type indicated by the first message type identifier, the method further includes: Display at least one application identifier; the application identifier is used to indicate a push program, the at least one application identifier indicating a push program that pushes the notification message of the message type indicated by the first message type identifier; Receive user input selecting one of the at least one application identifiers; The step of performing notification message processing on at least one notification message of the message type indicated by the first message type identifier includes: When the push notification program indicated by the application identifier selected by the selection input is running, a reminder message is output, which is the notification message pushed by the push notification program indicated by the application identifier selected by the selection input, among all notification messages of the message type indicated by the first message type identifier.

12. The method according to claim 1, characterized in that, After displaying at least one notification message of at least one message type identifier and the message type indicated by each message type identifier, the method further includes: Receive a notification message from the user indicating a first message type identifier and a fifth input indicating a second message type identifier among the at least one message type identifier; In response to the fifth input, the message type of the notification message selected by the fifth input is set to the second message type indicated by the second message type identifier, and the notification message selected by the fifth input is updated in the message display area corresponding to the second message type identifier.

13. The method according to claim 12, characterized in that, The message summary information of all notification messages indicated by the first message type identifier in at least one message type identifier is displayed on the message card; The fifth input for receiving a notification message and a second message type identifier from the first message type identifier in the at least one message type identifier includes: The user drags a message card of a notification message indicated by a first message type identifier from the at least one message type identifier to a drag input on a second message type identifier; Alternatively, the user can receive touch input from a message card and a second message type identifier for a notification message indicated by a first message type identifier among the at least one message type identifier.

14. The method according to claim 1, characterized in that, The at least one notification message displaying at least one message type identifier and the message type indicated by each message type identifier includes: Display at least one message type label and at least one message card; Each message type label includes a message type name, each message card corresponds to a notification message, and each message card displays a message summary of a notification message of a certain message type.

15. A terminal, characterized in that, The terminal includes: The display module is used to display at least one message type identifier and at least one notification message of the message type indicated by each message type identifier; The receiving module is configured to receive a first input from the user to a first message type identifier among the at least one message type identifiers displayed by the display module; The processing module is configured to, in response to the first input received by the receiving module, perform notification message processing on at least one notification message of the message type indicated by the first message type identifier; The notification message processing includes any one of the following: message clearing processing, message reminder processing; The at least one message type identifier includes a first message type identifier, a second message type identifier, and a third message type identifier; the first message type identifier indicates a first message type, the second message type identifier indicates a second message type, and the third message type identifier indicates a third message type. The display module is specifically used to display the first message type identifier, the second message type identifier, and the third message type identifier in the identifier display area of ​​the notification message display interface; to display at least one notification message of the first message type in the first sub-area of ​​the message display area in the notification message display interface; and to display the program icon of at least one push program that pushes the notification message of the second message type and the program icon of at least one push program that pushes the notification message of the third message type in the second sub-area and the third sub-area adjacent to the first sub-area, respectively. The display module is specifically configured to, after displaying the at least one message type identifier and at least one notification message of the message type indicated by each message type identifier, upon receiving user input for selecting the second message type identifier, update the display content of the first sub-area to at least one notification message of the second message type, and update the display content of the second sub-area to the program icon of at least one push notification program that pushes the notification message of the first message type; and upon receiving user input for selecting the third message type identifier, update the display content of the first sub-area to at least one notification message of the third message type, and update the display content of the third sub-area to the program icon of at least one push notification program that pushes the notification message of the first message type.

16. The terminal according to claim 15, characterized in that, The display module is specifically configured to display the first message type identifier in the first display area of ​​the notification message display interface, and display at least one notification message of the first message type indicated by the first message type identifier in the adjacent display area of ​​the first display area; and if the at least one message type identifier further includes a second message type identifier, display the second message type identifier in the second display area of ​​the notification message display interface, and display at least one notification message of the second message type indicated by the second message type identifier in the adjacent display area of ​​the second display area.

17. The terminal according to claim 16, characterized in that, The display module is specifically used to display at least two notification messages of the first message type in a stacked display manner in adjacent display areas of the first display area; Among the at least two notification messages, the display level of the notification message and the reception time of the notification message are positively correlated.

18. The terminal according to claim 17, characterized in that, The receiving module is further configured to receive a second input from the user on the at least two notification messages after displaying at least two notification messages of the first message type in a stacked display manner in an adjacent display area of ​​the first display area; The processing module is further configured to, in response to the second input received by the receiving module, clear the notification message with the highest display level among the at least two notification messages.

19. The terminal according to claim 16, characterized in that, The receiving module is further configured to receive a third input from the user for at least one notification message of the first message type after displaying at least one notification message of the first message type in an adjacent display area of ​​the first display area; The display module is further configured to, in response to the third input received by the receiving module, display all notification messages of the first message type in the notification message display interface.

20. The terminal according to claim 15, characterized in that, The message clearing process includes at least one of the following: timed message clearing process, batch clearing process based on importance, and clearing process based on message type identifier; The message notification processing includes at least one of the following: time-based scheduled notification processing and application-based scheduled notification processing.

21. The terminal according to claim 20, characterized in that, The notification message processing includes the message clearing process, which includes clearing process based on the message type identifier. The processing module is specifically configured to clear all notification messages of the message type indicated by the first message type identifier, and maintain the display of all notification messages of the message type indicated by all message type identifiers other than the first message type identifier among the at least one message type identifier.

22. The terminal according to claim 20, characterized in that, The notification message processing includes the message clearing process, which includes the batch clearing process based on importance; the at least one message type identifier includes a first message type identifier and a second message type identifier, wherein the first message type identifier indicates an important message type and the second message type identifier indicates a normal message type; The receiving module is also used to receive a fourth input from the user to the message clearing control; The processing module is further configured to, in response to the fourth input received by the receiving module, clear all notification messages of the message type indicated by the second message type identifier, and maintain the display of all notification messages of the message type indicated by the first message type identifier.

23. The terminal according to claim 20, characterized in that, The notification message processing includes the message clearing process, which includes the timed message clearing process. The display module is further configured to display a timeout duration setting control before the processing module performs notification message processing on at least one notification message of the message type indicated by the first message type identifier; The receiving module is also used to receive the duration input by the user in the timed duration setting control displayed on the display module; The processing module is specifically configured to, after the receiving module receives the duration from the time input by the user in the timed duration setting control, clear unread notification messages in all notification messages of the message type indicated by the first message type identifier, or clear all notification messages of the message type indicated by the first message type identifier.

24. The terminal according to claim 20, characterized in that, The notification message processing includes the message reminder processing, and the message reminder processing includes the time-based scheduled reminder processing; The display module is further configured to display an appointment time setting control before the processing module performs notification message processing on at least one notification message of the message type indicated by the first message type identifier; The receiving module is also used to receive the time point entered by the user in the appointment time setting control displayed on the display module; The processing module is specifically used to output reminder information for all notification messages of the message type indicated by the first message type identifier when the system time matches the time point received by the receiving module.

25. The terminal according to claim 20, characterized in that, The notification message processing includes the message reminder processing, and the message reminder processing includes the application-based scheduled reminder processing; The display module is further configured to display at least one application identifier before the processing module performs the notification message processing on at least one notification message of the message type indicated by the first message type identifier; the application identifier is used to indicate a push program, and the at least one application identifier indicates a push program that pushes the notification message of the message type indicated by the first message type identifier. The receiving module is further configured to receive user input for selecting one of the at least one application identifiers displayed by the display module; The processing module is specifically configured to, when the push program indicated by the application identifier selected by the selection input is running, output a reminder message of the notification message pushed by the push program indicated by the application identifier selected by the selection input among all notification messages of the message type indicated by the first message type identifier.

26. The terminal according to claim 15, characterized in that, The receiving module is further configured to receive a fifth input from the user for a notification message indicated by a first message type identifier and a second message type identifier after the display module displays the at least one message type identifier and at least one notification message of the message type indicated by each message type identifier. The processing module is further configured to, in response to the fifth input received by the receiving module, set the message type of the notification message selected by the fifth input to the second message type indicated by the second message type identifier, and update the notification message selected by the fifth input to the message display area corresponding to the second message type identifier.

27. The terminal according to claim 26, characterized in that, The message summary information of all notification messages indicated by the first message type identifier in at least one message type identifier is displayed on the message card; The receiving module is specifically configured to receive drag input from the user dragging a message card of a notification message indicated by a first message type identifier in the at least one message type identifier onto a second message type identifier; or, to receive touch input from the user on a message card of a notification message indicated by a first message type identifier and a second message type identifier in the at least one message type identifier.

28. The terminal according to claim 15, characterized in that, The display module is specifically used to display at least one message type label and at least one message card; Each message type label includes a message type name, each message card corresponds to a notification message, and each message card displays a message summary of a notification message of a certain message type.

29. An electronic device, characterized in that, It includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the steps of the message management method as described in any one of claims 1 to 14.

30. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the message management method as described in any one of claims 1 to 14.

Images