CN114780268A

CN114780268A - Notification message display method and electronic equipment

Info

Publication number: CN114780268A
Application number: CN202210704580.7A
Authority: CN
Inventors: 王彦恒
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-06-21
Filing date: 2022-06-21
Publication date: 2022-07-22
Anticipated expiration: 2042-06-21
Also published as: CN114780268B

Abstract

The embodiment of the application provides a display method of a notification message and electronic equipment. The method comprises the steps that a first notification window is displayed in an interface of the electronic equipment for displaying notification messages, at least one second notification window is displayed in the first notification window, and application notification messages interesting to a user are respectively displayed in each second notification window. Therefore, the display method can display the notification messages interested by the user in one notification message window in an aggregated mode, so that the user can conveniently check the notification messages, the user does not need to search the notification windows from a large number of application notification windows one by one, and the user experience is improved.

Description

Notification message display method and electronic equipment

Technical Field

The application relates to the technical field of intelligent terminals, in particular to a message notification display method and electronic equipment.

Background

With the popularization of terminal devices and terminal applications, more and more terminal applications notify users in a message pushing manner, and messages notifying the users are called notification messages. The user can see these pushed notification messages at the terminal device lock screen interface or the notification center (or notification bar) of the terminal device.

The popularization of terminal applications and the number of terminal applications installed by users have increased, with the consequent excessive number of notification messages and unfocused contents, the various notification messages being interleaved with each other, making it difficult for users to find the notification messages of their own interest quickly.

Disclosure of Invention

In order to solve the foregoing technical problem, an embodiment of the present application provides a notification message display method and an electronic device. In the method, the notification messages which are interested by the user can be aggregated in one notification message window for display, so that the user can conveniently check the notification messages, and the use experience of the user is improved.

In a first aspect, an embodiment of the present application provides a method for displaying a notification message. The method comprises the following steps: the electronic equipment displays a first interface; the first interface comprises a first notification window, at least one second notification window is displayed in the first notification window, and application notification messages which are interesting to the user are respectively displayed in each second notification window.

The first interface may be any interface that displays a notification message window, such as a notification center interface. For example, in addition to the first notification window, an application notification window corresponding to an arbitrary application, such as the application notification window 101, the application notification window 102, and the application notification window 103 shown in (2) in fig. 1, may be displayed in the first interface.

The first notification window is a notification aggregation display window, and the second notification window is an application notification window which is displayed in an aggregation mode in the first notification window. Illustratively, the application may be a social application, such as WeChat, QQ, short message, and the like.

Illustratively, any two second notification windows may correspond to the same application, such as a notification window for a WeChat application. That is, any two second notification windows may display notification messages from the same application.

Also illustratively, any two second notification windows may correspond to different applications, such as one for a short message application window and one for a short message application window. That is, any two second notification windows may display notification messages from different applications.

Therefore, the notification messages which are interested by the user can be aggregated and displayed in one notification message window, so that the user can check the notification messages conveniently, and the user experience is improved. The notification message of interest to the user may originate from the same application or from different applications.

According to a first aspect, a first notification window is used for displaying application notification messages corresponding to a first contact in an aggregation manner; the second notification windows are respectively used for displaying notification messages sent by the first contact in different applications.

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

Therefore, no matter which application the contact sends the notification message to the electronic equipment user, the electronic equipment user can view the corresponding notification message in the notification aggregation window corresponding to the contact without searching from a large number of application notification windows one by one, and the time cost for obtaining the information of interest by the user is simplified. The electronic equipment can wakedly display the contact notification message really concerned by the user to the user, so that the use experience of the user is improved.

According to a first aspect, or any implementation manner of the first aspect above, an electronic device displays a first interface, including: the electronic equipment acquires the first notification message, and determines 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 electronic equipment determines that a first contact person group to which the first notification message belongs exists 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.

Thus, if notification messages have been grouped based on contacts, the electronic device may display the notification messages in the notification aggregation window corresponding to the respective group.

According to the first aspect, or any implementation manner of the first aspect, before the electronic device displays the first interface, the method further includes: the electronic equipment displays 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; the session identifier of the second notification message is the first session identifier; in response to the first operation, a first contact group is created and a name of the first application and a first session identification are associated with the first contact group.

The second interface may be any interface that displays 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 notification messages sent by a contact of interest in an application, so that when other notification messages sent by the same contact in the application are received later, the notification messages can be displayed in a notification aggregation window corresponding to the contact group.

According to the first aspect, or any implementation manner of the first aspect above, before the electronic device displays the first interface, the method further includes: 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; the electronic device associates the name of the first application and the first session identification with the first contact group in response to the second operation.

The third interface may be any interface that displays 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 a notification message sent by an interested contact in a certain application, a user can associate an application name and a session identifier corresponding to the notification message with an existing contact group, so that when other notification messages sent by the same contact in the application are subsequently received, the notification messages can be displayed in a notification aggregation window corresponding to the contact group.

According to the first aspect, or any one of the above implementation manners of the first aspect, the method further includes: the electronic equipment displays 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; the session identifier of the fourth notification message is a second session identifier; in response to a third operation, the name of the second application and the second session identification are associated with the first group of contacts.

The fourth interface may be any interface that displays 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 the session identifier corresponding to the notification message with the existing contact group, so that when other notification messages sent by the same contact in the application are subsequently received, the notification messages can be displayed in the notification aggregation window corresponding to the contact group.

According to a first aspect, or any one of the above implementations of the first aspect, the method further comprises: and when the electronic equipment creates the first contact group, the electronic equipment carries out personalized setting on the first contact group in response to the fourth operation.

Illustratively, the personalized settings may include: a notification ring tone, a notification message display font, a notification window background color, a top-up display, an avatar, etc.

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

According to the first aspect, or any one of the above implementation manners of the first aspect, the method further includes: the electronic equipment displays 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, the electronic device disassociates the name of the first application and the first session identification from the first contact group.

Wherein the fifth interface may be understood as an application list interface associated with the contact group.

In this way, the user can perform deletion management on the applications associated with each contact group to avoid that notification messages that are no longer of interest remain displayed in the notification aggregation window.

According to the first aspect, or any one of the above implementation manners of the first aspect, the method further includes: the electronic equipment displays a fifth interface; the fifth interface displays the identifier of the first application; in response to a sixth operation on the identification of the first application, the electronic device displays a sixth interface; and displaying a session interface corresponding to the first session identifier in the first application in a sixth interface.

Therefore, the user can conveniently view the corresponding application session interface so that the user can confirm whether the notification message is sent out for the contact person interested in the user.

According to a first aspect, or any one of the above implementations of the first aspect, the method further comprises: the electronic equipment displays 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, the electronic device displays an eighth interface; and personalized setting information of the first contact group is displayed in the eighth interface.

Therefore, the user can conveniently check the details of each contact person group and perform personalized setting management.

According to the first aspect, or any one of the above implementation manners of the first aspect, the method further includes: the electronic equipment displays 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; the electronic device deletes the first group of contacts in response to an eighth operation on the identification of the first group of contacts.

In this way, the user can conveniently delete and manage the contact group, so that the notification message of the contact which is no longer interested can be still displayed in an aggregation mode.

According to the first aspect, or any one of the above implementation manners of the first aspect, the method further includes: the electronic equipment responds to a ninth operation on the first notification window, and the first notification window is switched from the unfolded state to the folded state; the electronic device responds to a tenth operation on the first notification window, and the first notification window is switched from the folded state to the unfolded state.

According to a first aspect, or any one of the above implementations of the first aspect, the method further comprises: and in response to the eleventh operation on the first notification window, deleting the first notification window in the interface.

According to a first aspect, or any one of the above implementations of the first aspect, the method further comprises: in response to the twelfth operation on the second notification window, the second notification window is deleted in the first notification window.

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

According to the first aspect, or any one of the above implementation manners of the first aspect, the method further includes: and responding to a thirteenth operation of the second notification window, acquiring a name and a third session identification of a third application corresponding to the second notification window, and disassociating the name and the third session identification of the third application from the first contact group.

In this way, in the notification aggregation window interface, the user can also perform deletion management on the applications associated with the contact group, so as to prevent notification messages that are no longer of interest from being still displayed in the notification aggregation window.

According to the first aspect, or any one of the above implementation manners of the first aspect, the method further includes: and if the electronic equipment determines that the first contact 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.

Thus, if the notification messages are not grouped based on contact, the electronic device may display the notification messages in the corresponding application notification window, as in the prior art.

For example, the first operation to the thirteenth operation mentioned above may refer to corresponding user operations in the following embodiments, which are not limited in this embodiment.

According to a first aspect, or any implementation manner of the first aspect above, the electronic device creating a first contact group, and associating a name of a first application and a first session identifier with the first contact group, includes: the electronic equipment adds a first record corresponding to the first contact group in the first data table; the first record at least comprises a contact person grouping identifier, and the contact person grouping identifier is a main key of the first data table; the electronic equipment adds 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 the primary key of the second data table, and the contact person group is the external key of the first data table and is associated with the contact person group identifier in the first data table.

For example, the first data table may be a groupInformation data table described below, and the second data table may be a conditionlist data table described below.

Similarly, deleting a record in the second data table may enable disassociation of the application name and session identification from the contacted group. Deleting a record in the first data table while deleting an associated record in the second data table may enable deleting a group of contacts.

In a second aspect, an embodiment of the present application provides an electronic device. The electronic device includes: 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 a notification message of any one of the first aspect and the first aspect.

Any one implementation manner of the second aspect and the second aspect corresponds to any one implementation manner of the first aspect and the first aspect, respectively. For technical effects corresponding to any one implementation manner of the second aspect and the second aspect, reference may be made to the technical effects corresponding to any one implementation manner of the first aspect and the first aspect, and details are not repeated here.

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

Any one implementation manner of the third aspect corresponds to any one implementation manner of the first aspect. For technical effects corresponding to any one implementation manner of the third aspect and the third aspect, reference may be made to the technical effects corresponding to any one implementation manner of the first aspect and the first aspect, and details are not described here again.

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

Any one implementation manner of the fourth aspect and the fourth aspect corresponds to any one implementation manner of the first aspect and the first aspect, respectively. For technical effects corresponding to any one implementation manner of the fourth aspect and the fourth aspect, reference may be made to the technical effects corresponding to any one implementation manner of the first aspect and the first aspect, and details are not repeated here.

In a fifth aspect, the present application provides a chip, which includes a processing circuit and a transceiver pin. Wherein the transceiving pin and the processing circuit are in communication with each other through an internal connection path, and the processing circuit performs the method of displaying the notification message as in any one of the first aspect or the first aspect to control the receiving pin to receive the signal and to control the transmitting pin to transmit the signal.

Any one implementation manner of the fifth aspect and the fifth aspect corresponds to any one implementation manner of the first aspect and the first aspect, respectively. For technical effects corresponding to any one of the implementation manners of the fifth aspect and the fifth aspect, reference may be made to the technical effects corresponding to any one of the implementation manners of the first aspect and the first aspect, and details are not described here.

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 architecture of an exemplary illustrated electronic device;

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

6 a-6 c are diagrams illustrating an application scenario;

FIGS. 7 a-7 c are schematic diagrams of an exemplary application scenario;

8 a-8 b are diagrams illustrating an exemplary application scenario;

FIGS. 9 a-9 d are diagrams illustrating 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 an embodiment of the present application;

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

FIGS. 13 a-13 d are diagrams illustrating an application scenario;

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 Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.

The terms "first" and "second," and the like, in the description and in the claims of the embodiments of the present application are used for distinguishing between different objects and not for describing a particular order of the objects. For example, the first target object and the second target object, etc. are specific sequences for distinguishing different target objects, rather than describing target objects.

In the embodiments of the present application, the words "exemplary" or "such as" are used herein to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

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

The popularity of terminal applications and the number of terminal applications installed by users have increased, with the consequent excessive number of notification messages and unfocused contents, the various notification messages being interlaced with each other, making it difficult for users to find out quickly the notification messages that they are interested in. The terminal device often performs aggregation presentation on notification messages from the same source, and displays the aggregated notification messages in the notification bar, so that the interface of the notification bar becomes concise and not cluttered to a certain extent. Illustratively, the terminal device groups the notification messages based on the notification ID, wherein the notification ID is predefined by the system. When the application sends the notification, one notification ID is selected by the application for sending, and the terminal carries out aggregation display on the notification messages based on the notification ID.

The following explanation is given by taking a mobile phone as an example, and is also given by taking other terminal devices as examples, and details are not repeated.

Fig. 1 shows an exemplary application scenario. Referring to fig. 1, while the mobile phone displays a main interface as shown in (1) of fig. 1, a user performs a slide-down operation on the left side of the top of the screen, and in response to the user operation, the mobile phone interface switches, and a notification center interface (or a notification bar interface) as shown in (2) of fig. 1 is displayed. As shown in (2) in fig. 1, in the notification center interface, notification messages from the same source are merged and displayed. Illustratively, notification messages from a WeChat application are displayed in a notification window (or notification card) 101, notification messages from a video application are displayed in a notification window 102, and notification messages from a short message application (or information application) are displayed in a notification window 103.

Fig. 2 shows an exemplary application scenario. Referring to fig. 2 (1), the mobile phone displays a plurality of notification windows in the screen locking interface, which are respectively used for merging and displaying communication messages from different applications. Illustratively, 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 short message application. Since the mobile phone is currently in a screen locking state, in order to protect the privacy of the user, only the number of notifications from a certain 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, which can be shown in (2) in fig. 2. Illustratively, details of 4 notifications from the WeChat application are displayed in the notification window 204, details of 1 notification from the video application are displayed in the notification window 205, and details of 1 notification from the short message application are displayed in the notification window 206.

However, the popularity of terminal applications and the number of terminal applications installed by users have risen, with the consequent plethora of notification messages and unfocused contents, various notification messages being interleaved with each other, making it difficult for users to quickly find out the notification message of their own interest.

When a plurality of social applications, such as WeChat, QQ, short message, Payment treasures, tremble, etc., are installed in the terminal device, the same person may send notification messages to the terminal device user based on the different applications. In the existing notification message display scheme, because the notification messages of each application are respectively combined and displayed, the notification messages sent by the same person to terminal equipment users in different applications are independently displayed, so that the user is difficult to quickly focus on the notification messages of a certain person concerned by the user, and the user experience is low.

Referring to (2) in fig. 1 or (2) in fig. 2, it is assumed that "Chen" in the wechat application contact and "Chen somebody" in the short message application contact are the same person in real life, and the notification messages sent by the person in each application are notification messages of which the user is interested more. However, notification messages issued by the person in different applications are displayed in different notification windows. Therefore, it is difficult for the user to quickly focus on the notification message of the person concerned by the user, and especially when the number of notification windows is large, the user is difficult to quickly find the notification message sent by the person through different applications in the plurality of notification windows, and the user experience is low.

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 referred to as a terminal device, and the terminal may be a cellular phone (cellular phone) or a tablet computer (pad), which is not limited in this application. It should be noted that the structural schematic diagram of the electronic device 100 can be applied to the mobile phone in fig. 1-2. It should be understood that the electronic device 100 shown in fig. 3 is only one example of an electronic device, and that the electronic device 100 may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration of components. The various components shown in fig. 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: the mobile terminal includes a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identity Module (SIM) card interface 195, and the like. Wherein 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, etc.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

Wherein the controller may be a neural center and a command center of the electronic device 100. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

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

The USB interface 130 is an interface conforming to the USB standard specification, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transmit data between the electronic device 100 and a peripheral device. And the method can also be used for connecting a headset and playing audio through the headset. The interface may also be used to connect other electronic devices, such as AR devices and the like.

The charging management module 140 is configured to receive a charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger via 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. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142.

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

The wireless communication function of the electronic device 100 may be implemented 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.

The

antennas

1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may 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 may provide a solution including wireless communication of 2G/3G/4G/5G, etc. applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like.

The wireless communication module 160 may provide solutions for wireless communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like.

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

The electronic device 100 implements display functions via 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 an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, 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, with N being a positive integer greater than 1.

The electronic device 100 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display 194, the application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability 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 code, which includes instructions. The processor 110 executes instructions stored in the internal memory 121 to execute various functional applications and data processing of the electronic device 100, for example, to enable the electronic device 100 to implement a display method of a notification message in the embodiment of the present application. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The storage data area may store data (such as audio data, phone book, etc.) created during use of the electronic device 100, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like.

The electronic device 100 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headset interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a 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 disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The electronic apparatus 100 can listen to music through the speaker 170A or listen to a hands-free call. In some embodiments, the electronic device 100 may be provided with a plurality of speakers 170A.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the electronic apparatus 100 receives a call or voice information, it can receive voice by placing the receiver 170B close to the ear of the person.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking the user's mouth near the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and perform directional recording.

The headphone interface 170D is used to connect a wired headphone. The headset interface 170D may be the USB interface 130, or may be a 3.5mm open mobile electronic device platform (OMTP) standard interface, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor is used for sensing a pressure signal and converting the pressure signal into an electric signal. In some embodiments, the pressure sensor may be disposed on the display screen 194. The electronic apparatus 100 may also calculate the touched position based on the detection signal of the pressure sensor.

The gyro sensor may be used to determine the motion pose of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 about three axes (i.e., the x, y, and z axes) may be determined by a gyroscope sensor.

The acceleration sensor may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The acceleration sensor can detect the magnitude and direction of gravity when the electronic device 100 is stationary. The acceleration sensor can also be used for identifying the posture of the electronic equipment, and is applied to transverse and vertical screen switching, pedometers and other applications.

Touch sensors, also known as "touch panels". The touch sensor may be disposed on the display screen 194, and the touch sensor and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor is used to detect a touch operation applied thereto or nearby. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic apparatus 100 may receive a key input, and generate a key signal input related to user setting and function control of the electronic apparatus 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The software system of the electronic device 100 may employ a hierarchical architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the electronic device 100.

Fig. 4 is a block diagram of a 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, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android Runtime (Android Runtime) and system library, and a kernel layer from top to bottom.

The application layer may include a series of application packages.

As shown in fig. 4, the application package may include applications such as WeChat, SMS, setup, Notification center, social application, Lancher, Notification packet management Module, and so on. Illustratively, the application packages may also include applications for calling, calendaring, maps, navigation, music, video, and so forth.

The social application may refer to any application capable of sending notification messages between contacts (or called friends), such as QQ, tremble, pay pal, and the like.

Among them, launchers may also be referred to as desktop applications or home screens. Generally, after the Android system is started, the Launcher can be used as a core application to reside in the Android system to run.

The notification center may be configured to implement presentation of the notification message, for example, presentation of communication messages from each application program.

In this embodiment, the notification group management module may be configured to implement management of displaying notification message groups based on contacts. The notification packet management module may be an independent functional module, or may be integrated in Lancher or a setting application, which is not limited in this embodiment. For example, the notification group management module may add or delete a contact notification message group (or called a contact group), add or delete application session information associated with a certain contact notification message group, and determine whether the notification message is grouped based on a contact based on an application name and a session identifier to which the notification message belongs.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 4, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and answered, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short 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 for the electronic device 100. Such as management of call status (including on, off, etc.).

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

The notification manager enables the application program to display notification information (or called notification messages) in the status bar (or the notification center interface, etc.), can be used for conveying notification type messages, can automatically disappear after short-time stay, does not need user interaction, and can stay for a long time to disappear after the user deletes the messages. Such as notification messages used to inform download completion, message reminders, and the like. The notification message may also be a notification that appears in the form of a chart or scrollbar text in a status bar at the top of the system, such as a notification of a running application in the background, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

In this embodiment, the notification manager may be further configured to parse the session ID and the application name of the notification message, so that the notification grouping management module may determine whether the notification message is grouped based on the contact based on the session ID and the application name of the notification message. And if a certain notification message is grouped based on the contact person, displaying the notification message in a notification aggregation window corresponding to the corresponding contact person, otherwise, displaying the notification message based on the prior art.

The Android Runtime comprises a core library and a virtual machine. The Android Runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

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

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

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

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

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

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

It is understood that, in order to implement the method for displaying the notification message in the embodiment of the present application, the electronic device includes hardware and/or software modules for performing the respective functions. The present application is capable of being implemented in hardware or a combination of hardware and computer software in conjunction with the exemplary algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, in conjunction with the embodiments, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In order to solve the problem that a user is difficult to quickly find a notification message of a certain contact concerned by the user in a plurality of notification windows, the embodiment of the application provides a display method of the notification message. The user can perform customized grouping on the same contact person (corresponding to a certain person in real life) in different applications, and the terminal device performs aggregated display on notification messages sent by the same contact person in different applications based on the customized grouping. Therefore, no matter which application the contact sends the notification message to the terminal equipment user, the terminal equipment user can look up the corresponding notification message in the notification aggregation window corresponding to the contact, and the user does not need to look up the notification messages from a large number of application notification windows one by one, so that the time cost for obtaining the interesting information by the user is simplified. Therefore, the terminal equipment can be used for displaying the contact person notification message really concerned by the user to the user in a striking manner, and the use experience of the user is improved.

Fig. 5 shows an exemplary application scenario. If the mobile phone user is interested in the notification message sent by the contact in real life, such as "boss", the mobile phone user may allocate the notification message sent by the contact in each application to a notification aggregation packet, for example, allocate the notification message sent by the contact in WeChat, SMS, QQ, and other applications to the notification aggregation packet corresponding to the contact. Therefore, when the boss sends a notification message to the mobile phone user by using any application of the applications, the notification message is displayed in a notification aggregation group (or notification aggregation window) corresponding to the contact of the boss. As shown in fig. 5, taking a notification center page as an example, a notification aggregation window 301 corresponding to a contact in real life, such as "boss" is displayed on the mobile phone. In the notification aggregation window 301, at least one application notification window corresponding to the contact of "boss" is displayed, such as a short message application notification window 3011 and a wechat application notification window 3012. Whether the contact person of the "boss" sends a notification message to the mobile phone user from the 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 another application, the notification message is displayed in the notification aggregation window 301 corresponding to the contact person of the "boss". When the user clicks the short message application notification window 3011 or the wechat application notification window 3012, the mobile phone may display a corresponding application interface so that the user may view the session message or notification message in the application.

It should be noted that the contact corresponding to a certain notification aggregation window is a certain contact in real life, and the contact name "boss" may be customized by the mobile phone user, and may be the same as or different from the remark of the contact in a certain application. The contact name corresponding to a certain notification aggregation window is not subject to a certain application.

It should be noted that the notification center interface shown in (2) in fig. 1 and the lock screen unlocking interface shown in (2) in fig. 2 are only exemplary notification window display interfaces, and the notification window may also be displayed in other interfaces, which is not limited in this embodiment. The following explains the display method of the notification message provided in this embodiment by taking only the notification center interface as an example, and also takes other notification window display interfaces as examples, which are not described again.

Before the mobile phone displays the notification message aggregation based on the contacts, a mobile phone user needs to create a contact notification message group according to personal requirements. Furthermore, after the contact person notification message packet is created, the mobile phone can perform notification message aggregation display in the notification aggregation window corresponding to the contact person notification message packet. The following explains the flows of creating and managing a contact notification message group, and displaying a notification message aggregate based on the contact notification message group in detail.

Scene one

In this scenario, the mobile phone does not have a contact notification message packet, and when the mobile phone receives a notification message, the mobile phone user can complete the creation of the contact notification message packet based on personal requirements. In the process of creating the contact person notification message packet, the notification packet management module of the mobile phone realizes the association between the contact person notification message packet and the application session information of the notification message.

Fig. 6 a-6 c illustrate an application scenario in which a user creates a contact notification message packet.

As shown in (1) in fig. 6a, in response to the sending of the notification message by the wechat application, a notification window 401 corresponding to the wechat application is displayed on the mobile phone notification center interface. In the notification window 401, the transmission time "just" of the WeChat application notification message, the sender "Chen" and the information content "xxxxxxxx" are displayed. If the sender "Chen" of the notification message is a contact (assumed to be "boss") that the mobile phone user is interested in, the mobile phone user can create a notification message packet corresponding to the contact "boss" so that the notification message sent by the contact "boss" in the WeChat application can be displayed in the notification aggregation window corresponding to the contact "boss". At this time, the cell phone user can perform a left-swipe operation in the notification window 401. In response to the user operation, the mobile phone displays an interface as shown in (2) in fig. 6 a. Referring to fig. 6a (2), due to the user's left-slide operation, only the right half of the notification window 401 is displayed on the interface. On the right side of the notification window 401, a contact notification message packet creation option 402 and a notification window deletion option 403 are displayed on the interface. When the user clicks the notification window delete option 403, the handset deletes the notification window 401 on the interface in response to the user operation. When the user clicks on the contact notification message packet creation option 402, the handset creates a contact notification message packet corresponding to "boss" in response to user action.

Fig. 6b (1) shows an information interface of a contact notification message packet by way of example. In response to the user clicking on the contact notification message packet creation option 402, the handset may display an interface as shown in fig. 6b (1). In this interface, the user can set the information of the contact notification message packet. Illustratively, the user clicks on the avatar option 501 and selects an image in the gallery, which may enable avatar settings for contact notification message groupings; the user clicks the grouping name option and types in the text information, so that the name setting of the contact person notification message grouping can be realized. As another example, the user may set whether to allow the contact notification message packet to be notified by clicking on the toggle option 503. As another example, user click option 504 may select a notification ring tone for a group of contact notification messages, user click option 505 may select a message font for a group of contact notification messages, user actuation of switch option 506 may set whether to top display a group of contact notification messages, and user click option 507 may select a background color for a message aggregation window for a group of contact notification messages. In this way, the user can personalize the contact notification message packet.

Fig. 6b (2) shows exemplary information of a contact notification message packet. The name of the contact person notification message packet is 'boss', the contact person notification message packet is allowed to carry out message notification, the notification ring of the contact person notification message packet is ring Y, the message font is font Y, the background color of the message aggregation window is gray, and the contact person notification message packet is displayed on the top. Referring to (2) in fig. 6b, in the information interface of the contact notification message packet, a confirmation option and a cancel option may also be displayed. When the user clicks the confirmation option, the mobile phone stores the information of the current contact person notification message packet and completes the creation of the contact person notification message packet. When the user clicks the cancel option, the mobile phone does not store the information of the current contact person notification message packet, and cancels the creation of the current contact person notification message packet.

With continued reference to fig. 6b (1), in the information interface of the contact notification message grouping, a grouping application details option 508 is also displayed. After the contact notification message packet "boss" is created, as shown in fig. 6b (2), the user clicks on the packet application details option 508, and in response to the user operation, the handset displays an application management interface as shown in fig. 6c (1). In the application management interface, the application information related to the contact person notification message group is displayed, that is, the application corresponding to the notification message which needs to be displayed in the contact person notification message group in an aggregated manner is displayed. Illustratively, the user creates a contact notification message packet based on the WeChat application message, so the application involved in the contact notification message packet includes WeChat, as shown in (1) in FIG. 6 c. Referring to fig. 6c (1), when the user clicks the WeChat application option 601, in response to the user operation, the mobile phone displays a chat interface of a corresponding contact in the WeChat application (i.e., a contact corresponding to the contact notification message packet), as shown in fig. 6c (2).

When the contact person notification message packet is created, the notification packet management module of the mobile phone needs to store the data of the contact person notification message packet. For example, this embodiment may store the data of the contact notification message packet in a database form or a file form, and the like, which is not limited in this embodiment. The following explanation will be made by taking the database format as an example.

In this embodiment, the notification packet management module of the mobile phone may implement data storage and management of the contact notification message packet based on two data tables. One for storing information for contact notification message groupings and one for storing grouped (i.e., grouped based on contact notification message groupings) application session information. The two data tables may be associated based on the ID of the contact notification message packet.

For example, a data table (e.g. a groupInformation data table) for storing information of the contact notification message packet may include the following information: an Identification (ID) of the contact notification message packet, a name (name) of the contact notification message packet, whether the contact notification message packet is allowed to perform message notification (allow _ notify), a ring tone (ring) of the contact notification message packet, a message font (font) of the contact notification message packet, whether the contact notification message packet is top-displayed (stick), a head portrait (avatar) of the contact notification message packet, and a notification aggregation window background color (bg _ color) of the contact notification message packet.

The Identifier (ID) of the contact person notification message packet is used for uniquely identifying one contact person notification message packet, and the data type is an integer type (INT) and is a main key of a groupInformation data table. Illustratively, the ID of the contact notification message packet is automatically incremented starting with 1.

In the groupInformation data table, the name of the contact person notification message packet, whether the contact person notification message packet is allowed to perform message notification, the ring of the contact person notification message packet, the message font of the contact person notification message packet, whether the contact person notification message packet is displayed at the top, the head of the contact person notification message packet, and one or more of the background colors of the notification aggregation windows of the contact person notification message packet can be set with default values.

As another example, a data table (e.g., a conditional list data table) for storing the grouped application session information may include the following information: an Identification (ID) of the grouped notification message, an application name (pkg _ name) to which the notification message belongs, a session identification (conversation ID) in the application, and a group (group) of the contact notification message to which the notification message belongs.

Wherein the Identification (ID) of the grouped notification message is used for uniquely identifying one grouped notification message, and the data type is an integer type (INT). Illustratively, the ID of the grouped notification message is automatically incremented starting from 1.

The application name (pkg _ name) to which the notification message belongs can uniquely distinguish which application originated the notification message, and the session identification (conversation id) in the application can uniquely distinguish which contact in the application originated the notification message based on the determination of the application that issued the notification message. Therefore, the application name (pkg _ name) and the session identification (convertionid) in the application to which the notification message belongs can uniquely identify a grouped notification message. Therefore, in the contentionlist, the application name (pkg _ name) to which the notification message belongs and the session identifier (conversation id) in the application jointly form the primary key of the list.

It should be noted that the session identification (conversation id) in the application can uniquely distinguish which contact in the application sent the notification message. The session identifier (conversation id) in different applications may be the same, so the embodiment uses the application name (pkg _ name) to which the notification message belongs and the session identifier (conversation id) 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 session construction method, and carries a session identifier (conversation id) of the notification message in the application. When the notification manager receives a notification message sent by an application, the notification message is analyzed based on a predefined session construction method, and a session identifier (conversation id) of the notification message in the application is acquired. At this time, in combination with the name of the application sending the notification message and the session identifier (conversation id) 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 customized session construction method, and the notification message carries a session identifier (conversation id) of the notification message in the application. When the notification manager receives a notification message sent by an application, the notification message is analyzed based on a session construction method matched with the application, and a session identifier (conversation id) of the notification message in the application is acquired. At this time, by combining the application name for sending out the notification message and the session identifier (conversation id) of the notification message in the application, it can be determined whether a notification message is a grouped notification message.

In yet another alternative embodiment, a notification message is constructed using a custom based session construction method. When the notification manager receives a notification message sent by an application, a session identifier (conversation id) of the notification message in the application is acquired based on a relevant interface provided by the application. At this time, by combining the application name for sending out the notification message and the session identifier (conversation id) of the notification message in the application, it can be determined whether a notification message is a grouped notification message.

In the constraint list data table, the contact notification message group (group) to which the notification message belongs is a foreign key, and is associated with an Identification (ID) field of the contact notification message group in the group information data table, so as to identify the contact notification message group to which the notification message belongs.

With continued reference to fig. 6a (2), when the user clicks on the contact notification message packet creation option 402, in response to user operation, the notification packet management module of the handset creates a contact notification message packet corresponding to "boss". In the process that the notification grouping management module creates the contact notification message grouping corresponding to the boss, the notification grouping management module automatically generates an ID of the contact notification message grouping boss, and adds a record in the groupInformation data table for indicating the information of the contact notification message grouping boss according to the information setting (such as name, image, whether to allow notification, whether to set top, bell, font, window background color and the like) of the contact notification message grouping of the user. Then, the notification grouping management module automatically generates an ID of a grouped notification message, and adds a record in a contractuallist data table for indicating a piece of grouped application session information according to the application name (pkg _ name) to which the notification message belongs, the session identification (conversation ID) of the notification message sent by "Chen" in the WeChat application, and the ID of a newly-created contact notification message group "boss". Wherein, the contact notification message group (group) of the grouped notification message is the ID of the newly-created contact notification message group "boss", thereby realizing the association between the newly-created contact notification message group "boss" and the application session information (i.e. pkg _ name and conversation ID) of the grouped notification message (i.e. the notification message sent by "Chen" in the WeChat application).

At this point, the notification packet management module of the mobile phone completes the creation of a contact notification message packet. Wherein the created contact notification message packet is associated with a piece of application session information. That is, when a notification message matching the application session, that is, a notification message sent by "Chen" in the WeChat application, is received, the mobile phone will display the notification message in the notification aggregation window corresponding to the contact notification message packet "boss".

Scene two

In this scenario, a contact notification message packet exists in the mobile phone, and when the mobile phone receives a notification message that is not based on the contact packet, a mobile phone user can associate application session information corresponding to the notification message with an existing contact notification message packet based on personal requirements.

Fig. 7 a-7 c illustrate an application scenario in which a user groups notification messages based on already created contact notification message groups.

As shown in fig. 7a (1), in response to the short message application sending the notification message, a notification window 701 corresponding to the short message application is displayed on the mobile phone notification center interface. In the notification window 701, the transmission time "just" of the short message application notification message, the sender "old certain" and the information content "xxxxxxxx" are displayed. If the sender of the notification message "old certain" is a contact (assumed to be "boss") concerned by the mobile phone user, the mobile phone user may associate the application session information corresponding to the notification message with the contact notification message packet "boss" so that the notification message sent by "old certain" in the short message application may be displayed in the notification aggregation window corresponding to the contact "boss". At this time, the user of the mobile phone may perform a left-swipe operation in the notification window 701. In response to the user operation, the mobile phone displays an interface as shown in (2) in fig. 7 a. Referring to fig. 7a (2), due to the user's left-slide operation, 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 packet creation option 702 is displayed on the interface. When the user clicks on the contact notification message packet creation option 702, the handset displays a contact notification message packet list interface, as shown in (1) in fig. 7b, in response to the user operation.

Referring to the contact notification message packet list interface shown in (1) in fig. 7b, the currently created contact notification message packet includes two contact notification message packets named "boss" and "zhang san". If the user desires to have the notification message sent in the short message application of "certain" displayed in the notification aggregation window corresponding to the contact "boss", the option 801 corresponding to the contact notification message packet "boss" may be clicked to select the contact notification message packet "boss". As shown in (2) in fig. 7b, a circle is displayed in the circle of the option 801 identifying that the contact notification message packet "boss" is selected.

After the contact notification message packet "boss" is selected, if the user clicks the confirmation option 802, the notification packet management module of the mobile phone completes association of application session information corresponding to the notification message (i.e., "certain" notification message sent in short message application) with the contact notification message packet "boss". At this time, the data in the groupInformation data table is not increased, and a record is added in the conditionlist data table for indicating a piece of grouped application session information, that is, indicating the application session information corresponding to the notification message sent by 'one certain in the short message application'. The session information is grouped into a contact notification message group "boss", that is, a contact notification message group (group) of the session information is an ID of the contact notification message group "boss" in the groupInformation data table.

After the contact notification message packet "boss" is selected, if the user clicks the cancel option 803, the notification packet management module of the mobile phone does not adjust the contact notification message packet data, that is, the data in the groupInformation data table and the constraint data table are not changed.

The user clicks the confirmation option 802, and the notification packet management module of the mobile phone completes association of application session information corresponding to the notification message (i.e., "certain" notification message sent in short message application) with the contact notification message packet "boss". In this case, if the user clicks the grouping application detail option 508 (see fig. 6b (2)) in the grouping information interface of the contact notification message grouping "boss", the handset displays an application management interface as shown in fig. 7c (1) in response to the user operation. In the application management interface, the application information related to the contact person notification message group is displayed, that is, the application corresponding to the notification message which needs to be displayed in the contact person notification message group in an aggregated manner is displayed. As shown in (1) of fig. 7c, the applications related to the contact notification message packet include a WeChat and a short message. Referring to fig. 7c (1), when the user clicks the short message application option 901, in response to the user operation, the mobile phone displays a chat interface of a corresponding contact in the short message application (i.e., a contact corresponding to the contact notification message packet), as shown in fig. 7c (2).

So far, the notification packet management module of the mobile phone completes the association of application session information and the existing contact notification message packet "boss". When a notification message matching the application session is received, i.e. a notification message sent in a short message application of "old person" is received, the mobile phone will display the notification message in the notification aggregation window corresponding to the contact notification message group "boss".

The association between the wechat application session information and the contact notification message packet "boss" is implemented when the contact notification message packet "boss" is created (see scene one), and the association between the short message application session information and the contact notification message packet "boss" is implemented after the contact notification message packet "boss" is created. Similarly, when the mobile phone receives a notification message sent by a contact "boss" in another application (e.g., QQ, pay for treasure, etc.), the user may associate session information of the notification message with the contact notification message group "boss" so that the contact "boss" may be displayed in the notification aggregation window corresponding to the contact notification message group "boss" through the notification message sent in each application, which is not described in detail in this embodiment.

Scene three

In this scenario, a group of contact notification messages exists in the mobile phone, and when the mobile phone receives a notification message that is not based on the group of contacts, a user of the mobile phone can create a new group of contact notification messages based on personal needs. In the process of creating the new contact notification message packet, the notification packet management module of the mobile phone implements association between the contact notification message packet and the application session information of the notification message.

Fig. 8 a-8 b illustrate an application scenario in which a user creates a contact notification message packet.

As shown in fig. 8a (1), in response to the short message application sending a notification message, a notification window 1001 corresponding to the short message application is displayed on the mobile phone notification center interface. In the notification window 1001, the transmission time "just" of the short message application notification message, the sender "something is in" and the information content "xxxxxxxx" are displayed. If the sender of the notification message, "lie somebody" is a contact person concerned by the mobile phone user (assumed to be "lie four"), and the notification message packet corresponding to "lie four" is not currently created, the mobile phone user may create the notification message packet corresponding to the contact "lie four", so that the notification message sent by the contact "lie four" in the short message application may be displayed in the notification aggregation window corresponding to the contact "lie four". At this time, the cell phone user can perform a left-swipe operation in the notification window 1001. In response to the user operation, the mobile phone displays an interface as shown in (2) in fig. 8 a. Referring to fig. 8a (2), only the right half of the notification window 1001 is displayed on the interface due to the user's left-slide operation. On the right side of the notification window 1001, a contact notification message packet creation option 1002 is displayed on the interface. When the user clicks on the contact notification message packet creation option 1002, the cell phone displays a contact notification message packet list interface, as shown in (1) in fig. 8b, in response to the user operation.

Referring to the contact notification message packet list interface shown in (1) in fig. 8b, the currently created contact notification message packet includes two contact notification message packets named "boss" and "zhang san". If the user desires to create a new contact notification message packet based on the notification message sent in the short message application "li-somer", the new contact notification message packet option 804 may be clicked. In response to the user clicking on the contact notification message grouping new option 804, the handset may display an interface as shown in (2) in fig. 8 b. In the interface, the user can set the information of the contact person notification message packet to complete the personalized setting of the contact person notification message packet. Regarding the flow of grouping the new contact notification messages at this time, reference may be made to the explanation of fig. 6b, which is not described herein again.

At this point, the notification packet management module of the mobile phone completes the creation of a contact notification message packet. Wherein, a record is added in the groupinformat data table for indicating the information of the contact notification message packet "Liquad". Then, the notification packet management module automatically generates an ID of a grouped notification message, and adds a record in the constraint list data table for indicating a piece of grouped application session information according to the application name (pkg _ name) "short message", "conversation ID of a notification message sent from" li somewhere "in the short message application, and the ID of the newly created contact notification message group. Wherein, the contact notification message packet (group) of the grouped notification message is the ID of the newly created contact notification message packet "lie four", thereby implementing the association of the newly created contact notification message packet "lie four" with the application session information (i.e. pkg _ name and convertionid) of the grouped notification message (i.e. "some lie" notification message sent in short message application). Further, when a notification message matching the piece of application session is received, the handset may display the notification message in a notification aggregation window corresponding to the contact notification message packet "Liquad".

Scene four

In this scenario, the user may manage the contact notification message packets in the setup application, or manage the contact notification message packets in the notification aggregation window.

Fig. 9 a-9 d exemplarily show application scenarios for a user to perform group management of contact notification messages in a setup application.

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

Exemplarily, fig. 9b (1) shows a notification group management interface of the handset. As shown in (1) of fig. 9b, the created individual contact notification message packets are shown in the notification packet management interface, where the contact notification message packets may be sorted by name. When a user clicks an option corresponding to a certain contact person notification message group, the mobile phone can display the detailed information of the contact person notification message group for the user. Illustratively, referring to (1) in fig. 9b, the user clicks on the option 1103 of the contact notification message group "boss", and in response to the user operation, the mobile phone may display an interface as shown in (2) in fig. 9 b. In the grouping interface, personalized setting information of a contact notification message group "boss" is displayed. In the grouping interface, the user can adjust the personalized setting information, and the user can refer to the prior art, which is not described herein again. When the user clicks on the group application details option 508, the handset displays an application management interface as shown in (1) in figure 9c in response to the user operation. In the application management interface, the application information related to the contact notification message group "boss" is displayed, that is, the applications corresponding to the notification messages required to be aggregated and displayed in the contact notification message group are displayed. Exemplary applications to which the contact notification message packet "boss" relates include wechat applications and short message applications.

Continuing with reference to fig. 9c (1), if the user wants to disassociate the short message application session from the contact notification message packet "boss" based on personal needs, that is, the notification message sent by the contact "boss" in the short message application no longer needs to be displayed in the notification aggregation window corresponding to the contact notification message packet "boss", the user may perform a left-sliding operation on the short message application option 901. In response to the user operation, the mobile phone displays an interface as shown in (2) in fig. 9 c. As shown in fig. 9c (2), a deletion option 902 corresponding to the short message application is displayed on the interface. If the user clicks the delete option 902, the notification group management module of the mobile phone performs an operation of disassociating the corresponding short message application session from the contact notification message group "boss", and the application management interface displayed by the mobile phone only includes the WeChat application, that is, the application related to the contact notification message group "boss" only includes the WeChat application.

When a notification grouping management module of the mobile phone executes the operation of disassociating the short message application session and the contact notification message grouping boss, the data in the grouping information data table is not changed, and a record is deleted from the constraint data table. In the deleted record in the contentionsist data table, the group value is the ID of a contact notification message packet "boss" in the groupInformation data table, the pkg _ name value is a short message application, and the convertionID value is a session identifier of a notification message sent by "Chen" in the short message application.

Referring to (1) in fig. 9d, if the user wants to delete the contact notification message packet "boss" based on personal needs, that is, the notification message sent by the contact "boss" in a different application does not need to be displayed in the notification aggregation window corresponding to the contact notification message packet "boss", the user may perform a left-sliding operation on the option 1103 of the contact notification message packet "boss". In response to the user operation, the mobile phone displays an interface as shown in (2) in fig. 9 d. As shown in fig. 9d (2), a delete option 1104 corresponding to the contact notification message packet "boss" is displayed on the interface. If the user clicks the delete option 1104, the notification group management module of the mobile phone performs an operation of deleting the contact notification message group "boss", and the contact notification message group created in the notification group management interface displayed by the mobile phone only includes the contact notification message group "zhang san".

When a notification grouping management module of the mobile phone executes the operation of grouping the contact notification messages into the 'boss' for deletion, a record is deleted from the groupInformation data table. Wherein, in the record deleted 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 contrivance list data table, wherein the group value of the deleted records is the ID of the contact notification message group "boss".

Continuing with reference to (1) in 9b, if the user wants to create a new contact notification message grouping based on personal needs, the new contact grouping option 1105 can be clicked. In response to the user operation, the handset may display an interface as shown in (1) in fig. 6 b. In the interface, the user can set the information of the contact person notification message packet to complete the personalized setting of the contact person notification message packet. Regarding the flow of grouping the new contact notification messages at this time, reference may be made to the explanation of fig. 6b, which is not described herein again.

When a notification grouping management module of the mobile phone executes a contact notification message grouping creation operation, a record is newly added in the groupInformation data table and used for indicating the newly created contact notification message grouping.

It should be noted that, when the user clicks the new contact grouping option 1105 to make the notification grouping management module of the mobile phone perform the operation of creating a contact notification message grouping, since the newly created contact notification message grouping is not associated with any notification message of any application, no record is added to the contentitlist data table at this time. When the mobile phone receives a notification message of an application and the user needs to associate an application session message of the notification message with the newly created contact notification message packet, the user may perform operations similar to those in fig. 7a to 7b, and at this time, a corresponding record is added to the containment list data table.

Fig. 10 exemplarily shows an application scenario of a user performing grouping 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 packet "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 from the contact notification message packet "boss" based on personal needs, that is, the notification message sent by the contact "boss" in the short message application no longer needs to be displayed in the notification aggregation window 1201 corresponding to the contact notification message packet "boss", the user may operate in the notification aggregation window 1201. Referring to fig. 10 (1), the user performs a left-sliding operation on the short message application notification window 1202, and in response to the user's operation, the mobile phone displays an interface as shown in fig. 10 (2). Referring to fig. 10 (2), only the right half of the short message application notification window 1202 is displayed on the interface of the notification aggregation window 1201 due to the user's left-slide operation. On the right side of the short message application notification window 1202, a notification aggregation window 1201 displays an option 1204 to remove the application notification in the contact notification message packet and an application notification window deletion option 1205. When the user clicks on the option 1204, in response to the user operation, the notification packet management module of the mobile phone performs an operation of disassociating the corresponding short message application session from the contact notification message packet "boss". At this time, if the user clicks an application management interface corresponding to the query contact notification message packet "boss", the application management interface no longer includes the short message application.

When a notification grouping management module of the mobile phone executes the operation of disassociating the short message application session from the contact notification message grouping "boss", the data in the grouping format data table is not changed, and a record is deleted from the linkage list data table. In the deleted record in the constraint list data table, the group value is the ID of a contact notification message packet "boss" in the group information data table, the pkg _ name value is a short message application, and the constraint ID value is a session identifier of a notification message sent by "Chen" in the short message application.

Fig. 11 is an interaction diagram of the modules. Referring to fig. 11, a flow of a method for displaying a notification message provided in an embodiment of the present application specifically includes:

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

The social application may refer to any application capable of sending a notification message between contacts (or called friends), such as WeChat, short message, QQ, tremble, Payment treasure, and the like.

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

Illustratively, the wechat application constructs a notification message based on a predefined session construction method, and carries a session identification (conversation id) of the notification message in the wechat application.

For example, the wechat application may also construct the notification message based on a customized session construction method, which is not limited in this embodiment.

S1302, the notification manager analyzes the notification message to obtain an application name and a 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 grouping management module.

After receiving the notification message sent by the wechat application, the notification manager analyzes the notification message based on a predefined session construction method, obtains a session identifier (conversation id) of the notification message in the wechat application, and obtains an application name and a session identifier to which the notification message belongs.

If the notification message sent by the wechat application is constructed based on the customized session construction method, the notification manager may parse the notification message based on the session construction method matched with the wechat application to obtain a session identifier (conversation id) of the notification message in the wechat application, or obtain the session identifier (conversation id) of the notification message in the wechat application based on a relevant interface provided by the wechat application.

S1303, the notification grouping management module determines whether the notification message is grouped based on the contact according to the application name and the session identifier to which the notification message belongs, if so, executes S1304, and if not, executes S1306.

The notification grouping management can determine whether a notification message is a grouped notification message by combining the name of the application sending the notification message and the session identifier (conversation id) of the notification message in the application.

After determining the application name (pkg _ name) to which the notification message belongs and the session identifier (conversation id) in the application, the notification group management performs data matching in the constraint data table to determine whether a contact notification message group (group) to which the notification message belongs exists. If yes, informing the grouping management to judge that the notification message is grouped based on the contact persons; if not, the notification grouping management judges that the notification message is not grouped based on the contact persons,

s1304, the notification packet management module determines a contact notification message packet associated with the notification message.

After determining the application name (pkg _ name) to which the notification message belongs and the session identification (conversation id) in the application, the notification group management performs data matching in the constraint list data table to determine the contact notification message group (group) to which the notification message belongs.

Further, the notification packet management may perform data matching in the group information data table according to a contact notification message packet (group) to which the notification message belongs, determine a contact notification message packet associated with the notification message, and acquire personalized configuration information of the contact notification message packet.

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 indication information to the notification center to instruct the notification center to display the notification messages in the notification aggregation window corresponding to the contact notification message group. The indication information may carry personalized configuration information of the contact notification message packet, such as personalized configuration information of a 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 the contact, the notification center is instructed to display the notification message in a prior art form, for example, in a WeChat application notification window.

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

S1307, the notification center obtains the notification message to be displayed and displays the notification message according to the indication.

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 acquires the notification information to be displayed and displays the notification message in the notification aggregation window corresponding to the associated contact notification message group, as shown in (1) in fig. 12. And the information such as the notification ring tone, the window background color, the display font and the like of the notification aggregation window conforms to the personalized configuration information of the corresponding contact notification message packet. The notification aggregation window may be configured to be set-top-displayed in the notification center interface if the set-top display is configured in the contact notification message grouping corresponding to the notification aggregation window.

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 fig. 12. In this case, as long as the notification manager can recognize the session identifier (conversation id) of the notification message in the application, the user may group the sessions corresponding to the notification message based on the contacts, which is described in detail in scenarios one, two, and three, and is not described herein again.

It should be noted that, in order to ensure the user experience, the notification aggregation window may inherit the related operations of the existing application notification window, such as a window folding operation, a window deleting operation, and the like.

Fig. 13 a-13 d illustrate exemplary application scenarios in which a user performs a related operation in a notification aggregation window.

As shown in fig. 13a (1), a notification aggregation window 1401 corresponding to the contact notification message packet "boss" is displayed in the cell phone notification center interface. In the notification aggregate 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 for folding and displaying the notification aggregation window is displayed in the notification aggregation window 1401. Referring to fig. 13a (1), the user clicks on the window folding option 1402, and in response to the user operation, the mobile phone displays the mobile phone notification center interface as shown in fig. 13a (2), and the display form of the notification aggregation window corresponding to the contact notification message packet "boss" is switched from the notification aggregation window 1401 to the notification aggregation window 1403.

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

With continued reference to (2) in fig. 13a, in the notification aggregate window 1403, the respective application notification windows are not displayed any more, but a notification message list 1405 is displayed for describing the respective notification messages displayed in the notification aggregate window. As shown in (2) in fig. 13a, the notification message list 1405 includes: the application names to which the respective notification messages displayed in the notification aggregation window 1401 belong, the number of notification messages corresponding to the respective applications, and the reception times of the latest notification message corresponding to the respective applications.

As shown in (1) in fig. 13b, a notification aggregation window 1401 corresponding to the contact notification message packet "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, a left-swipe operation may be performed on the notification aggregation window 1401. In response to the user's operation, the cellular phone displays a notification center interface as shown in (2) in fig. 13 b. Referring to fig. 13b (2), only the right half of the notification aggregation window 1401 is displayed on the notification center interface due to a left-slide operation by the user. On the right side of the notification aggregation window 1401, a to-be-deleted option 1405 is displayed on the notification center interface. When the user clicks the delete option 1405, the cellular phone performs an operation of deleting the notification aggregation window 1401 in the interface in response to the user operation.

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

As shown in (1) in fig. 13d, a notification aggregation window 1401 corresponding to the contact notification message packet "boss" is displayed in the mobile phone notification center interface. If the user wants to delete an application notification window in the notification aggregate window 1401, a left-swipe operation can be performed on the corresponding application notification window in the notification aggregate window 1401. Illustratively, referring to fig. 13d (1), the user performs a left swipe operation on the short message application notification window 1407. In response to the user's operation, the handset displays a notification center interface as shown in (2) in fig. 13 d. Referring to fig. 13d (2), only the right half of the short message application notification window 1407 is displayed in the notification aggregating window due to the user's left-sliding operation. On the right side of the short message application notification window 1407, a to delete option 1408 is displayed in the notification aggregation window. When the user clicks the delete option 1408, in response to the user operation, the mobile phone performs an operation of deleting the short message application notification window in the notification aggregate window 1401, so that only the short message application notification window is displayed in the notification aggregate window 1401.

It should be noted that the functions of each application notification window in the notification aggregation window may inherit the functions of the existing application notification window, including click-to-view, folding-and-unfolding, left-sliding-to-left deletion, automatic deletion after click-to-view, and the like, which are not described in this embodiment again.

It should be noted that if only one application notification window is included in the notification aggregation window, the user performs a left-sliding operation on the application notification window to delete the application notification window in the notification aggregation window, which may be equivalent to the user performing a left-sliding operation on the notification aggregation window to delete the notification aggregation window in the notification center interface. That is, when only one application notification window is included in the notification aggregation window, the user clicks the delete option after performing a left-swipe operation on the application notification window, and in response to the user operation, the notification aggregation window is no longer displayed on the notification center interface.

It should be noted that, in the notification center interface, not only the notification aggregation window provided in this embodiment may be displayed, but also other application notification windows may be displayed in an existing manner according to the notification message reception situation. Illustratively, as shown in fig. 14, on the cell phone notification center interface, a notification aggregation window 1401, and a wechat application notification window 1402 are displayed. In the notification aggregate 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 issued in the wechat application, the notification messages displayed in the wechat application notification window 14012 are of interest or interest to the user, have been associated with the contact notification message packet "boss," and are displayed in aggregate in the notification aggregation window 1401 corresponding to the contact notification message packet "boss. However, the notification messages displayed in the WeChat application notification window 1402 are not currently associated with any notification message packets and are therefore displayed in the corresponding application notification window in the existing manner.

In the foregoing embodiment, the notification aggregation window is explained by taking an example in which the notification aggregation window corresponds to one contact notification message packet. Similarly, one notification aggregation window may also correspond to any one notification message packet, where the notification message packet may be customized by a user based on personal needs, and the notification messages associated in the notification message packet may originate from the same application or different applications, which is not limited in this embodiment.

For example, if the notification message of interest or interest to the user is a notification message sent by contact a in one application (e.g., a WeChat application) and a notification message sent by contact B in another application (e.g., a short message application), a notification message packet may be created and associated with the notification message packet, the notification message sent by contact a in the corresponding application (e.g., the WeChat application) and the notification message sent by contact B in the corresponding application (e.g., the short message application). Further, the notification message sent by contact a in the corresponding application (e.g., the WeChat application) and the notification message sent by contact B in the corresponding application (e.g., the short message application) that are received subsequently are both displayed in the notification aggregation window corresponding to the notification message packet. Further, the notification message sent by contact a in the corresponding application (e.g., the WeChat application) and the notification message sent by contact B in the corresponding application (e.g., the short message application) are both displayed in the notification aggregation window corresponding to the notification message packet. For example, the short message sent by the contact "zhangao" and the WeChat sent by the WeChat friend "li" are notification messages that are interesting or concerned by the mobile phone user, the mobile phone user may create a notification message packet 1, and associate the application name and the session identifier (conversation id) corresponding to the short message sent by the contact "zhangao" and the application name and the session identifier (conversation id) corresponding to the WeChat notification message sent by the WeChat friend "li" with the notification message packet 1, so that the subsequently received short message sent by the contact "zhangao" and the WeChat sent by the WeChat friend "li" are both displayed in the notification aggregation window corresponding to the notification message packet 1. As shown in fig. 15, a notification aggregation window 1501 is a notification aggregation window corresponding to the notification message packet 1, and a short message application notification window 15011 and a wechat application notification window 15012 may be displayed in aggregation in the notification aggregation window 1501. The short message application notification window 15011 displays the short message sent by the contact person "zhan-in", 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 of interest or interest to the user is a notification message sent by contact a and contact B in an application (e.g., a WeChat application), a notification message packet may be created and associated with the notification message packet sent by contact a and contact B in the application. Further, the notification messages sent by the contact a and the contact B in the application, which are received subsequently, are both displayed in the notification aggregation window corresponding to the notification message packet. For example, the micro-communication notification messages sent by the micro-communication friend "CC" and the micro-communication friend "ZZ" are notification messages that are interesting or concerned by the mobile phone user, the mobile phone user may create a notification message group 2, and associate application names and session identifiers (conversation ids) corresponding to the micro-communication notification messages sent by the micro-communication friend "CC" and the micro-communication friend "ZZ", respectively, with the notification message group 2, so that the subsequently received micro-communication notification messages sent by the micro-communication friend "CC" and the micro-communication friend "ZZ" are all displayed in the notification aggregation window corresponding to the notification message group 2. As shown in fig. 16, a notification aggregation window 1601 is a notification aggregation window corresponding to the notification message packet 2, and a wechat application notification window 16011 and a wechat application notification window 16012 may be displayed in the notification aggregation window 1601 in an aggregated manner. The WeChat application notification window 16011 displays a WeChat notification message sent by the WeChat friend "CC", and the WeChat application notification window 16012 displays a WeChat notification message sent by the WeChat friend "ZZ".

The creation and management process of the

notification message packet

1 or 2, the process of associating or disassociating the application name and the session identifier corresponding to the notification message with the notification message packet, and other parts not explained in detail above can be referred to in the foregoing, and are not described herein again.

The present embodiment also provides a computer storage medium, in which computer instructions are stored, and when the computer instructions are run on an electronic device, the computer instructions cause the electronic device to execute the above related method steps to implement the method for displaying a notification message in the above embodiment.

The present embodiment also provides a computer program product, which when running on a computer, causes the computer to execute the above related steps to implement the display method of the notification message in the above embodiments.

Embodiments of the present application also provide an apparatus, which may be embodied as a chip, a component, or a module, and which may include a processor and a memory coupled together; the memory is used for storing computer execution instructions, and when the device runs, the processor can execute the computer execution instructions stored by the memory, so that the chip can execute the display method of the notification message in the above method embodiments.

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

In addition, the electronic device (such as a mobile phone, etc.), the computer storage medium, the computer program product or the chip provided in this embodiment are all used to execute the corresponding method provided above, so that the beneficial effects that can be achieved by the electronic device can refer to the beneficial effects in the corresponding method provided above, and are not described herein again.

Through the description of the above embodiments, those skilled in the art will understand that, for convenience and simplicity of description, only the division of the above functional modules is used as an example, and in practical applications, the above function distribution may be completed by different functional modules as needed, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, a module or a unit may be divided into only one logic function, and may be implemented in other ways, for example, a plurality of units or components may be combined or integrated into another apparatus, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and these modifications or substitutions do not depart from the scope of the technical solutions of the embodiments of the present application.

Claims

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, and application notification messages which are interesting to the user are respectively displayed in each second notification window.

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 person 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, prior to said displaying the first interface, further comprising:

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, further comprising, prior to said displaying the first interface:

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, in response to a second operation, the name of the first application and the first session identification with the first contact group.

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 contact group, 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 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 the eighth interface displays the personalized setting information of the first contact group.

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

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 group to which the first notification message belongs does not exist according to the name of the first application and the first session identifier, 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.