Application permission management method and device, and electronic device

Abstract

The application discloses an application permission management method and device and electronic equipment, the method comprises the following steps: in the case that a first application runs, a first input is received; in response to the first input, a first interface is displayed; wherein at least one permission identifier corresponding to the first application is displayed on the first interface; each permission identifier indicates an application permission of the first application.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to an application permission management method and device and electronic equipment. BACKGROUND

[0002] At present, in order to ensure that an electronic device application realizes corresponding functions, a user usually needs to set various permissions for the application in the electronic device during use of the electronic device.

[0003] In the related art, after an application is installed, the application requests the user to open the permissions of functions (such as photographing and positioning) provided by the application when the user uses the application for the first time. The user is asked whether to open the function permissions every time the application is used. Once the permissions are granted, the permissions are granted by default in the subsequent use process. If the user wants to modify the content of the application permissions, the user needs to enter a related setting page, find the specific item corresponding to the above permissions, and then complete the modification of the permissions.

[0004] However, the general user is not familiar with the related setting page for modifying the permissions, which leads to inconvenience in modifying the permissions and a cumbersome modification process. Therefore, the use experience of the user for the functions of the electronic device application is reduced. SUMMARY

[0005] Embodiments of the present application provide an application permission management method and device and electronic equipment, which can solve the technical problem of inconvenience in modifying the permissions of the electronic device application and a cumbersome modification process.

[0006] In a first aspect, embodiments of the present application provide an application permission management method, which comprises:

[0007] receiving a first input in a case where a first application runs;

[0008] displaying a first interface in response to the first input;

[0009] wherein at least one permission identifier corresponding to the first application is displayed on the first interface.

[0010] Each permission identifier indicates an application permission of the first application.

[0011] In a second aspect, embodiments of the present application provide an application permission management device, which comprises:

[0012] a receiving module configured to receive a first input in a case where a first application runs;

[0013] a display module configured to display a first interface in response to the first input received by the receiving module.

[0014] The at least one permission identifier corresponding to the first application is displayed on the first interface.

[0015] The first interface is an interface related to the first application.

[0016] Each permission identifier indicates an application permission of the first application.

[0017] In a third aspect, an electronic device is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the method of the first aspect are implemented.

[0018] In a fourth aspect, a readable storage medium is provided, which stores a program or instruction. When the program or instruction is executed by a processor, the steps of the method of the first aspect are implemented.

[0019] In a fifth aspect, a chip is provided, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to execute a program or instruction to implement the method of the first aspect.

[0020] In the embodiments of the present application, when the first application is running, a first input can be received, and then in response to the first input, a first interface is displayed. The at least one permission identifier corresponding to the first application is displayed on the first interface. Each permission identifier indicates an application permission of the first application. In this way, if the user needs to modify the permissions of the first application (for example, close the enabled permissions or enable the disabled permissions), the user can directly modify (for example, enable or disable) the application permission indicated by the permission identifier in the at least one permission identifier on the first interface, so that the modification of the permissions of the first application can be quickly and conveniently completed, and the user's experience of using the functions of the electronic device is improved. BRIEF DESCRIPTION OF DRAWINGS

[0021] Figure 1 One of the flowcharts of the application permission management method provided by the embodiments of the present application;

[0022] Figure 2 One of the interface diagrams of the application permission management method provided by the embodiments of the present application;

[0023] Figure 3 The second interface diagram of the application permission management method provided by the embodiments of the present application;

[0024] Figure 4 The third interface diagram of the application permission management method provided by the embodiments of the present application;

[0025] Figure 5Fig. 4 is a schematic diagram of an interface of the application permission management method according to an embodiment of the present application;

[0026] Figure 6 Fig. 1 is a schematic diagram of an application permission management device according to an embodiment of the present application;

[0027] Figure 7 Fig. 2 is a schematic diagram of an application permission management device according to an embodiment of the present application;

[0028] Figure 8 Fig. 3 is a schematic diagram of an application permission management device according to an embodiment of the present application;

[0029] Figure 9 Fig. 4 is a schematic diagram of an electronic device according to an embodiment of the present application;

[0030] Figure 10 Fig. 5 is a schematic diagram of a hardware of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0031] The technical solutions in the embodiments of the present application will be described clearly below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0032] The terms "first", "second", and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be exchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein. In addition, "and / or" in the specification and claims indicates at least one of the connected objects, and the character " / ", generally indicates that the front and rear associated objects are in a "or" relationship.

[0033] It should be noted that the marks in the embodiments of the present application are used to indicate the information of words, symbols, images, etc. can be displayed as a control or other container as a carrier of information, including but not limited to word marks, symbol marks, image marks.

[0034] The application permission management scheme provided in the embodiments of the present application can be applied to the permission modification scene of the application program.

[0035] In the related art, if a user wants to modify the application permission content, the user needs to enter a related setting page, find the corresponding entry, and then the permission change can be completed, which leads to inconvenient permission content modification and a cumbersome modification process. In addition, when some applications are not authorized, the applications cannot be used. After the permission is granted, the specific information content obtained by the application is unknown. The user does not know whether the application should be authorized or not, and cannot determine which private information is obtained by the application.

[0036] In the embodiment of the present application, at least one permission identifier corresponding to the first application can be displayed on the first interface. The first interface is an interface related to the first application; each permission identifier indicates an application permission of the first application; and the permissions of the first application include enabled permissions and disabled permissions. Thus, the user does not need to enter a related setting page to find the corresponding entry, but only needs to view or modify the permissions of the first application quickly, conveniently and intuitively through the at least one permission identifier displayed on the first interface, which simplifies the user operation and improves the user's experience of using the function of the electronic device application.

[0037] The application permission management method provided by the embodiment of the present application will be described in detail below in combination with the drawings, specific embodiments and application scenarios. The method will be exemplarily described below taking the execution subject as an application permission management device.

[0038] As shown in Figure 1 The application embodiment provides an application permission management method, which can include the following steps 101 and 102.

[0039] Step 101, receiving a first input in a case where a first application is running.

[0040] Step 102, displaying a first interface in response to the first input.

[0041] Wherein, at least one permission identifier corresponding to the first application is displayed on the first interface; each permission identifier indicates an application permission of the first application.

[0042] In the embodiment of the present application, the above-mentioned first input can be a touch input of the user, or a voice input, or other possible inputs, which can be set according to actual needs.

[0043] Exemplarily, the above-mentioned first input can be an input of the user to interface A. Further, the above-mentioned interface A can be: an application interface of the first application, or an application interface of another application, or a desktop, or other possible interfaces, which are not limited in the embodiment of the present application.

[0044] Exemplarily, the touch input can be a press input (e.g., a long press input or a short press input), a sliding input, a click input, or a drag input of the user at any position or a preset position of the interface A. Further, the preset position can be an edge position of the interface A.

[0045] In the embodiments of the present application, the at least one permission identifier includes one or more permission identifiers of a first application in the electronic device. Further, the at least one permission identifier can include a permission identifier of a permission that has been enabled for the first application, or a permission identifier of a permission that has not been enabled for the first application. That is, the permission identifiers displayed in the first interface can be permission identifiers of enabled permissions, or permission identifiers of disabled permissions, thereby facilitating the user to manage various permissions.

[0046] In an example, the first interface can also display permission identifiers of all or part of the applications in the electronic device, which is not limited in the embodiments of the present application.

[0047] In the embodiments of the present application, the first interface can be an interface related to the first application.

[0048] Exemplarily, the first interface can be a background task management interface, or the first interface can include a first application page of the first application.

[0049] In a possible example, the first interface is a background task management interface. The target region of the background task management interface displays a first page identifier of the first application and at least one permission identifier. The first page identifier is used to indicate a first application page of the first application.

[0050] Exemplarily, the background task management interface includes a page identifier display region and a first permission identifier display region. The page identifier display region displays a page identifier of a background running application (e.g., the first page identifier of the first application), and the first permission identifier display region displays the at least one permission identifier.

[0051] In an example, the first page identifier of the first application is displayed in a region A in the page identifier display region of the background task management interface, and the at least one permission identifier is displayed in a region B in the first permission identifier display region of the background task management interface. In other words, the target region can include the region A and the region B.

[0052] Exemplarily, the first permission identifier display region can be located on the left side, the right side, the upper side, the lower side, or other possible positions of the page identifier display region.

[0053] For example, the permission identifier displayed in the first permission identifier display area changes along with the page identifier displayed in the page identifier display area. Alternatively, the permission identifier displayed in the first permission identifier display area may be updated based on the page identifier selected by the user in the page identifier display area.

[0054] For example, if the page identifier display area currently displays page identifier 1 of page 1 of APP1, then the corresponding first permission identifier display area will display the permission identifier of APP1. At this time, if the user switches the page identifier displayed in the page identifier display area to page identifier 2 of page 2 of APP2, then the content displayed in the corresponding first permission identifier display area will be updated to the permission identifier of APP2.

[0055] For example, page icons can be switched in the page icon display area via gesture input (such as touch input or swipe input).

[0056] For example, the permission identifiers of enabled permissions and disabled permissions can be distinguished by icons or colors, making it easy for users to check whether the permissions of the selected application meet their needs.

[0057] Example 1, such as Figure 2 As shown, Figure 2 This shows a possible schematic diagram of the background task management interface. Figure 2 In the background task management interface, page identifier display area 31 displays page identifier 32 of APP1 and page identifier 33 of APP2 (i.e., the first page identifier of the first application). Since page identifier 33 of APP2 is located in the selected area of ​​page identifier display area 31 (i.e., area A above), the aforementioned first permission identifier display area 34 will display the four permission identifiers of APP2, namely first permission identifier 35, second permission identifier 36, third permission identifier 37, and fourth permission identifier 38. The first permission identifier display area 34 is located to the right of page identifier area 31.

[0058] It should be noted that, in combination Figure 2 The selected area of ​​page identifier display area 31 will typically display the page identifier selected by the user. For example, if the user selects page identifier 33 for APP2, page identifier 33 will be displayed in the selected area. If the user subsequently selects page identifier 32 for APP1, page identifier 33 can be switched to page identifier 32 in the selected area.

[0059] In another possible example, the first interface described above can include a first application page of the first application. It can be understood that the first interface includes a page display region of the first application page of the first application, and a second permission identifier display region. The second permission identifier display region displays the at least one permission identifier.

[0060] Exemplarily, the second permission identifier display region can be located at the left side, the right side, the top side, the bottom side, or other possible positions of the page display region.

[0061] It should be noted that if the user needs to modify the permission of the first application, the user can directly operate any one of the at least one permission identifier, so as to modify the application permission indicated by the permission identifier, for example, to enable or disable a certain application permission.

[0062] Example 2, Figure 3 An interface diagram of interface A containing a first application page of APP1 is shown. In combination with Figure 3 When the user wants to view the application permission of APP1, the user can long press interface A (i.e., the first input described above), so that the permission management apparatus updates interface A to the first interface. As Figure 4 shown, the first interface includes a page display region 41 and a second permission identifier display region 42, wherein the first application page 43 is displayed in the page display region 41, and four permission identifiers (i.e., at least one permission identifier) are displayed in the second permission identifier display region 42, which are the first permission identifier 44, the second permission identifier 45, the third permission identifier 56, and the fourth permission identifier 47. The user can enable or disable the application permission indicated by any one of the four permission identifiers, for example, the user can perform a click input on any one of the permission identifiers to enable or disable the corresponding application permission.

[0063] In the embodiments of the present application, when the first application is running, the first input can be received, and then the first interface is displayed in response to the first input. The first interface displays at least one permission identifier corresponding to the first application; each permission identifier indicates an application permission of the first application. In this way, if the user needs to modify the permission of the first application, the user can directly modify the application permission indicated by the permission identifier in the at least one permission identifier on the first interface (for example, enable or disable a certain application permission), so as to quickly and conveniently complete the modification of the permission of the first application, and improve the user's experience of using the function of the electronic device.

[0064] Optionally, in the embodiments of the present application, the permission level of the first application is associated with the enabled permission of the first application.

[0065] In the embodiments of the present application, several different permission levels can be set in advance.

[0066] Exemplarily, the permission levels can include three levels of "high, medium and low" permission levels, and different permission levels correspond to different permissions.

[0067] In a possible example, the permission level of the first application is related to the application type of the first application in the application store of the electronic device. That is, different types of applications correspond to different permission levels. It can be understood that if the permission level includes three levels, the application type can also include three types. Therefore, after the user downloads and installs a certain application of a certain type, the corresponding permission level can be directly opened.

[0068] In this way, in the embodiments of the present application, the user can customize different permission levels according to his own permission requirements, and when installing an application, different permission levels can be selected according to different applications.

[0069] In a possible example, the high-level permission level can be provided by the user to customize the content, the medium-level permission level can be preset according to the application of the "classification tag" in the application store of the electronic device, and the low-level permission level can be provided by default to provide most information without limiting the application to obtain.

[0070] It should be noted that the user can customize to open or close the permissions in different permission levels of the user.

[0071] It should be noted that for the medium-level permission level, the corresponding type of application can be set to default permission according to the "permission content" in the application store and the "classification tag" of the application, so as to minimize the allocation of necessary permissions under the premise of ensuring the normal use of the application. The service can be operated by the application store or authorized by the electronic device system, without the user's attention to the details of the corresponding permissions.

[0072] It should be noted that in the high-level permission level, most of the permissions are not granted to real information. In the page of setting the high-level permission, the user can view the private information that can be provided to the outside of the electronic device, and can customize a set of fictitious information to replace his own real private information in actual use. Avoiding the application from being unable to use due to unauthorized use.

[0073] Exemplarily, taking the permission level including "high, medium and low" three levels as an example, the process of setting the permission level can include the following steps.

[0074] S1, the user enters the permission management page of the electronic device.

[0075] S2, set the permission content to be opened in different permission levels.

[0076] Thus, the embodiments of the present application can provide different permission levels for applications, and different permission levels can be assigned to different applications, thereby refining the details of permission management. Different types of applications are configured with different levels of permission management. For some high-risk applications, high-level permission management is directly configured to reduce the possibility of leaking privacy. For some applications that rely on real information and have low risk, low-level permission management is performed according to default authorization. For some commonly used social software, medium-level permission management is directly configured according to the default recommendation of the application store.

[0077] Optionally, in the embodiments of the present application, the application permission management method provided by the embodiments of the present application can further include steps 201 to 204.

[0078] Step 201, receiving a fifth input.

[0079] Step 202, in response to the fifth input, setting all applications in the electronic device to the highest permission level.

[0080] Step 203, receiving a sixth input.

[0081] Step 204, in response to the sixth input, restoring all applications in the electronic device to the initial permission level.

[0082] The permission level of any application in the electronic device is associated with the permission that has been turned on by any application.

[0083] Exemplarily, the fifth input and the sixth input can refer to the description of the first input, for example, can be a touch input or a voice input of the user, or other possible inputs, which can be set according to actual needs.

[0084] Exemplarily, taking APP3 in the electronic device as an example, the scheme of the embodiments of the present application is described. If the permission levels in the electronic device include three levels of "high, medium and low", the initial permission level of APP3 is the medium-level permission level. After receiving the fifth input, the permission level of APP3 is adjusted to the high-level permission level. After receiving the fifth input, the permission level of APP3 returns to the medium-level permission level (i.e. the initial permission level).

[0085] In one possible example, the fifth input can be performed by the first user (e.g. the owner) when the operator of the electronic device is replaced from the first user to the second user. Then, after the second user uses the electronic device, the operator of the electronic device is replaced from the second user to the first user, and the sixth input is performed by the first user.

[0086] Therefore, the embodiments of the present application can assign different permission levels to different users. For example, when the electronic device is handed over from an adult (a first user) to a minor or other person (a second user), the one-key operation can be used to raise the permission of all applications in the entire system to the "high-level" permission level for global permission management.

[0087] In one possible example, if the electronic device is switched from a normal scenario to a first scenario (for example, a scenario in which there is a risk of privacy leakage), the fifth input can be performed. If the electronic device is switched from the first scenario to the normal scenario, the user can perform the sixth input to restore all applications in the electronic device to the initial permission level.

[0088] Therefore, the permission level of all applications installed in the electronic device can be quickly switched between the highest permission level and the initial permission level to meet different application permission requirements of the user, and the data information that does not meet the requirements of the user is prevented from being pushed.

[0089] Optionally, in the embodiments of the present application, when the first interface is a background task management interface, after step 102, the application permission management method provided by the embodiments of the present application further includes steps 103 and 104.

[0090] Step 103, receiving a second input.

[0091] Step 104, in response to the second input, displaying a second interface.

[0092] The second interface includes a first area and a second area. For example, the first area and the second area can be distributed vertically or horizontally, or in other possible forms.

[0093] For example, the second input can refer to the description of the first input, for example, it can be a touch input or a voice input of the user, or other possible inputs, which can be set according to actual requirements.

[0094] In one example, the second input includes an input of the user to the first permission identification display area.

[0095] For example, the first area displays a first application page.

[0096] For example, the second area displays permission information. This permission information includes at least one permission identifier and at least one of the following: historical permission information of the first application and current permission information of the first application. Further, the permission information can be: permission information for all permissions enabled by the first application, or permission information for some permissions enabled by the first application, or permission information for any one permission enabled by the first application. For example, the enabled permissions could be allowing access to location, allowing access to the photo album, allowing access to phone calls, or allowing access to the contacts.

[0097] For example, the above permission information may include: the permission obtained at a certain time, and the specific content of the permission.

[0098] Example 3, combined Figure 2 ,like Figure 5 As shown, the first area 51 is located on the left and the second area 52 is located on the right. The first area displays the first application page 53, and the second area displays permission information 54 and four permission identifiers (i.e., at least one permission identifier): first permission identifier 55, second permission identifier 56, third permission identifier 57, and fourth permission identifier 58.

[0099] It should be noted that, referring to Example 3, if the permission information shows all permissions already enabled for the first application, and the user wants to view the permission information for permission identifier 55, the user can click to select permission identifier 55, and the permission information will be updated to the corresponding permission information. Similarly, if the user wants to view the permission information for both permission identifiers 55 and 57, the user can click to select both permission identifiers 55 and 57, and the permission information will be updated to the corresponding permission information for each.

[0100] It should be noted that when the permission information shows only some of the permissions that the first application has enabled, users can click on the area outside the permission icon to display the permission information for all permissions that the first application has enabled.

[0101] It is understandable that users can directly control and use the first application page in the first area. During the user's use, as the first application runs, the permission information will be updated in real time. Thus, the permission information can display historical permission information and the currently updated permission information, making it convenient for users to check the access status of permissions in real time.

[0102] In this way, users can easily view the content information provided by the corresponding permissions while using the application, and can adjust the authorization level in a timely manner based on the information.

[0103] Optionally, in the embodiments of the present application, the permissions of the first application include enabled permissions and disabled permissions; the permission level of the first application is associated with the enabled permissions of the first application; and the second area further displays a permission level adjustment control.

[0104] Exemplarily, after the step 104, the application permission management method provided in the embodiments of the present application can further include the following steps 105 and 106:

[0105] The step 105 includes receiving a third input to the permission level adjustment control.

[0106] The step 106 includes adjusting the permission level of the first application in response to the third input.

[0107] Exemplarily, the third input can be a touch input, a voice input or other possible input of the user to the permission level adjustment control, which can be set according to actual requirements.

[0108] Exemplarily, the third input can refer to the description of the first input, for example, can be a touch input, a voice input or other possible input of the user, which can be set according to actual requirements.

[0109] Exemplarily, the permission level adjustment control can be in the shape of a bar, a ring or other possible shapes.

[0110] Exemplarily, the permission level adjustment control can display an adjustment cursor thereon, and the third input can be a pressing input or a dragging input to the adjustment cursor, so as to complete the adjustment of the permission level of the first application.

[0111] Exemplarily, in combination with Example 3 and Figure 5 The second area displays a permission level adjustment control 59, and the permission level adjustment control displays an adjustment cursor 60 thereon. The user can drag the adjustment cursor to different positions in the permission level adjustment control, and different positions correspond to different permission levels of the first application.

[0112] In this way, the permission level of the first application can be adjusted conveniently and quickly, and the use experience of the user to the function of the electronic device is improved.

[0113] Optionally, in the embodiments of the present application, when the user does not need to view the permission information, after the step 104, the application permission management method provided in the embodiments of the present application can further include the following steps 107 and 108:

[0114] The step 107 includes receiving a seventh input of the user.

[0115] The step 108 includes displaying a third interface in response to the seventh input.

[0116] The third interface displays the first application page of the first application and / or the at least one permission identifier.

[0117] For example, the seventh input can be a touch input, a voice input, or any other possible input, which can be set according to actual requirements.

[0118] For example, the third interface includes a page display region and a third permission identifier display region, the page display region displays the first application page, and the third permission identifier display region displays the at least one permission identifier.

[0119] In the embodiments of the present application, the third interface can not display the permission information.

[0120] In the embodiments of the present application, the seventh input is an input of the user to the second interface, for example, an input to the first region in the second interface or an input to the second region in the second interface. For example, the permission information can be dragged to cancel the display of the permission information and to display the first application page in an enlarged manner, or the first application page can be clicked to cancel the display of the permission information and to display the first application page in an enlarged manner.

[0121] For example, in combination with Figure 4 , the third interface schematic diagram can refer to Figure 4 , Figure 4 The first application page and four permission identifiers (i.e., the at least one permission identifier) are displayed, which are the first permission identifier 44, the second permission identifier 45, the third permission identifier 56, and the fourth permission identifier 47.

[0122] In this way, the display of the permission information can be canceled according to different permission viewing requirements of the user, so as to fully utilize the display screen of the electronic device.

[0123] Optionally, in the embodiments of the present application, if the user wants to view the permission information again, after step 108, the following steps are further included.

[0124] Step 109: receiving an eighth input of the user to the third interface.

[0125] Step 110: displaying the second interface in response to the eighth input.

[0126] For example, the eighth input can be a touch input, a voice input, or any other possible input, which can be set according to actual requirements.

[0127] In an example, the eighth input can be an input of the user to the third permission identifier display region of the third interface.

[0128] In this way, according to different permission viewing needs of the user, the first application can be normally controlled and used, and the permission information can be conveniently called out to facilitate the user to view.

[0129] Optionally, in the embodiment of the application, the permission of any application in the electronic device includes an enabled permission and a disabled permission; the permission level of any application is associated with the enabled permission of any application; the application permission management method provided by the embodiment of the application can further include the following step 301:

[0130] In step 301, during the running process of the first application page of the first application, if the permission information of the first application does not meet the preset permission requirement, the first prompt information is displayed.

[0131] The first prompt information is used to prompt the abnormal permission of the first application.

[0132] For example, during the running process of the first application, when the permission content is acquired, the corresponding permission identifier can have a corresponding dynamic effect prompt.

[0133] It can be understood that during the normal running process of the first application, the acquired permission information of the enabled permission of the first application should meet the preset permission requirement, if the preset permission requirement is not met, it means that the permission of the first application is abnormal, which has the risk of privacy leakage or other possible risks.

[0134] For example, if the first number (for example, permission frequency) of times of accessing or reading the permission content of the corresponding permission of the first application in a unit time should be less than or equal to the first threshold value, it means that the permission information of the first application meets the preset permission requirement, if the above first number of times is greater than the first threshold value, it means that the permission information of the first application does not meet the preset permission requirement, then the electronic device can display the first prompt information to remind the user to view and adjust the related permission of the first application, so as to avoid the risk of privacy leakage.

[0135] For example, if the first application accesses or reads the permission content of the corresponding permission beyond the necessary and reasonable behavior in a unit time, it means that the permission information of the first application does not meet the preset permission requirement, then the electronic device can display the first prompt information to remind the user to view and adjust the related permission of the first application, so as to avoid the risk of privacy leakage.

[0136] It should be noted that when the user uses the application, if the application cannot be normally used or the use is blocked due to permission and the like, the electronic device can enter the permission management interface through notification reminding and the like to adjust the corresponding permission to ensure normal use. Thus, during the use of the application, the user can dynamically adjust the permission level of the application according to the real-time situation of the permission information.

[0137] It should be noted that the application permission management method provided in the embodiments of the present application can be executed by an application permission management device or a control module in the application permission management device for executing the application permission management method. The application permission management method executed by the application permission management device is taken as an example in the embodiments of the present application to illustrate the application permission management device provided in the embodiments of the present application.

[0138] As shown in Figure 6 The application permission management device provided in the embodiments of the present application includes a receiving module 401 and a display module 402.

[0139] The receiving module 401 is configured to receive a first input in a case where a first application is running.

[0140] The display module 402 is configured to display a first interface in response to the first input received by the receiving module 401.

[0141] The first interface displays at least one permission identifier corresponding to the first application, and each permission identifier indicates an application permission of the first application.

[0142] Optionally, in the embodiments of the present application, the first interface is a background task management interface.

[0143] The target region of the background task management interface displays a first page identifier of the first application and at least one permission identifier, and the first page identifier is used to indicate a first application page of the first application.

[0144] Optionally, in the embodiments of the present application, the receiving module 401 is further configured to receive a second input after the display module 402 displays the first interface.

[0145] The display module 402 is further configured to display a second interface in response to the second input received by the receiving module 401.

[0146] The second interface includes a first region and a second region. The first region displays the first application page, and the second region displays permission information including at least one permission identifier and at least one of the following: historical permission information of the first application and current permission information of the first application.

[0147] Optionally, in the embodiments of the present application, the permissions of the first application include enabled permissions and disabled permissions, the permission level of the first application is associated with the enabled permissions of the first application, and the second region further displays a permission level adjustment control.

[0148] As shown in Figure 7 The device further includes an adjustment module 403.

[0149] The receiving module 401 is further configured to receive a third input on the permission level adjustment control after the display module 402 displays the second interface.

[0150] The adjusting module 403 is configured to adjust the permission level of the first application in response to the third input received by the receiving module.

[0151] Optionally, in the embodiments of the present application, the display module 402 is further configured to display first prompt information during running of a first application page of the first application, if the permission information of the first application does not meet the preset permission requirement.

[0152] The first prompt information is used to prompt that the permission of the first application is abnormal.

[0153] Optionally, in the embodiments of the present application, as shown in Figure 8 The apparatus further includes a setting module 404.

[0154] The receiving module 401 is further configured to receive a fifth input.

[0155] The setting module 404 is configured to set all applications in the electronic device to the highest permission level in response to the fifth input received by the receiving module 401.

[0156] The receiving module 401 is further configured to receive a sixth input.

[0157] The setting module 404 is further configured to restore all applications in the electronic device to the initial permission level in response to the sixth input received by the receiving module 401.

[0158] The permission level of any application in the electronic device is associated with a permission that has been enabled for the any application.

[0159] In the embodiments of the present application, the receiving module can receive the first input in the case that the first application is running, and then the display module can display the first interface in response to the first input received by the receiving module; the first interface displays at least one permission identifier corresponding to the first application; the first interface is an interface related to the first application; and each permission identifier indicates an application permission of the first application. In this way, if the user needs to modify the permission of the first application (for example, to close an enabled permission or to enable an unenabled permission), the user can directly modify (for example, enable or close) the application permission indicated by the permission identifier in the at least one permission identifier on the first interface, so that the user can quickly and conveniently modify the permission of the first application, and the use experience of the user on the function of the electronic device application is improved.

[0160] The beneficial effects of various implementation manners in the embodiments can be referred to the beneficial effects of the corresponding implementation manners in the above method embodiments. To avoid repetition, details are not described here.

[0161] The application permission management device in the embodiments can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. For example, mobile electronic devices can be mobile phones, tablets, laptops, PDAs, in-vehicle electronic devices, wearable devices, ultra-mobile personal computers (UMPCs), netbooks, or personal digital assistants (PDAs), etc., while non-mobile electronic devices can be servers, network attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service machines, etc. This application embodiment does not impose specific limitations.

[0162] The application permission management device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit it.

[0163] The application permission management device provided in this application embodiment can implement all the processes implemented in the above method embodiment. To avoid repetition, it will not be described again here.

[0164] like Figure 9 As shown, this application embodiment also provides an electronic device 200, including a processor 202, a memory 201, and a program or instructions stored in the memory 201 and executable on the processor 202. When the program or instructions are executed by the processor 202, they implement the various processes of the above-described application permission management method embodiment and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0165] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0166] Figure 10 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application.

[0167] The electronic device 1000 includes, but is not limited to, components such as: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0168] Those skilled in the art can understand that the electronic device 1000 can also include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 1010 through a power management system, so that the power management system can realize the functions of managing charging, discharging, and power consumption management. Figure 10 The electronic device structure shown in the above is not a limitation on the electronic device, and the electronic device can include more or fewer components than the diagram, or combine certain components, or different component arrangements, which are not described here.

[0169] The user input unit 1007 is configured to receive a first input in a case where a first application is running.

[0170] The display unit 1006 is configured to display a first interface in response to the first input received by the user input unit 1007.

[0171] The first interface displays at least one permission identifier corresponding to the first application; each permission identifier indicates an application permission of the first application.

[0172] Optionally, the first interface is a background task management interface.

[0173] The target region of the background task management interface displays a first page identifier of the first application and at least one permission identifier; the first page identifier is used to indicate a first application page of the first application.

[0174] Optionally, the user input unit 1007 is further configured to receive a second input after the display unit 1006 displays the first interface.

[0175] The display unit 1006 is further configured to display a second interface in response to the second input received by the user input unit 1007.

[0176] The second interface includes a first region and a second region; the first region displays the first application page; and the second region displays permission information including at least one permission identifier and at least one of the following: historical permission information of the first application and current permission information of the first application.

[0177] Optionally, the permissions of the first application include enabled permissions and disabled permissions; the permission level of the first application is associated with the enabled permissions of the first application; the second region further displays a permission level adjustment control; and the electronic device further includes an adjustment unit.

[0178] The user input unit 1007 is further configured to receive a third input on the permission level adjustment control after the display unit 1006 displays the second interface.

[0179] The adjusting unit is configured to adjust the permission level of the first application in response to a third input received by the user input unit 1007.

[0180] Optionally, the display unit 1006 is further configured to display first prompt information if the permission information of the first application does not meet the preset permission requirement during running of a first application page of the first application.

[0181] The first prompt information is used to prompt that the permission of the first application is abnormal.

[0182] Optionally, the electronic device further includes a setting unit.

[0183] The user input unit 1007 is further configured to receive a fifth input.

[0184] The setting unit is configured to set all applications in the electronic device to the highest permission level in response to the fifth input received by the user input unit 1007.

[0185] The user input unit 1007 is further configured to receive a sixth input.

[0186] The setting unit is further configured to restore all applications in the electronic device to the initial permission level in response to the sixth input received by the user input unit 1007.

[0187] The permission level of any application in the electronic device is associated with a permission that has been enabled for the application.

[0188] The electronic device provided by the embodiment of the present application can receive a first input when a first application is running, and then the display unit can display a first interface in response to the first input received by the receiving module; at least one permission identifier corresponding to the first application is displayed on the first interface; each permission identifier indicates an application permission of the first application. Therefore, when the user uses the application and cannot normally use it due to the permission, or the use is blocked, or the user needs to modify the permission of the first application (for example, closes the enabled permission or enables the unenabled permission) due to other reasons, the user can directly modify (for example, enable or close) the application permission indicated by the permission identifier in the at least one permission identifier on the first interface, so that the modification of the permission of the first application is quickly and conveniently completed, and the user experience of the function of the electronic device application is improved.

[0189] The beneficial effects of the various implementation manners in the embodiment can be referred to the beneficial effects of the corresponding implementation manners in the method embodiments, and details are not described herein again to avoid repetition.

[0190] It should be understood that in the embodiments of the present application, the input unit 1004 can include a graphics processing unit (GPU) 10041 and a microphone 10042. The graphics processing unit 10041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1006 can include a display panel 10061, which can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 can include two parts of a touch detection device and a touch controller. The other input devices 10072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), trackballs, mice, joysticks, etc., which will not be described here. The memory 1009 can be used to store software programs and various data, including but not limited to application programs and operating systems. The processor 1010 can integrate an application processor and a modem processor, wherein the application processor mainly processes operating systems, user interfaces and application programs, etc., and the modem processor mainly processes wireless communication. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 1010.

[0191] The embodiments of the present application also provide a readable storage medium, which stores programs or instructions, and the programs or instructions are executed by a processor to realize the processes of the above-mentioned application permission management method embodiments and achieve the same technical effects. To avoid repetition, details will not be described here.

[0192] The processor is a processor in the electronic device in the above-mentioned embodiments. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc. The embodiments of the present application also provide a chip, which includes a processor and a communication interface. The communication interface is coupled with the processor. The processor is used to run programs or instructions to realize the processes of the above-mentioned application permission management method embodiments and achieve the same technical effects. To avoid repetition, details will not be described here.

[0193] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip, etc.

[0194] It should be noted that, in the present document, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises the element. Furthermore, it is to be understood that the method and apparatus of the present application can be carried out by more than one process, method, article, or apparatus either simultaneously, concurrently, or with intervening action that are carried out at the same time, either in a simultaneous fashion or in a fashion that is interleaved in time. For example, the described methods can be performed in a different order from that described, and / or various steps can be combined or omitted, and / or additional steps can be added, without departing from the scope of the present application. Also, features described with respect to certain examples can be combined in other examples.

[0195] From the above description of the embodiments, it is apparent that the above-mentioned method can be realized by means of software and necessary universal hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solution of the present application can be embodied in the form of computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a plurality of instructions for making a terminal (which can be a mobile phone, computer, server, or network equipment, etc.) execute the method described in various embodiments of the present application.

[0196] The embodiments of the present application are described above in conjunction with the drawings, but the present application is not limited to the above-described specific embodiments, which are merely illustrative rather than restrictive, and a person of ordinary skill in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the protection scope of the claims.

Claims

1. An application permission management method, characterized in that, The method includes: While the first application is running, receive the first input; In response to the first input, the first interface is displayed; The first interface displays at least one permission identifier corresponding to the first application. Each of the permission identifiers indicates an application permission of the first application; wherein, the first interface is: a background task management interface; the target area of ​​the background task management interface displays the first page identifier of the first application and the at least one permission identifier; the first page identifier is used to indicate the first application page of the first application; After displaying the first interface, the method further includes: Receive the second input; In response to the second input, a second interface is displayed; The second interface includes a first area and a second area; The first area displays the first application page; the second area displays permission information, which includes at least one permission identifier and at least one of the following: historical permission information of the first application and current permission information of the first application; The permissions of the first application include enabled permissions and disabled permissions; the permission level of the first application is associated with the enabled permissions of the first application; the second area also displays permission level adjustment controls; After displaying the second interface, the method further includes: Receive a third input to the permission level adjustment control; In response to the third input, adjust the permission level of the first application; Wherein, the first application has a high permission level, which allows the first application to read false privacy information provided by the permissions that the first application has enabled; The first application has a high permission level, which allows the first application to read the minimum real privacy information required to maintain the operation of the first application from the permissions that the first application has enabled; The first application has a low permission level, which does not restrict the first application from reading real privacy information in the permissions that the first application has enabled.

2. The method according to claim 1, characterized in that, The method also includes, If the permission information of the first application does not meet the preset permission requirements during the operation of the first application's first application page, the first prompt message will be displayed. The first prompt message is used to indicate that the first application has abnormal permissions.

3. The method according to claim 1, characterized in that, The method also includes, Receive the fifth input; In response to the fifth input, all applications in the electronic device are set to the highest permission level; Receive the sixth input; In response to the sixth input, all applications in the electronic device are restored to their initial permission levels; The permission level of any application in the electronic device is associated with the permissions that the application has enabled.

4. An application permission management device, characterized in that, The device includes: A receiving module is used to receive a first input when the first application is running; The display module is used to display a first interface in response to the first input received by the receiving module; The first interface displays at least one permission identifier corresponding to the first application. Each of the permission identifiers indicates an application permission of the first application; The first interface is: the background task management interface; The target area of ​​the background task management interface displays the first page identifier of the first application and the at least one permission identifier; The first page identifier is used to indicate the first application page of the first application; The receiving module is also configured to receive a second input after the display module displays the first interface; The display module is also used to display a second interface in response to a second input received by the receiving module; The second interface includes a first area and a second area; The first area displays the first application page; the second area displays permission information, which includes at least one permission identifier and at least one of the following: historical permission information of the first application and current permission information of the first application; The permissions of the first application include enabled permissions and disabled permissions; the permission level of the first application is associated with the enabled permissions of the first application; the second area also displays permission level adjustment controls; The device also includes an adjustment module; The receiving module is also configured to receive a third input to the permission level adjustment control after the display module displays the second interface; The adjustment module is used to adjust the permission level of the first application in response to the third input received by the receiving module. Wherein, the first application has a high permission level, which allows the first application to read false privacy information provided by the permissions that the first application has enabled; The first application has a high permission level, which allows the first application to read the minimum real privacy information required to maintain the operation of the first application from the permissions that the first application has enabled; The first application has a low permission level, which does not restrict the first application from reading real privacy information in the permissions that the first application has enabled.

5. The apparatus according to claim 4, characterized in that, The display module is also used to display a first prompt message if the permission information of the first application does not meet the preset permission requirements during the operation of the first application page of the first application. The first prompt message is used to indicate that the first application has abnormal permissions.

6. The apparatus according to claim 4, characterized in that, The device also includes a setting module; The receiving module is also used to receive a fifth input; The setting module is used to set all applications in the electronic device to the highest permission level in response to the fifth input received by the receiving module; The receiving module is also used to receive a sixth input; The setting module is also configured to, in response to the sixth input received by the receiving module, restore all applications in the electronic device to their initial permission levels; The permission level of any application in the electronic device is associated with the permissions that the application has enabled.

7. An electronic device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein when the program or instructions are executed by the processor, they implement the steps of the application permission management method as described in any one of claims 1 to 3.

8. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the application permission management method as described in any one of claims 1 to 3.

Images