CN113722027A

CN113722027A - Notification message display method and electronic equipment

Info

Publication number: CN113722027A
Application number: CN202110400637.XA
Authority: CN
Inventors: 杨诗姝; 周珊如; 黄丽薇
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-04-14
Filing date: 2021-04-14
Publication date: 2021-11-30
Also published as: WO2022218053A1

Abstract

A display method of notification messages and electronic equipment relate to the technical field of terminals and can dynamically display the notification messages in a main screen of the electronic equipment, remind a user of checking related notification messages in time and improve the use experience of the user. The method comprises the following steps: the method comprises the steps that the electronic equipment displays a first desktop, and a first component is displayed in a first display area of the first desktop; after the electronic device acquires the first event, in response to the first event, a second component corresponding to the first event is displayed in the first display area (the second component is different from the first component, and the second component includes a first notification message), and the first component is not displayed in the first display area, that is, the first display area occupied by the first component is used for dynamically displaying a corresponding notification message.

Description

Notification message display method and electronic equipment

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a notification message display method and an electronic device.

Background

Currently, a notification bar (notification panel) is set in electronic devices such as mobile phones and the like, and is used for displaying notification messages received by an operating system or an application. Taking a mobile phone as an example, as shown in fig. 1 (a), the mobile phone can simultaneously display a status bar 101 when displaying an application such as a main screen (also referred to as a desktop). The status bar 101 may display time, power, signal strength, bluetooth status, and operator name.

If it is detected that the user performs a pull-down operation on the status bar 101, as shown in (b) of fig. 1, the cellular phone may display a pull-down menu 102. When there are notification messages for an application in the handset, the handset may display these notification messages in the notification bar 103 of the pull-down menu 102. The mobile phone can display the received notification messages of the respective applications in the notification bar 103 in the form of notification messages one by one.

However, when the number of notification messages is large, the user needs to slide up and down in the notification bar 103 to locate the corresponding notification message, and even some important notification messages are missed due to too many notification messages, so that the user experience in browsing and querying the notification messages is not high.

Disclosure of Invention

The application provides a display method of notification messages and electronic equipment, which can dynamically display the notification messages in a main screen of the electronic equipment, timely remind a user to check the related notification messages, and improve the use experience of the user.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, the present application provides a method for displaying a notification message, including: the method comprises the steps that the electronic equipment displays a first desktop, and a first component (such as a weather component and the like) is displayed in a first display area of the first desktop; after the electronic device acquires a first event (the first event is associated with a first notification message), a second component corresponding to the first event (the second component is different from the first component, and the content of the second component is associated with the content of the first notification message) can be displayed in a first display area in response to the first event, and the first component is not displayed in the first display area, namely, the corresponding notification message is dynamically displayed by using the first display area occupied by the first component. Therefore, a user can dynamically acquire related notification messages from the component (namely the first component) of the current desktop, and meanwhile, when the electronic equipment displays the notification messages by utilizing the original component in the desktop, the display layout of other controls such as application icons in the desktop is not required to be adjusted, so that the original display content in the desktop is not excessively interfered.

In a possible implementation manner, the second component may be located at an upper layer of the first component, that is, the electronic device may display the latest notification message in the form of a component (e.g., a card) on an upper layer of the original component in a stacked manner.

In one possible implementation manner, after the electronic device displays the second component corresponding to the first event in the first display area, the method further includes: after the second component displays the preset duration, the electronic device can display the first component in the first desktop, and the first display area does not display the second component. That is to say, after the electronic device displays the first notification message for a certain time through the second component, the second component can be automatically hidden in the desktop, and the original first component is displayed at the same time, so that the notification message can be dynamically displayed in the desktop and can be dynamically hidden in the desktop.

Or after the electronic device displays the second component corresponding to the first event in the first display area, the method further includes: if a preset deleting operation of the second assembly input by the user is received, the electronic equipment can display the first assembly in the first desktop, and the second assembly is not displayed in the first display area. That is, the user may also manually delete the displayed first notification message in the desktop while displaying the original first component.

Or after the electronic device displays the second component corresponding to the first event in the first display area, the method further includes: the electronic equipment acquires a second event, wherein the second event is used for indicating that the service corresponding to the first notification message is completed; at this time, in response to the second event, the electronic device may display the first component in the first desktop, and the first display area does not display the second component. That is, when the service corresponding to the first notification message is completed, the electronic device may also automatically hide the second component in the desktop and display the original first component.

In one possible implementation manner, after the electronic device displays the second component corresponding to the first event in the first display area, the method further includes: the electronic device acquiring a third event (the third event being associated with the second notification message); furthermore, if the priority of the third event is higher than that of the first event, the electronic device displays a third component corresponding to the third event in the first display area, wherein the third component can be located at an upper layer of the second component at this time, and the content of the third component is associated with the content of the second notification message; alternatively, if the priority of the first event is higher than the priority of the third event, the electronic device continues to display the second component in the first display area, at which time the third component may be positioned at a lower level than the second component, and likewise, the content of the third component is associated with the content of the second notification message.

For example, if the first event is the notification message 1 sent by APP 1 and the third event is the notification message 2 sent by APP 2, the electronic device may set the display order of the notification message 1 to be before the display order of the notification message 2 when the priority of the notification message 1 is higher than the priority of the notification message 2. Further, the electronic device may display the notification message 1 in the form of a component (i.e., a second component) on an upper layer of a third component containing the notification message 2. Accordingly, when the priority of the notification message 1 is lower than the priority of the notification message 2, the electronic apparatus may set the display order of the notification message 1 to be located after the display order of the notification message 2. Further, the electronic device can display the notification message 1 as a component (i.e., the second component) at a lower level of the third component containing the notification message 2, and at this time, the third component at an upper level is presented to the user in the desktop.

In one possible implementation manner, after the electronic device displays the third component corresponding to the third event in the first display area, the method further includes: if receiving a preset switching operation input by a user to the third component, the electronic device may display the second component in the first desktop, and the first display area does not display the third component. That is, when there are a plurality of components containing notification messages in the first display area, the user can manually switch the respective components to display in the desktop.

In one possible implementation manner, after the electronic device acquires the third event, the method further includes: the electronic device may display navigation points at or around the first display area, the navigation points for prompting a user for receipt of a plurality of notification messages. For example, the number of navigation points may be the same as the number of current notification messages.

In one possible implementation manner, after the electronic device acquires the third event, the method further includes: if the fact that the fingers of the user touch the first display area is detected, the electronic equipment displays navigation points on the first display area or the periphery of the first display area, and the navigation points are used for prompting the user to receive a plurality of notification messages. That is, the navigation point may be dynamically displayed or hidden around or in the component containing the notification message.

In a possible implementation manner, a fourth component may be displayed in the second display area of the first desktop, that is, two components, namely the first component and the fourth component, are arranged in the first desktop; at this time, after the electronic device displays the second component corresponding to the first event in the first display area, the method further includes: the electronic device acquires a fourth event (the fourth event is associated with the third notification message, for example, the server sends the event containing the third notification message); further, in response to a fourth event, the electronic device may display a fifth component corresponding to the fourth event in the second display area (the content of the fifth component is associated with the content of the third notification message), and the second display area does not display the fourth component. Thus, if multiple components are included in the desktop 1, the multiple components can be used to display notification messages, so that the user can know more notification messages from the current desktop.

In one possible implementation, the electronic device obtains a first event, including: the electronic equipment acquires a first event when displaying a third desktop, wherein the third desktop has no component; at this time, the electronic device displays a second component corresponding to the first event in the first display area, including: and if the electronic equipment is detected to switch the third desktop to the first desktop, the electronic equipment displays the second component in the first display area. That is, if the electronic device receives a notification message while displaying a desktop without a component (e.g., the second desktop), the electronic device may display a corresponding notification message in the above-described method while displaying a desktop provided with a component (e.g., the first desktop) for the first time, prompting the user to view the notification message in the first desktop.

Or, if the electronic device acquires the first event when displaying the third desktop (no component in the third desktop), the electronic device may also display a second component corresponding to the first event in a blank area of the third desktop, so that the user can obtain the latest notification message from the current desktop in time.

In one possible implementation manner, before the electronic device displays the first desktop, the method further includes: responding to the operation of adding the first component by a user, adding the first component in the first desktop by the electronic equipment, wherein the first component can be normally displayed when no notification message exists, and the first component can support the stack display of the component carrying the notification message when the notification message exists; at this time, the electronic device may display a guidance pop-up window for prompting an operation method of the component in the first display region, so that a user can conveniently and quickly learn a function of displaying the notification message in the component. Of course, the electronic device may display the guidance popup when the user first adds the first component and then no longer display the guidance popup when the user subsequently adds the first component again.

In a possible implementation manner, the method further includes: the electronic device may display a setting interface for setting one or more of a type, a number, or contents of the components displayed in the first display region. For example, a component (e.g., the second component) carrying the notification message may include a setting button, and a user may enter the setting interface by clicking the setting button to set a specific function of the second component when displaying the notification message.

In a possible implementation manner, the first event may include a first notification message; for example, the electronic device acquires the first event, which specifically includes: the electronic equipment acquires a first event carrying a first notification message from the server. Alternatively, the first event may not include the first notification message, for example, the first event may be an event in which a user sets a schedule in the calendar APP, and the electronic device may automatically generate a corresponding first notification message in response to the first event and display the first notification message according to the method.

In one possible implementation manner, after the electronic device acquires the first event, the method further includes: the electronic device sets a parameter of the second component corresponding to the first event, where the parameter includes one or more of a display order, an exposure duration, a retention duration, or a component type, which is not limited in any way in this application.

In a second aspect, the present application provides an electronic device comprising: the touch screen comprises a touch sensor and a display screen; one or more processors; a memory; wherein the memory has stored therein one or more computer programs, the one or more computer programs comprising instructions, which when executed by the electronic device, cause the electronic device to perform the steps of: displaying a first desktop, wherein a first assembly is displayed in a first display area of the first desktop; acquiring a first event (the first event being associated with a first notification message); in response to the first event, a second component corresponding to the first event is displayed in the first display area, and the first component is not displayed in the first display area, the second component being different from the first component, and the content of the second component being associated with the content of the first notification message.

In one possible implementation, the second component is located on an upper layer of the first component.

In one possible implementation manner, after the electronic device displays the second component corresponding to the first event in the first display area, the electronic device is further configured to perform: and when the second assembly displays the preset time, the first assembly is displayed in the first desktop, and the second assembly is not displayed in the first display area.

In one possible implementation manner, after the electronic device displays the second component corresponding to the first event in the first display area, the electronic device is further configured to perform: and if a preset deleting operation input by a user on the second component is received, displaying the first component in the first desktop, and not displaying the second component in the first display area.

In one possible implementation manner, after the electronic device displays the second component corresponding to the first event in the first display area, the electronic device is further configured to perform: acquiring a second event, wherein the second event is used for indicating that the service corresponding to the first notification message is completed; in response to a second event, the first component is displayed in the first desktop and the second component is not displayed in the first display area.

In one possible implementation manner, after the electronic device displays the second component corresponding to the first event in the first display area, the electronic device is further configured to perform: acquiring a third event (the third event being associated with the second notification message); if the priority of the third event is higher than that of the first event, displaying a third component corresponding to the third event in the first display area, wherein the third component is positioned on the upper layer of the second component, and the content of the third component is associated with the content of the second notification message; or if the priority of the first event is higher than that of the third event, continuing to display the second component in the first display area, wherein the third component is positioned at the lower layer of the second component, and the content of the third component is related to the content of the second notification message.

In one possible implementation manner, after the electronic device displays the third component corresponding to the third event in the first display area, the electronic device is further configured to perform: and if receiving a preset switching operation input by a user on the third component, displaying the second component in the first desktop, and not displaying the third component in the first display area.

In one possible implementation manner, after the electronic device acquires the third event, the electronic device is further configured to perform: and displaying navigation points at or around the first display area, wherein the navigation points are used for prompting the user to receive a plurality of notification messages.

In one possible implementation manner, after the electronic device acquires the third event, the electronic device is further configured to perform: and if the finger of the user is detected to touch the first display area, displaying a navigation point on the first display area or the periphery of the first display area, wherein the navigation point is used for prompting the user to receive a plurality of notification messages.

In one possible implementation, a fourth component is displayed in the second display area of the first desktop; after the electronic device displays the second component corresponding to the first event in the first display area, the electronic device is further used for executing: acquiring a fourth event (the fourth event is associated with the third notification message); in response to the fourth event, a fifth component corresponding to the fourth event is displayed in the second display area, and the fourth component is not displayed in the second display area, and the content of the fifth component is associated with the content of the third notification message.

In a possible implementation manner, the acquiring, by the electronic device, the first event specifically includes: the electronic equipment acquires a first event when displaying a third desktop, wherein the third desktop has no component; the electronic device displays a second component corresponding to the first event in the first display area, and specifically includes: and if the electronic equipment is detected to switch the third desktop to the first desktop, the electronic equipment displays the second component in the first display area.

In a possible implementation manner, the acquiring, by the electronic device, the first event specifically includes: the electronic equipment acquires a first event when displaying a third desktop, wherein the third desktop has no component; after the electronic device acquires the first event, the electronic device is further configured to perform: the electronic device displays a second component corresponding to the first event in a blank area of the third desktop.

In one possible implementation manner, before the electronic device displays the first desktop, the electronic device is further configured to perform: in response to an operation of adding a first component by a user, adding the first component in a first desktop by the electronic equipment; the electronic equipment displays a guide popup window which is used for prompting an operation method of the component in the first display area.

In one possible implementation, the electronic device is further configured to display a setting interface configured to set one or more of a type, a number, or a content of the component displayed in the first display area

In one possible implementation, the first event includes a first notification message; wherein, the electronic equipment acquires a first event, including: the electronic equipment acquires a first event carrying a first notification message from the server.

In one possible implementation manner, after the electronic device acquires the first event, the electronic device is further configured to perform: the electronic equipment sets parameters of the second component corresponding to the first event, wherein the parameters comprise one or more of display sequence, exposure time length, retention time length or component type.

In a third aspect, the present application provides an electronic device, comprising: a memory, a display screen, and one or more processors; the memory and the display screen are coupled with the processor. Wherein the memory is to store computer program code, the computer program code comprising computer instructions; the processor is configured to execute the one or more computer instructions stored by the memory when the electronic device is operating, so as to cause the electronic device to perform the method of displaying a notification message as described in any of the above first aspects.

In a fourth aspect, the present application provides a computer storage medium comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the method of displaying a notification message according to any of the first aspect.

In a fifth aspect, the present application provides a computer program product, which, when run on an electronic device, causes the electronic device to perform the method of displaying a notification message according to any one of the first aspect.

It is to be understood that the electronic device according to the second and third aspects, the computer storage medium according to the fourth aspect, and the computer program product according to the fifth aspect are all configured to execute the corresponding method provided above, and therefore, the beneficial effects achieved by the electronic device may refer to the beneficial effects in the corresponding method provided above, and are not described herein again.

Drawings

FIG. 1 is a diagram illustrating an application scenario for displaying notification messages in the prior art;

fig. 2 is a first schematic structural diagram of an electronic device according to an embodiment of the present disclosure;

fig. 3 is a schematic architecture diagram of a software architecture in an electronic device according to an embodiment of the present disclosure;

Fig. 4 is a first application scenario diagram of a display method of a notification message according to an embodiment of the present application;

fig. 5 is a schematic view of an application scenario of a display method of a notification message according to an embodiment of the present application;

fig. 6 is an interaction flow diagram of a method for displaying a notification message according to an embodiment of the present application;

fig. 7 is a schematic application scenario diagram three of a display method of a notification message according to an embodiment of the present application;

fig. 8 is a schematic view of an application scenario of a display method of a notification message according to an embodiment of the present application;

fig. 9 is a schematic application scenario diagram of a display method of a notification message according to an embodiment of the present application;

fig. 10 is a schematic application scenario diagram six of a display method of a notification message according to an embodiment of the present application;

fig. 11 is a schematic application scenario diagram seven of a display method of a notification message according to an embodiment of the present application;

fig. 12 is an application scenario diagram eight of a display method of a notification message according to an embodiment of the present application;

fig. 13 is a schematic view nine of an application scenario of a display method of a notification message according to an embodiment of the present application;

fig. 14A is a schematic application scenario diagram ten of a display method of a notification message according to an embodiment of the present application;

Fig. 14B is an application scenario diagram eleven of a display method of a notification message according to an embodiment of the present application;

fig. 15 is a schematic view twelve of an application scenario of a display method of a notification message according to an embodiment of the present application;

fig. 16 is a schematic application scenario thirteen of a display method of a notification message according to an embodiment of the present application;

fig. 17 is a schematic view fourteen of an application scenario of a display method of a notification message according to an embodiment of the present application;

fig. 18 is a schematic application scenario fifteen of a display method of a notification message according to an embodiment of the present application;

fig. 19 is a schematic view sixteen illustrating an application scenario of a display method of a notification message according to an embodiment of the present application;

fig. 20 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present embodiment, "a plurality" means two or more unless otherwise specified.

Embodiments of the present embodiment will be described in detail below with reference to the accompanying drawings.

For example, the notification message display method provided in the embodiment of the present application may be applied to an electronic device with a display function, such as a mobile phone, a vehicle-mounted device (also referred to as a car machine), a tablet computer, a notebook computer, an ultra-mobile personal computer (UMPC), a handheld computer, a netbook, a Personal Digital Assistant (PDA), a wearable electronic device, and a virtual reality device, and the embodiment of the present application does not limit the present application.

Taking a mobile phone as an example of the above electronic device, as shown in fig. 2, a schematic structural diagram of the mobile phone is shown.

The mobile phone may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, 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, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention is not to be specifically limited to a mobile phone. In other embodiments of the present application, the handset may include more or fewer components than shown, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

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

The

antennas

1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the handset 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 a mobile phone. 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 mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication applied to a mobile phone, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), Bluetooth (BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, the handset antenna 1 is coupled to the mobile communication module 150 and the handset antenna 2 is coupled to the wireless communication module 160 so that the handset can communicate with the network and other devices via wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The mobile phone realizes the display function through the GPU, the display screen 194, the application processor and the like. 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. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the cell phone may include 1 or N display screens 194, with N being a positive integer greater than 1.

Taking an OLED display panel as an example, one OLED display panel may include a plurality of OLED pixel units arranged in an array. As shown in fig. 2, each OLED pixel unit includes a cathode 201, an anode 202, and an electron transport layer 203, a hole transport layer 204, and an emission layer 205 located between the cathode 201 and the anode 202. The cathode 201 may be a metal electrode, and the anode 202 may be an ITO (indium tin oxide) transparent electrode.

When a driving voltage V is input to the cathode 201 and the anode 202, electrons are transported from the cathode 201 to the electron transport layer 203 and holes are injected from the anode 202 to the hole transport layer 204 under the action of the driving voltage V, and the holes and the hole transport layer 204 meet each other to generate excitons, so that light-emitting molecules in the light-emitting layer 205 are excited and a light source is generated after radiation. When the driving voltage V is different, the corresponding OLED pixel units can be excited to present different colors and brightness. In this way, each OLED pixel unit in the OLED display screen can display a corresponding picture under different driving voltages.

Among them, the organic materials in the electron transport layer 203, the hole transport layer 204, and the light emitting layer 205 are gradually aged during use. The phenomenon of image sticking occurring in the OLED display screen is that the OLED pixel unit at a certain fixed position always displays the same and static image for a long time, so that the organic material in the pixel unit is more worn out than other positions, and the luminous efficiency is more quickly attenuated, thereby leaving the image sticking on the OLED display screen.

The mobile phone can realize shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 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 the 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 handset may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the mobile phone selects the frequency point, the digital signal processor is used for performing fourier transform and the like on the frequency point energy.

Video codecs are used to compress or decompress digital video. The handset may support one or more video codecs. Thus, the mobile phone can play or record videos in various encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the storage capability of the mobile phone. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The processor 110 executes various functional applications of the cellular phone and data processing by executing instructions stored in the internal memory 121. 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 data storage area can store data (such as audio data, a phone book and the like) created in the use process of the mobile phone. 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 mobile phone can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music 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 handset can listen to music through the speaker 170A or listen to a hands-free conversation.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the mobile phone receives a call or voice information, the receiver 170B can be close to the ear to receive voice.

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 handset may be provided with at least one microphone 170C. In other embodiments, the mobile phone may be provided with two microphones 170C to achieve the noise reduction function in addition to collecting the sound signal. In other embodiments, the mobile phone may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.

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 sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

Certainly, the mobile phone may further include a charging management module, a power management module, a battery, a key, an indicator, 1 or more SIM card interfaces, and the like, which is not limited in this embodiment of the present application.

The software system of the electronic device 100 may adopt a layered 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. 3 is a block diagram of a software structure of the electronic device 100 according to the embodiment of the present application.

The layered architecture 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.

1. Application layer

The application layer may include a series of applications.

As shown in fig. 3, the application programs may include Applications (APP) such as call, contact, camera, gallery, calendar, map, navigation, bluetooth, music, video, and short message.

In some embodiments, the application programs may also include launchers (which may also be referred to as desktop applications or home screens, etc.). Generally, after the Android system is started, the Launcher can be used as a core application to reside in the Android system to run. Launcher as the Launcher of Android system can perform basic management on the installed application, such as deleting or displaying the application.

For example, the Launcher runtime may display one or more display interfaces as a desktop for the electronic device. For example, as shown in (a) of fig. 4, the display interface 401 is a first desktop surface of the electronic device, and as shown in (b) of fig. 4, the display interface 402 is a second desktop surface of the electronic device. Launcher may display icons, folders, etc. of application programs in display interface 401 (or display interface 402). In some embodiments, Launcher may also display components 403 such as weather, clocks, etc. in display interface 401 (or display interface 402). These components may also be referred to as widgets, components, cards, etc., and the embodiments of the present application do not limit this.

As also shown in fig. 4 (a), Launcher may divide the display interface 401 into a plurality of grid cells 404 of a certain size in advance. The grid cells 404 may be aligned to form the complete display interface 401. For example, display interface 401 includes 4 × 8 grid cells 404. Launchers generally perform layout and display in the display interface 401 in a minimum unit of one grid cell 404. For example, the size of the weather component 403 in the display interface 401 is 2 × 4, i.e., the weather component 403 occupies 8 grid cells 404 in size displayed in the display interface 401.

In other embodiments, the application programs may further include a notification center APP (also referred to as a notification APP, etc.). The notification center APP may receive notification messages sent by other applications and display the received notification messages in a notification bar (also referred to as a notification panel). The notification bar may be located in a drop-down menu, a minus one screen interface, or a lock screen interface, etc.

The notification message may be a notification message from an application (for example, a push message of a music APP), or may be a notification message from an operating system (for example, a version upgrade message), or may be a notification message from a Feature Availability (FA) or a pa (partition availability), which is not limited in this embodiment of the present application.

In the embodiment of the present application, the Launcher may also receive notification messages sent by other applications. For example, after receiving a flight message sent by the server and purchased by the user, the flight application may carry parameters such as a flight number, a check-in time, and a landing time in the flight message in the notification message 1 and send the notification message to the Launcher. Further, Launcher may display notification message 1 in the current desktop (e.g., display interface 401 or display interface 402 described above). For example, as shown in fig. 5, if Launcher is displaying display interface 401 when it receives notification message 1 described above, Launcher may display the component corresponding to notification message 1 in the display area occupied by weather component 403 while hiding weather component 403 (i.e., not displaying weather component 403). Illustratively, as also shown in fig. 5, the component corresponding to the notification message 1 may be presented to the user in the form of a card 501, which is illustrated in the following embodiments as the component of the corresponding notification message. For example, the card 501 may include parameters such as the flight number, boarding time, and landing time. That is, launchers can display the received notification message using the components in the current desktop, enabling the user to know the specific content of the notification message from the desktop in a timely manner.

Subsequently, Launcher can also dynamically hide the card 501. For example, after the card 501 is displayed for a predetermined time, the Launcher may automatically hide the card 501 to display the original weather component 403. For another example, when Launcher receives notification message 2 of higher priority, Launcher may automatically hide card 501 and overlay the card corresponding to notification message 2 on card 501. For another example, after the Launcher receives the message that the user successfully boards, the Launcher may also automatically hide the card 501, which will be described in detail in the following embodiments, and therefore, details are not described here.

That is to say, in the notification message display method provided in the embodiment of the present application, the Launcher may not only dynamically display the notification message by using the component in the current desktop, so as to facilitate the user to know the latest notification message in time, but also dynamically hide the displayed notification message, thereby ensuring the timeliness of the notification message displayed in the desktop and improving the user experience. Moreover, when the Launcher displays the notification message by using the original components in the desktop, the display layout of other controls such as application icons in the desktop does not need to be adjusted, and the original display content in the desktop is not excessively interfered.

2. Application framework layer

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.

Illustratively, an activity manager, a window manager, a content provider, a view system, a resource manager, an input method manager, etc. may be included in the application framework layer.

Wherein the campaign manager is operable to manage the lifecycle of each application. Applications typically run in the form of activity in the operating system. The activity manager may schedule activity processes of the applications to manage the lifecycle of each application. 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 received, 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 resource manager provides various resources, such as localized strings, icons, pictures, layout files, video files, etc., to the application.

3. Android runtime and system library

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.

Wherein the surface manager is used for managing the display subsystem and providing the fusion of the 2D and 3D layers for a plurality of application programs. 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, and the like. 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.

4. Inner core layer

The kernel layer is a layer between hardware and software. The kernel layer at least comprises a display driver, a camera driver, an audio driver, a sensor driver and the like, and the embodiment of the application does not limit the display driver, the camera driver, the audio driver, the sensor driver and the like.

The following still takes a mobile phone as an example, and details a method for displaying a notification message provided by the embodiment of the present application with reference to the drawings.

For example, each application installed in the handset may send a corresponding notification message to the Launcher to request the Launcher to display the notification message.

For example, the calendar APP may record one or more schedules entered by a user. The user can set the reminding time of the schedule in each schedule. When the reminder time of a certain schedule is reached, the calendar APP may send a corresponding notification message to the Launcher. For another example, the user may purchase a ticket order such as an air ticket, a train ticket, etc. using the travel APP. The ticket order generally includes one or more items of information such as flight number, takeoff time, boarding time, gate, ticket gate or departure time. The server (for example, server a) of the trip APP can maintain the ticket order purchased by each user. And the server A can send corresponding notification messages to the mobile phone based on various information in the ticket order. For example, when the server a detects that there is two hours from the boarding time in a certain ticketing order, it may send a corresponding notification message to the travel APP in the mobile phone. In turn, the travel APP may send the notification message to the Launcher.

It can be seen that the notification message acquired by the Launcher may be a notification message generated locally by the mobile phone in response to a certain event (for example, the notification message generated by the calendar APP according to a schedule set by a user), or may also be a notification message generated by a server of a third-party application (for example, the notification message sent by the server a), that is, the corresponding notification message is acquired in response to the event that the server sends the notification message. That is to say, no matter the notification message is generated locally by the mobile phone or acquired from the server, the embodiments of the present application can be collectively expressed as: the Launcher responds to some event (e.g., the first event) to get a corresponding notification message.

Of course, the server of the third-party application may also obtain the corresponding ticket order from the server of another system (or application) to generate the notification message of the ticket order. For example, the travel APP may obtain a ticketing order purchased by the user from a 12306 system of the china railway, generate a corresponding notification message according to the obtained ticketing order, and send the notification message to the travel APP of the mobile phone.

Illustratively, as shown in fig. 6, a Launcher of a mobile phone may include a display module 601 and a management module 602. Wherein the management module 602 can be used to manage various notification messages sent by other applications. For example, the notification messages are sorted, the priority, the display duration, the display position and size, and the like of the notification messages are set. The management module 602 may send a notification message to be displayed to the display module 601 for display.

Still as shown in fig. 6, taking an example of a notification message 1 that a travel APP sends a ticket order 1 to a Launcher, after the travel APP receives the notification message 1 sent by the server a, the content in the notification message 1 may be instantiated into a corresponding notification object 1 (that is, a notification object, which may also be referred to as a structure). For example, the notification object 1 may include parameters such as an identifier of the travel APP, a notification title, and notification content (e.g., flight number, boarding time, arrival time, and airport information), and one or more of these parameters may be used as content to be displayed in the subsequent notification message 1. Furthermore, the trip APP may call the relevant interface to send the created notification object 1 to the management module 602 in the Launcher, that is, send the notification message 1 to the Launcher.

As also shown in fig. 6, the Launcher management module 602 is used to maintain and manage notification objects (i.e., notification messages) sent from various applications in a preset database. For example, if the Launcher management module 602 has not received the notification object sent by another application before receiving the notification object 1, the management module 602 may set the display order of the notification object 1 to the 1 st bit in a preset database, as shown in table 1. Also, as still shown in table 1, the management module 602 may also set the exposure time length and the retention time length of the notification object 1. The exposure duration refers to the duration when the notification object 1 is displayed, the retention duration refers to the duration when the notification object 1 is retained on the desktop, and the notification object 1 may or may not be displayed when retained on the desktop. The retention duration of a notification object is typically greater than or equal to its exposure duration. For example, when the exposure time length of the notification object 1 is 2 minutes and the retention time length is 5 minutes, after detecting that the notification message 1 has been displayed for 2 minutes, the Launcher may hide the notification message 1 in the Launcher and display other notification messages. At this time, the notification message 1 remains in Launcher although it is not displayed in Launcher. For example, notification message 1 may be hidden under other notification messages, and the user may manually bring notification message 1 up to display in Launcher. Subsequently, when the Launcher detects that the notification message 1 has remained in the Launcher for 5 minutes, the Launcher may delete the notification object 1 corresponding to the notification message 1. At this time, the user cannot call out the notification message 1 in Launcher. Or, when the exposure duration and the retention duration of the notification object 1 are both 2 minutes, when the Launcher detects that the notification message 1 is displayed for 2 minutes, the Launcher can directly delete the notification object 1, so that the Launcher can not display the corresponding notification message 1 any more.

In some embodiments, the management module 602 may further set a card type of the notification object 1, such as a travel class card, an emergency notification class card, a push class card, and the like. Of course, the management module 602 may also set parameters such as a size and a position of a card used when the notification object 1 is displayed, which is not limited in this embodiment of the present application.

TABLE 1

Notification object	Display sequence	Duration of exposure	Duration of reservation	Card type
					Notification object
1	1 st position	2 minutes	5 minutes	Travel class

Further, as also shown in fig. 6, the managing module 602 of Launcher may send a notification message 1 to the display module 601, for notifying the display module 601 to display the corresponding notification message according to the database shown in table 1. In response to the notification message 1, the display module 601 may display a card corresponding to the notification object 1 in a display area in which components are currently provided within the desktop, and hide the components that are originally displayed.

Illustratively, as shown in fig. 7 (a), when the Launcher receives the above notification message 1 from the trip APP, the first desktop 701 is being displayed. A weather component 702 is disposed in the first desktop 701. The weather component 702 is located in the display area 1, and the size of the weather component 702 is 2 × 4 grid cells. When the display module 601 of laucher receives the notification message 1, since the notification object located in the 1 st display order recorded in table 1 is the notification object 1, as shown in (b) in fig. 7, the display module 601 of laucher may overlay the card 703 corresponding to the notification object 1 on the upper layer of the weather component 702, that is, the card 703 and the weather component 702 are stacked and displayed in the display area 1, the size of the card 703 is the same as that of the weather component 702, and the card 703 is located on the upper layer of the weather component 702, so that the weather component 702 is hidden in the first desktop 701. The card 703 may specifically include related parameters carried in the notification object 1, such as an identifier 703a of the travel APP, a flight number 703b, a departure time 703c, an arrival time 703d, a gate 703e, and the like.

Therefore, by receiving the notification message of other applications by the Launcher in the mobile phone, the specific content in the notification message can be displayed by using the component in the current desktop, so that the user can timely obtain the latest notification message from the current desktop, the user is prevented from missing the notification message, and the use experience of the user is improved. Meanwhile, when the existing components are used for displaying the notification messages, the extra display space on the current desktop is not occupied, and the overall display layout of the current desktop is not required to be adjusted, so that the mobile phone can display as much content as possible at the extremely low space adjustment cost.

Still taking the above card 703 as an example, after the display module 601 of Launcher displays the notification message 1 of the outgoing APP through the card 703, the management module 602 of Launcher may continue to manage the card 703 according to the database shown in table 1. For example, when the exposure time of the notification object 1 is set to 2 minutes in table 1, the Launcher management module 602 may monitor the display time of the card 703. For example, Launcher's administration module 602 may also update the remaining exposure time of the card 703 in real time. When the display time of the card 703 in the first desktop 701 reaches 2 minutes, as shown in (a) of fig. 8, the management module 602 may instruct the display module 601 to hide the card 703 in the first desktop 701. At this time, a weather component 702 underlying the card 703 is displayed in the first desktop 701.

At this time, although the display module 601 hides the card 703, since the retention time of the card 703 in the first desktop 701 does not exceed 5 minutes, the display module 601 may retain the card 703 in the first desktop 701. For example, the display module 601 may display the card 703 on a lower layer of the weather component 702. If the user needs to newly display the card 703 in the first desktop 701, as shown in (b) of fig. 8, the user may input a slide operation to the weather component 702 located on the upper layer. Further, the display module 601 may display the card 703 on the upper layer of the weather component 702 in response to the sliding operation, and recall the card 703.

Subsequently, when the management module 602 detects that the retention time of the card 703 in the first desktop 701 reaches 5 minutes, the management module 602 may delete the notification object 1 in table 1 and the display sequence, the exposure time, and other parameters corresponding to the notification object 1. At the same time, the management module 602 may instruct the display module 601 to delete the card 703 in the first desktop 701. At this time, the first desktop 701 may resume the interface shown in fig. 7 (a), i.e., showing the weather component 702 underlying the card 703.

Alternatively, during the period of time that the card 703 is displayed or retained in the first desktop 701, the travel APP may receive an event indicating that the service corresponding to the notification message 1 has been completed. For example, the event may be an event in which the server transmits a check-in success message or a boarding success message (i.e., a service completion message) to the travel APP. At this time, the trip APP may send the service completion message to the management module 602 of the Launcher, and the management module 602 may delete the notification object 1 in table 1 and parameters such as the display order and the exposure duration corresponding to the notification object 1 in response to the service completion message. At the same time, the management module 602 may instruct the display module 601 to delete the card 703 in the first desktop 701. In some embodiments, the event indicating that the service corresponding to notification message 1 is complete may also be generated locally by the handset. For example, a calendar APP in the mobile phone may generate a corresponding service completion message after a certain schedule is completed, and send the message to the Launcher. In some embodiments, the event indicating that the service corresponding to notification message 1 is complete may also be user input. For example, after detecting that the user sets the to-do item 1 in the mobile phone to be completed by the Launcher, the Launcher may delete the corresponding notification object and the corresponding parameters such as the display sequence and the exposure duration, which is not limited in this embodiment of the present application.

Still alternatively, when the Launcher displays the card 703 on the first desktop 701, the Launcher may delete the card 703 in response to a deletion operation input by the user. For example, as shown in fig. 9, when the Launcher displays the card 703 on the first desktop 701, if it is detected that the user inputs a sliding operation (e.g., a left-sliding operation or a right-sliding operation) on the card 703, the Launcher management module 602 may delete the notification object 1 and the parameters of the display order, the exposure duration, and the like corresponding to the notification object 1 in table 1 in response to the sliding operation. At the same time, the management module 602 may instruct the display module 601 to delete the card 703 in the first desktop 701. Illustratively, as also shown in fig. 9, when the display module 601 removes the card 703 from the first desktop 701, the user may gradually remove the card 703 from the first desktop 701 in response to a sliding operation input by the user, while gradually displaying the weather component 702 underlying the card 703.

The display module 601 of Launcher may set the background of the weather component 702 to be transparent or non-transparent when displaying the weather component 702, which is not limited in this embodiment of the application. For example, as also shown in fig. 7 (a), launchers may have the background of the weather component 702 transparent before the card 703 is displayed on the upper layer of the weather component 702. After the upper layer of the weather component 702 covers the card 703, launchers may set the background of the weather component 702 opaque. Accordingly, when the Launcher deletes the card 703 located on the upper layer of the weather component 702, the Launcher may restore the displayed background of the weather component 702 to the transparent display effect again, so as to prompt the user that there is no other notification message in the position where the weather component 702 is located.

That is to say, after the Launcher displays a corresponding notification message by using a certain current component, the Launcher may be triggered to delete the notification message by a retention time length set for the notification message by the Launcher, may also trigger the Launcher to delete the notification message by receiving a service completion message corresponding to the notification message, and may also trigger the Launcher to delete the notification message in response to a deletion operation of the notification message by a user, so that the notification message may not only be dynamically displayed in the current desktop, but also dynamically disappear from the current desktop.

It should be noted that when the user manually removes the card 703 from the first desktop 701 by inputting a deletion operation, the deletion operation may be, in addition to the sliding operation, an operation of clicking a deletion button (or referred to as an ignore button), or the like. For example, as shown in (a) in fig. 10, when Launcher displays a card 703 on the first desktop 701, if it is detected that a user inputs a long press operation on the card 703, the Launcher may display a management window 1001 of the card 703, and a deletion option 1002 may be set in the management window 1001. If the user is detected to select the delete option 1002, Launcher may delete the card 703 as described above. For another example, as shown in fig. 10 (b), when the Launcher displays the card 703 on the first desktop 701, the Launcher may further provide a delete button 1003 on the card 703. If the user is detected to select the delete button 1003, Launcher may delete the card 703 as described above.

The above embodiment is exemplified by the Launcher displaying one notification message by using the weather component 702 in the current desktop, in other embodiments, the Launcher may further receive different notification messages sent by different applications according to the above method, and further display the received notification messages in a deck form and stacked with the weather component 702.

Illustratively, after the Launcher management module 602 receives the notification object 1 sent by the trip APP, it may also receive notification objects sent by other applications. For example, when the calendar APP detects that the current time reaches the reminding time set by the user in the schedule 1, parameters such as the identifier, the notification title, and the notification content (e.g., the reminding time and the schedule content) of the calendar APP may be instantiated as the corresponding notification object 2, and then the notification object 2 is sent to the management module 602 in the Launcher, that is, the notification message 2 is sent to the Launcher.

At this time, as shown in table 2, the Launcher management module 602 may record the notification object 2 in a preset database. Also, similar to the notification object 1 described above, the Launcher management module 602 may also set parameters such as the display order, the exposure time period, the retention time period, and the card type of the notification object 2. In contrast, when there are a plurality of notification objects in the database, the management module 602 may update the display order between the respective notification objects by comparing the plurality of notification objects. For example, it may be previously set that the priority of the notification object of the travel class is higher than that of the notification object of the notification class. At this time, the management module 602 may set the display order of the notification object 1 to the 1 st position and set the display order of the notification object 2 to the 2 nd position. For another example, the management module 602 may extract notification contents in each notification object, and then determine a display order between the notification objects according to the specific notification contents, which is not limited in this embodiment of the present application.

TABLE 2

Notification object	Display sequence	Duration of exposure	Duration of reservation	Card type
					Notification object
1	1 st position	2 minutes	5 minutes	Travel class
					Notification object
2	Position 2	1 minute	3 minutes	Notification class

After the Launcher management module 602 updates the database, it may send a notification message 2 to the display module 601, so as to notify the display module 601 to display a plurality of current notification messages according to the database shown in table 2. At this time, if the display order of the notification object 2 is behind the display order of the notification object 1, the display module 601 of Launcher may still overlay the card 703 corresponding to the above-described notification object 1 on the weather component 702 of the first desktop 701 currently being displayed, as shown in fig. 11. At this time, the card 1101 corresponding to the notification object 1 is positioned below the card 703, and the card 1101 and the card 703 form a card group 1 of the notification message. Weather component 702 may be located in a lower layer of deck 1 hidden in first table top 701.

In addition, in order to prompt the user of receiving a new notification message, Launcher plays a preset animation, for example, an animation of vibrating a border of a card, when displaying the above-mentioned deck according to the database shown in table 2, so as to prompt the user to hide the newly received card 1101 under the card 703. Certainly, the mobile phone may also prompt the user to receive a new notification message through vibration or playing a prompt tone, and the like, which is not limited in this embodiment of the present application.

In some embodiments, as also shown in FIG. 11, display module 601 of Launcher may also display navigation points 1102 around deck 1. For example, the number of navigation points 1102 may be the same as the number of notification messages within the current deck 1. In this way, the user may also be prompted by the navigation point 1102 to receive a new notification message.

Illustratively, the above-described navigation points 1102 may be dynamically displayed or hidden around deck 1. For example, launchers may flash navigation points 1102 momentarily upon receiving a new notification message. For another example, Launcher may flash navigation points 1102 briefly when the number of notification messages changes in deck 1 described above. For another example, Launcher may flash navigation point 1102 briefly when the user switches from other display interfaces to the first desktop 701, which is not limited in this embodiment.

In other embodiments, the display module 601 of Launcher may also prompt the user for the number of notification messages received by setting a corner mark. For example, as shown in fig. 12, after a deck 1 composed of

cards

1101 and 703 is stacked and displayed on the upper layer of a weather component 702 by a display module 601 of Launcher, a corner mark 1201 may be displayed in the upper right corner of the deck 1 (or any one corner of the deck 1), and the number in the corner mark 1201 is the number of notification messages in the current deck 1. Moreover, the corner mark 1201 can also be dynamically displayed or hidden according to the above method, which is not limited in this embodiment.

Illustratively, after Launcher displays deck 1 by using weather component 702 in first desktop 701, notification messages sent by other applications may also be received. For example, the travel APP may also locate the user. For example, the travel APP may locate the user by means of a GPS, a base station, or a Wi-Fi signal, to obtain a location result of the user. When the latest positioning result indicates that the user is in (or near) a certain subway station, the travel APP may instantiate the parameters such as the name and the bus number of the subway station as the corresponding notification object 3, and then send the notification object 3 to the management module 602 of the Launcher.

At this time, similar to the above-described embodiment, as shown in table 3, the Launcher management module 602 may record the notification object 3 in a preset database. Also, the Launcher management module 602 may set parameters such as the display order, exposure time, retention time, and card type of the notification object 3. For example, if it is preset that the priority of the car code is higher than the priority of the flight information, as shown in table 3, the management module 602 may set the display order of the notification object 3 to 1 st, the display order of the notification object 1 to 2 nd, and the display order of the notification object 2 to 3 rd, to obtain the updated database.

TABLE 3

Notification object	Display sequence	Duration of exposure	Duration of reservation	Card type
					Notification object
3	1 st position	2 minutes	5 minutes	Travel class
					Notification object
1	Position 2	2 minutes	5 minutes	Travel class
					Notification object
2	Position 3	1 minute	3 minutes	Notification class

After the Launcher management module 602 updates the database, it may send a notification message 3 to the display module 601, so as to notify the display module 601 to display a plurality of current notification messages according to the database shown in table 3. At this time, as shown in (a) of fig. 13, the display module 601 may cover the deck 1 on the weather component 702 of the first desktop 701 currently being displayed, except that the card 1301 corresponding to the notification object 3 is positioned at the uppermost layer in the deck 1, the card 1101 (not shown in fig. 13) corresponding to the notification object 2 is positioned at the lowermost layer in the deck 1, and the card 703 (not shown in fig. 13) corresponding to the notification object 1 is positioned between the card 1101 and the card 1301. That is, if the latest received notification message has a higher priority than the card (e.g., the card 703) currently located at the uppermost layer of the deck, Launcher may display the latest received notification message in the uppermost layer of the deck in the form of a card, so that the user can know the content of the notification message having the highest priority in time.

In addition, when the plurality of notification messages are included in deck 1 described above, the user can also manually switch the notification message located at the uppermost layer of deck 1. As also shown in fig. 13 (a), after Launcher displays the card 1301 as the notification message on the uppermost layer on the first desktop 701, the user can switch the notification message on the uppermost layer of the deck 1 by inputting a switching operation (e.g., a slide-up operation or a slide-down operation) on the card 1301. Illustratively, if a user input swipe operation on the card 1301 is detected, Launcher may update the database shown in table 3, and adjust the display order of the respective notification objects. As shown in Table 4, the Launcher can set the display order of the notification object 3 to the 3 rd position, the display order of the notification object 1 to the 1 st position, and the display order of the notification object 2 to the 2 nd position by the management module 602. Further, Launcher can display a plurality of notification messages currently according to the database shown in table 4 through the display module 601. At this time, as shown in (b) of fig. 13, the display module 601 may cover the deck 1 on the weather component 702 of the first desktop 701, except that the deck 703 corresponding to the notification object 1 is positioned at the uppermost layer in the deck 1 at this time, thereby implementing switching of the notification message within the deck 1.

TABLE 4

Notification object	Display sequence	Duration of exposure	Duration of reservation	Card type
					Notification object
1	1 st position	2 minutes	5 minutes	Travel class
					Notification object
2	Position 2	1 minute	3 minutes	Notification class
					Notification object
3	Position 3	2 minutes	5 minutes	Travel class

Of course, Launcher may also automatically update the database corresponding to deck 1, and refresh deck 1 in first desktop 701 according to the updated database. For example, Launcher may set each card in card group 1 to display for 10 seconds in sequence and then switch to the next card to display, which is not limited in this embodiment.

In some embodiments, deck 1 may also include weather component 702 as described above. For example, the deck 1 may include the above-described card 703, card 1101, card 1301, and weather component 702. If the weather component 702 is the lower layer of the card 1301, after the Launcher receives the switching operation input by the user to the card 1301, the Launcher can display the weather component 702 positioned at the lower layer of the card 1301.

It should be noted that, in the above embodiment, the management module 602 is disposed in Launcher for example, and it is understood that the management module 602 may also be disposed in other applications, engines, or services in the application layer. Alternatively, the management module 602 may be disposed in the application framework layer. Or, the management module 602 may also be disposed in a server on a network side, and the mobile phone may implement the method by interacting with the management module 602 in the server, which is not limited in this embodiment of the present application.

While the above embodiments are illustrated with launchers occupying the display area of the weather component 702 to display a card or deck, in some embodiments, multiple components may be provided on the desktop on which the phone is displaying.

For example, as shown in (a) in fig. 14A, a weather component 702 and a calendar component 1402 may be provided in a second desktop 1401 which the mobile phone is displaying. At this time, if the Launcher receives one or more notification messages sent by other applications, the Launcher may display the notification messages in the display area where any one of the weather component 702 and the calendar component 1402 is located, according to the above-described method. For example, launchers may set up to display notification messages using the display area in which the weather component 702 is located by default. At this time, as shown in (b) in fig. 14A, the Launcher may set the size of a card 1403 (or a deck) corresponding to the received notification message to the size of the weather component 702, and the card 1403 is displayed on the upper layer of the weather component 702. Alternatively, Launcher may select the display area where the corresponding component is located for display according to the size of the card 1403. For example, if the size of card 1403 is the same as the size of weather component 702, Launcher may display card 1403 on the top level of weather component 702, at which time the display of calendar component 1402 is not affected. Of course, if the size of the card 1403 is the same as the size of the calendar component 1402, Launcher may display the card 1403 on the top level of the calendar component 1402, at which time the display of the weather component 702 is not affected

Alternatively, as shown in (a) in fig. 14B, still taking the example that the weather component 702 and the calendar component 1402 are included in the second desktop 1401, after the Launcher receives one or more notification messages sent by other applications, both of the above components may also be used to expose the notification messages. For example, as shown in (B) in fig. 14B, the Launcher may display a notification message sent by the travel APP received first on the upper layer of the weather component 702 in the form of a card 1403. Subsequently, if the Launcher in turn receives the notification message sent by the calendar APP, the Launcher may display the corresponding card 1404 on the upper layer of the calendar component 1402. For another example, when the Launcher receives a plurality of notification messages, the Launcher may display the notification messages whose display order is in the 1 st and 2 nd bits on the upper layers of the weather component 702 and the calendar component 1402, respectively. Of course, if the second desktop 1401 further includes more components, the Launcher may also display more notification messages according to the above method, so that the user can know more notification messages from the current desktop.

In other embodiments, there may be no component set in the desktop on which the handset is displaying when the Launcher receives one or more notification messages sent by other applications. Illustratively, as shown in fig. 15 (a), when the mobile phone displays the third desktop 1501 (no component in the third desktop 1501), the Launcher may receive one or more notification messages sent by other applications. For example, after the Launcher receives the notification message sent by the trip APP, the Launcher may still update a preset database (e.g., the database shown in table 1) according to the method provided in the foregoing embodiment. In contrast, Launcher may temporarily not notify the display module 601 to display according to the updated database. Accordingly, when the Launcher switches from the third desktop 1501 to the first desktop 701, for example, when it is detected that the user inputs a sliding operation to switch the third desktop 1501 to the first desktop 701, the Launcher may notify the display module 601 to display according to the updated database, and at this time, as shown in (b) in fig. 15, the Launcher may overlay the corresponding card 703 on the upper display of the weather component 702 in the first desktop 701.

In addition, when the Launcher switches from the third desktop 1501 to the first desktop 701, the Launcher may also view the notification message in the first desktop 701 by playing a preset animation on the card 703, or by displaying a navigation point or a corner mark, or by vibrating or playing a prompt tone, or the like.

Similarly, if the mobile phone receives one or more notification messages sent by each application when the screen is locked (also referred to as screen-off or screen-blacking), the mobile phone may also be installed with the method to display according to the updated database when the first desktop 701 is displayed for the first time, which is not limited in this embodiment of the present application.

In other embodiments, the desktop that the mobile phone is displaying is still taken as the third desktop 1501 without any component, at this time, after the Launcher receives one or more notification messages sent by other applications, the Launcher may also display a card (or a group of cards) corresponding to the notification message in a blank area in the third desktop 1501. The blank area refers to an area without controls such as application icons, components, folders and the like, and the blank area may include contents such as wallpapers and the like.

As shown in (a) of fig. 16, when the mobile phone displays the third desktop 1501, if the Launcher receives a notification message sent by the travel APP, the Launcher may update a preset database (for example, the database shown in table 1) according to the method provided in the above-described embodiment. Further, Launcher may notify the display module 601 to display in the third desktop 1501 according to the updated database. For example, the size of the card 703 corresponding to the notification message sent by the travel APP is 2 × 4, and as shown in fig. 16 (b), the Launcher may select a display area having a size of 2 × 4 in the blank area of the third desktop 1501 to display the card 703. For another example, the Launcher may first set the size of the card 703 according to the size of the blank area in the third desktop 1501, and generally, the size of the card 703 is smaller than or equal to the size of the blank area. Further, Launcher may display the card 703 in a blank area of the third desktop 1501.

In addition, the user can trigger Launcher to display the notification message in the above-mentioned way by adding a component in the desktop. Illustratively, the mobile phone may receive a preset operation of adding a component, which is input in the third desktop 1501 by a user, when the third desktop 1501 is displayed. For example, the preset operation may be a two-finger kneading operation. Further, as shown in (a) of fig. 17, Launcher may display a tool menu 1701 of the desktop in response to the above-described preset operation, wherein an option 1702 for adding a component may be set in the tool menu 1701. If the user selection option 1702 is detected, as shown in (b) in fig. 17, Launcher may present preview options of various components, for example, the preview option may include a UU card 1703 for intelligently displaying a notification message, and it is understood that the name of the card 1703 is not limited in this embodiment of the present application. UU card 1703 may be similar to existing weather component 702. For example, UU card 1703 may be the same as displayed in weather component 702, but the background color may be different, prompting the user that UU card 1703 defaults to display weather component 702 without a notification message. Alternatively, UU card 1703 may be similar to an existing calendar or like component to prompt the user to default to displaying the corresponding calendar or like component without a notification message. Subsequently, if it is detected that the user selects the UU card 1703, Launcher may display the UU card 1703 in the third desktop 1501, as shown in (c) of fig. 17. Because the Launcher has not received notification messages from other applications at this time, UU card 1703 may be displayed in the same manner as weather component 702. If the subsequent Launcher receives the notification message sent by other applications, the Launcher may display the corresponding card or group of cards by using the display position of the UU card 1703 according to the method in the above embodiment, so as to dynamically show the received notification message to the user.

In some embodiments, in order to better guide the user to know the notification message of the application by using the UU card 1703, when the Launcher displays the UU card 1703 added by the user in the third desktop 1501 for the first time, as shown in fig. 18, the Launcher may display a guide popup 1801, and the content in the guide popup 1801 is used for prompting the user about the specific function and operation method of the UU card 1703, and the like. For example, the guidance popup 1801 may include a plurality of pages of popup contents, which are respectively used to prompt a user about a specific function of the UU card 1703, an operation method for switching cards, an operation method for deleting cards, and the like. The user can view the contents of each page of the pop-up window through the sliding guide pop-up window 1801.

Or, the Launcher may not display the guidance popup 1801 when displaying the UU card 1703 added by the user in the third desktop 1501 for the first time, and correspondingly, the Launcher may display the guidance popup 1801 when receiving the notification message sent by another application for the first time, and guide the user to know the specific function and operation method of the UU card 1703. In this scenario, while displaying the above guidance popup 1801, Launcher may also display a corresponding notification message through the UU card 1703, which is not limited in this embodiment.

In other embodiments, the user may manually set the type, number, content, or the like of notification messages that the UU card 1703 is allowed to display. For example, as shown in (a) of fig. 19, Launcher may display a card 703 on the upper layer of a weather component 702 according to the method in the above embodiment. At this time, if it is detected that the user inputs a long press operation to the card 703, the Launcher may display a management window 1001 of the card 703, and a setting option 1901 may be set in the management window 1001. If the user is detected to select the setting option 1901, Launcher may jump to the setting interface 1902, as shown in fig. 19 (b). In setting interface 1902, a user may manually set one or more options such as the type, number, or content of notification messages displayed by UU card 1703. Subsequently, Launcher may display the notification message customized by the user in UU card 1703 according to the selection of the user in setting interface 1902, thereby improving the user experience. Of course, Launcher may also provide the user with options of setting the size, color, and the like of UU card 1703, which is not limited in this embodiment.

It should be noted that, in the embodiment, the notification message is displayed on a desktop by using a mobile phone by way of example, and it may be understood that the display method of the notification message may also be applied to electronic devices such as a vehicle-mounted device, a tablet computer, and a watch, and all of these devices may be used to implement the display method of the notification message described in the embodiment, which is not limited in this application.

As shown in fig. 20, an embodiment of the present application discloses an electronic device, which may be the above-mentioned mobile phone. The electronic device may specifically include: a touch screen 2001, the touch screen 2001 including a touch sensor 2006 and a display screen 2007; one or more processors 2002; a memory 2003; one or more application programs (not shown); and one or more computer programs 2004, which may be connected via one or more communication buses 2005. Wherein the one or more computer programs 2004 are stored in the memory 2003 and configured to be executed by the one or more processors 2002, the one or more computer programs 2004 comprising instructions that may be used to perform the steps associated with the embodiments described above.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, 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. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

Each functional unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or make a contribution to the prior art, or all or part of the technical solutions may be implemented in the form of a software product stored in a storage medium and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: flash memory, removable hard drive, read only memory, random access memory, magnetic or optical disk, and the like.

The above description is only a specific implementation of the embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the embodiments of the present application should be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

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

the method comprises the steps that electronic equipment displays a first desktop, and a first assembly is displayed in a first display area of the first desktop;

the electronic equipment acquires a first event;

in response to the first event, the electronic device displays a second component corresponding to the first event in the first display area, the first component is not displayed in the first display area, the second component is different from the first component, and the content of the second component is associated with the content of the first notification message;

wherein the first event is an event associated with the first notification message.

2. The method of claim 1, wherein the second component is located on an upper layer of the first component.

3. The method of claim 1, further comprising, after the electronic device displays a second component corresponding to the first event in the first display area:

after the second assembly is displayed for a preset time, the electronic equipment displays the first assembly in the first desktop, and the second assembly is not displayed in the first display area.

4. The method of claim 1, further comprising, after the electronic device displays a second component corresponding to the first event in the first display area:

and if a preset deleting operation input by a user on the second component is received, the first component is displayed in the first desktop by the electronic equipment, and the second component is not displayed in the first display area.

5. The method of claim 1, further comprising, after the electronic device displays a second component corresponding to the first event in the first display area:

the electronic equipment acquires a second event, wherein the second event is used for indicating that the service corresponding to the first notification message is completed;

in response to the second event, the electronic device displays the first component in the first desktop and the first display area does not display the second component.

6. The method of claim 1, further comprising, after the electronic device displays a second component corresponding to the first event in the first display area:

the electronic equipment acquires a third event;

if the priority of the third event is higher than that of the first event, the electronic equipment displays a third component corresponding to the third event in the first display area, wherein the third component is positioned on the upper layer of the second component, and the content of the third component is associated with the content of a second notification message; alternatively, the first and second electrodes may be,

if the priority of the first event is higher than that of the third event, the electronic equipment continues to display the second component in the first display area, a third component corresponding to the third event is positioned at the lower layer of the second component, and the content of the third component is associated with the content of a second notification message;

wherein the third event is an event associated with the second notification message.

7. The method of claim 6, further comprising, after the electronic device displays a third component corresponding to the third event in the first display area:

And if receiving a preset switching operation input by a user to the third component, displaying the second component in the first desktop by the electronic equipment, and not displaying the third component in the first display area.

8. The method of claim 6, after the electronic device obtains the third event, further comprising:

the electronic device displays a navigation point on the first display area or around the first display area, wherein the navigation point is used for prompting a user to receive a plurality of notification messages.

9. The method of claim 6, after the electronic device obtains the third event, further comprising:

if the fact that the finger of the user touches the first display area is detected, the electronic equipment displays a navigation point on the first display area or the periphery of the first display area, and the navigation point is used for prompting the user to receive a plurality of notification messages.

10. The method of claim 1, wherein a fourth component is displayed in the second display area of the first desktop surface;

after the electronic device displays a second component corresponding to the first event in the first display area, the method further includes:

The electronic equipment acquires a fourth event;

in response to the fourth event, the electronic device displays a fifth component corresponding to the fourth event in the second display area, and the second display area does not display the fourth component, the content of the fifth component being associated with the content of a third notification message;

wherein the fourth event is an event associated with the third notification message.

11. The method of claim 1, wherein the electronic device obtains a first event comprising:

the method comprises the steps that when a third desktop is displayed by the electronic equipment, a first event is obtained, and no component exists in the third desktop;

wherein the electronic device displays a second component corresponding to the first event in the first display area, and the method includes:

if the fact that the electronic equipment switches the third desktop to the first desktop is detected, the electronic equipment displays the second assembly in the first display area.

12. The method of claim 1, wherein the electronic device obtains a first event comprising:

After the electronic device acquires the first event, the method further comprises the following steps:

the electronic equipment displays a second component corresponding to the first event in a blank area of the third desktop.

13. The method of claim 1, further comprising, before the electronic device displays the first desktop surface:

in response to an operation of adding a first component by a user, adding the first component in the first desktop by the electronic equipment;

the electronic equipment displays a guide popup window which is used for prompting an operation method of the component in the first display area.

14. The method of claim 1, further comprising:

the electronic equipment displays a setting interface for setting one or more of the type, number or content of the components displayed in the first display area.

15. The method of claim 1, wherein the first event comprises the first notification message; wherein the electronic device acquires a first event, including:

and the electronic equipment acquires a first event carrying the first notification message from a server.

16. The method according to any of claims 1-15, further comprising, after the electronic device acquires the first event:

The electronic equipment sets parameters of a second component corresponding to the first event, wherein the parameters comprise one or more of display sequence, exposure time, retention time or component type.

17. An electronic device, comprising:

a touch screen comprising a touch sensor and a display screen;

one or more processors;

a memory;

wherein the memory has stored therein one or more computer programs, the one or more computer programs comprising instructions, which when executed by the electronic device, cause the electronic device to perform a method of displaying a notification message as claimed in any of claims 1-16.

18. A computer-readable storage medium having instructions stored therein, which when run on an electronic device, cause the electronic device to perform a method of displaying a notification message as recited in any of claims 1-16.