CN114564707A - Application authority management method and device and electronic equipment - Google Patents

Abstract

The application discloses an application authority management method, an application authority management device and electronic equipment, wherein the method comprises the following steps: receiving a first input in a case where a first application is running; displaying a first interface in response to the first input; displaying at least one authority identifier corresponding to the first application on the first interface; each permission identification indicates an application permission of the first application.

Description

Application rights management method, device and electronic device

technical field

The present application belongs to the field of communication technologies, and in particular relates to an application rights management method, device and electronic device.

Background technique

At present, in the process of using the electronic device, in order to ensure that the electronic device application realizes corresponding functions, it is usually necessary to set various permissions for the application in the electronic device.

In the related art, after the application is installed, when the user uses the application for the first time, the application will request the user for permission to enable these functions according to the functions provided by itself (such as taking pictures, positioning, etc.). Every time you use it, you will be asked whether to enable the function permission. Once the permission is granted, the permission will be granted by default in the subsequent use process. If the user wants to modify the content of the application permission, he needs to enter the relevant setting page and find the specific entry corresponding to the above permission to complete the permission change.

However, ordinary users are not familiar with the relevant setting pages for modifying permissions, which leads to inconvenient modification of permissions and cumbersome modification process. Therefore, the user's experience in using the functions of the electronic device application is reduced.

SUMMARY OF THE INVENTION

The purpose of the embodiments of the present application is to provide an application rights management method, apparatus, and electronic device, which can solve the technical problems of inconvenient modification and complicated modification process of using the rights of an electronic device application.

In a first aspect, an embodiment of the present application provides an application rights management method, which includes:

receiving a first input when the first application is running;

In response to the first input, displaying a first interface;

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.

In a second aspect, an embodiment of the present application provides an application rights management device, the device comprising:

a receiving module, configured to receive the first input when the first application is running;

a display module, configured to display a first interface in response to the first input received by the receiving module;

Wherein, at least one permission identifier corresponding to the first application is 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.

In a third aspect, an embodiment of the present application provides an electronic device, the electronic device includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and the program or instruction is implemented when executed by the processor Such as the steps of the method of the first aspect.

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

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

In the embodiment of the present application, when the first application is running, a first input may be received, and then 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. In this way, if the user needs to modify the permission of the first application (for example: turn off the permission that has been enabled, or enable the permission that has not been enabled), he can directly on the first interface, directly on the first interface, for the application permission indicated by the permission identifier in the at least one permission identifier, By modifying (for example: turning it on or off), the modification of the permissions of the first application can be completed quickly and conveniently, which improves the user's experience in using the functions of the electronic device application.

Description of drawings

FIG. 1 is one of the schematic flow charts of the application rights management method provided by the embodiment of the present application;

FIG. 2 is one of the interface schematic diagrams of the application rights management method provided by the embodiment of the present application;

FIG. 3 is the second schematic diagram of the interface of the application rights management method provided by the embodiment of the present application;

FIG. 4 is the third interface schematic diagram of the application rights management method provided by the embodiment of the present application;

FIG. 5 is the fourth schematic diagram of the interface of the application rights management method provided by the embodiment of the present application;

FIG. 6 is one of the schematic diagrams of the application rights management apparatus provided by the embodiment of the present application;

FIG. 7 is the second schematic diagram of the application rights management apparatus provided by the embodiment of the present application;

FIG. 8 is a third schematic diagram of an apparatus for managing application rights provided by an embodiment of the present application;

9 is a schematic diagram of an electronic device provided by an embodiment of the present application;

FIG. 10 is a schematic hardware diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

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

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

It should be noted that the identifiers in the embodiments of the present application are used to indicate words, symbols, images, etc. of information, and controls or other containers may be used as carriers for displaying information, including but not limited to text identifiers, symbol identifiers, and image identifiers.

The application rights management solution provided in the embodiment of the present application can be applied to the permission modification scenario of an application program.

In the related art, if the user wants to modify the content of the application permission, he needs to enter the relevant setting page and find the corresponding entry before completing the modification of the permission, resulting in inconvenient modification of the permission content and cumbersome modification process. In addition, some applications may not be able to use the application when they are not authorized. After the permission is granted, the content of the specific information obtained by the application is unknown. Users do not know whether to authorize or not, and cannot determine what private information the app has acquired.

However, in this embodiment of the present application, at least one permission identifier corresponding to the first application may 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; the permission of the first application includes an enabled permission and an unenabled permission. Therefore, the user does not need to enter the relevant setting page to find the corresponding entry, but only needs to use at least one permission identifier displayed on the first interface to quickly, conveniently and intuitively view or modify the permissions of the first application, which not only simplifies the user operation , which improves the user's experience in using the functions of the electronic device application.

The application rights management method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof. The method is exemplarily described below by taking the execution subject as an application rights management apparatus as an example.

As shown in FIG. 1 , an embodiment of the present application provides an application rights management method, and the method may include the following steps 101 and 102 .

Step 101: In the case of running the first application, receive a first input.

Step 102: In response to the first input, display a first interface.

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.

In this embodiment of the present application, the above-mentioned first input may be a user's touch input, or a voice input, or other feasible input, which may be specifically set according to actual needs.

Exemplarily, the above-mentioned first input may be an input to the interface A by the user. Further, the above-mentioned interface A may be: an application interface of the first application, or an application interface of other applications, or a desktop, or other possible interfaces, which are not limited in this embodiment of the present application.

Exemplarily, the above-mentioned touch input may be: a user's pressing input at any position or preset position of the interface A (for example, a long-press input or a short-press input), a sliding input, a click input, and a drag input. Further, the above-mentioned preset position may be: the edge position of the interface A.

In the embodiment of the present application, the at least one permission identifier includes: one or more permission identifiers of the first application in the electronic device. Further, the at least one permission identifier may include a permission identifier of a permission that has been enabled by the first application, and may also include a permission identifier of a permission that has not been enabled by the first application. That is to say, the permission identifier displayed in the first interface can be either the permission identifier of the enabled permission or the permission identifier of the unenabled permission, so as to facilitate the user to manage various permissions.

In an example, the above-mentioned first interface may also display permission identifiers of all or part of applications in the electronic device, which is not limited in this embodiment of the present application.

In this embodiment of the present application, the first interface may be an interface related to the first application.

Exemplarily, the first interface may be a background task management interface, or the first interface may include a first application page of the first application.

In a possible example, the first interface is a background task management interface. Wherein, the target area of the background task management interface displays the first page identifier of the first application and at least one permission identifier. The above-mentioned first page identifier is used to indicate the first application page of the first application.

Exemplarily, the above-mentioned background task management interface includes a page identification display area and a first authority identification display area. Wherein, the page ID of the application running in the background is displayed in the above-mentioned page ID display area (for example, the first page ID of the first application is displayed), and the above-mentioned at least one permission ID is displayed in the above-mentioned first permission ID display area.

In an example, the first page identifier of the first application is displayed in the area A in the page identifier display area in the above-mentioned background task management interface; the area B in the first authority identifier display area in the above-mentioned background task management interface is displayed. At least one permission ID is displayed. In other words, the above-mentioned target area may include the area A and the area B.

Exemplarily, the above-mentioned first authority identification display area may be located on the left side, the right side, the upper side, the lower side, or other possible positions of the page identification area.

Exemplarily, the authority identification displayed in the first authority identification display area may change with the page identification displayed in the page identification display area. Or, the authority identification displayed in the above-mentioned first authority identification display area will be updated based on the page identification selected by the user in the page identification display area.

For example, if the page ID display area currently displays page ID 1 of page 1 of APP1, the permission ID of APP1 will be displayed in the corresponding first permission ID display area. At this time, if the user displays the page ID displayed in the page ID display area If it is switched to the page ID 2 of the page 2 of APP2, the content displayed in the display area corresponding to the first permission ID will be updated to the permission ID of APP2.

Exemplarily, the page identifier can be switched in the page identifier display area through gesture input (eg, touch input or sliding input).

Exemplarily, an icon or a color may be used to distinguish the permission identifier of the enabled permission from the permission identifier of the unenabled permission, so that the user can check whether the permission of the selected application meets the user's requirement.

Example 1, as shown in Figure 2, which shows a possible schematic diagram of the background task management interface, in Figure 2, the page identification display area 31 in the background task management interface displays the page identification of the APP1 running in the background 32 and the page identifier 33 of APP2 (that is, the first page identifier of the first application), since the page identifier 33 of APP2 is located in the selected area of the page identifier display area 31 (that is, the above-mentioned area A), the above-mentioned first permission identifier display area 34 The 4 permission identifiers of APP2 will be displayed in the center, which are the first permission marker 35 , the second permission marker 36 , the third permission marker 37 , and the fourth permission marker 38 . The first authority identification display area 34 is located on the right side of the page identification area 31 .

It should be noted that, with reference to FIG. 2 , the selected area of the page identifier display area 31 usually displays the page identifier selected by the user. For example, if the user selects the page identifier 33 of APP2, the page identifier 33 may be displayed in the selected area. If the user subsequently selects the page identifier 32 of APP1, the page identifier 33 may be switched to the page identifier 32 in the selected area.

In another possible example, the above-mentioned first interface may include a first application page of the first application. It can be understood that the first interface includes a page display area of the first application page of the first application, and a second permission identification display area. Wherein, the second authority identification display area displays the above at least one authority identification.

Exemplarily, the second authority identification display area may be located on the left side, the right side, the upper side, the lower side, or other possible positions of the page display area.

It should be noted that, if the user needs to modify the authority of the first application, the user can directly operate any one of the above at least one authority mark, so as to modify the application authority indicated by the authority mark, such as opening a certain authority mark. App permissions or turn off an app permission.

Example 2, FIG. 3 shows a schematic interface diagram of interface A including the first application page of APP1. 3, when the user wants to view the application permissions of APP1, the user can long press the interface A (ie, the above-mentioned first input), so that the permission management apparatus updates the interface A to the first interface. As shown in FIG. 4 , the first interface includes a page display area 41 and a second authority mark display area 42, wherein the page display area 41 displays a first application page 43, and the second authority mark display area 42 displays four The authority identifiers (ie, at least one authority identifier) are respectively a first authority identifier 44 , a second authority identifier 45 , a third authority identifier 56 , and a fourth authority 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 click and input any one of the permission identifiers to complete the opening or closing of the corresponding application permission.

In this embodiment of the present application, when the first application is running, the first input may be received, and then the first interface may be displayed in response to the first input. 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. In this way, if the user needs to modify the authority of the first application, he can directly modify the application authority indicated by the authority mark in at least one authority mark on the first interface (for example, enable a certain application authority or close a certain application authority) , the modification of the authority of the first application can be completed quickly and conveniently, which improves the user's experience in using the functions of the electronic device application.

Optionally, in this embodiment of the present application, the permission level of the first application is associated with the permission that has been enabled by the first application.

In this embodiment of the present application, several groups of different permission levels may be preset.

Exemplarily, the permission levels may include three levels of permission levels of "high, medium, and low", and different permission levels have different permissions to be turned on.

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 in the electronic device. That is to say, different types of applications correspond to different permission levels. It can be understood that if the permission level includes three levels, correspondingly, the application type may also include three categories. Therefore, after the user downloads and installs an application of a certain type, the corresponding permission level can be directly enabled.

In this way, in the embodiment of the present application, the user can customize different permission levels according to their own permission requirements, and when installing applications, they can choose to use different permission levels according to different applications.

In a possible example, the high-level permission level can be provided by the user-defined permission content, and the middle-level permission level is based on the application store of the electronic device preset with the "category label", and preset permission content. The low-level permission level provides most information by default and does not restrict application access.

It should be noted that the user's permissions in different permission levels can be turned on or off by the user.

It should be noted that for the middle-level permission level, you can set the default permissions granted by the corresponding type of application according to the "permission content" in the app store and the "category label" of the application, and try to ensure the normal use of the application. This service can be operated by the application store or intelligently authorized by the electronic device system, without requiring users to pay attention to the corresponding permission details.

It should be noted that for high-level permission levels, most permissions do not grant real information by default. Under the page of setting high permission level, you can view the private information that the electronic device can provide externally, and users can customize a set of fictitious information to replace their real private information in actual use. Avoid using the application due to unauthorized use during use.

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

S1. The user enters the authority management page of the electronic device.

S2. Set the permission content that needs to be enabled for different permission levels.

In this way, the embodiments of the present application can provide different permission levels for applications, and different levels of 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, permission management with high-level permission levels is directly configured to reduce the possibility of privacy leakage. For some applications that rely on real information and have low risks, you can perform permission management according to the default authorization of low-level permission levels. For some commonly used social software, you can directly use the mid-level permission level authorization management configuration recommended by the app store by default.

Optionally, in the embodiment of the present application, the application rights management method provided by the embodiment of the present application may further include the following steps 201 to 204 .

Step 201, receiving a fifth input.

Step 202: In response to the fifth input, set all applications in the electronic device to the highest permission level.

Step 203, receiving a sixth input.

Step 204: In response to the sixth input, restore all applications in the electronic device to the initial permission level.

Wherein, the permission level of any application in the electronic device is associated with the opened permission of any application.

Exemplarily, both the fifth input and the sixth input may refer to the description of the first input, for example, may be a user's touch input, or a voice input, or other feasible input, which may be specifically set according to actual needs.

Exemplarily, taking APP3 in the electronic device as an example, the solution of the embodiment of the present application will be described. If the permission level in the electronic device includes three levels of "high, medium and low", the initial permission level of APP3 is the middle level permission. level, after receiving the fifth input, the permission level of APP3 is adjusted from the middle level to the high level permission level, and after receiving the fifth input, the permission level of APP3 is restored to the middle level permission level (ie the initial permission level).

In a possible example, in this embodiment of the present application, when the operator of the electronic device is changed from the first user (eg, the owner) to the second user, the first user can perform the fifth input. Then, after the second user finishes using the electronic device, and after the operator of the electronic device is changed from the second user to the first user, the first user performs the sixth input.

In this way, the embodiment of the present application can assign different permission levels to different users. For example, when the electronic device is handed over by an adult (first user) to a minor or other person (second user), all application permissions of the entire system can be raised to the "high-level" permission level by one-key operation Management, for global rights management.

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

In this way, the permission levels 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 users. Prevent data information that does not meet user needs from being pushed.

Optionally, in the embodiment of the present application, when the first interface is a background task management interface, after the above step 102, the application rights management method provided by the embodiment of the present application further includes the following steps 103 and 104.

Step 103, receiving a second input.

Step 104: In response to the second input, display a second interface.

Wherein, the second interface includes a first area and a second area. Exemplarily, the first area and the second area may be distributed up and down, or distributed left and right, or distributed in other possible forms.

Exemplarily, the second input may refer to the description of the first input, for example, may be a user's touch input, or a voice input, or other feasible input, which may be specifically set according to actual requirements.

In an example, the second input includes the user's input to the display area of the first authority identifier.

Exemplarily, a first application page is displayed in the above-mentioned first area.

Exemplarily, the above-mentioned second area is displayed with permission information. The above 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 above permission information may be: permission information of all permissions that have been enabled by the first application, or permission information of some permissions that have been enabled by the first application, or permission information of any permission that has been enabled by the first application. For example, the above enabled permissions may be to allow access to location, allow access to albums, allow to read phone calls, and allow to read contacts.

For example, the above-mentioned permission information may include: a certain time obtained a certain permission, and the specific content of the permission.

Example 3, in conjunction with FIG. 2 , as shown in FIG. 5 , the first area 51 is on the left, the second area 52 is on the right, the first application page 53 is displayed in the first area, and the permission information 54 and 4 are displayed in the second area A permission identifier (ie, at least one permission identifier), a first permission identifier 55 , a second permission identifier 56 , a third permission identifier 57 , and a fourth permission identifier 58 .

It should be noted that, in combination with Example 3, in the case where the permission information is the permission information of all the permissions that the first application has opened, if the user wants to view the permission information of the first permission identifier 55, the user can click to select the first permission identifier 55, The authority information will be updated to the authority information corresponding to the first authority identifier 55 . If the user wants to view the permission information of the first permission ID 55 and the first permission ID 57, the user can click to select the first permission ID 55 and the first permission ID 57, and the permission information will be updated to the first permission ID 55 and the first permission ID 57. The authority information corresponding to the authority identifier 57 .

It should be noted that, in the case where the permission information is permission information of some permissions that have been enabled by the first application, the user can click on an area other than the permission identifier, and the permission information will display permission information of all permissions that have been enabled by the first application.

It can be understood that the user can directly manipulate and use the first application page in the first area. During the user's use, along with the running of the first application, the permission information will be updated in real time, so that the permission information can display historical permission information and current real-time permission information. The updated permission information is convenient for users to view the access status of permissions in real time.

In this way, in the process of using the application, the user can conveniently view the content information provided by the corresponding authority, and can timely adjust the authorization level according to the information.

Optionally, in the embodiment of the present application, the permissions of the first application include opened permissions and unopened permissions; the permission level of the first application is associated with the opened permissions of the first application; the second area also displays permissions. Level adjustment controls.

Exemplarily, after the above step 104, the application rights management method provided by this embodiment of the present application may further include the following steps 105 and 106:

Step 105: Receive a third input to the authority level adjustment control.

Step 106: In response to the third input, adjust the permission level of the first application.

Exemplarily, the above-mentioned third input may be a user's touch input on the permission level adjustment control, or a voice input, or other feasible input, which may be specifically set according to actual needs.

Exemplarily, the third input may refer to the description of the first input, for example, it may be a user's touch input, or a voice input, or other feasible input, which may be specifically set according to actual needs.

Exemplarily, the permission level adjustment control may be in the shape of a bar, or a ring, or other possible shapes.

Exemplarily, an adjustment cursor may be displayed on the permission level adjustment control, and the third input may be a pressing input or a dragging input on the adjustment cursor, so as to complete the adjustment of the first application permission level.

Exemplarily, in conjunction with Example 3 and Figure 5, the second area displays an authority level adjustment control 59, and an adjustment cursor 60 is displayed on the authority level adjustment control, and the user can drag the adjustment cursor to different positions in the authority level adjustment control, Different locations have different permission levels for the first application.

In this way, the authority level of the first application can be adjusted conveniently and quickly, which improves the user's experience in using the functions of the electronic device application.

Optionally, in this embodiment of the present application, when the user does not need to view the above permission information, after step 104, the application permission management method provided in this embodiment of the present application may further include the following steps 107 and 108:

Step 107: Receive a seventh input from the user.

Step 108: In response to the seventh input, display a third interface.

Wherein, the third interface displays the first application page of the first application and/or the at least one permission identifier.

Exemplarily, the seventh input may refer to the description of the first input, for example, may be a user's touch input, or a voice input, or other feasible input, which may be specifically set according to actual needs.

Exemplarily, the third interface includes a page display area and a third authority mark display area, the page display area displays the first application page, and the third authority mark display area displays the at least one authority mark.

In this embodiment of the present application, the third interface may not display the above permission information.

In this embodiment of the present application, the seventh input is the user's input to the second interface, for example, the input to the first area in the second interface, or the input to the second area in the second interface. For example, the permission information can be dragged to cancel the display of the permission information, and the first application page can be displayed enlarged, or the first application page can be clicked and inputted to cancel the display of the permission information, and the first application page can be enlarged and displayed.

Exemplarily, in conjunction with Fig. 4, the third interface schematic diagram can refer to Fig. 4, in Fig. 4, a first application page and 4 permission identifiers (that is, at least one permission identifier) are displayed, which are respectively the first permission identifier 44, and the second permission identifier 44. The authority identification 45 , the third authority identification 56 , and the fourth authority identification 47 .

In this way, the display of the permission information can be canceled according to different permission viewing requirements of the user, so as to make full use of the display screen of the electronic device.

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

Step 109: Receive an eighth input from the user on the third interface.

Step 110: In response to the eighth input, display the above-mentioned second interface.

Exemplarily, reference may be made to the description of the first input for the eighth input, for example, it may be a user's touch input, or a voice input, or other feasible input, which may be specifically set according to actual requirements.

In an example, the eighth input may be: the user's input to the third authority identification display area of the third interface.

In this way, according to the different permission viewing requirements of the user, the first application can be controlled and used normally, and the permission information can be easily called up to facilitate the user's viewing.

Optionally, in the embodiment of the present application, the authority of any application in the electronic device includes an opened authority and an unopened authority; the authority level of any application is associated with the opened authority of any application; the embodiment of the present application The method for providing application rights management may further include the following step 301:

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, display first prompt information.

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

Exemplarily, during the running process of the first application, when the acquisition of permission content is involved, the corresponding permission identifier may have a corresponding dynamic effect prompt.

It can be understood that during the normal operation of the first application, the obtained permission information of the permission opened by the first application should meet the preset permission requirements. risk or other possible risks.

Exemplarily, if the first number of times the first application accesses or reads the corresponding permission content within a unit time (for example, the permission frequency) should be less than or equal to the first threshold, it means that the permission information of the first application meets the preset permission requirements. , if the above-mentioned first number of times is greater than the first threshold, indicating that the permission information of the first application does not meet the preset permission requirements, then the electronic device can display the first prompt information to remind the user to check and adjust the relevant permissions of the first application to avoid There are risks such as privacy leakage.

Exemplarily, if the first application accesses or reads the permission content of the corresponding permission within a unit time, and exceeds the necessary and reasonable behavior, it means that the permission information of the first application does not meet the preset permission requirements, then the electronic device can display the first application. A prompt message to remind the user to view and adjust the relevant permissions of the first application to avoid risks such as privacy leakage.

It should be noted that when the user cannot use the application normally due to permissions and other reasons, or the use is blocked, the electronic device can enter the permission management interface through notification reminders, etc., and adjust the corresponding permissions to ensure normal operation. use. Therefore, in the process of using the application, the user can dynamically adjust the permission level of the application according to the real-time situation of the permission information.

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

As shown in FIG. 6 , an embodiment of the present application provides an apparatus for managing application rights. The apparatus includes: a receiving module 401 and a display module 402 .

The receiving module 401 is configured to receive a first input when the first application is running.

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

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.

Optionally, in this embodiment of the present application, the above-mentioned first interface is: a background task management interface.

Wherein, the target area of the background task management interface displays the first page identifier of the first application and at least one permission identifier; the first page identifier is used to indicate the first application page of the first application.

Optionally, in this embodiment 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.

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

Wherein, the second interface includes a first area and a second area. A first application page is displayed in the first area; permission information is displayed in the second area, and the 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.

Optionally, in the embodiment of the present application, the permissions of the first application include opened permissions and unopened permissions; the permission level of the first application is associated with the opened permissions of the first application; the second area also displays Permission level adjustment controls.

As shown in FIG. 7 , the above-mentioned apparatus further includes an adjustment module 403 .

The receiving module 401 is further configured to receive a third input to the authority level adjustment control after the display module 402 displays the second interface,

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

Optionally, in this embodiment of the present application, the above-mentioned display module 402 is further configured to, 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 requirements, display the first application page. a prompt message;

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

Optionally, in this embodiment of the present application, as shown in FIG. 8 , the apparatus further includes a setting module 404 .

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

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

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

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 .

Wherein, the permission level of any application in the electronic device is associated with the opened permission of the any application.

In this embodiment of the present application, the receiving module may receive the first input when the first application is running, and then the display module may display the first interface in response to the first input received by the receiving module; wherein, on the first interface At least one permission identifier corresponding to the first application is displayed; the first interface is an interface related 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 (for example, turning off the permission that has been enabled, or opening the permission that has not been enabled), he can directly on the first interface, perform the application permission indicated by the permission identifier in at least one permission identifier. By modifying (for example, turning it on or off), the modification of the permission of the first application can be completed quickly and conveniently, which improves the user's experience in using the functions of the electronic device application.

For the beneficial effects of the various implementations in this embodiment, reference may be made to the beneficial effects of the corresponding implementations in the foregoing method embodiments, which are not repeated here to avoid repetition.

The application rights management device in the embodiment may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The apparatus may be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (personal digital assistant). , PDA), etc., the non-mobile electronic device may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc. The embodiments of the present application There is no specific limitation.

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 (Android) operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.

The application rights management apparatus provided in the embodiments of the present application can implement each process implemented by the foregoing method embodiments, and to avoid repetition, details are not described herein again.

As shown in FIG. 9 , an embodiment of the present application further provides an electronic device 200, including a processor 202, a memory 201, a program or instruction stored in the memory 201 and executable on the processor 202, the program or instruction being processed When the device 202 is executed, each process of the above-mentioned embodiment of the application rights management method is implemented, and the same technical effect can be achieved. In order to avoid repetition, details are not repeated here.

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

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

The electronic device 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010, etc. part.

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

The user input unit 1007 is configured to receive the first input when the first application is running.

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

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.

Optionally, the first interface is: a background task management interface.

Wherein, the target area of the background task management interface displays the first page identifier of the first application and at least one permission identifier; the first page identifier is used to indicate the first application page of the first application.

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

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 .

Wherein, the second interface includes a first area and a second area; the first area displays a first application page; the second area displays permission information, and the permission information includes at least one permission identifier and at least one of the following: Historical permission information and current permission information of the first application.

Optionally, the permissions of the first application include opened permissions and unopened permissions; the permission level of the first application is associated with the opened permissions of the first application; the second area also displays a permission level adjustment control; the electronic The device also includes an adjustment unit.

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

An adjustment unit, configured to adjust the permission level of the first application in response to the third input received by the user input unit 1007 .

Optionally, the display unit 1006 is further configured to: 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, display the first prompt information.

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

Optionally, the electronic device further includes a setting unit.

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

A setting unit, configured to set all applications in the electronic device to the highest authority level in response to the fifth input received by the user input unit 1007 .

The user input unit 1007 is further configured to: receive a sixth input;

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 .

Wherein, the permission level of any application in the electronic device is associated with the opened permission of any application.

In the electronic device provided by the embodiment of the present application, the user input unit may receive the first input when the first application is running, and then the display unit may display the 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 an interface; each permission identifier indicates an application permission of the first application. Therefore, when the user is using the application, it cannot be used normally due to reasons such as permissions; or when the use is blocked; or due to other reasons, the user needs to modify the permissions of the first application (for example, closing the opened permissions, or opening the When the permission is not enabled); the application permission indicated by the permission indicator in at least one permission indicator can be modified (for example, turned on or off) directly on the first interface, and the authorization of the first application permission can be completed quickly and conveniently. The modification improves the user's experience in using the functions of the electronic device application.

For the beneficial effects of the various implementations in this embodiment, reference may be made to the beneficial effects of the corresponding implementations in the foregoing method embodiments, which are not repeated here to avoid repetition.

It should be understood that, in this embodiment of the present application, the input unit 1004 may include a graphics processor (Graphics Processing Unit, GPU) 10041 and a microphone 10042. camera) to process the image data of still pictures or videos. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. 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 may include two parts, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here. Memory 1009 may be used to store software programs as well as various data, including but not limited to application programs and operating systems. The processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the like, and the modem processor mainly processes wireless communication. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 1010.

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

Wherein, the above-mentioned processor is the processor in the electronic device in the above-mentioned embodiment. The above-mentioned readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like. The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used for running a program or an instruction, implementing each process of the above-mentioned application rights management method embodiment, and can achieve The same technical effect, in order to avoid repetition, will not be repeated here.

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

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

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

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

Claims (14)

1. A method for application rights management, wherein the method comprises: in the case of running the first application, receiving a first input; In response to the first input, displaying a first interface; Wherein, at least one permission identifier corresponding to the first application is displayed on the first interface; Each of the permission identifiers indicates an application permission of the first application. 2. The method according to claim 1, wherein the first interface is: a background task management interface; Wherein, the first page identifier of the first application and the at least one permission identifier are displayed in the target area of the background task management interface; The first page identifier is used to indicate a first application page of the first application. 3. The method according to claim 2, wherein after the displaying the first interface, the method further comprises: receive a second input; In response to the second input, displaying a second interface; Wherein, the second interface includes a first area and a second area; The first application page is displayed in the first area; permission information is displayed in the second area, and the permission information includes the 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. 4 . The method according to claim 3 , wherein the permission of the first application includes an enabled permission and an unopened permission; the permission level of the first application is the same as the opened permission of the first application. 5 . Permissions are associated; the second area also displays a permission level adjustment control; After the displaying of the second interface, the method further includes: receiving a third input to the permission level adjustment control; In response to the third input, the permission level of the first application is adjusted. 5. The method of claim 3, wherein the method further comprises: 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, display first prompt information; The first prompt information is used to prompt that the permission of the first application is abnormal. 6. The method of claim 1, wherein the method further comprises: receive a fifth input; In response to the fifth input, set all applications in the electronic device to the highest permission level; receive a sixth input; In response to the sixth input, restore all applications in the electronic device to the initial permission level; Wherein, the permission level of any application in the electronic device is associated with the enabled permission of the any application. 7. An application rights management device, wherein the device comprises: a receiving module, configured to receive the first input when the first application is running; a display module, configured to display a first interface in response to the first input received by the receiving module; Wherein, at least one permission identifier corresponding to the first application is displayed on the first interface; Each of the permission identifiers indicates an application permission of the first application. 8. The device according to claim 7, wherein the first interface is: a background task management interface; Wherein, the first page identifier of the first application and the at least one permission identifier are displayed in the target area of the background task management interface; The first page identifier is used to indicate a first application page of the first application. 9. The device of claim 8, wherein The receiving module is further configured to receive a second input after the display module displays the first interface; The display module is further configured to display a second interface in response to the second input received by the receiving module; Wherein, the second interface includes a first area and a second area; The first application page is displayed in the first area; permission information is displayed in the second area, and the permission information includes the 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. 10 . The device according to claim 8 , wherein the permission of the first application includes an enabled permission and an unopened permission; the permission level of the first application is the same as the permission level of the first application that has been opened. 11 . Permissions are associated; the second area also displays a permission level adjustment control; The device also includes an adjustment module; The receiving module is further configured to receive a third input to the authority level adjustment control after the display module displays the second interface; The adjusting module is configured to adjust the permission level of the first application in response to the third input received by the receiving module. 11. The apparatus of claim 8, wherein The display module is further configured to display the first prompt information if the permission information of the first application does not meet the preset permission requirements during the running process of the first application page of the first application; The first prompt information is used to prompt that the permission of the first application is abnormal. 12. The apparatus according to claim 7, wherein the apparatus further comprises a setting module; The receiving module is further configured to receive a fifth input; the setting module, configured to set all applications in the electronic device to the highest authority level in response to the fifth input received by the receiving module; The receiving module is further configured to receive a sixth input; The setting module 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; Wherein, the permission level of any application in the electronic device is associated with the enabled permission of the any application. 13. An electronic device, characterized in that it comprises a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction being implemented when executed by the processor The steps of the application rights management method according to any one of claims 1 to 6. 14. A readable storage medium, characterized in that a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the application according to any one of claims 1 to 6 is realized The steps of the rights management method.

Images