CN106791168A - Information of mobile terminal guard method, device and mobile terminal - Google Patents

Abstract

The present invention provides a mobile terminal information protection method and device, which monitors the calling behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. The safe space for running resources, which is inaccessible in the normal mode of the system; when the screen capture interface is called, obtain the caller's identity information that calls the screen capture interface; judge whether the caller's identity is legal based on the caller's identity information, when calling When the identity of the caller is illegal, the calling behavior is rejected to prohibit the caller from capturing the screen. The method and device can effectively avoid operations such as stealthy screenshots of illegal applications, thereby reducing the risks of information leakage and fund theft, and can effectively improve system security. In addition, a mobile terminal is provided.

Description

Mobile terminal information protection method, device and mobile terminal

technical field

The present invention relates to the technical field of mobile terminal security, in particular, the present invention relates to a mobile terminal information protection method, device and mobile terminal.

Background technique

For safety considerations, some mobile terminals have set corresponding system protection modes to protect the safety of users in online transactions, online payments, bank inquiries, and the like. For example, the property isolation system of 360 mobile phones. On the one hand, the system prevents the intrusion of Trojan horses and counterfeit applications through the built-in security application store, ensuring the source security of applications from the source; on the other hand, it also builds special network channels , encrypt and transmit data such as account passwords to ensure data security during transmission. At the same time, financial management and other data are systematically isolated to prohibit illegal reading by malicious applications, which fundamentally guarantees the security of the user's payment environment.

For traditional mobile terminals, if an illegal application is unintentionally installed by the user in the system protection mode, and if the illegal application secretly screenshots the personal information pages of payment-related, wealth management-related, and banking-related applications, online transactions, online payments, etc. There will be a risk of information leakage or even fund theft under circumstances such as time, bank inquiries, etc., and the security needs to be improved.

Contents of the invention

The purpose of the present invention is to at least solve one of the above-mentioned technical defects, especially the technical defect of low security.

The present invention provides a mobile terminal information protection method, comprising the following steps:

Monitor the call behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. In the system protection mode, a security space is configured to provide running resources for the operation of predetermined applications. The security space is in the system normal mode inaccessible under

When the screen capture interface is called, obtain the identity information of the caller who calls the screen capture interface;

Judging whether the identity of the caller is legal according to the identity information of the caller, and rejecting the calling behavior to prohibit the caller from capturing the screen when the identity of the caller is illegal.

In one embodiment, the predetermined application includes at least one of a payment-related application, a wealth management-related application, and a bank-related application.

In one of the embodiments, the running resources include at least one of the application program itself, the application configuration data and the application user data, and the secure space includes storage space.

In one of the embodiments, the operation resource includes an operation protection policy, and the security space includes a storage space and a corresponding operation protection policy configuration environment.

In one of the embodiments, the screen capture interface is used for taking screenshots or recording screens.

In one of the embodiments, the system is an Android system, and the screen capture interface includes an adb shellscreencap command or a screenshot() method.

In one of the embodiments, the caller identity information is determined according to the common user account logged into the system; when the common user account is a predefined illegal user account, it is determined that the common user account is an illegal identity, Otherwise, it is determined to be legal.

In one embodiment, the system is an Android system, and the caller identity information includes the user identity certification UID of the common user account.

In one of the embodiments, the system is an Android system, and the process of judging whether the caller's identity is legal based on the caller's identity information includes: judging whether the user identity certificate UID of the ordinary user account is illegal by using the setScreenCaptureDisabled() method Identity's user certifies the UID and refuses to capture the screen when identified.

In one of the embodiments, the caller identity information is determined according to the application program to which the implementer process of the calling behavior belongs.

In one of the embodiments, the system is an Android system, and the caller identity information includes the package name of the calling application or the user identification UID of the calling application; when the package name of the calling application is a predefined illegal package name or calling When the user identification UID of the application is a predefined illegal user identification UID, it is determined that the package name of the calling application or the user identification UID of the calling application is an illegal identity, otherwise it is determined as a legal identity.

In one of the embodiments, the process of obtaining the identity information of the caller who calls the screen capture interface includes:

Obtain the process identification number PID of the calling application, and then obtain the package name of the calling application or the user identification UID of the calling application through the process identification number PID of the calling application.

In one of the embodiments, the process identification number PID of the calling application is acquired through a getCallingPid() method.

In one embodiment, the process of judging whether the caller's identity is legitimate according to the caller's identity information includes: judging whether the calling application is an application with a legal identity or an illegal identity through a pre-built white list or blacklist.

In one of the embodiments, the white list includes system applications.

In one of the embodiments, the system is an Android system, and an application whose user identity certificate UID is 1000 is identified as a system application and put into a white list.

In one of the embodiments, the information in the white list or black list is updated according to the update information of the server.

In one of the embodiments, if it is determined according to the historical record that the number of times the calling application has been rejected to capture the screen reaches a preset threshold, a warning message is issued.

The invention discloses a mobile terminal information protection device, comprising:

The monitoring module is used to monitor the calling behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. In the system protection mode, a security space for providing running resources for the operation of predetermined applications is configured. The space is not accessible in the normal mode of the system;

The acquisition module is used to obtain the identity information of the caller who calls the screen capture interface when the screen capture interface is called;

The processing module judges whether the caller's identity is legal according to the caller's identity information, and rejects the calling behavior to prohibit the caller from capturing the screen when the caller's identity is illegal.

In one embodiment, the predetermined application includes at least one of a payment-related application, a wealth management-related application, and a bank-related application.

In one of the embodiments, the running resources include at least one of the application program itself, the application configuration data and the application user data, and the secure space includes storage space.

In one of the embodiments, the operation resource includes an operation protection policy, and the security space includes a storage space and a corresponding operation protection policy configuration environment.

In one of the embodiments, the screen capture interface is used for taking screenshots or recording screens.

In one of the embodiments, the system is an Android system, and the screen capture interface includes an adb shellscreencap command or a screenshot() method.

In one of the embodiments, the caller identity information is determined according to the common user account logged into the system; when the common user account is a predefined illegal user account, it is determined that the common user account is an illegal identity, Otherwise, it is determined to be legal.

In one embodiment, the system is an Android system, and the caller identity information includes the user identity certification UID of the common user account.

In one of the embodiments, the system is an Android system, and the processing module is configured to: determine whether the user identity certification UID of the ordinary user account is an illegal user identity certification UID through the setScreenCaptureDisabled() method, and after determining Refuse to capture screen.

In one of the embodiments, the caller identity information is determined according to the application program to which the implementer process of the calling behavior belongs.

In one of the embodiments, the system is an Android system, and the caller identity information includes the package name of the calling application or the user identification UID of the calling application; when the package name of the calling application is a predefined illegal package name or calling When the user identification UID of the application is a predefined illegal user identification UID, it is determined that the package name of the calling application or the user identification UID of the calling application is an illegal identity, otherwise it is determined as a legal identity.

In one of the embodiments, the acquisition module is used for:

Obtain the process identification number PID of the calling application, and then obtain the package name of the calling application or the user identification UID of the calling application through the process identification number PID of the calling application.

In one of the embodiments, the process identification number PID of the calling application is acquired through a getCallingPid() method.

In one of the embodiments, the processing module judges whether the calling application is an application with a legal identity or an illegal identity through a pre-built white list or black list.

In one of the embodiments, the white list includes system applications.

In one of the embodiments, the system is an Android system, and an application whose user identity certificate UID is 1000 is identified as a system application and put into a white list.

In one of the embodiments, the information in the white list or black list is updated according to the update information of the server.

In one of the embodiments, the protection device further includes a warning module; the warning module is configured to: send a warning message if it is determined according to the historical record that the number of times the calling application is rejected from capturing the screen reaches a preset threshold.

The present invention also provides a mobile terminal, which includes:

touch-sensitive display;

one or more processors;

memory;

one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, the one or more program programs are configured to perform any A mobile terminal information protection method described in an embodiment.

The above-mentioned mobile terminal information protection method, device and mobile terminal monitor the calling behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. The safe space for running resources, which is inaccessible in the normal mode of the system; when the screen capture interface is called, obtain the caller's identity information that calls the screen capture interface; judge whether the caller's identity is legal based on the caller's identity information, when calling When the identity of the caller is illegal, the calling behavior is rejected to prohibit the caller from capturing the screen. When the screen capture interface is called, determine whether the caller is allowed to capture the screen by judging whether the caller’s identity is legal, which can effectively prevent illegal applications from secretly taking screenshots and other operations, thereby reducing the risk of information leakage and fund theft, and can effectively improve system security. .

For example, when the screen capture interface is called, determine whether to allow screen capture by judging whether the calling application is a legitimate or illegal application (for example, a whitelist or blacklist can be set), which can effectively prevent illegal applications from secretly taking screenshots and other operations; Alternatively, you can set all applications running in the system protection mode to prohibit screenshots, that is, when the screen capture interface is called, determine whether to allow it by judging the user identification UID of the ordinary user account corresponding to the login status of the calling application Capturing the screen (for example, applications running under a common user account whose user identity certificate UID=10 is prohibited from taking screenshots) can also effectively prevent illegal applications from sneaking screenshots and other operations, thereby reducing the risk of information leakage and fund theft, and can effectively improve system security. sex.

Additional aspects and advantages of the invention will be set forth in part in the description which follows, and will become apparent from the description, or may be learned by practice of the invention.

Description of drawings

The above and/or additional aspects and advantages of the present invention will become apparent and easy to understand from the following description of the embodiments in conjunction with the accompanying drawings, wherein:

Fig. 1 is a flowchart of a method for protecting mobile terminal information according to an embodiment;

FIG. 2 is a schematic diagram of a module of a mobile terminal information protection device according to an embodiment;

Fig. 3 shows a block diagram of a partial structure of a mobile phone related to a terminal provided by an embodiment of the present invention.

detailed description

Embodiments of the present invention are described in detail below, examples of which are shown in the drawings, wherein the same or similar reference numerals designate the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the figures are exemplary only for explaining the present invention and should not be construed as limiting the present invention.

Those skilled in the art will understand that unless otherwise stated, the singular forms "a", "an", "said" and "the" used herein may also include plural forms. It should be further understood that the word "comprising" used in the description of the present invention refers to the presence of said features, integers, steps, operations, elements and/or components, but does not exclude the presence or addition of one or more other features, Integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Additionally, "connected" or "coupled" as used herein may include wireless connection or wireless coupling. The expression "and/or" used herein includes all or any elements and all combinations of one or more associated listed items.

Those skilled in the art can understand that, unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which this invention belongs. It should also be understood that terms, such as those defined in commonly used dictionaries, should be understood to have meanings consistent with their meaning in the context of the prior art, and unless specifically defined as herein, are not intended to be idealized or overly Formal meaning to explain.

Those skilled in the art can understand that the "terminal" and "terminal equipment" used here not only include wireless signal receiver equipment, which only has wireless signal receiver equipment without transmission capabilities, but also include receiving and transmitting hardware. A device having receiving and transmitting hardware capable of performing bi-directional communication over a bi-directional communication link. Such equipment may include: cellular or other communication equipment, which has a single-line display or a multi-line display or a cellular or other communication equipment without a multi-line display; PCS (Personal Communications Service, personal communication system), which can combine voice, data Processing, facsimile and/or data communication capabilities; PDA (Personal Digital Assistant, Personal Digital Assistant), which may include radio frequency receiver, pager, Internet/Intranet access, web browser, notepad, calendar and/or GPS (Global Positioning System (Global Positioning System) receiver; a conventional laptop and/or palmtop computer or other device having and/or including a radio frequency receiver. As used herein, a "terminal", "terminal device" may be portable, transportable, installed in a vehicle (air, sea, and/or land), or adapted and/or configured to operate locally, and/or In distributed form, the operation operates at any other location on Earth and/or in space. The "terminal" and "terminal equipment" used here can also be communication terminals, Internet terminals, music/video playback terminals, such as PDAs, MIDs (Mobile Internet Devices, mobile Internet devices) and/or with music/video playback terminals. Functional mobile phones, smart TVs, set-top boxes and other devices.

Those skilled in the art can understand that the remote network device used here includes, but is not limited to, a computer, a network host, a single network server, a set of multiple network servers, or a cloud formed by multiple servers. Here, the cloud is composed of a large number of computers or network servers based on cloud computing (Cloud Computing), wherein cloud computing is a kind of distributed computing, a super virtual computer composed of a group of loosely coupled computer sets. In the embodiment of the present invention, the communication between the remote network equipment, the terminal equipment and the WNS server can be realized through any communication method, including but not limited to, mobile communication based on 3GPP, LTE, WIMAX, based on TCP/IP, UDP protocol Computer network communication and short-distance wireless transmission methods based on Bluetooth and infrared transmission standards.

In the following description, the system is the operating system of the mobile terminal, such as Android system, iOS mobile operating system and so on. In the following description, the Android system is used as an example, and the mobile terminal may be a smart terminal such as a mobile phone or a tablet computer.

Fig. 1 is a flowchart of a method for protecting information of a mobile terminal according to an embodiment.

The present invention provides a mobile terminal information protection method, comprising the following steps:

Step S100: Monitor the calling behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. Wherein, the system protection mode is configured with a security space for providing running resources for running predetermined applications, and the security space is inaccessible in the normal system mode.

In the system protection mode, the scheduled application will carry out strict security checks under the operation protection strategy, all transaction operations and payment operations related to funds will be strictly monitored, and the user's personal information will be strictly protected, such as chat records, text messages, etc. Leakage of user information such as verification codes. Among them, the predetermined application includes at least one of payment-related applications (such as WeChat APP, Alipay APP), financial management-related applications (such as Lufax APP) and banking-related applications (such as ICBC APP), so as to protect users Fund security and information security, of course, the predetermined application can also include all applications installed in the safe space in the system protection mode.

The running resources mentioned here can be understood as the application itself, the application configuration data (application configuration data), or the application user data (user's personal data). In this case, the security space mentioned above can be understood as a storage space. Of course, the running resource can also be understood as the running protection policy, and the security space can be understood as the storage space and its corresponding running protection policy configuration environment. Configuration environment for security protection measures such as Trojan horses.

In traditional technology, the system protection mode can be implemented with conventional "sandbox" isolation technology. But in this embodiment, it is implemented in multi-user mode. The Android system supports multi-user mode, which is similar to the multi-user mode of the WINDOWS system. The user data in the system logged in by different users is independent of each other and will not be affected by each other. Therefore, when the system is in the system normal mode when the administrator account (usually user identity certificate UID=0) logs in, the system is in the system protection mode when the system is in the common user account (such as user identity certificate UID=10) and logs in, and the system enters from the system normal mode The system protection mode is equivalent to switching the system from the administrator mode to the normal user mode. Since the multi-user mode can achieve a certain data isolation between users, it can realize the system security (application installation security, transaction security, user information security) of the user in the protection mode, and realize security isolation, which is better than the "sandbox" under certain circumstances. Isolation technology is much safer.

Therefore, the process of switching the system from the normal mode to the protected mode is equivalent to switching the system from an administrator account to a common user account. In the Android system, switch from an administrator account to an ordinary user account by calling the switchUser() method in the ActivityManager class. When the system is in the normal user account login state corresponding to the system protection mode, monitor the screen capture interface.

The screen capture interface is used to take screenshots or record screens, for example, it can be a command or a method. In this embodiment, the screen capture interface includes an adb shell screencap command or a screenshot() method, both of which can be used for screenshots. In the Android system, the adb shell screencap command is usually used when the PC is connected to the mobile terminal to take a screenshot. Therefore, if the mobile terminal is connected to the PC, the system protection mode of the PC terminal to the mobile terminal can be prevented by listening to the adb shell screencap command. Illegal screenshots of the apps below. The screenshot() method is usually used when capturing a screen at one end of the mobile terminal, and this method belongs to the SurfaceControl class.

In Android 5.0 and above systems, MediaProjection can be used to capture the screen, specifically, it can take screenshots and record screens. MediaProjection is managed and acquired by MediaProjectionManager. Screen capture requires the ImageReader class. The getSurface() method of this class obtains the surface and directly passes it to the MediaProjection.createVirtualDisplay() method. At this time, the interception can be performed. The Image of the current screen can be acquired through the ImageReader.acquireLatestImage() method, and can be saved as a Bitmap file after simple processing. Screen recording needs to use the MediaCodec class, which encodes the original screen data, and then encapsulates it into an mp4 format file through the MediaMuxer class and saves it. MediaCodec.createInputSurface() obtains a surface object and passes it to MediaProjection.createVirtualDisplay() to obtain the original multimedia data on the screen, and then reads the encoded output data of MediaCodec and then encapsulates it in MediaMuxer and converts it into mp4 for playback, thereby realizing screen recording. Therefore, the screen capture interface can also be the above-mentioned ImageReader.acquireLatestImage(), MediaProjection.createVirtualDisplay() and other methods.

In the following description, screen capture is taken as an example.

Step S200: When the screen capture interface is called, obtain the identity information of the caller who calls the screen capture interface.

The caller identity information may be calling application information or a user identity certification UID (USERIdentifier, user ID) of a common user account, and the calling application information may include a package name of the calling application or a user identity certification UID of the calling application. That is, the caller identity information is determined according to the user account logged into the system (that is, the common user account), and may also be determined according to the application program to which the implementer process of the calling behavior (such as the process identification number PID in the Android system) belongs. Here, two solutions are introduced for which applications are prohibited from obtaining the screen.

The first solution: determine whether to allow screen capture by judging whether the calling application is an application with a legal identity or an illegal identity (for example, a whitelist or a blacklist can be set). That is, you can allow some applications to take screenshots through the whitelist mechanism, or prohibit some applications from taking screenshots through the blacklist mechanism, or use a combination of whitelist and blacklist. Therefore, it is necessary to obtain the information of the calling application to determine whether to prohibit the application that captures the screen or Apps that allow screen capture.

The calling application information may include the calling application's package name (Package Name) or the calling application's user identification UID. In the Android system, the process of obtaining the information of the calling application that calls the screen capture interface includes: obtaining the process identification number PID (PROCESS Identifier, process ID) of the calling application, and then obtaining the package name or calling the calling application through the process identification number PID of the calling application. The application's user identification UID. The Binder.getCallingPid() method is used to obtain the process identification number PID of the currently calling application, so the process identification number PID of the calling application can be obtained through the Binder.getCallingPid() method. Binder is a class in Android, which inherits the IBinder interface, which is one of the Android system inter-process communication (IPC) methods, and the getCallingPid() method is a method for obtaining the process identification number PID of the currently calling application under the Binder class.

The following provides a piece of implementation code for obtaining the package name of the calling application through the process identification number PID of the calling application:

The second solution: you can set all applications running in the system protection mode to prohibit screenshots, that is, when the screen capture interface is called, the user identification UID of the ordinary user account corresponding to the login status of the calling application is determined. Determine whether to allow screen capture (for example, applications running under a common user account whose user identity certificate UID=10 are prohibited from capturing screens). Therefore, it is necessary to obtain the user identification UID of the common user account corresponding to the current system protection mode, so that all applications installed or running under the common user account are prohibited from taking screenshots. If the user identity certificate UID of the user account that logs in to the system meets the conditions, the application installed under the user account is a legal caller, otherwise it is an illegal caller.

After the identity information of the caller who calls the screen capture interface is acquired, step S300 is executed.

Step S300: Judging whether the identity of the caller is legal according to the information of the identity of the caller. If the identity of the caller is illegal, reject the calling behavior so as to prohibit the caller from capturing the screen. Rejecting the calling behavior can be understood as refusing to call the screen capture interface, or refusing to execute the calling command, or displaying an "error" message or "no right" message prompting the user, or directly displaying a blank page, which is not limited here. Continuing to take screenshots as an example, in the following description, the above identification of caller identity is realized by means of whitelist or blacklist.

For example, the system establishes a white list, and system applications are pre-added in the white list. Since the user identity certificate UID of the system application in the Android system is 1000, the application with the user identity certificate UID of 1000 is identified as a system application and included in the whitelist. In this way, it can be determined whether the calling application is a system application after obtaining the user identification UID of the calling application that calls the screen capture interface. The screen capture of the running system application is because the system application is safe enough. The present invention is only to prevent the illegal application from secretly capturing the screen, but not to prevent the screen capture of the system application. And gesture screenshots (such as three-finger screenshots or knuckle screenshots) and other screenshots that are realized through manual operations by the user. These screenshot methods ultimately need to be captured through SystemUI, and SystemUI belongs to the system application, and its user identification UID is 1000. Of course, third-party applications considered safe by the system designer can be added to the white list, and third-party applications considered safe by the user can also be added by the user, so that the third-party applications added by these users will be allowed when taking screenshots. The blacklist can also be connected to the server for data update, that is, the information of the blacklist can be updated according to the update information of the server. These whitelisted apps are legitimate callers.

Another example is that the system establishes a blacklist, adding third-party applications that the system designer considers unsafe to the blacklist, and users can also add third-party applications that they consider unsafe, so that when these third-party applications request screenshots, they refuse to take screenshots , further, the system may also issue prompt information for prompting the user. The blacklist can also be connected to the server for data update, that is, the information of the blacklist can also be updated according to the update information of the server. These blacklisted applications are callers with illegal identities. Further, if some third-party applications often request screenshots, a warning message may be sent to the user, for example, the user is advised to uninstall the application from the safe space in the system protection mode. Therefore, if it is determined according to the historical records that the number of times the application is rejected to capture the screen reaches a preset threshold (for example, 10 times), a warning message is issued.

Therefore, the process of judging whether the caller's identity is legitimate according to the caller's identity information may be: judging whether the calling application is a legitimate or illegal application through a pre-built white list or blacklist. The caller identity information includes the package name of the calling application or the user identification UID of the calling application. When the package name of the calling application is a predefined illegal package name or the UID of the user identification certificate of the calling application is a predefined illegal user identification UID, it is determined that the package name of the calling application or the user identification UID of the calling application is illegal identity, otherwise it is determined to be a legal identity. For example, the predefined illegal package name or the predefined illegal user identification UID can be the package name or user identification UID of the above-mentioned third-party application that the designer considers unsafe, and it is pre-listed in the blacklist, and the blacklist can be Connect to the server for data update.

For another example, it can be set that all applications running in the system protection mode are prohibited from taking screenshots, that is, when the screen capture interface is invoked, it is determined by judging the user identification UID of the ordinary user account corresponding to the login status of the calling application. Screen capture is allowed (for example, applications running under a common user account whose user identity certificate UID=10 are prohibited from taking screen captures).

When the system is an Android system, you can use the setScreenCaptureDisabled() method to determine whether the user identification UID of the ordinary user account is the user identification UID that is prohibited from capturing the screen and refuse to capture the screen after confirmation. For example, if the user identity certificate UID of the ordinary user account corresponding to the current system protection mode is 10, then public void setScreenCaptureDisabled(int userId, boolean disabled) can be used to prohibit all applications in the system protection mode from taking screenshots. The first parameter userId in the brackets is the ID of the parameter field, and the second parameter disabled is the status. All applications that can set userId=10 in this method are prohibited from taking screenshots.

Therefore, the process of judging whether the caller's identity is legal based on the caller's identity information may also be: judge whether the user identity certificate UID of the ordinary user account is an illegal user identity certificate UID through the setScreenCaptureDisabled() method, and after determining Refuse to capture screen. The identity information of the caller may be determined according to the common user account logged into the system. When the common user account is a predefined illegal user account, the common user account is determined to be an illegal identity, otherwise it is determined to be a legal identity.

So far, by monitoring and checking the screenshots of the applications in the system protection mode, some illegal applications can be prevented from secretly taking screenshots, and the system security is improved.

Fig. 2 is a schematic diagram of modules of a mobile terminal information protection device according to an embodiment.

Corresponding to the above mobile terminal information protection method, the present invention also provides a mobile terminal information protection device, which includes: a monitoring module 100 , an acquisition module 200 and a processing module 300 .

The monitoring module 100 is configured to monitor the calling behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. Wherein, the system protection mode is configured with a security space for providing running resources for the running of predetermined applications, and the security space is inaccessible in the normal mode of the system; the acquisition module 200 is used to acquire and call the screen capture interface when the screen capture interface is called. The identity information of the caller of the interface; the processing module 300 is used to judge whether the identity of the caller is legal according to the identity information of the caller, and when the identity of the caller is illegal, reject the calling behavior so as to prohibit the caller from capturing the screen.

When the system is in the login status of a common user account corresponding to the system protection mode, the monitoring module 100 monitors the screen capture interface. Wherein, the system protection mode is configured with a security space for providing running resources for running predetermined applications, and the security space is inaccessible in the normal system mode.

In the system protection mode, the scheduled application will carry out strict security checks under the operation protection strategy, all transaction operations and payment operations related to funds will be strictly monitored, and the user's personal information will be strictly protected, such as chat records, text messages, etc. Leakage of user information such as verification codes. Among them, the predetermined application includes at least one of payment-related applications (such as WeChat APP, Alipay APP), financial management-related applications (such as Lufax APP) and banking-related applications (such as ICBC APP), so as to protect users Fund security and information security, of course, the predetermined application can also include all applications installed in the safe space in the system protection mode.

The running resources mentioned here can be understood as the application itself, the application configuration data (application configuration data), or the application user data (user's personal data). In this case, the security space mentioned above can be understood as a storage space. Of course, the running resource can also be understood as the running protection policy, and the security space can be understood as the storage space and its corresponding running protection policy configuration environment. Configuration environment for security protection measures such as Trojan horses.

In traditional technology, the system protection mode can be implemented with conventional "sandbox" isolation technology. But in this embodiment, it is implemented in multi-user mode. The Android system supports multi-user mode, which is similar to the multi-user mode of the WINDOWS system. The user data in the system logged in by different users is independent of each other and will not be affected by each other. Therefore, when the system is in the system normal mode when the administrator account (usually user identity certificate UID=0) logs in, the system is in the system protection mode when the system is in the common user account (such as user identity certificate UID=10) and logs in, and the system enters from the system normal mode The system protection mode is equivalent to switching the system from the administrator mode to the normal user mode. Since the multi-user mode can achieve a certain data isolation between users, it can realize the system security (application installation security, transaction security, user information security) of the user in the protection mode, and realize security isolation, which is better than the "sandbox" under certain circumstances. Isolation technology is much safer.

Therefore, the process of switching the system from the normal mode to the protected mode is equivalent to switching the system from an administrator account to a common user account. In the Android system, switch from an administrator account to an ordinary user account by calling the switchUser() method in the ActivityManager class. When the system is in the normal user account login state corresponding to the system protection mode, the monitoring module 100 monitors the screen capture interface.

The screen capture interface is used to take screenshots or record screens, for example, it can be a command or a method. In this embodiment, the screen capture interface includes an adb shell screencap command or a screenshot() method, both of which can be used for screenshots. In the Android system, the adb shell screencap command is usually used when the PC is connected to the mobile terminal to take a screenshot. Therefore, if the mobile terminal is connected to the PC, the system protection mode of the PC terminal to the mobile terminal can be prevented by listening to the adb shell screencap command. Illegal screenshots of the apps below. The screenshot() method is usually used when capturing a screen at one end of the mobile terminal, and this method belongs to the SurfaceControl class.

In Android 5.0 and above systems, MediaProjection can be used to capture the screen, specifically, it can take screenshots and record screens. MediaProjection is managed and acquired by MediaProjectionManager. Screen capture requires the ImageReader class. The getSurface() method of this class obtains the surface and directly passes it to the MediaProjection.createVirtualDisplay() method. At this time, the interception can be performed. The Image of the current screen can be acquired through the ImageReader.acquireLatestImage() method, and can be saved as a Bitmap file after simple processing. Screen recording needs to use the MediaCodec class, which encodes the original screen data, and then encapsulates it into an mp4 format file through the MediaMuxer class and saves it. MediaCodec.createInputSurface() obtains a surface object and passes it to MediaProjection.createVirtualDisplay() to obtain the original multimedia data on the screen, and then reads the encoded output data of MediaCodec and then encapsulates it in MediaMuxer and converts it into mp4 for playback, thereby realizing screen recording. Therefore, the screen capture interface can also be the above-mentioned ImageReader.acquireLatestImage(), MediaProjection.createVirtualDisplay() and other methods.

In the following description, screen capture is taken as an example.

When the screen capture interface is called, the obtaining module 200 obtains the identity information of the caller who calls the screen capture interface.

The caller identity information may be calling application information or a user identity certification UID (USERIdentifier, user ID) of a common user account, and the calling application information may include a package name of the calling application or a user identity certification UID of the calling application. That is, the caller identity information is determined according to the user account logged into the system (that is, the common user account), and may also be determined according to the application program to which the implementer process of the calling behavior (such as the process identification number PID in the Android system) belongs. Here, two solutions are introduced for which applications are prohibited from obtaining the screen.

The first solution: the processing module 300 determines whether to allow screen capture by judging whether the calling application is an application with a legal identity or an illegal identity (for example, a whitelist or a blacklist can be set). That is, the processing module 300 can allow some applications to take screenshots through a whitelist mechanism, or prohibit some applications from taking screenshots through a blacklist mechanism, or use a combination of whitelist and blacklist, so it is necessary to obtain calling application information to determine whether to prohibit screenshots is still an app that allows screen capture.

The calling application information may include the calling application's package name (Package Name) or the calling application's user identification UID. In the Android system, the process of obtaining module 200's information of the calling application that calls the screen capture interface includes: obtaining the process identification number PID (PROCESS Identifier, process ID) of the calling application, and then obtaining the package of the calling application through the process identification number PID of the calling application. name or the UID of the user who invoked the application. The Binder.getCallingPid() method is used to obtain the process identification number PID of the currently calling application, so the obtaining module 200 can obtain the process identification number PID of the calling application through the Binder.getCalling process identification number PID() method. Binder is a class in Android, which inherits the IBinder interface, which is one of the Android system inter-process communication (IPC) methods, and the getCallingPid() method is a method for obtaining the process identification number PID of the currently calling application under the Binder class.

The following provides a piece of implementation code for obtaining the package name of the calling application through the process identification number PID of the calling application:

The second solution: the processing module 300 can set all applications running in the system protection mode to prohibit screenshots, that is, when the screen capture interface is called, the user identity of the ordinary user account corresponding to the login status of the calling application is judged. Prove the UID to determine whether to allow screen capture (for example, applications running under a common user account with user identity certificate UID=10 are prohibited from taking screen capture). Therefore, the acquiring module 200 needs to acquire the user identity certificate UID of the common user account corresponding to the current system protection mode, so that the processing module 300 can prohibit all applications installed or running under the common user account from taking screenshots. If the user identity certificate UID of the user account that logs in to the system meets the conditions, the application installed under the user account is a legal caller, otherwise it is an illegal caller.

After the obtaining module 200 obtains the calling application information or the user identity certificate UID of the common user account, the processing module 300 judges whether the identity of the caller is legal according to the identity information of the caller. The caller captures the screen. Rejecting the calling behavior can be understood as refusing to call the screen capture interface, or refusing to execute the calling command, or displaying an "error" message or "no right" message prompting the user, or directly displaying a blank page, which is not limited here. Continuing to take screenshots as an example, in the following description, the above identification of caller identity is realized by means of whitelist or blacklist.

For example, the system establishes a white list, and system applications are pre-added in the white list. Since the user identity certificate UID of the system application in the Android system is 1000, the application with the user identity certificate UID of 1000 is identified as a system application and included in the whitelist. In this way, after the obtaining module 200 obtains the UID of the user identity certificate of the calling application that calls the screen capture interface, the processing module 300 can determine whether the calling application is a system application. The screen capture of the running system application is because the system application is safe enough. The present invention is only to prevent the illegal application from secretly capturing the screen, but not to prevent the screen capture of the system application. And gesture screenshots (such as three-finger screenshots or knuckle screenshots) and other screenshots that are realized through manual operations by the user. These screenshot methods ultimately need to be captured through SystemUI, and SystemUI belongs to the system application, and its user identification UID is 1000. Of course, third-party applications considered safe by the system designer can be added to the white list, and third-party applications considered safe by the user can also be added by the user, so that the third-party applications added by these users will be allowed when taking screenshots. The blacklist can also be connected to the server for data update, that is, the information of the blacklist can be updated according to the update information of the server. These whitelisted apps are legitimate callers.

Another example is that the system establishes a blacklist, and adds third-party applications that the system designer thinks are unsafe to the blacklist, and users can also add third-party applications that they think are unsafe, so that the processing module 300 requests screenshots in these third-party applications. When rejecting the screenshot, further, the system can also issue a prompt message for prompting the user. The blacklist can also be connected to the server for data update, that is, the information of the blacklist can also be updated according to the update information of the server. These blacklisted applications are callers with illegal identities. Further, the mobile terminal information protection device may also include a warning module (not shown in the figure). If some third-party applications frequently request screenshots, the warning module may send a warning message to the user, for example, suggesting that the user uninstall the application from the safe space in the system protection mode. Therefore, if it is determined according to the historical records that the number of times the application is rejected to capture the screen reaches a preset threshold (for example, 10 times), the warning module sends a warning message.

Therefore, the process of judging whether the caller's identity is legitimate according to the caller's identity information may be: judging whether the calling application is a legitimate or illegal application through a pre-built white list or blacklist. The caller identity information includes the package name of the calling application or the user identification UID of the calling application. When the package name of the calling application is a predefined illegal package name or the UID of the user identification certificate of the calling application is a predefined illegal user identification UID, it is determined that the package name of the calling application or the user identification UID of the calling application is illegal identity, otherwise it is determined to be a legal identity. For example, the predefined illegal package name or the predefined illegal user identification UID can be the package name or user identification UID of the above-mentioned third-party application that the designer considers unsafe, and it is pre-listed in the blacklist, and the blacklist can be Connect to the server for data update.

For another example, the processing module 300 can set all applications running in the system protection mode to prohibit screenshots, that is, when the screen capture interface is invoked, the user identification UID of the ordinary user account corresponding to the login status of the invoking application is judged. To determine whether to allow screen capture (for example, applications running under a common user account whose user identity certificate UID=10 are prohibited from capturing screens).

When the system is an Android system, the processing module 300 can judge whether the user identity certificate UID of the common user account is the user identity certificate UID prohibited from capturing the screen through the setScreenCaptureDisabled() method and refuse to capture the screen after determination. For example, if the user identity certificate UID of the ordinary user account corresponding to the current system protection mode is 10, then public void setScreenCaptureDisabled(int userId, booleandisabled) can be used to realize that all applications in the system protection mode are prohibited from taking screenshots. The first parameter userId in the brackets is the ID of the parameter field, and the second parameter disabled is the status. All applications that can set userId=10 in this method are prohibited from taking screenshots.

Therefore, the process of judging whether the caller's identity is legal based on the caller's identity information may also be: judge whether the user identity certificate UID of the ordinary user account is an illegal user identity certificate UID through the setScreenCaptureDisabled() method, and after determining Refuse to capture screen. The identity information of the caller may be determined according to the common user account logged into the system. When the common user account is a predefined illegal user account, the common user account is determined to be an illegal identity, otherwise it is determined to be a legal identity.

The embodiment of the present invention also provides a mobile terminal. As shown in FIG. 3 , for convenience of description, only the parts related to the embodiment of the present invention are shown. For specific technical details not disclosed, please refer to the method part of the embodiment of the present invention. The terminal can be any terminal device including mobile phone, tablet computer, PDA (Personal Digital Assistant, personal digital assistant), POS (Point of Sales, sales terminal), vehicle-mounted computer, etc. Taking the terminal as a mobile phone as an example:

Fig. 3 shows a block diagram of a partial structure of a mobile phone related to a terminal provided by an embodiment of the present invention. Referring to FIG. 3 , the mobile phone includes: a radio frequency (Radio Frequency, RF) circuit 1510, a memory 1520, an input unit 1530, a display unit 1540, a sensor 1550, an audio circuit 1560, a wireless fidelity (wireless fidelity, Wi-Fi) module 1570, a processing Device 1580, and power supply 1590 and other components. Those skilled in the art can understand that the structure of the mobile phone shown in FIG. 3 does not constitute a limitation to the mobile phone, and may include more or less components than shown in the figure, or combine some components, or arrange different components.

The following is a specific introduction to each component of the mobile phone in conjunction with Figure 3:

The RF circuit 1510 can be used for sending and receiving information or receiving and sending signals during a call. In particular, after receiving the downlink information from the base station, it is processed by the processor 1580; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit 1510 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (Low Noise Amplifier, LNA), a duplexer, and the like. In addition, RF circuitry 1510 may also communicate with networks and other devices via wireless communications. The above-mentioned wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile Communication (Global System of Mobile communication, GSM), General Packet Radio Service (General Packet Radio Service, GPRS), Code Division Multiple Access (Code Division Multiple Access) , CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (Long Term Evolution, LTE), email, Short Messaging Service (Short Messaging Service, SMS), etc.

The memory 1520 can be used to store software programs and modules, and the processor 1580 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 1520 . Memory 1520 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, at least one application program required by a function (such as a sound playback function, an image playback function, etc.) and the like; Data created by the use of mobile phones (such as audio data, phonebook, etc.), etc. In addition, the memory 1520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage devices.

The input unit 1530 can be used to receive input numbers or character information, and generate key signal input related to user settings and function control of the mobile phone. Specifically, the input unit 1530 may include a touch panel 1531 and other input devices 1532 . The touch panel 1531, also referred to as a touch screen, can collect touch operations of the user on or near it (for example, the user uses any suitable object or accessory such as a finger or a stylus on the touch panel 1531 or near the touch panel 1531). operation), and drive the corresponding connection device according to the preset program. Optionally, the touch panel 1531 may include two parts, a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, and detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and sends it to the to the processor 1580, and can receive and execute commands sent by the processor 1580. In addition, the touch panel 1531 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1531 , the input unit 1530 may also include other input devices 1532 . Specifically, other input devices 1532 may include but not limited to one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), trackball, mouse, joystick, and the like.

The display unit 1540 may be used to display information input by or provided to the user and various menus of the mobile phone. The display unit 1540 may include a display panel 1541. Optionally, the display panel 1541 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an organic light-emitting diode (Organic Light-Emitting Diode, OLED), or the like. Furthermore, the touch panel 1531 may cover the display panel 1541, and when the touch panel 1531 detects a touch operation on or near it, it transmits to the processor 1580 to determine the type of the touch event, and then the processor 1580 determines the type of the touch event according to the The type provides a corresponding visual output on the display panel 1541 . Although in FIG. 3 , the touch panel 1531 and the display panel 1541 are used as two independent components to realize the input and input functions of the mobile phone, in some embodiments, the touch panel 1531 and the display panel 1541 can be integrated to form a mobile phone. Realize the input and output functions of the mobile phone.

The handset may also include at least one sensor 1550, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1541 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 1541 and/or when the mobile phone is moved to the ear. or backlight. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when it is stationary, and can be used to identify the application of mobile phone posture (such as horizontal and vertical screen switching, related Games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc.; as for other sensors such as gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc. repeat.

The audio circuit 1560, the speaker 1561, and the microphone 1562 can provide an audio interface between the user and the mobile phone. The audio circuit 1560 can transmit the electrical signal converted from the received audio data to the speaker 1561, and the speaker 1561 converts it into an audio signal for output; After being received, it is converted into audio data, and then the audio data is processed by the output processor 1580, and then sent to another mobile phone through the RF circuit 1510, or the audio data is output to the memory 1520 for further processing.

Wi-Fi is a short-distance wireless transmission technology. Through the Wi-Fi module 1570, mobile phones can help users send and receive emails, browse web pages, and access streaming media. It provides users with wireless broadband Internet access. Although Fig. 3 shows the Wi-Fi module 1570, it can be understood that it is not an essential component of the mobile phone, and can be completely omitted as required without changing the essence of the invention.

The processor 1580 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. By running or executing software programs and/or modules stored in the memory 1520, and calling data stored in the memory 1520, execution Various functions and processing data of the mobile phone, so as to monitor the mobile phone as a whole. Optionally, the processor 1580 may include one or more processing units; preferably, the processor 1580 may integrate an application processor and a modem processor, wherein the application processor mainly processes operating systems, user interfaces, and application programs, etc. , the modem processor mainly handles wireless communications. It can be understood that the foregoing modem processor may not be integrated into the processor 1580 .

The mobile phone also includes a power supply 1590 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 1580 through the power management system, so that functions such as charging, discharging, and power consumption management can be realized through the power management system.

Although not shown, the mobile phone may also include a camera, a Bluetooth module, etc., which will not be repeated here.

In the embodiment of the present invention, the processor 1580 included in the terminal also has the following functions: monitor the calling behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. In the system protection mode, the configuration is useful To provide a safe space for running resources for the operation of the scheduled application, the safe space is not accessible in the normal mode of the system; when the screen capture interface is called, obtain the caller's identity information that calls the screen capture interface; judge the call based on the caller's identity information Whether the identity of the caller is legal. When the identity of the caller is illegal, the calling behavior is rejected to prohibit the caller from capturing the screen. That is, the processor 1580 is capable of executing the above-mentioned mobile terminal information protection method, which will not be repeated here.

The above-mentioned mobile terminal information protection method, device and mobile terminal monitor the calling behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. The safe space for running resources, which is inaccessible in the normal mode of the system; when the screen capture interface is called, obtain the caller's identity information that calls the screen capture interface; judge whether the caller's identity is legal based on the caller's identity information, when calling When the identity of the caller is illegal, the calling behavior is rejected to prohibit the caller from capturing the screen. When the screen capture interface is called, determine whether the caller is allowed to capture the screen by judging whether the caller’s identity is legal, which can effectively prevent illegal applications from secretly taking screenshots and other operations, thereby reducing the risk of information leakage and fund theft, and can effectively improve system security. .

For example, when the screen capture interface is called, determine whether to allow screen capture by judging whether the calling application is a legitimate or illegal application (for example, a whitelist or blacklist can be set), which can effectively prevent illegal applications from secretly taking screenshots and other operations; Alternatively, you can set all applications running in the system protection mode to prohibit screenshots, that is, when the screen capture interface is called, determine whether to allow screen capture by judging the UID of the ordinary user account corresponding to the login status of the calling application ( For example, applications running under a common user account with UID=10 are prohibited from taking screenshots), which can also effectively prevent illegal applications from sneaking screenshots and other operations, thereby reducing the risk of information leakage and fund theft, and can effectively improve system security.

The invention discloses the following scheme:

A1, a mobile terminal information protection method, comprising the steps of:

Monitor the call behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. In the system protection mode, a security space is configured to provide running resources for the operation of predetermined applications. The security space is in the system normal mode inaccessible under

When the screen capture interface is called, obtain the identity information of the caller who calls the screen capture interface;

Judging whether the identity of the caller is legal according to the identity information of the caller, and rejecting the calling behavior to prohibit the caller from capturing the screen when the identity of the caller is illegal.

A2. According to the mobile terminal information protection method described in A1, the predetermined application includes at least one of payment-related applications, wealth management-related applications, and bank-related applications.

A3. According to the mobile terminal information protection method described in A1, the running resources include at least one of the application program itself, the application configuration data and the application user data, and the secure space includes storage space.

A4. According to the mobile terminal information protection method described in A1, the operation resource includes an operation protection policy, and the security space includes a storage space and a corresponding operation protection policy configuration environment.

A5. According to the mobile terminal information protection method described in A1, the screen capture interface is used for taking screenshots or recording screens.

A6, according to the mobile terminal information protection method described in A1, the system is an Android system, and the screen capture interface includes an adb shell screencap command or a screenshot () method.

A7. According to the mobile terminal information protection method described in A1, the caller identity information is determined according to the ordinary user account logged into the system; when the ordinary user account is a predefined illegal user account, it is determined that the ordinary user account The user account is an illegal identity, otherwise it is determined to be a legal identity.

A8. According to the mobile terminal information protection method described in A7, the system is an Android system, and the caller identity information includes the user identity certification UID of the common user account.

A9, according to the mobile terminal information protection method described in A8, the system is an Android system, and the process of judging whether the caller's identity is legal according to the caller's identity information includes: judging the user of the common user account by the setScreenCaptureDisabled() method Whether the identification UID is the user identification UID of an illegal identity and refuses to capture the screen after determination.

A10. According to the mobile terminal information protection method described in A1, the caller identity information is determined according to the application program to which the caller process belongs.

A11, according to the mobile terminal information protection method described in A10, the system is an Android system, and the caller identity information includes the package name of the calling application or the user identity certificate UID of the calling application; when the package name of the calling application is predefined When the illegal package name of the calling application or the user identification UID of the calling application is a predefined illegal user identification UID, the package name of the calling application or the user identification UID of the calling application is determined to be illegal, otherwise it is determined to be legal.

A12, according to the mobile terminal information protection method described in A11, the process of obtaining the identity information of the caller who calls the screen capture interface includes:

Obtain the process identification number PID of the calling application, and then obtain the package name of the calling application or the user identification UID of the calling application through the process identification number PID of the calling application.

A13. According to the mobile terminal information protection method described in A12, the process identification number PID of the calling application is acquired through the getCallingPid() method.

A14. According to the mobile terminal information protection method described in A1, the process of judging whether the caller’s identity is legal according to the caller’s identity information includes: judging whether the calling application is a legal identity or a pre-built white list or blacklist Application of illegal identity.

A15. According to the mobile terminal information protection method described in A14, the white list includes system applications.

A16. According to the mobile terminal information protection method described in A15, the system is an Android system, and an application whose user identity certificate UID is 1000 is identified as a system application and included in the whitelist.

A17. According to the mobile terminal information protection method described in A14, the information in the white list or black list is updated according to the update information of the server.

A18. According to the mobile terminal information protection method described in A14, if it is determined according to historical records that the number of times that the calling application is rejected to capture the screen reaches a preset threshold, a warning message is issued.

B19. A mobile terminal information protection device, comprising:

The monitoring module is used to monitor the calling behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. In the system protection mode, a security space for providing running resources for the operation of predetermined applications is configured. The space is not accessible in the normal mode of the system;

The acquisition module is used to obtain the identity information of the caller who calls the screen capture interface when the screen capture interface is called;

The processing module judges whether the caller's identity is legal according to the caller's identity information, and rejects the calling behavior to prohibit the caller from capturing the screen when the caller's identity is illegal.

B20. According to the mobile terminal information protection device described in B19, the predetermined application includes at least one of payment-related applications, wealth management-related applications and bank-related applications.

B21. According to the mobile terminal information protection device described in B19, the running resources include at least one of the application program itself, the application configuration data and the application user data, and the secure space includes storage space.

B22. According to the mobile terminal information protection device described in B19, the operation resource includes an operation protection policy, and the security space includes a storage space and a corresponding operation protection policy configuration environment.

B23. According to the mobile terminal information protection device described in B19, the screen capture interface is used for taking screenshots or recording screens.

B24, according to the mobile terminal information protection device described in B19, the system is an Android system, and the screen capture interface includes an adb shell screencap command or a screenshot () method.

B25. According to the mobile terminal information protection device described in B19, the caller identity information is determined according to the ordinary user account logged into the system; when the ordinary user account is a predefined illegal user account, it is determined that the ordinary user account The user account is an illegal identity, otherwise it is determined to be a legal identity.

B26. According to the mobile terminal information protection device described in B25, the system is an Android system, and the caller identity information includes the user identity certification UID of the common user account.

B27, according to the mobile terminal information protection device described in B26, the system is an Android system, and the processing module is used for: judging whether the user identity certification UID of the common user account is an illegal user identity by the setScreenCaptureDisabled () method Certify the UID and refuse to capture the screen when identified.

B28. According to the mobile terminal information protection device described in B19, the caller identity information is determined according to the application program to which the implementer process of the calling behavior belongs.

B29, according to the mobile terminal information protection device described in B18, the system is an Android system, and the caller identity information includes calling the package name of the application or calling the user identity certificate UID of the application; when the package name of the calling application is predefined When the illegal package name of the calling application or the user identification UID of the calling application is a predefined illegal user identification UID, the package name of the calling application or the user identification UID of the calling application is determined to be illegal, otherwise it is determined to be legal.

B30. According to the mobile terminal information protection device described in B29, the acquisition module is used for:

Obtain the process identification number PID of the calling application, and then obtain the package name of the calling application or the user identification UID of the calling application through the process identification number PID of the calling application.

B31. According to the mobile terminal information protection device described in B30, obtain the process identification number PID of the calling application through the getCallingPid() method.

B32. According to the mobile terminal information protection device described in B19, the processing module judges whether the calling application is an application with a legal identity or an illegal identity through a pre-built white list or black list.

B33. According to the mobile terminal information protection device described in B32, the white list includes system applications.

B34. According to the mobile terminal information protection device described in B33, the system is an Android system, and an application whose user identity certificate UID is 1000 is identified as a system application and is included in the whitelist.

B35. According to the mobile terminal information protection device described in B32, the information in the white list or black list is updated according to the update information of the server.

B36, according to the mobile terminal information protection device described in B32, the protection device also includes a warning module; the warning module is used to: if it is determined according to historical records that the number of times that the calling application is rejected to capture the screen reaches a preset threshold, then Issue a warning message.

C37, a kind of mobile terminal, it comprises:

touch-sensitive display;

one or more processors;

memory;

one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs are configured to perform as The mobile terminal information protection method described in any one of A1 to A18.

It should be understood that although the various steps in the flow chart of FIG. 1 are displayed sequentially according to the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in Fig. 1 may include multiple sub-steps or multiple stages, these sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and the execution order is not necessarily performed sequentially, but may be performed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

The above descriptions are only part of the embodiments of the present invention. It should be pointed out that those skilled in the art can make some improvements and modifications without departing from the principles of the present invention. It should be regarded as the protection scope of the present invention.

Claims (10)

1. A mobile terminal information protection method, is characterized in that, comprises the steps: Monitor the call behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. In the system protection mode, a security space is configured to provide running resources for the operation of predetermined applications. The security space is in the system normal mode inaccessible under When the screen capture interface is called, obtain the identity information of the caller who calls the screen capture interface; Judging whether the identity of the caller is legal according to the identity information of the caller, and rejecting the calling behavior to prohibit the caller from capturing the screen when the identity of the caller is illegal. 2 . The method for protecting mobile terminal information according to claim 1 , wherein the predetermined application includes at least one of payment-related applications, wealth management-related applications and bank-related applications. 3 . 3. The mobile terminal information protection method according to claim 1, wherein the running resources include at least one of the application program itself, the application configuration data and the application user data, and the secure space includes storage space . 4. The method for protecting information of a mobile terminal according to claim 1, wherein the operation resource includes an operation protection policy, and the security space includes a storage space and a corresponding operation protection policy configuration environment. 5. The method for protecting mobile terminal information according to claim 1, wherein the screen capture interface is used for taking screenshots or recording screens. 6. The mobile terminal information protection method according to claim 1, wherein the system is an Android system, and the screen capture interface includes an adb shell screencap command or a screenshot () method. 7. The mobile terminal information protection method according to claim 1, wherein the identity information of the caller is determined according to the common user account logged into the system; when the common user account is a predefined illegal user account , it is determined that the common user account is an illegal identity, otherwise it is determined that it is a legal identity. 8. The method for protecting mobile terminal information according to claim 7, wherein the system is an Android system, and the caller identity information includes the user identity certification UID of the common user account. 9. A mobile terminal information protection device, characterized in that it comprises: The monitoring module is used to monitor the calling behavior of the screen capture interface triggered in the system protection mode logged in as an ordinary user account. In the system protection mode, a security space for providing running resources for the operation of predetermined applications is configured. The space is not accessible in the normal mode of the system; The acquisition module is used to obtain the identity information of the caller who calls the screen capture interface when the screen capture interface is called; The processing module judges whether the caller's identity is legal according to the caller's identity information, and rejects the calling behavior to prohibit the caller from capturing the screen when the caller's identity is illegal. 10. A mobile terminal, characterized in that it comprises: touch-sensitive display; one or more processors; memory; one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs are configured to perform as The mobile terminal information protection method described in any one of claims 1 to 8.