Notification display method and terminal

Patent metadata

Field	Value
Publication number	US-12223154-B2
Application number	US-202217969150-A
Country	US
Kind code	B2
Filing date	Oct 19, 2022
Priority date	Sep 30, 2017
Publication date	Feb 11, 2025
Grant date	Feb 11, 2025

Abstract

This application discloses a notification display method. The method comprises: when there is a to-be-notified event, displaying, by a terminal, a notification by classification based on a notification type of the notification corresponding to the to-be-notified event; and displaying, by the terminal, in different display modes based on a priority of the notification, wherein the different display modes comprise: displaying in expanded form or displaying in collapsed form in the corresponding display pane, or the different display modes comprise: displaying in a first mode or displaying in a second mode in the corresponding display pane, and content displayed in the first mode is more than content displayed in the second mode.

First claim

The invention claimed is:

1. A notification display method implemented by a terminal, comprising:
obtaining at least two to-be-notified events, wherein the at least two to-be-notified events comprises a first to-be-notified event of a first application and a second to-be-notified event of a second application;
obtaining matching information from object information of the at least two to-be-notified events;
matching the matching information against a rule in a rule repository to determine the first to-be-notified event and the second to-be-notified event correspond to a first notification type, wherein the matching information includes jump information and application package name information and the jump information specifies instructions to jump to an interface corresponding to the at least two to-be-notified events after an action is performed on a notification associated with the at least two to-be-notified events, wherein when the first to-be-notified event and the second to-be-notified event belong to a same notification type, the first to-be-notified event and the second to-be-notified event have a same jump information, wherein the matching includes matching the jump information against a jump matching condition of a jump rule corresponding to the first notification type, and matching the application package name information against an application package name matching condition corresponding to the jump matching condition, wherein the jump information includes at least an Action field, a Class field, an uriString field, or a user-defined field; and
displaying a notification by classification, comprising displaying a first notification corresponding to the first to-be-notified event and the second to-be-notified event with the first notification type in a first display pane in a centralized manner.

2. The method according to claim 1 , wherein the at least two to-be-notified events comprises a third to-be-notified event, the third to-be-notified event correspond to a second notification type;
wherein the displaying a notification by classification further comprising:
displaying a second notification comprising information corresponding to the third to-be-notified event with the second notification type in a second display pane in a centralized manner, wherein the first display pane and the second display pane occupy different display position.

3. The method according to claim 2 , wherein the first notification is displayed in a collapsed form and the second notification is displayed in an expanded form, wherein the second notification type has a higher priority than the first notification type.

4. The method according to claim 3 , wherein the displaying a notification by classification further comprises:
displaying, by the terminal, the second notification in the collapsed form in response to detecting an input operation performed on the second notification.

5. The method according to claim 3 , wherein the priorities of the first notification and the second notification are determined based on user usage habit information or are set by a user.

6. The method according to claim 5 , wherein the user usage habit information comprises at least one of the following:
user historical notification tapping frequency information;
user historical notification deletion frequency information; or
user profile information.

7. The method according to claim 2 , wherein a size of the second notification is displayed larger than a size of the first notification, wherein the second notification type has a higher priority than the first notification type.

8. A terminal, comprising:
one or more processors;
a memory coupled to the one or more processors, wherein the one or more processors are configured to:
obtain at least two to-be-notified events, wherein the at least two to-be-notified events comprises a first to-be-notified event of a first application and a second to-be-notified event of a second application;
obtain matching information from object information of the at least two to-be-notified events;
match the matching information against a rule in a rule repository to determine the first to-be-notified event and the second to-be-notified event correspond to a first notification type, wherein the matching information includes jump information and application package name information and the jump information specifies instructions to jump to an interface corresponding to the at least two to-be-notified events after an action is performed on a notification associated with the at least two to-be-notified events, wherein when the first to-be-notified event and the second to-be-notified event belong to a same notification type, the first to-be-notified event and the second to-be-notified event have a same jump information, wherein the matching includes matching the jump information against a jump matching condition of a jump rule corresponding to the first notification type, and matching the application package name information against an application package name matching condition corresponding to the jump matching condition, wherein the jump information includes at least an Action field, a Class field, an uriString field, or a user-defined field; and
display a notification by classification, comprising displaying a first notification corresponding to the first to-be-notified event and the second to-be-notified event with the first notification type in a first display pane in a centralized manner.

9. The terminal according to claim 8 , wherein the at least two to-be-notified events comprises a third to-be-notified event, the third to-be-notified event correspond to a second notification type;
wherein the displaying a notification by classification further comprising:
displaying a second notification comprising information corresponding to the third to-be-notified event with the second notification type in a second display pane in a centralized manner, wherein the first display pane and the second display pane occupy different display position.

10. The terminal according to claim 9 , wherein the first notification is displayed in a collapsed form and the second notification is displayed in an expanded form, wherein the second notification type has a higher priority than the first notification type.

11. The terminal according to claim 10 , wherein the displaying a notification by classification further comprises:
displaying, by the terminal, the second notification in the collapsed form in response to detecting an input operation performed on the second notification.

12. The terminal according to claim 10 , wherein the priorities of the first notification and the second notification are determined based on user usage habit information or are set by a user.

13. The terminal according to claim 12 , wherein the user usage habit information comprises at least one of the following:
user historical notification tapping frequency information;
user historical notification deletion frequency information; or
user profile information.

14. The terminal according to claim 9 , wherein a size of the second notification is displayed larger than a size of the first notification, wherein the second notification type has a higher priority than the first notification type.

15. A non-transitory computer-readable storage medium, comprising an instruction, which when executed by at least one processor of a terminal, cause the at least one processor to perform operations, comprising:
obtaining at least two to-be-notified events, wherein the at least two to-be-notified events comprises a first to-be-notified event of a first application

Assignees

• Huawei Tech Co Ltd

Inventors

• Liu Mohan
• Zhou Li
• Jiang Jiyong
• Yang Renzhi

Classifications

• H04W4/20

  Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel · CPC title

• G06N5/01

  Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound · CPC title

• H04L51/224

  providing notification on incoming messages, e.g. pushed notifications of received messages · CPC title

• G06N5/048

  Fuzzy inferencing · CPC title

• G06N20/20

  Ensemble learning · CPC title