Notification message display method and electronic device

Abstract

A notification message display method and an electronic device, relating to the technical field of terminals. According to the method, a plurality of real-time progress notification messages of one service are aggregated and displayed on the basis of a real-time progress notification message template, reducing the display number of the real-time progress notification messages, and a unified template is used to display the real-time progress notification messages, so that a display interface is neater. According to the method, real-time progress notification messages and non-real-time progress notification messages are displayed in different areas, important messages and non-important messages in the non-real-time progress notification messages are displayed in different areas, the important notification messages are displayed at the upper part of an interface, and the plurality of notification messages are displayed in order, so that a user can quickly find a required notification message, and high human-machine interaction efficiency is achieved.

Description

Notification message display method and electronic device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on August 3, 2023, with application number 202310978111.9 and application name “Method for displaying notification messages and electronic device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminal technology, and in particular to a method for displaying notification messages and an electronic device. Background Art

[0003] System UI (System UI) notifications can be displayed in the status bar or notification panel of an electronic device. Displaying System UI notifications in the status bar or notification panel conveys important system or application messages in an intuitive way, and serves as the primary channel for real-time, proactive interaction between system and ecosystem applications and users.

[0004] In the related art, there are many SystemUI notification messages in electronic devices, making it difficult for users to quickly find the notification messages they need, and the human-computer interaction efficiency is low.

[0005] Summary of the Invention

[0006] The present application provides a method for displaying notification messages and an electronic device, which can aggregate and display multiple real-time progress notification messages of a business, so that users can quickly find the real-time progress notification messages they need, thereby improving human-computer interaction efficiency.

[0007] In order to achieve the above objectives, the embodiments of the present application provide the following technical solutions:

[0008] In a first aspect, the present application provides a method for displaying a notification message, the method comprising: obtaining a first real-time progress notification message parameter; displaying the first real-time progress notification message according to the first real-time progress notification message parameter; obtaining a second real-time progress notification message parameter; updating the first real-time progress notification message according to the second real-time progress notification message parameter, and displaying it as a second real-time progress notification message.

[0009] In this way, multiple real-time progress notification messages are displayed in an aggregated manner, which reduces the number of displayed real-time progress notification messages, makes the display interface more concise, and allows users to quickly find the real-time progress notification messages they need, thereby improving human-computer interaction efficiency.

[0010] For example, taking a takeaway delivery notification message as an example, as shown in FIG14(a), after the rider accepts the order, a first real-time progress notification message 1002 is displayed, indicating that the rider has accepted the order and is on his way to the merchant. As shown in FIG14(b), after the rider picks up the takeaway, a second real-time progress notification message 1002' is displayed, indicating that the rider has picked up the takeaway and is on his way to the user. The second real-time progress notification message 1002' is updated based on the first real-time progress notification message 1002.

[0011] As another example, taking a takeout delivery notification as an example, as shown in FIG23(a), after the rider accepts the order, a first real-time progress notification message 2005 is displayed, indicating that the rider has accepted the order and is on their way to the merchant. After the rider picks up the takeout, a second real-time progress notification message 2005' is displayed, indicating that the rider has picked up the takeout and is on their way to the user. The second real-time progress notification message 2005' is updated based on the first real-time progress notification message 2005.

[0012] In one possible implementation, the method further includes: displaying a second real-time progress notification message based on the first real-time progress notification message parameters and the second real-time progress notification message parameters. Thus, the second real-time progress notification message includes the content of the first real-time progress notification message parameters and the second real-time progress notification message parameters. The user can obtain partial content of the first real-time progress notification message through the second real-time progress notification message, learn the historical status of the real-time progress notification message, and better understand the content of the second real-time progress notification message.

[0013] For example, taking the takeaway notification message as an example, as shown in (b) of Figure 14, after the rider picks up the takeaway, a second real-time progress notification message 1002' is displayed. The expansion area 1006' in the second real-time progress notification message 1002' also includes the rider's historical status from the rider having accepted the order to the merchant time.

[0014] In one possible implementation, updating the first real-time progress notification message to the second real-time progress notification message includes: generating the second real-time progress notification message based on parameters of the second real-time progress notification message; and replacing the first real-time progress notification message with the second real-time progress notification message. The replacement process is simple and the algorithm is simple.

[0015] Exemplarily, taking the takeaway notification message as an example, as shown in FIG14 , the second real-time progress notification message 1002 ′ replaces the first real-time progress notification message 1002 , and the second real-time progress notification message 1002 ′ is displayed.

[0016] In one possible implementation, updating a first real-time progress notification message to a second real-time progress notification message includes: updating a portion of the first real-time progress notification message based on parameters of the second real-time progress notification message to generate the second real-time progress notification message; and displaying the second real-time progress notification message. In this way, only a portion of the first real-time progress notification message is updated, saving resources and improving update efficiency.

[0017] For example, taking the takeaway notification message as an example, as shown in FIG14 , the main information area 1004, the sub-information area 1005 and the extended area 1006 in the first real-time progress notification message 1002 are updated to the main information area 1004', the sub-information area 1005' and the extended area 1006' according to the second real-time progress notification message parameters, and the second real-time progress notification message 1002' is displayed.

[0018] In a possible implementation, the application framework layer applied to the terminal device obtains the first real-time progress notification message parameter, including: the application framework layer obtains the first real-time progress notification message parameter from the first application.

[0019] In this way, after the application framework layer of the terminal device obtains the first real-time progress notification message parameters, it can uniformly generate and manage the first real-time progress notification message.

[0020] In one possible implementation, displaying the first real-time progress notification message includes: displaying the first real-time progress notification message according to a real-time progress notification message template; the real-time progress notification message template includes an icon area; the icon area is used to display an application icon, a service icon, or a superimposed icon of the application icon and the service icon. In this way, a unified real-time progress notification message template can be used to display the real-time progress notification message, neatly displaying the real-time progress notification message and improving the user's visual experience.

[0021] Optionally, the real-time progress notification message template may be the real-time progress notification template in the notification bar as shown in FIG6 , or the live capsule template in the status bar as shown in FIG20 .

[0022] Optionally, the service icon is used to represent an icon related to the service running in the application. For example, the service icon includes a contact avatar icon in a call notification message in a call application, a music cover icon in a music playback notification message, or a direction icon in a navigation application.

[0023] Exemplarily, the icon area can be an icon of a food delivery application as shown in (a) of FIG10 ; it can also be a direction icon of a navigation application as shown in (b) of FIG9 ; or it can be an overlay icon of a call application and a contact avatar as shown in (a) of FIG7 .

[0024] In one possible implementation, displaying a first real-time progress notification message according to a real-time progress notification message template includes: the first real-time progress notification message parameter includes a first parameter, and when the first parameter indicates that the first real-time progress notification message parameter is a real-time progress notification message parameter, displaying the first real-time progress notification message according to the real-time progress notification message template.

[0025] Exemplarily, when the first real-time progress notification message parameter includes the first parameter, and the first real-time progress notification message parameter is a real-time progress notification message parameter, the first real-time progress notification message is displayed according to the real-time progress notification message template.

[0026] For example, when the first parameter is true and the first real-time progress notification message parameter is a real-time progress notification message parameter, the first real-time progress notification message is displayed according to the real-time progress notification message template. This embodiment of the present application does not impose any specific limitation on this.

[0027] In one possible implementation, the real-time progress notification message template includes a first real-time progress notification message template; the first real-time progress notification message template includes an icon area, a primary information area, and a secondary information area; the primary information area includes a rich text control or a timer control; and the secondary information area includes a rich text control. This displays necessary information about the real-time progress notification message to ensure that the user understands the content of the real-time progress notification message.

[0028] Optionally, the real-time progress notification message generated by the first real-time progress notification message template (real-time progress notification message template) is displayed in the notification bar.

[0029] For example, a high-speed rail notification message is shown in Figure 9(a). Icon area 903 displays the high-speed rail application icon. Primary information area 904 displays a rich text control, "Train xxx from station A is leaving at 20:35." This text can be rich text, such as in bold. Secondary information area 905 includes a rich text control, "Ticket gate 6B, seat 03, car 12F." This text can also be rich text.

[0030] As another example, as shown in FIG7(c), the icon area 723 of the recording notification message 722 is the icon of the recording application. The main information area 724 is a timer control indicating the duration of the recording. The secondary information area 725 is the text "Recording", which can be rich text.

[0031] In one possible implementation, the first real-time progress notification message template further includes at least one of an auxiliary area and an extended area; the auxiliary area includes at least one of an operation control and a progress control for the service corresponding to the first real-time progress notification message; and the extended area includes at least one of progress information, detailed information, and operation information for the service corresponding to the first real-time progress notification message. This allows for simple operations on the real-time progress notification message, or displays more detailed information about the real-time progress notification message, improving the user's viewing and usage experience.

[0032] For example, as shown in FIG7(a), call notification message 702 further includes auxiliary area 706, which includes operation controls for call notification message 702. As shown in FIG8(a), Bluetooth transmission notification message 802 also includes auxiliary area 806, which includes a progress control for Bluetooth transmission notification message 802.

[0033] As another example, as shown in FIG10( a ), the takeout notification message 1002 includes an extension area 1006 , and the extension area 1006 includes progress information of the takeout notification message 1002 .

[0034] In a possible implementation, the real-time progress notification message template includes a second real-time progress notification message template; the second real-time progress notification message template includes at least one of a text control, a progress control, and a timing control.

[0035] Optionally, the real-time progress notification message generated by the second real-time progress notification message template (live capsule template) is displayed in the status bar.

[0036] Optionally, the second real-time progress notification message template does not include a main information area and a sub-information area.

[0037] For example, as shown in FIG21( b ), the status bar 2112 may include a screen recording capsule 2113 and a call recording capsule 2114. The screen recording capsule 2113 includes an icon of the screen recording application and a timer control indicating the recording duration. The call recording capsule 2114 includes an icon of the call application and a timer control indicating the call duration.

[0038] In one possible implementation, the method further includes: carrying a second parameter in the second real-time progress notification message parameters, and determining whether to terminate the display of the second real-time progress notification message based on the second parameter; terminating the display of the second real-time progress notification message when the display duration of the second real-time progress notification message reaches a preset duration; or terminating the display of the second real-time progress notification message when the difference between the creation time of the first real-time progress notification message and the last refresh time of the second real-time progress notification message is greater than a preset time. In this way, the display of the real-time progress notification message can be terminated actively or passively, preventing the real-time progress notification message from occupying the interface position for a long time.

[0039] Optionally, when the second real-time progress notification message parameters include a second parameter, it may indicate that the display of the second real-time progress notification message ends when the display duration of the second real-time progress notification message reaches a preset duration. Alternatively, when the second parameter included in the second real-time progress notification message parameters is true, it may indicate that the display of the second real-time progress notification message ends when the display duration of the second real-time progress notification message reaches a preset duration.

[0040] In one possible implementation, the method further includes: displaying real-time progress notification messages in a first area; displaying non-real-time progress notification messages in a second area; the first area being located above the second area; the non-real-time progress notification messages including service notification messages and / or content information; the service notification messages including notification messages from social applications and / or important applications; and the content information including notification messages from advertising applications. In this way, multiple notification messages can be displayed in an orderly manner without overwhelming important real-time progress notification messages. Real-time progress notification messages are presented first, improving the user experience.

[0041] Exemplarily, as shown in FIG16 , the first area is for real-time progress notification messages, and the second area is for non-real-time progress notification messages.

[0042] In one possible implementation, displaying non-real-time progress notification messages in the second area includes: displaying service notification messages in the third area; displaying content information in the fourth area; the third and fourth areas being subareas of the second area; and the third area being located above the fourth area. In this way, non-real-time progress notification messages are categorized by type, allowing multiple non-real-time progress notification messages to be displayed in an orderly manner, with service notification messages displayed above content information, making it easier for users to view more important service notification messages and improving their user experience.

[0043] For example, as shown in Figure 16, the second area also includes a third area and a fourth area, the third area displays service notification messages, and the fourth area displays content information. The third area is located above the fourth area.

[0044] In one possible implementation, non-real-time progress notification messages are displayed in the second area; the first area is located above the second area and further includes: non-real-time progress notification messages including important notification messages and / or non-important notification messages; important notification messages are displayed in the third area; and non-important notification messages are displayed in the fourth area; the third and fourth areas are subareas of the second area; and the third area is located above the fourth area. In this way, non-real-time progress notification messages are categorized according to their importance and displayed in different areas. Important notification messages are displayed above non-important notification messages, making it easier for users to view more important notification messages and improving the user experience.

[0045] In one possible implementation, the method further includes: calibrating the importance of the non-real-time progress notification message, and determining the display area of ​​the non-real-time progress notification message based on the calibration result. In this way, the importance of the non-real-time progress notification message can be re-determined to prevent the flooding of important notification messages.

[0046] In one possible implementation, the importance of non-real-time progress notification messages is calibrated, and the area in which the non-real-time progress notification messages are displayed is determined based on the calibration results. This includes: weighting the first importance of the non-real-time progress notification message based on at least one of the importance of the channel through which the non-real-time progress notification message is sent, the importance of the application to which the non-real-time progress notification message corresponds, and the importance of the content in the non-real-time progress notification message to obtain a second importance of the non-real-time progress notification message; the first importance is the importance set for the non-real-time progress notification message by the application to which the non-real-time progress notification message corresponds; if the second importance is greater than or equal to a preset threshold, the non-real-time progress notification message is displayed in a third area; if the second importance is less than the preset threshold, the non-real-time progress notification message is displayed in a fourth area. By evaluating the importance of non-real-time progress notification messages from multiple perspectives, the accuracy of the calibration results is improved.

[0047] In a second aspect, the present application provides a method for displaying a notification message, the method comprising: displaying a first real-time progress notification message; displaying the first real-time progress notification message according to a real-time progress notification message template; the real-time progress notification message template including an icon area; the icon area being used to display an application icon, a service icon, or a superimposed icon of the application icon and the service icon; updating the first real-time progress notification message to a second real-time progress notification message; the second real-time progress notification message conforming to the real-time progress notification message template. In this manner, a unified real-time progress notification message template can be used to display the real-time progress notification message, neatly displaying the real-time progress notification message and improving the user's visual experience.

[0048] In one possible implementation, the first real-time progress notification message is displayed according to the real-time progress notification message template, including: the first real-time progress notification message parameters include a first parameter, and when the first parameter indicates that the first real-time progress notification message parameter is a real-time progress notification message parameter, the first real-time progress notification message is displayed according to the real-time progress notification message template.

[0049] In one possible implementation, the real-time progress notification message template includes a first real-time progress notification message template; the first real-time progress notification message template includes an icon area, a main information area, and a sub-information area; the main information area includes a rich text control or a timing control; and the sub-information includes a rich text control.

[0050] In one possible implementation, the first real-time progress notification message template also includes at least one of an auxiliary area and an extended area; the auxiliary area includes at least one of an operation control and a progress control of the business corresponding to the first real-time progress notification message; the extended area includes at least one of progress information, detailed information, and operation information of the business corresponding to the first real-time progress notification message.

[0051] In a possible implementation, the real-time progress notification message template includes a second real-time progress notification message template; the second real-time progress notification message template includes at least one of a text control, a progress control, and a timing control.

[0052] In a third aspect, the present application provides an electronic device, comprising: a processor coupled to a memory; the processor being configured to execute a computer program stored in the memory so that the electronic device executes the method as described in the first aspect, or executes the method as described in the second aspect.

[0053] In a fourth aspect, the present application provides a computer-readable storage medium, which includes a computer program or instructions. When the computer program or instructions are run on an electronic device, the electronic device executes the method as described in the first aspect, or executes the method as described in the second aspect.

[0054] In a fifth aspect, the present application provides a chip system comprising at least one processor and at least one interface circuit, wherein the at least one interface circuit is used to perform transceiver functions and send instructions to at least one processor. When the at least one processor executes the instructions, the at least one processor executes the method as described in any one of the first aspects above, or executes the method as described in the second aspect.

[0055] In a sixth aspect, the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method as described in any one of the first aspects, or the method as described in the second aspect.

[0056] In a seventh aspect, an embodiment of the present application provides a circuit system, the circuit system including a processing circuit, the processing circuit being configured to execute the method of the first aspect or any one of the implementations of the first aspect, or to execute the method as described in the second aspect.

[0057] The technical effects corresponding to the second to seventh aspects and any implementation method of the second to seventh aspects can be referred to the technical effects corresponding to the above-mentioned first aspect and any implementation method of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] FIG1 is a schematic diagram of a process for sending a notification message according to an embodiment of the present application;

[0059] FIG2 is a schematic diagram of an interface of a notification message provided in an embodiment of the present application;

[0060] FIG3 is a schematic structural diagram of an electronic device provided in an embodiment of the present application;

[0061] FIG4 is a schematic structural diagram of a mobile phone provided in an embodiment of the present application;

[0062] FIG5 is a schematic diagram of a system architecture provided in an embodiment of the present application;

[0063] FIG6 is a schematic diagram of a notification message template provided in an embodiment of the present application;

[0064] FIG7 is a schematic diagram of a notification message provided in an embodiment of the present application;

[0065] FIG8 is a schematic diagram of another notification message provided in an embodiment of the present application;

[0066] FIG9 is a schematic diagram of another notification message provided in an embodiment of the present application;

[0067] FIG10 is a schematic diagram of another notification message provided in an embodiment of the present application;

[0068] FIG11 is a schematic diagram of another notification message provided in an embodiment of the present application;

[0069] FIG12 is a schematic diagram of another notification message interface provided in an embodiment of the present application;

[0070] FIG13 is a schematic diagram of a notification message update provided in an embodiment of the present application;

[0071] FIG14 is a schematic diagram of another notification message update provided in an embodiment of the present application;

[0072] FIG15 is a flow chart of a notification message display method provided in an embodiment of the present application;

[0073] FIG16 is a schematic diagram of another notification message interface provided in an embodiment of the present application;

[0074] FIG17A is a schematic diagram of another notification message interface provided in an embodiment of the present application;

[0075] FIG17B is a schematic diagram of another notification message interface provided in an embodiment of the present application;

[0076] FIG18 is a flow chart of another method for displaying notification messages according to an embodiment of the present application;

[0077] FIG19 is a schematic diagram of another notification message interface provided in an embodiment of the present application;

[0078] FIG20 is a schematic diagram of another notification message provided in an embodiment of the present application;

[0079] FIG21 is a schematic diagram of another notification message interface provided in an embodiment of the present application;

[0080] FIG22 is a schematic diagram of another notification message interface provided in an embodiment of the present application;

[0081] FIG23 is a schematic diagram of another notification message update provided in an embodiment of the present application;

[0082] FIG24 is a flow chart of another notification message display method provided in an embodiment of the present application;

[0083] Figure 25 is a flow chart of another notification message display method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0084] The following describes in detail a method for displaying a notification message and an electronic device provided in an embodiment of the present application with reference to the accompanying drawings.

[0085] The terms "including," "having," and any variations thereof mentioned in the description of the embodiments of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to the process, method, product, or apparatus.

[0086] It should be noted that in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being more preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0087] In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more. "And / or" in this document is merely a description of the association relationship between associated objects, indicating that three relationships can exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone.

[0088] Notification is a reminder method for applications to interact with users. As shown in Figure 1, current notification methods include application notification and agent notification.

[0089] Among them, application notifications are notifications sent directly through the notification interface in the application, and the sender of the application notification is the application. Optionally, application notifications can include local notifications and third-party push (PUSH) notifications. Local notifications can be directly triggered and sent by the third-party application end side (such as the terminal where the third-party application is installed) through interaction logic. Third-party PUSH notifications require the third-party application server on the cloud side or other cloud-side servers to interact with the third-party application end side. After the third-party application server on the cloud side or other cloud-side servers trigger the third-party PUSH notification, it is sent by the third-party application.

[0090] Proxy notifications are notifications sent through the channel and interface for the Push client to send notifications, and the sender of the proxy notification is the Push client. Among them, the channel and interface for the proxy to send notifications are provided by the push service (PushKit) of Huawei Mobile Core Services (Huawei Mobile Services Core, HMS Core). After the third-party application is connected to PushKit, the third-party application server on the cloud side sends a notification message to the PUSH server on the cloud side through PUSH. After receiving the notification message, the PUSH server sends the notification message to the Push client on the end side. After that, the Push client proxy sends the notification message. Optionally, the target party of the proxy notification is the application. When the Push client sends the proxy notification, the third-party application does not need to be kept alive.

[0091] In the related art, application notifications or proxy notifications are displayed in a drop-down notification bar. There are many application notifications or proxy notifications in the drop-down notification bar, which are disorganized and difficult for users to quickly find the required notification messages, resulting in a low user experience.

[0092] Taking a mobile phone as an example, as shown in FIG2 (a), the mobile phone can simultaneously display a status bar 101 when displaying applications such as the desktop. The status bar 101 can display time, battery level, signal strength, Bluetooth status, etc.

[0093] If the user is detected to have pulled down the status bar 101, the phone may display a pull-down notification bar 102, as shown in FIG2(b). When there are notification messages from applications in the phone, the phone may display these notification messages in the pull-down notification bar 102. The phone may display the received notification messages one by one in chronological order in the notification bar 102 in the form of notification messages (such as weather messages) or notification message groups (a notification message group may contain multiple notification messages, such as food delivery messages). When there are too many notification messages in the pull-down notification bar 102, the identifiers of the applications that received the earlier notification messages are displayed in the notification management bar 103.

[0094] When a user wants to find a text message notification message or an earlier notification message from a text message contact named Zhang, they need to scroll through the notification bar to find the earlier notification message among the numerous notification messages. This makes it slow for users to find notification messages, resulting in a poor user experience.

[0095] To solve the above problems, an embodiment of the present application proposes a method for displaying notification messages, which can aggregate multiple notification messages of real-time progress in the operating system of an electronic device, and then display the aggregated notification messages. The aggregated real-time progress notification messages can dynamically display the services that the user cares about, and can refresh the business progress in real time, and aggregate and display key notification information. Among them, the real-time progress notification message is a time-based, state-changing notification message, wherein the state change can include a change in progress. The method can also provide a unified real-time progress notification message display template. The method can also classify notification messages according to the type and importance level of the notification message, and notification messages of different categories are displayed in different areas. Important notification messages are placed in a location that is easy for users to view, and unimportant notification messages can be placed in a location that is not easy for users to view, or folded and displayed to reduce interference to users.

[0096] In this way, multiple notification messages can be displayed in order without overwhelming important notification messages. Important notifications and notifications that users are interested in are presented first, improving the user experience.

[0097] In one possible implementation, the embodiment of the present application can be applied to an electronic device, which can implement the above-mentioned method for displaying notification messages. The electronic device can be a personal computer (PC), a mobile phone, a tablet computer (Pad), a laptop computer, a desktop computer, a laptop computer, a computer with a transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), a wearable device, a vehicle-mounted device, and other terminal devices. The embodiment of the present application does not impose any special restrictions on the specific form of the electronic device.

[0098] FIG3 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. The electronic device includes at least one processor 401, a communication circuit 402, a memory 403, and at least one communication interface 404. The memory 403 may also be included in the processor 401.

[0099] The processor 401 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc. In the embodiment of the present application, the processor 401 may aggregate multiple real-time progress notification messages, calibrate the importance of non-real-time progress notification messages, etc.

[0100] The communication link 402 may include a pathway for transmitting information between the aforementioned components.

[0101] Communication interface 404 is used to communicate with other devices. The communication interface can be a module, circuit, bus, interface, transceiver, or other device capable of implementing communication functions, used to communicate with other devices. Optionally, when the communication interface is a transceiver, the transceiver can be a standalone transmitter that can be used to send information to other devices, or a standalone receiver that can be used to receive information from other devices. The transceiver can also be a component that integrates the functions of sending and receiving information. The embodiments of the present application do not limit the specific implementation of the transceiver.

[0102] The memory 403 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The memory may be independent and connected to the processor 401 via the communication line 402. The memory 403 may also be integrated with the processor 401.

[0103] The memory 403 is used to store computer-executable instructions for implementing the solution of the present application, and is controlled by the processor 401. The processor 401 is used to execute the computer-executable instructions stored in the memory 403, thereby implementing the method for displaying notification messages provided in the following embodiments of the present application.

[0104] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, instructions, computer programs or other names, which are not specifically limited in the embodiments of the present application.

[0105] In a specific implementation, as an embodiment, the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 3 .

[0106] In a specific implementation, as an embodiment, an electronic device may include multiple processors, such as processor 401 and processor 405 in FIG3 . Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0107] The above-mentioned electronic device can be a general device or a dedicated device, and the embodiment of the present application does not limit the type of the electronic device.

[0108] It is understood that the structures illustrated in the embodiments of the present application do not constitute specific limitations on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0109] In the embodiments of this application, the electronic device is described as a mobile phone, but this does not constitute a limitation on the form, function, etc. of the electronic device. Referring to Figure 4, a schematic diagram of the structure of a mobile phone provided in the embodiments of this application is shown. The methods in the following embodiments can be implemented in a mobile phone having the aforementioned hardware structure.

[0110] As shown in FIG4 , the mobile phone may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a camera 193, and a display screen 194. Optionally, the mobile phone may also include a mobile communication module 150, etc.

[0111] It should be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the mobile phone. In other embodiments, the mobile phone may include more or fewer components than shown, or some components may be combined or separated, or arranged differently. The components shown in the illustrations may be implemented in hardware, software, or a combination of software and hardware.

[0112] The processor 110 may include one or more processing units. For example, 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). The different processing units may be independent devices or integrated into one or more processors.

[0113] The controller is the nerve center and command center of the mobile phone. It can generate operation control signals based on instruction opcodes and timing signals to complete the control of instruction fetching and execution.

[0114] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or is reusing. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system. In the embodiment of the present application, the processor 401 may aggregate multiple real-time progress notification messages, calibrate the importance of non-real-time progress notification messages, and the like.

[0115] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (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 USB interface, etc.

[0116] The charging management module 140 is configured to receive charging input from a charger. While charging the battery 142, the charging management module 140 can also power the mobile phone through the power management module 141. The power management module 141 is configured to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 can also receive input from the battery 142 to power the mobile phone.

[0117] The wireless communication function of the mobile phone can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.

[0118] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in a mobile phone can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0119] When a mobile phone includes a mobile communication module 150, it can provide wireless communication solutions for 2G / 3G / 4G / 5G networks. The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low-noise amplifier (LNA), and other components. The mobile communication module 150 receives electromagnetic waves from the antenna 1, filters and amplifies the received electromagnetic waves, and transmits them to the modem processor for demodulation.

[0120] The modulation and demodulation processor may include a modulator and a demodulator, wherein the modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal.

[0121] The wireless communication module 160 can provide wireless communication solutions for mobile phones, including wireless local area networks (WLAN) (such as Wi-Fi networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), NFC, infrared technology (IR), etc. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module.

[0122] In some embodiments, the mobile phone's antenna 1 is coupled to the mobile communication module 150 , and the antenna 2 is coupled to the wireless communication module 160 , so that the mobile phone can communicate with the network and other devices through wireless communication technology.

[0123] The mobile phone implements display functions through a GPU, display screen 194, and an application processor. The GPU is a microprocessor for image processing that connects the display screen 194 and the application processor. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

[0124] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the mobile phone may include one or N display screens 194, where N is a positive integer greater than 1. In some embodiments of the present application, the display screen 194 of the mobile phone may display interfaces or content as shown in Figures 7-14, 16, 17A, 17B, 19-23, etc.

[0125] The mobile phone can implement the shooting function through the ISP, camera 193, video codec, GPU, display 194 and application processor, etc. In some embodiments, the mobile phone can include 1 or N cameras 193, where N is a positive integer greater than 1.

[0126] The external memory interface 120 can be used to connect an external memory card to expand the storage capacity of the mobile phone. The external memory card communicates with the processor 110 through the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0127] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the mobile phone by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the mobile phone (such as audio data, a call book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0128] The mobile phone can implement audio functions such as music playback and recording through the audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0129] As shown in FIG5 , it is a system architecture diagram of an embodiment of the present application, which includes a cloud architecture and a software structure diagram of a mobile phone.

[0130] Optionally, the cloud includes a PUSH server, an application market server, a third-party application server, and other application servers.

[0131] Among them, the third-party application server can be the provider of the notification message, and can be connected to the PUSH server to achieve interaction and notification message display with the third-party application.

[0132] The PUSH server is the service provider of notification messages. It interacts with the PUSH client, can send proxy notification messages, and provides a classification engine for notification message classification and a recommendation engine for aggregated recommendations of notifications.

[0133] Optionally, in the software structure diagram of the mobile phone, the layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In the embodiment of the present application, the system can be divided into three layers, namely, the application layer, the application framework layer, and the local service layer from top to bottom. It should be understood that this article uses the illustrated system as an example to illustrate that in other electronic devices, as long as the functions implemented by each functional module are similar to those in the embodiment of the present application, the solution of the present application can also be implemented.

[0134] Optionally, the application layer may include basic applications, cloud server applications, system pre-installed applications, third-party applications, etc.

[0135] Optionally, the basic application may include a system user interface notification component (component), a desktop component, a mobile phone manager component, a lock screen component, an always on display (AOD) component, and the like.

[0136] Among them, the SystemUI notification component includes multiple modules such as notification module, navigation bar, volume panel, status bar, etc., which can provide users with reminders and displays of notification messages.

[0137] Optionally, for important notification messages, the SystemUI notification component can provide multiple reminder methods such as desktop pop-up reminders, ringtone reminders, and vibration reminders.

[0138] Optionally, the SystemUI notification component can display different notification messages in the notification bar according to the category and importance of the notification messages, and provide notification interaction and notification management functions.

[0139] Optionally, the desktop component includes modules such as icons and notification badges. The mobile manager component includes modules such as permission management and notification switch management. Optionally, users can set application permissions and whether to enable notifications for applications in the mobile manager component. The lock screen component includes modules such as lock screen unlock and lock screen notifications. The lock screen display component includes modules such as lock screen display and off-screen notifications. Optionally, users can set whether notification messages are displayed on the lock screen and whether to turn off-screen notifications.

[0140] Optionally, the cloud server application includes a PUSH client component, an application market component, a music component, etc.

[0141] The PUSH client component can act as a proxy for sending notifications from third-party applications and is the sender of notification messages. Specifically, the PUSH client component can receive notification messages from third-party applications from the PUSH server in the cloud and push the notification messages to the mobile phone notification bar for display. The third-party application is the business party of the notification message. The third-party application interacts with the third-party application server in the cloud, and the third-party application server can provide the display and interaction methods of the notification message content on the mobile phone. At the same time, the third-party application also supports the local sending of notification messages.

[0142] Optionally, the application market component includes modules such as application management and permission manager. The music component includes modules such as music playback and notification service.

[0143] Optionally, the system pre-installed applications may include a call component, a Bluetooth transmission component, and other components.

[0144] The call component can include modules such as audio and video calls, notification services, etc. The Bluetooth transmission component can include modules such as Bluetooth transmission, notification services, etc. Other application components can include modules such as user interface and notification services.

[0145] Optionally, third-party applications may include important information applications, navigation applications, social applications, food delivery applications, and other applications.

[0146] Important information applications may include modules such as important information and notification services. For example, such applications may be banking applications. Navigation applications may include modules such as navigation services and notification services. Social applications may include modules such as user interfaces and notification services. Food delivery applications may include modules such as user interfaces and notification services. Other applications may also include modules such as user interfaces and notification services.

[0147] Optionally, the application framework layer may include an activity manager service (AMS), a window manager service (WMS), a package manager service (PMS), a control (UIKit), a view manager (View), an input manager (Input Manager), a lock screen manager (Kayguard Manager), a lock screen control (Kayguard Controller), a notification manager (Notification Manager), a notification service (Notification Service), etc.

[0148] The application framework layer provides framework capabilities for application execution and interaction, while the notification manager interacts with SystemUI notifications to manage system notification information.

[0149] Optionally, the native server layer may include modules such as input distribution, cryptographic services, surface rendering, multimedia services, and audio rendering.

[0150] It should be understood that the applications or modules included in the above-mentioned layers are only examples, and each layer may also include other applications or modules, and the embodiments of the present application do not impose specific limitations on this.

[0151] In one embodiment, the embodiment of the present application may not include a cloud server, and the notification message is sent and received locally and displayed.

[0152] As follows, a method for displaying a real-time progress notification message in an embodiment of the present application is introduced by taking an example of a third-party application sending a local notification message to the operating system of a mobile phone.

[0153] Optionally, the real-time progress notification message refers to a notification message that is time-based and has state changes, wherein the state change may include a change in progress. For example, a call notification message in progress, a countdown notification message in progress, a recording notification message in progress, a screen recording notification message in progress, a Bluetooth transmission notification message, a takeaway notification message in progress, a taxi-hailing notification message in progress, a navigation notification message in progress, a music playback notification message in progress, etc. Optionally, the real-time progress notification message may also be other time-based and state-changing notification messages, wherein the state change may include a change in progress, and the embodiments of the present application do not impose specific restrictions on this.

[0154] In one embodiment, the notification message sent by the third-party application to the operating system carries an extended parameter, and the extended parameter may indicate whether the notification message is a real-time progress notification message.

[0155] Notification#extras of a standard notification is additional data of the notification message. It supports notification messages to carry extended parameters and can add additional information or parameters to the notification message.

[0156] Optionally, a third-party application may add a notification message category identifier to the extended parameter of Notification#extras to distinguish real-time progress notification messages and display the real-time progress notification messages in an aggregated manner.

[0157] For example, when a third-party application can set the extended parameter of the extended field 0 in the notification message to true (true), it indicates that the notification message is a real-time progress notification message; when the extended parameter of the extended field 0 in the notification message is false (false), it indicates that the notification message is not a real-time progress notification message.

[0158] In this way, after receiving a notification message from a third-party application, if the operating system identifies the extended parameter in the notification message as true, it determines that the notification message is a real-time progress notification message and displays the notification message using the real-time progress notification message template. If the extended parameter in the notification message is false, it determines that the notification message is not a real-time progress notification message and displays the notification message normally.

[0159] Optionally, embodiments of the present application may further set an extended parameter in the notification message to other conditions to indicate whether the notification message is a real-time progress notification message. For example, a third-party application may set the extended parameter in the notification message to false to indicate that the notification message is a real-time progress notification message; or set the extended parameter in the notification message to true to indicate that the notification message is not a real-time progress notification message. Embodiments of the present application do not impose specific limitations on this.

[0160] Optionally, the extended parameters and their interface information may be reflected in the specification of display template parameters of the real-time progress notification message.

[0161] Optionally, the extended parameters and interfaces may only be agreed upon between the third-party application and the operating system, and no software development kit (SDK) interface and definition may be provided to the outside world.

[0162] For example, embodiments of the present application can include extended parameters and their interfaces in the parameter specification of the real-time progress notification message display template. Third-party applications can use the extended parameters and their interfaces specified in this specification to interact with the operating system. The operating system can then parse and process the received extended parameters to determine whether a notification message carrying the extended parameters is a real-time progress notification message.

[0163] In one embodiment, if the notification message received by the operating system is a real-time progress notification message, the real-time progress notification message is displayed using a unified real-time progress notification message display template.

[0164] Optionally, a real-time progress notification message display template may be as shown in FIG6 . The real-time progress notification message display template 601 may include an icon area 602, a primary information area 603, a secondary information area 604, an auxiliary area 605, and an extended area 606. The icon area 602, the primary information area 603, and the secondary information area 604 are mandatory areas, while the auxiliary area 605 and the extended area 606 are optional areas.

[0165] Optionally, the icon area 602 can display an application icon of a third-party application (which can also be a system preset application or other application), or a business icon, or an overlay icon of an application icon and a business icon; the main information area 603 can display the main information of the real-time progress notification message in text form, such as the notification message title, the time of real-time progress, etc.; the secondary information area 604 can display the secondary information of the real-time progress notification message in text form, supporting multi-field rich text to highlight the key information of the notification message; the auxiliary area 605 can display operation controls (such as a mute control or hang-up control for a call) or the progress of a business (such as a file transfer progress), etc., and supports the expansion of a combined view of multiple controls. The embodiment of the present application can provide a standard control implementation for use by third-party applications; the extended area 606 can display extended information of the real-time progress notification message, such as progress visualization (such as a progress bar, progress nodes), detailed operations (such as music playback control), detailed information supplement (such as navigation multi-lane), etc.

[0166] In one embodiment, the real-time progress notification message templates can be further classified according to the type of real-time progress message. Specifically, as shown in Table 1:

[0167] Table 1

[0168] Optionally, real-time progress notification message templates can be further divided into system operation templates, system progress templates, important information reminder templates, rich media progress display templates, and rich media detailed display templates. Each template includes an icon area, a main information area, and a secondary information area, where the main information area and the secondary information area can display rich text.

[0169] Optionally, the system operation template includes an icon area, a primary information area, a secondary information area, and an auxiliary area, but does not include an extended area. The auxiliary area may include some operation controls. Optionally, the auxiliary area generally includes 1-3 operation controls. Of course, the auxiliary area may also include more operation controls, and this embodiment of the application does not impose specific limitations on this.

[0170] Optionally, system operation templates can be applied to scenarios such as call notification messages, timer notification messages, recording notification messages, and screen recording notification messages.

[0171] For example, as shown in FIG7( a ), it is a schematic diagram of a call notification message 701 before using the real-time progress notification message template and a call notification message 702 after using the real-time progress notification message template.

[0172] Among them, the call notification message 702 includes an icon area 703, which includes the avatar image of the contact Xiao Ming and the icon of the call application; the main information area 704 is the call time "13:12"; the sub-information area 705 is the contact "Xiao Ming" of the call; the auxiliary area 706 includes call operation controls: mute control, hands-free control and hang up control.

[0173] As another example, as shown in FIG7( b ), it is a schematic diagram of a timer notification message 711 before using the real-time progress notification message template and a timer notification message 712 after using the real-time progress notification message template.

[0174] Among them, the timer notification message 712 includes an icon area 713, which includes the icon of the timer application; the main information area 714 is the timing time "17:37"; the sub-information area 715 is the countdown indication "Countdown"; the auxiliary area 716 includes timing operation controls: timing off control, and timing pause control.

[0175] As another example, as shown in FIG7( c ), it is a schematic diagram of a recording notification message 721 before using the real-time progress notification message template and a recording notification message 722 after using the real-time progress notification message template.

[0176] Among them, the recording notification message 722 includes an icon area 723, which includes the icon of the recording application; the main information area 724 is the recording time "00:07"; the sub-information area 725 is the recording indication "recording"; the auxiliary area 726 includes recording operation controls: recording off control.

[0177] As another example, as shown in (d) of FIG7 , it is a schematic diagram of a screen recording notification message 731 before using the real-time progress notification message template and a screen recording notification message 732 after using the real-time progress notification message template.

[0178] Among them, the screen recording notification message 732 includes an icon area 733, and the icon area 733 includes the icon of the screen recording application; the main information area 734 is the screen recording time "00:09"; the sub-information area 735 is the screen recording indication "recording"; the auxiliary area 736 includes the screen recording operation controls: the screen recording close control.

[0179] Optionally, the system operation template can also be applied to other message display scenarios, and the embodiments of the present application do not impose specific limitations.

[0180] In some embodiments, the system operation template may also include an extension area, such as adding an extension area to a call notification message to display the contact's historical call records, etc. This embodiment of the present application does not impose any specific restrictions on this.

[0181] Optionally, the system progress template includes an icon area, a main information area, a secondary information area, and an auxiliary area, but does not include an extension area. The auxiliary area can be a progress display control.

[0182] Optionally, the system progress template can be applied to scenarios such as Bluetooth transmission notification messages and step counting notification messages in sports health.

[0183] For example, as shown in FIG8( a ), it is a schematic diagram of a Bluetooth transmission notification message 801 before using the real-time progress notification message template and a Bluetooth transmission notification message 802 after using the real-time progress notification message template.

[0184] Among them, the Bluetooth transmission notification message 802 includes an icon area 803, which includes a Bluetooth icon; the main information area 804 is the Bluetooth transmission progress "35% received"; the sub-information area 805 is the content of the Bluetooth transmission "File 1"; the auxiliary area 806 includes a Bluetooth transmission progress display control: a Bluetooth transmission progress bar, which can be circular.

[0185] As another example, as shown in FIG8( b ), it is a schematic diagram of a sports health notification message 811 before using the real-time progress notification message template and a sports health notification message 812 after using the real-time progress notification message template.

[0186] Among them, the sports health notification message 812 includes an icon area 813, which includes the icon of the sports health application; the main information area 814 is the number of steps and energy consumed by the user in sports health "9204 steps | 302 kcal"; the sub-information area 815 is the sports health indication "sports health"; the auxiliary area 816 includes a step progress display control in sports health: a step progress bar, which can be the ratio of the user's actual steps to the preset steps.

[0187] Optionally, the system progress template can also be applied to other message display scenarios, and the embodiment of the present application does not impose any specific limitations.

[0188] In some embodiments, the system progress template may also include an extension area, such as adding an extension area to a Bluetooth transmission notification message to display a history of Bluetooth transmissions, etc. This embodiment of the present application does not impose any specific restrictions on this.

[0189] Optionally, the important information reminder template may include an icon area, a main information area, and a sub-information area, but not an auxiliary area and an extended area.

[0190] Optionally, the important information reminder template can be applied to scenarios such as high-speed rail (or train, flight, etc.) notification messages and navigation notification messages.

[0191] For example, as shown in FIG9( a ), it is a schematic diagram of a high-speed rail notification message 901 before using the real-time progress notification message template and a high-speed rail notification message 902 after using the real-time progress notification message template.

[0192] Specifically, high-speed rail notification message 902 includes an icon area 903, which includes an icon for a high-speed rail application; a primary information area 904 displays the high-speed rail destination, train, and departure time (e.g., "A station xxx train is leaving at 20:35"); and a secondary information area 905 displays the ticket gate and seat number for this high-speed rail trip (e.g., "Gate: 6B, Seat: Car 03, 12F."). Optionally, primary information area 904 and secondary information area 905 may also include other content, such as the departure location and arrival time. This embodiment of the present application does not impose specific limitations on this.

[0193] As another example, as shown in FIG9( b ), it is a schematic diagram of a navigation notification message 911 before using the real-time progress notification message template and a navigation notification message 912 after using the real-time progress notification message template.

[0194] Among them, the navigation notification message 912 includes an icon area 913, and the icon area 913 includes a right-turn icon for the real-time navigation service. Exemplarily, the icons for the real-time navigation service may include a "left-turn icon", a "straight-forward icon", and a "right-turn icon". When the navigation application instructs to turn left, the icon area 913 displays a "left-turn icon". When the navigation application instructs to go straight, the icon area 913 displays a "straight-forward icon". When the navigation application instructs to turn right, the icon area 913 displays a "right-turn icon". The main information area 914 is the real-time navigation information "Turn right after 118 meters". The sub-information area 915 is the real-time navigation result "Go to xx Road", that is, turn right after 118 meters and enter xx Road. Optionally, the main information area 904 and the sub-information area 905 may also include other content. For example, the main information area 904 may also include the current road name, and the sub-information area 905 may also include the navigation destination, etc. This embodiment of the application does not impose specific restrictions on this.

[0195] In some embodiments, the important information reminder template may also include an auxiliary area and an extended area, such as adding an extended area to a high-speed rail notification message to display the stations that the high-speed rail train passes through, etc. This embodiment of the application does not impose specific limitations on this.

[0196] Optionally, the rich media progress display template includes an icon area, a main information area, a secondary information area, and an extended area, but does not include an auxiliary area. The extended area can be a progress visualization control for some services.

[0197] Optionally, the rich media progress display template can be applied to scenarios such as takeaway notification messages and taxi notification messages.

[0198] For example, as shown in (a) of FIG10 , it is a schematic diagram of a takeaway notification message 1001 before using the real-time progress notification message template and a takeaway notification message 1002 after using the real-time progress notification message template.

[0199] Among them, the takeaway notification message 1002 includes an icon area 1003, which includes the icon of the takeaway application; the main information area 1004 is the current progress of the takeaway "the rider has accepted the order"; the secondary information area 1005 is the rider's current specific progress "300 meters away from the merchant, delivered at 12:50"; the extended area 1006 includes a takeaway progress visualization control: including three progress points: rider accepting the order, rider picking up the food, and delivered. The current rider is between the rider order acceptance progress point and the rider pick up the food progress point.

[0200] Optionally, the takeaway extension area 1006 may also include other controls, such as progress point controls such as the merchant is preparing food and the merchant has completed food preparation. This embodiment of the present application does not impose specific restrictions on this.

[0201] Exemplarily, as shown in (b) of FIG. 10, it is a schematic diagram of the taxi-hailing notification message 1011 before using the real-time progress notification message template and the taxi-hailing notification message 1012 after using the real-time progress notification message template.

[0202] Among them, the taxi-hailing notification message 1012 includes an icon area 1013, and the icon area 1013 includes the icon of the taxi-hailing application; the main information area 1014 is the current progress of the taxi-hailing "the driver is about to arrive"; the secondary information area 1015 is the vehicle information "White, license plate number: Shanghai A P8xx"; the expansion area 1016 includes a taxi-hailing progress visualization control: including the user's current location, the driver's current location, and the route between the driver and the user.

[0203] Optionally, the expansion area 1016 of the taxi-hailing may further include other controls, such as controls for the distance between the driver and the user, etc. The embodiments of the present application do not make specific limitations thereto.

[0204] In some embodiments, the rich media progress display template may also include an auxiliary area. For example, an auxiliary area is added to the food delivery notification message to display the rider's contact information; an auxiliary area is added to the taxi-hailing notification message to display the driver's contact information, etc. The embodiments of the present application do not make specific limitations thereto.

[0205] Optionally, the rich media detailed display template includes an icon area, a main information area, a secondary information area, and an expansion area, and does not include an auxiliary area. Among them, the expansion area may be detailed information controls for some services.

[0206] Optionally, the rich media detailed display template can be applied to scenarios such as multi-lane navigation notification messages, music playback notification messages, etc.

[0207] Exemplarily, as shown in (a) of FIG. 11, it is a schematic diagram of the multi-lane navigation notification message 1101 before using the real-time progress notification message template and the multi-lane navigation notification message 1102 after using the real-time progress notification message template.

[0208] Among them, the multi-lane navigation notification message 1102 includes an icon area 1103, and the icon area 1103 includes a right-turn icon for the multi-lane navigation service. Exemplarily, the icons of the real-time navigation service may include "left-turn icon", "straight-ahead icon", "right-turn icon", etc.; the main information area 1104 is the real-time multi-lane navigation information "turn right after 118 meters"; the secondary information area 1105 is the real-time multi-lane navigation result "going to xx Road", that is, turn right after 118 meters and enter xx Road; the expansion area 1106 includes detailed information controls for the multi-lane navigation service: left-turn control, straight-ahead control, right-turn control. Among them, the current navigation information of the multi-lane navigation service is "turn right after 118 meters", and the right-turn control in the expansion area 1106 can be displayed in another color, such as black.

[0209] As another example, as shown in FIG11( b ), it is a schematic diagram of a music playing notification message 1111 before using the real-time progress notification message template and a music playing notification message 1112 after using the real-time progress notification message template.

[0210] Music playback notification message 1112 includes an icon area 1113, which includes the song cover image and the music application icon. Optionally, icon area 1113 may also include the song album cover image or the artist's portrait. Primary information area 1114 displays the artist's name, "Xiao Hong." Secondary information area 1115 displays the song title, "Song A." Extended area 1116 includes detailed music playback service controls: controls for "My Favorite Music," "Play Previous Song," "Play Music," "Play Next Song," and "Display Lyrics."

[0211] In some embodiments, the rich media detailed display template may also include an auxiliary area, such as adding an auxiliary area to a multi-lane navigation notification message to display a navigation voice prompt, etc. The embodiments of the present application do not impose specific restrictions on this.

[0212] In some embodiments, the real-time progress notification message can be displayed in the notification bar interface or in the lock screen interface. Taking the takeaway notification message as an example, as shown in (a) of Figure 12, a schematic diagram of the takeaway notification message being displayed in the notification bar interface 1201 is shown, and as shown in (b) of Figure 12, a schematic diagram of the takeaway notification message being displayed in the lock screen interface 1202 is shown. The lock screen interface can refer to the interface in the off-screen state, or it can be the interface displayed when the phone is awakened from the off-screen state. For example, if the phone is currently off, the user double-clicks the phone screen, the phone lights up, and displays the real-time progress notification message.

[0213] In one embodiment, the real-time progress notification message template can be a basic style framework as shown in Figure 6, which is then expanded into various sub-modules. In the sub-modules, each area of ​​the template is designed according to the actual needs of the notification message. The sub-modules are then checked and combined according to the designed style.

[0214] Optionally, the real-time progress notification message template may uniformly specify parameters such as the size, quantity, position arrangement, and corresponding operations of icons in the notification message.

[0215] Optionally, a third-party application may fill in parameters such as icons, operation controls, and detailed information according to the style set in the real-time progress notification message template.

[0216] Optionally, the icon area may include application icons and / or service icons. An extended field 1 may be set in the real-time progress notification message template to indicate whether the icon area is a composite icon of application icons and service icons.

[0217] Optionally, the service icon is used to represent an icon related to the service running in the application. For example, the service icon includes a contact avatar icon in a call notification message in a call application, a music cover icon in a music playback notification message, or a direction icon in a navigation application.

[0218] Optionally, when the operating system receives a real-time progress notification message with extension field 1 set to true, the icon area for the real-time progress notification message is a composite icon. The operating system can overlay the application icon and the service icon into a composite icon and fill the icon area. If extension field 1 is false, the icon area is an application icon or a service icon. The operating system can then display the corresponding application icon or service icon in the icon area.

[0219] Optionally, for scenarios involving contacts (such as call application scenarios and social application scenarios), if extended field 1 is true, the contact icon (avatar) and the application icon are superimposed and filled in the icon area. For example, in the call notification message 702 shown in Figure 7(a), the icon area includes the contact avatar and the call application icon. The contact avatar is a large icon, and the call application icon is a small icon (smallIcon).

[0220] Optionally, for other service scenarios (such as music playback), if the extended field 1 is true, the service icon and the application icon are superimposed and filled in the icon area. For example, in the call notification message 1112 shown in Figure 11 (b), the icon area includes a music cover icon and a music application icon. The music cover icon is a large icon, and the music application icon is a small icon.

[0221] Optionally, the main information area and the sub-information area need to support rich text (bold, italic, color and other formats). Third-party applications can use SpannableString to pass tags carrying rich text information to the text of the notification message, and set the text of the notification message to bold, italic, color, etc. After that, the operating system can parse the tag and display the rich text. For example, as shown in (a) of Figure 7, the main information area 704 "13:12" is bold text. For another example, as shown in (b) of Figure 11, the sub-information area 1115 "Song A" is bold text.

[0222] Optionally, the auxiliary area is an optional area. Extension Field 2 can be set in the real-time progress notification message template to indicate whether the real-time progress notification message includes the auxiliary area. For example, if Extension Field 2 is true, the real-time progress notification message includes the auxiliary area; if Extension Field 2 is false, the real-time progress notification message does not include the auxiliary area.

[0223] Optionally, the extension area is also optional. Extension Field 3 can be set in the real-time progress notification message template to indicate whether the real-time progress notification message includes the extension area. For example, if Extension Field 3 is true, the real-time progress notification message includes the extension area; if Extension Field 3 is false, the real-time progress notification message does not include the extension area.

[0224] Optionally, a viewstub can be attached to the bottom of the root layout for the operating system's real-time progress notifications. This is hidden by default. To display the extended area, replace the viewstub with the extended area layout view. Alternatively, to display a control in the extended area, unhide the control view.

[0225] The real-time progress notification message template specifies the width and maximum height of the extension area. Third-party applications need to fill in the extension area parameters according to the regulations.

[0226] Optionally, the extended area can display rich media content. As shown in FIG11( b ), the extended area 1116 includes various song-related controls.

[0227] Optionally, for an extension area view with a relatively fixed structure, a strong format and a local view may be used for display. As shown in FIG11( b ), the controls included in the extension area 1116 are fixed-format music playback service controls.

[0228] For complex extension area views, you can use remote views. However, the real-time progress notification messages of remote views need to be limited in scope and restricted. Remote views prioritize using views with standard scopes.

[0229] For example, if the music player notifies the user to display a music video (MV) of song A in the extended area, a remote view may be used to display the MV.

[0230] The real-time progress notification message template specifies the width and maximum height of the extension area. Third-party applications need to fill in the extension area parameters according to the regulations.

[0231] In one embodiment, the real-time progress notification message may be updated.

[0232] Optionally, the user can trigger the update of the real-time progress notification message. For example, for a music playback notification message, the user can click the "play next music control" of the music playback notification message to update the music playback service.

[0233] Optionally, for the same third-party application service, the third-party application can send new real-time progress notification message parameters to the operating system. The real-time progress notification message parameters carry the notification message content of the status update, use the channel and importance level of the original real-time progress notification message, and specify the notification ID of the original real-time progress notification message.

[0234] After receiving a new real-time progress notification message, the operating system can identify the notification identifier and confirm that the real-time progress notification message is an existing notification message. When displaying it in the notification bar, the operating system updates the content of the original real-time progress notification message based on the new real-time progress notification message.

[0235] For example, as shown in (a) of FIG13 , which is the original real-time progress notification message 902 of the high-speed rail notification message, the main information area 904 can remind the user that the xxx train bound for place A will depart at 20:35. When ticket checking is required for this high-speed rail train, the high-speed rail application needs to send a new real-time progress notification message to remind the user to check the ticket. For example, as shown in (b) of FIG13 , which is a new real-time progress notification message 902', the notification message 902' is updated based on the notification message 902. Among them, the icon area and the sub-information area in the notification message 902' are consistent with the icon area and the sub-information area in the notification message 902, and only the main information area 904' indicating the real-time progress of the high-speed rail is updated to "xxx train ticket checking reminder".

[0236] As another example, as shown in (a) of Figure 14, it is the original real-time progress notification message 1002 of the takeaway notification message. The main information area 1004 can display the real-time progress of the takeaway as "the rider has accepted the order". The extended area 1006 can visualize the progress of the takeaway, wherein the rider is located between the rider's order acceptance progress point and the rider's meal pickup progress point. After the rider picks up the takeaway, the takeaway application can send a new real-time progress notification to prompt the user of the current progress of the takeaway. For example, as shown in (b) of Figure 14, it is a new real-time progress notification message 1002', and the notification message 1002' is updated based on the notification message 1002. Among them, the icon area in the notification message 1002' is consistent with the icon area in the notification message 1002, indicating that the main information area 1004', the secondary information area 1005' and the extended area 1006' of the real-time progress of the high-speed rail are updated.

[0237] Among them, the main information area 1004' is the latest progress of the takeaway "the rider has picked up the food"; the secondary information area 1005' is the rider's latest specific progress "500 meters away from the user, delivered at 12:50"; in the extended area 1006', the rider is located between the rider's food pickup progress point and the delivery progress point.

[0238] In one embodiment, the real-time progress notification message may be subjected to lifecycle management. Specifically, when the task is completed, the real-time progress notification message may end.

[0239] Optionally, the termination mode of the real-time progress notification message can be divided into active termination and passive termination according to different triggering parties.

[0240] Optionally, a third-party application can trigger an active termination and remove the real-time progress notification message.

[0241] Optionally, the third-party application can send a new real-time progress notification message to the operating system. This new real-time progress notification message uses the same notification channel, severity level, and notification ID as the original real-time progress notification message, and carries an end command in its extended information. Upon receiving the end notification indication, the operating system terminates the real-time progress notification message after a preset duration has expired.

[0242] For example, when a takeout order is delivered, the food delivery application can send a new real-time progress notification message to the operating system to indicate that the food has been delivered. The extended information of this new real-time progress notification message can include an end command. After receiving the end notification instruction, the operating system will proactively end the food delivery notification message after more than 10 seconds.

[0243] The operating system can trigger a passive end, removing the real-time progress notification message.

[0244] Optionally, the operating system can set a preset time for real-time progress notification messages for each service and record the creation time and last refresh time of each service's real-time progress notification message. If the difference between the creation time and the last refresh time of a service's real-time progress notification message is greater than the preset time, it indicates that the real-time progress notification message for that service may be erroneous and the operating system needs to remove the real-time progress notification message for that service. Each service may include multiple real-time progress notification messages, and these multiple real-time progress notification messages may have the same notification ID.

[0245] Among them, the preset time of the real-time progress notification message of each business can be set according to the historical record of the real-time progress notification message or according to the developer's experience, and the embodiment of the present application does not impose any specific limitation on this.

[0246] For example, the takeout notification message is generally displayed for 30 to 120 minutes. The preset time for the takeout notification message can be 240 minutes. If the difference between the creation time and the last refresh time of the takeout notification message exceeds 240 minutes, the takeout notification message may be erroneous and the operating system needs to remove the takeout notification message.

[0247] In some embodiments, as shown in FIG15 , a flowchart of creating, updating, interacting, switching, and removing real-time progress notification messages in an embodiment of the present application is provided. The notification service module supports extended templates for real-time progress notification messages (e.g., adding extended parameters based on the real-time progress notification message template). The notification service module, notification control module, notification display module, and lock screen display module are located in the operating system. Specifically, the following steps are included:

[0248] S101. The notification service module sends a real-time progress notification message template development guide to a third-party application.

[0249] Optionally, the third-party application may pre-agreed with the notification service module to use a real-time progress notification message template to display the real-time progress notification message.

[0250] Optionally, the notification service module can send the real-time progress notification message template development guide to the third-party application. Among them, the real-time progress notification message template development guide contains the filling rules for the real-time progress notification message template parameters. For example, it is stipulated that the real-time progress notification message needs to indicate through extended parameters that the notification message is a real-time progress notification message. For another example, it is stipulated that the third-party application needs to fill in the icon area parameters, main information area parameters and sub-information area parameters, and can fill in the extended area parameters and auxiliary area parameters as needed. The third-party application can indicate through extended parameters whether the icon area is a composite icon, and / or the rich text information in the main information area and the sub-information area, and / or whether the real-time progress notification message includes an extended area or an auxiliary area, etc.

[0251] S1501: A user triggers a real-time progress service of a third-party application.

[0252] For example, taking the third-party application as a food delivery application, a user can place an order and pay for the food delivery order in the food delivery application to trigger the real-time progress of the food delivery service.

[0253] S1502: The third-party application generates a first real-time progress notification message parameter.

[0254] After the third-party application starts the real-time progress service, it will generate a first real-time progress notification message parameter to notify the user that the real-time progress service has started.

[0255] Optionally, the first real-time progress notification message parameters may include application or service icon parameters, main information parameters of the notification message, and secondary information parameters of the notification message. The first real-time progress notification message parameters may also include operation control parameters, notification detailed information parameters, etc. according to the needs of specific applications.

[0256] The first real-time progress notification message parameter may carry an extended parameter.

[0257] Exemplarily, when the extension parameter in the extension field 0 carried in the first real-time progress notification message parameter is true, it indicates that the notification message is a real-time progress notification message;

[0258] As another example, the extended parameter in the extended field 1 carried in the first real-time progress notification message parameter is true, indicating that the icon area of ​​the notification message is a composite icon.

[0259] S1503: The third-party application sends the first real-time progress notification message parameter to the notification service module.

[0260] S1504: The notification service module creates a first real-time progress notification message according to the first real-time progress notification message parameters, and sends the message to the notification control module.

[0261] Optionally, the notification service module is located in the application framework layer of the operating system, that is, after the operating system receives the first real-time progress notification message parameters from the third-party application, it creates the first real-time progress notification message in the operating system.

[0262] Exemplarily, if the extended field 0 in the real-time progress service notification message parameter is true, the notification message is a real-time progress notification message. The notification service module creates a first real-time progress notification message based on the real-time progress notification message template, and fills the application or service icon, notification main message, notification secondary message, operation control, notification detailed information parameters and other contents in the real-time progress service notification message into the real-time progress notification message template.

[0263] Optionally, the notification service module may receive first real-time progress notification message parameters from multiple third-party applications, and then create multiple corresponding first real-time progress notification messages.

[0264] S1505: The notification control module receives the first real-time progress notification message and triggers the notification display module to display the first real-time progress notification message.

[0265] Optionally, the notification display module may be a notification center or a notification bar in the SystemUI notification component. This embodiment of the present application does not impose any specific restrictions on this.

[0266] S1506: The notification display module displays a first real-time progress notification message.

[0267] Exemplarily, the notification display module may display the first real-time progress notification message as shown in FIG. 7 to FIG. 11 in the notification bar.

[0268] In one embodiment, the first real-time progress notification message may also be displayed in a pop-up window on the mobile phone desktop, on the lock screen interface, etc.

[0269] S1511. The user triggers the lock screen display module to enter the lock screen interface.

[0270] For example, the user can click the lock screen button of the mobile phone to trigger the lock screen.

[0271] S1512. The lock screen display module sends a lock screen notification to the notification control module.

[0272] S1513: The notification control module triggers the lock screen to display the first real-time progress notification message.

[0273] Optionally, after receiving the lock screen notification from the lock screen display module, the notification control module triggers the lock screen display module to display the first real-time progress notification message on the lock screen.

[0274] S1514. The lock screen display module displays the first real-time progress notification message on the lock screen.

[0275] Exemplarily, as shown in (b) of FIG12 , the lock screen display module may display a takeaway notification message on the lock screen interface.

[0276] In one embodiment, when the service status of the third-party application changes, the real-time progress notification message may be updated.

[0277] Among them, the real-time progress update service can be triggered by the user or by a third-party application, and the embodiment of the present application does not impose any specific restrictions on this.

[0278] S1521. The user triggers the update of the real-time progress service.

[0279] For example, for a music playing notification message, the user may click on a “play next music control” in the music playing notification message to update the music playing service.

[0280] or,

[0281] S1521', a third-party application triggers an update of the real-time progress service.

[0282] For example, for a takeaway notification message, as shown in FIG14 , after the rider picks up the meal, the takeaway application can trigger an update of the real-time progress message of the takeaway.

[0283] S1522: The third-party application generates a second real-time progress notification message parameter.

[0284] Optionally, when the real-time progress service is updated, the third-party application generates a second real-time progress notification message parameter to notify the user that the real-time progress service has been updated.

[0285] In one embodiment, the second real-time progress notification message parameters may include application or service icon parameters, primary information parameters of the notification message, and secondary information parameters of the notification message. The second real-time progress notification message parameters may also include operation control parameters, detailed notification information parameters, and the like, depending on the needs of the specific application.

[0286] The parameters corresponding to the updated content are changed compared to the parameters of the first real-time progress notification message. For example, as shown in Figure 14, for a takeout notification message, when the takeout progress changes, the parameters of the second takeout notification message, such as the primary information parameter, secondary information parameter, and detailed information parameter of the notification, are also changed.

[0287] In a possible embodiment, the second real-time progress notification message parameters also include the historical parameters in the first real-time progress notification message parameters.

[0288] Optionally, the history parameter may be a detailed information parameter of the notification message in the second real-time progress notification message parameter and the first real-time progress notification message parameter.

[0289] Exemplarily, the second takeaway notification message parameters also include detailed information parameters of the notification message in the first takeaway notification message parameters, etc.

[0290] Optionally, the second real-time progress notification message parameter may also carry an extended parameter.

[0291] In another embodiment, the second real-time progress notification message parameter may carry a mask parameter, and the mask parameter may indicate some parameters of the area that needs to be updated in the first real-time progress notification message.

[0292] For example, it is shown in Table 2 below:

[0293] Table 2

[0294] Among them, when the icon area of ​​the first real-time progress notification message needs to be updated, the mask bit carried in the second real-time progress notification message parameter is 0x01; when the main information area of ​​the first real-time progress notification message needs to be updated, the mask bit carried in the second real-time progress notification message parameter is 0x02; when the secondary information area of ​​the first real-time progress notification message needs to be updated, the mask bit carried in the second real-time progress notification message parameter is 0x04; when the auxiliary area of ​​the first real-time progress notification message needs to be updated, the mask bit carried in the second real-time progress notification message parameter is 0x08; when the extended area of ​​the first real-time progress notification message needs to be updated, the mask bit carried in the second real-time progress notification message parameter is 0x10.

[0295] Optionally, when multiple areas of the first real-time progress notification message need to be updated, the second real-time progress notification message parameter may carry multiple mask bits.

[0296] Exemplarily, when the icon area and the main information area of ​​the first real-time progress notification message need to be updated, the mask bit 1 carried in the second real-time progress notification message parameter is 0x01, and the mask bit 2 is 0x02;

[0297] Optionally, the second real-time progress notification message parameters may also only include parameters of the update area and corresponding mask bits.

[0298] For example, when the icon area of ​​the first real-time progress notification message needs to be updated, the mask bit carried in the second real-time progress notification message parameter is 0x01, and the second real-time progress notification message parameter only includes parameters related to the icon area. This embodiment of the present application does not impose specific limitations on this.

[0299] S1523: The third-party application sends the second real-time progress notification message parameters to the notification service module.

[0300] S1524: The notification service module updates the first real-time progress notification message according to the second real-time progress notification message parameters, obtains the second real-time progress notification message, and sends it to the notification control module.

[0301] Optionally, the notification service module is located in the application framework layer of the operating system, that is, after the operating system receives the second real-time progress notification message parameters from the third-party application, it updates the first real-time progress notification message, obtains the second real-time progress notification message, and sends it to the notification control module.

[0302] Optionally, the notification service module may update the first real-time progress notification message according to the mask bit carried in the second real-time progress notification message parameter.

[0303] For example, for a takeout notification message, if mask bit 1 in the second takeout notification message parameter is 0x02, mask bit 2 is 0x04, and mask bit 3 is 0x10, then the contents of the primary information area, secondary information area, and extended area in the first takeout notification message need to be updated. The first takeout notification message is updated based on the parameters of the primary information area, secondary information area, and extended area in the second takeout notification message parameter. As shown in Figure 14, the notification service module can update and replace the primary information area 1004', secondary information area 1005', and extended area 1006' in the corresponding positions in the first takeout notification message.

[0304] Optionally, the second real-time progress notification message may further include historical information in the first real-time progress notification message.

[0305] Exemplarily, for a takeout notification message, as shown in FIG14 , the extension area 1006 ′ of the second takeout notification message also includes the historical progress track in the first takeout notification message 1006 .

[0306] In a possible embodiment, the notification service module may create a second real-time progress notification message according to the second real-time progress notification message parameters, and then replace the first real-time progress notification message.

[0307] For example, for a high-speed rail notification message, as shown in FIG13 , the notification service module may create a second high-speed rail notification message 902 ′ based on the second high-speed rail notification message parameters, and then the second high-speed rail notification message 902 ′ replaces the first high-speed rail notification message 902 .

[0308] In a possible embodiment, the second real-time progress notification message parameters may further include historical parameters of the first real-time progress notification message parameters. The notification service module may create a second real-time progress notification message according to the second real-time progress notification message parameters and then replace the first real-time progress notification message.

[0309] For example, for a food delivery notification message, the second food delivery notification message parameters include parameters such as the detailed notification information displayed in extended area 1006, which were included in the first food delivery notification message parameters. As shown in FIG14 , the notification service module can directly create a second food delivery notification message 1002′ based on the second food delivery notification message parameters. Second food delivery notification message 1002′ then replaces first food delivery notification message 1002.

[0310] S1525: The notification control module receives the second real-time progress notification message and triggers the notification display module to display the second real-time progress notification message.

[0311] S1526: The notification display module displays a second real-time progress notification message.

[0312] Exemplarily, the notification display module may display the second high-speed rail notification message 902 ′ as shown in FIG. 13 in the notification bar.

[0313] In one embodiment, the second real-time progress notification message may also be displayed in a pop-up window on the mobile phone desktop, on the lock screen interface, etc.

[0314] S1531. The notification control module triggers the lock to display a second real-time progress notification message.

[0315] Optionally, after receiving the lock screen notification from the lock screen display module, the notification control module triggers the lock screen display module to display the second real-time progress notification message on the lock screen.

[0316] S1532. The lock screen display module displays the second real-time progress notification message on the lock screen.

[0317] Exemplarily, as shown in FIG14 , the lock screen display module may display a second takeaway notification message 1002 ′ on the lock screen interface.

[0318] In one embodiment, the user may interact with real-time progress notification messages.

[0319] S1541. The user clicks on the real-time progress notification message.

[0320] S1542: Notify the control module to respond to the user's click operation.

[0321] S1543. Notify the control module to control the application to jump to the application interface.

[0322] Optionally, the notification control module controls the mobile phone application to jump to the application interface corresponding to the real-time progress notification message.

[0323] In one embodiment, the user can also interact with the real-time progress notification message on the lock screen interface.

[0324] S1551. The user clicks the real-time progress notification message on the lock screen interface.

[0325] S1552: Notify the control module to respond to the user's click operation.

[0326] Optionally, the notification control module responds to a click operation by the user to unlock the phone screen.

[0327] S1553. Notify the control module to control the application to jump to the application interface.

[0328] Optionally, the notification control module controls the mobile phone application to jump to the application interface corresponding to the real-time progress notification message.

[0329] In one embodiment, the real-time progress notification message can be displayed in a switchable manner between the notification bar interface and the lock screen interface.

[0330] Optionally, when the real-time progress notification message is displayed on the notification bar interface, it can be switched to the lock screen interface for display.

[0331] S1561. The user triggers the lock screen display module to enter the lock screen interface.

[0332] Optionally, the user can click the lock screen button of the mobile phone to trigger the lock screen, triggering the lock screen display module to enter the lock screen interface.

[0333] S1562. The lock screen display module sends a lock screen notification to the notification control module.

[0334] S1563. The notification control module displays the real-time progress notification message on the lock screen interface.

[0335] S1564. The lock screen display module displays a real-time progress notification message on the lock screen.

[0336] Exemplarily, as shown in FIG12( b ), the takeaway notification message 1002 is displayed on the lock screen interface 1202 .

[0337] Optionally, when the real-time progress notification message is displayed on the lock screen interface, it can be switched to the notification bar interface for display.

[0338] S1571. The user triggers the lock screen display module to enter the unlock screen.

[0339] Optionally, the user can click the unlock button on the phone to trigger unlocking.

[0340] S1572. The lock screen display module sends a notification to the notification control module to remove the real-time progress notification message of the lock screen interface.

[0341] S1573. The notification control module displays the real-time progress notification message on the notification bar interface.

[0342] S1574. The notification display module displays a real-time progress notification message on the notification bar interface.

[0343] Exemplarily, as shown in FIG12( a ), a takeaway notification message 1002 is displayed on a notification bar interface 1201 .

[0344] In one embodiment, the real-time progress notification message may be removed.

[0345] The end of the real-time progress notification message may be triggered by the user or by the third-party application itself; or the real-time progress notification message may be ended passively.

[0346] S1581. The user triggers the end of the real-time progress notification message.

[0347] For example, for a navigation notification message, the user can end navigation in the navigation application.

[0348] S1581′: The third-party application triggers the end of the real-time progress notification message.

[0349] For example, for a takeaway notification message, when the rider arrives to deliver the food, the takeaway application can trigger a real-time progress message to end the takeaway.

[0350] S1582: The third-party application sends the end real-time progress notification message parameters to the notification service module.

[0351] Optionally, the third-party application may carry an end command when sending the real-time progress notification message parameters.

[0352] S1581”, passive end real-time progress notification message.

[0353] Optionally, a preset time can be set for each service's real-time progress notification message, and the creation time and last refresh time of each service's real-time progress notification message can be recorded. If the difference between the creation time and the last refresh time of a service's real-time progress notification message is greater than the preset time, it indicates that the real-time progress notification message for that service may have an error, and the notification control module triggers a command to terminate the real-time progress notification message for that service.

[0354] S1582′: The notification control module sends a command for triggering the end of the real-time progress notification message to the notification service module.

[0355] S1583: The notification service module sends a command to end the real-time progress notification message to the notification control module.

[0356] S1584. The notification control module sends a command to remove the real-time progress notification message to the notification display module according to the end real-time progress notification message.

[0357] Optionally, the notification display module removes the real-time progress notification message from the notification bar interface.

[0358] S1594. The notification control module sends a command to remove the real-time progress notification message to the lock screen display module according to the end real-time progress notification message.

[0359] Optionally, the lock screen display module removes the real-time progress notification message on the lock screen interface.

[0360] Optionally, the notification message may be divided into a real-time progress notification message and a non-real-time progress notification message.

[0361] Optionally, real-time progress notification messages can be displayed in the first area, while non-real-time progress notification messages can be displayed in the second area. The first area is located above the second area, making it easier for users to quickly find important notifications.

[0362] In one embodiment, the non-real-time progress notification messages may be divided into service notification messages and content information according to their categories.

[0363] Service notifications, including notifications from social apps and important service reminders (such as bank service reminders), are displayed in the third area, while content information, including advertising messages, is displayed in the fourth area. The third and fourth areas are subareas of the second area.

[0364] Optionally, the third area is located above the fourth area, so that users can quickly find important notifications.

[0365] In another embodiment, the non-real-time progress notification messages may be divided into important notification messages and non-important notification messages according to their importance.

[0366] Optionally, important notification messages are displayed in the third area, and non-important notification messages are displayed in the fourth area. The third and fourth areas are subareas of the second area. Optionally, the third area is located above the fourth area. This allows users to quickly find important notifications.

[0367] Optional. Generally, service notification messages are important notification messages; content information is non-important notification messages.

[0368] Exemplarily, as shown in FIG16 , the notification bar interface 1601 includes multiple notification messages.

[0369] Among them, the takeaway notification message 1602 is a real-time progress notification message, which is displayed in the first area at the top of the notification bar interface 1601 for the user to quickly view. The remaining non-real-time progress notification messages are displayed in the second area below.

[0370] Optionally, the SMS notification message 1603 and the call notification message 1605 are notification messages of social applications, and the bank notification message 1604 is an important service reminder, which are displayed in the third area in the middle of the notification bar interface 1601 to facilitate users to quickly find important notification messages.

[0371] Optionally, the video notification message 1606 and the shopping notification message 1607 are advertising notification messages, which are displayed in the fourth area at the bottom of the notification bar interface 1601 to prevent the user from being disturbed by advertising notification messages and unable to quickly find important notification messages.

[0372] In one embodiment, newly added notification messages are displayed in corresponding areas according to the classification and importance of the notification messages.

[0373] Optionally, if a new real-time progress notification message is added, it will be displayed in the first area at the top of the notification bar interface 1601. The new real-time progress notification message can be located above or below the takeaway notification message 1602. This embodiment of the present application does not limit this.

[0374] Optionally, if a new service notification message is added, it will be displayed in the third area in the middle of the notification bar interface 1601. The new notification message can be located below or above the existing notification message in the third area. This embodiment of the present application does not limit this.

[0375] Exemplarily, as shown in FIG. 16 , the latest bank notification message 1604 in the third area is located above the call notification message 1605 .

[0376] Optionally, the user can also set a notification message to be pinned in each area. For example, as shown in Figure 16, SMS notification message 1603 in the third area is earlier than bank notification message 1604. If the user sets SMS notification message 1603 as the pinned message, SMS notification message 1603 will be at the top of the third area.

[0377] Optionally, if a new content information is added, it is displayed in the third area at the bottom of the notification bar interface 1601. The new content information can be located below or above the existing notification message in the fourth area. This embodiment of the application does not limit this. Optionally, the content information can be displayed in the "More Notifications" area as shown in Figure 16.

[0378] Exemplarily, as shown in FIG. 16 , the latest video notification message 1606 in the fourth area is located above the shopping notification message 1607 .

[0379] In one embodiment, three view stubs may be attached to the original notification list root layout to implement the function of displaying notification messages in different regions.

[0380] Optionally, you can manage the notification message list for each region through a list view. Each region's notification list implements interfaces such as adding, sorting, and removing. When a notification message arrives for a region, the notification message list view for that region replaces the original notification message list view with the corresponding view stub under the layout to load the layout. The overall functional division can be shown in Table 3 below:

[0381] Table 3

[0382] As shown in Table 3, the operating system in the mobile phone may include three sub-modules, namely, a notification display module, a notification control module, and a notification service module.

[0383] Optionally, the notification display module includes a notification message list view function. Specifically, the notification display module includes multiple core classes that can implement the notification message list view function.

[0384] Optionally, NotificationCenterRootView has the notification message list root layout function of the notification center (notification bar). INotificationListView can provide the notification message partition list operation interface. RealTimeProgressNotificationListView

[0385] It can realize the function of real-time progress notification message list view. ServiceNotificationListView can realize the function of service notification message list view. ContentInformationListView can realize the function of content information notification message list view.

[0386] Optionally, the notification display module includes a notification center (notification bar) view management function. Specifically, the core class NotificationCenterLayoutManager in the notification display module manages the notification center (notification bar) view.

[0387] Optionally, the notification control module includes an internal notification message management function. Specifically, the notification control module includes multiple core classes that can implement the internal notification message management function.

[0388] Optionally, NotificationController is a notification message controller that can manage and control notification messages. NotificationClassifier is a notification message classifier that identifies the category of notification messages. NotificationListener is a notification message listener that receives new notification message events.

[0389] Optionally, the notification service module includes an external notification data service function. Specifically, the notification service module includes multiple core classes that can implement the external notification data service function.

[0390] Optionally, NotificationManagerService is a notification management service that provides operating system-level notification message management and new notification messages. NotificationCache can implement notification message caching.

[0391] In one embodiment, different notification message reminder modes may be set for notification messages of different importance.

[0392] Optionally, strong reminders can be issued for important notifications. For example, real-time progress notifications and service notifications can be displayed in a variety of ways, with priority displayed in the interface. For example, SMS notifications, considered important, can be displayed in the notification bar, as pop-up windows on the phone's desktop, or on the lock screen. The screen can also be illuminated after receiving an SMS message.

[0393] For unimportant notification messages, weak reminders are provided. For example, content information can be displayed only in the notification bar interface with low priority to avoid excessive interference to users.

[0394] Optionally, the content information can also be folded and displayed. For example, as shown in FIG17A , the video notification message 1606 and the shopping notification message 1607 in the more notifications in FIG16 can be folded and displayed as the more notification folding box 1701 in FIG17A .

[0395] In one embodiment, when content information is displayed in a folded form, notification messages that may be of interest to the user may be intelligently recommended.

[0396] Specifically, based on data such as user click-through rate, application usage rate, content type, etc., notification messages that users are interested in are actively recommended and displayed.

[0397] Optionally, for a notification message, when the user click rate and the application usage rate corresponding to the notification message are both greater than a first threshold and the content type is the type that the user is interested in (for example, the user likes ancient style types), the operating system can recommend the notification message in more notifications.

[0398] For example, if the first threshold is 10%, and the click-through rate of a gufeng music recommendation notification message is 12%, and the user usage rate of a music app is 20%, both exceeding the first threshold, then the gufeng music recommendation notification message can be determined to be of a type that the user likes. The operating system can then recommend the gufeng music recommendation notification message in more notifications.

[0399] For example, as shown in FIG17B , the ancient music recommendation notification message 1703 in the more notifications 1702 is expanded and displayed, while the video notification message 1606 and the shopping notification message 1607 are collapsed.

[0400] In one embodiment, the display area of ​​the notification message may be determined based on the authorized user portrait.

[0401] For example, the notification messages that the user is interested in from more notifications can be displayed in the third area. For example, if the user uses the short video application frequently, with a usage rate greater than 40%, the notification message of the short video can be displayed in the third area.

[0402] In related technologies, third-party applications generally set whether notification messages are important messages. However, in order to increase their own exposure and importance, third-party applications often set most notification messages as important messages, resulting in an overflow of notification messages and excessive interference to users.

[0403] In the embodiment of the present application, each notification message can be recalibrated to determine whether the notification message is an important message, and the notification message can be displayed in the corresponding notification bar area.

[0404] Optionally, the PUSH server can calibrate the importance of feature messages. Specifically, the PUSH server can weight the importance of the notification message based on the original importance of the notification message, the importance of the notification message sending channel, the importance of the notification message application, and the importance of the notification message content. The importance of the notification message application is given a higher weight.

[0405] Optionally, the notification message may be sent through a Push client proxy or through other means.

[0406] For example, a third-party application can send a notification message through a Push client proxy. This can be done by using the extended fields in the notification message to select different channels based on the importance of the message. Different channels have different importance levels.

[0407] For example, when a food delivery app sends a notification message related to a system upgrade, it carries an extension field indicating that the system upgrade notification message should be sent via channel 1. When a food delivery app sends a notification message related to an advertisement, it carries an extension field indicating that the advertisement notification message should be sent via channel 0. The importance of channel 1 is 8, and the importance of channel 0 is 2.

[0408] Optionally, the original importance of the notification message and the channel information for sending the notification message can be obtained from the notification message parameters sent by the third-party application. The importance of the notification message sending channel, the importance of the notification message application, and the importance of the notification message content can be determined based on big data or set based on the developer's experience. The embodiments of the present application do not impose any specific restrictions on this.

[0409] For example, the original importance weight of a notification message is 1, the original channel weight of the notification message is 2, the importance weight of the notification message application is 5, and the importance weight of the notification message content is 2. If the importance of a notification message is greater than or equal to the preset threshold, it is considered an important message and a strong reminder is issued; if the importance of a notification message is less than the preset threshold, it is considered a non-important message and a weak reminder is issued.

[0410] For example, the preset threshold can be set to 5. If the original importance of the SMS notification message is 8, the importance of the SMS notification message sending channel is 8, the importance of the SMS application is 8, and the importance of the SMS notification message content is 8, then the calibrated importance of the SMS notification message is 8, which is greater than the preset threshold. The SMS notification message is considered an important message and a strong reminder is issued.

[0411] For another example, the original importance of the video notification message is 8, the importance of the video notification message sending channel is 2, the importance of the video application is 2, and the importance of the SMS notification message content is 1. Then the calibrated importance of the video notification message is 2.4, which is less than the preset threshold. The video notification message is a non-important message and a weak reminder is given.

[0412] Optional, Huawei Push Service (HMS Core Push Service) is a solution platform that provides notification push for third-party applications in the ecosystem expansion. Combined with the use of Push Service, there are three typical scenarios for sending notification messages:

[0413] (1) In-app local notification scenario

[0414] For example, a notification message scenario is triggered by local logic within a third-party application, or a notification message is triggered by a third-party application through a third-party push platform. In this scenario, the sender of the notification message is the local third-party application, and the responder of the notification application is also the third-party application.

[0415] Optionally, in this scenario, when a notification message is received in the notification listener, the Push interface can be called back to calibrate the notification message to determine whether the notification message is an important message.

[0416] (2) Cloud Push in-app notification scenario

[0417] Specifically, the Push cloud server sends a notification message to the Push client, which then triggers the third-party application to send a notification message. In this scenario, the sender of the notification message is the local third-party application, and the responder of the notification application is also the third-party application.

[0418] Optionally, in this scenario, the intelligent classification engine in the Push cloud server may calibrate the notification message, and carry the calibration result of the notification message when sending the notification message.

[0419] (3) Cloud Push cross-application notification scenarios

[0420] Specifically, the Push cloud server sends a notification message to the Push client, which then sends the notification. The sender of the notification message is the Push client, and the responder is the application.

[0421] Optionally, in this scenario, the intelligent classification engine in the Push cloud server may calibrate the notification message, and carry the calibration result of the notification message when sending the notification message.

[0422] Optionally, the notification process for the above three scenarios may be as shown in FIG18 :

[0423] For the in-app local notification scenario, the notification process may include the following steps S1801-S1810:

[0424] Among them, steps S1801 to S1804 of creating a notification message can refer to the contents of steps S1501 to S1504 of creating the first real-time progress notification message, which will not be repeated here.

[0425] S1805: The notification control module triggers the PUSH server calibration notification message.

[0426] S1806. Push the server calibration notification message.

[0427] Optionally, the PUSH server may calculate the importance of the notification message by weighting according to the original importance of the notification message, the importance of the notification message sending channel, the importance of the notification message application, and the importance of the notification message content.

[0428] For example, the importance of the SMS notification message before calibration is 8, and the importance after calibration is 8; the importance of the video notification message before calibration is 8, and the importance after calibration is 2.4.

[0429] S1807. The PUSH server sends the notification message calibration result to the notification control module.

[0430] Exemplarily, the PUSH server sends the calibrated importance levels of the SMS notification message and the video notification message to the notification control module.

[0431] S1808. The notification control module determines a display area for the notification message according to the notification message calibration result.

[0432] Optionally, the notification control module may set a preset threshold of 5. When the importance of the notification message is greater than or equal to 5, it is displayed in the third area, and when the importance of the notification message is less than 5, it is displayed in the fourth area. For example, SMS notification messages are displayed in the third area, and video notification messages are displayed in the fourth area.

[0433] S1809: The notification control module triggers the notification display module to display the notification message.

[0434] S1810. The notification display module displays a notification message.

[0435] Exemplarily, as shown in FIG16 , the SMS notification message 1603 is displayed in the third area; and the video notification message 1606 is displayed in the fourth area.

[0436] For the Cloud Push in-app notification scenario, the notification process can be as follows: S1821-S1832:

[0437] S1821. User triggers notification service.

[0438] For example, a user opens a food delivery app.

[0439] Optionally, a third-party application server may also trigger a notification service, as described in detail in step S1823 below.

[0440] S1822. The third-party application triggers a third-party application server notification service.

[0441] For example, the food delivery application may trigger the food delivery application server to send a notification message in response to the user opening the food delivery application.

[0442] S1823. The third-party application server triggers a notification service.

[0443] Alternatively, the third-party application server can use internal logic and rules to determine when to send notification messages. For example, a food delivery app can send users a discount notification message at 11:00 AM every day to remind them to use the food delivery app.

[0444] S1824. The third-party application server sends notification message parameters to the PUSH server.

[0445] Optionally, the food delivery application server may send notification message parameters via a PUSH server.

[0446] S1825. PUSH the server calibration notification message parameters.

[0447] Optionally, the PUSH server may calculate the importance of the notification message by weighting according to the original importance of the notification message, the importance of the notification message sending channel, the importance of the notification message application, and the importance of the notification message content.

[0448] For example, the importance of the SMS notification message before calibration is 8, and the importance after calibration is 8; the importance of the video notification message before calibration is 8, and the importance after calibration is 2.4.

[0449] Optionally, the PUSH server may carry the notification message calibration result in an extended parameter.

[0450] S1826. The PUSH server sends the calibrated notification message parameters to the PUSH client.

[0451] S1827. The PUSH client sends the calibrated notification message parameters to the third-party application.

[0452] S1828. The third-party application sends the calibrated notification message parameters to the notification service module.

[0453] S1829. The notification service module creates a notification message and sends it to the notification control module.

[0454] Optionally, the notification service module may send the created notification message and the notification message calibration result to the notification control module.

[0455] Optionally, steps S1830-S1832 of determining the notification message display area and displaying the notification message may refer to the above steps S1808-S1810 and will not be repeated here.

[0456] For the Cloud Push cross-application notification scenario, the notification process can be as follows: Steps S1841-S1849:

[0457] S1841. The third-party application server triggers a notification service.

[0458] Optionally, the user can also trigger a notification service.

[0459] S1842. The third-party application server sends the notification message parameters to the PUSH server.

[0460] S1843. PUSH the server calibration notification message parameters.

[0461] For details, please refer to the above step S1825.

[0462] S1844. The PUSH server sends the calibrated notification message parameters to the PUSH client.

[0463] S1845. The PUSH client sends the calibrated notification message parameters to the notification service module.

[0464] Optionally, steps S1846-S1849 of creating a notification message, determining a notification message display area, and displaying the notification message may refer to the above steps S1829-S1832 and will not be repeated here.

[0465] In this way, the operating system can calibrate the importance of notification messages, display notification messages in appropriate areas, and improve user experience.

[0466] In one embodiment, the real-time progress notification message can be displayed in the form of a unified live capsule in the mobile phone status bar and support interactive operations.

[0467] In related art, as shown in Figure 19, the mobile phone desktop interface is cluttered with various real-time progress notification messages, affecting the user experience. To address this issue, the present embodiment uses capsule information of real-time progress notification messages to uniformly display them on the mobile phone desktop using live capsules. This keeps the mobile phone desktop tidy and improves the user experience.

[0468] Optionally, the notification message sent by the third-party application to the operating system carries an extended parameter, and the extended parameter may indicate whether the notification message can be displayed as a live capsule.

[0469] For example, a third-party application can add a notification message identifier to the extended parameter of Notification#extras to distinguish whether the notification message can be displayed as a live capsule. For specific parameter settings, please refer to the following Tables 4 and 5:

[0470] Table 4

[0471] Notification.Capsule is a boolean. When true, it indicates that the notification message supports Live Capsule display; when false, it indicates that the notification message does not support Live Capsule display. Notification.CapsuleAction is an int. When 0, it indicates creating a Live Capsule display; when 1, it indicates updating a Live Capsule display; when -1, it indicates ending a Live Capsule display. Notification.CapsuleParams is a Bundle, indicating the parameters of the Live Capsule.

[0472] Optionally, the parameters of the live capsule in Table 4 may be as shown in Table 5 below:

[0473] Table 5

[0474] Among them, notification.capsule.Type is an Int type data, which includes multiple subcategories. When this parameter is 1, the Live Capsule is displayed as an icon, such as the call Live Capsule 2001 shown in Figure 20; when this parameter is 2, the Live Capsule is displayed as an icon text type, such as the takeout Live Capsule 2005 shown in Figure 20; when this parameter is 3, the Live Capsule is displayed as a timer type, such as the call Live Capsule 2002, screen recording Live Capsule 2003, and countdown Live Capsule 2004 shown in Figure 20; when this parameter is 4, the Live Capsule is displayed as a progress type, such as the Bluetooth transmission Live Capsule 2006 shown in Figure 20; when this parameter is 5, the Live Capsule is displayed as a percentage type, such as the step counting Live Capsule 2007 in the sports health section shown in Figure 20. notification.capsule.Icon is an SVG type data, which is used to indicate the Live Capsule icon or icon animation. notification.capsule.BgColor is an Int type data, which is used to indicate that the Live Capsule has a solid color background. notification.capsule.BgPic is a Bitmap-type data type, used to indicate the background image of the Live Capsule. This parameter is optional. notification.capsule.HintText is a SpannableString-type data type, used to indicate the Live Capsule's hint text (icon text type). notification.capsule.ResumeTime is a Time-type data type, used to indicate the start time of the Live Capsule's pause, resume, or countdown (timing type). notification.capsule.TimeReverse is a Boolean-type data type. When this parameter is true, it indicates that the Live Capsule is a countdown Live Capsule; when this parameter is false, it indicates that the Live Capsule is not a countdown Live Capsule. notification.capsule.ProgressTotel is an int-type data type, used to indicate the total progress of the task in the Live Capsule. notification.capsule.ProgressCurrent is an int-type data type, used to indicate the current progress of the Live Capsule (progress type, percentage type).

[0475] In one embodiment, the live capsule may be adaptively lengthened when displayed on a larger screen.

[0476] Optionally, when the live capsule is displayed in an unfolded state on a wide-screen device such as a foldable phone or tablet, or in landscape mode on a narrow-screen device such as a mobile phone, more content may be displayed in the live capsule.

[0477] 20 , a call live video capsule 2012 includes a call application icon, a call time of 00:20, and a contact person named “Xiao Ming.” A takeaway live video capsule 2015 includes a takeaway application icon, a distance of 500 meters between the rider and the merchant, and the takeaway status “the rider has accepted the order.”

[0478] Optionally, the Live Capsule can be adaptively extended to not display more content.

[0479] Exemplarily, as shown in FIG. 20 , the Bluetooth transmission live capsule 2016 includes a Bluetooth icon and Bluetooth transmission progress.

[0480] Optionally, FIG21( a ) is a schematic diagram showing real-time progress messages displayed on a desktop 2101 in the related art, including a screen recording notification message 2102 and a call notification message 2103 .

[0481] Optionally, in an embodiment of the present application, the screen recording notification message and the call notification message can be displayed in the status bar in the form of a live capsule. As shown in (b) of Figure 21, the status bar 2112 in the desktop 2111 includes a screen recording live capsule 2113 and a call live capsule 2114.

[0482] Optionally, the original layout of the status bar (e.g., the time control) can be displaced accordingly according to the display or exit of the live capsule. As shown in FIG21( b ), the time control is displaced from the original left side of the status bar to the middle of the status bar.

[0483] Optionally, a view stub can be attached to the status bar root layout as the live capsule root layout. When the live capsule needs to be displayed, the live capsule root layout replaces the stub view.

[0484] Optionally, the icon in the live capsule can be a picture or an animation. The icon of the live capsule can be an application icon or a service icon, which is not specifically limited in the embodiment of the present application.

[0485] Optionally, the background of the live capsule can be a solid color background or a background with other patterns. For example, as shown in Figure 21 (b), the screen recording live capsule 2113 has a solid color background, and the call live capsule 2114 has a patterned background. The specific background can be determined by a third-party application or operating system, and this embodiment of the application does not impose specific restrictions on this.

[0486] Optionally, the text and time in the Live Capsule can be refreshed based on the progress of the service. For example, the time "00:20" in the call Live Capsule 2002 in Figure 20 can be refreshed in real time. The text "Rider has accepted the order" in the takeaway Live Capsule 2005 can be refreshed based on the real-time progress of the takeaway. For example, when the rider picks up the takeaway, the text is refreshed to "Rider has picked up the meal."

[0487] Optionally, users can interact with the live capsules.

[0488] For example, taking the interaction between a user and a live call capsule as an example, as shown in FIG22(a), the user can click on a live call capsule 2202 on desktop 2201. In response to the user clicking on live call capsule 2202, the mobile phone can display a call card 2204 on interface 2203, as shown in FIG22(b). Subsequently, the user can click on call card 2204 on interface 2203. In response to the user clicking on call card 2204 on interface 2203, the mobile phone can display a call interface 2205, as shown in FIG22(c).

[0489] Optionally, the user can click the return control on call interface 2205 in Figure 22(c), or swipe left (or right) to return to interface 2203 and display call card 2204. The user can click the phone homepage or swipe left (or right) to return to homepage 2201 and display call capsule 2202. Alternatively, the user can swipe call interface 2205 to return to homepage 2201 and display call capsule 2202.

[0490] Optionally, the user can click on the call live capsule 2202 in the desktop 2201. In response to the user clicking on the notification live capsule 2202, the mobile phone can directly display the call interface 2205 as shown in FIG22(c). This embodiment of the application does not make any specific restrictions on this.

[0491] Optional. The live capsule display of notification messages is implemented based on the extended parameters of standard notifications. The submodules are divided as shown in Table 6 below:

[0492] Table 6

[0493] The capsule display module (status bar) is located in the display layer and can display and refresh live capsules based on notification messages from third-party applications, and supports interaction with live capsules. Specifically, the capsule display module can display and exit live capsules; the capsule display module can also expand live capsules to cards and open the corresponding application interface based on user operations, as shown in Figure 22. The capsule display module can also collapse application interfaces to cards or live capsules, and collapse cards to live capsules based on user operations.

[0494] The capsule control module, located in the control layer, manages the status of live video capsules, manages the refresh of live video capsules, and manages multiple live video capsules. Specifically, the capsule expansion module receives notification messages from applications to display and exit live video capsules. It also receives update notification messages from applications to refresh live video capsules.

[0495] The capsule extension template module, located in the service layer, supports notification service module extensions carrying capsule parameters, supports capsule parameter parsing, and is compatible with notification messages that do not adapt to capsule parameters. Specifically, the capsule extension template module can obtain and parse the capsule parameters carried in the notification message template.

[0496] Optionally, specific parameters in the capsule display module, capsule control module, and capsule extension template module may be as shown in Table 7 below:

[0497] The capsule display module includes the display and refresh functions of the live capsule. Specifically, the capsule display module includes multiple core classes that can realize the display and refresh functions of the live capsule.

[0498] Optionally, StatusBarCapsule is a Live Action Capsule object that manages individual Live Action Capsules. StatusBarCapsuleView is the base Live Action Capsule view class, implementing basic Live Action Capsule display and refresh functionality. TimeCapsuleView extends Timer-type Live Action Capsules, supporting timed refreshes. ProgressCapsuleView extends Task Progress-type Live Action Capsules. PercentCapsuleView extends Percent-type Live Action Capsules. TextCapsuleView extends Icon-text-type Live Action Capsules.

[0499] Optionally, the capsule display module further includes displaying and refreshing the live capsule expanded into a card state. Specifically, the capsule display module includes multiple core classes to implement this function.

[0500] Optionally, ExpandCapsuleCard is a Live Capsule expansion card object that implements Live Capsule card management; ExpandCapsuleCardView is the Live Capsule expansion card view base class that implements the basic functions of displaying and refreshing Live Capsule expansion cards; TimerExpandCapsuleCardView supports the extended implementation of timer-type Live Capsule expansion cards and supports timed refresh; ProgressExpandCapsuleCardView supports the extended implementation of task progress-type Live Capsule expansion cards; PercentExpandCapsuleCardView supports the extended implementation of percentage-type Live Capsule expansion cards; TextExpandCapsuleCardView supports the extended implementation of icon and text-type Live Capsule expansion cards.

[0501] Optionally, the capsule control module includes functions of providing management of live capsules and external interaction. Specifically, the capsule control module includes multiple core classes to implement the functions.

[0502] Optionally, the CapsuleManager is responsible for external interaction, receiving live capsule expansion notification messages or broadcasts from the application, and refreshing the live capsule status through the CapsuleController based on parameters. The CapsuleController can connect to external data and other internal modules and is responsible for creating, refreshing, and exiting the display of live capsules, as well as prioritizing and displaying multiple live capsules.

[0503] Optionally, the capsule service module includes a function of providing a live capsule extended parameter template. Specifically, the capsule service module includes multiple core classes to implement this function.

[0504] Optionally, CapsuleExtraTemplate is the base class for the live capsule extended parameter template; TimerCapsuleExtraTemplate is the base class for the live capsule extended parameter template for the timer type; ProgressCapsuleExtraTemplate is the base class for the live capsule extended parameter template for the task progress type; PercentCapsuleExtraTemplate is the base class for the live capsule extended parameter template for the percentage type; and TextCapsuleExtraTemplate is the base class for the live capsule extended parameter template for the icon text type.

[0505] Table 7

[0506] In one embodiment, the content in the live capsule can be updated.

[0507] Optionally, for the same third-party application, the third-party application can send new live capsule parameters to the operating system. The live capsule parameters carry the live capsule content of the updated status, use the channel and importance level of the original live capsule, and specify the notification ID of the original live capsule. For details, please refer to the above-mentioned update method of the real-time progress notification message, which will not be repeated here.

[0508] For example, taking the takeaway live capsule as an example, as shown in (a) of Figure 23, when the real-time progress notification message of the takeaway is updated, the "rider has accepted the order" in the takeaway live capsule 2005 is updated to the "rider has picked up the meal" in the takeaway live capsule 2005'.

[0509] As another example, taking the call live capsule as an example, as shown in (b) of Figure 23, as time progresses, the call duration is refreshed. After 1 second, the call duration "00:20" in the call live capsule 2002 is updated to the call duration "00:21" in the call live capsule 2002'.

[0510] In one embodiment, the live capsule can be managed for its life cycle. Specifically, when the task is completed, the live capsule can be terminated (exit display).

[0511] Optionally, the termination method of the live capsule can be divided into active termination and passive termination according to the triggering party. For details, please refer to the termination method of the real-time progress notification message mentioned above.

[0512] In some embodiments, as shown in Figure 24, a flowchart of live capsule creation, updating, interaction, and termination in an embodiment of the present application is provided. The capsule service module supports the live capsule extension template. The capsule service module, capsule control module, and capsule display module are located in the operating system. Specifically, the steps include:

[0513] S201. The capsule service module sends a live capsule template development guide to a third-party application.

[0514] Optionally, the third-party application may pre-agreed with the notification service module to display the live capsule using the live capsule template.

[0515] Optionally, the notification service module can send live capsule template development instructions to third-party applications. These instructions include rules for filling in live capsule template parameters. For example, they specify parameters related to live capsule display, such as icon, text, and background color; or parameters related to live capsule management, such as creation, update, and termination.

[0516] S2401: The user collapses the live video capsule.

[0517] Optionally, the user can exit the real-time progress service interface on the phone, display it on the phone desktop, and collapse the real-time progress service into a live capsule. For example, as shown in Figure 22(c), the user swipes the screen to exit the call interface 2205. In response to the user exiting the call interface 2205, the phone can collapse the call service into a live capsule.

[0518] Optionally, steps S2402-2406 of creating and displaying a live capsule may refer to steps S1502-1506 of creating and displaying a real-time progress notification message, which will not be described in detail here.

[0519] For example, the mobile phone may display a call live capsule 2202 as shown in FIG. 22( a ).

[0520] In some embodiments, when the service status of the third-party application changes, the live capsule may be updated.

[0521] Optionally, steps S2411-2416 of updating and displaying the live capsule may refer to steps S1521-1516 of creating and displaying the real-time progress notification message, which will not be described in detail here.

[0522] The second live capsule parameter may also carry a mask parameter, and the mask parameter may indicate an area where the first live capsule needs to be updated.

[0523] For example, it is shown in Table 8 below:

[0524] Table 8

[0525] When the icon of the first live capsule needs to be updated, the mask bit carried in the second live capsule parameter is 0x40; when the text of the first live capsule needs to be updated, the mask bit carried in the second live capsule parameter is 0x41; when the background of the first live capsule needs to be updated, the mask bit carried in the second live capsule parameter is 0x42;

[0526] For example, as shown in (a) of Figure 23, after the rider picks up the takeaway, the mask bit carried in the second live capsule parameter is 0x41, and the "rider has accepted the order" in the first takeaway live capsule 2005 is updated to the "rider has picked up the meal" in the second takeaway live capsule 2005'.

[0527] As another example, as shown in FIG23( b ), the call duration is updated as time progresses. 1 second later, the call duration "00:20" in the first call live capsule 2002 is updated to "00:21" in the second call live capsule 2002'.

[0528] In one embodiment, a user may interact with the live capsule.

[0529] S2421. The user clicks the live capsule.

[0530] Optionally, taking the live call capsule as an example, as shown in FIG22( a ), the user may click on the live call capsule 2202 on the desktop 2201 .

[0531] S2422: The notification display module responds to the user's click on the live capsule operation, and sends the user's click on the live capsule operation to the notification control module.

[0532] S2423. The notification control module triggers the notification display module to display the card.

[0533] S2424. The notification display module displays the card.

[0534] Optionally, the card is a real-time progress notification message card.

[0535] For example, as shown in FIG. 22( b ), the notification display module may display a call card 2204 on the interface 2203 .

[0536] S2425. The user clicks the card.

[0537] For example, as shown in FIG22( b ), the user may click on the call card 2204 of the interface 2203 .

[0538] S2426: The notification display module responds to the user clicking the card and sends the user clicking the card to the notification control module.

[0539] S2427. The notification control module triggers the notification display module to display the card.

[0540] For example, in response to the user clicking the call card 2204 on the interface 2203 , the mobile phone may display a call interface 2205 as shown in FIG. 22( c ).

[0541] In one embodiment, the live capsule may be removed.

[0542] The end of the live capsule can be triggered by the user or by the third-party application itself; or the live capsule can be ended passively.

[0543] Optionally, steps S2431-S2434 of ending the live capsule may refer to steps S1581-S1584 of ending the real-time progress notification message, which will not be repeated here.

[0544] In this way, using the live capsule to uniformly display real-time progress notification messages on the mobile phone desktop, the mobile desktop is tidy and improves the user experience.

[0545] The following is a flow chart of a method for displaying a notification message provided in an embodiment of the present application. As shown in FIG25 , the method includes multiple steps S2501-S2504:

[0546] S2501: The operating system obtains a first real-time progress notification message parameter.

[0547] Specifically, the notification service module in the operating system may obtain the first real-time progress notification message parameter of the application service from the application.

[0548] S2502: The operating system displays a first real-time progress notification message.

[0549] The first real-time progress notification message is displayed according to the first real-time progress notification message parameters.

[0550] Optionally, the notification service module may create a first real-time progress notification message according to the first real-time progress notification message parameters and the real-time progress notification message template, and send the first real-time progress notification message to the notification display module to display the first real-time progress notification message.

[0551] For example, for a takeaway notification message, the mobile phone notification bar displays a real-time progress notification message as shown in (a) of Figure 12. Alternatively, the mobile phone status bar may display a live capsule as shown in the takeaway live capsule 2005 of Figure 20.

[0552] S2503: The operating system obtains parameters of the second real-time progress notification message.

[0553] Specifically, the notification service module in the operating system may obtain the second real-time progress notification message parameter of the application service from the application.

[0554] S2504: The operating system updates the first real-time progress notification message to a second real-time progress notification message.

[0555] The second real-time progress notification message is displayed according to the second real-time progress notification message parameters.

[0556] Optionally, the notification service module in the operating system may obtain the second real-time progress notification message parameter of the application service from the application.

[0557] In one embodiment, the notification service module can create a second real-time progress notification message based on the second real-time progress notification message parameters and the real-time progress notification message template, and send the second real-time progress notification message to the notification display module, and the notification display module replaces the first real-time progress notification message with the second real-time progress notification message.

[0558] In another embodiment, the second real-time progress notification message parameters carry a mask parameter, and the mask parameter may indicate some parameters of the first real-time progress notification message that need to be updated.

[0559] The notification service module displays the second real-time progress notification message according to the first real-time progress notification message parameters and the partial parameters of the second real-time progress notification message parameters that need to be updated indicated by the mask parameter.

[0560] It should be noted that some operations in the processes of the above-mentioned method embodiments are optionally combined, and / or the order of some operations is optionally changed. In addition, the execution order between the steps of each process is only exemplary and does not constitute a limitation on the execution order between the steps. There may also be other execution orders between the steps. It is not intended to indicate that the execution order is the only order in which these operations can be performed. Those of ordinary skill in the art will think of various ways to reorder the operations described herein. In addition, it should be noted that the process details involved in a certain embodiment of this invention are also applicable to other embodiments in a similar manner, or different embodiments can be used in combination.

[0561] Furthermore, some steps in the method embodiments may be equivalently replaced with other possible steps. Alternatively, some steps in the method embodiments may be optional and may be deleted in certain usage scenarios. Alternatively, other possible steps may be added to the method embodiments.

[0562] Furthermore, the above method embodiments may be implemented separately or in combination.

[0563] An embodiment of the present application also provides a chip system, which includes at least one processor and at least one interface circuit. The processor and the interface circuit can be interconnected via lines. For example, the interface circuit can be used to receive signals from other devices. For another example, the interface circuit can be used to send signals to other devices. Exemplarily, the interface circuit can read instructions stored in a memory and send the instructions to the processor. When the instructions are executed by the processor, the electronic device can execute the various steps performed by the mobile phone in the above embodiment. Of course, the chip system can also include other discrete components, which are not specifically limited in the embodiment of the present application.

[0564] An embodiment of the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the notification message display method in the above-mentioned embodiment.

[0565] An embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the above-mentioned related steps to implement the method for displaying notification messages in the above-mentioned embodiment.

[0566] In addition, an embodiment of the present application also provides a device, which can specifically be a component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor can execute the computer-executable instructions stored in the memory to enable the device to execute the notification message display method in the above-mentioned method embodiments.

[0567] Among them, the electronic device, computer-readable storage medium, computer program product or chip provided in the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0568] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, the division of the above-described functional modules is used only as an example. In actual applications, the above-described functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific operating processes of the above-described systems, devices, and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0569] In the several embodiments provided in this application, it should be understood that the disclosed methods can be implemented in other ways. For example, the electronic device embodiments described above are merely illustrative. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of modules or units, which can be electrical, mechanical or other forms.

[0570] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0571] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0572] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned readable storage medium includes: various media that can store program instructions, such as flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk.

[0573] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for displaying a notification message, characterized in that: include: Get the first real-time progress notification message parameters; Displaying a first real-time progress notification message; The first real-time progress notification message is displayed according to the first real-time progress notification message parameters; Get the second real-time progress notification message parameters; The first real-time progress notification message is updated to a second real-time progress notification message; and the second real-time progress notification message is displayed according to the second real-time progress notification message parameters.

2. The method according to claim 1, characterized in that The method further comprises: The second real-time progress notification message is displayed according to the first real-time progress notification message parameters and the second real-time progress notification message parameters.

3. The method according to claim 1, characterized in that The updating of the first real-time progress notification message to a second real-time progress notification message includes: generating a second real-time progress notification message according to the second real-time progress notification message parameters; The first real-time progress notification message is replaced by the second real-time progress notification message.

4. The method according to claim 2, characterized in that: The updating of the first real-time progress notification message to a second real-time progress notification message includes: Part of the content in the first real-time progress notification message is updated according to the second real-time progress notification message parameter to generate the second real-time progress notification message and display the second real-time progress notification message.

5. The method according to any one of claims 1 to 4, characterized in that: The application framework layer applied to the terminal device, the obtaining of the first real-time progress notification message parameter includes: The application framework layer obtains the first real-time progress notification message parameter from the first application.

6. The method according to any one of claims 1 to 5, characterized in that: The displaying of the first real-time progress notification message includes: Displaying the first real-time progress notification message according to a real-time progress notification message template; the real-time progress notification message template includes an icon area; The icon area is used to display application icons, service icons, or superimposed icons of application icons and service icons.

7. The method according to claim 6, characterized in that The displaying of the first real-time progress notification message according to the real-time progress notification message template includes: The first real-time progress notification message parameter includes a first parameter. When the first parameter indicates that the first real-time progress notification message parameter is a real-time progress notification message parameter, the first real-time progress notification message is displayed according to a real-time progress notification message template.

8. The method according to claim 6 or 7, characterized in that: The real-time progress notification message template includes a first real-time progress notification message template; The first real-time progress notification message template includes an icon area, a main information area, and a secondary information area; The main information area includes a rich text control or a timing control; the sub-information area includes a rich text control.

9. The method according to claim 8, characterized in that The first real-time progress notification message template further includes at least one of an auxiliary area and an extended area; The auxiliary area includes at least one of an operation control and a progress control of the service corresponding to the first real-time progress notification message; The extended area includes at least one of progress information, detailed information, and operation information of the service corresponding to the first real-time progress notification message.

10. The method according to claim 6 or 7, characterized in that: The real-time progress notification message template includes a second real-time progress notification message template; The second real-time progress notification message template includes at least one of a text control, a progress control, and a timing control.

11. The method according to any one of claims 1 to 10, characterized in that: The method further comprises: The second real-time progress notification message parameter carries a second parameter, and determines to end displaying the second real-time progress notification message according to the second parameter; when the display time of the second real-time progress notification message reaches a preset time, the display of the second real-time progress notification message ends; Alternatively, when the difference between the creation time of the first real-time progress notification message and the last refresh time of the second real-time progress notification message is greater than a preset time, the display of the second real-time progress notification message ends.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: Displaying the real-time progress notification message in the first area; displaying the non-real-time progress notification message in the second area; the first area is located above the second area; The non-real-time progress notification message includes a service notification message and / or content information; the service notification message includes a notification message of a social application and / or a notification message of an important application; the content information includes a notification message of an advertising application.

13. The method according to claim 12, characterized in that The displaying the non-real-time progress notification message in the second area includes: The service notification message is displayed in the third area; the content information is displayed in the fourth area; the third area and the fourth area are sub-areas of the second area; the third area is located above the fourth area.

14. The method according to any one of claims 1 to 11, characterized in that: said displaying said non-real-time progress notification message in the second area; The first area is located above the second area, and further includes: The non-real-time progress notification message includes an important notification message and / or a non-important notification message; the important notification message is displayed in a third area; the non-important notification message is displayed in a fourth area; the third area and the fourth area are sub-areas of the second area; the third area is located above the fourth area.

15. The method according to claim 14, characterized in that The method further comprises: The importance of the non-real-time progress notification message is calibrated, and the area where the non-real-time progress notification message is displayed is determined according to the calibration result.

16. The method according to claim 15, characterized in that The step of calibrating the importance of the non-real-time progress notification message and determining the area where the non-real-time progress notification message is displayed according to the calibration result includes: A second importance of the non-real-time progress notification message is obtained by weighted calculation according to at least one of the importance of the non-real-time progress notification message sending channel, the importance of the application corresponding to the non-real-time progress notification message, the importance of the content in the non-real-time progress notification message, and the first importance of the non-real-time progress notification message; the first importance is the importance set for the non-real-time progress notification message by the application corresponding to the non-real-time progress notification message; If the second importance is greater than or equal to a preset threshold; displaying the non-real-time progress notification message in the third area; If the second importance is less than a preset threshold, the non-real-time progress notification message is displayed in the fourth area.

17. A method for displaying a notification message, characterized in that: include: Displaying a first real-time progress notification message; The first real-time progress notification message is displayed according to a real-time progress notification message template; The real-time progress notification message template includes an icon area; the icon area is used to display an application icon, a service icon, or a superimposed icon of an application icon and a service icon; Updating the first real-time progress notification message to a second real-time progress notification message; The second real-time progress notification message complies with the real-time progress notification message template.

18. The method according to claim 17, characterized in that The first real-time progress notification message is displayed according to the real-time progress notification message template, including: The first real-time progress notification message parameter includes a first parameter. When the first parameter indicates that the first real-time progress notification message parameter is a real-time progress notification message parameter, the first real-time progress notification message is displayed according to a real-time progress notification message template.

19. The method according to claim 17 or 18, characterized in that The real-time progress notification message template includes a first real-time progress notification message template; The first real-time progress notification message template includes an icon area, a main information area, and a secondary information area; The main information area includes a rich text control or a timing control; the secondary information area includes a rich text control.

20. The method according to claim 19, characterized in that The first real-time progress notification message template further includes at least one of an auxiliary area and an extended area; The auxiliary area includes at least one of an operation control and a progress control of the service corresponding to the first real-time progress notification message; The extended area includes at least one of progress information, detailed information, and operation information of the service corresponding to the first real-time progress notification message.

21. The method according to claim 17 or 18, characterized in that The real-time progress notification message template includes a second real-time progress notification message template; The second real-time progress notification message template includes at least one of a text control, a progress control, and a timing control.

22. An electronic device, characterized in that: include: A processor, a memory and a display screen, wherein the memory is coupled to the processor, and the memory is used to store computer program code, wherein the computer program code includes computer instructions, and when the processor reads the computer instructions from the memory, the electronic device executes the method as described in any one of claims 1 to 16, or executes the method as described in any one of claims 17 to 21.

23. A computer-readable storage medium having instructions stored therein, characterized in that: When the instruction is executed on an electronic device, the electronic device executes the method as claimed in any one of claims 1 to 16, or executes the method as claimed in any one of claims 17 to 21.

Images