CN115408708A

CN115408708A - Graphical interface display method, electronic device, medium, and program product

Info

Publication number: CN115408708A
Application number: CN202110594724.3A
Authority: CN
Inventors: 杜奕全; 邓勐; 杨晓; 李凯
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-05-28
Filing date: 2021-05-28
Publication date: 2022-11-29
Also published as: WO2022247664A1

Abstract

The present disclosure relates to a graphical interface display method, an electronic device, a computer-readable storage medium, and a computer program product. Displaying a User Interface (UI) on a screen of an electronic device according to the graphical interface display method described herein; detecting a protection operation associated with the UI; and in response to detecting the protection operation, causing content associated with at least a portion of the UI to not be displayed normally on the screen. In this way, user information may be protected from unauthorized users, thereby enhancing the security of the electronic device and significantly improving the user experience.

Description

Graphical interface display method, electronic device, medium, and program product

Technical Field

The present disclosure relates generally to the field of information technology, and more particularly, to a graphical interface display method, an electronic device, a computer-readable storage medium, and a computer program product.

Background

With the popularization of electronic devices, information security and privacy protection are more and more concerned by people. For example, typical information protection approaches include application locks, privacy spaces, artificial Intelligence (AI) hidden notification content, and the like. However, the conventional user information protection method cannot effectively prevent information from being peeped, and how to further improve the information security is still a key for improving the user experience.

Disclosure of Invention

According to some embodiments of the present disclosure, a graphical interface display method, an electronic device, a medium, and a program product are provided, which can protect user information so that the user information is not viewed by an unauthorized user, thereby enhancing security of the electronic device and significantly improving user experience.

In a first aspect of the disclosure, a graphical interface display method is provided. Displaying a User Interface (UI) on a screen of an electronic device according to the graphical interface display method of the first aspect; detecting a protection operation associated with the UI; and in response to detecting the protection operation, causing content associated with at least a portion of the UI to not be displayed normally on the screen. In this way, the user information can be protected so that the user information cannot be viewed by an unauthorized user, thereby enhancing the security of the electronic device and significantly improving the user experience.

In some implementations, the content associated with at least a portion of the UI includes at least one of: content displayed by at least a portion of the UI, and content accessed via at least a portion of the UI. In this way, content currently displayed by the UI and/or content further accessed via the content currently displayed by the UI can be protected, thereby enhancing the security of the electronic device and significantly improving the user experience.

In some implementations, the protection operation includes: and performing element protection operation for protecting the UI element in the UI, wherein the element protection operation prevents the content associated with the UI element from being displayed normally, or performing interface protection operation for protecting the UI, and the interface protection operation prevents at least part of the content of the UI from being displayed normally. In this way, user information can be protected at the granularity of a UI or UI element in a UI, thereby enhancing the security of the electronic device and significantly improving the user experience.

In some implementations, the protection operation is the element protection operation, and causing the content to be displayed without error includes: determining a target UI element corresponding to the element protection operation based on the element protection operation; and causing the content associated with the target UI element to not be displayed normally. In this way, the target UI element can be easily determined and protected, thereby enhancing flexibility of information protection and improving user experience.

In some implementations, the element protection operation includes a control display operation and a selection operation, and the determining a target UI element corresponding to the element protection operation based on the element protection operation includes: displaying an element protection control corresponding to at least one UI element included in the UI on the screen based on the control display operation; and determining the UI element corresponding to the element protection control acted by the selection operation as the target UI element based on the selection operation. In this way, the target UI element can be intuitively selected through the element protection control and protected, thereby enhancing flexibility of information protection and improving user experience.

In some implementations, disabling normal display of the content associated with the target UI element includes: determining a mode to protect the target UI element, the mode indicating at least one of: obfuscating the content and preventing access to the content via the target UI element; and disabling normal display of the content associated with the target UI element based on the pattern. In this way, different protection modes can be applied to different UI elements, thereby enhancing flexibility in information protection and improving user experience.

In some implementations, disabling normal display of the content associated with the target UI element includes: blurring the content. For example, obfuscating the content may include obfuscating content displayed by the target UI element itself and/or obfuscating content accessed via the target UI element. In this way, an unauthorized user is prevented from clearly viewing the content that the user desires to protect.

In some implementations, disabling normal display of the content associated with the target UI element includes: preventing access to the content via the target UI element. For example, preventing access to the content via the target UI element may include disabling the user from operating on the target UI element and/or causing the target UI element to no longer respond to the user operation. In this manner, unauthorized users are prevented from accessing content that the user desires to protect.

In some implementations, the protection operation is the element protection operation, and the method further includes: detecting an unprotection operation that acts on the target UI element; and in response to detecting the unprotection operation, causing the content associated with the target UI element to be displayed normally. In this way, the protection of the content can be released, so that the user can view the desired content.

In some implementations, causing the content associated with the target UI element to be displayed normally includes: verifying the identity of the user initiating the unprotection operation; and in response to the authentication being successful, causing the content associated with the target UI element to be displayed normally. In this way, an authorized user whose authentication is successful is enabled to view desired content.

In some implementations, the protection operation is the interface protection operation, and disabling normal display of the all content of the UI includes: obfuscating the all content of the UI. In this way, an unauthorized user is prevented from clearly viewing the content that the user desires to protect.

In some implementations, the protection operation is the interface protection operation, and the method further includes: detecting a unprotection operation acting on the UI; in response to detecting the unprotection operation, determining a target area in the UI indicated by a location where the unprotection operation occurred; and enabling the target area to be displayed normally. In this way, the protection of the content can be released, so that the user can view the desired content.

In some implementations, the unprotection operation is a click operation, the UI includes at least one window, and determining the target region includes: and determining a target window in the at least one window where the click operation occurs as the target area. In this way, the protection of the clicked window can be released, so that the user can easily view the content he desires by clicking.

In some implementations, the unprotect operation is a region-drawing operation, and determining the target region includes: and determining the part enclosed by the region drawing operation in the UI as the target region. For example, the user may draw the target region through a pre-shaped shape. Alternatively, the user may also be free to draw the target area arbitrarily. In this way, the protection of the portion in the circle can be released, so that the user can easily view the content he desires through the region drawing operation.

In some implementations, the unprotection operation is a swipe operation, and determining the target area includes: determining a portion of the UI where the swipe operation occurs as the target area. In this way, the protection of the wiped portion can be released, so that the user can easily view the content he desires through the wiping operation.

In a second aspect of the disclosure, an electronic device is provided. The electronic device comprises a processor and a memory storing instructions that, when executed by the processor, cause the electronic device to perform any of the methods according to the first aspect and implementations thereof.

In a third aspect of the disclosure, a computer-readable storage medium is provided. The computer readable storage medium has instructions stored thereon, which when executed by a processor cause the electronic device to perform any of the methods according to the first aspect and its implementations.

In a fourth aspect of the disclosure, a computer program product is provided. The computer program product comprises instructions which, when executed by a processor, cause the electronic device to perform any of the methods according to the first aspect and its implementations.

Drawings

Features, advantages and other aspects of various implementations of the disclosure will become more apparent with reference to the following detailed description when taken in conjunction with the accompanying drawings. Several implementations of the present disclosure are illustrated herein by way of example, and not by way of limitation, in the figures of the accompanying drawings:

fig. 1A to 1B show schematic diagrams of a hardware structure and a software structure of an electronic device in which an embodiment of the present disclosure can be implemented.

FIG. 2 illustrates a block diagram of another electronic device in which embodiments of the present disclosure may be implemented.

Figures 3A-3I illustrate schematic diagrams of a first example of a UI associated with an element protection operation, according to some embodiments of the present disclosure.

4A-4L illustrate diagrams of a second example of a UI associated with an element protection operation, according to some embodiments of the present disclosure.

5A-5P illustrate schematic diagrams of a third example of a UI associated with an element protection operation, according to some embodiments of the present disclosure.

6A-6D illustrate schematic diagrams of a fourth example of a UI associated with an interface protection operation, according to some embodiments of the present disclosure.

7A-7E illustrate schematic diagrams of a fifth example of a UI associated with an interface protection operation, according to some embodiments of the present disclosure.

Figures 8A-8E illustrate schematic diagrams of a sixth example of a UI associated with an interface protection operation, according to some embodiments of the disclosure.

9A-9E illustrate schematic diagrams of a seventh example of a UI associated with an interface protection operation, according to some embodiments of the present disclosure.

10A-10E illustrate schematic diagrams of an eighth example of a UI associated with an interface protection operation, according to some embodiments of the present disclosure.

Fig. 11 shows a flowchart of a graphical interface display method according to an embodiment of the present disclosure.

Fig. 12 shows a schematic diagram of a system architecture according to an embodiment of the present disclosure.

Fig. 13 shows a schematic diagram of a partial sharpening architecture according to an embodiment of the disclosure.

Fig. 14 shows a schematic diagram of physical elements according to an embodiment of the disclosure.

Detailed Description

Some example implementations of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain example implementations of the disclosure are shown in the drawings, it should be understood that the disclosure may be embodied in various forms and should not be limited to the example implementations set forth herein. Rather, these implementations are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

The term "include" and variations thereof as used herein is meant to be inclusive in an open-ended manner, i.e., "including but not limited to". Unless stated otherwise, the term "or" means "and/or". The term "based on" means "based at least in part on". The terms "embodiment" and "some embodiments" mean "at least some embodiments". The terms "first", "second", etc. are used to describe, distinguish, etc., different objects, and do not denote any order, nor do the terms "first" and "second" denote any order, or importance.

The term "UI" as used herein refers to an interface for user interaction and information exchange with an application or operating system that enables conversion between an internal form of information and a form that is acceptable to the user. For example, the UI of the application is source code written by java, extensible markup language (XML), and the like in a specific computer language, and the UI source code is parsed, rendered, and finally presented as content that can be recognized by the user, such as pictures, words, buttons, and other UI elements, on the electronic device.

In some embodiments, the properties and content of UI elements in the UI are defined by tags or nodes, such as XML specifying the UI elements that the UI contains by nodes < TextView >, < ImgView >, < VideoView >, etc. A node corresponds to a UI element or attribute in the UI, and the node is rendered as user-viewable content after parsing and rendering. In addition, many applications, such as hybrid applications (hybrid applications), typically include web pages in their UIs. A web page may be understood as a special UI element embedded in the UI of an application, the web page is a source code written in a specific computer language, such as hypertext markup language (HTML), cascading Style Sheets (CSS), java scripts (JavaScript, JS), etc., and the source code of the web page may be loaded and displayed as content recognizable to a user by a browser or a web page display component similar to the browser function. The specific content contained in the web page is also defined by tags or nodes in the source code of the web page, such as HTML, which defines elements and attributes of the web page by < p >, < img >, < video >, < canvas >.

The term "UI element" as used herein includes, but is not limited to: a window (window), a scroll bar (scrollbar), a table view (tablevew), a button (button), a menu bar (menu bar), a text box (text box), a navigation bar, a tool bar (toolbar), an image (image), a static text (tabtext), a component (Widget), and the like.

In some of the flows described in the embodiments of the present disclosure, a plurality of operations or steps occurring in a specific order are included, but it should be understood that these operations or steps may be executed out of order or in parallel as they occur in the embodiments of the present disclosure, and the order of the operations is merely used to distinguish between the various operations, and the order itself does not represent any execution order. In addition, the flows may include more or less operations, and the operations or steps may be performed sequentially or in parallel, and the operations or steps may be combined.

As described above, with the popularization of electronic devices, information security and privacy protection are receiving more and more attention. Conventionally, there are a variety of information protection ways to protect information security and privacy, such as application lock, privacy space, AI-hidden notification content, and the like. However, these information protection approaches have their own drawbacks. For example, the application lock can only prevent unauthorized users from entering the application to view the content of the application, protect the scene singularly, and prevent the application content from leaking in real time. Furthermore, an application lock can only protect the content of the entire application, and cannot protect the content of a certain control or page within the application alone. The privacy space can only prevent unauthorized users from entering the privacy space, so that the single scene is protected, and the privacy space cannot be prevented from being leaked in real time. In addition, the AI-hidden notification content can only protect the message notification scenario, and cannot protect other scenarios.

Therefore, the traditional information protection mode has the defect of single protection scene and cannot meet the requirements of users. For example, when a user uses an electronic device in a subway, the content displayed on the electronic device is easily seen by others, which causes information leakage. The scene cannot be solved by applying traditional information protection modes such as locks, privacy spaces and the like.

Therefore, the embodiment of the disclosure provides a new scheme for displaying a graphical interface. Embodiments of the present disclosure relate to applying a protection operation to at least a portion of associated content of a UI such that the content is not normally displayed on a screen. Specifically, the protection operation includes an element protection operation and an interface protection operation. In the element protection operation, the protection of the local content is realized by adopting a mode of protecting the control and the layout. For example, when a user uses an application, the user may not want a certain control or layout that others see, in which case the user may employ element protection operations to protect the content. After such content is protected, it needs to be verified via passwords, fingerprints, faces, etc. to be able to view a particular control or layout within the application. In addition, in the interface protection operation, the electronic device is only enabled to display a part of the UI, and the other part cannot be normally displayed, for example, obscured, to realize information protection. By means of displaying the local content, the content which is expected to be protected of the electronic equipment can be protected in real time from being leaked, so that the safety of the electronic equipment is enhanced, and the user experience is remarkably improved.

Some example embodiments of the present disclosure will be described below with reference to fig. 1A to 13.

Fig. 1A shows a schematic diagram of a hardware structure of an electronic device 100 in which an embodiment of the present disclosure may be implemented. As shown in fig. 1, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identification Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It should be understood that the illustrated structure of the embodiments of the present disclosure does not constitute a specific limitation on the electronic device 100. In other embodiments of the present disclosure, electronic device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), and the like. The different processing units may be separate devices or may be integrated into one or more processors. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose-input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The I2C interface is a bidirectional synchronous serial bus including a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, the processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc., respectively, through different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K through an I2C interface, such that the processor 110 and the touch sensor 180K communicate through an I2C bus interface to implement the touch function of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 through an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through the I2S interface, so as to implement a function of receiving a call through a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to implement a function of answering a call through a bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 with the wireless communication module 160. For example, the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through a UART interface, so as to implement the function of playing music through a bluetooth headset.

A MIPI interface may be used to connect processor 110 with peripheral devices such as display screen 194, camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the capture functionality of electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display screen 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transmit data between the electronic device 100 and a peripheral device. And the method can also be used for connecting a headset and playing audio through the headset. The interface may also be used to connect other electronic devices, such as AR devices and the like.

It is understood that the exemplary interfacing relationship between the modules according to the embodiments of the disclosure is only illustrative, and does not limit the structure of the electronic device 100. In other embodiments of the present disclosure, the electronic device 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also provide power to the electronic device 100 through the power management module 141 while charging the battery 142.

The power management module 141 is used for connecting the battery 142, the charging 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, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like. The antenna 1 and the antenna 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example, the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including wireless communication of 2G/3G/4G/5G/6G, etc. applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs), such as wireless fidelity (Wi-Fi) networks, bluetooth (BT), global Navigation Satellite System (GNSS), frequency Modulation (FM), near Field Communication (NFC), infrared (IR), and the like. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150 and antenna 2 is coupled to wireless communication module 160 so that electronic device 100 can communicate with networks and other devices through wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), general Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), wideband Code Division Multiple Access (WCDMA), time division code division multiple access (TD-SCDMA), long Term Evolution (LTE), 5G and subsequent evolution standards, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, and the like. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou satellite navigation system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The electronic device 100 implements display functions through the GPU, the display screen 194, and the application processor, etc. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. In some embodiments, the electronic device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The electronic device 100 may implement a photographing function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, the application processor, and the like. The ISP is used to process the data fed back by the camera 193. For example, when a user takes a picture, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, an optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and converting into an image visible to the naked eye. The ISP can also carry out algorithm optimization on noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP to be converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and so on.

The NPU is a neural-network (NN) computing processor, which processes input information quickly by referring to a biological neural network structure, for example, by referring to a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent recognition of the electronic device 100, for example, image recognition, face recognition, voice recognition, text understanding, and the like, may be implemented by the NPU.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The data storage area may store data (e.g., audio data, a phone book, etc.) created during use of the electronic device 100, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one disk memory device, a flash memory device, a universal flash memory (UFS), and the like. The processor 110 executes various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The electronic device 100 may implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor, etc. Such as music playing, recording, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be attached to and detached from the electronic apparatus 100 by being inserted into the SIM card interface 195 or being pulled out from the SIM card interface 195. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. The same SIM card interface 195 can be inserted with multiple cards at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with an external memory card. The electronic device 100 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, i.e., embedded SIM cards. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The software system of the electronic device 100 may employ a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present disclosure takes a mobile operating system of a layered architecture as an example, and illustrates a software structure of the electronic device 100.

Fig. 1B is a schematic diagram of a software structure of the electronic device 100 of the embodiment of the present disclosure. The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the operating system may be divided into four layers, an application layer, an application framework layer, an operating system runtime (runtime) and system libraries, and a kernel layer, from top to bottom, respectively.

The application layer may include a series of application packages. As shown in fig. 1B, the application packages may include camera, gallery, calendar, phone, map, navigation, WLAN, bluetooth, music, video, short message, etc. applications.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 1B, the application framework layers may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like. The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like. Content providers are used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, dialed and received telephone calls, browsing history and bookmarks, phone books, etc. The view system includes visual controls, such as controls to display text, controls to display images, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying an image. The phone manager is used to provide communication functions of the electronic device 100. Such as management of call status (including on, off, etc.). The resource manager provides various resources for the application, such as localized strings, icons, images, layout files, video files, and the like. The notification manager enables the application program to display notification information in the status bar, can be used for conveying notification type messages, can automatically disappear after a short time of stay, and does not need user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

With continued reference to FIG. 1B, the operating system runtime includes a core library and a virtual machine. The operating system runtime is responsible for scheduling and management of the operating system. The core library comprises two parts, one part is a function which needs to be called by Java language, and the other part is the core library for operating the system. The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform the functions of object lifecycle management, stack management, thread management, security and exception management, and garbage collection. The system library may include a plurality of functional modules. Such as surface managers (surface managers), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide a fusion of the 2D and 3D layers for multiple applications. The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like. The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like. The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

FIG. 2 illustrates a block diagram of another electronic device 200 in which embodiments of the present disclosure may be implemented. As shown in fig. 2, electronic device 200 may be in the form of a general purpose computing device. The components of electronic device 200 may include, but are not limited to, one or more processors or processing units 210, memory 220, storage 230, one or more communication units 240, one or more input devices 250, and one or more output devices 260. The processing unit 210 may be a real or virtual processor and can perform various processes according to programs stored in the memory 220. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of the electronic device 200.

Electronic device 200 typically includes a number of computer storage media. Such media may be any available media that is accessible by electronic device 200 and includes, but is not limited to, volatile and non-volatile media, removable and non-removable media. The memory 220 may be volatile memory (e.g., registers, cache, random Access Memory (RAM)), non-volatile memory (e.g., read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory), or some combination thereof. Storage 230 may be a removable or non-removable medium and may include a machine-readable medium, such as a flash drive, a magnetic disk, or any other medium that may be capable of being used to store information and/or data (e.g., training data for training) and that may be accessed within electronic device 200.

The electronic device 200 may further include additional removable/non-removable, volatile/nonvolatile storage media. Although not shown in FIG. 2, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. Memory 220 may include a computer program product 225 having one or more program modules configured to perform the object editing methods or processes of embodiments of the present disclosure.

The communication unit 240 enables communication with other computing devices over a communication medium. Additionally, the functionality of the components of the electronic device 200 may be implemented in a single computing cluster or multiple computing machines, which are capable of communicating over a communications connection. Thus, the electronic device 200 may operate in a networked environment using logical connections to one or more other servers, network Personal Computers (PCs), or another network node.

Input device 250 may be one or more input devices such as a mouse, keyboard, trackball, or the like. Output device 260 may be one or more output devices such as a display, speakers, printer, or the like. In an embodiment of the present disclosure, the output device 260 may include a touch screen having a touch sensor, which may receive a touch input of a user. Electronic device 200 may also communicate with one or more external devices (not shown), such as storage devices, display devices, etc., as desired through communication unit 240, with one or more devices that enable a user to interact with electronic device 200, or with any device (e.g., network card, modem, etc.) that enables electronic device 200 to communicate with one or more other computing devices. Such communication may be performed via input/output (I/O) interfaces (not shown).

It should be understood that the electronic device 100 illustrated in fig. 1 and the electronic device 200 illustrated in fig. 2 above are merely two example electronic devices capable of implementing one or more embodiments of the present disclosure and should not be construed as limiting in any way the functionality and scope of the embodiments described herein.

The electronic device is described above. Further, as described above, embodiments of the present disclosure relate to applying a protection operation to at least a portion of associated content of a UI such that the content cannot be normally displayed on a screen. In some embodiments, the content associated with at least a portion of the UI is content displayed by at least a portion of the UI (e.g., setting a setting in a list of options), and/or content accessed via at least a portion of the UI (e.g., clicking on a settings interface displayed after the setting).

Specifically, the protection operation includes an element protection operation and an interface protection operation. In the element protection operation, the protection of the local content is realized by adopting a mode of protecting the control and the layout. In addition, in the interface protection operation, the electronic device is only enabled to display a part of the UI, and the other part cannot be normally displayed, for example, obscured, to realize information protection. To this end, example UIs associated with element protection operations are described below with reference to FIGS. 3A-5P, and example UIs associated with interface protection operations are described below with reference to FIGS. 6A-10E.

In the element protection operation, the electronic device may detect an element protection operation associated with the UI. Thus, the electronic device can determine a target UI element corresponding to the element protection operation based on the element protection operation and cause the content associated with the target UI element not to be normally displayed. For example, the electronic device may monitor whether the user has triggered an element protection operation, such as a long press of three fingers, a slide down of three fingers, a particular voice command, or any other suitable action. If an element protection operation is detected, the electronic device may cause content associated with at least a portion of the UI to not be displayed normally on the screen.

In some embodiments, the element protection operations may include a control display operation and a selection operation. In this case, the electronic device may display an element protection control corresponding to at least one UI element included in the UI on the screen based on the control display operation. In addition, the electronic device may determine, based on the selection operation, a UI element corresponding to the element protection control on which the selection operation acts as a target UI element. For example, the electronic device can monitor whether the user has triggered a control display operation, such as a long press with three fingers, a slide down with three fingers, a particular voice command, or any other suitable action. If the control display operation is detected, the electronic device can display an element protection control corresponding to at least one UI element included in the UI on the screen. The electronic device can detect a selection operation acting on the element protection control, such as any appropriate action of clicking, double-clicking, long-pressing, specific voice command, and the like, and determine the UI element corresponding to the element protection control acted on by the selection operation as the target UI element, thereby realizing the selection of the target UI element. If a selection operation is detected, the electronic device may cause content associated with the target UI element to be displayed abnormally.

In some embodiments, if a selection operation is detected, the electronic device may determine a mode in which the target UI element is to be protected. The mode may indicate to obscure the content, or to prevent access to the content via the target UI element. For example, to prevent access to content via the target UI element, the user may be made unable to operate on the target UI element, such as the target UI element may be grayed out, hidden, etc., so that the user cannot click on the target UI element. Alternatively, the target UI element may also be made to no longer affect the user operation, such as no longer displaying the content that would otherwise be displayed after clicking the target UI element, or no longer jumping to the content that would otherwise be jumped to after clicking the target UI element. Thus, the electronic device may cause the content associated with the target UI element to not be displayed normally based on the determined mode. However, alternatively, the mode of protecting the target UI element may also be predetermined, and thus the electronic device need not further determine the mode of protecting the target UI element.

For example, if a user desires to protect a UI element, he or she may enter the UI element into a protected state by clicking on the element protection control corresponding to the UI element, thereby rendering the content of the UI element, or content accessed via the UI element, incapable of being displayed properly. For example, the electronic device can cause content of the UI element to be obscured, cause content accessed via the UI element to be obscured, or cause content to be inaccessible via the UI element. This enables information protection.

Further, after causing the target UI element to enter the protected state, the electronic device may also detect an unprotection operation that acts on the target UI element. If an unprotection operation is detected, the electronic device may cause the content associated with the target UI element to be displayed normally. In some embodiments, the electronic device may also verify the identity of the user initiating the unprotection operation in the event that the unprotection operation is detected. If the authentication is successful, the electronic device can cause the content associated with the target UI element to be displayed normally. For example, if a user wants to view content associated with a UI element that enters a protected state, it may trigger a de-protected authentication interface (e.g., any suitable authentication means such as a password, fingerprint, face, etc.) by any suitable action such as long-pressing, double-clicking on the UI element, etc. After the user authentication is successful, the electronic device can cause the UI element to leave the protected state, thereby displaying the content associated with the UI element normally. For example, the electronic device can clarify content of the UI element, clarify content accessed via the UI element, or enable access to content via the UI element. This enables the information to be unprotected.

3A-3I illustrate schematic diagrams of a first example of UIs 300A-300I associated with element protection operations, according to some embodiments of the present disclosure. In particular, in the examples of FIGS. 3A-3I, scenarios are shown in which the content of a control is protected.

As shown in FIG. 3A, UI 300A may include multiple UI elements, such as UI element 330 and UI elements 340-1 through 340-7 (hereinafter collectively referred to as "UI element 340"). For example, UI 300A may be a messaging interface of an instant messaging application, in which case UI element 330 may be a control to open an additional action list or add a new message, while UI element 340 may be a message from a different sender. As another example, UI 300A may be a settings interface of an electronic device, in which case UI element 300 may be a control to open an additional list of operations or add new settings, while UI element 340 may be a different setting option.

It should be understood that UI 300A and UI elements 330 and 340 are merely examples, and that the UI may be virtually any suitable interface and the UI elements may be any suitable controls. As noted above, the term "UI element" as used herein includes, but is not limited to: a window (window), a scroll bar (scrollbar), a table view (tablevew), a button (button), a menu bar (menu bar), a text box (text box), a navigation bar, a tool bar (toolbar), an image (image), a static text (tabitext), a component (Widget), and the like.

As shown in fig. 3B, the electronic device can detect an element protection operation associated with the UI. As described above, element protection operations may include control display operations and selection operations. For example, the electronic device may monitor whether the user has triggered a control display operation, such as a long press of three fingers, a slide down of three fingers, a particular voice command, or any other suitable action. If a control display operation is detected, the electronic device may display, on the screen, element protection controls corresponding to at least one UI element included in the UI, for example, element protection controls 310-1 to 310-7 (hereinafter collectively referred to as "element protection controls 310") corresponding to UI elements 340-1 to 340-7, and element protection control 320 corresponding to UI element 330, as shown in FIG. 3C. It should be understood that the shape, size, and location, etc. of the element protection controls 310 and 320 are merely examples, and in fact, the element protection controls may have any suitable shape, size, and location. Further, although element protection controls corresponding to UI elements 330 and 340 are shown in fig. 3C, the number of element protection controls is merely an example. In fact, the electronic device may display more or fewer element protection controls, for example, the element protection control 320 corresponding to the UI element 330 may not be displayed, or more element protection controls corresponding to the status bar of the electronic device (i.e., the uppermost status bar of the UI showing information about network, power, time, etc.) may be displayed.

As shown in fig. 3D, the electronic device may detect a selection operation, such as any suitable action, e.g., a click, double click, long press, specific voice command, etc., acting on an element protection control corresponding to a target UI element of the at least one UI element. If a selection operation is detected, the electronic device may cause the content of the target UI element to be displayed abnormally. For example, as shown in FIG. 3E, the user desires to protect UI element 340-3 and clicks on the element protection control 310-3 corresponding to UI element 340-3. Thus, as shown in FIG. 3F, UI element 340-3 enters a protected state, thereby rendering the content of UI element 340-3 incapable of being displayed normally, e.g., such that the content of UI element 340-3 is obscured. This enables information protection. It should be appreciated that obfuscation is merely an example of being unable to display normally, and in fact, the content of the UI element may be made unable to display normally in any suitable way, such as overlaying with another image having a suitable transparency, disorganizing the display order of the content of the UI element, and so forth.

Further, after causing the target UI element to enter the protected state, the electronic device may also detect an unprotection operation that acts on the target UI element. If an unprotection operation is detected, the electronic device may cause the content of the target UI element to be displayed normally. In some embodiments, the electronic device may also verify the identity of the user initiating the unprotection operation in the event that the unprotection operation is detected. If the authentication is successful, the electronic device may cause the contents of the target UI element to be displayed normally. For example, as shown in FIG. 3G, the user wants to view the contents of UI element 340-3 that enters the protected state and triggers an unprotected authentication interface (e.g., a password, fingerprint, face, etc. authentication interface) as shown in FIG. 3H by any suitable action such as long pressing, double clicking on UI element 340-3, etc. After the user authentication is successful, the UI element 340-3 may be caused to leave the protected state, so that the contents of the UI element are displayed normally, as shown in FIG. 3I.

4A-4L illustrate schematic diagrams of a second example of UIs 400A-400L associated with element protection operations, according to some embodiments of the present disclosure. 4A-4L, scenarios are shown for protecting content accessed via a widget.

To more clearly understand the present example scenario, an example UI in the case where the element UI does not enter a protected state will first be described with reference to FIGS. 4A-4C. As shown in FIG. 4A, the UI 400A may include multiple UI elements, such as a UI element 430 and UI elements 440-1 through 440-7 (hereinafter collectively referred to as "UI element 440"). For example, UI 400A may be a messaging interface of an instant messaging application, in which case UI element 430 may be a control to open an additional list of operations or add a new message, while UI element 440 may be a message from a different sender. As another example, UI 400A may be a settings interface of an electronic device, in which case UI element 400 may be a control to open an additional list of operations or a control to add new settings, while UI element 440 may be a different setting option.

It should be understood that the UI 400A and UI elements 430 and 440 are merely examples, and that the UI may be virtually any suitable interface and the UI elements may be any suitable controls. As noted above, the term "UI element" as used herein includes, but is not limited to: a window (window), a scroll bar (scrollbar), a table view (tablevew), a button (button), a menu bar (menu bar), a text box (text box), a navigation bar, a tool bar (toolbar), an image (image), a static text (tabtext), a component (Widget), and the like.

As shown in FIG. 4B, the user wants to view content accessed via the UI element 430, e.g., the user wants to open an additional action list and has clicked on the UI element 430. In this case, as shown in FIG. 4C, the electronic device displays a list of additional operations, such as operations 1-3, that are accessible via UI element 430.

An example UI in the case where the element UI does not enter a protected state is described above, and an example UI in the case where the element UI is protected will be described below with reference to fig. 4D to 4L.

Similar to fig. 4A, as shown in fig. 4D, the UI 400D may include multiple UI elements, such as a UI element 430 and a UI element 440. As shown in fig. 4E, the electronic device can detect an element protection operation associated with the UI. As described above, the element protection operation may include a control display operation and a selection operation. For example, the electronic device may monitor whether the user has triggered a control display operation, such as a long press of three fingers, a slide down of three fingers, a particular voice command, or any other suitable action. If a control display operation is detected, the electronic device may display on the screen, as shown in FIG. 4F, element protection controls corresponding to at least one UI element included in the UI, for example, element protection controls 410-1 through 410-7 (collectively referred to as "element protection controls 410" hereinafter) corresponding to UI elements 440-1 through 440-7, and element protection control 420 corresponding to UI element 430. It should be understood that the shape, size, and location, etc. of element protection controls 410 and 420 are merely examples, and that in fact, the element protection controls may have any suitable shape, size, and location. Further, while element protection controls corresponding to UI elements 430 and 440 are shown in fig. 4F, the number of element protection controls is merely an example. In fact, the electronic device may display more or fewer element protection controls, for example, the element protection control 420 corresponding to the UI element 430 may not be displayed, or more element protection controls corresponding to the status bar of the electronic device (i.e., the uppermost status bar of the UI showing information about network, power, time, etc.) may be displayed.

As shown in fig. 4G, the electronic device may detect a selection operation, such as any suitable action, e.g., a click, double click, long press, specific voice command, etc., acting on an element protection control corresponding to a target UI element of the at least one UI element. If a selection operation is detected, the electronic device may cause content accessed via the target UI element to be displayed abnormally. For example, as shown in fig. 4H, the user desires to protect the UI element 430 and clicks on the element protection control 420 corresponding to the UI element 430. Thus, as shown in FIG. 4I, the UI element 430 enters a protected state, such that content accessed via the UI element 430 cannot be displayed normally, e.g., such that the UI element 430 becomes represented by a dashed line, and the additional operations list will not be opened via the UI element 430. This enables information protection. It should be appreciated that the dashed line represents an example of a UI element that is merely entering a protected state, and indeed, the UI element may be entered into a protected state in any suitable manner, such as to replace the UI element with another image, to graying out the UI element, and so forth.

Further, after causing the target UI element to enter the protected state, the electronic device may also detect an unprotection operation that acts on the target UI element. If an unprotection operation is detected, the electronic device can cause the content accessed via the target UI element to be displayed normally. In some embodiments, the electronic device may also verify the identity of the user initiating the unprotection operation in the event that the unprotection operation is detected. If the authentication is successful, the electronic device can cause the content accessed via the target UI element to be displayed normally. For example, as shown in FIG. 4J, the user wants to view content accessed via the UI element 430 entering the protected state, and triggers the un-protected verification interface (e.g., password, fingerprint, face, etc. verification interface) shown in FIG. 4K by any suitable action, such as long pressing, double clicking on the UI element 430, etc. After the user authentication is successful, the UI element 430 may be brought out of the protected state and the additional list of operations accessed via the UI element 430 is displayed normally, as shown in FIG. 4L.

The protection of the controls is described above with reference to fig. 3A-4L, and the protection of the layout is described below with reference to fig. 5A-5P. 5A-5P illustrate schematic diagrams of a third example of UIs 500A-500P associated with element protection operations, according to some embodiments of the present disclosure. 5A-5P, scenarios are shown that protect layouts accessed via a control.

To more clearly understand the present example scenario, an example UI in the case where the element UI does not enter a protected state will first be described with reference to FIGS. 5A-5C. As shown in fig. 5A, UI 500A may include a plurality of UI elements, such as controls associated with various smart devices and controls associated with home, mall, smart, and my layouts or pages. It should be understood that UI 500A and the UI elements therein are merely examples, and that UI may be virtually any suitable interface and that UI elements may be any suitable controls. As noted above, the term "UI element" as used herein includes, but is not limited to: a window (window), a scroll bar (scrollbar), a table view (tablevew), a button (button), a menu bar (menu bar), a text box (text box), a navigation bar, a tool bar (toolbar), an image (image), a static text (tabtext), a component (Widget), and the like.

As shown in FIG. 5B, the user wants to view the contents of the mall page and clicks on the mall control. In this case, the electronic device displays the content of the mall page, as shown in FIG. 5C.

An example UI in the case where the element UI does not enter the protected state is described above, and an example UI in the case where the element UI is protected will be described below with reference to fig. 5D to 5P.

Similar to FIG. 5A, as shown in FIG. 5D, UI 500D may include multiple UI elements, such as controls associated with various smart devices and controls associated with home, mall, smart, and My layouts or pages. As shown in fig. 5E, the electronic device may detect an element protection operation associated with the UI. As described above, element protection operations may include control display operations and selection operations. For example, the electronic device may monitor whether the user has triggered a control display operation, such as a long press of three fingers, a slide down of three fingers, a particular voice command, or any other suitable action. If the control display operation is detected, the electronic device may display, on the screen, element protection controls corresponding to at least one UI element included in the UI, for example, element protection controls 510-540 corresponding to a home control, a mall control, a smart control, and a my control, respectively, as shown in fig. 5F. It should be understood that the shape, size, and location, etc. of the element protection controls 510-540 are merely examples, and in fact, the element protection controls may have any suitable shape, size, and location. Further, while the element protection controls corresponding to the home control, the mall control, the smart control, and the my control, respectively, are shown in fig. 5F, the number of element protection controls is merely an example. In fact, the electronic device may display more or fewer element protection controls, e.g., may not display element protection controls 510 corresponding to home controls, or more element protection controls corresponding to various smart devices (e.g., controls of a television in a living room).

As shown in fig. 5G, the electronic device may detect a selection operation, such as any suitable action, e.g., a click, double click, long press, specific voice command, etc., acting on an element protection control corresponding to a target UI element of the at least one UI element. If a selection operation is detected, the electronic device may cause content accessed via the target UI element to be displayed abnormally. For example, as shown in FIG. 5H, the user desires to protect content accessed via a mall control, and clicks on an element protection control 520 corresponding to the mall control. Thus, as shown in FIG. 5I, content accessed via the mall controls enters a protected state and causes the mall controls to become represented by dashed lines. In this case, as shown in fig. 5J, even if the user wants to view the content accessed via the mall control by clicking on the mall control, the content accessed via the mall control cannot be displayed normally, e.g., such that the mall page is obscured (as shown in fig. 5K) or will not be accessible via the mall control (as shown in fig. 5L). This enables information protection.

It should be appreciated that the dashed line represents an example of a UI element that is merely entering a protected state, and indeed, the UI element may be entered into a protected state in any suitable manner, such as to replace the UI element with another image, graying out the UI element, and so forth. Moreover, blurring is also merely an example of not being able to display normally, and in fact, the content of the UI element may be made unable to display normally in any suitable manner, such as overlaying with another image having a suitable transparency, disordering the display order of the content of the UI element, and so forth.

Further, after causing the target UI element to enter the protected state, the electronic device may also detect an unprotection operation that acts on the target UI element. If an unprotection operation is detected, the electronic device may cause the content accessed via the target UI element to be displayed normally. In some embodiments, the electronic device may also verify the identity of the user initiating the unprotection operation in the event that the unprotection operation is detected. If the authentication is successful, the electronic device may cause the content accessed via the target UI element to be displayed normally. For example, the user may want to view content accessed via a mall control that enters a protected state and trigger a unprotected authentication interface (e.g., a password, fingerprint, face, etc. authentication interface) as shown in FIG. 5O by any suitable action, such as long pressing, double clicking on the mall control (as shown in FIG. 5N), or content associated with the mall control (as shown in FIG. 5M). After the user authentication is successful, the mall control may be brought out of the protected state and the mall page accessed via the mall control is displayed normally, as shown in fig. 5P.

The element protection operation is described above with reference to fig. 3A-5P, and the interface protection operation will be described below with reference to fig. 6A-10E. In the interface protection operation, the electronic device may detect an interface protection operation associated with the UI. For example, the electronic device may monitor whether the user has triggered any suitable action, such as an interface protection control, a particular voice command, and so forth. If an interface protection operation is detected, the electronic device may cause at least a portion of the content of the UI to not be displayed normally. For example, when the user clicks on an interface protection control, all or a portion of the contents of the UI are obscured. In this case, for example, when the user is on a public transportation such as a subway, other people cannot see the contents of the UI, thereby achieving information protection.

Further, after causing the content of the target UI element to enter the protected state, the electronic device may also detect a unprotection operation acting on the UI. If an unprotection operation is detected, the electronic device may cause at least a portion of the content of the UI to be displayed normally. In some embodiments, the electronic device may further determine a target area indicated by a position where the unprotection operation occurred in the UI and cause the target area to be displayed normally, in the case where the unprotection operation is detected. For example, in a case where the unprotection operation is a click operation and the UI includes at least one window, a target window in the at least one window in which the click operation has occurred may be determined as the target area. As another example, in a case where the unprotection operation is the region drawing operation, a portion surrounded by the region drawing operation in the UI may be determined as the target region. In some embodiments, the user may draw the target region by a predetermined shape (e.g., any suitable shape such as a circle, rectangle, etc.). For example, the user may draw the target area by dragging on the screen, zooming in and out of a predetermined shape, and the like. In this case, the target area may have a regular shape. Alternatively, the user may draw the target region arbitrarily. In this case, the target region may have an irregular shape. As still another example, in a case where the deprotection operation is a slide-wipe operation, a portion of the UI where the slide-wipe operation occurs may be determined as the target region.

6A-6D illustrate schematic diagrams of a fourth example of UIs 600A-600D associated with interface protection operations, according to some embodiments of the present disclosure. In particular, in the examples of FIGS. 6A-6D, a single floating window scenario is shown.

As shown in fig. 6A, the UI includes an interface protection control 610, a floating window 620, and other background portions. The electronic device may detect an interface protection operation associated with the UI. For example, the electronic device may monitor whether the user has triggered any suitable action, such as interface protection control 610, a particular voice command, and so forth. If an interface protection operation is detected, the electronic device may cause at least a portion of the content of the UI to not be displayed normally. For example, as shown in FIG. 6B, the user wants to protect at least a portion of the content of the UI and clicks on interface protection control 610. When the user clicks on interface protection control 610, at least a portion of the contents of the UI are obscured, as shown in fig. 6C. In this case, for example, when the user is on a public transportation tool such as a subway, other people cannot see the contents of the UI, thereby achieving information protection. It should be understood that while all of the contents of the UI are shown obscured in fig. 6C, only a portion of the contents of the UI may be obscured, such as only the floating window 620. In some embodiments, the protected content is settable by the electronic device or by a user.

Further, after causing at least a portion of the content of the UI to enter a protected state, the electronic device may also detect an unprotection operation acting on the UI. If an un-protect operation is detected, the electronic device may cause at least a portion of the content of the UI to be displayed normally. In some embodiments, the electronic device may further determine a target area indicated by a position where the unprotection operation occurred in the UI and cause the target area to be displayed normally, in the case where the unprotection operation is detected. For example, in a case where the unprotection operation is a click operation and the UI includes at least one window, a target window of the at least one window in which the click operation has occurred may be determined as the target area. For example, as shown in fig. 6D, in the event that the user has clicked on the floating window 620, the electronic device may determine the floating window 620 as a target area to resume normal display, thereby causing the floating window 620 to become legible again while continuing to keep other portions of the UI obscured.

Furthermore, in some embodiments, the electronic device may also verify the identity of the user initiating the unprotection operation (e.g., verification of a password, fingerprint, face, etc.) if the unprotection operation is detected. If the identity verification is successful, the electronic device can cause the target area to be displayed normally.

7A-7E illustrate schematic diagrams of a fifth example of UIs 700A-700E associated with interface protection operations, according to some embodiments of the present disclosure. In particular, in the examples of FIGS. 7A-7E, a multi-floating window scenario is shown.

As shown in fig. 7A, the UI interface includes an interface protection control 710, a floating window 720, a floating window 730, and other background portions. The electronic device may detect an interface protection operation associated with the UI. For example, the electronic device can monitor whether the user has triggered any suitable action, such as interface protection control 710, a particular voice command, and so forth. If an interface protection operation is detected, the electronic device may cause at least a portion of the content of the UI to not be displayed normally. For example, as shown in FIG. 7B, the user wants to protect at least a portion of the content of the UI and clicks on the interface protection control 710. When the user clicks on the interface protection control 710, at least a portion of the contents of the UI are obscured, as shown in FIG. 7C. In this case, for example, when the user is on a public transportation means such as a subway, other people cannot see the contents of the UI, thereby achieving information protection. It should be understood that while all of the contents of the UI are shown obscured in fig. 7C, only a portion of the contents of the UI may be obscured, such as obscuring only the floating

windows

720 and 730. In some embodiments, the protected content is settable by the electronic device or by a user.

Further, after causing at least a portion of the content of the UI to enter a protected state, the electronic device may also detect an unprotection operation acting on the UI. If an un-protect operation is detected, the electronic device may cause at least a portion of the content of the UI to be displayed normally. In some embodiments, the electronic device may further determine a target area indicated by a position where the unprotection operation occurred in the UI and cause the target area to be displayed normally, in the case where the unprotection operation is detected. For example, in a case where the unprotection operation is a click operation and the UI includes at least one window, a target window of the at least one window in which the click operation has occurred may be determined as the target area. For example, as shown in fig. 7D, in the event that the user has clicked on the floating window 720, the electronic device may determine the floating window 720 as the target area to resume normal display, thereby causing the floating window 720 to become legible again while continuing to keep other portions of the UI obscured. As another example, in the event that the user clicks on the floating window 730, the electronic device can determine the floating window 730 as the target area to resume normal display, thereby making the floating window 730 re-clear while continuing to keep other portions of the UI obscured.

8A-8E illustrate schematic diagrams of a sixth example of UIs 800A-800E associated with interface protection operations, according to some embodiments of the present disclosure. In particular, in the example of FIGS. 8A-8E, a split screen scenario is shown.

As shown in fig. 8A, the UI interface includes an interface protection control 810, a split screen window 820, a split screen window 830, and other background portions. The electronic device may detect an interface protection operation associated with the UI. For example, the electronic device can monitor whether the user has triggered any suitable action, such as interface protection control 810, a particular voice command, and so forth. If an interface protection operation is detected, the electronic device may cause at least a portion of the content of the UI to not be displayed normally. For example, as shown in FIG. 8B, the user wants to protect at least a portion of the content of the UI and has clicked on the interface protection control 810. When the user clicks on the interface protection control 810, at least a portion of the contents of the UI are obscured, as shown in fig. 8C. In this case, for example, when the user is on a public transportation means such as a subway, other people cannot see the contents of the UI, thereby achieving information protection. It should be understood that while all of the contents of the UI are shown obscured in fig. 8C, only a portion of the contents of the UI may be obscured, such as only obscuring the

split screen windows

820 and 830. In some embodiments, the protected content is settable by the electronic device or by a user.

Further, after causing at least a portion of the content of the UI to enter a protected state, the electronic device may also detect a unprotection operation acting on the UI. If an un-protect operation is detected, the electronic device may cause at least a portion of the content of the UI to be displayed normally. In some embodiments, the electronic device may further determine a target area indicated by a position where the unprotection operation occurred in the UI and cause the target area to be displayed normally, in the case where the unprotection operation is detected. For example, in a case where the unprotection operation is a click operation and the UI includes at least one window, a target window of the at least one window in which the click operation has occurred may be determined as the target area. For example, as shown in fig. 8D, in the event that the user has clicked on the split-screen window 820, the electronic device may determine the split-screen window 820 as the target area to resume normal display, thereby causing the split-screen window 820 to become legible again while continuing to keep other portions of the UI obscured. As another example, in the event that the user clicks on the split screen window 830, the electronic device may determine the split screen window 830 as a target area to resume normal display, thereby causing the split screen window 830 to become legible again while continuing to keep other portions of the UI obscured.

Furthermore, in some embodiments, the electronic device may also verify the identity of the user initiating the unprotection operation (e.g., verification of a password, fingerprint, face, etc.) if the unprotection operation is detected. If the authentication is successful, the electronic device can cause the target area to be displayed normally.

9A-9E illustrate schematic diagrams of a seventh example of UIs 900A-900E associated with interface protection operations, according to some embodiments of the present disclosure. In particular, in the example of FIGS. 9A-9E, a parallel view scene is shown.

As shown in fig. 9A, the UI includes interface protection controls 910, a parallel view window 920, a parallel view window 930, and other background portions. The electronic device may detect an interface protection operation associated with the UI. For example, the electronic device may monitor whether the user has triggered any suitable action, such as interface protection control 910, a particular voice command, and so forth. If an interface protection operation is detected, the electronic device may cause at least a portion of the content of the UI to not be displayed normally. For example, as shown in FIG. 9B, the user wants to protect at least a portion of the content of the UI and clicks on the interface protection control 910. When the user clicks on the interface protection control 910, at least a portion of the contents of the UI are obscured, as shown in FIG. 9C. In this case, for example, when the user is on a public transportation such as a subway, other people cannot see the contents of the UI, thereby achieving information protection. It should be understood that while all of the contents of the UI are shown obscured in fig. 9C, only a portion of the contents of the UI may be obscured, such as obscuring only

parallel view windows

920 and 930. In some embodiments, the protected content is settable by the electronic device or by a user.

Further, after causing at least a portion of the content of the UI to enter a protected state, the electronic device may also detect a unprotection operation acting on the UI. If an un-protect operation is detected, the electronic device may cause at least a portion of the content of the UI to be displayed normally. In some embodiments, the electronic device may further determine a target area indicated by a position where the unprotection operation occurred in the UI and cause the target area to be displayed normally, in the case where the unprotection operation is detected. For example, in a case where the unprotection operation is a click operation and the UI includes at least one window, a target window of the at least one window in which the click operation has occurred may be determined as the target area. For example, as shown in fig. 9D, in the event that the user has clicked on the parallel view window 920, the electronic device may determine the parallel view window 920 as the target area to resume normal display, thereby causing the parallel view window 920 to become clearer again while continuing to keep other portions of the UI obscured. As another example, where the user has clicked on the parallel view window 930, the electronic device may determine the parallel view window 930 as a target region to resume normal display, thereby causing the parallel view window 930 to become clearer again while continuing to keep other portions of the UI obscured.

10A-10E illustrate schematic diagrams of an eighth example of a UI 1000A-1000E associated with an interface protection operation, according to some embodiments of the disclosure. In particular, in the example of FIGS. 10A-10E, a partial content display scenario is shown.

As shown in FIG. 10A, the UI includes an interface protection control 1010 and various other UI elements. The electronic device may detect an interface protection operation associated with the UI. For example, the electronic device may monitor whether the user has triggered any suitable action, such as interface protection control 1010, a particular voice command, and so forth. If an interface protection operation is detected, the electronic device may cause at least a portion of the content of the UI to not be displayed normally. For example, as shown in FIG. 10B, the user wants to protect at least a portion of the content of the UI and clicks on interface protection control 1010. When the user clicks on the interface protection control 1010, at least a portion of the contents of the UI are obscured, as shown in fig. 10C. In this case, for example, when the user is on a public transportation such as a subway, other people cannot see the contents of the UI, thereby achieving information protection. It should be understood that while all of the contents of the UI are shown obscured in fig. 10C, only a portion of the contents of the UI may be obscured, such as only the controls associated with situational intelligence and the controls associated with parking. In some embodiments, the protected content is settable by the electronic device or by a user.

Further, after causing at least a portion of the content of the UI to enter a protected state, the electronic device may also detect an unprotection operation acting on the UI. If an un-protect operation is detected, the electronic device may cause at least a portion of the content of the UI to be displayed normally. In some embodiments, the electronic device may further determine a target area indicated by a position where the unprotection operation occurred in the UI and cause the target area to be displayed normally, in the case where the unprotection operation is detected.

In some embodiments, in a case where the unprotection operation is the region-drawing operation, the electronic device may determine a portion of the UI surrounded by the region-drawing operation as the target region. For example, as shown in FIG. 10D, the user may circle the target area 1020 on the screen with a finger, thereby causing the target area 1020 to become clearer again while continuing to keep other portions of the UI obscured.

Alternatively, in a case where the deprotection operation is a slide-wipe operation, the electronic device may determine a portion of the UI where the slide-wipe operation occurs as the target region. For example, as shown in FIG. 10E, the user may wipe the target area 1030 out of the screen with a finger, thereby causing the target area 1030 to become clearer again while continuing to keep other portions of the UI obscured.

It should be understood that the target area 1020 is merely an example, and in fact, the user may circle any suitable area with a regular or irregular shape on the screen with a finger, and may wipe any suitable area with a regular or irregular shape.

In the above, an example scenario of information protection is described in detail. Hereinafter, a flowchart of a graphical interface display method 1100 according to an embodiment of the present disclosure will be further described with reference to fig. 11. It should be understood that method 1100 may be performed by electronic device 100 described above with reference to fig. 1 or electronic device 200 described with reference to fig. 2. The method 1100 is described herein with reference to the UIs 300A-1000E of FIGS. 3A-10E. However, it should be understood that UIs 300A-1000E are merely examples, and method 1100 may be applicable to any suitable interface, including but not limited to UIs 300A-1000E.

At block 1110, a user interface UI is displayed on a screen of the electronic device. At block 1120, the electronic device detects a protection operation associated with the UI. At block 1130, in response to detecting the protection operation, the electronic device causes content associated with at least a portion of the UI to not be displayed normally on the screen. In this way, user information can be protected so that the user information cannot be viewed by an unauthorized user, thereby enhancing the security of the electronic device and significantly improving the user experience.

In some implementations, the protection operation includes: and performing element protection operation for protecting a UI element in the UI, wherein the element protection operation prevents the content associated with the UI element from being normally displayed, or performing interface protection operation for protecting the UI, and the interface protection operation prevents at least part of the content of the UI from being normally displayed. In this way, user information can be protected at the granularity of the UI or UI elements in the UI, thereby enhancing the security of the electronic device and significantly improving the user experience.

In some implementations, the protection operation is the element protection operation, and causing the content to be displayed normally includes: determining a target UI element corresponding to the element protection operation based on the element protection operation; and causing the content associated with the target UI element to not be displayed normally. In this way, the target UI element can be easily determined and protected, thereby enhancing flexibility of information protection and improving user experience.

In some implementations, disabling normal display of the content associated with the target UI element includes: blurring the content. Obfuscating the content may include obfuscating content displayed by the target UI element itself and/or obfuscating content accessed via the target UI element. In this way, an unauthorized user is prevented from clearly viewing the content that the user desires to protect.

In some implementations, disabling normal display of the content associated with the target UI element includes: preventing access to the content via the target UI element. In this way, unauthorized users are prevented from accessing content that the user desires to protect.

In some implementations, the unprotect operation is a region-drawing operation, and determining the target region includes: and determining the part enclosed by the region drawing operation in the UI as the target region. In this way, the protection of the portion in the circle can be released, so that the user can easily view the content he desires through the region drawing operation.

In some implementations, the unprotection operation is a swipe operation, and determining the target area includes: and determining a part of the UI where the sliding wiping operation occurs as the target area. In this way, the protection of the wiped portion can be released, so that the user can easily view the content he desires through the wiping operation.

The system architecture, local clearing architecture and physical elements to implement the graphical interface display proposed by embodiments of the present disclosure are described below.

Fig. 12 shows a schematic diagram of a system architecture 1200 according to an embodiment of the present disclosure. At the hardware layer 1210, the display device and the touch device receive the gesture event, trigger an interrupt, and notify the display driver and the touch driver of the kernel layer 1220 to obtain gesture data. At the kernel layer 1220, the display driver and the touch driver receive interrupts, obtain gesture data, and convert the gesture data into gesture events to be posted to the hardware abstraction layer 1230, so that the hardware abstraction layer 1230 posts the gesture events to the framework layer 1240. Framework layer 1240 includes protection services 1245. Protection services 1245 are used to implement the graphical interface display proposed by embodiments of the present disclosure to implement information protection.

In an element protection operation, protection service 1245 monitors gesture events, triggers protection functions, and displays element protection controls. Protection services 1245 monitor the selection operation and determine the type of protection. The protection types include control protection and layout protection, as described above with reference to FIGS. 3A-5P. The protection service 1245 protects the control or layout, for example, obfuscating the content of the control or layout, or graying out the control so that the content is not accessible via the control. Further, the protection service 1245 monitors the unprotection operation and invokes an authentication interface (e.g., password, fingerprint, face, etc.). In the case where the user inputs authentication information and the authentication is successful, the protection service 1245 causes the content entered in the protected state to be normally displayed.

Further, in interface protection operations, the protection service 1245 monitors gesture events, triggers protection functions, and protects the UI, e.g., obfuscates all of the contents of the UI. Further, the protection service 1245 monitors the unprotection operation and determines the type of unprotection operation. Types of unprotection operations include clicking, area drawing, swipe wiping, and the like, as described above with reference to fig. 6A-10E. In addition, protection services 1245 determine the multi-window type. The multi-window types include single floating window, multi-floating window, split screen, parallel view, etc., as described above with reference to fig. 6A-10E. After determining the particular multi-window type, the protection service 1245 determines the multi-window location, matches the gesture focus with the multi-window location, and causes the matched window to be displayed normally. Alternatively, the protection service 1245 determines a gesture drawing area or a gesture swipe area, and causes the determined area to be displayed normally.

Fig. 13 shows a schematic diagram of a partial sharpening architecture 1300 according to an embodiment of the disclosure. As shown in fig. 13, at block 1310, the electronic device detects a trigger interface protection control and obtains a UI screenshot. At block 1320, the electronic device invokes the canvas. At block 1330, the electronic device displays the protected UI. The electronic device monitors for gesture events. Where a region drawing gesture is detected, the path. And in the event that a swipe wipe gesture is detected, the paint. At block 1360, the electronic device invokes the onDraw function to draw the locally clarified UI. Thus, at block 1370, the electronic device displays the locally-clarified UI.

Fig. 14 shows a schematic diagram 1400 of physical elements according to an embodiment of the disclosure. As shown in fig. 14, embodiments of the present disclosure relate to physical elements including a processor 1440 (e.g., a CPU, or GPU, etc.), a display device 1430 (e.g., an LCD display, an LED display, or a CRT display, etc.), and a touch device 1420. The user can control the display device to safely display information by displaying a UI on a screen of the electronic device and operating various UI elements (e.g., windows, controls, or the like) in the UI.

Claims

1. A graphical interface display method, comprising:

displaying a User Interface (UI) on a screen of an electronic device;

detecting a protection operation associated with the UI; and

in response to detecting the protection operation, causing content associated with at least a portion of the UI to not be displayed normally on the screen.

2. The method of claim 1, wherein content associated with at least a portion of the UI comprises at least one of:

content displayed by at least a portion of the UI, and

content accessed via at least a portion of the UI.

3. The method of claim 1 or 2, wherein the protection operation comprises:

an element protection operation to protect a UI element in the UI, the element protection operation disabling normal display of content associated with the UI element, or

And performing interface protection operation for protecting the UI, wherein the interface protection operation prevents all contents of the UI from being normally displayed.

4. The method of claim 3, wherein the protection operation is the element protection operation, and disabling normal display of the content comprises:

determining a target UI element corresponding to the element protection operation based on the element protection operation; and

disabling normal display of the content associated with the target UI element.

5. The method of claim 4, wherein the element protection operation comprises a control display operation and a selection operation, and the determining a target UI element corresponding to the element protection operation based on the element protection operation comprises:

displaying an element protection control corresponding to at least one UI element included in the UI on the screen based on the control display operation; and

and determining the UI element corresponding to the element protection control acted by the selection operation as the target UI element based on the selection operation.

6. The method of claim 4 or 5, wherein disabling normal display of the content associated with the target UI element comprises:

determining a mode to protect the target UI element, the mode indicating at least one of:

obfuscating the content, an

Preventing access to the content via the target UI element; and

disabling normal display of the content associated with the target UI element based on the pattern.

7. The method of claim 4 or 5, wherein disabling normal display of the content associated with the target UI element comprises:

blurring the content.

8. The method of claim 4 or 5, wherein disabling normal display of the content associated with the target UI element comprises:

preventing access to the content via the target UI element.

9. The method of any of claims 4-8, wherein the protection operation is the element protection operation, and the method further comprises:

detecting an unprotection operation on the target UI element; and

in response to detecting the unprotection operation, causing the content associated with the target UI element to be displayed normally.

10. The method of claim 9, wherein causing the content associated with the target UI element to be normally displayed comprises:

verifying the identity of the user initiating the unprotection operation; and

in response to the authentication being successful, causing the content associated with the target UI element to be displayed normally.

11. The method of claim 3, wherein the protection operation is the interface protection operation, and disabling normal display of the all content of the UI comprises:

obfuscating the all content of the UI.

12. The method of claim 3 or 11, wherein the protection operation is the interface protection operation, and the method further comprises:

detecting a unprotection operation acting on the UI;

in response to detecting the unprotection operation, determining a target area in the UI indicated by a location where the unprotection operation occurred; and

and enabling the target area to be displayed normally.

13. The method of claim 12, wherein the unprotection operation is a click operation, the UI comprises at least one window, and determining the target region comprises:

and determining a target window in the at least one window where the click operation occurs as the target area.

14. The method of claim 12, wherein the unprotect operation is a region-drawing operation, and determining the target region comprises:

and determining the part enclosed by the region drawing operation in the UI as the target region.

15. The method of claim 12, wherein the unprotection operation is a swipe operation, and determining the target region comprises:

determining a portion of the UI where the swipe operation occurs as the target area.

16. An electronic device, comprising: a processor, and a memory storing instructions that, when executed by the processor, cause the electronic device to perform the method of any of claims 1-15.

17. A computer-readable storage medium having stored thereon instructions that, when executed by an electronic device, cause the electronic device to perform the method of any one of claims 1-15.

18. A computer program product, characterized in that the computer program product comprises instructions which, when executed by an electronic device, cause the electronic device to perform the method according to any of claims 1 to 15.