Interface display method, electronic device and computer readable storage medium

Abstract

This application relates to the field of electronic technology, providing an interface display method, an electronic device, and a computer-readable storage medium. The method includes: detecting that a Media Projection Manager interface is called for the first time by a first application; when the electronic device's call mode is in VoIP mode, displaying a first interface, the first interface including a first prompt message and a first notification message, the first prompt message indicating that the first notification message is not displayed on the other end; when the electronic device's call mode is in VoIP mode and a first factor exists, displaying a second interface, the second interface including a second prompt message, the second prompt message indicating that the second interface is not displayed on the other end; detecting that the Media Projection Manager interface is not called for the first time by a second application, and when the electronic device's call mode is in other modes, displaying a third interface. This method can prevent the leakage of privacy information.

Description

Technical Field

[0001] This application relates to the field of Internet technology, specifically to an interface display method, an electronic device, and a computer-readable storage medium. Background Technology

[0002] With the rapid development of internet technology, the convenience it brings to people is undeniable. However, the various risks brought by the internet are also attracting increasing attention.

[0003] Many criminals often use the internet to steal users' private information and thus steal their property. Summary of the Invention

[0004] This application provides an interface display method, apparatus, chip, electronic device, computer-readable storage medium, and computer program product that can protect users' privacy information, thereby ensuring the security of users' information and property.

[0005] Firstly, a method for displaying an interface is provided, applied to an electronic device, comprising: detecting that the Media Projection Manager interface is called for the first time by a first application; when the electronic device's call mode is in VoIP (Voice over Internet Protocol) mode, displaying a first interface, the first interface including a first prompt message and a notification message, the first prompt message indicating that the notification message is not displayed on the other end; when the electronic device's call mode is in VoIP mode and a first factor exists, displaying a second interface, the second interface including a second prompt message, the second prompt message indicating that the second interface is not displayed on the other end, the first factor indicating that the electronic device is at risk of fraud; detecting that the Media Projection Manager interface is called by a second application for the second time, when the electronic device's call mode is in other modes, displaying a third interface, the third interface not including the first and second prompt messages, the other call modes being different from both VoIP mode and carrier call mode.

[0006] This Media Projection Manager interface is for Media Projection Manager. When the Media Projection Manager interface is invoked, the terminal device may be in screen recording or screen sharing mode. We believe that screen recording is a safe scenario and can operate normally without requiring protection; however, screen sharing poses a risk of privacy information leakage and requires appropriate protection.

[0007] If the package name of the first application does not exist in the historical call record, meaning the first application is calling the MediaProjection Manager interface for the first time, and the electronic device is currently in VoIP mode, it indicates that screen sharing is in progress, posing a risk of privacy leakage. The terminal device can then perform corresponding protection operations.

[0008] Specifically, the terminal device can choose not to display the notification message content to the other end during the display process. In other words, the other end will not see the notification message popped up on this end, preventing the other end from seeing the notification message and protecting the user's privacy. At the same time, the interface displayed on this end is the first interface containing the initial prompt information. Users can know from this prompt information that the other end will not see the notification message popped up on this end, eliminating concerns about privacy leaks and improving the user experience.

[0009] If the local device still detects the presence of the first factor (i.e., the fraud risk factor mentioned later), or if the fraud risk value is a value representing a fraudulent scenario, then it indicates that the local device faces a fraud risk. The terminal device will not send any content from its second interface to the other end, ensuring that the other end cannot see any content displayed on the local device's second interface. This comprehensively protects the user's privacy information, prevents its leakage, and thus ensures the user's financial security. Simultaneously, the local device can also display a second prompt message on the second interface, allowing the user to know that the other party will not see any content on the local device's second interface, eliminating concerns about privacy leaks and improving the user experience.

[0010] If the terminal device detects that the Media Projection Manager interface has been called by a second application before, and the electronic device is in another call mode, the likelihood of the terminal device entering screen sharing mode is low; it is more likely to be in screen recording mode. Therefore, the terminal device does not need to perform any protection operations and can call the Media Projection Manager interface normally. The local device also does not need to display the first or second prompt messages.

[0011] It should be noted that the electronic device's call mode can be simply referred to as call mode, and will not be elaborated further in the following text.

[0012] In some possible implementations, the method also includes: after detecting that the Media Projection Manager interface is called by a third application for the first time; when the electronic device enters VoIP mode, displaying the first interface; when the electronic device enters VoIP mode and the first factor exists, displaying the second interface; wherein the package name of the third application exists in the preset screen sharing application whitelist.

[0013] When the Media Projection Manager interface is in the calling state, the package name of the third application that calls the Media Projection Manager interface exists in the historical call record, that is, the third application is not calling the Media Projection Manager interface for the first time.

[0014] The aforementioned preset screen-sharing application whitelist includes the package names of several applications with screen-sharing functionality. If the third-party application's package name is present in this whitelist, and the terminal device first detects that the MediaProjection Manager interface is being called by a third-party application, and then detects that the call mode has switched to VoIP mode, it indicates a high probability that screen sharing has been initiated. The terminal device can then perform corresponding protection operations, such as not sending notification messages to the other end, and not sending any content to the other end if there is a risk of fraud. This prevents the leakage of privacy information and comprehensively protects the user's information and property security.

[0015] In some possible implementations, the method also includes: detecting that the Media Projection Manager interface is called by a fourth application before its first call; displaying a third interface when the electronic device enters VoIP mode; wherein the third application is different from the fourth application, and the package name of the fourth application is not in the preset screen sharing application whitelist.

[0016] If the package name of the fourth application is not in the preset screen sharing application whitelist, it means that the fourth application most likely does not have screen sharing functionality. If the terminal device first detects that the Media Projection Manager interface has been called by the fourth application before, and then detects that the electronic device has entered VoIP mode, the likelihood of the terminal device entering screen sharing mode is even lower; it is more likely to be in screen recording mode. Therefore, the terminal device does not need to perform any protection operations and can call the Media Projection Manager interface normally. The local device also does not need to display the first or second prompt messages.

[0017] In some possible implementations, the method also includes: after the electronic device enters the operator's call mode; when it is detected that the Media Projection Manager interface is called by the fifth application for the first time, the first interface is displayed; when it is detected that the Media Projection Manager interface is called by the fifth application for the first time and the first factor exists, the second interface is displayed; wherein, the package name of the fifth application exists in the preset screen sharing application whitelist.

[0018] If the package name of the fifth application exists in the preset screen sharing application whitelist, it indicates that the fifth application has screen sharing functionality. If the terminal device first detects that the call mode has entered the carrier's "fairy mode," and then detects that the MediaProjection Manager interface has been called by the fifth application before its first time, then the terminal device is likely to enter screen sharing mode. Therefore, the terminal device can perform corresponding protection operations. For details on the execution method and technical effects of these protection operations, please refer to the relevant descriptions in this document; they will not be repeated here.

[0019] In some possible implementations, the method also includes: after the electronic device enters the carrier call mode; when it is detected that the Media Projection Manager interface is called by the sixth application for the first time, the third interface is displayed; wherein the package name of the sixth application is not in the preset screen sharing application whitelist.

[0020] If the package name of the sixth application is not in the preset screen sharing application whitelist, it indicates that the sixth application may not have screen sharing functionality. If the terminal device first detects that the call mode has entered carrier-controlled mode, and then detects that the Media Projection Manager interface has been called by the sixth application before, then the terminal device is likely to enter screen recording mode. Therefore, the terminal device does not need to perform any protection operations and can call the Media Projection Manager interface normally. The local device also does not need to display the first or second prompt messages.

[0021] In some possible implementations, the method also includes: when the first interface is displayed, adding the notification layer corresponding to the notification message to the privacy layer; generating a first virtual screen interface based on other layers besides the privacy layer; and sending the first virtual screen interface to the other end.

[0022] Specifically, one way to hide notification messages is to add the corresponding notification layer to a privacy layer. During the transmission of the notification to the other end, the content in the privacy layer will not appear in the first virtual screen interface. In other words, when the terminal device transmits the notification to the other end, the privacy layer window will not be overlaid when compositing the first virtual screen interface. Therefore, when transmitting the notification to the other end based on this first virtual screen interface, the other end will not display the privacy layer window, preventing the leakage of the privacy layer's content.

[0023] In some possible implementations, the notification layer corresponding to the notification message is added to the privacy layer, including adding a privacy label to the notification layer to make the notification layer added to the privacy layer.

[0024] Specifically, adding a notification layer to a privacy layer involves adding a privacy tag to the notification layer, thus marking the layer that needs to be hidden. Alternatively, adding a privacy tag can be done by setting a privacy flag on the notification layer, thereby adding the notification layer to the privacy layer and preventing the content of the notification layer from being sent to the other end.

[0025] Among some possible implementations, the method also includes: detecting that the Media Projection Manager interface is not being called; removing the privacy label from the notification layer and displaying a third interface.

[0026] If the terminal device detects that the Media Projection Manager interface is not being called, meaning Media Projection Manager has stopped collecting screen data, then the screen sharing state has ended. The terminal device can then remove the notification layer from the privacy layer, that is, remove the privacy label from the notification layer. At this point, since there is no risk of privacy information leakage, the third-party interface on this device will not display the first and second prompt messages. If the privacy label is not removed in time, when the terminal device enters screen recording mode again, the recorded video file will not contain the notification message due to the unremoved privacy label, resulting in incomplete information in the screen recording video file, which may affect user experience. Therefore, timely removal of the privacy label from the notification layer can avoid incomplete information acquisition in scenarios such as screen recording.

[0027] In some possible implementations, the method also includes: when the second interface is displayed, adding the second interface to a security layer; generating a second virtual screen interface based on the security layer; sending the second virtual screen interface to the other end for display; the second virtual screen interface is a black interface.

[0028] Specifically, one way to prevent the content of the second interface from being displayed on the other end is to add a security layer to the second interface. During the transmission of the display to the other end, the interface with the security layer will not be displayed on the other end. In other words, when the terminal device transmits the display to the other end, it will not overlay any windows of the second interface when compositing the second virtual screen interface, but will instead generate a completely black or completely blurred second virtual screen interface. Therefore, when the display is transmitted to the other end based on such a second virtual screen interface, the other end will not display any content from the second interface, thus preventing the leakage of privacy information.

[0029] In some possible implementations, a security layer is added to the second interface, including adding a security label to the second interface to enable the second interface to be included in the security layer.

[0030] Specifically, the second interface is added to the security layer by adding a security label to the second interface, thereby marking the interface that needs to be hidden. Optionally, adding a security label can be done by setting a security flag for the second interface, thereby adding the second interface to the security layer and preventing the content of the second interface from being sent to the other end.

[0031] Among some possible implementations, the method also includes: detecting that the Media Projection Manager interface is not being called; removing the security label of the security layer and displaying a third interface.

[0032] If the terminal device detects that the Media Projection Manager interface is not being called, meaning Media Projection Manager has stopped collecting screen data, then the screen sharing state has ended. The terminal device can then remove the second interface from the security layer, i.e., remove the security label from the second interface. At this point, since there is no risk of privacy information leakage, the third interface on this device will not display the first and second prompt messages. If the security label is not removed in time, when the terminal device enters screen recording mode again, a completely black video file may be recorded due to the security label not being removed, affecting user experience. Therefore, timely removal of the security label from the second interface can prevent situations where screen information cannot be obtained in screen recording and other scenarios.

[0033] In a second aspect, an interface display device is provided, comprising a unit composed of software and / or hardware, the unit being used to perform any one of the methods described in the first aspect.

[0034] Thirdly, embodiments of this application provide a chip including a processor; the processor is used to read and execute a computer program stored in a memory to perform any one of the methods described in the first aspect.

[0035] Optionally, the chip further includes a memory, which is connected to the processor via a circuit or wire.

[0036] Alternatively, the chip may further include a communication interface.

[0037] Fourthly, an electronic device is provided, comprising: a processor, a memory, and an interface; the processor, memory, and interface cooperate with each other to enable the electronic device to perform any one of the methods described in the first aspect.

[0038] Fifthly, a computer-readable storage medium is provided, wherein a computer program is stored therein, and when the computer program is executed by a processor, the processor performs any one of the methods described in the first aspect.

[0039] In a sixth aspect, a computer program product is provided, the computer program product comprising: computer program code, which, when executed on an electronic device, causes the electronic device to perform any one of the methods described in the first aspect. Attached Figure Description

[0040] Figure 1 This is a scene diagram illustrating screen sharing provided in an embodiment of this application;

[0041] Figure 2 This is a schematic diagram of the structure of a terminal device 100 provided in an embodiment of this application;

[0042] Figure 3 This is a software structure block diagram of the terminal device 100 provided in the embodiments of this application;

[0043] Figure 4 This is a flowchart of an example protection operation provided in an embodiment of this application;

[0044] Figure 5 This is a schematic diagram of the interface between the local end and the remote end in the case of an example of a protection notification message provided in an embodiment of this application;

[0045] Figure 6 This is a schematic diagram of the interface between the local end and the remote end in the case of another protection notification message provided in the embodiments of this application;

[0046] Figure 7 This is a flowchart of another protection operation provided in the embodiments of this application;

[0047] Figure 8 This is a schematic diagram of an interface with potential fraud risk provided in an embodiment of this application;

[0048] Figure 9 This is another example of the interface diagram between the local end and the remote end when there is a risk of fraud, provided by the embodiments of this application;

[0049] Figure 10 This is an interactive diagram of an example interface display method provided in an embodiment of this application;

[0050] Figure 11 This is a flowchart of an example interface display method provided in an embodiment of this application. Detailed Implementation

[0051] To clearly describe the technical solution of this application, the terms used in this application are explained below:

[0052] Screen data capture status: Under the Android mechanism, screen data capture requires calling the MediaProjectionManager service. Screen data captured through the MediaProjectionManager service can be used for video recording (screen recording) or screen sharing.

[0053] Screen sharing refers to a user using an application with screen sharing functionality to call the MediaProjectionManager service to share collected screen data in real time to a peer, allowing the peer to view the content displayed on their screen. When a user uses a terminal device to share their screen, the screen state of the terminal device can be referred to as screen sharing state.

[0054] Screen recording refers to calling the MediaProjectionManager service to collect screen data, generate a video file, and save it. When a user records their screen using a terminal device, the screen state of the terminal device can be referred to as the screen recording state.

[0055] Call modes include: MODE_IN_COMMUNICATION (VoIP mode), MODE_IN_CALL mode (carrier call mode), MODE_INVALID (no call mode), MODE_NORMAL (normal call mode), MODE_RINGTONE (ringtone mode), and MODE_CALL_SCREENING (call display mode).

[0056] VoIP mode is a voice over Internet Protocol (IP) transmission mode. In VoIP mode, AudioManager can be set to MODE_IN_COMMUNICATION. Therefore, when AudioManager is set to MODE_IN_COMMUNICATION, it can be determined that the current call mode is VoIP mode.

[0057] Privacy risk: This indicates that the screen is being shared, posing a risk of privacy information leakage.

[0058] Fraud risk: This indicates that there is fraudulent activity or that you are in a fraudulent situation.

[0059] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in this text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0060] Hereinafter, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include one or more of that feature.

[0061] With the rapid development of internet technology, the convenience it brings to people is undeniable. However, the various risks brought by the internet are also increasingly attracting attention. Many criminals frequently use the internet to steal users' private information. For example, some criminals induce users to download and install applications with screen-sharing functions, such as meeting apps and chat apps. They then use these installed applications to share their screens with the users. Figure 1 As shown, if a notification message pops up during screen sharing, such as an SMS verification code or a message from a received email containing sensitive information (or privacy information), there is a risk of sensitive information being leaked.

[0062] The interface display method provided in this application embodiment, by monitoring the screen status, allows the terminal device (which may be referred to as the local device) to identify when the local device is in a screen sharing state, for example... Figure 1 In the scenario shown, pop-up notifications can be blocked during the screen sharing process. This means the terminal device won't send pop-up notifications to the other end, preventing sensitive information like notifications from being seen during screen sharing and thus avoiding data leakage. If the terminal device also detects a potential fraud risk, it can add a security layer to the shared interface before displaying it, preventing the other user from seeing the content and further enhancing information and asset security during screen sharing.

[0063] The interface display method provided in this application can be applied to terminal devices such as mobile phones, tablets, wearable devices, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs). This application does not impose any restrictions on the specific type of terminal device.

[0064] For example, Figure 2 This is a schematic diagram of the structure of a terminal device 100 provided in an embodiment of this application. The terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0065] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the terminal device 100. In other embodiments of this application, the terminal device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0066] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the terminal device 100. In other embodiments of this application, the terminal device 100 may also adopt different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.

[0067] The software system of terminal device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses the layered architecture Android system as an example to exemplify the software structure of terminal device 100.

[0068] Figure 3 This is a software structure block diagram of the terminal device 100 according to an embodiment of this application. The layered architecture divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer. The application layer may include a series of application packages.

[0069] like Figure 3 As shown, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and SMS.

[0070] The application package may also include a system manager, which is used for scheduling and management of the system.

[0071] The system manager includes a security center for managing system security. Specifically, the security center includes a fraud risk monitoring module and a screen sharing status monitoring module.

[0072] The fraud risk monitoring module is used to identify fraud-related scenarios.

[0073] The screen sharing status monitoring module is used to monitor whether the terminal device is currently in screen sharing mode.

[0074] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0075] like Figure 3 As shown, the application framework layer may include a Window Manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, a media projection manager, and a surface compositor, etc.

[0076] The window manager is used to manage window programs. It can obtain the screen size, determine the presence of a status bar, lock the screen, and capture the screen. The window manager is also used to add notification messages to a privacy layer when the screen sharing state monitoring module detects a screen sharing state, and to set a security layer and send the security layer information to the display compositor when the fraud risk monitoring module detects a fraudulent scenario.

[0077] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0078] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0079] The phone manager is used to provide communication functions for terminal device 100. For example, it manages call status (including connection, hang-up, etc.).

[0080] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0081] Media Projection Manager can be configured with an extended interface, Media Projection Manager Interface, also known as MediaProjectionManagerEX. Terminal devices can invoke the Media Projection Manager service by calling the Media Projection Manager Interface to capture screen data. In the native Android mechanism, the invocation of the Media Projection Manager Interface (or the invocation of Media Projection Manager) signifies that the terminal device is performing screen sharing and / or screen recording.

[0082] The Notification Manager allows applications to display notifications in the status bar. These notifications can be used to convey informational messages and can disappear automatically after a short pause, requiring no user interaction. Examples include notifications of download completion and message alerts. The Notification Manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog windows on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating the device, and flashing indicator lights. Furthermore, when the screen sharing state monitoring module detects screen sharing, the Notification Manager can send a command to the Window Manager to block notifications. The Window Manager then responds by setting a privacy flag on the notification message layer and sending this privacy flag setting information to the display compositor.

[0083] The display synthesizer can block notification messages when it receives information to set a privacy flag, that is, when sending the shared interface to the other end, it does not send the notification message layer; it can also stop sending the shared interface to the other end when it receives information to set a security layer, and instead generate a blurred security layer to send to the other end.

[0084] The Android runtime consists of core libraries and a virtual machine. The Android runtime is responsible for scheduling and managing the Android system.

[0085] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0086] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0087] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0088] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0089] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0090] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0091] A 2D graphics engine is a graphics engine for 2D drawing.

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

[0093] In the technical solution of this application, the terminal device can monitor the current screen status. If the current screen status is in a screen sharing state, the pop-up notification messages can be blocked when sending the display to the other end, and the current shared interface can be added to a security layer to prevent leakage. Next, let's combine the above... Figure 3 The software architecture framework shown illustrates how to identify screen sharing status.

[0094] When a terminal device is in screen sharing mode, it needs to call the Media Projection Manager interface. In this application, the screen sharing state listening module in the application layer registers a broadcast with the Media ProjectionManager in the application framework layer to listen for the call status of the Media Projection Manager interface. When screen data needs to be collected, the Media Projection Manager interface is in the called state. When the screen sharing state listening module detects that the Media Projection Manager interface has been called, it may be in screen sharing mode or screen recording mode. Generally, screen recording files are automatically saved locally on the terminal device after recording and will not be obtained by third parties unless actively shared by the user. Therefore, screen recording mode can be considered a safe use case. However, in screen sharing mode, third parties can obtain the information displayed on the shared screen, posing a privacy risk due to the leakage of privacy information. Therefore, when the Media Projection Manager interface is in the called state, it is necessary to distinguish between screen recording mode and screen sharing mode. If it is in screen recording mode, it can be determined as a safe scenario and no corresponding processing is required. If it is in screen sharing mode, a privacy risk is determined, and corresponding protection operations can be performed. The specific description of the protection operations can be found later and will not be repeated here.

[0095] It should be noted that when the Media Projection Manager interface is invoked, the terminal device can record the invocation information for each call, thereby forming a historical invocation record.

[0096] Next, we will describe how to distinguish between screen sharing and screen recording states when the Media Projection Manager interface is called. In screen sharing mode, users often need to communicate with meeting participants via voice, which requires entering VoIP mode. However, in screen recording mode, the call mode is not necessarily VoIP mode. Therefore, screen sharing and screen recording states can be distinguished based on the different call modes. Optionally, the screen sharing state monitoring module can obtain the current call mode by calling the AudioManager.getMode class.

[0097] Specifically, when the terminal device obtains the current call mode as AudioManager.MODE_IN_COMMUNICATION (i.e., VoIP mode), and the Media Projection Manager interface is in the called state, it can be directly determined that the current screen state is screen sharing state, rather than screen recording state.

[0098] Optionally, in some scenarios, such as game live streaming, screen recording is required simultaneously by calling the Media ProjectionManager interface, and the call mode will also switch to VoIP mode. However, in game live streaming, screen sharing is not performed, so there is no privacy risk. If the screen state in a game live streaming scenario is simply determined based on the call status of the Media ProjectionManager interface and the VoIP mode, it will be mistakenly identified as a screen sharing state. Based on this, embodiments of this application can define two judgment scenarios: a single scenario and a combined scenario.

[0099] Here we will introduce two judgment scenarios:

[0100] Single scenario: When the Media Projection Manager interface is in the called state, if the package name of the application currently calling the Media Projection Manager interface does not exist in the historical call record (that is, the application currently calling the Media Projection Manager interface is calling the Media Projection Manager interface for the first time), this can be determined as a single scenario.

[0101] Optionally, if the terminal device is powered on for the first time, the historical call record will be empty. In this case, regardless of which application calls the Media Projection Manager interface, the screen sharing state and screen recording state can be distinguished according to the judgment conditions of a single scenario.

[0102] In a single scenario, if the Media Projection Manager interface is in a called state and the call mode is VoIP mode, then it can be determined that the current screen state is screen sharing state, rather than screen recording state.

[0103] Combined scenario: When the Media Projection Manager interface is in the invoked state, the package name of the application currently calling the Media Projection Manager interface exists in the call history. That is to say, the application currently calling the Media Projection Manager interface has called the Media Projection Manager interface before, and this call is at least the second call (not the first call). This can be identified as a combined scenario.

[0104] In combined scenarios, when the screen sharing status monitoring module detects that the Media Projection Manager interface is in a called state, it can continue to determine the screen status based on the call status.

[0105] Combined scenarios can include the following four situations:

[0106] Scenario 1: When the screen sharing status monitoring module detects that the Media Projection Manager interface has entered the called state, and the call mode is already in carrier call mode (MODE_IN_CALL mode), it can determine whether the current screen state is screen sharing or screen recording by combining the preset screen sharing application whitelist. It should be noted that the preset screen sharing application whitelist includes the package names of several applications that support screen sharing functionality.

[0107] For example, when a terminal device makes or receives a call with another device, it is in carrier call mode. In this case, the screen sharing state monitoring module first calls AudioManager.getMode to obtain the current call mode as MODE_IN_CALL. If it also detects that the Media Projection Manager interface is in a called state, it considers there is a possibility of being in a screen sharing state. Alternatively, if the terminal device detects that the Media Projection Manager interface is in a called state, and also obtains the current call mode as MODE_IN_CALL, and the terminal device enters MODE_IN_CALL mode before the Media Projection Manager interface is detected as being called, it is also considered that there is a possibility of being in a screen sharing state.

[0108] When there is a possibility that the screen is in a shared state, the screen sharing state monitoring module can further distinguish the current screen state based on a preset screen sharing application whitelist:

[0109] If the package name of the application currently calling the Media Projection Manager interface exists in the preset screen sharing application whitelist, it means that the application supports screen sharing. Therefore, the current screen state is likely to be screen sharing mode, and the screen sharing state monitoring module can confirm that it is currently in screen sharing mode.

[0110] If the package name of the application currently calling the Media Projection Manager interface is not in the preset screen sharing application whitelist, it means that the application most likely does not support screen sharing. Therefore, the current screen state is likely screen recording, and can be confirmed as screen recording.

[0111] Optionally, if the package name of the application currently calling the Media ProjectionManager interface is not found in the preset screen sharing application whitelist, it can be further determined whether the application currently calling the Media ProjectionManager interface is the system's built-in screen recording software. If the application currently calling the Media ProjectionManager interface is the system's built-in screen recording software, it can be determined that the current screen state is a screen recording state, not a screen sharing state; if the application currently calling the Media ProjectionManager interface is not the system's built-in screen recording software, it can be determined that the current screen state is not a screen recording state, or other conditions can be combined to further distinguish the current screen state.

[0112] It should be noted that the preset screen-sharing application whitelist includes the package names of multiple pre-installed applications, all of which support screen sharing functionality. For example, the preset screen-sharing application whitelist may include the package names of currently mainstream applications with screen-sharing capabilities, as well as the package names of user-added applications with screen-sharing functionality. Optionally, the preset screen-sharing application whitelist may be downloaded from the cloud or automatically generated based on application usage records and attributes; this application does not impose any limitations on this.

[0113] Scenario 2: When the screen sharing status monitoring module detects that the Media Projection Manager interface is in a called state, the call mode is a non-carrier call mode, and it is a non-VoIP mode, it determines that the current screen state is screen recording state.

[0114] Call modes that are not carrier call modes and are not VoIP modes can be called other call modes.

[0115] For example, when the screen sharing status monitoring module calls the AudioManager.getMode class and finds that the call mode is any of the following: MODE_INVALID (no call mode), MODE_NORMAL (normal call mode), MODE_RINGTONE (ringtone mode), or MODE_CALL_SCREENING (call display mode), it indicates that the call mode is another call mode.

[0116] Scenario 3: If the screen sharing status monitoring module detects a call to the Media Projection Manager interface and then detects a transition from call mode to carrier call mode, the terminal device will stop calling the Media Projection Manager interface based on Android's resource allocation logic, thus stopping the current screen sharing or screen recording state. In this case, there is no privacy risk, and no further protection operations are required.

[0117] Scenario 4: If the screen sharing status monitoring module first detects that the Media Projection Manager interface is in a called state, and then detects that the call mode has entered VoIP mode, it can be determined that it is not in a screen sharing state based on the preset screen sharing application whitelist. Alternatively, if the terminal device detects that the Media Projection Manager interface is in a called state, and also obtains that the call mode is MODE_IN_CALL mode, and the terminal device enters VoIP mode before the time when the Media Projection Manager interface is detected as being called, it is also considered that there is a possibility of being in a screen sharing state, and it can be determined that it is not in a screen sharing state based on the preset screen sharing application whitelist.

[0118] For example, in a game live-streaming scenario, the Media Projection Manager interface is used for screen recording, while the call mode is switched to VoIP mode. However, this is not actually a screen sharing state, and there is no privacy risk. In this case, the current screen state can be further distinguished based on a preset whitelist of screen sharing applications.

[0119] Specifically, the screen sharing status monitoring module can check the applications currently calling the Media Projection Manager interface. If the application calling the Media Projection Manager interface is the system's built-in screen recording software, it can be determined that the application is currently in screen recording mode; if the application calling the Media Projection Manager interface is not the system's built-in screen recording software, it cannot be determined whether the application is in screen recording mode. When it is impossible to determine whether the application is in screen recording mode, the screen status can be further distinguished based on a preset screen sharing application whitelist. Specifically, if the package name of the application calling the Media Projection Manager interface is in the preset screen sharing application whitelist, it is determined that the application is currently in screen sharing mode; if the package name of the application calling the Media Projection Manager interface is not in the preset screen sharing application whitelist, then the application calling the Media Projection Manager interface is likely a third-party screen recording software, and it is determined that the application is currently in screen recording mode.

[0120] Once the terminal device determines the current screen state, it can update the historical call record as a call record. The historical call record can be stored in a mapping table according to a mapping relationship. For example, each call to the MediaProjection Manager interface can be expressed in the form of a key and a corresponding true value. The key indicates whether the MediaProjection Manager interface call is in screen recording or screen sharing mode, and the corresponding value indicates the package name of the application calling the MediaProjectionManager interface. For example, if a meeting app calls the MediaProjection Manager interface for screen sharing, it will generate a call record: Screen Sharing (key) - Meeting App (value).

[0121] Based on the above, the terminal device can distinguish whether the current screen state is in screen sharing or screen recording state when the Media Projection Manager interface is called. Since screen recording is a scenario without privacy risks, no subsequent protection operations need to be performed, and the current operation, such as normal screen recording, can continue. If the current screen state is screen sharing, it is considered to have privacy risks, and the terminal device can perform subsequent protection operations to prevent information leakage and fraud. Specific implementation methods for these protection operations can be found in the description below.

[0122] First, the terminal device can perform protection operations on the content of notification messages. When the terminal device calls the screen sharing status monitoring module to determine that the current screen state is screen sharing, it can add the notification message to a privacy layer to prevent the notification message from being leaked.

[0123] Secondly, when the terminal device calls the screen sharing status monitoring module to determine that the current screen status is screen sharing, if the terminal device determines that there is a risk of fraud on its end, it will add a security layer to the shared interface, so that the other end cannot see the shared screen, thus avoiding the risk of being defrauded.

[0124] To clearly describe how the above protection operations are implemented, the mechanism of sending the display from the local end to the remote end in screen sharing mode is explained here. Here, the local end is the generator of the shared interface, and the remote end is the receiver of the shared interface.

[0125] When a user opens an application on a terminal device, each running application can display a corresponding window, and each window displays unique window content. Each window content corresponds to a layer. When multiple application windows are displayed on the screen, the multiple windows may overlap, which can be understood as the overlapping of the layers corresponding to the windows. The layers of different windows are independent of each other, and the window content corresponding to each layer can be fully captured.

[0126] When the terminal device is in screen sharing mode, each application can pass its window content to the window manager. The window manager can then obtain information about each window currently displayed on the screen (e.g., identifier, size, coordinates) based on the window content. This allows the terminal device to dynamically obtain information about windows on different layers in a screen sharing scenario, ensuring that changes in window size and position are recorded.

[0127] In this application, layer overlay can be understood as the overlay of cached data corresponding to layers (also known as "buffer overlay"). In screen sharing scenarios, the terminal device overlays layers from multiple applications to generate a virtual screen interface. The terminal device can send the data of this virtual screen interface to the other end, and the other end can display the virtual screen interface upon receiving the data. This process is called terminal device sending display to the other end. Specifically, the terminal device can generate a virtual screen interface from the overlay of each frame and send it to the other end, thereby achieving screen sharing. For example... Figure 1 As shown, the window manager overlays the desktop, window 1, window 2, window 3, and notification message 1 layers on the current screen to generate a virtual screen interface, which is then sent to the other end. This allows the other device to display the same shared interface as the local device. Next, combining... Figures 4 to 7 This explains the specific procedures and display methods for protection operations.

[0128] Figure 4 A flowchart of a protection operation is shown to protect notification messages from being leaked. The method includes:

[0129] S401. Confirm screen sharing status.

[0130] Terminal devices can detect when the current screen state is in screen sharing mode through a screen sharing status monitoring module. The specific method is described above and will not be repeated here.

[0131] S402, Set the screen sharing status flag.

[0132] Specifically, when the screen sharing status monitoring module detects that the current screen state is in screen sharing mode, it uses the Settings.Secure.putInt method to switch the status value of the screen_sharing_state field of the screen sharing status flag to protected_status (or set it to 1). The protected_status (or 1) field indicates that the screen is currently in screen sharing mode.

[0133] S403. Monitor changes in the screen sharing status flag in the database.

[0134] Specifically, the notification manager can use the ContentObserver class to listen for changes in the screen_sharing_state state value and obtain specific state values ​​(such as protected_status).

[0135] S404. When the screen sharing status flag indicates that the screen sharing state is currently active, set the notification message layer to a privacy layer.

[0136] When the notification manager detects that the status value of the screen_sharing_state field has switched to protected_status (or 1), it adds the notification message layer to the privacy layer.

[0137] Specifically, adding a notification message layer to a privacy layer can be achieved by the notification manager instructing the display compositor to add a privacy label to the notification message layer via the window manager. When a terminal device sends a display to a peer device, the notification message layer carrying the privacy label can be masked during the overlay of multiple window layers. In other words, the display compositor does not overlay the notification message layer when generating the virtual screen interface. Therefore, the generated virtual screen interface will not display the notification message, and when this virtual screen interface is sent to the peer device, the peer device's interface will also not display the notification message.

[0138] For details, please refer to [link / reference]. Figure 5 As shown, Figure 5 Figure a in the diagram shows a schematic of a notification message popping up on the local interface. Figure 5 Figure b in the diagram shows an interface where the notification message displayed on the local end is not shown in the peer's interface. Optionally, a prompt message can be added to the local end's interface; see [link to documentation] for details. Figure 6 As shown. Figure 6 The image in Figure 'a' uses a banner notification as an example to inform the user that the other end cannot see the notification message from this end. Figure 6Figure b in the diagram shows the interface as seen by the other end, excluding notification messages. Users on their local devices will see a notification on their screen, informing them that the other end will not display notification messages. Therefore, they do not need to immediately switch screens or disable notifications to avoid data leakage. This reduces user operations and improves the user experience while ensuring privacy.

[0139] S405, Turn off screen sharing.

[0140] The interface on this device can also display a control to disable screen sharing, for example, in Figure 6 Figure a shows the "Stop Sharing" control. Users can click this control to close the screen, and the terminal device responds by disabling screen sharing.

[0141] When sending content from one end to the other, the terminal device can also add privacy labels to the layers of the prompt information and the close control to prevent these information and the close control from being displayed on the other end's interface. The method for adding privacy labels to the layers of the prompt information and the close control is the same as the method for adding privacy labels to the layers of notification messages described earlier, and will not be repeated here.

[0142] When the terminal device stops screen sharing, for example, when the user clicks... Figure 6 When the control is closed as shown in Figure a, the screen sharing status monitoring module detects the broadcast notification of the Media Projection Manager interface, thus confirming that screen sharing is off. In other words, the Media Projection Manager interface is in an uninvoked state. The screen sharing status monitoring module then uses the Settings.Secure.putInt method to set the screen_sharing_state field of the screen sharing status flag to normal_status (or 0), indicating that the current state is not screen sharing.

[0143] S406, Disable privacy layer.

[0144] When the notification manager detects that the screen_sharing_state field has switched to normal_status (or 0), it can instruct the removal of the privacy label from the layer displaying compositor notification messages. This prevents the notification message layer from being hidden, thus avoiding the inability to display notification messages in other scenarios. Optionally, the notification manager can also remove the privacy labels from previously labeled tooltip layers and close control layers as well.

[0145] When the terminal device stops screen sharing, the layers for the notification information and the close control will be destroyed and will no longer be displayed on the local device.

[0146] When a terminal device is in a scenario suspected of being fraudulent (referred to as a fraud-related scenario or a risk of being fraudulent), it indicates that there is a possibility of being defrauded, and the privacy risk will be higher when the screen is shared.

[0147] Specifically, the system administrator for the terminal device monitors its status through a fraud risk monitoring module. For example, if the module detects that the terminal device makes or receives a fraudulent call for more than one minute, replies to a fraudulent text message, or visits a fraudulent website for more than a certain duration (e.g., more than 15 seconds), it will continue to monitor the terminal device's behavior. If the fraud risk monitoring module detects that the terminal device initiates fraudulent activities such as payment requests or transfers (fraudulent apps initiating financial payment applications), the terminal device will record these characteristic behaviors and input them into the fraud identification model (or the fraud risk monitoring module) within the terminal device for identification. If the fraud identification model identifies characteristic behaviors indicating a fraud risk for the current terminal device, it can set a fraud risk value to represent the fraudulent scenario, or generate a fraud risk factor (i.e., the first factor) representing the fraudulent scenario.

[0148] Optionally, the fraud risk monitoring module can also report the aforementioned characteristic behaviors to the cloud server, so that the cloud server can retrain the fraud identification model based on the characteristic behaviors reported by the terminal, thereby improving the accuracy of the fraud identification model and thus improving the accuracy of the identification results. The cloud server can also distribute the latest fraud identification model to the terminal devices for use at appropriate times.

[0149] Optionally, the terminal device can also display a fraud risk warning message on its local interface when there is a risk of fraud, and can also send a text message to emergency contacts to provide a reminder.

[0150] When the fraud risk monitoring module receives the screen sharing status flag from the screen sharing status monitoring module, and the flag's value indicates that the screen is currently in a sharing state, it retrieves the fraud risk value or queries whether a fraud risk factor exists. If the fraud risk value indicates a fraudulent scenario or the existence of a fraud risk factor, the shared interface is added to a security layer, and the display is sent to the other end based on this security layer. If the fraud risk value indicates no fraudulent scenario or the absence of a fraud risk factor, adding the shared interface to a security layer is unnecessary. Optionally, the security layer can be a completely black layer, displaying no window content; or it can be a blurred layer, also displaying no actual content. Therefore, based on the security layer, the other end cannot see the content displayed on this end's screen.

[0151] For specific procedures regarding protection in cases of fraud risk, please refer to [reference needed]. Figure 7 As shown, it includes:

[0152] S701, Determine screen sharing status.

[0153] For a detailed description of step S701, please refer to the description of S401 above, which will not be repeated here.

[0154] S702. Determine whether the current situation is a fraud-related scenario.

[0155] Specifically, terminal devices can access the fraud risk monitoring module to detect risky behaviors. If risky behaviors such as making or receiving fraudulent phone calls for more than one minute, replying to fraudulent text messages, or visiting fraudulent websites for more than 15 seconds are detected, the terminal device can initiate anti-fraud monitoring. Anti-fraud monitoring can include monitoring fraudulent behaviors and monitoring fraudulent operations. When the terminal device detects fraudulent behavior or operations, it determines that it is currently in a fraudulent scenario and sets a fraud risk value to represent the situation or generates a fraud risk factor.

[0156] S703. If the current situation involves fraud, add the current shared interface to the security layer.

[0157] In fraud-related scenarios, terminal devices can invoke the window manager to set the current shared interface (Display) as a secure layer (or add a secure layer). Specifically, the window manager can add a security tag to the shared interface to set it as a secure layer. Adding a security tag can be done by setting a security layer flag for the shared interface. The window manager then sends the security layer flag to the display compositor. Under the influence of the security layer flag, the display compositor generates a completely black or blurred virtual screen interface, which serves as the secure layer interface, and then sends this interface to the other end.

[0158] Figure 8 This is a schematic diagram of the interface when about to enter screen sharing mode in a fraud-related scenario. When in a fraud-related scenario, the terminal device initiates or receives a screen sharing message, and the interface displays... Figure 8 The screen sharing interface is waiting for the connection to be established. Figure 8 In Figure a, since the terminal device is in a fraud-related scenario, the screen sharing interface awaiting connection can also display an anti-fraud alert card. This card includes alert text and an icon; it can also include a path to disable anti-fraud protection, such as Settings > Security > Anti-fraud Protection, allowing users to access settings to turn the alert on or off. The card can also include links to anti-fraud cases, such as "View Anti-fraud Cases." Users can click these links to view and learn about anti-fraud cases. Additionally, the card can display a countdown timer. When the user clicks the "OK" button to end the countdown, the terminal device displays... Figure 8 The prompt card shown in Figure b is displayed. Users can also wait for the countdown to finish before the terminal device automatically displays a message like this. Figure 8 The prompt card shown in Figure b is an example. This card includes controls for "Direct Sharing" and "Enable Protection." If the user is certain that they will not disclose private information or perform any fraudulent actions, they can click the "Direct Sharing" control. In this case, the terminal device can proceed with the normal sharing process, and the other end can display the sharing interface normally. If the user is concerned about privacy leaks or the risk of being scammed, they can click the "Enable Protection" control. In this case, the terminal device adds a security layer to the sharing interface, preventing the other end from displaying the sharing interface.

[0159] After a security layer is added to the shared interface, the terminal device can display the previous shared interface normally. Furthermore, the terminal device's shared interface can display prompts such as: "Anti-fraud firewall is enabled; the other party will not be able to see your screen content." See [link to documentation] for details. Figure 9 As shown in Figure a. At this time, the other end will display a completely black screen, for example... Figure 9As shown in Figure b.

[0160] Optionally, if the user performs screen recording after setting a security layer, the terminal device can simultaneously enter screen recording mode while in screen sharing mode, meaning the terminal device can share the screen and record simultaneously. It should be noted that the mechanism of screen recording is similar to that of screen sharing; both involve overlaying multiple windows in the current shared interface to generate a virtual screen interface. In screen recording mode, the terminal device can store the virtual screen interface frame by frame. Therefore, when a security layer is added to the shared interface, the virtual screen interface recorded during screen recording is the interface of the security layer, resulting in a completely black video file.

[0161] S704, Screen sharing is off.

[0162] For a detailed description of S704, please refer to the description of S405 above, which will not be repeated here.

[0163] S705, Remove security layer.

[0164] Terminal devices can call the window manager to remove the security label of the current shared interface (Display) after screen sharing is stopped, thereby canceling the security layer.

[0165] Next, in order to fully describe the technical solution of this application, in conjunction with Figure 10 The interactive diagram shown provides a detailed explanation. It should be noted that the screen sharing status monitoring module can also be divided into two functional parts: ScreenSharingProtection and ScreenSharingManager. ScreenSharingProtection manages the screen sharing status; ScreenSharingManager initiates and executes corresponding protection operations based on the screen sharing status. For example... Figure 10 As shown, it includes:

[0166] S1001, The screen sharing protector initializes when the terminal device is powered on and instructs the screen sharing manager to start broadcast listening.

[0167] Specifically, the screen sharing protector initializes when the terminal device powers on. The screen sharing protector can obtain the status of the protection switch in the system manager's security center. If the protection switch is in the "on" state, it means that protection needs to be enabled for the terminal device. Therefore, during initialization, it instructs the screen sharing manager to start broadcast listening to monitor the call status of the MediaProjection Manager interface. If the protection switch is in the "off" state, it means that protection does not need to be enabled for the terminal device. Therefore, during initialization, it either does not need to instruct the screen sharing manager to start broadcast listening or instructs the screen sharing manager to disable broadcast listening.

[0168] S1002, Screen sharing protector initializes screen sharing state.

[0169] Specifically, the screen sharing protector initializes the screen sharing state to a non-screen sharing state. For example, it refreshes the screen sharing state flag (e.g., screen_sharing_state) to a status value representing the non-screen sharing state (e.g., normal_status or 0).

[0170] S1003, Screen Sharing Manager registers a broadcast with Media Projection Manager.

[0171] Specifically, under the instruction of the screen sharing protector, the screen sharing manager registers a broadcast with the Media Projection Manager through the Media Projection Manager interface in the application framework layer, in order to listen for the call status of the Media Projection Manager interface.

[0172] S1004, Media Projection Manager sends a callback broadcast message (onReceive) to the Screen Sharing Manager.

[0173] The callback broadcast information includes: the Media Projection Manager interface is in the called state, and the package name of the application that called the Media Projection Manager interface.

[0174] S1005. The screen sharing manager obtains the current call mode and determines whether it is in screen sharing mode based on the current call mode.

[0175] Specifically, the screen sharing manager calls the AudioManager.getMode() method to obtain the current call mode, and combines the current call mode with the call status of the Media Projection Manager interface to determine whether the current screen state is in screen sharing mode. The detailed process can be found in the previous descriptions and will not be repeated here.

[0176] The screen sharing manager can also add the package name of the application that calls the Media Projection Manager interface and the status value representing the screen sharing state to the history of calls (in the form of a hash table). A description of the history of calls can be found in the previous section and will not be repeated here.

[0177] S1006. The screen sharing manager instructs the screen sharing protector to update the field of the screen sharing status flag.

[0178] S1007. The screen sharing protector responds to the instructions of the screen sharing manager by setting the status value of the screen sharing status flag.

[0179] The screen sharing manager can send commands to the screen sharing protector to instruct it to update the screen sharing status flag field.

[0180] If the screen sharing state is confirmed, the screen sharing manager can send a command to the screen sharing protector. The screen sharing protector then responds to the command by calling the Settings.Secure.putInt method to set the screen_sharing_state field of the screen sharing status flag to protect_status (or 1), indicating that the screen is currently in a screen sharing state.

[0181] When the screen sharing manager determines that the screen is not in a screen sharing state (i.e., it is in screen recording state), it can send a command to the screen sharing protector. The screen sharing protector, in response to the command, calls the `Settings.Secure.putInt` method to set the `screen_sharing_state` field of the screen sharing status flag to `normal_status` (or 0), indicating that the current state is not screen sharing. Afterward, the terminal device can abort the process and stop performing subsequent protection operations.

[0182] S1008, Notification Manager listens for changes in the screen sharing status flag field.

[0183] Specifically, the notification manager uses the ContentObserver class to monitor changes in the state value of the screen_sharing_state field from the screen sharing protector. Then, steps S1013 can be executed.

[0184] S1009. The screen sharing manager obtains the fraud monitoring results detected by the fraud risk monitoring module.

[0185] Specifically, fraud monitoring results can be represented by a fraud risk value. When the fraud risk monitoring module detects that a terminal device makes or receives a fraudulent call for more than one minute, replies to a fraudulent text message, or visits a fraudulent website for more than 15 seconds, and also detects fraudulent behavior or operations, then a fraud risk can be identified. Based on this, a fraud risk value can be set to represent a fraudulent scenario or a fraud risk factor can be generated. Otherwise, the fraud risk value is determined to represent a non-fraudulent scenario or no fraud risk factor is generated.

[0186] The screen sharing manager can read fraud risk values ​​or query whether fraud risk factors exist.

[0187] Optionally, the screen sharing manager can also send the status value of the screen sharing status flag to the fraud risk monitoring module, which will then determine the current processing scope. The method by which the fraud risk monitoring module determines the current processing scope is similar to the logic of the screen sharing manager's related operations and will not be elaborated further.

[0188] S1010 The fraud risk monitoring module sends the collected fraud-related behavior sequences to the application behavior sequence collector (AppBehaviorDataReporter).

[0189] S1011, The application behavior sequence collector reports the behavior sequence of fraudulent behavior to the cloud server.

[0190] The cloud testing server can be used to train the fraud risk monitoring module and thus update the fraud identification model.

[0191] S1012, Screen Sharing Manager determines the current processing range.

[0192] Specifically, after S1009 above, if the screen is in a shared state, the screen sharing manager can determine whether the processing scope is to hide only the notification message, or to hide the notification message and add a security layer to the shared interface at the same time.

[0193] The screen sharing manager can determine whether to add the shared interface to the security layer based on a fraud risk value or the presence of a fraud risk factor. When the fraud risk value indicates a non-fraudulent scenario or no fraud risk factor exists, the processing scope can be determined to be simply hiding the notification message. When the fraud risk value indicates a fraudulent scenario or a fraud risk factor exists, the processing scope can be determined to include both hiding the notification message and adding the shared interface to the security layer. See the previous description for details, which will not be repeated here.

[0194] Optionally, the execution order of S1010, S1011, and S1012 can be interchanged, and this application embodiment does not limit it.

[0195] S1013. In screen sharing mode, the notification manager instructs the display compositor to add the notification message layer to the privacy layer.

[0196] For example, if the notification manager detects that the screen sharing status flag changes from normal_status to protected_status, it indicates that screen sharing is in progress. Therefore, the window manager can send the screen sharing status flag value to the display compositor. Based on the screen sharing status flag value, the display compositor generates a virtual screen interface for the layer that does not include notification messages and sends it to the other end.

[0197] It should be noted that step S1013 can be executed after S1008, and the execution order of S1013, S1010, S1011, and S1012 is not limited.

[0198] S1014. The display compositor, in response to the instruction from the notification manager, generates a virtual screen interface for a layer that does not contain notification messages and displays it.

[0199] S1015, The screen sharing manager sends a command to the screen sharing protector to add a security layer.

[0200] S1016. The screen sharing protector responds to the instructions sent by the screen sharing manager by sending a message to the window manager to set a security layer.

[0201] S1017, The window manager indicates that the compositor will add the shared interface to the security layer.

[0202] Specifically, when the screen sharing status flag changes from `normal_status` to `protect_status`, and the fraud monitoring results indicate a fraud risk, the screen sharing manager determines that the scope of processing is to hide the notification message and add a security layer to the shared interface. The notification manager detects the screen sharing status flag changing from `normal_status` to `protect_status` and sends this status value to the display compositor. Based on the screen sharing status flag value, the display compositor generates a completely black security layer and sends it to the other end.

[0203] S1014' The display compositor responds to the window manager's instruction, generates a completely black safety layer, and displays it.

[0204] Optionally, steps S1014 and S1014' can also be executed simultaneously.

[0205] S1018, The screen share protector sends a callback broadcast message (onReceive) to the screen share manager.

[0206] When the user turns off screen sharing, the screen sharing manager will receive a broadcast message from the screen sharing protector again, indicating that screen sharing is off.

[0207] S1019. The screen sharing manager determines that screen sharing is off based on broadcast information.

[0208] S1020, The screen sharing manager instructs the screen sharing protector to update the field of the screen sharing status flag.

[0209] S1021. The screen sharing protector responds to the instructions of the screen sharing manager by setting the status value of the screen sharing status flag.

[0210] When the Screen Sharing Manager receives a broadcast message from the Media Projection Manager indicating that screen sharing is off, it can instruct the Screen Sharing Protector to update the screen sharing status flag to the value for the non-screen sharing state.

[0211] Specifically, the screen sharing manager sends a command to the screen sharing protector. In response to this command, the screen sharing protector updates the status value of the screen_sharing_state field of the screen sharing status flag to a status value indicating that the screen sharing status flag is not in the screen sharing status flag (e.g., from protect_status to normal_status, or from 1 to 0).

[0212] When the screen sharing manager determines that it is not in screen sharing mode, if a security layer exists, the current processing scope includes: canceling the privacy layer and canceling the security layer; if a security layer does not exist, the current processing scope includes: canceling the privacy layer.

[0213] S1022. The notification manager detects that the screen sharing status flag indicates that it is in a non-screen sharing state.

[0214] S1023, Disable privacy layer in Notification Manager.

[0215] The notification manager uses the ContentObserver class to monitor changes in the screen_sharing_state field from the screen sharing protector. When it detects that the screen sharing status flag indicates a non-screen sharing state, it removes the privacy label from the privacy layer.

[0216] S1024. The screen sharing protector, in response to the instruction from the screen sharing manager, sends a message to the window manager to cancel the security layer.

[0217] S1025, Window Manager removes the security layer.

[0218] When the window manager receives or listens to the screen sharing status flag indicating that it is not in screen sharing state, the security layer is canceled.

[0219] Optionally, the window manager can also receive status notification messages sent by the notification manager. Optionally, the notification manager can send a status notification message to the window manager when it detects that the screen sharing status flag indicates a non-screen sharing state. Responding to the status notification message, the window manager, knowing it is not currently in a screen sharing state, can then cancel the security layer.

[0220] The above Figure 10 The implementation principles and technical effects of these steps can be found in the relevant descriptions above, and will not be repeated here.

[0221] The interface display method provided in this application embodiment is applied to electronic devices, and can be found in, for example... Figure 11 As shown, it includes:

[0222] S1101: The Media Projection Manager interface was detected to be called for the first time by the first application.

[0223] S1102A. When the electronic device is in the VoIP (Voice over Internet Protocol) mode, a first interface is displayed. The first interface includes a first prompt message and a notification message. The first prompt message indicates that the notification message is not displayed on the other end.

[0224] S1102B When the electronic device is in VoIP mode and a first factor exists, a second interface is displayed. The second interface includes a second prompt message, which indicates that the second interface is not displayed on the other end. The first factor indicates that the electronic device is at risk of being involved in fraud.

[0225] S1103. If the Media Projection Manager interface is detected to be called by a second application for the first time, and the electronic device is in another call mode, a third interface is displayed. The third interface does not include the first and second prompt information. Other call modes are call modes that are different from both VoIP mode and carrier call mode.

[0226] This Media Projection Manager interface is for Media Projection Manager. When the Media Projection Manager interface is invoked, the terminal device may be in screen recording or screen sharing mode. We believe that screen recording is a safe scenario and can operate normally without requiring protection; however, screen sharing poses a risk of privacy information leakage and requires appropriate protection.

[0227] If the package name of the first application does not exist in the historical call record, meaning the first application is calling the MediaProjection Manager interface for the first time, and the electronic device is currently in VoIP mode, it indicates that screen sharing is in progress, posing a risk of privacy leakage. The terminal device can then perform corresponding protection operations.

[0228] Specifically, the terminal device can choose not to display the notification message content to the other end during the display process. In other words, the other end will not see the notification message popped up on this end, preventing the other end from seeing the notification message and protecting the user's privacy. At the same time, the interface displayed on this end is the first interface containing the initial prompt information. Users can know from this prompt information that the other end will not see the notification message popped up on this end, eliminating concerns about privacy leaks and improving the user experience.

[0229] If the local device still detects the presence of the first factor (i.e., the fraud risk factor mentioned later), or if the fraud risk value is a value representing a fraudulent scenario, then it indicates that the local device faces a fraud risk. The terminal device will not send any content from its second interface to the other end, ensuring that the other end cannot see any content displayed on the local device's second interface. This comprehensively protects the user's privacy information, prevents its leakage, and thus ensures the user's financial security. Simultaneously, the local device can also display a second prompt message on the second interface, allowing the user to know that the other party will not see any content on the local device's second interface, eliminating concerns about privacy leaks and improving the user experience.

[0230] If the terminal device detects that the Media Projection Manager interface has been called by a second application before, and the electronic device is in another call mode, the likelihood of the terminal device entering screen sharing mode is low; it is more likely to be in screen recording mode. Therefore, the terminal device does not need to perform any protection operations and can call the Media Projection Manager interface normally. The local device also does not need to display the first or second prompt messages.

[0231] It should be noted that the electronic device's call mode can be simply referred to as call mode, and will not be elaborated further in the following text.

[0232] In some possible implementations, the method also includes: after detecting that the Media Projection Manager interface is called by a third application for the first time; when the electronic device enters VoIP mode, displaying the first interface; when the electronic device enters VoIP mode and the first factor exists, displaying the second interface; wherein the package name of the third application exists in the preset screen sharing application whitelist.

[0233] When the Media Projection Manager interface is in the calling state, the package name of the third application that calls the Media Projection Manager interface exists in the historical call record, that is, the third application is not calling the Media Projection Manager interface for the first time.

[0234] The aforementioned preset screen-sharing application whitelist includes the package names of several applications with screen-sharing functionality. If the third-party application's package name is present in this whitelist, and the terminal device first detects that the MediaProjection Manager interface is being called by a third-party application, and then detects that the call mode has switched to VoIP mode, it indicates a high probability that screen sharing has been initiated. The terminal device can then perform corresponding protection operations, such as not sending notification messages to the other end, and not sending any content to the other end if there is a risk of fraud. This prevents the leakage of privacy information and comprehensively protects the user's information and property security.

[0235] In some possible implementations, the method also includes: detecting that the Media Projection Manager interface is called by a fourth application before its first call; displaying a third interface when the electronic device enters VoIP mode; wherein the third application is different from the fourth application, and the package name of the fourth application is not in the preset screen sharing application whitelist.

[0236] If the package name of the fourth application is not in the preset screen sharing application whitelist, it means that the fourth application most likely does not have screen sharing functionality. If the terminal device first detects that the Media Projection Manager interface has been called by the fourth application before, and then detects that the electronic device has entered VoIP mode, the likelihood of the terminal device entering screen sharing mode is even lower; it is more likely to be in screen recording mode. Therefore, the terminal device does not need to perform any protection operations and can call the Media Projection Manager interface normally. The local device also does not need to display the first or second prompt messages.

[0237] In some possible implementations, the method also includes: after the electronic device enters the operator's call mode; when it is detected that the Media Projection Manager interface is called by the fifth application for the first time, the first interface is displayed; when it is detected that the Media Projection Manager interface is called by the fifth application for the first time and the first factor exists, the second interface is displayed; wherein, the package name of the fifth application exists in the preset screen sharing application whitelist.

[0238] If the package name of the fifth application exists in the preset screen sharing application whitelist, it indicates that the fifth application has screen sharing functionality. If the terminal device first detects that the call mode has entered the carrier's "fairy mode," and then detects that the MediaProjection Manager interface has been called by the fifth application before its first time, then the terminal device is likely to enter screen sharing mode. Therefore, the terminal device can perform corresponding protection operations. For details on the execution method and technical effects of these protection operations, please refer to the relevant descriptions in this document; they will not be repeated here.

[0239] In some possible implementations, the method also includes: after the electronic device enters the carrier call mode; when it is detected that the Media Projection Manager interface is called by the sixth application for the first time, the third interface is displayed; wherein the package name of the sixth application is not in the preset screen sharing application whitelist.

[0240] If the package name of the sixth application is not in the preset screen sharing application whitelist, it indicates that the sixth application may not have screen sharing functionality. If the terminal device first detects that the call mode has entered carrier-controlled mode, and then detects that the Media Projection Manager interface has been called by the sixth application before, then the terminal device is likely to enter screen recording mode. Therefore, the terminal device does not need to perform any protection operations and can call the Media Projection Manager interface normally. The local device also does not need to display the first or second prompt messages.

[0241] In some possible implementations, the method also includes: when the first interface is displayed, adding the notification layer corresponding to the notification message to the privacy layer; generating a first virtual screen interface based on other layers besides the privacy layer; and sending the first virtual screen interface to the other end.

[0242] Specifically, one way to hide notification messages is to add the corresponding notification layer to a privacy layer. During the transmission of the notification to the other end, the content in the privacy layer will not appear in the first virtual screen interface. In other words, when the terminal device transmits the notification to the other end, the privacy layer window will not be overlaid when compositing the first virtual screen interface. Therefore, when transmitting the notification to the other end based on this first virtual screen interface, the other end will not display the privacy layer window, preventing the leakage of the privacy layer's content.

[0243] In some possible implementations, the notification layer corresponding to the notification message is added to the privacy layer, including adding a privacy label to the notification layer to make the notification layer added to the privacy layer.

[0244] Specifically, adding a notification layer to a privacy layer involves adding a privacy tag to the notification layer, thus marking the layer that needs to be hidden. Alternatively, adding a privacy tag can be done by setting a privacy flag on the notification layer, thereby adding the notification layer to the privacy layer and preventing the content of the notification layer from being sent to the other end.

[0245] Among some possible implementations, the method also includes: detecting that the Media Projection Manager interface is not being called; removing the privacy label from the notification layer and displaying a third interface.

[0246] If the terminal device detects that the Media Projection Manager interface is not being called, meaning Media Projection Manager has stopped collecting screen data, then the screen sharing state has ended. The terminal device can then remove the notification layer from the privacy layer, that is, remove the privacy label from the notification layer. At this point, since there is no risk of privacy information leakage, the third-party interface on this device will not display the first and second prompt messages. If the privacy label is not removed in time, when the terminal device enters screen recording mode again, the recorded video file will not contain the notification message due to the unremoved privacy label, resulting in incomplete information in the screen recording video file, which may affect user experience. Therefore, timely removal of the privacy label from the notification layer can avoid incomplete information acquisition in scenarios such as screen recording.

[0247] In some possible implementations, the method also includes: when the second interface is displayed, adding the second interface to a security layer; generating a second virtual screen interface based on the security layer; sending the second virtual screen interface to the other end for display; the second virtual screen interface is a black interface.

[0248] Specifically, one way to prevent the content of the second interface from being displayed on the other end is to add a security layer to the second interface. During the transmission of the display to the other end, the interface with the security layer will not be displayed on the other end. In other words, when the terminal device transmits the display to the other end, it will not overlay any windows of the second interface when compositing the second virtual screen interface, but will instead generate a completely black or completely blurred second virtual screen interface. Therefore, when the display is transmitted to the other end based on such a second virtual screen interface, the other end will not display any content from the second interface, thus preventing the leakage of privacy information.

[0249] In some possible implementations, a security layer is added to the second interface, including adding a security label to the second interface to enable the second interface to be included in the security layer.

[0250] Specifically, the second interface is added to the security layer by adding a security label to the second interface, thereby marking the interface that needs to be hidden. Optionally, adding a security label can be done by setting a security flag for the second interface, thereby adding the second interface to the security layer and preventing the content of the second interface from being sent to the other end.

[0251] Among some possible implementations, the method also includes: detecting that the Media Projection Manager interface is not being called; removing the security label of the security layer and displaying a third interface.

[0252] If the terminal device detects that the Media Projection Manager interface is not being called, meaning Media Projection Manager has stopped collecting screen data, then the screen sharing state has ended. The terminal device can then remove the second interface from the security layer, i.e., remove the security label from the second interface. At this point, since there is no risk of privacy information leakage, the third interface on this device will not display the first and second prompt messages. If the security label is not removed in time, when the terminal device enters screen recording mode again, a completely black video file may be recorded due to the security label not being removed, affecting user experience. Therefore, timely removal of the security label from the second interface can prevent situations where screen information cannot be obtained in screen recording and other scenarios.

[0253] The foregoing has detailed examples of the methods provided in this application. It is understood that the corresponding apparatus, in order to achieve the above functions, includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0254] This application can divide the interface display device into functional modules based on the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0255] The specific manner in which the interface display device executes the interface display method and the beneficial effects thereof can be found in the relevant descriptions in the method embodiments, and will not be repeated here.

[0256] This application also provides an electronic device, including the processor described above. The electronic device provided in this embodiment may be... Figure 2 The terminal device 100 shown is used to execute the above-described interface display method. When using integrated units, the terminal device may include a processing module, a storage module, and a communication module. The processing module can be used to control and manage the actions of the terminal device; for example, it can support the terminal device in executing the steps performed by the display unit, the detection unit, and the processing unit. The storage module can be used to support the terminal device in executing stored program code and data. The communication module can be used to support communication between the terminal device and other devices.

[0257] The processing module can be a processor or a controller. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination of functions that implement computing capabilities, such as a combination of one or more microprocessors, a digital signal processor (DSP), and a microprocessor, etc. The storage module can be a memory. The communication module can specifically be a radio frequency circuit, a Bluetooth chip, a Wi-Fi chip, or other devices that interact with other terminal devices.

[0258] In one embodiment, when the processing module is a processor and the storage module is a memory, the terminal device involved in this embodiment can be a device having... Figure 2 The device with the structure shown.

[0259] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the interface display method described in any of the above embodiments.

[0260] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the interface display method described in the above embodiments.

[0261] In this embodiment, the electronic device, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0262] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between devices or units. The replaced units may or may not be physically separate. The component shown as a unit may be one physical unit or multiple physical units, that is, it may be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0263] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0264] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0265] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for displaying an interface, applied to an electronic device, characterized in that, The method includes: The Media Projection Manager interface was detected to be called for the first time by the first application; When the electronic device is in the VoIP (Voice over Internet Protocol) mode, a first interface is displayed. The first interface includes a first prompt message and a notification message. The first prompt message indicates that the notification message is not displayed on the other end. When the first interface is displayed, data of a first virtual screen interface is sent. The first virtual screen interface does not overlay the notification layer corresponding to the notification message. When the electronic device is in the VoIP mode and a first factor exists, a second interface is displayed. The second interface includes a second prompt message. The second prompt message indicates that the second interface is not displayed on the other end. The first factor indicates that the electronic device is at risk of being involved in fraud. When the second interface is displayed, data for a second virtual screen interface is sent. The second virtual screen interface is a black interface or a blurred interface. It was detected that the Media Projection Manager interface was called by the second application on a non-first-time basis; When the electronic device is in another call mode, a third interface is displayed. The third interface does not include the first prompt information and the second prompt information. The other call mode is a call mode that is different from both the VoIP mode and the carrier call mode.

2. The method according to claim 1, characterized in that, The method further includes: After detecting that the Media Projection Manager interface was called by a third application for the first time; When the electronic device enters the VoIP mode, the first interface is displayed; When the electronic device enters the VoIP mode and the first factor is present, the second interface is displayed; The package name of the third application exists in the preset screen sharing application whitelist.

3. The method according to claim 2, characterized in that, The method further includes: After detecting that the Media Projection Manager interface was called by the fourth application for the first time; When the electronic device enters the VoIP mode during a call, the third interface is displayed. The third application is different from the fourth application, and the package name of the fourth application is not in the preset screen sharing application whitelist.

4. The method according to claim 1, characterized in that, The method further includes: After the electronic device enters the operator's call mode; When it is detected that the Media Projection Manager interface is called by the fifth application for the first time, the first interface is displayed. When it is detected that the Media Projection Manager interface is not being called by the fifth application for the first time, and the first factor exists, the second interface is displayed; The package name of the fifth application exists in the preset screen sharing application whitelist.

5. The method according to claim 1 or 4, characterized in that, The method further includes: After the electronic device enters the operator's call mode; When it is detected that the Media Projection Manager interface is called by the sixth application for the first time, the third interface is displayed; The package name of the sixth application is not in the preset screen sharing application whitelist.

6. The method according to any one of claims 1 to 5, characterized in that, The step of sending data for the first virtual screen interface when the first interface is displayed includes: When the first interface is displayed, the notification layer corresponding to the notification message is added to the privacy layer; A first virtual screen interface is generated based on layers other than the privacy layer, and the data of the first virtual screen interface is sent to the other end.

7. The method according to claim 6, characterized in that, Adding the notification layer corresponding to the notification message to the privacy layer includes: Add a privacy label to the notification layer to add the notification layer to the privacy layer.

8. The method according to claim 7, characterized in that, The method further includes: The Media Projection Manager interface was not detected to be invoked. Remove the privacy label from the notification layer and display the third interface.

9. The method according to any one of claims 1 to 8, characterized in that, When the second interface is displayed, sending data for the second virtual screen interface includes: When the second interface is displayed, a security layer is added to the second interface; A second virtual screen interface is generated based on the security layer, and the data of the second virtual screen interface is sent to the other end. The security layer is a black layer or a blurred layer.

10. The method according to claim 9, characterized in that, Adding the second interface to the security layer includes: Add a security label to the second interface to add the security layer to the second interface.

11. The method according to claim 10, characterized in that, The method further includes: The Media Projection Manager interface was not detected to be invoked. Remove the security label from the security layer and display the third interface.

12. An electronic device, characterized in that, include: Processor, memory, and interface; The processor, the memory, and the interface cooperate with each other to enable the electronic device to perform the method as described in any one of claims 1 to 11.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to perform the method of any one of claims 1 to 11.

Images