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] The present application relates to the field of terminal technology, and in particular to an application sensitive behavior reminding method, a related apparatus, and a communication system. [Background Art]

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

[0003] Therefore, electronic devices need to monitor sensitive behaviors and provide users with sensitive behavior reminders, so that users can know the specific accessed device permissions of the electronic device and the specific user information obtained by a specific application, and users can manage the device permissions that can be accessed by the application based on the sensitive behavior of the application. This prevents applications 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, associated apparatus, and communication system. According to this method, sensitive behavior prompts indicating that device permissions are being accessed can be displayed on the status bar and / or control center interface of an electronic device to remind the user of sensitive and cross-device sensitive behavior of an application on the device. In addition, the user can further manage device permissions based on the sensitive behavior prompts displayed on the control center interface. According to the aforementioned method, it may be convenient for the user to know about and control sensitive and cross-device sensitive behavior of an application on the device.

[0005] According to a first aspect, the present application provides an application-sensitive behavior reminder method. A first electronic device may receive a first request from a second electronic device, the first request being used to request access to a first device authorization 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 authorization and display a first icon in the status bar, the first icon indicating that the first device authorization has been accessed. The first electronic device receives a first operation. In response to the first operation, the first electronic device may display a first interface, the first interface including a first prompt, the first prompt including a first icon.

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

[0007] From the method described above, it can be seen that when the first electronic device detects that device permissions are being accessed, it may display a device permissions icon in the status bar and / or control center interface. Visitors to device permissions may include applications on the first electronic device and devices other than the first electronic device, such as a second electronic device. According to the method described above, this can be convenient for the user to intuitively know about sensitive behavior on the first electronic device based on the status bar or by calling the first interface, and the user can know about and control the sensitive behavior of applications on the device and cross-device sensitive behavior.

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

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

[0010] Referring to the first aspect, in some embodiments, a first electronic device receives a third operation on first information. In response to the third operation, the first electronic device may display a first control, which is used to manage the second electronic device's access to first device authorization. The first control may be used to adjust the conditions for the second electronic device to access the first device authorization. For example, the second electronic device may always be able to access the first device authorization, or the first electronic device may need to query the user each time the second electronic device tries to access the first device authorization. Optionally, the first control may be used to prevent the second electronic device from accessing the first device authorization. The third operation may be, for example, a tap or touch operation on the first information.

[0011] From the embodiments described above, it can be seen that users can quickly manage visitors to device permissions based on sensitive behavior prompts (e.g., the first prompt) displayed on the first interface of the first electronic device. This reduces the misuse 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 a first operation, the first electronic device may further query the access record of access to the device authorization of the first electronic device during a first period to obtain a first access record, the first period being the period before the first operation is received, and the first access record includes first access data of the second electronic device accessing the first device authorization. Based on the first access record, the first electronic device may display a first interface, the first interface including a first prompt, and a first icon included in the first prompt being determined based on the first access data.

[0013] From the embodiments described above, it can be seen that after receiving a first operation that invokes the first interface, the first electronic device may obtain a record of sensitive behaviors accessed in the most recent period (i.e., the first period) for the device authorization of the first electronic device. The first electronic device may then display a sensitive behavior prompt on the first interface indicating the device authorization accessed in the most recent period. In this way, in addition to the currently accessed device authorization, the user can more quickly learn about sensitive behaviors that have occurred in the first electronic device in the most recent period.

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

[0015] Referring to the first aspect, in some embodiments, the first icon and K icons included in the first prompt are displayed collapsed based on a first priority. The first priority indicates the priority of device permissions for the first electronic device, where higher priority device permissions in the first priority indicate that icons indicating that the device permission is accessed are displayed at a higher level in the first interface, and icons displayed in higher layers partially block icons displayed in lower layers. The first prompt further includes an identifier for the device permission visitor corresponding to the icon displayed at the highest level in the first prompt.

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

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

[0018] When the first electronic device detects that a first type of device permission is being accessed, it may display a first type of device permission icon in its status bar. The first device permission may be a single first type of device permission. When the first electronic device receives the first operation, the second electronic device still has access to the first device permission.

[0019] Upon receiving a first operation to invoke a first interface, the first electronic device may query access logs to see if a first type of device authorization is currently being accessed and if a second type of device authorization has been accessed in a recent period (e.g., a first period). The first electronic device may then display a first prompt on the first interface based on the query results.

[0020] In other words, the K icons included in the first prompt may include a first type of device permission icon and 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 its access to the first device authorization. The first electronic device removes the display of the first icon in the status bar.

[0022] Referring to the first aspect, in some embodiments, before the first electronic device clears 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 authorization exceeds the first duration. If it determines that the first access duration for the second electronic device to access the first device authorization exceeds the first duration, the first electronic device may directly clear the display of the first icon in the status bar when the second electronic device terminates its access to the first device authorization.

[0023] Referring to the first aspect, in some embodiments, the first electronic device detects that the second electronic device has terminated its access to the first device authorization. The first electronic device determines whether the first access duration for the second electronic device to access the first device authorization exceeds the first duration. If it determines 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 for a second period, the second period being a period within the first extended duration that begins from the time the second electronic device terminated its access to the first device authorization.

[0024] Referring to the first aspect, in some embodiments, the first electronic device detects the re-access of the first device permission during a second period. The first electronic device continues to display the first icon in the status bar during the re-access period of the first device permission. The first electronic device determines whether the second access duration of the re-access of the first device permission exceeds the first duration. If it determines that the second access duration exceeds the first duration, the first electronic device removes the display of the first icon in the status bar when the re-access of the first device permission ends. Alternatively, if it determines 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, the third period being a period within the second extended duration starting from when the re-access of the first device permission ended.

[0025] From the embodiments described above, it can be seen that when the access duration of the accessed device permission is excessively short, the first electronic device may extend the display duration of the device permission icon after the permission visitor has finished accessing it, so that the device permission icon continues to be displayed in the status bar for a certain period of time, thereby causing the display duration of the device permission to reach a preset duration. The described method may be used to avoid the device permission icon displayed in the status bar flashing frequently when the device permission is accessed frequently, to prevent the first electronic device from frequently refreshing the device permission icon displayed in the status bar, to improve the user experience when browsing the status bar, and to 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 device permissions 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 device permissions of the first electronic device.

[0027] It can be seen from the foregoing embodiments that a user can manage cross-device sensitive behavior on the first electronic device, and allow or prohibit another electronic device (for example, the second electronic device) from accessing device permissions 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, to adjust whether each application on the electronic device can access device permissions of the first electronic device. 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 first electronic device. This can better meet the usage requirements of the user and improve the security of the user's privacy information.

[0028] Referring to the first aspect, in some embodiments, after the first electronic device receives the first operation, the first electronic device may further query an access record of access to device permission of another electronic device by the first electronic device within a first period to obtain a second access record, wherein the first period is a 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. The first interface further includes a second prompt, 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.

[0029] In a possible implementation, the first electronic device can find 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 access to the second device permission of the third electronic device by a 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 for the second prompt and display a fourth control based on the operation. The fourth control can 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 embodiments described above, it can be seen that the user may perform further operations on the first electronic device in order to separately perform permission management for each application on the first electronic device. This coordinates each application on the first electronic device's access to device permissions on another electronic device (e.g., a third electronic device). In other words, the user may authorize different applications on the first electronic device to access different device permissions on another electronic device, based on requirements and privacy security considerations. This can better meet the user's usage requirements and improve the security of user privacy information.

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

[0033] The aforementioned operation of calling the first interface is simple and may be convenient for the user to quickly call the first interface (i.e., the control center interface) to view the sensitive behavior of the first electronic device over the past 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 transmit a first request to the first electronic device, the first request being used to request access to a first device authorization of the first electronic device. The first electronic device may, based on the first request, enable the second electronic device to access the first device authorization and display a first icon in the status bar, the first icon indicating that the first device authorization has been 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 including a first prompt, and the first prompt including a first icon.

[0035] Enabling a second electronic device to access a first device authorization may include the first electronic device providing the second electronic device with a service corresponding to the first device authorization. For example, if the first device authorization is a camera authorization, 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 transmit the captured image to the second electronic device. The second electronic device may display the image from the first electronic device.

[0036] Referring to a 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 permissions of the first electronic device. When the application on the first electronic device detects that it has accessed the device permissions of the first electronic device, the first electronic device may be configured to display an accessed device permissions icon in its status bar. In addition, the first interface may include an accessed device permissions icon in addition to the first icon in the first prompt.

[0037] From the method described above, it can be seen that when the first electronic device detects that device permissions are being accessed, it may display a device permissions icon in the status bar and / or control center interface. Visitors to device permissions may include applications on the first electronic device and devices other than the first electronic device, such as a second electronic device. According to the method described above, this can be convenient for the user to intuitively know about sensitive behavior on the first electronic device based on the status bar or by calling the first interface, and the user can know about and control the sensitive behavior of applications on the device and cross-device sensitive behavior.

[0038] Referring to a second aspect, in some embodiments, the first electronic device may be configured to receive a second operation in response to a first prompt and to display a first authorization list based on the second operation, the first authorization list containing first information, the first information indicating that the first device authorization is accessed by the second electronic device.

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

[0040] Referring to a second aspect, in some embodiments, a first electronic device may be configured to receive a third operation on first information and to display a first control based on the third operation, the first control being used to manage the second electronic device's access to a first device authorization. The first control may be used to adjust the conditions for the second electronic device to access the first device authorization. For example, the second electronic device may always be able to access the first device authorization, or the first electronic device may need to query the user each time the second electronic device tries to access the first device authorization. Optionally, the first control may be used to prevent the second electronic device from accessing the first device authorization.

[0041] From the embodiments described above, it can be seen that users can quickly manage visitors to device permissions based on sensitive behavior prompts (e.g., the first prompt) displayed on the first interface of the first electronic device. This reduces the misuse of device permissions and improves the security of user privacy information.

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

[0043] From the embodiments described above, it can be seen that after receiving a first operation that invokes the first interface, the first electronic device may obtain a record of sensitive behaviors accessed in the most recent period (i.e., the first period) for the device authorization of the first electronic device. The first electronic device may then display a sensitive behavior prompt on the first interface indicating the device authorization accessed in the most recent period. In this way, in addition to the currently accessed device authorization, the user can more quickly learn about sensitive behaviors that have occurred in the first electronic device in the most recent period.

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

[0045] Referring to a second aspect, in some embodiments, the first icon and K icons included in the first prompt are displayed collapsed based on a first priority. The first priority indicates the priority of device permissions for a first electronic device, where higher priority device permissions in the first priority indicate that icons indicating that the device permission is accessed are displayed at a higher level in the first interface, and icons displayed in higher layers partially block icons displayed in lower layers. The first prompt further includes an identifier for the device permission visitor corresponding to the icon displayed at the highest level in the first prompt.

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

[0047] Referring to a second aspect, in some embodiments, the first electronic device may be configured to clear the display of the first icon in the status bar when it detects that the second electronic device has terminated its access to the first device authorization.

[0048] Referring to a second aspect, in some embodiments, the first electronic device may be configured to determine whether the first access duration for the second electronic device to access the first device authorization exceeds the first duration before removing the display of the first icon in the status bar. If the first electronic device determines that the first access duration for the second electronic device to access the first device authorization exceeds the first duration, the first electronic device may be configured to directly remove the display of the first icon in the status bar when the second electronic device terminates its access to the first device authorization.

[0049] Referring to a second aspect, in some embodiments, the first electronic device may be configured to determine whether the first access duration for the second electronic device to access the first device authorization exceeds the first duration when it detects that the second electronic device has terminated its access to the first device authorization. If it determines 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 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 for a second period, the second period being a period within the first extended duration that begins from the time the second electronic device terminated its access to the first device authorization.

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

[0051] From the embodiments described above, it can be seen that when the access duration of the accessed device permission is excessively short, the first electronic device may extend the display duration of the device permission icon after the permission visitor has finished accessing it, so that the device permission icon continues to be displayed in the status bar for a certain period of time, thereby causing the display duration of the device permission to reach a preset duration. The described method may be used to avoid the device permission icon displayed in the status bar flashing frequently when the device permission is accessed frequently, to prevent the first electronic device from frequently refreshing the device permission icon displayed in the status bar, to improve the user experience when browsing the status bar, and to reduce the power consumption of the first electronic device for refreshing the device permission icon.

[0052] Referring to a 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, the second control being used to manage the second electronic device's access to the device authorization of the first electronic device. Alternatively, the first electronic device may display a third control based on the fourth operation, the third control being used to manage the access of different applications on the second electronic device to the device authorization of the first electronic device.

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

[0054] From the embodiments described above, it can be seen that when the second electronic device accesses the device authorization of another electronic device, the second electronic device may also display a sensitive behavior prompt in the status bar or a fifth interface (e.g., the control center interface) to inform the user of this sensitive behavior of the second electronic device accessing the device authorization of another electronic device.

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

[0056] Access by a second electronic device to a first device authorization in the first electronic device may specifically mean that a second application on the second electronic device accesses the first device authorization in the first electronic device. The second information may include an identifier for the second application to inform the user that the second application on the second electronic device is accessing the first device authorization in the first electronic device.

[0057] Referring to a second aspect, in some embodiments, a second electronic device may be configured to receive a seventh operation on second information and to display a fifth control based on the seventh operation. The fifth control is a second application on the second electronic device that is connected to the first device. permission It can be used to manage permissions for accessing [something].

[0058] From the embodiments described above, it can be seen that the user may perform further operations on the second electronic device in order to separately perform permission management for each application on the second electronic device. This coordinates each application on the second electronic device's access to device permissions on another electronic device (e.g., the first electronic device). In other words, the user may authorize different applications on the second electronic device to access different device permissions on another electronic device, based on requirements and privacy security considerations. This can better meet the user's usage requirements and improve the security of user privacy information.

[0059] According to a third aspect, the present application provides an electronic device, which may include a screen, memory, and one or more processors. The memory may be configured to store computer programs. One or more processors may be configured to invoke computer programs, thereby enabling the electronic device to perform the method in any possible implementation of the first aspect.

[0060] According to a fourth aspect, the present application provides a computer-readable storage medium containing instructions. When the instructions are executed on an electronic device, the electronic device becomes capable of performing the method in any possible implementation 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 becomes capable of performing the method in any possible implementation of the first aspect.

[0062] According to a sixth aspect, the present application provides a chip used in an electronic device, the chip comprising one or more processors, the processors configured to call computer instructions, thereby the electronic device performing the method in any possible implementation 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 perform the methods provided in the embodiments of this 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, please refer to the beneficial effects in the corresponding methods. Further details are not described herein. [Brief explanation of the drawing]

[0064] [Figure 1] This is a diagram showing the structure of an electronic device 100 according to one embodiment of this application. [Figure 2] This is a block diagram of the software structure of an electronic device 100 according to one embodiment of this application. [Figure 3] This is a diagram showing the architecture of a communication system according to one embodiment of this application. [Figure 4] This is a diagram showing the structure of a communication system according to one embodiment of this application. [Figure 5A] This is a diagram of the interface of an electronic device 100 according to one embodiment of this application. [Figure 5B] This is a diagram of the interface of an electronic device 100 according to one embodiment of this application. [Figure 6A] This is a diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 6B] This is a diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 6C] This is a diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 6D] This is a diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 7A] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 7B] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 7C] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 8A] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 8B] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 8C]This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 9A] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 9B] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 9C] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10A] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10B] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10C] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10D] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10E] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10F] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10G] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10H] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10I] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10J] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10K] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 10L] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 11A] This is a diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 11B] This is a diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 11C] This is a diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 12A] This is another diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 12B] This is another diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 12C] This is another diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 13A] This is another diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 13B] This is another diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 13C] This is another diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 13D] This is another diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 13E] This is another diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 14A] This is another diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 14B] This is another diagram of a sensitive behavior management scenario according to one embodiment of the present application. [Figure 15A] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 15C] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 15D] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 15E]This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 15F] This is another diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 16A] This is a diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 16B] This is a diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 16C] This is a diagram of a sensitive behavior reminder scenario according to one embodiment of the present application. [Figure 17A] This is a flowchart of a sensitive behavior reminder method according to one embodiment of this application. [Figure 17B] This is a flowchart of a sensitive behavior reminder method according to one embodiment of this application. [Figure 17C] This is a flowchart of a sensitive behavior reminder method according to one embodiment of this application. [Figure 17D] This is a flowchart of a sensitive behavior reminder method according to one embodiment of this application. [Figure 17E] This is a flowchart of a sensitive behavior reminder method according to one embodiment of this application. [Modes for carrying out the invention]

[0065] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. In describing the embodiments of this application, the terms used in the following embodiments are intended solely to describe specific embodiments and are not intended to limit this application. The singular terms “one,” “the,” “the preceding,” “this,” and “the one” as used in this specification and the accompanying claims are intended to also include expressions such as “one or more,” unless explicitly specified otherwise in the context. In the following embodiments of this application, it should be further understood that “at least one” and “one or more” mean one or more (including two). The terms “and / or” are used to describe a relationship between related objects and indicate that three relationships may exist. For example, A and / or B may indicate that only A exists, both A and B exist, and 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,” etc., described herein indicate that one or more embodiments of this application include certain features, structures, or characteristics described with reference to the embodiments. Thus, phrases such as “in one embodiment,” “in some embodiments,” “in some other embodiments,” and “in other embodiments,” appearing elsewhere in this specification, do not necessarily refer to the same embodiment. Rather, these phrases mean “one or more embodiments, but not all of them,” unless otherwise specifically emphasized. The terms “include,” “have,” and their variations all mean “include, but not limited to,” unless otherwise specifically emphasized. “Connections” include direct and indirect connections unless otherwise specified. “First” and “second” are intended solely for illustrative purposes and should not be understood as indicating or implying the relative importance of the quantity of technical features shown or any implicit reference.

[0067] In the embodiments of this application, terms such as “example” and “for example” are used to provide examples, illustrations, or explanations. Any embodiment or design described as “example” or “for example” in the embodiments of this application should not be construed as being preferable or advantageous to another embodiment or design. More precisely, the use of terms such as “example” and “for example” is intended to present the relevant concepts in a particular manner.

[0068] In the following embodiments of this application, the term "user interface (UI)" refers to a medium interface for interaction and information exchange between an application (APP) or operating system (OS) and a user, enabling the conversion of information between its internal format and a format acceptable to the user. A user interface is source code written in a specific computer language, such as Java® or an extensible markup language (XML). The interface source code is parsed and rendered on an electronic device and ultimately presented as user-identifiable content. A user interface is typically represented in the form of a graphical user interface (GUI), which is a user interface related to computer operation and displayed graphically. A user interface can be a visual interface element, 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 may monitor device permission access data. The device permission access data may include data on access to the device permission by an application on the electronic device, and may further include data on access to the device permission of the electronic device by another electronic device (i.e., an application on another electronic device). When the electronic device detects that the device permission is being accessed, it may display a device permission icon in the status bar to inform the user that the device permission corresponding to the device permission icon is being accessed. When the electronic device detects that the device permission is being accessed, it may further display a device permission icon in the control center interface to inform the user that the device permission corresponding to the device permission icon is being accessed. The control center interface may integrate the control with functions such as media playback control functions and shortcut switch functions (such as Bluetooth® switches and wireless local area network switches). An electronic device may provide controls used to manage device permissions in response to operations on a device permission icon within a control center interface, thereby allowing the user to manage device permissions for electronic devices that an application on the electronic device can access, and device permissions for electronic devices that another electronic device (or an application on another electronic device) can access.

[0070] As described above, when an electronic device detects that device permissions are being accessed, it may display a device permissions icon in the status bar and / or control center interface, allowing the user to know and control sensitive and cross-device sensitive behavior of applications on the device.

[0071] In some embodiments, device authorization for an electronic device may include a first type of device authorization and a second type of device authorization.

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

[0073] A second type of device permission may refer to a device permission in which the access behavior of a single access can be completed instantaneously. That is, the access behavior of an application making a one-time access to a second type of device permission may be a separate action, without considering the start and end of the access (i.e., without considering the duration of the access). Second types of device permissions may include contact permissions, media and file permissions, device information permissions, call log permissions, etc. For example, when an application makes a one-time access to a contact permission, a request to retrieve contact data may be sent in order to obtain contact data on an electronic device. Sending a request to retrieve contact data may be equivalent to the access behavior of the application making access to the contact permission.

[0074] When the electronic device detects that a first type of device permission is being accessed, it may display a device permission icon in the status bar. For example, when it detects that a camera permission is being accessed, the electronic device may display a camera icon in the status bar to inform the user that all cameras are being accessed. Furthermore, in the process of accessing a first type of device permission, in response to an operation to open the control center interface, the electronic device may display the control center interface and display an icon corresponding to the device permission (e.g., a camera icon) in the control center interface. In addition, the electronic device may further query access data for a second type of device permission within a predetermined period prior to the operation to open the control center interface being received. When it is determined that a second type of device permission has been accessed within the predetermined period, the electronic device may further display a device permission icon in the control center interface. For example, when it is determined that a contact permission has been accessed within the predetermined period, the electronic device may further display a contact icon in the control center interface, in addition to the camera icon, to inform the user that the contact permission is being accessed.

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

[0076] Note that one device permission can correspond to at least one service. Once an application is granted a device permission, the application can access that device permission to invoke the service corresponding to that permission.

[0077] For example, camera permission could correspond to a camera service. A camera service might be a service that captures image data by using a camera. When an application accesses camera permission, the application can call the camera service to retrieve image data.

[0078] In another example, microphone permission could correspond to a microphone service. A microphone service might be a service that captures audio data using a microphone. When an application accesses microphone permission, it can call the microphone service to retrieve audio data.

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

[0080] In another example, contact permission could correspond to a contact service. A contact service might be a service that retrieves contact information on an electronic device. When an application accesses contact permission, the application can call the contact service to retrieve contact information.

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

[0082] Sensitive behavior in this application may represent behavior that accesses device permissions of an electronic device, or behavior that calls a service corresponding to device permissions of an electronic device. Accessing parties to access device permissions of an electronic device may include applications on the electronic device and electronic devices other than the electronic device itself. For example, a communication connection is established between an electronic device and another electronic device. The other electronic device may access the camera permissions of the electronic device to activate the electronic device's camera and acquire image data.

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

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

[0085] As shown in Figure 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 charge 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, and the like.

[0086] It can be understood that the structure shown in this embodiment of the present application does not constitute a particular 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 figures, some components may be combined, some components may be separated, or different component arrangements may be used. The components shown in the figures may be implemented by hardware, software, or a combination of software and hardware.

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

[0088] The controller may be the central and command center of the electronic device 100. The controller may generate operation control signals based on instruction operation codes and time-series signals, and complete the control of instruction fetching and instruction execution.

[0089] Memory may be located within the processor 110 and configured to store instructions and data. In some embodiments, the memory within the processor 110 is a cache. The memory may store instructions or data that have been used or periodically used by the processor 110. When the processor 110 needs to use an instruction or data again, the processor may retrieve the instruction or data directly from memory. This avoids repeated access, reduces latency for the processor 110, and improves system efficiency.

[0090] The USB interface 130 is an interface that conforms to the USB standard specification, and specifically may 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, or to transmit data between the electronic device 100 and peripheral devices, or 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 may be a wireless charger or a wired charger. The charging management module 140 charges the battery 142 while simultaneously supplying power to the electronic device via the power management module 141.

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

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

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

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

[0096] The wireless communication module 160 may provide a wireless communication solution applicable to the electronic device 100, which includes wireless local area networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite systems (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 integrating at least one communication processor module. The wireless communication module 160 receives electromagnetic waves with antenna 2, performs frequency modulation and filtering on the electromagnetic wave signal, and transmits the processed signal to processor 110. The wireless communication module 160 may further receive the signal transmitted from processor 110, perform frequency modulation and amplification on that signal, and convert the signal into electromagnetic waves via antenna 2 for radiation.

[0097] The electronic device 100 may implement display functions via 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 perform mathematical and geometric calculations and to 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 shooting functions via an ISP, camera 193, video codec, GPU, display 194, application processor, etc.

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

[0101] The camera 193 is configured to capture still images or 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] A digital signal processor is configured to process digital signals and may process other digital signals in addition to digital image signals. For example, when electronic device 100 selects a frequency, the digital signal processor is configured to perform a Fourier transform on the frequency energy.

[0103] An NPU is a neural network (NN) computing processor. By referencing the structure of biological neural networks, such as the communication modes between nerve cells in the human brain, an NPU can rapidly process input information and even perform continuous self-learning. Applications such as intelligent cognition in electronic devices 100, including image recognition, face recognition, speech recognition, and text comprehension, can be implemented via an NPU.

[0104] The external memory interface 120 can be used to connect to an external storage card, such as a microSD card, in order to expand the storage capacity of the electronic device 100. memoryThe card communicates with the processor 110 via the external memory interface 120 to implement data storage functionality. Files such as music and videos are stored on the external storage card.

[0105] The internal memory 121 may be configured to store computer executable program code. The executable program code includes instructions. The processor 110 executes 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 the 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 high-speed random access memory, or non-volatile memory, such as at least one magnetic disk storage device, flash memory, or universal flash storage (UFS).

[0106] The electronic device 100 can 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, and the like.

[0107] The audio module 170 is configured to convert digital audio information into an analog audio signal for output, and also to convert 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 located within the processor 110, or some functional modules within the audio module 170 may be located within the processor 110. The speaker 170A, also called the “loudspeaker,” is configured to convert an electrical audio signal into a sound signal. The receiver 170B, also called the “earpiece,” is configured to convert an electrical audio signal into a sound signal. The microphone 170C, also called the “mike” or “mic,” is configured to convert a sound signal into an electrical signal. The headset jack 170D is configured to connect to a wired headset.

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

[0109] Buttons 190 include power buttons, volume buttons, etc. Motor 191 may generate vibration prompts. Indicator 192 may be an indicator light and may be configured to show the charging status and power changes, or to show messages, missed calls, notifications, etc.

[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 make contact with or disconnect 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 the network via the SIM card to implement functions such as conversation and data communication. 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 running iOS®, Android®, Windows®, Harmony®OS, or another operating system, such as a mobile phone, tablet computer, notebook computer, smartwatch, or smart band. The specific type of electronic device 100 is not limited to 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® system having a layered architecture is used as an example to illustrate 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, each with a distinct role and task. The layers communicate with each other through software interfaces. In some embodiments, the Android® system is divided into four layers from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

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

[0116] As shown in Figure 2, the application package may include applications such as camera, gallery, calendar, browser, map, AA chat, WLAN, Bluetooth®, email, and privacy indicator.

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

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

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

[0120] A window manager is configured to manage windowed programs. A window manager might retrieve the display size, determine if there's a status bar, perform screen locking, take screenshots, and so on.

[0121] Content providers are configured to store and retrieve data and enable applications to access it. This data may include videos, images, audio, outgoing and incoming calls, browsing history and bookmarks, address books, and more.

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

[0123] The telephone manager is configured to provide communication functions for the electronic device 100, such as managing call status (including answering, rejecting, etc.).

[0124] The resource manager provides applications with various resources such as localized text, icons, images, layout files, and video files.

[0125] A notification manager can be configured to allow an application to display notification information in the status bar or a dropdown notification bar and to deliver notification messages. The notification information may disappear automatically after a short pause without user interaction. For example, a notification manager can be used to notify that a download is complete, or to deliver message notifications. Alternatively, a notification manager may appear in the form of a graph or scrollbar text in the system's top status bar, for example, notifications from applications running in the background, or notifications that appear on the screen in the form of a dialog window. For example, it may display text information in the status bar, make announcements, vibrate electronic devices, or flash indicator lights.

[0126] The Activity Manager is responsible for managing activities, including starting, switching, and scheduling each component within the system, as well as managing and scheduling applications. Higher-level applications can call the Activity Manager to start the corresponding activities.

[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 authorization management service, and a device authorization provisioning service.

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

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

[0130] The device permission management service may be used to listen for device permission access data from the application behavior recording module. In possible implementations, the device permission management service may listen for access data for a first type of device permission (such as camera permission, microphone permission, and location permission) from the application behavior recording module. When any one of the first type of device permission 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 for the first type of device permission.

[0131] When the device authorization management service obtains through listening that a first type of device authorization is being accessed, it may be used to send a message to the sensitive behavior reminder module to notify the device authorization management service of the access data for the first type of device authorization.

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

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

[0134] For example, upon receiving a message indicating that access to camera permissions is beginning, the sensitive behavior reminder module may instruct the status bar controller to display a camera icon in the status bar. Upon receiving a message indicating that access to camera permissions has ended, the sensitive behavior reminder module may instruct the status bar controller to remove the camera icon from the status bar.

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

[0136] In this application, upon detecting an operation to open the control center interface, the control center module may send a message to the privacy indicator instructing the privacy indicator to display a device permission icon on the control center interface.

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

[0138] The kernel library consists of two parts: functions that need to be called in the Java language and the Android kernel library itself.

[0139] The application layer and application framework layer run on a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is configured to implement features such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0140] The system library 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 fusion of 2D and 3D layers for multiple applications.

[0142] The media library supports 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 3D graphics processing library is configured to implement 3D graphics drawing, image rendering, compositing, image layer processing, and more.

[0144] A 2D graphics engine is a rendering engine used for 2D drawing.

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

[0146] It should be understood that the software module shown in Figure 2 is merely an example for illustrative purposes of this application and does not constitute a limitation to this application. In some embodiments, the electronic device 100 may include more or fewer modules, or some modules may be combined, or some modules may be divided.

[0147] From the embodiments described above, it can be seen that the application-sensitive behavior reminder method provided in this application is applicable to a communication system including multiple electronic devices. Sensitive behavior detected by electronic device 100 can be performed by an application on electronic device 100 or by an application on an electronic device other than electronic device 100.

[0148] The following describes a diagram of the architecture of the communication system 30 according to an embodiment of this application.

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

[0150] As shown in Figure 3, the communication system 30 may include multiple electronic devices such as electronic device 100, electronic device 200, electronic device 201, electronic device 202, and electronic device 203. For the structures of electronic devices 200 to 203, please refer to the description of the structure of electronic device 100 in the above embodiment. Further details will not be described herein. Not limited to the electronic devices shown in Figure 3, the communication system 30 may further include other types of electronic devices, such as personal computers (PCs), desktop computers, laptop computers, handheld computers, augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, head units, game consoles, treadmills, cloud hosts / cloud servers, or other intelligent wearable devices, or further including Internet of Things (IoT) devices, or smart home devices such as smart water heaters, smart lamps, smart air conditioners, and smart scales. The types of electronic devices are not limited in this application.

[0151] In some embodiments, the communication system 30 may also be referred to as a “super terminal.” A “super terminal” may mean that the capabilities of multiple 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 to the outside, thereby enabling different electronic devices to implement rapid connectivity, mutual cooperation of capabilities, and resource sharing.

[0152] A communication connection can be established between all electronic devices included in the communication system 30. For example, one electronic device and another electronic device in the communication system 30 may be electronic devices located in the same communication network (e.g., the same Wi-Fi network). Alternatively, one electronic device may 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 may be an electronic device that establishes a trust relationship with another electronic device in a different way, for example, an electronic device paired via Bluetooth®, or an electronic device connected to a hotspot shared by another electronic device. Alternatively, one electronic device may be an electronic device that has established a Wi-Fi P2P connection to another electronic device. The methods by which electronic devices included in the communication system 30 establish a communication connection are not limited to this embodiment of the present application.

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

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

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

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

[0157] Figure 4 shows another structure of an example of a communication system 30 according to one embodiment of this application.

[0158] As shown in Figure 4, the communication system 30 may include electronic devices 100, 200, 201, 202, and the like. For the method of establishing communication connections between the electronic devices included in the communication system 30, please refer to the explanation above shown in Figure 3. Further details will not be explained in this specification.

[0159] In some embodiments, the electronic device 100 may include applications such as application 1, application 2, and application 3. The applications 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 to this embodiment of the present application. The electronic device 100 may further include a device authorization provisioning service 410, an application behavior recording module 420, a behavior recording database 430, a device authorization 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 authorization provisioning service 410 may include services corresponding to device authorization of the electronic device 100, such as a camera service 411, a microphone service 412, a location service 413, a contact service 414, or a media and file service 415. The device authorization provisioning service 410 may include many more services, which are not limited to the present application. Each application (such as Application 1, Application 2, and Application 3) within electronic device 100 and other electronic devices (such as electronic device 200, electronic device 201, and electronic device 202) can access the device authorization of electronic device 100 and invoke services within the device authorization provisioning service 410.

[0160] Upon receiving a request to invoke a service, the device authorization provisioning service 410 provides the service invoked by the device authorization provisioning service 410 to the service invoker and sends a message to the application behavior recording module 420 notifying it of the service invocation data. In a possible implementation, application 1 requests to invoke the camera service, camera service 411 provides the camera service to application 1 and sends a message to the application behavior recording module 420 notifying it of the camera service invocation data. For example, the camera service invocation data may include the identifier of the camera service invoker (i.e., the identifier of application 1), the time when the camera service invocation starts, the time when the camera service invocation ends, and so on.

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

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

[0163] Sent by Device Authorization Provisioning Service 410 camera Upon receiving service call data for the Service, Microphone Service, and Location Service, the Application Behavior Recording Module 420 may transmit the service call data to the Device Authorization Management Service 440.

[0164] Upon receiving service call data, the device authorization management service 440 may transmit the service call data to the sensitive behavior reminder module 450 so that the sensitive behavior reminder module 450 can refresh the call data for the camera service, microphone service, and location service.

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

[0166] This specification uses an example in which Application 1 calls the camera service in electronic device 100 for illustrative purposes.

[0167] For example, application 1 requests to invoke the camera service. Camera service 411 may provide application 1 with a camera service so that application 1 can capture image data by using the camera of electronic device 100. Camera service 411 may further transmit camera service invocation data to application behavior recording module 420. Camera service invocation data may include the identifier of application 1 and the time when application 1 initiates the camera service invocation. Application behavior recording module 420 may transmit camera service invocation data to device permission management service 440. Device permission management service 440 may transmit camera service invocation data to sensitive behavior reminder module 450. Sensitive behavior reminder module 450 may store the camera service invocation data and instruct status bar controller 460 to display a camera icon in the status bar. In this way, the user can be notified that camera permission has been accessed and the camera of electronic device 100 has been invoked.

[0168] Furthermore, Application 1 terminates the call to the camera service. The camera service 411 may send camera service call termination data to the application behavior recording module 420. The camera service call termination data 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 camera service call termination data to the device permission management service 440. The device permission management service 440 may send the camera service call termination data to the sensitive behavior reminder module 450. The sensitive behavior reminder module 450 stores the camera service call termination data and may instruct the status bar controller 460 to remove the camera icon from the status bar.

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

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

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

[0172] When the communication system 30 shown in Figure 4 detects that device permission is being accessed, the electronic device 100 may display a device permission icon in the status bar and / or control center interface, allowing the user to know and control the sensitive and cross-device sensitive behavior of applications on the device.

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

[0174] Figures 5A and 5B illustrate examples of the interface of electronic device 100 when sensitive behavior is not currently occurring.

[0175] As shown in Figure 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 for 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 so on. 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 mobile communication signal strength indicator, a Wi-Fi signal strength indicator, 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 notify the user of the sensitive behavior occurring in the electronic device 100 by displaying a device permission icon for the device permission accessed in the sensitive behavior on the status bar 511.

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

[0179] It can be understood that when an authorized visitor accesses the first type of device authorization, they typically access it continuously for a certain period of time; that is, there is an access start point and an access end point. The electronic device 100 may start displaying the device authorization icon on the status bar 511 when access to the first type of device authorization begins, and may remove the display of the device authorization icon on the status bar 511 when access to the first type of device authorization ends. It can be seen that the electronic device 100 can display the device authorization icon on the status bar 511 in real time during the process in which the first type of device authorization is being accessed, and notify the user that the first type of device authorization is being accessed.

[0180] However, when a second type of device permission is accessed, the access behavior of the permitted visitor is typically a separate, one-time action. If the electronic device 100 displays a device permission icon in the status bar 511 when it detects that a second type of device permission is being accessed, the electronic device 100 will display a second type of device permission icon in the status bar 511. permission After displaying the device permission icon, the display of the device permission icon can be quickly dismissed. If the user does not view the electronic device 100 in a timely manner, the user may miss sensitive behavior reminders regarding access to the second type of device. In addition, if an authorized visitor frequently accesses the second type of device permission, the icon corresponding to the device permission within the second type of device permission, displayed on the status bar 511 by the electronic device 100, may flash frequently. It is found that the electronic device 100 displaying the device permission icon for the second type of device permission on the status bar 511 has a poor sensitive behavior reminder effect, consumes a lot of power, and affects the user's screen viewing experience. Therefore, the electronic device 100 can display the device permission icon for the first type of device permission on the status bar 511 only when the first type of device permission is accessed.

[0181] In response to an operation to open the control center interface, the electronic device 100 may display the control center interface 520 shown in Figure 5B. The operation to open the control center interface may, for example, be a slide operation from the upper right to the lower part of the screen of the electronic device 100 shown in Figure 5A. The aforementioned operation to open the control center interface is not limited to the embodiments of this application.

[0182] As shown in Figure 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 used to control music playback (such as play control, pause control, previous track control, and next track control). 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 for one or more electronic devices. One or more electronic devices may include electronic devices that have established a cooperative connection with electronic device 100, or electronic devices that have been detected by electronic device 100 but have not established a cooperative connection. This is not limited to the embodiments of this application. The device icons in the super terminal card 524 may be used to trigger electronic device 100 to establish a cooperative connection with the electronic device corresponding to the device icon, or to disconnect the cooperative connection. Establishing a cooperative connection between two electronic devices can represent one of the two electronic devices virtualizing the other, using the capabilities of the other electronic device to operate cooperatively, and thereby providing a service to the user.

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

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

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

[0186] Figures 6A to 6D are some examples of sensitive behavior reminder scenarios.

[0187] As shown in Figure 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 the user interface 610 shown in Figure 6B. The user interface 610 may be the user interface of the recorder application.

[0188] As shown in Figure 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 the microphone to capture audio data and display the user interface 620 shown in Figure 6C.

[0189] As shown in Figure 6C, the user interface 620 may include a recording pause control 622 and a recording end control 623. The recording pause control 622 can be used to pause recording. The recording end control 623 can be used to end 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 microphone permission. If the recorder application determines that it has microphone permission, the electronic device 100 may provide microphone services to the recorder application. In this way, the recorder application may invoke the microphone services and capture audio data by using the microphone of the electronic device 100. The electronic device 100 may detect that the recorder application has access to microphone permission and display the microphone icon 621 shown in Figure 6C in the status bar. Specifically, the electronic device 100 may display the microphone icon 621 in the status bar from the time the recorder application initiates an invoke to the microphone services (i.e., from the time the microphone starts operating and captures audio data). The microphone icon 621 may remind the user of the sensitive behavior of the microphone being activated.

[0191] In response to an operation to open the control center interface shown in Figure 6C, the electronic device 100 may display the control center interface 630 shown in Figure 6D. The control center interface 630 may include a sensitive behavior prompt 632 and a microphone icon 631 displayed in the status bar. For details on the microphone icon 631, please refer to the description of the microphone icon 621 shown in Figure 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 prior to the operation to open the control center interface and display a sensitive behavior prompt on the control center interface based on the sensitive behavior found. 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 device permission access data for the 10 seconds prior to time t1.

[0193] The electronic device 100 may detect that the recorder application has accessed microphone permissions within a preset period prior to the operation of opening the control center interface. In this case, the electronic device 100 may display a sensitive behavior prompt 632, as shown in Figure 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, the user can know, based on the sensitive behavior prompt 632, that the microphone permissions of the electronic device 100 have been accessed and that 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 Figure 6C is detected, the recorder application may terminate permission to access the microphone. The electronic device 100 may turn off the microphone to stop capturing audio data. When the recorder application detects that permission to access the microphone has been terminated, the electronic device 100 may remove the display of the microphone icon 621 shown in Figure 6C from the status bar.

[0195] Note that when the control center interface 630 is displayed, 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 may be frozen. That is, the sensitive behavior prompt 632 and the microphone icon 631 may remain unchanged. For example, when the control center interface 520 is displayed, the electronic device 100 may continue to display the microphone icon 631 and the sensitive behavior prompt 632 even after detecting that the recorder application has terminated permission to access the microphone. Furthermore, upon detecting an operation to close the control center interface 630, the electronic device 100 may remove the display of the microphone icon 621 shown in Figure 6C in the status bar of the user interface displayed after the control center interface 630 is closed. In another example, when the control center interface 630 is displayed, the electronic device 100 may continue to display the microphone icon 631 and the sensitive behavior prompt 632 in succession even if it detects that camera permission is being accessed, without adding a camera icon to the status bar or adding a sensitive behavior prompt to the control center interface 630 indicating that camera permission is being accessed. Furthermore, if it detects an operation to close the control center interface 630, the electronic device 100 may display a 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 camera permission is being accessed.

[0196] Figures 7A to 7C are some other diagrams of an example of a sensitive behavior reminder scenario.

[0197] As shown in Figure 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 may provide a video call function. In response to an operation to start the video call function, the electronic device 100 may display the user interface 710 shown in Figure 7B.

[0198] As shown in Figure 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 to be started, the AA chat application may request permission to access the camera and microphone. If the AA chat application determines that it has camera permission and microphone permission, the electronic device 100 may provide camera and microphone services to the AA chat application. In this way, the AA chat application can invoke camera permission and microphone permission to capture images 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 has access to camera permission and microphone permission and display the microphone icon 711 and camera icon 712 shown in Figure 7B. The microphone icon 711 may remind the user of sensitive behavior in which the microphone is activated. The camera icon 712 may remind the user of sensitive behavior in which the camera is activated.

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

[0200] As shown in Figure 7C, the control center interface 720 may include a sensitive behavior prompt 723 and microphone icons 721 and camera icons 722 displayed in the status bar. For details on microphone icons 721 and camera icons 722, please refer to the descriptions of microphone icons 711 and camera icons 712 shown in Figure 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 microphone icon may be displayed in a collapsed state. For example, the camera icon may be displayed on top of the microphone icon, partially blocking 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 microphone icon included in the sensitive behavior prompt 723.

[0201] From the embodiments described above, it can be seen that in response to an operation to open the control center interface, the electronic device 100 may query sensitive behavior within a preset period prior to the operation to open the control center interface and display a sensitive behavior prompt on the control center interface based on the sensitive behavior found. From Figure 7B, it can be seen that the electronic device 100 receives an operation to open the control center interface in the process in which the AA chat application accesses camera permission and microphone permission. In this case, the electronic device 100 may find that the AA chat application accessed camera permission and microphone permission within a preset period prior to the operation to open the control center interface. The electronic device 100 may display the sensitive behavior prompt 723 shown in Figure 7C on the control center interface 720. In this way, the user can know, based on the sensitive behavior prompt 723, that the microphone permission and 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 terminate access to the microphone and camera permissions. The electronic device 100 may turn off the camera and microphone to stop capturing image and audio data. When the AA chat application detects that it has terminated permission to access the microphone and camera, the electronic device 100 may remove the microphone icon 711 and camera icon 712 shown in Figure 7B from the status bar.

[0203] In some embodiments, when querying sensitive behavior within a preset period prior to an operation to open the control center interface, the electronic device 100 finds that multiple device permissions have been accessed. The electronic device 100 may display a sensitive behavior prompt in the control center interface that includes an icon corresponding to one of the multiple device permissions. Thus, the user can conveniently know which device permissions of the electronic device 100 have been accessed in the most recent period.

[0204] In possible implementations, when displaying a sensitive behavior prompt in the control center interface that includes icons corresponding to multiple device permissions, the electronic device 100 may display the icons corresponding to multiple device permissions in a collapsed manner. For example, the electronic device 100 may display the icons corresponding to device permissions in a collapsed manner according to a pre-configured permission priority. The electronic device 100 may display the device permission icon for the device permission with the highest permission priority at the highest level, and the device permission icon for the device permission with the lowest permission priority at the lowest level. Icons displayed in higher layers that correspond to device permissions may partially block icons displayed in lower layers that correspond to device permissions. For example, permission priorities sorted in descending order may be Camera permission > Microphone permission > Location permission > Media and file permission > Contact permission. If the electronic device 100 detects sensitive behavior that accessed Camera permission, Microphone permission, Media and file permission, and Contact permission within a pre-configured period prior to the operation of opening the control center interface, it may display a sensitive behavior prompt in the control center interface. Sensitive behavior prompts may include a camera icon, microphone icon, media and file icon, and contact icon, which are displayed in a collapsed state. According to the aforementioned pre-configured permission priority, 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 aforementioned authorization priority is merely an example for illustrative purposes in the embodiments of this application and does not constitute a limitation to this application. When it is determined that multiple device authorizations are being accessed, the electronic device 100 may further present icons corresponding to the device authorizations among the multiple device authorizations being accessed in a different display manner to inform the user of sensitive behavior occurring on the electronic device 100.

[0206] In some embodiments, the electronic device 100 may further provide the name of the authorized visitor when displaying a sensitive behavior prompt on the control center interface. That is, the sensitive behavior prompt may further include the name of the authorized visitor. If the authorized visitor is an application on the electronic device 100, the electronic device 100 may display the name of the application. If the authorized 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 authorization.

[0207] In possible implementations, the electronic device 100 detects that multiple device permissions have been accessed within a predetermined period prior to the operation of opening the control center interface. If the permission visitors for multiple device permissions are the same, for example, all of them being application 1 within the electronic device 100, the electronic device 100 may display a sensitive behavior prompt in the control center interface. The sensitive behavior prompt may include an icon corresponding to the device permission among the multiple device permissions and the name of application 1. Alternatively, if the permission visitors for multiple device permissions are different, for example, if the permission visitors for multiple device permissions include application 1, application 2, and electronic device 200, the electronic device 100 may display a sensitive behavior prompt in the control center interface. The sensitive behavior prompt may include an icon corresponding to the device permission among the multiple device permissions, displayed in a collapsed state, and the name of the permission visitor accessing the device permission with the highest permission priority among the multiple device permissions. For example, electronic device 100 detects sensitive behavior that accessed camera permission, microphone permission, media and file permission, and contact permission within a predetermined period prior to the operation of opening the control center interface. The visitor who granted camera permission is electronic device 200. 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 granted camera permission (i.e., the name of electronic device 200). The camera icon, microphone icon, media and file icon, and contact icon may be displayed collapsed, with the camera icon displayed at the highest level.

[0208] From the scenarios shown in Figures 7A to 7C, it can be seen that when it is determined that multiple device permissions are being accessed, the electronic device 100 may display a sensitive behavior prompt on the control center interface to inform the user that multiple device permissions are being accessed. The sensitive behavior prompt may further include the names of the permission visitors. In this way, the user can quickly become aware of sensitive behavior in the electronic device 100.

[0209] Figures 8A to 8C are some other diagrams of an example of a sensitive behavior reminder scenario.

[0210] In this specification, an example in which the electronic device 100 receives an operation to open the control center interface in the process by which the AA chat application accesses the camera permission and microphone permission of the electronic device 100 is still used for illustrative purposes.

[0211] As shown in Figure 8A, in response to an operation to open the control center interface, the electronic device 100 may display the control center interface 810. The control center interface 810 may include a sensitive behavior prompt 813 and a microphone icon 811 and a camera icon 812 displayed in the status bar. The microphone icon 811 and the camera icon 812 may indicate that microphone permission and camera permission are accessed, respectively, when the electronic device 100 receives an operation to open the control center interface. The sensitive behavior prompt 813 may include a collapsed camera icon, a microphone icon, media and file icons, as well as a contact icon and the name of the visitor for camera permission (for example, the name of the AA chat application, "AA chat"). For details on the sensitive behavior prompt 813, see the description of the sensitive behavior prompt 723 shown in Figure 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 authorization is accessed within a predetermined period of time while the control center interface is open. If it is determined that a first type of device authorization is accessed, the electronic device 100 may query whether a second type of device authorization is accessed within the predetermined period. In other words, based on the fact that the sensitive behavior prompt displayed on the control center interface includes a device authorization icon for a first type of device authorization, the electronic device 100 may present the device authorization icon for the second type of device authorization being accessed to the sensitive behavior prompt. If it is determined that a first type of device authorization has not been accessed within the predetermined period, the electronic device 100 does not need to display a sensitive behavior prompt on the control center interface.

[0213] In response to an operation on the sensitive behavior prompt 813, such as a tap, the electronic device 100 may display the permission prompt box 820 shown in Figure 8B. The permission prompt box 820 may display the specific circumstances under which 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 in which camera permission, microphone permission, media and file permission, and contact permission are being 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. Permission prompt information 821 may indicate that the AA chat application is currently accessing camera permission. Permission prompt information 822 may indicate that the AA chat application is currently accessing microphone permission. Permission prompt information 823 may indicate that the email application has recently accessed media and file permission. 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 records of more sensitive behaviors in the electronic device 100.

[0216] In some embodiments, in response to an operation on the sensitive behavior prompt 813, such as a tap, the electronic device 100 may further inquire whether the authorized visitor has terminated access to one or more device permissions in the first type of device permission. If it is determined 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 Figure 8B to indicate that the first type of device permission being accessed is in an access state. Alternatively, if it is determined that the authorized visitor has terminated 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 Figure 8B to indicate that the first type of device permission being accessed was recently accessed but is now no longer accessible.

[0217] When an operation to open the control center interface is received, the authorized visitor may understand that they may be accessing a 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 access to the first type of device permission. When an operation to the sensitive behavior prompt 813 is received, the authorized visitor may still be able to access the first type of device permission, or may terminate access to the first type of device permission. Based on the access data of the first type of device permission found when the operation to the sensitive behavior prompt 813 is received, the electronic device 100 may decide whether to display "Accessing" or "Recently Accessed" in the permission prompt box 820 shown in Figure 8B.

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

[0219] In some embodiments, the permission prompt information in 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 Figure 8B, in response to an operation on the authorization prompt information 824, the electronic device 100 may display the user interface 830 shown in Figure 8C.

[0221] As shown in Figure 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 a “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 under which the browser application can access contact permissions. For example, when the “While using the application” control 833A is selected, the electronic device 100 may allow the browser application to access contact permissions and retrieve contact information only when it is running in the foreground. The “Always” control 833B is used to adjust the conditions under which the browser application can access contact permissions, allowing the browser application to access contact permissions under any conditions. The “Never” control 833C may be used to prohibit the browser application from accessing contact permissions.

[0222] From the scenarios described above, shown in Figures 8A to 8C, it can be seen that the user can quickly find out which device permissions of the electronic device 100 are being accessed by opening the control center interface. Accessed device permissions may include first type device permissions such as camera permission, microphone permission, and location permission, as well as contact permission and media permission. AoThis may further include a second type of device permission, such as file permissions. In addition, users can more quickly see the specific circumstances under which each device permission is accessed (e.g., permission visitors and whether the permission has recently been accessed or is currently being accessed) based on sensitive behavior prompts within the control center interface. Furthermore, users can quickly manage permission visitors based on sensitive behavior prompts within the control center interface and adjust the conditions under which device permission visitors can access device permissions. This can help users manage device permissions conveniently and quickly, reduce the misuse of device permissions, and improve the security of user privacy information.

[0223] Figures 9A to 9C are some other diagrams illustrating an example of a sensitive behavior reminder scenario.

[0224] This specification uses, for illustrative purposes, an example in which the electronic device 100 receives an operation to open the control center interface during a process in which a camera application accesses the camera permissions of the electronic device 100, and a browser application and a map application access the location permissions of the electronic device 100.

[0225] As shown in Figure 9A, in response to an operation to open 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 and location icons 911 and camera icons 912 displayed in the status bar. The location icon 911 and camera icon 912 may indicate that location and camera permissions are accessed when the electronic device 100 receives an operation to open the control center interface, respectively. The sensitive behavior prompt 913 may include a collapsed camera icon, location icon, media and file icons, as well as a contact icon and the name of the visitor for camera permissions (for example, the name of the camera application, "Camera"). For details on the sensitive behavior prompt 913, see the description of the sensitive behavior prompt 723 shown in Figure 7C.

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

[0227] As shown in Figure 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. Permission prompt information 921 may indicate that a camera application has recently accessed camera permissions. Permission prompt information 922 may indicate that multiple permission visitors, such as a browser application, are currently accessing location permissions. Permission prompt information 923 may indicate that an email application has recently accessed media and file permissions. Permission prompt information 924 may indicate that a browser application has recently accessed contact permissions.

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

[0229] When a single device permission is accessed by multiple permitted visitors, the electronic device 100 may display the name of the permitted visitor whose access time is closest to the current time in the permission prompt box 920 shown in Figure 9B, and append the text identifier "..." to that name to indicate that multiple permitted visitors are accessing the device permission. For example, if it is determined that both a browser application and a map application are accessing the location permission, the electronic device 100 may display the permission prompt information 922 shown in Figure 9B. The permission prompt information 922 may include the text identifier "browser..." to indicate that multiple permitted visitors, including a browser application, are accessing the location permission.

[0230] In response to an operation on the authorization prompt information 922, such as a tap operation, the electronic device 100 may display the user interface 930 shown in Figure 9C.

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

[0232] It can be understood that both the browser application and the map application that access location permissions are applications on electronic device 100. If the authorized visitors accessing location permissions also include other electronic devices besides electronic device 100, for example, electronic device 200, electronic device 100 may further display options corresponding to electronic device 200 in the user interface 930 shown in Figure 9C, thereby opening a user interface for the user to manage electronic device 200 for accessing location permissions of electronic device 100.

[0233] From the scenarios shown in Figures 9A to 9C, it can be seen that when a single device authorization is accessed by multiple authorization visitors, the electronic device 100 may provide a sensitive behavior reminder to inform the user of the names of the multiple authorization visitors and that the device authorization is being accessed by multiple authorization visitors. Thus, the user can conveniently and better know the access status of the device authorization of the electronic device 100, thereby enabling the user to know and control sensitive behavior in the electronic device 100.

[0234] Figures 10A to 10L illustrate an example of a cross-device sensitive behavior reminder scenario.

[0235] As shown in Figure 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, such as a tap, the electronic device 100 may start the camera application and display the user interface 1010 shown in Figure 10B. The user interface 1010 may be the camera application's shooting interface.

[0236] As shown in Figure 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 images captured by using the camera. The mode selection area 1012 may include multiple shooting mode options, such as a video option, a photo option, a professional option, and other options 1012A. Shutter control 1013 This can be used to perform a photograph. For example, when the photograph option is selected, the electronic device 100 controls the shutter. 1013 In response to an operation on this, the image displayed in the preview area 1011 can be saved to the gallery.

[0237] Note that when the camera application is started, the camera application may have access to the camera permissions of electronic device 100 in order to capture images by using the camera of 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 Figure 10B, the electronic device 100 may display the user interface 1020 shown in Figure 10C.

[0239] As shown in Figure 10C, the user interface 1020 may include multiple shooting mode options, for example, a multi-camera option 1021. The multi-camera option 1021 can 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 the camera selection box 1030 shown in Figure 10D.

[0240] As shown in Figure 10D, the camera selection box 1030 may include a camera selection area 1031. Multiple camera options, for example, the electronic device 100 (front camera) option, the electronic device 100 (rear camera) option, the electronic device 200 (front camera) option, and the 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 identifiers of the camera options are not particularly limited in the embodiments of this application.

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

[0242] In possible implementations, 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 the camera options corresponding to the found electronic device in the camera selection box 1030 shown in Figure 10D.

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

[0244] Upon receiving a request for access to camera permissions from electronic device 100, electronic device 200 may display a request prompt box 1040, as shown in Figure 10E. The request prompt box 1040 may be used to inform the user that electronic device 100 is requesting access to the camera permissions of electronic device 200 and to activate the rear camera of electronic device 200, and to ask the user whether they consent to this. The request prompt box 1040 may include a No control 1041 and an OK control 1042. The No control 1041 may be used to deny electronic device 100 access to the camera permissions of electronic device 200. The OK control 1042 may be used to allow electronic device 100 access to the camera permissions of electronic device 200.

[0245] In the process in which electronic device 100 requests access to camera permissions on electronic device 200, electronic device 100 may further display the text identifier "Requesting cooperation..." in the location corresponding to camera option 1034 in the camera selection box 1030 shown in Figure 10E. The text identifier may remind the user to wait for electronic device 100 to activate the camera on electronic device 200. The specific content of the text identifier is not limited to the embodiments of this application.

[0246] In response to an operation on the OK control 1042 shown in Figure 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 does not need to display the request prompt box 1040 shown in Figure 10E. Specifically, upon receiving a request for camera permission access from the electronic device 100, the electronic device 200 may directly activate the rear camera to capture an image and send the captured image back to the electronic device 100.

[0248] As shown in Figure 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 exit control 1063. The content of the text prompt 1061 may be "Sharing with electronic device 100", indicating that the electronic device 200 is sharing images captured by using its camera with the electronic device 100. The preview area 1062 may display images captured by using the camera of the electronic device 200. The exit control 1063 may be used to stop sharing images 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. The status bar may display a camera icon 1064. The camera icon 1064 may indicate that the camera permissions of the electronic device 200 are being accessed.

[0249] Upon receiving an image shared by electronic device 200, electronic device 100 may display the user interface 1050 shown in Figure 10F. The user interface 1050 may include a preview area 1051, a camera selection control 1052, and a multi-camera function termination control 1053. The preview area 1051 may display the image shared between electronic device 200 and electronic device 100.

[0250] The camera selection control 1052 can be used to select a camera to capture images. In response to an operation on the camera selection control 1052, the electronic device 100 searches for an electronic device equipped with a camera and, based on the search result, may display the camera selection box 1030 shown in Figure 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 may be used to terminate the multi-camera function. In response to an operation on the multi-camera function termination control 1053, electronic device 100 may terminate its access to the camera permissions of another electronic device (e.g., electronic device 200) and display the images captured by using the camera of electronic device 100 in the preview area 1051.

[0252] As shown in Figure 10G, in response to an operation to open the control center interface, the electronic device 100 may display the control center interface 1070 shown in Figure 10H. The operation to open the control center interface may, for example, be a swipe down from the upper right corner of the screen of the electronic device 200. The aforementioned operation to open the control center interface is not limited to the embodiments of this application.

[0253] As shown in Figure 10H, the control center interface 1070 may 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, please refer to the description of the display of the sensitive behavior prompt on the control center interface by the electronic device 100 in the embodiments described above. Further 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 for one or more electronic devices, for example, an icon 1073A for electronic device 100, an icon for electronic device 201, and an icon for electronic device 202. In the super terminal card 1073, the display style of the device icons for electronic devices that have established a cooperative connection with electronic device 200 may differ from the display style of the device icons for electronic devices that have not established a cooperative connection with electronic device 200. For example, the device icons for electronic devices that have established a cooperative connection with electronic device 200 may have a dark display style, while the device icons for electronic devices that have not established a cooperative connection with 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 to the embodiments of this application.

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

[0256] In some embodiments, when a cooperative connection is established between the first electronic device 100 and the second electronic device 200, in response to an operation, e.g., a tap operation, performed on the icon 1073A of the first electronic device 100, the second electronic device 200 may stop cooperating with the first electronic device 100. For example, the second electronic device 200 shares images captured by using a camera thereof with the first electronic device 100. Upon receiving the operation on the icon 1073A of the first electronic device 100, the second electronic device 200 may stop sharing the images captured by using the camera with the first electronic device 100.

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

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

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

[0260] In response to an operation to open the control center interface shown in Figure 10I, the electronic device 100 may display the control center interface 1080 shown in Figure 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 being accessed. The sensitive behavior prompt 1082 may include the camera icon of the camera permission being accessed and the text identifier "The camera application will activate the camera on electronic device 200." The sensitive behavior prompt 1082 may inform the user that when accessing the camera permission on electronic device 200, the camera application on electronic device 100 will activate the camera on electronic device 200.

[0261] In some embodiments, in response to an operation to open the control center interface, the electronic device 100 may query which device permissions of the electronic device 100 will be accessed within a predetermined period prior to the operation to open the control center interface, and whether the electronic device 100 will access the device permissions of another electronic device within the predetermined period. For example, in addition to knowing that the electronic device 100 will access the camera permission of electronic device 200 within the predetermined period, the electronic device 100 may further find that multiple device permissions of the electronic device 100 will be accessed within the predetermined period. In this case, in addition to the camera icon shown in Figure 10J, the sensitive behavior prompt 1082 displayed by the electronic device 100 on the control center interface 1080 shown in Figure 10J may further include icons corresponding to the device permissions in the multiple device permissions accessed by the electronic device 100. This can help the user quickly know and control the sensitive behavior and cross-device sensitive behavior of applications on the device.

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

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

[0264] It should be noted that in some embodiments, when the control center interface 1080 is displayed, both the sensitive behavior prompt 1082 and the camera icon 1081 displayed in the status bar may be frozen. Therefore, even if the electronic device 100 terminates access to camera permission for the electronic device 200 based on an operation on the icon 1083A of the electronic device 100 shown in Figure 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 Figure 10K, in response to an operation to fold the control center interface, the electronic device 100 may display the user interface 1090 shown in Figure 10L. The operation to fold the control center interface may be, for example, an operation to slide the screen of the electronic device 100 from bottom to top. The aforementioned operation to fold the control center interface is not limited to the embodiments of this application.

[0266] As shown in Figure 10K, the user interface 1090 may be a shooting interface for a camera application. Since the electronic device 100 has terminated its access to the camera of the electronic device 200, the electronic device 100 may display images captured by using the camera of the electronic device 100 (e.g., the rear camera) to the user interface 1090. For details of the user interface 1090, please refer to the description of the embodiment shown in Figure 10B. Further details will not be described further herein.

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

[0268] Figures 11A to 11C show some examples of sensitive behavior management scenarios.

[0269] As shown in Figure 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 details of the control center interface 1110, please refer to the description of the control center interface 1070 shown in Figure 10H. Further details will not be described further in this specification.

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

[0271] As shown in Figure 11B, the authorization prompt box 1120 may include authorization prompt information 1121 and a stop control 1122. The authorization prompt information 1121 may indicate that electronic device 100 is accessing camera authorization on electronic device 200. The stop control 1122 may be used to terminate electronic device 100's access to camera authorization on electronic device 200. In response to an operation on the stop control 1122, electronic device 200 may stop sharing images captured by using the camera with electronic device 100.

[0272] In possible implementations, upon receiving an operation on the sensitive behavior prompt 1112, the electronic device 200 may query whether the first type of device authorization of the electronic device 200 is still being accessed. For example, if it is determined that the electronic device 100 is still accessing the camera authorization, the electronic device 200 may display the text identifier "Accessing" shown in Figure 11B in the authorization prompt box 1120 to indicate that the electronic device 100 is accessing the camera authorization of the electronic device 200. Alternatively, if it is determined that the electronic device 100 has terminated its access to the camera authorization, the electronic device 200 may change "Accessing" shown in Figure 11B to the text identifier "Recently Accessed" in the authorization prompt box 1120 to indicate that the electronic device 100 recently accessed the camera authorization of the electronic device 200, but has now terminated its access to the camera authorization of the electronic device 200.

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

[0274] As shown in Figure 11C, the user interface 1130 may include an identifier 1131 for the electronic device 100 and an authorization management box 1132. The identifier 1131 for the electronic device 100 may include identifier information such as the device icon and device name of the electronic device 100. The authorization 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 authorization of the electronic device 200, so that the electronic device 200 displays a prompt message each time the electronic device 100 accesses the camera authorization. This obtains the user's consent for the electronic device 200. For information on the prompt message displayed by the electronic device 200, see the request prompt box 1040 shown in Figure 10E. The “Always” control 1132B is used to invoke the conditions for electronic device 100 to access camera permission from electronic device 200, allowing electronic device 200 to directly consent to the camera permission request from electronic device 100 without displaying a prompt message. The “Deny” control 1132C can be used to deny electronic device 100 access to camera permission from electronic device 200. When the “Deny” control 1132C is selected, electronic device 200 may directly reject the request each time it receives a request from electronic device 100 to access camera permission.

[0275] From the scenarios described above, shown in Figures 11A to 11C, it can be seen that the user can quickly find out which device permissions of the electronic device 200 are being accessed by opening the control center interface. Accessed device permissions may include first type device permissions such as camera permission, microphone permission, and location permission, as well as contact permission and media permission. AoThis may further include a second type of device permission, such as file permissions. In addition, users can more quickly see the specific circumstances under which each device permission is accessed (e.g., permission visitors and whether the permission has recently been accessed or is currently being accessed) based on sensitive behavior prompts within the control center interface. Furthermore, users can quickly manage permission visitors based on sensitive behavior prompts within the control center interface and adjust the conditions under which device permission visitors can access device permissions. Permission visitors may be applications on electronic device 200 or electronic devices other than electronic device 200. This can help users conveniently and quickly manage device permissions, reduce misuse of device permissions, and improve the security of user privacy information.

[0276] Figures 12A to 12C are some other diagrams illustrating an example of a sensitive behavior management scenario.

[0277] In this specification, an example in which electronic device 100 accesses the camera permissions of electronic device 200 is still used for illustrative purposes.

[0278] As shown in Figure 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 indicate that the electronic device 100 is accessing camera permissions for 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, as shown in Figure 12B. The user interface 1220 may be a super terminal settings interface.

[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 a 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". Information related to 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 a 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 types of devices that can discover the electronic device 200. For example, types of devices that can discover the electronic device 200 may include nearby devices and my nearby devices. When the device type is nearby devices, all nearby electronic devices can discover the electronic device 200. When the device type is my nearby devices, a nearby electronic device whose login account is the same as that of the electronic device 200 can discover the electronic device 200. For example, after the electronic device 200 is discovered by an electronic device 100, the electronic device 100 can display a super terminal card the device icon of the electronic device 200 (refer to a super terminal card 1083 shown in FIG. 10J).

[0282] The authorization management box 1232 may be used to manage device authorization for electronic device 200, which can be accessed by electronic devices that can discover electronic device 200. For example, the authorization management box 1232 may include a switch corresponding to device authorization. When the switch is in the ON position, electronic devices that can discover electronic device 200 can access the device authorization for electronic device 200 corresponding to the switch. For example, if the switch corresponding to camera authorization in the authorization management box 1232 is in the ON position, all electronic devices that can discover electronic device 200 can access the camera authorization for electronic device 200. If the switch corresponding to camera authorization in the authorization management box 1232 is in the OFF position, none of the electronic devices that can discover electronic device 200 can access the camera authorization for electronic device 200.

[0283] The scenarios shown in Figures 12A to 12C demonstrate that the user can manage cross-device sensitive behavior in electronic device 200 and allow or deny another electronic device access to the device permissions of electronic device 200.

[0284] Figures 13A to 13E are some other diagrams illustrating an example of a sensitive behavior management scenario.

[0285] As shown in Figure 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 for one or more electronic devices, for example, icon 1311A for electronic device 100. In response to an operation on icon 1311A for electronic device 100, for example, a long press, the electronic device 100 may display a settings option box 1320, as shown in Figure 13A. The settings option box 1320 may include a cooperation establishment control 1321 and an authorization 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 authorization management control 1322 may be used to manage device authorization for the electronic device 200 that can be accessed by the electronic device 100.

[0286] As shown in Figure 13B, in response to an operation on the authorization management control 1322, such as a tap operation, the electronic device 200 may display the user interface 1330 shown in Figure 13C.

[0287] As shown in Figure 13C, the user interface 1330 may include an authorization management box 1331. The authorization management box 1331 may be used to manage device authorizations for electronic device 200 that can be accessed by electronic device 100. For example, the authorization management box 1331 may include a switch corresponding to a device authorization. When the switch is in the ON position, electronic device 100 can access the device authorization of electronic device 200 corresponding to the switch. For example, if the switch in the authorization management box 1331 corresponding to camera authorization is in the ON position, electronic device 100 can access the camera authorization of electronic device 200, and if the switch in the authorization management box 1331 corresponding to camera authorization is in the OFF position, electronic device 100 cannot access the camera authorization of electronic device 200.

[0288] Figure 13C shows that a user can separately manage permissions for electronic devices connected to electronic device 200 in order to coordinate device permissions for electronic device 200 that may be accessed by other electronic devices. In other words, a user can authorize different electronic devices to access different device permissions of electronic device 200 based on requirements and privacy security considerations. This can better meet the user's usage requirements and improve the security of user privacy information.

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

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

[0291] As shown in Figure 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 media and file permission options. Using one device permission option, a user interface may be opened to manage access by each application on electronic device 100 to device permissions corresponding to device permission options on electronic device 200.

[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 Figure 13E.

[0293] As shown in Figure 13E, the user interface 1350 may include an authorization switch display area 1351. The authorization switch display area 1351 may include switches corresponding to applications. These applications may be applications on the electronic device 100. The switches in the authorization switch display area 1351 may be used to allow or deny the applications on the electronic device 100 that correspond to the switches to access the camera permissions of the electronic device 200. For example, the authorization switch display area 1351 may include a switch corresponding to an AA chat application. When the switch corresponding to the AA chat application is ON, the AA chat application on the electronic device 100 can access the camera permissions of the electronic device 200. When the switch corresponding to the AA chat application is OFF, the AA chat application on the electronic device 100 cannot access the camera permissions of the electronic device 200.

[0294] In possible implementations, after electronic device 100 establishes a communication connection to electronic device 200, electronic device 100 may transmit information about the application on electronic device 100 (such as the application name and application icon) to electronic device 200. Based on the information about the application on electronic device 100, electronic device 200 may display the user interface 1350 shown in Figure 13E. When electronic device 100 requests access to device authorization on electronic device 200, electronic device 100 may transmit to electronic device 200 the identifier of the application residing in electronic device 100 that is requesting access to device authorization. Based on the application identifier, electronic device 200 may determine whether the application on electronic device 100 can access the requested device authorization in order to determine whether to provide the service corresponding to the device authorization.

[0295] The scenarios shown in Figures 13D and 13E demonstrate that the user can separately manage permissions for each application on an electronic device connected to the electronic device 200 in order to coordinate the device permissions of the electronic device 200 that each application on the electronic device may access. In other words, the user can authorize different applications on the electronic device to access different device permissions of the electronic device 200, based on requirements and privacy security considerations. This allows for better meeting of the user's usage requirements and improved security of user privacy information.

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

[0297] In this specification, an example in which electronic device 100 accesses the camera permissions of electronic device 200 is still used for illustrative purposes.

[0298] As shown in Figure 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 in the status bar. The sensitive behavior prompt 1412 may be used to inform the user that a camera application on the electronic device 100 is accessing camera permissions on the electronic device 200. For details of the control center interface 1410, please refer to the control center interface 1080 shown in Figure 10J. Further details are not described herein.

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

[0300] As shown in Figure 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 camera permissions for the electronic device 200, such as a “While this application is in use” control, a “Always” control, and a “Do not allow” control.

[0301] For example, when the “In Use of This Application” control is selected, electronic device 100 may allow only the camera application to access the camera permissions of electronic device 200 while it is running in the foreground. In other words, when the “In Use of This Application” control is selected and the camera application is running in the foreground, and electronic device 100 detects a request to access the camera permissions of electronic device 200, electronic device 100 may send the request to electronic device 200 to invoke the camera service of electronic device 200. When the “In Use of This Application” control is selected and the camera application is not running in the foreground, and electronic device 100 detects a request to access the camera permissions of electronic device 200, electronic device 100 may refuse to send the request to electronic device 200. When the “Always” control is selected, electronic device 100 may allow the camera application to access the camera permissions of electronic device 200 under any circumstances. When the “Do not allow” control is selected, electronic device 100 may prevent the camera application from accessing the camera permissions of electronic device 200.

[0302] The scenarios shown in Figures 14A and 14B demonstrate that the user can perform further operations on electronic device 100 to coordinate device permissions for electronic device 200 that may be accessed by each application on electronic device 100, by performing permission management separately for each application on electronic device 100. In other words, the user can authorize different applications on the electronic device to access different device permissions of electronic device 200, based on requirements and privacy security considerations. This allows for better meeting of user usage requirements and improved security of user privacy information.

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

[0304] The following describes another sensitive behavior prompt scenario provided in the embodiments of this application.

[0305] Figures 15A to 15F are some other diagrams illustrating an example of a sensitive behavior prompt scenario.

[0306] In this specification, an example is used to illustrate how a recorder application on an electronic device 100 can access the microphone permissions of the electronic device 100.

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

[0308] User interface 1510 may include a recording start control 1511. The user may start recording by tapping the recording start control 1511 at the first 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 1520 shown in Figure 15B. For user interface 1520, see user interface 610 shown in Figure 6C. 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 Figure 15B in the status bar of user interface 1520.

[0309] As shown in Figure 15B, the user may end the recording by tapping the recording end control 1523 at 3 seconds. In response to the operation on the recording end control 1523, the electronic device 100 may close the microphone and display the user interface 1530 shown in Figure 15C.

[0310] In possible implementations, the electronic device 100 may determine whether the duration for which an authorized visitor accesses 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 to the embodiments of this application. If it is determined that the duration for which an authorized visitor accesses 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 has finished calling for 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 Figure 15C, the user interface 1530 may include an audio 1 option 1531 and a recording start control 1511. Audio 1, corresponding to audio 1 option 1531, may be audio recorded by the electronic device 100 in response to operations on the recording start control 1511 shown in Figure 15A and on the recording end control 1523 shown in Figure 15B. It can be seen that the recording time segment of audio 1 is from second 1 to third 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. The electronic device 100 may be understood to receive an operation to tap the start recording control 1511 at 1 second and an operation to tap the end recording control 1523 at 3 seconds. The electronic device 100 may understand that the recorder application will start accessing microphone permission at 1 second and the microphone at 3 seconds N-permissionIt may be determined that the access to the microphone permission will end. That is, the recorder application accesses the microphone permission from second 1 to third second, and the access duration is only two seconds. If the preset duration is five 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 has finished accessing the microphone permission, the electronic device 100 may continue to display the microphone icon 1521 in the status bar shown in Figure 15C. In addition, the electronic device 100 may extend the display duration of the microphone icon 1521 to five seconds. Since the electronic device 100 has displayed the microphone icon 1521 in the status bar from second 1 to third second (i.e., the microphone icon 1521 has been displayed for two seconds), the electronic device 100 may continue to display the microphone icon in the status bar for three seconds. In other words, the electronic device 100 may continue to display the microphone icon 1521 in the status bar from third second to sixth second. If no access to microphone permission is detected between the 3rd and 6th seconds, the electronic device 100 may remove the display of the microphone icon 1521 in the status bar at the 6th second. If re-access to microphone permission is detected between the 3rd and 6th seconds, 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 microphone permission.

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

[0314] As shown in Figure 15D, the user may start recording by tapping the record start control 1511 at 4 seconds. In response to the operation on the record start control 1511, the electronic device 100 may activate the microphone to capture audio data and display the user interface 1540 shown in Figure 15E. For user interface 1540, see user interface 610 shown in Figure 6C. User interface 1540 may include a record pause control 1522 and a record 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 Figure 15E in the status bar of user interface 1540.

[0315] As shown in Figure 15E, the user may end the recording by tapping the recording end control 1523 at 6 seconds. 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 Figure 15F.

[0316] As shown in Figure 15F, the user interface 1550 may include an audio 1 option 1531, an audio 2 option 1551, and a recording start control 1511. For details on the audio 1 option 1531, please refer to the description in the embodiments above. Audio 2, corresponding to the audio 2 option 1551, may be audio recorded by the electronic device 100 in response to operations on the recording start control 1511 shown in Figure 15D and the recording end control 1523 shown in Figure 15E. 2 The recording time segment is from the 4th 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. The electronic device 100 may understand that at 4 seconds it receives an operation to tap the record start control 1511, and at 6 seconds it receives an operation to tap the record end control 1523. The electronic device 100 may determine that the access duration for the recorder application to access microphone permission is 2 seconds and does not exceed a preset duration (i.e., 5 seconds). In this case, after the recorder application has finished accessing microphone permission, the electronic device 100 may continue to display the microphone icon 1521 in the status bar shown in Figure 15F. The electronic device 100 may extend the display duration of the microphone icon 1521 to 5 seconds by using the display time when the microphone icon 1521 begins to appear in the status bar when microphone permission was last accessed as the start time. In other words, the electronic device 100 may display the microphone icon 1521 in the status bar for at least 5 seconds, starting from the 4th second, by using the time point "4 seconds" when the operation for the recording start control 1511 is received as the time starting point shown in Figure 15D. Since the recorder application terminates access to 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 microphone permission is detected from the 6th second to the 9th second, the electronic device 100 may remove the display of the microphone icon 1521 in the status bar at the 9th second.

[0318] From the scenarios in Figures 15A to 15F, it can be seen that when the access duration of the accessed device permission is excessively short, the electronic device 100 may extend the display duration of the device permission icon after the permission visitor has finished accessing it, so that the device permission icon continues to be displayed in the status bar for a certain period of time, thereby ensuring that the display duration of the device permission reaches a preset duration. The method described above can be used to avoid the device permission icon displayed in the status bar flashing frequently when the device permission is accessed frequently, to prevent the electronic device 100 from frequently refreshing the device permission icon displayed in the status bar, to improve the user experience when browsing the status bar, and to reduce the power consumption of the electronic device 100 for refreshing the device permission icon.

[0319] The sensitive behavior reminder method provided in the embodiments of this application will be described below based on the scenarios shown in Figures 15A to 15F.

[0320] In possible implementations, the electronic device 100 may display a device permission icon in the status bar by using a delay interpolation mechanism. The delay interpolation mechanism may include ensuring that the display duration of the device permission icon in the status bar satisfies the minimum display duration. If the access duration of the accessed device permission does not exceed the minimum display duration, the electronic device 100 may interpolate the display duration of the device permission icon in the status bar so that its display duration reaches at least the minimum display duration.

[0321] Specifically, the electronic device 100 can store a preset duration. The preset duration is the minimum display duration of the device permission icon. In this specification, an example in which the preset duration is 5 seconds is used for illustrative purposes. Alternatively, the preset duration may be a different value. The value of the preset duration is not limited to the embodiments of this application.

[0322] When electronic device 100 detects that device permissions are being accessed, it may obtain the time when the authorized visitor begins accessing the device permissions and the time when the authorized visitor ends accessing the device permissions. The start time may be denoted as currentTime1. The end time may be denoted as currentTime2. From currentTime1, electronic device 100 may display the device permissions icon for the accessed device permissions in the status bar. 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 can determine whether the duration is greater than a preset duration.

[0324] If it is determined that the duration is longer than a preset duration, the electronic device 100 may, in currentTime2, remove the display of the device permission icon in the status bar for a device permission that has finished accessing.

[0325] Alternatively, if it is determined that the duration does not exceed 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 continue to display the device permission icon in the status bar after the permission visitor has stopped accessing the device permission by using the preset duration - extended duration as a result of the preset duration. Furthermore, if the electronic device 100 does not detect re-access to the device permission during the extended period in which the device permission icon is displayed, the electronic device 100 may remove the display of the device permission icon in the status bar after the preset duration - duration period has been extended. Alternatively, if the electronic device 100 detects re-access to the device permission during the extended period in which the device permission icon is displayed, the electronic device 100 may redisplay the device permission icon by using a delay interpolation mechanism, using the display point in time when the device permission icon began to appear in the status bar when the device permission was last accessed as the time starting point. For example, if electronic device 100 detects that an authorized visitor has re-accessed the device permission during the period in which the display of the device permission icon is extended, electronic device 100 may obtain the time when the re-access to the device permission begins and the time when the re-access to the device permission ends. The time when the re-access to the device permission begins may be denoted as currentTime3. The time when the re-access to the device permission ends may be denoted as currentTime4. Based on currentTime3, currentTime4, and a preset duration, electronic device 100 may determine the duration for which the device permission icon is displayed in the status bar.

[0326] Optionally, if electronic device 100 detects a re-access to a device permission during a period in which the display of the device permission icon is extended, electronic device 100 may determine whether the duration between the time when the display of the device permission icon for the device permission begins and the time when the re-access to the device permission ends exceeds a preset duration. If the duration exceeds the preset duration, electronic device 100 may remove the display of the device permission icon in the status bar when the re-access to the device permission ends. Alternatively, if the duration does not exceed the preset duration, electronic device 100 may supplement 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 to the device permission begins may be indicated as currentTime3. The time when the re-access to the device permission ends may be indicated as currentTime4. Electronic device 100 may determine whether the result of currentTime4 - currentTime1 exceeds a preset duration. If currentTime4 - currentTime1 exceeds a preset duration, electronic device 100 may remove the display of the device permission icon for the accessed device permission in the status bar at currentTime4. Alternatively, if currentTime4 - currentTime1 does not exceed a preset duration, the electronic device 100 may continue to display the device permission icon for accessed devices in the status bar after currentTime4 by using an extended duration resulting from the preset duration - (currentTime4 currentTime1).

[0327] In the delayed completion mechanism, it should be noted that the device permission icon may be the device permission icon of the first type of device permission in this application.

[0328] Figures 16A to 16C show several examples of sensitive behavior reminder scenarios according to one embodiment of the present application.

[0329] In this specification, an example of a recorder application accessing microphone permissions is used for illustrative purposes.

[0330] Figure 16A illustrates a scenario in which the electronic device 100 displays the microphone icon in the status bar when the recorder application accesses the microphone permission once and the access duration exceeds a preset duration. The preset duration may be, for example, 5 seconds.

[0331] As shown in Figure 16A, the electronic device 100 receives an operation to start recording at 1 second. The operation to start recording may be, for example, an operation to the recording start control 1511 shown in Figure 15A. In response to the operation to start recording, the recorder application may start accessing the microphone permission of the electronic device 100 and 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 at which the microphone icon starts to appear in the status bar may be 1 second. The electronic device 100 receives an operation to end recording at 7 seconds. The operation to end recording may be, for example, an operation to the recording end control 1523 shown in Figure 15B. In response to the operation to end recording, the recorder application may terminate its access to the microphone permission of the electronic device 100 at this point. In this case, the electronic device 100 may determine that the duration of microphone permission access at this point (i.e., a total of 6 seconds from 1 second to 7 seconds) exceeds a preset duration. The electronic device 100 may remove the microphone icon from the status bar at 7 seconds. In the scenario shown in Figure 16A, where the recorder application accesses microphone permission, it can be seen that the electronic device 100 may continuously display the microphone icon in the status bar from 1 second to 7 seconds (a total duration of 6 seconds).

[0332] Figure 16B illustrates a scenario in which the electronic device 100 displays the microphone icon in the status bar when the recorder application accesses the microphone permission once and the access duration does not exceed a preset duration. The preset duration may be, for example, 5 seconds.

[0333] As shown in Figure 16B, the electronic device 100 receives a recording start command at 1 second. In response to the recording start command, the recorder application may initiate access to the microphone permission of the electronic device 100. The electronic device 100 displays "microphone permission" in the status bar. icon The microphone icon may begin to appear in the status bar at 1 second. At 3 seconds, the electronic device 100 receives an operation to end recording. In response to the operation to end recording, the recorder application may terminate its access to the microphone permission of the electronic device 100 at this point. In this case, the electronic device 100 may determine that the duration of access to the microphone permission at this point (i.e., a total of 2 seconds from 1 second to 3 seconds) does not exceed a preset duration. The electronic device 100 may extend the display duration of the microphone icon in the status bar. Based on the preset duration - (the time when access to the microphone permission ends (i.e., 3 seconds) - the time when access to the microphone permission begins (i.e., 1 second)), the electronic device 100 may determine that the extended 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 from 3 seconds for 3 seconds. At 6 seconds, the electronic device 100 may remove the display of the microphone icon in the status bar. In the scenario shown in Figure 16B, where the recorder application accesses microphone permission, it can be seen that the electronic device 100 may continuously display a microphone icon in the status bar from second 1 to second 6 (a total duration of 5 seconds).

[0334] Figure 16C illustrates a scenario in which the electronic device 100 displays the microphone icon in the status bar when the recorder application accesses the microphone permission twice, the duration of the two accesses does not exceed a preset duration, and the start of the second access to the microphone permission falls within an extension period based on the access duration of the first access to the microphone permission. The preset duration may be, for example, 5 seconds.

[0335] As shown in Figure 16C, the recorder application accesses the microphone permission of electronic device 100 during a first period from 1 second to 3 seconds, and accesses the microphone permission of electronic device 100 during a second period from 4 seconds to 6 seconds. From the embodiments described above, it can be seen that electronic device 100 may begin displaying the microphone icon in the status bar at 1 second. At 3 seconds, upon receiving an operation to end recording, electronic device 100 may determine that the access duration for the first access of the microphone permission (i.e., a total of 2 seconds from 1 second to 3 seconds) does not exceed a preset duration. Electronic device 100 may extend the display duration of the microphone icon in the status bar. From the embodiment shown in Figure 16B, it can be seen that the period during which electronic device 100 extends the display of the microphone icon may be from 3 seconds to 6 seconds (a total of 3 seconds). When the recorder application detects that it will access microphone permission for the second time between seconds 4 and 6, the electronic device 100 may re-determine the display duration of the microphone icon by using the start time of the second access to microphone permission (i.e., seconds 4) as the start time, using a delay interpolation mechanism. At seconds 6, upon receiving an operation to end recording, the electronic device 100 may determine that the access duration for the second access to microphone permission (i.e., a total of 2 seconds from seconds 4 to 6) does not exceed a preset duration. Based on the preset duration - (the time when the second access to microphone permission ends (i.e., seconds 6) - the time when the second access to microphone permission started (i.e., seconds 4)), 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 from seconds 6 for 3 seconds. At seconds 9, the electronic device 100 may remove the display of the microphone icon in the status bar.In the scenario shown in Figure 16C, where the recorder application accesses microphone permission, it can be seen that the electronic device 100 may continuously display a microphone icon in the status bar from second 1 to second 9 (a total duration of 8 seconds).

[0336] From the scenarios in Figures 16A to 16C, it can be seen that when the access duration of the accessed device permission is excessively short, the electronic device 100 may extend the display duration of the device permission icon after the permission visitor has finished accessing it, so that the device permission icon continues to be displayed in the status bar for a certain period of time, thereby ensuring that the display duration of the device permission reaches a preset duration. The method described above can be used to avoid the device permission icon displayed in the status bar flashing frequently when the device permission is accessed frequently, to prevent the electronic device 100 from frequently refreshing the device permission icon displayed in the status bar, to improve the user experience when browsing the status bar, and to reduce the power consumption of the electronic device 100 for refreshing the device permission icon.

[0337] The following describes the sensitive behavior reminder method provided in the embodiments of this application.

[0338] Figures 17A to 17E are flowcharts of an example of a sensitive behavior reminder method according to one embodiment of this application. This method is applied to the electronic device 100 and communication system 30 described in the above-mentioned embodiment. From the embodiment shown in Figure 4, it can be seen that the electronic device 100 may include a device authorization provisioning service 410, an application behavior recording module 420, a device authorization 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 Figures 17A to 17E, this method may include steps S1 to S23.

[0340] (1) In steps S1 to S7, a first type of device authorization is accessed, and the electronic device 100 displays the device authorization icon for the first type of device authorization in its status bar.

[0341] In this specification, camera permission in the first type of device permission is used specifically as an example for illustrative purposes. The first type of device permission may further include microphone permission, location permission, and so on. For how electronic device 100 displays a device permission icon in the status bar when another first type of device permission is accessed, see How electronic device 100 displays a camera icon in the status bar.

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

[0343] In possible implementations, the device authorization management service 440 may register listeners with the application behavior recording module 420. When access to a first type of device authorization of an electronic device 100 is detected, the listener may instruct the application behavior recording module 420 to send access information for the first type of device authorization to the device authorization management service 440.

[0344] The timing at which the device authorization management service 440 registers a listener is not limited to this embodiment of the present application. For example, the device authorization management service 440 may register a listener with the application behavior recording module 420 after the electronic device 100 has received a power-on operation.

[0345] S2: Authorized visitors may have access to camera permissions from the device's authorization provisioning service 410.

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

[0347] An authorized visitor may send a request to the device authorization provision service 410 to access camera authorization. The device authorization provision service 410 may determine whether the authorized visitor is entitled to access camera authorization. If it determines that the authorized visitor is entitled to access camera authorization, the device authorization provision service 410 may allow the authorized visitor to access camera authorization, thereby enabling the authorized visitor to call the camera service of electronic device 100 and capture images by using the camera of electronic device 100. Alternatively, if it determines that the authorized visitor is not entitled to access camera authorization, the device authorization provision service 410 may deny the authorized visitor access to camera authorization.

[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 camera permission access was initiated.

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

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

[0351] Since the device permission management service 440 registers the 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 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 visitor information and the time when camera permission access was initiated.

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

[0354] In possible implementations, the sensitive behavior reminder module 450 may store access information for a first type of device permission in a cache. Upon receiving message 3, the sensitive behavior reminder module 450 may update the cache and store access information for the last accessed camera permission. The access information may include information about the visitor accessing the last accessed camera permission and the time the access began.

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

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

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

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

[0359] For a scenario in which the status bar controller 460 displays a device permission icon on the status bar for the electronic device 200 accessed by the first electronic device, please refer to the aforementioned scenario shown in Figures 10I to 10K.

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

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

[0362] S8: Authorized visitors may have access to contact authorization from device authorization provisioning service 410.

[0363] An authorized visitor may send a request to the device authorization provision service 410 to access contact authorization. The device authorization provision service 410 may determine whether the authorized visitor is entitled to access contact authorization. If it determines that the authorized visitor is entitled to access contact authorization, the device authorization provision service 410 may allow the authorized visitor to access contact authorization, thereby enabling the authorized visitor to call the contact service of the electronic device 100 and obtain contact information for the electronic device 100. Alternatively, if it determines that the authorized visitor is not entitled to access contact authorization, the device authorization provision service 410 may deny the authorized visitor access to contact authorization.

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

[0365] After enabling an authorized visitor to access contact permissions, 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 contact permissions have been accessed.

[0366] S10: The application behavior recording module 420 may store visitor information and the access time for 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 authorization and the second type of device authorization are being accessed.

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

[0369] For instructions on how to open the control center interface, please refer to the previously described procedure shown in Figure 5A.

[0370] When an operation to open the control center interface is detected, the control center module 480 may trigger the electronic device 100 to display the control center interface. For details on the control center interface, please refer to the control center interface shown in Figure 5B.

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

[0372] S12: In response to an operation to open the control center interface, the control center module 480 may send message 6 to the privacy indicator 470, instructing it 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 access information for a first type of device permission.

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

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

[0376] In a possible implementation, the privacy indicator 470 may be required to obtain which first type of device permission of the electronic device 100 is accessed when an operation to open the control center interface is received. From steps S2 to S7 above, it can be seen that the authorized visitor has access to the camera permission. In this case, the access information of the first type of device permission sent 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 access information of a second type of device permission from the application behavior recording module 420 during period T1, where period T1 is a preset period prior to time ta.

[0378] From the aforementioned characteristics of the second type of device authorization, it can be seen that the action by an authorized visitor to access the second type of device authorization is usually a separate action and may not continue over a period of time. The privacy indicator 470 may request to obtain the access information of the authorized visitor accessing the second type of device authorization during a predetermined period (i.e., period T1) prior to the operation to open the control center interface being received.

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

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

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

[0382] For sensitive behavior prompts displayed in the control center interface by the privacy indicator 470, please refer to the sensitive behavior prompt 813 shown in Figure 8A.

[0383] (4) In steps S18 to S23, access to the first type of device authorization is terminated, and the electronic device 100 removes the display of the device authorization icon for the first type of device authorization in the status bar.

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

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

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

[0387] Since the device permission management service 440 registers the 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 authorized visitor has terminated 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 camera permission has ended.

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

[0390] Camera permission access information may include information about the last visitor accessing the camera permission, as well as the time when the access ended.

[0391] S23: The sensitive behavior reminder module 450 may send message 10 to the status bar controller 460, instructing it to remove the camera icon from the status bar.

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

[0393] In a possible implementation, upon receiving message 10, the status bar controller 460 may remove the camera icon from the status bar.

[0394] In another possible implementation, upon receiving message 10, the status bar controller 460 may determine the point at which the camera icon is removed from the status bar by using a delay interpolation mechanism. The status bar controller 460 may determine the access duration based on when access to camera permission begins and when access to camera permission ends, and compare the access duration with a preset duration to determine whether to extend the display time of the camera icon in the status bar. For details of the delay interpolation mechanism, please refer to the description of the embodiments above. Further details will not be described herein.

[0395] It should be noted that steps S18 to S23 described above may be performed after the electronic device 100 has collapsed the control center interface. If, during the process of the electronic device 100 displaying the control center interface, the authorized visitor has terminated access to camera permission, the electronic device 100 may leave the sensitive behavior prompt displayed on the control center interface unchanged. The sensitive behavior prompt on the control center interface may still include the camera icon for camera permission. The electronic device 100 may then collapse the control center interface. The electronic device 100 may remove the camera icon from the status bar of the user interface displayed after the control center interface has collapsed.

[0396] In this embodiment of the present application, it may be understood that the sensitive behavior reminder method provided herein is specifically illustrated by using an example in which the sensitive behavior prompt is displayed in a control center interface. Not limited to the control center interface, the sensitive behavior prompt may be displayed in another user interface, such as a pull-down notification interface.

[0397] As shown in Figures 17A to 17E, when electronic device 100 detects that a device permission is being accessed by an application on electronic device 100 or another electronic device, electronic device 100 may display a device permission icon in the status bar and / or control center interface, thereby letting the user know that they can be aware of and control the sensitive behavior and cross-device sensitive behavior of the application on the device. Sensitive behavior reminders provided by electronic device 100 include reminders that a first type of device permission, such as camera permission or microphone permission, is being accessed, as well as contact permission, media Ao The system may further include reminders that a second type of device permission, such as file permissions, is being accessed. Thus, the user can more intuitively and conveniently know the access data for each device permission. In addition, the electronic device 100 may further display device permission icons in the status bar by using a delayed interpolation mechanism to inform the user that the corresponding device permission is being accessed. The delayed interpolation mechanism may be used to avoid frequent flashing of the device permission icons displayed in the status bar, to prevent the electronic device 100 from frequently refreshing the device permission icons displayed in the status bar, to improve the user experience when browsing the status bar, and to reduce the power consumption of the electronic device 100 for refreshing the device permission icons.

[0398] It should be understood that each user interface described in the embodiments of this application is merely illustrative and does not constitute a limitation to the solutions of this application. In other embodiments, the user interface may use a different interface layout, include more or fewer controls, add or remove other functional options, and all fall within the scope of protection of this application, provided that the user interface is based on the same inventive idea provided in this application.

[0399] It should be noted that, unless there is a contradiction or conflict, any feature or any part of any feature in any embodiment of this application may be combined, and the combined technical solution will also fall within the scope of the embodiments of this application.

[0400] In conclusion, the embodiments described above are intended solely to illustrate the technical solutions of this application and not to limit it. Although this application is described in detail with reference to the embodiments described above, those skilled in the art should understand that modifications may still be made to the technical solutions described in the embodiments described above, or equivalent substitutions may be made to some of their technical features, without departing from the scope of the technical solutions of the embodiments of this application.

Claims

1. Application-sensitive behavior reminder method, A first electronic device receives 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 to obtain user privacy information; In response to the first request, the first electronic device enables the second electronic device to access the first device permission, and displays a first icon in the status bar, the first icon indicating that the first device permission is being accessed. The first electronic device receives a first operation, A step of displaying a first interface in response to a first operation by the first electronic device, wherein the first interface includes a first prompt, and the first prompt includes a first icon. A method that includes this.

2. The first electronic device receives a second operation in response to the first prompt, A step of displaying a first authorization list in response to a second operation by the first electronic device, wherein the first authorization list includes first information, the first information indicating that the first device authorization is accessed by the second electronic device; The method according to claim 1, further comprising:

3. The first electronic device receives a third operation on the first information, A step of displaying a first control in response to a third operation by the first electronic device, wherein the first control is used to manage the second electronic device's access to the first device authorization. The method according to claim 2, further comprising:

4. After the step of receiving the first operation by the first electronic device, the method, A step of obtaining a first access record by querying the access record of access to the device authorization of the first electronic device during a first period, wherein the first period is the period before the first operation is received, and the first access record includes first access data of access to the first device authorization by the second electronic device. It further includes, The step of displaying a first interface by the first electronic device, wherein the first interface includes a first prompt, the step is particularly, A step of displaying a first interface based on a first access record using the first electronic device, wherein the first interface includes a first prompt, and the first icon included in the first prompt is determined based on the first access data. The method according to claim 1, including the method described in claim 1.

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, each of which indicates 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 displayed collapsed according to the first priority. The first priority indicates the priority of the device authorization for the first electronic device, a higher priority device authorization in the first priority indicates that an icon indicating that the device authorization is accessed is displayed at a higher level in the first interface, and the icon displayed in the higher layer partially blocks the icon displayed in the lower layer. The first prompt further includes an identifier for the device permission visitor corresponding to the icon displayed at the highest level in the first prompt, The method according to claim 5.

7. The first electronic device detects that the second electronic device has terminated its access to the first device authorization, The first electronic device performs the steps of: clearing the display of the first icon in the status bar; The method according to claim 1, further comprising:

8. Prior to the step of removing the display of the first icon in the status bar by the first electronic device, the method: The first electronic device determines that the first access duration for the second electronic device to access the first device authorization exceeds the first duration. The method according to claim 7, further comprising:

9. The first electronic device detects that the second electronic device has terminated its access to the first device authorization, The first electronic device determines whether the first access duration for the second electronic device to access the first device authorization 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. A step of continuing to display the first icon on the status bar by the first electronic device for a second period, wherein the second period is a period within the first extended duration that begins when the second electronic device terminates access to the first device permission. The method according to claim 1, further comprising:

10. The first electronic device detects the re-access granted by the first device during the second period, The first electronic device continues to display the first icon on the status bar during the period of re-access granted to the first device, The first electronic device determines whether the second access duration of the first device authorization exceeds the first duration, If it is determined that the second access duration exceeds the first duration, the first electronic device removes the display of the first icon in the status bar when the re-access of the first device permission is completed, or If 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. A step of continuing to display the first icon on the status bar by the first electronic device for a third period, wherein the third period is a period within the second extended duration that begins from the time the re-access of the first device permission is completed. The method according to claim 9, further comprising:

11. The first electronic device receives the fourth operation, A step of displaying a second control by the first electronic device in response to the fourth operation, wherein the second control is used to manage the second electronic device's access to the first electronic device's device authorization, or A step of displaying a third control in response to a fourth operation by the first electronic device, wherein the third control is used to manage access of different applications on the second electronic device to the device authorization of the first electronic device, and The method according to claim 1, further comprising:

12. After the step of receiving the first operation by the first electronic device, the method, A step of obtaining a second access record by querying the access record of the first electronic device's access to the device authorization of another electronic device during a first period, wherein the first period is the period before the first operation is received, and the second access record includes access data of the first electronic device's access to the second device authorization of a third electronic device. It further includes, The first interface further includes a second prompt, the second prompt being determined based on the second access log, and the second prompt indicating that the first electronic device has access to the second device authorization of the third electronic device. The method according to claim 1.

13. The method according to claim 1, wherein the device permissions for the first electronic device include camera permission, microphone permission, location permission, contact permission, and media and file permission.

14. The method according to claim 1, wherein the first operation is a sliding operation from the upper right to the lower part of the screen of the first electronic device, and the first interface is the control center interface of the first electronic device.

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

16. A computer-readable storage medium comprising an instruction, wherein when the instruction is executed on an electronic device, the electronic device is capable of performing the method according to any one of claims 1 to 14.

17. A computer program product, wherein the computer program product includes computer instructions, and when the computer instructions are executed on an electronic device, the electronic device becomes capable of performing the method according to any one of claims 1 to 14.

Images