Application permission management methods, devices and electronic devices

Abstract

The present application discloses an application permission management method, device and electronic device, which belongs to the field of communication technology and can solve the problem of low flexibility of electronic devices in prompting application permissions. The method includes: receiving a first input from a user while displaying a first interface of an application store, the first interface includes at least one application identifier and at least one permission identifier corresponding to the application indicated by each application identifier, each permission identifier is used to indicate an application permission, the first input is the user's input of a target application identifier in at least one application identifier; in response to the first input, downloading and installing a target application based on M application permissions, the M application permissions are application permissions that the target application is allowed to access in at least one application permission corresponding to the target application, the target application is the application indicated by the target application identifier, and M is a positive integer.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to an application permission management method, device and electronic device. Background Art

[0002] Usually, when a user installs an application through an electronic device, the electronic device will prompt the user whether to allow the application to obtain corresponding permissions (such as camera, address book, etc.) for the user to choose. However, among these permissions corresponding to the application, there may be some privacy permissions (that is, permissions that the user needs to prohibit the application from accessing), so the user usually chooses to prohibit the application from obtaining the corresponding permissions.

[0003] However, when the user subsequently uses the application and requires the application to access certain permissions, the user needs to set the permissions allowed for the application again in the settings application, so the flexibility of the electronic device in prompting the application for permissions is low. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide an application permission management method, device and electronic device, which can solve the problem of low flexibility in prompting the permissions of application programs by electronic devices.

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

[0006] In a first aspect, an embodiment of the present application provides an application permission management method, which includes: receiving a first input from a user while displaying a first interface of an application store, the first interface including at least one application identifier and at least one permission identifier corresponding to an application indicated by each application identifier, each permission identifier being used to indicate an application permission, the first input being an input by the user of a target application identifier in at least one application identifier; in response to the first input, downloading and installing a target application based on M application permissions, the M application permissions being application permissions allowed to be accessed by the target application in at least one application permission corresponding to the target application, the target application being the application indicated by the target application identifier, and M being a positive integer.

[0007] In a second aspect, an embodiment of the present application provides an application permission management device, which includes: a receiving module and a downloading module. The receiving module is used to receive a first input from a user while displaying a first interface of an application store, wherein the first interface includes at least one application identifier and at least one permission identifier corresponding to an application indicated by each application identifier, each permission identifier is used to indicate an application permission, and the first input is an input of a target application identifier in at least one application identifier by the user. The downloading module is used to download and install a target application based on M application permissions in response to the first input received by the receiving module, wherein the M application permissions are application permissions that are allowed to be accessed by the target application in at least one application permission corresponding to the target application, and the target application is the application indicated by the target application identifier, and M is a positive integer.

[0008] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

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

[0010] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.

[0011] In an embodiment of the present application, when displaying the first interface of the application store, the electronic device can download and install the target application based on M application permissions according to the user's first input, the first interface includes at least one application identifier and at least one permission identifier corresponding to the application indicated by each application identifier, and the M application permissions are application permissions that the target application is allowed to access among the at least one application permission corresponding to the target application. Since the electronic device can display at least one application identifier and at least one permission identifier corresponding to the application indicated by each application identifier in the interface of the application store when displaying the interface of the application store to prompt the user of the application permissions corresponding to each application, when the user needs to download a certain application, the user can input the application identifier of the application, so that the electronic device can install the target application based on the application permissions that correspond to the application and are allowed to access the application, without the user having to subsequently set the application permissions corresponding to the application, thereby improving the efficiency of the electronic device in installing applications and improving the flexibility of the electronic device in prompting application permissions. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 This is one of the schematic diagrams of an application permission management method provided in an embodiment of the present application;

[0013] Figure 2 This is one of the example schematic diagrams of a mobile phone interface provided in an embodiment of the present application;

[0014] Figure 3 This is a second schematic diagram of an application permission management method provided in an embodiment of the present application;

[0015] Figure 4 This is a third schematic diagram of an application permission management method provided in an embodiment of the present application;

[0016] Figure 5 This is a second example schematic diagram of an interface of a mobile phone provided in an embodiment of the present application;

[0017] Figure 6 This is a fourth schematic diagram of an application permission management method provided in an embodiment of the present application;

[0018] Figure 7 This is a third example schematic diagram of an interface of a mobile phone provided in an embodiment of the present application;

[0019] Figure 8 It is a structural diagram of an application permission management device provided in an embodiment of the present application;

[0020] Fig. 9 This is one of the hardware structure diagrams of an electronic device provided in an embodiment of the present application;

[0021] Fig.10 This is the second schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions 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 ordinary technicians in this field without creative work are within the scope of protection of this application.

[0023] The terms "first", "second", etc. 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 interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0024] The following is a detailed description of the application permission management method provided by the embodiment of the present application through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0025] In response to the problem in the related art that when an electronic device installs an application, the setting of application access permissions is relatively inconvenient and inflexible, an embodiment of the present application provides a solution for managing application permissions corresponding to an application: when a user downloads an application through an electronic device, the electronic device can directly display some permission identifiers corresponding to the application, so that the user can select a permission identifier that allows the application to access application permissions from these permission identifiers, thereby realizing quick setting of application permissions corresponding to the application.

[0026] In one implementation of the embodiment of the present application, the electronic device can display the identifier of the corresponding application permission (i.e., the permission identifier) ​​of each application in the download interface, and provide an option (such as a "switch" option) for each application permission for the user to select, and after the user selects, it can be installed with one click. In this way, it can avoid multiple pop-up boxes after downloading to ask the user to choose whether to enable this permission, thereby reducing the power consumption caused by multiple pop-up boxes and reducing the complexity of the mobile phone system.

[0027] In another implementation method of the embodiment of the present application, the user can customize general rules (for example, the user pre-sets whether to allow the corresponding permission identifier to be displayed in the form of a pop-up window) or set permissions for each category according to the category of the application. The electronic device can match the rules according to the user-defined rules and analyze the user's permission information required by the application, and enable the application that meets the matching requirements. Then the user can quickly install it without being disturbed by pop-up windows.

[0028] The present application provides an application permission management method. Figure 1 A flowchart of an application permission management method provided by an embodiment of the present application is shown, and the method can be applied to electronic devices. Figure 1 As shown, the application permission management method provided in the embodiment of the present application may include the following steps 201 and 202.

[0029] Step 201: While displaying a first interface of an application store, the electronic device receives a first input from a user.

[0030] In an embodiment of the present application, the above-mentioned first interface includes at least one application identifier and at least one permission identifier corresponding to the application indicated by each application identifier, each permission identifier is used to indicate an application permission, and each application identifier is used to indicate an application, and the above-mentioned first input is the user's input of the target application identifier in the at least one application identifier.

[0031] In an embodiment of the present application, after the user opens an application that can download various applications (such as an application mall / app store), the electronic device can display installation options for each application, such as the application identifier of the application (such as including a name and icon, etc.), the data packet size of the application, the number of installed devices, etc.

[0032] It should be noted that the application identifier can be understood as: an installation option of an application or an installation label of an application. The application identifier may include at least one of the following: the name of the application, the icon of the application, the data packet size of the application, and the download control of the application (used to download and install the application), etc. The user can input the application identifier so that the electronic device can download and install the application indicated by the application identifier.

[0033] Optionally, in an embodiment of the present application, the first input may be a user's selection input of a target application identifier (eg, a click input of a download control) to trigger the electronic device to download and install the target application.

[0034] It should be noted that downloading and installing an application can be understood as: downloading and installing a data package of the application.

[0035] Optionally, in an embodiment of the present application, application permissions may include at least one of the following: storage permission, address book permission, location permission, camera permission, microphone permission, phone permission, address permission, etc.

[0036] Optionally, in an embodiment of the present application, the electronic device may add a permission enable switch option (such as whether to enable storage permission, whether to enable address book reading permission, etc.) in the area corresponding to each application identifier so that the user can make a selection.

[0037] For example, the electronic device is a mobile phone. Figure 2 As shown, the mobile phone displays a first interface 10, which includes at least one application identifier, such as application identifiers 11 to 13, each of which includes the name of the application, the icon of the application, and the download control of the application; the user can make a first input to the target application identifier (such as application identifier 11) in the at least one application identifier, so that the mobile phone displays at least one permission identifier corresponding to the target application (such as an address book permission identifier, a location permission identifier, a camera permission identifier, and a storage permission identifier) ​​in the area corresponding to the target application identifier, so that the user can select from these permission identifiers (such as the address book permission identifier, the location permission identifier, and the camera permission identifier) ​​to set the application permissions corresponding to the target application.

[0038] Step 202: The electronic device downloads and installs a target application based on M application permissions in response to the first input.

[0039] In the embodiment of the present application, the above-mentioned M application permissions are application permissions that the target application is allowed to access among at least one application permission corresponding to the target application, the above-mentioned target application is the application indicated by the target application identifier, and M is a positive integer.

[0040] In an embodiment of the present application, after receiving the first input, the electronic device can parse the target application to obtain at least one application permission corresponding to the target application, and determine the application permissions allowed to be accessed by the target application from the at least one application permission, so as to download and install the target application based on these application permissions.

[0041] It should be noted that the at least one application permission corresponding to the target application can be understood as: at least one application permission that the target application can use.

[0042] Optionally, in the embodiment of the present application, the electronic device may determine M application permissions in the following three ways:

[0043] In one implementation of the embodiment of the present application, when the electronic device displays at least one permission identifier corresponding to the target application, the user can select M permission identifiers from the at least one permission identifier before performing a download input (i.e., a first input), so that the electronic device sets M application permissions corresponding to the target application. Figure 1 ,like Figure 3 As shown, before "the electronic device receives the first input of the user" in the above step 201, the application permission management method provided in the embodiment of the present application also includes the following steps 301 and 302.

[0044] Step 301: While displaying a first interface of an application store, the electronic device receives a second input from a user.

[0045] In the embodiment of the present application, the second input is the user's input of M permission identifiers, and the M permission identifiers are permission identifiers in at least one permission identifier corresponding to the target application identifier.

[0046] Optionally, in an embodiment of the present application, the second input is a user's selection input of M permission identifiers.

[0047] Step 302: In response to the second input, the electronic device sets the M application permissions indicated by the M permission identifiers to allow the target application to access the M application permissions.

[0048] It can be understood that after the electronic device downloads the target application based on M application permissions, when the electronic device subsequently uses the target application, when the electronic device accesses a certain application permission, if the application permission is any application permission among the M application permissions, the electronic device can directly access the application permission.

[0049] It should be noted that, in the case of executing the above steps 301 and 302, the above step 201 is: the electronic device receives a first input from a user.

[0050] In an embodiment of the present application, when a user chooses to install an application, he or she can select the application permissions corresponding to the application, thereby eliminating the need for the user to subsequently set the application permissions corresponding to the application, thereby improving the flexibility of the electronic device in prompting the application's permissions and the efficiency of installing the application.

[0051] In another implementation of the embodiment of the present application, after receiving the download input from the user, the electronic device may display a prompt message to prompt the user to set application permissions to allow the target application to access. Figure 1 ,like Figure 4As shown, before "downloading and installing the target application based on M application permissions" in the above step 202, the application permission management method provided in the embodiment of the present application also includes the following steps 401 to 403.

[0052] Step 401: The electronic device displays first prompt information in response to a first input.

[0053] In an embodiment of the present application, the above-mentioned first prompt information includes L permission identifiers, and the first prompt information is used to prompt the user to set application permissions allowed for access by the target application. The L permission identifiers are permission identifiers among at least one permission identifier corresponding to the target application, and L is an integer greater than or equal to M.

[0054] It can be understood that the above L permission identifiers are part of or all of the at least one permission identifier corresponding to the target application. After receiving the first input, the electronic device can display certain permission identifiers corresponding to the target application in the form of prompt information to facilitate the user to set application permissions.

[0055] Optionally, in the embodiment of the present application, the L permission identifiers may be partial permission identifiers pre-selected by the user. Before the above step 201, the application permission management method provided in the embodiment of the present application further includes the following steps 404 and 405.

[0056] Step 404: While displaying the authority management interface, the electronic device receives a fourth input from the user.

[0057] In the embodiment of the present application, the above-mentioned permission management interface includes at least one permission identifier corresponding to the target application, and the above-mentioned fourth input is the user's input of L permission identifiers among the at least one permission identifier corresponding to the target application.

[0058] In an embodiment of the present application, a user can trigger the opening of a setting application in advance and display a permission management interface, which includes at least one permission identifier corresponding to multiple applications. The user can select and input L permission identifiers from at least one permission identifier corresponding to the target application to trigger the electronic device to select L permission identifiers.

[0059] Step 405: In response to the fourth input, the electronic device determines the L permission identifiers as permission identifiers that allow prompting when downloading the target application.

[0060] For example, Figure 5As shown, the mobile phone displays a permission management interface, which includes at least one permission identifier corresponding to the target application, such as a storage permission identifier, a phone permission identifier, a camera permission identifier, and a microphone permission identifier; the user can make a fourth input for L permission identifiers (such as a phone permission identifier, a camera permission identifier, and a microphone permission identifier) ​​among the at least one permission identifier, so that the mobile phone can determine the L permission identifiers as permission identifiers that are allowed to be prompted when downloading the target application, so that when the user subsequently downloads the target application, the electronic device can prompt the user with the L permission identifiers in the form of prompt information, so that the user can set M application permissions based on the L permission identifiers.

[0061] In an embodiment of the present application, the user sets in advance the application identifier that allows prompt information when using the application, so that the electronic device can, according to the user's usage needs, when subsequently installing the application, not directly prompt the user for all application permissions corresponding to the application, but prompt the user for the application permissions that have been set in advance, that is, flexibly displaying the permission identifier that enables application permission setting, thereby improving the flexibility of the electronic device in prompting application permissions and the efficiency of installing applications.

[0062] Step 402: The electronic device receives a third input from the user.

[0063] In the embodiment of the present application, the third input is the user's input of M permission identifiers out of L permission identifiers.

[0064] Step 403: In response to the third input, the electronic device sets the M application permissions indicated by the M permission identifiers to allow the target application to access the M application permissions.

[0065] It should be noted that, when executing the above steps 401 to 403, the above step 202 is: the electronic device downloads and installs the target application based on M application permissions.

[0066] In an embodiment of the present application, before downloading a target application, the electronic device may first prompt the user to set application permissions to allow the target application to access in the form of a prompt message, thereby allowing the user to flexibly set the application permissions corresponding to the target application without the user having to set the application permissions corresponding to the application when using the application later, thereby improving the flexibility of the electronic device in prompting application permissions and the efficiency of installing applications.

[0067] In another implementation of the embodiment of the present application, after receiving the download input from the user, the electronic device may display prompt information according to the application category to which the target application belongs, so as to prompt the user to set application permissions to allow the target application to access. Figure 1 ,like Figure 6 As shown, before "downloading and installing the target application based on M application permissions" in the above step 202, the application permission management method provided in the embodiment of the present application also includes the following steps 501 to 504.

[0068] Step 501: In response to a first input, the electronic device determines a target application category to which a target application belongs and P application permissions corresponding to the target application category.

[0069] Wherein, P is an integer greater than or equal to M.

[0070] In an embodiment of the present application, the electronic device can search for the identifier of the target application from multiple category groups (each category group includes at least one application identifier, and one category group corresponds to one application category) to determine the application category to which the target application belongs.

[0071] Optionally, in the embodiment of the present application, the above-mentioned multiple category groups may be pre-set or default for the electronic device. Each application category corresponds to at least one application permission, and the application permissions corresponding to each application category are completely different or partially different.

[0072] It can be understood that the above P permission identifiers are part of or all of the at least one permission identifier corresponding to the target application category. After receiving the first input, the electronic device can first determine the application category of the target application and determine at least one permission identifier corresponding to the application category, and then display the P permission identifiers in the at least one permission identifier in the form of prompt information to facilitate the user to set application permissions.

[0073] Optionally, in the embodiment of the present application, the P permission identifiers may be partial permission identifiers pre-selected by the user. Before the above step 201, the application permission management method provided in the embodiment of the present application further includes the following steps 505 and 506.

[0074] Step 505: When the authority management interface is displayed, the electronic device receives a sixth input from the user.

[0075] In an embodiment of the present application, the above-mentioned permission management interface includes at least one category identifier and at least one permission identifier corresponding to each category identifier, each category identifier is used to indicate an application category, and the above-mentioned sixth input is the user's input of P permission identifiers out of at least one permission identifier corresponding to the target category identifier, and the target category identifier is the category identifier corresponding to the target application category.

[0076] In an embodiment of the present application, a user can pre-trigger the opening of a settings application and display a permission management interface, which includes at least one permission identifier corresponding to multiple application categories. The user can select and input P permission identifiers from at least one permission identifier corresponding to the application category to which the target application belongs to trigger the electronic device to select P permission identifiers.

[0077] Step 506: In response to the sixth input, the electronic device sets the P application permissions indicated by the P permission identifiers to allow the target application to access the P application permissions.

[0078] For example, Figure 7 As shown, the mobile phone displays a permission management interface, which includes at least one category identifier (such as a communication and social category identifier, a travel category identifier, and a photography category identifier) ​​and at least one permission identifier corresponding to each category identifier (such as an address book permission identifier, a location permission identifier, a camera permission identifier, and a storage permission identifier); the user can make a sixth input for some of the permission identifiers corresponding to any category identifier, so that the mobile phone can determine these permission identifiers as permission identifiers that are allowed to be prompted when downloading the corresponding application, so that when the user subsequently downloads the corresponding application, the electronic device can prompt the user with these permission identifiers in the form of prompt information, so that the user can set M application permissions based on these permission identifiers.

[0079] In an embodiment of the present application, the user sets application permissions corresponding to different application categories in advance so that the electronic device can, based on the user's usage needs, prompt the user with corresponding application permissions when subsequently installing the application according to the application category to which the application belongs. That is, the permission identifier that enables application permission setting is flexibly displayed, thereby improving the flexibility of the electronic device in prompting the application's permissions and the efficiency of installing the application.

[0080] Step 502: The electronic device displays a second prompt message.

[0081] In the embodiment of the present application, the second prompt information includes P permission identifiers corresponding to P application permissions, and the second prompt information is used to prompt the user to set application permissions that are allowed to be accessed by the target application.

[0082] Step 503: The electronic device receives a fifth input from the user.

[0083] In the embodiment of the present application, the fifth input is the user's input of M permission identifiers out of P permission identifiers.

[0084] Step 504: In response to the fifth input, the electronic device sets the M application permissions indicated by the M permission identifiers to allow the target application to access the M application permissions.

[0085] It should be noted that, when executing the above steps 501 to 504, the above step 202 is: the electronic device downloads and installs the target application based on M application permissions.

[0086] In an embodiment of the present application, before downloading a target application, the electronic device can obtain P application permissions corresponding to the target application category to which the target application belongs, and prompt the user to set application permissions allowed to be accessed by the target application in the form of prompt information, thereby allowing the user to flexibly set the application permissions corresponding to the target application without the user having to set the application permissions corresponding to the application when using the application later, thereby improving the flexibility of the electronic device in prompting application permissions and the efficiency of installing applications.

[0087] The embodiment of the present application provides an application permission management method, in which, when displaying the first interface of the application store, the electronic device can download and install the target application based on M application permissions according to the first input of the user, the first interface includes at least one application identifier and at least one permission identifier corresponding to the application indicated by each application identifier, and the M application permissions are application permissions that the target application is allowed to access among the at least one application permission corresponding to the target application. Since the electronic device can display at least one application identifier in the interface of the application store while displaying at least one permission identifier corresponding to the application indicated by each application identifier to prompt the user of the application permissions corresponding to each application, when the user needs to download a certain application, the user can input the application identifier of the application, so that the electronic device can install the target application based on the application permissions corresponding to the application and allowed to access by the application, without the user having to subsequently set the application permissions corresponding to the application, thereby improving the efficiency of the electronic device in installing applications and improving the flexibility of the electronic device in prompting the permissions of applications.

[0088] It should be noted that the application permission management method provided in the embodiment 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. In the embodiment of the present application, the application permission management device provided in the embodiment of the present application is described by taking the application permission management device executing the application permission management method as an example.

[0089] Figure 8 A possible structural diagram of the application rights management device involved in the embodiment of the present application is shown. Figure 8 As shown, the application rights management device 70 may include: a receiving module 71 and a downloading module 72 .

[0090] The receiving module 71 is used to receive a first input from a user while displaying the first interface of the application store. The first interface includes at least one application identifier and at least one permission identifier corresponding to the application indicated by each application identifier. Each permission identifier is used to indicate an application permission. The first input is the user's input of a target application identifier in at least one application identifier. The downloading module 72 is used to download and install a target application based on M application permissions in response to the first input received by the receiving module 71. The M application permissions are application permissions that the target application is allowed to access in at least one application permission corresponding to the target application. The target application is the application indicated by the target application identifier, and M is a positive integer.

[0091] In a possible implementation, the above-mentioned receiving module 71 is also used to receive a second input from the user before receiving the first input from the user, the second input being the user's input of M permission identifiers, and the M permission identifiers are permission identifiers in at least one permission identifier corresponding to the target application identifier. The application permission management device 70 provided in the embodiment of the present application also includes: a setting module. Among them, the setting module is used to set the M application permissions indicated by the M permission identifiers to: allow the target application to access the M application permissions in response to the second input received by the receiving module 71.

[0092] In a possible implementation, the application permission management device 70 provided in the embodiment of the present application also includes: a display module and a setting module. Among them, the display module is used to display a first prompt message before the download module 72 downloads and installs the target application based on M application permissions. The first prompt message includes L permission identifiers. The first prompt message is used to prompt the user to set the application permissions that the target application is allowed to access. The L permission identifiers are permission identifiers in at least one permission identifier corresponding to the target application, and L is an integer greater than or equal to M. The above-mentioned receiving module 71 is also used to receive a third input from the user, and the third input is the user's input of M permission identifiers out of the L permission identifiers. The setting module is used to set the M application permissions indicated by the M permission identifiers to: allow the target application to access the M application permissions in response to the third input received by the receiving module 71.

[0093] In a possible implementation, the above-mentioned receiving module 71 is also used to receive the user's fourth input before receiving the user's first input when displaying the first interface of the application store, and when displaying the permission management interface, the permission management interface includes at least one permission identifier corresponding to the target application, and the fourth input is the user's input of L permission identifiers. The application permission management device 70 provided in the embodiment of the present application also includes: a determination module. Among them, the determination module is used to determine the L permission identifiers as permission identifiers that are allowed to be prompted when downloading the target application in response to the fourth input received by the receiving module 71.

[0094] In a possible implementation, the application permission management device 70 provided in the embodiment of the present application also includes: a determination module, a display module and a setting module. Among them, the determination module is used to determine the target application category to which the target application belongs and the P application permissions corresponding to the target application category before the download module 72 downloads and installs the target application based on the M application permissions, where P is an integer greater than or equal to M. The display module is used to display a second prompt message, which includes P permission identifiers corresponding to the P application permissions, and the second prompt message is used to prompt the user to set the application permissions that the target application is allowed to access. The above-mentioned receiving module 71 is also used to receive the user's fifth input, which is the user's input of M permission identifiers among the P permission identifiers. The setting module is used to set the M application permissions indicated by the M permission identifiers to: allow the target application to access the M application permissions in response to the fifth input received by the receiving module 71.

[0095] In a possible implementation, the receiving module 71 is also used to receive the user's sixth input before receiving the user's first input when displaying the first interface of the application store, and when displaying the permission management interface, the permission management interface includes at least one category identifier and at least one permission identifier corresponding to each category identifier, each category identifier is used to indicate an application category, and the sixth input is the user's input of P permission identifiers in at least one permission identifier corresponding to the target category identifier, and the target category identifier is the category identifier corresponding to the target application category. The determination module is also used to determine the P permission identifiers as permission identifiers that allow prompts when downloading applications of the target application category in response to the sixth input received by the receiving module 71.

[0096] An embodiment of the present application provides an application permission management device. When displaying an interface of an application store, the application permission management device can display at least one application identifier in the interface and at least one permission identifier corresponding to the application indicated by each application identifier, so as to prompt the user of the application permissions corresponding to each application. When the user needs to download an application, the user can input the application identifier of the application, so that the application permission management device can install the target application based on the application permissions corresponding to the application and allowed to be accessed by the application, without the user having to subsequently set the application permissions corresponding to the application, thereby improving the efficiency of the application permission management device in installing applications and improving the flexibility of the application permission management device in prompting the permissions of applications.

[0097] The application permission management device provided in the embodiment of the present application can implement each process implemented by the electronic device in the above method embodiment. To avoid repetition, the detailed description will not be repeated here.

[0098] The application rights management device in the embodiment of the present application 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. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc. The non-mobile electronic device can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0099] The application rights management device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0100] Alternatively, if Fig. 9 As shown, an embodiment of the present application also provides an electronic device 800, including a processor 801, a memory 802, and a program or instruction stored in the memory 802 and executable on the processor 801. When the program or instruction is executed by the processor 801, each process of the above-mentioned method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0101] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0102] Fig.10 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of the present application.

[0103] The electronic device 100 includes but is not limited to components such as a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110.

[0104] Those skilled in the art will appreciate that the electronic device 100 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 110 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.10 The electronic device structure shown in the figure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0105] Among them, the user input unit 107 is used to receive the user's first input when displaying the first interface of the application store, and the first interface includes at least one application identifier and at least one permission identifier corresponding to the application indicated by each application identifier, each permission identifier is used to indicate an application permission, and the first input is the user's input of the target application identifier in the at least one application identifier.

[0106] The processor 110 is used to download and install a target application in response to a first input based on M application permissions, where the M application permissions are application permissions allowed to be accessed by the target application among at least one application permission corresponding to the target application, and the target application is an application indicated by a target application identifier, and M is a positive integer.

[0107] An embodiment of the present application provides an electronic device. When the electronic device displays an interface of an application store, it can display at least one application identifier in the interface and at least one permission identifier corresponding to the application indicated by each application identifier, so as to prompt the user of the application permissions corresponding to each application. When the user needs to download an application, the user can input the application identifier of the application, so that the electronic device can install the target application based on the application permissions corresponding to the application and allowed to be accessed by the application, without the user having to subsequently set the application permissions corresponding to the application, thereby improving the efficiency of the electronic device in installing applications and improving the flexibility of the electronic device in prompting the permissions of applications.

[0108] Optionally, the user input unit 107 is further used to receive a second input from the user before receiving a first input from the user, where the second input is the user's input of M permission identifiers, where the M permission identifiers are permission identifiers among at least one permission identifier corresponding to the target application identifier.

[0109] The processor 110 is further configured to, in response to the second input, set the M application permissions indicated by the M permission identifiers to: allow the target application to access the M application permissions.

[0110] It should be understood that in the embodiment of the present application, the input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Other input devices 1072 may include but are not limited to a physical keyboard, a function key (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which will not be repeated here. The memory 109 can be used to store software programs and various data, including but not limited to applications and operating systems. The processor 110 can integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, the user interface, and the application program, etc., and the modem processor mainly processes wireless communication. It is understandable that the above-mentioned modem processor may not be integrated into the processor 110.

[0111] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0112] The processor is a processor in the electronic device described in the above embodiment. 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.

[0113] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0114] 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 chip, etc.

[0115] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0116] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0117] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for managing application permissions, characterized in that: The method comprises: In the case of displaying a first interface of the application store, receiving a first input from a user, wherein the first interface includes at least one application identifier and at least one permission identifier corresponding to an application program indicated by each application identifier, each permission identifier being used to indicate an application permission, the first input being an input by the user to a target application identifier in the at least one application identifier, and the first input being used to trigger a download operation of the electronic device to the target application; In response to the first input, downloading and installing a target application based on M application permissions, where the M application permissions are application permissions that the target application is allowed to access among at least one application permission corresponding to the target application, the target application is the application indicated by the target application identifier, and M is a positive integer; Before downloading and installing the target application based on the M application permissions, the method further includes: Determine a target application category to which the target application belongs and P application permissions corresponding to the target application category, where P is an integer greater than or equal to M; Displaying second prompt information, wherein the second prompt information includes P permission identifiers corresponding to the P application permissions, and the second prompt information is used to prompt the user to set application permissions that allow the target application to access; receiving a fifth input from a user, wherein the fifth input is an input by the user for M authority identifiers among the P authority identifiers; In response to the fifth input, the M application permissions indicated by the M permission identifiers are set to: allow the target application program to access the M application permissions.

2. The method according to claim 1, characterized in that Before receiving the first input from the user, the method further includes: receiving a second input from a user, where the second input is an input by the user for M permission identifiers, where the M permission identifiers are permission identifiers in at least one permission identifier corresponding to the target application identifier; In response to the second input, the M application permissions indicated by the M permission identifiers are set to: allow the target application to access the M application permissions.

3. The method according to claim 1, characterized in that Before downloading and installing the target application based on the M application permissions, the method further includes: Displaying a first prompt message, wherein the first prompt message includes L permission identifiers, and the first prompt message is used to prompt the user to set application permissions that allow the target application to access, the L permission identifiers being permission identifiers in at least one permission identifier corresponding to the target application, and L being an integer greater than or equal to M; Receiving a third input from a user, where the third input is an input from the user for M of the L permission identifiers; In response to the third input, the M application permissions indicated by the M permission identifiers are set to: allow the target application to access the M application permissions.

4. The method according to claim 3, characterized in that: In the case where the first interface of the application store is displayed, before receiving the first input from the user, the method further includes: In the case of displaying the permission management interface, receiving a fourth input from the user, wherein the permission management interface includes at least one permission identifier corresponding to the target application, and the fourth input is an input of the L permission identifiers by the user; In response to the fourth input, the L permission identifiers are determined as permission identifiers that allow prompting when downloading the target application.

5. The method according to claim 1, characterized in that In the case where the first interface of the application store is displayed, before receiving the first input from the user, the method further includes: In the case of displaying a permission management interface, receiving a sixth input from the user, the permission management interface including at least one category identifier and at least one permission identifier corresponding to each category identifier, each category identifier being used to indicate an application category, the sixth input being the user's input of P permission identifiers among at least one permission identifier corresponding to a target category identifier, the target category identifier being a category identifier corresponding to the target application category; In response to the sixth input, the P permission identifiers are determined as permission identifiers that allow prompting when downloading an application program of the target application category.

6. An application rights management device, characterized in that: The application rights management device comprises: a receiving module and a downloading module; The receiving module is used to receive a first input from a user when displaying a first interface of the application store, wherein the first interface includes at least one application identifier and at least one permission identifier corresponding to an application program indicated by each application identifier, each permission identifier is used to indicate an application permission, and the first input is an input of a target application identifier in the at least one application identifier by the user, and the first input is used to trigger a download operation of the electronic device on the target application; The download module is configured to download and install a target application in response to the first input received by the receiving module based on M application permissions, wherein the M application permissions are application permissions that the target application is allowed to access among at least one application permission corresponding to the target application, the target application is the application indicated by the target application identifier, and M is a positive integer; The application authority management device further includes: a determination module, a display module and a setting module; The determination module is used to determine the target application category to which the target application belongs and P application permissions corresponding to the target application category before the download module downloads and installs the target application based on the M application permissions, where P is an integer greater than or equal to M; The display module is used to display second prompt information, wherein the second prompt information includes P permission identifiers corresponding to the P application permissions, and the second prompt information is used to prompt the user to set application permissions that allow the target application to access; The receiving module is further used to receive a fifth input from the user, where the fifth input is the user's input of M authority identifiers among the P authority identifiers; The setting module is configured to, in response to the fifth input received by the receiving module, set the M application permissions indicated by the M permission identifiers to allow the target application to access the M application permissions.

7. The device according to claim 6, characterized in that The receiving module is further configured to receive a second input from the user before receiving the first input from the user, wherein the second input is the user's input of M permission identifiers, and the M permission identifiers are permission identifiers in at least one permission identifier corresponding to the target application identifier; The application authority management device further includes: a setting module; The setting module is configured to, in response to the second input received by the receiving module, set the M application permissions indicated by the M permission identifiers to allow the target application to access the M application permissions.

8. The device according to claim 6, characterized in that The application authority management device further includes: a display module and a setting module; The display module is used to display a first prompt message before the download module downloads and installs the target application based on the M application permissions, the first prompt message including L permission identifiers, the first prompt message being used to prompt the user to set application permissions that the target application is allowed to access, the L permission identifiers being permission identifiers in at least one permission identifier corresponding to the target application, and L being an integer greater than or equal to M; The receiving module is further used to receive a third input from a user, where the third input is an input from the user on M of the L permission identifiers; The setting module is configured to, in response to the third input received by the receiving module, set the M application permissions indicated by the M permission identifiers to allow the target application to access the M application permissions.

9. The device according to claim 8, characterized in that The receiving module is further configured to receive a fourth input from the user when displaying a permission management interface before receiving the first input from the user when displaying the first interface of the application store, wherein the permission management interface includes at least one permission identifier corresponding to the target application, and the fourth input is an input of the L permission identifiers by the user; The application authority management device further includes: a determination module; The determining module is configured to determine, in response to the fourth input received by the receiving module, the L permission identifiers as permission identifiers that allow prompting when downloading the target application.

10. The device according to claim 6, characterized in that The receiving module is further used to receive a sixth input from the user before receiving the first input from the user when displaying the first interface of the application store, when displaying the permission management interface, wherein the permission management interface includes at least one category identifier and at least one permission identifier corresponding to each category identifier, each category identifier is used to indicate an application category, and the sixth input is the user's input of P permission identifiers among the at least one permission identifier corresponding to the target category identifier, and the target category identifier is the category identifier corresponding to the target application category; The determining module is further configured to, in response to the sixth input received by the receiving module, determine the P permission identifiers as permission identifiers that allow prompting when downloading an application of the target application category.

11. An electronic device, characterized in that: The invention comprises a processor, a memory and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the application permission management method as described in any one of claims 1 to 5.

12. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the application permission management method according to any one of claims 1 to 5 are implemented.

Images