WO2015176673A1

WO2015176673A1 - Method and device for storing status bar notification, and management handover method and device

Info

Publication number: WO2015176673A1
Application number: PCT/CN2015/079490
Authority: WO
Inventors: 张迪; 马鸣
Original assignee: 北京奇虎科技有限公司; 奇智软件（北京）有限公司
Priority date: 2014-05-22
Filing date: 2015-05-21
Publication date: 2015-11-26

Abstract

A method and a device for storing a status bar notification, and a management handover method and device are disclosed in the present invention. A status bar manager is provided in the application program layer of the operating system. The method for storing a status bar notification comprises: the status bar manager checks whether an application program invokes an interface to send a status bar notification message to the system server processes in the system framework layer; upon determining the application program invokes an interface to send a status bar notification message, said manager retrieves via said interface parameters for the sent status bar notification message; and, performs data conversion on parameters of said message, and stores the converted data. The invention allows for status bar notifications to be saved in the same manner short messages are saved, making it easy to check said notifications.

Description

Method and device for storing status bar notification and method and device for taking over

Technical field

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for storing a status bar notification, and a method and apparatus for taking over a status bar notification.

Background technique

The Android platform has hundreds of millions of users as the world's most popular mobile operating system. Its status bar (notification bar) design is an important innovation in the mobile operating system. Applications can send messages to The system status bar allows users to view status bar notifications simply, easily and quickly.

However, the current status bar design also has shortcomings. The status bar can only save transient messages. If the phone is restarted, or the application that sent the notification is killed, or the user accidentally cancels it, it will cause the status. The column notification will not be restored. Users will have such requirements: important status bar notifications that you want to display can be saved, and some missing status bar notifications can be viewed later.

Summary of the invention

In view of the above problems, the present invention has been made in order to provide a storage method and apparatus for a status bar notification that overcomes the above problems or at least partially solves the above problems, and further provides a method and apparatus for taking over a status bar notification.

According to an aspect of the present invention, a storage method of a status bar notification is provided, and a status bar manager is set in an application layer of an operating system, the method comprising: the status bar manager detecting whether an application calls a system framework The system service process in the layer sends an interface of the status bar notification message; when detecting that the application invokes the interface that sends the status bar notification message, the parameter of the status bar notification message sent through the interface is retrieved; the status bar is notified The parameters of the message are converted into data, and the data after the data conversion is stored.

According to another aspect of the present invention, a storage device for status bar notification is provided, in which a status bar manager is set in an application layer of an operating system, the device comprising: a detecting unit for detecting by the status bar manager Whether the application invokes an interface that sends a status bar notification message to the system service process in the system framework layer; the parameter retrieval unit is configured to: when the detection unit detects that the application invokes the interface that sends the status bar notification message, The parameter of the status bar notification message sent by the interface; the conversion storage unit is configured to perform data conversion on the parameter of the status bar notification message, and store the data after the data conversion.

According to an aspect of the present invention, a method for taking over a status bar notification is provided, in which a status bar takeover service corresponding to a status bar manager in an application layer is set in a system framework layer of an operating system, the method comprising: Determining, in the status bar manager, a filter condition for a status bar notification of an application; the status bar manager providing the filter condition to the status bar takeover service; the status bar taking over service to a system user interface process Sending a status bar notification display command indicating that the system user interface process only displays satisfaction The status bar notification of the filter condition.

According to another aspect of the present invention, a status bar notification receiving device is provided, in which a status bar takeover service corresponding to a status bar manager in an application layer is set in a system framework layer of an operating system, the device comprising: a filter condition determining unit, configured to determine, in the status bar manager, a filter condition for a status bar notification of an application; a filter condition providing unit, configured to provide the filter condition to the status bar takeover service; And a control unit, configured to send, by using the status bar takeover service, a status bar notification display command to the system user interface process, to instruct the system user interface process to display only the status bar notification that satisfies the filtering condition.

According to an aspect of the invention there is also provided a computer program comprising computer readable code, when said computer readable code is run on a terminal device, causing said terminal device to perform a status bar as described in any of the above A storage method of the notification, or a takeover method that causes the terminal device to perform the status bar notification as described in any of the above.

According to another aspect of the present invention, there is also provided a computer readable medium storing a computer program as described above.

It can be seen that, in the storage method of the status bar notification provided by the present invention, the API call of the status bar notification message is sent to the system server process by the detection application (app), so that the parameter of the status bar notification message is retrieved and passed. The data conversion method implements storage of status bar notifications. Preferably, selective storage of status bar notifications for a particular application can be implemented by setting storage conditions. The invention enables the status bar notification to be saved like a text message and can be viewed at any time.

The above description is only an overview of the technical solutions of the present invention, and the above-described and other objects, features and advantages of the present invention can be more clearly understood. Specific embodiments of the invention are set forth below.

DRAWINGS

Various other advantages and benefits will become apparent to those skilled in the art from a The drawings are only for the purpose of illustrating the preferred embodiments and are not to be construed as limiting. Throughout the drawings, the same reference numerals are used to refer to the same parts. In the drawing:

Figure 1 shows a schematic diagram of the implementation of the status bar;

2 is a schematic diagram showing a storage system architecture of a status bar notification according to an embodiment of the present invention;

FIG. 3 is a flow chart showing a storage method of a status bar notification according to an embodiment of the present invention.

4 is a schematic diagram showing the architecture of a takeover system notified by a status bar according to an embodiment of the present invention;

Figure 5 illustrates a flow chart of a takeover method for status bar notifications in accordance with one embodiment of the present invention.

Figure 6 shows schematically a block diagram of a terminal device for carrying out the method according to the invention;

Fig. 7 schematically shows a storage unit for holding or carrying program code implementing the method according to the invention.

Specific embodiment

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the embodiments of the present invention have been shown in the drawings, the embodiments Rather, these embodiments are provided so that this disclosure will be more fully understood and the scope of the disclosure will be fully disclosed.

As described above, in view of the problem that the status bar notification cannot be saved in the prior art, the present invention enables the status bar notification to be saved like a short message and can be viewed at any time.

Those skilled in the art understand that the operating system includes an application layer (app layer) and a system framework layer (framework layer), and other layers that may be included from the functional division are not discussed in the present invention. Among them, usually the app layer can be understood as the upper layer, which is responsible for interacting with the user, such as application (app, software) maintenance, and identifying different kinds of click content when the page is clicked to display different context menus and the like. Usually the framework layer acts as the middle layer. The main responsibility of this layer is to forward the user requests obtained by the app layer, such as launching the application, clicking the link, clicking to save the image, etc., and forwarding it to the lower layer; Or distribute it to the upper layer through a message or through an intermediate proxy class to present it to the user.

A preferred implementation of the present invention is to improve the app layer and the framework layer, thereby implementing a status bar message storage scheme by utilizing the cooperation of the two layers. Specifically, a status bar manager may be added at the app layer, and the status bar manager stores the status bar notification according to the set storage policy, for example, notifying the status bar of the more important application set by the user. Store to achieve the purpose of saving important status bar notifications. Through the invention, the physical storage of the status bar notification can be realized, which is convenient for the user to view.

In order to better understand the present invention, the principle and architecture of the status bar of android are first introduced.

Those skilled in the art understand that the basis of the entire android framework is a service running in the system server process. Among them, NotificationManagerService (Notification Management Service) and NotificationManager (Notification Management) are the services responsible for managing and notifying the background events, that is, the services that implement the status bar notification. There are two classes that must be used to send a status bar notification: NotificationManager and Notification. Among them, NotificationManager is the management class of the status bar notification, responsible for sending notifications, clearing notifications, and so on. NotificationManager is a system Service (service) that must be obtained by the getSystemService() method. Notification is a specific status bar notification object. You can set parameters such as icon (icon format), text, prompt sound, and vibration. For example, the basic parameters required to set up a notification include: An icon (notified icon); A title and expanded message; A PendingIntent; optional parameters include: A Ticker-text message (message message at the top of the status bar); An alert sound; A vibrate setting; A flashing LED setting.

Creating and displaying a Notification requires the following five steps:

1. Get a NotificationManager object through the getSystemService method.

2. Create a Notification object. Each Notification corresponds to a Notification object. In this step, you need to set the notification message displayed in the status bar at the top of the screen, the image resource ID in front of the notification message, and the time when the notification is sent.

3. Because Notification can be detached from the application. This means that Notification will still appear in the status bar even if the application is closed. Once the application is launched again, you can regain control of these Notifications. Such as clearing or replacing them. Therefore, you need to create a PendingIntent object. This object is maintained by the Android system, so the object will still not be released after the application is closed.

4. Use the setLatestEventInfo method of the Notification class to set the details of the Notification.

5. Use the notify method of the NotificationManager class to display the Notification message. In this step you need to specify a unique ID that identifies the Notification.

See Figure 1 for a schematic diagram of the status bar implementation. First, the application of the app layer sends a status bar notification to the NotificationManagerService of the framework layer through the NotificationManager.notify method; then, in the NotificationManagerService, the status bar notification entry sent by the application is saved in the list; finally, the NotificationManagerService passes the StatusBar.addNotification( The method sends a display status bar notification to the SystemUi (system user interface) process where the system status bar is located, so that the status bar notification sent by the application is displayed in the system status bar. In FIG. 1, only one application is used as an example in the app layer. It can be understood that, in the case of a mobile phone, for example, a plurality of applications may be displayed to display a status bar notification.

As can be seen from Figure 1, from the creation of a notification by the app to the display of the notification in the system status bar, the processing and relaying of the NotificationManagerService in the system_server process of the framework layer is required, and finally the SystemUi is responsible for displaying. In the present invention, through the android injection technology, through the status bar manager of the app layer, the API call of the status bar notification message sent by the app to the sysytem server is detected, the parameters of the status bar notification are retrieved from the middle, and the status bar notification is implemented by using the storage technology. Storage.

FIG. 2 is a schematic structural diagram of a storage system notified by a status bar according to an embodiment of the present invention.

Compared with the system described in FIG. 1, the main reason is to increase the status bar manager running in the app layer, the status bar manager detects the calling API of the application to the NotificationManagerService in the system server process, and transmits the status bar notification message copy of the transmission. One copy and stored in a physical file such as a disk. It can be understood that the status bar manager does not interfere with the original status bar notification mechanism, only the parameters notified by the status bar are copied and stored. Among them, the status bar manager can be understood as an application-implemented function, such as a function in the 360 security guards.

The following describes how to store and restore a Notification parameter. As already mentioned, the application constructs a Notification entity class when it sends a status bar notification message to indicate a notification to be displayed. The more important parameters required to set up a Notification include: display view and click execution page jump, where clicking the execution page jump can also be called post-click behavior.

The display view of the status bar notification is implemented via RemoteViews (remote view). Those skilled in the art understand that in the constructor of the RemoteViews, the "view of the layout file (RemoteViews)" is obtained by passing in the id of the layout file; then, the method in the RemoteViews can be called to set the components in the layout (for example, , you can call setTextViewText () to set the TextView component The text, you can call setOnClickPendingIntent () to set the Button's click response event), so you can think of RemoteViews as a collection of all the views contained in the layout file. RemoteViews is a serializable object. In the embodiment of the present invention, the RemoteViews are serialized to obtain a byte stream, and then the byte stream is stored in a physical file such as a disk to implement permanent storage. Serializable is the process of writing the state of an object to a byte stream. In short, serialization is to save the state of the object, and the saved object state can be read out again. In this way, when you need to view the status bar, you can read it from the disk, then deserialize it into a RemoteViews object, and then construct the View object through the apply method, and finally display the display view of the status bar notification. Among them, the apply method is a javascript function, which is a method of hijacking another object, inheriting the attributes of another object.

The click execution page jump of the status bar notification is implemented by PendingIntent. The PendingIntent itself is not serializable, but the event handler maintained by the ActvityManagerService. The handle actually corresponds to an Intent object, which can be persisted. Those skilled in the art understand that the Intent table diagram, Pending represents an upcoming event or an upcoming event. The PendingIntent class is used to handle what is going to happen. For example, in Notification Notification, it is used to jump to the page, but not immediately. The Intent is started in time, and the Intent disappears with the disappearance of the activity (one of the Android components). PendingIntent can be regarded as a wrapper for the Intent. Usually, getPliveIntent is obtained through getActivity, getBroadcast, getService. The current activity can't start the Intent it contains immediately. Instead, it calls Intent when executing PendingIntent externally. Just because the PendingIntent holds the Context of the current App, it gives the external App a capability that allows the external App to execute the Intent in the PendingIntent just like the current App, even if the current App does not exist at the time of execution. The Intent can be executed by the Context in the PendingIntent. In addition, you can also handle the operation after the Intent is executed. Therefore, it can be understood that PendingIntent is a description of the Intent, which can be passed to other processes, and other processes do Intent scheduling at a later time according to this description. In the embodiment of the present invention, by persisting the Intent object, the PendingIntent can be used instead to implement the click execution page jump. Persistence is the preservation of data (such as objects) into a permanently stored storage device (such as a disk).

The status bar notification is important or not. It is of course important for the important status bar to inform the user that it can be stored for later viewing, and vice versa for unimportant status bar notifications. In the embodiment of the present invention, the notification item of the specific application is stored according to the storage condition set in advance, so that only the status bar notification of the application(s) can be selectively stored. Specifically, the status bar manager of the app layer may provide an interface for setting a storage condition to the user, and store a status bar notification of the application that satisfies the storage condition according to the storage condition. This scenario uses the way the user sets the application to which the status bar notifications are to be saved, and selects which status bar notifications to persist which applications to save. In addition, the status bar manager may also pre-fetch a list of applications that need to store the Notification and provide it to the user for reference when setting the storage conditions. The list of applications can be obtained through the configuration of the cloud server. Cloud servers are based on a large number of sample operations and The artificial intelligence method is configured, including sandboxing, static code analysis, dynamic code feature scanning, etc., so it has the advantages of large and accurate samples. Of course, you can also use the default list of applications in the status bar manager without additional user settings.

After the status bar notification storage is implemented, the user can be provided with a stored status bar notification through the display interface, so that the user can view it when necessary. As described above, after the status bar message is converted into a physical file such as a disk by data conversion by the status bar manager, a notification viewing interface can be provided in the status bar manager when the user opens or logs in. The interface displays the stored status bar notifications to the user.

In addition, status bar notifications may contain sensitive data content and need to be considered for encrypted storage. Specifically, after obtaining the parameters of the status bar notification and serializing or persisting, the status bar manager encrypts the serialized or persistent data, and then stores the encrypted data in a physical file such as a disk. When the encrypted data is read, the encryption key corresponding to the encryption key is used for decryption. The embodiment of the present invention does not limit the encryption algorithm. For example, a popular encryption algorithm such as DES (Data Encryption Standard) algorithm, 3DES (Triple DES) algorithm, RC2 and RC4 symmetric algorithm, and IDEA (Intellational Data Encryption Algorithm) international data may be used. Encryption algorithm, RSA algorithm, etc.

FIG. 3 is a flowchart of a method for storing a status bar notification according to an embodiment of the present invention. Wherein, the status bar manager is set in the application layer (app layer) of the operating system, and the method includes:

S301: The status bar manager detects whether the application invokes an interface that sends a status bar notification message to a system server process in the system framework layer;

For example, through the android injection technology, through the status bar manager of the app layer, the API call of the status bar notification message sent by the app to the NotificationManagerService in the sysytem server process is detected.

S302: When detecting that the application invokes the interface that sends the status bar notification message, the parameter of the status bar notification message sent through the interface is retrieved;

S303: Perform data conversion on the parameter of the status bar notification message, and store the data after the data conversion.

Data transfer is the process of changing data from one representation to another. In the embodiment of the present invention, data conversion includes, but is not limited to, serialization and persistence. The purpose of data conversion is to obtain a data form that can be used for storage in a physical file.

As already described, the parameters of the more important status bar notification message include two: display view parameters, click to execute page jump parameters. The process of displaying the view parameters is: serializing the remote view (RemoteViews) object that implements the display view to get the byte stream, and then storing the byte stream in the physical file; when you need to view the status bar notification, from the physical The byte stream is read from the file, and the byte stream is deserialized into a RemoteViews object, and then the display view is constructed according to the RemoteViews object. The process of clicking and executing the page jump parameter is: obtaining an intent object corresponding to an upcoming event (PendingIntent) object that implements a click execution page jump, and persisting the Intent object.

In addition to the above steps, preferably, the step of setting the storage condition may be further included to enable selective storage of the status bar notification of the specific application according to the storage condition. Specifically, in the status bar manager The storage condition for the status bar notification of the application is determined; wherein the status bar manager stores only the status bar notification of the application that satisfies the storage condition according to the storage condition. The storage condition may be set in various manners, for example, receiving a user setting manner to determine a storage condition, or pre-acquiring a list of applications that need to store a status bar notification to determine a storage condition. Of course, the user setting and the application list may be combined. Use, that is, provide a list of pre-acquired applications to the user for reference, and the user finalizes the storage conditions after setting. Among them, the application list is preferably obtained from the cloud server.

It should be noted that the foregoing embodiment of the present invention is described by taking the andriod system as an example. However, it should be understood that the solution of the present invention is applied to an intelligent terminal, particularly an intelligent mobile terminal. Therefore, the embodiment of the present invention can be adapted to Based on the Linux kernel operating system, not just the android operating system.

It can be seen that, in the storage method of the status bar notification provided by the present invention, by detecting that the app sends an API call of the status bar notification message to the system server process, the parameter of the status bar notification message is retrieved, and the serialization or persistent mode is implemented. The storage of status bar notifications. Preferably, selective storage of status bar notifications for a particular application can be implemented by setting storage conditions. The invention enables the status bar notification to be saved like a text message and can be viewed at any time.

Corresponding to the above method, the present invention also provides a storage device for status bar notification. The device can be implemented by hardware, software or a combination of software and hardware. The device may refer to a functional module inside the terminal, or may refer to the smart terminal itself, as long as the smart terminal includes functions for implementing the device.

The storage device notified by the status bar is used for an operating system of the smart terminal, and the operating system includes an application layer and a system framework layer, wherein a status bar manager is set in an application layer of the operating system, and the device includes: detecting a unit, configured to detect, by the status bar manager, whether an application invokes an interface that sends a status bar notification message to a system service process in a system framework layer; a parameter retrieval unit, configured to: when the detection unit detects an application call When the interface of the status bar notification message is sent, the parameter of the status bar notification message sent through the interface is retrieved; the conversion storage unit is configured to perform data conversion on the parameter of the status bar notification message, and the data is converted. The data is stored.

The conversion storage unit is specifically configured to: serialize parameters of the status bar notification message, or/and persist the parameters of the status bar notification message, and serialize and/or persist. After the data is stored.

In one case, when the parameter of the status bar notification message includes a display view parameter, the conversion storage unit is specifically configured to serialize a remote view object that implements the display view to obtain a byte stream, and then use a word stream. The throttle is stored in a physical file. The method may further include: a viewing unit, configured to read the byte stream from the physical file when the status bar notification needs to be viewed, and deserialize the byte stream into a remote view object, and then deserialize according to the deserialization The resulting remote view object constructs a display view.

In another case, when the parameter of the status bar notification message includes a click execution page jump parameter, the conversion storage unit is specifically configured to acquire an intent object corresponding to an upcoming event object that implements the click execution page jump. , persisting the intent object.

Preferably, the device further comprises: a storage condition determining unit, configured to determine the pin in the status bar manager The storage condition notified to the status bar of the application; at this time, the conversion storage unit stores only the status bar notification of the application that satisfies the storage condition according to the storage condition. Further, the device further includes: an application list obtaining unit, configured to pre-acquire a list of applications that need to store a status bar notification for the status bar manager; at this time, the conversion storage unit is configured according to the application list To determine the storage criteria for the application's status bar notifications. Further, the device further includes: a storage setting unit, configured to provide a storage condition setting interface to the user by using the status bar manager, and receive a storage setting of the status bar notification by the user. The application list is obtained from a cloud server.

Preferably, the device further includes: a notification viewing unit, configured to provide a notification viewing interface for viewing the stored status bar notification, and display the stored status bar notification to the user through the notification viewing interface.

Preferably, the device further includes: an encryption unit, configured to encrypt the serialized or persistent data; at this time, the conversion storage unit is configured to store the encrypted data.

In addition, Android's status bar (notification bar) gives users some malicious adware to take advantage of while viewing the message. Some malicious adwares even include some normal software that frequently pops up multiple status bar messages. If the user does not clean up in time, the status bar will have dozens of status bar messages at the same time, most of which are useless messages to the user, which has seriously disturbed the user. .

In view of the problem that the user is disturbed by too many status bar messages in the prior art, the present invention proposes a takeover scheme of status bar notification, which can greatly reduce the disturbance caused by the useless status bar notification to the user, and does not make the user lose important. Status bar notification.

A preferred implementation of the present invention is to improve the app layer and the framework layer, thereby utilizing the synergy of the two layers to implement a status bar message takeover solution. Specifically, a system service called a status bar takeover service may be added in the framework layer, and the status bar takeover service filters the status bar notification according to the notification item filtering policy set by the status layer manager of the app layer, for example, maliciously The application's status bar notifications are filtered, and only the status bar notifications after filtering are displayed, and the useless status bar notifications do not bother the user. In addition, preferably, the notification management service of the framework layer is invoked through the status bar manager of the app layer, thereby achieving the purpose of viewing all status bar notifications. It can be seen that, by the present invention, only the filtered status bar notification is displayed when the status bar notification is displayed, thereby reducing the disturbance to the user. Also, when the user needs to view all status bar notifications, all status bar notifications can be viewed through the status bar manager.

As can be seen from Figure 1, from the creation of a notification by the app to the display of the notification in the system status bar, the processing and relaying of the NotificationManagerService in the system_server process of the framework layer is required, and finally the SystemUi is responsible for displaying. In the present invention, by the android injection technology, the status bar takeover service corresponding to the app layer status bar manager is added in the framework layer, which is equivalent to running a specific code in the system_server process, and then replacing the handle sent to the SystemUi command, thereby Selectively blocking the NotificationManagerService to send a status bar display command to the sytemUi process to achieve the purpose of taking over the status bar.

FIG. 4 is a schematic structural diagram of a takeover system notified by a status bar according to an embodiment of the present invention.

The status bar notification takeover implementation is divided into two major parts. The first part is the status bar takeover service added in the framework layer. It runs in the system_server process and is used to filter the status bar notification entries according to the preset conditions, so that only the status bar notification after filtering is displayed in the system status bar. That is, through the code injection method, the status bar takeover service detects that the system server process calls the status bar to notify the display of the interface (API), and the status bar takes over the service to call the interface, thereby sending a status bar notification display command to the SystemUi process, only Show status bar notifications that meet the filter criteria. The second part is the status bar manager running in the app layer. By calling the NotificationManagerService, for example, calling the NotificationManagerService via the GetAllNotifications method, it can be used to view all current status bar notification lists, including the status bar notification items that are hidden in the system status bar. It can be understood that the status bar takeover service and the status bar manager are corresponding, and it can be understood that the background part of the status bar takes over and the user interface part, and the two operate in cooperation. On the one hand, the status bar manager determines the filter condition of the status bar notification, and provides the filter condition to the status bar to take over the service; on the other hand, the status bar manager calls the NotificationManagerService in the system_server process to obtain and display the list saved in the NotificationManagerService. All status bar notifications. Among them, the status bar manager can be understood as an application-implemented function, such as a function in the 360 security guards.

Wherein, in the status bar takeover service of the first part, the notification item is filtered according to the preset filter condition, so that only the status bar notification of some (application) applications can be selectively taken over. Specifically, the status bar manager of the app layer can provide the user with an interface for setting the filtering condition, and provide the status bar takeover service after the user setting is completed. For example, the user can select certain IM (instant messaging) software and online banking software to be whitelisted applications, and the status bar notifications of these applications can still be sent to the system status bar normally. Users can also select certain software as blacklisted applications, and status bar notifications for these blacklisted applications will not be sent to the system status bar. Of course, users can also use a combination of whitelist and blacklist. The whitelist of the application or the blacklist of the application can be pre-fetched by the status bar manager and provided to the user, so that the user can refer to when setting the filtering condition. For example, a blacklist or a whitelist is configured on the cloud server to obtain a whitelist of applications or a blacklist of applications. Because the cloud solution is based on a large number of sample operations and artificial intelligence methods, including sandboxing, static code analysis, dynamic code feature scanning, etc., it has the advantages of large and accurate samples. Of course, you can also use the default whitelist or / and blacklist of the status bar manager directly, without user settings.

FIG. 5 is a flowchart of a method for taking over a status bar notification according to an embodiment of the present invention. The status bar takeover service corresponding to the status bar manager in the application layer (app layer) is set in the system framework layer (framework layer) of the operating system, and the method includes:

S501: determining, in the status bar manager, a filter condition for the status bar notification of the application;

As described earlier, the status bar manager can provide a setting interface to the user, and the user sets the filtering conditions, for example, setting a status bar notification that allows some applications to be displayed, and setting a status bar notification that prohibits displaying other applications. . In the specific implementation, it can be combined with the pre-acquired application whitelist to allow display A status bar notification for the application in the application whitelist. Similarly, it is also possible to combine the pre-acquired application blacklist to prohibit the display of the status bar notification of the application in the application blacklist. Of course, application whitelists and application blacklists can be combined. Users can make adjustments based on the default application whitelist and/or application blacklist, or they can use the default method directly. The application whitelist or the application blacklist is obtained as described above and can be obtained from the cloud server.

S502: The status bar manager provides the filter condition to the status bar takeover service;

As mentioned above, the status bar manager and the status bar takeover service are two parts of the app layer and the framework layer respectively implementing the status bar of the present invention, and the two operate in cooperation. After the status bar manager determines the status bar notification filter, the filter condition is sent to the status bar takeover service. Of course, it is not excluded that the status bar takes over the service or directly obtains the implementation of the filter condition.

S503: The status bar takeover service sends a status bar notification display command to the system user interface (SystemUi) process, instructing the system user interface (SystemUi) process to display only the status bar notification that satisfies the filtering condition on the smart terminal.

Before step S503, the status bar takeover service is required to replace the NotificationManagerService in the system server process in the prior art to call the SystemUi process. Specifically, the SystemUi process is not called by the NotificationManagerService, but is detected by the code injection mode, and the status bar takeover service detects The system server process invokes the status bar to notify the interface (API) that displays the command, which is invoked by the status bar takeover service to send a status bar notification display command to the SystemUi process. The notification display command instructs the SystemUi process to display the status bar notification that satisfies the filtering condition only on the smart terminal, thereby filtering the malicious notification or reducing the notification interference problem.

In addition to the above three steps, preferably, in order to facilitate the user to view all status bar notifications as necessary, the status bar manager provides the user with the ability to view status bar notifications. As mentioned earlier, after the application at the app layer sends a status bar notification message to the system server process, the NotificationManagerService in the system server process is responsible for creating a Notification and saving the Notification in the status bar notification list. The present invention does not interfere with this step, that is, the NotificationManager requests will still create and save the notifications requested by all applications, and the present invention only takes over when the subsequent call to the SystemUi process, so that only the notification after filtering is displayed. Since the notification requested by all applications is still created and saved in the NotificationManagerService, the status bar notification list can be obtained by calling the NotificationManagerService through the status bar manager, so that all status bar notifications can be displayed to the user. Specifically, the notification display interface is convenient for the user to view all status bar notifications. As described above, the status bar manager invokes the notification management service in the system framework layer to obtain a status bar notification list saved in the notification management service; then displays all status bar notifications in the list to the user through the notification display interface.

It can be seen that, in the method for taking over the status bar notification provided by the present invention, only the status bar notification that satisfies the filtering condition is displayed by controlling the SystemUi process, and the status bar notification that does not satisfy the filtering condition is not displayed, thereby greatly reducing the More or malicious application status bar notifications, reducing interference to users. The setting of the filtering condition may be selected by the application whitelist and/or blacklist mode, and only the status bar notification of the specific application may be selected for display, and the status bar notification is not performed for the application whose history is blacklisted. display. In addition, the ability to view all status bar notifications provided by the status bar manager makes it easy for users to view all status bar notifications and avoid the loss of important status bar notifications.

Corresponding to the above method, the present invention also provides a takeover device for status bar notification. The device can be implemented by hardware, software or a combination of software and hardware. The device may refer to a functional module inside the terminal, or may refer to the smart terminal itself, as long as the smart terminal includes functions for implementing the device.

The takeover device notified by the status bar is used for an operating system of the smart terminal, wherein a status bar takeover service corresponding to the status bar manager in the application layer is set in a system framework layer of the operating system, and the device includes: filtering a condition determining unit, configured to determine, in the status bar manager, a filter condition for a status bar notification of an application; a filter condition providing unit, configured to provide the filter condition to the status bar takeover service; and notify display control And a unit, configured to send, by using the status bar takeover service, a status bar notification display command to the system user interface process, to instruct the system user interface process to display only the status bar notification that satisfies the filtering condition on the smart terminal.

Preferably, the apparatus further includes: a status bar notification display unit, configured to invoke, by the status bar manager, the notification management service in the system framework layer to obtain a status bar notification list saved by the notification management service; The status bar manager is used to display all status bar notifications in the list to the user.

Preferably, the apparatus further comprises: a notification management service unit, configured to receive, by the notification management service, a status bar notification message sent by one or more application programs, and save the received status bar notification message in a status bar notification list in.

Preferably, the device further includes: a system user interface process takeover unit, configured to detect, by means of code injection, an interface of the system service process calling status bar to notify the display command, wherein the interface is invoked by the status bar to take over the interface, thereby enabling The notification display control unit sends a status bar notification display command to the system user interface process.

Preferably, the apparatus further includes: an application list obtaining unit, configured to pre-acquire an application whitelist or/and an application blacklist for the status bar manager; the filtering condition determining unit is configured according to the application whitelist Or / and the application blacklist to determine the filter criteria for the application's status bar notifications. The method further includes a filtering condition setting unit, configured to provide a filtering condition setting interface to the user through the status bar manager, and receive a filtering setting of the status bar notification by the user. The application whitelist or/and the application blacklist are obtained from the cloud server.

Preferably, the device further includes: a notification viewing unit, configured to provide a notification viewing interface, and display, by the notification viewing interface, all status bar notifications in the status bar notification list to the user.

Preferably, the operating system comprises a Linux kernel based operating system for a smart mobile terminal, For example, the operating system is an Andriod operating system.

It can be seen that, in the method for taking over the status bar notification provided by the present invention, only the status bar notification that satisfies the filtering condition is displayed through the control system user interface process, and the status bar notification that does not satisfy the filtering condition is not displayed, thereby greatly Reduce the status bar notifications for excessive or malicious applications, reducing interference to users. The setting of the filtering condition may be selected by the application whitelist and/or blacklist mode, and only the status bar notification of the specific application may be selected for display, and the status bar notification is not performed for the application whose history is blacklisted. display. In addition, the ability to view all status bar notifications provided by the status bar manager makes it easy for users to view all status bar notifications and avoid the loss of important status bar notifications.

The algorithms and displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general purpose systems can also be used with the teaching based on the teachings herein. The structure required to construct such a system is apparent from the above description. Moreover, the invention is not directed to any particular programming language. It is to be understood that the invention may be embodied in a variety of programming language, and the description of the specific language has been described above in order to disclose the preferred embodiments of the invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that the embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of the description.

Similarly, the various features of the invention are sometimes grouped together into a single embodiment, in the above description of the exemplary embodiments of the invention, Figure, or a description of it. However, the method disclosed is not to be interpreted as reflecting the intention that the claimed invention requires more features than those recited in the claims. Rather, as the following claims reflect, inventive aspects reside in less than all features of the single embodiments disclosed herein. Therefore, the claims following the specific embodiments are hereby explicitly incorporated into the embodiments, and each of the claims as a separate embodiment of the invention.

Those skilled in the art will appreciate that the modules in the devices of the embodiments can be adaptively changed and placed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and further they may be divided into a plurality of sub-modules or sub-units or sub-components. In addition to such features and/or at least some of the processes or units being mutually exclusive, any combination of the features disclosed in the specification, including the accompanying claims, the abstract and the drawings, and any methods so disclosed, or All processes or units of the device are combined. Each feature disclosed in this specification (including the accompanying claims, the abstract and the drawings) may be replaced by alternative features that provide the same, equivalent or similar purpose.

In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features that are included in other embodiments and not in other features, combinations of features of different embodiments are intended to be within the scope of the present invention. Different embodiments are formed and formed. For example, in the following claims, any one of the claimed embodiments can be used in any combination.

Various component embodiments of the present invention may be implemented in hardware or on one or more processors The software module implementation of the line, or a combination of them. Those skilled in the art will appreciate that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the status bar notification storage device and the status bar notification takeover device in accordance with an embodiment of the present invention. Some or all of the features of the part. The invention can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein. Such a program implementing the invention may be stored on a computer readable medium or may be in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

For example, FIG. 6 shows a terminal device that can implement the storage method of the status bar notification or the takeover method of the status bar notification according to the present invention. The terminal device conventionally includes a processor 610 and a computer program product or computer readable medium in the form of a memory 620. The memory 620 may be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), an EPROM, a hard disk, or a ROM. Memory 620 has a memory space 630 for program code 631 for performing any of the method steps described above. For example, storage space 630 for program code may include various program code 631 for implementing various steps in the above methods, respectively. The program code can be read from or written to one or more computer program products. These computer program products include program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks. Such a computer program product is typically a portable or fixed storage unit as described with reference to FIG. The storage unit may have a storage section, a storage space, and the like arranged similarly to the storage 620 in the terminal device of FIG. The program code can be compressed, for example, in an appropriate form. Typically, the storage unit comprises computer readable code 631', ie code that can be read by a processor, such as 610, which when executed by the terminal device causes the terminal device to perform each of the methods described above step.

"an embodiment," or "an embodiment," or "an embodiment," In addition, it is noted that the phrase "in one embodiment" is not necessarily referring to the same embodiment.

It is to be noted that the above-described embodiments are illustrative of the invention and are not intended to be limiting, and that the invention may be devised without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as a limitation. The word "comprising" does not exclude the presence of the elements or steps that are not recited in the claims. The word "a" or "an" The invention can be implemented by means of hardware comprising several distinct elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means can be embodied by the same hardware item. The use of the words first, second, and third does not indicate any order. These words can be interpreted as names.

In addition, it should also be noted that the language used in this specification is primarily for readability and teaching. It is chosen for the purpose, and is not chosen to explain or define the subject matter of the invention. Therefore, many modifications and changes will be apparent to those skilled in the art without departing from the scope of the invention. The disclosure of the present invention is intended to be illustrative, and not restrictive, and the scope of the invention is defined by the appended claims.

Claims

A method for storing a status bar notification, characterized in that a status bar manager is set in an application layer of an operating system, the method comprising:

The status bar manager detects whether an application invokes an interface that sends a status bar notification message to a system service process in the system framework layer;

When detecting that the application invokes the interface that sends the status bar notification message, the parameter of the status bar notification message sent through the interface is retrieved;

The parameters of the status bar notification message are data-converted, and the data-converted data is stored.
The method of claim 1, wherein said converting data of said status bar notification message comprises: serializing parameters of said status bar notification message, or/and, said state The parameters of the column notification message are persisted.
The method of claim 2, wherein the parameter of the status bar notification message comprises displaying a view parameter; serializing the remote view object implementing the display view to obtain a byte stream, and then storing the byte stream In the physical file.
The method of claim 3, further comprising: reading the byte stream from the physical file when the status bar notification needs to be viewed, and deserializing the byte stream into a remote view object And construct a display view based on the deserialized remote view object.
The method of claim 2, wherein the parameter of the status bar notification message comprises clicking to execute a page jump parameter; and acquiring an intent object corresponding to an upcoming event object that implements the click execution page jump, The intent object is persisted.
The method of claim 1 further comprising:

Determining storage conditions for the application's status bar notifications in the status bar manager;

The status bar manager stores only the status bar notification of the application that satisfies the storage condition according to the storage condition.
The method of claim 6 further comprising:

The status bar manager obtains in advance a list of applications that need to store a status bar notification;

The status bar manager determines a storage condition for the status bar notification of the application based on the application list.
The method of claim 6 further comprising:

The status bar manager provides a storage condition setting interface to the user, and receives the storage setting of the status bar notification by the user.
The method of claim 8 wherein said list of applications is obtained from a cloud server.
The method of claim 1 further comprising:

Providing a notification viewing interface for viewing the stored status bar notification;

The stored status bar notification is displayed to the user through the notification viewing interface.
The method according to any one of claims 1 to 10, further comprising: before storing the serialized or persistent data, further comprising:

Encrypt data after serialization or persistence.
The method of any of claims 1 to 10, wherein the operating system comprises a Linux kernel based operating system for a smart mobile terminal.
The method of claim 12 wherein said operating system is an Andriod operating system.
A storage device for status bar notification, characterized in that a status bar manager is set in an application layer of an operating system, the device comprising:

a detecting unit, configured to detect, by the status bar manager, whether an application invokes an interface that sends a status bar notification message to a system service process in a system framework layer;

a parameter retrieval unit, configured to: when the detecting unit detects an interface that the application invokes the status bar notification message, retrieve a parameter of the status bar notification message sent by using the interface;

The conversion storage unit is configured to perform data conversion on the parameter of the status bar notification message, and store the data after the data conversion.
The device according to claim 14, wherein the conversion storage unit is specifically configured to serialize parameters of the status bar notification message, or/and to persist parameters of the status bar notification message. And serialize and/or persist the data for storage.
The device according to claim 15, wherein the parameter of the status bar notification message comprises a display view parameter; the conversion storage unit is specifically configured to serialize a remote view object that implements the display view to obtain a word Throttling, and then storing the byte stream in a physical file.
The apparatus according to claim 16, further comprising: a viewing unit, configured to read the byte stream from the physical file and deserialize the byte stream when the status bar notification needs to be viewed Transform into a remote view object, and then construct a display view based on the deserialized remote view object.
The device according to claim 14, wherein the parameter of the status bar notification message comprises a click execution page jump parameter; the conversion storage unit is specifically configured to obtain an upcoming occurrence of the click execution page jump An intent object corresponding to the event object, and the intent object is persisted.
The device of claim 14 further comprising:

a storage condition determining unit, configured to determine, in the status bar manager, a storage condition for a status bar notification of the application;

The storage unit stores only the status bar notification of the application that satisfies the storage condition according to the storage condition.
The device of claim 19, further comprising:

An application list obtaining unit, configured to pre-fetch the required status bar for the status bar manager a list of known applications;

The storage unit determines a storage condition for the status bar notification of the application according to the application list.
The device of claim 19, further comprising:

And a storage setting unit, configured to provide a storage condition setting interface to the user by using the status bar manager, and receive a storage setting of the status bar notification by the user.
The apparatus of claim 21 wherein said list of applications is obtained from a cloud server.
The device of claim 14 further comprising:

The notification viewing unit is configured to provide a notification viewing interface for viewing the stored status bar notification, and display the stored status bar notification to the user through the notification viewing interface.
The apparatus according to any one of claims 14 to 23, further comprising: an encryption unit configured to encrypt the serialized or persistent data; and the storage unit is configured to perform the encrypted data storage.
The apparatus of any one of claims 14 to 23, wherein the operating system comprises a Linux kernel based operating system for a smart mobile terminal.
The apparatus of claim 25 wherein said operating system is an Andriod operating system.
A method for taking over a status bar notification, characterized in that a status bar takeover service corresponding to a status bar manager in an application layer is set in a system framework layer of an operating system, the method comprising:

Determining, in the status bar manager, a filter condition for a status bar notification of an application;

The status bar manager provides the filter condition to the status bar takeover service;

The status bar takeover service sends a status bar notification display command to the system user interface process, instructing the system user interface process to display only status bar notifications that satisfy the filter condition.
The method of claim 26, further comprising:

The status bar manager invokes a notification management service in the system framework layer to obtain a status bar notification list saved in the notification management service;

The status bar manager displays to the user all status bar notifications in the list.
The method of claim 28, wherein before the status bar takeover service sends a status bar notification display command to the system user interface process, the method further includes:

The notification management service receives a status bar notification message sent by one or more applications and saves the received status bar notification message in a status bar notification list.
The method of claim 27, wherein before the status bar takeover service sends a status bar notification display command to the system user interface process, the method further includes:

Through the code injection method, detecting that the system service process calls the status bar to notify the display of the interface, and the status bar takes over the interface, thereby sending a status bar notification display to the system user interface process. command.
The method of claim 27, further comprising:

The status bar manager obtains an application whitelist or/and an application blacklist in advance;

The status bar manager determines a filter condition for the status bar notification of the application based on the application whitelist or/and the application blacklist.
The method of claim 31, further comprising:

The status bar manager provides a filter condition setting interface to the user, and receives a filtering setting of the status bar notification by the user.
The method of claim 31 wherein said application whitelist or/and application blacklist is obtained from a cloud server.
The method of claim 27, wherein said status bar takes over the service, runs a particular code in the system service process, and then replaces a handle to send a command to the system user interface process, thereby selectively blocking notification management The service sends a status bar display command to the system user interface process to achieve the purpose of taking over the status bar.
The method of claim 27, further comprising:

Provide a notification viewing interface;

Through the notification viewing interface, the user is presented with all status bar notifications in the status bar notification list.
The method of any of claims 27 to 35, wherein the operating system comprises a Linux kernel based operating system for a smart mobile terminal.
The method of claim 36 wherein said operating system is an Andriod operating system.
A takeover device for status bar notification, characterized in that a status bar takeover service corresponding to a status bar manager in an application layer is set in a system framework layer of an operating system, the device comprising:

a filter condition determining unit, configured to determine, in the status bar manager, a filter condition for a status bar notification of the application;

a filter providing unit for providing the filter condition to the status bar takeover service;

The notification display control unit is configured to use the status bar takeover service to send a status bar notification display command to the system user interface process, instructing the system user interface process to display only the status bar notification that satisfies the filtering condition.
The device of claim 38, further comprising:

a status bar notification display unit, configured to invoke a notification management service in the system framework layer by using the status bar manager, acquire a status bar notification list saved in the notification management service; and use the status bar manager to The user displays all status bar notifications in the list.
The device of claim 39, wherein the device further comprises:

The notification management service unit is configured to receive, by the notification management service, a status bar notification message sent by one or more applications, and save the received status bar notification message in the status bar notification list.
The device of claim 38, further comprising:

a system user interface process takeover unit, configured to detect, by means of code injection, an interface of the system service process call status bar notification display command, wherein the interface is invoked by the status bar takeover service, so that the notification display control unit is to the system The user interface process sends a status bar notification to display the command.
The device of claim 38, further comprising:

An application list obtaining unit, configured to pre-acquire an application whitelist or/and an application blacklist for the status bar manager;

The filter condition determining unit determines a filter condition for the status bar notification of the application according to the application whitelist or/and the application blacklist.
The device of claim 42 further comprising:

The filter condition setting unit is configured to provide a filter condition setting interface to the user through the status bar manager, and receive a filtering setting of the status bar notification by the user.
The apparatus of claim 42, wherein the application whitelist or/and application blacklist is obtained from a cloud server.
38. The apparatus of claim 38, wherein the status bar takes over a service, runs a particular code in a system service process, and then replaces a handle to send a command to a system user interface process, thereby selectively blocking notification management The service sends a status bar display command to the system user interface process to achieve the purpose of taking over the status bar.
The device of claim 38, further comprising:

The notification viewing unit is configured to provide a notification viewing interface, and display, by using the notification viewing interface, all status bar notifications in the status bar notification list to the user.
The apparatus of any of claims 38 to 46, wherein the operating system comprises a Linux kernel based operating system for a smart mobile terminal.
The apparatus of claim 47, wherein the operating system is an Andriod operating system.
A computer program comprising computer readable code, when the computer readable code is run on a terminal device, causing the terminal device to perform a storage method of the status bar notification according to any one of claims 1-13 Or a takeover method causing the terminal device to perform the status bar notification according to any one of claims 27-37.
A computer readable medium storing the computer program of claim 49.