CN105653903B - The management method and device of application program permission - Google Patents

Abstract

The disclosure is directed to the management methods and device of a kind of application program permission, wherein the management method of application program permission includes: to be monitored to the front and back switching state of current application program；If monitoring, current application program by being switched to foreground from the background, is cancelled current application program permission and is limited；If monitoring, current application program is switched to backstage by foreground, obtains the behavioural information of current application program, and limitation is limited current application program permission or cancelled according to behavioural information.The embodiment of the present disclosure, it can decide whether to limit current application program permission according to the behavioural information of current application program, substantially increase limitation accuracy rate, so as in the case where not influencing normal use application program, reduce mobile terminal system load, improve mobile terminal response speed and battery performance.

Description

Method and device for managing application program permissions

technical field

The present disclosure relates to the technical field of mobile terminals, and in particular to a method and device for managing application rights.

Background technique

In the smart phone system, the background of the application program has many permissions such as networking and global positioning system (GPS). The application program can use these permissions to enrich its functions, but multiple applications use these permissions in disorder, such as using it to carry out Pushing advertisements will cause the background load of the entire mobile phone system to not be released for a long time, reduce the overall response performance and battery performance of the mobile phone, generate frequent advertisement pushes, and affect the user experience.

In order to reduce the background load of the mobile phone system, it can be realized by closing the permissions of some background applications at present. However, this method will affect the normal functions of some applications.

Contents of the invention

In order to overcome the problems existing in related technologies, the present disclosure provides a method and device for managing application rights.

According to the first aspect of the embodiments of the present disclosure, a method for managing application rights is provided, including:

Monitor the front and back switching status of the current application;

If it is detected that the current application program is switched from the background to the foreground, the current application program permission is canceled;

If it is detected that the current application program is switched from the foreground to the background, the behavior information of the current application program is obtained, and the permission of the current application program is restricted or canceled according to the behavior information.

In an embodiment, the acquiring the behavior information of the current application, and restricting or canceling the restriction on the permission of the current application according to the behavior information includes:

Start a preset timer, and record the notification behavior of the current application program before the timer expires;

If the notification behavior is not recorded when the timed time arrives, restrict the current application permissions;

If the notification behavior is recorded when the timer arrives, continue to start the timer, and execute the notification behavior of recording the current application before the timer arrives until the timer arrives The described notification behavior is not documented.

In an embodiment, the not recording the notification behavior when the timing time arrives includes:

When the timing time arrives, it is not detected that the current application program sends out the notification behavior; and/or

When the timing time arrives, it is detected that all the notification behaviors sent by the current application are deleted.

In an embodiment, the restricting the current application program permissions includes:

Canceling at least one of the networking permission and the location permission for the current application program.

In one embodiment, the notification behavior includes a notification log.

According to the second aspect of the embodiments of the present disclosure, there is provided an application permission management device, including:

The monitoring module is configured to monitor the switching state of the front and back of the current application program;

Determine the unrestriction module, configured to cancel the restriction on the current application program authority if the monitoring module detects that the current application program is switched from the background to the foreground;

The determination processing module is configured to obtain behavior information of the current application program if the monitoring module detects that the current application program is switched from the foreground to the background program, and restrict or limit the permissions of the current application program according to the behavior information Lift restrictions.

In one embodiment, the determination processing module includes:

Start the recording submodule, configured to start a preset timer, and record the notification behavior of the current application program before the timer expires;

The determination restriction submodule is configured to restrict the current application program authority if the start recording submodule does not record the notification behavior when the timing time arrives;

Determine the call submodule, configured to call the start record submodule to continue to start the timer if the start recording submodule records the notification behavior when the timing time arrives, and execute the timer at the timing Recording the notification behavior of the current application program before the time is up, until the notification behavior is not recorded when the timing time is up.

In one embodiment, the determining restriction submodule includes:

The first determining unit is configured to not detect that the current application program sends the notification behavior when the timing time arrives; and/or

The second determining unit is configured to detect that all notifications sent by the current application are deleted when the timing time arrives.

In one embodiment, the determining restriction submodule includes:

The restricting unit is configured to cancel at least one of networking permission and location permission for the current application program.

In one embodiment, the notification behavior includes a notification log.

According to a third aspect of the embodiments of the present disclosure, there is provided an application permission management device, including:

processor;

memory for storing processor-executable instructions;

where the processor is configured as:

Monitor the front and back switching status of the current application;

If it is detected that the current application program is switched from the background to the foreground, the current application program permission is canceled;

If it is detected that the current application program is switched from the foreground to the background, the behavior information of the current application program is obtained, and the permission of the current application program is restricted or canceled according to the behavior information.

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects: By monitoring the switching state of the current application program from the background to the foreground, and canceling the restriction on the current application program permissions when the current application program is switched from the background to the foreground, the current When the application is switched from the foreground to the background, the behavior information of the current application is obtained, and the permissions of the current application are restricted or canceled according to the behavior information, so that in the implementation process, it is possible to decide whether to The current application permissions are restricted, which greatly improves the accuracy of the restriction, so that the system load of the mobile terminal can be reduced, and the response speed and battery performance of the mobile terminal can be improved without affecting the normal use of the application.

By recording the notification behavior of the current application program, and when the notification behavior is recorded, continue to monitor the notification behavior of the current application program, and when the notification behavior is not recorded, the current application program permissions are restricted, and the implementation process is simple. And the accuracy of the restriction on application permissions is high.

It provides a basis for restricting the current application permissions by identifying two cases where notification behavior is not recorded when the timed time is reached.

Describes the content of restricting the current application permissions, and the restricted permissions are flexible and diverse.

Describe the content of the notification behavior, making the implementation clearer and easier to implement.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description serve to explain the principles of the invention.

Fig. 1 is a flow chart showing a method for managing application rights according to an exemplary embodiment.

Fig. 2 is a flow chart showing another application permission management method according to an exemplary embodiment.

Fig. 3 is a block diagram of an apparatus for managing application rights according to an exemplary embodiment.

Fig. 4 is a block diagram of another device for managing application rights according to an exemplary embodiment.

Fig. 5 is a block diagram of another device for managing application rights according to an exemplary embodiment.

Fig. 6 is a block diagram of another device for managing application rights according to an exemplary embodiment.

Fig. 7 is a block diagram showing a device suitable for managing application rights according to an exemplary embodiment.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with aspects of the invention as recited in the appended claims.

Fig. 1 is a flowchart of a method for managing application rights according to an exemplary embodiment. As shown in Fig. 1, the method for managing application rights can be applied to a mobile terminal, and the method includes the following steps S101- S103:

In step S101, the switching state of the current application program is monitored.

In this embodiment, the current application program can run on a mobile terminal, which can be a mobile phone with different operating systems, such as an Android (Android) mobile phone, an Apple mobile phone, and the like.

When the mobile terminal is an Android phone, the phone can register a listener based on the Activity Manager Service (AMS) provided by the Android system, and monitor the front-background switching status of the current application through the listener.

Wherein, the front-background switching state of the current application program may include two states: switching from the background to the foreground and switching from the foreground to the background.

In step S102, if it is detected that the current application program is switched from the background to the foreground, the restriction on the authority of the current application program is cancelled.

In this embodiment, if it is detected that the current application program is switched from the background to the foreground, it indicates that the user needs the current application program to run normally, and therefore needs to cancel the restriction on the permission of the current application program.

In step S103, if it is detected that the current application is switched from the foreground to the background, the behavior information of the current application is obtained, and the permission of the current application is restricted or canceled according to the behavior information.

In this embodiment, if it is detected that the current application program is switched from the foreground to the background, it is impossible to determine whether the user needs the current application program to run normally. At this time, it is necessary to obtain the behavior information of the current application program, and decide whether to Current application permissions are restricted.

In the embodiment of the management method of the above-mentioned application program authority, by monitoring the front-background switching state of the current application program, and when the current application program is switched from the background to the foreground, the current application program authority is removed from the restriction, and when the current application program is switched from the foreground When going to the background, obtain the behavior information of the current application program, and restrict or cancel the restriction on the current application program permissions according to the behavior information, so that in the implementation process, it can be determined whether to restrict the current application program permissions based on the current application program's behavior information. The limitation greatly improves the accuracy of the limitation, so that it can reduce the system load of the mobile terminal and improve the response speed and battery performance of the mobile terminal without affecting the normal use of the application program.

Fig. 2 is a flow chart of another application permission management method according to an exemplary embodiment. As shown in Fig. 2, the method includes the following steps:

In step S201, the switching state of the current application program is monitored.

In step S202, it is determined whether the current application is switched from the foreground to the background, if yes, execute step S203, otherwise, cancel the restriction on the authority of the current application.

In step S203, a preset timer is started, and the notification behavior of the current application is recorded before the timer expires.

Wherein, the notification behavior may include a notification log.

In this embodiment, a timer of 5 minutes can be preset, and the notification behavior of the current application program can be recorded before the timer expires.

It should be noted that the timing of the timer can be set as required, and 5 minutes is just an example, and it can also be 7 minutes, 10 minutes, etc.

In step S204, it is judged whether a notification behavior is recorded when the timer arrives, if no notification behavior is recorded, execute step S205, and if a notification behavior is recorded, execute step S203.

In step S205, restrict the current application program permissions.

In this embodiment, if no notification behavior is recorded, it indicates that the current application program is in an inactive state, therefore, the current application program authority can be restricted. If the notification behavior is recorded, it indicates that the current application program is active, and the notification behavior of the current application program still needs to be monitored, so turn to step S203 until no notification behavior is recorded.

In this embodiment, the notification behavior that is not recorded when the scheduled time arrives may include the following two situations:

The first case: when the scheduled time arrives, the notification behavior of the current application is not detected.

The second case: when the scheduled time arrives, it is detected that all the notification behaviors sent by the current application are deleted. That is, the current application has issued notifications, but all of them have been deleted by the user.

In this embodiment, restricting the permission of the current application program may include, but not limited to, canceling at least one of the networking permission and the location permission for the current application program.

In the above embodiments of the management method for application program permissions, by recording the notification behavior of the current application program, and when the notification behavior is recorded, the notification behavior of the current application program is continuously monitored; when the notification behavior is not recorded, the current application program Application program permissions are restricted, the implementation process is simple, and the accuracy of application program permissions is high.

Corresponding to the aforementioned embodiment of the method for managing application rights, the present disclosure also provides embodiments of an apparatus for managing application rights.

Fig. 3 is a block diagram of a device for managing application rights according to an exemplary embodiment. As shown in Fig. 3 , the device for managing application rights includes: a monitoring module 31, a determination cancel restriction module 32 and a determination processing module 33 .

The monitoring module 31 is configured to monitor the switching state of the current application program.

In this embodiment, the current application program can run on a mobile terminal, which can be a mobile phone with different operating systems, such as an Android (Android) mobile phone, an Apple mobile phone, and the like.

When the mobile terminal is an Android phone, the monitoring module 31 can register a listener (listener) based on the component management service (ActivityManagerService, AMS) provided by the Android system, and monitor the front-background switching status of the current application program through the listener.

Wherein, the front-background switching state of the current application program may include two states: switching from the background to the foreground and switching from the foreground to the background.

The determination to cancel the restriction module 32 is configured to cancel the restriction on the permission of the current application program if the monitoring module 31 detects that the current application program is switched from the background to the foreground.

In this embodiment, if it is detected that the current application program is switched from the background to the foreground, it indicates that the user needs the current application program to run normally, and therefore needs to cancel the restriction on the permission of the current application program.

The determination processing module 33 is configured to obtain the behavior information of the current application program if the monitoring module 31 detects that the current application program is switched from the foreground to the background program, and restrict or cancel the restriction on the current application program authority according to the behavior information.

In this embodiment, if it is detected that the current application program is switched from the foreground to the background, it is impossible to determine whether the user needs the current application program to run normally. At this time, it is necessary to obtain the behavior information of the current application program, and decide whether to Current application permissions are restricted.

The device shown in FIG. 3 is used to implement the above-mentioned method flow shown in FIG. 1 , and the relevant content involved is described in the same way, and will not be repeated here.

The embodiment of the management device of the above-mentioned application program authority monitors the front-background switching state of the current application program, and cancels the restriction on the current application program authority when the current application program is switched from the background to the foreground, and when the current application program is switched from the foreground When going to the background, obtain the behavior information of the current application program, and restrict or cancel the restriction on the current application program permissions according to the behavior information, so that in the implementation process, it can be determined whether to restrict the current application program permissions based on the current application program's behavior information. The limitation greatly improves the accuracy of the limitation, so that it can reduce the system load of the mobile terminal and improve the response speed and battery performance of the mobile terminal without affecting the normal use of the application program.

Fig. 4 is a block diagram of another application permission management device shown according to an exemplary embodiment. As shown in Fig. 4, on the basis of the above-mentioned embodiment shown in Fig. 3, the determination processing module 33 may include: The submodule 331 , the determination restriction submodule 332 and the determination calling submodule 333 .

The start recording sub-module 331 is configured to start a preset timer, and record the notification behavior of the current application program before the timer expires.

Wherein, the notification behavior may include a notification log.

In this embodiment, a timer of 5 minutes can be preset, and the notification behavior of the current application program can be recorded before the timer expires.

It should be noted that the timing of the timer can be set as required, and 5 minutes is just an example, and it can also be 7 minutes, 10 minutes, etc.

The determination restriction sub-module 332 is configured to restrict the current application program authority if the start-up recording sub-module 331 does not record the notification behavior when the timer time arrives.

Determine that the calling submodule 333 is configured such that if the start record submodule 331 records the notification behavior when the timer arrives, then call the start record submodule to continue to start the timer, and perform the notification behavior of recording the current application before the timer arrives, No notification behavior is recorded until the timed time is reached.

In this embodiment, if no notification behavior is recorded, it indicates that the current application program is in an inactive state, therefore, the current application program authority can be restricted. If the notification behavior is recorded, it indicates that the current application program is in an active state, and the notification behavior of the current application program can be continuously monitored by calling the sub-module until no notification behavior is recorded.

The device shown in FIG. 4 is used to implement the above-mentioned method flow shown in FIG. 2 , and related content is described in the same way, and will not be repeated here.

The above-mentioned embodiment of the management device for application rights records the notification behavior of the current application program, and when the notification behavior is recorded, continues to monitor the notification behavior of the current application program, and when the notification behavior is not recorded, the current application program Application program permissions are restricted, the implementation process is simple, and the accuracy of application program permissions is high.

Fig. 5 is a block diagram of another device for managing application rights according to an exemplary embodiment. As shown in Fig. 5 , on the basis of the above-mentioned embodiment shown in Fig. 4 , the determining restriction submodule 332 may include: At least one of the first determining unit 3321 and the second determining unit 3322.

The first determining unit 3321 is configured to detect that the current application does not send a notification when the timeout arrives.

The second determining unit 3322 is configured to detect that all notifications sent by the current application are deleted when the timeout arrives.

The device shown in FIG. 5 is used to implement the above-mentioned method flow shown in FIG. 2 , and the relevant content involved is described in the same way and will not be repeated here.

In the embodiment of the above-mentioned application rights management device, the first determination unit and the second determination unit determine the two situations that no notification behavior is recorded when the timer arrives, so as to provide a basis for restricting the current application rights.

Fig. 6 is a block diagram of another application permission management device according to an exemplary embodiment. As shown in Fig. 6, on the basis of the above-mentioned embodiment shown in Fig. 4, the determining restriction submodule 332 may include: restricting Unit 3323.

The restricting unit 3323 is configured to cancel at least one of the networking permission and the location permission for the current application program.

The device shown in FIG. 6 is used to implement the above-mentioned method flow shown in FIG. 2 , and related content is described in the same way, and will not be repeated here.

In the above embodiments of the management apparatus for application program rights, the restricting unit describes the content of restricting the current application program rights, and the restricted rights are flexible and diverse.

Regarding the apparatus in the above embodiments, the specific manner in which each module and sub-module performs operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Fig. 7 is a block diagram showing a device suitable for managing application rights according to an exemplary embodiment. For example, the apparatus 700 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, an aircraft, and the like.

7, device 700 may include one or more of the following components: processing component 702, memory 704, power supply component 706, multimedia component 708, audio component 710, input/output (I/O) interface 712, sensor component 714, and communication component 716 .

The processing component 702 generally controls the overall operations of the device 700, such as those associated with display, telephone calls, data communications, camera operations, and recording operations. The processing element 702 may include one or more processors 720 to execute instructions to complete all or part of the steps of the above method. Additionally, processing component 702 may include one or more modules that facilitate interaction between processing component 702 and other components. For example, processing component 702 may include a multimedia module to facilitate interaction between multimedia component 708 and processing component 702 .

Memory 704 is configured to store various types of data to support operations at device 700 . Examples of such data include instructions for any application or method operating on device 700, contact data, phonebook data, messages, pictures, videos, and the like. The memory 704 can be realized by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.

Power component 706 provides power to various components of device 700 . Power components 706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for device 700 .

The multimedia component 708 includes a screen that provides an output interface between the device 700 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or swipe action, but also detect duration and pressure associated with the touch or swipe action. In some embodiments, the multimedia component 708 includes a front camera and/or a rear camera. When the device 700 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.

The audio component 710 is configured to output and/or input audio signals. For example, the audio component 710 includes a microphone (MIC), which is configured to receive external audio signals when the device 700 is in operation modes, such as call mode, recording mode and voice recognition mode. Received audio signals may be further stored in memory 704 or sent via communication component 716 . In some embodiments, the audio component 710 also includes a speaker for outputting audio signals.

The I/O interface 712 provides an interface between the processing component 702 and a peripheral interface module, which may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.

Sensor assembly 714 includes one or more sensors for providing various aspects of status assessment for device 700 . For example, the sensor component 714 can detect the open/closed state of the device 700, the relative positioning of components, such as the display and keypad of the device 700, and the sensor component 714 can also detect a change in the position of the device 700 or a component of the device 700 , the presence or absence of user contact with the device 700 , the device 700 orientation or acceleration/deceleration and the temperature change of the device 700 . Sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. Sensor assembly 714 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 714 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

The communication component 716 is configured to facilitate wired or wireless communication between the apparatus 700 and other devices. The device 700 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 716 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 716 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, apparatus 700 may be programmed by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the methods described above.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as the memory 704 including instructions, which can be executed by the processor 720 of the device 700 to implement the above method. For example, the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

Other embodiments of the disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, and these modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure . The specification and examples are to be considered exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It should be understood that the present disclosure is not limited to the precise constructions which have been described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (9)

1. A method for managing application rights, characterized in that the method comprises: Monitor the front and back switching status of the current application; If it is detected that the current application program is switched from the background to the foreground, the current application program permission is canceled; If it is detected that the current application is switched from the foreground to the background, the behavior information of the current application is obtained, and the permissions of the current application are restricted or canceled according to the behavior information, and the behavior information is used to indicate the current the application is active or inactive; The acquiring the behavior information of the current application program, and restricting or canceling the restriction on the permission of the current application program according to the behavior information includes: Start a preset timer, and record the notification behavior of the current application program before the timer expires; If the notification behavior is not recorded when the timed time arrives, restrict the current application permissions; If the notification behavior is recorded when the timer arrives, continue to start the timer, and execute the notification behavior of recording the current application before the timer arrives until the timer arrives The described notification behavior is not documented. 2. The method for managing application rights according to claim 1, wherein the notification behavior not being recorded when the timer arrives comprises: When the timing time arrives, it is not detected that the current application program sends out the notification behavior; and/or When the timing time arrives, it is detected that all the notification behaviors sent by the current application are deleted. 3. The method for managing application rights according to claim 1, wherein said restricting said current application rights comprises: Canceling at least one of the networking permission and the location permission for the current application program. 4. The method for managing application rights according to any one of claims 1-3, wherein the notification behavior includes a notification log. 5. A device for managing application rights, characterized in that the device comprises: The monitoring module is configured to monitor the switching state of the front and back of the current application program; Determine the unrestriction module, configured to cancel the restriction on the current application program authority if the monitoring module detects that the current application program is switched from the background to the foreground; The determination processing module is configured to obtain behavior information of the current application program if the monitoring module detects that the current application program is switched from the foreground to the background program, and restrict or limit the permissions of the current application program according to the behavior information Cancel the restriction, the behavior information is used to indicate that the current application is active or inactive; The determination processing module includes: Start the recording submodule, configured to start a preset timer, and record the notification behavior of the current application program before the timer expires; The determination restriction submodule is configured to restrict the current application program authority if the start recording submodule does not record the notification behavior when the timing time arrives; Determine the call submodule, configured to call the start record submodule to continue to start the timer if the start recording submodule records the notification behavior when the timing time arrives, and execute the timer at the timing Recording the notification behavior of the current application program before the time is up, until the notification behavior is not recorded when the timing time is up. 6. The application program rights management device according to claim 5, characterized in that, the determination restriction submodule comprises: The first determining unit is configured to not detect that the current application program sends the notification behavior when the timing time arrives; and/or The second determining unit is configured to detect that all notifications sent by the current application are deleted when the timing time arrives. 7. The device for managing application rights according to claim 5, wherein the determining and restricting submodule comprises: The restricting unit is configured to cancel at least one of networking permission and location permission for the current application program. 8. The apparatus for managing application rights according to any one of claims 5-7, wherein the notification behavior includes a notification log. 9. A device for managing application rights, comprising: processor; memory for storing processor-executable instructions; Wherein, the processor is configured as: Monitor the front and back switching status of the current application; If it is detected that the current application program is switched from the background to the foreground, the current application program permission is canceled; If it is detected that the current application is switched from the foreground to the background, the behavior information of the current application is obtained, and the permissions of the current application are restricted or canceled according to the behavior information, and the behavior information is used to indicate the current the application is active or inactive; The acquiring the behavior information of the current application program, and restricting or canceling the restriction on the permission of the current application program according to the behavior information includes: Start a preset timer, and record the notification behavior of the current application program before the timer expires; If the notification behavior is not recorded when the timed time arrives, restrict the current application permissions; If the notification behavior is recorded when the timer arrives, continue to start the timer, and execute the notification behavior of recording the current application before the timer arrives until the timer arrives The described notification behavior is not documented.