Application-Sensitive Behavior Reminder Method, Related Device, and Communication System

Abstract

This application provides an application-sensitive behavior reminder method, related device, and communication system. When detecting that device permission is accessed by an application on a first electronic device or by a second electronic device, the first electronic device may display a sensitive behavior prompt indicating that the device permission is accessed on the status bar and / or control center interface. Additionally, the first electronic device may display a control used to manage the device permission in response to an operation on the sensitive behavior prompt displayed on the control center interface. According to the foregoing method, this may be convenient for a user to know and control the sensitive behavior of applications on the device and cross-device sensitive behavior.

Description

Technical Field

[0001] [Technical Field] This application relates to the field of terminal technologies, and in particular, to an application-sensitive behavior reminder method, related apparatus, and communication system.

Background Art

[0002] With the evolution of electronic devices, more applications (APPs) can be installed on electronic devices. An app can access one or more device permissions (such as camera permission, microphone permission, location permission, contact permission, and media and file permission) of an electronic device to obtain corresponding information. Information (such as images, audio, location, and contacts) obtained by an application by accessing device permissions may be the user's privacy information. The behavior of accessing device permissions is a sensitive behavior.

[0003] Therefore, an electronic device needs to monitor sensitive behaviors and provide a sensitive behavior reminder to the user, so that the user can know the specific device permissions accessed by the electronic device and the specific user information obtained by a specific application, and the user can manage the device permissions that the application can access based on the sensitive behavior of the application. This prevents the application from abusing device permissions and protects the user's privacy information.

Summary of the Invention

[0004] This application provides an application-sensitive behavior reminder method, related devices, and a communication system. According to this method, a sensitive behavior prompt indicating that device permission is accessed can be displayed on the status bar and / or control center interface of an electronic device to remind the user of the sensitive behavior of applications on the device and cross-device sensitive behavior. In addition, the user can further manage device permission based on the sensitive behavior prompt displayed on the control center interface. According to the foregoing method, this can be convenient for the user to know and control the sensitive behavior of applications on the device and cross-device sensitive behavior.

[0005] According to a first aspect, this application provides an application-sensitive behavior reminder method. A first electronic device may receive a first request from a second electronic device, and the first request is used to request access to the first device permission of the first electronic device. In response to the first request, the first electronic device may enable the second electronic device to access the first device permission and display a first icon in the status bar, and the first icon may indicate that the first device permission is accessed. The first electronic device receives a first operation. The first electronic device may display a first interface in response to the first operation, the first interface includes a first prompt, and the first prompt includes the first icon.

[0006] Referring to the first aspect, in some embodiments, when an application on the first electronic device detects access to the device permission of the first electronic device, the first electronic device may also display an accessed device permission icon in the status bar. In addition, in the first interface, in addition to the first icon, the first prompt may also include the accessed device permission icon.

[0007] From the foregoing method, it can be seen that when it is detected that device permission is accessed, the first electronic device may display a device permission icon in the status bar and / or control center interface. The visitors of the device permission may include applications on the first electronic device and devices other than the first electronic device, for example, the second electronic device. According to the foregoing method, this can be convenient for the user to intuitively know the sensitive behavior in the first electronic device based on the status bar or by calling the first interface. The user can know and control the sensitive behavior of the applications on the device and the cross-device sensitive behavior.

[0008] Referring to the first aspect, in some embodiments, the first electronic device receives a second operation on the first prompt. The first electronic device may display a first permission list in response to the second operation. The first permission list includes first information, and the first information indicates that the first device permission is accessed by the second electronic device. The second operation may be, for example, a tap operation or a touch operation on the first prompt.

[0009] From the foregoing embodiments, it can be seen that after displaying the first interface in response to the first operation, the first electronic device may display a first prompt on the first interface. The first prompt may include a device permission icon that is accessed to notify the user that one or more device permissions of the first electronic device are accessed. The first electronic device displays a first permission list in response to an operation on the first prompt. The first permission list may include detailed information regarding the access of the device permission of the first electronic device, for example, an identifier of the visitor who accesses the device permission.

[0010] Referring to the first aspect, in some embodiments, the first electronic device receives a third operation on the first information. The first electronic device may display a first control in response to the third operation, and the first control is used to manage the access of the second electronic device to the first device permission. The first control may be used to adjust the conditions for the second electronic device to access the first device permission. For example, the second electronic device may always be able to access the first device permission, or the first electronic device may need to query the user every time the second electronic device accesses the first device permission. Optionally, the first control may be used to prohibit the second electronic device from accessing the first device permission. The third operation may be, for example, a tap operation or a touch operation on the first information.

[0011] From the foregoing embodiments, it can be seen that the user can quickly manage the visitors of the device permission based on the sensitive behavior prompt (e.g., the first prompt) displayed on the first interface of the first electronic device. This reduces the abuse of device permissions and improves the security of user privacy information.

[0012] Referring to the first aspect, in some embodiments, after the first electronic device receives the first operation, the first electronic device may further query the access record of the first electronic device's access to the device permission during the first period to obtain the first access record. The first period is the period before the first operation is received, and the first access record includes the first access data for the second electronic device to access the first device permission. The first electronic device may display the first interface based on the first access record, and the first interface includes a first prompt. The first icon included in the first prompt is determined based on the first access data.

[0013] From the foregoing embodiments, it can be seen that after receiving the first operation to call the first interface, the first electronic device may obtain a sensitive behavior record in which the device permission of the first electronic device was accessed during the most recent period (i.e., the first period). Next, the first electronic device may display, on the first interface, a sensitive behavior prompt indicating the device permission accessed during the most recent period. In this way, in addition to the currently accessed device permission, the user can more quickly learn about the sensitive behaviors that occurred on the first electronic device during the most recent period.

[0014] Referring to the first aspect, in some embodiments, the first access record further includes access data for accessing K device permissions of the first electronic device, where K is a positive integer. The first prompt within the first interface further includes K icons, and the K icons respectively indicate that the K device permissions are accessed.

[0015] Referring to the first aspect, in some embodiments, the first icon and the K icons included in the first prompt are folded and displayed based on a first priority order. The first priority order indicates the priority order of the device permissions of the first electronic device. A device permission with a higher priority in the first priority order is indicated by an icon indicating that the device permission is accessed being displayed at a higher level in the first interface, and the icon displayed in the upper layer partially blocks the icon displayed in the lower layer. The first prompt further includes an identifier of the visitor of the device permission corresponding to the icon displayed at the highest level in the first prompt.

[0016] Referring to the first aspect, in some embodiments, the device permissions of the first electronic device include camera permission, microphone permission, location permission, contact permission, and media and file permission.

[0017] The device permission of the first electronic device can be classified into a first type of device permission and a second type of device permission. The first type of device permission may refer to a device permission whose access duration for one access can be a continuous period. For example, the first type of device permission may include a camera permission, a microphone permission, a location permission, etc. The second type of device permission may refer to a device permission whose access behavior for one access can be completed instantaneously. For example, the second type of device permission may include a contact permission, a media and file permission, etc.

[0018] When detecting that the first type of device permission is accessed, the first electronic device may display a first type of device permission icon in the status bar. The first device permission may be one first type of device permission. When the first electronic device receives a first operation, the second electronic device is still accessing the first device permission.

[0019] When receiving a first operation for invoking a first interface, the first electronic device may query an access record in which the first type of device permission is currently accessed and the second type of device permission is accessed in a recent period (for example, a first period). Then, the first electronic device may display a first prompt on the first interface based on the query result.

[0020] In other words, the K icons included in the first prompt may include a first type of device permission icon and may also include a second type of device permission icon.

[0021] Referring to the first aspect, in some embodiments, the first electronic device detects that the second electronic device has terminated access to the first device permission. The first electronic device cancels the display of the first icon in the status bar.

[0022] Referring to the first aspect, in some embodiments, before the first electronic device cancels the display of the first icon in the status bar, the first electronic device determines whether the first access duration for the second electronic device to access the first device permission exceeds the first duration. If it is determined that the first access duration for the second electronic device to access the first device permission exceeds the first duration, the first electronic device may directly cancel the display of the first icon in the status bar when the second electronic device finishes accessing the first device permission.

[0023] Referring to the first aspect, in some embodiments, the first electronic device detects that the second electronic device has finished accessing the first device permission. The first electronic device determines whether the first access duration for the second electronic device to access the first device permission exceeds the first duration. If it is determined that the first access duration does not exceed the first duration, the first electronic device determines a first extended duration based on the difference between the first access duration and the first duration. The first electronic device continues to display the first icon in the status bar during a second period, where the second period is a period within the first extended duration starting from the time when the second electronic device finishes accessing the first device permission.

[0024] Referring to the first aspect, in some embodiments, the first electronic device detects a re-access of the first device permission during a second period. The first electronic device continues to display a first icon in the status bar during the period of the re-access of the first device permission. The first electronic device determines whether a second access duration of the re-access of the first device permission exceeds a first duration. When it is determined that the second access duration exceeds the first duration, the first electronic device cancels the display of the first icon in the status bar when the re-access of the first device permission ends. Alternatively, when it is determined that the second access duration does not exceed the first duration, the first electronic device determines a second extended duration based on the difference between the second access duration and the first duration, and the first electronic device continues to display the first icon in the status bar during a third period, where the third period is a period within the second extended duration starting from the time when the re-access of the first device permission ends.

[0025] From the foregoing embodiments, when the access duration of the accessed device permission is excessively short, the first electronic device extends the display duration of the device permission icon after the permission visitor finishes the access, and continuously displays the device permission icon in the status bar for a certain period, so that the display duration of the device permission can reach a preset duration. It can be seen that the foregoing method can be used to avoid the frequent flashing of the device permission icon displayed in the status bar when the device permission is frequently accessed, prevent the first electronic device from frequently refreshing the device permission icon displayed in the status bar, improve the experience of the user browsing the status bar, and reduce the power consumption of the first electronic device for refreshing the device permission icon.

[0026] Referring to the first aspect, in some embodiments, the first electronic device receives a fourth operation. The first electronic device displays a second control in response to the fourth operation, and the second control is used to manage the access of the second electronic device to the device permission of the first electronic device. Alternatively, the first electronic device displays a third control in response to the fourth operation, and the third control is used to manage the access of different applications on the second electronic device to the device permission of the first electronic device.

[0027] From the foregoing embodiments, it can be seen that the user can manage cross-device sensitive behavior in the first electronic device and permit or prohibit another electronic device (e.g., the second electronic device) from accessing the device permission of the first electronic device. Alternatively, the user may separately perform permission management for each application on the electronic device connected to the first electronic device in order to adjust so that each application on the electronic device can access the device permission of the first electronic device. In other words, the user can authorize different applications on the electronic device to access different device permissions of the first electronic device based on requirements and privacy security considerations. Thereby, the user's usage requirements can be better met, and the security of the user privacy information can be improved.

[0028] Referring to the first aspect, in some embodiments, after the first electronic device receives a first operation, the first electronic device may further query an access record of accessing the device permission of another electronic device by the first electronic device during a first period to obtain a second access record during the first period. The first period is a period before the first operation is received, and the second access record includes access data of accessing the second device permission of the third electronic device by the first electronic device. The first interface further includes a second prompt, which is determined based on the second access record, and the second prompt indicates that the first electronic device accesses the second device permission of the third electronic device.

[0029] In a possible implementation, the first electronic device may find out which application on the first electronic device accesses the device permission of another electronic device. For example, the second record may include access data of accessing the second device permission of the third electronic device by the first application on the first electronic device. The second prompt may indicate that the first application on the first electronic device accesses the second device permission of the third electronic device.

[0030] The first electronic device may receive an operation on the second prompt and display a fourth control based on this operation. The fourth control may be used to manage the first application on the first electronic device that accesses the second device permission of the third electronic device.

[0031] From the foregoing embodiments, it can be seen that the user can further perform operations on the first electronic device to separately execute permission management for each application on the first electronic device. This adjusts for each application on the first electronic device to access the device permissions of another electronic device (for example, the third electronic device). In other words, the user can authorize different applications on the first electronic device to access different device permissions of another electronic device based on requirements and privacy security considerations. Thereby, the user's usage requirements can be better met, and the security of the user's privacy information can be improved.

[0032] Referring to the first aspect, in some embodiments, the first operation is an operation of sliding down from the upper right of the screen of the first electronic device, and the first interface is the control center interface of the first electronic device.

[0033] The foregoing operation for calling the first interface is simple, and it may be convenient for the user to quickly call the first interface (that is, the control center interface) to view the sensitive behavior of the first electronic device in the recent period.

[0034] According to a second aspect, the present application provides a communication system. The communication system may include a first electronic device and a second electronic device. The second electronic device may be configured to send a first request to the first electronic device, and the first request is used to request access to the first device permission of the first electronic device. The first electronic device may be configured to enable the second electronic device to access the first device permission based on the first request and display a first icon in the status bar, and the first icon may indicate that the first device permission is accessed. The first electronic device may be configured to receive a first operation and display a first interface based on the first operation, the first interface includes a first prompt, and the first prompt includes the first icon.

[0035] Enabling the first electronic device to allow the second electronic device to access the first device permission may include the first electronic device providing a service corresponding to the first device permission to the second electronic device. For example, if the first device permission is a camera permission, the first electronic device may provide a camera service to the second electronic device. The first electronic device may capture an image by using the camera and send the captured image to the second electronic device. The second electronic device may display the image received from the first electronic device.

[0036] Referring to the second aspect, in some embodiments, the first electronic device may be configured to monitor whether an application on the first electronic device accesses the device permission of the first electronic device. When it detects that an application on the first electronic device accesses the device permission of the first electronic device, the first electronic device may be configured to display an accessed device permission icon in the status bar. In addition, in the first interface, in addition to the first icon, the first prompt may also include the accessed device permission icon.

[0037] From the foregoing method, it can be seen that when detecting that the device permission is accessed, the first electronic device may display a device permission icon in the status bar and / or control center interface. The visitors of the device permission may include applications on the first electronic device and devices other than the first electronic device, for example, the second electronic device. According to the foregoing method, this may be convenient for the user to intuitively know the sensitive behavior in the first electronic device based on the status bar or by invoking the first interface. The user can know and control the sensitive behavior of the applications on the device and the cross-device sensitive behavior.

[0038] Referring to the second aspect, in some embodiments, the first electronic device may be configured to receive a second operation for the first prompt and display a first permission list based on the second operation. The first permission list includes first information, and the first information indicates that the first device permission is accessed by the second electronic device.

[0039] From the foregoing embodiments, it can be seen that after displaying the first interface in response to the first operation, the first electronic device may display a first prompt on the first interface. The first prompt may include the device permission icon being accessed to inform the user that one or more device permissions of the first electronic device are accessed. The first electronic device displays the first permission list in response to an operation on the first prompt. The first permission list may include detailed information regarding the access of the device permission of the first electronic device, for example, the identifier of the visitor accessing the device permission.

[0040] Referring to the second aspect, in some embodiments, the first electronic device may be configured to receive a third operation on the first information and display a first control based on the third operation, and the first control is used to manage the access of the second electronic device to the first device permission. The first control may be used to adjust the conditions for the second electronic device to access the first device permission. For example, the second electronic device may always be able to access the first device permission, or the first electronic device may need to query the user every time the second electronic device accesses the first device permission. Optionally, the first control may be used to prohibit the second electronic device from accessing the first device permission.

[0041] From the foregoing embodiments, it can be seen that the user can quickly manage the visitors of the device permission based on the sensitive behavior prompt (e.g., the first prompt) displayed on the first interface of the first electronic device. Thereby, the abuse of device permission is reduced and the security of user privacy information is improved.

[0042] Referring to the second aspect, in some embodiments, after receiving the first operation, the first electronic device may be configured to query the access record of the access of the first electronic device to the device permission in the first period to obtain the first access record, where the first period is the period before the first operation is received, and the first access record includes the first access data of the access of the second electronic device to the first device permission. The first electronic device may be configured to display a first interface based on the first access record, the first interface includes a first prompt, and the first icon included in the first prompt is determined based on the first access data.

[0043] From the foregoing embodiments, it can be seen that after receiving a first operation to invoke a first interface, the first electronic device may obtain a sensitive behavior record in which the device permission of the first electronic device was accessed during a recent period (i.e., the first period). Next, the first electronic device may display, on the first interface, a sensitive behavior prompt indicating the device permission accessed during the recent period. In this way, in addition to the currently accessed device permission, the user can more quickly learn about the sensitive behavior that occurred on the first electronic device during the recent period.

[0044] Referring to the second aspect, in some embodiments, the first access record further includes access data for accessing K device permissions of the first electronic device, where K is a positive integer. The first prompt within the first interface further includes K icons, and the K icons respectively indicate that the K device permissions are accessed.

[0045] Referring to the second aspect, in some embodiments, the first icon and the K icons included in the first prompt are folded and displayed based on a first priority order. The first priority order indicates the priority order of the device permissions of the first electronic device. A device permission with a higher priority in the first priority order means that the icon indicating that the device permission is accessed is displayed at a higher level in the first interface, and the icon displayed in the upper layer partially blocks the icon displayed in the lower layer. The first prompt further includes an identifier of the visitor of the device permission corresponding to the icon displayed at the highest level in the first prompt.

[0046] Referring to the second aspect, in some embodiments, the device permissions of the first electronic device include camera permission, microphone permission, location permission, contact permission, and media and file permission.

[0047] Referring to the second aspect, in some embodiments, the first electronic device may be configured to cancel the display of the first icon in the status bar when detecting that the second electronic device has terminated access to the first device permission.

[0048] Referring to the second aspect, in some embodiments, the first electronic device may be configured to determine whether a first access duration during which the second electronic device accesses the first device permission exceeds a first duration before canceling the display of the first icon in the status bar. If it is determined that the first access duration during which the second electronic device accesses the first device permission exceeds the first duration, the first electronic device may be configured to directly cancel the display of the first icon in the status bar when the second electronic device terminates access to the first device permission.

[0049] Referring to the second aspect, in some embodiments, the first electronic device may be configured to determine whether a first access duration during which the second electronic device accesses the first device permission exceeds a first duration when detecting that the second electronic device has terminated access to the first device permission. If it is determined that the first access duration does not exceed the first duration, the first electronic device may be configured to determine a first extended duration based on a difference between the first access duration and the first duration. The first electronic device continues to display the first icon in the status bar during a second period, which is a period within the first extended duration starting from the time when the second electronic device terminates access to the first device permission.

[0050] Referring to the second aspect, in some embodiments, when the first electronic device detects a re-access of the first device permission during the second period, the first electronic device may be configured to continuously display the first icon in the status bar during the period of the re-access of the first device permission. The first electronic device may be configured to determine whether a second access duration of the re-access of the first device permission exceeds the first duration. When it is determined that the second access duration exceeds the first duration, the first electronic device may be configured to cancel the display of the first icon in the status bar when the re-access of the first device permission ends. Alternatively, when it is determined that the second access duration does not exceed the first duration, the first electronic device may determine a second extended duration based on the difference between the second access duration and the first duration, and the first electronic device may be configured to continuously display the first icon in the status bar during a third period, where the third period is a period within the second extended duration starting from the time when the re-access of the first device permission ends.

[0051] From the foregoing embodiments, when the access duration of the accessed device permission is excessively short, the first electronic device extends the display duration of the device permission icon after the permission visitor finishes the access, and continuously displays the device permission icon in the status bar for a certain period, so that the display duration of the device permission can reach a preset duration. It can be seen that the foregoing method can be used to avoid the frequent flashing of the device permission icon displayed in the status bar when the device permission is frequently accessed, prevent the first electronic device from frequently refreshing the device permission icon displayed in the status bar, improve the experience of the user browsing the status bar, and reduce the power consumption of the first electronic device for refreshing the device permission icon.

[0052] Referring to the second aspect, in some embodiments, the first electronic device may be configured to receive a fourth operation and display a second control based on the fourth operation, and the second control is used to manage access of the second electronic device to the device permission of the first electronic device. Alternatively, the first electronic device may display a third control based on the fourth operation, and the third control is used to manage access of different applications on the second electronic device to the device permission of the first electronic device.

[0053] Referring to the second aspect, in some embodiments, the second electronic device may be configured to display a second icon in the status bar in the process of accessing the first device permission of the first electronic device, and the second icon may indicate that the first device permission is accessed. The second electronic device may be configured to receive a fifth operation and display a fifth interface based on the fifth operation, and the fifth interface may include a third prompt. The third prompt may include the second icon. The fifth operation may be, for example, a tap operation or a touch operation on the third prompt.

[0054] From the foregoing embodiments, it can be seen that when the second electronic device accesses the device permission of another electronic device, the second electronic device may also display a sensitive behavior prompt in the status bar or the fifth interface (for example, the control center interface) to notify the user of the sensitive behavior that the second electronic device accesses the device permission of another electronic device.

[0055] Referring to the second aspect, in some embodiments, the second electronic device may be configured to receive a sixth operation for a third prompt and display a second permission list based on the sixth operation, and the second permission list may include second information. The second information may indicate that the second electronic device accesses the first device permission within the first electronic device. The sixth operation may be, for example, a tap operation or a touch operation on the third prompt.

[0056] The second electronic device accessing the first device permission within the first electronic device may specifically be that the second application on the second electronic device accesses the first device permission within the first electronic device. The second information may include an identifier of the second application to inform the user that the second application on the second electronic device accesses the first device permission within the first electronic device.

[0057] Referring to the second aspect, in some embodiments, the second electronic device may be configured to receive a seventh operation for the second information and display a fifth control based on the seventh operation. The fifth control may be used to manage the permission for the second application on the second electronic device to access the first device Permission for access.

[0058] From the foregoing embodiments, it can be seen that the user may further perform operations on the second electronic device to separately execute permission management for each application on the second electronic device. This adjusts the access of each application on the second electronic device to the device permission of another electronic device (for example, the first electronic device). In other words, the user can approve the access of different applications on the second electronic device to different device permissions of another electronic device based on requirements and privacy security considerations. Thereby, the user's usage requirements can be better met, and the security of the user privacy information can be improved.

[0059] According to a third aspect, the present application provides an electronic device. The electronic device may include a screen, a memory, and one or more processors. The memory may be configured to store a computer program. The one or more processors may be configured to call the computer program, whereby the electronic device executes the method in any possible implementation form of the first aspect.

[0060] According to a fourth aspect, the present application provides a computer-readable storage medium including instructions. When the instructions are executed on an electronic device, the electronic device can execute the method in any possible implementation form of the first aspect.

[0061] According to a fifth aspect, the present application provides a computer program product. The computer program product may include computer instructions, and when the computer instructions are executed on an electronic device, the electronic device can execute the method in any possible implementation form of the first aspect.

[0062] According to a sixth aspect, the present application provides a chip. The chip is used in an electronic device. The chip includes one or more processors, and the processors are configured to call computer instructions, whereby the electronic device executes the method in any possible implementation form of the first aspect.

[0063] It can be understood that the electronic device provided in the third aspect, the computer-readable storage medium provided in the fourth aspect, the computer program product provided in the fifth aspect, and the chip provided in the sixth aspect are all configured to execute the method provided in the embodiments of the present application. Therefore, for the beneficial effects that can be achieved by the electronic device, the computer-readable storage medium, the computer program product, and the chip, reference may be made to the beneficial effects in the corresponding method. Details will not be described again in this specification.

Brief Description of the Drawings

[0064]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5A

Figure 5B

Figure 6A

Figure 6B

Figure 6C

Figure 6D

Figure 7A

Figure 7B

Figure 7C

Figure 8A

Figure 8B

Figure 8C

Figure 9A

Figure 9B

Figure 9C

Figure 10A

Figure 10B

Figure 10C

Figure 10D

Figure 10E

Figure 10F

Figure 10G

Figure 10H

Figure 10I

Figure 10J

Figure 10K

Figure 10L

Figure 11A

Figure 11B

Figure 11C

Figure 12A

Figure 12B

Figure 12C

Figure 13A

Figure 13B

Figure 13C

Figure 13D

Figure 13E

Figure 14A

Figure 14B

Figure 15A

Figure 15C

Figure 15D

Figure 15E

Figure 15F

Figure 16A

Figure 16B

Figure 16C

Figure 17A

Figure 17B

Figure 17C

Figure 17D

Figure 17E

Mode for Carrying Out the Invention

[0065] Hereinafter, with reference to the accompanying drawings in the embodiments of the present application, the technical solutions in the embodiments of the present application will be described. In the description of the embodiments of the present application, the terms used in the following embodiments are only intended to describe specific embodiments and are not intended to limit the present application. The singular terms "one", "the", "the preceding", "this", and "the one" used in the specification and the appended claims of the present application are intended to include expressions such as "one or more" unless otherwise specified clearly in the context. In the following embodiments of the present application, it should be further understood that "at least one" and "one or more" mean one or more (including two). The term "and / or" is used to describe the relationship between related objects and indicates that three relationships may exist. For example, A and / or B may indicate the case where only A exists, the case where both A and B exist, and the case where only B exists, where A and B may be singular or plural. The character " / " generally indicates an "or" relationship between related objects.

[0066] References to "an embodiment", "some embodiments", and the like described in this specification indicate that one or more embodiments of this application include the specific features, structures, or characteristics described with reference to the embodiment. Thus, descriptions such as "in one embodiment", "in some embodiments", "in some other embodiments", and "in other embodiments" that appear in different places in this specification do not necessarily refer to the same embodiment. Rather, these descriptions mean "one or more but not all of the embodiments" unless otherwise particularly emphasized. The terms "include", "have", and their variants all mean "include but are not limited to" unless otherwise particularly emphasized. "Connection" includes direct connection and indirect connection unless otherwise specified. "First" and "second" are for illustrative purposes only and should not be construed as indicating or implying the relative importance of the amount of the technical features shown.

[0067] In the embodiments of this application, terms such as "example", "for example" are used to give examples, illustrations, or explanations. Any embodiment or design method described as "example" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than another embodiment or design method. Exactly, the use of terms such as "example", "for example" is intended to present the relevant concepts in a specific way.

[0068] In the following embodiments of this application, the term "user interface (UI)" is a media interface for interaction and information exchange between an application (APP) or an operating system (OS) and a user, and realizes the conversion between the internal form of information and the form acceptable to the user. The user interface is source code written in a specific computer language, such as Java (registered trademark) or an extensible markup language (XML). The interface source code is parsed and rendered on an electronic device and finally presented as content that can be identified by the user. The user interface is usually represented in the form of a graphical user interface (GUI), which is a user interface related to computer operations and displayed in a graphical manner. The user interface can be visual interface elements, such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, or widgets displayed on the display of an electronic device.

[0069] This application provides an application-sensitive behavior reminder method. In this method, an electronic device can monitor access data for device permissions. The access data for device permissions can include data on access to device permissions by applications on the electronic device, and can further include data on access to the device permissions of the electronic device by another electronic device (i.e., an application on another electronic device). When detecting that a device permission is accessed, the electronic device can display a device permission icon in the status bar to notify the user that the device permission corresponding to the device permission icon has been accessed. When detecting that a device permission is accessed, the electronic device can further display a device permission icon in the control center interface to notify the user that the device permission corresponding to the device permission icon has been accessed. The control center interface can integrate controls with functions such as media playback control functions and shortcut switch (such as Bluetooth (registered trademark) switch and wireless local area network switch) functions. The electronic device can provide controls used to manage device permissions in response to operations on the device permission icon within the control center interface, whereby the user can manage the device permissions of the electronic device that applications on the electronic device can access, and the device permissions of the electronic device that another electronic device (or an application on another electronic device) can access.

[0070] From the foregoing method, when detecting that a device permission is accessed, the electronic device can display a device permission icon in the status bar and / or the control center interface, whereby the user can know and control the sensitive behavior of applications on the device and cross-device sensitive behavior.

[0071] In some embodiments, the device permissions of an electronic device may include a first type of device permission and a second type of device permission.

[0072] The first type of device permission may refer to a device permission where the access duration of one access can be a continuous period. That is, when an application makes a single access to the first type of device permission, the duration from when the application starts accessing the first type of device permission to when the application ends accessing the first type of device permission can be a continuous duration. The first type of device permission may include camera permission, microphone permission, location permission, etc. For example, when an application makes a single access to camera permission, the application may start accessing camera permission at time point t1 and end accessing camera permission at time point t2 in order to obtain the image data captured by the camera during the access duration (t1 - t2) of this access.

[0073] The second type of device permission may refer to a device permission where the access behavior of one access can be completed instantaneously. That is, the access behavior when an application makes a single access to the second type of device permission can be a separate action without considering the access start time point and the access end time point (that is, without considering the access duration). The second type of device permission may include contact permission, media and file permission, device information permission, call record permission, etc. For example, when an application makes a single access to contact permission, a request for obtaining contact data may be sent to obtain the contact data in the electronic device. Sending a request for obtaining contact data may be equivalent to the access behavior when the application accesses contact permission.

[0074] When detecting that the first type of device permission is accessed, the electronic device may display a device permission icon in the status bar. For example, when detecting that the camera permission is accessed, the electronic device may display a camera icon in the status bar to inform the user that all cameras are accessible. Further, in the process of accessing the first type of device permission, in response to an operation of opening the control center interface, the electronic device may display the control center interface and display an icon corresponding to the device permission (for example, a camera icon) on the control center interface. In addition, the electronic device may further query the access data of the second type of device permission within a preset period before the operation of opening the control center interface is received. When it is known that the second type of device permission has been accessed within the preset period, the electronic device may further display a device permission icon on the control center interface. For example, when it is known that the contact permission has been accessed within the preset period, in addition to the camera icon, the electronic device may further display a contact icon on the control center interface to inform the user that the contact permission has been accessed.

[0075] From the foregoing embodiments, in addition to displaying a camera icon, a microphone icon, and a location icon on the control center interface, it can be seen that the electronic device may further display a contact icon and a device permission icon of the second type of device permission, such as a media and file icon, on the control center interface. In this way, the user can more conveniently and intuitively know the access data of each device permission.

[0076] Note that one device permission can correspond to at least one service. When one device permission is granted to an application, the application can call the service corresponding to that device permission by accessing the device permission.

[0077] For example, the camera permission can correspond to the camera service. The camera service can be a service that captures image data by using the camera. When the application accesses the camera permission, the application can call the camera service to obtain image data.

[0078] In another example, the microphone permission can correspond to the microphone service. The microphone service can be a service that captures audio data by using the microphone. When the application accesses the microphone permission, the application can call the microphone service to obtain audio data.

[0079] In another example, the location permission can correspond to the location service. The location service can be a service that obtains location information by using a location information acquisition module (such as GPS). When the application accesses the location permission, the application can call the location service to obtain location information.

[0080] In another example, the contact permission can correspond to the contact service. The contact service can be a service that obtains contact information in an electronic device. When the application accesses the contact permission, the application can call the contact service to obtain contact information.

[0081] In another example, media and file permissions may correspond to media and file services. The media and file services may be services that obtain media file data (such as photos, videos, and audio) and other types of file data (such as documents on which text editing is performed) in an electronic device. When an application accesses media and file permissions, the application can call the media and file services to obtain media file data and other types of file data.

[0082] The sensitive behavior in this application may indicate the behavior of accessing the device permissions of the electronic device or the behavior of calling the service corresponding to the device permissions of the electronic device. The access parties for accessing the device permissions of the electronic device may include applications on the electronic device and electronic devices other than the electronic device. For example, a communication connection is established between an electronic device and another electronic device. The other electronic device may access the camera permission of the electronic device to activate the camera of the electronic device and obtain image data.

[0083] Hereinafter, the structure of the electronic device 100 in this application will be described.

[0084] FIG. 1 is a diagram of an example of the structure of an electronic device 100 according to an embodiment of this application.

[0085] As shown in FIG. 1, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headset jack 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, a subscriber identification module (SIM) card interface 195, etc.

[0086] It can be understood that the structure shown in this embodiment of the present application does not constitute a specific limitation on the electronic device 100. In some other embodiments of the present application, the electronic device 100 may include more or fewer components than those shown in the figure, some components may be combined, some components may be divided, or different component arrangements may be used. The components shown in the figure may be implemented by hardware, software, or a combination of software and hardware.

[0087] Processor 110 may include one or more processing units. For example, processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, a neural-network processing unit (NPU) and / or the like. Different processing units may be independent components or integrated into one or more processors.

[0088] The controller may be the central part and command center of the electronic device 100. The controller may generate an operation control signal based on an instruction operation code and a time series signal, and complete the control of instruction fetching and instruction execution.

[0089] The memory may be disposed within processor 110 and configured to store instructions and data. In some embodiments, the memory within processor 110 is a cache. The memory may store instructions or data used by or periodically used by processor 110. When processor 110 needs to reuse an instruction or data, the processor may directly call the instruction or data from the memory. This avoids repeated accesses, reduces the latency of processor 110, and improves system efficiency.

[0090] The USB interface 130 is an interface compliant with the USB standard specification. Specifically, it can be a mini USB interface, a micro USB interface, a USB type-C interface, etc. The USB interface 130 may be configured to connect to a charger to charge the electronic device 100, may be configured to transmit data between the electronic device 100 and a peripheral device, or may be configured to connect to a headset to play audio via the headset.

[0091] The charging management module 140 is configured to receive a charging input from a charger. The charger can be a wireless charger or a wired charger. The charging management module 140 supplies power to the electronic device via the power management module 141 while charging the battery 142.

[0092] The power management module 141 is configured to connect to the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives inputs from the battery 142 and / or the charging management module 140 and supplies power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, etc.

[0093] The wireless communication function of the electronic device 100 can be implemented via the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, the baseband processor, etc.

[0094] Antenna 1 and Antenna 2 are configured to receive and transmit electromagnetic wave signals. Each antenna within the electronic device 100 can be configured to cover one or more communication frequency bands. Different antennas can be multiplexed to improve antenna utilization. For example, Antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0095] The mobile communication module 150 is applied to the electronic device 100 and can provide a wireless communication solution including 2G / 3G / 4G / 5G, etc. The mobile communication module 150 can include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via Antenna 1, perform processing such as filtering or amplification on the received electromagnetic waves, and transmit the electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can further amplify the signal modulated by the modem processor and convert the signal into an electromagnetic wave for radiation via Antenna 1.

[0096] The wireless communication module 160 may provide a wireless communication solution applied to the electronic device 100, which includes a wireless local area network (WLAN) (e.g., a wireless fidelity (Wi-Fi) network), Bluetooth (BT), a global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) technology, and the like. The wireless communication module 160 may be one or more components that integrate at least one communication processor module. The wireless communication module 160 receives electromagnetic waves through the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may further receive signals transmitted from the processor 110, perform frequency modulation and amplification on the signals, and convert the signals into electromagnetic waves through the antenna 2 for radiation.

[0097] The electronic device 100 may implement a display function through a GPU, a display 194, an application processor, and the like. The GPU is a microprocessor for image processing and is connected to the display 194 and the application processor. The GPU is configured to execute mathematical and geometric calculations and render images.

[0098] The display 194 is configured to display images, videos, and the like. In some embodiments, the electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0099] The electronic device 100 may implement a shooting function via an ISP, a camera 193, a video codec, a GPU, a display 194, an application processor, etc.

[0100] The ISP is configured to process the data fed back by the camera 193. For example, during shooting, the shutter is pressed, and light is transmitted through the lens to the photosensitive element of the camera. The optical signal is converted into an electrical signal, and the photosensitive element of the camera transmits the electrical signal to the ISP for processing to convert the electrical signal into a visible image.

[0101] The camera 193 is configured to capture a still image or a video. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0102] The digital signal processor is configured to process digital signals and may process another digital signal in addition to the digital image signal. For example, when the electronic device 100 selects a frequency, the digital signal processor is configured to perform a Fourier transform on the frequency energy.

[0103] The NPU is a neural-network (NN) computing processor. The NPU can quickly process input information with reference to the structure of a biological neural network, such as the transmission mode between human brain nerve cells, and can continuously perform self-learning. Applications such as intelligent recognition of the electronic device 100, such as image recognition, face recognition, voice recognition, and text understanding, can be implemented via the NPU.

[0104] The external memory interface 120 can be used to connect to an external memory card, such as a micro SD card, to expand the storage capacity of the electronic device 100. External MemoryThe card communicates with the processor 110 via the external memory interface 120 in order to implement a data storage function. Files such as music and videos are stored in the external memory card, for example.

[0105] The internal memory 121 may be configured to store computer-executable program code. The executable program code includes instructions. The processor 110 executes the instructions stored in the internal memory 121 to perform various functional applications and data processing of the electronic device 100. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store an operating system, applications required by at least one function (e.g., an audio playback function or an image playback function), etc. The data storage area may store data created when the electronic device 100 is used (e.g., audio data or an address book), etc. In addition, the internal memory 121 may include a high-speed random access memory, or may include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory, or a universal flash storage (UFS).

[0106] The electronic device 100 may implement audio functions, such as music playback and recording, via an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headset jack 170D, an application processor, etc.

[0107] The audio module 170 is configured to convert digital audio information into an analog audio signal for output, and is also configured to convert an analog audio input into a digital audio signal. The audio module 170 may be configured to encode and decode audio signals. In some examples, the audio module 170 may be disposed within the processor 110, or some functional modules within the audio module 170 may be disposed within the processor 110. The speaker 170A, also referred to as a "loudspeaker", is configured to convert an audio electrical signal into an audio signal. The receiver 170B, also referred to as an "earpiece", is configured to convert an electrical audio signal into an audio signal. The microphone 170C, also referred to as a "mic", is configured to convert an audio signal into an electrical signal. The headset jack 170D is configured to connect to a wired headset.

[0108] The sensor module 180 may include a pressure sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, an optical proximity sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

[0109] The button 190 includes a power button, a volume button, and the like. The motor 191 may generate a vibration prompt. The indicator 192 may be an indicator light and may be configured to indicate a charging state and a power change, or may be configured to indicate a message, a missed call, a notification, and the like.

[0110] The SIM card interface 195 is configured to connect to a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to effect contact with or separation from the electronic device 100. The electronic device 100 may support one or N SIM card interfaces, where N is a positive integer greater than 1. The electronic device 100 interacts with a network via the SIM card to implement functions such as conversations and data communications. In some examples, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card is embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0111] The electronic device 100 may be an electronic device equipped with iOS (registered trademark), Android (registered trademark), Windows (registered trademark), Harmony (registered trademark) OS (Harmony (registered trademark) OS), or another operating system, such as a mobile phone, a tablet computer, a notebook computer, a smartwatch, or a smartband. The specific type of the electronic device 100 is not limited in this embodiment of the present application.

[0112] The software system of the electronic device 100 may use a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. In this embodiment of the present application, an Android (registered trademark) system having a layered architecture is used as an example to show the software structure of the electronic device 100.

[0113] Figure 2 is a block diagram of the software structure of the electronic device 100 according to this embodiment of the present application.

[0114] In a layered architecture, software is divided into several layers, and each layer has a clear role and task. The layers communicate with each other via software interfaces. In some embodiments, the Android (registered trademark) system is divided into four layers from top to bottom: an application layer, an application framework layer, an Android runtime and system libraries, and a kernel layer.

[0115] The application layer may include a series of application packages.

[0116] As shown in Figure 2, the application packages may include applications such as a camera, a gallery, a calendar, a browser, a map, an AA chat, a WLAN, Bluetooth (registered trademark), an e-mail, and a privacy indicator.

[0117] The privacy indicator may be used to obtain the access data of the device permissions of the electronic device 100 and display the device permission icons of the accessed device permissions on the control center interface based on the access data of the device permissions.

[0118] The application framework layer provides APIs and programming frameworks for applications in the application layer. The application framework layer includes some predefined functions.

[0119] As shown in Figure 2, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, an activity manager, etc.

[0120] The window manager is configured to manage window programs. The window manager can obtain the size of the display, determine whether there is a status bar, execute screen locking, take screenshots, and the like.

[0121] The content provider is configured to store and obtain data and enable the data to be accessed by an application. The data can include videos, images, audio, outgoing and incoming calls, browsing history and bookmarks, address books, and the like.

[0122] The view system includes visual controls such as controls used to display text and controls used to display images. The view system can be configured to build an application. The display interface can include one or more views. For example, a display interface including an SMS message notification icon can include a text display view and an image display view.

[0123] The phone manager is configured to provide communication functions for the electronic device 100, for example, manage call states (including answering, rejecting, etc.).

[0124] The resource manager provides various resources such as localized strings, icons, images, layout files, video files, etc. to the application.

[0125] The notification manager can be configured to enable an application to display notification information in the status bar or the drop-down notification bar and convey notification messages. The notification information may automatically disappear after a short pause without user interaction. For example, the notification manager is used to notify the completion of a download, issue a message notification, etc. Alternatively, the notification manager may be a notification that appears in the top status bar of the system in the form of a graph or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, it can display text information in the status bar, make an announcement, vibrate the electronic device, or blink the display light.

[0126] The activity manager is responsible for the management of activities, and is responsible for the start, switching, scheduling of each component in the system, and the management and scheduling of applications. The activity manager can be called by the upper-layer application to start the corresponding activity.

[0127] In some embodiments, the application framework may further include a status bar controller, a sensitive behavior reminder module, an application behavior recording module, a control center module, a device permission management service, and a device permission provisioning service.

[0128] The device permission provisioning service can be used to provide services corresponding to each device permission. For example, services that the device permission provisioning service can provide may include a camera service, a microphone service, a location service, a contacts service, a media and file service, etc. An application on the electronic device 100 or an electronic device other than the electronic device 100 may request the device permission provisioning service to invoke a service corresponding to the device permission. In a possible implementation, upon receiving a request to invoke a service, the device permission provisioning service may determine whether the service invoker has permission to invoke the service (i.e., whether the service invoker is authorized to access the device permission corresponding to the service). If it is determined that the service invoker has permission to invoke the service, the device permission provisioning service may provide the service to the service invoker. The method for determining whether the service invoker has permission to invoke the service is not limited in this embodiment of the present application.

[0129] The application behavior recording module may be configured to record the access data of the device permissions (i.e., sensitive behavior) of the electronic device 100. When a service provided by the device permission provisioning service is called, the device permission provisioning service may send a message to the application behavior recording module to notify the application behavior recording module of the data of the called service (i.e., the access data of the device permission). In a possible implementation, the application behavior recording module may be implemented by an application operation service (AppOpsService). AppOpsService provides a tracking and recording function. The electronic device 100 may record the access data of the device permissions of the electronic device 100 by using AppOpsService. The device permission provisioning service may notify the called data to AppOpsService by calling the startOp function.

[0130] The device permission management service may be used to listen for the access data of the device permissions from the application behavior recording module. In a possible implementation, the device permission management service may listen for the access data of the first type of device permissions (such as camera permission, microphone permission, and location permission, etc.) from the application behavior recording module. When any one of the first type of device permissions is accessed, the application behavior recording module may send a message to the device permission management service to notify the device permission management service of the access data of the first type of device permissions.

[0131] The device permission management service may be used to send a message to the sensitive behavior reminder module to notify the access data of the first type of device permissions when it obtains through listening that the first type of device permissions is accessed.

[0132] When the sensitive behavior reminder module receives a message containing access data for the first type of device permission, it may be configured to instruct the status bar controller to refresh the device permission icon displayed in the status bar.

[0133] The status bar controller may be configured to refresh the device permission icon displayed in the status bar based on an instruction from the sensitive behavior reminder module.

[0134] For example, when receiving a message indicating that access to the camera permission has started, the sensitive behavior reminder module may instruct the status bar controller to display a camera icon in the status bar. When receiving a message indicating that access to the camera permission has ended, the sensitive behavior reminder module may instruct the status bar controller to cancel the display of the camera icon in the status bar.

[0135] The control center module may be configured to manage the control center. The control center may integrate functions such as a media playback control function (e.g., a function to control music playback) and shortcut switches (e.g., a Bluetooth® switch, a wireless local area network switch, a camera switch, and a screen recording switch) functions. When detecting an operation to open the control center interface, the control center module may control the electronic device 100 to display the control center interface.

[0136] In the present application, when detecting an operation to open the control center interface, the control center module may send a message to the privacy indicator and instruct the privacy indicator to display a device permission icon in the control center interface.

[0137] The Android runtime includes kernel libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0138] The kernel libraries include two parts: functions that need to be called in the Java language and the Android kernel libraries.

[0139] The application layer and the application framework layer operate on the 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 configured to implement functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0140] The system libraries may include multiple functional modules, such as a surface manager, a media library, a 3D graphics processing library (e.g., OpenGL ES), and a 2D graphics engine (e.g., SGL).

[0141] The surface manager manages the display subsystem and is configured to provide the fusion of 2D layers and 3D layers for multiple applications.

[0142] The media library supports the playback and recording of multiple commonly used audio and video formats, as well as still image files. The media library may support multiple audio and video encoding formats, such as MPEG-4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0143] The three-dimensional graphics processing library is configured to implement three-dimensional graphics drawing, image rendering, composition, image layer processing, and the like.

[0144] The 2D graphics engine is a drawing engine for 2D drawing.

[0145] The kernel layer is a layer between hardware and software. The kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver.

[0146] It can be understood that the software modules shown in Figure 2 are merely examples for the description of this application and do not constitute limitations to this application. In some embodiments, the electronic device 100 may include more or fewer modules, may combine some modules, or may divide some modules.

[0147] From the foregoing embodiments, it can be seen that the application-sensitive behavior reminder method provided in this application is applicable to a communication system including a plurality of electronic devices. The sensitive behavior detected by the electronic device 100 may be executed by an application on the electronic device 100 or by an application on an electronic device other than the electronic device 100.

[0148] Hereinafter, a diagram of the architecture of the communication system 30 according to the embodiments of this application will be described.

[0149] Figure 3 is a diagram of the architecture of the communication system 30 according to an embodiment of this application.

[0150] As shown in FIG. 3, the communication system 30 may include a plurality of electronic devices such as the electronic device 100, the electronic device 200, the electronic device 201, the electronic device 202, and the electronic device 203. For the structures of the electronic devices 200 to 203, refer to the description of the structure of the electronic device 100 in the foregoing embodiments. Details will not be described again in this specification. Not limited to the electronic devices shown in FIG. 3, the communication system 30 may further include another type of electronic device, for example, a personal computer (PC), a desktop computer, a laptop computer, a handheld computer, an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a head unit, a game console, a treadmill, a cloud host / cloud server, or another intelligent wearable device, and may further include an Internet of Things (IoT) device, or a smart home device such as a smart water heater, a smart lamp, a smart air conditioner, a smart weighing scale, etc. The type of the electronic device is not limited in this application.

[0151] In some embodiments, the communication system 30 may also be referred to as a "super terminal". The "super terminal" means that the capabilities of a plurality of electronic devices are integrated by using distributed technology, stored in a virtual hardware resource pool, and managed, scheduled, and integrated in a unified manner based on service requirements to provide services externally, thereby enabling different electronic devices to implement fast connection, mutual assistance of capabilities, and resource sharing.

[0152] Communication connections can be established between all the electronic devices included in the communication system 30. For example, one electronic device and another electronic device within the communication system 30 can be electronic devices located within the same communication network (e.g., located within the same Wi-Fi network). Alternatively, one electronic device can be an electronic device whose login account and the login account of another electronic device are the same account (e.g., a Huawei account), or an electronic device whose login account and the login account of another electronic device belong to the same group (e.g., the same family account). Alternatively, one electronic device can be an electronic device that establishes a trust relationship with another electronic device in another way, for example, an electronic device paired via Bluetooth (registered trademark), or an electronic device connected to a hotspot shared by another electronic device. Alternatively, one electronic device can be an electronic device that has established a Wi-Fi P2P connection to another electronic device. The manner in which communication connections are established by the electronic devices included in the communication system 30 is not limited in this embodiment of the present application.

[0153] One electronic device within the communication system 30 can access the device permissions of another electronic device within the communication system 30.

[0154] For example, the electronic device 100 can access the camera permission of the electronic device 200 and call the camera service of the electronic device 200. In this way, the electronic device 100 can capture image data by using the camera of the electronic device 200.

[0155] The electronic device 100 can access the media and file permissions of the electronic device 201 and call the media and file services of the electronic device 201. In this way, the electronic device 100 can obtain data such as media files and other types of files stored in the electronic device 201.

[0156] The electronic device 100 can access the microphone permission of the electronic device 203 and call the microphone service of the electronic device 203. In this way, the electronic device 100 can capture audio data by using the microphone of the electronic device 203.

[0157] FIG. 4 is a diagram of another structure of an example of a communication system 30 according to an embodiment of the present application.

[0158] As shown in FIG. 4, the communication system 30 may include an electronic device 100, an electronic device 200, an electronic device 201, an electronic device 202, and the like. For the method of establishing a communication connection between the electronic devices included in the communication system 30, refer to the foregoing description shown in FIG. 3. Details will not be described again in this specification.

[0159] In some embodiments, the electronic device 100 may include apps such as Application 1, Application 2, and Application 3. The apps included in the electronic device 100 may be, for example, a camera application, a recorder application, and a browser application. The applications on the electronic device 100 are not limited in this embodiment of the present application. The electronic device 100 may further include a device permission provisioning service 410, an application behavior recording module 420, a behavior recording database 430, a device permission management service 440, a sensitive behavior reminder module 450, a status bar controller 460, a privacy indicator 470, and a control center module 480. The device permission provisioning service 410 may include services corresponding to the device permissions of the electronic device 100, such as a camera service 411, a microphone service 412, a location service 413, a contacts service 414, or a media and file service 415. The device permission provisioning service 410 may include even more services. This is not limited in the present application. Each application (such as Application 1, Application 2, and Application 3) in the electronic device 100 and other electronic devices (such as electronic device 200, electronic device 201, and electronic device 202) may access the device permissions of the electronic device 100 and call the services in the device permission provisioning service 410.

[0160] When receiving a request to call a service, the device permission provisioning service 410 provides the service invoked by the device permission provisioning service 410 to the service invoker, and sends a message to the application behavior recording module 420 to notify service call data. In a possible implementation form, application 1 requests to call the camera service, the camera service 411 provides the camera service to application 1, and sends a message to the application behavior recording module 420 to notify the call data of the camera service. For example, the call data of the camera service may include the identifier of the camera service invoker (i.e., the identifier of application 1), the time when the call of the camera service starts, the time when the call of the camera service ends, and the like.

[0161] The application behavior recording module 420 may store the received service call data. The application behavior recording module 420 may store the service call data in the behavior recording database 430.

[0162] The device permission management service 440 may listen to the service call data corresponding to the first type of device permission from the application behavior recording module 420. For example, the device permission management service 440 may listen to the call data of the camera service, the microphone service, and the location service from the application behavior recording module 420.

[0163] Sent by the device permission provisioning service 410 Camera When receiving the service call data of the service, the microphone service, and the location service, the application behavior recording module 420 may send the service call data to the device permission management service 440.

[0164] When receiving service call data, the device permission management service 440 may send the service call data to the sensitive behavior reminder module 450 so that the sensitive behavior reminder module 450 can refresh the call data of the camera service, the microphone service, and the location service.

[0165] Based on the refreshed call data of the camera service, the microphone service, and the location service, the sensitive behavior reminder module 450 may instruct the status bar controller 460 to refresh the device permission icon in the status bar.

[0166] In this specification, an example where application 1 calls the camera service in the electronic device 100 is used for illustration.

[0167] For example, application 1 requests to call the camera service. The camera service 411 may provide the camera service to application 1 so that application 1 can capture image data by using the camera of the electronic device 100. The camera service 411 may further send the call data of the camera service to the application behavior recording module 420. The call data of the camera service may include the identifier of application 1 and the time when application 1 starts the call of the camera service. The application behavior recording module 420 may send the call data of the camera service to the device permission management service 440. The device permission management service 440 may send the call data of the camera service to the sensitive behavior reminder module 450. The sensitive behavior reminder module 450 may store the call data of the camera service and may instruct the status bar controller 460 to display the camera icon in the status bar. In this way, it can notify the user that the camera permission is accessed and the camera of the electronic device 100 is called.

[0168] Furthermore, Application 1 terminates the call to the camera service. The camera service 411 may send the call termination data of the camera service to the application behavior recording module 420. The call termination data of the camera service may include the identifier of Application 1 and the time when Application 1 terminated the call to the camera service. The application behavior recording module 420 may send the call termination data of the camera service to the device permission management service 440. The device permission management service 440 may send the call termination data of the camera service to the sensitive behavior reminder module 450. The sensitive behavior reminder module 450 may store the call termination data of the camera service and may instruct the status bar controller 460 to cancel the display of the camera icon in the status bar.

[0169] The control center module 480 may be configured to manage the control center. When detecting an operation to open the control center interface, the control center module 480 may send a message to the privacy indicator 470 to instruct the privacy indicator 470 to refresh the device permission icon in the control center interface.

[0170] Upon receiving a message instructing to refresh the device permission icon in the control center interface from the control center module 480, the privacy indicator 470 may query the application behavior recording module 420 and the device permission management service 440 about the data displayed in the control center interface. The data displayed in the control center interface may include service call data corresponding to the device permission of the electronic device 100.

[0171] The privacy indicator 470 can obtain service call data corresponding to a second type of device permission of the electronic device 100 from the application behavior recording module 420, and can obtain service call data corresponding to a first type of device permission of the electronic device 100 from the device permission management service 440. The privacy indicator 470 can display, on the control center interface, a device permission icon for the second type of device permission being accessed based on the service call data corresponding to the second type of device permission. The privacy indicator 470 can display, on the control center interface, a device permission icon for the first type of device permission being accessed based on the service call data corresponding to the first type of device permission. In this way, the electronic device 100 can inform the user, on the control center interface, of the device permissions being accessed in the first type of device permission and the second type of device permission, and the visitors accessing the device permissions.

[0172] When detecting that a device permission is accessed from the communication system 30 shown in FIG. 4, the electronic device 100 can display a device permission icon on the status bar and / or the control center interface, whereby the user can know and control the sensitive behavior of the applications on the device and the cross-device sensitive behavior.

[0173] Based on the foregoing electronic device 100 and the foregoing communication system 30, some sensitive behavior reminder scenarios provided in the embodiments of the present application will be described below.

[0174] FIGS. 5A and 5B are diagrams of an example of the interface of the electronic device 100 when no sensitive behavior is currently occurring.

[0175] As shown in FIG. 5A, the electronic device 100 may display a user interface 510. The user interface 510 may be the home screen of the electronic device 100. The user interface 510 may include a status bar 511 and application icons of applications. For example, the application icons may include a recorder application icon 512, an AA chat application icon 513, a camera application icon 514, a browser application icon 515, and the like. The application icons may be used to trigger the electronic device 100 to start the application corresponding to the application icon.

[0176] The status bar 511 may include a signal strength indicator for a mobile communication signal, a signal strength indicator for a Wi-Fi signal, a battery status indicator, and a time indicator.

[0177] In some embodiments, when sensitive behavior is detected (i.e., when device permission is accessed), the electronic device 100 may display the device permission icon of the device permission accessed in the sensitive behavior in the status bar 511 to notify the user of the sensitive behavior occurring in the electronic device 100.

[0178] In a possible implementation, the electronic device 100 may display the device permission icon of the first type of device permission in the status bar 511 only when it detects that the first type of device permission is accessed, and the electronic device 100 may not display the device permission icon of the second type of device permission in the status bar 511 when it detects that the second type of device permission is accessed.

[0179] Authorized visitors are generally understood to continuously access the first type of device permission for a certain period when accessing the first type of device permission. That is, there are an access start time and an access end time. When the access to the first type of device permission starts, the electronic device 100 begins to display a device permission icon in the status bar 511, and when the access to the first type of device permission ends, the display of the device permission icon in the status bar 511 can be cancelled. It can be seen that during the process in which the first type of device permission is being accessed, the electronic device 100 can display the device permission icon in the status bar 511 in real time and notify the user that the first type of device permission is being accessed.

[0180] However, when the second type of device permission is accessed, the access behavior of the authorized visitor is usually a separate one-time action. When the electronic device 100 detects that the second type of device permission is accessed, if it displays a device permission icon in the status bar 511, the electronic device 100 can quickly cancel the display of the device permission icon after displaying the device permission icon of the second type of device in the status bar 511. If the user does not view the electronic device 100 in a timely manner, the user may miss the sensitive behavior reminder regarding the access to the second type of device. In addition, if the authorized visitor frequently accesses the second type of device permission, the icon corresponding to the device permission displayed in the status bar 511 by the electronic device 100 within the second type of device permission may frequently blink. It can be seen that the electronic device 100 displaying the device permission icon of the second type of device permission in the status bar 511 has a poor sensitive behavior reminder effect, high power consumption, and affects the user's screen viewing experience. Therefore, the electronic device 100 can display the device permission icon of the first type of device permission in the status bar 511 only when the first type of device permission is accessed. Permission After displaying the device permission icon of the second type of device in the status bar 511, the display of the device permission icon can be quickly cancelled. If the user does not view the electronic device 100 in a timely manner, the user may miss the sensitive behavior reminder regarding the access to the second type of device. In addition, if the authorized visitor frequently accesses the second type of device permission, the icon corresponding to the device permission displayed in the status bar 511 by the electronic device 100 within the second type of device permission may frequently blink. It can be seen that the electronic device 100 displaying the device permission icon of the second type of device permission in the status bar 511 has a poor sensitive behavior reminder effect, high power consumption, and affects the user's screen viewing experience. Therefore, the electronic device 100 can display the device permission icon of the first type of device permission in the status bar 511 only when the first type of device permission is accessed.

[0181] In response to an operation of opening the control center interface, the electronic device 100 may display a control center interface 520 as shown in FIG. 5B. The operation of opening the control center interface may be, for example, an operation of sliding down from the upper right of the screen of the electronic device 100 shown in FIG. 5A. The foregoing operation of opening the control center interface is not limited in the embodiments of the present application.

[0182] As shown in FIG. 5B, the control center interface 520 may include a music card 521, a WLAN card 522, a Bluetooth card 523, and a super terminal card 524. The music card 521 may include one or more controls (such as play control, pause control, previous song control, and next song control) used to control music playback. The WLAN card 522 may include a switch used to enable / disable the WLAN function. The Bluetooth card 523 may include a switch used to enable / disable Bluetooth. The super terminal card 524 may include device icons of one or more electronic devices. The one or more electronic devices may include electronic devices that have established a cooperative connection with the electronic device 100, or may include electronic devices detected by the electronic device 100 that have not established a cooperative connection. This is not limited in the embodiments of the present application. The device icons in the super terminal card 524 may be used to trigger the electronic device 100 to establish or disconnect a cooperative connection with the electronic device corresponding to the device icon. Establishing a cooperative connection between two electronic devices may indicate that one of the two electronic devices virtualizes the other electronic device and operates cooperatively using the capabilities of the other electronic device, thereby providing services to the user.

[0183] In some embodiments, in response to an operation of opening the control center interface, the electronic device 100 may query sensitive behavior within a preset period before receiving the operation of opening the control center interface. Based on the sensitive behavior within the preset period, the electronic device 100 may display a device permission icon of the accessed device permission in the sensitive behavior on the control center interface 520 to notify the user of the sensitive behavior occurring in the electronic device 100.

[0184] In a possible implementation, based on the sensitive behavior of accessing the first type of device permission, the electronic device 100 may display a device permission icon of the accessed first type of device permission on the control center interface 520, and based on the sensitive behavior of accessing the second type of device permission, the electronic device 100 may display a device permission icon of the accessed second type of device permission on the control center interface 520.

[0185] In addition to displaying a camera icon, a microphone icon, and a location icon on the control center interface 520, it can be seen that the electronic device 100 may further display a device permission icon of a second type of device permission, such as a contact icon and a media and file icon, on the control center interface 520. In this way, the user can more conveniently and intuitively know the sensitive behavior that has occurred on the electronic device 100 in the recent period.

[0186] FIGS. 6A to 6D are some diagrams of an example of a sensitive behavior reminder scenario.

[0187] As shown in FIG. 6A, the electronic device 100 may display a user interface 510. The user interface 510 may include a recorder application icon 512. In response to an operation on the recorder application icon 512, such as a touch operation, the electronic device 100 may display a user interface 610 shown in FIG. 6B. The user interface 610 may be a user interface of the recorder application.

[0188] As shown in FIG. 6B, the user interface 610 may include a recording start control 611. In response to an operation on the recording start control 611, the electronic device 100 may activate a microphone to capture audio data and may display a user interface 620 shown in FIG. 6C.

[0189] As shown in FIG. 6C, the user interface 620 may include a recording pause control 622 and a recording end control 623. The recording pause control 622 may be used to pause the recording. The recording end control 623 may be used to end the recording.

[0190] The user interface 620 may further include a microphone icon 621 displayed in the status bar. When an operation on the recording start control 611 is detected, the recorder application may request access to the microphone permission. When the recorder application determines that it has the microphone permission, the electronic device 100 may provide the microphone service to the recorder application. In this way, the recorder application may call the microphone service and capture audio data by using the microphone of the electronic device 100. The electronic device 100 may detect that the recorder application accesses the microphone permission and display the microphone icon 621 shown in FIG. 6C in the status bar. Specifically, the electronic device 100 may display the microphone icon 621 in the status bar from the time when the recorder application starts to call the microphone service (i.e., the time when the microphone starts to operate and captures audio data). The microphone icon 621 may remind the user of the sensitive behavior when the microphone is activated.

[0191] In response to an operation to open the control center interface shown in FIG. 6C, the electronic device 100 may display the control center interface 630 shown in FIG. 6D. The control center interface 630 may include a sensitive behavior prompt 632 and a microphone icon 631 displayed in the status bar. For the microphone icon 631, refer to the description of the microphone icon 621 shown in FIG. 6C. The sensitive behavior prompt 632 may include the microphone icon and the name of the recorder application, "Recorder".

[0192] In response to an operation to open the control center interface, the electronic device 100 may query sensitive behavior within a preset period before the operation to open the control center interface, and display a sensitive behavior prompt on the control center interface based on the found sensitive behavior. The preset period may be, for example, 5 seconds, 10 seconds, or 1 minute. For example, at time t1, the electronic device 100 receives an operation to open the control center interface. The electronic device 100 may query the access data of device permission in the 10 seconds before time t1.

[0193] The electronic device 100 may find that the recorder application accessed the microphone permission within a preset period before the operation to open the control center interface. In this case, the electronic device 100 may display a sensitive behavior prompt 632 as shown in FIG. 6D on the control center interface 630. The sensitive behavior prompt 632 may include a microphone icon and the name of the recorder application. In this way, based on the sensitive behavior prompt 632, the user can know that the microphone permission of the electronic device 100 has been accessed and the visitor is the recorder application.

[0194] In some embodiments, when an operation on the recording pause control 622 or recording end control 623 shown in FIG. 6C is detected, the recorder application may terminate the permission to access the microphone. The electronic device 100 may turn off the microphone to stop capturing audio data. When detecting that the recorder application has terminated the permission to access the microphone, the electronic device 100 may cancel the display of the microphone icon 621 shown in FIG. 6C in the status bar.

[0195] When the control center interface 630 is displayed, it should be noted that both the sensitive behavior prompt (e.g., sensitive behavior prompt 632) and the device permission icon (e.g., microphone icon 631) displayed in the status bar can be in a frozen state. That is, the sensitive behavior prompt 632 and the microphone icon 631 can be left unchanged without modification. For example, when the control center interface 520 is displayed, even if the electronic device 100 detects that the recorder application has terminated permission to access the microphone, the microphone icon 631 and the sensitive behavior prompt 632 can continue to be continuously displayed. Further, when detecting an operation to close the control center interface 630, the electronic device 100 can cancel the display of the microphone icon 621 shown in FIG. 6C in the status bar included in the user interface displayed after the control center interface 630 is closed. In another example, when the control center interface 630 is displayed, even if the electronic device 100 detects that the camera permission is accessed, the microphone icon 631 and the sensitive behavior prompt 632 can continue to be continuously displayed, the camera icon is not added to the status bar, and a sensitive behavior prompt indicating that the camera permission is accessed is not added to the control center interface 630. Further, when detecting an operation to close the control center interface 630, the electronic device 100 can display the camera icon in the status bar included in the user interface displayed after the control center interface 630 is closed to remind the user that the camera permission has been accessed.

[0196] FIGS. 7A - 7C are some other figures of an example of a sensitive behavior reminder scenario.

[0197] As shown in FIG. 7A, the electronic device 100 may display a user interface 510. The user interface 510 may include an AA chat application icon 513. In response to an operation on the AA chat application icon 513, the electronic device 100 may start the AA chat application. The AA chat application can provide a video call function. In response to an operation to start the video call function, the electronic device 100 may display a user interface 710 as shown in FIG. 7B.

[0198] As shown in FIG. 7B, the user interface 710 may include a microphone icon 711 and a camera icon 712 displayed in the status bar. When it is detected that the video call function is started, the AA chat application may request permission to access the camera and the microphone. When the AA chat application determines that it has camera permission and microphone permission, the electronic device 100 may provide the AA chat application with a camera service and a microphone service. In this way, the AA chat application can call for camera permission and microphone permission, capture an image by using the camera of the electronic device 100, and capture audio data by using the microphone of the electronic device 100. The electronic device 100 may detect that the AA chat application accesses the camera permission and the microphone permission, and may display the microphone icon 711 and the camera icon 712 as shown in FIG. 7B. The microphone icon 711 may remind the user of the sensitive behavior when the microphone is activated. The camera icon 712 may remind the user of the sensitive behavior when the camera is activated.

[0199] In response to an operation to open the control center interface shown in FIG. 7B, the electronic device 100 may display a control center interface 720 as shown in FIG. 7C.

[0200] As shown in FIG. 7C, the control center interface 720 may include a sensitive behavior prompt 723, a microphone icon 721 and a camera icon 722 displayed on the status bar. For the microphone icon 721 and the camera icon 722, refer to the descriptions of the microphone icon 711 and the camera icon 712 shown in FIG. 7B respectively. The sensitive behavior prompt 723 may include a camera icon, a microphone icon, and the name of the AA chat application, "AA Chat". In the sensitive behavior prompt 723, the camera icon and the microphone icon may be displayed in a folded manner. For example, the camera icon may be displayed on top of the microphone icon and may partially block the microphone icon. The application name displayed in the sensitive behavior prompt 723 may be the name of the application that accesses the device permissions corresponding to the camera icon and the microphone icon included in the sensitive behavior prompt 723.

[0201] From the foregoing embodiments, it can be seen that in response to an operation to open the control center interface, the electronic device 100 may query for sensitive behavior within a preset period before the operation to open the control center interface, and display a sensitive behavior prompt on the control center interface based on the found sensitive behavior. From FIG. 7B, it can be seen that the electronic device 100 receives an operation to open the control center interface in the process where the AA chat application accesses the camera permission and the microphone permission. In this case, the electronic device 100 may find that the AA chat application has accessed the camera permission and the microphone permission within a preset period before the operation to open the control center interface. The electronic device 100 may display a sensitive behavior prompt 723 shown in FIG. 7C on the control center interface 720. In this way, based on the sensitive behavior prompt 723, the user can know that the microphone permission and the camera permission of the electronic device 100 have been accessed and that the visitor is the AA chat application.

[0202] In some embodiments, when an operation to end a video call is detected, the AA chat application may end access to the microphone permission and the camera permission. The electronic device 100 may turn off the camera and the microphone to stop capturing image and audio data. When detecting that the AA chat application has ended permission to access the microphone and the camera, the electronic device 100 may cancel the display of the microphone icon 711 and the camera icon 712 shown in FIG. 7B in the status bar.

[0203] In some embodiments, when querying sensitive behavior within a preset period before the operation of opening the control center interface, the electronic device 100 finds that a plurality of device permissions are accessed. The electronic device 100 may display a sensitive behavior prompt including an icon corresponding to the device permission among the plurality of device permissions on the control center interface. Accordingly, the user can conveniently know which device permissions of the electronic device 100 have been accessed in the recent period.

[0204] In a possible implementation form, when displaying a sensitive behavior prompt including icons corresponding to multiple device permissions on the control center interface, the electronic device 100 may fold and display the icons corresponding to the multiple device permissions. For example, the electronic device 100 may fold and display the icons corresponding to the device permissions according to a preset permission priority. The electronic device 100 may display the device permission icon of the device permission with the highest permission priority at the highest level and display the device permission icon of the device permission with the lowest permission priority at the lowest level. The icon displayed in the upper layer corresponding to the device permission may partially block the icon displayed in the lower layer corresponding to the device permission. For example, the permission priorities sorted in descending order may be camera permission > microphone permission > location permission > media and file permission > contact permission. When finding sensitive behaviors accessed to the camera permission, microphone permission, media and file permission, and contact permission within a preset period before the operation of opening the control center interface, the electronic device 100 may display a sensitive behavior prompt on the control center interface. The sensitive behavior prompt may include a folded and displayed camera icon, microphone icon, media and file icon, and contact icon. According to the aforementioned preset permission priority order, the electronic device 100 sequentially displays the camera icon, microphone icon, media and file icon, and contact icon based on the display level from top to bottom. The camera icon is above the microphone icon and partially blocks the microphone icon. The microphone icon is above the media and file icon and may partially block the media and file icon. The media and file icon is above the contact icon and may partially block the contact icon.

[0205] The foregoing permission priorities are merely examples for the purpose of explanation in the embodiments of the present application and do not constitute a limitation to the present application. When it is known that multiple device permissions are accessed, the electronic device 100 may further present an icon corresponding to the device permission among the multiple accessed device permissions in another display manner to notify the user of the sensitive behavior occurring in the electronic device 100.

[0206] In some embodiments, when displaying the sensitive behavior prompt on the control center interface, the electronic device 100 may further provide the name of the permission visitor. That is, the sensitive behavior prompt may further include the name of the permission visitor. When the permission visitor is an application on the electronic device 100, the electronic device 100 may display the name of the application. When the permission visitor is an electronic device other than the electronic device 100, the electronic device 100 may display the name of the electronic device accessing the device permission.

[0207] In a possible implementation, the electronic device 100 finds that a plurality of device permissions have been accessed within a preset period before the operation of opening the control center interface. If the permission visitors of the plurality of device permissions are the same, for example, if all are Application 1 within the electronic device 100, the electronic device 100 may display a sensitive behavior prompt on the control center interface. The sensitive behavior prompt may include an icon corresponding to the device permission among the plurality of device permissions and the name of Application 1. Alternatively, if the permission visitors of the plurality of device permissions are different, for example, if the permission visitors of the plurality of device permissions include Application 1, Application 2, and the electronic device 200, the electronic device 100 may display a sensitive behavior prompt on the control center interface. The sensitive behavior prompt may correspond to the device permission among the plurality of device permissions and may include an icon that is folded and displayed and the name of the permission visitor who accesses the device permission with the highest permission priority among the plurality of device permissions. For example, the electronic device 100 finds sensitive behaviors that have accessed the camera permission, microphone permission, media and file permission, and contact permission within a preset period before the operation of opening the control center interface. The visitor of the camera permission is the electronic device 200. The electronic device 100 may display a sensitive behavior prompt on the control center interface. The sensitive behavior prompt may include a camera icon, a microphone icon, a media and file icon, and a contact icon, and may further include the name of the visitor who has the camera permission (i.e., the name of the electronic device 200). The camera icon, the microphone icon, the media and file icon, and the contact icon may be displayed in a folded manner, and the camera icon is displayed at the highest level.

[0208] As can be seen from the scenarios shown in FIGS. 7A to 7C, when it is known that multiple device permissions are accessed, the electronic device 100 can display a sensitive behavior prompt used to notify that multiple device permissions are accessed on the control center interface. The sensitive behavior prompt may further include the name of the permission visitor. In this way, the user can quickly know the sensitive behavior in the electronic device 100.

[0209] FIGS. 8A to 8C are some other views of an example of the sensitive behavior reminder scenario.

[0210] In this specification, in the process of the AA chat application accessing the camera permission and microphone permission of the electronic device 100, an example where the electronic device 100 receives an operation to open the control center interface is still used for the purpose of explanation.

[0211] As shown in FIG. 8A, in response to an operation to open the control center interface, the electronic device 100 may display a control center interface 810. The control center interface 810 may include a sensitive behavior prompt 813, a microphone icon 811 and a camera icon 812 displayed in the status bar. The microphone icon 811 and the camera icon 812 may respectively indicate that the microphone permission and the camera permission are accessed when the electronic device 100 receives an operation to open the control center interface. The sensitive behavior prompt 813 may include a folded camera icon, a microphone icon, a media and file icon, and a contact icon, and the name of the visitor of the camera permission (for example, the name of the AA chat application "AA Chat"). For the sensitive behavior prompt 813, refer to the description of the sensitive behavior prompt 723 shown in FIG. 7C.

[0212] In some embodiments, in response to an operation to open the control center interface, the electronic device 100 may query whether a first type of device permission is accessed within a preset period during which the control center interface is open. If it is found that the first type of device permission is accessed, the electronic device 100 may query whether a second type of device permission is accessed within the preset period. In other words, based on the fact that the sensitive behavior prompt displayed on the control center interface includes the device permission icon of the first type of device permission, the electronic device 100 may present the device permission icon of the second type of device permission to be accessed in the sensitive behavior prompt. If it is found that the first type of device permission is not accessed within the preset period, the electronic device 100 may not need to display the sensitive behavior prompt on the control center interface.

[0213] In response to an operation on the sensitive behavior prompt 813, for example, a tap operation, the electronic device 100 may display the permission prompt box 820 shown in FIG. 8B. The permission prompt box 820 may display specific cases where the device permission indicated by the sensitive behavior prompt 813 is accessed.

[0214] For example, the sensitive behavior prompt 813 may indicate that camera permission, microphone permission, media and file permission, and contact permission are being accessed. The permission prompt box 820 may display specific cases where camera permission, microphone permission, media and file permission, and contact permission are accessed. The permission prompt box 820 may include permission prompt information 821, permission prompt information 822, permission prompt information 823, and permission prompt information 824. The permission prompt information 821 may indicate that the AA chat application is accessing camera permission. The permission prompt information 822 may indicate that the AA chat application is accessing microphone permission. The permission prompt information 823 may indicate that the email application has recently accessed media and file permission. The permission prompt information 824 may indicate that the browser application has recently accessed contact permission.

[0215] The permission prompt box 820 may further include a "More" control 825. The "More" control 825 may be used to view more records of sensitive behavior in the electronic device 100.

[0216] In some embodiments, in response to an operation on the sensitive behavior prompt 813, such as a tap operation, the electronic device 100 may further inquire whether the authorized visitor has terminated the access of one or more devices in the first type of device permission. If it is found that the authorized visitor is still accessing the first type of device permission, the electronic device 100 may display the text identifier "Accessing" in the permission prompt box 820 shown in FIG. 8B to indicate that the first type of device permission being accessed is in an access state. Alternatively, if it is found that the authorized visitor has terminated the access to the first type of device permission, the electronic device 100 may display the text identifier "Recently Accessed" in the permission prompt box 820 shown in FIG. 8B to indicate that the first type of device permission being accessed was recently accessed but is now access-terminated.

[0217] When an operation to open the control center interface is received, it can be understood that the authorized visitor may be accessing the first type of device permission (such as camera permission and microphone permission). However, in the process of displaying the control center interface, the authorized visitor may terminate the access to the first type of device permission. When an operation on the sensitive behavior prompt 813 is received, the authorized visitor may still access the first type of device permission or terminate the access to the first type of device permission. Based on the access data of the first type of device permission found when an operation on the sensitive behavior prompt 813 is received, the electronic device 100 may determine whether to display "Accessing" or "Recently Accessed" in the permission prompt box 820 shown in FIG. 8B.

[0218] For example, upon receiving an operation on the sensitive behavior prompt 813, the electronic device 100 may inquire whether the AA chat application still has access to the camera permission and the microphone permission. If it is found that the AA chat application still has access to the camera permission and the microphone permission, the electronic device 100 may display the text identifier "Accessing" as shown in FIG. 8B in the permission prompt information 821 and the permission prompt information 822. Alternatively, if it is found that the AA chat application has terminated access to the camera permission and the microphone permission, the electronic device 100 may display "Accessing" in the permission prompt information 821 and the permission prompt information 822 shown in FIG. 8B as the text identifier "Recently Accessed".

[0219] In some embodiments, the permission prompt information within the permission prompt box 820 may be used to trigger the electronic device 100 to display a device permission management interface so that the user can manage device permissions.

[0220] As shown in FIG. 8B, in response to an operation on the permission prompt information 824, the electronic device 100 may display the user interface 830 shown in FIG. 8C.

[0221] As shown in FIG. 8C, the user interface 830 may include a browser application icon 831, a browser application name 832, and a permission management box 833. The permission management box 833 may include an "While using the application" control 833A, an "Always" control 833B, and a "Never" control 833C. The "While using the application" control 833A may be used to adjust the conditions for the browser application to access the contact permission. For example, when the "While using the application" control 833A is selected, the electronic device 100 may enable the browser application to access the contact permission and obtain contact information only while running in the foreground. The "Always" control 833B may be used to adjust the conditions for the browser application to access the contact permission, and may enable the browser application to access the contact permission under any conditions. The "Never" control 833C may be used to prohibit the browser application from accessing the contact permission.

[0222] From the foregoing scenarios shown in FIGS. 8A through 8C, it can be seen that the user can quickly know which device permissions of the electronic device 100 are accessed by opening the control center interface. The device permissions accessed may include a first type of device permissions such as camera permission, microphone permission, and location permission, contact permission, and media A ohIt may further include a second type of device permission such as a call file permission. In addition, based on the sensitive behavior prompt in the control center interface, the user can more quickly see the specific situations in which each device permission is accessed (for example, who the permitted visitor is, and whether the permission has been recently accessed or is being accessed). In addition, based on the sensitive behavior prompt in the control center interface, the user can quickly manage the permitted visitors and adjust the conditions for the device permission visitors to access the device permission. This can help the user conveniently and quickly manage the device permission, reduce the abuse of the device permission, and improve the security of the user privacy information.

[0223] Figures 9A-9C are some other figures of an example of a sensitive behavior reminder scenario.

[0224] In this specification, an example of the electronic device 100 receiving an operation to open the control center interface is used to illustrate the process in which the camera application accesses the camera permission of the electronic device 100, and the browser application and the map application access the location permission of the electronic device 100.

[0225] As shown in FIG. 9A, in response to an operation of opening the control center interface, the electronic device 100 may display the control center interface 910. The control center interface 910 may include a sensitive behavior prompt 913, a location icon 911 and a camera icon 912 displayed in the status bar. The location icon 911 and the camera icon 912 may respectively indicate that location permission and camera permission are accessed when the electronic device 100 receives an operation of opening the control center interface. The sensitive behavior prompt 913 may include a folded camera icon, a location icon, a media and file icon, and a contact icon, and the name of the visitor to the camera permission (for example, the name of the camera application "Camera"). For the sensitive behavior prompt 913, refer to the description of the sensitive behavior prompt 723 shown in FIG. 7C.

[0226] In response to an operation on the sensitive behavior prompt 913, for example, a tap operation, the electronic device 100 may display the permission prompt box 920 shown in FIG. 9B.

[0227] As shown in FIG. 9B, the permission prompt box 920 may include permission prompt information 921, permission prompt information 922, permission prompt information 923, and permission prompt information 924. The permission prompt information 921 may indicate that the camera application has recently accessed the camera permission. The permission prompt information 922 may indicate that a plurality of permission visitors such as a browser application are accessing the location permission. The permission prompt information 923 may indicate that the email application has recently accessed the media and file permission. The permission prompt information 924 may indicate that the browser application has recently accessed the contact permission.

[0228] From the foregoing embodiments, it can be seen that when receiving an operation on the sensitive behavior prompt 913, the electronic device 100 can further inquire whether the authorized visitor has terminated access to the first type of device permission. For example, when receiving an operation to open the control center interface, the electronic device 100 finds that the device permission being accessed includes camera permission and location permission. In this case, when receiving an operation on the sensitive behavior prompt 913, the electronic device 100 can inquire whether the authorized visitor has terminated access to the camera permission and the location permission. If it is found that the authorized visitor has terminated access to the camera permission, the electronic device 100 may display the permission prompt information 921 shown in FIG. 9B. The permission prompt information 921 may include the text identifier "Recently accessed" to indicate that the camera application has recently accessed the camera permission but the access has now ended. If it is found that the authorized visitor has not terminated access to the location permission, the electronic device 100 may display the permission prompt information 922 shown in FIG. 9B. The permission prompt information 922 may include the text identifier "Accessing" to indicate that a plurality of authorized visitors, such as a browser application, are accessing the location permission.

[0229] When one device permission is accessed by a plurality of authorized visitors, it can be seen that the electronic device 100 can display the name of the authorized visitor whose access time is closest to the current time in the permission prompt box 920 shown in FIG. 9B, and add the text identifier "..." to the name to indicate that a plurality of authorized visitors are accessing the device permission. For example, if it is found that both the browser application and the map application are accessing the location permission, the electronic device 100 may display the permission prompt information 922 shown in FIG. 9B. The permission prompt information 922 may include the text identifier "Browser..." to indicate that a plurality of authorized visitors, including the browser application, are accessing the location permission.

[0230] In response to an operation on the permission prompt information 922, for example, a tap operation, the electronic device 100 may display the user interface 930 shown in FIG. 9C.

[0231] As shown in FIG. 9C, the user interface 930 may include browser options 931 and map options 932. The browser options 931 may be used to trigger the electronic device 100 to open a user interface for managing a browser application to access location permission. The map options 932 may be used to trigger the electronic device 100 to open a user interface for managing a map application to access location permission. For the user interface for managing a browser application or a map application to access location permission, refer to the user interface 830 shown in FIG. 8C for managing a browser application to access contact permission.

[0232] It can be understood that both the browser application and the map application for accessing location permission are applications on the electronic device 100. If the permission visitor for accessing location permission further includes an electronic device other than the electronic device 100, for example, the electronic device 200, the electronic device 100 may further display an option corresponding to the electronic device 200 in the user interface 930 shown in FIG. 9C, whereby the user opens a user interface for managing the electronic device 200 to access the location permission of the electronic device 100.

[0233] From the scenarios shown in FIGS. 9A to 9C, it can be seen that when one device permission is accessed by multiple authorized visitors, the electronic device 100 may provide a sensitive behavior reminder to inform the user of the names of the multiple authorized visitors and that the device permission is accessed by the multiple authorized visitors. Therefore, the user can conveniently and better know the access status of the device permission of the electronic device 100, whereby the user can know and control the sensitive behavior in the electronic device 100.

[0234] FIGS. 10A to 10L are diagrams of an example of a cross-device sensitive behavior reminder scenario.

[0235] As shown in FIG. 10A, the electronic device 100 may display a user interface 510. The user interface 510 may include a camera application icon 514. In response to an operation on the camera application icon 514, for example, a tap operation, the electronic device 100 may start the camera application and display a user interface 1010 shown in FIG. 10B. The user interface 1010 may be a shooting interface of the camera application.

[0236] As shown in FIG. 10B, the user interface 1010 may include a preview area 1011, a mode selection area 1012, and a shutter control 1013. The preview area 1011 may be used to display an image captured by using the camera. The mode selection area 1012 may include a plurality of shooting mode options, for example, a video option, a photo option, a professional option, and other options 1012A. The shutter control 1013 may be used to execute shooting. For example, when the photo option is selected, the electronic device 100 may save the image displayed in the preview area 1011 to the gallery in response to an operation on the shutter control 1013 ​

[0237] Note that when the camera application is started, the camera application may access the camera permission of the electronic device 100 to capture an image by using the camera of the electronic device 100.

[0238] Other option 1012A may be used by the user to select more other shooting mode options. In response to an operation on the other option shown in FIG. 10B, the electronic device 100 may display a user interface 1020 shown in FIG. 10C.

[0239] As shown in FIG. 10C, the user interface 1020 may include a plurality of shooting mode options, for example, a multi-camera option 1021. The multi-camera option 1021 may be used to trigger the electronic device 100 to activate the camera of another electronic device to capture an image. In response to an operation on the multi-camera option 1021, for example, a tap operation, the electronic device 100 may display a camera selection box 1030 shown in FIG. 10D.

[0240] As shown in FIG. 10D, the camera selection box 1030 may include a camera selection area 1031. A plurality of camera options, for example, an electronic device 100 (front camera) option, an electronic device 100 (rear camera) option, an electronic device 200 (front camera) option, and an electronic device 200 (rear camera) option may be displayed in the camera selection area 1031. The electronic device 100 (front camera) option may have a text identifier "electronic device 100 (front camera)". The electronic device 100 (rear camera) option may have a text identifier "electronic device 100 (rear camera)". The electronic device 200 (front camera) option may have a text identifier "electronic device 200 (front camera)". The text identifier of the camera option is not particularly limited in the embodiments of the present application.

[0241] When a camera option is selected, the electronic device 100 may display, in the preview area 1011 shown in FIG. 10B, an image captured by using a camera corresponding to the camera option. As shown in FIG. 10D, when the electronic device 100 (rear camera) is selected, it may indicate that the electronic device 100 is currently capturing an image by using the rear camera of the electronic device 100. The electronic device 100 may display, in the preview area 1011, an image captured by using the rear camera of the electronic device 100. In other words, the user may select one or more camera options in the camera selection box 1030 and execute shooting.

[0242] In a possible implementation, upon receiving an operation on the multi-camera option 1021, the electronic device 100 may search for an electronic device equipped with a camera. Based on the search results, the electronic device 100 may display, in the camera selection box 1030 shown in FIG. 10D, a camera option corresponding to the found electronic device.

[0243] As shown in FIG. 10E, in response to an operation on the camera option 1034, such as a tap operation, the electronic device 100 may access the camera permission of the electronic device 200 and request to activate the rear camera of the electronic device 200 to capture an image. The camera option 1034 may be an electronic device 200 (rear camera) option.

[0244] Upon receiving a request for access to camera permission from the electronic device 100, the electronic device 200 may display a request prompt box 1040 as shown in FIG. 10E. The request prompt box 1040 may be used to inform the user that the electronic device 100 is accessing the camera permission of the electronic device 200 and requesting activation of the rear camera of the electronic device 200, and to inquire whether the user agrees thereto. The request prompt box 1040 may include a No control 1041 and an OK control 1042. The No control 1041 may be used to reject the electronic device 100 from accessing the camera permission of the electronic device 200. The OK control 1042 may be used to permit the electronic device 100 to access the camera permission of the electronic device 200.

[0245] In the process of the electronic device 100 requesting access to the camera permission of the electronic device 200, the electronic device 100 may further display a text identifier "Requesting cooperation..." at a position corresponding to the camera option 1034 in the camera selection box 1030 shown in FIG. 10E. The text identifier may remind the user to wait for the electronic device 100 to activate the camera of the electronic device 200. The specific content of the text identifier is not limited in the embodiments of the present application.

[0246] In response to an operation on the OK control 1042 shown in FIG. 10E, the electronic device 200 may activate the rear camera to capture an image and transmit the captured image to the electronic device 100.

[0247] In some embodiments, the electronic device 200 may not display the request prompt box 1040 shown in FIG. 10E. Specifically, upon receiving a request for access to camera permission from the electronic device 100, the electronic device 200 may directly activate the rear camera to capture an image and transmit the captured image to the electronic device 100.

[0248] As shown in FIG. 10F, the electronic device 200 may display a user interface 1060. The user interface 1060 may include a text prompt 1061, a preview area 1062, and an end control 1063. The content of the text prompt 1061 may be "Sharing with electronic device 100", indicating that the electronic device 200 is sharing an image captured by using a camera with the electronic device 100. The preview area 1062 may display an image captured by using the camera of the electronic device 200. The end control 1063 may be used to stop sharing an image captured by using the camera of the electronic device 200 with the electronic device 100. The user interface 1060 may further include a status bar. A camera icon 1064 may be displayed on the status bar. The camera icon 1064 may indicate that the camera permission of the electronic device 200 is accessed.

[0249] When receiving an image shared by the electronic device 200, the electronic device 100 may display a user interface 1050 shown in FIG. 10F. The user interface 1050 may include a preview area 1051, a camera selection control 1052, and a multi-camera function end control 1053. The preview area 1051 may display an image that the electronic device 200 shares with the electronic device 100.

[0250] The camera selection control 1052 may be used to select a camera for capturing an image. In response to an operation on the camera selection control 1052, the electronic device 100 may search for an electronic device equipped with a camera and, based on the search result, may display a camera selection box 1030 shown in FIG. 10E. In this way, the user can select different electronic devices to capture images and experience the multi-camera shooting function.

[0251] The multi-camera function termination control 1053 can be used to terminate the multi-camera function. In response to an operation on the multi-camera function termination control 1053, the electronic device 100 can terminate access to the camera permission of another electronic device (e.g., the electronic device 200) and display the image captured by using the camera of the electronic device 100 in the preview area 1051.

[0252] As shown in FIG. 10G, in response to an operation to open the control center interface, the electronic device 100 can display the control center interface 1070 shown in FIG. 10H. The operation to open the control center interface can be, for example, an operation of sliding down from the upper right of the screen of the electronic device 200. The above-described operation to open the control center interface is not limited in the embodiments of the present application.

[0253] As shown in FIG. 10H, the control center interface 1070 can include a sensitive behavior prompt 1072 and a camera icon 1071 displayed in the status bar. For the display of the sensitive behavior prompt 1072 by the electronic device 200, refer to the description of the display of the sensitive behavior prompt in the control center interface by the electronic device 100 in the foregoing embodiments. Details will not be described again in this specification.

[0254] In some embodiments, the control center interface 1070 may further include a super terminal card 1073. The super terminal card 1073 may include device icons of one or more electronic devices, for example, an icon 1073A of the electronic device 100, an icon of the electronic device 201, and an icon of the electronic device 202. In the super terminal card 1073, the display style of the device icon of the electronic device that has established a cooperative connection with the electronic device 200 may be different from the display style of the device icon of the electronic device that has not established a cooperative connection with the electronic device 200. For example, the device icon of the electronic device that has established a cooperative connection with the electronic device 200 may have a dark display style, and the device icon of the electronic device that has not established a cooperative connection with the electronic device 200 may have a light display style. The display style of the device icons in the super terminal card 1073 is not limited in the embodiments of the present application.

[0255] From the foregoing embodiments shown in FIGS. 10E to 10G, it can be seen that the electronic device 100 activates the camera of the electronic device 200 to capture an image. Specifically, a cooperative connection is established between the electronic device 100 and the electronic device 200. The icon 1073A of the electronic device 100 may be displayed in a dark display style. In addition, in order to notify the user that the electronic device 200 is operating cooperatively with the electronic device 100, a text identifier "cooperating" may be displayed at a position corresponding to the icon 1073A of the electronic device 100.

[0256] In some embodiments, when a cooperative connection is established between the electronic device 100 and the electronic device 200, in response to an operation on the icon 1073A of the electronic device 100, for example, a tap operation, the electronic device 200 may stop cooperating with the electronic device 100. For example, the electronic device 200 may share an image captured by using a camera with the electronic device 100. When receiving an operation on the icon 1073A of the electronic device 100, the electronic device 200 may stop sharing an image captured by using a camera with the electronic device 100.

[0257] In some embodiments, the electronic device 100 may access the device permission (such as camera permission) of the electronic device 200, and the electronic device 100 may also provide a sensitive behavior reminder to remind the user that the electronic device 100 is accessing the device permission of another electronic device.

[0258] FIGS. 10I to 10L are diagrams of a scenario in which the electronic device 100 accesses the camera permission of the electronic device 200 and provides a sensitive behavior reminder.

[0259] As shown in FIG. 10I, when accessing the camera permission of the electronic device 200, the electronic device 100 may display the user interface 1050. The user interface 1050 may display an image captured by using the camera of the electronic device 200. For the method for the electronic device 100 to access the camera permission of the electronic device 200, refer to the description of the foregoing embodiments.

[0260] In response to an operation to open the control center interface shown in FIG. 10I, the electronic device 100 may display the control center interface 1080 shown in FIG. 10J. The control center interface 1080 may include a sensitive behavior prompt 1082 and a camera icon 1081 displayed in the status bar. The camera icon 1081 may indicate that camera permission is accessed. The sensitive behavior prompt 1082 may include the camera icon of the accessed camera permission and the text identifier "The camera application will activate the camera of the electronic device 200". The sensitive behavior prompt 1082 may inform the user that the camera application on the electronic device 100 will activate the camera of the electronic device 200 when accessing the camera permission of the electronic device 200.

[0261] In some embodiments, in response to an operation to open the control center interface, the electronic device 100 may inquire which device permissions of the electronic device 100 are accessed within a preset period before the operation to open the control center interface, and may inquire whether the electronic device 100 accesses the device permissions of another electronic device within the preset period. For example, in addition to knowing that the electronic device 100 accesses the camera permission of the electronic device 200 within a preset period, the electronic device 100 further finds that a plurality of device permissions of the electronic device 100 are accessed within the preset period. In this case, in addition to the camera icon shown in FIG. 10J, the sensitive behavior prompt 1082 displayed on the control center interface 1080 shown in FIG. 10J by the electronic device 100 may further include an icon corresponding to the device permission in the plurality of accessed device permissions of the electronic device 100. This can help the user quickly know and control the sensitive behavior of the applications on the device and the cross-device sensitive behavior.

[0262] As shown in FIG. 10J, the control center interface 1080 may further include a super terminal card 1083. The super terminal card 1083 may include icons of electronic devices, for example, an icon 1083A of the electronic device 200. For the display style of the icons of the electronic devices in the super terminal card 1083, refer to the description of the super terminal card 1073 shown in FIG. 10H.

[0263] The electronic device 100 is currently activating the camera of the electronic device 200. That is, the electronic device 100 and the electronic device 200 are currently in cooperation. The icon 1083A of the electronic device 200 in the super terminal card 1083 may be displayed in the dark display style shown in FIG. 10J. In response to an operation on the icon 1083A of the electronic device 200 shown in FIG. 10J, the electronic device 100 may stop the cooperation with the electronic device 200 and display the icon 1083A of the electronic device 200 in the bright display style shown in FIG. 10K. In other words, the electronic device 100 may terminate the access to the camera permission of the electronic device 200.

[0264] Note that in some embodiments, when the control center interface 1080 is displayed, both the sensitive behavior prompt 1082 and the camera icon 1081 displayed on the status bar may be in a frozen state. Therefore, even if the electronic device 100 terminates the access to the camera permission of the electronic device 200 based on an operation on the icon 1083A of the electronic device 100 shown in FIG. 10J, the electronic device 100 may still continue to display the sensitive behavior prompt 1082 and the camera icon 1081 on the control center interface 1080.

[0265] As shown in FIG. 10K, in response to an operation of folding the control center interface, the electronic device 100 may display a user interface 1090 shown in FIG. 10L. The operation of folding the control center interface may be, for example, an operation of sliding from the bottom to the top of the screen of the electronic device 100. The foregoing operation of folding the control center interface is not limited in the embodiments of the present application.

[0266] As shown in FIG. 10K, the user interface 1090 may be a shooting interface of a camera application. Since the electronic device 100 has terminated access to the camera of the electronic device 200, the electronic device 100 may display, on the user interface 1090, an image captured by using the camera (for example, the rear camera) of the electronic device 100. For the user interface 1090, refer to the description of the embodiment shown in FIG. 10B. Details will not be described again in this specification.

[0267] From the scenarios shown in FIGS. 10A to 10L, it can be seen that the electronic device 100 can access the device permission of another electronic device, for example, the electronic device 200, across multiple devices. When the electronic device 100 accesses the device permission of the electronic device 200, both the electronic device 100 and the electronic device 200 may provide a sensitive behavior reminder. In this way, the user can quickly view the cross-device sensitive behavior of the electronic device 100 on the electronic device 100. The user can also know which device permissions of the electronic device 200 are accessed on the electronic device 200. In addition, the user can further terminate the cross-device sensitive behavior on either the electronic device 100 or the electronic device 200.

[0268] FIGS. 11A to 11C are some diagrams of examples of a sensitive behavior management scenario.

[0269] As shown in FIG. 11A, the electronic device 200 may display a control center interface 1110. The control center interface 1110 may include a sensitive behavior prompt 1112 and a camera icon 1111 displayed in the status bar. For the control center interface 1110, refer to the description of the control center interface 1070 shown in FIG. 10H. Details will not be described again in this specification.

[0270] In response to an operation on the sensitive behavior prompt 1112, for example, a tap operation, the electronic device 200 may display a permission prompt box 1120 as shown in FIG. 11B.

[0271] As shown in FIG. 11B, the permission prompt box 1120 may include permission prompt information 1121 and a stop control 1122. The permission prompt information 1121 may indicate that the electronic device 100 has access to the camera permission of the electronic device 200. The stop control 1122 may be used to end the access of the electronic device 100 to the camera permission of the electronic device 200. In response to an operation on the stop control 1122, the electronic device 200 may stop sharing the images captured by using the camera with the electronic device 100.

[0272] In a possible implementation form, when receiving an operation on the sensitive behavior prompt 1112, the electronic device 200 may inquire whether the first type of device permission of the electronic device 200 is still being accessed. For example, if it is found that the electronic device 100 is still accessing the camera permission, the electronic device 200 may display the text identifier "accessing" shown in FIG. 11B in the permission prompt box 1120 to indicate that the electronic device 100 is accessing the camera permission of the electronic device 200. Alternatively, if it is found that the electronic device 100 has terminated access to the camera permission, the electronic device 200 may adjust the "accessing" shown in FIG. 11B to the text identifier "recent access" in the permission prompt box 1120 to indicate that the electronic device 100 has recently accessed the camera permission of the electronic device 200 but the access to the camera permission of the electronic device 200 has been terminated.

[0273] In response to an operation on the permission prompt information 1121 shown in FIG. 11B, for example, a tap operation, the electronic device 200 may display the user interface 1130 shown in FIG. 11C.

[0274] As shown in FIG. 11C, the user interface 1130 may include an identifier 1131 of the electronic device 100 and a permission management box 1132. The identifier 1131 of the electronic device 100 may include identifier information such as a device icon and a device name of the electronic device 100. The permission management box 1132 may include an "Ask before each access" control 1132A, an "Always" control 1132B, and a "Never" control 1132C. The "Ask before each access" control 1132A is used to adjust the conditions for the electronic device 100 to access the camera permission of the electronic device 200, and the electronic device 200 may display a prompt message each time the electronic device 100 accesses the camera permission. Thereby, the consent of the user of the electronic device 200 is obtained. For the display of the prompt message by the electronic device 200, refer to the request prompt box 1040 shown in FIG. 10E. The "Always" control 1132B is used to call the conditions for the electronic device 100 to access the camera permission of the electronic device 200, and the electronic device 200 may directly consent to the request for the camera permission of the electronic device 100 without displaying a prompt message. The "Never" control 1132C may be used to reject the electronic device 100 from accessing the camera permission of the electronic device 200. When the "Never" control 1132C is selected, the electronic device 200 may directly reject the request each time it receives a request for accessing the camera permission from the electronic device 100.

[0275] From the foregoing scenarios shown in FIGS. 11A to 11C, it can be seen that the user can quickly know which device permissions of the electronic device 200 are accessed by opening the control center interface. The device permissions accessed may include first - type device permissions such as camera permission, microphone permission, and location permission, contact permissions, and media A ohIt may further include a second type of device permission such as call file permission. In addition, based on the sensitive behavior prompt in the control center interface, the user can more quickly view the specific situations (such as who the permission visitor is and whether the permission has been recently accessed or is being accessed) in which each device permission is accessed. In addition, based on the sensitive behavior prompt in the control center interface, the user can quickly manage the permission visitors and adjust the conditions for the device permission visitors to access the device permission. The permission visitor may be an application on the electronic device 200 or an electronic device other than the electronic device 200. This can help the user conveniently and quickly manage device permissions, reduce the abuse of device permissions, and improve the security of user privacy information.

[0276] FIGS. 12A-12C are several other diagrams of an example of a sensitive behavior management scenario.

[0277] In this specification, an example where the electronic device 100 accesses the camera permission of the electronic device 200 is still used for illustration.

[0278] As shown in FIG. 12A, the electronic device 200 may display a control center interface 1210. The control center interface 1210 may include a sensitive behavior prompt 1212 and a camera icon 1211 displayed in the status bar. The sensitive behavior prompt 1212 may be used to notify that the electronic device 100 accesses the camera permission of the electronic device 200. The control center interface 1210 may further include a super terminal card 1213. The super terminal card 1213 may include a "Settings" control 1213A. In response to an operation on the "Settings" control 1213A, the electronic device 100 may display a user interface 1220 shown in FIG. 12B. The user interface 1220 may be a settings interface of the super terminal.

[0279] As shown in FIG. 12B, the user interface 1220 may include a device information box 1221. The device information box 1221 may display information such as the name of the electronic device 200 and the login account on the electronic device 200. For example, the name of the electronic device 200 is "electronic device 200", and the login account on the electronic device 200 is "123456". The information regarding the electronic device 200 is not limited in the embodiments of the present application. In response to an operation on the device information box 1221, for example, a tap operation, the electronic device 200 may display the user interface 1230 shown in FIG. 12C.

[0280] As shown in FIG. 12C, the user interface 1230 may include a device discovery control 1231 and a permission management box 1232.

[0281] The device discovery control 1231 may be used to manage the types of devices that can discover the electronic device 200. For example, the types of devices that can discover the electronic device 200 may include nearby devices and nearby my devices. When the type of device is a nearby device, all nearby electronic devices can discover the electronic device 200. When the type of device is a nearby my device, nearby electronic devices with the same login account as the login account of the electronic device 200 can discover the electronic device 200. For example, when the electronic device 200 is discovered by the electronic device 100, the electronic device 100 may display the device icon of the electronic device 200 on the super Terminal card in the control center interface (see the super terminal card 1083 shown in FIG. 10J).

[0282] The permission management box 1232 can be used to manage the device permissions of the electronic device 200 that can be accessed by an electronic device capable of discovering the electronic device 200. For example, the permission management box 1232 may include a switch corresponding to the device permission. When the switch is in the on state, an electronic device capable of discovering the electronic device 200 can access the device permission of the electronic device 200 corresponding to the switch. For example, when the switch corresponding to the camera permission in the permission management box 1232 is in the on state, all electronic devices capable of discovering the electronic device 200 can access the camera permission of the electronic device 200; when the switch corresponding to the camera permission in the permission management box 1232 is in the off state, none of the electronic devices capable of discovering the electronic device 200 can access the camera permission of the electronic device 200.

[0283] From the scenarios shown in FIGS. 12A to 12C, it can be seen that the user can manage the cross-device sensitive behavior in the electronic device 200 and permit or prohibit another electronic device from accessing the device permissions of the electronic device 200.

[0284] FIGS. 13A to 13E are some other figures of an example of the sensitive behavior management scenario.

[0285] As shown in FIG. 13A, the electronic device 200 may display a control center interface 1310. The control center interface 1310 may include a super terminal card 1311. The super terminal card 1311 may display device icons of one or more electronic devices, for example, an icon 1311A of the electronic device 100. In response to an operation on the icon 1311A of the electronic device 100, for example, a long-press operation, the electronic device 100 may display a setting option box 1320 shown in FIG. 13A. The setting option box 1320 may include a cooperation establishment control 1321 and a permission management control 1322. The cooperation establishment control 1321 may be used to trigger the electronic device 200 to establish a cooperative connection with the electronic device 100. The permission management control 1322 may be used to manage the device permission of the electronic device 200 that can be accessed by the electronic device 100.

[0286] As shown in FIG. 13B, in response to an operation on the permission management control 1322, for example, a tap operation, the electronic device 200 may display a user interface 1330 shown in FIG. 13C.

[0287] As shown in FIG. 13C, the user interface 1330 may include a permission management box 1331. The permission management box 1331 may be used to manage the device permission of the electronic device 200 that can be accessed by the electronic device 100. For example, the permission management box 1331 may include a switch corresponding to the device permission. When the switch is in the on state, the electronic device 100 can access the device permission of the electronic device 200 corresponding to the switch. For example, when the switch corresponding to the camera permission in the permission management box 1331 is in the on state, the electronic device 100 can access the camera permission of the electronic device 200, and when the switch corresponding to the camera permission in the permission management box 1331 is in the off state, the electronic device 100 cannot access the camera permission of the electronic device 200.

[0288] As can be seen from FIG. 13C, the user can separately perform permission management on an electronic device connected to the electronic device 200 in order to adjust the device permission of the electronic device 200 that can be accessed by the electronic device. In other words, the user can authorize different electronic devices to access different device permissions of the electronic device 200 based on requirements and privacy security considerations. Thereby, the user's usage requirements can be better met, and the security of the user privacy information can be improved.

[0289] In some embodiments, in cross-device sensitive behavior, the electronic device 100 accessing the device permission of the electronic device 200 may specifically be an application on the electronic device 100 accessing the device permission of the electronic device 200. The user can separately manage the device permissions of the electronic device 200 that can be accessed by each application on the electronic device 100.

[0290] In response to an operation on the permission management control 1322 shown in FIG. 13B, the electronic device 200 may display the user interface 1340 shown in FIG. 13D.

[0291] As shown in FIG. 13D, the user interface 1340 may include a permission management box 1341. The permission management box 1341 may include device permission options, such as a camera permission option 1341A, a microphone permission option, a location permission option, a contact permission option, and a media and file permission option. Using one device permission option, a user interface for managing access to the device permission corresponding to the device permission option on the electronic device 200 by each application on the electronic device 100 can be opened.

[0292] For example, in response to an operation on the camera permission option 1341A, such as a tap operation, the electronic device 200 may display the user interface 1350 shown in FIG. 13E.

[0293] As shown in FIG. 13E, the user interface 1350 may include a permission switch display area 1351. The permission switch display area 1351 may include switches corresponding to applications. These applications may be applications on the electronic device 100. The switches within the permission switch display area 1351 may be used to permit or prohibit an application corresponding to the switch within the electronic device 100 from accessing the camera permission of the electronic device 200. For example, the permission switch display area 1351 includes a switch corresponding to the AA chat application. When the switch corresponding to the AA chat application is in the on state, the AA chat application on the electronic device 100 may access the camera permission of the electronic device 200. When the switch corresponding to the AA chat application is in the off state, the AA chat application on the electronic device 100 cannot access the camera permission of the electronic device 200.

[0294] In a possible implementation form, after the electronic device 100 establishes a communication connection to the electronic device 200, the electronic device 100 may send information about the applications on the electronic device 100 (such as the names of the applications and the application icons) to the electronic device 200. The electronic device 200 may display the user interface 1350 shown in FIG. 13E based on the information about the applications on the electronic device 100. When the electronic device 100 requests access to the device permission of the electronic device 200, the electronic device 100 may send the identifier of the application within the electronic device 100 that requests access to the device permission to the electronic device 200. The electronic device 200 may determine whether the application on the electronic device 100 can access the requested device permission based on the identifier of the application in order to determine whether to provide the service corresponding to the device permission.

[0295] From the scenarios shown in FIGS. 13D and 13E, it can be seen that the user can separately execute permission management for each application on the electronic device connected to the electronic device 200 in order to adjust the device permissions of the electronic device 200 that can be accessed by each application on the electronic device. In other words, the user can approve different applications on the electronic device to access different device permissions of the electronic device 200 based on requirements and privacy security considerations. This can better meet the user's usage requirements and improve the security of the user's privacy information.

[0296] FIGS. 14A and 14B are some other diagrams of an example of a sensitive behavior management scenario.

[0297] In this specification, an example where the electronic device 100 accesses the camera permission of the electronic device 200 is still used for the purpose of illustration.

[0298] As shown in FIG. 14A, the electronic device 100 may display a control center interface 1410. The control center interface 1410 may include a sensitive behavior prompt 1412 and a camera bar 1411 displayed on the status bar. The sensitive behavior prompt 1412 may be used to inform the user that the camera application on the electronic device 100 accesses the camera permission of the electronic device 200. For the control center interface 1410, refer to the control center interface 1080 shown in FIG. 10J. Details will not be described again in this specification.

[0299] In response to an operation on the sensitive behavior prompt 1412, for example, a tap operation, the electronic device 100 may display a user interface 1420 shown in FIG. 14B.

[0300] As shown in FIG. 14B, the user interface 1420 may include a camera application identifier 1421 and a permission management box 1422. The camera application identifier 1421 may include identifier information such as the icon and name of the camera application. The permission management box 1422 may include controls used to manage the camera application to access the camera permission of the electronic device 200, for example, an "In use of this application" control, an "Always" control, and a "Do not permit" control.

[0301] For example, when the "During use of this application" control is selected, the electronic device 100 may enable only the camera application to access the camera permission of the electronic device 200 while running in the foreground. In other words, when the "During use of this application" control is selected and the camera application is running in the foreground, if the electronic device 100 detects a request to access the camera permission of the electronic device 200, the electronic device 100 may send the request to the electronic device 200 and request to invoke the camera service of the electronic device 200. When the "During use of this application" control is selected and the camera application is not running in the foreground, if the electronic device 100 detects a request to access the camera permission of the electronic device 200, the electronic device 100 may reject sending the request to the electronic device 200. When the "Always" control is selected, the electronic device 100 may enable the camera application to access the camera permission of the electronic device 200 under any circumstances. When the "Do not permit" control is selected, the electronic device 100 may prohibit the camera application from accessing the camera permission of the electronic device 200.

[0302] From the scenarios shown in FIGS. 14A and 14B, it can be seen that the user can further perform operations on the electronic device 100 to separately execute permission management for each application on the electronic device 100 in order to adjust the device permissions of the electronic device 200 that can be accessed by each application on the electronic device 100. In other words, based on requirements and privacy security considerations, the user can authorize different applications on the electronic device to access different device permissions of the electronic device 200. Thereby, the user's usage requirements can be better met, and the security of the user privacy information can be improved.

[0303] In some embodiments, when one device permission of the electronic device 100 is frequently accessed, after a permission visitor finishes one access to the device permission, the electronic device 100 may extend the time for displaying the device permission icon of the device permission in the status bar. In this case, when the permission visitor accesses the device permission again during the extended time for displaying the device permission icon, the electronic device 100 may continue to display the device permission icon in the status bar. When the permission visitor accesses the same device permission twice in succession in a relatively short time, it can be seen that the electronic device 100 may continue to continuously display the device permission icon in the status bar during the time interval between the two accesses. The sensitive behavior prompting method provided in the foregoing embodiments can be used to avoid the frequent flashing of the device permission icon displayed in the status bar of the electronic device 100 when the device permission is frequently accessed, and to improve the user experience of browsing the status bar.

[0304] Next, another sensitive behavior prompting scenario provided in the embodiments of the present application will be described.

[0305] FIGS. 15A to 15F are some other figures of an example of the sensitive behavior prompting scenario.

[0306] In this specification, an example in which a recorder application on the electronic device 100 accesses the microphone permission of the electronic device 100 is used for illustration.

[0307] As shown in FIG. 15A, the electronic device 100 may display a user interface 1510. The user interface 1510 may be a user interface of the recorder application. For the user interface 1510, refer to the user interface 610 shown in FIG. 6B.

[0308] The user interface 1510 may include a recording start control 1511. The user may tap the recording start control 1511 at the first second to start recording. In response to an operation on the recording start control 1511, the electronic device 100 may activate a microphone to capture audio data and display the user interface 1520 shown in FIG. 15B. For the user interface 1520, refer to the user interface 610 shown in FIG. 6C. The user interface 1520 may include a recording pause control 1522 and a recording end control 1523. Since the recorder application has access to the microphone permission of the electronic device 100, the electronic device 100 may display the microphone icon 1521 shown in FIG. 15B in the status bar of the user interface 1520.

[0309] As shown in FIG. 15B, the user may tap the recording end control 1523 at the third second to end the recording. In response to an operation on the recording end control 1523, the electronic device 100 may close the microphone and display the user interface 1530 shown in FIG. 15C.

[0310] In a possible implementation, the electronic device 100 may determine whether the duration for which the authorized visitor accesses the microphone permission exceeds a preset duration. The preset duration may be, for example, 5 seconds or 8 seconds. The value of the preset duration is not limited in the embodiments of the present application. If it is determined that the duration for which the authorized visitor accesses the microphone permission does not exceed the preset duration, the electronic device 100 may continue to display the microphone icon in the status bar even after the authorized visitor ends the call for the microphone permission. The electronic device 100 may supplement the display duration of the microphone icon in the status bar so that the display duration of the microphone icon in the status bar reaches the preset duration.

[0311] As shown in FIG. 15C, the user interface 1530 may include an Audio 1 option 1531 and a recording start control 1511. The Audio 1 corresponding to the Audio 1 option 1531 may be the audio recorded by the electronic device 100 in response to an operation on the recording start control 1511 shown in FIG. 15A and an operation on the recording end control 1523 shown in FIG. 15B. It can be seen that the recording time segment of Audio 1 is from the 1st second to the 3rd second, and the recording duration is 2 seconds.

[0312] The microphone icon 1521 may still be displayed in the status bar of the user interface 1530. It can be understood that the electronic device 100 receives an operation of tapping the recording start control 1511 at the 1st second and an operation of tapping the recording end control 1523 at the 3rd second. The electronic device 100 starts the recorder application to access the microphone permission at the 1st second and the microphone N permissionIt may be determined to end the access. That is, the recorder application accesses the microphone permission from the 1st second to the 3rd second, and the access duration is only 2 seconds. If the preset duration is 5 seconds, the electronic device 100 may determine that the access duration for the recorder application to access the microphone permission does not exceed the preset duration. In this case, after the recorder application finishes accessing the microphone permission, the electronic device 100 may continue to display the microphone icon 1521 in the status bar shown in FIG. 15C. In addition, the electronic device 100 may make up the display duration of the microphone icon 1521 to 5 seconds. Since the electronic device 100 displays the microphone icon 1521 in the status bar from the 1st second to the 3rd second (that is, the microphone icon 1521 is displayed for 2 seconds), the electronic device 100 may continue to display the microphone icon in the status bar for 3 seconds. In other words, the electronic device 100 may continue to display the microphone icon 1521 in the status bar from the 3rd second to the 6th second. If no access to the microphone permission is detected from the 3rd second to the 6th second, the electronic device 100 may cancel the display of the microphone icon 1521 in the status bar at the 6th second. If a re-access to the microphone permission is detected between the 3rd second and the 6th second, the electronic device 100 may determine the display duration of the microphone icon in the status bar based on the access duration of the re-access to the microphone permission.

[0313] For example, the electronic device 100 continues to display the microphone icon 1521 in the status bar from the 3rd second to the 4th second.

[0314] As shown in FIG. 15D, the user may start recording by tapping the recording start control 1511 at the 4th second. In response to the operation on the recording start control 1511, the electronic device 100 may activate the microphone to capture audio data and display the user interface 1540 shown in FIG. 15E. For the user interface 1540, refer to the user interface 610 shown in FIG. 6C. The user interface 1540 may include a recording pause control 1522 and a recording end control 1523. Since the recorder application has access to the microphone permission of the electronic device 100, the electronic device 100 may display the microphone icon 1521 shown in FIG. 15E in the status bar of the user interface 1540.

[0315] As shown in FIG. 15E, the user may end the recording by tapping the recording end control 1523 at the 6th second. In response to the operation on the recording end control 1523, the electronic device 100 may close the microphone and display the user interface 1550 shown in FIG. 15F.

[0316] As shown in FIG. 15F, the user interface 1550 may include an audio 1 option 1531, an audio 2 option 1551, and a recording start control 1511. For the audio 1 option 1531, refer to the description in the foregoing embodiments. The audio 2 corresponding to the audio 2 option 1551 may be the audio recorded by the electronic device 100 in response to the operation on the recording start control 1511 shown in FIG. 15D and the operation on the recording end control 1523 shown in FIG. 15E. 2 It can be seen that the recording time segment of the audio is from the 4th second to the 6th second, and the recording duration is 2 seconds.

[0317] The microphone icon 1521 may still be displayed in the status bar of the user interface 1550. It can be understood that the electronic device 100 receives an operation of tapping the recording start control 1511 at the 4th second and an operation of tapping the recording end control 1523 at the 6th second. The electronic device 100 may determine that the access duration for the recorder application to access the microphone permission is 2 seconds and does not exceed a preset duration (i.e., 5 seconds). In this case, after the recorder application terminates the access to the microphone permission, the electronic device 100 may continue to display the microphone icon 1521 in the status bar shown in FIG. 15F. The electronic device 100 can compensate the display duration of the microphone icon 1521 to 5 seconds by using the display start time when the microphone icon 1521 starts to be displayed in the status bar when the microphone permission was last accessed as the start time. In other words, the electronic device 100 can display the microphone icon 1521 in the status bar for at least 5 seconds starting from the 4th second by using the time point "the 4th second" when the operation on the recording start control 1511 is received as the time start point shown in FIG. 15D. Since the recorder application terminates the access to the microphone permission at the 6th second, the electronic device 100 may continue to display the microphone icon 1521 in the status bar from the 6th second to the 9th second. If no access to the microphone permission is detected from the 6th second to the 9th second, the electronic device 100 may cancel the display of the microphone icon 1521 in the status bar at the 9th second.

[0318] From the scenarios of FIGS. 15A to 15F, when the access duration of the accessed device permission is excessively short, after the permission visitor finishes accessing, the electronic device 100 extends the display duration of the device permission icon and continuously displays the device permission icon in the status bar for a certain period, so that the display duration of the device permission can reach the preset duration. It can be seen that the above method can avoid the frequent flashing of the device permission icon displayed in the status bar when the device permission is frequently accessed, prevent the electronic device 100 from frequently refreshing the device permission icon displayed in the status bar, improve the experience of the user browsing the status bar, and reduce the power consumption of the electronic device 100 for refreshing the device permission icon.

[0319] Hereinafter, based on the scenarios shown in FIGS. 15A to 15F, the sensitive behavior reminder method provided in the embodiments of the present application will be described.

[0320] In a possible implementation form, the electronic device 100 may display the device permission icon in the status bar by using a delay compensation mechanism. The delay compensation mechanism may include that the display duration of the device permission icon in the status bar needs to satisfy the shortest display duration. When the access duration of the accessed device permission does not exceed the shortest display duration, the electronic device 100 may compensate the display duration of the device permission icon in the status bar so that the display duration of the device permission icon in the status bar reaches at least the shortest display duration.

[0321] Specifically, the electronic device 100 may store a preset duration. The preset duration is the shortest display duration of the device permission icon. In this specification, an example where the preset duration is 5 seconds is used for illustration. Alternatively, the preset duration may be another value. The value of the preset duration is not limited in the embodiments of the present application.

[0322] When detecting that the device permission is accessed, the electronic device 100 may obtain the time point when the permission visitor starts accessing the device permission and the time point when the permission visitor ends accessing the device permission. The start time point may be denoted as currentTime1. The end time point may be denoted as currentTime2. The electronic device 100 may display the device permission icon of the accessed device permission in the status bar from currentTime1. The electronic device 100 may determine the result of currentTime2 - currentTime1. The result of currentTime2 - currentTime1 may be denoted as the duration.

[0323] The electronic device 100 may determine whether the duration is greater than a preset duration.

[0324] If it is determined that the duration is greater than the preset duration, the electronic device 100 may cancel the display of the device permission icon of the device permission whose access has ended in the status bar at currentTime2.

[0325] Alternatively, if it is determined that the duration has not exceeded a preset duration, the electronic device 100 may extend the display duration of the device permission icon in the status bar. The electronic device 100 may use the preset duration - the extended duration as a result of the duration to continue to display the device permission icon of the device permission in the status bar after the authorized visitor stops accessing the device permission. Further, if the electronic device 100 does not detect a re-access of the device permission during the period when the display of the device permission icon is extended, the electronic device 100 may cancel the display of the device permission icon in the status bar after the preset duration - the period of the duration is extended. Alternatively, if the electronic device 100 detects a re-access of the device permission during the period when the display of the device permission icon is extended, the electronic device 100 may use the display start point when the device permission icon starts to be displayed in the status bar when the device permission was last accessed as the time start point, and may redisplay the device permission icon by using a delay compensation mechanism. For example, if the electronic device 100 detects that the authorized visitor re-accesses the device permission during the period when the display of the device permission icon is extended, the electronic device 100 may obtain the time point when the re-access of the device permission starts and the time point when the re-access of the device permission ends. The time point when the re-access of the device permission starts may be denoted as currentTime3. The time point when the re-access of the device permission ends may be denoted as currentTime4. The electronic device 100 may determine the display duration of the device permission icon in the status bar based on currentTime3, currentTime4, and the preset duration.

[0326] Optionally, if the electronic device 100 detects a re-access of device permission during a period when the display of the device permission icon is extended, the electronic device 100 may determine whether the duration between the time when the display of the device permission icon of the device permission starts and the time when the re-access of the device permission ends exceeds a preset duration. If the duration exceeds the preset time, the electronic device 100 may cancel the display of the device permission icon in the status bar when the re-access of the device permission ends. Alternatively, if the duration does not exceed the preset time, the electronic device 100 may compensate for the display duration of the device permission icon so that the total display duration of the device permission icon is at least the preset duration. For example, the time when the re-access of the device permission starts may be denoted as currentTime3. The time when the re-access of the device permission ends may be denoted as currentTime4. The electronic device 100 may determine whether the result of currentTime4 - currentTime1 exceeds the preset duration. If currentTime4 - currentTime1 exceeds the preset duration, the electronic device 100 may cancel the display of the device permission icon of the accessed device permission in the status bar at currentTime4. Alternatively, if currentTime4 - currentTime1 does not exceed the preset duration, the electronic device 100 may continue to display the device permission icon of the accessed device permission in the status bar after currentTime4 by using the extended duration as the result of the preset duration-(currentTime4 - currentTime1).

[0327] Note that in the delay compensation mechanism, the device permission icon may be the device permission icon of the first type of device permission in this application.

[0328] 16A-16C illustrate some examples of sensitive behavior reminder scenarios according to an embodiment of the present application.

[0329] In this specification, an example where a recorder application accesses the microphone permission is used for explanation.

[0330] FIG. 16A shows a scenario where the electronic device 100 displays a microphone in the status bar when the recorder application accesses the microphone permission once and the access duration exceeds a preset duration. The preset duration can be, for example, 5 seconds.

[0331] As shown in FIG. 16A, at the 1st second, the electronic device 100 receives an operation to start recording. The operation to start recording can be, for example, an operation on the recording start control 1511 shown in FIG. 15A. In response to the operation to start recording, the recorder application starts accessing the microphone permission of the electronic device 100 and can capture audio data by using the microphone of the electronic device 100. The electronic device 100 may start displaying a microphone icon in the status bar. The point in time when the microphone icon starts to be displayed in the status bar can be the 1st second. At the 7th second, the electronic device 100 receives an operation to end recording. The operation to end recording can be, for example, an operation on the recording end control 1523 shown in FIG. 15B. In response to the operation to end recording, the recorder application may end the access to the microphone permission of the electronic device 100 at this time. In this case, the electronic device 100 may determine that the access duration of the microphone permission at this time (that is, a total of 6 seconds from the 1st second to the 7th second) exceeds the preset duration. At the 7th second, the electronic device 100 may cancel the display of the microphone icon in the status bar. In the scenario shown in FIG. 16A where the recorder application accesses the microphone permission, it can be seen that the electronic device 100 may continuously display the microphone icon in the status bar from the 1st second to the 7th second (a total duration of 6 seconds).

[0332] FIG. 16B shows a scenario where the recorder application accesses the microphone permission once and the access duration does not exceed a preset duration, and the electronic device 100 displays the microphone in the status bar. The preset duration can be, for example, 5 seconds.

[0333] As shown in FIG. 16B, at the first second, the electronic device 100 receives an operation to start recording. In response to the operation to start recording, the recorder application may start accessing the microphone permission of the electronic device 100. The electronic device 100 may start displaying the microphone in the status bar. The time when the microphone icon starts to be displayed in the status bar may be the first second. At the third second, the electronic device 100 receives an operation to end recording. In response to the operation to end recording, the recorder application may end the access to the microphone permission of the electronic device 100 at this time. In this case, the electronic device 100 may determine that the access duration of the microphone permission at this time (that is, a total of 2 seconds from the first second to the third second) does not exceed the preset duration. The electronic device 100 may compensate for the display duration of the microphone icon in the status bar. Based on the preset duration - (the time when the access to the microphone permission ends (that is, the third second) - the time when the access to the microphone permission starts (that is, the first second)), the electronic device 100 may determine that the extension duration for extending the display of the microphone icon is 3 seconds. Therefore, the electronic device 100 may extend the display of the microphone icon in the status bar for 3 seconds from the third second. The electronic device 100 may cancel the display of the microphone icon in the status bar at the sixth second. In the scenario shown in FIG. 16B where the recorder application accesses the microphone permission, it can be seen that the electronic device 100 can continuously display the microphone icon in the status bar from the first second to the sixth second (a total duration of 5 seconds). Icon

[0334] ​FIG. 16C shows a scenario in which an electronic device 100 displays a microphone in a status bar when a recorder application accesses the microphone permission twice, the access duration for accessing the microphone permission twice does not exceed a preset duration, and the point in time when the second access to the microphone permission starts falls within an extended period during which the display of the microphone icon is extended based on the access time of the first access to the microphone permission. The preset duration can be, for example, 5 seconds.

[0335] As shown in FIG. 16C, the recorder application accesses the microphone permission of the electronic device 100 during a first period from the 1st second to the 3rd second and accesses the microphone permission of the electronic device 100 during a second period from the 4th second to the 6th second. From the foregoing embodiments, it can be understood that the electronic device 100 may start displaying the microphone icon in the status bar at the 1st second. When an operation to end the recording is received at the 3rd second, the electronic device 100 may determine that the access duration during which the microphone permission is accessed for the first time (i.e., a total of 2 seconds from the 1st second to the 3rd second) does not exceed a preset duration. The electronic device 100 may compensate for the display duration of the microphone icon in the status bar. From the embodiment shown in FIG. 16B, it can be understood that the period during which the electronic device 100 extends the display of the microphone icon may be from the 3rd second to the 6th second (a total of 3 seconds). When the recorder application detects that it accesses the microphone permission for the second time from the 4th second to the 6th second, the electronic device 100 may re-determine the display duration of the microphone icon by using a delay compensation mechanism, using the time point when the second access to the microphone permission starts (i.e., the 4th second) as the start time point. When an operation to end the recording is received at the 6th second, the electronic device 100 may determine that the access duration during which the microphone permission is accessed for the second time (i.e., a total of 2 seconds from the 4th second to the 6th second) does not exceed a preset duration. The electronic device 100 may determine that the extension duration for extending the display of the microphone icon is 3 seconds based on the preset duration - (the time point when the second access to the microphone permission ends (i.e., the 6th second) - the time point when the second access to the microphone permission starts (i.e., the 4th second)). Therefore, the electronic device 100 may extend the display of the microphone icon in the status bar for 3 seconds from the 6th second. The electronic device 100 may cancel the display of the microphone icon in the status bar at the 9th second.In the scenario shown in FIG. 16C where the recorder application accesses the microphone permission, it can be seen that the electronic device 100 may continuously display the microphone icon in the status bar from the 1st second to the 9th second (a total duration of 8 seconds).

[0336] From the scenarios of FIGS. 16A to 16C, when the access duration of the accessed device permission is excessively short, after the permission visitor finishes accessing, the electronic device 100 extends the display duration of the device permission icon and still continuously displays the device permission icon in the status bar for a certain period, so that the display duration of the device permission can reach the preset duration. It can be seen that the above method can avoid the frequent flashing of the device permission icon displayed in the status bar when the device permission is frequently accessed, prevent the electronic device 100 from frequently refreshing the device permission icon displayed in the status bar, improve the experience of the user browsing the status bar, and reduce the power consumption of the electronic device 100 for refreshing the device permission icon.

[0337] Hereinafter, the sensitive behavior reminder method provided in the embodiments of the present application will be described.

[0338] FIGS. 17A to 17E are flowcharts of an example of the sensitive behavior reminder method according to an embodiment of the present application. This method is applicable to the electronic device 100 and the communication system 30 described in the foregoing embodiments. From the embodiment shown in FIG. 4, it can be seen that the electronic device 100 may include a device permission provision service 410, an application behavior recording module 420, a device permission management service 440, a sensitive behavior reminder module 450, a status bar controller 460, a privacy indicator 470, and a control center module 480.

[0339] As shown in FIGS. 17A to 17E, this method may include steps S1 to S23.

[0340] (1) In steps S1 to S7, when the first type of device permission is accessed, the electronic device 100 displays the device permission icon of the first type of device permission in the status bar.

[0341] In this specification, the camera permission in the first type of device permission is specifically used as an example for explanation. The first type of device permission may further include microphone permission, location permission, etc. For how the electronic device 100 displays the device permission icon in the status bar when another first type of device permission is accessed, refer to how the electronic device 100 displays the camera icon in the status bar.

[0342] S1: The device permission management service 440 may register a listener with the application behavior recording module 420.

[0343] In a possible implementation, the device permission management service 440 may register a listener with the application behavior recording module 420. The listener may instruct the application behavior recording module 420 to send the access information of the first type of device permission to the device permission management service 440 when the access to the first type of device permission of the electronic device 100 is detected.

[0344] The time when the device permission management service 440 registers the listener is not limited in this embodiment of the present application. For example, the device permission management service 440 may register a listener with the application behavior recording module 420 after the electronic device 100 receives a power-on operation.

[0345] S2: The permission visitor may access the camera permission from the device permission provisioning service 410.

[0346] In this application, the authorized visitor may be each application on the electronic device 100, or may be an electronic device other than the electronic device 100 (for example, the electronic device 200 or the electronic device 201).

[0347] The authorized visitor may send a request to the device permission provisioning service 410 to access the camera permission. The device permission provisioning service 410 may determine whether the authorized visitor is eligible to access the camera permission. If it is determined that the authorized visitor is eligible to access the camera permission, the device permission provisioning service 410 may enable the authorized visitor to access the camera permission, whereby the authorized visitor can call the camera service of the electronic device 100 and capture an image by using the camera of the electronic device 100. Alternatively, if it is determined that the authorized visitor is not eligible to access the camera permission, the device permission provisioning service 410 may reject the authorized visitor's access to the camera permission.

[0348] S3: The device permission provisioning service 410 may send message 1 to the application behavior recording module 420, where message 1 includes visitor information and the time when the access to the camera permission started.

[0349] After enabling the authorized visitor to access the camera permission, the device permission provisioning service 410 may send message 1 to the application behavior recording module 420 to notify the application behavior recording module 420 that the camera permission has been accessed. Message 1 may include the visitor information and the time when the access to the camera permission started. For example, if the authorized visitor is application 1 within the electronic device 100, the information about the visitor in message 1 may be the identifier of application 1. If the authorized visitor is the electronic device 200, the information about the visitor in message 1 may be the identifier of the electronic device 200. The content included in message 1 is not limited in this embodiment of the present application. Message 1 may include even more content.

[0350] S4: The application behavior recording module 420 may send message 2 to the device permission management service 440, where message 2 includes the visitor information and the time when the access to the camera permission started.

[0351] Since the device permission management service 440 registers a listener with the application behavior recording module 420, after receiving message 1, the application behavior recording module 420 may send message 2 to the device permission management service 440 to notify the device permission management service 440 that the camera permission has been accessed.

[0352] S5: The device permission management service 440 may send message 3 to the sensitive behavior reminder module 450, where message 3 includes the visitor information and the time when the access to the camera permission started.

[0353] S6: The sensitive behavior reminder module 450 may update the access information of the camera permission based on message 3.

[0354] In a possible implementation form, the sensitive behavior reminder module 450 may store the access information of the first type of device permission in the cache. When receiving message 3, the sensitive behavior reminder module 450 may update the cache and store the access information of the last accessed camera permission. The access information may include information about the visitor who accessed the last accessed camera permission and the access start time.

[0355] S7: The sensitive behavior reminder module 450 may send message 4 to the status bar controller 460, where message 4 instructs to display a camera icon in the status bar.

[0356] Based on message 3, the sensitive behavior reminder module 450 can further send message 4 to the status bar controller 460 to instruct the status bar to refresh the device permission icon displayed in the status bar.

[0357] Upon receiving message 4, the status bar controller 460 may display a camera icon in the status bar to notify the user that the camera permission has been accessed. For the scenario where the status bar controller 460 displays the device permission icon of the first type of device permission in the status bar, refer to the scenarios shown in FIGS. 6A to 6C, FIGS. 7A, and FIGS. 7B.

[0358] In some embodiments, the application behavior recording module 420 may further detect that the electronic device 100 has accessed the device permission of another electronic device, for example, the electronic device 200. When detecting that the electronic device 100 accesses the device permission of the electronic device 200, the application behavior recording module 420 may send access information indicating that the device permission of the electronic device 200 has been accessed to the device permission management service 440. The device permission management service 440 may send the access information indicating that the device permission of the electronic device 200 has been accessed to the sensitive behavior reminder module 450. Further, the sensitive behavior reminder module 450 may instruct the status bar controller 460 to display the device permission icon of the accessed device permission of the electronic device 200 on the status bar.

[0359] For the scenario where the status bar controller 460 displays the device permission icon of the device permission of the electronic device 200 accessed by the first electronic device on the status bar, refer to the foregoing scenario shown in FIGS. 10I to 10K.

[0360] (2) In steps S8 to S10, the second type of device permission is accessed, and the electronic device 100 stores the access information of the second type of device permission.

[0361] In this specification, the contact permission in the second type of device permission is specifically used as an example for explanation. The second type of device permission may further include media and file permissions, device information permissions, call recording permissions, and the like.

[0362] S8: The permission visitor may access the contact permission from the device permission provisioning service 410.

[0363] An authorized visitor may send a request to the device permission provisioning service 410 to access the contact permission. The device permission provisioning service 410 may determine whether the authorized visitor is eligible to access the contact permission. If it is determined that the authorized visitor is eligible to access the contact permission, the device permission provisioning service 410 may enable the authorized visitor to access the contact permission, whereby the authorized visitor can call the contact service of the electronic device 100 to obtain the contact information of the electronic device 100. Alternatively, if it is determined that the authorized visitor is not eligible to access the contact permission, the device permission provisioning service 410 may reject the authorized visitor's access to the contact permission.

[0364] S9: The device permission provisioning service 410 may send message 5 to the application behavior recording module 420, where message 5 includes visitor information and the access time of the contact permission.

[0365] After enabling the authorized visitor to access the contact permission, the device permission provisioning service 410 may send message 5 to the application behavior recording module 420 to notify the application behavior recording module 420 that the contact permission has been accessed.

[0366] S10: The application behavior recording module 420 may store the visitor information and the access time of the contact permission based on message 5.

[0367] (3) In steps S11 to S17, the control center interface is opened, and the control center interface displays a sensitive behavior prompt indicating that the first type of device permission and the second type of device permission have been accessed.

[0368] S11: The control center module 480 detects an operation to open the control center interface at time ta.

[0369] For the operation of opening the control center interface, refer to the aforementioned operation shown in FIG. 5A.

[0370] When detecting the operation of opening the control center interface, the control center module 480 may trigger the electronic device 100 to display the control center interface. For the control center interface, refer to the control center interface shown in FIG. 5B.

[0371] In some embodiments, at time ta, the authorized visitor still has access to the camera permission of the electronic device 100.

[0372] S12: In response to the operation of opening the control center interface, the control center module 480 may send message 6 to the privacy indicator 470, where message 6 instructs to update the sensitive behavior prompt in the control center interface.

[0373] S13: The privacy indicator 470 may request the device permission management service 440 to obtain the access information of the first type of device permission.

[0374] S14: The device permission management service 440 may query the sensitive behavior reminder module 450 about the access information of the first type of device permission.

[0375] S15: The device permission management service 440 may send the access information of the first type of device permission to the privacy indicator 470.

[0376] In a possible implementation form, when an operation to open the control center interface is received, the privacy indicator 470 may request to obtain which first type of device permission of the electronic device 100 is accessed. From the above steps S2 to S7, it can be seen that the permission visitor is accessing the camera permission. In this case, the access information of the first type of device permission transmitted to the privacy indicator 470 by the device permission management service 440 may include the access information of the camera permission.

[0377] S16: The privacy indicator 470 may obtain, from the application behavior recording module 420, the access information of the second type of device permission during the period T1, where the period T1 is a preset period before the time point ta.

[0378] From the above characteristics of the second type of device permission, it can be seen that the action of the permission visitor accessing the second type of device permission is usually a separate action and may not continue for a certain period. The privacy indicator 470 may request to obtain the access information of the permission visitor accessing the second type of device permission during a preset period (i.e., the period T1) before the operation to open the control center interface is received.

[0379] From the above steps S8 to S10, it can be seen that the permission visitor is accessing the contact permission of the electronic device 100. If the access time when the permission visitor accesses the contact permission is within the period T1, the application behavior recording module 420 transmits the access information indicating that the permission visitor accessed the contact permission in steps S8 to S10 to the privacy indicator 470.

[0380] It can be understood that the application behavior recording module 420 may further query the access records of other visitors during the period T1 and transmit the access information corresponding to the access records to the privacy indicator 470.

[0381] S17: The privacy indicator 470 may summarize the access information of the first type of device permission and the second type of device permission, and display a sensitive behavior prompt on the control center interface.

[0382] Regarding the sensitive behavior prompt displayed on the control center interface by the privacy indicator 470, refer to the sensitive behavior prompt 813 shown in FIG. 8A.

[0383] (4) In steps S18 to S23, when the access to the first type of device permission ends, the electronic device 100 cancels the display of the device permission icon of the first type of device permission in the status bar.

[0384] S18: The permission visitor ends the access to the camera permission.

[0385] S19: The device permission provision service 410 may send message 7 to the application behavior recording module 420, where message 7 includes the visitor information and the time when the access to the camera permission ends.

[0386] S20: The application behavior recording module 420 may send message 8 to the device permission management service 440, where message 8 includes the visitor information and the time when the access to the camera permission ends.

[0387] Since the device permission management service 440 registers a listener with the application behavior recording module 420, after receiving message 7, the application behavior recording module 420 may send message 8 to the device permission management service 440 to notify the device permission management service 440 that the permission visitor has ended the access to the camera permission.

[0388] S21: The device permission management service 440 may send message 9 to the sensitive behavior reminder module 450, where message 9 includes visitor information and the time when access to the camera permission ended.

[0389] S22: The sensitive behavior reminder module 450 may update the access information of the camera permission based on message 9.

[0390] The access information of the camera permission may include information about the visitor who last accessed the camera permission and the time when the access ended.

[0391] S23: The sensitive behavior reminder module 450 may send message 10 to the status bar controller 460, where message 10 instructs to cancel the display of the camera icon in the status bar.

[0392] The sensitive behavior reminder module 450 may send message 10 to the status bar controller 460 based on message 9 and instruct the status bar to refresh the device permission icon displayed in the status bar.

[0393] In a possible implementation, upon receiving message 10, the status bar controller 460 may cancel the display of the camera icon in the status bar.

[0394] In another possible implementation, when receiving the message 10, the status bar controller 460 may determine, by using a delay compensation mechanism, the time point at which the display of the camera icon in the status bar is cancelled. The status bar controller 460 determines an access duration based on the time point when the access to the camera permission starts and the time point when the access to the camera permission ends, compares the access duration with a preset duration, and may determine whether to extend the display time of the camera icon in the status bar. For the delay compensation mechanism, refer to the description of the foregoing embodiments. Details will not be described again in this specification.

[0395] It should be noted that the foregoing steps S18 to S23 may be performed after the electronic device 100 folds the control center interface. In the process of the electronic device 100 displaying the control center interface, if the authorized visitor ends the access to the camera permission, the electronic device 100 may leave the sensitive behavior prompt displayed on the control center interface unchanged. The sensitive behavior prompt in the control center interface may still include the camera icon for the camera permission. Then, the electronic device 100 may fold the control center interface. The electronic device 100 may cancel the display of the camera icon in the status bar of the user interface displayed after the control center interface is folded.

[0396] In this embodiment of the present application, it can be understood that the sensitive behavior reminder method provided in the present application is specifically described by using an example in which a sensitive behavior prompt is displayed on a control center interface. The sensitive behavior prompt is not limited to the control center interface and may be displayed on another user interface, for example, a pull-down notification interface.

[0397] When it is detected from the method shown in FIGS. 17A to 17E that device permission is accessed by an application on the electronic device 100 or another electronic device, the electronic device 100 may display a device permission icon in the status bar and / or the control center interface, whereby the user can know and control the sensitive behavior of the applications on the device and the cross-device sensitive behavior. The sensitive behavior reminder provided by the electronic device 100 includes a reminder of the access of a first type of device permission such as camera permission or microphone permission, and may further include a reminder of the access of a second type of device permission such as contact permission, media A oh and file permission. Therefore, the user can more intuitively and conveniently know the access data of each device permission. In addition, the electronic device 100 may further display a device permission icon in the status bar by using a delay compensation mechanism to notify the user that the corresponding device permission has been accessed. The delay compensation mechanism can avoid the frequent blinking of the device permission icon displayed in the status bar, prevent the electronic device 100 from frequently refreshing the device permission icon displayed in the status bar, improve the user experience of browsing the status bar, and can be used to reduce the power consumption of the electronic device 100 for refreshing the device permission icon.

[0398] It can be understood that each user interface described in the embodiments of the present application is only an exemplary interface and does not constitute a limitation to the solutions of the present application. In another embodiment, the user interface may use a different interface layout, may include more or fewer controls, may add or reduce other function options, and as long as the user interface is based on the same inventive idea provided in the present application, all fall within the protection scope of the present application.

[0399] In the case where no contradiction or opposition occurs, any feature or any part of any feature in any embodiment of the present application may be combined, and it should be noted that the combined technical solution also falls within the scope of the embodiments of the present application.

[0400] In conclusion, the foregoing embodiments are only for explaining the technical solution of the present application and not for limiting the present application. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still make changes to the technical solutions described in the foregoing embodiments or perform equivalent substitutions for some of its technical features without departing from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An application-sensitive behavior reminder method, comprising: receiving, by a first electronic device, a first request from a second electronic device, the first request being used to request access to a first device permission of the first electronic device; in response to the first request, enabling, by the first electronic device, the second electronic device to access the first device permission and displaying a first icon in a status bar, the first icon indicating that the first device permission is accessed; receiving, by the first electronic device, a first operation; displaying, by the first electronic device, a first interface in response to the first operation, the first interface including a first prompt, the first prompt including the first icon. A method comprising the above steps.

2. receiving, by the first electronic device, a second operation on the first prompt; displaying, by the first electronic device, a first permission list in response to the second operation, the first permission list including first information, the first information indicating that the first device permission is accessed by the second electronic device. The method according to claim 1, further comprising the above steps.

3. receiving, by the first electronic device, a third operation on the first information; displaying, by the first electronic device, a first control in response to the third operation, the first control being used to manage access of the second electronic device to the first device permission. The method according to claim 2, further comprising the above steps.

4. After the step of receiving, by the first electronic device, the first operation, the method further comprises: A step of querying, by the first electronic device, an access record of access to a device permission of the first electronic device in a first period to obtain a first access record, where the first period is a period before the first operation is received, and the first access record includes first access data of access to the first device permission by the second electronic device further comprising A step of displaying, by the first electronic device, a first interface, where the first interface includes a first prompt, and in particular A step of displaying, by the first electronic device, the first interface based on the first access record, where the first interface includes the first prompt, and the first icon included in the first prompt is determined based on the first access data The method according to any one of claims 1 to 3, including

5. The first access record further includes access data for accessing K device permissions of the first electronic device, where K is a positive integer The first prompt in the first interface further includes K icons, and the K icons respectively indicate that the K device permissions are accessed The method according to claim 4

6. The first icon and the K icons included in the first prompt are folded and displayed based on a first priority The first priority indicates the priority of the device permissions of the first electronic device. A device permission with a higher priority in the first priority is indicated by an icon indicating that the device permission is accessed being displayed at a higher level in the first interface. The icon displayed in the upper layer partially blocks the icon displayed in the lower layer The first prompt further includes an identifier of a visitor of a device permission corresponding to the icon displayed at the highest level in the first prompt The method according to claim 5

7. A step of detecting, by the first electronic device, that the second electronic device has terminated access to the first device permission The step of canceling the display of the first icon in the status bar by the first electronic device The method according to any one of claims 1 to 6, further comprising.

8. Before the step of canceling the display of the first icon in the status bar by the first electronic device, the method comprises: The step of determining by the first electronic device that a first access duration during which the second electronic device accesses the first device permission exceeds a first duration The method according to claim 7, further comprising.

9. The step of detecting by the first electronic device that the second electronic device has terminated access to the first device permission; and The step of determining by the first electronic device whether a first access duration during which the second electronic device accesses the first device permission exceeds a first duration; and When it is determined that the first access duration does not exceed the first duration, the step of determining, by the first electronic device, a first extended duration based on a difference between the first access duration and the first duration; and The step of continuously displaying the first icon in the status bar by the first electronic device in a second period, where the second period is a period within the first extended duration starting from the time when the second electronic device terminates access to the first device permission The method according to any one of claims 1 to 6, further comprising.

10. The step of detecting by the first electronic device a re-access to the first device permission in the second period; and The step of continuously displaying the first icon in the status bar by the first electronic device during the period of re-access to the first device permission; and The step of determining by the first electronic device whether a second access duration of the re-access to the first device permission exceeds the first duration; and When it is determined that the second access duration exceeds the first duration, the step of canceling the display of the first icon in the status bar by the first electronic device at the time when the re-access to the first device permission ends, or When it is determined that the second access duration does not exceed the first duration, a step of determining, by the first electronic device, a second extended duration based on a difference between the second access duration and the first duration; A step of continuously displaying, by the first electronic device, the first icon in the status bar in a third period, where the third period is a period within the second extended duration starting from the time when the re-access of the first device permission ends; The method according to claim 9, further comprising.

11. A step of receiving, by the first electronic device, a fourth operation; A step of displaying, by the first electronic device, a second control in response to the fourth operation, where the second control is used to manage the access of the second electronic device to the device permission of the first electronic device, or A step of displaying, by the first electronic device, a third control in response to the fourth operation, where the third control is used to manage the access of a different application on the second electronic device to the device permission of the first electronic device; The method according to any one of claims 1 to 10, further comprising.

12. After the step of receiving, by the first electronic device, the first operation, the method comprises: A step of querying, by the first electronic device, an access record of access to the device permission of another electronic device by the first electronic device in the first period to obtain a second access record, where the first period is the period before the first operation is received, and the second access record includes access data of access to the second device permission of a third electronic device by the first electronic device; further comprising, The first interface further includes a second prompt, where the second prompt is determined based on the second access record, and the second prompt indicates that the first electronic device accesses the second device permission of the third electronic device; The method according to any one of claims 1 to 11.

13. The device permission of the first electronic device includes camera permission, microphone permission, location permission, contact permission, and media and file permission, and the method according to any one of claims 1 to 12.

14. The first operation is an operation of sliding down from the upper right of the screen of the first electronic device, and the first interface is the control center interface of the first electronic device, and the method according to any one of claims 1 to 13.

15. An electronic device, the electronic device includes a screen, a memory, and one or more processors, the memory is configured to store a computer program, and the one or more processors are configured to call the computer program, whereby the electronic device executes the method according to any one of claims 1 to 14.

16. A computer-readable storage medium, including instructions, when the instructions are executed on an electronic device, the electronic device can execute the method according to any one of claims 1 to 14.

17. A computer program product, the computer program product includes computer instructions, when the computer instructions are executed on an electronic device, the electronic device can execute the method according to any one of claims 1 to 14.

Images