CN113792327B - Authority management method, user interface and electronic equipment - Google Patents

Abstract

The present application discloses a rights management method, a user interface and an electronic device. The method can divide applications into whitelist applications and blacklist applications according to the degree of adaptation of different applications to a single authorization. The degree of adaptation is good, so when configuring permissions for this type of application, there is an option for single authorization, so that users can choose whether to authorize the application once according to their own needs. The degree of adaptation is poor, so when configuring permissions for this type of application, there is no single authorization option, which avoids the problem of abnormal operation after the user authorizes the application for a single time.

Description

Rights management method, user interface and electronic device

technical field

The present application relates to the technical field of terminals and communications, and in particular, to a rights management method, a user interface, and an electronic device.

Background technique

With the development of the Internet, more and more applications can be installed on electronic devices. During the running process of the application, it needs to call the hardware and software resources of the electronic device to support its own operation. The hardware and software resources of the electronic device involve the user's private information. Therefore, when the application is opened for the first time or the application is running, the electronic device will display a permission window to prompt the user to grant permission, and after obtaining the user's consent, allow the application to call In electronic equipment, the corresponding hardware or software resources.

Among them, according to different authorization durations, the permission window also provides a variety of authorization methods: always allow, allow during use, allow this run, prohibit, etc., among which, this run permission means that the application is allowed to be used only once in the application Use permissions during runtime. However, due to the different degrees of adaptation of different applications to the authorization methods allowed for this operation, when the application is configured with the authorization methods allowed for this operation, it may happen that when the application returns to the foreground to run again, access rights cannot be accessed, or user data is lost. The problem.

Therefore, how to manage the access of different applications to permissions, and avoid the problems that applications cannot access permissions and user data are lost, is an urgent problem to be solved at present.

SUMMARY OF THE INVENTION

Some embodiments of the present application provide rights management methods, user interfaces, and electronic devices.

The methods provided by some embodiments of the present application can provide different authorization modes for different applications and different permissions, so as to avoid the problem of abnormal operation due to the application not adapting to a single authorization.

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

The electronic device displays a first window of a first application, and the first window displays a permission item with a first permission;

If the first application is a whitelisted application, the first application is allowed to use the first permission during a single running of the first application, and the authorization mode of the first permission includes a first authorization mode, and the first The authorization method is to allow the first authorization to be used during a single operation of the first application; otherwise, the authorization method of the first authorization does not include the first authorization method; after the user interface of the whitelist application is closed and displayed , when it is displayed again after a period of time, there is one of the following exceptions: the user data of the whitelist application is lost, the first function of the whitelist application fails to invoke the first permission, or the exception does not exist.

By implementing the method provided by the first aspect, it is possible to analyze in advance whether the application is a whitelisted application according to the situation in which the application uses the permission valid during a single operation. A whitelisted application refers to whether the degree of authorization for a single time is good, and there are only exceptions in which user data is lost or the function fails to invoke the permission during operation, or there are no such exceptions. If the application is a whitelisted application, it means that the application is well adapted to a single authorization, and the electronic device can provide a single authorization option for the authorization in the authorization window of the application, so that the user can choose according to their own needs. Whether to authorize the application once. Otherwise, the application is a blacklisted application, that is, the degree of adaptation of the application to a single authorization is poor, and the electronic device may not provide the single authorization option of the authorization in the authorization window of the application, which prevents the user from performing a single authorization on the application. After a single authorization, the problem of abnormal operation occurs.

With reference to the first aspect, in a possible implementation manner, the method further includes: if user data is lost when the user interface of the first application is displayed after being closed for a period of time, then the first application is displayed again after a period of time. For a period of time after the user interface of the application is closed and displayed, the electronic device still runs the first application, and the duration of the period of time exceeds a preset period of time. After the preset period of time is exceeded, the electronic device recycles the first application. of this first authority.

When the application is running and user data is lost, it may be caused by the application running in the background for more than a certain period of time and ending the operation, then the electronic device can run the application in the background without ending the running of the application, only recycling the The permission granted by the application is valid during a single operation, to avoid the loss of user data, to improve the operation of the application, and to enhance the user's experience.

With reference to the first aspect, in a possible implementation manner, the method further includes: after the user interface of the first application is closed and displayed, when the user interface of the first application is displayed again after a period of time, the user interface of the first application is not displayed A user data loss exception occurs.

With reference to the first aspect, in a possible implementation manner, the method further includes: after the user interface of the first application is closed and displayed, when the user interface of the first application is displayed again after a period of time, the electronic device does not display the first application startup interface.

Since the application has been running after entering the background, when the application returns to the foreground to run again, the application does not need to be restarted, so the application startup interface will not be displayed.

With reference to the first aspect, in a possible implementation manner, the startup interface includes one or more of the following pages provided by the first application while waiting for the first application to be started: a startup page and an advertisement page.

With reference to the first aspect, in a possible implementation manner, the user interface of the first application is a video playback interface, and the user data is the video playback progress.

That is to say, when there is data loss in the application, the application may be a video playback application. When the application switches to the background and returns to the foreground after a period of time, the playback progress may be cleared and the video will be restored. When playback starts at the beginning. Such a video playback application is suitable for keeping running after switching to the background, thereby avoiding the problem of user data loss.

With reference to the first aspect, in a possible implementation manner, the method further includes: if the user interface of the first application is displayed again after a period of time after being closed and displayed, the first function calls the first If the permission is abnormal, when the user interface of the first application is closed and displayed for more than a preset time period, the electronic device ends running the first application, and the electronic device reclaims the first permission of the first application.

When the application is running and the function call permission fails, it may be because the application has been running in the background after switching to the background, and the permission obtained by the application is valid during a single operation. If it is recycled by an electronic device, the permission required for the function cannot be obtained when the application starts the function, and the function fails to run, then the electronic device can run the application in the background and end running the application after the preset time period has expired, and the application will be recycled and granted The effective permissions during a single operation can avoid the failure of function call permissions, improve the operation of the application, and enhance the user experience.

With reference to the first aspect, in a possible implementation manner, the method further includes: after the user interface of the first application is displayed after being closed and displayed again after a period of time, the first function successfully invokes the first permission .

With reference to the first aspect, in a possible implementation manner, the method further includes: after the user interface of the first application is turned off and displayed, when the user interface of the first application is displayed again after a period of time, the electronic device displays the user interface of the first application. Start interface.

Since the electronic device will end the running of the application when the application runs in the background for more than the preset time period, when the application returns to the foreground to run again, the electronic device needs to restart the process of the application, and the electronic device will display the display when the application is started. The application's launch interface.

With reference to the first aspect, in a possible implementation manner, the first function is a voice chat function, and the first authority is a microphone.

That is to say, when there is data loss in the application, the function may be a voice chat function. The application can use the voice chat function normally before switching to the background operation. When the application enters the background and runs for more than a preset time, the electronic device will recycle the application's microphone. permission, when the app returns to the foreground again, there may be a possibility that the voice chat function cannot obtain the user's voice information. Such an application is suitable for ending the operation after switching to the background and exceeding the preset time period, thereby avoiding the problem of the failure of the application's function invocation permission.

With reference to the first aspect, in a possible implementation manner, the method further includes: after the user interface of the first application is closed and displayed and displayed again after a period of time, the electronic device responds to the activation of the first function in response to operation, a second window is displayed, prompting the user to grant the first application to use the first permission.

That is, when the application returns to the foreground to run again, the electronic device can actively display the permission window when the function of the application requires permission, and prompt the user to grant permission to the application, thereby ensuring the normal operation of the application.

In combination with the first aspect, in a possible implementation manner, the method further includes: for some sensitive permissions (such as location, shooting, or recording permissions), it is recommended to authorize only once, for example, it is recommended to select the option to allow only once by default. .

In a second aspect, an embodiment of the present application provides another authorization management method. The method includes: the electronic device allows the first application to use the first authorization during a single execution of the first application; the electronic device closes the display of the first authorization The user interface of an application displays the user interface of the first application again after a period of time; the electronic device displays a second window in response to the operation of starting the first function, prompting the user to grant the first application the first permission.

Implementing the method provided in the second aspect, when the electronic device grants the application a permission valid for a single running period, if the application is switched to the background to run for more than a preset period of time, the electronic device will actively reclaim the permission of the application. At this time, When the application returns to the foreground to run again, the electronic device can actively display the permission window when the function of the application requires permission, prompting the user to grant permission to the application, so as to ensure the normal operation of the application.

With reference to the second aspect, in a possible implementation manner, before the electronic device allows the first application to use the first permission during a single running of the first application, the method further includes: the electronic device displays the first application The first window, the first window displays the permission item of the first permission, the authorization mode of the first permission includes the first authorization mode, and the first authorization mode is to allow the first application during a single running period Use this first permission.

That is to say, the electronic device may grant a permission valid during a single run to the application when receiving the option that the user selects a single authorization, that is, allow the application to use the permission during a single run of the application.

In combination with the second aspect, in a possible implementation manner, the first application is a whitelisted application, and after the user interface of the whitelisted application is closed and displayed, when it is displayed again after a period of time, there is one of the following exceptions : The user data of the whitelist application is lost, the first function of the whitelist fails to invoke the first permission, or the exception does not exist.

That is to say, if the electronic device allows the application to use the permission during a single operation of the application, it means that the application is well adapted to the single authorization, that is, only the user data is lost or the function fails to invoke the permission during the operation of the application. , or the above exception does not exist.

In combination with the second aspect, in a possible implementation manner, if user data is lost when the user interface of the first application is displayed after being turned off and displayed again after a period of time, the user interface of the first application is displayed in For a period of time after the display is turned off, the electronic device still runs the first application, and the duration of the period of time exceeds the preset time period. After the preset time period is exceeded, the electronic device reclaims the first permission of the first application. .

When the application is running and user data is lost, it may be caused by the application running in the background for more than a certain period of time and ending the operation, then the electronic device can run the application in the background without ending the running of the application, only recycling the The permission granted by the application is valid during a single operation, to avoid the loss of user data, to improve the operation of the application, and to enhance the user's experience.

With reference to the second aspect, in a possible implementation manner, the method further includes: after the user interface of the first application is closed and displayed, when the user interface of the first application is displayed again after a period of time, the user interface of the first application is not displayed A user data loss exception occurs.

With reference to the second aspect, in a possible implementation manner, the method further includes: after the user interface of the first application is closed and displayed, when the user interface of the first application is displayed again after a period of time, the electronic device does not display the first application startup interface.

Since the application has been running after entering the background, when the application returns to the foreground to run again, the application does not need to be restarted, so the application startup interface will not be displayed.

With reference to the second aspect, in a possible implementation manner, the startup interface includes one or more of the following pages provided by the first application while waiting for the first application to be started: a startup page and an advertisement page.

With reference to the second aspect, in a possible implementation manner, the user interface of the first application is a video playback interface, and the user data is the video playback progress.

That is to say, when there is data loss in the application, the application may be a video playback application. When the application switches to the background and returns to the foreground after a period of time, the playback progress may be cleared and the video will be restored. When playback starts at the beginning. Such a video playback application is suitable for keeping running after switching to the background, thereby avoiding the problem of user data loss.

With reference to the second aspect, in a possible implementation manner, the method further includes: if the user interface of the first application is displayed again after a period of time after being closed and displayed, the first function calls the first If the permission is abnormal, when the user interface of the first application is closed and displayed for more than a preset time period, the electronic device ends running the first application, and the electronic device reclaims the first permission of the first application.

When the application is running and the function call permission fails, it may be because the application has been running in the background after switching to the background, and the permission obtained by the application is valid during a single operation. If it is recycled by an electronic device, the permission required for the function cannot be obtained when the application starts the function, and the function fails to run, then the electronic device can run the application in the background and end running the application after the preset time period has expired, and the application will be recycled and granted The effective permissions during a single operation can avoid the failure of function call permissions, improve the operation of the application, and enhance the user experience.

In combination with the second aspect, in a possible implementation manner, the method further includes: after the user interface of the first application is displayed after being closed and displayed again after a period of time, the first function successfully invokes the first permission .

With reference to the second aspect, in a possible implementation manner, the method further includes: after the user interface of the first application is closed and displayed, when the user interface of the first application is displayed again after a period of time, the electronic device displays the user interface of the first application. Start interface.

Since the electronic device will end the running of the application when the application runs in the background for more than the preset time period, when the application returns to the foreground to run again, the electronic device needs to restart the process of the application, and the electronic device will display the display when the application is started. The application's launch interface.

With reference to the second aspect, in a possible implementation manner, the first function is a voice chatting function, and the first authority is a microphone.

That is to say, when there is data loss in the application, the function may be a voice chat function. The application can use the voice chat function normally before switching to the background operation. When the application enters the background and runs for more than a preset time, the electronic device will recycle the application's microphone. permission, when the app returns to the foreground again, there may be a possibility that the voice chat function cannot obtain the user's voice information. Such an application is suitable for ending the operation after switching to the background and exceeding the preset time period, thereby avoiding the problem of the failure of the application's function invocation permission.

In a third aspect, embodiments of the present application provide an electronic device, including: a display screen, a memory, one or more processors, multiple application programs, and one or more programs; wherein the one or more programs are stored in The memory is characterized in that, when the one or more processors execute the one or more programs, the electronic device enables the electronic device to implement the method described in the first aspect or any one of the implementation manners of the first aspect.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium includes instructions, and when the instructions are executed on an electronic device, the electronic device is made to perform the first aspect or the first aspect The method described in any one of the embodiments.

In a fifth aspect, the embodiments of the present application provide a computer program product, which, when the computer program product runs on a computer, causes the computer to execute the method described in the first aspect or any one of the implementation manners of the first aspect.

By implementing the technical solutions provided by the embodiments of the present application, the electronic device can determine whether to provide a single authorization authorization method for the permission in the permission window of the application according to whether the application is a whitelist application or a blacklist application when the permission is configured for the application. , to prevent the user from choosing an authorization method that affects the running of the application.

Description of drawings

1 is a schematic diagram of the relationship between different authorization modes of an application and the running state of the application;

Fig. 2A-Fig. 2C is a kind of scenario of single authorization to the application;

3 is a hardware structure diagram of an electronic device provided by an embodiment of the present application;

4 is a software structure diagram of an electronic device provided by an embodiment of the present application;

5A-5H provide some user interfaces according to the embodiments of the present application;

FIG. 6 is a schematic flowchart of a rights management method provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described clearly and in detail below with reference to the accompanying drawings. Wherein, in the description of the embodiments of the present application, unless otherwise specified, “/” means or, for example, A/B can mean A or B; “and/or” in the text is only a description of an associated object The association relationship indicates that there can be three kinds of relationships, for example, A and/or B can indicate that A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of this application , "plurality" means two or more than two.

Hereinafter, the terms "first" and "second" are only used for descriptive purposes, and should not be construed as implying or implying relative importance or implying the number of indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present application, unless otherwise specified, the "multiple" The meaning is two or more.

The term "user interface (UI)" in the following embodiments of this application is a medium interface for interaction and information exchange between an application program or an operating system and a user, which realizes the internal form of information and the form acceptable to the user. conversion between. The user interface is a source code written in a specific computer language such as java and extensible markup language (XML). A commonly used form of user interface is a graphical user interface (graphic user interface, GUI), which refers to a user interface related to computer operations displayed in a graphical manner. It can be text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, and other visual interface elements displayed on the display screen of the electronic device.

For ease of understanding, a brief explanation of the authorization methods involved in application authorization is given first.

Since the application is opened for the first time or in the process of running the application, the electronic device will display a permission window to prompt the user to grant permission, and the permission window can also display various authorization methods: always allow, allow during use, allow this run, prohibit, etc. etc., so that users can grant permissions for different durations of applications according to different needs.

Among them, always allow means that after the permission is granted to the application, the application always has the permission. Allowed during use means that after a permission is granted to an app, the app only has the permission while the user is using the app. This running permission means that after the permission is granted to the application, the application only has the permission during the last time the user uses the application. Blocking means denying permission to an app.

FIG. 1 exemplarily shows the relationship between the above authorization mode and the running state of the application.

As can be seen from Figure 1, the running state of the application includes three types: foreground running, background running, and closing. It should be noted that the running state of the application mentioned here is understood from the user's point of view. From the user's point of view, foreground operation means that the electronic device runs the application, and the running process of the application is visible to the user, and the application can interact with the user. For example, the user can browse the user interface provided by the application through the display of the electronic device. Background running means that the electronic device runs the application, but the running process of the application is invisible to the user, and the application cannot interact with the user. Off means the electronic device is not running the application. Wherein, when the electronic device is a mobile phone, the user can switch the application from the foreground running to the background running through a sliding operation (for example, an upward sliding operation) on the display screen. The interface switches from the user interface of the application to another interface, for example, the main interface of the electronic device. The user can view the historical access records to the application through the multitasking window, wherein the multitasking window can display the user interface of one or more applications that the user has viewed historically, and the electronic device can receive the user acting on one of the applications. The sliding operation of the interface (for example, the upward sliding operation) completely closes the application, that is, the operation of the application ends.

Among them, in stages 0-t1, t8-t9, the application is closed, after t1-t3, t4-t5, t7-t8, and t9, the application is in the foreground running state, and in stages t3-t4, t5-t7, the application is running in the background state. When the authorization method is Prohibited, no matter whether the application is running or not, the application has no permission. When the authorization method is Always Allowed, the application will always have the permission after obtaining the permission at time t2. After permission, the application will have this permission every time it runs in the foreground, and the running time in the background does not exceed the threshold, which is the duration of t5-t6). After obtaining the permission, the application has the permission only during a single running process and the background running time does not exceed the threshold, that is, the t2-t6 stage.

It can be seen that when the authorization method is allowed for this operation, when the application permission is granted, the application only has the permission during a single operation, and the time when the application enters the background operation does not exceed the threshold. When the application is running in the background When the time exceeds the threshold, the electronic device will reclaim the permission of the application.

It can be understood that the permission granting situation mentioned above is for a single permission, and in other embodiments of the present application, this operation permission may also be referred to as this use permission, single permission, one-time authorization, single permission. Sub-authorization, single-time authority, only this time, etc., the name is not limited in this embodiment of the present application.

In the following embodiments of the present application, for the convenience of description, the authorization mode allowed in this operation is referred to as a single authorization.

Figures 2A-2C illustrate a scenario in which an application is authorized for a single time.

FIG. 2A shows a permission window 01 that prompts the electronic device to authorize the browser when the browser is opened for the first time. After the user grants the permission to the browser for this operation, the browser can obtain the process of this operation. Permission to access location information in .

FIG. 2B shows the user interface of the browser displayed by the electronic device after the browser authorization is completed, and the browser is in the foreground running state at this time. The area 02 in the user interface is used to display some news pushed by the browser when the browser enables the nearby news push function, and these news are the news searched by the browser in combination with the user's geographic location. At this time, since the electronic device grants the access authority to the location information to the browser when the browser is opened, the nearby news push function of the browser can operate normally at this time.

FIG. 2C shows a user interface displayed by the electronic device when the browser is switched from running in the foreground to running in the background, and after a period of time, the browser runs in the foreground again. At this time, when the duration of the period of time is greater than the threshold, the electronic device will reclaim the browser's permission to access location information when the threshold time elapses after the browser switches from the foreground to the background. Then, when the browser returns to the foreground to run again, the app's nearby news feed function does not work properly. At this time, the nearby recommended news cannot be displayed in the area 02, and the prompt information 03 is displayed in the area 02. The prompt information 03 is used to remind the application that the location information of the electronic device cannot be obtained, so the positioning fails and the nearby news cannot be searched.

It can be seen from Fig. 2A-Fig. 2C that after the application is switched to running in the background, when the elapsed time exceeds the threshold, the electronic device will reclaim the valid permissions during a single operation of the application, resulting in the function of the application (nearby news push function) calling Permission (location information) failed.

One solution is that after a single authorization of the application, when the time for the application to switch to the background running exceeds the threshold, the electronic device can end running the application, that is, kill the process of the application, thereby ending the single running process of the application. , when the application is restarted, the historical interface displayed by the application before switching to the background can be re-displayed, and since the application has started a new running phase, the user can be requested to grant permission again, avoiding the occurrence of the application's permission recovery. , the app no longer displays the permission window, prompting the user for authorization issues.

However, the process of killing the application also has certain problems. When some applications are restarted after being closed, they may not be fully restored to the historical interface displayed by the application before switching to the background. For example, for video playback applications, the historical interface It can refer to the video playback interface. When the video playback application returns to the foreground to display again, it may not be able to locate the last video playback progress, that is, there is a problem of user data loss, which still affects the user's experience of the application.

Whether it is the failure of the function call permission or the loss of user data, the above problems are caused by the poor adaptation of the application to a single authorization, causing the application to run abnormally. Therefore, how to control the access of different applications to permissions and avoid the problem of abnormal operation of the application is an urgent problem to be solved at present.

The embodiment of the present application provides a rights management method, which can divide applications into blacklist applications and whitelist applications according to the degree of adaptation of different applications to a single authorization, and the degree of adaptation of a whitelist application to a single authorization Therefore, when configuring permissions for this type of application, the authorization method includes a single authorization, and the whitelist application is poorly adapted to a single authorization. Therefore, when configuring permissions for this type of application, the authorization A single authorization is not included in the method.

In this way, when the adaptation of the application to the single authorization is poor, the option of the single authorization can be removed to prevent the user from authorizing the application once. On the contrary, when the application is well adapted to a single authorization, that is, even if the application is configured with a single authorization, there will be no problem of abnormal operation, or when the problem of abnormal operation of the application is small, it can be used in the application. In the permission configuration of , add the option of the single authorization, and increase the user's choice. In general, this method can combine the adaptation of different applications to a single authorization, and customize the authorization method, realize the reasonable authorization of the application, and avoid the problem of large abnormal operation of the application due to the configuration of permissions.

When a whitelisted application runs in the foreground and switches to the background, and is displayed again after a period of time, there is one of the following exceptions: the user data of the whitelisted application is lost, the function call permission of the whitelisted application fails, or the above exception does not exist ; otherwise, the above two exceptions exist in the blacklist application.

Further, the whitelisted application can be further subdivided into two subclasses. The first subclass is mainly for the situation where the function access permission fails only when the application returns to the foreground after running in the background for a period of time. After this type of application enters the background to run for a preset time, the permissions of this type of application can be reclaimed, and the process of this type of application can be killed. The second subclass is mainly for applications that only appear when they return to the foreground after entering the background to run for a period of time. In the case of user data loss, the electronic device may only reclaim the permissions of such applications after such applications enter the background to run for a preset period of time, without killing the processes of such applications. Among them, according to which subclass in the whitelist the application is, you can authorize the application once during the application detection phase, and observe that after the application switches to the background to run for a preset time, kill the process of the application, or not kill the application. In the process of the application, whether there will be abnormal functional access rights or loss of user data, to determine whether the application is suitable for killing the process or not killing the process, so as to complete the division of subclasses in the whitelist.

That is to say, this method can further eliminate the problem of minor abnormal operation after the application is authorized for a single time by killing the process of the application or not killing the process of the application when the application is running in the background. . In this way, the electronic device can further control the application to adopt different operation modes according to the degree of adaptation of the application to a single authorization, so as to eliminate the problem of abnormal operation of the application, and improve the user's sense of experience.

The embodiment of the present application also provides a permission management method, which can grant a first permission valid during a single running period to an application, switch the application from foreground running to background running, and return to running in the foreground after a period of time At the time, the electronic device may display a permission window in response to the operation of enabling the function of the application, where the permission window is used to prompt the user to grant the first permission to the application.

This is because, when the application has a valid permission during a single run, if the time for the application to switch to the background running exceeds the threshold, the electronic device will reclaim the application's permission, but the application does not perceive the reclaimed permission and still exists by default. Continue to run under the permission setting, which means that when the application starts the function that requires the permission, the function cannot run normally. Therefore, the method can actively display the authorization window when the application returns to the foreground to run again and enable the function that requires the permission, and prompts the user to grant the application permission, so as to avoid the failure of the function access permission in the application.

The application mentioned in the method is a whitelisted application. When the application is a whitelisted application, there is a single authorization authorization method in the permission window displayed by the electronic device. Authorize the corresponding option to grant permissions valid for a single run to the application. For a specific description of the whitelist application, reference may be made to the foregoing content, which will not be repeated here.

In addition, when the application switches from the foreground to the background running, the electronic device can also end running the application or not after a preset time. Whether the application ends running can be determined in advance according to when the application ends running or does not end running. , whether there is a function call permission failure, or user data loss to select. For a specific description about whether the application has finished running, see the subsequent content, which will not be repeated here.

FIG. 3 shows a schematic diagram of a hardware structure of an electronic device 100 provided by an embodiment of the present application.

The electronic device 100 may be a cell phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as cellular telephones, personal digital assistants (personal digital assistants) digital assistant (PDA), augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, wearable devices, in-vehicle devices, smart home devices and/or smart cities equipment, etc., the specific types of the electronic equipment are not particularly limited in the embodiments of the present application.

The electronic device 100 may include a processor 101, a memory 102, a wireless communication module 103, a mobile communication module 104, an antenna 103A, an antenna 104A, a power switch 105, a sensor module 106, an audio module 107, a camera 108, a display screen 109, and the like. The sensor module 106 may include a gyro sensor 106A, an air pressure sensor 106B, a touch sensor 106C, and the like. The wireless communication module 103 may include a WLAN communication module, a Bluetooth communication module, and the like. The above multiple parts can transmit data through the bus.

In some embodiments, the processor 101 may be configured to determine whether the application is a whitelisted application or a blacklisted application, or, further, determine which subclass of the whitelisted application the application is.

In some embodiments, the memory 102 may be used to store a black and white list, in which the categories described by different applications are recorded, that is, a white list application or a black list application, or a certain sub-type application in the white list application.

In some embodiments, the mobile communication module 104 and the wireless communication module 103 may be used to receive other devices, such as black and white lists sent by a server. The black and white list can be obtained by the server testing each application. For the specific test process of the server, please refer to the subsequent content, which will not be repeated here.

The electronic device 100 may implement a display function through a GPU, a display screen 109, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display screen 109 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 101 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 109 is used to display images, videos, and the like. The display screen 109 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode). , AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diodes (quantum dot light emitting diodes, QLED) and so on. In some embodiments, the electronic device 100 may include one or N display screens 109 , where N is a positive integer greater than one.

In some embodiments, the display screen 109 can be used to display the user interface provided by the application, and when the permissions are configured for the application, the permission window of the application is displayed. For details about the content displayed on the display screen 109, please refer to the subsequent UI embodiments, here I won't go into details first.

It can be understood that, the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or less components than shown, or combine some components, or separate some components, or arrange different components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The electronic device may be a portable terminal device equipped with iOS, Android, Microsoft or other operating systems, such as a mobile phone, a tablet computer, a wearable device, etc., or a laptop computer (Laptop) with a touch-sensitive surface or a touch panel, Non-portable end devices such as desktop computers with touch-sensitive surfaces or touch panels. The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present invention takes an Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100 as an example.

FIG. 4 is a block diagram of the software structure of the electronic device 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, which are, from top to bottom, an application layer, an application framework layer, an Android runtime (Android runtime) and system libraries, and a kernel layer.

The application layer can include a series of application packages.

As shown in Figure 4, the application package can include applications such as camera, gallery, calendar, phone, address book, navigation, WLAN, music, settings, SMS and so on.

In some embodiments, during the running of the application, the application may need to access other application programs to obtain resources required for its own functions, such as accessing pictures in the gallery. At this time, the electronic device 100 may display an authorization window to prompt the user to request Grant the app permission to access other apps, which can refer to the aforementioned camera, gallery, calendar, and so on.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for the applications of the application layer. The application framework layer includes some predefined functions.

As shown in Figure 4, the application framework layer may include window managers, content providers, view systems, telephony managers, resource managers, notification managers, and the like.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, take screenshots, etc.

Content providers are used to store and retrieve data and make these data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone book, etc. Wherein, before the application accesses the data, the electronic device 100 may first display an authorization window, prompting the user to request permission for the application to access the data.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. View systems can be used to build applications. A display interface can consist of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide the communication function of the electronic device 100 . For example, the management of call status (including connecting, hanging up, etc.).

The resource manager provides various resources for the application, such as localization strings, icons, pictures, layout files, video files and so on.

The notification manager enables applications to display notification information in the status bar, which can be used to convey notification-type messages, and can disappear automatically after a brief pause without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also display notifications in the status bar at the top of the system in the form of graphs or scroll bar text, such as notifications of applications running in the background, and notifications that appear on the screen in the form of dialog windows. For example, text information is prompted in the status bar, a prompt sound is issued, the electronic device vibrates, and the indicator light flashes.

Android Runtime includes core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one is the function functions that the java language needs to call, and the other is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, safety and exception management, and garbage collection.

A system library can include multiple functional modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL) and so on.

The Surface Manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display drivers, camera drivers, audio drivers, and sensor drivers.

Some user interfaces involved in the rights management method are described below with reference to FIGS. 5A-5H .

In the user interface shown in FIGS. 5A-5H , taking the electronic device 100 running a browser application as an example, a browser application refers to a type of application program used to retrieve, display and transmit network information resources, and other implementations in this application In an example, the electronic device may run other applications, and the embodiments of the present application do not limit the applications run by the electronic device.

FIG. 5A illustrates an exemplary user interface 21 for an application menu on the electronic device 100 , which may be referred to as the main interface of the electronic device 100 .

As shown in FIG. 5A , the user interface 21 may include: a status bar 211 , a calendar indicator 212 , a weather indicator 213 , a settings icon 214 , and a browser icon 215 . in:

The status bar 211 may include one or more signal strength indicators for mobile communication signals, one or more signal strength indicators for wireless fidelity (WiFi) signals, a battery status indicator, and a time indicator. Calendar indicator 212 may be used to indicate the current time. Weather indicator 213 may be used to indicate the type of weather.

As shown in FIG. 5A , the electronic device 100 can detect the operation of opening the browser for the first time, that is, detect the user operation acting on the browser icon 215 , and display the user interface 31 shown in FIG. 5B in response to the user operation. Here, opening the browser for the first time may refer to opening the browser for the first time after the electronic device 100 installs or updates the browser, or opening the browser when the browser does not occupy data in the storage space of the electronic device 100 .

As shown in FIG. 5B , the user interface 31 is a user interface provided by a browser, and the user interface may be a home page provided by the browser, or a startup page displayed when the browser is first opened, or the like. In FIG. 5B, the user interface 31 is the main page provided by the browser.

In addition, the user interface 31 also includes a permission window 311 . The permission window 311 is used to display one or more permissions requested by the browser. Wherein, the permission window 311 includes a permission item 311A, the permission item 311A indicates the access permission of the browser to request the location information, wherein, the permission item 311A also includes the authorization method provided by the electronic device 100, wherein the authorization method can include this Authorization methods such as permission for the second operation, permission and prohibition when using this application, etc., different authorization methods indicate different time periods for the electronic device 100 to grant permissions to the application. In the permission item 311A shown in FIG. 5B , the permission item 311A includes a first authorization option 3111A, and the first authorization option 3111A indicates an authorization method that the electronic device 100 provides for the browser to allow for the current operation. The electronic device 100 provides the first authorization option 3111A in the permission window 311, which is determined according to the degree of adaptation of the browser to the authorization method. Here, the electronic device 100 provides the first authorization option 3111A to the browser, indicating that The browser adapts well to the single authorization, and the problem of abnormal application running will not occur because the electronic device 100 configures the single authorization for the browser, or the problem of abnormal application running is small.

It can be understood that when the browser does not adapt well to a single authorization, the authorization item 311A will not display the authorization mode allowed for this operation, that is, referring to FIG. 5C , in the authorization window 311, about the location In the permission item 311A of the information, compared with the permission item 311A in FIG. 5B , the electronic device 100 does not provide the option of single authorization.

That is, when the browser is poorly adapted to the single authorization, the electronic device 100 may not provide an option corresponding to the single authorization.

In addition, in the user interface shown in FIG. 5B , the permission window 311 further includes a cancel option 311B and a confirmation option 311C, wherein the cancel option 311B is used to cancel the configuration of the browser permission this time, and the confirmation option 311C is used to Window 311, configure permissions for the browser, wherein, when the first authorization option 3111A in the permission item 311A is selected, it means that the user has configured the browser to allow access to the location information of the electronic device 100 during this running process. permissions. After that, when the electronic device 100 receives the user operation acting on the determination control 311C, the electronic device 100 completes the permission configuration for the browser, runs the browser in the foreground, and displays the user interface 41 shown in FIG. The runtime interface provided for the browser.

As shown in FIG. 5D , the user interface 41 is used to display the retrieval entry of the browser, retrieval keywords and news recommended by the browser according to the location information. The user interface 41 includes a news display area 411, which is used to display the information searched according to the location information of the electronic device 100 when the browser activates the nearby news push function. This is because before running the application, the user has granted the application permission to access the location information during the current operation in the permission window 311 shown in FIG. 5B , so the browser can successfully obtain nearby news and display it in the news display area 411.

FIG. 5E shows that when the electronic device 100 is running the browser in the foreground, the electronic device 100 detects an operation of switching the running state of the application (eg, a slide-up operation), and the electronic device 100 switches the browser from running in the foreground to running in the background. After that, the user interface displayed by the electronic device 100 is switched from the running interface (user interface 41 ) provided by the browser to the main interface of the electronic device 100 as shown in FIG. 5F .

Optionally, the electronic device 100 may have other ways to switch the running state of the application. For example, when the electronic device 100 runs a browser, the browser can trigger the opening of another application. At this time, the electronic device 100 can display The user interface of another application. At this time, the browser switches from foreground to background. This embodiment of the present application does not limit the manner of switching the running state of the application.

As shown in FIG. 5F , after the browser is switched to run in the background and the first time elapses, the electronic device 100 detects the user operation acting on the browser icon 215 in the user interface 21 as shown in FIG. 5F , and responds to In this operation, the electronic device 100 runs the browser in the foreground again.

Wherein, after the browser is switched to run in the background, the electronic device 100 may have two optional modes: one is to close the process of the browser when the threshold time is reached, and the other is to run the browser in the background all the time. In this way, when the electronic device 100 uses the first method, when the electronic device 100 runs the browser in the foreground again, the electronic device 100 will first start the browser, that is, the process of creating the browser, and then display the running interface of the browser. When the electronic device 100 uses the second method, when the electronic device 100 runs the browser in the foreground again, the electronic device 100 directly displays the running interface of the browser without creating a process of the browser. Then, when the electronic device 100 creates the process of the browser, the electronic device 100 will first display a start page of the browser, or a start interface waiting for the browser to start, such as an advertisement page.

That is to say, when the electronic device 100 switches the browser to run in the background, and the threshold time (less than the first time) elapses, the electronic device 100 will kill the process of the browser. When the user operates the browser icon 215, the electronic device 100 will start the browser process, display the browser startup interface 51 as shown in FIG. 5G, and wait for the browser startup to complete. Afterwards, the electronic device 100 displays the operating interface of the browser shown in FIG. 5H again, and the operating interface is the user interface displayed during the foreground operation when the browser switched from foreground operation to background operation last time, that is, the user interface shown in FIG. 5D User interface 41 . After the electronic device 100 switches the browser to run in the background, and the electronic device 100 keeps running the browser in the background, when the time reaches the first time and the user operation acting on the browser icon 215 is detected, the electronic device 100 directly displays the following: User interface 41 shown in Figure 5H.

In the user interface 41 shown in FIG. 5H , since the browser has a news push function in this interface, the location information of the electronic device 100 needs to be called to obtain nearby information, so the electronic device 100 can display the information shown in FIG. 5H . The permission window 412 requests the user to grant the application permission to access location information. After the user agrees to grant the permission, the browser can continue to recommend nearby news to the user to avoid the problem that the browser cannot display nearby news.

FIG. 6 exemplarily shows a schematic flowchart of a rights management method provided by an embodiment of the present application.

As shown in Figure 6, the method includes:

S101. The electronic device 100 displays a first window for configuring a first permission of a first application.

The first window is used to display one or more permissions requested by the first application. Wherein, the first window displays permission items with the first permission.

Before the electronic device 100 displays the first window, the electronic device 100 may detect the first operation that triggers the configuration of the permission of the first application. For the electronic device 100 to display the first window of the first application, specifically, the electronic device 100 displays the first window of the first application in response to the first operation.

The electronic device 100 can trigger the configuration of the first application permission in the following three situations:

1) The electronic device 100 triggers the configuration of the first application permission in the setting application

That is, the electronic device 100 can configure the permissions of the first application through the setting application. Specifically, the electronic device 100 can find the permission list of the first application by setting the permission management in the application, so as to configure the first permission of the first application. Then, at this time, the first operation may be a click operation on an option corresponding to the authority management.

2) The electronic device 100 triggers the configuration of the permissions of the first application when the first application is opened for the first time without running the first application

The electronic device 100 opening the first application for the first time may mean that the electronic device 100 opens the first application for the first time after installing or updating the first application.

At this time, the electronic device 100 may trigger the display of a permission window of the first application by opening the first application, where the permission window indicates the permission requested by the first application. Then, at this time, the first operation may be a click operation on the icon of the first application, and the click operation may be used to trigger the opening of the first application and then trigger the display of the permission window of the first application, instructing the user to perform the permission of the first application. configuration.

It can be understood that the first operation is not limited to a click operation on the icon of the first application, and the first operation can be any operation for triggering the opening of the first application, for example, voice input, or acting on other applications. The operation is used to trigger other applications to open the first application during the running process.

Referring to FIG. 5A , the first application may be a browser, and the first operation may refer to a user operation acting on the browser icon 215 .

3) During the process of running the first application, the electronic device 100 starts the function of the first application and triggers the configuration of the first application permission

When the function of the first application requires the electronic device 100 to grant the corresponding permission to the first application to be able to start normally, when the electronic device 100 detects an operation that triggers the opening of the function of the first application, the permission window of the first application will be displayed. The permission window is used to request the user to grant the first permission required by the function of the first application. Then, at this time, the first operation may refer to an operation that triggers the function of opening the first application.

It can be understood that, it is not limited to the above three situations of triggering the first application permission configuration, which are not limited in this embodiment of the present application.

In addition, the electronic device 100 may determine whether to display the single authorization option in the permission window according to the adaptation of the application to the single authorization.

When the first application is a whitelisted application, the first application is allowed to use the first permission during a single operation of the first application, and the authorization mode of the first permission includes the first authorization mode, and the first authorization mode is to allow The first permission is used during a single run of the first application. In other words, when the first application is a whitelisted application, the first window may include a one-time authorization option for the first permission; when the first application is a blacklisted application, the first application is not allowed in the first application If the first authorization is used during a single operation, the authorization mode of the first authorization does not include the first authorization mode. In other words, when the first application is a blacklisted application, the first window does not include a single authorization option for the first permission.

Among them, the whitelist application refers to the application with a good degree of adaptation to a single authorization. After the user interface of the whitelist application is closed and displayed, when it is displayed again after a period of time, there is one of the following exceptions: User data is lost, the first function of the whitelisted application fails to invoke the first permission, or the above exception does not exist. Here, the first function refers to a function in the whitelist application that requires the first permission. On the contrary, a blacklisted application refers to an application with a poor degree of adaptation to a single authorization. After the user interface of the blacklisted application is closed and displayed, the above two exceptions exist when it is displayed again after a period of time.

The one-time authorization option is used to trigger the electronic device 100 to grant the first permission to the first application, which is valid during a single operation. The single running period refers to the running period during which the first application runs in the background and cannot exceed the threshold in this continuous stage from the start of the application to the end of the running. When the time that the first application runs in the background exceeds the preset duration, the first permission is granted to the first application during the single running period, and a continuous stage of running until running to the preset duration node is started. That is, when the time that the first application runs in the background exceeds the threshold, the electronic device 100 will reclaim the first permission granted to the first application that is valid during a single running period, and the first application will enter the next running period, or, the first The application finishes running.

In this embodiment of the present application, the electronic device 100 may store a configuration table, and the configuration table indicates that there are two types of applications, one type of application is a whitelist application, and one type of application is a blacklist application. In this way, before the electronic device 100 displays a window (eg, the first window) in which the first application configures the first permission, the electronic device 100 can determine whether the first application is a whitelisted application or a blacklisted application according to the configuration table, so as to decide whether to A one-time authorization option for the first permission is available in this window.

Wherein, the configuration table may configure a single authorization for the first application in advance, that is, grant the first authorization valid during a single operation to the first application, and test whether the first application has abnormal operation. If the first application is switched from the foreground to the background, and returns to the foreground after a period of time, one of the above whitelisted applications is abnormal or there is no abnormality, it means that the first application is a whitelisted application, and the The result is recorded in the configuration table. If during the test, the first application has the two exceptions mentioned in the above whitelist application, it means that the first application is a blacklist application, and the result is recorded in the configuration table.

In this way, when a user configures permissions for an application, the user can be prevented from selecting an authorization method that affects the operation of the application as much as possible, and the user's experience can be improved.

5B-5C, when the first application is a whitelist application, the first window may refer to the permission window 311 shown in FIG. 5B , the first permission is location information, the permission item is permission item 311A, the The first authorization method is the authorization method indicated in the first authorization option 3111A. When the first application is a blacklist application, the first window may be the authorization window 311 shown in FIG. 5C .

S102. The electronic device 100 grants the first permission valid during a single operation to the first application.

Specifically, the electronic device 100 may detect an operation acting on the first window, and in response to the operation, grant the first permission to the first application that is valid during a single operation, that is, allow the first application to operate in a single operation of the first application. Use this first permission during the period.

This operation may refer to an operation of configuring permissions by a user. For example, referring to FIG. 5B , the operation may refer to a selection operation acting on the first authorization option 3111A and a user operation acting on the determination option 311C. In this way, the electronic device 100 can Finish granting the app permission to access location information during a single run. The first authority is location information.

It should be noted that, when the electronic device 100 grants the first permission valid during a single operation to the first application, it means that the first application mentioned in S102-S106 is a whitelisted application.

S103, the electronic device 100 closes the user interface displayed by the first application.

The user interface displayed by the electronic device 100 closing the first application includes two meanings:

1) Before the electronic device 100 closes the user interface displayed by the first application, the electronic device 100 displays the user interface of the first application, that is, the electronic device 100 runs the first application in the foreground.

2) The electronic device 100 only closes the user interface displayed by the first application, that is, the electronic device 100 runs the first application in the background.

In other words, closing the user interface displayed by the first application by the electronic device 100 may mean that the electronic device 100 switches the first application from running in the foreground to running in the background.

Referring to FIG. 5D , the user interface 41 may refer to the user interface of the first application displayed when the electronic device 100 runs the first application in the foreground. It can be seen from the news display area 411 that the application can obtain the location information of the electronic device 100 and According to the location information, the nearby news push function is successfully run, and the news acquired according to the location information is displayed in the news display area 411 .

The electronic device 100 switches the first application from foreground running to background running may specifically be that the electronic device 100 detects the user's operation, and in response to the operation, switches the application running in the foreground to running in the background. The operation may be an operation of returning to the main interface of the electronic device 100, or an operation of opening other applications, and the embodiment of the present application does not limit the operation of switching the running state of the first application.

Referring to FIG. 5E , the operation may refer to a slide-up operation acting on the display screen, and the slide-up operation may be used to switch the user interface of the browser displayed by the electronic device 100 to the main interface of the electronic device 100 .

S104. After a period of time, the electronic device 100 displays the user interface of the first application again.

The electronic device 100 displaying the user interface of the first application again may mean that the electronic device 100 runs the first application in the foreground again. The user interface may refer to the user interface displayed when the application was last run in the foreground. Referring to FIG. 5H , when the electronic device runs the first application in the foreground again, the displayed user interface may refer to the user interface 41 .

Since the first permission is a permission that is valid during a single running period configured by the electronic device 100 for the first application, when the time elapsed after the first application is switched to run in the background is greater than a preset time period (for example, 5 minutes), the electronic device 100 will reclaim the first permission of the first application.

In addition, in addition to determining whether to display the single authorization option in the permission window according to the adaptation of the first application to the single authorization, it is also possible to further determine whether the preset time period ends after the user interface of the first application is closed and displayed. Run the first application.

This is because different applications may behave differently when the user interface is displayed again after a period of time after the user interface is closed.

If user data is lost when the user interface of the first application is displayed again after being closed for a period of time, the electronic device still runs the first application during the period of time that the user interface of the first application is closed and displayed. The running of the first application is not terminated. At this time, since some applications are switched from foreground to background, if the application ends running in the background, when the application returns to the foreground, some applications may not be able to restore or fail to return to the state of the last foreground operation. Fully restored to the user interface displayed in the last foreground run, there is a loss of user data. Taking a video playback application as an example, the user interface displayed again may refer to the video playback interface, and the user data may refer to the video playback progress. Some video playback applications may not be restored to the previous foreground when they return to the foreground to run again. At runtime, the node where the video plays, may replay the video from the beginning of the video. Therefore, the problem of user data loss when returning to the foreground can be avoided by not killing the application process. In this way, after the user interface of the first application is turned off and displayed, when it is displayed again after a period of time, the user interface of the first application does not show an abnormality of user data loss.

However, if the user interface of the first application is displayed after being closed and displayed again after a period of time, an exception occurs when the first function invokes the first permission, and the user interface of the first application is closed and displayed for more than a preset period of time. , the electronic device 100 may end running the first application. This is because the first permission of the first application is a permission valid during a single operation, and when the user interface of the first application is closed and displayed for more than a preset period of time, the electronic device 100 will reclaim the first permission of the first application, However, some applications may not be able to perceive the lack of the first permission, so that the first application cannot obtain the first permission required by the first function, that is, the first function of the application fails to invoke the first permission, causing the application to run abnormally. Taking chat applications as an example, the first function may refer to the voice chat function, and the first permission may refer to the microphone. Some chat applications may return to the foreground to run again, because the permission to access the microphone has been revoked, and the chat category The application cannot obtain the user's voice information, but will not display a prompt message to prompt the user to enable the microphone permission, which will cause the voice chat function to fail. Therefore, you can actively end the single running phase of the application by killing the process of the application, so as to avoid the problem that the function call permission fails when returning to the foreground again. In this way, after the user interface of the first application is closed and displayed, when the user interface of the first application is displayed again after the first time, the first function of the first application can successfully invoke the first permission.

Therefore, the configuration table can be further subdivided into two subclasses of applications in the whitelist. The applications in the first subclass can only reclaim the permissions of the application after the application enters the background to run for a period of time, keeping the application running, and the second This subclass of applications can reclaim the permissions of the application and end the running of the application when the application enters the background running.

In this way, the electronic device can further control the application to adopt different authorization details according to the degree of adaptation of the application to a single authorization, so as to avoid the problem that the application runs abnormally when the application is authorized for a single time, and improve the user's sense of experience.

Similarly, it is possible to determine which sub-type application each application is specifically applicable to in the whitelisted applications by testing the abnormality of the application when the user interface of the application is displayed again after a period of time after being displayed.

Wherein, when the first application is an application of the first subclass, after the user interface of the first application is closed and displayed and displayed again after a period of time, the first application runs directly from the background to the foreground, and the electronic The device 100 does not display a startup interface of the first application, where the startup interface includes one or more pages such as a startup page and an advertisement page provided by the first application while waiting for the first application to start. Referring to FIG. 5G , the startup interface may refer to the user interface 51 .

When the first application is an application of the second subclass, after the user interface of the first application is closed and displayed and displayed again after a period of time, after the first application switches from the foreground to the background, it will It ends running after a preset duration, and then restarts and runs in the foreground when a certain period of time is reached. Then, during the process of restarting the first application by the electronic device 100, the electronic device 100 will first start the process of the application, display the startup interface of the first application, and then display the running interface of the application after the first application is started. 5F-5H, when the electronic device 100 receives a user operation on the browser icon 215 by the user, and runs the browser in the foreground again, the electronic device 100 displays the user interface 51 shown in FIG. 5G, and then displays the following The user interface 41 provided by the browser shown in FIG. 5H.

To sum up, when the electronic device 100 determines that the first application is the first sub-type application, when the electronic device 100 displays the user interface of the first application again, the startup interface of the first application will not be displayed. When it is determined that the first application is the second sub-type application, when the electronic device 100 displays the user interface of the first application again, the startup interface of the first application will be displayed.

S105. In response to the operation of starting the first function, the electronic device 100 displays a second window, where the second window is used to prompt the user to grant the first application the first permission to use.

After the electronic device 100 reclaims the first permission of the first application, the electronic device 100 may display the permission window again, that is, the second window, prompting the user that the first permission has been reclaimed and the first application needs to be granted the first permission again. In this way, the electronic device 100 can actively prompt the user to authorize the application, which can prevent the application from affecting the running of the application due to lack of permission.

Referring to FIG. 5H , the second window may be referred to as the permissions window 412 .

S106, the electronic device 100 completes the configuration of the first permission for the first application.

Completing the configuration of the first permission by the electronic device 100 may refer to receiving an operation that the user grants the first permission to the application, and granting the first permission to the application, or, receiving an operation that the user refuses to grant the first permission to the application, refusing to grant the first permission to the application. a permission.

In this way, the user can determine whether to grant the first permission to the first application again according to his own needs, thereby improving the operability of the user.

It can be understood that the above black and white list is only for a single permission of an application. For example, for the first permission of an application, the application may include a single authorization option, and for the second permission of an application, the application may not include a single authorization. options. This is due to the different degrees of adaptation of applications to a single authorization for different permissions. In this way, the electronic device can adjust the authorization method of different permissions in the permission window according to the degree of adaptation of the application to a single authorization for different permissions, so as to avoid the abnormal operation of the application due to a single authorization as much as possible, which affects the user experience. The problem.

The various embodiments of the present application can be arbitrarily combined to achieve different technical effects.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The computer program instructions, when loaded and executed on a computer, result in whole or in part of the processes or functions described herein. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented. The process can be completed by instructing the relevant hardware by a computer program, and the program can be stored in a computer-readable storage medium. When the program is executed , which may include the processes of the foregoing method embodiments. The aforementioned storage medium includes: ROM or random storage memory RAM, magnetic disk or optical disk and other mediums that can store program codes.

In a word, the above descriptions are merely examples of the technical solutions of the present invention, and are not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present invention shall be included within the protection scope of the present invention.

Claims (19)

1. A rights management method, characterized in that the method comprises: The electronic device displays the first window of the first application, and the first window displays the permission item with the first permission; If the first application is a whitelisted application, the first application is allowed to use the first permission during a single running of the first application, and the authorization mode of the first permission includes the first authorization mode, the first authorization mode is to allow the first authorization to be used during a single operation of the first application; otherwise, the first authorization mode is not included in the authorization mode of the first authorization; After the user interface of the whitelist application is closed and displayed again after a period of time, there is one of the following exceptions: the user data of the whitelist application is lost, the first function of the whitelist application calls the The first permission fails, or the exception does not exist; If user data is lost when the user interface of the first application is displayed again after being closed for a period of time, the electronic The device still runs the first application, the duration of the period of time exceeds a preset duration, and after the preset duration is exceeded, the electronic device reclaims the first permission of the first application; If the user interface of the first application is displayed after being closed and displayed again after a period of time, if the first function fails to invoke the first permission, the user interface of the first application is closed and displayed. When the preset time period is exceeded, the electronic device ends running the first application, and the electronic device reclaims the first permission of the first application. 2. The method according to claim 1, wherein the method further comprises: After the user interface of the first application is closed and displayed, when the user interface of the first application is displayed again after the period of time, the user interface of the first application does not exhibit an abnormality of user data loss. 3. The method according to claim 1, wherein the method further comprises: After the user interface of the first application is turned off and displayed, when the user interface of the first application is displayed again after the period of time has elapsed, the electronic device does not display the startup interface of the first application. 4 . The method according to claim 3 , wherein the startup interface comprises one or more of the following pages provided by the first application while waiting for the first application to be started: a startup page and an advertisement page. 5 . 5 . The method according to claim 1 , wherein the user interface of the first application is a video playback interface, and the user data is a video playback progress. 6 . 6. The method of claim 1, wherein the method further comprises: When the user interface of the first application is displayed again after a period of time after being closed and displayed, the first function successfully invokes the first permission. 7. The method according to claim 1 or 6, wherein the method further comprises: After the user interface of the first application is turned off and displayed and displayed again after a period of time, the electronic device displays the startup interface of the first application. 8. The method according to claim 1 or 6, wherein the first function is a voice chatting function, and the first authority is a microphone. 9. The method according to claim 1 or 6, wherein the method further comprises: After the user interface of the first application is closed and displayed, after a period of time has elapsed, the user interface is displayed again, In response to the operation of starting the first function, the electronic device displays a second window, prompting the user to grant the first application the use of the first permission. 10. An authorization management method, characterized in that the method comprises: The electronic device allows the first application to use the first permission during a single run of the first application; The electronic device closes and displays the user interface of the first application, and displays the user interface of the first application again after a period of time; The electronic device displays a second window in response to the operation of starting the first function, prompting the user to grant the first application to use the first permission; The first application is a whitelist application, and the user interface of the whitelist application is displayed again after a period of time after being closed and displayed, and there is one of the following exceptions: the user data of the whitelist application is lost, all The first function of the whitelist fails to invoke the first permission, or the exception does not exist; If user data is lost when the user interface of the first application is displayed again after being closed for a period of time, the electronic The device still runs the first application, the duration of the period of time exceeds a preset duration, and after the preset duration is exceeded, the electronic device reclaims the first permission of the first application; If the user interface of the first application is displayed after being closed and displayed again after a period of time, if the first function fails to invoke the first permission, the user interface of the first application is closed and displayed. When the preset time period is exceeded, the electronic device ends running the first application, and the electronic device reclaims the first permission of the first application. 11. The method of claim 10, wherein before the electronic device allows the first application to use the first permission during a single execution of the first application, the method further comprises: The electronic device displays the first window of the first application, the first window displays the permission items of the first permission, the authorization mode of the first permission includes a first authorization mode, the first The authorization mode is to allow the first permission to be used during a single execution of the first application. 12. The method of claim 10, wherein the method further comprises: After the user interface of the first application is closed and displayed, when the user interface of the first application is displayed again after the period of time, the user interface of the first application does not exhibit an abnormality of user data loss. 13. The method of claim 10, wherein the method further comprises: After the user interface of the first application is turned off and displayed, when the user interface of the first application is displayed again after the period of time has elapsed, the electronic device does not display the startup interface of the first application. 14. The method according to claim 13, wherein the startup interface comprises one or more of the following pages provided by the first application while waiting for the first application to be started: a startup page and an advertisement page. 15 . The method according to claim 10 , wherein the user interface of the first application is a video playback interface, and the user data is a video playback progress. 16 . 16. The method of claim 10, wherein the method further comprises: When the user interface of the first application is displayed again after a period of time after being closed and displayed, the first function successfully invokes the first permission. 17. The method according to claim 10 or 16, wherein the method further comprises: After the user interface of the first application is turned off and displayed and displayed again after a period of time, the electronic device displays the startup interface of the first application. The method according to claim 10 or 16, wherein the first function is a voice chat function, and the first authority is a microphone. 19. An electronic device, characterized in that it comprises a processor and a memory, the memory includes an internal memory and an external memory, and the processor is used to execute a computer program stored in the internal memory or the external memory, so as to realize as claimed in the claims The method of any one of 1 to 9, or any one of 10 to 18.

Images