CN114780268B - Display method and electronic device of notification message - Google Patents

Abstract

Embodiments of the present application provide a method and an electronic device for displaying a notification message. Wherein, a first notification window is displayed in the interface for displaying notification messages of the electronic device, at least one second notification window is displayed in the first notification window, and application notification messages of interest to the user are respectively displayed in each second notification window. Therefore, the display method can aggregate the notification messages that the user is interested in for display in one notification message window, so as to facilitate the user to view, and the user does not need to search one by one from a large number of application notification windows, which improves the user experience.

Description

Notification message display method and electronic device

technical field

The present application relates to the technical field of smart terminals, and in particular to a method for displaying message notifications and electronic equipment.

Background technique

With the popularization of terminal devices and terminal applications, more and more terminal applications notify users by means of message push, and these messages for notifying users are called notification messages. Users can see these push notification messages on the lock screen interface of the terminal device or the notification center (or notification bar) of the terminal device.

With the popularity of terminal applications and the increase in the number of terminal applications installed by users, there are too many notification messages and unfocused content. Various notification messages are intertwined, making it difficult for users to quickly find the notification messages they care about.

Contents of the invention

In order to solve the above technical problem, embodiments of the present application provide a method for displaying a notification message and an electronic device. In this method, the notification messages that the user is interested in can be aggregated and displayed in one notification message window, which is convenient for the user to view and improves the user experience.

In a first aspect, the embodiment of the present application provides a method for displaying a notification message. The method includes: the electronic device displays a first interface; wherein, the first interface includes a first notification window, at least one second notification window is displayed in the first notification window, and a user-sensitive App notification messages of interest.

Wherein, the first interface may be any interface displaying a notification message window, such as a notification center interface. Exemplarily, in addition to displaying the first notification window on the first interface, an application notification window corresponding to any application may also be displayed, for example, the application notification window 101, the application notification window 102, the application notification window 102 shown in (2) in FIG. Application notification window 103 .

Wherein, the first notification window is a notification aggregation display window, and the second notification window is an application notification window aggregated and displayed in the first notification window. Exemplarily, the application may be a social application, such as WeChat, QQ, short message and so on.

Exemplarily, any two second notification windows may correspond to the same application, for example, both are WeChat application notification windows. That is, any two second notification windows can display notification messages from the same application.

As another example, any two second notification windows may also correspond to different applications, for example, one is a WeChat application window and the other is a short message application window. That is, any two second notification windows can display notification messages from different applications.

In this way, the notification messages that the user is interested in can be aggregated and displayed in one notification message window, which is convenient for the user to view and improves the user experience. Wherein, the notification messages of interest to the user may originate from the same application, or may originate from different applications.

According to the first aspect, the first notification window is used to collectively display application notification messages corresponding to the first contact; the second notification window is respectively used to display notification messages sent by the first contact in different applications.

Wherein, the first notification window may be, for example, a notification aggregation window described below, which is used to aggregate and display notification messages sent by a certain contact in different applications. Each second notification window is an application notification window corresponding to the contact.

In this way, no matter which application the contact uses to send a notification message to the user of the electronic device, the user of the electronic device can view the corresponding notification message in the notification aggregation window corresponding to the contact, without needing to check the corresponding notification message from a large number of application notification windows one by one. Searching simplifies the time cost for users to obtain information of interest. The electronic device can conspicuously display the contact notification message that the user really cares about to the user, thereby improving the user experience.

According to the first aspect, or any implementation manner of the above first aspect, the electronic device displays the first interface, including: the electronic device obtains the first notification message, determines the name of the first application to which the first notification message belongs and the first notification message The first session identifier of the message; if the electronic device determines that there is a first contact group to which the first notification message belongs according to the name of the first application and the first session identifier, it will correspond to the name of the first application in the first notification window The first notification message is displayed in the second notification window; wherein, the first notification window is a notification window corresponding to the first contact group.

In this way, if the notification message has been grouped based on contacts, the electronic device will display the notification message in the notification aggregation window corresponding to the corresponding group.

According to the first aspect, or any implementation of the above first aspect, before the electronic device displays the first interface, it further includes: the electronic device displays the second interface; the second interface includes a third notification window, and the third notification window The second notification message of the first application is displayed in ; wherein, the session identifier of the second notification message is the first session identifier; in response to the first operation, the first contact group is created, and the name of the first application and the first The session identifier is associated with the first contact group.

Wherein, the second interface may be any interface displaying a notification message window, such as a notification center interface.

Wherein, the second notification message and the first notification message are sent by the same contact in the same application.

In this way, the user can create a contact group based on the notification messages sent by the interested contacts in a certain application, so that when receiving other notification messages from the same contact in this application, these notification messages can be shared with the contact It will be displayed in the notification aggregation window corresponding to the person group.

According to the first aspect, or any implementation of the above first aspect, before the electronic device displays the first interface, it further includes: displaying a third interface; the third interface includes a fourth notification window, and the fourth notification window displays There is a third notification message of the first application; wherein, the session identifier of the third notification message is the first session identifier; the electronic device links the name of the first application and the first session identifier with the first contact in response to the second operation Groups are associated.

Wherein, the third interface may be any interface displaying a notification message window, such as a notification center interface.

Wherein, the third notification message and the first notification message are sent by the same contact in the same application.

In this way, based on the notification message sent by the interested contact in a certain application, the user can associate the application name and session ID corresponding to the notification message with the existing contact group, so that the subsequent receipt of the same contact in the When other notification messages are sent in this application, these notification messages can be displayed in the notification aggregation window corresponding to the contact group.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: the electronic device displays a fourth interface; the fourth interface includes a fifth notification window, and the fifth notification window displays the information of the second application A fourth notification message; wherein, the session ID of the fourth notification message is the second session ID; in response to the third operation, associating the name of the second application and the second session ID with the first contact group.

Wherein, the fourth interface may be any interface displaying a notification message window, such as a notification center interface.

Wherein, the fourth notification message and the first notification message are sent by the same contact in different applications.

In this way, based on the notification message sent by the interested contact in a certain application, the user can associate the application name and session ID corresponding to the notification message with the existing contact group, so that the subsequent receipt of the same contact in the When other notification messages are sent in this application, these notification messages can be displayed in the notification aggregation window corresponding to the contact group.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: when the electronic device creates the first contact group, in response to the fourth operation, the electronic device personalizes the first contact group set up.

Exemplarily, the personalized setting may include: notification ringtone, notification message display font, notification window background color, whether to display on top, avatar, etc.

In this way, based on the personalized setting of the contact group, the notification messages in the notification aggregation window of different contact groups can be distinguished, and the user experience is better. Moreover, when the first notification window corresponding to the first contact group is displayed on top, the electronic device may prominently display the notification information that the user is interested in for the user to view.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: the electronic device displays a fifth interface; the fifth interface displays the identification of the first application; responding to the identification of the first application In a fifth operation, the electronic device disassociates the name of the first application and the first session identifier from the first contact group.

Wherein, the fifth interface can be understood as an application list interface associated with contact groups.

In this way, the user can delete and manage the applications associated with each contact group, so as to prevent notification messages that are no longer interested in still being displayed in the notification aggregation window.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: the electronic device displays a fifth interface; the fifth interface displays the identification of the first application; responding to the identification of the first application In a sixth operation, the electronic device displays a sixth interface; where a session interface in the first application corresponding to the first session identifier is displayed on the sixth interface.

Wherein, the fifth interface can be understood as an application list interface associated with contact groups.

In this way, the user can conveniently check the corresponding application session interface, so that the user can confirm whether the notification message is sent by the contact person he/she is interested in.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: the electronic device displays a seventh interface; a contact group list is displayed on the seventh interface, and the contact group list includes the first contact Group identification; in response to the seventh operation of identifying the first contact group, the electronic device displays an eighth interface; the eighth interface displays personalized setting information of the first contact group.

In this way, it is convenient for the user to view details and manage personalized settings for each contact group.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: the electronic device displays a seventh interface; a contact group list is displayed on the seventh interface, and the contact group list includes the first contact Group identification; the electronic device deletes the first contact group in response to the eighth operation of identifying the first contact group.

In this way, it is convenient for the user to delete and manage the contact group, so as to prevent the notification messages of the no longer interested contacts from being aggregated and displayed.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: the electronic device switches the first notification window from an expanded state to a folded state in response to the ninth operation on the first notification window; the electronic device In response to the tenth operation on the first notification window, the first notification window is switched from the collapsed state to the expanded state.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: in response to the eleventh operation on the first notification window, deleting the first notification window in the interface.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: in response to the twelfth operation on the second notification window, deleting the second notification window in the first notification window.

In this way, the user can operate any application notification window in the notification aggregation window.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: in response to the thirteenth operation on the second notification window, acquiring the name of the third application corresponding to the second notification window and the name of the third application Three session identifiers, disassociate the name of the third application and the third session identifier from the first contact group.

In this way, in the notification aggregation window interface, the user can also delete and manage the applications associated with the contact group, so as to avoid notification messages that are no longer of interest still displayed in the notification aggregation window.

According to the first aspect, or any implementation manner of the above first aspect, the method further includes: if the electronic device determines that there is no first contact to which the first notification message belongs according to the name of the first application and the first session identifier grouping, the first notification message is displayed in the application notification window corresponding to the first application.

In this way, if the notification message is not grouped based on contacts, the electronic device will display the notification message in the corresponding application notification window, which is the same as the prior art.

Exemplarily, for the first to thirteenth operations mentioned above, reference may be made to corresponding user operations in the following embodiments, which are not limited in this embodiment.

According to the first aspect, or any implementation manner of the above first aspect, the electronic device creates a first contact group, and associates the name of the first application and the first session identifier with the first contact group, including: The electronic device adds a first record corresponding to the first contact group in the first data table; wherein, the first record includes at least a contact group identifier, and the contact group identifier is the primary key of the first data table; A second record corresponding to the name of the first application and the first session identifier is added to the data table, and the second record at least includes the application name to which the notification message belongs, the session identifier of the notification message, and the contact group; wherein, the notification message belongs to The application name and the session ID of the notification message are both the primary key of the second data table, and the contact group is the foreign key of the first data table, which is associated with the contact group ID in the first data table.

Exemplarily, the first data table may be the groupInformation data table described below, and the second data table may be the convationlist data table described below.

Similarly, deleting a record in the second data table can realize disassociation of the application name and the session identifier from the contact group. Deleting a record in the first data table and deleting an associated record in the second data table can realize the deletion of the contact group.

In a second aspect, the embodiment of the present application provides an electronic device. The electronic device includes: one or more processors; memory; and one or more computer programs, wherein the one or more computer programs are stored on the memory, and when executed by the one or more processors, the electronic device Execute the first aspect and the method for displaying the notification message in any one of the first aspect.

The second aspect and any implementation manner of the second aspect correspond to the first aspect and any implementation manner of the first aspect respectively. For technical effects corresponding to the second aspect and any implementation manner of the second aspect, reference may be made to the technical effects corresponding to the above-mentioned first aspect and any implementation manner of the first aspect, and details are not repeated here.

In a third aspect, the embodiments of the present application provide a computer-readable storage medium. The computer-readable storage medium includes a computer program, and when the computer program is run on the electronic device, the electronic device is made to execute the first aspect and the method for displaying a notification message in any one of the first aspect.

The third aspect and any implementation manner of the third aspect correspond to the first aspect and any implementation manner of the first aspect respectively. For technical effects corresponding to the third aspect and any implementation manner of the third aspect, reference may be made to the technical effects corresponding to the above-mentioned first aspect and any implementation manner of the first aspect, and details are not repeated here.

In a fourth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when the computer program is executed, causes the computer to execute the method for displaying a notification message as in the first aspect or any one of the first aspect.

The fourth aspect and any implementation manner of the fourth aspect correspond to the first aspect and any implementation manner of the first aspect respectively. For the technical effects corresponding to the fourth aspect and any one of the implementation manners of the fourth aspect, refer to the above-mentioned first aspect and the technical effects corresponding to any one of the implementation manners of the first aspect, and details are not repeated here.

In a fifth aspect, the present application provides a chip, and the chip includes a processing circuit and transceiving pins. Wherein, the transceiving pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the display method of the notification message as in the first aspect or any one of the first aspect, to control the receiving pin to receive a signal, to control The send pin sends a signal.

The fifth aspect and any implementation manner of the fifth aspect correspond to the first aspect and any implementation manner of the first aspect respectively. For the technical effects corresponding to the fifth aspect and any one of the implementation manners of the fifth aspect, refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation manners of the first aspect, and details are not repeated here.

Description of drawings

FIG. 1 is a schematic diagram of an exemplary application scenario;

FIG. 2 is a schematic diagram of an exemplary application scenario;

FIG. 3 is a schematic diagram of a hardware structure of an exemplary electronic device;

FIG. 4 is a schematic diagram of a software structure of an exemplary electronic device;

FIG. 5 is a schematic diagram of an exemplary application scenario;

Fig. 6a-Fig. 6c are schematic diagrams showing an exemplary application scenario;

FIG. 7a-FIG. 7c are exemplary schematic diagrams showing an application scenario;

Fig. 8a-Fig. 8b is a schematic diagram of an exemplary application scenario;

FIG. 9a-FIG. 9d are exemplary schematic diagrams showing an application scenario;

FIG. 10 is a schematic diagram of an exemplary application scenario;

Fig. 11 is a schematic diagram of module interaction provided by the embodiment of the present application;

Fig. 12 is a schematic diagram of an exemplary application scenario;

Figure 13a-Figure 13d is a schematic diagram of an application scenario exemplarily shown;

Fig. 14 is a schematic diagram of an exemplary application scenario;

Fig. 15 is a schematic diagram of an exemplary application scenario;

Fig. 16 is a schematic diagram of an exemplary application scenario.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of this application.

The term "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations.

The terms "first" and "second" in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order of objects. For example, the first target object, the second target object, etc. are used to distinguish different target objects, rather than describing a specific order of the target objects.

In the embodiments of the present application, words such as "exemplary" or "for example" are used as examples, illustrations or illustrations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application shall not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete manner.

In the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more. For example, multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.

With the popularity of terminal applications and the increase in the number of terminal applications installed by users, there are too many notification messages and unfocused content. Various notification messages are intertwined, making it difficult for users to quickly find the notification messages they care about. Terminal devices often aggregate and present notification messages from the same source, and display the aggregated notification messages in the notification bar, thereby making the interface of the notification bar simple and not cluttered to a certain extent. Exemplarily, the terminal device groups the notification messages based on the notification ID, where the notification ID is predefined by the system. When the application sends a notification, it selects a notification ID to send, and the terminal aggregates and displays the notification messages based on the notification ID.

The mobile phone is taken as an example for explanation below, and the same is true for taking other terminal devices as examples, and details will not be repeated here.

Fig. 1 exemplarily shows an application scenario. Referring to Figure 1, when the mobile phone displays the main interface as shown in (1) in Figure 1, the user performs a sliding operation on the top left of the screen, and in response to the user operation, the mobile phone interface switches, as shown in (2) in Figure 1 The notification center interface (or notification bar interface) of . As shown in (2) in Figure 1, in the notification center interface, notification messages from the same source are combined and displayed. Exemplarily, a notification message from a WeChat application is displayed in a notification window (or called a notification card) 101, a notification message from a video application is displayed in a notification window 102, and a notification message from a short message application (or called an information application) is displayed in The notification window 103 is displayed.

Fig. 2 exemplarily shows an application scenario. Referring to (1) in FIG. 2 , the mobile phone displays multiple notification windows on the lock screen interface, which are respectively used to combine and display communication messages from different applications. Exemplarily, 4 notifications are displayed in the notification window 201 from the WeChat application, 1 notification is displayed in the notification window 202 from the video application, and 1 notification is displayed in the notification window 203 from the SMS application. Since the phone is currently locked, in order to protect user privacy, only the number of notifications from an application is displayed in the notification window. After the mobile phone is unlocked, a notification message from an application can be displayed in each notification window, as shown in (2) in Figure 2. Exemplarily, the detailed information of 4 notifications from the WeChat application is displayed in the notification window 204, the detailed information of 1 notification from the video application is displayed in the notification window 205, and the detailed information of 1 notification from the short message application is displayed in the notification window 204. A notification window 206 is displayed.

However, with the popularity of terminal applications and the increase in the number of terminal applications installed by users, there are too many notification messages and the content is not focused. Various notification messages are intertwined, making it difficult for users to quickly find the notification messages they care about. .

When multiple social applications are installed in the terminal device, such as WeChat, QQ, SMS, Alipay, Douyin, etc., the same person can send notification messages to the terminal device user based on different applications. In the existing notification message display scheme, since the notification messages of each application are combined and displayed separately, the notification messages sent by the same person to the terminal device user in different applications are displayed independently, making it difficult for users to quickly focus on themselves Notification message of someone, the user experience is poor.

Referring to (2) in Figure 1 or (2) in Figure 2, it is assumed that "Chen" in the WeChat application contact and "Chen Moumou" in the SMS application contact are the same person in real life, and this person is in each The notification messages sent by the application are the notification messages that the user pays more attention to. However, notification messages sent by the person in different applications are displayed in different notification windows. As a result, it is difficult for users to quickly focus on the notification messages of the person they care about, especially when the number of notification windows is large, it is difficult for the user to quickly find the notification messages sent by this person through different applications in multiple notification windows, and the user experience is poor. .

FIG. 3 is a schematic structural diagram of the electronic device 100 . Optionally, the electronic device 100 may be a terminal, which may also be called a terminal device, and the terminal may be a device such as a cellular phone (cellular phone) or a tablet computer (pad), which is not limited in this application. It should be noted that the schematic structural diagram of the electronic device 100 may be applicable to the mobile phones shown in FIGS. 1-2 . It should be understood that the electronic device 100 shown in FIG. 3 is only an example of an electronic device, and the electronic device 100 may have more or fewer components than those shown in the figure, and may combine two or more components, or may have different component configurations. The various components shown in Figure 3 may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.

The electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, and an antenna 2. Mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, And a subscriber identification module (subscriber identification module, SIM) card interface 195 and so on. The sensor module 180 may include a pressure sensor, a gyroscope sensor, an acceleration sensor, a temperature sensor, a motion sensor, an air pressure sensor, a magnetic sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor ( image signal processor (ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU), etc. . Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

Wherein, the controller may be the nerve center and command center of the electronic device 100 . The controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory.

The USB interface 130 is an interface conforming to the USB standard specification, specifically, it may be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100 , and can also be used to transmit data between the electronic device 100 and peripheral devices. It can also be used to connect headphones and play audio through them. This interface can also be used to connect other electronic devices, such as AR devices.

The charging management module 140 is configured to receive a charging input from a charger. Wherein, the charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger through the USB interface 130 . In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 100 . While the charging management module 140 is charging the battery 142 , it can also provide power for electronic devices through the power management module 141 .

The power management module 141 is used for connecting the battery 142 , the charging management module 140 and the processor 110 . The power management module 141 receives the input from the battery 142 and/or the charging management module 140 to provide power for the processor 110 , the internal memory 121 , the external memory, the display screen 194 , the camera 193 , and the wireless communication module 160 .

The wireless communication function of the electronic device 100 can be realized by the antenna 1 , the antenna 2 , the mobile communication module 150 , the wireless communication module 160 , a modem processor, a baseband processor, and the like.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 may be used to cover single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: Antenna 1 can be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the electronic device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like.

The wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (wireless local area networks, WLAN) (such as wireless fidelity (wireless fidelity, Wi-Fi) network), bluetooth (bluetooth, BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions.

In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology.

The electronic device 100 realizes the display function through the GPU, the display screen 194 , and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos and the like. The display screen 194 includes a display panel. In some embodiments, the electronic device 100 may include 1 or N display screens 194 , where N is a positive integer greater than 1.

The electronic device 100 can realize the shooting function through the ISP, the camera 193 , the video codec, the GPU, the display screen 194 and the application processor.

The ISP is used for processing the data fed back by the camera 193 . For example, when taking a picture, open the shutter, the light is transmitted to the photosensitive element of the camera through the lens, and the light signal is converted into an electrical signal, and the photosensitive element of the camera transmits the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be located in the camera 193 .

Camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects it to the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a complementary metal-oxide-semiconductor (complementary metal-oxide-semiconductor, CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other image signals. In some embodiments, the electronic device 100 may include 1 or N cameras 193 , where N is a positive integer greater than 1.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100 . The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function.

The internal memory 121 may be used to store computer-executable program codes including instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the internal memory 121 , such as enabling the electronic device 100 to implement the method for displaying notification messages in the embodiment of the present application. The internal memory 121 may include an area for storing programs and an area for storing data. Wherein, the stored program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like. The storage data area can store data created during the use of the electronic device 100 (such as audio data, phonebook, etc.) and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like.

The electronic device 100 can implement audio functions through the audio module 170 , the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playback, recording, etc.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be set in the processor 110 , or some functional modules of the audio module 170 may be set in the processor 110 .

Speaker 170A, also referred to as a "horn", is used to convert audio electrical signals into sound signals. Electronic device 100 can listen to music through speaker 170A, or listen to hands-free calls. In some embodiments, the electronic device 100 may be provided with a plurality of speakers 170A.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the receiver 170B can be placed close to the human ear to receive the voice.

The microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can put his mouth close to the microphone 170C to make a sound, and input the sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In some other embodiments, the electronic device 100 may be provided with two microphones 170C, which may also implement a noise reduction function in addition to collecting sound signals. In some other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and realize directional recording functions, etc.

The earphone interface 170D is used for connecting wired earphones. The earphone interface 170D may be the USB interface 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association of the USA (CTIA) standard interface.

The pressure sensor is used to sense the pressure signal and convert the pressure signal into an electrical signal. In some embodiments, a pressure sensor may be located on the display screen 194 . The electronic device 100 may also calculate the touched position according to the detection signal of the pressure sensor.

The gyro sensor can be used to determine the motion posture of the electronic device 100 . In some embodiments, the angular velocity of the electronic device 100 around three axes (ie, x, y and z axes) may be determined by a gyro sensor.

The acceleration sensor can detect the acceleration of the electronic device 100 in various directions (generally three axes). The acceleration sensor can detect the magnitude and direction of gravity when the electronic device 100 is stationary. Acceleration sensors can also be used to identify the attitude of electronic devices, and are used in applications such as horizontal and vertical screen switching, pedometers, etc.

Touch sensor, also known as "touch panel". The touch sensor can be arranged on the display screen 194, and the touch sensor and the display screen 194 form a touch screen, also called “touch screen”. The touch sensor is used to detect a touch operation on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event.

The buttons 190 include a power button (or called a power button), a volume button, and the like. The key 190 may be a mechanical key. It can also be a touch button. The electronic device 100 can receive key input and generate key signal input related to user settings and function control of the electronic device 100 .

The motor 191 can generate a vibrating reminder. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations applied to different applications (such as taking pictures, playing audio, etc.) may correspond to different vibration feedback effects.

The indicator 192 can be an indicator light, and can be used to indicate charging status, power change, and can also be used to indicate messages, missed calls, notifications, and the like.

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100 .

FIG. 4 is a block diagram of the software structure of the electronic device 100 according to the embodiment of the present application.

The layered architecture of the electronic device 100 divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, which are, from top to bottom, the application program layer, the application program framework layer, the Android Runtime (Android Runtime) and the system library, and the kernel layer.

The application layer can consist of a series of application packages.

As shown in FIG. 4 , the application program package may include application programs such as WeChat, short message, setting, notification center, social application, Lancher, and notification group management module. Exemplarily, the application program package may also include application programs such as call, calendar, map, navigation, music, and video.

Wherein, the social application may refer to any application capable of sending notification messages between contacts (or called friends), such as QQ, Douyin, Alipay, and the like.

Wherein, the Launcher may also be referred to as a desktop application or a main screen. Generally, after the Android system is started, the Launcher can run resident in the Android system as a core application.

Wherein, the notification center may be used to display notification messages, for example, to display communication messages from various application programs.

In this embodiment, the notification group management module can be used to manage the group display of notification messages based on contacts. Wherein, the notification group management module may be an independent functional module, or may be integrated in the Lancher or setting application, which is not limited in this embodiment. Exemplarily, the notification group management module can add or delete a contact notification message group (or called a contact group), and can also add or delete application session information associated with a contact notification message group, and can also The application name and the session identifier to which the message belongs determine whether the notification message has been grouped based on contacts.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 4, the application framework layer can include window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data and make it accessible to applications. Said data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebook, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. The view system can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100 . For example, the management of call status (including connected, hung up, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and so on.

The notification manager enables applications to display notification information (or notification messages) in the status bar (or notification center interface, etc.), which can be used to convey notification-type messages, which can disappear automatically after a short stay without user interaction, or It stays for a long time and disappears after the user deletes it. For example, notification messages are used to inform download completion, message reminders, etc. The notification message can also be a notification appearing on the status bar at the top of the system in the form of a chart or scroll bar text, such as a notification of an application program running in the background, or a notification appearing on the screen in the form of a dialog window. For example, prompting text information in the status bar, issuing a prompt sound, vibrating the electronic device, and flashing the indicator light, etc.

In this embodiment of the application, the notification manager can also be used to parse the session ID and application name of the notification message, so that the notification group management module can judge whether the notification message is based on the contact person based on the session ID and application name of the notification message. grouping. If a notification message is grouped based on contacts, the notification message is displayed in the notification aggregation window corresponding to the corresponding contact; otherwise, the notification message is displayed based on the prior art.

Android Runtime includes core library and virtual machine. Android Runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one part is the function function that the java language needs to call, and the other part is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application program layer and the application program framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

A system library can include multiple function modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of various commonly used audio and video formats, as well as still image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing, etc.

2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, audio driver, Wi-Fi driver, sensor driver, etc. Wherein, the hardware includes at least a processor, a display screen, a Wi-Fi module, a sensor, and the like.

It can be understood that the layers in the software structure shown in FIG. 4 and the components contained in each layer do not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer layers than shown, and each layer may include more or fewer components, which is not limited in the present application.

It can be understood that, in order to implement the method for displaying notification messages in the embodiments of the present application, the electronic device includes corresponding hardware and/or software modules for performing various functions. Combining the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions in combination with the embodiments for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

In order to solve the problem that "it is difficult for a user to quickly find a notification message of a contact he/she cares about in multiple notification windows", an embodiment of the present application provides a method for displaying a notification message. Among them, the user can customize the grouping of the same contact (corresponding to a person in real life) in different applications, and the terminal device will aggregate and display the notification messages sent by the same contact in different applications based on the custom grouping . As a result, no matter which application the contact uses to send a notification message to the terminal device user, the terminal device user can view the corresponding notification message in the notification aggregation window corresponding to the contact, without having to click through a large number of application notification windows. One search simplifies the time cost for users to obtain interested information. In this way, the terminal device can conspicuously display the contact notification message that the user really cares about to the user, which improves the user experience.

Fig. 5 exemplarily shows an application scenario. Assuming that the mobile phone user pays more attention to the notification messages sent by the contact "boss" in real life, the mobile phone user can assign the notification messages sent by the contact "boss" in each application to a notification aggregation group, For example, the notification messages sent by the "boss" in WeChat, SMS, QQ and other applications are assigned to the notification aggregation group corresponding to the contact "boss". Therefore, when the "boss" uses any of these applications to send a notification message to the mobile phone user, the notification message will be displayed in the notification aggregation group (or notification aggregation window) corresponding to the "boss" contact . As shown in FIG. 5 , taking the notification center page as an example, the mobile phone displays a notification aggregation window 301 corresponding to the real-life contact "boss". In the notification aggregation window 301, at least one application notification window corresponding to the contact "boss" is displayed, such as a short message application notification window 3011 and a WeChat application notification window 3012. Among them, no matter whether the "boss" contact person sends a notification message to the mobile phone user from a short message application, sends a notification message to the mobile phone user from the WeChat application, or sends a notification message to the mobile phone user from other applications, the notification message will be sent to the mobile phone user. It is displayed in the notification aggregation window 301 corresponding to the "boss" contact. When the user clicks on the notification window 3011 of the SMS application or the notification window 3012 of the WeChat application, the mobile phone can display the corresponding application interface, so that the user can view the conversation message or notification message in the application.

It should be noted that the contact corresponding to a notification aggregation window is a contact in real life, and the title of the contact "boss" can be customized by the mobile phone user, and can be related to the contact's name in an application. Remarks are the same or different. Wherein, the contact name corresponding to a certain notification aggregation window is not subject to a certain application.

It should be pointed out that the notification center interface shown in (2) in Figure 1 and the lock screen unlocking interface shown in (2) in Figure 2 are only exemplary notification window display interfaces, and the notification window can also display In other interfaces, this embodiment does not limit it. The following only uses the notification center interface as an example to explain the method for displaying notification messages provided by this embodiment, and the same is true for other notification window display interfaces, so details will not be repeated here.

Among them, before the mobile phone aggregates and displays notification messages based on contacts, mobile phone users need to create contact notification message groups according to individual needs. Furthermore, after the contact notification message group is created, the mobile phone can display the notification message aggregation in the notification aggregation window corresponding to the contact notification message group. The processes of creating and managing contact notification message groups and aggregated display of notification messages based on contact notification message groups are explained in detail below.

scene one

In this scenario, there is no contact notification message group in the mobile phone. When the mobile phone receives the notification message, the mobile phone user can complete the creation of the contact notification message group based on personal needs. Wherein, during the process of creating a contact notification message group, the notification group management module of the mobile phone implements the association between the contact notification message group and the application session information of this notification message.

6a-6c exemplarily show an application scenario in which a user creates a contact notification message group.

As shown in (1) in FIG. 6 a , in response to the notification message sent by the WeChat application, a notification window 401 corresponding to the WeChat application is displayed on the mobile phone notification center interface. Wherein, in the notification window 401, the sending time "just now", the sender "Chen" and the message content "xxxxxxxx" of the WeChat application notification message are displayed. If the sender "Chen" of the notification message is a contact (assumed to be "boss") followed by the mobile phone user, the mobile phone user can create a notification message group corresponding to the contact "boss", so that the contact "boss" is in the The notification message sent in the WeChat application may be displayed in a notification aggregation window corresponding to the contact "boss". At this point, the mobile phone user can perform a left-swipe operation in the notification window 401 . In response to user operations, the mobile phone displays an interface as shown in (2) in Figure 6a. Referring to (2) in FIG. 6 a , due to the left sliding operation of the user, only the right half of the notification window 401 is displayed on the interface. On the right side of the notification window 401 , the contact notification message group creation option 402 and the notification window deletion option 403 are displayed on the interface. When the user clicks the notification window deletion option 403, in response to the user operation, the mobile phone deletes the notification window 401 on the interface. When the user clicks on the contact notification message group creation option 402, in response to the user operation, the mobile phone creates a contact notification message group corresponding to "boss".

(1) in FIG. 6b exemplarily shows an information interface of a contact notification message group. In response to the user's operation of clicking the contact notification message group creation option 402, the mobile phone may display an interface as shown in (1) in FIG. 6b. In this interface, the user can set the information of the contact notification message group. Exemplarily, the user clicks on the avatar option 501 and selects an image in the gallery to realize the avatar setting of the contact notification message group; the user clicks the group name option and enters text information to realize the name setting of the contact notification message group . For another example, the user clicks the switch option 503 to set whether to allow the contact notification message group to perform message notification. As another example, the user clicks option 504 to select a notification ringtone for the contact notification message group, the user clicks option 505 to select a message font for the contact notification message group, and the user operates the switch option 506 to set whether to display the contact notification message group on top , the user can click option 507 to select a background color for the message aggregation window of the contact notification message group. In this way, the user can personalize the grouping of contact notification messages.

(2) in FIG. 6b exemplarily shows information of a contact notification message group. Among them, the name of the contact notification message group is "boss", which allows the contact notification message group to perform message notification. The notification ringtone of the contact notification message group is ringtone Y, the message font is font Y, and the background color of the message aggregation window is Gray, and the contact notification message group will be displayed on top. Referring to (2) in FIG. 6 b , in the information interface of the contact notification message group, a confirmation option and a cancel option may also be displayed. When the user clicks the confirmation option, the mobile phone saves the information of the current contact notification message group, and completes the creation of the contact notification message group. When the user clicks the cancel option, the mobile phone does not save the information of the notification message group of the current contact, and cancels the creation of the notification message group of the current contact.

Continuing to refer to (1) in FIG. 6 b , in the information interface of the contact notification message group, a group application details option 508 is also displayed. After the contact notification message group "boss" is created, as shown in (2) in Figure 6b, the user clicks the group application details option 508, and in response to the user operation, the mobile phone displays the application as shown in (1) in Figure 6c management interface. In the application management interface, the application information related to the contact notification message group is displayed, that is, the application corresponding to the notification messages that need to be aggregated and displayed in the contact notification message group is displayed. Exemplarily, the contact notification message group created by the user based on the WeChat application message, so the application involved in the contact notification message group includes WeChat, as shown in (1) in FIG. 6c. Referring to (1) in Figure 6c, when the user clicks on the WeChat application option 601, in response to the user operation, the mobile phone displays the chat interface of the corresponding contact in the WeChat application (that is, the contact corresponding to the contact notification message group), as shown in the figure Shown in (2) in 6c.

Wherein, when creating a contact notification message group, the notification group management module of the mobile phone needs to store the data of the contact notification message group. Exemplarily, in this embodiment, the data of the contact notification message group may be stored in the form of a database or a file, which is not limited in this embodiment. The following uses the database format as an example for explanation.

In this embodiment, the notification group management module of the mobile phone can implement data storage and management of contact notification message groups based on two data tables. Wherein, one data table is used for storing information of contact notification message groups, and one data table is used for storing grouped (that is, grouped based on contact notification message grouping) application session information. These two data tables can be associated based on the ID of the contact notification message group.

Exemplarily, the data table (such as the groupInformation data table) for storing the information of the contact notification message group may include the following information: the identification (ID) of the contact notification message group, the name (name) of the contact notification message group , Whether to allow the contact notification message group to perform message notification (allow_notify), the ringtone of the contact notification message group (ring), the message font of the contact notification message group (font), whether the contact notification message group is displayed on top (stick), The avatar (avatar) of the contact notification message group, and the background color (bg_color) of the notification aggregation window of the contact notification message group.

Wherein, the identification (ID) of the contact notification message group is used to uniquely identify a contact notification message group, and the data type is an integer type (INT), which is the primary key of the groupInformation data table. Exemplarily, the ID of the contact notification message group starts from 1 and increases automatically.

Among them, in the groupInformation data table, the name of the contact notification message group, whether the contact notification message group is allowed to perform message notification, the ringtone of the contact notification message group, the message font of the contact notification message group, whether the contact notification message group is Default values can be set for one or more of the top display, the avatar of the contact notification message group, and the background color of the notification aggregation window of the contact notification message group.

As another example, the data table (such as the convationlist data table) for storing grouped application session information may include the following information: the identifier (ID) of the grouped notification message, the name of the application (pkg_name) to which the notification message belongs, and the ConversationID, the contact notification group to which the notification message belongs.

Wherein, the identifier (ID) of the grouped notification message is used to uniquely identify a grouped notification message, and the data type is an integer type (INT). Exemplarily, the ID of the grouped notification message starts from 1 and increases automatically.

The application name (pkg_name) to which the notification message belongs can uniquely distinguish which application sent the notification message, and on the basis that the application that sent the notification message has been determined, the conversation ID (ConversationID) in the application can uniquely distinguish which application the notification message is from. Which contact sent it. Therefore, the application name (pkg_name) to which the notification message belongs and the conversation ID (ConversationID) in the application can uniquely identify a grouped notification message. Therefore, in the convationlist data table, the application name (pkg_name) to which the notification message belongs and the conversation ID (ConversationID) in the application together form the primary key of the data table.

It should be pointed out that the conversation ID (ConversationID) in the application can uniquely distinguish which contact in the application sends the notification message. Conversation IDs in different applications may be the same, so this embodiment uses the application name (pkg_name) to which the notification message belongs and the conversation ID (ConversationID) in the application to uniquely identify a grouped notification message.

In an optional implementation manner, the application constructs a notification message based on a predefined conversation construction method, and the notification message carries its conversation identifier (ConversationID) in the application. When the notification manager receives the notification message sent by the application, it parses the notification message based on the predefined session construction method, and obtains the conversation ID (ConversationID) of the notification message in the application. At this point, combining the name of the application that sends the notification message and the conversation ID (ConversationID) of the notification message in the application, it can be determined whether a notification message is a grouped notification message.

In another optional implementation manner, the application constructs a notification message based on a custom session construction method, and the notification message carries its conversation ID (ConversationID) in the application. When the notification manager receives the notification message sent by the application, it parses the notification message based on the conversation construction method matching the application, and obtains the conversation ID (ConversationID) of the notification message in the application. At this point, combining the name of the application that sends the notification message and the conversation ID (ConversationID) of the notification message in the application, it can be determined whether a notification message is a grouped notification message.

In yet another optional implementation manner, the application constructs the notification message based on a custom session construction method. After receiving the notification message sent by the application, the notification manager obtains the conversation ID (ConversationID) of the notification message in the application based on the relevant interface provided by the application. At this point, combining the name of the application that sends the notification message and the conversation ID (ConversationID) of the notification message in the application, it can be determined whether a notification message is a grouped notification message.

In the convationlist data table, the contact notification message group (group) to which the notification message belongs is a foreign key, which is associated with the identification (ID) field of the contact notification message group in the groupInformation data table, and is used to identify the contact to which the notification message belongs Notification message grouping.

Continuing to refer to (2) in FIG. 6 a , when the user clicks on the contact notification message group creation option 402 , in response to the user operation, the notification group management module of the mobile phone creates a contact notification message group corresponding to "boss". Wherein, in the process of creating a contact notification message group corresponding to "boss" by the notification group management module, the notification group management module automatically generates a contact notification message group "boss" ID, and groups the contact notification message according to the user Information settings (such as name, image, whether to allow notifications, whether to stick to the top, ringtones, fonts, window background colors, etc.), add a record in the groupInformation data table, which is used to indicate the information of the contact notification message group "Boss". Then, the notification group management module automatically generates an ID of a grouped notification message, and according to the application name (pkg_name) of the notification message, the conversation ID (ConversationID) of the notification message sent by "Chen" in the WeChat application, and the newly created contact Add a record to the convationlist data table for the ID of the person notification message group "boss", which is used to indicate a grouped application session information. Among them, the contact notification message group (group) of the grouped notification message is the ID of the newly created contact notification message group "boss", so as to realize the newly created contact notification message group "boss", which is consistent with this Correlation of application session information (ie, pkg_name and ConversationID) of grouped notification messages (that is, notification messages sent by "Chen" in the WeChat application).

So far, the notification group management module of the mobile phone has completed the creation of a contact notification message group. Wherein, the created contact notification message group is associated with a piece of application session information. That is to say, when receiving a notification message matching the application session, that is, when receiving a notification message sent by "Chen" in the WeChat application, the mobile phone will display the notification message in the contact notification message group "boss". ” in the corresponding notification aggregation window.

scene two

In this scenario, there are contact notification message groups in the mobile phone. When the mobile phone receives a notification message that is not based on contact grouping, the mobile phone user can combine the application session information corresponding to the notification message with an existing one based on personal needs. Contact notification messages are grouped for association.

7a-7c exemplarily show an application scenario where a user groups notification messages based on the created contact notification message groups.

As shown in (1) in FIG. 7 a , in response to the notification message sent by the short message application, a notification window 701 corresponding to the short message application is displayed on the mobile phone notification center interface. Wherein, in the notification window 701, the sending time "just now", the sender "Chen XX" and the message content "xxxxxxxx" of the short message application notification message are displayed. If the sender of the notification message "Chen Moumou" is a contact (assumed to be "boss") followed by the mobile phone user, the mobile phone user can compare the application session information corresponding to the notification message with the contact notification message group "boss". Association, so that the notification message sent by "Chen XX" in the short message application can be displayed in the notification aggregation window corresponding to the contact "Boss". At this point, the mobile phone user can perform a left swipe operation in the notification window 701 . In response to user operations, the mobile phone displays an interface as shown in (2) in Figure 7a. Referring to (2) in FIG. 7 a , due to the left sliding operation of the user, only the right half of the notification window 701 is displayed on the interface. On the right side of the notification window 701, a contact notification message group creation option 702 is displayed on the interface. When the user clicks the contact notification message group creation option 702, in response to the user operation, the mobile phone displays a contact notification message group list interface, as shown in (1) in FIG. 7b.

Referring to the contact notification message group list interface shown in (1) in FIG. 7b, the currently created contact notification message group includes two contact notification message groups named "Boss" and "Zhang San". If the user needs to aggregate and display the notification messages sent by "Chen XX" in the short message application in the notification aggregation window corresponding to the contact "boss", he can click on the option 801 corresponding to the contact notification message group "boss". Group "boss" with the selected contact notification message. As shown in (2) in FIG. 7 b , a dot is displayed in the circle of option 801 , indicating that the contact notification message group "boss" is selected.

After the contact notification message group "boss" is selected, if the user clicks on the confirmation option 802, the notification group management module of the mobile phone completes the corresponding application Association of session information with contact notification message group "boss". At this time, the data in the groupInformation data table does not increase, and a record is added in the convationlist data table to indicate a grouped application session information, that is, to indicate the application corresponding to the notification message sent by "Chen Moumou" in the short message application session information. Wherein, the session information is grouped into the contact notification message group "boss", that is, the contact notification message group (group) of the session information, which is the ID of the contact notification message group "boss" in the groupInformation data table.

After the contact notification message group "boss" is selected, if the user clicks the cancel option 803, the notification group management module of the mobile phone will not adjust the contact notification message group data, that is, the data in the groupInformation data table and the convationlist data table are both constant.

The user clicks the confirmation option 802, and the notification group management module of the mobile phone completes the association of the application session information corresponding to the notification message (that is, the notification message sent by "Chen XX" in the SMS application) with the contact notification message group "Boss". In this case, if the user clicks the group application details option 508 (refer to (2) in Figure 6b) in the group information interface of the contact notification message group "Boss", the mobile phone responds to the user operation and displays the information shown in Figure 7c The application management interface shown in (1). In the application management interface, the application information related to the contact notification message group is displayed, that is, the application corresponding to the notification messages that need to be aggregated and displayed in the contact notification message group is displayed. As shown in (1) in FIG. 7c , the applications involved in the contact notification message group include WeChat and SMS. Referring to (1) in Figure 7c, when the user clicks on the short message application option 901, in response to the user operation, the mobile phone displays the chat interface of the corresponding contact in the short message application (that is, the contact corresponding to the contact notification message group), As shown in (2) in Figure 7c.

So far, the notification group management module of the mobile phone has completed the association of a piece of application session information with the existing contact notification message group "Boss". When receiving a notification message matching the application session, that is, when receiving a notification message sent by "Chen Moumou" in the SMS application, the mobile phone will display the notification message in the contact notification message group "Boss" ” in the corresponding notification aggregation window.

Among them, the WeChat application session information is associated with the contact notification message group "Boss", which is realized when the contact notification message group "Boss" is created (see Scenario 1), and the SMS application session information is associated with the contact notification message group "Boss". The "boss" association is realized after the contact notification message group "boss" is created. Similarly, when the mobile phone receives a notification message sent by the contact "Boss" in other applications (such as QQ, Alipay, etc.), the user can associate the session information of the notification message with the contact notification message group "Boss", so that The notification messages sent by the contact "boss" through various applications can be displayed in the notification aggregation window corresponding to the contact notification message group "boss", which will not be repeated in this embodiment.

scene three

In this scenario, there are contact notification message groups in the mobile phone. When the mobile phone receives a notification message that is not based on the contact group, the mobile phone user can create a new contact notification message group based on personal needs. Wherein, during the process of creating the new contact notification message group, the notification group management module of the mobile phone implements the association between the contact notification message group and the application session information of the notification message.

Fig. 8a- Fig. 8b exemplarily show an application scenario in which a user creates a contact notification message group.

As shown in (1) in FIG. 8 a , in response to the notification message sent by the short message application, a notification window 1001 corresponding to the short message application is displayed on the mobile phone notification center interface. Wherein, in the notification window 1001, the sending time "just now", the sender "Li XX" and the message content "xxxxxxxx" of the short message application notification message are displayed. If the sender of the notification message "Li XX" is a contact that the mobile phone user follows (assuming it is "Li Si"), and there is no notification message group corresponding to "Li Si" currently created, the mobile phone user can create and contact The notification messages corresponding to the person "Li Si" are grouped, so that the notification messages sent by the contact "Li Si" in the short message application can be displayed in the notification aggregation window corresponding to the contact "Li Si". At this point, the mobile phone user can perform a left swipe operation in the notification window 1001 . In response to user operations, the mobile phone displays an interface as shown in (2) in Figure 8a. Referring to (2) in FIG. 8 a , due to the left sliding operation of the user, only the right half of the notification window 1001 is displayed on the interface. On the right side of the notification window 1001, a contact notification message group creation option 1002 is displayed on the interface. When the user clicks the contact notification message group creation option 1002, in response to the user operation, the mobile phone displays a contact notification message group list interface, as shown in (1) in FIG. 8b.

Referring to the contact notification message group list interface shown in (1) in FIG. 8b, the currently created contact notification message group includes two contact notification message groups named "Boss" and "Zhang San". If the user needs to create a new contact notification message group based on the notification message sent by "Li XX" in the short message application, the user can click the contact notification message group creation option 804 . In response to the user's operation of clicking the option 804 to create a new contact notification message group, the mobile phone may display an interface as shown in (2) in FIG. 8b. In this interface, the user can set the information of the contact notification message group, so as to complete the personalized setting of the contact notification message group. As for the process of creating a new contact notification message group at this time, reference may be made to the previous explanation about FIG. 6 b , and details will not be repeated here.

So far, the notification group management module of the mobile phone has completed the creation of a contact notification message group. Wherein, a record is added in the groupInformation data table for instructing the contact to notify the information of the message group "Li Si". Then, the notification group management module automatically generates an ID of a grouped notification message, and according to the application name (pkg_name) "short message" of the notification message, the session identifier ( ConversationID), and the ID of the new contact notification message group, add a record in the convationlist data table to indicate a grouped application conversation information. Among them, the contact notification message group (group) of the grouped notification message is the ID of the newly created contact notification message group "Li Si", so as to realize that the newly created contact notification message group "Li Si" is the same as this Association of the application session information (ie pkg_name and ConversationID) of the grouped notification messages (that is, the notification message sent by "Li XX" in the SMS application). Further, when receiving a notification message matching the application session, the mobile phone will display the notification message in the notification aggregation window corresponding to the contact notification message group "Li Si".

scene four

In this scenario, the user can manage contact notification message groups in the settings application, or manage contact notification message groups in the notification aggregation window.

9a-9d exemplarily show an application scenario where a user performs group management of contact notification messages in a setting application.

In the setting application interface as shown in ( 1 ) in FIG. 9 a , the user clicks on the notification option 1101 . In response to the user's operation, the mobile phone may display a notification setting interface as shown in (2) in FIG. 9a. Wherein, in the notification setting interface, a notification grouping option 1102 is displayed. Referring to (2) in FIG. 9a, the user clicks on the notification group option 1102, and in response to the user operation, the mobile phone can display the notification group management interface.

Exemplarily, (1) in FIG. 9b shows the notification group management interface of the mobile phone. As shown in (1) in FIG. 9b , the created contact notification message groups are shown in the notification group management interface, wherein these contact notification message groups can be sorted by name. When the user clicks on an option corresponding to a contact notification message group, the mobile phone can display detailed information of the contact notification message group for the user. Exemplarily, referring to (1) in FIG. 9b, the user clicks the option 1103 of the contact notification message group "boss", and in response to the user operation, the mobile phone may display the interface as shown in (2) in FIG. 9b. In the group interface, the personalized setting information of the contact notification message group "boss" is displayed. In the grouping interface, the user can adjust the personalized setting information, which can refer to the prior art, and will not be repeated here. When the user clicks on the group application details option 508, in response to the user operation, the mobile phone displays the application management interface as shown in (1) in FIG. 9c. In the application management interface, the application information related to the contact notification message group "boss" is displayed, that is, the application corresponding to the notification messages that need to be aggregated and displayed in the contact notification message group is displayed. Exemplarily, the applications involved in the contact notification message group "boss" include WeChat applications and short message applications.

Continuing to refer to (1) in 9c, if the user wants to disassociate the SMS application session from the contact notification message group "Boss" based on personal needs, that is, it is no longer necessary to send messages with the contact "Boss" in the SMS application. The notification message is displayed in the notification aggregation window corresponding to the contact notification message group “boss”, and the user can perform a left-swipe operation on the short message application option 901 . In response to user operations, the mobile phone displays an interface as shown in (2) in Figure 9c. As shown in (2) in FIG. 9c, a delete option 902 corresponding to the short message application is displayed on the interface. If the user clicks on the delete option 902, the notification group management module of the mobile phone performs the operation of disassociate the corresponding SMS application session from the contact notification message group "boss", and the application management interface displayed on the mobile phone only includes the WeChat application, that is, At this time, the application involved in the contact notification message group "boss" only includes the WeChat application.

When the notification group management module of the mobile phone performs the operation of disassociation between the short message application session and the contact notification message group "boss", the data in the groupInformation data table remains unchanged, and a record is deleted in the convationlist data table. Among them, among the records deleted in the convationlist data table, the group value is the ID of the contact notification message group "Boss" in the groupInformation data table, the pkg_name value is the SMS application, and the ConversationID value is the notification message sent by "Chen" in the SMS The session ID in the application.

Referring to (1) in 9d, if the user wants to delete the contact notification message group "boss" based on personal needs, that is, it is no longer necessary to display the notification messages sent by the contact "boss" in different applications on the same page as the contact notification message. In the notification aggregation window corresponding to the message group "boss", the user can perform a left-swipe operation on the option 1103 of the contact notification message group "boss". In response to user operations, the mobile phone displays an interface as shown in (2) in Figure 9d. As shown in (2) in FIG. 9d , a delete option 1104 corresponding to the contact notification message group "boss" is displayed on the interface. If the user clicks on the delete option 1104, the notification group management module of the mobile phone executes the operation of deleting the contact notification message group "boss", and the contact notification message group created in the notification group management interface displayed on the mobile phone only includes contact notifications. Message grouping "Zhang San".

When the notification group management module of the mobile phone executes the operation of deleting the contact notification message group "boss", a record is deleted in the groupInformation data table. Wherein, in the deleted record in the groupInformation data table, the ID of the contact notification message group is the ID of the contact notification message group "boss". At the same time, at least one record is deleted in the convationlist data table, wherein the group value of these deleted records is the ID of the contact notification message group "boss".

Continuing to refer to (1) in 9b, if the user wants to create a new contact notification message group based on personal needs, he can click on the option 1105 of creating a new contact group. In response to user operations, the mobile phone may display an interface as shown in (1) in Figure 6b. In this interface, the user can set the information of the contact notification message group, so as to complete the personalized setting of the contact notification message group. As for the process of creating a new contact notification message group at this time, reference may be made to the previous explanation about FIG. 6 b , and details will not be repeated here.

When the notification group management module of the mobile phone executes the contact notification message group creation operation, a new record is added in the groupInformation data table, which is used to indicate the newly created contact notification message group.

It should be noted that when the user clicks the new contact group option 1105 to enable the notification group management module of the mobile phone to execute the operation of creating a contact notification message group, since the newly created contact notification message group is not associated with any notification message of any application, Then no records will be added in the convationlist data table at this time. When the mobile phone receives a notification message from an application, and the user needs to associate the application session message of the notification message with the newly created contact notification message group, the user can perform operations similar to those shown in Figure 7a-7b. At this time, the convationlist data Add the corresponding record to the table.

FIG. 10 exemplarily shows an application scenario where a user performs group management of contact notification messages in a notification aggregation window. As shown in (1) in FIG. 10 , a notification aggregation window 1201 corresponding to the contact notification message group "boss" is displayed in the mobile phone notification center interface. In the notification aggregation window 1201, a short message application notification window 1202 and a WeChat application notification window 1203 are displayed. If the user wants to disassociate the short message application session with the contact notification message group "boss" based on personal needs, that is, it is no longer necessary to display the notification message sent by the contact "boss" in the short message application on the contact In the notification aggregation window 1201 corresponding to the notification message group "Boss", the user can perform operations in the notification aggregation window 1201. Referring to (1) in FIG. 10 , the user performs a left-swipe operation on the notification window 1202 of the short message application, and in response to the user's operation, the mobile phone displays an interface as shown in (2) in FIG. 10 . Referring to (2) in FIG. 10 , only the right half of the SMS application notification window 1202 is displayed on the interface of the notification aggregation window 1201 due to the left sliding operation of the user. On the right side of the short message application notification window 1202, the notification aggregation window 1201 displays an option 1204 to remove the application notification in the contact notification message group and an option 1205 to delete the application notification window. When the user clicks option 1204, in response to the user operation, the notification group management module of the mobile phone performs an operation of disassociate the corresponding short message application session from the contact notification message group "boss". At this time, if the user clicks to check the application management interface corresponding to the contact notification message group "boss", the application management interface does not include the short message application.

Wherein, when the notification group management module of the mobile phone performs the operation of disassociate the short message application session from the contact notification message group "boss", the data in the groupInformation data table remains unchanged, and a record is deleted in the convationlist data table. Among them, among the records deleted in the convationlist data table, the group value is the ID of the contact notification message group "Boss" in the groupInformation data table, the pkg_name value is the SMS application, and the ConversationID value is the notification message sent by "Chen" in the SMS The session ID in the application.

Figure 11 is a schematic diagram of the interaction of each module. Referring to FIG. 11 , the flow of the notification message display method provided by the embodiment of the present application specifically includes:

S1301. The social application constructs a notification message, and sends the notification message to the notification manager.

Wherein, a social application may refer to any application capable of sending notification messages between contacts (or called friends), such as WeChat, SMS, QQ, Douyin, Alipay, and the like.

Taking the WeChat application as an example, when mobile phone user A's WeChat friend B sends a message to A, the WeChat application constructs a corresponding notification message.

Exemplarily, the WeChat application constructs a notification message based on a predefined conversation construction method, and carries the conversation ID (ConversationID) of the notification message in the WeChat application in the notification message.

Exemplarily, the WeChat application may also construct a notification message based on a custom session construction method, which is not limited in this embodiment.

S1302. The notification manager parses the notification message to obtain the application name and the session identifier to which the notification message belongs, and sends the application name and the session identifier to which the notification message belongs to the notification group management module.

When the notification manager receives the notification message sent by the WeChat application, it parses the notification message based on the predefined session construction method, obtains the conversation ID (ConversationID) of the notification message in the WeChat application, and obtains the application name and session to which the notification message belongs logo.

If the notification message sent by the WeChat application is constructed based on a custom session construction method, the notification manager can parse the notification message based on the session construction method that matches the WeChat application to obtain the session ID of the notification message in the WeChat application (ConversationID), or obtain the conversation ID (ConversationID) of the notification message in the WeChat application based on the relevant interface provided by the WeChat application.

S1303. The notification group management module judges whether the notification message has been grouped based on the contact according to the application name and the session identifier to which the notification message belongs. If yes, execute S1304; if not, execute S1306.

Notification group management combines the name of the application that sends the notification message and the conversation ID (ConversationID) of the notification message in the application to determine whether a notification message is a grouped notification message.

Among them, after the notification group management determines the application name (pkg_name) to which the notification message belongs and the conversation ID (ConversationID) in the application, data matching is performed in the convationlist data table to determine whether there is a contact notification message group (group) to which the notification message belongs . If so, the notification group management judges that the notification message has been grouped based on contacts; if not, the notification group management judges that the notification message is not grouped based on contacts,

S1304. The notification group management module determines a contact notification message group associated with the notification message.

Notification group management After determining the application name (pkg_name) to which the notification message belongs and the conversation ID (ConversationID) in the application, perform data matching in the convationlist data table to determine the contact notification message group (group) to which the notification message belongs.

Furthermore, the notification group management can perform data matching in the groupInformation data table according to the contact notification message group (group) to which the notification message belongs, determine the contact notification message group associated with the notification message, and obtain the contact notification message group personalized configuration information.

S1305, the notification group management module instructs the notification center to display the notification message in the notification aggregation window corresponding to the contact notification message group.

The notification group management module sends instruction information to the notification center to instruct the notification center to display the notification message in the notification aggregation window corresponding to the contact notification message group. Wherein, the indication information may carry the personalized configuration information of the contact notification message group, such as carrying the personalized configuration information of the notification aggregation window.

S1306, the notification group management module instructs the notification center to display the notification message in the corresponding application notification window.

If the notification grouping management module determines that the notification message is not grouped based on contacts, it instructs the notification center to display the notification information in a prior art form, for example, the notification message is displayed in the WeChat application notification window.

The content and format of the indication information sent by the notification group management module are not limited in this embodiment.

S1307. The notification center acquires the notification message to be displayed, and displays the notification message according to the instruction.

If the notification group management module instructs the notification center to display the notification message in the notification aggregation window corresponding to the contact notification message group, the notification center obtains the notification information to be displayed, and displays the notification information in the notification aggregation window corresponding to the associated contact notification message group For displaying notification messages, refer to (1) in Figure 12. Wherein, the notification ringtone, window background color, display font and other information of the notification aggregation window are consistent with the personalized configuration information of the corresponding contact notification message group. If top display is configured in the contact notification message group corresponding to the notification aggregation window, the notification aggregation window will be displayed on top in the notification center interface.

If the notification group management module instructs the notification center to display the notification message in the corresponding application notification window, the notification center obtains the notification information to be displayed, and displays the notification message in the corresponding application notification window, as shown in (2) in Figure 12 Show. In this case, as long as the notification manager can identify the conversation ID (ConversationID) of the notification message in the application, the user can group the conversations corresponding to the notification message based on contacts. For details, see Scenarios 1, 2, and Three, I will not repeat them here.

It should be pointed out that, in order to ensure the user experience, the notification aggregation window can inherit the related operations of the existing application notification window, such as window folding operation, window deletion operation and so on.

Fig. 13a- Fig. 13d exemplarily show the application scenario where the user performs related operations in the notification aggregation window.

As shown in (1) in FIG. 13a, a notification aggregation window 1401 corresponding to the contact notification message group "boss" is displayed in the mobile phone notification center interface. In the notification aggregation window 1401, a short message application notification window and a WeChat application notification window are displayed. Wherein, the notification aggregation window 1401 is in an expanded state. A window folding option 1402 is displayed in the notification aggregation window 1401 for folding and displaying the notification aggregation window. Referring to (1) in Figure 13a, the user clicks the window collapse option 1402, and in response to the user operation, the mobile phone displays the mobile phone notification center interface as shown in Figure 13a (2), and the notification aggregation corresponding to the contact notification message group "boss" The display form of the window is switched from the notification aggregation window 1401 to the notification aggregation window 1403 .

Referring to (2) in FIG. 13a, the notification aggregation window 1403 is in a collapsed state. A window expansion option 1404 is displayed in the notification aggregation window 1403 for expanding and displaying the notification aggregation window. If the user clicks the window expansion option 1404, in response to the user operation, the mobile phone displays the mobile phone notification center interface as shown in (1) in Figure 13a, and the display form of the notification aggregation window corresponding to the contact notification message group "boss" is determined by the notification aggregation The window 1403 is switched to the notification aggregation window 1401 .

Continuing to refer to (2) in FIG. 13 a , in the notification aggregation window 1403 , instead of displaying individual application notification windows, a notification message list 1405 is displayed, which is used to describe each notification message displayed in the notification aggregation window. As shown in (2) in Figure 13a, the notification message list 1405 includes: the name of each application to which each notification message displayed in the notification aggregation window 1401 belongs, the number of notification messages corresponding to each application, and the number of notification messages corresponding to each application. The receiving time of the corresponding latest notification message.

As shown in (1) in FIG. 13b , a notification aggregation window 1401 corresponding to the contact notification message group "boss" is displayed in the mobile phone notification center interface (the window is in an expanded state). If the user wants to delete the notification aggregation window 1401 on the notification center interface, the user may perform a left-swipe operation on the notification aggregation window 1401 . In response to the user's operation, the mobile phone displays the notification center interface as shown in (2) in Figure 13b. Referring to (2) in Figure 13b, due to the user's left-swipe operation, only the right half of the notification aggregation window 1401 is displayed on the notification center interface. On the right side of the notification aggregation window 1401, a delete option 1405 is displayed on the notification center interface. When the user clicks the delete option 1405, in response to the user operation, the mobile phone performs an operation of deleting the notification aggregation window 1401 in the interface.

As shown in (1) in FIG. 13c , a notification aggregation window 1403 corresponding to the contact notification message group "boss" is displayed in the mobile phone notification center interface (the window is in a folded state). If the user wants to delete the notification aggregation window 1403 on the notification center interface, the user can perform a left-swipe operation on the notification aggregation window 1403 . In response to the user's operation, the mobile phone displays the notification center interface as shown in (2) in Figure 13c. Referring to (2) in Figure 13c, due to the user's left-swipe operation, only the right half of the notification aggregation window 1403 is displayed on the notification center interface. On the right side of the notification aggregation window 1403, a delete option 1406 is displayed on the notification center interface. When the user clicks the delete option 1406, in response to the user operation, the mobile phone performs an operation of deleting the notification aggregation window 1403 in the interface.

As shown in (1) in FIG. 13d , a notification aggregation window 1401 corresponding to the contact notification message group "boss" is displayed in the mobile phone notification center interface. If the user wants to delete a certain application notification window in the notification aggregation window 1401 , the user may perform a left-swipe operation on the corresponding application notification window in the notification aggregation window 1401 . Exemplarily, referring to (1) in FIG. 13 d , the user performs a left swipe operation on the notification window 1407 of the short message application. In response to the user's operation, the mobile phone displays the notification center interface as shown in (2) in Figure 13d. Referring to (2) in FIG. 13d , due to the user's left-swipe operation, only the right half of the SMS application notification window 1407 is displayed in the notification aggregation window. On the right side of the notification window 1407 of the short message application, an option 1408 to be deleted is displayed in the notification aggregation window. When the user clicks on the delete option 1408, in response to the user operation, the mobile phone executes the operation of deleting the SMS application notification window in the notification aggregation window 1401, so that only the WeChat application notification window is displayed in the notification aggregation window 1401.

It should be pointed out that the functions of each application notification window in the notification aggregation window can inherit the functions of the existing application notification window, including clicking to view, folding and unfolding, left sliding to delete, and automatic deletion after clicking to view. A repeat.

It should be noted that if there is only one application notification window in the notification aggregation window, the user performs a left-swipe operation on the application notification window to delete the application notification window in the notification aggregation window, which can be equivalent to the user clicking on the notification aggregation window. Swipe left to delete the notification aggregation window on the notification center interface. That is, when the notification aggregation window includes only one application notification window, the user performs a left-swipe operation on the application notification window and then clicks the delete option. In response to the user's operation, the notification aggregation window is no longer displayed on the notification center interface.

It should be pointed out that in the notification center interface, not only the notification aggregation window provided by this embodiment can be displayed, but also other application notification windows can be displayed in an existing manner according to the notification message receiving situation. Exemplarily, as shown in FIG. 14 , a notification aggregation window 1401 and a WeChat application notification window 1402 are displayed on the mobile phone notification center interface. Wherein, in the notification aggregation window 1401, a short message application notification window 14011 and a WeChat application notification window 14012 are displayed. Although both the WeChat application notification window 14012 and the WeChat application notification window 1402 display notification messages sent in the WeChat application, the notification messages displayed in the WeChat application notification window 14012 are those that the user is interested in or concerned about, and have been notified with contacts. The group "boss" is associated and aggregated and displayed in the notification aggregation window 1401 corresponding to the contact notification message group "boss". However, the notification message displayed in the WeChat application notification window 1402 is currently not associated with any notification message group, so it is displayed in the corresponding application notification window in the existing manner.

In the foregoing embodiments, an explanation is made by taking a notification aggregation window corresponding to a contact notification message group as an example. Similarly, a notification aggregation window can also correspond to any notification message group, where the notification message group can be customized by the user based on personal needs, and the notification messages associated in the notification message group can come from the same application, It may also come from different applications, which is not limited in this embodiment.

Exemplarily, if the notification message that the user cares about or is interested in is a message sent by contact A in a certain application (such as WeChat application), and a notification sent by contact B in another application (such as a short message application) message, you can create a notification message group, and combine the notification message sent by contact A in the corresponding application (such as WeChat application), and the notification message sent by contact B in the corresponding application (such as SMS application), Associate with the notification message group. Furthermore, the notification message sent by contact A in the corresponding application (such as WeChat application) and the notification message sent by contact B in the corresponding application (such as SMS application) received subsequently will be displayed in the notification In the notification aggregation window corresponding to the message group. Furthermore, the notification message sent by contact A in the corresponding application (such as WeChat application) and the notification message sent by contact B in the corresponding application (such as SMS application) received subsequently will be displayed in the notification In the notification aggregation window corresponding to the message group. For example, if the short message sent by the contact "Zhang XX" and the WeChat message sent by the WeChat friend "Li" are notification messages that the mobile phone user is interested in or concerned about, the mobile phone user can create a notification message group 1 and assign the contact "Zhang XX The application name and conversation ID (ConversationID) corresponding to the short message sent by "" and the application name and conversation ID (ConversationID) corresponding to the WeChat notification message sent by WeChat friend "Li" are associated with notification message group 1, so that subsequent The received short message sent by the contact "Zhang XX" and the WeChat message sent by the WeChat friend "Li" will be displayed in the notification aggregation window corresponding to the notification message group 1. As shown in FIG. 15 , the notification aggregation window 1501 is a notification aggregation window corresponding to the notification message group 1. In the notification aggregation window 1501 , a short message application notification window 15011 and a WeChat application notification window 15012 can be aggregated and displayed. Among them, the short message application notification window 15011 displays the short message sent by the contact "Zhang XX", and the WeChat application notification window 15012 displays the WeChat notification message sent by the WeChat friend "Li".

As another example, if the notification message that the user is concerned about or interested in is the notification message sent by contact A and contact B in a certain application (such as a WeChat application), a notification message group can be created and the contact The notification messages sent by A and contact B in the application are associated with the notification message group. Furthermore, the subsequent notification messages sent by contact A and contact B in the application will be displayed in the notification aggregation window corresponding to the notification message group. For example, if the WeChat notification message sent by the WeChat friend "CC" and the WeChat friend "ZZ" is a notification message that the mobile phone user is interested in or concerned about, the mobile phone user can create a notification message group 2 and group the WeChat friend "CC" and the WeChat friend "ZZ". The application names and conversation IDs (ConversationID) corresponding to the WeChat notification messages sent by ZZ” are associated with the notification message group 2, so that the WeChat notification messages sent by WeChat friend “CC” and WeChat friend “ZZ” received subsequently , will be displayed in the notification aggregation window corresponding to notification message group 2. As shown in FIG. 16 , the notification aggregation window 1601 is a notification aggregation window corresponding to the notification message group 2, and the WeChat application notification window 16011 and the WeChat application notification window 16012 can be aggregated and displayed in the notification aggregation window 1601 . Among them, the WeChat application notification window 16011 displays the WeChat notification message sent by the WeChat friend "CC", and the WeChat application notification window 16012 displays the WeChat notification message sent by the WeChat friend "ZZ".

Among them, the creation and management process of notification message group 1 or 2, the process of associating or disassocating the application name and session ID corresponding to the notification message with the notification message group, and other details that have not been explained in detail can refer to the above, here No longer.

This embodiment also provides a computer storage medium, in which computer instructions are stored, and when the computer instructions are run on the electronic device, the electronic device executes the above-mentioned related method steps to realize the display of the notification message in the above-mentioned embodiment method.

This embodiment also provides a computer program product, which, when running on a computer, causes the computer to execute the above related steps, so as to realize the method for displaying the notification message in the above embodiment.

Embodiments of the present application also provide a device, which may specifically be a chip, component or module, and the device may include a connected processor and a memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor The computer execution instructions stored in the memory can be executed, so that the chip executes the method for displaying the notification message in the above method embodiments.

In addition, embodiments of the present application also provide a chip, which may include one or more processing circuits and one or more transceiver pins; wherein, the transceiver pins and the processing circuits communicate with each other through an internal connection path The processing circuit executes the above related method steps to implement the notification message display method in the above embodiment, to control the receiving pin to receive a signal, and to control the sending pin to send a signal.

Among them, the electronic devices (such as mobile phones, etc.), computer storage media, computer program products or chips provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that it can achieve can refer to the above The beneficial effects of the corresponding method provided herein will not be repeated here.

Through the description of the above embodiments, those skilled in the art can understand that for the convenience and brevity of the description, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions can be assigned by different Completion of functional modules means that the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or It may be integrated into another device, or some features may be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still understand the foregoing The technical solutions described in each embodiment are modified, or some of the technical features are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the application.

Claims (19)

1. A method for displaying a notification message, comprising:

displaying a first interface;

the first interface comprises a first notification window, at least one second notification window is displayed in the first notification window, the second notification window is an application notification window, and application notification messages interesting to a user are respectively displayed in each second notification window;

the notification message group corresponding to the first notification window is created by a user in advance according to requirements, and the application name and the session identifier of the application notification message displayed in each second notification window are associated with the notification message group by the user in advance according to requirements;

the application notification messages displayed in the second notification windows have different application names and/or session identifiers, and the session identifiers are used for indicating sending users of the application notification messages.

2. The method of claim 1,

the first notification window is used for displaying application notification messages corresponding to the first contact in an aggregation mode; and each second notification window is respectively used for displaying notification messages sent by the first contact in different applications.

3. The method of claim 1, wherein displaying the first interface comprises:

acquiring a first notification message, and determining the name of a first application to which the first notification message belongs and a first session identifier of the first notification message;

if the first contact group to which the first notification message belongs is determined to exist according to the name of the first application and the first session identifier, displaying the first notification message in a second notification window corresponding to the name of the first application in the first notification window;

the first notification window is a notification window corresponding to the first contact group.

4. The method of claim 3, further comprising, prior to said displaying the first interface:

displaying a second interface; the second interface comprises a third notification window, and a second notification message of the first application is displayed in the third notification window; wherein the session identifier of the second notification message is the first session identifier;

in response to a first operation, a first contact group is created and the name of the first application and the first session identification are associated with the first contact group.

5. The method of claim 3, prior to said displaying the first interface, further comprising:

displaying a third interface; the third interface comprises a fourth notification window, and a third notification message of the first application is displayed in the fourth notification window; wherein the session identifier of the third notification message is the first session identifier;

associating the name of the first application and the first session identification with the first contact group in response to a second operation.

6. The method of claim 4 or 5, further comprising:

displaying a fourth interface; the fourth interface comprises a fifth notification window, and a fourth notification message of the second application is displayed in the fifth notification window; wherein, the session identifier of the fourth notification message is a second session identifier;

in response to a third operation, associating the name of the second application and the second session identification with the first contact group.

7. The method of claim 4, wherein, when creating the first group of contacts, further comprising:

and responding to a fourth operation, and performing personalized setting on the first contact group.

8. The method of claim 4 or 5, further comprising:

displaying a fifth interface; the fifth interface displays the identifier of the first application;

in response to a fifth operation on the identification of the first application, disassociating the name of the first application and the first session identification from the first contact group.

9. The method of claim 4 or 5, further comprising:

displaying a fifth interface; the fifth interface displays the identifier of the first application;

displaying a sixth interface in response to a sixth operation on the identification of the first application;

and displaying a session interface corresponding to the first session identifier in the first application in the sixth interface.

10. The method of claim 4 or 5, further comprising:

displaying a seventh interface; a contact person grouping list is displayed on the seventh interface, and the contact person grouping list comprises the identifier of the first contact person group;

in response to a seventh operation on the identification of the first contact group, displaying an eighth interface; and personalized setting information of the first contact person group is displayed in the eighth interface.

11. The method of claim 4 or 5, further comprising:

displaying a seventh interface; a contact person grouping list is displayed on the seventh interface, and the contact person grouping list comprises the identifier of the first contact person group;

deleting the first group of contacts in response to an eighth operation on the identification of the first group of contacts.

12. The method of claim 1 or 2, further comprising:

in response to a ninth operation on the first notification window, the first notification window is switched from an unfolded state to a folded state;

in response to a tenth operation on the first notification window, the first notification window is switched from a collapsed state to an expanded state.

13. The method of claim 1 or 2, further comprising:

in response to an eleventh operation on the first notification window, deleting the first notification window in an interface.

14. The method of claim 1 or 2, further comprising:

in response to a twelfth operation on the second notification window, deleting the second notification window in the first notification window.

15. The method of claim 3, further comprising:

and responding to a thirteenth operation of the second notification window, acquiring a name and a third session identifier of a third application corresponding to the second notification window, and disassociating the name and the third session identifier of the third application from the first contact group.

16. The method of claim 3, further comprising:

and if the first contact person group to which the first notification message belongs does not exist according to the name of the first application and the first session identification, displaying the first notification message in an application notification window corresponding to the first application.

17. The method of claim 4, wherein creating a first contact group and associating the name of the first application and the first session identification with the first contact group comprises:

adding a first record corresponding to the first contact group in a first data table; the first record at least comprises a contact person grouping identifier, and the contact person grouping identifier is a primary key of the first data table;

adding a second record corresponding to the name of the first application and the first session identification in a second data table, wherein the second record at least comprises the application name to which the notification message belongs, the session identification of the notification message, and a contact group; the application name to which the notification message belongs and the session identifier of the notification message are both the primary key of the second data table, and the contact group is the external key of the first data table and is associated with the contact group identifier in the first data table.

18. An electronic device, comprising:

one or more processors;

a memory;

and one or more computer programs, wherein the one or more computer programs are stored on the memory, and when executed by the one or more processors, cause the electronic device to perform the method of displaying the notification message of any of claims 1-17.

19. A computer-readable storage medium comprising a computer program which, when run on an electronic device, causes the electronic device to perform a method of displaying a notification message according to any of claims 1-17.

Images