A notification message management method and device based on user portrait

Abstract

The present invention discloses a notification message management method and device based on user portrait, which belongs to the field of mobile communication technology and is used to solve the following technical problem: the existing notification management method cannot perform targeted management, resulting in a poor user experience. The method includes: inheriting and registering a notification monitoring service from the operating system; when the notification monitoring service receives a notification message, determining whether to store the notification message through the list management operation performed by the user on the sender of the notification message; if not, matching the notification message with the user's usage habits; and determining whether to display the notification message based on the matching result. The above scheme combines user usage habits with notification message management, realizes targeted notification message management, and enhances user experience.

Description

Technical Field

[0001] The present application relates to the field of mobile communication technology, and in particular to a notification message management method and device based on user portrait. Background Art

[0002] With the development of mobile terminals, smartphones have become a must-have tool for everyone, and their functions have evolved from making phone calls to a medium for information transmission. However, with the popularity of smartphones and the improvement of their configurations, various applications have emerged in an endless stream, and even hundreds of applications can be installed on each mobile phone. These applications often send spam messages or even advertisements through notifications, which seriously disturb users.

[0003] Current smartphones all have notification management functions, and users can manually disable application notifications. Mobile phone manufacturers usually put notification management in a hidden place, but it is usually difficult for ordinary users to find this function. At the same time, this requires each application to operate to close the notification, which undoubtedly greatly increases the tediousness. Of course, some applications have already implemented notification collection functions, but they are often rather rigid. For a single application, either all are displayed or all are collected, or they are filtered based on keywords. It is impossible to manage notifications in a targeted manner, and users cannot experience personalized functions, resulting in a poor user experience of existing notification interception. Summary of the invention

[0004] The embodiments of the present application provide a notification message management method and device based on user portrait, which are used to solve the following technical problems: the existing notification management method cannot perform targeted management, resulting in a poor user experience.

[0005] The present application embodiment adopts the following technical solutions:

[0006] On the one hand, an embodiment of the present application provides a notification message management method based on user portrait, which is applied to a mobile terminal, and the method includes:

[0007] Inherit and register the notification listening service from the operating system;

[0008] When the notification monitoring service receives a notification message, determining whether to store the notification message through a list management operation performed by a user on the sender of the notification message;

[0009] If not, matching the notification message with the user's usage habits;

[0010] According to the matching result, it is determined whether to display the notification message.

[0011] In one or more embodiments of the present application specification, after inheriting and registering the notification listening service from the operating system, the method further includes:

[0012] When installing the notification message sender, the user is guided to enable the notification message management function so that the notification monitoring service obtains the notification message management authority.

[0013] In one or more embodiments of the present application specification, the list management operation performed by the user on the notification message sender specifically includes:

[0014] The notification message sender is added to a blacklist, and / or, the notification message sender is added to a whitelist, and / or, a storage keyword is set for the notification message manager.

[0015] In one or more embodiments of the present application specification, before matching the notification message with the user's usage habits, the method further includes:

[0016] According to the stored notification messages and the displayed notification messages, the notification message analysis data is sorted out, and the notification message analysis data at least includes: mobile terminal MAC address, user information, bounce rate, stay time, trigger number, interaction depth and notification message attributes;

[0017] The notification message analysis data is connected to a preset data analysis website to determine the user's usage habits.

[0018] In one or more embodiments of the present application, the method further includes:

[0019] Using the StatusBarNotification class in the notification monitoring service, obtain the message content of the notification message;

[0020] The message content is added to the notification message analysis data.

[0021] In one or more embodiments of the present application, the method further includes:

[0022] In response to a user clicking on a stored notification message, obtaining a package path of a page associated with the notification message through the onNotificationPosted class in the notification listening service;

[0023] Open the notification message associated page through the package path.

[0024] On the other hand, an embodiment of the present application further provides a notification message management device based on user portrait, the device comprising:

[0025] Register the module, inherit and register the notification listening service from the operating system;

[0026] a determination module, which, when the notification monitoring service receives a notification message, determines whether to store the notification message through a list management operation performed by a user on a sender of the notification message;

[0027] A matching module, if not, matches the notification message with the user's usage habits;

[0028] The determination module determines whether to display the notification message according to the matching result.

[0029] In one or more embodiments of the present application specification, the device further includes:

[0030] The guiding module guides the user to enable the notification message management function when installing the notification message sender, so that the notification monitoring service obtains the notification message management authority.

[0031] In one or more embodiments of the present application specification, the determination module,

[0032] According to the stored notification messages and the displayed notification messages, the notification message analysis data is sorted out, and the notification message analysis data at least includes: mobile terminal MAC address, user information, bounce rate, stay time, trigger number, interaction depth and notification message attributes;

[0033] The notification message analysis data is connected to a preset data analysis website to determine the user's usage habits.

[0034] In one or more embodiments of the present application, the device further includes:

[0035] An acquisition module, using the StatusBarNotification class in the notification monitoring service, to acquire the message content of the notification message;

[0036] The message content is added to the notification message analysis data.

[0037] A notification message management method and device based on user portrait provided in the embodiment of the present application have the following beneficial effects: on the basis of the existing notification management technology, personalized elements and user habits are added. In addition to the original notification interception function, when a notification comes, the user matches the notification keyword and the user portrait to determine whether it is a message of interest to the user; at the same time, based on the user's opening frequency, time and stay time, sample features are provided for data mining, thereby strengthening the user portrait. Through the above scheme, targeted notification message management is achieved, and the user experience is enhanced. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0039] Figure 1 A flowchart of a notification message management method based on user portrait provided in an embodiment of the present application;

[0040] Figure 2 A notification message management operation process diagram provided in an embodiment of the present application;

[0041] Figure 3 A structural diagram of a notification message management device based on user portrait provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0043] The embodiment of the present application provides a notification message management method based on user portrait, which uses mobile notification messages to perform data mining, builds user portraits for users, and determines whether to display or hide notifications based on user portraits. This is an application of data analysis on mobile terminals. When a user receives a notification message, the notification message is first stored or displayed based on the user's blacklist and whitelist settings; secondly, based on the user big data recorded in the system, the user's usage habits are analyzed through big data, that is, a user portrait is generated, and the notifications that should be displayed in the whitelist are matched with the user's usage habits, and a final judgment is made based on the matching results whether to display them.

[0044] The notification message management method in the embodiment of the present application is explained in detail below with reference to the accompanying drawings.

[0045] Figure 1 A flowchart of a notification message management method based on user portrait provided in an embodiment of the present application. Figure 1 As shown, the notification message management method in the embodiment of the present application at least includes the following execution steps:

[0046] Step 101: Inherit and register the notification monitoring service from the operating system.

[0047] The notification message management method in the embodiment of the present application is applied on the mobile terminal / terminal side, and the terminal can be a smart phone, a tablet, etc., and the implementation basis of the notification message management method is the notification listening service NotificationListenerService from the Android system. First, the mobile terminal such as a smart phone needs to register the service, and it can be used after successful registration. It should be noted that the registration of the notification listening service on the terminal side can be implemented by existing technical means, and the embodiment of the present application will not be repeated here.

[0048] Furthermore, the most important thing about using the notification management function is to turn on the notification management function of the smartphone. Therefore, after the user installs the application using a mobile phone or other terminal, the user needs to be guided to turn on the notification management function, and then the user will have the permission to manage the notifications of the application.

[0049] Step 102: When the notification monitoring service receives a notification message, it determines whether to store the notification message through the list management operation performed by the user on the sender of the notification message.

[0050] In an example of the present application, after the user installs the application, the mobile terminal such as a smart phone will guide the user to choose whether to add the application to the blacklist. The role of the blacklist here is to reject all notification messages sent by the application, that is, to prohibit the application from popping up notification messages to the user on the terminal. Therefore, the so-called list management operation is to add the application to the blacklist, and / or, to add the application to the whitelist, and / or, to set storage keywords / pop-up keywords for the application. It can be understood that after the storage keyword is set, the notification message carrying the storage keyword will not be displayed. Similarly, after the pop-up keyword is set, the notification message carrying the pop-up keyword will be displayed. In this process, the sender of the above notification message represents the application installed on the mobile terminal that sends the notification message.

[0051] For example, users can manage whitelists and blacklists for all apps on their phones, and notifications from blacklisted apps will not be displayed. Secondly, users can set keywords, and all specified keywords will be collected.

[0052] After the mobile terminal inherits the Android system's notification listening service NotificationListenerService and registers, the notification listening service can always run in the background. The NotificationListenerService service has interfaces for related notification operations, including obtaining all notifications on the notification bar, removing all removable notifications, removing notifications with specified keys, triggering callbacks after the system receives new notifications, and triggering callbacks after system notifications are deleted.

[0053] When a mobile device such as a mobile phone receives a notification message, the system will also send a notification to the notification monitoring service. After that, the notification monitoring service can handle different businesses based on the content of the received notification.

[0054] Specifically, the notification monitoring service will first determine whether the application that sent the notification message is added to the blacklist. If so, the notification message will be directly stored. The so-called storage means that the notification message is stored in a specific storage path and will not be displayed on mobile devices such as mobile phones. If the application that sent the notification message is not added to the blacklist, it is necessary to further determine whether to display the notification message.

[0055] Step 103: If not, match the notification message with the user's usage habits.

[0056] In an example of the present application, when it is determined that the application that sends the notification message has not been added to the blacklist, it is continued to be determined whether there is a keyword in the notification message. If the previously set keyword is a storage keyword, when it is determined that the notification message contains the keyword, the notification message is directly stored. If the previous device keyword is a display keyword, when the notification message contains the display keyword, the notification message is displayed.

[0057] Furthermore, in an example of the present application, when the application that sends the notification message is not added to the blacklist, the notification message can also be matched with the user's usage habits. The so-called user usage habits are obtained by processing and analyzing the user's big data. Specifically, read the notification messages previously collected by the user and the notification messages previously displayed, perform data analysis on the read messages, and obtain notification message analysis data. The notification message analysis data here includes at least: mobile terminal mac address, user information, bounce rate, dwell time, number of triggers, interaction depth, and notification message attributes. Afterwards, the aforementioned notification message analysis data is connected to the data analysis website and analyzed to obtain the user's usage habits, that is, the user portrait.

[0058] For the above-mentioned data analysis websites, you can directly use third-party Sensors data. Sensors is a third-party website that specializes in data mining and analytical insights on big data. You can directly use its SaaS version to push notification message analysis data to Sensors. After a certain amount of data accumulation, you can form a user portrait.

[0059] In an example of the present application, for the control of notifications, after the service is registered (the CustomService mentioned above), the callback of the notification will call the relevant functions in the NotificationListenerService service (see below for details); under the condition of enabling notification management permissions, the Android system has provided relevant functions for operating notifications, including canceling specified notifications and canceling all notifications. The tatusBarNotification class can pass objects in multiple processes, and all notification information will be passed in this class. It can be used to obtain the content of the notification, and then the message content of the notification message is added to the aforementioned notification message analysis data and sent to the data analysis website to analyze the notification content and obtain the user portrait. Of course, it is also possible to analyze the message content of the notification message and match it with the user portrait to determine whether to display the notification message.

[0060] The following are the related methods of the two classes, among which getNotification() can get the Notification object and get the specific information of the notification:

[0061] NotificationListenerService main method (member variable):

[0062] cancelAllNotifications(): Delete all notifications that can be cleared in the system;

[0063] cancelNotification(String pkg,String tag,int id): delete a specific notification;

[0064] getActiveNotifications(): Returns a list of all current system notifications to StatusBarNotification[];

[0065] onNotificationPosted(StatusBarNotification sbn): callback is triggered when the system receives a new notification;

[0066] onNotificationRemoved(StatusBarNotification sbn): callback triggered when the system notification is deleted;

[0067] StatusBarNotification Class

[0068] getId(): returns the id corresponding to the notification;

[0069] getNotification(): returns the notification object;

[0070] getPackageName(): returns the package name corresponding to the notification;

[0071] getPostTime(): returns the time when the notification was initiated;

[0072] getTag(): Returns the Tag of the notification, or null if not set;

[0073] isClearable(): Returns whether the notification can be cleared, FLAG_ONGOING_EVENT, FLAG_NO_CLEAR;

[0074] isOngoing(): Checks whether the notification flag is FLAG_ONGOING_EVENT.

[0075] Step 104: Determine whether to display the notification message based on the matching result.

[0076] After matching the notification message with the user portrait, it can be determined whether to display the notification message based on the matching result, that is, if the two are matched successfully, the notification message will be displayed, and if the two are matched unsuccessfully, the notification message will be stored, that is, the notification message will not be displayed. It should be noted that the aforementioned matching can be to match the message content of the notification message (which can be obtained through the StatusBarNotification class in the service as explained above) with the user portrait, that is, the user usage habits analyzed above. The specific matching process between the two can be achieved through existing matching technology, which will not be elaborated in the embodiments of this application.

[0077] In one or more possible implementation methods of the embodiments of the present application, the main function of the notification message is to quickly open the application page through the notification bar. Its jump is saved through Intent. The fundamental reason for the jump is that the Intent contains the package path and related data of the specified page. Therefore, the package path information associated with the notification message can be obtained through the onNotificationPosted class under the NotificationListenerService service, and then the package path information is saved in the database. As a result, the received notification message can jump to the specified page associated with it and display it by clicking.

[0078] Registration of notification service, CuetomeService service inherits NotificationListenerService service and implements its interface, see below for details, so that CuetomeService service will be called back when receiving notification:

[0079] <service android:name=".CuetomeService"

[0080] android:label="@string / service_name"

[0081] android:permission="android.permission.BIND_NOTIFICATION_LISTENERSERVICE">

[0082] <intent-filter>

[0083] <actionandroid:name="android.service.notification.NotificationListenerServic e" / >

[0084]

[0085]

[0086] In order to provide a more detailed explanation of the technical solutions in the embodiments of the present application, the following supplementary descriptions are also provided in the embodiments of the present application.

[0087] Figure 2 A notification message management operation process diagram provided in an embodiment of the present application. Figure 2 As shown, the operation process is as follows:

[0088] After starting, first call the onNotificationPosted class under the NotificationListenerService service to determine whether the notification message sent by the application is received. Then, determine whether the application is on the whitelist. If not, save the Intent (i.e. data) in the aforementioned notification message, call the system function to cancel the notification, so that the notification bar no longer displays the notification message, but through the onNotificationPosted class, you can open the collected notification message by clicking in the application, and then end.

[0089] Furthermore, if the application that sends the notification message is on the whitelist, it is further determined whether there is a keyword (for example, the keyword here is a display keyword) in the notification message. If not, the data of the notification message is saved and the process ends.

[0090] Furthermore, if the notification message contains keywords that the user wants to be displayed, the notification message will be matched with the user portrait. If the match is successful, the notification message will be released and displayed normally in the notification bar of the mobile terminal. This process ends when the user opens the notification bar and clicks on the notification message.

[0091] Finally, since the notification message management method in the embodiment of the present application takes user portraits into consideration, in the operation process, the collected notification messages and the displayed notification messages can be sorted out and sent to Sensors Data for calculation. After the calculation is completed, the user portrait in the process is fed back to facilitate a more accurate match between the notification message content and the user portrait.

[0092] In addition, based on the same inventive concept, the embodiment of the present application also provides a notification message management device based on user portrait, whose structure is as follows: Figure 3 shown.

[0093] Figure 3 A schematic diagram of the structure of a notification message management device based on user portrait provided in an embodiment of the present application. Figure 3 As shown, the notification message management device 300 in the embodiment of the present application includes:

[0094] The registration module 301 inherits and registers the notification monitoring service from the operating system;

[0095] Determination module 302, when the notification monitoring service receives a notification message, determines whether to store the notification message through the list management operation performed by the user on the sender of the notification message;

[0096] Matching module 303, if not, matching the notification message with the user's usage habits;

[0097] The determination module 302 determines whether to display the notification message according to the matching result.

[0098] In one or more possible implementations of the embodiments of the present application, the device further includes:

[0099] The guiding module 304 guides the user to enable the notification message management function when installing the notification message sender, so that the notification monitoring service obtains the notification message management authority.

[0100] In one or more possible implementations of the embodiment of the present application, the determining module 302,

[0101] According to the stored notification messages and the displayed notification messages, the notification message analysis data is sorted out, and the notification message analysis data at least includes: mobile terminal MAC address, user information, bounce rate, stay time, trigger number, interaction depth and notification message attributes;

[0102] The notification message analysis data is connected to a preset data analysis website to determine the user's usage habits.

[0103] In one or more possible implementations of the embodiments of the present application, the device further includes:

[0104] The acquisition module 305 uses the StatusBarNotification class in the notification monitoring service to acquire the message content of the notification message;

[0105] The message content is added to the notification message analysis data.

[0106] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0107] For the convenience of description, the above devices are described in terms of functions and are divided into various units / modules. Of course, when implementing this specification, the functions of each unit / module can be implemented in the same or multiple software and / or hardware.

[0108] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may be in the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the embodiments of this specification may be in the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0109] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0110] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0111] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0112] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0113] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0114] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims

1. A notification message management method based on user portrait, characterized in that: Applied to a mobile terminal, the method includes: Inherit and register the notification listening service from the operating system, and guide the user to enable the notification message management function when installing the notification message sender, so that the notification listening service obtains the notification message management authority; When the notification monitoring service receives a notification message, determining whether to store the notification message through a list management operation performed by a user on the sender of the notification message; If not, matching the notification message with the user portrait; Determine whether to display the notification message according to the matching result; Before matching the notification message with the user portrait, the method further includes: According to the stored notification messages and the displayed notification messages, the notification message analysis data is sorted out, and the notification message analysis data at least includes: mobile terminal MAC address, user information, bounce rate, stay time, trigger number, interaction depth and notification message attributes; Using the StatusBarNotification class in the notification monitoring service, obtaining the message content of the notification message, and adding the message content to the notification message analysis data; The notification message analysis data is connected to a preset data analysis website to determine the user portrait.

2. A notification message management method based on user portrait according to claim 1, characterized in that: The list management operation performed by the user on the sender of the notification message specifically includes: The notification message sender is added to a blacklist, and / or, the notification message sender is added to a whitelist, and / or, a storage keyword is set for the notification message manager.

3. A notification message management method based on user portrait according to claim 1, characterized in that: The method further comprises: In response to a user clicking on a stored notification message, obtaining a package path of a page associated with the notification message through the onNotificationPosted class in the notification listening service; Open the notification message associated page through the package path.

4. A notification message management device based on user portrait, characterized in that: The device comprises: A registration module inherits and registers the notification monitoring service from the operating system, and guides the user to enable the notification message management function when installing the notification message sender, so that the notification monitoring service obtains the notification message management authority; a determination module, which, when the notification monitoring service receives a notification message, determines whether to store the notification message through a list management operation performed by a user on a sender of the notification message; A matching module, if not, matches the notification message with the user portrait; The determination module determines whether to display the notification message according to the matching result; The determination module collects and obtains notification message analysis data according to the stored notification messages and the displayed notification messages, wherein the notification message analysis data at least includes: mobile terminal MAC address, user information, bounce rate, stay time, trigger number, interaction depth and notification message attributes; An acquisition module, using the StatusBarNotification class in the notification monitoring service, acquires the message content of the notification message, and adds the message content to the notification message analysis data; The notification message analysis data is connected to a preset data analysis website to determine the user portrait.

Images