Call management method, device and storage medium of terminal multimedia device

Abstract

This application relates to a method, apparatus, and storage medium for managing the use of multimedia devices on a terminal. The method includes: reading a whitelist, the whitelist recording applications permitted to use multimedia devices on the terminal; obtaining data items of applications running on the terminal that are associated with the multimedia device; filtering out data items belonging to applications in the whitelist from the data items; generating process information indicating the usage status of a target application on the multimedia device based on the filtered data items; wherein the target application is not in the whitelist; and outputting a prompt message prompting the target application to use the multimedia device based on the process information. The solution provided by this application can prevent applications from illegally enabling multimedia devices on the terminal, thus avoiding security risks to user information and improving user information security.

Description

Technical Field

[0001] The present application relates to the field of information security technology, and in particular to a method, device and storage medium for managing the calling of a terminal multimedia device. Background Art

[0002] With the continuous development of computer technology and mobile network technology, more and more users enjoy various digital services through applications on various smart terminals. However, some applications installed on the terminal will enable multimedia devices (such as microphones and cameras) on the terminal to collect user information without the user's knowledge, thus posing potential security risks to user information. Summary of the invention

[0003] Based on this, as more and more applications are installed on user terminals, it is necessary to provide a method, device and storage medium for calling and managing terminal multimedia devices to address the technical problem that applications illegally enable multimedia devices on terminals and cause security risks to user information.

[0004] A method for managing the calling of a terminal multimedia device, comprising:

[0005] Reading a whitelist, wherein the whitelist records applications that are permitted to use the multimedia device on the terminal;

[0006] Acquire data items of an application program running on the terminal and associated with the multimedia device;

[0007] filtering out data items belonging to applications in the whitelist from the data items;

[0008] Based on the filtered data items, obtaining process information of the target application's use status of the multimedia device; the target application does not belong to the whitelist;

[0009] A prompt message for prompting the target application to use the multimedia device is output according to the process information.

[0010] A call management device for a terminal multimedia device, the device comprising:

[0011] A whitelist reading module, used to read a whitelist, wherein the whitelist records the application programs that are allowed to use the multimedia device on the terminal;

[0012] A data acquisition module, used to acquire data items of an application running on the terminal and associated with the multimedia device;

[0013] A data filtering module, used to filter out data items belonging to the application in the whitelist from the data items;

[0014] A process information acquisition module, used to obtain process information of the target application's use status of the multimedia device based on the data items obtained after filtering;

[0015] The prompt message output module is used to output a prompt message for prompting the target application to use the multimedia device according to the process information.

[0016] A computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the processor executes the steps of the calling management method of the terminal multimedia device as described above.

[0017] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the calling management method of the terminal multimedia device as described above.

[0018] The above-mentioned terminal multimedia device call management method, device and storage medium configure a whitelist of applications that are allowed to use multimedia devices. During the monitoring process, data items belonging to applications in the whitelist are filtered out, so that data items about target applications outside the whitelist can be obtained, and then process information about the target application's use of the multimedia device can be obtained, so that targeted monitoring of applications can be achieved according to user needs. A prompt message for prompting the target application to use the multimedia device is output based on the process information, so that the user can know that the application is illegally using the multimedia device, so that the user can perform corresponding operations, thereby effectively preventing the application from illegally using the multimedia device to collect user information, and ensuring the security of user information. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 An application environment diagram of a method for managing the call of a terminal multimedia device in one embodiment;

[0020] Figure 2 A schematic diagram of a process flow of a method for managing the calling of a terminal multimedia device in one embodiment;

[0021] Figure 3 A schematic diagram of a monitoring entry page of a client in one embodiment;

[0022] Figure 4 A schematic diagram of a monitoring setting page for protecting a multimedia device in one embodiment;

[0023] Figure 5 A schematic diagram of a whitelist configuration page in an embodiment;

[0024] Figure 6A schematic diagram of an application selection page in one embodiment;

[0025] Figure 7 A schematic diagram of a monitoring log page in one embodiment;

[0026] Figure 8 is a schematic diagram of a prompt box containing a prompt message in one embodiment;

[0027] Fig. 9 A schematic diagram of a prompt box for allowing an application to use a multimedia device in one embodiment;

[0028] Fig.10 A flowchart of steps of obtaining process information and providing message prompts according to the process information in one embodiment;

[0029] Fig.11 A timing diagram of a method for managing the calling of a terminal multimedia device in one embodiment;

[0030] Fig.12 A schematic diagram of a main control window, a whitelist window, an application selection window and a log window in one embodiment;

[0031] Fig.13 A schematic diagram of a system notification UI in one embodiment;

[0032] Fig.14 A schematic diagram of allowing a UI once or always in one embodiment;

[0033] Fig.15 A schematic diagram of a camera monitoring model, a microphone monitoring model, a whitelist model, and a daemon process processing item model in one embodiment;

[0034] Fig.16 A schematic diagram of a functional module corresponding to a control layer in an embodiment;

[0035] Fig.17 A schematic flow chart of a method for managing the calling of a terminal multimedia device in another embodiment;

[0036] Fig.18 A schematic flow chart of a method for managing the calling of a terminal multimedia device in another embodiment;

[0037] Fig.19 A schematic diagram of a page for configuring device protection in an embodiment;

[0038] Fig. 20 A schematic diagram of a process flow of obtaining process information by a daemon process in one embodiment;

[0039] Fig.21A structural block diagram of a call management device for a terminal multimedia device in one embodiment;

[0040] Fig. 22 It is a structural block diagram of a call management device of a terminal multimedia device in another embodiment;

[0041] Fig.23 FIG. 4 is a structural block diagram of a computer device in one embodiment. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0043] Figure 1 FIG. 1 is an application environment diagram of a method for managing the calling of a terminal multimedia device in an embodiment. Figure 1 , the call management method of the terminal multimedia device is applied to the monitoring system of the application. The monitoring system of the application includes a terminal 110 and a multimedia device 120. The terminal 110 and the multimedia device 120 are connected through a network or a line. The terminal 110 reads the whitelist configured through the whitelist configuration page, and the whitelist records the applications that are allowed to use the multimedia device 120 on the terminal; obtains data items of the running application and associated with the multimedia device 120; filters out data items belonging to the applications in the whitelist from the data items; based on the data items obtained after filtering, generates process information for indicating the use status of the target application for the multimedia device 120, and the target application does not belong to the whitelist; outputs a prompt message for prompting the target application to use the multimedia device 120 according to the process information.

[0044] The terminal 110 is installed with a client for monitoring multimedia devices. The terminal 110 may be a desktop terminal or a mobile terminal, and the mobile terminal may be at least one of a mobile phone, a tablet computer, a laptop computer, etc. The multimedia device 120 includes at least one of a microphone and a camera, and the multimedia device 120 may exist in the form of an independent device or may be a media device installed on the terminal 110.

[0045] like Figure 2 As shown, in one embodiment, a method for managing the calling of a terminal multimedia device is provided. This embodiment mainly applies the method to the above Figure 1 The terminal 110 in FIG. Figure 2 The calling management method of the terminal multimedia device specifically includes the following steps:

[0046] S202, reading a white list, where the white list records the application programs that are allowed to use the multimedia devices on the terminal.

[0047] The whitelist is a list of applications that is pre-configured on a whitelist configuration page and is used to indicate that the applications are allowed to use the multimedia device.

[0048] In one embodiment, the configuration method of the whitelist includes: the terminal displays the monitoring setting page of the multimedia device; when an operation instruction triggered by the whitelist control on the monitoring setting page is obtained, the whitelist configuration page is displayed; when a whitelist addition instruction is received, the application specified by the whitelist addition instruction is added to the whitelist configuration page; and the use permission of the multimedia device is configured for the added application.

[0049] In one embodiment, before the step of displaying the monitoring setting page of the multimedia device by the terminal, the method further includes: after the terminal starts the client (which can be the foreground start or the background start), the taskbar logo of the client will be displayed on the taskbar of the desktop. When a click or touch operation triggered by the taskbar logo is detected, or the cursor is above the taskbar logo, the terminal displays the monitoring entry page. When a client opening operation triggered by the monitoring entry page is detected, the terminal opens the client, or switches the client from the background to the foreground, and displays the monitoring setting page of the multimedia device on the display of the terminal.

[0050] As an example, see Figure 3-6 , Figure 3 This is a schematic diagram of the client's monitoring entry page. Figure 4 A diagram of a monitoring setting page for protecting multimedia devices. Figure 5 A diagram of the whitelist configuration page. Figure 6 A diagram showing the selection page for the application. Figure 3 As shown in the figure, when the user places the mouse cursor on the taskbar icon of the client, the monitoring entry page will be displayed. Figure 4 As shown, when the user clicks the "Open Lemon" control on the monitoring entry page, the monitoring setting page of the multimedia device will be displayed. In the monitoring setting page, you can choose to monitor at least one of the camera and microphone. For example, through the camera and microphone switch buttons in the middle of the page, you can turn on or off the monitoring of the camera and microphone, thereby protecting the camera and / or microphone. Among them, turning on the camera and microphone switch buttons means that the corresponding application has the permission to use the camera and microphone. In addition, by clicking the "Monitoring Log" control in the lower left corner, you can open the Log log details page about the use of the camera or microphone; in addition, by clicking the "Whitelist" control, you can view the corresponding whitelist. As shown Figure 5As shown in the figure, when the user clicks the "Whitelist" control on the monitoring setting page, it will jump to the whitelist configuration page, on which the user can set the application to use the camera and / or microphone through the check box button, such as Figure 5 The Siri app in . Figure 5 You can also remove an application from the whitelist by clicking the "Remove" control. If you want to allow other applications to use the camera and / or microphone, you can click Figure 5 Click the "Add" control in the upper right corner of the whitelist configuration page. Figure 6 ,exist Figure 6 Users can select the corresponding applications and add them to the whitelist to allow them to use the camera and / or microphone.

[0051] In one embodiment, before S202, the method may further include: the terminal starts a client for monitoring multimedia devices, and the client may be a Lemon client. After starting, the terminal starts a main process for the client and allocates a process identifier (PID) for the main process.

[0052] When running an application, the terminal will start at least one process for the application. If the application is executed on different data sets, it will become a different process. Each process can be identified by a unique process identifier.

[0053] In one embodiment, before S202, the terminal sends a verification request carrying a digital signature to the daemon process through the main process, so that the daemon process verifies the digital signature carried by the verification request. When the digital signature meets the signature conditions, the main process will be able to communicate with the daemon process, thereby preventing other applications from invading the daemon process and ensuring the security of data and communication channels.

[0054] In another embodiment, the terminal sends an acquisition request carrying a digital signature to the daemon process through the main process, so that the daemon process verifies the digital signature carried by the acquisition request. When the digital signature meets the signature conditions, the daemon process reads the whitelist configured through the whitelist configuration page and executes S204 to obtain process information of whether the target application uses the multimedia device, and then sends the obtained process information to the main process, thereby preventing other applications from invading the daemon process and ensuring the security of data and communication channels.

[0055] For example, for the Lemon client, before the Lemon client is first released to users, the application developer will apply for a digital signature from the operating system provider. When the user uses the Lemon client, the terminal will start a main process, and send a digitally signed acquisition request to the daemon process through the main process, so that the daemon process responds to the acquisition request, including process information on whether the running application uses multimedia devices, and returns it to the main process.

[0056] In one embodiment, before S202, the terminal also sends a white list to the daemon process so that the daemon process filters out data items of some applications according to the white list.

[0057] S204, obtaining data items of the application program running on the terminal and associated with the multimedia device.

[0058] The application is also called application software, which can be a system-provided application or a third-party application. When the application is running on the terminal, data items of the application and associated with the multimedia device can be obtained. The above data items include but are not limited to the type of multimedia device, the application process identifier of the application, the application name, the path of the application, and the number of times the multimedia device is called.

[0059] In one embodiment, after the terminal sends an acquisition instruction for acquiring process information to the daemon process through the main process, the daemon process acquires the auxiliary process identifier corresponding to the multimedia device, and acquires the data item of the running application corresponding to the multimedia device according to the auxiliary process identifier.

[0060] Among them, a daemon process can be a process that runs in the background and is not controlled by the terminal. The function of monitoring and analyzing multimedia devices is placed in the daemon process. The daemon process generally resides in the background, has greater authority, and can obtain process information of each running application.

[0061] In one embodiment, when the terminal receives an acquisition request through the daemon, it obtains the auxiliary process identifier corresponding to the multimedia device, adds the auxiliary process identifier to the system help instruction (LSMP), and obtains the data item corresponding to the running application by executing the system help instruction.

[0062] S206, filtering out data items belonging to the application programs in the whitelist from the data items.

[0063] In one embodiment, the terminal determines the application corresponding to the corresponding data item according to the process identifier carried in the data item through the daemon process. The terminal determines whether the application corresponding to the data item is in the whitelist through the daemon process. If it is in the whitelist, the data items belonging to the application in the whitelist are filtered out to obtain the data items of the application outside the whitelist. The terminal passes the obtained data items to the main process through the daemon process, so that the client obtains the data items of the application outside the whitelist.

[0064] S208, generating process information for indicating the use status of the target application for the multimedia device according to the data items obtained after filtering; the target application does not belong to the whitelist.

[0065] The data items obtained after filtering are data items that do not belong to the applications in the whitelist. The process information may include information about the multimedia devices (such as microphones or cameras) used during the running of the application. In addition, the process information may also include a process identifier to distinguish the application to which the process information belongs.

[0066] In one embodiment, the terminal obtains the historical data item, obtains the data change item by comparing the data item with the historical data item, and generates process information including the data change item. The data change item can be used to indicate the use status of the multimedia device by the target application. The use status can include the state of being used and the state of not being used.

[0067] The data change item can be used to indicate whether the target application uses the multimedia device. For example, the data change item can include one of the three values ​​of -1, 0 and 1. When the multimedia device is a microphone, -1 indicates that the application does not use the microphone. 0 indicates that the state has not changed. If the target application was detected to use the microphone last time, it is also using the microphone this time; if the target application was detected not to use the microphone last time, it is also not using the microphone this time. 1 indicates that the target application is using the microphone.

[0068] In one embodiment, after the terminal obtains the process information through the main process, the data change items carried in the process information are added to the monitoring log according to the process identifier. The monitoring log is stored in the database to find out the situation of the application using the multimedia device, such as whether it is being used or stopped. Among them, -1 means that the application is not using the multimedia device; or, if it was being used during the last monitoring, it means that the application has stopped using the multimedia device. 0 means that the status has not changed. 1 means that the target application is using the multimedia device.

[0069] In one embodiment, when a log display operation triggered on a monitoring setting page is detected, the terminal displays a monitoring log page, which contains the parsed monitoring log. When displaying the content in the monitoring log, the data change item is converted into corresponding text content, such as converting a data change item -1 into "multimedia device not in use" or the multimedia device has stopped being used.

[0070] For example, when a user clicks Figure 4 When you click the "Monitoring Log" control in the terminal display, the page on the terminal display will jump to the monitoring log page, such as Figure 7 As shown in the figure, during the first monitoring (i.e. YYYY.MM.DD hh1:mm1), application 1 is using the camera; during the second monitoring (i.e. YYYY.MM.DD hh2:mm2), application 1 has stopped using the camera. Among them, YYYY represents the year, MM represents the month, DD represents the two-digit date of the month (such as 01-31), hh represents the hour, and mm represents the minute. In actual application, it can also be accurate to seconds.

[0071] S210: Outputting a prompt message for prompting the target application to use the multimedia device according to the process information.

[0072] The prompt message may be in the form of pure text or text + dialog box. For example, a dialog box is output to indicate that application A is using the camera, and controls such as "allow" and "block" may be set on the dialog box. Figure 8 When you click the "Allow" control, it means that the application A is allowed to use the camera. When you click the "Block" control, it means that the application A is not allowed to use the camera.

[0073] In one embodiment, after the terminal receives the process information of the target application's use of the multimedia device, the terminal determines whether the target application is using the multimedia device based on the process information through the main process. If not, the monitoring process continues to be initiated in the next scheduled monitoring cycle; if yes, a prompt message containing prompt text and corresponding selection controls is generated. When receiving an instruction issued by the "allow" control, the target application is allowed to use the multimedia device. When receiving an instruction issued by the "block" control, a blocking instruction is issued to block the target application from using the multimedia device, so that the terminal blocks the target system from calling the multimedia device through the corresponding management process or management system.

[0074] In one embodiment, after the terminal displays the prompt message, if an instruction issued by the first control is detected, the terminal displays a selection page, and the first confirmation option or the second confirmation option can be selected on the selection page. When the first confirmation instruction in response to the prompt message is received, the target application is allowed to use the multimedia device this time; when the second confirmation instruction in response to the prompt message is received, the target application is added to the whitelist; when the blocking instruction in response to the prompt message is received, the target application is stopped from using the multimedia device.

[0075] like Fig. 9 As shown in the selection page, the user can select Allow only this time. If Allow only this time is selected, the target application is allowed to use the multimedia device this time. If Allow all the time is selected, the target application is added to Figure 5 The target application is added to the whitelist so that the target application is always allowed to use the multimedia device this time.

[0076] In one embodiment, before S210, the method may further include: the terminal determines whether a prompt message for prompting the target application to use the multimedia device has been output within a historical time period; if not, the terminal outputs a prompt message for prompting the target application to use the multimedia device; if so, the prompt message is not output, so as to avoid frequent prompts to the user when the user ignores the prompt, thereby affecting the user experience.

[0077] The historical time period may be calculated starting from the current monitoring time, such as t0 (current monitoring time), t1 (a certain time in history) and t2 (a certain time in the future). Then, the historical time period is the time period from t1 to t2.

[0078] In the above embodiment, by configuring a whitelist of applications that are allowed to use multimedia devices, data items belonging to applications in the whitelist are filtered out during the monitoring process, so that data items about target applications outside the whitelist can be obtained, and then process information about the use status of multimedia devices by the target applications can be obtained, so that targeted monitoring of applications can be achieved according to user needs. A prompt message for prompting the target application to use the multimedia device is output based on the process information, so that the user can know that the application is illegally using the multimedia device, so that the user can perform corresponding operations, thereby effectively preventing the application from illegally using the multimedia device to collect user information, and ensuring the security of user information.

[0079] In one embodiment, Fig.10 As shown, the method may also include:

[0080] S1002, sending a verification request carrying a signature to the daemon process through the main process.

[0081] The signature may be an encrypted string, which is a digital authentication code applied to the operating system provider. The encryption method may be public key encryption or private key encryption.

[0082] For example, for the Lemon client, before the Lemon client is first released to users, the application developer will apply for a signature from the operating system provider. When the user uses the Lemon client, the terminal will start a main process, and send a verification request with a signature to the daemon process through the main process, so that the daemon process can establish a communication connection with the main process. When the daemon process obtains the process information of whether the target application uses the multimedia device, it returns the process information to the main process.

[0083] In one embodiment, the method further includes: the terminal monitors system callback events; when the system callback event is an event to start monitoring multimedia devices, start a timer; after S1002, the method may further include: sending a process information acquisition request to the daemon process according to the timing period of the timer.

[0084] In one embodiment, before the terminal monitors the system callback event, it also receives a multimedia device start instruction triggered on the monitoring setting page, and then starts monitoring the use of the multimedia device. When the system uses the multimedia device, the terminal receives the system callback event through the main process.

[0085] For example, Figure 4 As shown, when the user turns on the switch button of the camera and / or microphone protection, the monitoring of the camera and / or microphone use will be started. When the system uses the camera or microphone, the terminal will receive the system callback event through the main process to turn on or off the timer according to the system callback event.

[0086] S1004: When the signature meets the signature condition, a communication connection between the main process and the daemon process is established.

[0087] In one embodiment, the terminal parses the verification request through the daemon process to obtain the signature, and then decrypts the signature to obtain the corresponding string. The terminal obtains the application authentication list through the daemon process. The application authentication list is stored in the sandbox and only the daemon process is allowed to access it. It determines whether the string matches the authentication code in the application authentication list. If it matches, it means that the signature meets the signature condition. Alternatively, the terminal sends the decrypted string to the verification server through the daemon process so that the verification server can perform signature verification on the string.

[0088] S1006: Send a process information acquisition request to the daemon process through the communication connection.

[0089] In one embodiment, the terminal starts a timer, and sends a process information acquisition request to the daemon process through the communication connection according to the timing period of the timer.

[0090] S1008, reading a white list, where the white list records the application programs that are allowed to use the multimedia devices on the terminal.

[0091] S1010, obtaining data items of an application program running on the terminal and associated with the multimedia device.

[0092] S1012, filtering out data items belonging to applications in the whitelist from the data items.

[0093] For S1008-S1012, reference may be made to S204-S208.

[0094] S1014, based on the filtered data items, obtaining process information of the target application's use status of the multimedia device; the target application does not belong to the whitelist.

[0095] In one embodiment, the terminal compares the filtered data items with the historical data items through a daemon process to obtain data change items; the data change items are used to indicate the status of the target application using the multimedia device; process information including the data change items is generated; the method also includes: returning the process information to the main process; the returned process information is used to instruct the main process to output a prompt message for prompting the target application to use the multimedia device.

[0096] The multimedia device may be a camera or a microphone. When the multimedia device is a camera, the corresponding auxiliary process may be a camera auxiliary process (VDCAssistant) that provides image acquisition. When the multimedia device is a microphone, the corresponding auxiliary process may be an audio auxiliary process (coreaudiod) that provides audio services.

[0097] In one embodiment, the step of generating process information including data change items may specifically include: when the multimedia device is a microphone, assembling the data change items to generate process information including the assembled data change items; when the multimedia device is a camera and the application using the camera belongs to a preset application set, updating the application array of the application for indicating the camera usage status according to the data change items, and generating process information based on the updated application array.

[0098] Among them, when the multimedia device is a microphone, it is possible to directly determine whether the application is using the microphone through the data change item. For a certain application, when there are many corresponding data change items, the data change items can be combined together. The preset application set can be a set of applications developed by the operating system provider. The application belongs to the preset application set, which means that the application is an application developed by the operating system provider.

[0099] In one embodiment, when the terminal obtains the auxiliary process identifier corresponding to the microphone, the terminal adds the auxiliary process identifier to the LSMP, and obtains the data items of all running applications calling the microphone through the LSMP. The terminal obtains the data change item by comparing the data item with the historical data item, and generates process information including at least the data change item.

[0100] The above data items include but are not limited to microphone type, application process identifier of the application, application name, path of the application and number of times the microphone is called.

[0101] For example, in the data item obtained this time, the number of times the microphone is called is m times, and the number of times the microphone is called in the historical data item is n. If m is greater than n, it means that the application is using the microphone; if m is equal to n, it means that the application's use of the microphone has not changed. If the application did not use the microphone during the last monitoring, it did not use the microphone this time; if the application was using the microphone during the last monitoring, it is also using the microphone this time; if m is less than n, it means that the application is not using the microphone. It should be noted that for the number of times the microphone is called in the data item, if the microphone is called, it will be increased by 1 based on the last time, and if the call is stopped or the call ends, it will be reduced by 1 based on the last time.

[0102] In one embodiment, the step of generating process information including data change items may specifically include: when the multimedia device is a camera and the application using the camera does not belong to a preset application set, the terminal extracts the application process identifier in the data item; obtains application data of the corresponding application according to the application process identifier; when it is determined that the application data includes a camera feature interface, the terminal marks the camera status identifier as enabled in the data change item; and generates process information including the marked data change items.

[0103] In one embodiment, when it is determined that the application data does not contain a camera feature interface, the terminal determines whether there is a historical activation item for enabling the camera; if so, the camera status identifier is marked as a disabled state in the data change item; and process information including the marked data change item is generated.

[0104] The fact that the application does not belong to the preset application set indicates that the application is not developed by the operating system provider but by a third-party service provider. The application data is the data generated during the operation of the application, which may also be referred to as sample data in subsequent embodiments.

[0105] For example, when the multimedia device is a camera, and the application using the camera is not an application developed by the operating system provider, an application instance (sample) analysis is performed for the application process identifier in the data item, and the instance data of the corresponding application process is obtained according to the application process identifier, and it is determined whether the instance data contains the characteristic interface "CMIOGraph::DoWork" for using the camera. If it does, the Delta identifier in the data change item is marked as the camera enable state. If it does not contain, the historical enablement item is obtained, and it is determined whether there is an enablement item in the historical enablement item for the application to enable the camera last time. If not, the enablement item is ignored; if it does, the Delta identifier in the data change item is marked as the camera disable state, and process information containing the marked data change item is generated, and the corresponding startup item is removed.

[0106] S1016: Outputting a prompt message for prompting the target application to use the multimedia device according to the process information.

[0107] In one embodiment, the method may further include: when the main process receives process information returned by the daemon process and indicating that the target application uses the multimedia device, determining whether the target application uses the multimedia device based on the process information by the main process; when the target application is using the multimedia device, outputting a prompt message; the prompt message is used to indicate that the target application is using the multimedia device.

[0108] In the above embodiment, before obtaining the process information of the application, it is necessary to perform signature verification on the main process, and establish a communication connection between the main process and the daemon process after the verification is passed, thereby effectively preventing the application from illegally using multimedia devices to collect user information and ensuring the security of user information.

[0109] like Fig.11 As shown, in one embodiment, a timing diagram of a call management method of a terminal multimedia device is provided, and the call management method of the terminal multimedia device specifically includes the following steps:

[0110] S1102, the main process sends a process information acquisition request to the daemon process according to the timing cycle of the timer.

[0111] In one embodiment, before S1102, the method may further include: monitoring a system callback event; and when the system callback event is an event for starting to monitor a multimedia device, starting a timer.

[0112] S1104, when the signature of the main process meets the signature condition, a communication connection between the main process and the daemon process is established.

[0113] S1106: The daemon process reads a white list, which records the applications that are allowed to use the multimedia devices on the terminal.

[0114] S1108, the daemon process obtains the auxiliary process identifier corresponding to the multimedia device.

[0115] S1110, the daemon process executes LSMP to obtain data items of running applications corresponding to the multimedia device, and filters out data items of applications in the whitelist.

[0116] S1112, the daemon process compares the data item with the historical data item to obtain a data change item.

[0117] S1114, when the multimedia device is a microphone, the daemon process assembles data change items and generates process information including the data change items.

[0118] S1116, process information of the main process application.

[0119] S1118, the main process outputs a prompt message.

[0120] S1120: When the multimedia device is a camera and the application program using the camera belongs to a preset application set, the daemon process updates the application array and generates process information including the updated application array.

[0121] S1122, process information of the main process application.

[0122] S1124, the main process outputs a prompt message.

[0123] S1126: When the multimedia device is a camera and the application program using the camera does not belong to the preset application set, the daemon process extracts the application process identifier in the data item.

[0124] S1128, the daemon process obtains application data of the corresponding application program according to the application process identifier.

[0125] S1130, when the application data includes a camera feature interface, the daemon process marks the camera status identifier as an enabled state in the data change item, and generates process information including the marked data change item.

[0126] In one embodiment, when it is determined that the application data does not contain a camera feature interface, the daemon process determines whether there is a historical activation item for enabling the camera; if so, the camera status identifier is marked as disabled in the data change item; and process information containing the marked data change item is generated.

[0127] S1132, process information of the main process application.

[0128] S1134, the main process outputs a prompt message.

[0129] In one embodiment, after outputting the prompt message, the method may further include: when a first confirmation instruction in response to the prompt message is received, allowing the target application to use the multimedia device this time; when a second confirmation instruction in response to the prompt message is received, adding the target application to a whitelist; when a blocking instruction in response to the prompt message is received, stopping the target application from using the multimedia device.

[0130] Since monitoring and analysis of microphones and cameras requires administrator privileges and cannot be performed in upper-level applications, multiple processes are mainly used to implement this. The logic control and UI parts are placed in the main process, and the monitoring and analysis parts are placed in the daemon process, where:

[0131] The main process is responsible for control logic, UI interface, whitelist, system notification and other logic, and adopts MVC three-layer architecture: presentation layer, data layer and control layer.

[0132] Among them, (1) the display layer includes two parts: UI window and system notification UI. The UI window part includes four windows: main control window, whitelist window, application selection window and log window. Fig.12 As shown in (a)-(d) in .

[0133] System notification contains two interactive logics, such as Fig.13 As shown in the figure, it includes allowing and blocking applications to use the camera or microphone. If you allow an application to use the camera or microphone, a pop-up window will pop up asking you to allow it once or always. The pop-up window UI is as follows: Fig.14 If it is blocked, then the process using the camera and / or microphone is stopped.

[0134] (2) Data layer, including: camera monitoring model, microphone monitoring model, whitelist model and daemon processing item model. Fig.15As shown in (a) in the figure, the model includes: device name (deviceName), device connection identifier (deviceConnectionID), event of starting the listening camera (startListenCamera) and event of stopping the listening camera (stopListenCamera). Fig.15 As shown in (b) in the figure, the model includes: device name (deviceName), device connection identifier (deviceConnectionID), event of starting to listen to the camera (startListenAudio) and event of stopping to listen to the camera (stopListenAudio). Fig.15 As shown in (c) in the figure, the model includes: application icon (appIcon), executable name (executName), application path (appPath), application identifier (appIdentifrer), application name (appName), whether to monitor the camera (isWatchCamera) and whether to monitor the microphone (isWatchAudio). The daemon process processing item model is as follows Fig.15 As shown in (d) in FIG. 1 , the model includes: device type (device_type), process ID (PID), name (name), number of times the multimedia device is called (time_count) and path of the application (path).

[0135] (3) Control layer, such as Fig.16 As shown in the figure, the control class OwlManager coordinates the overall control process. OwlManager registers the system's camera and microphone device monitoring through CameraDeviceObserver and AudioDeviceObserver. When receiving the system callback event, if it is an on event, the timer polling daemon is started to obtain the specific process information of the camera and microphone, and then a system notification pops up to remind the user; if it is a deactivation event, the timer is ended.

[0136] In addition to the device coordination control logic, the control class also includes control UI interaction logic, including interface pop-ups, jumps, system notifications and allowed interactions, as well as database operation logic, user whitelist interaction data, device usage information, etc., which will be persisted in the local database.

[0137] As an example, the above-mentioned call management method of the terminal multimedia device can be implemented on a MAC device, which has a Lemon client installed. When the Lemon client is started, the main process will be started to start monitoring the behavior of the application using the camera and microphone, such as Fig.17 As shown, the specific steps are as follows:

[0138] S1702, read the configured whitelist.

[0139] S1704, the main process starts monitoring of the camera and microphone.

[0140] S1706, receiving the monitoring event, starting the timer, obtaining the process information of the camera and microphone from the daemon process, and filtering out the process information of the application on the whitelist.

[0141] S1708, the daemon process obtains the data items and processes using the camera and microphone through the system's auxiliary process, and returns the results to the main process.

[0142] S1710, the main process receives the process information returned by the daemon process, and pops up a system notification to prompt.

[0143] S1712: Allow or prevent the application from using the camera or microphone according to the operation performed by the user on the system notification.

[0144] As another example, after the Lemon client is started, the main process is started to start monitoring the application's use of the camera and microphone, such as Fig.18 As shown, the specific steps are as follows:

[0145] S1802, the main process starts monitoring of the camera and microphone.

[0146] S1804, the main process receives the monitoring event.

[0147] S1806, start the timer and initiate a process analysis request to the daemon process.

[0148] S1808, the daemon process obtains process information using the camera and microphone.

[0149] S1810, return the result to the main process.

[0150] S1812, the main process displays UI notifications.

[0151] S1814: When no monitoring event is received, stop the timer.

[0152] The user can use the monitoring setting page (such as Figure 4 As shown), after the protection of the camera and microphone is turned on, the main thread starts the camera and microphone to monitor the system. When the application uses the camera or microphone, the main thread receives a callback event, and then starts or ends the timer according to the callback event to perform subsequent related operations, such as Fig.19 shown.

[0153] When the timer reaches the set timing cycle, the main process sends a request to the daemon through inter-process communication (XPC) to obtain process information, so as to obtain specific process information from the daemon. The daemon obtains process information related to the camera and microphone through the system's auxiliary process. If it is a camera, it is also necessary to sample and obtain feature information from the target process for analysis, and finally obtain the process information that actually uses the camera and microphone and return it to the main process. Fig. 20 As shown, the specific implementation logic of the daemon process is as follows:

[0154] The daemon process receives the acquisition request sent by the main process. If the daemon process determines that the acquisition request comes from a signed and authenticated process, it can start communicating with the main process. When the request is for obtaining microphone usage information, the PID of the microphone auxiliary process is obtained, the whitelist is filtered out, and then the LSMP command is executed. The data items using the microphone in the microphone auxiliary process are analyzed by LSMP, and the current data items are compared with the historical MSLP data items to obtain the newly added data change items. The obtained data change items are assembled, and finally the process information containing the data change items is obtained and returned to the main process.

[0155] When the request is for obtaining camera usage information, obtain the PID of the camera auxiliary process, filter out the whitelist, and then execute the LSMP command. Use LSMP to analyze the data items of the camera used in the camera auxiliary process, compare the current data items with the historical MSLP data items, and obtain the newly added data change items. Continue to determine whether the application corresponding to the PID in the data item is an Apple application. If it is an Apple application, update the application data of the Apple application, assemble the obtained data change items, and finally obtain the process information containing the data change items, and then return it to the main process.

[0156] If it is not an Apple application, a sub-process analysis is performed, that is, the corresponding instance data is obtained for the PID in the data item for analysis, and it is determined whether the instance data contains the camera usage feature interface "CMIOGraph::DoWork". If it does, the Delta identifier in the data change item is marked as the camera enabled state. If it does not contain, the historical enabled item is obtained to determine whether there is an enabled item in the historical enabled item that enabled the camera last time by the application. If not, the enabled item is ignored; if it does, the Delta identifier in the data change item is marked as the camera disabled state, and the obtained data change items are assembled to finally obtain the process information containing the data change items, which is then returned to the main process, and the corresponding startup item is removed.

[0157] After the main process receives the process information returned by the daemon process, it will add the data item to the Log monitoring log, save it in the database, and pop up a system notification to remind the user. The user can allow or block the application from using the camera and / or microphone based on the interaction with the notification. The allow operation is divided into one-time allowance and always allowance. If it is always allowed, the application will be added to the whitelist, such as Fig. 9 shown.

[0158] Regarding the whitelist, each time the Lemon client is started, the set whitelist will be passed to the daemon through inter-process communication (XPC), so that the daemon will filter out the whitelist items when analyzing the application process. Using the XPC method, the main process can communicate with the daemon only after signature authentication, preventing the daemon from being invaded by the application and ensuring the security of data and communication channels.

[0159] By implementing the above embodiments, personal computers can be effectively protected, and users can be notified when using cameras and microphones, preventing applications from starting cameras or microphones in the background to obtain users' private data.

[0160] Figure 2 , 11 , 17-18, 20 are flowcharts of a method for managing the calling of a terminal multimedia device in an embodiment. It should be understood that although Figure 2 , 11 The steps in the flowcharts of 17-18 and 20 are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 , 11 , 17-18, and at least part of the steps in 20 may include multiple sub-steps or multiple stages. These sub-steps or stages do not necessarily have to be executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily one by one, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0161] like Fig.21 As shown, in one embodiment, a call management device for a terminal multimedia device is provided, and the call management device for the terminal multimedia device specifically includes: a whitelist reading module 2102, a data acquisition module 2104, a data filtering module 2106, a process information acquisition module 2108 and a prompt message output module 2110; wherein:

[0162] A whitelist reading module 2102 is used to read a whitelist, which records the applications that are allowed to use the multimedia devices on the terminal;

[0163] The data acquisition module 2104 is used to acquire data items of the application running on the terminal and associated with the multimedia device;

[0164] A data filtering module 2106, used to filter out data items belonging to applications in the whitelist from the data items;

[0165] The process information acquisition module 2108 is used to obtain the process information of the target application's use status of the multimedia device based on the data items obtained after filtering; the target application does not belong to the whitelist;

[0166] The prompt message output module 2110 is used to output a prompt message for prompting the target application to use the multimedia device according to the process information.

[0167] In one embodiment, Fig. 22 As shown, the device also includes: a whitelist configuration module 2112; wherein: the whitelist configuration module 2112 is used to display the whitelist configuration page when an operation instruction triggered by the whitelist control on the monitoring setting page is obtained; when a whitelist adding instruction is received, the application specified by the whitelist adding instruction is added to the whitelist configuration page; and the use rights of the multimedia device are configured for the added application.

[0168] In the above embodiment, by configuring a whitelist of applications that are allowed to use multimedia devices, data items belonging to applications in the whitelist are filtered out during the monitoring process, so that data items about target applications outside the whitelist can be obtained, and then process information about the use status of multimedia devices by the target applications can be obtained, so that targeted monitoring of applications can be achieved according to user needs. A prompt message for prompting the target application to use the multimedia device is output based on the process information, so that the user can know that the application is illegally using the multimedia device, so that the user can perform corresponding operations, thereby effectively preventing the application from illegally using the multimedia device to collect user information, and ensuring the security of user information.

[0169] In one embodiment, Fig. 22 As shown, the device may further include: a verification module 2112; wherein:

[0170] Verification module 2112, used to send a verification request carrying a signature to the daemon process through the main process; when the signature meets the signature condition, establish a communication connection between the main process and the daemon process;

[0171] The whitelist reading module 2102 is also used to read the whitelist configured through the whitelist configuration page through the daemon process when a process information acquisition request for acquiring the running application process is received according to the communication connection.

[0172] In one embodiment, the data acquisition module 2104 is further used to: acquire the auxiliary process identifier corresponding to the multimedia device through the daemon process; and acquire the data items of the running application corresponding to the multimedia device according to the auxiliary process identifier.

[0173] In one embodiment, the process information acquisition module 2108 is further used to: compare the filtered data items with the historical data items through the daemon process to obtain data change items; the data change items are used to indicate the state of the target application using the multimedia device; generate process information including the data change items;

[0174] The process information acquisition module 2108 is also used to return the process information to the main process; the returned process information is used to instruct the main process to output a prompt message for prompting the target application to use the multimedia device.

[0175] In one embodiment, the process information acquisition module 2108 is also used for: when the multimedia device is a microphone, assembling the data change items to generate process information containing the assembled data change items; when the multimedia device is a camera and the application using the camera belongs to a preset application set, updating the application array of the application for indicating the camera usage status according to the data change items, and generating process information based on the updated application array.

[0176] In one embodiment, the process information acquisition module 2108 is also used for: when the multimedia device is a camera and the application using the camera does not belong to a preset application set, extracting the application process identifier in the data item; obtaining application data of the corresponding application according to the application process identifier; when it is determined that the application data contains a camera feature interface, marking the camera status identifier as enabled in the data change item; and generating process information including the marked data change item.

[0177] In one embodiment, the process information acquisition module 2108 is also used for: when it is determined that the application data does not contain a camera feature interface, determining whether there is a historical activation item for enabling the camera; if so, marking the camera status identifier as a disabled state in the data change item; and generating process information including the marked data change item.

[0178] In one embodiment, the prompt message output module 2110 is also used for: when the main process receives process information returned by the daemon process and indicating that the target application uses the multimedia device, the main process determines whether the target application uses the multimedia device based on the process information; when the target application is using the multimedia device, outputs a prompt message; the prompt message is used to indicate that the target application is using the multimedia device.

[0179] In one embodiment, Fig. 22 As shown, the device may further include: a monitoring module 2114; wherein:

[0180] The monitoring module 2114 is used to monitor system callback events; when the system callback event is an event to start monitoring multimedia devices, the timer is started; and a process information acquisition request is sent to the daemon process according to the timing cycle of the timer.

[0181] In one embodiment, Fig. 22 As shown, the device further includes: a processing module 2116; wherein:

[0182] Processing module 2116 is used to: when a first confirmation instruction is received in response to a prompt message, allow the target application to use the multimedia device this time; when a second confirmation instruction is received in response to the prompt message, add the target application to the whitelist; when a blocking instruction is received in response to the prompt message, stop the target application from using the multimedia device.

[0183] In the above embodiment, before obtaining the process information of the application, it is necessary to perform signature verification on the main process, and establish a communication connection between the main process and the daemon process after the verification is passed, thereby effectively preventing the application from illegally using multimedia devices to collect user information and ensuring the security of user information.

[0184] Fig.23 The internal structure diagram of a computer device in one embodiment is shown. The computer device may specifically be Figure 1 The terminal 110 in FIG. Fig.23As shown, the computer device includes a processor, a memory, a network interface, an input device and a display screen connected through a system bus. Among them, the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program. When the computer program is executed by the processor, the processor can implement a call management method for a terminal multimedia device. The internal memory may also store a computer program. When the computer program is executed by the processor, the processor can execute a call management method for a terminal multimedia device. The display screen of the computer device may be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device may be a touch layer covering the display screen, or a button, trackball or touchpad provided on the housing of the computer device, or an external keyboard, touchpad or mouse, etc.

[0185] Those skilled in the art will understand that Fig.23 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0186] In one embodiment, the calling management device of the terminal multimedia device provided by the present application can be implemented in the form of a computer program. The computer program can be Fig.23 The memory of the computer device can store various program modules constituting the call management device of the terminal multimedia device, for example, Fig.21 The whitelist reading module 2102, data acquisition module 2104, data filtering module 2106, process information acquisition module 2108 and prompt message output module 2110 are shown. The computer program composed of each program module enables the processor to execute the steps of the calling management method of the terminal multimedia device of each embodiment of the present application described in this specification.

[0187] For example, Fig.23 The computer device shown can be Fig.21 The whitelist reading module 2102 in the call management device of the terminal multimedia device shown executes S202. The computer device may execute S204 through the data acquisition module 2104. The computer device may execute S206 through the data filtering module 2106. The computer device may execute S208 through the process information acquisition module 2108. The computer device may execute S210 through the prompt message output module 2110.

[0188] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the calling management method of the terminal multimedia device. The steps of the calling management method of the terminal multimedia device here may be the steps of the calling management method of the terminal multimedia device in each of the above embodiments.

[0189] In one embodiment, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a processor, the processor executes the steps of the calling management method of the terminal multimedia device. The steps of the calling management method of the terminal multimedia device here can be the steps of the calling management method of the terminal multimedia device in each of the above embodiments.

[0190] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0191] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0192] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for managing the calling of a terminal multimedia device, applied to a client for monitoring the multimedia device, comprising: Reading a whitelist, wherein the whitelist records applications that are allowed to use multimedia devices on the terminal; After sending an acquisition instruction for acquiring process information to the daemon process through the main process of the client, the auxiliary process identifier corresponding to the multimedia device is acquired through the daemon process; the auxiliary process identifier is added to the system help instruction, and the data items corresponding to the application running on the terminal are acquired by executing the system help instruction; the data items include the type of multimedia device, the application process identifier of the application, the application name, the path of the application and the number of times the multimedia device is called; filtering out data items belonging to applications in the whitelist from the data items; By comparing the filtered data items with the historical data items, a data change item is obtained, and process information including the data change item is generated; the process information is used to indicate whether the target application uses a multimedia device during operation, and the target application does not belong to the whitelist; When it is determined according to the process information that the target application uses the multimedia device, outputting a prompt message for prompting the target application to use the multimedia device; When it is determined according to the process information that the target application does not use the multimedia device, the monitoring process is continuously initiated in the next scheduled monitoring cycle.

2. The method according to claim 1, characterized in that The method further comprises: Display the monitoring settings page of multimedia devices; When an operation instruction triggered by a whitelist control on the monitoring setting page is obtained, a whitelist configuration page is displayed; When receiving a whitelist adding instruction, adding the application specified by the whitelist adding instruction to the whitelist configuration page; The usage permission of the multimedia device is configured for the added application.

3. The method according to claim 1, characterized in that The method further comprises: Send a verification request with a signature to the daemon process through the main process; When the signature meets the signature condition, establishing a communication connection between the main process and the daemon process; The read whitelist includes: When a process information acquisition request for acquiring a running application process is received according to the communication connection, the whitelist configured through the whitelist configuration page is read through the daemon process.

4. The method according to claim 1, characterized in that The method further comprises: The data change items carried in the process information are added to the monitoring log according to the process identifier; wherein the monitoring log is stored in a database so as to find out the situation of the application using the multimedia device.

5. The method according to claim 3 or 4, characterized in that: The step of obtaining a data change item by comparing the filtered data item with the historical data item and generating process information including the data change item comprises: Comparing the filtered data items with the historical data items through the daemon process to obtain data change items; generating process information including the data change items; The method further includes: returning the process information to the main process; the returned process information is used to instruct the main process to output a prompt message for prompting the target application to use the multimedia device.

6. The method according to claim 5, characterized in that The generating of the process information including the data change item includes: When the multimedia device is a microphone, the data change items are assembled to generate process information including the assembled data change items; When the multimedia device is a camera and the application using the camera belongs to a preset application set, the application array of the application for indicating the camera usage status is updated according to the data change item, and process information is generated based on the updated application array.

7. The method according to claim 5, characterized in that The generating of the process information including the data change item includes: When the multimedia device is a camera, and the application program using the camera does not belong to the preset application set, extracting the application process identifier in the data item; Acquire application data of a corresponding application program according to the application process identifier; When it is determined that the application data includes a camera feature interface, marking the camera state identifier as an enabled state in the data change item; Generate process information including the marked data change items.

8. The method according to claim 7, characterized in that The method further comprises: When it is determined that the application data does not include a camera feature interface, determining whether there is an activation item for historically activating the camera; If yes, marking the camera status identifier as disabled in the data change item; Generate process information including the marked data change items.

9. The method according to claim 3, characterized in that: When it is determined according to the process information that the target application uses the multimedia device, outputting a prompt message for prompting the target application to use the multimedia device comprises: When the main process receives the process information returned by the daemon process and indicating that the target application uses the multimedia device, the main process determines whether the target application uses the multimedia device according to the process information; When the target application is using the multimedia device, a prompt message is output; the prompt message is used to indicate that the target application is using the multimedia device.

10. The method according to claim 3, characterized in that: The method further comprises: Monitor system callback events; When the system callback event is an event for starting to monitor the multimedia device, starting a timer; Send a process information acquisition request to the daemon process according to the timing period of the timer.

11. The method according to claim 1, characterized in that: The method further comprises: When receiving a first confirmation instruction in response to the prompt message, allowing the target application to use the multimedia device this time; When a second confirmation instruction in response to the prompt message is received, adding the target application to the whitelist; When a blocking instruction is received in response to the prompt message, the target application is stopped from using the multimedia device.

12. A terminal multimedia device call management device, applied to a client of a monitoring multimedia device, characterized in that: The device comprises: A whitelist reading module, used to read a whitelist configured through a whitelist configuration page, wherein the whitelist records applications that are permitted to use multimedia devices on the terminal; A data acquisition module, configured to acquire an auxiliary process identifier corresponding to the multimedia device through the daemon process after sending an acquisition instruction for acquiring process information to the daemon process through the main process of the client; add the auxiliary process identifier to a system help instruction, and acquire data items corresponding to the application running on the terminal by executing the system help instruction; the data items include the type of multimedia device, the application process identifier of the application, the name of the application, the path of the application, and the number of times the multimedia device is called; A data filtering module, used to filter out data items belonging to the application in the whitelist from the data items; A process information acquisition module, used to obtain data change items by comparing the filtered data items with the historical data items, and generate process information including the data change items; the process information is used to indicate whether the target application uses a multimedia device during operation, and the target application does not belong to the whitelist; A prompt message output module is used to output a prompt message for prompting the target application to use the multimedia device when it is determined according to the process information that the target application uses the multimedia device; when it is determined according to the process information that the target application does not use the multimedia device, continue to initiate the monitoring process in the next scheduled monitoring cycle.

13. The device according to claim 12, characterized in that The device also includes: A whitelist configuration module is used to display a monitoring setting page of a multimedia device; when an operation instruction triggered by a whitelist control on the monitoring setting page is obtained, the whitelist configuration page is displayed; when a whitelist adding instruction is received, the application specified by the whitelist adding instruction is added to the whitelist configuration page; and the use rights of the multimedia device are configured for the added application.

14. The device according to claim 12, characterized in that The device also includes: A verification module, used to send a verification request carrying a signature to the daemon process through the main process; when the signature meets the signature condition, establish a communication connection between the main process and the daemon process; The whitelist reading module is further configured to read the whitelist configured through the whitelist configuration page through the daemon process when a process information acquisition request for acquiring the running application process is received according to the communication connection.

15. The device according to claim 12, characterized in that The device also includes: The process information acquisition module is further used to add the data change items carried in the process information to the monitoring log according to the process identifier; wherein the monitoring log is stored in a database to facilitate searching for situations in which an application uses a multimedia device.

16. The device according to claim 14 or 15, characterized in that The process information acquisition module is further used to compare the data items obtained after filtering with the historical data items through the daemon process to obtain data change items; and generate process information including the data change items; The prompt message output module is also used to return the process information to the main process; the returned process information is used to instruct the main process to output a prompt message for prompting the target application to use the multimedia device.

17. The device according to claim 16, characterized in that The process information acquisition module is also used to assemble the data change items when the multimedia device is a microphone, and generate process information including the assembled data change items; when the multimedia device is a camera and the application using the camera belongs to a preset application set, the application array of the application for indicating the usage status of the camera is updated according to the data change items, and process information is generated based on the updated application array.

18. The device according to claim 16, characterized in that The process information acquisition module is also used to extract the application process identifier in the data item when the multimedia device is a camera and the application using the camera does not belong to a preset application set; obtain application data of the corresponding application according to the application process identifier; when it is determined that the application data contains a camera feature interface, mark the camera status identifier as an enabled state in the data change item; and generate process information including the marked data change item.

19. The device according to claim 18, characterized in that The process information acquisition module is also used to determine whether there is a historical activation item for enabling the camera when it is determined that the application data does not contain a camera feature interface; if so, mark the camera status identifier as a disabled state in the data change item; and generate process information including the marked data change item.

20. The device according to claim 14, characterized in that The prompt message output module is also used to determine whether the target application uses the multimedia device based on the process information when the main process receives the process information returned by the daemon process and indicating that the target application uses the multimedia device; when the target application is using the multimedia device, output a prompt message; the prompt message is used to indicate that the target application is using the multimedia device.

21. The device according to claim 14, characterized in that The device also includes: The monitoring module is used to monitor system callback events; when the system callback event is an event for starting to monitor the multimedia device, a timer is started; and a process information acquisition request is sent to the daemon process according to the timing cycle of the timer.

22. The device according to claim 12, characterized in that The device also includes: A processing module is used to allow the target application to use the multimedia device this time when a first confirmation instruction is received in response to the prompt message; add the target application to the whitelist when a second confirmation instruction is received in response to the prompt message; and stop the target application from using the multimedia device when a blocking instruction is received in response to the prompt message.

23. A computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, the processor is caused to perform the steps of the method according to any one of claims 1 to 11.

24. A computer device comprising a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the method according to any one of claims 1 to 11.

Images