CN108984234B - Calling prompt method for mobile terminal and camera device - Google Patents
Calling prompt method for mobile terminal and camera device Download PDFInfo
- Publication number
- CN108984234B CN108984234B CN201810865919.5A CN201810865919A CN108984234B CN 108984234 B CN108984234 B CN 108984234B CN 201810865919 A CN201810865919 A CN 201810865919A CN 108984234 B CN108984234 B CN 108984234B
- Authority
- CN
- China
- Prior art keywords
- calling
- mobile terminal
- target application
- behavior
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephone Function (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application aims to provide a calling prompt method of a mobile terminal and a camera device, and the method comprises the following steps: detecting a calling behavior of a target application program to a camera device interface of the mobile terminal; obtaining an analysis result about the calling behavior based on the related calling information corresponding to the calling behavior; and outputting calling prompt information about the target application program based on the analysis result. The method and the device can inform the calling condition of the application to the camera device to the user in time so as to protect the privacy of the user, and the system is high in judgment efficiency, difficult to miss judgment and good in user experience.
Description
Technical Field
The application relates to the field of communication, in particular to a calling prompt technology of a mobile terminal camera device.
Background
A mobile terminal (e.g., a mobile phone, a tablet computer, etc.) is usually provided with a front or rear camera for a user to use. With the continuous development of the technology, various application programs for the mobile terminal are developed, which greatly facilitates the work, life and entertainment of users. However, the industry also has misuse of the camera of the mobile terminal. For example, in the case where the user is not notified, the application secretly takes a picture through the camera, so that the user is violated in privacy without any notice.
Disclosure of Invention
The application aims to provide a calling prompt method of a mobile terminal camera device.
According to one aspect of the application, a calling prompt method of a mobile terminal camera device is provided, and the method comprises the following steps:
detecting a calling behavior of a target application program to a camera device interface of the mobile terminal;
obtaining an analysis result about the calling behavior based on the related calling information corresponding to the calling behavior;
and outputting calling prompt information about the target application program based on the analysis result.
According to another aspect of the present application, there is provided a call prompt apparatus of a camera apparatus of a mobile terminal, the apparatus including:
the detection module is used for detecting the calling behavior of a target application program to a camera device interface of the mobile terminal;
the analysis module is used for acquiring an analysis result related to the calling behavior based on the related calling information corresponding to the calling behavior;
and the output module is used for outputting calling prompt information about the target application program based on the analysis result.
According to one aspect of the application, a calling prompt device of a mobile terminal camera device is provided, and the device comprises a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
detecting a calling behavior of a target application program to a camera device interface of the mobile terminal;
obtaining an analysis result about the calling behavior based on the related calling information corresponding to the calling behavior;
and outputting calling prompt information about the target application program based on the analysis result.
According to another aspect of the application, there is provided a computer-readable medium comprising instructions that, when executed, cause a system to:
detecting a calling behavior of a target application program to a camera device interface of the mobile terminal;
obtaining an analysis result about the calling behavior based on the related calling information corresponding to the calling behavior;
and outputting calling prompt information about the target application program based on the analysis result.
Compared with the prior art, the method and the device have the advantages that the calling of other applications to the camera device is detected, the calling behavior of the target application program is analyzed, and the corresponding calling prompt information is output to the user, so that the purpose of informing the user that other applications are using the camera device or warning the user that the camera device is stolen by the applications is achieved. Compared with the prior art, the prompt mode provided by the application can inform the user of the calling condition of the camera device in time by the application, so that the privacy of the user is protected, the judgment efficiency of the system is high, and the user experience is good.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
fig. 1 is a flowchart illustrating a method for calling a prompt of a camera device of a mobile terminal according to an embodiment of the present application;
FIG. 2 illustrates a system service of a mobile terminal according to one embodiment of the present application;
fig. 3 illustrates a structure of a call prompt apparatus of a mobile terminal camera apparatus according to an embodiment of the present application;
fig. 4 illustrates a call prompting apparatus of a mobile terminal camera according to an embodiment of the present application.
The same or similar reference numbers in the drawings identify the same or similar elements.
Detailed Description
The present application is described in further detail below with reference to the attached figures.
In a typical configuration of the present application, the terminal, the device serving the network, and the trusted party each include one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
The device referred to in this application includes, but is not limited to, a user device, a network device, or a device formed by integrating a user device and a network device through a network. The user equipment includes, but is not limited to, any mobile electronic product, such as a smart phone, a tablet computer, etc., capable of performing human-computer interaction with a user (e.g., human-computer interaction through a touch panel), and the mobile electronic product may employ any operating system, such as an android operating system, an iOS operating system, etc. The network device includes an electronic device capable of automatically performing numerical calculation and information processing according to a preset or stored instruction, and hardware thereof includes, but is not limited to, a microprocessor, an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), an embedded device, and the like. The network device includes but is not limited to a computer, a network host, a single network server, a plurality of network server sets or a cloud of a plurality of servers; here, the Cloud is composed of a large number of computers or web servers based on Cloud Computing (Cloud Computing), which is a kind of distributed Computing, one virtual supercomputer consisting of a collection of loosely coupled computers. Including, but not limited to, the internet, a wide area network, a metropolitan area network, a local area network, a VPN network, a wireless Ad Hoc network (Ad Hoc network), etc. Preferably, the device may also be a program running on the user device, the network device, or a device formed by integrating the user device and the network device, the touch terminal, or the network device and the touch terminal through a network.
Of course, those skilled in the art will appreciate that the foregoing is by way of example only, and that other existing or future devices, which may be suitable for use in the present application, are also encompassed within the scope of the present application and are hereby incorporated by reference.
In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.
According to one aspect of the application, a calling prompting method of a mobile terminal camera device is provided, which is used for prompting a user about calling of the mobile terminal camera device by an application. The method is described in detail below based on a mobile terminal. In the description related to the present application, the image capturing apparatus is used for capturing image information, and generally includes a photosensitive element for converting an optical signal into an electrical signal, and may further include a light refracting/reflecting member (e.g., a lens or a lens assembly) for adjusting a propagation path of an incident light.
Fig. 1 shows a flowchart of a call prompting method according to an embodiment of the application, for prompting a user of a call of an application to a mobile terminal camera. The method includes step S100, step S200, and step S300. In step S100, the mobile terminal detects a call behavior of a target application to a camera interface of the mobile terminal; in step S200, the mobile terminal obtains an analysis result about the invoking behavior based on the related invoking information corresponding to the invoking behavior; in step S300, the mobile terminal outputs call prompt information about the target application based on the analysis result.
Specifically, in step S100, the mobile terminal detects a call behavior of a target application to its camera interface. In some embodiments, the target application is specified by a user, for example, the mobile terminal generates a corresponding application list based on user input (including but not limited to by clicking items in the candidate list, entering text in a text box, adding/modifying/importing a configuration file, etc.), determines one or more applications in currently installed applications as target applications based on the application list, and detects the calling behavior of the camera interface by the target applications. In other embodiments, the target application is determined by the system. For example, an application installed or running on the mobile terminal is taken as a target application; for another example, if the method is executed when an application is running, other applications installed or running on the mobile terminal other than the application are used as the target application. Of course, those skilled in the art should understand that the above-mentioned method for determining the target application is only an example and not a limitation of the present application, and other existing or future methods for determining the target application, such as those that can be applied to the present application, are also included in the scope of the present application and are included by reference.
In step S200, when the mobile terminal detects a call behavior of a target application to an interface of a camera device, an analysis result about the call behavior is obtained based on relevant call information corresponding to the call behavior. In some embodiments, the analysis result is obtained based on related invocation information related to the invocation behavior, for example, part or all of the information in the analysis result is included in the related invocation information, or the analysis result is obtained after the mobile terminal processes the related invocation information. The related calling information includes but is not limited to: the name of the application, the category of the application, the developer of the application, the process name of the application, the call authorization status of the application (e.g., whether the corresponding application is authorized to call the camera interface of the mobile terminal), the lock status of the mobile terminal (e.g., the mobile terminal is unlocked or locked when the camera interface is called), etc. In some embodiments, the related call information includes a call request of the target application program to the interface of the image capturing device, and the related call information can be obtained based on the call request.
In step S300, the mobile terminal outputs call prompt information about the target application based on the analysis result. For example, the analysis results include: whether the target application program has the right to call the camera device interface, the calling frequency of the target application program to the camera device interface and the like, and the mobile terminal determines corresponding calling prompt information according to the corresponding analysis result (for example, the target application program does not have the right to call the camera device interface but calls the camera device interface), for example, the mobile terminal outputs the calling prompt information in a mode of displaying warning information, making sound, generating vibration and the like so as to prompt a user correspondingly.
In some embodiments, the calling of the camera interface to the target application is based on a listening service. For example, referring to fig. 2, in one embodiment, the system services include a camera listening service in addition to a battery service, a window service, a multimedia service, and other sub-services of the system. The camera device listening service (hereinafter referred to as a listening service) listens for a call to a camera device interface (for example, listens for a camera device call request). In some embodiments, the mobile terminal first registers the above listening service in a system service, and then detects a calling behavior of a target application program to a camera interface of the mobile terminal based on the listening service, for example, a calling of a system photographing method by the target application program is listened to. Based on the monitoring service, not only can the relevant information of the target application program calling the interface of the camera device be obtained, but also the detection of calling the interface of the camera device by the target application program is not easy to miss.
In some embodiments, the listening service also analyzes a call log of the camera interface. And when the mobile terminal detects the calling behavior of the target application program to the interface of the camera device, the mobile terminal acquires related calling information related to the calling behavior based on the calling log. Wherein the content of the call log of the image pickup device interface is generated by an application program calling the image pickup device interface. For example, the format of a call record of a typical camera interface is as follows:
2018.7.185: 57 com camera screen status lock screen
The calling record comprises the calling date and the calling time of the camera device interface, the process name and the application name of the camera device interface, and the screen state of the mobile terminal, and the information can be used as related calling information corresponding to the corresponding calling behavior. And after acquiring the relevant calling information, the mobile terminal acquires an analysis result about the calling behavior according to the relevant calling information. In some embodiments, monitoring the call of the camera and analyzing the call log of the camera can be performed synchronously, for example, after the call of the target application program to the interface of the camera is monitored, the call log of the camera is analyzed to obtain information such as call time and screen state of the mobile terminal; for example, all the calling behaviors of the camera are monitored, when the calling of the application program to the interface of the camera is monitored, the calling log of the camera is analyzed to obtain information such as the name of the application program calling the interface of the camera, and if the calling behavior is determined to be initiated by the target application program, the obtained other information (such as calling time, screen state of the mobile terminal and the like) is taken as the related calling information corresponding to the calling behavior and analyzed. For example, after the call of the target application to the interface of the imaging apparatus is monitored, a history call record of the target application is determined based on the call log of the imaging apparatus, and the related information (for example, the call frequency, and the like) is analyzed as related call information corresponding to the call of the target application to the interface of the imaging apparatus.
In other embodiments, related calling information about calling behavior can be directly obtained based on the listening service. For example, based on the listening service, the name or process name of the target application program included in the call request of the target application program to the image pickup device interface and the call time (for example, the current system time) when the target application program calls the image pickup device interface are acquired, and the name or process name of the target application program and the call time when the image pickup device interface is called are used as the relevant call information.
On the other hand, the detection of the target application calling the camera interface may also be performed based on the associated system log. For example, the camera interface call record in the system log records the call condition of one or more application programs to the camera interface, and the newly added camera interface call record records the corresponding new call. In some embodiments, the mobile terminal obtains update information (e.g., a newly added call record of the camera interface) of a call log of its camera interface (e.g., by reading one or more call records in the call log), and detects a call behavior of a target application program to the camera interface according to the update information. For example, the mobile terminal reads one or more image pickup device interface call records closest to the current time in the call log. Similar to the above, in some embodiments, the format of a call record for a typical camera interface is as follows:
2018.7.185: 57 com camera screen status lock screen
The calling record comprises the calling date and the calling time of the camera device interface, the process name and the application name of the camera device interface, and the screen state of the mobile terminal, and the information can be used as related calling information corresponding to the corresponding calling behavior. The mobile terminal can detect whether the calling record is generated by a monitored target application program according to the process name or the application name of the calling camera device interface, so that the detection that the target application program calls the camera device interface is realized; in some embodiments, upon determining that one or more call records have been generated by the target application, a call behavior corresponding to the call record is determined to have been initiated by the target application. After acquiring the related call information (for example, including but not limited to, the call date when the target application calls the camera interface, the call time, the screen state of the mobile terminal, the number of calls counted according to the number of records corresponding to the same application, etc.), the mobile terminal acquires the analysis result about the call behavior according to the related call information.
In some embodiments, the analysis of the related call information corresponding to the call behavior is performed based on a call analysis model. In step S200, the mobile terminal inputs the relevant calling information about the calling behavior into a calling analysis model to obtain an analysis result about the calling behavior. The calling analysis model outputs an analysis result about the calling behavior of the target application program according to the input related calling information. In some embodiments, the call analysis model is implemented based on techniques including, but not limited to, support vector machines, decision trees, neural networks, and the like; in a preferred embodiment, the above-mentioned calling analysis model is generated based on a deep learning model. Of course, those skilled in the art should understand that the above data model is only an example and not intended to limit the present application, and other existing or future data models, such as may be suitable for use in the present application, are also included within the scope of the present application and are incorporated by reference herein.
And the analysis result is used for determining calling prompt information output to the user, and the calling prompt information is used for providing the relevant information of the relevant calling behavior to the user. In some embodiments, some related calling information, such as the name of the target application or the corresponding process name, the time when the camera interface is called, and the like, may be obtained directly based on the listening service or based on the related system log; and other information, such as whether the target application program is candid of the target application program without permission of the user, needs further processing to obtain the information, and the corresponding processing process can be carried out based on the calling analysis model. For example, generally speaking, compared to the application currently running in the foreground, the calling of the camera interface by the application running in the background poses a greater threat to the privacy of the user, or the calling of the camera interface by the application not authorized by the user for multiple times poses a greater threat to the privacy of the user, so that it is necessary to analyze the related calling information based on the call analysis model to obtain information that cannot be directly obtained, such as whether the current target application is running in the background or whether the target application is unauthorized to call the camera interface for multiple times.
The related call information about the call to the image capturing device interface includes one or more items of information, for example, the related call information includes (but is not limited to) one or more of the following items: information about the application itself, attributes related to a calling behavior for calling the camera interface, status information of the mobile terminal when the camera interface of the mobile terminal is called, and the like. In some embodiments, the relevant invocation information includes one or more of: the name of the target application program, the process name corresponding to the target application program, the calling authorization state of the target application program to the camera device interface (for example, the calling authorization state is provided by system preset or specified by a user, for example, authorization is realized by the technologies of password, fingerprint, face recognition and the like), the calling time of the target application program calling the camera device interface, the calling times of the camera device interface, a calling frequency of the camera interface (e.g., calculated from the aforementioned number of calls and calling time), a screen state of the mobile terminal (e.g., a screen of the current mobile terminal is lit or unlit), a lock state of the mobile terminal (e.g., the current mobile terminal is locked or unlocked), a system idle state of the mobile terminal, and the like. In some embodiments, the system idle state is determined by detecting whether the system is currently executing the user's instruction and is not completed, or detecting whether there is an input operation of the user within a certain period of time, and the like, and is used for indicating whether the system is currently in the idle state; in other embodiments, the system idle state is used to indicate a situation where system resources are occupied, e.g., the system idle state comprises utilization of a processor of the mobile terminal.
After obtaining the related calling information, the mobile terminal inputs the related calling information into a calling analysis model to obtain an analysis result about the calling behavior. The analysis result is used for judging whether to prompt a corresponding calling behavior for the user or determining calling prompt information which should be output when prompting the user, for example, the analysis result includes whether the interface of the camera device is actively called by the user or not, and if not, the user is prompted to call the interface of the camera device; for another example, the analysis result includes whether the target application calls the camera interface without permission of the user when the system is idle. In some embodiments, the call prompt information for output to the user includes one or more of: the name of the target application program, the process name corresponding to the target application program, the calling authorization state of the target application program to the camera device interface, the calling time of the target application program calling the camera device interface, the calling times of the camera device interface, the calling frequency of the camera device interface, the screen state of the mobile terminal, the locking state of the mobile terminal, the system idle state of the mobile terminal and the like. In some embodiments, a part of the call prompt information (for example, the name of the target application, the number of calls of the camera interface, the system idle state of the mobile terminal, and the like) may be directly from the related call information, and another part is generated by the call analysis model (for example, from an analysis result about the call behavior of the target application); the call prompt message may only include the related call message, or only include the analysis result. For example, if the call prompt information only includes the related call information, the mobile terminal only presents the name of the target application program or the corresponding process name, call time, and the like to the user; if the calling prompt information only contains the analysis result, the mobile terminal only presents corresponding information to the user to prompt the user that the target application program is not authorized and tries to call the interface of the camera device, the target application program responds to the active calling of the user and calls the interface of the camera device, and the like, and the user does not need to be prompted with specific information of an application name, a process name and the like.
The calling prompt information is used for prompting the user according to analysis of calling behaviors of the target application program to the interface of the camera device. In some embodiments, the mobile terminal performs a prompt output operation based on the analysis result to output call prompt information about the target application. The form of the cue output operation includes one or more of: vibration, ringing, voice prompt, pop-up notification message (including but not limited to pictures, text, animation, video, etc.), push the call prompt information to an external device (e.g., a device connected to the mobile terminal via bluetooth protocol, including but not limited to a wearable device such as a smart watch), update the screen display status of the mobile terminal (e.g., change foreground/background color of the current screen display, adjust screen brightness, change color scheme of the current display window, change color of the edge of the screen display area, etc.).
By analyzing the calling behavior of the target application program, the method and the device can achieve the purpose of informing the user that other applications use the camera device, and the user can also know the relevant information of the application program which is not allowed to use the camera device currently. In order to facilitate users to timely screen their privacy infringement through the camera device, and further improve the user experience, in some embodiments, the analysis result includes: the calling authorization state of the target application program is unauthorized; the calling prompt message comprises: the image pickup device calls the warning information. For example, when the mobile terminal detects that the target application program calls the camera interface to take a picture in an unauthorized state, the mobile terminal outputs the camera call warning information by displaying the warning information, making a sound, generating a vibration and the like, so as to warn the user accordingly. The output mode of the camera device calling the warning information can be distinguished from other types of calling prompt information.
According to another aspect of the application, a call prompting device of a mobile terminal camera device is provided, which is used for prompting a user of calling of the camera device of the mobile terminal by an application. The apparatus is described in detail below based on a mobile terminal.
Fig. 3 is a block diagram illustrating a call prompting apparatus for prompting a user of a call of an application to a mobile terminal image pickup apparatus according to an embodiment of the present application. The apparatus comprises a detection module 100, an analysis module 200 and an output module 300. The detection module 100 is configured to detect a calling behavior of a target application program to a camera interface of the mobile terminal based on relevant calling information corresponding to the calling behavior; the analysis module 200 is configured to obtain an analysis result about the call behavior; the output module 300 outputs call prompt information about the target application based on the analysis result.
Specifically, the detection module 100 detects a call behavior of a target application to its camera interface. In some embodiments, the target application is specified by a user, for example, the mobile terminal generates a corresponding application list based on user input (including but not limited to by clicking items in the candidate list, entering text in a text box, adding/modifying/importing a configuration file, etc.), determines one or more applications in currently installed applications as target applications based on the application list, and detects the calling behavior of the camera interface by the target applications. In other embodiments, the target application is determined by the system. For example, an application installed or running on the mobile terminal is taken as a target application; for another example, if the method is executed when an application is running, other applications installed or running on the mobile terminal other than the application are used as the target application. Of course, those skilled in the art should understand that the above-mentioned method for determining the target application is only an example and not a limitation of the present application, and other existing or future methods for determining the target application, such as those that can be applied to the present application, are also included in the scope of the present application and are included by reference.
When a call behavior of the target application to the interface of the image capturing apparatus is detected, the analysis module 200 obtains an analysis result about the call behavior based on the relevant call information corresponding to the call behavior. In some embodiments, the analysis result is obtained based on related invocation information related to the invocation behavior, for example, part or all of the information in the analysis result is included in the related invocation information, or the analysis result is obtained after the mobile terminal processes the related invocation information. The related calling information includes but is not limited to: the name of the application, the category of the application, the developer of the application, the process name of the application, the call authorization status of the application (e.g., whether the corresponding application is authorized to call the camera interface of the mobile terminal), the lock status of the mobile terminal (e.g., the mobile terminal is unlocked or locked when the camera interface is called), etc. In some embodiments, the related call information includes a call request of the target application program to the interface of the image capturing device, and the related call information can be obtained based on the call request.
The output module 300 outputs call prompt information about the target application based on the analysis result. For example, the analysis results include: whether the target application program has the right to call the camera device interface, the calling frequency of the target application program to the camera device interface and the like, and the mobile terminal determines corresponding calling prompt information according to the corresponding analysis result (for example, the target application program does not have the right to call the camera device interface but calls the camera device interface), for example, the mobile terminal outputs the calling prompt information in a mode of displaying warning information, making sound, generating vibration and the like so as to prompt a user correspondingly.
In some embodiments, the calling of the camera interface to the target application is based on a listening service. For example, still referring to fig. 2, in one embodiment, the system services include camera listening services in addition to battery services, window services, multimedia services, and other sub-services of the system. The camera device listening service (hereinafter referred to as a listening service) listens for a call to a camera device interface (for example, listens for a camera device call request). In some embodiments, the mobile terminal first registers the above listening service in a system service, and then detects a calling behavior of a target application program to a camera interface of the mobile terminal based on the listening service, for example, a calling of a system photographing method by the target application program is listened to. Based on the monitoring service, not only can the relevant information of the target application program calling the interface of the camera device be obtained, but also the detection of calling the interface of the camera device by the target application program is not easy to miss.
In some embodiments, the listening service also analyzes a call log of the camera interface. And when the mobile terminal detects the calling behavior of the target application program to the interface of the camera device, the mobile terminal acquires related calling information related to the calling behavior based on the calling log. Wherein the content of the call log of the image pickup device interface is generated by an application program calling the image pickup device interface. For example, the format of a call record of a typical camera interface is as follows:
2018.7.185: 57 com camera screen status lock screen
The calling record comprises the calling date and the calling time of the camera device interface, the process name and the application name of the camera device interface, and the screen state of the mobile terminal, and the information can be used as related calling information corresponding to the corresponding calling behavior. After obtaining the relevant calling information, the mobile terminal inputs the relevant calling information into a calling analysis model to obtain an analysis result about the calling behavior. In some embodiments, monitoring the call of the camera and analyzing the call log of the camera can be performed synchronously, for example, after the call of the target application program to the interface of the camera is monitored, the call log of the camera is analyzed to obtain information such as call time and screen state of the mobile terminal; for example, all the calling behaviors of the camera are monitored, when the calling of the application program to the interface of the camera is monitored, the calling log of the camera is analyzed to obtain information such as the name of the application program calling the interface of the camera, and if the calling behavior is determined to be initiated by the target application program, the obtained other information (such as calling time, screen state of the mobile terminal and the like) is input into the calling analysis model as the related calling information corresponding to the calling behavior for analysis. For example, after the call of the target application to the interface of the imaging apparatus is monitored, a history call record of the target application is determined based on the call log of the imaging apparatus, and the related information (for example, the call frequency, and the like) is analyzed as related call information corresponding to the call of the target application to the interface of the imaging apparatus.
In other embodiments, related calling information about calling behavior can be directly obtained based on the listening service. For example, based on the listening service, the name or process name of the target application program included in the call request of the target application program to the image pickup device interface and the call time (for example, the current system time) when the target application program calls the image pickup device interface are acquired, and the name or process name of the target application program and the call time when the image pickup device interface is called are used as the relevant call information.
On the other hand, the detection of the target application calling the camera interface may also be performed based on the associated system log. For example, the camera interface call record in the system log records the call condition of one or more application programs to the camera interface, and the newly added camera interface call record records the corresponding new call. In some embodiments, the mobile terminal obtains update information (e.g., a newly added call record of the camera interface) of a call log of its camera interface (e.g., by reading one or more call records in the call log), and detects a call behavior of a target application program to the camera interface according to the update information. For example, the mobile terminal reads one or more image pickup device interface call records closest to the current time in the call log. Similar to the above, in some embodiments, the format of a call record for a typical camera interface is as follows:
2018.7.185: 57 com camera screen status lock screen
The calling record comprises the calling date and the calling time of the camera device interface, the process name and the application name of the camera device interface, and the screen state of the mobile terminal, and the information can be used as related calling information corresponding to the corresponding calling behavior. The mobile terminal can detect whether the calling record is generated by a monitored target application program according to the process name or the application name of the calling camera device interface, so that the detection that the target application program calls the camera device interface is realized; in some embodiments, upon determining that one or more call records have been generated by the target application, a call behavior corresponding to the call record is determined to have been initiated by the target application. After acquiring the related call information (for example, including but not limited to, the call date, the call time, the screen state of the mobile terminal, the number of calls counted according to the number of records corresponding to the same application, etc.) described above, the analysis module 200 acquires the analysis result about the call behavior according to the related call information.
In some embodiments, the analysis of the related call information corresponding to the call behavior is performed based on a call analysis model. The analysis module 200 inputs the relevant calling information corresponding to the calling behavior into a calling analysis model to obtain an analysis result about the calling behavior. The calling analysis model outputs an analysis result about the calling behavior of the target application program according to the input related calling information. In some embodiments, the call analysis model is implemented based on techniques including, but not limited to, support vector machines, decision trees, neural networks, and the like; in a preferred embodiment, the above-mentioned calling analysis model is generated based on a deep learning model. Of course, those skilled in the art should understand that the above data model is only an example and not intended to limit the present application, and other existing or future data models, such as may be suitable for use in the present application, are also included within the scope of the present application and are incorporated by reference herein.
And the analysis result is used for determining calling prompt information output to the user, and the calling prompt information is used for providing the relevant information of the relevant calling behavior to the user. In some embodiments, some related calling information, such as the name of the target application or the corresponding process name, the time when the camera interface is called, and the like, may be obtained directly based on the listening service or based on the related system log; and other information, such as whether the target application program is candid of the target application program without permission of the user, needs further processing to obtain the information, and the corresponding processing process can be carried out based on the calling analysis model. For example, generally speaking, compared to the application currently running in the foreground, the calling of the camera interface by the application running in the background poses a greater threat to the privacy of the user, or the calling of the camera interface by the application not authorized by the user for multiple times poses a greater threat to the privacy of the user, so that it is necessary to analyze the related calling information based on the call analysis model to obtain information that cannot be directly obtained, such as whether the current target application is running in the background or whether the target application is unauthorized to call the camera interface for multiple times.
The related call information corresponding to the above-mentioned call to the interface of the image capturing apparatus includes one or more items of information, for example, the related call information includes (but is not limited to) one or more of the following items: information about the application itself, attributes related to a calling behavior for calling the camera interface, status information of the mobile terminal when the camera interface of the mobile terminal is called, and the like. In some embodiments, the relevant invocation information includes one or more of: the name of the target application program, the process name corresponding to the target application program, the calling authorization state of the target application program to the camera device interface (for example, the calling authorization state is provided by system preset or specified by a user, for example, authorization is realized by the technologies of password, fingerprint, face recognition and the like), the calling time of the target application program calling the camera device interface, the calling times of the camera device interface, a calling frequency of the camera interface (e.g., calculated from the aforementioned number of calls and calling time), a screen state of the mobile terminal (e.g., a screen of the current mobile terminal is lit or unlit), a lock state of the mobile terminal (e.g., the current mobile terminal is locked or unlocked), a system idle state of the mobile terminal, and the like. In some embodiments, the system idle state is determined by detecting whether the system is currently executing the user's instruction and is not completed, or detecting whether there is an input operation of the user within a certain period of time, and the like, and is used for indicating whether the system is currently in the idle state; in other embodiments, the system idle state is used to indicate a situation where system resources are occupied, e.g., the system idle state comprises utilization of a processor of the mobile terminal.
After obtaining the related calling information, the mobile terminal inputs the related calling information into a calling analysis model to obtain an analysis result about the calling behavior. The analysis result is used for judging whether to prompt a corresponding calling behavior for the user or determining calling prompt information which should be output when prompting the user, for example, the analysis result includes whether the interface of the camera device is actively called by the user or not, and if not, the user is prompted to call the interface of the camera device; for another example, the analysis result includes whether the target application calls the camera interface without permission of the user when the system is idle. In some embodiments, the call prompt information for output to the user includes one or more of: the name of the target application program, the process name corresponding to the target application program, the calling authorization state of the target application program to the camera device interface, the calling time of the target application program calling the camera device interface, the calling times of the camera device interface, the calling frequency of the camera device interface, the screen state of the mobile terminal, the locking state of the mobile terminal, the system idle state of the mobile terminal and the like. In some embodiments, a part of the call prompt information (for example, the name of the target application, the number of calls of the camera interface, the system idle state of the mobile terminal, and the like) may be directly from the related call information, and another part is generated by the call analysis model (for example, from an analysis result about the call behavior of the target application); the call prompt message may only include the related call message, or only include the analysis result. For example, if the call prompt information only includes the related call information, the mobile terminal only presents the name of the target application program or the corresponding process name, call time, and the like to the user; if the calling prompt information only contains the analysis result, the mobile terminal only presents corresponding information to the user to prompt the user that the target application program is not authorized and tries to call the interface of the camera device, the target application program responds to the active calling of the user and calls the interface of the camera device, and the like, and the user does not need to be prompted with specific information of an application name, a process name and the like.
The calling prompt information is used for prompting the user according to analysis of calling behaviors of the target application program to the interface of the camera device. In some embodiments, the output module 300 performs a prompt output operation based on the analysis result to output call prompt information about the target application. The form of the cue output operation includes one or more of: vibration, ringing, voice prompt, pop-up notification message (including but not limited to pictures, text, animation, video, etc.), push the call prompt information to an external device (e.g., a device connected to the mobile terminal via bluetooth protocol, including but not limited to a wearable device such as a smart watch), update the screen display status of the mobile terminal (e.g., change foreground/background color of the current screen display, adjust screen brightness, change color scheme of the current display window, change color of the edge of the screen display area, etc.).
By analyzing the calling behavior of the target application program, the method and the device can achieve the purpose of informing the user that other applications use the camera device, and the user can also know the relevant information of the application program which is not allowed to use the camera device currently. In order to facilitate users to timely screen their privacy infringement through the camera device, and further improve the user experience, in some embodiments, the analysis result includes: the calling authorization state of the target application program is unauthorized; the calling prompt message comprises: the image pickup device calls the warning information. For example, when the mobile terminal detects that the target application program calls the camera interface to take a picture in an unauthorized state, the mobile terminal outputs the camera call warning information by displaying the warning information, making a sound, generating a vibration and the like, so as to warn the user accordingly. The output mode of the camera device calling the warning information can be distinguished from other types of calling prompt information.
According to another aspect of the present application, there is provided a mobile terminal including
One or more processors;
a memory for storing one or more computer programs;
the one or more computer programs, when executed by the one or more processors, cause the one or more processors to implement the methods described above.
FIG. 4 illustrates an exemplary system that can be used to implement the various embodiments described in this application.
As shown in fig. 4, in some embodiments, the system 400 can operate as any of the mobile terminals in the various described embodiments. In some embodiments, system 400 may include one or more computer-readable media (e.g., system memory or NVM/storage 420) having instructions and one or more processors (e.g., processor(s) 405) coupled with the one or more computer-readable media and configured to execute the instructions to implement modules to perform the actions described herein.
For one embodiment, system control module 410 may include any suitable interface controllers to provide any suitable interface to at least one of the processor(s) 405 and/or any suitable device or component in communication with system control module 410.
The system control module 410 may include a memory controller module 430 to provide an interface to the system memory 415. The memory controller module 430 may be a hardware module, a software module, and/or a firmware module.
System memory 415 may be used, for example, to load and store data and/or instructions for system 400. For one embodiment, system memory 415 may include any suitable volatile memory, such as suitable DRAM. In some embodiments, system memory 415 may include a double data rate type four synchronous dynamic random access memory (DDR4 SDRAM).
For one embodiment, system control module 410 may include one or more input/output (I/O) controllers to provide an interface to NVM/storage 420 and communication interface(s) 425.
For example, NVM/storage 420 may be used to store data and/or instructions. NVM/storage 420 may include any suitable non-volatile memory (e.g., flash memory) and/or may include any suitable non-volatile storage device(s) (e.g., one or more Hard Disk Drives (HDDs), one or more Compact Disc (CD) drives, and/or one or more Digital Versatile Disc (DVD) drives).
NVM/storage 420 may include storage resources that are physically part of the device on which system 400 is installed or may be accessed by the device and not necessarily part of the device. For example, NVM/storage 420 may be accessed over a network via communication interface(s) 425.
Communication interface(s) 425 may provide an interface for system 400 to communicate over one or more networks and/or with any other suitable device. System 400 may wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and/or protocols.
For one embodiment, at least one of the processor(s) 405 may be packaged together with logic for one or more controller(s) of the system control module 410, such as memory controller module 430. For one embodiment, at least one of the processor(s) 405 may be packaged together with logic for one or more controller(s) of the system control module 410 to form a System In Package (SiP). For one embodiment, at least one of the processor(s) 405 may be integrated on the same die with logic for one or more controller(s) of the system control module 410. For one embodiment, at least one of the processor(s) 405 may be integrated on the same die with logic of one or more controllers of the system control module 410 to form a system on a chip (SoC).
In various embodiments, system 400 may be, but is not limited to being: a server, a workstation, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet, a netbook, etc.). In various embodiments, system 400 may have more or fewer components and/or different architectures. For example, in some embodiments, system 400 includes one or more cameras, a keyboard, a Liquid Crystal Display (LCD) screen (including a touch screen display), a non-volatile memory port, multiple antennas, a graphics chip, an Application Specific Integrated Circuit (ASIC), and speakers.
The present application also provides a computer readable storage medium having stored thereon computer code which, when executed, performs a method as in any one of the preceding.
The present application also provides a computer program product, which when executed by a computer device, performs the method of any of the preceding claims.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, implemented using Application Specific Integrated Circuits (ASICs), general purpose computers or any other similar hardware devices. In one embodiment, the software programs of the present application may be executed by a processor to implement the steps or functions described above. Likewise, the software programs (including associated data structures) of the present application may be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Additionally, some of the steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
In addition, some of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application through the operation of the computer. Those skilled in the art will appreciate that the form in which the computer program instructions reside on a computer-readable medium includes, but is not limited to, source files, executable files, installation package files, and the like, and that the manner in which the computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Computer-readable media herein can be any available computer-readable storage media or communication media that can be accessed by a computer.
Communication media includes media by which communication signals, including, for example, computer readable instructions, data structures, program modules, or other data, are transmitted from one system to another. Communication media may include conductive transmission media such as cables and wires (e.g., fiber optics, coaxial, etc.) and wireless (non-conductive transmission) media capable of propagating energy waves such as acoustic, electromagnetic, RF, microwave, and infrared. Computer readable instructions, data structures, program modules, or other data may be embodied in a modulated data signal, for example, in a wireless medium such as a carrier wave or similar mechanism such as is embodied as part of spread spectrum techniques. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. The modulation may be analog, digital or hybrid modulation techniques.
By way of example, and not limitation, computer-readable storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. For example, computer-readable storage media include, but are not limited to, volatile memory such as random access memory (RAM, DRAM, SRAM); and non-volatile memory such as flash memory, various read-only memories (ROM, PROM, EPROM, EEPROM), magnetic and ferromagnetic/ferroelectric memories (MRAM, FeRAM); and magnetic and optical storage devices (hard disk, tape, CD, DVD); or other now known media or later developed that can store computer-readable information/data for use by a computer system.
An embodiment according to the present application comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform a method and/or a solution according to the aforementioned embodiments of the present application.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.
Claims (13)
1. A calling prompt method of a mobile terminal camera device is disclosed, wherein the method comprises the following steps:
detecting a calling behavior of a target application program to a camera device interface of the mobile terminal, wherein the target application program is specified by a user or determined by a system;
if the calling behavior is determined to be initiated by the target application program, acquiring an analysis result about the calling behavior based on related calling information corresponding to the calling behavior, wherein the analysis result is used for judging whether the calling behavior is required to be prompted to the user or determining calling prompt information which should be output when the user is prompted;
and outputting calling prompt information related to the target application program based on the analysis result, wherein when the analysis result includes that the calling authorization state of the target application program is unauthorized, the calling prompt information includes camera device calling warning information.
2. The method of claim 1, wherein the detecting a calling behavior of a target application to a camera interface of the mobile terminal comprises:
and detecting the calling behavior of a target application program to a camera device interface of the mobile terminal based on the monitoring service.
3. The method of claim 2, wherein the detecting a calling behavior of a target application to a camera interface of the mobile terminal based on the listening service comprises:
registering a listening service in a system service;
and detecting the calling behavior of a target application program to a camera device interface of the mobile terminal based on the monitoring service.
4. The method of claim 2, wherein the obtaining of the analysis result about the invoking behavior based on the related invoking information corresponding to the invoking behavior comprises:
when the calling behavior is detected, acquiring related calling information corresponding to the calling behavior based on a calling log of the camera device interface;
and obtaining an analysis result about the calling behavior based on the related calling information.
5. The method of claim 1, wherein the detecting the invocation behavior of the target application program to the camera interface of the mobile terminal comprises:
and detecting the calling behavior of a target application program to the camera device interface based on the updated information of the calling log of the camera device interface of the mobile terminal.
6. The method of claim 5, wherein the obtaining of the analysis result about the invoking behavior based on the related invoking information corresponding to the invoking behavior comprises:
when the calling behavior is detected, acquiring related calling information corresponding to the calling behavior based on the updating information;
and obtaining an analysis result about the calling behavior based on the related calling information.
7. The method of claim 1, wherein the obtaining an analysis result about the invoking behavior based on the related invoking information corresponding to the invoking behavior comprises:
and inputting related calling information about the calling behavior into a calling analysis model to obtain an analysis result about the calling behavior.
8. The method of claim 7, wherein the call analysis model is generated based on a deep learning model.
9. The method of claim 1, wherein the relevant invocation information includes at least any one of:
a name of the target application;
the process name corresponding to the target application program;
a call authorization state of the target application;
the calling time of the camera device interface;
the calling times of the camera device interface;
the calling frequency of the camera device interface;
a screen state of the mobile terminal;
a locked state of the mobile terminal;
a system idle state of the mobile terminal.
10. The method of claim 1, wherein the call prompt information further comprises at least any one of:
a name of the target application;
the process name corresponding to the target application program;
a call authorization state of the target application;
the calling time of the camera device interface;
the calling times of the camera device interface;
the calling frequency of the camera device interface;
a screen state of the mobile terminal;
a locked state of the mobile terminal;
a system idle state of the mobile terminal.
11. The method of any of claims 1-10, wherein the outputting call prompt information about the target application based on the analysis results comprises:
based on the analysis result, executing a prompt output operation to output call prompt information about the target application program:
wherein the prompt output operation includes at least any one of:
vibrating;
ringing;
voice prompt;
popping up a notification message;
pushing the calling prompt information to external equipment;
and updating the screen display state of the mobile terminal.
12. A mobile terminal, wherein the mobile terminal comprises:
a processor; and
a memory arranged to store computer-executable instructions that, when executed, cause the processor to perform operations according to the method of any one of claims 1 to 11.
13. A computer-readable medium comprising instructions that, when executed, cause a mobile terminal to perform operations according to any of claims 1 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810865919.5A CN108984234B (en) | 2018-08-01 | 2018-08-01 | Calling prompt method for mobile terminal and camera device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810865919.5A CN108984234B (en) | 2018-08-01 | 2018-08-01 | Calling prompt method for mobile terminal and camera device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108984234A CN108984234A (en) | 2018-12-11 |
| CN108984234B true CN108984234B (en) | 2021-08-06 |
Family
ID=64554585
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810865919.5A Active CN108984234B (en) | 2018-08-01 | 2018-08-01 | Calling prompt method for mobile terminal and camera device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108984234B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111383582B (en) * | 2018-12-29 | 2021-08-03 | 北京小米移动软件有限公司 | Display control method, display control device, electronic equipment and computer-readable storage medium |
| CN109743503A (en) * | 2019-01-17 | 2019-05-10 | 维沃移动通信有限公司 | Reminding method and terminal |
| CN109918898A (en) * | 2019-03-14 | 2019-06-21 | 上海龙旗科技股份有限公司 | Method for secret protection and equipment |
| CN111444497B (en) * | 2020-04-13 | 2024-03-08 | Oppo广东移动通信有限公司 | Application program detection method and device and electronic equipment |
| CN111611631A (en) * | 2020-04-14 | 2020-09-01 | 上海卓易科技股份有限公司 | Terminal peeping prevention method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102510373B (en) * | 2011-09-30 | 2015-10-07 | 百度在线网络技术（北京）有限公司 | A kind of method, apparatus and system for running application in a mobile device |
| CN103488939B (en) * | 2013-08-30 | 2017-02-08 | 小米科技有限责任公司 | Method, device and terminal for prompting user |
| CN106657785A (en) * | 2016-12-23 | 2017-05-10 | 广东小天才科技有限公司 | Camera operation control method and camera operation control device |
-
2018
- 2018-08-01 CN CN201810865919.5A patent/CN108984234B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108984234A (en) | 2018-12-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108984234B (en) | Calling prompt method for mobile terminal and camera device | |
| CN107209818B (en) | Method and system for detecting false user interactions with a mobile device for improved malware protection | |
| US9448859B2 (en) | Exploiting hot application programming interfaces (APIs) and action patterns for efficient storage of API logs on mobile devices for behavioral analysis | |
| CN110336735B (en) | Method and equipment for sending reminding message | |
| CN110245518B (en) | Data storage method, device and equipment | |
| US10447924B2 (en) | Camera usage notification | |
| US11593478B2 (en) | Malware collusion detection | |
| US20190325134A1 (en) | Neural network detection of malicious activity | |
| CN114207613A (en) | Techniques for an energized intrusion detection system | |
| CN110780955A (en) | Method and equipment for processing emoticon message | |
| CN111162990A (en) | Method and equipment for presenting message notification | |
| US10172069B2 (en) | Paired smart device theft deterrent | |
| CN117149476A (en) | Fault reporting method and related device | |
| US20220358914A1 (en) | Operational command boundaries | |
| US20220405185A1 (en) | Dynamic remote collection of supplemental diagnostic data and triggering of client actions for client software application | |
| CN116049820A (en) | Rogue application detection method, electronic equipment and communication system | |
| CN110750162B (en) | Input method and device | |
| CN114296651A (en) | Method and equipment for storing user-defined data information | |
| US11194904B2 (en) | Security actions based on monitored computer and user physical activities | |
| CN110958315A (en) | Method and equipment for presenting message notification | |
| US20130067570A1 (en) | Content Inspection | |
| US20230224652A1 (en) | Computer technology for prediction of hearing issues | |
| US11232457B1 (en) | Systems and methods for protecting users | |
| CN116048829B (en) | Interface calling method, device and storage medium | |
| CN113923000B (en) | Security processing method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |