WO2020015656A1

WO2020015656A1 - Mobile terminal and permission management method and device for application program

Info

Publication number: WO2020015656A1
Application number: PCT/CN2019/096211
Authority: WO
Inventors: 李静
Original assignee: 奇酷互联网络科技（深圳）有限公司
Priority date: 2018-07-17
Filing date: 2019-07-16
Publication date: 2020-01-23
Also published as: CN109241765B; CN109241765A

Abstract

Disclosed by the present invention are a mobile terminal and a permission management method and device for an application program, wherein the method comprises: obtaining a permission retrieval instruction for the application program; reading, according to the permission retrieval instruction, permissions corresponding to the application program and forming the permissions into a permission management list, wherein switches for controlling each permission are provided in the permission management list; and displaying the permission management list at a specified position in a form of a floating window. According to the present application, when the permission of an application program is subjected to management, it is unnecessary to enter a setting interface of a system, and the permission corresponding to the application program is directly mapped to a permission management list and displayed in a form of a floating window, so that a user can complete permission setting of the application program in the floating window. Thus, the permission setting speed of the application program is improved, the process required for the user to set the permission of the application program is reduced, the time of the user is saved and the user experience is improved.

Description

Method and device for managing rights of mobile terminal and application program

[Technical Field]

The present invention relates to the field of computers, and in particular, to a method and device for managing rights of a mobile terminal and an application program.

【Background technique】

In the past, we set the application's network permissions, database access permissions, camera usage permissions, etc., which need to be entered from different entrances in the settings, and it is necessary to find the relevant permission entries multiple times for operation, which is very complicated. So how to easily and quickly set the access permissions of the application is an urgent problem.

[Summary of the Invention]

The main purpose of the present invention is to provide a method and a device for managing the permissions of a mobile terminal and an application, which are aimed at solving the problem that when setting permissions of an application in the prior art, it is necessary to enter a specific setting interface for setting, and the setting process takes time.

The invention proposes a method for managing the authority of an application, which includes:

Obtaining a permission call instruction for the application;

Reading the permissions corresponding to the application according to the permission calling instruction, and forming the permissions into a permission management list, wherein a switch for controlling each permission is set in the permission management list;

Displaying the rights management list in the form of a floating window at a specified position.

Further, the step of obtaining a permission call instruction for the application program includes:

Before opening the application program, determining whether the entry information of the application program has received a trigger operation of permission call;

If yes, the authority call instruction is generated.

Further, the step of displaying the rights management list in the form of a floating window at a specified position includes:

Determine the first position of the entry information of the application on the system desktop;

Displaying the rights management list in the form of a floating window at a second position close to or overlapping the first position.

Further, the step of displaying the permission management list in the form of a floating window at a specified position includes:

Displaying the rights management list in the form of a floating window at the bottom of the system desktop.

After opening the application, obtaining a first permission that the application needs to be opened / closed according to a user's operation instruction;

Generate a permission call instruction that calls the first permission.

Further, after the application is opened, the step of obtaining the first permission that the application needs to be opened / closed according to a user's operation instruction includes:

After opening the application, executing the operation instruction of the user, and determining whether the operation instruction can be normally executed;

If the execution fails, determine whether the reason for the failure is that the corresponding first authority is not enabled / disabled;

If it can be executed normally, the step of generating a permission call instruction that calls the first permission is performed.

Further, after the step of displaying the rights management list in the form of a floating window at a specified position, the method includes:

Generating a recovery command when the application is closed;

According to the restoration command, the authority operation set in the floating window is restored.

Judging the use frequency of the application program in the foreground of the system;

If the use frequency is less than a preset frequency threshold, generating a recovery command when the application is closed;

Further, the step of reading the permissions corresponding to the application includes:

Find the installation package of the application;

Obtaining attributes and functions of the application from the installation package;

Read multiple permissions that need to be opened or closed when the application is executed according to the attributes and functions.

Obtaining basic functions of the application;

A first right corresponding to the basic function is obtained from the right management list, and the first right corresponding to the basic function is displayed in a specified window in the form of a floating window.

Further, the step of displaying the permission management list in the form of a floating window at a specified position further includes:

Obtaining a specific function triggered by the application;

Obtain a second right corresponding to the specific function from the right management list, and display the second right corresponding to the specific function in a specified window in the form of a floating window.

This application also provides a permission management device for an application, including:

An obtaining unit, configured to obtain a permission call instruction for the application program;

The reading forming unit is configured to read the permission corresponding to the application according to the permission call instruction, and form the permission into a permission management list, wherein a switch for controlling each permission is set in the permission management list. ;

A display unit is configured to display the rights management list in a floating window in a specified position.

Further, the obtaining unit includes:

A first determining module, configured to determine whether the entry information of the application program has received a triggering operation of permission call before opening the application program;

A first generating module is configured to generate the permission call instruction if the trigger operation is received.

Further, the display unit includes:

A second determining module, configured to determine a first position of the entry information of the application on a system desktop;

A display module, configured to display the permission management list in the form of a floating window at a second position close to or overlapping the first position.

Further, the obtaining unit includes:

An obtaining module, configured to obtain a first permission that the application needs to be opened / closed according to a user's operation instruction after the application is opened;

The second generating module is configured to generate a permission call instruction for invoking the first permission.

This application also provides a mobile terminal, including a processor and a memory,

The memory is configured to store a program that implements a permission management device of the application to execute the permission management method of the application according to any one of the foregoing;

The processor is configured to execute a program stored in the memory.

The mobile terminal and the permission management method and device of the application of this application, when managing the permission of an application, there is no need to first enter the system setting interface, and then find the application and click the application to enter its corresponding The permission management interface is used to set the permissions, but the permissions corresponding to the application are directly mapped to a permission management list and displayed in the form of a floating window, so that users can complete the permission setting of the application in the floating window to improve Speed of setting permissions for applications, reducing the processes required for users to set permissions for applications, saving users time, and improving user experience.

[Brief Description of the Drawings]

FIG. 1 is a schematic flowchart of an application program permission management method according to an embodiment of the present invention; FIG.

2 is a schematic block diagram of a structure of an authority management device for an application according to an embodiment of the present application;

FIG. 3 is a schematic block diagram of a mobile terminal according to an embodiment of the present application.

The realization of the purpose, functional characteristics and advantages of the present invention will be further explained with reference to the embodiments and the drawings.

【detailed description】

It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

Referring to FIG. 1, an embodiment of the present application provides a method for managing a permission of an application, which includes steps:

S1. Obtain a permission call instruction for the application;

S2. Read the permissions corresponding to the application according to the permission call instruction, and form the permissions into a permission management list, where a switch for controlling each permission is set in the permission management list;

S3. Display the rights management list in the form of a floating window at a specified position.

As described in step S1 above, the permission call command is a permission management command generated when the mobile terminal on which the application is installed receives a specified operation by the user, or when a permission setting is required due to the user operation. The above-mentioned mobile terminal is an electronic device such as a mobile phone or a tablet computer that can execute an application program.

As described in step S2 above, after obtaining the permission call command, the system of the mobile terminal will find the installation package of the application according to the unique information such as the package name of the application, and then parse out the attributes and functions of the application , And then read out the various permissions that the application may need to open or close during execution. Different applications may have different permissions. For example, navigation applications include GPS permissions, network permissions, voice broadcast permissions, and WeChat applications include network permissions, camera permissions, and so on. In this embodiment, all permissions corresponding to the application can be read. You can also read out some permissions based on the user ’s usage habits. For example, each time a user opens an application, certain permissions are set, and only these permissions are read. The read permissions are mapped to a permission management list, which is convenient for users to handle. The above permission switch is generally the opening permission or the closing permission.

As mentioned in step S3 above, the floating window is a window suspended above the current interface, so that users can directly set permissions in the floating window, greatly reducing the user's process of setting application permissions and improving settings. Efficiency, improve user rights management experience. In this embodiment, when the above application program is reset in the floating window, it will be synchronized to the setting interface, that is, after the setting interface is opened, the permission setting of the application is consistent with the setting in the floating window.

In order to further facilitate the user's operation, it also includes the following determination process: determine the basic function of the application, and display the first permission closely related to the basic function of the application during the initial opening process; for example, start navigation software, such as For Gaode maps, etc., if you need to obtain the current location information, you need to open the “location” permission. When the user opens the basic function of the application, the “location” permission is used as a closely related first permission in the application. After opening it, it is highlighted; subsequent triggering of a specific function in the application; this specific function belongs to the scene permissions in a certain application scenario, and as a second permission, is temporarily displayed for the user to choose, for example, using Gaode map as For example, when the camera needs to be called, the camera permission switch is temporarily displayed in suspension for the user to choose; subsequently, when the user closes the relevant specific function, the second permission is turned off; at the same time, the second permission switch is turned off Set to two states, permanent on and temporary on; When the second permission switch is called for the second time, it is displayed to the user; this prevents the first user from turning on the second permission, and the second time the user wants to turn on the second permission switch, the user is given a choice of temporarily or permanently .

This method can show the user the most important permission control related to the use of the basic function of the application when the user first opens the application; then, when the user occasionally calls the corresponding specific function, the specific function is corresponding The second permission switch is temporarily provided to the user; and when the user turns on the second permission switch for the second time, the user is given the option to temporarily or permanently enable the permission; both the implementation of the application function and the actual user are considered. demand.

In one embodiment, the above-mentioned step S1 of obtaining a permission call instruction for the application program includes:

S101. Before opening the application program, determine whether the entry information of the application program has received a trigger operation of permission call;

S102. If yes, generate the permission call instruction.

In this embodiment, the permission obtaining instruction is obtained before the application is opened. The specific obtaining method is to perform a specified operation on the entry information of the application, so that the system knows which application permission to read, etc. . The triggering operation of the foregoing permission retrieval includes multiple types, for example, the time for pressing the entry information of the application program is greater than a preset time threshold; or the pressure for pressing the entry information of the application program is greater than a preset pressure threshold.

In this embodiment, the above-mentioned step S3 of displaying the authority management list in the form of a floating window at a specified position includes:

S31. Determine the first position of the entry information of the application on the system desktop;

S32. Display the rights management list in the form of a floating window at a second position close to or overlapping the first position.

In this embodiment, the above floating window will be suspended on the system desktop because no application is currently open. At this time, for the convenience of operation, first obtain the entry information at the first position on the system desktop, and then set the floating window at Close to the first position or at a second position overlapping the first position. In a specific embodiment, when the floating window is disposed on one side of the first position, the floating window is further provided with a mark or the like pointing to its corresponding application program.

In another real time, the floating window is displayed on the bottom of the mobile terminal, which is convenient for users to perform one-handed operation. Further, it is also determined which hand the user is holding the mobile terminal, and a floating window is set at the bottom of the system desktop of the mobile terminal, leaning to the side holding the hand of the mobile terminal, and so on.

S111. After opening the application, according to a user operation instruction, obtain a first permission that the application needs to be opened / closed;

S112. Generate a permission call instruction to call the first permission.

In this embodiment, the permission obtaining instruction is obtained after the application is opened. The specific obtaining method is whether the user's operation instruction can be executed normally. If it cannot be executed normally, it is judged that it cannot be executed normally. Whether it is because the corresponding first permission is not turned on / off, and if so, a permission call instruction that calls the first permission is generated, so as to put the first permission in the permission management list, and then in the form of a floating window It is displayed on the current interface. There is no need for the user to put the application into the background to run or directly jump to the setting interface to set the first permission. In a specific embodiment, a user opens a navigation application to view a route, because a large amount of map information is cached in the mobile terminal. To view a route, only a start point and an end point need to be input, and then a planned route is automatically generated. No GPS signal is required. When the user chooses to follow the planned route for navigation, if the navigation application's permission to retrieve GPS signals is turned off, the permission needs to be re-opened. At this time, when issuing according to the planned route When the navigation command is issued, a permission call instruction called "the permission to call the GPS signal" is generated in order to generate a floating window and complete the setting of the GPS signal permission in the floating window.

In an embodiment, after the step S3 of displaying the permission management list in a floating window in a specified position, the method includes:

S4. Generate a recovery command when the application is closed;

S5. Restore the authority operation set in the floating window according to the restore command.

As described in steps S4 and S5 above, that is, after the application is closed, the permissions operation set in the floating window is used for restoration. For example, when using a navigation application, the permission to "get GPS signals" is not turned on, and the permission to "get GPS signals" is turned on in the floating window. When the navigation application is closed, , Will generate a restore command to automatically turn off the permission to "get GPS signal permission" and so on.

In this embodiment, the use frequency of the above-mentioned application program in the system foreground refers to the frequency that the above-mentioned application program is opened and used in the system foreground. In this embodiment, it is necessary to obtain the frequency of use of the application in the system foreground, because although some application users are not opened in the system foreground, they will be pulled in the system background by push advertisements sent by the server corresponding to the application From then on, although the above application program is used, it is used in the background of the system and will not be used to calculate the frequency of use in this application. If the application is used frequently, the permission to open or close in the floating window may be the permission mode that the user wants to fix for a long time. In this case, the permissions set in the floating box will be restored after exiting the application. It will contradict the user's assumptions, so it will not be restored. If the application is used relatively infrequently, the permission to open or close in the floating window may be the user's current permission mode. In this case, the permissions set in the floating box will be restored after exiting the application. , Will improve the user experience.

In the method for managing permissions of an application in the embodiment of the present application, when managing the permissions of an application, there is no need to first enter the system setting interface, and then find the application and click the application to enter its corresponding permission management. The interface sets permissions, but directly maps the permissions corresponding to the application to a permission management list and displays them in the form of a floating window, so that users can complete the permission setting of the application in the floating window and improve the application program. The speed of setting permissions reduces the processes required for users to set permissions on applications, saves users time, and improves user experience.

Referring to FIG. 2, an embodiment of the present application further provides an authority management device for an application program, including:

An obtaining unit 10, configured to obtain a permission call instruction for the application program;

The reading forming unit 20 is configured to read a permission corresponding to the application according to the permission call instruction, and form the permission into a permission management list. The permission management list is provided with a control for each permission. switch;

The display unit 30 is configured to display the rights management list in a floating window in a specified position.

In the obtaining unit 10, the authority obtaining command is a authority management command generated when the mobile terminal on which the application is installed receives a user-specified operation, or when the authority setting is required due to the user operation. The above-mentioned mobile terminal is an electronic device such as a mobile phone or a tablet computer that can execute an application program.

In the above-mentioned reading forming unit 20, after obtaining the permission call command, the system of the mobile terminal finds the installation package of the application according to the unique information such as the package name of the application, and then parses out the attributes of the application And functions to read out multiple permissions that the application may need to open or close during execution. Different applications may have different permissions. For example, navigation applications include GPS permissions, network permissions, and voice broadcast permissions, while WeChat applications include network permissions, camera permissions, and so on. In this embodiment, all permissions corresponding to the application can be read. You can also read out some permissions based on the user ’s usage habits. For example, each time a user opens an application, certain permissions are set, and only these permissions are read. The read permissions are mapped to a permission management list, which is convenient for users to handle. The above permission switch is generally the opening permission or the closing permission.

In the display unit 30, the floating window is a window suspended above the current interface, so that users can directly set permissions in the floating window, which greatly reduces the user's process of setting application permissions and improves settings. Efficiency, improve user rights management experience. In this embodiment, when the above application program is reset in the floating window, it will be synchronized to the setting interface, that is, after the setting interface is opened, the permission setting of the application is consistent with the setting in the floating window.

In order to further facilitate the operation of the user, it also includes, for example, an initial management unit, which is used to determine the basic functions of the application, and displays the first permission closely related to the basic functions of the application during the initial opening process; for example, enabling navigation Software, such as Gaode maps, needs to open the “location” permission to obtain the current location information. The “location” permission related to the basic functions of the application is used as a closely related first permission. After the application is opened, it is highlighted; subsequent specific functions are triggered in the application; this specific function belongs to the scene permissions under a certain application scenario, and is temporarily displayed as a second permission for the user to choose. For example, For example, in the case of the German map, when the camera needs to be called, the camera permission switch is temporarily displayed for the user to choose; in the case of the user closing the related specific function, the second permission is closed; at the same time, the first The two permission switches are set to two states, permanently on and temporarily on; When the user calls the second permission switch for the second time, it is displayed to the user; this prevents the first user from turning on the second permission, and the second time the user wants to turn on the second permission switch, giving the user a temporary or permanent permission s Choice.

In one embodiment, the obtaining unit 10 includes:

In this embodiment, the display unit 30 includes:

In one embodiment, the obtaining unit 10 includes:

In one embodiment, the device for managing rights of the application further includes:

Closing the generating unit, configured to generate a recovery command when the application is closed;

The restoration unit is configured to restore the authority operation set in the floating window according to the restoration command.

In this embodiment, after the application program is closed, the permission operation set in the floating window is used for restoration. For example, when using a navigation application, the permission to "get GPS signals" is not turned on, and the permission to "get GPS signals" is turned on in the floating window. When the navigation application is closed, , Will generate a restore command to automatically turn off the permission to "get GPS signal permission" and so on.

In one embodiment, the above-mentioned application rights management device further includes:

A frequency judging unit, configured to judge a use frequency of the application program in the foreground of the system;

Closing the generating unit, configured to generate a recovery command when the application is closed if the frequency of use is less than a preset frequency threshold;

The authority management device of the application in the embodiment of the present application does not need to first enter the system setting interface when managing the authority of an application, and then finds the application and clicks the application to enter its corresponding authority management. The interface sets permissions, but directly maps the permissions corresponding to the application to a permission management list and displays them in the form of a floating window, so that users can complete the permission setting of the application in the floating window and improve the application program. The speed of setting permissions reduces the processes required for users to set permissions on applications, saves users time, and improves user experience.

Referring to FIG. 3, an embodiment of the present invention further provides a mobile terminal, including a processor 1080 and a memory 1020, where the memory 1020 is configured to store a program for a permission management device of an application program to execute the permission management method of the foregoing application program; The processor 1080 is configured to execute a program stored in the memory.

For ease of description, only the parts related to the embodiment of the present invention are shown, and specific technical details are not disclosed, please refer to the method part of the embodiment of the present invention. The mobile terminal may be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), and a vehicle-mounted computer. Taking the mobile terminal as a mobile phone as an example:

FIG. 3 is a block diagram showing a partial structure of a mobile phone related to a mobile terminal according to an embodiment of the present invention. Referring to FIG. 3, the mobile phone includes: a radio frequency (RF) circuit 1010, a memory 1020, an input unit 1030, a display unit 1040, a sensor 1050, an audio circuit 1060, a wireless fidelity (WiFi) module 1070, and a processor 1080 , And power supply 1090 and other components. Those skilled in the art can understand that the structure of the mobile phone shown in FIG. 3 does not constitute a limitation on the mobile phone, and may include more or fewer parts than those shown in the figure, or combine certain parts, or arrange different parts.

The following describes each component of the mobile phone in detail with reference to FIG. 3:

The RF circuit 1010 can be used for receiving and transmitting signals during information transmission and reception or during a call. In particular, the downlink information of the base station is received and processed by the processor 1080; in addition, the uplink data of the design is transmitted to the base station. Generally, the RF circuit 1010 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuit 1010 can also communicate with a network and other devices through wireless communication. The above wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (Code Division Multiple Access) Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), E-mail, Short Messaging Service (SMS), etc.

The memory 1020 may be used to store software programs and modules. The processor 1080 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 1020. The memory 1020 may mainly include a storage program area and a storage data area, where the storage program area may store an operating system, at least one function required application program (such as a sound playback function, an image playback function, etc.), etc .; the storage data area may store data according to Data (such as audio data, phone book, etc.) created by the use of mobile phones. In addition, the memory 1020 may include a high-speed random access memory, and may further include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage device.

The input unit 1030 can be used to receive inputted numeric or character information, and generate key signal inputs related to user settings and function control of the mobile phone. Specifically, the input unit 1030 may include a touch panel 1031 and other input devices 1032. Touch panel 1031, also known as touch screen, can collect user's touch operations on or near it (such as the user using a finger, stylus, etc. any suitable object or accessory on touch panel 1031 or near touch panel 1031 Operation), and drive the corresponding connection device according to a preset program. Optionally, the touch panel 1031 may include two parts, a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch position, and detects the signal caused by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into contact coordinates, and sends it To the processor 1080, and can receive the commands sent by the processor 1080 and execute them. In addition, various types such as resistive, capacitive, infrared, and surface acoustic wave can be used to implement the touch panel 1031. In addition to the touch panel 1031, the input unit 1030 may include other input devices 1032. Specifically, other input devices 1032 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, an operation lever, and the like.

The display unit 1040 may be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 1040 may include a display panel 1041, and optionally, the display panel 1041 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like. Further, the touch panel 1031 may cover the display panel 1041. When the touch panel 1031 detects a touch operation on or near the touch panel 1031, the touch panel 1031 transmits the touch operation to the processor 1080 to determine the type of the touch event. The type provides corresponding visual output on the display panel 1041. Although in FIG. 3, the touch panel 1031 and the display panel 1041 are implemented as two independent components to implement the input and input functions of the mobile phone, in some embodiments, the touch panel 1031 and the display panel 1041 can be integrated and Realize the input and output functions of the mobile phone.

The mobile phone may further include at least one sensor 1050, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor may adjust the brightness of the display panel 1041 according to the brightness of the ambient light. The proximity sensor may close the display panel 1041 and / Or backlight. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three axes), and can detect the magnitude and direction of gravity when it is stationary. It can be used for applications that recognize the attitude of mobile phones (such as horizontal and vertical screen switching, Games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc .; as for the mobile phone can also be equipped with gyroscope, barometer, hygrometer, thermometer, infrared sensor and other sensors, no longer here To repeat.

The audio circuit 1060, the speaker 1061, and the microphone 1062 can provide an audio interface between the user and the mobile phone. The audio circuit 1060 can transmit the received electrical data converted electrical signal to the speaker 1061, and the speaker 1061 converts the sound signal to an audio signal output. On the other hand, the microphone 1062 converts the collected sound signal into an electrical signal, and the audio circuit 1060 After receiving, it is converted into audio data, and then the audio data is output to the processor 1080 for processing, and then sent to, for example, another mobile phone via the RF circuit 1010, or the audio data is output to the memory 1020 for further processing.

WiFi is a short-range wireless transmission technology. The mobile phone can help users send and receive emails, browse web pages, and access streaming media through the WiFi module 1070. It provides users with wireless broadband Internet access. Although FIG. 3 shows the WiFi module 1070, it can be understood that it does not belong to the necessary configuration of the mobile phone, and can be omitted as needed without changing the essence of the invention.

The processor 1080 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. The processor 1080 runs or executes software programs and / or modules stored in the memory 1020, and calls data stored in the memory 1020 to execute. Various functions and processing data of the mobile phone, so as to monitor the mobile phone as a whole. Optionally, the processor 1080 may include one or more processing units; preferably, the processor 1080 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and an application program, etc. The modem processor mainly handles wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 1080.

The mobile phone also includes a power supply 1090 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 1080 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system.

Although not shown, the mobile phone may further include a camera, a Bluetooth module, and the like, and details are not described herein again.

Referring to FIG. 3, in an embodiment of the present invention, the processor 1080 included in the mobile terminal also has the following functions:

Obtaining a permission call instruction for the application;

Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist separately physically, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional unit.

A person of ordinary skill in the art may understand that all or part of the steps in the method of the foregoing embodiment may be implemented by a program instructing related hardware. The program may be stored in a computer-readable storage medium. The medium may be a read-only memory, a magnetic disk, or an optical disk.

The above is only a preferred embodiment of the present invention, and thus does not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made by using the description and drawings of the present invention, or directly or indirectly used in other related The technical field is included in the patent protection scope of the present invention.

Claims

An application program permission management method, including:

Obtaining a permission call instruction for the application;

Reading the permissions corresponding to the application according to the permission calling instruction, and forming the permissions into a permission management list, wherein a switch for controlling each permission is set in the permission management list;

Displaying the rights management list in the form of a floating window at a specified position.
The method for managing permissions of an application program according to claim 1, wherein the step of obtaining a permission call instruction for the application program comprises:

Before opening the application program, determining whether the entry information of the application program has received a trigger operation of permission call;

If yes, the authority call instruction is generated.
The method for managing rights of an application program according to claim 2, wherein the step of displaying the rights management list at a specified position in the form of a floating window comprises:

Determine the first position of the entry information of the application on the system desktop;

Displaying the rights management list in the form of a floating window at a second position close to or overlapping the first position.
The method for managing rights of an application program according to claim 2, wherein the step of displaying the rights management list at a specified position in the form of a floating window comprises:

Displaying the rights management list in the form of a floating window at the bottom of the system desktop.
The method for managing permissions of an application program according to claim 1, wherein the step of obtaining a permission call instruction for the application program comprises:

After opening the application, obtaining a first permission that the application needs to be opened / closed according to a user's operation instruction;

Generate a permission call instruction that calls the first permission.
The permission management method for an application program according to claim 5, wherein after the opening the application program, the step of obtaining a first permission that the application program needs to open / close according to a user's operation instruction, comprising:

After opening the application, executing the operation instruction of the user, and determining whether the operation instruction can be normally executed;

If the execution fails, determine whether the reason for the failure is that the corresponding first authority is not enabled / disabled;

If it can be executed normally, the step of generating a permission call instruction that calls the first permission is performed.
The method for managing a permission of an application program according to any one of claims 1 to 5, wherein after the step of displaying the permission management list at a specified position in the form of a floating window, comprises:

Generating a recovery command when the application is closed;

According to the restoration command, the authority operation set in the floating window is restored.
The method for managing a permission of an application program according to any one of claims 1 to 5, wherein after the step of displaying the permission management list at a specified position in the form of a floating window, comprises:

Judging the use frequency of the application program in the foreground of the system;

If the use frequency is less than a preset frequency threshold, generating a recovery command when the application is closed;

According to the restoration command, the authority operation set in the floating window is restored.
The method for managing permissions of an application program according to claim 1, wherein the step of reading the permissions corresponding to the application program comprises:

Find the installation package of the application;

Obtaining attributes and functions of the application from the installation package;

Read multiple permissions that need to be opened or closed when the application is executed according to the attributes and functions.
The method for managing rights of an application program according to claim 1, wherein the step of displaying the rights management list at a specified position in the form of a floating window comprises:

Obtaining basic functions of the application;

A first right corresponding to the basic function is obtained from the right management list, and the first right corresponding to the basic function is displayed in a specified window in the form of a floating window.
The permission management method for an application program according to claim 10, wherein the step of displaying the permission management list in the form of a floating window at a specified position further comprises:

Obtaining a specific function triggered by the application;

Obtain a second right corresponding to the specific function from the right management list, and display the second right corresponding to the specific function in a specified window in the form of a floating window.
An application program authority management device, including:

An obtaining unit, configured to obtain a permission call instruction for the application program;

The reading forming unit is configured to read the permission corresponding to the application according to the permission call instruction, and form the permission into a permission management list, wherein a switch for controlling each permission is set in the permission management list. ;

A display unit is configured to display the rights management list in a floating window in a specified position.
The authority management device for an application program according to claim 12, wherein the obtaining unit comprises:

A first determining module, configured to determine whether the entry information of the application program has received a triggering operation of permission call before opening the application program;

A first generating module is configured to generate the permission call instruction if the trigger operation is received.
The method for managing rights of an application program according to claim 13, wherein the display unit comprises:

A second determining module, configured to determine a first position of the entry information of the application on a system desktop;

A display module, configured to display the permission management list in the form of a floating window at a second position close to or overlapping the first position.
The method according to claim 12, wherein the obtaining unit comprises:

An obtaining module, configured to obtain a first permission that the application needs to be opened / closed according to a user's operation instruction after the application is opened;

The second generating module is configured to generate a permission call instruction for invoking the first permission.
A mobile terminal including a processor and a memory,

The memory is configured to store a program that implements a rights management device of an application to execute the rights management method of the application according to any one of rights 1 to 11;

The processor is configured to execute a program stored in the memory.