A method, device and medium for protecting user privacy information

By judging the permission restrictions of cross-application call operations and the running status of the calling application on the mobile terminal, unauthorized permission access is prohibited, which solves the security problem of user privacy information when calling across applications and achieves more detailed permission management. .

CN113806694BActive Publication Date: 2025-01-21BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202010536383.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-06-12
Publication Date
2025-01-21
Estimated Expiration
2040-06-12

AI Technical Summary

Technical Problem

Existing mobile terminal technologies are difficult to meticulously manage cross-application permission calls, resulting in user privacy information being accessed without authorization.

Method used

By learning the cross-application calling operation, it can be determined whether the callee is involved in permission restrictions, and whether the calling application is running in the foreground. If the callee involves permission restrictions and the calling application is not running in the foreground, the calling operation is prohibited.

Benefits of technology

Effectively protect user privacy information, prevent unauthorized access, and enhance the security of user privacy.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113806694B_ABST
    Figure CN113806694B_ABST
Patent Text Reader

Abstract

The present disclosure provides a method, device and medium for protecting user privacy information, the method comprising: obtaining a cross-application call operation, obtaining a caller application and a callee of the call operation; determining whether the callee involves permission restrictions, and determining whether the caller application is running in the foreground; when the callee involves permission restrictions and the caller application is not running in the foreground, prohibiting the execution of the call operation. In the present disclosure, after obtaining a cross-application call operation, when the callee involves permission restrictions and the caller application is not running in the foreground, prohibiting the execution of the call operation, and denying access to the permissions of the callee, thereby protecting user privacy information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of mobile terminal data processing technology, and in particular to a method, device and medium for protecting user privacy information. Background Art

[0002] Many applications in mobile terminals involve users' private information, such as identity information, contact information, multimedia data, etc.

[0003] After a first application is newly installed and obtains the permission of another installed second application, during actual use, the user does not know when the first application will call the second application, that is, does not know when the first application uses the permission related to user privacy in the second application.

[0004] As users' awareness of privacy protection increases, more detailed permission management methods are urgently needed. Summary of the invention

[0005] In order to overcome the problems existing in the related art, this article provides a method, device and medium for protecting user privacy information.

[0006] According to a first aspect of an embodiment of this document, a method for protecting user privacy information is provided, including:

[0007] Acquire a cross-application call operation, and acquire a caller application and a callee of the call operation;

[0008] Determine whether the called party involves permission restrictions, and determine whether the calling party application is running in the foreground;

[0009] When the callee involves permission restrictions and the caller application is not running in the foreground, the calling operation is prohibited from being executed.

[0010] In one implementation, determining whether the calling application is running in the foreground includes:

[0011] Determine the running state of the process of the calling application, and when the running state belongs to a set state set, determine that the calling application is running in the foreground; when the running state does not belong to the set state set, determine that the calling application is not running in the foreground.

[0012] In one embodiment, the method further comprises: determining a set of set states;

[0013] The determining and setting the state set includes: setting a priority threshold of a process in an activity management service;

[0014] Determine a priority set that is greater than or equal to the priority threshold; determine an operating state set corresponding to the priority set according to a mapping relationship between a process priority in an activity management service and an operating state in a permission management service, and use the operating state set as a set state set.

[0015] In one embodiment, setting the priority threshold of a process in an activity management service includes: determining a priority set of processes of the calling application in the activity management service when the calling application has a component located in a top-level interface during operation, and determining the lowest priority from the priority set as the priority threshold.

[0016] In one implementation, the obtaining of the cross-application call operation includes: receiving call information of an instant call function of an application operation management class, or receiving call information of a continuous call function of an application operation management class.

[0017] According to a second aspect of the embodiments of this document, a device for protecting user privacy information is provided, including:

[0018] An acquisition module, used to acquire cross-application call operations, and acquire a caller application and a callee of the call operation;

[0019] A determination module, used to determine whether the called party involves permission restrictions, and to determine whether the calling party application is running in the foreground;

[0020] The processing module is used to prohibit the execution of the calling operation when the called party involves permission restrictions and the calling party application is not running in the foreground.

[0021] In one implementation, the determination module is used to determine whether the calling application is running in the foreground using the following method:

[0022] Determine the running state of the process of the calling application, and when the running state belongs to a set state set, determine that the calling application is running in the foreground; when the running state does not belong to the set state set, determine that the calling application is not running in the foreground.

[0023] In one embodiment, the device further comprises: a first determining module, configured to determine a set of set states;

[0024] The first determining module includes:

[0025] A first setting module, used to set a priority threshold of a process in an activity management service;

[0026] A second determination module, configured to determine a priority set greater than or equal to the priority threshold;

[0027] The third determination module is used to determine the running state set corresponding to the priority set according to the mapping relationship between the process priority in the activity management service and the running state in the authority management service, and use the running state set as the set state set.

[0028] In one embodiment, the first setting module is used to set the priority threshold of the process in the activity management service using the following method: determine the priority set of the process of the calling application in the activity management service when the calling application has a component located in the top-level interface during operation, and determine the lowest priority from the priority set as the priority threshold.

[0029] In one embodiment, the acquisition module is used to obtain the cross-application call operation by using the following method: receiving call information of an instant call function of an application operation management class, or receiving call information of a continuous call function of an application operation management class.

[0030] According to a third aspect of the embodiments of this document, a device for protecting user privacy information is provided, including:

[0031] processor;

[0032] a memory for storing processor-executable instructions;

[0033] Wherein, the processor is configured to:

[0034] Acquire a cross-application call operation, and acquire a caller application and a callee of the call operation;

[0035] Determine whether the called party involves permission restrictions, and determine whether the calling party application is running in the foreground;

[0036] When the callee involves permission restrictions and the caller application is not running in the foreground, the calling operation is prohibited from being executed.

[0037] According to a fourth aspect of the embodiments of this document, a non-transitory computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of a mobile terminal, the mobile terminal is enabled to perform a method for protecting user privacy information, the method comprising:

[0038] Acquire a cross-application call operation, and acquire a caller application and a callee of the call operation;

[0039] Determine whether the called party involves permission restrictions, and determine whether the calling party application is running in the foreground;

[0040] When the callee involves permission restrictions and the caller application is not running in the foreground, the calling operation is prohibited from being executed.

[0041] The technical solution provided by the embodiments of this article may include the following beneficial effects: after knowing the cross-application calling operation, when the called party involves permission restrictions and the calling party application is not running in the foreground, the calling operation is prohibited and the access to the permissions of the called party is denied, thereby protecting user privacy information.

[0042] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the present invention.

[0044] Figure 1 is a flow chart showing a method for protecting user privacy information according to an exemplary embodiment;

[0045] Figure 2 is a flow chart showing a method for protecting user privacy information according to an exemplary embodiment;

[0046] Figure 3 is a structural diagram of a device for protecting user privacy information according to an exemplary embodiment;

[0047] Figure 4 The figure is a structural diagram of a device for protecting user privacy information according to an exemplary embodiment. DETAILED DESCRIPTION

[0048] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this document. Instead, they are merely examples of devices and methods consistent with some aspects of this document as detailed in the appended claims.

[0049] The present disclosure provides a method for protecting user privacy information. Figure 1 , Figure 1 FIG. 1 is a flow chart showing a method for protecting user privacy information according to an exemplary embodiment. Figure 1 As shown, this method includes:

[0050] Step S11, obtaining a cross-application calling operation, and obtaining a calling application and a called party of the calling operation.

[0051] Step S12, determining whether the called party involves permission restrictions, and determining whether the calling party application is running in the foreground.

[0052] Step S13: When the called party is subject to permission restrictions and the calling party application is not running in the foreground, the calling operation is prohibited.

[0053] The called party is an application, such as a contact application, a photo album application, a call log application, etc. Alternatively, the called party is a system service, such as a positioning service, a recording service.

[0054] In one implementation, when the callee involves permission restrictions and the caller application is running in the foreground, the calling operation is allowed to be performed.

[0055] In this embodiment, a cross-application calling operation is learned, and when the called party is subject to permission restrictions and the calling application is not running in the foreground, the calling operation is prohibited and access to the permissions of the called party is denied, thereby protecting user privacy information.

[0056] In an embodiment of the present disclosure, a method for protecting user privacy information is provided. In this method, the permission management service in the framework layer is improved so that the permission management service can execute steps S11 and S12, and a permission management application is set in the application layer so that the permission management application constructs a notification message according to the results of the permission management service executing steps S11 and S12.

[0057] like Figure 2 As shown, when application A calls system service B, a cross-application call is generated. The corresponding management service of system service B in the framework layer receives the call request, and calls the corresponding application operation management class call function when verifying permissions. The permission management service learns of this call and learns of the caller application A and the callee B of the call function, and determines whether the callee B involves permission restrictions, and whether the caller application A is running in the foreground. When the callee B does not involve permission restrictions, the call operation is allowed to be executed, and when the caller application A is running in the foreground, the call operation is allowed to be executed. When the callee B involves permission restrictions and the caller application A is not running in the foreground, the call operation is prohibited. The permission management service determines the identification information of the caller application based on the caller application, and determines the representation information of the callee based on the callee. The permission management service notifies the permission management application of the determined processing result of the call operation, and also notifies the permission management application of the identification information of the caller application and the representation information of the callee (for example, notifying the permission management application in an asynchronous and cross-process manner). The permission management application records the identification information of the caller application, the representation information of the callee, and the processing result of the call operation, and may also organize notification information based on the identification information of the caller application, the representation information of the callee, and the processing result of the call operation to display this notification information.

[0058] In this embodiment, step S11 acquires the cross-application call operation, including: receiving the call information of the instant call function of the application operation management (AppOpsManager) class, or receiving the call information of the continuous call function of the application operation management (AppOpsManager) class.

[0059] The continuously calling function is the startOp function, which is an application programming interface (API) in the AppOpsManager class. The parameters of the StartOp function include: the operation name (op) in string format, the source identifier (uid) in integer format, and the package name (packageName) in string format. The operation name refers to the name of the called party, the source identifier is the label code of the caller application, and the package name refers to the unique identifier of the caller application in the system. The StartOp function corresponds to the function of continuously executing calls within a certain period of time.

[0060] The instant call function is the noteOp function, which is an application programming interface (API) in the AppOpsManager class. The parameters of the noteOp function include: the operation name (op) in string format, the source identifier (uid) in integer format, and the package name (packageName) in string format. The operation name refers to the name of the called party, the source identifier is the label code of the caller application, and the package name refers to the unique identifier of the caller application in the system. The StartOp function corresponds to a single execution call.

[0061] The present disclosure provides a method for protecting user privacy information, which includes: Figure 1 The method shown in the figure, and: in step S12, the determining whether the calling application is running in the foreground includes:

[0062] Determine the running state of the process of the calling application, and when the running state belongs to a set state set, determine that the calling application is running in the foreground; when the running state does not belong to the set state set, determine that the calling application is not running in the foreground.

[0063] In one embodiment, the method further includes: determining a set state set. The determining the set state set includes: setting a priority threshold of a process in an activity management service (ActivityManageService). Determining a priority set greater than or equal to the priority threshold; determining an operating state set corresponding to the priority set according to a mapping relationship between a process priority in the activity management service and an operating state in the permission management service, and using the operating state set as the set state set.

[0064] For example, the priorities of processes in the ActivityManageService are as follows from high to low:

[0065] PROCESS_STATE_TOP;

[0066] UID_STATE_FOREGROUND_SERVICE;

[0067] PROCESS_STATE_BOUND_FOREGROUND_SERVICE;

[0068] PROCESS_STATE_IMPORTANT_FOREGROUND etc.

[0069] The process priority in the activity management service and the running status in the authority management service form a mapping relationship, as shown in Table 1.

[0070] Table 1

[0071]

[0072]

[0073] Set the priority threshold of the process in the activity management service (ActivityManageService) to PROCESS_STATE_FOREGROUND_SERVICE. Determine that the priority set greater than or equal to the priority threshold includes PROCESS_STATE_TOP and PROCESS_STATE_FOREGROUND_SERVICE. According to the mapping relationship between the process priority in the activity management service and the running state in the authority management service, determine that the running state set corresponding to the priority set includes UID_STATE_TOP and UID_STATE_FOREGROUND_SERVICE, and use the running state set as the set state set.

[0074] In one embodiment, setting a priority threshold of a process in an activity management service includes: determining a priority set of a process of a caller application in the activity management service when the caller application has a component located in a top-level interface during operation, and determining a lowest priority from the priority set as the priority threshold.

[0075] The following is an explanation using several examples.

[0076] Example 1: When a user starts a map navigation application, and the user interface of the map navigation application is displayed on the terminal interface, the functional components of the map navigation application are displayed on the interface, and the priority of the process of the map navigation application in the activity management service is PROCESS_STATE_TOP. When the map navigation application calls the system's positioning service at this time, it is determined that the called party involves permission restrictions and the calling application is running in the foreground, and the call operation is allowed to be executed. When a user starts an instant messaging application, the instant messaging application interface and the notification bar are displayed on the terminal interface, and the notification bar displays a prompt message that triggers the map navigation application to navigate in the background, when the notification bar of the map navigation application is displayed on the terminal interface, the priority of the process of the map navigation application in the activity management service is PROCESS_STATE_FOREGROUND_SERVICE. When the map navigation application calls the system's positioning service at this time, it is determined that the called party involves permission restrictions and the calling application is running in the foreground, and the call operation is allowed to be executed.

[0077] The map navigation application moves to the background, and no related components are displayed on the terminal interface. When calling the system's positioning service at this time, if it is determined that the called party is subject to permission restrictions and the calling application is running in the background, this calling operation is prohibited.

[0078] Example 2: When the user starts an image processing application and the image processing application user interface is displayed on the terminal interface, the image processing functional components are displayed on the interface, and the image processing application process priority in the activity management service is PROCESS_STATE_TOP. When the image processing application calls the system's clipboard service at this time, it is determined that the callee involves permission restrictions and the caller application is running in the foreground, and the call operation is allowed.

[0079] When the user starts the instant messaging application, the terminal interface displays the interface of the instant messaging application and the notification bar, and the notification bar displays the prompt information that triggers the image processing application to process in the background, and the notification bar of the image processing application is displayed on the terminal interface, the priority of the image processing application process in the activity management service is PROCESS_STATE_FOREGROUND_SERVICE. When the image processing application calls the clipboard service at this time, it is determined that the callee involves permission restrictions and the caller application is running in the foreground, and the call operation is allowed to be executed.

[0080] The image processing application is transferred to the background, and no related components are displayed on the terminal interface. When the clipboard service is called at this time, if it is determined that the callee involves permission restrictions and the caller application is running in the background, the call operation is prohibited.

[0081] Example 3: The user starts an image processing application. When the user interface of the image processing application is displayed on the terminal interface, the image processing functional components are displayed on the interface, and the priority of the image processing application process in the activity management service is PROCESS_STATE_TOP. When the image processing application calls the photo album application at this time, it is determined that the called party involves permission restrictions and the calling application is running in the foreground, so the call operation is allowed.

[0082] When the user starts the instant messaging application, the terminal interface displays the interface of the instant messaging application and the notification bar, and the notification bar displays the prompt information that triggers the image processing application to process in the background, and the notification bar of the image processing application is displayed on the terminal interface, the priority of the image processing application process in the activity management service is PROCESS_STATE_FOREGROUND_SERVICE. When the image processing application calls the photo album application at this time, it is determined that the called party involves permission restrictions and the calling application is running in the foreground, and the call operation is allowed to be executed.

[0083] The image processing application is transferred to the background, and no related components are displayed on the terminal interface. When the photo album application is called at this time, if it is determined that the called party is subject to permission restrictions and the calling application is running in the background, the calling operation is prohibited.

[0084] The present disclosure provides a method for protecting user privacy information, which includes: Figure 1 The method shown, and step S12, judging whether the called party involves permission restriction, includes: when the called party is an application, judging whether the called party belongs to a set application set; when the called party belongs to a set application set, determining that the called party involves permission restriction; when the called party does not belong to a set application set, determining that the called party does not involve permission restriction. When the called party is a system service, judging whether the called party belongs to a set service set; when the called party belongs to a set service set, determining that the called party involves permission restriction; when the called party does not belong to a set service set, determining that the called party does not involve permission restriction.

[0085] The set application set includes the system default applications involving permission restrictions and / or the user-marked applications involving permission restrictions. The set service set includes the system default services involving permission restrictions and / or the user-marked services involving permission restrictions.

[0086] The present disclosure provides a device for protecting user privacy information. Figure 3 , Figure 3 FIG. 1 is a structural diagram of a device for protecting user privacy information according to an exemplary embodiment. Figure 3 As shown, the device comprises:

[0087] The acquisition module 301 is used to obtain the cross-application calling operation, and obtain the calling application and the called party of the calling operation;

[0088] The judgment module 302 is used to judge whether the called party involves permission restriction, and whether the calling party application is running in the foreground;

[0089] The processing module 303 is used to prohibit the execution of the calling operation when the called party involves permission restrictions and the calling party application is not running in the foreground.

[0090] The present disclosure provides a device for protecting user privacy information, which includes: Figure 3 The device shown, and the judgment module 302 is used to use the following method to determine whether the calling application is running in the foreground: determine the running state of the process of the calling application, and when the running state belongs to a set state set, determine that the calling application is running in the foreground; when the running state does not belong to the set state set, determine that the calling application is not running in the foreground.

[0091] In one embodiment, the device further comprises: a first determining module, configured to determine a set of set states;

[0092] The first determining module includes:

[0093] A first setting module, used to set a priority threshold of a process in an activity management service;

[0094] A second determination module, configured to determine a priority set greater than or equal to the priority threshold;

[0095] The third determination module is used to determine the running state set corresponding to the priority set according to the mapping relationship between the process priority in the activity management service and the running state in the authority management service, and use the running state set as the set state set.

[0096] In one embodiment, the first setting module is used to set the priority threshold of the process in the activity management service using the following method: determine the priority set of the process of the calling application in the activity management service when the calling application has a component located in the top-level interface during operation, and determine the lowest priority from the priority set as the priority threshold.

[0097] The present disclosure provides a device for protecting user privacy information, which includes: Figure 3 The device shown in the figure has an acquisition module 301, which is used to obtain the cross-application calling operation by using the following method: receiving the calling information of the instant calling function of the application operation management class, or receiving the calling information of the continuous calling function of the application operation management class.

[0098] Figure 4 4 is a block diagram of an apparatus 400 for protecting user privacy information according to an exemplary embodiment. For example, the apparatus 400 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0099] Reference Figure 4 , the device 400 may include one or more of the following components: a processing component 402 , a memory 404 , a power component 406 , a multimedia component 408 , an audio component 410 , an input / output (I / O) interface 412 , a sensor component 414 , and a communication component 416 .

[0100] The processing component 402 generally controls the overall operation of the device 400, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 402 may include one or more processors 320 to execute instructions to complete all or part of the steps of the above-described method. In addition, the processing component 402 may include one or more modules to facilitate interaction between the processing component 402 and other components. For example, the processing component 402 may include a multimedia module to facilitate interaction between the multimedia component 408 and the processing component 402.

[0101] The memory 404 is configured to store various types of data to support operations on the device 400. Examples of such data include instructions for any application or method operating on the device 400, contact data, phone book data, messages, pictures, videos, etc. The memory 404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0102] The power supply component 406 provides power to the various components of the device 400. The power supply component 406 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device 400.

[0103] The multimedia component 408 includes a screen that provides an output interface between the device 400 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 408 includes a front camera and / or a rear camera. When the device 400 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0104] The audio component 410 is configured to output and / or input audio signals. For example, the audio component 410 includes a microphone (MIC), and when the device 400 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 404 or sent via the communication component 416. In some embodiments, the audio component 410 also includes a speaker for outputting audio signals.

[0105] I / O interface 412 provides an interface between processing component 402 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0106] The sensor assembly 414 includes one or more sensors for providing various aspects of the status assessment of the device 400. For example, the sensor assembly 414 can detect the open / closed state of the device 400, the relative positioning of components, such as the display and keypad of the device 400, and the sensor assembly 414 can also detect the position change of the device 400 or a component of the device 400, the presence or absence of user contact with the device 400, the orientation or acceleration / deceleration of the device 400, and the temperature change of the device 400. The sensor assembly 414 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 414 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 414 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0107] The communication component 416 is configured to facilitate wired or wireless communication between the device 400 and other devices. The device 400 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 416 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 416 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0108] In an exemplary embodiment, the apparatus 400 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above method.

[0109] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 404 including instructions, and the instructions can be executed by the processor 320 of the device 400 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0110] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary techniques in the art that are not disclosed herein. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present invention are indicated by the following claims.

[0111] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A method for protecting user privacy information, characterized in that: include: Acquire a cross-application call operation, and acquire a caller application and a callee of the call operation; Determine whether the called party involves permission restrictions, and determine whether the calling party application is running in the foreground; When the called party is subject to permission restrictions and the calling party application is not running in the foreground, prohibiting execution of the calling operation; The determining whether the calling application is running in the foreground includes: Determine the running state of the process of the calling application, and when the running state belongs to a set state set, determine that the calling application is running in the foreground; when the running state does not belong to the set state set, determine that the calling application is not running in the foreground; the set state set is obtained based on the priority threshold of the process in the activity management service.

2. The method according to claim 1, characterized in that The method further includes: determining a set of set states; The determining of the set state set includes: setting a priority threshold of a process in the activity management service; determining a priority set greater than or equal to the priority threshold; determining an operating state set corresponding to the priority set according to a mapping relationship between the process priority in the activity management service and the operating state in the authority management service, and using the operating state set as the set state set; The setting of the priority threshold of the process in the activity management service includes: determining a priority set of the process of the caller application in the activity management service when the caller application has a component located in the top-level interface during operation, and determining the lowest priority from the priority set as the priority threshold.

3. The method according to claim 1, characterized in that The obtaining of the cross-application calling operation includes: receiving calling information of an instant calling function of an application operation management class, or receiving calling information of a continuous calling function of an application operation management class.

4. A device for protecting user privacy information, characterized in that: include: An acquisition module, used to acquire cross-application call operations, and acquire a caller application and a callee of the call operation; A determination module, used to determine whether the called party involves permission restrictions, and to determine whether the calling party application is running in the foreground; A processing module, used for prohibiting the execution of the calling operation when the called party involves permission restriction and the calling party application is not running in the foreground; The determination module is used to determine whether the calling application is running in the foreground by using the following method: Determine the running state of the process of the calling application, and when the running state belongs to the set state set, determine that the calling application is running in the foreground; when the running state does not belong to the set state set, determine that the calling application is not running in the foreground; The set state set is obtained based on a priority threshold of a process in the activity management service.

5. The device according to claim 4, characterized in that The device further includes: a first determining module, configured to determine a set of set states; The first determining module includes: A first setting module, used to set a priority threshold of a process in an activity management service; A second determination module, configured to determine a priority set greater than or equal to the priority threshold; A third determination module is used to determine the running state set corresponding to the priority set according to the mapping relationship between the process priority in the activity management service and the running state in the authority management service, and use the running state set as the set state set; The first setting module is used to set the priority threshold of the process in the activity management service using the following method: determine the priority set of the process of the calling application in the activity management service when the calling application has a component located in the top-level interface during operation, and determine the lowest priority from the priority set as the priority threshold.

6. The device according to claim 4, characterized in that The acquisition module is used to obtain the cross-application calling operation by using the following method: receiving the calling information of the instant calling function of the application operation management class, or receiving the calling information of the continuous calling function of the application operation management class.

7. A device for protecting user privacy information, characterized in that: include: processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to: Acquire a cross-application call operation, and acquire a caller application and a callee of the call operation; Determine whether the called party involves permission restrictions, and determine whether the calling party application is running in the foreground; When the called party is subject to permission restrictions and the calling party application is not running in the foreground, prohibiting execution of the calling operation; The determining whether the calling application is running in the foreground includes: Determine the running state of the process of the calling application, and when the running state belongs to a set state set, determine that the calling application is running in the foreground; when the running state does not belong to the set state set, determine that the calling application is not running in the foreground; the set state set is obtained based on the priority threshold of the process in the activity management service.

8. A non-transitory computer-readable storage medium, when the instructions in the storage medium are executed by a processor of a mobile terminal, enables the mobile terminal to perform a method for protecting user privacy information, the method comprising: Acquire a cross-application call operation, and acquire a caller application and a callee of the call operation; Determine whether the called party involves permission restrictions, and determine whether the calling party application is running in the foreground; When the called party is subject to permission restrictions and the calling party application is not running in the foreground, prohibiting execution of the calling operation; The determining whether the calling application is running in the foreground includes: Determine the running state of the process of the calling application, and when the running state belongs to a set state set, determine that the calling application is running in the foreground; when the running state does not belong to the set state set, determine that the calling application is not running in the foreground; the set state set is obtained based on the priority threshold of the process in the activity management service.

Citation Information

Patent Citations

  • Secret divulgence prevention processing method and device for privacy authority, electronic equipment and storage medium

    CN111259421A