WO2021036811A1 - 应用权限显示方法、装置、移动终端及存储介质 - Google Patents

应用权限显示方法、装置、移动终端及存储介质 Download PDF

Info

Publication number
WO2021036811A1
WO2021036811A1 PCT/CN2020/109073 CN2020109073W WO2021036811A1 WO 2021036811 A1 WO2021036811 A1 WO 2021036811A1 CN 2020109073 W CN2020109073 W CN 2020109073W WO 2021036811 A1 WO2021036811 A1 WO 2021036811A1
Authority
WO
WIPO (PCT)
Prior art keywords
permission
application
target application
notification mode
target
Prior art date
Application number
PCT/CN2020/109073
Other languages
English (en)
French (fr)
Inventor
罗继超
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2021036811A1 publication Critical patent/WO2021036811A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices

Definitions

  • the present disclosure relates to the field of mobile communication technology, and in particular to a method, device, mobile terminal, and storage medium for displaying application permissions.
  • mobile terminals such as mobile phones, etc.
  • mobile phones such as mobile phones, etc.
  • the embodiments of the present disclosure provide an application permission display method, device, mobile terminal, and storage medium, so as to solve the situation in the prior art that only after the application permission is called, the user will know that the application permission is called, and when the user is calling It is unknown, leading to the problem of user privacy exposure.
  • embodiments of the present disclosure provide an application permission display method, including: receiving a call operation for the target application permission corresponding to the target application; When the permission notification mode corresponding to the application permission is the permitted notification mode, the target application, the target application permission, and the invocation information of the target application permission are displayed in a specified interface in association with each other.
  • an embodiment of the present disclosure provides an application permission display device, including: a call operation receiving module for receiving a call operation for the target application permission corresponding to the target application; an application permission display module for responding to all In the calling operation, when the permission notification mode corresponding to the target application permission is the permission notification mode, the target application, the target application permission, and the calling information of the target application permission are displayed on a designated interface in association with each other.
  • embodiments of the present disclosure provide a mobile terminal, including a processor, a memory, and a computer program stored on the memory and running on the processor, the computer program being executed by the processor When realizing the steps of the application permission display method described in any one of the above.
  • embodiments of the present disclosure provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the application permission display described in any one of the above is realized Method steps.
  • the target application by receiving the calling operation for the target application permission corresponding to the target application, in response to the calling operation, in the case where it is determined that the permission notification mode corresponding to the target application permission is the allowed notification mode, the target application, The target application permission and the calling information of the target application permission are displayed in the specified interface in association with each other.
  • the application permission to be run, the application permission invoked by the running application, and the calling details are displayed when the application permission is invoked according to the permission notification mode set according to the application permission of the application, which can be displayed when the application permission is invoked. That is, to show the user the situation that the application permission is invoked, which improves the user's perception, and can also greatly reduce the problem of user privacy exposure.
  • FIG. 1 is a flowchart of steps of an embodiment of an application permission display method of the first aspect of the present disclosure
  • FIG. 2 is a flowchart of another embodiment of the application permission display method of the first aspect of the present disclosure
  • FIG. 2a is a schematic diagram of an example of an application permission setting interface applying the application permission display method of the first aspect of the present disclosure
  • 2b is a schematic diagram of an example of an exemplary authority management interface applying the application authority display method of the first aspect of the present disclosure
  • FIG. 2c is a schematic diagram of an example of a permission usage notification using the application permission display method of the first aspect of the present disclosure
  • 2d is a schematic diagram of an example of displaying application permissions using the application permission display method of the first aspect of the present disclosure
  • 2e is a schematic diagram of an example of displaying application permissions using the application permission display method of the first aspect of the present disclosure
  • 2f is a schematic diagram of an example of viewing application permissions using the application permission display method of the first aspect of the present disclosure
  • 2g is a schematic diagram of an example of viewing application permissions using the application permission display method of the first aspect of the present disclosure
  • FIG. 2h is a schematic diagram of an example of application permission invocation history using the application permission display method of the first aspect of the present disclosure
  • Fig. 2i is a schematic diagram of an example of application permission invocation history using the application permission display method of the first aspect of the present disclosure
  • FIG. 3 is a schematic structural diagram of an embodiment of an application permission display device in the second aspect of the present disclosure.
  • FIG. 4 is a schematic structural diagram of another embodiment of the application permission display device of the second aspect of the present disclosure.
  • Fig. 5 is a structural block diagram of an embodiment of a mobile terminal in the third aspect of the present disclosure.
  • Fig. 1 shows a flow chart of the steps of an embodiment of an application permission display method in the first aspect of the present disclosure.
  • the method for displaying application permissions may specifically include the following steps:
  • Step 101 Receive a call operation for the target application permission corresponding to the target application.
  • the embodiments of the present disclosure may be applied to the terminal side.
  • the terminal may include a mobile terminal and a PC (Personal Computer) terminal.
  • the mobile terminal may be a mobile electronic device such as a mobile phone or a PAD (Portable Android Device).
  • the PC terminal may be a desktop computer, Electronic equipment such as laptops.
  • the target application refers to an application that needs to call application permissions for multiple applications that have been downloaded and installed successfully in the mobile terminal, for example, social apps, video apps, communication apps, etc. that have been installed on the mobile phone. Specifically, you can It depends on the actual situation.
  • FIG. 2c shows a schematic diagram of an example of permission usage notification.
  • the "58.com App” is pre-authorized with "storage” permission, "phone” permission, “location” permission, “contact” permission, “microphone” permission, and "camera” permission.
  • the target application permission refers to the permission called during the running of the target application. For example, when the "camera” permission is called during the running of the video app, the "camera” permission is taken as the target application permission.
  • the calling operation refers to the operation of calling the permission of the target application during the running process of the target application. For example, when the “camera” permission is called during the running of the video app, the operation of starting the “camera” is regarded as the calling operation.
  • a monitoring program corresponding to the permission call operation can be preset in the mobile terminal system, and the monitoring program can monitor the call operation of the target application permission in real time.
  • step 102 After receiving the call operation for the target application permission corresponding to the target application, step 102 is executed.
  • step 102 in response to the calling operation, when the permission notification mode corresponding to the target application permission is the permission notification mode, the target application, the target application permission, and the calling information of the target application permission are displayed on the designated interface in association with each other.
  • the permission notification mode may include an allow notification mode and a rejection notification mode.
  • the permission notification modes include: “off” mode, "smart notification” mode, and “notify when in use” mode.
  • the “off” mode it means that the user uses the application to call the corresponding
  • the "off" mode is the rejection notification mode; and when the user selects the "smart notification” mode or the “notify when in use” mode, the user can be notified when the user invokes the corresponding permission.
  • the mobile terminal can automatically detect whether it is a mandatory call. If so, notify the user that the application permission is forcibly called, then the above-mentioned "smart notification” mode or "use Time notification” mode is the allowed notification mode.
  • the permission notification mode triggered by the invoking the target application permission is the permitted notification mode.
  • the permission notification mode set by the user for the target application permission corresponding to the target application in advance is the in-use notification mode
  • the permission notification mode is triggered when it is detected that the target application calls the target application permission.
  • Mandatory call notification mode refers to the mode of notification when a malicious (ie mandatory) call is made by an identified application according to the manufacturer’s intelligent algorithm. For example, when the user is using a social app, the user does not perform the activation of the "camera” When the “camera” operation is performed, the social app is forced to call the “camera”, and the forced call is a forced call operation.
  • the permission notification mode triggered by calling the target application permission can be determined That is to allow notification mode.
  • the calling information refers to the detailed description information of the calling target application permission, such as the time of calling the target application permission, the operating user and other information.
  • Figure 2d shows a schematic diagram showing an example of application permissions. As shown in Figure 2d, the display has a reason for use: user operation, the reason for use can be used as invocation information.
  • the designated interface refers to a certain interface in the display screen of the mobile terminal.
  • the designated interface can be an APP user interface.
  • the display screen can be directly used as the designated interface.
  • the permission notification mode preset by the user for the target application permission corresponding to the target application is the rejection notification mode, as shown in Figure 2c
  • the permission notification mode triggered by calling the target application permission is the rejection notification mode.
  • the rejection notification mode just call the target application permission of the target application directly without notification processing.
  • the permission notification mode triggered by calling the target application permission is the permission notification Mode, in the allowed notification mode, the target application, target application permission, and call information of the target application permission can be associated and displayed on the specified interface.
  • the target application permission corresponding to the target application is the "smart notification" mode (that is, one of the allowed notification modes)
  • the target is forced to be called when the target application is running in the foreground or background.
  • the permission notification mode can be triggered.
  • the target application, target application permission, and target application permission invocation information can be associated and displayed on the specified interface; for example, when a user uses a social app, When the user does not perform the operation of starting the "camera", the social APP forcibly invokes the operation of the "camera” permission to trigger the permission notification mode.
  • the target application, the target application permission, and the calling information of the target application permission can be associated and displayed on the designated interface.
  • the target application permission when the target application permission is invoked, it can be displayed in the APP user interface that "something is starting in association with the reason for use: user operation".
  • the authorized application permissions of the specified application can also be displayed in the display interface.
  • the notification mode set for each application permission can be displayed to show the user.
  • FIG. 2e when the mobile terminal is in the off-screen state, "target application”, “authorization usage notification”, "something is being associated with startup” and “use reason: user operation” may be displayed on the display screen.
  • notification methods such as popping up a window on the display screen, displaying the target application, target application permissions, and calling information in the window.
  • the application permission to be run, the application permission invoked by the running application, and the calling details are displayed when the application permission is invoked according to the permission notification mode set according to the application permission of the application, which can be displayed when the application permission is invoked. That is, to show the user how the application permissions are being invoked.
  • the application permission display method receives the calling operation for the target application permission corresponding to the target application, and according to the calling operation, detects whether the permission notification mode triggered by calling the target application permission is the permitted notification mode, and determines the target When the permission notification mode corresponding to the application permission is the allowed notification mode, the target application, the target application permission, and the calling information of the target application permission are associated and displayed on the designated interface.
  • the application permission to be run, the application permission invoked by the running application, and the calling details are displayed when the application permission is invoked according to the permission notification mode set according to the application permission of the application, which can be displayed when the application permission is invoked. That is, to show the user the situation that the application permission is called, which improves the user's perception, and can minimize the problem of user privacy exposure.
  • Fig. 2 shows a flowchart of another embodiment of the application permission display method of the first aspect of the present disclosure.
  • the method for displaying application permissions may specifically include the following step 201:
  • the embodiments of the present disclosure may be applied to the terminal side.
  • the terminal may include a mobile terminal and a PC (Personal Computer) terminal.
  • the mobile terminal may be a mobile electronic device such as a mobile phone or a PAD (Portable Android Device).
  • the PC terminal may be a desktop computer, Electronic equipment such as laptops.
  • the target application refers to an application that currently requires application permission settings among multiple applications that have been successfully downloaded and installed in the mobile terminal, for example, social apps, video apps, and communication apps that have been installed on the mobile phone. Specifically, it can be determined according to the actual situation.
  • the permission setting operation refers to the operation of setting the notification mode of the application permission for the target application.
  • the authority management interface can be preset, and multiple applications can be preset in the authority management interface.
  • FIG. 2b shows a schematic diagram of an example of a rights management interface.
  • there are multiple applications displayed in the authority management interface such as "58.com”, “Alibaba”, “iqiyi”, “Anjuke” and other applications.
  • the permission notification mode for setting the application permissions for the application is started.
  • the permission notification mode for setting the application permissions for the "Anjuke” application is started.
  • the "customer" application is the target application, and the click operation performed by the user can be regarded as a permission setting operation.
  • the permission setting operation may also be other forms of operations, such as a drag-and-drop operation, a double-click operation, etc., which may be specifically determined according to business requirements, which is not limited in the embodiment of the present disclosure.
  • an APP when an APP applies for listing on the application market, it needs to fill in the type of permission to be called and the reason for calling the permission.
  • the application market will review the permission application of the APP. After the user downloads the APP, the APP will be prohibited from obtaining the unapplied Permission; At the user level, the unapplied permission switch is grayed out and cannot be clicked, or is not displayed. If the APP wants to update its own permission type, it needs to reapply and review it.
  • the above example only describes the application permission application process of the APP, and when the permission notification mode corresponding to the application permission is set for each APP in the following process, it is for the application permission authorized by the application.
  • the settings made.
  • the monitoring program corresponding to the permission setting operation can be preset in the mobile terminal system, and the permission setting operation performed by the user on the target application can be monitored in real time through the monitoring program.
  • the application permission display method of this embodiment executes step 202 after receiving the permission setting operation corresponding to the target application.
  • step 202 in response to the permission setting operation, a permission setting interface corresponding to the target application is displayed; multiple authorized application permissions are displayed in the permission setting interface.
  • the permission setting interface refers to an interface used to set a permission notification mode for one or more authorized application permissions of a target application.
  • Figure 2c shows a schematic diagram of an example of a permission usage notification mode.
  • multiple authorized application permissions can be displayed, such as “storage”, “location”, “phone”, “contact”, “ Authorized application permissions such as "microphone”, “headphone”, etc., when the user sets the permission notification mode for an authorized application permission, you can click the authorized application permission, for example, when the user clicks on "storage", it is the "storage” application Permission setting permission notification mode, the click operation can be regarded as permission setting operation.
  • the user sets the permission notification mode for the target application, he can combine with the corresponding application permission set for the same type of application before, and set the prompt.
  • the target application is A
  • A is the same type of application
  • the program is B
  • the notification mode is preset for B each time the phone permission is used.
  • the target application permission mentioned in the following steps is one application permission among multiple authorized application permissions.
  • the application permission display method of this embodiment performs step 203 after displaying the permission setting interface corresponding to the target application in response to the permission setting operation.
  • step 203 the permission notification mode set by the user for each authorized application permission is obtained and saved.
  • FIG. 2a shows a schematic diagram of an example of an application permission setting interface.
  • FIG. 2a shows a schematic diagram of an example of an application permission setting interface.
  • FIG. 2a when you click on an authorized application permission, you can display the interface as shown in Figure 2a.
  • "Do not ask again after prohibition” ie reject notification mode
  • Smart notification and “Notify every time you use” three permission notification modes, among which, "Smart notification” and “Notify every time you use” are allowed notification modes. Users can choose one of them as the permission notification mode for authorized application permissions. .
  • a recommended logo can also be displayed, as shown in Figure 2a, to prompt the user that the permission notification mode is more suitable.
  • the set permission notification mode can be saved. For example, you can set a save button on the permission setting interface. After the user clicks the save button, the user is saved as Authorization notification mode for authorized application permission settings.
  • the application permission display method of this embodiment further includes step 204: receiving a call operation for the target application permission corresponding to the target application.
  • the application permission display method of this embodiment further includes step 205: in response to the calling operation, when the permission notification mode corresponding to the target application permission is the permission notification mode, the target application, the target application permission, and the calling information of the target application permission The association is displayed on the specified interface.
  • steps 204 to 205 is similar to the specific implementation of steps 101 to 102 in the first embodiment.
  • steps 101 to 102 please refer to the description of the first embodiment. I won't repeat them in the example.
  • the application permission display method of this embodiment further includes step 206: receiving target input for the target application.
  • the target input refers to an input operation used to view the application permissions set for the target application.
  • the target input can be a drag operation, a sliding operation, etc., such as dragging the target application from position A to position B, and so on.
  • the target input may also be other operations, specifically, it may be determined according to business requirements, which is not limited in the embodiments of the present disclosure.
  • the mobile terminal can monitor the user's target input to the target application in real time, and after receiving the target input for the target application, step 207 is executed.
  • the application permission display method of this embodiment further includes step 207: In response to the target input, according to the input parameters corresponding to the target input, obtain the target permission notification mode set for the target application.
  • the current permission notification mode refers to the permission notification mode set for multiple authorized application permissions corresponding to the target application.
  • the authorized application permissions corresponding to the target application include permission a and permission b.
  • the permission notification mode is set for permission a When it is the "notification mode when in use” and the permission notification mode set for permission b is the “compulsory call notification mode", the target permission notification mode is the "use notification mode” and the "force call notification mode".
  • the input parameter refers to the parameter corresponding to the target input.
  • the drag parameter may be the drag position, that is, the end position of the drag operation, and the drag operation reaches the drag operation.
  • the location is triggered to obtain the target permission notification mode set for the target application.
  • FIG. 2f a schematic diagram of viewing application permissions provided by the embodiment of the first aspect of the present disclosure is shown, as shown in FIG. 2f.
  • the window for viewing permissions can be set in the display interface. This window can be regarded as the target location for viewing the permission notification mode set for an application. When an application is dragged and dropped into the window, it is triggered to obtain the The permission notification mode set by the application.
  • the application permission display method of this embodiment further includes step 208: displaying the target permission notification mode on the permission viewing interface.
  • the target permission notification mode set for the target application can be obtained in response to the target input according to the input parameters corresponding to the target input, and step 208 is executed.
  • the permission viewing interface refers to an interface used to display the permission notification mode set for the target application.
  • the target permission notification mode set for the target application can be displayed on the permission viewing interface.
  • FIG. 2g shows a schematic diagram of an example of viewing application permissions.
  • the permission notification mode set for the "Didi Travel” application is: "Storage”: Allow notification; “Phone”: Allow notification; “Location”: Allow notification; “Contact”, “Microphone” , "Camera” are not allowed to notify.
  • the application permission display method of this embodiment further includes step 209: receiving a viewing operation for the target application permission.
  • the viewing operation refers to the operation used to view the historical call records of the target application permissions.
  • the viewing operation may be an operation preset by the mobile terminal, such as double-clicking an APP, or clicking a designated operation to view historical call records, etc. Specifically, it may be determined according to business requirements, which is not limited in the embodiment of the present disclosure.
  • the monitoring program corresponding to the viewing operation can be preset in the system, and the viewing operation performed by the user on the target application authority can be monitored in real time through the monitoring program.
  • the application permission display method of this embodiment executes step 210 after receiving the viewing operation for the target application permission.
  • step 210 in response to the viewing operation, a historical call record corresponding to the permission of the target application is obtained.
  • the historical call record refers to the historical behavior of calling the target application permission when the target application is running.
  • the viewing operation After receiving the viewing operation for the permission of the target application, the viewing operation can be responded to, and the historical behavior corresponding to the permission of calling the target application during the running of the target application can be obtained, that is, the historical calling record.
  • the application permission display method of this embodiment executes step 211 after obtaining the historical call record corresponding to the target application permission.
  • step 211 the historical call record and the target application program are associated and displayed on the historical record viewing interface.
  • the historical record viewing interface refers to the interface used to display the historical behavior of calling the target application permissions during the historical running of the target application.
  • FIG. 2h shows a schematic diagram of an example of an application permission call history record.
  • the historical record of the target application's permission call to the target application includes: "access call history", time: 2019/04/27, 14:51; "forbidden to read installed application information", time It is: 2019/04/27, 14:49; "It is prohibited to read installed applications", and the time is: 2019/04/27, 14:49 and so on.
  • the behavior data of the target application calling permission of the target application can be obtained, so as to execute the process of detecting whether there is a forced calling behavior in the subsequent steps.
  • the application permission display method of this embodiment performs step 212 after the historical call record and the target application are associated and displayed on the historical record viewing interface.
  • step 212 obtain the mandatory call behavior existing in the historical call record.
  • the historical call record it can also be detected whether there is a forced call behavior. If there is a forced call behavior and the user is not notified, the forced call behavior in the historical call record can be obtained.
  • the application permission display method of this embodiment executes step 213 after obtaining the mandatory calling behavior existing in the historical calling record.
  • step 213 a reminder message corresponding to the forced call behavior is generated and output.
  • a reminder message corresponding to the mandatory call behavior can be generated, and the reminder information can be sent to the user to remind the user when the target application is forced to call the target application permission, and
  • the user can perform operations such as resetting the permission notification mode of the target application permission, further avoiding the leakage of user privacy.
  • the method for invoking application permissions provided by the embodiments of the present disclosure can also remind the user of forced invoking of application permissions, so that the user can clarify which applications exist.
  • the behavior of forcibly invoking application permissions can further avoid the disclosure of user privacy.
  • FIG. 3 shows a schematic structural diagram of an embodiment of an application permission display device in the second aspect of the present disclosure.
  • the application permission display device 300 may include the following modules:
  • the calling operation receiving module 301 is used to receive the calling operation for the target application permission corresponding to the target application;
  • the application permission display module 302 is used to display the invocation information of the target application, the target application permission, and the target application permission in a specified interface in response to the calling operation, when the permission notification mode corresponding to the target application permission is the allowed notification mode .
  • the application permission display device receives the calling operation for the target application permission corresponding to the target application, and in response to the calling operation, when it is determined that the permission notification mode corresponding to the target application permission is the permitted notification mode, the The target application, the target application permission, and the calling information of the target application permission are displayed in the specified interface in association.
  • the application permission to be run, the application permission invoked by the running application, and the calling details are displayed when the application permission is invoked according to the permission notification mode set according to the application permission of the application, which can be displayed when the application permission is invoked. That is, to show the user the situation that the application permission is called, which improves the user's perception and can minimize the problem of user privacy exposure.
  • Fig. 4 shows a schematic structural diagram of an application authority display device in the second aspect of the present disclosure.
  • the application permission display device 400 may specifically include the following modules:
  • the setting operation receiving module 401 is used to receive permission setting operations for the target application
  • the setting interface display module 402 is used to display the permission setting interface corresponding to the target application in response to the permission setting operation; multiple authorized application permissions are displayed in the permission setting interface, and the target application permission is one of the multiple authorized application permissions.
  • the permission mode acquisition module 403 is used to obtain and save the permission notification mode set by the user for each authorized application permission; wherein, the permission notification mode includes any one of the permission notification mode and the rejection notification mode, and the permission notification mode includes the use time Notification mode and mandatory call notification mode;
  • the calling operation receiving module 404 is configured to receive the calling operation for the target application permission corresponding to the target application;
  • the notification mode detection module 405 is configured to respond to the calling operation and display the calling information of the target application, the target application permission, and the target application permission on the designated interface in a case that the permission notification mode corresponding to the target application permission is the allowed notification mode. ;
  • the target input receiving module 406 is configured to receive target input for the target application
  • the target mode obtaining module 407 is configured to obtain the target authority notification mode set for the target application according to the input parameters corresponding to the target input in response to the target input;
  • the target mode display module 408 is used to display the target permission notification mode on the permission view interface
  • the viewing operation receiving module 409 is configured to receive the viewing operation for the target application permissions
  • the historical behavior obtaining module 410 is configured to obtain the historical call record corresponding to the target application permission in response to the viewing operation;
  • the historical behavior display module 411 is used to display historical call records and target applications in association with the historical record viewing interface
  • the mandatory behavior acquisition module 412 is used to acquire the mandatory calling behaviors existing in the historical calling records
  • the reminder information generating module 413 is configured to generate and output reminder information corresponding to the forced calling behavior.
  • the application permission invoking device provided by the embodiment of the present disclosure has the beneficial effects of the application permission invoking device provided in the third embodiment above, and can also remind the behavior of forcibly invoking the application permission, so that the user can clarify which applications exist.
  • the behavior of forcibly invoking application permissions can further avoid the disclosure of user privacy.
  • a third aspect of the present disclosure also provides a mobile terminal, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor.
  • the computer program is executed by the processor, the application authority display of the above-mentioned first aspect is realized.
  • the steps of the various embodiments of the method can achieve the same technical effect. In order to avoid repetition, details are not described here.
  • Fig. 5 shows a structural block diagram of an embodiment of a mobile terminal of the third aspect of the present disclosure.
  • the mobile terminal 500 includes but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, and a memory 509 , The processor 510, and the power supply 511 and other components.
  • a radio frequency unit 501 includes but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, and a memory 509 , The processor 510, and the power supply 511 and other components.
  • the mobile terminal 500 includes but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, and a memory 509 , The processor 510, and the power supply 511 and other
  • the processor 510 is the control center of the mobile terminal. It uses various interfaces and lines to connect the various parts of the entire mobile terminal, runs or executes software programs and/or modules stored in the memory 509, and calls data stored in the memory 509 , Perform various functions of the mobile terminal and process data, so as to monitor the mobile terminal as a whole.
  • the processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface, application programs, etc., and the modem
  • the processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 510.
  • the processor 510 may be used to control the user input unit 507 to receive the invocation operation for the target application permission corresponding to the target application; in response to the invocation operation, when the permission notification mode corresponding to the target application permission is the permission notification mode
  • the control and display unit 506 displays the target application program, the target application authority, and the calling information of the target application authority in association with the designated interface.
  • the target application by receiving the calling operation for the target application permission corresponding to the target application, in response to the calling operation, in the case where it is determined that the permission notification mode corresponding to the target application permission is the allowed notification mode, the target application, The target application permission and the calling information of the target application permission are displayed in the specified interface in association with each other.
  • the permission notification mode set according to the application permission of the application when the application permission is invoked, the application to be run, the application permission invoked by the running application, and the invocation details are displayed, which can be displayed when the application permission is invoked. Show the user how the application permission is called, which improves user perception and minimizes the problem of user privacy exposure.
  • the radio frequency unit 501 can be used for receiving and sending signals in the process of sending and receiving information or talking. Specifically, after receiving the downlink data from the base station, it is processed by the processor 510; Uplink data is sent to the base station.
  • the radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio frequency unit 501 can also communicate with the network and other devices through a wireless communication system.
  • the mobile terminal provides users with wireless broadband Internet access through the network module 502, such as helping users to send and receive emails, browse web pages, and access streaming media.
  • the audio output unit 503 may convert the audio data received by the radio frequency unit 501 or the network module 502 or stored in the memory 509 into an audio signal and output it as sound. Moreover, the audio output unit 503 may also provide audio output related to a specific function performed by the mobile terminal 500 (for example, call signal reception sound, message reception sound, etc.).
  • the audio output unit 503 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 504 is used to receive audio or video signals.
  • the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042.
  • the graphics processor 5041 is configured to monitor images of still pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode.
  • the data is processed.
  • the processed image frame may be displayed on the display unit 506.
  • the image frame processed by the graphics processor 5041 may be stored in the memory 509 (or other storage medium) or sent via the radio frequency unit 501 or the network module 502.
  • the microphone 5042 can receive sound, and can process such sound into audio data.
  • the processed audio data can be converted into a format that can be sent to a mobile communication base station via the radio frequency unit 501 for output in the case of a telephone call mode.
  • the mobile terminal 500 also includes at least one sensor 505, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor.
  • the ambient light sensor can adjust the brightness of the display panel 5061 according to the brightness of the ambient light.
  • the proximity sensor can close the display panel 5061 and the display panel 5061 when the mobile terminal 500 is moved to the ear. / Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three-axis), and can detect the magnitude and direction of gravity when it is stationary, and can be used to identify the posture of the mobile terminal (such as horizontal and vertical screen switching, related games).
  • sensor 505 can also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, Infrared sensors, etc., will not be repeated here.
  • the display unit 506 is used to display information input by the user or information provided to the user.
  • the display unit 506 may include a display panel 5061, and the display panel 5061 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the user input unit 507 may be used to receive inputted numeric or character information, and generate key signal input related to user settings and function control of the mobile terminal.
  • the user input unit 507 includes a touch panel 5071 and other input devices 5072.
  • the touch panel 5071 also known as a touch screen, can collect the user's touch operations on or near it (for example, the user uses any suitable objects or accessories such as fingers, stylus, etc.) on the touch panel 5071 or near the touch panel 5071. operating).
  • the touch panel 5071 may include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the user's touch position, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it To the processor 510, the command sent by the processor 510 is received and executed.
  • the touch panel 5071 can be implemented in multiple types such as resistive, capacitive, infrared, and surface acoustic wave.
  • the user input unit 507 may also include other input devices 5072.
  • other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.
  • the touch panel 5071 can be overlaid on the display panel 5061.
  • the touch panel 5071 detects a touch operation on or near it, it is transmitted to the processor 510 to determine the type of the touch event, and then the processor 510 determines the type of the touch event according to the touch.
  • the type of event provides corresponding visual output on the display panel 5061.
  • the touch panel 5071 and the display panel 5061 are used as two independent components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 5071 and the display panel 5061 can be integrated
  • the implementation of the input and output functions of the mobile terminal is not specifically limited here.
  • the interface unit 508 is an interface for connecting an external device with the mobile terminal 500.
  • the external device may include a wired or wireless headset port, an external power source (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc.
  • the interface unit 508 can be used to receive input (for example, data information, power, etc.) from an external device and transmit the received input to one or more elements in the mobile terminal 500 or can be used to connect to the mobile terminal 500 and external Transfer data between devices.
  • the memory 509 can be used to store software programs and various data.
  • the memory 509 may mainly include a storage program area and a storage data area.
  • the storage program area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.), etc.; Data created by the use of mobile phones (such as audio data, phone book, etc.), etc.
  • the memory 509 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
  • the memory 509 may store a computer program, and when the computer program is executed by the processor 510, the steps of each embodiment of the application permission display method of the first aspect are implemented, which will not be repeated here.
  • the mobile terminal 500 may also include a power source 511 (such as a battery) for supplying power to various components.
  • a power source 511 such as a battery
  • the power source 511 may be logically connected to the processor 510 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system. And other functions.
  • the mobile terminal 500 includes some functional modules not shown, which will not be repeated here.
  • the fourth aspect of the present disclosure also provides a computer-readable storage medium on which a computer program is stored.
  • a computer program When the computer program is executed by a processor, the steps of each embodiment of the application permission display method of the first aspect are implemented. , And can achieve the same technical effect, in order to avoid repetition, I will not repeat it here.
  • Examples of computer-readable storage media include non-transitory computer-readable storage media, such as read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disks, or optical disks.
  • Such a processor may be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic array. It should also be understood that each block in the block diagram and/or flowchart, and a combination of blocks in the block diagram and/or flowchart, can also be implemented by a dedicated hardware-based system that performs the specified function or action, Or it can be implemented by a combination of dedicated hardware and computer instructions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Computer Hardware Design (AREA)
  • Telephone Function (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

一种应用权限显示方法、装置（300，400）及移动终端（500）。所述方法包括：接收针对目标应用程序对应的目标应用权限的调用操作（101）；响应于所述调用操作，在所述目标应用权限对应的权限通知模式为允许通知模式的情况下，将所述目标应用程序、所述目标应用权限和所述目标应用权限的调用信息关联展示于指定界面（102）。

Description

应用权限显示方法、装置、移动终端及存储介质
相关申请的交叉引用
本申请要求享有于2019年08月29日提交的名称为“应用权限显示方法、装置及移动终端”的中国专利申请201910820974.7的优先权，该申请的全部内容通过引用并入本文中。
技术领域
本公开涉及移动通信技术领域，特别是涉及一种应用权限显示方法、装置、移动终端及存储介质。
背景技术
随着移动通信技术的迅猛发展，移动终端(如手机等)已经成为人们生活和工作中不可或缺的一部分。
当前移动终端内下载安装的各种APP(Application，应用程序)存在过度获取应用权限，导致用户隐私暴露，安全感越来越差，对APP产生不信任感。目前，市面上的移动终端，均是在“设置”界面简单的展示APP权限授予情况，在先方案中，只有在应用权限被调用之后，用户才会知道应用权限被调用的情况，而在调用时用户是未知的，导致用户隐私暴露。
发明内容
本公开实施例提供一种应用权限显示方法、装置、移动终端及存储介质，以解决现有技术中只有在应用权限被调用之后，用户才会知道应用权限被调用的情况，而在调用时用户是未知的，导致用户隐私暴露的问题。
为了解决上述技术问题，第一方面，本公开实施例提供了一种应用权限显示方法，包括：接收针对目标应用程序对应的目标应用权限的调用操作；响应于所述调用操作，在所述目标应用权限对应的权限通知模式为允 许通知模式的情况下，将所述目标应用程序、所述目标应用权限和所述目标应用权限的调用信息关联展示于指定界面。
第二方面，本公开实施例提供了一种应用权限显示装置，包括：调用操作接收模块，用于接收针对目标应用程序对应的目标应用权限的调用操作；应用权限展示模块，用于响应于所述调用操作，在所述目标应用权限对应的权限通知模式为允许通知模式的情况下，将所述目标应用程序、所述目标应用权限和所述目标应用权限的调用信息关联展示于指定界面。
第三方面，本公开实施例提供了一种移动终端，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述任一项所述的应用权限显示方法的步骤。
第四方面，本公开实施例提供了一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现上述任一项所述的应用权限显示方法的步骤。
在本公开实施例中，通过接收针对目标应用程序对应的目标应用权限的调用操作，响应于调用操作，在确定目标应用权限对应的权限通知模式为允许通知模式的情况下，将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面。本公开实施例通过根据对应用程序的应用权限设置的允许通知模式，在调用应用权限时，即将运行的应用程序、运行应用程序调用的应用权限以及调用详情进行展示，可以在应用权限被调用时即向用户展示应用权限的被调用的情况，提高了用户感知，并且，还能够很大限度降低用户隐私暴露的问题。
附图说明
从下面结合附图对本公开的具体实施方式的描述中可以更好地理解本公开其中，相同或相似的附图标记表示相同或相似的特征。
图1是本公开第一方面的应用权限显示方法的实施例的步骤流程图；
图2是本公开第一方面的应用权限显示方法的另一实施例步骤流程图；
图2a是应用本公开第一方面的应用权限显示方法的应用权限设置界面的示例的示意图；
图2b是应用本公开第一方面的应用权限显示方法的示例性权限管理界面的示例的示意图；
图2c是应用本公开第一方面的应用权限显示方法的权限使用通知的示例的示意图；
图2d是应用本公开第一方面的应用权限显示方法的展示应用权限的示例的示意图；
图2e是应用本公开第一方面的应用权限显示方法的展示应用权限的示例的示意图；
图2f是应用本公开第一方面的应用权限显示方法的查看应用权限的示例的示意图；
图2g是应用本公开第一方面的应用权限显示方法的查看应用权限的示例的示意图；
图2h是应用本公开第一方面的应用权限显示方法的应用权限调用历史记录的示例的示意图；
图2i是应用本公开第一方面的应用权限显示方法的应用权限调用历史记录的示例的示意图；
图3是本公开第二方面的应用权限显示装置的实施例的结构示意图；
图4是本公开第二方面的应用权限显示装置的另一实施例的结构示意图；
图5是本公开第三方面的移动终端的实施例的结构框图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的应用权限显示方法进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的其他实施例，都属于本公开保护 的范围。
实施例一
图1示出了本公开第一方面应用权限显示方法的实施例的步骤流程图。参考图1，该应用权限显示方法具体可以包括如下步骤：
步骤101：接收针对目标应用程序对应的目标应用权限的调用操作。
本公开实施例可以应用于终端侧，终端可以包括移动终端和PC(Personal Computer，个人计算机)端，移动终端可以为手机、PAD(Portable Android Device)等移动电子设备，PC端可以为台式电脑、笔记本电脑等电子设备。
目标应用程序是指移动终端中已经下载安装成功的多个应用程序需要调用应用权限的一个应用程序，例如，手机中已经安装的社交类APP、视频类APP、通讯类APP等，具体地，可以根据实际情况而定。
在移动终端中可以预先为每个应用程序授权多个应用权限，例如，图2c示出了一种权限使用通知的示例的示意图。如图2c所示，预先为“58同城APP”授权有“存储”权限、“电话”权限、“定位”权限、“联系人”权限、“麦克风”权限和“相机”权限等。
目标应用权限是指在目标应用程序的运行过程中所调用的权限，例如，在视频类APP运行过程中，调用“相机”权限时，则将“相机”权限作为目标应用权限。
调用操作是指在目标应用程序的运行过程中，调用目标应用权限的操作，例如，在视频类APP运行过程中，调用“相机”权限时，则将启动“相机”的操作视为调用操作。
在移动终端系统内可以预先设置权限调用操作对应的监控程序，该监控程序可以实时监控对目标应用权限的调用操作。
在接收针对目标应用程序对应的目标应用权限的调用操作之后，执行步骤102。
在步骤102，响应于调用操作，在目标应用权限对应的权限通知模式为允许通知模式的情况下，将目标应用程序、目标应用权限和目标应用权 限的调用信息关联展示于指定界面。
在移动终端可以在应用程序首次调用权限时，由用户设置权限通知模式，权限通知模式可以包括允许通知模式和拒绝通知模式。例如，如图2c所示，权限通知模式包括：“关闭”模式、“智能通知”模式和“使用时通知”模式，其中，在用户选择“关闭”模式时，表示在用户使用应用程序调用相应权限时，不再向用户进行通知，即“关闭”模式即为拒绝通知模式；而在用户选择“智能通知”模式或“使用时通知”模式，即在用户调用相应权限时，可以通知用户应用权限被调用的情况；或在相应应用权限被强制调用时，移动终端可以自动检测是否为强制调用，若是，则通知用户应用权限被强制调用，则上述提及的“智能通知”模式或“使用时通知”模式即为允许通知模式。
可以理解地，上述示例仅是为了更好地理解本公开实施例的应用权限显示方法而列举的示例，不作为对本公开实施例的唯一限制。
在接收到针对目标应用权限的调用操作之后，可以响应于调用操作，确定出调用目标应用权限触发的权限通知模式是否为允许通知模式。
在本公开实施例中，在用户预先为目标应用程序对应的目标应用权限设置的权限通知模式为使用时通知模式时，在监测到目标应用程序调用目标应用权限时，即触发允许通知模式。
强制调用通知模式是指据厂商智能算法，在识别应用程序进行恶意(即强制)调用时，进行通知的模式，例如，例如，在用户使用社交类APP的过程中，在用户未执行启动“相机”的操作时，该社交类APP强制调用“相机”，该强制调用即为强制调用操作。
在用户预先为目标应用程序对应的目标应用权限设置的权限通知模式为强制调用通知模式，且目标应用程序调用目标应用权限的操作为强制调用操作时，可以确定调用目标应用权限触发的权限通知模式即为允许通知模式。
调用信息是指调用目标应用权限的详细描述信息，如调用目标应用权限的时间，操作用户等信息。例如，图2d示出了一种展示应用权限的示 例的示意图。如图2d所示，展示有使用原因：用户操作，使用原因可以作为调用信息。
指定界面是指移动终端显示屏幕内的某个界面，例如，如图2d，指定界面可以为APP使用界面。或者，如图2e中示出的一种展示应用权限的示例所示的，在移动终端处于灭屏状态下，可以直接将显示屏幕作为指定界面。
在用户为目标应用程序对应的目标应用权限预先设置的权限通知模式为拒绝通知模式，如图2c所示的“关闭”模式时，则调用目标应用权限触发的权限通知模式即为拒绝通知模式，在拒绝通知模式下，直接调用目标应用程序的目标应用权限即可，不做通知处理。
而在用户为目标应用程序对应的目标应用权限预先设置的权限通知模式为“使用时通知”模式(即允许通知模式的一种)时，在调用目标应用权限触发的权限通知模式即为允许通知模式，在允许通知模式下，可以将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面。
而在用户为目标应用程序对应的目标应用权限预先设置的权限通知模式为“智能通知”模式(即允许通知模式的一种)时，在前台或后台运行目标应用程序的过程中，强制调用目标应用权限时，可以触发允许通知模式，在允许通知模式下，可以将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面；例如，在用户使用社交类APP的过程中，在用户未执行启动“相机”的操作时，该社交类APP强制调用“相机”权限的操作即触发允许通知模式。
可以理解地，上述示例仅是为了更好地理解本公开实施例的应用权限显示方法而列举的示例，不作为对本公开实施例的唯一限制。
在权限通知模式为允许通知模式的情况下，可以将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面。例如，如图2d所示，在APP操作界面内，调用目标应用权限时，可以在APP使用界面内展示“某某正在关联启动，使用原因：用户操作”。当然，在该显示 界面内还可以展示指定应用的授权应用权限，如，在目标应用程序为“58应用程序”时，可以展示为各应用权限设置的通知模式，以向用户展示。再如，如图2e所示，在移动终端处于灭屏状态下，可以将在显示屏幕上显示“目标应用程序”“权限使用通知”“某某正在关联启动”“使用原因：用户操作”。
当然，在具体实现中，还可以采用其它通知方式，如在显示屏幕上弹出一个窗口，在窗口内展示目标应用程序、目标应用权限，及调用信息。
可以理解地，上述示例仅是为了更好地理解本公开实施例的应用权限显示方法而列举的示例，不作为对本公开实施例的唯一限制。
本公开实施例通过根据对应用程序的应用权限设置的允许通知模式，在调用应用权限时，即将运行的应用程序、运行应用程序调用的应用权限以及调用详情进行展示，可以在应用权限被调用时即向用户展示应用权限的被调用的情况。
本公开实施例提供的应用权限显示方法，通过接收针对目标应用程序对应的目标应用权限的调用操作，根据调用操作，检测调用目标应用权限触发的权限通知模式是否为允许通知模式，并在确定目标应用权限对应的权限通知模式为允许通知模式的情况下，将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面。本公开实施例通过根据对应用程序的应用权限设置的允许通知模式，在调用应用权限时，即将运行的应用程序、运行应用程序调用的应用权限以及调用详情进行展示，可以在应用权限被调用时即向用户展示应用权限的被调用的情况，提高了用户感知，并且，能够最大限度降低用户隐私暴露的问题。
实施例二
图2示出了本公开第一方面的应用权限显示方法的另一实施例的步骤流程图。如图2所示，该应用权限显示方法具体可以包括如下步骤201：
接收针对目标应用程序的权限设置操作。
本公开实施例可以应用于终端侧，终端可以包括移动终端和PC(Personal Computer，个人计算机)端，移动终端可以为手机、PAD (Portable Android Device)等移动电子设备，PC端可以为台式电脑、笔记本电脑等电子设备。
目标应用程序是指移动终端中已经下载安装成功的多个应用程序中，当前需要进行应用权限设置的一个应用程序，例如，手机中已经安装的社交类APP、视频类APP、通讯类APP等，具体地，可以根据实际情况而定。
权限设置操作是指为目标应用程序设置应用权限的通知模式的操作。
在移动终端内的“设置”项可以预先设置权限管理界面，而在权限管理界面可以预先设置多个应用程序。例如，图2b示出了一种权限管理界面的示例的示意图。如图2b，所示，在该权限管理界面内显示有多个应用程序，如“58同城”、“阿里巴巴”、“爱奇艺”、“安居客”等应用程序，在用户点击某个应用程序时，即启动为该应用程序设置应用权限的权限通知模式，如在用户点击“安居客”应用程序时，即开始为“安居客”应用程序设置应用权限的权限通知模式，即将“安居客”应用程序作为目标应用程序，而用户执行的点击操作可以视为权限设置操作。
在具体实现中，权限设置操作还可以为其它形式的操作，如拖拽操作、双击操作等等，具体可以根据业务需求而定，本公开实施例对此不加以限制。
当然，APP在应用市场上申请上市时，需要填写要调用哪些权限类型，并填写调用权限的原因，应用市场方对APP的权限申请进行审核，用户下载APP后，APP将被禁止获取未申请的权限；而在用户层面，未申请的权限开关灰显不可点击，或是不显示，若APP想更新自己的权限类型，则需重新申请并进行审核。
可以理解地，上述示例仅是针对APP的应用权限的申请过程进行了描述，而在下述过程中为每个APP设置应用权限对应的权限通知模式时，均是针对该应用程序已授权的应用权限进行的设置。
在移动终端系统中可以预先设置权限设置操作对应的监测程序，通过该监测程序可以实时监测用户在对目标应用程序执行的权限设置操作。
如图2所示，本实施例的应用权限显示方法在接收针对目标应用程序对应的权限设置操作之后，执行步骤202。
在步骤202：响应于权限设置操作，展示与目标应用程序对应的权限设置界面；权限设置界面内显示有多个已授权应用权限。
权限设置界面是指用于为目标应用程序的一个或多个已授权应用权限设置权限通知模式的界面。例如，图2c示出了一种权限使用通知模式的示例的示意图，在权限设置界面可以展示多个已授权应用权限，如“存储”、“定位”、“电话”、“联系人”、“麦克风”、“耳机”等已授权应用权限，在用户为某个已授权应用权限设置权限通知模式时，可以点击该已授权应用权限，例如，用户点击“存储”时，即为“存储”应用权限设置权限通知模式，该点击操作可以视为权限设置操作。
当然，在用户为目标应用程序设置权限通知模式时，可以结合在先为同类型的应用程序设置了相应的应用权限，进行设置提示，例如，目标应用程序为A，与A为同类型的应用程序为B，而为B预先设置了每次使用电话权限时通知模式，那么在为A设置电话权限时，可以在“每次使用时通知”字段后增加“推荐”字段，即提示用户为B设置每次使用电话权限时进行通知的模式。
可以理解地，上述示例仅是为了更好地理解本公开实施例的应用权限显示方法而列举的示例，不作为对本公开实施例的唯一限制。
可以理解地，下述步骤中提及的目标应用权限为多个已授权应用权限中的一个应用权限。
如图2所示，本实施例的应用权限显示方法在响应于权限设置操作，展示与目标应用程序对应的权限设置界面之后，执行步骤203。
在步骤203，获取并保存用户为每个已授权应用权限设置的权限通知模式。
用户为每个已授权应用权限设置权限通知模式时，可以点击某个已授权应用权限，进而，展示权限通知模式设置界面。例如，图2a示出了一种应用权限设置界面的示例的示意图。如图2a所示，在点击某个已授权应用 权限时，可以显示如图2a所示界面，在该界面内显示有“禁止后不再询问”(即拒绝通知模式)、“智能通知”和“每次使用时通知”三种权限通知模式，其中，“智能通知”和“每次使用时通知”为允许通知模式，用户可以选择其中一种，作为为已授权应用权限设置的权限通知模式。
当然，在权限设置界面内，还可以展示有推荐的标识，如图2a所示，以向用户提示那种权限通知模式比较适用。
在用户为每个已授权应用权限设置相应的权限通知模式之后，可以对设置的权限通知模式进行保存，例如，可以在权限设置界面设置保存按钮，在用户点击保存按钮之后，即保存用户为已授权应用权限设置的权限通知模式。
如图2所示，本实施例的应用权限显示方法还包括步骤204：接收针对目标应用程序对应的目标应用权限的调用操作。
本实施例的应用权限显示方法还包括步骤205：响应于调用操作，在目标应用权限对应的权限通知模式为允许通知模式的情况下，将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面。
可以理解地，在本公开中，上述步骤204～步骤205的具体实施方式，与上述实施例一中步骤101～步骤102的具体实施方式相似，具体过程可参考实施例一的描述，在本实施例中不再加以赘述。
本实施例的应用权限显示方法还包括步骤206：接收针对目标应用程序的目标输入。
目标输入是指用于查看为目标应用程序设置的应用权限的输入操作，目标输入可以为拖拽操作、滑动操作等，如将目标应用程序从位置A拖拽至位置B的操作等等。
在具体实现中，目标输入还可以为其它操作，具体地，可以根据业务需求而定，本公开实施例对此不加以限制。
移动终端可以实时监测用户对目标应用程序执行的目标输入，并在接收到针对目标应用程序的目标输入之后，执行步骤207。
本实施例的应用权限显示方法还包括步骤207：响应于目标输入，根 据目标输入对应的输入参数，获取为目标应用程序设置的目标权限通知模式。
目前权限通知模式是指为目标应用程序对应的多个已授权应用权限设置的权限通知模式，例如，目标应用程序对应的已授权应用权限包括权限a和权限b，为权限a设置的权限通知模式为“使用时通知模式”，而为权限b设置的权限通知模式为“强制调用通知模式”时，目标权限通知模式即为“使用时通知模式”和“强制调用通知模式”。
在本公开中，输入参数是指目标输入所对应的参数，例如，在目标输入为拖拽操作时，拖拽参数可以为拖拽位置，即拖拽操作结束位置，在拖拽操作达到拖拽位置时，即触发获取为目标应用程序设置的目标权限通知模式，例如，参照图2f，示出了本公开第一方面的实施例提供的一种查看应用权限的示意图，如图2f所示，在显示界面内可以设置查看权限的窗口，该窗口可以视为查看为某个应用程序设置的权限通知模式的目标位置，在将某个应用程序拖拽至该窗口内时，即触发获取为该应用程序设置的权限通知模式。
可以理解地，上述示例仅是为了更好地理解本公开实施例的应用权限显示方法而列举的示例，不作为对本公开实施例的唯一限制。
如图2所示，本实施例的应用权限显示方法还包括步骤208：将目标权限通知模式展示于权限查看界面。
根据本实施例的方法，在接收到针对目标应用程序的目标输入时，可以响应目标输入，根据目标输入对应的输入参数，获取为目标应用程序设置的目标权限通知模式，并执行步骤208。
权限查看界面是指用于展示为目标应用程序设置的权限通知模式的界面。
在获取目标应用程序设置的目标权限通知模式之后，可以将为目标应用程序设置的目标权限通知模式展示于权限查看界面。例如，图2g示出了一种查看应用权限的示例的示意图。如图2f所示，在将“滴滴出行”拖拽至查看权限的窗口内时，可以获取为“滴滴出行”设置的目标权限通知 模式，在对“滴滴出行”对应的目标通知模式展示时，可以得到如图2g所示的界面。如图2g所示，对于“滴滴出行”应用程序设置的权限通知模式为：“存储”：允许通知；“电话”：允许通知；“定位”：允许通知；“联系人”、“麦克风”、“相机”均为不允许通知。
可以理解地，上述示例仅是为了更好地理解本公开实施例的应用权限显示方法而列举的示例，不作为对本公开实施例的唯一限制。
本实施例的应用权限显示方法还包括步骤209：接收针对目标应用权限的查看操作。
查看操作是指用于查看对目标应用权限的历史调用记录的操作。
查看操作可以是移动终端预先设置的操作，如双击APP、或点击指定查看历史调用记录的操作等等，具体地，可以根据业务需求而定，本公开实施例对此不加以限制。
在系统中可以预先设置查看操作对应的监控程序，通过该监控程序可以实时监测用户对目标应用权限执行的查看操作。
本实施例的应用权限显示方法在接收到针对目标应用权限的查看操作之后，执行步骤210。
在步骤210，响应于查看操作，获取目标应用权限对应的历史调用记录。
历史调用记录是指在目标应用程序运行时，调用目标应用权限的历史行为。
在接收到针对目标应用权限的查看操作之后，可以响应该查看操作，并获取目标应用程序运行过程中调用目标应用权限对应的历史行为，即历史调用记录。
本实施例的应用权限显示方法在获取目标应用权限对应的历史调用记录之后，执行步骤211。
在步骤211，将历史调用记录及目标应用程序关联展示于历史记录查看界面。
历史记录查看界面是指用于展示目标应用程序的历史运行过程中，调 用目标应用权限的历史行为的界面。
在获取目标应用权限对应的历史调用记录之后，可以将历史调用记录及目标应用程序关联展示于历史记录查看界面内。例如，图2h示出了一种应用权限调用历史记录的示例的示意图。如图2h所示，目标应用程序对目标应用权限调用的历史记录包括：“访问通话记录”，时间为：2019/04/27，14:51；“被禁止读取已安装应用信息”，时间为：2019/04/27，14:49；“被禁止读取已安装应用程序”，时间为：2019/04/27，14:49等等。
通过二者的关联，可以获知目标应用程序调用目标应用权限的行为数据，以执行后续步骤中检测是否存在强制调用行为的过程。
本实施例的应用权限显示方法在将历史调用记录及目标应用程序关联展示于历史记录查看界面之后，执行步骤212。
在步骤212，获取历史调用记录中存在的强制调用行为。
当然，在历史调用记录中还可以检测是否存在强制调用行为，如果存在强制调用行为，未通知给用户情况，可以获取历史调用记录中存在的强制调用行为。
本实施例的应用权限显示方法在获取历史调用记录存在的强制调用行为之后，执行步骤213。
在步骤213，生成并输出与强制调用行为对应的提醒信息。
在获取历史调用记录存在的强制调用行为之后，可以生成与强制调用行为对应的提醒信息，并向用户发送该提醒信息，以提示用户目标应用程序在具体什么时间，强制调用了目标应用权限，以使用户可以对目标应用权限的权限通知模式执行重新设置等操作，进一步避免了用户隐私的泄露。
本公开实施例提供的应用权限调用方法，除了具备上述实施例一提供的应用权限调用方法所具备的有益效果外，还可以对于强制调用应用权限的行为进行提醒，可以使用户明确哪些应用程序存在强制调用应用权限的行为，可以进一步避免用户隐私的泄露。
实施例三
图3示出了本公开第二方面的应用权限显示装置的实施例的结构示意图。如图3所示，该应用权限显示装置300可以包括如下模块：
调用操作接收模块301，用于接收针对目标应用程序对应的目标应用权限的调用操作；
应用权限展示模块302，用于响应于调用操作，在目标应用权限对应的权限通知模式为允许通知模式的情况下，将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面。
本公开实施例提供的应用权限显示装置，通过接收针对目标应用程序对应的目标应用权限的调用操作，响应于调用操作，在确定目标应用权限对应的权限通知模式为允许通知模式的情况下，将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面。本公开实施例通过根据对应用程序的应用权限设置的允许通知模式，在调用应用权限时，即将运行的应用程序、运行应用程序调用的应用权限以及调用详情进行展示，可以在应用权限被调用时即向用户展示应用权限的被调用的情况，提高了用户感知，并且，能够最大限度降低用户隐私暴露的问题。
实施例四
图4示出了本公开第二方面的应用权限显示装置的结构示意图。如图4所示，该应用权限显示装置400具体可以包括如下模块：
设置操作接收模块401，用于接收针对目标应用程序的权限设置操作；
设置界面展示模块402，用于响应于权限设置操作，展示与目标应用程序对应的权限设置界面；权限设置界面内显示有多个已授权应用权限，目标应用权限为多个已授权应用权限中的一个应用权限；
权限模式获取模块403，用于获取并保存用户为每个已授权应用权限设置的权限通知模式；其中，权限通知模式包括允许通知模式和拒绝通知模式中的任一种，允许通知模式包括使用时通知模式和强制调用通知模式；
调用操作接收模块404，用于接收针对目标应用程序对应的目标应用权限的调用操作；
通知模式检测模块405，用于响应于调用操作，在目标应用权限对应的权限通知模式为允许通知模式的情况下，将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面；
目标输入接收模块406，用于接收针对目标应用程序的目标输入；
目标模式获取模块407，用于响应于目标输入，根据目标输入对应的输入参数，获取为目标应用程序设置的目标权限通知模式；
目标模式展示模块408，用于将目标权限通知模式展示于权限查看界面；
查看操作接收模块409，用于接收针对目标应用权限的查看操作；
历史行为获取模块410，用于响应于查看操作，获取目标应用权限对应的历史调用记录；
历史行为展示模块411，用于将历史调用记录及目标应用程序关联展示于历史记录查看界面；
强制行为获取模块412，用于获取历史调用记录中存在的强制调用行为；
提醒信息生成模块413，用于生成并输出与强制调用行为对应的提醒信息。
本公开实施例提供的应用权限调用装置，除了具备上述实施例三提供的应用权限调用装置所具备的有益效果外，还可以对于强制调用应用权限的行为进行提醒，可以使用户明确哪些应用程序存在强制调用应用权限的行为，可以进一步避免用户隐私的泄露。
实施例五
本公开第三方面还提供一种移动终端，包括处理器，存储器，存储在存储器上并可在处理器上运行的计算机程序，该计算机程序被处理器执行时实现上述第一方面的应用权限显示方法的各个实施例的步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
图5示出了本公开第三方面的移动终端的实施例的结构框图。
如图5所示，该移动终端500包括但不限于：射频单元501、网络模块502、音频输出单元503、输入单元504、传感器505、显示单元506、用户输入单元507、接口单元508、存储器509、处理器510、以及电源511等部件。本领域技术人员可以理解，图5中示出的移动终端结构并不构成对移动终端的限定，移动终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。在本公开实施例中，移动终端包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
处理器510是移动终端的控制中心，利用各种接口和线路连接整个移动终端的各个部分，通过运行或执行存储在存储器509内的软件程序和/或模块，以及调用存储在存储器509内的数据，执行移动终端的各种功能和处理数据，从而对移动终端进行整体监控。处理器510可包括一个或多个处理单元；优选的，处理器510可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器510中。
在本实施例中，处理器510可用于控制用户输入单元507接收针对目标应用程序对应的目标应用权限的调用操作；响应于调用操作，在目标应用权限对应的权限通知模式为允许通知模式的情况下，控制显示单元506将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面。
在本公开实施例中，通过接收针对目标应用程序对应的目标应用权限的调用操作，响应于调用操作，在确定目标应用权限对应的权限通知模式为允许通知模式的情况下，将目标应用程序、目标应用权限和目标应用权限的调用信息关联展示于指定界面。本公开实施例通过根据应用程序的应用权限设置的允许通知模式，在调用应用权限时，即将运行的应用程序、运行应用程序调用的应用权限以及调用详情进行展示，可以在应用权限被 调用时即向用户展示应用权限的被调用的情况，提高了用户感知，并且，能够最大限度降低用户隐私暴露的问题。
应理解的是，本公开实施例中，射频单元501可用于收发信息或通话过程中，信号的接收和发送，具体的，将来自基站的下行数据接收后，给处理器510处理；另外，将上行的数据发送给基站。通常，射频单元501包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频单元501还可以通过无线通信系统与网络和其他设备通信。
移动终端通过网络模块502为用户提供了无线的宽带互联网访问，如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元503可以将射频单元501或网络模块502接收的或者在存储器509中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元503还可以提供与移动终端500执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收声音等等)。音频输出单元503包括扬声器、蜂鸣器以及受话器等。
输入单元504用于接收音频或视频信号。输入单元504可以包括图形处理器(Graphics Processing Unit，GPU)5041和麦克风5042，图形处理器5041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元506上。经图形处理器5041处理后的图像帧可以存储在存储器509(或其它存储介质)中或者经由射频单元501或网络模块502进行发送。麦克风5042可以接收声音，并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元501发送到移动通信基站的格式输出。
移动终端500还包括至少一种传感器505，比如光传感器、运动传感器以及其他传感器。具体地，光传感器包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板5061的亮度，接近传感器可在移动终端500移动到耳边时，关闭显示面板5061和/ 或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别移动终端姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；传感器505还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等，在此不再赘述。
显示单元506用于显示由用户输入的信息或提供给用户的信息。显示单元506可包括显示面板5061，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板5061。
用户输入单元507可用于接收输入的数字或字符信息，以及产生与移动终端的用户设置以及功能控制有关的键信号输入。具体地，用户输入单元507包括触控面板5071以及其他输入设备5072。触控面板5071，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板5071上或在触控面板5071附近的操作)。触控面板5071可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器510，接收处理器510发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板5071。除了触控面板5071，用户输入单元507还可以包括其他输入设备5072。具体地，其他输入设备5072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
进一步的，触控面板5071可覆盖在显示面板5061上，当触控面板5071检测到在其上或附近的触摸操作后，传送给处理器510以确定触摸事件的类型，随后处理器510根据触摸事件的类型在显示面板5061上提供相应的视觉输出。虽然在图5中，触控面板5071与显示面板5061是作为 两个独立的部件来实现移动终端的输入和输出功能，但是在某些实施例中，可以将触控面板5071与显示面板5061集成而实现移动终端的输入和输出功能，具体此处不做限定。
接口单元508为外部装置与移动终端500连接的接口。例如，外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元508可以用于接收来自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到移动终端500内的一个或多个元件或者可以用于在移动终端500和外部装置之间传输数据。
存储器509可用于存储软件程序以及各种数据。存储器509可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器509可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
在本实施例中，存储器509可存储计算机程序，该计算机程序被处理器510执行时实现上述第一方面的应用权限显示方法的各个实施例的步骤，在此不再赘述。
移动终端500还可以包括给各个部件供电的电源511(比如电池)，优选的，电源511可以通过电源管理系统与处理器510逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外，移动终端500包括一些未示出的功能模块，在此不再赘述。
本公开第四方面还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述第一方面的应用权限显示方法的各个实施例的步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。计算机可读存储介质的示例包括非暂态计算机 可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上面参考根据本公开的实施例的方法、装置(系统)或计算机程序产品的流程图和/或框图描述了本公开的各方面。应当理解，流程图和/或框图中的每个方框以及流程图和/或框图中各方框的组合可以由计算机程序指令实现。这些计算机程序指令可被提供给通用计算机、专用计算机、或其它可编程数据处理装置的处理器，以产生一种机器，使得经由计算机或其它可编程数据处理装置的处理器执行的这些指令使能对流程图和/或框图的一个或多个方框中指定的功能/动作的实现。这种处理器可以是但不限于是通用处理器、专用处理器、特殊应用处理器或者现场可编程逻辑阵列。还应理解，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，也可以由执行指定的功能或动作的专用的基于硬件的系统来实现，或者可以由专用硬件和计算机指令的组合来实现。
上面结合附图对本公开的实施例进行了描述，但是本公开并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本公开的启示下，在不脱离本公开宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本公开的保护之内。

Claims (10)

  1. 一种应用权限显示方法，包括：
    接收针对目标应用程序对应的目标应用权限的调用操作；
    响应于所述调用操作，在所述目标应用权限对应的权限通知模式为允许通知模式的情况下，将所述目标应用程序、所述目标应用权限和所述目标应用权限的调用信息关联展示于指定界面。
  2. 根据权利要求1所述的方法，其中，在所述接收针对目标应用程序对应的目标应用权限的调用操作之前，还包括：
    接收针对所述目标应用程序的权限设置操作；
    响应于所述权限设置操作，展示与所述目标应用程序对应的权限设置界面；所述权限设置界面内显示有多个已授权应用权限，所述目标应用权限为所述多个已授权应用权限中的一个应用权限；
    获取并保存用户为每个所述已授权应用权限设置的权限通知模式；
    其中，所述权限通知模式包括所述允许通知模式和拒绝通知模式中的任一种，所述允许通知模式包括使用时通知模式和强制调用通知模式。
  3. 根据权利要求2所述的方法，其中，在所述获取并保存用户为每个所述已授权应用权限设置的权限通知模式之后，还包括：
    接收针对所述目标应用程序的目标输入；
    响应于所述目标输入，根据所述目标输入对应的输入参数，获取为所述目标应用程序设置的目标权限通知模式；
    将所述目标权限通知模式展示于权限查看界面。
  4. 根据权利要求1所述的方法，其中，在所述将所述目标应用程序、所述目标应用权限和所述目标应用权限的调用信息关联展示于指定界面之后，还包括：
    接收针对所述目标应用权限的查看操作；
    响应于所述查看操作，获取所述目标应用权限对应的历史调用记录；
    将所述历史调用记录及所述目标应用程序关联展示于历史记录查看界面；
    获取所述历史调用记录中存在的强制调用行为；
    生成并输出与所述强制调用行为对应的提醒信息。
  5. 一种应用权限显示装置，包括：
    调用操作接收模块，用于接收针对目标应用程序对应的目标应用权限的调用操作；
    应用权限展示模块，用于响应于所述调用操作，在所述目标应用权限对应的权限通知模式为允许通知模式的情况下，将所述目标应用程序、所述目标应用权限和所述目标应用权限的调用信息关联展示于指定界面。
  6. 根据权利要求5所述的装置，其中，还包括：
    设置操作接收模块，用于接收针对所述目标应用程序的权限设置操作；
    设置界面展示模块，用于响应于所述权限设置操作，展示与所述目标应用程序对应的权限设置界面；所述权限设置界面内显示有多个已授权应用权限，所述目标应用权限为所述多个已授权应用权限中的一个应用权限；
    权限模式获取模块，用于获取并保存用户为每个所述已授权应用权限设置的权限通知模式；
    其中，所述权限通知模式包括所述允许通知模式和拒绝通知模式中的任一种，所述允许通知模式包括使用时通知模式和强制调用通知模式。
  7. 根据权利要求6所述的装置，其中，还包括：
    目标输入接收模块，用于接收针对所述目标应用程序的拖拽操作；
    目标模式获取模块，用于响应于所述目标输入，根据所述目标输入对应的输入参数，获取为所述目标应用程序设置的目标权限通知模式；
    目标模式展示模块，用于将所述目标权限通知模式展示于权限查看界面。
  8. 根据权利要求5所述的装置，其中，还包括：
    查看操作接收模块，用于接收针对所述目标应用权限的查看操作；
    历史行为获取模块，用于响应于所述查看操作，获取所述目标应用权限对应的历史调用记录；
    历史行为展示模块，用于将所述历史调用记录及所述目标应用程序关联展示于历史记录查看界面；
    强制行为获取模块，用于获取所述历史调用记录中存在的强制调用行为；
    提醒信息生成模块，用于生成并输出与所述强制调用行为对应的提醒信息。
  9. 一种移动终端，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至4中任一项所述的应用权限显示方法的步骤。
  10. 一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现如权利要求1至4中任一项所述的应用权限显示方法的步骤。
PCT/CN2020/109073 2019-08-29 2020-08-14 应用权限显示方法、装置、移动终端及存储介质 WO2021036811A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910820974.7 2019-08-29
CN201910820974.7A CN110674490B (zh) 2019-08-29 2019-08-29 应用权限显示方法、装置及移动终端

Publications (1)

Publication Number Publication Date
WO2021036811A1 true WO2021036811A1 (zh) 2021-03-04

Family

ID=69076645

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/109073 WO2021036811A1 (zh) 2019-08-29 2020-08-14 应用权限显示方法、装置、移动终端及存储介质

Country Status (2)

Country Link
CN (1) CN110674490B (zh)
WO (1) WO2021036811A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113268185A (zh) * 2021-05-31 2021-08-17 维沃移动通信（杭州）有限公司 信息提供方法、装置及电子设备

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110674490B (zh) * 2019-08-29 2022-03-15 维沃移动通信有限公司 应用权限显示方法、装置及移动终端
CN112199255A (zh) * 2020-10-15 2021-01-08 Oppo广东移动通信有限公司 权限使用监控方法、装置、设备及存储介质
CN113343304A (zh) * 2021-06-29 2021-09-03 挂号网（杭州）科技有限公司 一种权限申请方法、装置、电子设备及存储介质
CN116451264A (zh) * 2022-01-10 2023-07-18 华为技术有限公司 应用程序管理方法及相关装置
CN117667839A (zh) * 2022-08-31 2024-03-08 华为技术有限公司 一种文件管理、应用管理的方法和电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130347096A1 (en) * 2012-06-22 2013-12-26 Wistron Corp. Permission management method for applications, electronic device thereof, and computer readable medium
CN104732147A (zh) * 2015-04-13 2015-06-24 成都睿峰科技有限公司 一种应用程序处理方法
CN104732140A (zh) * 2015-04-13 2015-06-24 成都睿峰科技有限公司 一种程序数据处理方法
CN109669730A (zh) * 2018-12-26 2019-04-23 北京达佳互联信息技术有限公司 一种进程保活方法、装置、电子设备及介质
CN110674490A (zh) * 2019-08-29 2020-01-10 维沃移动通信有限公司 应用权限显示方法、装置及移动终端

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6051715B2 (ja) * 2012-09-14 2016-12-27 株式会社リコー 画像処理システムおよび権限判断方法
CN105677313A (zh) * 2015-11-06 2016-06-15 乐视移动智能信息技术（北京）有限公司 通知消息的显示方法、装置及终端设备
CN106228063A (zh) * 2016-07-27 2016-12-14 北京金山安全软件有限公司 辅助功能权限操控方法、装置及终端设备
CN108133124B (zh) * 2017-12-29 2020-09-08 上海连尚网络科技有限公司 一种用于应用程序获取系统权限方法及设备
CN109241765B (zh) * 2018-07-17 2022-06-17 奇酷互联网络科技（深圳）有限公司 移动终端和应用程序的权限管理方法、装置
CN109815678B (zh) * 2018-12-17 2020-09-01 维沃移动通信有限公司 一种权限配置方法及移动终端

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130347096A1 (en) * 2012-06-22 2013-12-26 Wistron Corp. Permission management method for applications, electronic device thereof, and computer readable medium
CN104732147A (zh) * 2015-04-13 2015-06-24 成都睿峰科技有限公司 一种应用程序处理方法
CN104732140A (zh) * 2015-04-13 2015-06-24 成都睿峰科技有限公司 一种程序数据处理方法
CN109669730A (zh) * 2018-12-26 2019-04-23 北京达佳互联信息技术有限公司 一种进程保活方法、装置、电子设备及介质
CN110674490A (zh) * 2019-08-29 2020-01-10 维沃移动通信有限公司 应用权限显示方法、装置及移动终端

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113268185A (zh) * 2021-05-31 2021-08-17 维沃移动通信（杭州）有限公司 信息提供方法、装置及电子设备
CN113268185B (zh) * 2021-05-31 2023-08-01 维沃移动通信（杭州）有限公司 信息提供方法、装置及电子设备

Also Published As

Publication number Publication date
CN110674490B (zh) 2022-03-15
CN110674490A (zh) 2020-01-10

Similar Documents

Publication Publication Date Title
WO2021036811A1 (zh) 应用权限显示方法、装置、移动终端及存储介质
US20220276909A1 (en) Screen projection control method and electronic device
WO2019154181A1 (zh) 显示控制方法及移动终端
US20220413670A1 (en) Content Sharing Method and Electronic Device
CN109889348B (zh) 一种图像分享方法及装置
WO2021017776A1 (zh) 信息处理方法及终端
WO2020020126A1 (zh) 信息处理方法及终端
WO2021083040A1 (zh) 消息查看方法及终端
WO2021121180A1 (zh) 信息处理方法及电子设备
WO2019174541A1 (zh) 移动终端的操作方法及移动终端
WO2020238463A1 (zh) 消息处理方法及终端
WO2019218862A1 (zh) 屏幕操作方法及移动终端
WO2021136138A1 (zh) 信息提示方法及电子设备
WO2020199987A1 (zh) 信息显示方法及移动终端
WO2020199783A1 (zh) 界面显示方法及终端设备
CN108681427B (zh) 一种访问权限控制的方法及终端设备
WO2021057290A1 (zh) 信息控制方法及电子设备
WO2021197265A1 (zh) 信息展示方法、电子设备及存储介质
CN111163260B (zh) 一种摄像头启动方法及电子设备
WO2021031717A1 (zh) 截屏方法及终端设备
WO2020220893A1 (zh) 截图方法及移动终端
WO2021143669A1 (zh) 一种获取配置信息的方法及电子设备
WO2021115220A1 (zh) 信息共享方法、电子设备及计算机可读存储介质
WO2020173316A1 (zh) 图像显示方法、终端和移动终端
WO2021121225A1 (zh) 应用程序安装方法及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20858350

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20858350

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 20858350

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 12/10/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20858350

Country of ref document: EP

Kind code of ref document: A1