A car machine application privacy protection method, device and equipment and readable storage medium

Abstract

A vehicle machine application privacy protection method, device and equipment and readable storage medium, the method comprises: monitoring the operation instruction for the target application of the vehicle machine end; in response to the operation instruction, collecting at least two kinds of biological characteristic information of the current operator; the biological characteristic information is matched with the preset owner characteristic template stored locally to carry out authentication; if the authentication is passed, the privacy interface of the target application is controlled to be displayed, if the authentication is not passed, the non-private interface is controlled to be displayed, and the account login session of the target application is maintained without interruption. When the authentication is not passed, the non-private interface is controlled to be displayed and the account login session is maintained without interruption, avoiding the cumbersome process of re-login caused by forced exit of account due to verification failure, ensuring the continuity and convenience of the owner when using again, so as to ensure the smoothness of user experience on the premise of ensuring the safety of private data.

Description

Technical Field

[0001] This application relates to the field of automotive smart cockpit technology, specifically to a method, device, equipment, and readable storage medium for protecting privacy in vehicle infotainment applications. Background Technology

[0002] With the rapid development of intelligent connected vehicle technology, the smart cockpit has become a core component of vehicles. The in-vehicle infotainment system not only provides basic navigation and entertainment functions but also widely integrates third-party applications such as payment, social communication, and personalized recommendations. These applications generate a large amount of user privacy data during use, such as payment accounts, historical routes, contact lists, and personal preference settings. With the increasing popularity of family car sharing and ride-sharing scenarios, it is becoming more common for different users to use in-vehicle applications in the same vehicle. How to ensure a convenient user experience for car owners while effectively preventing non-owners from snooping on or leaking the owner's privacy data has become a pressing technical requirement in the field of smart cockpits.

[0003] In existing technologies, privacy protection for in-vehicle applications typically employs either system-level account authentication or application-level separate login. In system-level authentication schemes, vehicle owners log in to their in-vehicle system account using a password or biometric identification. Upon successful login, they can access all third-party applications. Some schemes will forcibly log out the account if the driver leaves or the vehicle is turned off. In application-level protection schemes, some higher-security applications will have independent application locks, using biometric information for verification. If verification fails, the system will typically directly deny access, lock the screen, or forcibly log out the currently logged-in account, requiring the vehicle owner to re-enter their credentials to log in.

[0004] However, existing technical solutions have the following drawbacks: Current privacy protection strategies typically employ rigid tactics such as forcibly logging out the account or locking the device when authentication fails. This forces legitimate vehicle owners to re-execute a cumbersome login process after authentication failures due to factors like lighting or posture. The resulting session interruption severely impacts the continuity and convenience of use, making it difficult for existing privacy protection strategies to effectively balance user experience. Therefore, there is an urgent need for a technical solution that can effectively identify the operator to ensure security while maintaining session continuity even when authentication fails, thus ensuring a good user experience. Summary of the Invention

[0005] This application provides a method, apparatus, device, and readable storage medium for protecting privacy in in-vehicle applications, which can solve the technical problems in the prior art, such as forced account logout due to authentication failure leading to session interruption, poor convenience, and difficulty in balancing privacy protection and user experience.

[0006] In a first aspect, embodiments of this application provide a method for protecting privacy in in-vehicle applications, including: Monitor operational commands for target applications on the vehicle's infotainment system; In response to an operation command, at least two biometric information of the current operator are collected; Biometric information is matched and authenticated against a locally stored preset vehicle owner feature template; If authentication is successful, control the display of the target application's privacy interface; if authentication fails, control the display of the non-privacy interface and maintain the target application's account login session without interruption.

[0007] In conjunction with the first aspect, in one implementation, at least two biometric information of the current operator are collected, including: Identify the triggering scenarios for obtaining operation commands; Determine the target biometric combination strategy based on the triggering scenario; Biometric information of the current operator is collected based on a target biometric combination strategy. The triggering scenarios include touch screen operation scenarios and voice operation scenarios, and different triggering scenarios correspond to different biometric combination strategies.

[0008] In conjunction with the first aspect, in one implementation, determining a target biometric combination strategy based on the triggering scenario includes: When the triggering scenario is a touch screen operation scenario, the corresponding target biometric combination strategy is a combination of facial feature information and body posture feature information; When the triggering scenario is a voice operation scenario, the corresponding target biometric combination strategy is a combination of facial feature information and voiceprint feature information.

[0009] In conjunction with the first aspect, in one implementation, biometric information is matched and authenticated against a locally stored preset vehicle owner feature template, including: Extract feature vectors from biological characteristic information respectively; The similarity score is obtained by matching the feature vector with the corresponding template vector in the preset car owner feature template. If the similarity score is greater than or equal to the preset authentication threshold, the authentication is deemed successful.

[0010] In conjunction with the first aspect, in one implementation method, the in-vehicle application privacy protection method further includes: Record vehicle owner's historical usage data and determine reliable scenarios based on the historical usage data; In trusted scenarios, the preset authentication threshold is adjusted to the first threshold, which is lower than the preset authentication threshold. Among them, trusted scenarios include the time periods when car owners frequently perform operations.

[0011] In conjunction with the first aspect, in one implementation method, the in-vehicle application privacy protection method further includes: Responding to the owner's settings commands, obtain the privacy protection level set by the owner; Update the preset authentication threshold based on the preset mapping relationship between privacy protection level and authentication threshold.

[0012] In conjunction with the first aspect, in one implementation, the in-vehicle application privacy protection method further includes an identity verification step during operation: During the period when the target application displays the privacy interface, the biometric information of the current operator is collected again according to a preset time period or when a change in vehicle status is detected. The re-collected biometric information will be matched and authenticated with the preset vehicle owner feature template; If the number of consecutive authentication failures reaches a preset threshold, the target application will be switched from the privacy interface to the non-privacy interface, while the account login session will continue uninterrupted.

[0013] Secondly, embodiments of this application provide a vehicle infotainment application privacy protection device, including: The instruction detection module is used to monitor operation instructions for target applications on the vehicle's infotainment system. The biometric acquisition module is used to collect at least two biometric information of the current operator in response to operation commands; The matching and authentication module is used to match and authenticate biometric information with preset vehicle owner feature templates stored locally. The privacy control module is used to control the display of the target application's privacy interface if authentication is successful, and to control the display of the non-privacy interface if authentication fails, while maintaining the target application's account login session.

[0014] Thirdly, embodiments of this application provide a vehicle-mounted application privacy protection device, which includes a processor, a memory, and a vehicle-mounted application privacy protection program stored in the memory and executable by the processor. When the vehicle-mounted application privacy protection program is executed by the processor, it implements the steps of the vehicle-mounted application privacy protection method described above.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium storing a vehicle-mounted application privacy protection program, wherein when the vehicle-mounted application privacy protection program is executed by a processor, it implements the steps of the vehicle-mounted application privacy protection method described above.

[0016] The beneficial effects of the technical solutions provided in this application include: By monitoring operation commands for target applications on the vehicle's infotainment system, the system collects the current operator's biometric information and matches it with locally stored preset vehicle owner feature templates for authentication. This effectively identifies the current operator and prevents non-owner users from spying on or leaking private data through impersonation, thus improving the security of in-vehicle applications. At the same time, when authentication fails, the system controls the display of non-privacy interfaces and maintains the account login session without interruption. This avoids the cumbersome process of re-login caused by forced account exit due to verification failure, ensuring continuity and convenience for vehicle owners when they use the system again. Thus, while ensuring the security of privacy data, the system also considers the smoothness of the user experience. Attached Figure Description

[0017] Figure 1 This is a flowchart illustrating the first embodiment of the vehicle infotainment application privacy protection method of this application; Figure 2 This is a schematic diagram of the process for collecting biometric information according to an embodiment of this application; Figure 3 This is a detailed flowchart illustrating step S202 in an embodiment of this application; Figure 4 This is a schematic diagram of the matching authentication process in an embodiment of this application; Figure 5 This is a flowchart illustrating the identity verification steps in an embodiment of this application; Figure 6 This is a schematic diagram of the functional modules of an embodiment of the vehicle infotainment privacy protection device of this application; Figure 7 This is a schematic diagram of the hardware structure of the vehicle-mounted application privacy protection device involved in the embodiments of this application. Detailed Implementation

[0018] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0019] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0020] Firstly, embodiments of this application provide a method for protecting the privacy of in-vehicle applications.

[0021] In one embodiment, reference is made to Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the vehicle infotainment application privacy protection method of this application. Figure 1 As shown, the privacy protection methods for in-vehicle applications include: S101. Monitor operation commands for target applications on the vehicle's infotainment system; S102. In response to the operation command, collect at least two biometric information of the current operator; S103. Match and authenticate the biometric information with the preset vehicle owner feature template stored locally; S104. If authentication is successful, control the display of the target application's privacy interface; if authentication fails, control the display of the non-privacy interface and maintain the target application's account login session.

[0022] Specifically, in the embodiment of the vehicle infotainment system privacy application protection method, when configuring the owner's feature template for the first time, facial images can be captured through the vehicle's built-in DMS (Driver Monitoring System) camera, sitting posture skeletal key point information can be captured through the OMS (Occupant Monitoring System) camera, and voice samples can be captured through a microphone array. The vehicle's processor extracts the feature vectors of the above information, encrypts them, and stores them in the vehicle's local secure storage area to form a preset owner feature template. Meanwhile, for the target applications that need protection, these can be system-preset sensitive applications, such as payment-related applications, or applications containing a large amount of personal privacy information, or the vehicle owner can actively select the target applications that need protection.

[0023] Then, when the system detects the operation commands of the person in the vehicle to the target application, it first determines the current triggering scenario based on the type of operation command: if the operation command is a touch screen signal, it is determined to be a touch screen operation scenario; if the operation command is a voice wake-up signal, it is determined to be a voice operation scenario.

[0024] When the triggering scenario is a touchscreen operation, the system calls the DMS camera to collect the current operator's facial features, and simultaneously calls the OMS camera to assist in collecting the current operator's body posture features, forming a two-factor combination of face and posture. When the triggering scenario is a voice operation, the system calls the DMS camera to collect facial features, and simultaneously calls the microphone array to collect the current operator's voiceprint features, forming a two-factor combination of face and voiceprint.

[0025] Next, the collected biometric information is converted into feature vectors and matched with the corresponding template vectors in the stored preset car owner templates to obtain a similarity score. If the similarity score is greater than or equal to the preset authentication threshold, authentication is considered successful, and it is assumed that the operation command is from the car owner, requiring no privacy protection. If the similarity score is less than the preset authentication threshold, it is assumed that the operation command is from someone else, and the privacy control module sends a blocking command to the application layer, controlling the target application to only display a non-privacy interface or a blank interface, and prompting that authorization has not been granted, but maintaining the account login session of the target application without interruption. When the car owner returns to the vehicle and verifies again, there is no need to go through the complicated login process again, and the privacy content can be viewed directly again.

[0026] In addition, during operation, the embodiment requires periodic identity verification. The embodiment collects the current operator's biometric information for rapid verification (e.g., facial verification only) at preset time intervals (e.g., every 10 seconds) or when a change in vehicle status is detected (e.g., door opening, gear shifting). If multiple verifications fail, it indicates that the operator may have been replaced by someone other than the vehicle owner. The system then switches the target application from a private interface to a non-private interface and continues to maintain the account login session until authentication is successful again.

[0027] In this embodiment, by monitoring the operation commands of the target application on the vehicle-mounted system, the biometric information of the current operator is collected and matched with the preset vehicle owner feature template stored locally for authentication. This effectively identifies the current operator's identity and prevents non-vehicle owner users from spying on or leaking private data through impersonation, thus improving the security of the vehicle-mounted system application. At the same time, when authentication fails, a non-privacy interface is displayed while maintaining the account login session. This avoids the cumbersome process of re-login caused by forced account exit due to verification failure, ensuring continuity and convenience for vehicle owners when using the system again. Thus, while ensuring the security of privacy data, the system also considers the smoothness of the user experience.

[0028] Furthermore, in one embodiment, Figure 2 This is a schematic diagram of the process for collecting biometric information according to an embodiment of this application, such as... Figure 2 As shown, at least two biometric information of the current operator are collected, including: S201, the triggering scenario for obtaining operation instructions; S202. Determine the target biometric combination strategy based on the triggering scenario; S203. Collect the biometric information of the current operator based on the target biometric combination strategy; The triggering scenarios include touch screen operation scenarios and voice operation scenarios, and different triggering scenarios correspond to different biometric combination strategies.

[0029] Furthermore, in one embodiment, Figure 3 This is a detailed flowchart illustrating step S202 in an embodiment of this application, as shown below. Figure 3 As shown, the strategy for determining the combination of target biometric features based on the triggering scenario includes: S301. When the triggering scenario is a touch screen operation scenario, the corresponding target biometric combination strategy is a combination of facial feature information and body posture feature information. S302. When the triggering scenario is a voice operation scenario, the corresponding target biometric combination strategy is a combination of facial feature information and voiceprint feature information.

[0030] Specifically, when an operation command is detected and authentication is required, the embodiment employs a scenario-differentiated authentication strategy. In this embodiment, the triggering scenario can be determined based on the type of operation command, including touch screen operation scenarios and voice operation scenarios. For example, when the operation command is a touch command with coordinates within the target application icon, it is determined to be a touch screen operation scenario; when the operation command is a voice command, it is determined to be a voice operation scenario.

[0031] For touchscreen operation scenarios, the embodiment uses a DMS camera to identify the facial information of the current operator and an OMS camera to assist in collecting the operator's position (driver, passenger or rear seat) and body features, focusing on detecting whether the driver or passenger is operating the touchscreen, and obtaining a combination of facial feature information and body posture feature information.

[0032] For voice operation scenarios, the embodiment identifies the facial information of the current operator through the DMS camera and collects the voiceprint information of the current operator through the microphone array to obtain a combination of facial feature information and voiceprint feature information.

[0033] In addition, to ensure the effective collection of relevant data, for facial feature information, the embodiment can use binocular structured light technology to improve recognition accuracy. For voice operation scenarios, the voiceprint information of the current operator is only collected when a specific wake word is recognized.

[0034] In this embodiment, the biometric feature collection strategy is naturally linked to user interaction behavior (such as collecting voiceprints during voice operation and collecting gestures during touch screen operation), avoiding recognition failures caused by feature loss (such as no voice input during touch screen operation) or environmental interference in specific scenarios, thus enhancing the environmental adaptability of authentication. Simultaneously, a two-factor authentication method is used for different scenarios, which is more difficult to forge than a single feature, improving the level of privacy protection.

[0035] Furthermore, in one embodiment, Figure 4 This is a schematic diagram of the matching authentication process in an embodiment of this application, as shown below. Figure 4 As shown, the biometric information is matched and authenticated against a locally stored preset vehicle owner feature template, including: S401. Extract the feature vectors of biological feature information respectively; S402. Perform similarity matching between the feature vector and the corresponding template vector in the preset car owner feature template to obtain a similarity score; S403. If the similarity score is greater than or equal to the preset authentication threshold, then the authentication is deemed successful.

[0036] Furthermore, in one embodiment, the in-vehicle application privacy protection method further includes: Responding to the owner's settings commands, obtain the privacy protection level set by the owner; Update the preset authentication threshold based on the preset mapping relationship between privacy protection level and authentication threshold.

[0037] Specifically, during the matching and authentication process, for the collected biometric information, the embodiment performs matching and authentication by extracting the corresponding feature vectors and comparing them with the corresponding template vectors in the preset vehicle owner feature template. For different types of biometric information in different scenarios, authentication is only considered successful when the similarity between all types of biometric information and the corresponding template vectors is greater than the corresponding preset authentication threshold.

[0038] In touchscreen operation scenarios, this embodiment uses facial feature information as the primary authentication information and body posture features as secondary authentication information. For facial feature information, if the extracted feature vector matches a template vector of the vehicle owner's facial information stored locally with a similarity greater than or equal to 95%, the face matching is considered successful. For body posture features, if the extracted feature vector matches a template vector of body posture stored locally with a similarity greater than or equal to 60%, the body posture matching is considered successful. When both face matching and body posture matching are successful, authentication is considered successful, allowing the operator to access the protected target application, and an operation log is recorded (stored locally only for the vehicle owner's later review). If either matching fails, authentication is considered unsuccessful, only the application login interface or a blank interface is displayed, with the message "The current user has not authorized access to the app containing privacy information," without triggering an account logout, ensuring the convenience of subsequent use by the vehicle owner.

[0039] In voice operation scenarios, this embodiment uses facial feature information as the primary authentication information and voiceprint feature information as the secondary authentication information. For facial feature information, if the similarity between the extracted feature vector and the locally stored template vector of the vehicle owner's facial information is greater than or equal to 95%, the face matching is considered successful. For voiceprint feature information, if the similarity between the extracted feature vector and the locally stored template vector of the vehicle owner's voiceprint is greater than or equal to 90%, the voiceprint matching is considered successful. When both face and voiceprint matching are successful, authentication is considered successful, allowing the operator to access the protected target application, and an operation log is also recorded. If either matching fails, authentication is considered unsuccessful, only the application login interface or a blank interface is displayed, and a prompt message is generated, without triggering an account logout operation, ensuring the convenience of subsequent use by the vehicle owner.

[0040] In addition, if authentication fails multiple times in a row, the system will automatically lock the target application, requiring the car owner to unlock it again through multi-factor authentication, further enhancing privacy and security.

[0041] In other embodiments, the authentication threshold can be divided into multiple levels based on security and privacy levels, and a mapping relationship between the authentication threshold and each security and privacy level can be set. When the vehicle owner adjusts the global privacy level, the global authentication threshold can be updated and adjusted accordingly based on the mapping relationship between the privacy protection level and the authentication threshold. For some applications, a privacy level can also be set separately. For example, payment and communication-related applications can be set to a higher privacy level by default, or the vehicle owner can adjust it manually.

[0042] In this embodiment, the vector similarity-based matching algorithm has low computational complexity. Combined with local template comparison, it can quickly output authentication results, meeting the user's requirements for operation response speed in the vehicle-mounted system scenario and reducing user waiting time. At the same time, the quantified authentication threshold can also be dynamically adjusted in conjunction with security and privacy levels, allowing the system to achieve a flexible balance between security and convenience.

[0043] Furthermore, in one embodiment, the in-vehicle application privacy protection method further includes: Record vehicle owner's historical usage data and determine reliable scenarios based on the historical usage data; In trusted scenarios, the preset authentication threshold is adjusted to the first threshold, which is lower than the preset authentication threshold. Among them, trusted scenarios include the time periods when car owners frequently perform operations.

[0044] Specifically, in the embodiments, by recording the car owner's historical usage data, the car owner's daily usage habits can also be determined through statistical clustering and other methods to determine credible scenarios. For example, based on the car owner's historical usage data, the car owner's commonly used operation time period can be determined, and that time period can be used as a credible scenario.

[0045] In trusted scenarios, the implementation can adjust and lower the authentication threshold. For example, in voice operation scenarios, the matching threshold of voiceprint feature information used for auxiliary authentication can be appropriately lowered to improve authentication response speed while balancing security and convenience. However, it should be noted that the implementation can only lower the authentication threshold when authentication is continuously successful, i.e., when the vehicle owner is operating the system. If authentication fails, the threshold should be restored to the normal value to balance security and convenience.

[0046] In this embodiment, by classifying trusted scenarios based on the car owner's daily usage habits, the user's privacy needs are guaranteed while further improving the smoothness of the user experience.

[0047] Furthermore, in one embodiment, Figure 5 This is a flowchart illustrating the identity verification steps in an embodiment of this application, as shown below. Figure 5 As shown, the identity verification steps during operation include: S501. During the period when the target application displays the privacy interface, collect the current operator's biometric information again according to the preset time period or when a change in vehicle status is detected. S502. Match and authenticate the biometric information collected again with the preset vehicle owner feature template; S503. If the number of consecutive authentication failures reaches a preset threshold, the target application will be switched from the privacy interface to the non-privacy interface, and the account login session will continue to be maintained without interruption.

[0048] Specifically, to cover all usage scenarios and avoid privacy leaks when operators switch roles mid-operation, the embodiment also includes an identity verification step. After the application is opened, the system periodically (e.g., every 10 seconds) or when the vehicle status changes (e.g., doors open, gear shifting) to repeatedly collect biometric information and perform identity verification. In this scenario, only single biometric information can be detected, such as only facial features, without voiceprint detection, to avoid interfering with repeated verification for the user. When the number of consecutive authentication failures reaches a set threshold, indicating that the operator may have been replaced by someone other than the vehicle owner, the system controls the target application to switch from the privacy interface to the non-privacy interface, while maintaining the account login session without interruption until authentication is successful again.

[0049] In this embodiment, the identity verification step enables full-cycle protection, effectively preventing privacy leaks caused by changes in operators after initial authentication and during use, extending protection granularity to the entire usage process. Simultaneously, even if verification fails, the strategy of "blocking the interface but maintaining session continuity" is executed, ensuring that even if verification fails due to factors such as light obstruction, the user does not need to log in again; simply removing the obstruction restores visibility, ensuring enhanced security without sacrificing user experience continuity.

[0050] Secondly, embodiments of this application also provide a privacy protection device for in-vehicle applications.

[0051] In one embodiment, reference is made to Figure 6 , Figure 6 This is a schematic diagram of the functional modules of an embodiment of the vehicle infotainment privacy protection device of this application. Figure 6 As shown, the in-vehicle infotainment application privacy protection device includes: The instruction detection module 601 is used to monitor operation instructions for the target application on the vehicle-mounted system; The biometric acquisition module 602 is used to acquire at least two biometric information of the current operator in response to an operation command; The matching and authentication module 603 is used to match and authenticate biometric information with a preset vehicle owner feature template stored locally. The privacy control module 604 is used to control the display of the privacy interface of the target application if the authentication is successful, and to control the display of the non-privacy interface if the authentication fails, while maintaining the account login session of the target application without interruption.

[0052] The functions of each module in the above-mentioned vehicle application privacy protection device correspond to the steps in the above-mentioned vehicle application privacy protection method embodiment, and their functions and implementation processes will not be described in detail here.

[0053] Thirdly, this application provides a vehicle application privacy protection device, which can be a device with data processing functions such as an in-vehicle ECU.

[0054] Reference Figure 7 , Figure 7 This is a schematic diagram of the hardware structure of the in-vehicle application privacy protection device involved in the embodiments of this application. In this embodiment, the in-vehicle application privacy protection device may include a processor, a memory, a communication interface, and a communication bus.

[0055] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.

[0056] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting internal components of the in-vehicle infotainment privacy protection device, as well as interfaces used for interconnecting the in-vehicle infotainment privacy protection device with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.

[0057] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0058] The processor can be a general-purpose processor, which can call the vehicle-mounted application privacy protection program stored in the memory and execute the vehicle-mounted application privacy protection method provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the vehicle-mounted application privacy protection program is called can be referred to in the various embodiments of the vehicle-mounted application privacy protection method of this application, and will not be repeated here.

[0059] Those skilled in the art will understand that Figure 7 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0060] Fourthly, embodiments of this application also provide a computer-readable storage medium.

[0061] The present application has a computer-readable storage medium storing a vehicle infotainment application privacy protection program, wherein when the vehicle infotainment application privacy protection program is executed by a processor, it implements the steps of the vehicle infotainment application privacy protection method described above.

[0062] The method implemented when the vehicle infotainment application privacy protection program is executed can be referred to in various embodiments of the vehicle infotainment application privacy protection method of this application, and will not be repeated here.

[0063] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0064] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0065] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.

[0066] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0067] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0068] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods of the various embodiments of this application.

[0069] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method for protecting privacy in in-vehicle infotainment applications, characterized in that, include: Monitor operational commands for target applications on the vehicle's infotainment system; In response to the operation command, at least two biometric information of the current operator are collected; The biometric information is matched and authenticated with a preset vehicle owner feature template stored locally. If authentication is successful, the privacy interface of the target application is displayed; if authentication fails, the non-privacy interface is displayed, and the account login session of the target application is maintained without interruption.

2. The vehicle infotainment application privacy protection method according to claim 1, characterized in that, The collection of at least two biometric information of the current operator includes: Obtain the triggering scenario for the operation command; Determine the target biometric combination strategy based on the triggering scenario; The biometric information of the current operator is collected based on the target biometric combination strategy; The triggering scenarios include touch screen operation scenarios and voice operation scenarios, with different triggering scenarios corresponding to different biometric combination strategies.

3. The vehicle infotainment application privacy protection method according to claim 2, characterized in that, The strategy for determining the target biometric combination based on the triggering scenario includes: When the triggering scenario is a touch screen operation scenario, the corresponding target biometric combination strategy is a combination of facial feature information and body posture feature information; When the triggering scenario is a voice operation scenario, the corresponding target biometric combination strategy is a combination of facial feature information and voiceprint feature information.

4. The vehicle infotainment application privacy protection method according to claim 1, characterized in that, The step of matching and authenticating the biometric information with a locally stored preset vehicle owner feature template includes: Extract the feature vectors of the biometric information respectively; The feature vector is matched with the corresponding template vector in the preset car owner feature template to obtain a similarity score; If the similarity score is greater than or equal to the preset authentication threshold, then the authentication is deemed successful.

5. The vehicle infotainment application privacy protection method according to claim 4, characterized in that, The method further includes: Record the vehicle owner's historical usage data and determine reliable scenarios based on the historical usage data; In the trusted scenario, the preset authentication threshold is adjusted to a first threshold, where the first threshold is lower than the preset authentication threshold. The trusted scenarios include the time periods when car owners frequently operate the vehicle.

6. The vehicle infotainment application privacy protection method according to claim 4, characterized in that, The method further includes: Responding to the owner's settings commands, obtain the privacy protection level set by the owner; The preset authentication threshold is updated based on the preset mapping relationship between privacy protection level and authentication threshold.

7. The vehicle infotainment application privacy protection method according to claim 1, characterized in that, The method also includes an identity verification step during operation: During the period when the privacy interface is displayed in the target application, the biometric information of the current operator is collected again according to a preset time period or when a change in vehicle status is detected. The biometric information collected again will be matched and authenticated with the preset vehicle owner feature template; If the number of consecutive authentication failures reaches a preset threshold, the target application will be switched from the privacy interface to the non-privacy interface, and the account login session will continue to be maintained without interruption.

8. A privacy protection device for in-vehicle infotainment applications, characterized in that, include: The instruction detection module is used to monitor operation instructions for target applications on the vehicle's infotainment system. A biometric acquisition module is used to acquire at least two biometric information of the current operator in response to the operation command; The matching and authentication module is used to match and authenticate the biometric information with a preset vehicle owner feature template stored locally. The privacy control module is used to control the display of the privacy interface of the target application if the authentication is successful, and to control the display of the non-privacy interface if the authentication fails, while maintaining the account login session of the target application without interruption.

9. A privacy protection device for in-vehicle infotainment applications, characterized in that, The in-vehicle application privacy protection device includes a processor, a memory, and an in-vehicle application privacy protection program stored in the memory and executable by the processor, wherein when the in-vehicle application privacy protection program is executed by the processor, it implements the steps of the in-vehicle application privacy protection method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a vehicle application privacy protection program, wherein when the vehicle application privacy protection program is executed by a processor, it implements the steps of the vehicle application privacy protection method as described in any one of claims 1 to 7.

Images