Interface display method, electronic equipment and computer readable storage medium

Abstract

The invention relates to the technical field of electronics, and provides an interface display method, electronic equipment and a computer readable storage medium, the method comprises the following steps: monitoring that a Media Projection Manager interface is called by a first application for the first time; when the call mode of the electronic equipment is in the VoIP mode, a first interface is displayed, the first interface comprises first prompt information and a first notification message, and the first prompt information prompts that the first notification message is in an opposite-end non-display state; when the call mode of the electronic equipment is in the VoIP mode and the first factor exists, a second interface is displayed, the second interface comprises second prompt information, and the second prompt information prompts that the second interface is in an opposite-end non-display state; and when it is monitored that the Media Projection Manager interface is not called by the second application for the first time, when the call mode of the electronic equipment is in other modes, displaying a third interface. According to the method, privacy information leakage can be avoided.

Description

Technical Field

[0001] This application relates to the field of Internet technologies, and in particular, to an interface display method, an electronic device, and a computer-readable storage medium. Background Art

[0002] With the rapid development of Internet technologies, the convenience brought by the Internet to people cannot be ignored. However, various risks brought by the Internet have also attracted more and more attention.

[0003] Many lawbreakers often steal users' privacy information through the Internet and then steal property. Summary of the Invention

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

[0005] In a first aspect, an interface display method is provided, which is applied to an electronic device and includes: detecting that the MediaProjection Manager interface is first called by a first application; when the call mode of the electronic device is in the Voice over Internet Protocol (VoIP) mode, displaying a first interface, where the first interface includes a first prompt message and a notification message, and the first prompt message indicates that the notification message is in a non-display state for the other party; when the call mode of the electronic device is in the VoIP mode and there is a first factor, displaying a second interface, where the second interface includes a second prompt message, and the second prompt message indicates that the second interface is in a non-display state for the other party, and the first factor represents that the electronic device has a risk of being involved in fraud; detecting that the Media Projection Manager interface is called by a second application non-first time, and when the call mode of the electronic device is in other modes, displaying a third interface, where the third interface does not include the first prompt message and the second prompt message, and the other call mode is a call mode different from both the VoIP mode and the operator call mode.

[0006] The Media Projection Manager interface is the interface of the Media Projection Manager. When the Media Projection Manager interface is in a called state, the terminal device may be in a screen recording state or a screen sharing state. We believe that the screen recording state is a safe scenario and can operate normally without performing protection operations; while there is a risk of privacy information leakage in the screen sharing state, and corresponding protection operations need to be performed.

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

[0008] Specifically, the terminal device may not display the content of the notification message to the peer during the display process. That is to say, the peer will not see the notification message popped up on the local end, avoiding the notification message being seen by the peer and protecting the user's privacy information. At the same time, the interface displayed on the local end is the first interface containing the first prompt message. The user can learn from the first prompt message that the peer will not see the notification message popped up on the local end and does not need to worry about privacy information leakage, improving the user experience.

[0009] If the local end also detects the existence of a first factor (i.e., the fraud risk factor in the following text) at this time, or the fraud risk value is a value indicating being in a fraud scenario, it means that there is a fraud risk at the local end. The terminal device will not send any content in the second interface of the local end to the peer, so that the peer cannot see any content displayed in the second interface of the local end, comprehensively protecting the user's privacy information and avoiding the leakage of privacy information, thus ensuring the user's property safety. At the same time, the local end can also display a second prompt message in the second interface. The user can learn from the second prompt message that the peer will not see any content in the second interface of the local end and does not need to worry about privacy information leakage, improving the user experience.

[0010] If the terminal device monitors that the Media Projection Manager interface is called by a second application non-first time, when the call mode of the electronic device is in other call modes, then the possibility of the terminal device entering the screen sharing state is low, and it is probably in the screen recording state. Therefore, the terminal device does not need to perform protection operations and can normally call the Media ProjectionManager interface. The local end also does not need to display content such as the first prompt message and the second prompt message.

[0011] It should be noted that the call mode of the electronic device can be abbreviated as the call mode, which will not be elaborated further in the following text.

[0012] In some possible implementation manners, the method further includes: after monitoring that the Media Projection Manager interface is called by a third application non-first time; when the call mode of the electronic device enters the VoIP mode, displaying the first interface; when the call mode of the electronic device enters the VoIP mode and there is a first factor, displaying the second interface; where 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 call state, the package name of the third application that calls the Media Projection Manager interface exists in the historical call records, that is, the third application is not calling the Media Projection Manager interface for the first time.

[0014] The above preset screen sharing application whitelist includes the package names of multiple application programs with screen sharing functions. If the package name of the third application exists in the preset screen sharing application whitelist, and the terminal device first detects that the Media Projection Manager interface is called by the third application and then detects that the call mode enters the VoIP mode, it indicates that the possibility of entering the screen sharing state is high at this time. The terminal device can then perform corresponding protection operations, such as not sending a display notification message to the peer, and not sending any content to the peer when there is a risk of fraud. This can avoid the leakage of privacy information and comprehensively protect the user's information and property security.

[0015] In some possible implementation manners, the method further includes: after detecting that the Media Projection Manager interface is non-first called by a fourth application; when the call mode of the electronic device enters the VoIP mode, displaying a third interface; wherein, the third application and the fourth application are different, 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 does not exist in the preset screen sharing application whitelist, it indicates that the fourth application probably does not have the screen sharing function. When the terminal device first detects that the Media Projection Manager interface is non-first called by the fourth application and then detects that the call mode of the electronic device enters the VoIP mode, the possibility of the terminal device entering the screen sharing state is lower, and it is probably in the screen recording state. Therefore, the terminal device does not need to perform protection operations and can normally call the Media Projection Manager interface. The local end also does not need to display content such as the first prompt message and the second prompt message.

[0017] In some possible implementation manners, the method further includes: after the call mode of the electronic device enters the operator call mode; when detecting that the Media Projection Manager interface is non-first called by a fifth application, displaying a first interface; when detecting that the Media Projection Manager interface is non-first called by the fifth application and there is a first factor, displaying a second interface; 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 white list of screen sharing applications, it indicates that the fifth application has the screen sharing function. When the terminal device first monitors that the call mode enters the carrier call mode, and then monitors that the MediaProjection Manager interface is called by the fifth application for the non-first time, the probability that the terminal device enters the screen sharing state is high. Therefore, the terminal device can perform corresponding protection operations. For the execution method and technical effects of the protection operations, please refer to the relevant descriptions in this article, which will not be elaborated here.

[0019] In some possible implementation manners, the method further includes: after the call mode of the electronic device enters the carrier call mode; when it is monitored that the Media Projection Manager interface is called by a sixth application for the non-first time, a third interface is displayed; wherein, the package name of the sixth application is not in the preset white list of screen sharing applications.

[0020] If the package name of the sixth application is not in the preset white list of screen sharing applications, it indicates that the sixth application may not have the screen sharing function. When the terminal device first monitors that the call mode enters the carrier call mode, and then monitors that the MediaProjection Manager interface is called by the sixth application for the non-first time, the probability that the terminal device enters the screen recording state is high. Therefore, the terminal device does not need to perform protection operations and can normally call the Media Projection Manager interface. The local end also does not need to display the first prompt message, the second prompt message, and other contents.

[0021] In some possible implementation manners, the method further 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 according to other layers outside the privacy layer, and sending the first virtual screen interface to the peer end for display.

[0022] Specifically, the way to hide the notification message can be to add the notification layer corresponding to the notification message to the privacy layer. During the process of sending and displaying to the peer end, the content in the layer added to the privacy layer will not appear in the first virtual screen interface. That is to say, when the terminal device synthesizes the first virtual screen interface during the process of sending and displaying to the peer end, the window of the privacy layer will not be superimposed. Therefore, based on such a first virtual screen interface for sending and displaying to the peer end, the peer end will not display the window of the privacy layer, avoiding the leakage of the content of the privacy layer.

[0023] In some possible implementation manners, adding the notification layer corresponding to the notification message to the privacy layer includes: adding a privacy label to the notification layer so that the notification layer is added to the privacy layer.

[0024] Specifically, the method of adding a notification layer to a privacy layer is to add a privacy label to the notification layer to mark the layer that needs to be hidden. Optionally, the method of adding a privacy label can be to set a privacy flag bit for the notification layer, so as to add the notification layer to the privacy layer and avoid sending the content of the notification layer to the peer end for display.

[0025] In some possible implementation manners, the method further includes: detecting that the Media Projection Manager interface is not called; removing the privacy label of the notification layer, and displaying a third interface.

[0026] If the terminal device detects that the Media Projection Manager interface is not called, that is, the MediaProjection Manager stops collecting screen data, it indicates that the screen sharing state has ended. The terminal device can then move the notification layer out of the privacy layer, that is, remove the privacy label of the notification layer. At this time, since there is no risk of privacy information leakage, the first prompt message and the second question message will not be displayed on the third interface of the local end. If the privacy label is not removed in time, then when the terminal device enters the screen recording state again, a video file that does not contain notification messages may be recorded due to the privacy label not being removed, resulting in incomplete information in the video file obtained by screen recording, which may affect the user experience. Therefore, removing the privacy label of the notification layer in time can avoid the situation of incomplete information obtained in some scenarios such as screen recording.

[0027] In some possible implementation manners, the method further includes: when the second interface is displayed, adding the second interface to a security layer; generating a second virtual screen interface according to the security layer, and sending the second virtual screen interface to the peer end for display, where the second virtual screen interface is a black interface.

[0028] Specifically, the method of protecting the content of the second interface from being displayed at the peer end can be to add the second interface to the security layer. During the process of sending and displaying at the peer end, the interface added to the security layer will not be displayed at the peer end. That is to say, when the terminal device sends and displays to the peer end, any window in the second interface will not be superimposed when synthesizing the second virtual screen interface, but a completely black or completely blurred second virtual screen interface will be generated. Therefore, based on such a second virtual screen interface sent to the peer end, the peer end will not display any content in the second interface, avoiding the leakage of privacy information.

[0029] In some possible implementation manners, adding the second interface to the security layer includes: adding a security label to the second interface to enable the second interface to be added to the security layer.

[0030] Specifically, the method of adding the second interface to the security layer is to add a security label to the second interface, thereby marking the interface that needs to be hidden. Optionally, the method of adding the security label can be to set a security flag bit for the second interface, thereby adding the second interface to the security layer to avoid sending the content of the second interface to the peer end for display.

[0031] In some possible implementation manners, the method further includes: detecting that the Media Projection Manager interface is not 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 called, that is, the MediaProjection Manager stops collecting screen data, it indicates that the screen sharing state has ended. The terminal device can then remove the second interface from the security layer, that is, remove the security label of the second interface. At this time, since there is no risk of privacy information leakage, the first prompt message and the second question information will not be displayed on the third interface of the local end. If the security label is not removed in time, then when the terminal device enters the screen recording state again, a situation where a completely black video file is recorded due to the security label not being removed will occur, affecting user experience. Therefore, removing the security label of the second interface in time can avoid the situation where screen information cannot be obtained in some scenarios such as screen recording.

[0033] In a second aspect, there is provided an interface display device, including a unit composed of software and / or hardware, and the unit is configured to execute any one of the methods in the technical solutions described in the first aspect.

[0034] In a third aspect, an embodiment of the present application provides a chip, including a processor; the processor is configured to read and execute a computer program stored in a memory to execute any one of the methods in the technical solutions described in the first aspect.

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

[0036] Further optionally, the chip further includes a communication interface.

[0037] In a fourth aspect, there is provided an electronic device, including: a processor, a memory, and an interface; the processor, the memory, and the interface cooperate with each other to enable the electronic device to execute any one of the methods in the technical solutions described in the first aspect.

[0038] In a fifth aspect, there is provided a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the processor is enabled to execute any one of the methods in the technical solutions described in the first aspect.

[0039] In a sixth aspect, a computer program product is provided, which includes computer program code that, when running on an electronic device, causes the electronic device to execute any one of the methods in the technical solutions described in the first aspect. Description of the Drawings

[0040] Figure 1 is a scenario diagram of screen sharing provided by an embodiment of the present application;

[0041] Figure 2 is a schematic structural diagram of a terminal device 100 provided by an embodiment of the present application;

[0042] Figure 3 is a software structural block diagram of the terminal device 100 provided by an embodiment of the present application;

[0043] Figure 4 is a flowchart of a protection operation provided by an embodiment of the present application;

[0044] Figure 5 is a schematic diagram of the interfaces of the local end and the peer end in the case of a protection notification message provided by an embodiment of the present application;

[0045] Figure 6 is a schematic diagram of the interfaces of the local end and the peer end in another case of a protection notification message provided by an embodiment of the present application;

[0046] Figure 7 is a flowchart of another protection operation provided by an embodiment of the present application;

[0047] Figure 8 is a schematic diagram of an interface with a fraud risk provided by an embodiment of the present application;

[0048] Figure 9 is a schematic diagram of the interfaces of the local end and the peer end when there is another fraud risk provided by an embodiment of the present application;

[0049] Figure 10 is an interaction diagram of an interface display method provided by an embodiment of the present application;

[0050] Figure 11 is a flowchart of an interface display method provided by an embodiment of the present application. Detailed Embodiments

[0051] To clearly describe the technical solutions of the present application, the terms involved in the present application are described herein:

[0052] Screen data collection status: Under the Android mechanism, when collecting screen data, the MediaProjectionManager service needs to be called. The screen data collected through the MediaProjectionManager service can be used for video recording (screen recording) or for screen sharing.

[0053] Among them, screen sharing means that the user uses an application with screen sharing function to call the MediaProjectionManager service to share the collected screen data in real time to the other end, so that the user at the other end can view the content displayed on the screen of the local end. When the user uses the terminal device for screen sharing, the screen state of the terminal device can be called the screen sharing state.

[0054] Screen recording means calling the MediaProjectionManager service to generate and save the collected screen data as a video file. When the user uses the terminal device for screen recording, the screen state of the terminal device can be called 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 (conventional call mode), MODE_RINGTONE (ringtone mode), MODE_CALL_SCREENING (call display mode).

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

[0057] Privacy risk: It means that when in the screen sharing state, there is a risk of privacy information leakage;

[0058] Fraud risk: It means that there is a fraud behavior and it is in a fraud scenario.

[0059] Next, the technical solutions in the embodiments of the present application will be described in conjunction with the accompanying drawings in the embodiments of the present application. Among them, in the description of the embodiments of the present application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. The "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more than two.

[0060] Hereinafter, the terms "first", "second", and "third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first", "second", and "third" may explicitly or implicitly include one or more of such features.

[0061] With the rapid development of Internet technology, the convenience brought by the Internet cannot be ignored. However, various risks brought by the Internet have also attracted more and more attention. Many lawbreakers often steal users' privacy information through the Internet. For example, some lawbreakers induce users to download and install some application programs with screen sharing functions, such as meeting APPs, chat APPs, etc. Then, they use the installed application programs to share the screen with the users. As Figure 1 shown, during screen sharing, if a notification message pops up, such as a text message verification code or a message in the received email and other sensitive information (or called privacy information), there is a risk of leakage of sensitive information.

[0062] The interface display method provided by the embodiments of the present application can identify that when the local device (which can be called the local end) is in the screen sharing state by monitoring the screen state. For example, Figure 1 in the scenario shown, during the process of sending and displaying to the peer end, the popped-up notification message can be blocked. That is to say, the terminal device will not send and display the popped-up notification message to the peer end, so that the user at the peer end will not see the popped-up notification message and other such sensitive information during screen sharing, thus avoiding the leakage of sensitive information. If the terminal device also detects that there is a current risk of fraud at this time, the terminal device can add the shared interface to the security layer and then send and display it, so that the user at the peer end cannot see the display content of the shared interface, improving the security of information and property during screen sharing.

[0063] The interface display method provided by the embodiments of this application can be applied to terminal devices such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs). The embodiments of this application do not impose any restrictions on the specific types of terminal devices.

[0064] Exemplarily, Figure 2 is a schematic structural diagram of a terminal device 100 provided by the embodiments 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 interface 170D, a sensor module 180, a button 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 acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0065] It can be understood that the structure schematically shown in the embodiments of this application does 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 shown in the figure, or combine certain components, or split certain components, or have different component arrangements. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0066] It can be understood that the interface connection relationships between the modules schematically shown in the embodiments of this application are only 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 in the above embodiments, or a combination of multiple interface connection methods.

[0067] The software system of the terminal device 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. In the embodiments of the present application, taking the Android system with a layered architecture as an example, the software structure of the terminal device 100 will be exemplarily described.

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

[0069] As Figure 3 shown, the application packages may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

[0070] The application packages may also include a system manager, which is used to schedule and manage the system.

[0071] A security center is set in the system manager 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 scenarios.

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

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

[0075] As Figure 3 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 Flinger, etc.

[0076] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc. The window manager is also used to add the layer of the notification message to the privacy layer when the screen sharing status monitoring module monitors that the current state is the screen sharing state, and is used to set a security layer when the fraud risk monitoring module monitors that the current state is a fraud scenario, and send the information of the set security layer to the display compositor.

[0077] The content provider is used to store and obtain data, and make this data accessible to application programs. The data may include videos, images, audio, incoming and outgoing calls, browsing history and bookmarks, phone books, etc.

[0078] The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, etc. The view system can be used to build application programs. The display interface can be composed of one or more views. For example, a display interface including a SMS notification icon may include a view for displaying text and a view for displaying pictures.

[0079] The telephone manager is used to provide the communication function of the terminal device 100. For example, the management of call status (including connection, disconnection, etc.).

[0080] The resource manager provides various resources for application programs, such as localized strings, icons, pictures, layout files, video files, and so on.

[0081] The Media Projection Manager can set the extended interface Media Projection Manager interface, which can also be denoted as MediaProjectionManagerEX. The terminal device can call the Media Projection Manager service by calling the Media ProjectionManager interface to collect screen data. In the Android native mechanism, the call of the Media Projection Manager interface (or the call of the Media Projection Manager) means that the terminal device is performing screen sharing and / or screen recording.

[0082] The Notification Manager enables an application to display notification information in the status bar. It can be used to convey messages of an informative nature, which can disappear automatically after a short stay without user interaction. For example, the Notification Manager is used to inform that a download is complete, a message reminder, etc. The Notification Manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialogue window. For example, it can prompt text information in the status bar, emit a prompt sound, cause the terminal device to vibrate, and the indicator light to flash, etc. The Notification Manager can also, when the screen sharing state monitoring module monitors that the device is in the screen sharing state, send an instruction to the window manager to block the notification message. In response to the instruction of the Notification Manager, the window manager sets a privacy flag bit for the layer of the notification message and sends the information with the privacy flag bit set to the display compositor.

[0083] The display compositor can, when receiving the information with the privacy flag bit set, block the notification message, that is, when sending the shared interface to the peer, not send the layer of the notification message; it can also, when receiving the information for setting the security layer, no longer send the shared interface to the peer, but generate a blurred security layer and send it to the peer for display.

[0084] Android runtime includes the core libraries and the virtual machine. Android runtime is responsible for the scheduling and management of the Android system.

[0085] The core libraries include two parts: one part is the functional functions that need to be called by the Java language, and the other part is the core libraries of Android.

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

[0087] The system libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (such as: OpenGL ES), 2D graphics engine (such as: SGL), etc.

[0088] The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

[0089] The media library supports the playback and recording of a variety of common audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

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

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

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

[0093] In the technical solution of this application, the terminal device can monitor the current screen state. When the current screen state is in the screen sharing state, it can block the pop-up notification message when sending the display to the peer end, and can also add the current shared interface to the security layer to avoid information leakage. Next, first combine the above Figure 3 shown software structure framework to illustrate how to identify the screen sharing state.

[0094] When the terminal device is in the screen sharing state, it is necessary to call the Media Projection Manager interface. In this application, the screen sharing state monitoring module in the application layer registers a broadcast with the Media ProjectionManager in the application framework layer to monitor the call status of the Media Projection Manager interface. When it is necessary to collect screen data, the Media Projection Manager interface is in the called state. When the screen sharing state monitoring module monitors that the Media Projection Manager interface is called, it may be in the screen sharing state at this time, but it may also be in the screen recording state. Generally speaking, the screen recording file is automatically saved locally on the terminal device after recording, and will not be obtained by a third party without the user's active sharing operation. Therefore, it can be considered that the screen recording state is a safe usage scenario. However, in the screen sharing state, a third party 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 the screen recording state and the screen sharing state. If it is the screen recording state, it can be determined as a safe scenario and no corresponding processing is required. If it is the screen sharing state, it is determined that there is a privacy risk, and corresponding protection operations can be executed. The specific description of the protection operations can be seen in the following text, and will not be elaborated here for the time being.

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

[0096] Next, in the case where the Media Projection Manager interface is called, how to distinguish between the screen sharing state and the screen recording state will be described. In the screen sharing state, users often need to have voice communication with the participants in the meeting, so they need to enter the VoIP mode. In the screen recording state, the call mode is not necessarily the VoIP mode. Therefore, the screen sharing state and the screen recording state 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 current call mode obtained by the terminal device is: AudioManager.MODE_IN_COMMUNICATION (that is, the VoIP mode), combined with the Media Projection Manager interface being in the called state, it can be directly determined that the current screen state is the screen sharing state, rather than the screen recording state.

[0098] Optionally, in some scenarios, such as the game live broadcast scenario, it is necessary to call the Media ProjectionManager interface to record the screen, and the call mode will also enter the VoIP mode. However, in the game live broadcast scenario, there is no screen sharing, so there is no privacy risk. If the screen state in the game live broadcast scenario is simply judged based on the above-mentioned call state of the Media Projection Manager interface and the VoIP mode at this time, it will be misjudged as the screen sharing state. Based on this, the embodiments of the present application can define two judgment scenarios, one is a single scenario and the other is a combined scenario.

[0099] Here, the two judgment scenarios are introduced:

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

[0101] Optionally, if the terminal device is powered on for the first time, the historical call record is empty. In this case, no matter which application calls the Media Projection Manager interface, the screen sharing status and the screen recording status 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 the called state and the call mode is the VoIP mode, it can be determined that the current screen state is the screen sharing state rather than the screen recording state.

[0103] Combined scenario: When the Media Projection Manager interface is in the called state, the package name of the application that currently calls the Media Projection Manager interface exists in the historical call record. That is to say, the application that currently calls 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). At this time, it can be determined as a combined scenario.

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

[0105] The combined scenario can include the following four cases:

[0106] Case 1: When the screen sharing status monitoring module monitors that the Media Projection Manager interface enters the called state and the call mode is already in the operator call mode (MODE_IN_CALL mode), the preset screen sharing application whitelist can be combined to determine whether the current screen state is the screen sharing state or the screen recording state. It should be noted that the preset screen sharing application whitelist includes the package names of multiple application programs that support the screen sharing function.

[0107] For example, when the terminal device makes or receives a call with another device, it is in the carrier call mode. At this time, the screen sharing state monitoring module first calls AudioManager.getMode to obtain that the current call mode is MODE_IN_CALL. If it also monitors that the Media Projection Manager interface is in an uninvoked state, it is considered that there is a possibility of being in the screen sharing state. Alternatively, if the terminal device monitors that the Media Projection Manager interface is in an invoked state, obtains that the current call mode is MODE_IN_CALL, and the time when the terminal device enters the MODE_IN_CALL mode is earlier than the time when it monitors that the Media Projection Manager interface is invoked, it is also considered that there is a possibility of being in the screen sharing state.

[0108] When there is a possibility of being in the screen sharing 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 that currently invokes the Media Projection Manager interface exists in the preset screen sharing application whitelist, it indicates that the application supports the screen sharing function. Then the possibility that the current screen state is the screen sharing state is high, and the screen sharing state monitoring module can determine that the current is in the screen sharing state.

[0110] If the package name of the application that currently invokes the Media Projection Manager interface does not exist in the preset screen sharing application whitelist, it indicates that the application probably does not support the screen sharing function. Then the possibility that the current screen state is the screen recording state is high, and it can be determined as the screen recording state.

[0111] Optionally, when the package name of the application that currently invokes the Media Projection Manager interface does not exist in the preset screen sharing application whitelist, it can continue to determine whether the application that currently invokes the Media Projection Manager interface is the system-built screen recording software. If the application that currently invokes the Media Projection Manager interface is the system-built screen recording software, it can be determined that the current screen state is the screen recording state, rather than the screen sharing state; if the application that currently invokes the Media Projection Manager interface is not the system-built screen recording software, it can be determined that the current screen state is not the screen recording state, or continue to further distinguish the current screen state in combination with other conditions.

[0112] It should be noted that the preset whitelist of screen sharing applications includes the package names of multiple pre-installed applications, and these applications all support the screen sharing function. For example, the preset whitelist of screen sharing applications can cover the package names of current mainstream applications with screen sharing functions, and can also include the package names of applications with screen sharing functions added by users. Optionally, the preset whitelist of screen sharing applications can be downloaded from the cloud or automatically summarized and generated according to the usage records and attributes of the applications, and the present application does not limit this.

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

[0114] A call mode that is a non-operator call mode and is a non-VoIP mode can be called other call modes.

[0115] For example, when the screen sharing status monitoring module obtains that the call mode is any one of MODE_INVALID (non-call mode), MODE_NORMAL (normal call mode), MODE_RINGTONE (ringtone mode), and MODE_CALL_SCREENING (call display mode) by calling the AudioManager.getMode class, it indicates that the call mode is other call modes.

[0116] Case 3: If the screen sharing status monitoring module monitors that the Media Projection Manager interface is called, and then monitors that the call mode enters the operator call mode, at this time, based on the resource allocation logic of the Android system, the terminal device will stop calling the Media Projection Manager interface, that is, stop the current screen sharing state or screen recording state. In this case, there will be no privacy risk, and no subsequent protection operation needs to be performed.

[0117] Case 4: When 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 enters the VoIP mode, it can determine that it is not in the screen sharing state according to the preset screen sharing application whitelist. Or, when the terminal device detects that the Media Projection Manager interface is in an uncalled state, obtains that the call mode is MODE_IN_CALL mode, and the time when the terminal device enters the VoIP mode is earlier than the time when the Media Projection Manager interface is detected to be called, it is also considered that there is a possibility of being in the screen sharing state, and it can be determined that it is not in the screen sharing state according to the preset screen sharing application whitelist.

[0118] For example, in the game live broadcast scenario, the Media Projection Manager interface is called for screen recording and the call mode enters the VoIP mode. However, since it is not actually in the screen sharing state and there is no privacy risk, the preset screen sharing application whitelist can be used to further distinguish the current screen state.

[0119] Specifically, the screen sharing status monitoring module can view the application that currently calls the Media Projection Manager interface. If the application that currently calls the Media Projection Manager interface is the system's built-in screen recording software, it can be determined that the current state is screen recording; if the application that currently calls the Media Projection Manager interface is not the system's built-in screen recording software, it cannot be determined whether it is in the screen recording state. When it is impossible to determine whether it is in the screen recording state, the screen state can be further distinguished according to the preset screen sharing application whitelist. Specifically, when the package name of the application that currently calls the Media Projection Manager interface exists in the preset screen sharing application whitelist, it is determined that the current state is screen sharing; when the package name of the application that currently calls the Media Projection Manager interface is not in the preset screen sharing application whitelist, then the application that currently calls the Media Projection Manager interface is probably a third-party screen recording software, and it is determined that the current state is screen recording.

[0120] When the terminal device determines the current screen state, it can update the determination result as a call record in the historical call record. The historical call record can be stored in a mapping table according to the mapping relationship. For example, the call information for each call to the MediaProjection Manager interface can be expressed in the form of a key-value pair (a key value and a corresponding true value). Among them, the key value indicates whether the call to the Media Projection Manager interface this time is a call in the screen recording state or a screen sharing state, and the corresponding value value indicates the package name of the application that called the Media ProjectionManager interface this time. For example, if the meeting APP calls the Media Projection Manager interface once for screen sharing, a call information will be generated: screen sharing (key value) - meeting APP (value value).

[0121] Based on the above, the terminal device can distinguish whether the current screen state is in the screen sharing state or the screen recording state when the Media Projection Manager interface is called. Since the screen recording state is a scenario without privacy risks, subsequent protection operations do not need to be performed, and the current operation can be normally executed, such as normally recording the screen. If the current screen state is the screen sharing state, it is considered that there is a privacy risk, and the terminal device can perform subsequent protection operations to avoid information leakage and being scammed. For the specific implementation method of the protection operation, please refer to the following description.

[0122] First, the terminal device can perform a protection operation on the content of the notification message. When the terminal device calls the screen sharing state monitoring module to determine that the current screen state is the screen sharing state, the notification message can be added to the privacy layer to avoid the leakage of the notification message.

[0123] Second, when the terminal device calls the screen sharing state monitoring module to determine that the current screen state is the screen sharing state, if the terminal device determines that there is a fraud risk at its own end, the shared interface will be added to the security layer so that the other end cannot view the shared screen, avoiding the risk of being scammed.

[0124] To clearly describe how to implement the above protection operation, the mechanism of sending and displaying from the local end to the remote end in the screen sharing state is described here. Among them, the local end is the generating end of the shared interface, and the remote end is the receiving end of the shared interface.

[0125] When a user opens an application on a terminal device, each running application can display a corresponding window, and unique window content is correspondingly displayed in each window. 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. Moreover, the layers of different windows are independent of each other, and the window content corresponding to each layer can be completely obtained.

[0126] When the terminal device is in the screen sharing state, each application can transmit its window content transparently to the window manager. The window manager can obtain information about each window displayed on the current screen (such as identification, size, coordinates, etc.) based on the window content, so that in the screen sharing scenario, the terminal device can dynamically obtain information about windows of different layers, ensuring that changes in window size and position can be recorded.

[0127] In this application, layer overlay can be understood as the overlay of cache data corresponding to the layers (also known as "buffer overlay"). In the screen sharing scenario, the terminal device overlays the layers of multiple applications to generate a virtual screen interface. The terminal device can send the data of this virtual screen interface to the peer end. When the peer end receives the data of this virtual screen interface, it can display this virtual screen interface, and this process is called the terminal device sending and displaying to the peer end. Specifically, the terminal device can generate a virtual screen interface for each frame of layer overlay and send and display it to the peer end, thereby realizing screen sharing. For example Figure 1 as shown in, the window manager overlays the layers of the desktop, Window 1, Window 2, Window 3, and Notification Message 1 on the current screen to generate a virtual screen interface, and then sends and displays it to the peer end. Thus, the peer end device can display the same shared interface as the local end. Next, in combination with Figures 4 to 7 to illustrate the specific process and display method of the protection operation.

[0128] Figure 4 shows a flowchart of a protection operation method for protecting notification messages from being leaked. The method includes:

[0129] S401. Determine the screen sharing state.

[0130] The terminal device can monitor through the screen sharing state monitoring module that the current screen state is the screen sharing state. The specific method can refer to the foregoing, and will not be elaborated here.

[0131] S402. Set the screen sharing state flag bit.

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

[0133] S403. Monitor the change of the screen sharing state flag in the database.

[0134] Specifically, the notification manager can use the ContentObserver class to monitor the change of the status value of screen_sharing_state and obtain the specific status value (such as protect_status).

[0135] S404. When the screen sharing state flag indicates that the current is in the screen sharing state, set the layer of the notification message to the privacy layer.

[0136] When the notification manager monitors that the status value of the field screen_sharing_state switches to protect_status (or 1), add the layer of the notification message to the privacy layer.

[0137] Specifically, the method of adding the layer of the notification message to the privacy layer can include: the notification manager uses the window manager to instruct the display compositor to add a privacy label to the layer of the notification message. When the terminal device sends a display to the peer end, during the superposition process of the layers of multiple windows, the layer of the notification message with the privacy label can be blocked. That is, the display compositor does not superimpose the layer of the notification message when generating the virtual screen interface. Then the notification message will not be displayed in the generated virtual screen interface, and based on this virtual screen interface to send a display to the peer end, the notification message will not be displayed in the interface of the peer end.

[0138] Specifically, please refer to Figure 5 as shown Figure 5 Figure a in shows the schematic diagram of the interface where the notification message pops up in the local interface, Figure 5 Figure b in is the schematic diagram of the interface where the notification message popped up locally is not displayed in the interface of the peer end. Optionally, a prompt message can also be added to the local interface. Specifically, please refer to Figure 6 as shown Figure 6 Figure a in takes the form of a banner notification as an example to prompt the user that the peer end cannot see the notification message of the local end. Figure 6Figure b in [document] is a schematic diagram of the interface seen by the peer end, which does not include notification messages. The user of the terminal device can see the prompt information in the local interface, knowing that the peer end will not display the notification messages. Therefore, there is no need to immediately switch the screen or close the notification messages to avoid leakage of secrets. Without compromising the privacy information, the user operations are reduced and the user experience is improved.

[0139] S405. Close the screen sharing status.

[0140] The local interface can also display a close control for closing the screen sharing. For example, the "Stop Sharing" control shown in Figure a in [document]. The user can click this close control, and the terminal device responds to the user's operation of clicking the close control to close the screen sharing status, that is, stop the screen sharing. Figure 6 When the local end sends a display to the peer end, the terminal device can also add privacy labels to the layers of the prompt information and the close control to prevent the prompt information and the close control from being displayed in the peer end's interface. The method of adding privacy labels to the layers of the prompt information and the close control is the same as that described in the previous text for adding privacy labels to the layer of the notification message, and will not be elaborated here.

[0141]

[0142] When the terminal device stops screen sharing, for example, when the user clicks the close control as described in Figure a in [document], the screen sharing status monitoring module monitors the broadcast close notification of the Media Projection Manager interface, and can determine that the screen sharing status is closed. That is to say, the Media Projection Manager interface is in an uninvoked state. The screen sharing status monitoring module then uses the method function of Settings.Secure.putInt to set the status value of the field screen_sharing_state of the screen sharing status flag to normal_status (or 0), indicating that the current is not the screen sharing status. Figure 6

[0143] S406. Cancel the privacy layer.

[0144] When the notification manager monitors that the status value of the field screen_sharing_state switches to normal_status (or 0), it can instruct the privacy label of the layer that displays the notification message of the display compositor to be removed, so that the layer of the notification message will not be blocked, avoiding the inability to display the notification message in other scenarios. Optionally, the notification manager can also remove the privacy labels of the layers of the prompt information and the close control that have been added with privacy labels before.

[0145] ​​When the screen sharing of the terminal device stops, the layers of the prompt message and the close control will be destroyed and will not be displayed on the local side either.

[0146] When the terminal device is in a suspected fraud scenario (referred to as a fraud-related scenario or there is a fraud risk), it indicates the possibility of being defrauded. Then, the privacy risk is higher in the screen sharing state.

[0147] Specifically, the system steward of the terminal device monitors the status of the terminal device through the fraud risk monitoring module. For example, when the fraud risk monitoring module detects that the terminal device makes or answers a fraud call for more than one minute, replies to a fraud text message, or accesses a fraud website for more than a certain duration (such as more than 15 seconds), the fraud risk monitoring module will continue to monitor the behavior of the terminal device. If the fraud risk monitoring module detects fraud-related behaviors or operations such as pulling up payment or transferring money on the terminal device (the fraud app pulls up a financial payment application), the terminal device will record these characteristic behaviors based on these fraud-related behaviors and operations, and then input the characteristic behaviors into the fraud recognition model (which can also be the fraud risk monitoring module) in the terminal device for recognition. If the fraud recognition model recognizes that the characteristic behaviors indicate that the current terminal device has a fraud risk, the fraud risk value can be set to a value indicating a fraud-related scenario, or a fraud risk factor (i.e., the first factor) indicating a fraud-related scenario can be generated.

[0148] Optionally, the fraud risk monitoring module can also report the above characteristic behaviors to the cloud server, so that the cloud server can retrain the fraud recognition model based on the characteristic behaviors reported from the terminal side, thereby improving the accuracy of the fraud recognition model and further improving the accuracy of the recognition results. The cloud server can also send the latest fraud recognition model to the terminal device for use at an appropriate time.

[0149] Optionally, when there is a fraud risk, the terminal device can also display a prompt message indicating a fraud risk on the local interface, and at the same time, it can also send a text message to the emergency contact for prompt.

[0150] When the fraud risk monitoring module receives the screen sharing status flag transmitted by the screen sharing status monitoring module, and the status value of the screen sharing status flag indicates that the current is in the screen sharing state, it obtains the fraud risk value or queries whether there is a fraud risk factor. If the fraud risk value indicates that it is in a fraud scenario or there is a fraud risk factor, it adds the shared interface to the security layer and sends it to the peer end for display based on the security layer. If the fraud risk value indicates that it is not in a fraud scenario or there is no fraud risk factor, there is no need to add the shared interface to the security layer. Optionally, the security layer can be a completely black layer that does not display the content of any window; the security layer can also be a blurred layer, and no substantial display content will be shown in the blurred layer. Therefore, when sending the display based on the security layer, the peer end cannot see the content displayed on the screen of the local end.

[0151] For the specific process of protection operations in the case of fraud risks, please refer to Figure 7 as shown below, including:

[0152] S701. Determine the screen sharing status.

[0153] For the detailed description of this S701 step, please refer to the description of S401 above, and it will not be elaborated here.

[0154] S702. Judge whether it is currently in a fraud scenario.

[0155] Specifically, the terminal device can call the fraud risk monitoring module to obtain the monitored risk behaviors. If risk behaviors such as making or answering a fraud call for more than one minute, replying to a fraud text message, or accessing a fraud website for more than 15 seconds are detected, the terminal device can start the anti-fraud monitoring operation. The anti-fraud monitoring operation can include: monitoring fraud behaviors and monitoring fraud operations. When the terminal device monitors that there are fraud behaviors or fraud operations, it determines that it is currently in a fraud scenario and sets the fraud risk value to a value indicating that it is in a fraud scenario or generates a fraud risk factor.

[0156] S703. If it is currently in a fraud scenario, add the current shared interface to the security layer.

[0157] In a fraud-related scenario, the terminal device can call the window manager to set the current shared interface (Display) as a secure layer (or add it to the secure layer). Specifically, the window manager can add a security label to the shared interface to set it as a secure layer. Among them, the way to add a security label can be to set a secure layer flag bit for the shared interface. After that, the window manager can send the secure layer flag bit to the display compositor. Under the effect of the secure layer flag bit, the display compositor generates a virtual screen interface that is all black or blurred. The all-black or blurred virtual screen interface is the interface of the secure layer, and then sends the all-black or blurred virtual screen interface to the peer for display.

[0158] Figure 8 It is a schematic diagram of the interface when about to enter the screen sharing state in a fraud-related scenario. When in a fraud-related scenario, the terminal device initiates or receives a screen sharing message, and the interface shows Figure 8 the interface waiting to connect to screen sharing. In Figure 8 Figure a in Figure 8 , since the terminal device is in a fraud-related scenario, a content card with anti-fraud reminder can also be displayed in the interface waiting to connect to screen sharing. The content card includes reminder text, reminder icons; it can also include the closing path of anti-fraud protection, for example: Settings > Security > Anti-fraud Protection. Users can enter the settings page according to the closing path to turn off or turn on the anti-fraud reminder; the content card can also include a link control for anti-fraud cases, such as "View Anti-fraud Cases". Users can click on the link control for anti-fraud cases to view and learn anti-fraud cases. At the same time, a countdown second control can also be displayed in the content card. When the user clicks the second control "Got it" to end the countdown, the terminal device displays a prompt card as shown in Figure 8 Figure b in

[0159] When the shared interface is added to the secure layer, the terminal device can normally display the previous shared interface. And a prompt message can also be displayed in the shared interface of the terminal device, for example: "The anti-fraud firewall has been enabled, and the other party will not be able to see the content of your screen", specifically as shown in Figure 9 Figure a in Figure 9as shown in Figure b in

[0160] Optionally, if the user performs a screen recording operation after setting the security layer, the terminal device can also enter the screen recording state while in the screen sharing state, that is, the terminal device records the screen while sharing the screen. It should be noted that the mechanism of screen recording is similar to that of screen sharing, both of which stack multiple windows in the current shared interface to generate a virtual screen interface. In the screen recording state, the terminal device can store the virtual screen interface frame by frame. Then, when the security layer is added to the shared interface, the virtual screen interface recorded during the screen recording process is the interface of the security layer, that is, a completely black video file will be recorded.

[0161] S704. Close the screen sharing state.

[0162] For the specific description of S704, reference can be made to the description of S405 in the previous text, which will not be elaborated here.

[0163] S705. Cancel the security layer.

[0164] The terminal device can call the window manager to remove the security label of the current shared interface (Display) after stopping the screen sharing to cancel the security layer.

[0165] Next, in order to completely describe the technical solution of this application, a detailed description will be given in combination with Figure 10 the interaction diagram shown. It should be noted that the screen sharing state monitoring module can also be divided into: ScreenSharingProtection and ScreenSharingManager according to functions. The ScreenSharingProtection is used to manage the screen sharing state; the ScreenSharingManager is used to start and execute corresponding protection operations according to the screen sharing state. As Figure 10 shown, it includes:

[0166] S1001. The ScreenSharingProtection initializes when the terminal device boots and instructs the ScreenSharingManager to start broadcast listening.

[0167] Specifically, when the terminal device boots, the ScreenSharingProtection initializes. The ScreenSharingProtection can obtain the status of the protection switch in the security center of the system steward. If the status of the protection switch is on, it means that protection needs to be enabled for the terminal device at this time, so it instructs the ScreenSharingManager to start broadcast listening during initialization to monitor the call status of the MediaProjection Manager interface. If the status of the protection switch is off, it means that protection does not need to be enabled for the terminal device at this time, so it does not need to instruct the ScreenSharingManager to start broadcast listening during initialization, or instruct the ScreenSharingManager to close the broadcast listening.

[0168] S1002. The screen sharing protector initializes the screen sharing state.

[0169] Specifically, the screen sharing protector initializes the screen sharing state to a non-screen sharing state. For example, the flag bit for refreshing the screen sharing state (such as screen_sharing_state) is set to a state value representing the non-screen sharing state (such as normal_status or 0).

[0170] S1003. The screen sharing manager registers a broadcast with the Media Projection Manager.

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

[0172] S1004. The Media Projection Manager feeds back the callback broadcast information (onReceive) to the screen sharing manager.

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

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

[0175] Specifically, the screen sharing manager obtains the current call mode by calling the AudioManager.getMode() method, and determines whether the current screen state is in the screen sharing state by combining the current call mode and the call status of the Media Projection Manager interface. The specific process can refer to the relevant description in the previous text and will not be elaborated here.

[0176] The screen sharing manager can also add the package name of the application that calls the Media Projection Manager interface and the state value representing the screen sharing state to the historical call record (in the form of a hash table). The description of the historical call record can also refer to the relevant description in the previous text and will not be elaborated here.

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

[0178] S1007. In response to the instruction of the screen sharing manager, the screen sharing protector sets the status value of the screen sharing status flag bit.

[0179] The screen sharing manager can send an instruction to the screen sharing protector to instruct the screen sharing protector to update the field of the screen sharing status flag bit.

[0180] If it is determined that it is in the screen sharing state, the screen sharing manager can send an instruction to the screen sharing protector. In response to the instruction of the screen sharing manager, the screen sharing protector calls the method function Settings.Secure.putInt to set the status value of the field screen_sharing_state of the screen sharing status flag bit to switch to protect_status (or 1), indicating that it is currently in the screen sharing state.

[0181] When the screen sharing manager determines that it is not in the screen sharing state and can be determined to be in the screen recording state, the screen sharing manager can send an instruction to the screen sharing protector. In response to the instruction of the screen sharing manager, the screen sharing protector calls the method function Settings.Secure.putInt to set the status value of the field screen_sharing_state of the screen sharing status flag bit to switch to normal_status (or 0), indicating that it is currently in the non-screen sharing state. After that, the terminal device can abort the process and no longer perform subsequent protection operations.

[0182] S1008. The notification manager monitors the change of the field of the screen sharing status flag bit.

[0183] Specifically, the notification manager monitors the change of the status value of the field screen_sharing_state from the screen sharing protector through the class ContentObserver. After that, the steps of S1013 can also be executed.

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

[0185] Specifically, the fraud-related monitoring result can be characterized by a fraud-related risk value. When the fraud-related risk monitoring module detects behaviors such as the terminal device making or answering a fraud call for more than one minute, replying to a fraud text message, or accessing a fraud website for more than 15 seconds, and also detects a fraud-related behavior or operation, it can determine that there is a fraud-related risk. Based on this, a fraud-related risk value can be set as a value representing a fraud-related scenario or a fraud-related risk factor can be generated. Otherwise, it is determined that the fraud-related risk value is a value representing a non-fraud-related scenario or no fraud-related risk factor is generated.

[0186] The screen sharing manager can read the fraud-related risk value or query whether there is a fraud-related risk factor.

[0187] Optionally, the screen sharing manager can also send the status value of the screen sharing status flag bit to the fraud-related risk monitoring module, and the fraud-related risk monitoring module determines the current processing scope. The method by which the fraud-related risk monitoring module determines the current processing scope can refer to the logic of the screen sharing manager performing relevant operations, which will not be elaborated here.

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

[0189] S1011. The application behavior sequence collector reports the behavior sequence of the fraud-related behavior to the cloud server.

[0190] The cloud test server can then train the fraud-related risk monitoring module to update the fraud recognition model.

[0191] S1012. The screen sharing manager determines the current processing scope.

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

[0193] The screen sharing manager can combine the fraud-related risk value or whether there is a fraud-related risk factor to determine whether to add the shared interface to the security layer. When the fraud-related risk value is a value representing a non-fraud-related scenario or there is no fraud-related risk factor, it can be determined that the processing scope is to only hide the notification message. When the fraud-related risk value is a value representing a fraud-related scenario or there is a fraud-related risk factor, it can be determined that the processing scope is to hide the notification message and also add the shared interface to the security layer. For specific details, please refer to the previous description and will not be elaborated here.

[0194] Optionally, the execution order of the above S1010, S1011, and S1012 can be interchanged, and the embodiments of the present application do not make any limitations.

[0195] S1013. The notification manager, in the screen sharing state, instructs the display compositor to add the layer of the notification message to the privacy layer.

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

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

[0198] S1014. The display compositor, in response to the instruction of the notification manager, generates a virtual screen interface that does not include the layer of the notification message and sends it for display.

[0199] S1015. The screen sharing manager sends an instruction to join the security layer to the screen sharing protector.

[0200] S1016. The screen sharing protector, in response to the instruction sent by the screen sharing manager, sends a message to set the security layer to the window manager.

[0201] S1017. The window manager instructs the display compositor to add the shared interface to the security layer.

[0202] Specifically, when the status value of the screen sharing status flag changes from normal_status to protect_status, and the fraud monitoring result indicates the existence of fraud risk. At this time, the screen sharing manager determines that the processing scope is to add the shared interface to the security layer while hiding the notification message. The notification manager monitors that the status value of the screen sharing status flag changes from normal_status to protect_status, and then sends the status value of the screen sharing status flag to the display compositor. Based on the status value of the screen sharing status flag, the display compositor generates a completely black security layer and sends it to the peer for display.

[0203] S1014'. The display compositor, in response to the instruction of the window manager, generates a completely black security layer and sends it for display.

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

[0205] S1018. The screen sharing protector feeds back the callback broadcast information (onReceive) to the screen sharing manager.

[0206] When the user turns off the screen sharing status, the screen sharing manager will receive again the broadcast information called back by the screen sharing protector, and this broadcast information indicates that the screen sharing status is turned off.

[0207] S1019. The screen sharing manager determines that the screen sharing status is turned off according to the broadcast information.

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

[0209] S1021. In response to the instruction of the screen sharing manager, the screen sharing protector sets the status value of the screen sharing status flag bit.

[0210] When the screen sharing manager receives the broadcast message sent by the Media Projection Manager indicating that the screen sharing status is turned off, it can instruct the screen sharing protector to update the status value of the screen sharing status flag bit to the value representing the non-screen sharing status.

[0211] Specifically: The screen sharing manager sends an instruction to the screen sharing protector. In response to this instruction, the screen sharing protector updates the status value of the field screen_sharing_state of the screen sharing status flag bit to the status value representing the non-screen sharing status flag bit (for example, from protect_status to normal_status, or from 1 to 0).

[0212] When the screen sharing manager determines that it is not in the screen sharing status, if there is a security layer currently, the current processing scope includes: canceling the privacy layer and canceling the security layer; if there is no security layer currently, the current processing scope includes: canceling the privacy layer.

[0213] S1022. The notification manager monitors that the flag bit of the screen sharing status flag bit indicates the non-screen sharing status.

[0214] S1023. The notification manager cancels the privacy layer.

[0215] The notification manager monitors the change of the status value of the field screen_sharing_state from the screen sharing protector through the class ContentObserver. When it monitors that the screen sharing status flag bit indicates the non-screen sharing status, it removes the privacy label of the privacy layer.

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

[0217] S1025. The window manager cancels the security layer.

[0218] When the window manager receives or monitors that the screen sharing status flag bit indicates that the device is not in the screen sharing state, it cancels the security layer.

[0219] Optionally, the window manager can also receive a status notification message sent by the notification manager. Optionally, the notification manager can send a status notification message to the window manager when it monitors that the status value of the screen sharing status flag bit indicates that the device is not in the screen sharing state. In response to the status notification message, the window manager knows that the device is not currently in the screen sharing state and can cancel the security layer.

[0220] The above Figure 10 For the implementation principle and technical effects of the steps, reference can also be made to the relevant descriptions in the foregoing text, which will not be elaborated here.

[0221] The interface display method provided in the embodiments of this application is applied to an electronic device. As shown in Figure 11 it includes:

[0222] S1101. It is monitored that the Media Projection Manager interface is first called by a first application.

[0223] S1102A. When the call mode of the electronic device is in the Voice over Internet Protocol (VoIP) 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 to the other party.

[0224] S1102B. When the call mode of the electronic device is in the VoIP mode and there is a first factor, 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 to the other party. The first factor indicates that the electronic device has a risk of being involved in fraud.

[0225] S1103. It is monitored that the Media Projection Manager interface is called non-first by a second application. When the call mode of the electronic device is in other modes, a third interface is displayed. The third interface does not include the first prompt message and the second prompt message. The other call mode is a call mode that is different from both the VoIP mode and the operator call mode.

[0226] The Media Projection Manager interface is the interface of the Media Projection Manager. When the Media Projection Manager interface is in the called state, the terminal device may be in the screen recording state or the screen sharing state. We believe that the screen recording state is a safe scenario and can run normally without performing protection operations; while there is a risk of privacy information leakage in the screen sharing state, and corresponding protection operations need to be performed.

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

[0228] Specifically, the terminal device can not display the content of the notification message to the peer during the display process. That is to say, the peer will not see the notification message popped up on the local end, avoiding the notification message being seen by the peer and protecting the user's privacy information. At the same time, the interface displayed on the local end is the first interface containing the first prompt message, and the user can know from the first prompt message that the peer will not see the notification message popped up on the local end and does not need to worry about privacy information leakage, improving the user experience.

[0229] If the local end also detects the existence of the first factor (i.e., the fraud risk factor in the following text) at this time, or the fraud risk value is a value indicating a fraud scenario, it means that there is a fraud risk at the local end. The terminal device will not send any content in the second interface of the local end to the peer, so that the peer cannot see any content displayed in the second interface of the local end, comprehensively protecting the user's privacy information, avoiding the leakage of privacy information, and thus ensuring the user's property safety. At the same time, the local end can also display the second prompt message in the second interface, and the user can know from the second prompt message that the peer will not see any content in the second interface of the local end and does not need to worry about privacy information leakage, improving the user experience.

[0230] If the terminal device monitors that the Media Projection Manager interface is called by the second application non-first time, when the call mode of the electronic device is in other call modes, then the possibility of the terminal device entering the screen sharing state is low, and it is probably in the screen recording state. Therefore, the terminal device does not need to perform protection operations and can normally call the MediaProjection Manager interface. The local end also does not need to display content such as the first prompt message and the second prompt message.

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

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

[0233] When the Media Projection Manager interface is in a call 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 calling the Media Projection Manager interface for a non-first time.

[0234] The above-mentioned preset screen sharing application whitelist includes the package names of multiple application programs with screen sharing functions. If the package name of the third application exists in the preset screen sharing application whitelist and the terminal device first detects that the Media Projection Manager interface is called by the third application and then detects that the call mode enters the VoIP mode, it indicates that the possibility of entering the screen sharing state is high at this time. The terminal device can then perform corresponding protection operations, such as not sending a display notification message to the peer end, and not sending any content to the peer end when there is a risk of fraud. This can avoid the leakage of private information and comprehensively protect the user's information and property security.

[0235] In some possible implementations, the method further includes: after it is detected that the Media Projection Manager interface is called by a fourth application for a non-first time; when the call mode of the electronic device enters the VoIP mode, display a third interface; wherein, the third application and the fourth application are different, and the package name of the fourth application does not exist in the preset screen sharing application whitelist.

[0236] If the package name of the fourth application does not exist in the preset screen sharing application whitelist, it indicates that the fourth application probably does not have the screen sharing function. When the terminal device first detects that the Media Projection Manager interface is called by the fourth application for a non-first time and then detects that the call mode of the electronic device enters the VoIP mode, the possibility of the terminal device entering the screen sharing state is lower, and it is probably in the screen recording state. Therefore, the terminal device does not need to perform protection operations and can normally call the Media Projection Manager interface. The local end also does not need to display content such as a first prompt message and a second prompt message.

[0237] In some possible implementation manners, the method further includes: after the call mode of the electronic device enters the carrier call mode; when it is detected that the Media Projection Manager interface is called by a fifth application for a non-first time, display a first interface; when it is detected that the Media Projection Manager interface is called by the fifth application for a non-first time and there is a first factor, display a second interface; wherein, the package name of the fifth application exists in a 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 the screen sharing function. When the terminal device first detects that the call mode enters the carrier call mode and then detects that the MediaProjection Manager interface is called by the fifth application for a non-first time, the probability that the terminal device enters the screen sharing state is high. Therefore, the terminal device can perform corresponding protection operations. For the execution manner and technical effects of the protection operations, reference can be made to the relevant descriptions in this article, which will not be elaborated here.

[0239] In some possible implementation manners, the method further includes: after the call mode of the electronic device enters the carrier call mode; when it is detected that the Media Projection Manager interface is called by a sixth application for a non-first time, display a third interface; 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 the screen sharing function. When the terminal device first detects that the call mode enters the carrier call mode and then detects that the MediaProjection Manager interface is called by the sixth application for a non-first time, the probability that the terminal device enters the screen recording state is high. Therefore, the terminal device does not need to perform protection operations and can normally call the Media Projection Manager interface. The local end also does not need to display content such as a first prompt message and a second prompt message.

[0241] In some possible implementation manners, the method further includes: when the first interface is displayed, add a notification layer corresponding to a notification message to a privacy layer; generate a first virtual screen interface according to other layers outside the privacy layer, and send the first virtual screen interface to the peer end for display.

[0242] Specifically, the way to hide the notification message can be to add the corresponding notification layer of the notification message to the privacy layer. During the display process on the opposite end, the content in the layer added to the privacy layer will not appear in the first virtual screen interface. That is to say, when the terminal device sends the display to the opposite end, the window of the privacy layer will not be superimposed when synthesizing the first virtual screen interface. Therefore, based on such a first virtual screen interface to send the display to the opposite end, the opposite end will not display the window of the privacy layer, avoiding the leakage of the content of the privacy layer.

[0243] In some possible implementation manners, adding the corresponding notification layer of the notification message to the privacy layer includes: adding a privacy label to the notification layer so that the notification layer is added to the privacy layer.

[0244] Specifically, the way to add the notification layer to the privacy layer is to add a privacy label to the notification layer, thereby marking the layer that needs to be hidden. Optionally, the way to add the privacy label can be to set a privacy flag bit for the notification layer, thereby adding the notification layer to the privacy layer and avoiding sending the content of the notification layer to the opposite end.

[0245] In some possible implementation manners, the method further includes: detecting that the Media Projection Manager interface is not called; removing the privacy label of the notification layer, and displaying a third interface.

[0246] If the terminal device detects that the Media Projection Manager interface is not called, that is, the MediaProjection Manager stops collecting screen data, it means that the screen sharing state has ended. The terminal device can then move the notification layer out of the privacy layer, that is, remove the privacy label of the notification layer. At this time, since there is no risk of privacy information leakage, the first prompt message and the second question message will not be displayed on the third interface of the local end. If the privacy label is not removed in time, then when the terminal device enters the screen recording state again, a video file that does not contain the notification message may be recorded due to the privacy label not being removed, resulting in incomplete information in the video file obtained by screen recording, which may affect the user experience. Therefore, removing the privacy label of the notification layer in time can avoid the situation of incomplete information obtained in some scenarios such as screen recording.

[0247] In some possible implementation manners, the method further includes: when the second interface is displayed, adding the second interface to the security layer; generating a second virtual screen interface according to the security layer, and sending the second virtual screen interface to the opposite end, where the second virtual screen interface is a black interface.

[0248] Specifically, the method for protecting the content of the second interface from being displayed on the peer side can be to add the second interface to a secure layer. During the process of sending and displaying on the peer side, the interface added to the secure layer will not be displayed on the peer side. That is to say, when the terminal device sends and displays to the peer side, any window in the second interface will not be superimposed when synthesizing the second virtual screen interface. Instead, a completely black or completely blurred second virtual screen interface will be generated. Therefore, based on such a second virtual screen interface for sending and displaying to the peer side, the peer side will not display any content in the second interface, avoiding the leakage of privacy information.

[0249] In some possible implementation manners, adding the second interface to the secure layer includes: adding a security label to the second interface so that the second interface is added to the secure layer.

[0250] Specifically, the method for adding the second interface to the secure layer is to add a security label to the second interface, thereby marking the interface that needs to be hidden. Optionally, the method for adding a security label can be to set a security flag bit for the second interface, thereby adding the second interface to the secure layer and avoiding sending and displaying the content of the second interface to the peer side.

[0251] In some possible implementation manners, the method further includes: detecting that the Media Projection Manager interface is not called; removing the security label of the secure layer and displaying the third interface.

[0252] If the terminal device detects that the Media Projection Manager interface is not called, that is, the MediaProjection Manager stops collecting screen data, it indicates that the screen sharing state has ended. The terminal device can then remove the second interface from the secure layer, that is, remove the security label of the second interface. At this time, since there is no risk of privacy information leakage, the first prompt message and the second prompt message will not be displayed on the third interface of the local side either. If the security label is not removed in a timely manner, then when the terminal device enters the screen recording state again, a situation where a completely black video file is recorded due to the security label not being removed will occur, affecting the user experience. Therefore, timely removing the security label of the second interface can avoid the situation where screen information cannot be obtained in some scenarios such as screen recording.

[0253] Examples of the method provided in this application are described in detail above. It can be understood that, in order to implement the above functions, the corresponding device includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, combining the units and algorithm steps of each example described in the embodiments disclosed in this article, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described function for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0254] This application can divide the function modules of the interface display device according to the above method examples. For example, each function can be divided into each function module, or two or more functions can be integrated into one module. The above integrated module can be implemented in the form of hardware or in the form of a software function module. It should be noted that the division of modules in this application is illustrative, only a logical function division, and there can be other division methods in actual implementation.

[0255] For the specific manner in which the interface display device executes the interface display method and the beneficial effects produced, reference can be made to the relevant descriptions in the method embodiments, which will not be elaborated here.

[0256] This application embodiment also provides an electronic device, including the above-mentioned processor. The electronic device provided in this embodiment can be Figure 2 the terminal device 100 shown in the figure, which is used to execute the above interface display method. In the case of adopting an integrated unit, the terminal device can include a processing module, a storage module, and a communication module. Among them, the processing module can be used to control and manage the actions of the terminal device. For example, it can be used to support the terminal device to execute 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 to execute storing program codes and data, etc. The communication module can be used to support the communication between the terminal device and other devices.

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

[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 with Figure 2 the structure shown.

[0259] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the processor is caused to execute the interface display method described in any of the above embodiments.

[0260] An embodiment of the present application also provides a computer program product. When the computer program product runs on a computer, the computer is caused to execute the above-related steps to implement the interface display method in the above embodiments.

[0261] Among them, the electronic device, computer-readable storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be elaborated here.

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

[0263] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0264] When an integrated unit is implemented in the form of 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 solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions for causing a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods of the various embodiments of the present application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0265] The above content is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An interface display method, applied to an electronic device, characterized in that, The method includes: Detecting that the Media Projection Manager interface is first called by a first application; When the call mode of the electronic device is in the Voice over Internet Protocol (VoIP) mode, displaying a first interface, where the first interface includes a first prompt message and a notification message, and the first prompt message indicates that the notification message is in a non-display state for the other party; When the call mode of the electronic device is in the VoIP mode and there is a first factor, displaying a second interface, where the second interface includes a second prompt message, and the second prompt message indicates that the second interface is in a non-display state for the other party, and the first factor indicates that the electronic device has a fraud-related risk; Detecting that the Media Projection Manager interface is non-first called by a second application; When the call mode of the electronic device is in other call modes, displaying a third interface, where the third interface does not include the first prompt message and the second prompt message, and the other call mode is a call mode different from both the VoIP mode and the carrier call mode.

2. The method according to claim 1, wherein The method further includes: After detecting that the Media Projection Manager interface is non-first called by a third application; When the call mode of the electronic device enters the VoIP mode, displaying the first interface; When the call mode of the electronic device enters the VoIP mode and there is the first factor, displaying the second interface; Wherein, the package name of the third application exists in a preset whitelist of screen sharing applications.

3. The method according to claim 1 or 2, characterized in that, The method further includes: After detecting that the Media Projection Manager interface is non-first called by a fourth application; When the call mode of the electronic device enters the VoIP mode, displaying the third interface; Wherein, the third application and the fourth application are different, and the package name of the fourth application is not in the preset whitelist of screen sharing applications.

4. The method according to claim 1, characterized in that, The method further includes: After the call mode of the electronic device enters the carrier call mode; When detecting that the Media Projection Manager interface is non-first called by a fifth application, displaying the first interface; When detecting that the Media Projection Manager interface is non-first called by the fifth application and there is the first factor, displaying the second interface; Wherein, the package name of the fifth application exists in the preset whitelist of screen sharing applications.

5. The method according to claim 1 or 4, characterized in that, The method further includes: After the call mode of the electronic device enters the carrier call mode; When detecting that the Media Projection Manager interface is non-first called by a sixth application, displaying the third interface; Wherein, the package name of the sixth application is not in the preset whitelist of screen sharing applications.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: When displaying the first interface, adding the notification layer corresponding to the notification message to the privacy layer; Generate a first virtual screen interface according to other layers outside the privacy layer, and send and display the first virtual screen interface to the peer end.

7. The method according to claim 6, wherein The adding the corresponding notification layer of the notification message to the privacy layer includes: Adding a privacy label to the notification layer so that the notification layer is added to the privacy layer.

8. The method according to claim 7, wherein The method further includes: Detecting that the Media Projection Manager interface is not called; Removing the privacy label of the notification layer and displaying the third interface.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: When the second interface is displayed, adding the second interface to the security layer; Generate a second virtual screen interface according to the security layer, and send and display the second virtual screen interface to the peer end, where the second virtual screen interface is a black interface.

10. The method according to claim 9, wherein The adding the second interface to the security layer includes: Adding a security label to the second interface so that the second interface is added to the security layer.

11. The method according to claim 10, characterized in that, The method further includes: Detecting that the Media Projection Manager interface is not called; Removing the security label of the security layer and displaying the third interface.

12. An electronic device, characterized in that, including: A processor, a memory, and an interface; The processor, the memory, and the interface cooperate with each other to enable the electronic device to execute the method according to 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, and when the computer program is executed by the processor, the processor is enabled to execute the method according to any one of claims 1 to 11.

Images