Authority management method, user interface and electronic equipment
The permissions requested by the application are displayed through the centralized permission window, and the permissions that are recommended or not recommended based on the authorization status of multiple users, solving the blindness of users when granting application permissions, and improving privacy and security and application configuration efficiency.
Patent Information
- Application Number
- CN202411107080.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2021-08-12
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2041-08-12
AI Technical Summary
The lack of understanding of users when granting application permissions leads to the application's random or malicious calls to the hardware and software resources of electronic devices, increasing the risk of user privacy information leakage.
Provides a permission management method, displays the permissions obtained by the application through a centralized permission window, and recommends or disrecommended permissions based on the authorization status of multiple users, helping users quickly and reasonably configure permissions and reduces the risk of privacy information leakage.
Simplify user operations, reduce the risk of privacy information leakage, improve the speed and security of user permission configuration to the application, and ensure the normal operation of the application.
Smart Images

Figure CN118940317A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of terminal and communication technology, and in particular to a permission management method, a user interface and an electronic device. Background Art
[0002] With the development of the Internet, more and more applications can be installed on electronic devices. During the operation of the application, it is necessary 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 privacy information. Therefore, when the application is opened for the first time or during the operation of the application, 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 the corresponding hardware or software resources in the electronic device.
[0003] However, since many users do not understand or pay attention to the interests of granting application permissions, they grant permissions to applications at will, resulting in the applications making arbitrary or malicious calls to the hardware and software resources of electronic devices, causing the risk of leakage of users' privacy information, affecting the privacy security of users.
[0004] So, how to control the reasonable acquisition of permissions by applications is a problem that needs to be solved urgently. Summary of the invention
[0005] The present application provides a permission management method, a user interface and an electronic device.
[0006] In some embodiments of the present application, permissions requested by an application are displayed through a centralized permission window, and the centralized permission window also displays the minimum permissions recommended by the electronic device, which can guide the user to grant the minimum permissions to the application.
[0007] In a first aspect, the present application provides a permission management method, comprising: an electronic device starts an application when the application is not running;
[0008] In response to opening the application, the electronic device displays a first window including a first permission item and a second permission item, the first window indicating the permission requested by the application, the first permission item indicating the permission recommended by the electronic device for the user to grant to the application, the second permission item indicating that the electronic device does not recommend the user to grant to the application, and the permission indicated by the first permission item is the minimum permission that the application is stipulated to use.
[0009] In implementing the method provided in the first aspect, the electronic device can display a centralized permission window when opening the application for the first time, and the centralized permission window is used to display multiple permissions requested by the application, and the centralized permission window displays permissions that the electronic device recommends the user to grant to the application, and permissions that the user is not recommended to grant to the application. In this way, the user can refer to the permissions recommended and not recommended by the electronic device to configure permissions for the application, avoiding the user blindly granting permissions to the application, causing the user's privacy information to be leaked, and speeding up the user's configuration of application permissions.
[0010] In combination with the first aspect, in one possible implementation, the permissions recommended by the electronic device are permissions when multiple users have pre-authorized the application and the number of users who agree to grant the application the use of the permissions is greater than a threshold; the permissions not recommended by the electronic device are permissions when multiple users have pre-authorized the application and the number of users who refuse to grant the application the use of the permissions is greater than a threshold.
[0011] That is, when authorizing the application, the permissions recommended and not recommended by the electronic device can be obtained based on the permissions granted and rejected by multiple users when configuring permissions. In this way, the electronic device can provide the public's tendency to authorize the application as a reference to the user, helping the user to quickly complete the application authorization.
[0012] In combination with the first aspect, in a possible implementation method, the permissions recommended by the electronic device are permissions when multiple users have pre-authorized similar applications of the application and the number of users who agree to grant similar applications of the application the use of the permissions is greater than a threshold; the permissions not recommended by the electronic device are permissions when multiple users have pre-authorized similar applications of the application and the number of users who refuse to grant similar applications of the application the use of the permissions is greater than a threshold.
[0013] That is, when authorizing the application, the electronic device can obtain the permissions recommended and not recommended by the application based on the permissions granted and denied to similar applications by multiple users when configuring permissions. In this way, the electronic device can provide the user with the public's tendency to authorize applications similar to the application as a reference, helping the user to quickly complete the application authorization.
[0014] In combination with the first aspect, in a possible implementation, before the electronic device opens the application without running the application, the method also includes: the electronic device obtains a permission configuration table sent by the server, and the permission configuration table is used to determine the permissions recommended and not recommended by the electronic device.
[0015] That is, the permissions recommended and not recommended by the electronic device may be determined by the server, and the server may determine the recommended permissions and not recommended permissions by analyzing the configuration of permissions by multiple users.
[0016] In combination with the first aspect, in a possible implementation, the method also includes: the electronic device detects an operation by a user to enable a first function of the application, and the permission required for the first function is not the permission indicated by the first permission item; the electronic device displays a second window, and a third permission item is displayed in the second window, and the third permission item includes first indication information of whether the electronic device recommends that the user grant the application the permission required for the first function.
[0017] It can be seen that during the running of the application, the electronic device can also detect the operation of enabling the application function, display the function permission window, and prompt the user to grant the required permission for the function. The function permission window also displays a prompt message indicating whether the electronic device recommends the permission. In this way, the user can refer to the prompt message to determine whether to grant the permission to the application, thereby protecting the user's privacy and security as much as possible.
[0018] In combination with the first aspect, in a possible implementation, the permission indicated by the third permission item is location information, and the second window includes a precise location option and a fuzzy location option and second indication information, the precise location option is used to instruct the application to obtain a first location of the electronic device, and the fuzzy location option is used to instruct the application to obtain a second location of the electronic device, wherein the first location is the actual geographical location of the electronic device; the accuracy of the second location is lower than that of the first location, and / or there is an offset between the second location and the first location, and the second indication information is used to indicate whether the location option recommended by the electronic device is the precise location option or the fuzzy location option.
[0019] During the running of an application, when the application requests permission for location information, the electronic device can also provide two modes for the application to obtain location information: precise location and fuzzy location. In this way, the electronic device can distinguish different scenarios and recommend whether users should grant precise location information, thereby avoiding privacy information leakage as much as possible while ensuring the running of the application.
[0020] In combination with the first aspect, in a possible implementation manner, the first permission item includes a switch option in an on state, and the second permission item includes a switch option in a off state.
[0021] That is, the electronic device can add a switch option in the permission window and use the on or off state of the switch option to indicate whether the electronic device recommends the permission.
[0022] In combination with the first aspect, in a possible implementation, the first permission item includes first indication information, and the first indication information describes the proportion of users who agree to authorize the permission indicated by the first permission item when multiple users authorize the application.
[0023] That is to say, the electronic device can add the public's selection of permission items in the permission window, such as the ratio of those who choose to agree to the authorization, and use the ratio as the user's reference data. When the ratio is high, the user can know that most people have chosen to agree to the authorization for the permission, and when the ratio is low, the user can know that most people have chosen to refuse the authorization for the permission. In this way, the ratio is used to provide a reference for the user, helping the user to quickly complete the permission configuration of the application.
[0024] In combination with the first aspect, in one possible implementation, the first permission item includes second indication information, and the second permission item does not include the second indication information, and the second prompt information is used to indicate that the permission indicated by the first permission item is the permission that the electronic device recommends the user to grant to the application, and the permission indicated by the second permission item is the permission that the electronic device does not recommend the user to grant to the application.
[0025] That is to say, the electronic device can add additional information to the recommended permission items to distinguish them from the non-recommended permission items. For example, the electronic device can add text information such as "recommended" and "priority" to the recommended permission items to guide the user to grant the permission to the application.
[0026] In combination with the first aspect, in a possible implementation, the first window also includes countdown prompt information, and the countdown prompt information is used to prompt the user to complete the authorization of the application within the time limit. After the electronic device displays the first window, the method also includes: after the countdown ends, when the electronic device does not detect any operation on the first window, the electronic device grants the application the permission indicated by the first permission item.
[0027] That is to say, by displaying a countdown in the permission window, it is possible to prevent users from wasting too much time when authorizing an application, and guide users to quickly complete the authorization of the application.
[0028] In combination with the first aspect, in a possible implementation, the permission indicated by the first permission item is location information, and the first permission item includes a location mode option and third indication information. The location mode option is used to trigger the application to obtain the precise geographic location of the electronic device, and the third indication information is used to indicate whether the electronic device recommends the application to obtain the precise geographic location of the electronic device.
[0029] In a second aspect, an embodiment of the present application provides an electronic device, comprising: a display screen, a memory, one or more processors, multiple applications, and one or more programs; wherein the one or more programs are stored in the memory; and characterized in that when the one or more processors execute the one or more programs, the electronic device implements the method described in the first aspect or any one of the embodiments of the first aspect.
[0030] In a third aspect, an embodiment of the present application provides a computer-readable storage medium, which includes instructions. When the instructions are executed on an electronic device, the electronic device executes the method described in the first aspect or any one of the implementations of the first aspect.
[0031] In a fourth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a computer, it enables the computer to execute the method described in the first aspect or any one of the implementation modes of the first aspect.
[0032] By implementing the technical solution provided in the embodiments of the present application, the electronic device can provide a centralized permission window for the permission configuration of the application, and display the permissions requested by the application in a centralized permission window, thereby simplifying the user's operation. In addition, the electronic device can also indicate in the centralized permission window the permissions that are recommended for users to grant to the application and the permissions that are not recommended for users to grant, thereby providing a reference for users to authorize the application, guiding users to grant the least permissions to the application, and minimizing the risk of leakage of user privacy information. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] Figure 1A-Figure 1C Some user interfaces involved in obtaining permissions for an application;
[0034] Figure 2 A hardware structure diagram of an electronic device provided in an embodiment of the present application;
[0035] Figure 3 A software structure diagram of an electronic device provided in an embodiment of the present application;
[0036] Figure 4A-4B , Figure 5A-Figure 5B , Figure 6A-6B Some user interfaces provided for embodiments of the present application;
[0037] Figure 7 A flowchart of the permission management method provided in the embodiment of the present application. DETAILED DESCRIPTION
[0038] The technical solutions in the embodiments of the present application will be described clearly and in detail below in conjunction with the accompanying drawings. 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 the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.
[0039] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.
[0040] The term "user interface (UI)" in the following embodiments of the present application refers to a medium interface for interaction and information exchange between an application or operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. The user interface is a source code written in a specific computer language such as Java and extensible markup language (XML). The interface source code is parsed and rendered on an electronic device, and finally presented as content that can be recognized by the user. The commonly used form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operation displayed in a graphical manner. It can be a visual interface element such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. displayed on the display screen of an electronic device.
[0041] Figure 1A-Figure 1C Some user interfaces involved in application obtaining permissions are shown as examples.
[0042] Figure 1A , Figure 1B , Figure 1C The following diagram shows the user interfaces displayed by the electronic device in sequence when the application is first opened. These user interfaces are used to display permission windows 01-03 respectively, and each permission window is used to prompt the user to grant permissions related to the application.
[0043] Among them, permission windows 01-03 are used to prompt the user to grant the application permission to obtain device information, storage space, and location information of the electronic device. Among them, after receiving the user's processing of a permission window, for example, setting the application to always allow, allow or prohibit the application from using the application, and a permission mentioned in the permission window, the electronic device will display the next permission window to prompt the user to grant the application the next permission.
[0044] That is to say, before using the application, the user needs to process multiple permission windows in succession, that is, to process whether to grant the application the corresponding permissions. It can be seen that the continuous prompts for authorization information and complex operations not only affect the user's operating experience of the application, but also easily wear out the user's patience, causing the user to arbitrarily handle the permission window and grant the application too many permissions, which indirectly leads to the user's privacy leakage. In addition, for users who do not understand the relevant information about application authorization, it is often difficult to decide whether to grant the application the corresponding permissions, which wastes too much time in authorizing the application, resulting in the user's inability to use the application normally.
[0045] The embodiment of the present application provides a permission management method, which can display a centralized permission window when the application is opened for the first time. The centralized authorization window is used to indicate the permissions requested by the application, and the centralized permission window contains multiple permission items. The multiple permission items can be divided into two categories: one category of permission items indicates the permissions that the electronic device recommends the user to grant to the application, and the other category of permission items indicates the permissions that the electronic device does not recommend the user to grant to the application. Among them, the permission items that the electronic device recommends the user to grant permissions are the minimum permission items specified to ensure the normal operation of the application. Afterwards, after the electronic device completes the configuration of the application permissions, the running interface of the application can be displayed for the user to use the functions of the application.
[0046] It can be seen that the authorization recommendation method can avoid the user's multiple processing of permissions by displaying multiple permissions in a centralized permission window when the user opens the application for the first time, simplifying the user's operation and improving the user experience. In addition, the centralized permission window distinguishes which permissions are recommended and not recommended to grant, provides a reference for users to grant permissions, guides users to grant the least permissions to the application, and helps users quickly complete the authorization of the application. In addition, the minimum permission item determined by the electronic device is the minimum permission that the application is allowed to use, and can also refer to the minimum permission granted to the application to meet the application operation requirements. This can minimize the risk of user privacy information leakage while ensuring the operation of the application.
[0047] The permission item indicates the permission that the application requests to obtain. The permission describes the application's right to access the resources of the electronic device. Granting the application permission can refer to granting the application the right to access the resources of the electronic device. Among them, the resources of the electronic device include hardware resources and software resources. Hardware resources include sensors, detectors, memory, microphones, speakers, etc. on the electronic device. Software resources include storage space, location information, applications (for example, address book, text messages, calendar, phone, gallery, camera), floating windows, etc. Take the navigation application as an example. When using the navigation function of the navigation application, the navigation application needs to obtain the location information of the electronic device in order to obtain the surrounding road conditions of the user's location based on the user's location, provide the user with a navigation route, and help the user reach the destination. That is to say, the navigation application needs the electronic device to grant it permission to obtain location information in order to operate the navigation function it provides normally.
[0048] The electronic device may indicate whether the permission is recommended in one or more of the following ways:
[0049] 1. Configure different selection states for permission items
[0050] Since the permission item can receive the user's operation and change the selection state of the permission item, the selection state can include a selected state and an unselected state. The electronic device can configure a default selection state for each permission item when displaying the centralized authorization window. Among them, the permission items recommended by the electronic device can be in a selected state, and the permission items that are not recommended can be in an unselected state. Specifically, the electronic device can display the selection state of the permission item through switches, font colors, font sizes, font thicknesses, and the like. In this way, the user can determine whether the electronic device recommends the permission item through the different display methods of the permission item, and the user does not need to configure the permission again. The user can directly click Confirm on the default configuration of the electronic device to complete the configuration of the application permission, thereby reducing the user's operation.
[0051] 2. Add additional prompt information to one of the permission items
[0052] For example, the electronic device can add text information such as "recommended" or "priority" after the recommended permission item. In this way, the electronic device can know from the prompt text in the permission item that the permission indicated by the permission item is the permission recommended by the electronic device for the user to grant to the application.
[0053] 3. Display statistics on permission items
[0054] The electronic device can determine whether the permission item is recommended or not by comparing the amount of statistical data or other statistical data. For example, there is a permission item corresponding to the location information, and the location information can show the proportion of other users who have granted the permission to the application or similar applications, such as 80%. Through this score, the user can know that 80% of people have chosen to agree to grant the permission, thereby indirectly knowing that the permission item is a permission item recommended for authorization by the electronic device.
[0055] It is understandable that the electronic device can also indicate whether the permission is recommended in other ways, such as changing the order of permissions, and arranging the permission items recommended by the electronic device above the permission items not recommended by the electronic device. For specific information about the expression of the permissions recommended and not recommended by the electronic device, please refer to the subsequent content, which will not be repeated here.
[0056] Figure 2 A schematic diagram of the hardware structure of the electronic device 100 provided in an embodiment of the present application is shown.
[0057] The electronic device 100 may be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device and / or a smart city device, etc. The embodiments of the present application do not impose any special restrictions on the specific type of the electronic device.
[0058] 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, etc. Among them, the sensor module 106 may include a gyroscope sensor 106A, an air pressure sensor 106B, a touch sensor 106C, etc. Among them, the wireless communication module 103 may include a WLAN communication module, a Bluetooth communication module, etc., and the audio module 107 includes a speaker 107A, a receiver 107B, a microphone 107C, and an earphone interface 107D. The above multiple parts can transmit data through a bus.
[0059] In some embodiments, the processor 101 may be used to determine whether the permission requested by the application is a permission recommended for the user to grant, and grant the application the corresponding permission according to the user's configuration of the permission, or refuse to grant the application the corresponding permission.
[0060] In some embodiments, the memory 102 is used to store the permission configuration table sent by the server, which records one or more applications, the minimum permissions specified, and the permissions recommended for users to grant and the permissions not recommended for users to grant. For a specific description of the permission configuration table, please refer to the subsequent embodiments, which will not be repeated here.
[0061] The electronic device 100 can realize the display function through a GPU, a display screen 109, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 109 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 101 may include one or more GPUs, which execute program instructions to generate or change display information.
[0062] The display screen 109 is used to display images, videos, etc. 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 (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 109, where N is a positive integer greater than 1.
[0063] In some embodiments, the display screen 109 can be used to display an authorization window when configuring application permissions. The authorization window is used to display one or more permissions that the application requests the user to grant, as well as the permissions that the electronic device 100 recommends and does not recommend the user to grant.
[0064] For some sensitive permissions (such as location, shooting, or recording permissions), it is recommended to authorize only once, such as selecting the option to allow only once by default.
[0065] It is to be understood that the structure illustrated in the embodiment of the present application does 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 fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
[0066] 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., and may also be a non-portable terminal device such as a laptop computer with a touch-sensitive surface or a touch panel, a desktop computer with a touch-sensitive surface or a touch panel. The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present invention takes the Android system of the layered architecture as an example to exemplify the software structure of the electronic device 100.
[0067] Figure 3 It is a software structure block diagram of the electronic device 100 according to an embodiment of the present application.
[0068] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.
[0069] The application layer can include a series of application packages.
[0070] like Figure 3 As shown, the application package may include applications such as camera, gallery, calendar, phone, address book, navigation, WLAN, music, settings, and text messages.
[0071] In some embodiments, during the running of an application, the application may need to access other applications to obtain resources required for its own functions, such as accessing pictures in a gallery. At this time, the electronic device 100 may display an authorization window, prompting the user to request permission to grant the application access to other applications. The other applications may refer to the camera, gallery, calendar, and other applications mentioned above.
[0072] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.
[0073] like Figure 3 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.
[0074] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.
[0075] The content provider is used to store and obtain data and make the data accessible to the application. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc. Before the application accesses the data, the electronic device 100 may first display an authorization window to prompt the user to request permission for the application to access the data.
[0076] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.
[0077] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including connecting, hanging up, etc.).
[0078] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.
[0079] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.
[0080] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.
[0081] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.
[0082] The application layer and the application framework layer run in a virtual machine. 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 life cycle management, stack management, thread management, security and exception management, and garbage collection.
[0083] The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.
[0084] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.
[0085] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
[0086] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.
[0087] A 2D graphics engine is a drawing engine for 2D drawings.
[0088] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.
[0089] Combine the following Figure 4A-4B , Figure 5A-Figure 5B , Figure 6A-6B Introduce some user interfaces involved in the permission management method.
[0090] exist Figure 4A-4B , Figure 5A-Figure 5B , Figure 6A-6B In the user interface shown, 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. In other embodiments of the present application, the electronic device can run other applications, and the embodiments of the present application do not limit the applications run by the electronic device.
[0091] Figure 4A-4B It shows the user interface involved when the electronic device 100 opens an application for the first time and the electronic device 100 displays a centralized authority window.
[0092] Figure 4A An exemplary user interface 21 for an application menu on the electronic device 100 is exemplarily shown.
[0093] like Figure 4A As shown, the user interface 21 may include: a status bar 211, a calendar indicator 212, a weather indicator 213, a setting icon 214, and a browser icon 215. Among them:
[0094] The status bar 211 may include one or more signal strength indicators of mobile communication signals, one or more signal strength indicators of wireless fidelity (WiFi) signals, a battery status indicator, and a time indicator. A calendar indicator 212 may be used to indicate the current time. A weather indicator 213 may be used to indicate the weather type.
[0095] like Figure 4A As shown, 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 Figure 4B The user interface 31 is shown. 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.
[0096] like Figure 4B As shown, the user interface 31 is a user interface provided by the browser, which may be a main page provided by the browser, or a startup page displayed when the browser is first opened. Figure 4B In the example, the user interface 31 is a main page provided by the browser.
[0097] In addition, the user interface 31 also includes a centralized permission window 311. The centralized permission window 311 is used to centrally display the permissions requested when the browser is first started. Among them, the centralized permission window 311 includes a first permission item 311A, a second permission item 311B, and a third permission item 311C, which respectively indicate that the permissions requested by the browser are: storage, device information, and location information. The permission items also include authorization switches, such as the first switch 3111A in the first permission item 311A, the second switch 3111B in the second permission item 311B, and the third switch 3111C in the third permission item 311C, where the "prohibit" option is in the on state. In other words, the centralized permission window 311 also displays the default configuration of the electronic device 100 for permissions. At the same time, the first switch 3111A-the third switch 3111C can change the on or off state of the switch in response to the user's operation. In this way, the user can modify the configuration of the permissions again under the premise that the default configuration already exists in the centralized permission window 311.
[0098] from Figure 4BIt can be seen from the centralized permission window 311 shown in the figure that the permission item corresponding to "storage" is in a state of granting permission by default, the permission item corresponding to "device information" is in a state of not granting permission by default, and the permission item corresponding to "location information" is in a state of not granting permission by default. Cancel option 311D can be used to exit the setting of the centralized permission window 311 and cancel the permission granted to the application. Confirm option 311E can be used to confirm the setting of the centralized permission window 311 and grant the corresponding permission to the application according to the permission configured in the centralized permission window 311. For example, when the electronic device detects that the function is similar to that of Figure 4B When the touch operation of the confirmation option 311E is performed, the electronic device 100 grants the browser permission to access the storage space of the electronic device 100 according to the permission configuration in the centralized permission window 311, and refuses to grant permission to access the device information and location information of the electronic device 100.
[0099] from Figure 4A-4B It can be seen that when the electronic device 100 opens an application for the first time, the electronic device 100 can display a centralized permission window, which can include the first or multiple permissions requested by the application before running, and the electronic device 100 can set a default configuration for the permissions in the centralized permission window, which can include whether to enable the permission, or further, include the authorization method of the permission, which indicates the length of time the electronic device grants the permission to the application. For example, the authorization method can refer to: always allow, allow when using this application, prohibit, etc., wherein always allow means that after the electronic device grants the application permission, the application always has the permission, allow when using this application means that after the electronic device grants the application permission, the application is allowed to use the permission during operation, and prohibit means that the electronic device refuses to grant the permission to the application.
[0100] It is understandable that the electronic device 100 can Figure 4B The default switch state shown in the figure indicates whether the permission item is recommended, or the electronic device 100 may indicate whether the permission item is recommended in other ways. For example, the electronic device 100 may add text prompts such as "recommended" or "priority" to the recommended permission item to prompt the user that the permission item is recommended by the electronic device 100, or display the proportion of other users agreeing to authorize or refusing to authorize in the permission item. For details about the way in which the electronic device 100 recommends permission items, please refer to the subsequent embodiments, which will not be described here.
[0101] Figure 5A-Figure 5B The following example illustrates some user interfaces involved when requesting permissions during the running of an application.
[0102] Figure 5AThe diagram exemplarily shows a search interface, namely, a user interface 31, provided by a browser when the electronic device 100 is running the browser in the foreground.
[0103] Among them, the user interface 31 includes a search box 312 and a browsing area 313. The browsing area 313 can be used to display news or consultation information provided by the browser, and the search box 312 is used to provide a user search entry. The search box 312 includes a voice control 312A, and the voice control 312A can be used to enable the voice search function of the browser. When the electronic device 100 receives an operation by the user on the voice control 312A, the browser turns on the voice search function. The browser needs to obtain the voice input by the user through the microphone, and recognize the search keyword output by the user based on the voice, so as to implement the search based on the search keyword. At this time, since the browser does not have permission to access the microphone, the electronic device 100 can display the following in the user interface 31. Figure 5B Permissions window 314 is shown.
[0104] like Figure 5B As shown, the permission window 314 is used to prompt the user whether to allow the "browser" to access the microphone of the electronic device 100. In addition, the permission window 314 may include multiple options for the electronic device 100 to grant different permission durations to the application. Specifically, the multiple options may include: "Always allow" option, "Allow while using this application" option, "Prohibit" option, etc. Among them, the "Always allow" option means that after the application permission is granted, the application always has the permission regardless of whether the user uses the application. The "Allow while using this application" option means that after the application permission is granted, the application only has the permission when the user uses the application. The "Prohibit" option means refusing to grant the application permission. In other words, the "Always allow" option, the "Allow while using this application" option, and the "Prohibit" option gradually reduce the duration of the permission granted to the application. In addition, the permission window 314 also shows the default permission settings of the electronic device 100. The electronic device 100 can indicate the options recommended by the electronic device 100 by highlighting the options, such as Figure 5B It can be seen that the target option 314A is the option recommended by the electronic device 100 .
[0105] That is to say, when the electronic device 100 is running the application in the foreground, the electronic device 100 can still display the authorization box to prompt whether to allow the application to obtain permissions. Here, the permissions requested by the application are different from the permissions requested by the application when the application is opened. The permissions requested during the application operation can be permissions required for a specific function of the application, and the permissions requested when the application is started can be permissions requested for basic functions of the application, and the permissions recommended by the electronic device 100 when the application is started are the minimum permissions provided to ensure the basic operation of the application. In this way, the electronic device 100 can reduce the risk of user privacy leakage as much as possible while ensuring the basic operation of the application. At the same time, the authorization window displayed during the application operation can still indicate the authorization options recommended by the electronic device 100. In this way, users can make the most appropriate choice faster.
[0106] Figure 6A-6B The diagram exemplifies some user interfaces involved when an application requests location information and the electronic device 100 provides a precise location or a fuzzy location.
[0107] Fig. 6A The user interface 31 displayed by the electronic device 100 when the browser is opened for the first time is shown.
[0108] The user interface 31 includes a centralized authority window 315, which is similar to Figure 4B The centralized permission window 311 in the browser is used to centrally display the permissions requested by the browser when it is first started. The difference is that when the centralized permission window 315 contains location information, the centralized permission window 315 can also include a location mode option 315A. The location mode option 315A is used to determine the mode in which the application obtains location information. The modes include: precise location and mode location. The precise location is used to provide the application with the correct and accurate geographic location of the electronic device 100, and the fuzzy location is used to provide the application with a rough and incorrect geographic location. In addition, the location mode option 315A includes a switch 3151A, and the switch 3151A is used to control the selection of the location mode. Specifically, when the switch 3151A is in the off state, the mode in which the browser obtains location information is the fuzzy location, and when the switch 3151A is in the on state, the mode in which the browser obtains location information is the precise location. Similarly, similar to Figure 4BIn the centralized permission window 311, there may also be a default configuration in the centralized permission window 315, which refers to the minimum permissions pre-set by the electronic device 100 in the centralized permission window 315. Among them, whether the switch 3151A is in the on state can also be determined according to the function of the application. For example, when the browser can recommend nearby news to the user by obtaining the location information of the electronic device 100, the news recommendation function of the browser is realized. However, although the browser can recommend nearby news to the electronic device 100 based on the location information of the electronic device 100, the browser can also realize the news recommendation function without the precise location. Therefore, here, the switch 3151A can be in the off state by default.
[0109] Figure 6B It shows the permission window 316 displayed in the user interface 31 when the browser requests to obtain location information during operation.
[0110] The permission window 316 is used to prompt the user whether to allow the "browser" to obtain the location information of the electronic device 100. The permission window 316 includes an accurate location option 316A, a fuzzy location option 316B, a first optional option 316C, a target option 316D, and a second optional option 316E. The accurate location option 316A is used to allow the application to obtain accurate location information, the fuzzy location option 316B is used to allow the application to obtain fuzzy location information, the first optional option 316C, the target option 316D, and the second optional option 316E are three options corresponding to different permission durations granted by the electronic device 100 to the application. For a detailed description of these three options, please refer to Figure 5B . In addition, the authorization method indicated by the target option 316D is the authorization method of the electronic device 100 for the location information recommended by the browser. Compared with the first optional option 316C and the second optional option 316E, the target option 316D is in a selected state. Here, the option can be highlighted, that is, the background color is changed to distinguish whether the option is selected. When the background color of the option is darker, the option is in a selected state, and when the background color of the option is lighter, the option is in a non-selected state. Furthermore, the fuzzy position 316B is in a selected state, and the precise position option 316A is in an unselected state. Whether the precise position option 316A and the fuzzy position option 316B are in a selected state can be reflected by whether the border is bold. When the option border is bold, the option is in a selected state, and when the option border is not bold, the option is in an unselected state.
[0111] In addition, the electronic device 100 can also receive user operations (such as click operations) on the precise location option 316A, the fuzzy location option 316B, the first optional option 316C, the target option 316D, and the second optional option 316E to modify the default configuration recommended by the electronic device 100.
[0112] It can be seen that when the application is started for the first time, or during the operation of the application, when the application requests permission to obtain location information, the electronic device 100 can display the location mode option in the permission window to further subdivide the accuracy and / or precision of the location information obtained by the application. In addition, the electronic device 100 can also have a default configuration, that is, indicating in the permission window whether the electronic device 100 recommends that the application obtain the precise location or the analog location, providing a reference for the user's permission configuration for location information, reducing the user's operations, and minimizing privacy leakage as much as possible without affecting the operation of the application.
[0113] Figure 7 The flowchart of the permission management method provided in the embodiment of the present application is exemplified.
[0114] like Figure 7 As shown, the method includes:
[0115] S101. The electronic device 100 obtains a permission configuration table from a server.
[0116] The permission configuration table is used to determine the recommended permissions for the application, that is, the electronic device 100 prompts the user to grant permissions when the application is first opened or during operation, and the permissions that the electronic device 100 recommends the user to grant to the application and the permissions that it does not recommend the user to grant to the application.
[0117] Permissions describe the access rights of an application to the resources of the electronic device 100. Granting permissions to an application may refer to granting the application the right to access the resources of the electronic device 100. The description of the resources of the electronic device 100 can be found in the above content, which will not be repeated here.
[0118] The permission configuration table can be generated in the following ways:
[0119] 1) The permission configuration table can be obtained by the server based on the statistics of the user's permission configuration of the application or similar applications of the application.
[0120] The permission configuration describes whether the user grants permission when authorizing the application or similar applications of the application. Specifically, for a permission, when the proportion of users agreeing to authorize is greater than a first threshold, the server can determine the permission as a permission recommended for users to grant to the application. On the contrary, when the proportion of users refusing to authorize is greater than the first threshold, the server can determine the permission as a permission not recommended for users to grant to the application.
[0121] The user may refer to a user who uses the application on the electronic device 100, and in this case, the permission configuration table may reflect the user's habit of configuring permissions. The user may refer to multiple users who use the application, and in this case, the permission configuration table may reflect the habit of most users in configuring permissions.
[0122] 2) The permission configuration table can be obtained by the server through testing the installation package of the application.
[0123] Specifically, the server can obtain the installation package of the application from the application market, and install the application and run the application on the server to determine the permissions requested by the application when it is started and during operation. When configuring different authorization methods for the application, the server can analyze the privacy leakage risk of the application to determine which permissions are recommended for users to grant to the application and which permissions are not recommended for users to grant to the application.
[0124] When testing the application, the server obtains the permission window displayed when the application is first started. For example, when the application displays three permission windows in succession, and these three permission windows respectively request the user to grant permission to use storage, location information, and device information, the server can instruct the electronic device 100 to display these three permissions in a centralized permission window.
[0125] The following shows the codes involved when the electronic device 100 displays the three permissions in a centralized permission window:
[0126] <package packageName=”ctrip.android.view”>
[0127] <permissioncfg> 0< / permissioncfg>
[0128] <permissioncode> 280< / permissioncode>
[0129]
[0130] 3) The permission configuration table may be a configuration table determined according to permission configuration rules.
[0131] For example, the permission configuration rule may be the relevant specifications formulated by the Ministry of Industry and Information Technology for application authorization, or the permission configuration rule may be the principle of minimizing personal data in the General Data Protection Regulation (GDPR).
[0132] It is understandable that the permission configuration table can be generated by combining one or more of the above-mentioned methods, wherein the permission configuration table needs to at least meet the permission configuration rules in method 3. The generation method of the permission configuration table is not limited to the three methods mentioned above, and the embodiment of the present application does not limit this.
[0133] The following describes the permission configuration table using a specific example. Table 1 exemplarily shows a permission configuration table for an application.
[0134] Table 1
[0135] Permissions Recommended method First recommendation storage Always allow Y Device Information prohibit Y Location Information Allow (blur location) when using this app Y camera You are allowed to use this app N microphone You are allowed to use this app N Contacts prohibit N calendar prohibit N
[0136] As can be seen from Table 1, the permission configuration table may include three items: permission, recommendation method, and first recommendation. Permissions include permissions requested by the application. Recommendation methods include authorization methods such as always allowing, allowing when using this application, and prohibiting, which grant permissions of different lengths to the application. The first recommendation is used to determine whether to request permissions from the user when the application is first opened. Among them, "Y" indicates first recommendation, and "N" indicates non-first recommendation. Permissions not recommended for the first time refer to permissions required by the application when the application function is triggered during the operation of the application.
[0137] According to Table 1, when the application is run for the first time, the electronic device 100 can display the authorization window about "storage", "device information" and "location information", and "storage" is the permission that the electronic device 100 recommends the user to grant to the application, and "device information" and "location information" are the permissions that the electronic device 100 does not recommend the user to grant to the application. At this time, the permission window displayed by the electronic device 100 can be as follows: Fig. 6A Centralized permissions window 315 is shown.
[0138] It is understandable that the content of the permission configuration table is not limited to the above-mentioned three items of permission, recommendation method, and first recommendation. In other embodiments of the present application, the permission configuration table may also include more or less content. The present application embodiment does not limit the content of the permission configuration table.
[0139] In some embodiments, the permission configuration table may also include a user ratio, which is used to indicate the ratio of granting or denying permissions by multiple users when configuring permissions. In this way, the permission ratio can be displayed in the permission window displayed on the electronic device 100 as reference data for user configuration of permissions, helping users to complete the permission configuration more quickly.
[0140] In some other embodiments, the permission configuration table may also include permission classifications of permissions, and the permission classifications include: minimum necessary permissions and reasonable additional permissions. The minimum necessary permissions are the minimum permissions determined to ensure the operation of the application, and the reasonable additional permissions are the permissions required for the application's functions in addition to the minimum necessary permissions. Among them, the minimum necessary permissions will appear in the permission window displayed when the application is first opened, and the minimum necessary permissions are the permissions recommended for users to grant to the application. The reasonable additional permissions are the permissions requested in the permission window displayed when the application starts a function during the operation of the application and the function requires permissions. The permissions can be permissions granted to recommended users or permissions granted to non-recommended users. For example, in combination with the permissions in Table 1 above, it can be seen that storage and location information can be the minimum necessary permissions, and other permissions can be reasonable additional permissions.
[0141] The timings for the electronic device 100 to obtain the permission configuration table may include the following situations:
[0142] 1) Electronic device 100 periodically obtains permission configuration table
[0143] For example, the electronic device 100 may obtain the permission configuration table every 7 days. In this way, the electronic device 100 may periodically update the permission configuration table.
[0144] 2) The electronic device 100 triggers the acquisition of the permission configuration table when installing the application
[0145] That is to say, the electronic device 100 can obtain the permission configuration table when receiving the user's operation to install the application. In this way, after the user installs the application, the electronic device 100 can determine the permissions recommended and not recommended by the electronic device 100 in the application based on the permission configuration table.
[0146] In addition, the electronic device 100 installing an application may refer to the electronic device 100 installing the application for the first time, or may refer to the electronic device 100 updating the application.
[0147] 3) The electronic device 100 obtains the permission configuration table in response to the user operation
[0148] That is, the electronic device 100 can obtain the permission configuration table upon receiving a user operation for obtaining the permission configuration table.
[0149] It is understandable that the timing for the electronic device 100 to obtain the permission configuration table may also include other situations, and the embodiment of the present application does not limit this.
[0150] Furthermore, the permission configuration table can be used to determine the permission recommendations of multiple applications. In this case, the permission configuration table can include the permissions requested by multiple applications. In this way, the electronic device 100 can determine the permission recommendations of multiple applications after receiving the permission configuration table, thereby reducing the frequency of the electronic device 100 obtaining the permission configuration table.
[0151] S102: The electronic device 100 starts an application when the application is not running.
[0152] Launching an application on the electronic device 100 means that the electronic device 100 launches the application for the first time, and before launching the application, the application is not in the foreground running state or the background running state.
[0153] There are several situations in which an application can be started:
[0154] 1) The electronic device 100 opens the application for the first time after the application is installed
[0155] 2) When the application does not occupy data in the storage space of the electronic device 100, the electronic device 100 opens the application for the first time
[0156] It is understandable that the activation of an application is not limited to the above two methods. The activation of an application may also refer to the first activation after the electronic device 100 is turned on. This embodiment of the present application does not limit this.
[0157] The ways to start the application include but are not limited to the following three:
[0158] 1) User-initiated: The application can be triggered to start in response to user operations.
[0159] 2) Associated startup: the application can be triggered to start while running other applications.
[0160] 3) Self-start: The application can be automatically triggered to start when the preset conditions (such as a specific time) are met.
[0161] See also Figure 4A , the electronic device 100 can trigger the opening of the browser application after receiving a user operation acting on the browser icon 215 .
[0162] S103. In response to the opening of the application, the electronic device 100 displays a centralized authority window.
[0163] The centralized permission window indicates the permissions requested by the application, and the centralized permission window includes a first permission item and a second permission item. The first permission item indicates the permissions that the electronic device 100 recommends the user to grant to the application, and the second permission item indicates the permissions that the electronic device 100 does not recommend the user to grant to the application, and the first permission item is the minimum permission that the application is specified to use.
[0164] The minimum permissions describe the minimum permissions that the application is allowed to use, or, further, describe the minimum time that the application is allowed to use permissions. The time that the application uses permissions can be represented by the authorization method of the permissions, and the authorization methods may include: always allowed, allowed during use, prohibited, etc., where always allowed indicates that the application uses permissions for the least time, allowed during use is second, and prohibited indicates that the application uses permissions for zero time. In other words, in addition to displaying the permissions recommended and not recommended for granting by the electronic device 100, the centralized permissions window can also display the authorization method recommended by the electronic device 100. In this way, a more detailed authorization reference can be provided to the user, helping the user to authorize more reasonably.
[0165] The electronic device 100 may indicate whether to recommend a permission in one or more of the following ways:
[0166] 1) Configure different selection states for permission items
[0167] Since the permission item can receive the user's operation and change the selection state of the permission item, which can include a selected state and an unselected state, the electronic device can configure a default selection state for each permission item when displaying the centralized authorization window. In this way, when the electronic device 100 displays the centralized permission window, the user can directly click Confirm to authorize the application according to the selection states of different permissions in the centralized permission window.
[0168] Among them, the permission items recommended by the electronic device can be in a selected state, and the permission items not recommended can be in an unselected state. Specifically, the electronic device can display the selection state of the permission item through a switch, font color, font size, font thickness, etc. In this way, the user can determine whether the electronic device recommends the permission item through different display methods of the permission item, and the user does not need to configure the permission again, and can directly click on the default permission of the electronic device to complete the configuration of the application permission, thereby reducing the user's operation.
[0169] See also Figure 4B , the centralized authority window can refer to Figure 4BIn the centralized permission window 311 shown in FIG, it can be seen from the first switch 3111A in the first permission item 311A being turned on that the permission indicated by the first permission item 311A (i.e., storage) is the permission recommended by the electronic device 100 for the user to grant to the application, and it can be seen from the second switch 3111B in the second permission item 311B being turned off, and the third switch 3111C in the third permission item 311C being turned off that the permission indicated by the second permission item 311B (i.e., device information) and the permission indicated by the third permission item 311C (i.e., location information) are the permissions that the electronic device 100 does not recommend the user to grant to the application.
[0170] 2) Add additional prompt information to one of the permission items
[0171] For example, the electronic device can add text information such as "recommended" or "priority" after the recommended permission item. In this way, the electronic device can know from the prompt text in the permission item that the permission indicated by the permission item is the permission recommended by the electronic device for the user to grant to the application.
[0172] 3) Display statistics on permission items
[0173] The electronic device can determine whether the permission item is recommended or not by comparing the amount of statistical data or other statistical data. For example, there is a permission item corresponding to the location information, and the location information can show that other users have granted the permission to the application, for example, 80%. Through this score, the user can know that 80% of people have chosen to agree to grant the permission, thereby indirectly knowing that the permission item is a permission item recommended for authorization by the electronic device.
[0174] It is understandable that the electronic device can also express whether permissions are recommended in other ways, such as changing the order of permissions, and arranging the permission items recommended by the electronic device above the permission items not recommended by the electronic device. The embodiment of the present application does not limit the way in which the electronic device 100 expresses whether permissions are recommended.
[0175] S104. The electronic device 100 completes authorization of the application according to the centralized authority window.
[0176] The triggering methods for the electronic device 100 to complete the authorization of the application may include the following two methods:
[0177] 1) The electronic device completes authorization of the application according to the user's operation on the centralized permission window.
[0178] This operation can have the following three meanings:
[0179] a) This operation may refer to the user's confirmation operation on the centralized authority window
[0180] The confirmation operation may be a Figure 4B Determine the operation of option 311E.
[0181] That is, in the centralized permission window, the permission recommended by the electronic device 100 is already selected, and the permission not recommended by the electronic device 100 is not selected. After the electronic device 100 receives the confirmation operation, it authorizes the application according to the permission configured by default by the electronic device 100, that is, grants the permission recommended by the electronic device 100 (for example, the permission indicated by the first permission item 311A) to the application. In this way, when the electronic device 100 displays the centralized permission window, the user can directly authorize the application according to the permission configured by the electronic device 100, reducing the user's operations and speeding up the user's access to the application.
[0182] b) The operation may include the user's modification operation on the centralized authority window, as well as the confirmation operation
[0183] The modification operation refers to the operation of modifying the permission configuration in the centralized permission window.
[0184] That is, in the centralized permission window, the permissions recommended by the electronic device 100 are already selected, and the permissions not recommended by the electronic device 100 are not selected. However, the centralized permission window can still accept the user's operation to modify the default configuration of the electronic device 100, and after the modification is completed, receive the user's confirmation operation and authorize the application according to the modified permission configuration. In this way, the user's operability can be enhanced.
[0185] c) The operation may include the user's configuration operation on the centralized authority window, as well as the confirmation operation
[0186] The configuration operation refers to the operation of configuring the permissions in the centralized permission window.
[0187] That is to say, in the centralized permission window, whether it is the permission recommended by the electronic device 100 or the permission not recommended, it is in an unselected state, and the user needs to configure the permission independently. The electronic device 100 can mark the permission recommended by the electronic device 100 and the permission not recommended through the indication information in the permission item. The electronic device 100 also needs to receive the user's confirmation operation after the user configuration is completed before it can authorize the application according to the permission configured by the user. In this way, the user can refer to the permission recommended by the electronic device 100 and the permission not recommended to configure the permission in the centralized permission window.
[0188] 2) The electronic device 100 automatically completes the authorization of the application after the timer ends.
[0189] That is, when the electronic device 100 displays the centralized permission window, it can display a countdown prompt in the centralized permission window, and the countdown prompt is used to prompt the user to complete the authorization of the application within the time limit. If the electronic device 100 detects the user's operation on the centralized permission window during the process of displaying the centralized permission window, the authorization of the application is automatically completed, and the permission indicated by the first permission item is granted to the application.
[0190] In this way, by displaying the countdown prompt information, users can complete the application authorization more quickly, avoiding wasting too much time when users hesitate to configure permissions for the application.
[0191] In some embodiments, when the centralized permission window indicates that the permission requested by the application includes location information, the centralized permission window may include a location mode option, which is used to trigger the application to obtain the precise geographic location of the electronic device.
[0192] It should be noted that only when the location information recommends that the user grant permission to the application for the electronic device 100, can the location mode option receive the user's operation to determine whether the application obtains the precise geographic location or the vague geographic location of the electronic device 100. Then, at this time, the location information is a permission indicated by the first permission item. In addition, the first permission item also includes indication information, which is used to indicate whether the electronic device 100 recommends that the application obtain the precise geographic location of the electronic device 100. In this way, the user can refer to the permission recommendation of the electronic device 100 and decide whether to grant the application precise location information or vague location information, thereby avoiding the leakage of user location information as much as possible and ensuring the privacy and security of the user.
[0193] S105. During the running of the application, the electronic device 100 detects an operation of starting the first function of the application.
[0194] After completing the authorization of the application through the centralized permission window, the electronic device 100 can run the application normally.
[0195] The first function is a function possessed by the application, for example, a camera function of a camera application, a navigation function of a navigation application, and the like.
[0196] See also Figure 5A , which can refer to Figure 5A The operation acting on the voice control 312A, at this time, the first function may refer to the voice detection function of the browser.
[0197] S106. The electronic device 100 displays a function permission window, in which the third permission item is displayed.
[0198] When the first function requires permission to be enabled, the electronic device 100 may display a function permission window to request the user to grant the permission required for the first function. The third permission item may include information indicating whether the electronic device 100 recommends that the user grant the application the permission required for the first function. The permission required for the first function is not the permission indicated by the first permission item, but may be the permission indicated by the second permission item or other permissions.
[0199] See also Figure 5B , the function permissions window can refer to Figure 5B In the permission window 314, the permission indicated by the third permission item is the permission indicated in the permission window 314, and the indication information can be the prompt information with the background of the target option 314A highlighted.
[0200] Here, the manner of expressing whether the electronic device 100 recommends permissions can refer to the relevant content of S103, which will not be repeated here.
[0201] S107. The electronic device 100 completes authorization of the application according to the function permission window.
[0202] The electronic device 100 completing the authorization of the application according to the function permission window may mean that the electronic device 100 grants the application the permission required for the first function, or refuses to grant the application the permission required for the first function.
[0203] Here, the triggering manner for the electronic device 100 to complete the authorization of the application may include two types:
[0204] 1) The electronic device 100 detects the operation on the function authorization window and completes the authorization of the application
[0205] 2) After the countdown ends, the electronic device 100 completes the authorization of the application
[0206] For details about the manner in which the electronic device 100 completes the authorization of the application, please refer to the relevant content in S104, which will not be repeated here.
[0207] In some embodiments, when the permission required for the first function is location information, the function permission window may also include a precise location option (e.g., Fig. 6A The precise location option 316A shown) and the fuzzy location option (e.g., Figure 6B The fuzzy location option 316B shown in the figure can be used to provide the application with the precise geographic location of the electronic device 100, and the fuzzy location option can be used to provide the application with the fuzzy geographic location of the electronic device 100. The location accuracy of the fuzzy geographic location can be lower than the location accuracy of the precise geographic location, and / or the fuzzy geographic location deviates from the precise geographic location.
[0208] It should be noted that only when the electronic device 100 recommends the user to grant the application location information, the precise location option and the fuzzy location option can receive the user's operation to select the precise geographic location or the fuzzy geographic location for the application. In addition, the third permission item also includes the second indication information (for example, Fig. 6A The second indication information is used to indicate whether the location option recommended by the electronic device 100 is a precise location option or a fuzzy location option. In this way, when the user grants the application permission to access location information, the user can further determine whether the application accesses precise location information or fuzzy location information, thereby minimizing the leakage of the user's real and precise location information.
[0209] In some embodiments, the electronic device 100 can also determine the recommended user permissions to grant to the application and the recommended user permissions to grant to the application in combination with the user portrait. The user portrait refers to a label that can represent the real user extracted based on the user's information. For example, if the user portrait indicates that the user is a photography expert, when the electronic device 100 displays the permission window, even if it is concluded according to the permission configuration table that the electronic device 100 should not recommend the user to grant the application permission to access the photo album, then the electronic device 100 can indicate in the permission window that it is recommended that the user grant the application permission to access the photo album. In this way, a more personalized permission management can be provided to users, helping users to complete the authorization of applications more reasonably.
[0210] In general, using the permission management method provided in the embodiment of the present application, the permission windows displayed by different applications may contain different permissions, and the permissions recommended or not recommended by the electronic device 100 may not be the same, because different applications have different functions and the specified minimum permissions are also different. The permission windows displayed by the same application at different times may also contain different permissions, and the permissions recommended or not recommended by the electronic device 100 may not be the same, because the same application may contain different functions after being updated, or, when combined with the analysis of the authorization of multiple users to the application, the ratio of authorization and refusal of authorization by multiple users to the application may change, then at this time, the permission windows displayed by the same application at different times may also be different. The permissions recommended or not recommended in the permission windows displayed by different users of the same application may not be the same, because the electronic device 100 can customize personalized permission management solutions for different users more reasonably in combination with user portraits to enhance the user experience.
[0211] The various implementation modes of the present application can be combined arbitrarily to achieve different technical effects.
[0212] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using 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. When the computer program instructions are loaded and executed on a computer, the process or function described in the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)), etc.
[0213] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.
[0214] In short, the above description is only an embodiment of the technical solution of the present invention, and is 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 in the protection scope of the present invention.
Claims
1. A rights management method, characterized in that: The method comprises: In response to a first operation input by a user, the electronic device displays a first user interface of the first application; the first user interface includes a first window, and the first window includes a first permission item of the first application, a second permission item of the first application, a first authorization method of the first permission item, a second authorization method of the second permission item, and a first option; When accepting the user's second operation on the first option, the first permission item is authorized in the first authorization method, and the second permission item is authorized in the second authorization method.
2. The method according to claim 1, characterized in that The first authorization method indicates a recommended authority, and the second authorization method is different from the first authorization method.
3. The method according to claim 1, characterized in that When the user's operation of modifying and confirming the first permission item in the first window is accepted, the first permission item is authorized in the third authorization mode.
4. The method according to claim 1, characterized in that: The first user interface includes a first functional control; In response to a third operation of the user on the first function control, a second window is displayed, wherein the second window includes a third permission item.
5. The method according to claim 4, characterized in that Also includes: In response to a fourth operation of the user on the second window, the third permission item is authorized in a third authorization manner.
6. The method according to claim 5, characterized in that The second window includes a first permission option; The first permission option indicates the third authorization mode; The fourth operation performed by the user on the second window includes: an operation performed by the user on the first permission option.
7. The method according to claim 6, characterized in that The second window also includes a second permission option and a third permission option, the second permission option indicates a fourth authorization method, the third permission option indicates a fifth authorization method, and the fourth authorization method and the fifth authorization method are different from the third authorization method.
8. The method according to claim 4, characterized in that The first function can be started only after the third permission item is authorized.
9. The method according to claim 4, characterized in that The third authorization method is to always allow, any one of allowing or prohibiting when using this application.
10. The method according to claim 1, characterized in that The first authorization method and the second authorization method are always allowed, and are either allowed or prohibited when using this application.
11. The method according to claim 1, characterized in that: The first application is opened for the first time after the electronic device installs or updates the first application.
12. An electronic device comprising: A display screen, a memory, one or more processors, multiple applications, and one or more programs; wherein the one or more programs are stored in the memory; it is characterized in that when the one or more processors execute the one or more programs, the electronic device implements the method described in any one of claims 1 to 11.
13. A computer-readable storage medium, comprising instructions, wherein when the instructions are executed on an electronic device, the electronic device executes the method according to any one of claims 1 to 11.
Citation Information
Patent Citations
Permission management method for application, electronic device, and computer readable medium
CN103514386A
Application access permission setting method, system and device, and readable medium
CN108427886A
Application permission processing method, terminal and server
CN108537011A
Application program right prompting method and a terminal device thereof
CN109522741A
Permission setting method and terminal equipment
CN111125680A
