CN111695151A - Application permission setting method and device, electronic equipment and readable storage medium - Google Patents

Abstract

The present application discloses an application authority setting method, device, electronic device and readable storage medium, which belong to the technical field of application authority allocation. The method includes: in the case of receiving the first input for the target application, acquiring the application type of the target application; The target application permission corresponding to the application type of the program; the target application permission is set for the target application. The application can improve the authority setting efficiency, perform reasonable authority control, and improve the security performance of the system.

Description

Application permission setting method, device, electronic device and readable storage medium

technical field

The present application belongs to the technical field of application authority allocation, and in particular relates to a method, apparatus, electronic device and readable storage medium for setting application authority.

Background technique

With the development of the Internet industry and the prosperity of the Internet application market, there are more and more applications in mobile phones, and users can download and install various applications from the Internet to obtain different services.

After the application is installed on the mobile phone, when the user activates the application, it will prompt the user that the application needs to authorize the system function permission, so as to obtain the necessary data or information by using it, and then realize the function or service provided by the application. With the increase in the type and number of applications, more and more permissions are required for applications, including phone permissions, storage permissions, camera permissions, location permissions, contacts permissions, microphone permissions, notification permissions, and more.

At present, when the user activates the application, the authorization of the system permissions will pop up one by one in the form of a pop-up window. The user needs to make multiple authorization selections before the application can be used normally. The efficiency of permission allocation is low, and the application will also request Some permissions are not necessary for its functions, and users will also be over-authorized due to reasons such as wrong clicks, so that permissions cannot be reasonably controlled, and there are security risks.

SUMMARY OF THE INVENTION

The purpose of the embodiments of the present application is to provide an application permission setting method, device, electronic device and readable storage medium, which can solve the problem that in the prior art, the user is required to perform multiple authorization selections, the permission allocation efficiency is low, and the error caused by the user The problem of over-authorization.

In order to solve the above technical problems, this application is implemented as follows:

In a first aspect, an embodiment of the present application provides a method for setting application permissions, the method comprising:

In the case of receiving the first input for the target application, obtain the application type of the target application;

Determine the target application permission corresponding to the application type of the target application according to the mapping relationship between the application type and the preset application permission;

The target application permission is set for the target application.

In a second aspect, an embodiment of the present application provides an application permission setting device, the device:

a target type acquisition module, configured to acquire the application type of the target application when the first input for the target application is received;

a target permission determination module, configured to determine the target application permission corresponding to the application type of the target application according to the mapping relationship between the application type and the preset application permission;

A target permission setting module, configured to set the target application permission for the target application.

In a third aspect, embodiments of the present application provide an electronic device, the electronic device includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being The processor implements the steps of the method for setting application rights according to the first aspect when executed.

In a fourth aspect, an embodiment of the present application provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the application permission setting described in the first aspect is implemented steps of the method.

In a fifth aspect, an embodiment of the present application provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, and implement the first aspect The described application permission setting method.

In the embodiment of the present application, the application type of the target application is obtained when the first input for the target application is received, and according to the mapping relationship between the application type and the preset application permission, the application type of the target application is determined. Set the target application permission for the target application. In the embodiment of the present application, a set of preset application permissions is set for different application types in advance, so that when the application of the application type is activated, the preset application permissions can be automatically set for the application, so that the user does not need to make multiple authorization selections. The efficiency of permission setting is improved, and the problem of excessive authorization for the application program due to the user's mistaken click is avoided, reasonable permission control can be performed, and the security performance of the system is improved.

Description of drawings

1 is a flowchart of steps of a method for setting application permissions provided by an embodiment of the present application;

2 is a schematic diagram of a quick authorization function for enabling authority provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of a permission details display interface provided by an embodiment of the present application;

4 is a schematic diagram of a single application labeling provided by an embodiment of the present application;

5 is a schematic diagram of batch application labeling provided by an embodiment of the present application;

6 is a schematic diagram of a rights management page provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of an application permission setting device provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of another electronic device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present application.

The terms "first", "second" and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that data so used may be interchanged under appropriate circumstances so that embodiments of the application can be practiced in sequences other than those illustrated or described herein. In addition, "and/or" in the description and claims indicates at least one of the connected objects, and the character "/" generally indicates that the associated objects are in an "or" relationship.

The permission allocation method provided by the embodiments of the present application will be described in detail below through specific embodiments and application scenarios with reference to the accompanying drawings.

Referring to FIG. 1, a flowchart of steps of an application permission setting method provided by an embodiment of the present application is shown. As shown in FIG. 1, the application permission setting method may specifically include the following steps:

Step 101: In the case of receiving the first input for the target application, obtain the application type of the target application.

The embodiments of the present application may be applied to scenarios in which preset application permissions are automatically set for applications according to application types.

In this embodiment, when it is necessary to automatically set application permissions for an activated application according to the method provided in this embodiment, the function of "application shortcut authorization" needs to be enabled in the electronic device in advance, as shown in FIG. 2 , in the electronic device The device is pre-configured with the function option of "Quick Authorization of Application", and the user can choose whether to enable the function of "Quick Authorization of Application" for the electronic device by clicking "Yes" or "No".

A target application refers to an application installed in the system that requires application permission settings when activated. In this embodiment, the target application may be a video application or a social application. Specifically, it may be determined according to the actual situation, which is not limited in this embodiment.

The first input refers to an input for activating the target application. In this embodiment, the first input may be an input operation triggered by the user clicking on the target application for the first time after the target application is installed in the system. Of course, the first input may also be an input that is automatically triggered after the target application is installed. Specifically, it may be determined according to the actual situation, which is not limited in this embodiment.

In this embodiment, the application type may be the type of the target application acquired by the system. For example, when the target application is a video application, the type of the target application automatically acquired by the system is a video. The application type may also be a label type pre-set by the user for the target application. For example, the user may pre-label multiple applications, and the type of the application is limited by the labels that the user labels.

In the case of receiving the first input for the target application, the application type of the target application may be acquired, and then step 102 is performed.

Step 102: Determine a target application permission corresponding to the application type of the target application according to the mapping relationship between the application type and the preset application permission.

In this embodiment, the mapping relationship between different application types and preset application permissions can be pre-stored. Specifically, the mapping relationship between different application types and preset application permissions can be preset in the following two ways.

1. The mapping relationship between system custom application types and preset application permissions.

The manner of setting the mapping relationship between application types and preset application permissions may be as described in the following steps A1 to A2.

Step A1: Acquire at least one application type.

In the embodiment of the present application, the electronic device system may preset a set of corresponding preset application permissions for different application types. Application types (such as video, social, map, etc.), at least one application type includes the target application type mentioned above.

After acquiring at least one application type, step A2 is performed.

Step A2: Setting the mapping relationship between the at least one application type and the preset application authority.

After acquiring at least one application type, a mapping relationship between at least one application type and preset application permissions can be set. Specifically, according to the basic necessity of application permissions and whether there are hidden dangers after authorization, application permissions can be divided into Basic permissions (such as storage permissions, network usage permissions, etc.) and non-basic permissions (such as location permissions, address book permissions, etc.). The basic authority may be authorized by default, which is not limited in this embodiment. For non-basic permissions, each application type and its necessary non-basic permissions can be mapped one by one according to the main functions of different application types, and the mapping result is the preset application permissions corresponding to each application type.

2. The user pre-labels the application (each label corresponds to an application type), and sets the preset application permissions corresponding to different application labels

For setting preset application permissions corresponding to different application labels, the following steps B1 to B2 can be used:

Step B1: Obtain the application type set by the user for at least one application program.

In this embodiment, the user can set its corresponding application type for at least one application.

First, with reference to FIG. 4 , the way of labeling a single application is described. As shown in Figure 4, if you select "select labels only for the current application", you will enter the separate marking process, pop up the floating layer and display the optional labels. Here, the default system related labels are checked by default, and the user can choose to reselect or directly inherit the system related labels, and the labels are single-choice. Each tag corresponds to an application type, such as "social", "map", "game", "novel" and so on as shown in Figure 4.

Next, with reference to Fig. 5, the method of batch application labeling is described. As shown in Figure 5, if "Select more applications" is selected, the batch marking process will be entered. The user can select the same-label application on the mobile phone interface, and can select N multiple (N is a positive integer greater than or equal to 2), and supports turning pages to select applications that are not on the same screen. After the selection is complete, click "√ to complete the selection" in the upper right corner to enter the labeling operation.

It can be understood that the above examples are only examples listed for better understanding of the technical solutions of the embodiments of the present application, and are not intended to be the only limitations on the embodiments of the present application.

After acquiring the application type set by the user for at least one application program, step B2 is performed.

Step B2: Setting the mapping relationship between the application types and preset application permissions.

In this embodiment, for different application types set by the user, a set of corresponding preset application permissions can be set for them. As required by the main functions of the application types, map each application type and its necessary non-basic permissions one by one, and the mapping result is the preset application permission corresponding to each application type.

It is understandable that the above two specific implementation manners both pre-set a mapping relationship between an application type and a set of preset application permissions, and the specific implementation manner may be determined according to business requirements, which is not limited in this embodiment. .

After the target application type corresponding to the target application is obtained, the target application permission corresponding to the target application type can be obtained according to the mapping relationship between the application type and the preset application permission. For example, two mapping relationships are pre-stored in the system : 1. There is a mapping relationship between video applications and positioning permissions. 2. There is a mapping relationship between social applications and address book permissions. When it is determined that the target application type of the target application is video, the preset corresponding to the target application type Let the application permission be: positioning permission.

It can be understood that one application type may correspond to one application permission, or may correspond to multiple application permissions, and specifically, it may be determined according to the actual situation, which is not limited in this embodiment.

Step 103 is performed after determining the target application authority corresponding to the application type of the target application according to the mapping relationship between the application type and the preset application authority.

Step 103: Set the target application permission for the target application.

After acquiring the target application permission corresponding to the application type of the target application, the target application permission can be set for the target application, that is, authorizing the target application.

In this embodiment, by presetting a set of preset application permissions for different application types, the preset application permissions can be automatically assigned to the application when the application of the application type is first input, so that the user does not need to perform multiple Authorization selection improves the efficiency of authorization distribution.

After the target application is authorized, a permission details interface can be displayed on the screen of the electronic device to prompt the user for the application permission set for the target application. The user can also adjust the application permission automatically set by the system. Specifically, the following can be combined The specific implementation is described in detail.

In a specific implementation manner of the present application, after the above step 103, the following steps C1 to C3 may also be included:

Step C1: Display a permission setting interface corresponding to the target application; the permission setting interface displays the preset application permission.

In this embodiment of the present application, the permission setting interface refers to an interface for prompting the user to automatically set preset application permissions for the target application.

After setting the preset application permission for the target application, the user can be prompted that the target application has been authorized quickly, and the permission setting interface is displayed, as shown in Figure 3, the permission setting interface can display "You have authorized us to You have completed automatic authorization for quick permission management”, and display the application permissions set for the target application, such as “This authorization includes: storage permission, phone permission, and network usage permission”.

After the permission setting interface corresponding to the target application is displayed, step C2 is performed.

Step C2: Receive an editing operation for the preset application permission.

Editing operations refer to operations performed by users on preset application permissions, such as modifying operations.

Of course, application permissions that are not set for the target application can also be displayed in the permission assignment interface. As shown in Figure 3, the permissions that are not set for the target application include "Location Permission" and "Notification Permission". Editing application permissions means deleting the permissions that have been set for the target application. Of course, it is also possible to add corresponding application permissions that are not authorized by the target application. Specifically, it can be determined according to business requirements, and this embodiment does not apply this. limit.

After receiving the editing operation for the preset application authority, step C3 is performed.

Step C3: In response to the editing operation, adjust the preset application authority set by the target application program.

After receiving the editing operation for the preset application permission, the preset application permission set by the target application can be adjusted accordingly according to the editing operation, such as deleting an assigned application permission or adding another application permissions, etc.

In this embodiment, the user can also be prompted whether to display the prompt information of the authorized permission assignment interface when activating the application subsequently. As shown in FIG. 3 , after the preset application permission is set for the target application, a prompt page can be displayed, In the prompt page, the prompt message "Do you need to show you permission details for subsequent authorization" is displayed, and two buttons "Need" and "No need" are displayed. Each subsequent activation of the application will display the authorization details (that is, display the permission assignment interface), and support quick permission modification (check or remove the check), complete and click close to enter the application. If the user selects no prompt, that is, clicks the "No need" button, the subsequent activation of the application will skip the authorization process and enter directly.

Of course, since the user has customized the application type and the system has defined a set of corresponding preset application permissions for the application type, the user can manage the preset application permissions corresponding to the application type. Specifically, detailed description may be made in conjunction with the following specific implementation manners.

In another specific implementation manner of the present application, after the above step 103, the following steps D1 to D2 may also be included:

Step D1: Receive a permission editing operation corresponding to an application of the application type.

In this embodiment, the permission editing operation refers to the operation of editing the permission of the application program of the purpose type.

The user can customize and modify the application permissions corresponding to the applications of the application type. Specifically, when the user needs to adjust the preset application permissions corresponding to an application type, he can enter the "Tag Permission Management Page" through the Settings Center, and click each button. Each tab, you can see the application permissions corresponding to the application type, as shown in Figure 6, the user can enter the permission management interface through the "Settings Center", and multiple application types can be displayed in the permission management interface, as shown in the middle of Figure 6 As shown in a picture, when the user needs to manage the preset application permissions corresponding to a certain application type, as shown in the rightmost picture in Figure 6, when the user clicks "Social", the corresponding "Social" category can be displayed. , such as "Storage Permission", "Network Permission", "Phone Permission", "Contacts Permission", "Camera Permission", "Notification Permission". The user can adjust the preset application permission of the application type, such as deleting a preset application permission, or re-adding a certain application permission, and so on.

After receiving the permission adjustment operation for the application of the application type, step D2 is performed.

Step D2: In response to the permission editing operation, adjust the application permission set by the application program of the application type.

After receiving the permission editing operation corresponding to the application of the application type, the application permission set by the application of the application type may be adjusted according to the permission editing operation.

In this embodiment, the electronic device system can also record the permissions assigned to the application, and when the first input of the application is received again, the application permissions can be automatically set for the application according to the record information. Detailed description will be given in conjunction with the following specific implementation manners.

In another specific implementation manner of the present application, after the above step 103, the following steps E1 to E2 may also be included:

Step E1: Record the target application permission corresponding to the target application.

In this embodiment, after the target application authority is set for the target application, the target application authority set for the target application may be recorded, and then step E2 is performed.

Step E2: In the case of receiving the first input for the target application again, set the target application permission for the target application.

When the first input for the target application is received again, that is, after the target application has been uninstalled and reinstalled by the user, the instruction received when it is activated again can automatically be the target application according to the recorded permissions of the target application. The program sets the target application permissions.

In the application permission setting method provided by the embodiment of the present application, the application type of the target application is obtained when the first input for the target application is received, and according to the mapping relationship between the application type and the preset application permission, the The target application permission corresponding to the application type of the target application, set the target application permission for the target application. In the embodiment of the present application, a set of preset application permissions is set for different application types in advance, so that when the application of the application type is activated, the preset application permissions can be automatically set for the application, so that the user does not need to make multiple authorization selections. The efficiency of permission setting is improved, and the problem of excessive authorization for the application program due to the user's mistaken click is avoided, reasonable permission control can be performed, and the security performance of the system is improved.

It should be noted that, in the application permission setting method provided by the embodiment of the present application, the execution subject may be an application permission setting device, or a control module in the application permission setting device for executing the loading application permission setting method. In the embodiment of the present application, the application authority setting apparatus provided by the embodiment of the present application is described by taking the application authority setting apparatus executing the method for setting the authority for loading an application as an example.

Referring to FIG. 7 , a schematic structural diagram of an application permission setting device provided by an embodiment of the present application is shown. As shown in FIG. 7 , the application permission setting device 200 may specifically include the following modules:

a target type obtaining module 210, configured to obtain the application type of the target application when the first input for the target application is received;

a target permission determination module 220, configured to determine the target application permission corresponding to the application type of the target application according to the mapping relationship between the application type and the preset application permission;

A target permission setting module 230, configured to set the target application permission for the target application.

Optionally, the application permission setting apparatus 200 further includes:

a permission interface display module, configured to display a permission setting interface corresponding to the target application; the permission setting interface displays the preset application permission;

an editing operation receiving module, configured to receive an editing operation for the preset application authority;

A first permission adjustment module, configured to adjust the preset application permission set by the target application program in response to the editing operation.

Optionally, the application permission setting apparatus 200 further includes:

a permission editing operation receiving module, configured to receive a permission editing operation corresponding to an application of the application type;

A second permission adjustment module, configured to adjust the application permission set by the application program of the application type in response to the permission editing operation.

Optionally, the application permission setting apparatus 200 further includes:

a target permission recording module, used to record the target application permission corresponding to the target application;

A target application permission assignment module, configured to set the target application permission for the target application when the first input for the target application is received again.

The device for setting application authority in this embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The apparatus may be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (personal digital assistant). assistant, PDA), etc., the non-mobile electronic device can be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc. This application Examples are not specifically limited.

The device for setting application rights in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.

The application permission setting apparatus provided in the embodiment of the present application can implement each process implemented by the application permission setting method in the method embodiment of FIG. 1 , which is not repeated here to avoid repetition.

The application permission setting device provided by the embodiment of the present application obtains the application type of the target application when the first input for the target application is received, and determines the application type according to the mapping relationship between the application type and the preset application permission. The target application permission corresponding to the application type of the target application, set the target application permission for the target application. In the embodiment of the present application, a set of preset application permissions is set for different application types in advance, so that when the application of the application type is activated, the preset application permissions can be automatically set for the application, so that the user does not need to make multiple authorization selections. The efficiency of permission setting is improved, and the problem of excessive authorization for the application program due to the user's mistaken click is avoided, reasonable permission control can be performed, and the security performance of the system is improved.

Optionally, an embodiment of the present application further provides an electronic device. As shown in FIG. 8 , the electronic device 300 includes a processor 310 , a memory 309 , and a program stored in the memory 309 and running on the processor 310 or instruction, when the program or instruction is executed by the processor 310, each process of the above-mentioned embodiment of the application permission setting method is implemented, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.

It should be noted that the electronic devices in the embodiments of the present application include the aforementioned mobile electronic devices and non-mobile electronic devices.

FIG. 9 is a schematic diagram of a hardware structure of another electronic device implementing an embodiment of the present application.

The electronic device 300 includes but is not limited to: a radio frequency unit 301, a network module 302, an audio output unit 303, an input unit 304, a sensor 305, a display unit 306, a user input unit 307, an interface unit 308, a memory 309, and a processor 310, etc. part.

Those skilled in the art can understand that the electronic device 300 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 310 through a power management system, so that the power management system can manage charging, discharging, and power management. consumption management and other functions. The structure of the electronic device shown in FIG. 9 does not constitute a limitation to the electronic device. The electronic device may include more or less components than the one shown, or combine some components, or arrange different components, which will not be repeated here. .

It should be understood that, in this embodiment of the present application, the input unit 304 may include a graphics processor (Graphics Processing Unit, GPU) 3041 and a microphone 3042. camera) to process the image data of still pictures or videos. The display unit 306 may include a display panel 3061, and the display panel 3061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. The user input unit 307 includes a touch panel 3071 and other input devices 3072 . The touch panel 3071 is also called a touch screen. The touch panel 3071 may include two parts, a touch detection device and a touch controller. Other input devices 3072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here. Memory 309 may be used to store software programs as well as various data including, but not limited to, application programs and operating systems. The processor 310 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the like, and the modem processor mainly processes wireless communication. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 310.

The processor 310 is configured to determine the target application permission corresponding to the application type of the target application according to the mapping relationship between the application type and the preset application permission; set the target application permission for the target application .

In this embodiment of the present application, the application type of the target application is obtained when the first input for the target application is received, and the application type of the target application is determined according to the mapping relationship between the application type and the preset application permission. The corresponding target application permission, set the target application permission for the target application. In the embodiment of the present application, a set of preset application permissions is set for different application types in advance, so that when the application of the application type is activated, the preset application permissions can be automatically set for the application, so that the user does not need to make multiple authorization selections. The efficiency of permission setting is improved, and the problem of excessive authorization for the application program due to the user's mistaken click is avoided, reasonable permission control can be performed, and the security performance of the system is improved.

Optionally, the display unit 306 is configured to display a permission assignment interface corresponding to the target application; the permission assignment interface displays the preset application permission;

The processor 310 is further configured to receive an editing operation for the preset application permission; in response to the editing operation, adjust the preset application permission assigned by the target application.

storage 309, used for storing the target application permission corresponding to the target application;

The processor 310 is further configured to set the target application permission for the target application when the first input for the target application is received again.

In the embodiment of the present application, the batch management of the preset application permissions can be realized by the user setting the application types for the application programs in batches.

Embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the foregoing application permission setting method embodiment is implemented, and can achieve The same technical effect, in order to avoid repetition, will not be repeated here.

Wherein, the processor is the processor in the electronic device described in the foregoing embodiments. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.

An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used for running a program or an instruction to implement the above embodiment of the application permission setting method and can achieve the same technical effect, in order to avoid repetition, it will not be repeated here.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip, or the like.

It should be noted that, herein, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in the reverse order depending on the functions involved. To perform functions, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to some examples may be combined in other examples.

From the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of this application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific embodiments, which are merely illustrative rather than restrictive. Under the inspiration of this application, without departing from the scope of protection of the purpose of this application and the claims, many forms can be made, which all fall within the protection of this application.

Claims (10)

1. An application authority setting method is characterized by comprising the following steps:

acquiring an application type of a target application program under the condition that a first input aiming at the target application program is received;

determining a target application authority corresponding to the application type of the target application program according to the mapping relation between the application type and the preset application authority;

and setting the target application permission for the target application program.

2. The method of claim 1, further comprising, after the setting the target application permission for the target application program:

displaying an authority setting interface corresponding to the target application program; the preset application permission is displayed on the permission setting interface;

receiving editing operation aiming at the preset application permission;

and responding to the editing operation, and adjusting the preset application permission set by the target application program.

3. The method of claim 1, further comprising, after the setting the target application permission for the target application program:

receiving authority editing operation corresponding to the application program of the application type;

and responding to the authority editing operation, and adjusting the application authority set by the application program of the application type.

4. The method of claim 1, further comprising, after the setting the target application permission for the target application program:

recording a target application authority corresponding to the target application program;

and setting the target application permission for the target application program under the condition that the first input aiming at the target application program is received again.

5. An application authority setting configuration apparatus, comprising:

the device comprises a target type acquisition module, a first display module and a second display module, wherein the target type acquisition module is used for acquiring the application type of a target application program under the condition of receiving first input aiming at the target application program;

the target permission determining module is used for determining a target application permission corresponding to the application type of the target application program according to the mapping relation between the application type and the preset application permission;

and the target permission setting module is used for setting the target application permission for the target application program.

6. The apparatus of claim 5, further comprising:

the authority interface display module is used for displaying an authority setting interface corresponding to the target application program; the preset application permission is displayed on the permission setting interface;

the editing operation receiving module is used for receiving editing operation aiming at the preset application authority;

and the first permission adjusting module is used for responding to the editing operation and adjusting the preset application permission set by the target application program.

7. The apparatus of claim 5, further comprising:

the permission editing operation receiving module is used for receiving permission editing operation corresponding to the application program of the application type;

and the second permission adjusting module is used for responding to the permission editing operation and adjusting the application permission set by the application program of the application type.

8. The apparatus of claim 5, further comprising:

the target permission recording module is used for recording the target application permission corresponding to the target application program;

and the target application permission distribution module is used for setting the target application permission for the target application program under the condition that the first input aiming at the target application program is received again.

9. An electronic device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the application rights setting method as claimed in any one of claims 1-4.

10. A readable storage medium, on which a program or instructions are stored, which when executed by a processor, implement the steps of the application rights setting method as claimed in any one of claims 1 to 4.

Images