Vehicle-mounted system account management method and device, electronic equipment and storage medium

What is AI technical title?
AI technical title is built by Patsnap AI team. It summarizes the technical point description of the patent document.
By introducing account level configuration and privacy data storage areas into the on-board system, the problem of privacy information leakage in the on-board system is solved, and the security of user privacy and improved ride experience is achieved.

CN119167428APending Publication Date: 2024-12-20CHINA FAW CO LTD +1

View PDF 0 Cites 0 Cited by

Patent Information

Application Number: CN202411241836.0
Authority / Receiving Office: CN · China
Patent Type: Applications(China)
Current Assignee / Owner
Filing Date: 2024-09-05
Publication Date: 2024-12-20

AI Technical Summary

Technical Problem

The lack of effective privacy data management in the existing vehicle-mounted systems leads to easy leakage of passenger privacy information, especially in complicated business vehicles, where passengers have poor vehicle experience and it is difficult to ensure privacy and security.

Method used

By introducing the concepts of account level configuration and privacy data storage in the on-board system, the account level is divided according to the privacy of the application, the account information and application data are stored, and the corresponding privacy data storage area is directly called when the user switches or logs in. , or create a new privacy data storage area when logging in for the first time to ensure user privacy and security.

Benefits of technology

It effectively reduces the risk of privacy leakage, improves users' ride experience and privacy security, saves data storage space in the on-board system, and automatically reconfigures the account status after the user gets off the car to avoid information leakage.

✦ Generated by Eureka AI based on patent content.

Smart Images

Figure CN119167428A_ABST

Patent Text Reader

Abstract

The invention discloses a vehicle-mounted system account management method and device, electronic equipment and a storage medium, and belongs to the technical field of data processing. The method at least comprises the following steps: in response to an account level configuration operation of a user, determining an account level of at least one account related to the vehicle-mounted system; determining a mapping relation between each application program and an account grade according to the privacy degree of each application program in the vehicle-mounted system so as to correspondingly store account information of each account and privacy application program data in a privacy data storage area; in response to account switching or login operation of the user, directly calling privacy application program data corresponding to the target account according to the account information of the target account, or adding a privacy data storage area in the vehicle-mounted system based on the account information of the target account so as to carry out data storage; and in response to a user getting-off event, reconfiguring the account to be in a to-be-switched or logged-in state. According to the invention, the privacy leakage risk of the vehicle-mounted system can be reduced, and the riding experience of the user can be improved.

Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of data processing technology, and in particular to a vehicle-mounted system account management method, device, electronic device, and storage medium. Background Art

[0002] With the iterative development of automobile technology, the in-vehicle functions of existing cars are becoming increasingly rich. Many cars are equipped with in-vehicle display screens in the front and rear rows, through which passengers can browse information online, listen to music, watch TV series, etc.

[0003] However, most existing car systems only have one account, and it is very inconvenient to manage information related to passenger privacy. This is particularly serious in commercial vehicles that are busy picking up and dropping off passengers. For passengers who value privacy protection, their browsing history, client account login and other private information obviously do not want to be seen by other passengers, but it is easy to forget to clear this information when getting off the car. In view of this, the existing car system at least has the risk of easy privacy leakage, and the passenger experience is poor. Summary of the invention

[0004] Embodiments of the present invention provide a vehicle-mounted system account management method, device, electronic device, and storage medium to at least reduce the risk of privacy leakage of the vehicle-mounted system and help improve the user's riding experience.

[0005] In a first aspect, an embodiment of the present invention provides a vehicle system account management method, which at least includes:

[0006] In response to an account level configuration operation by a user, determining an account level of at least one account related to the in-vehicle system;

[0007] According to the privacy level of at least one application in the vehicle system, clarify the mapping relationship between each application and the account level, so as to store the account information and the private application data of each account in at least one private data storage area of the vehicle system accordingly;

[0008] In response to the account switching or login operation of the user, the private application data in the private data storage area corresponding to the target account is directly called according to the account information of the target account to realize the account switching or login and restore the user usage trace of the target account, or at least one of the private data storage areas is added to the vehicle-mounted system based on the account information of the target account to store at least the account information and private application data of the target account;

[0009] In response to a user exiting the vehicle, reconfiguring the account to a waiting-to-switch or logged-in state;

[0010] The account information includes the account level and the biometric characteristics of the user to whom the account belongs, and at least one of the account name and the account serial number.

[0011] Optionally, it also includes:

[0012] After the target account is switched or logged in, the account information of the target account is configured to be visible, and the account information of other accounts except the target account is set to be hidden.

[0013] Optionally, after the target account is switched or logged in, the account information in any application under the target account is configured to be hidden.

[0014] Optionally, in response to the account switching or login operation of the user, directly calling the private application data in the private data storage area corresponding to the target account according to the account information of the target account to implement the account switching or login and restore the user usage trace of the target account, at least includes:

[0015] In response to an account switching or login operation of the user, obtaining a human biometric feature of the user to which the target account belongs;

[0016] Determining whether the target account already exists in the vehicle-mounted system according to the biological characteristics of the user to whom the target account belongs;

[0017] If the target account already exists in the vehicle-mounted system, the private application data in the private data storage area corresponding to the target account is directly called according to the human biometric characteristics of the user to which the target account belongs, so as to realize account switching or login and restore the user usage traces of the target account.

[0018] Optionally, in response to the account switching or login operation of the user, directly calling the private application data in the private data storage area corresponding to the target account according to the account information of the target account to implement the account switching or login and restore the user usage trace of the target account, at least includes:

[0019] In response to an account switching or login operation of the user, obtaining a human biometric feature of the user to which the target account belongs and an account level of the target account;

[0020] Determining whether the target account already exists in the vehicle-mounted system according to the biological characteristics of the user to whom the target account belongs;

[0021] If the target account already exists in the vehicle-mounted system, continue to determine whether the number of the target account is equal to 1;

[0022] If the number of the target account is equal to 1, the private application data in the private data storage area corresponding to the target account is directly called to implement account switching or login, and restore the user usage trace of the target account;

[0023] If the number of target accounts is greater than 1, the privacy application data in the privacy data storage area corresponding to the target account is directly called according to the account name, account serial number and / or account level of the target account to achieve account switching or login and restore the user usage traces of the target account.

[0024] Optionally, in response to the account switching or login operation of the user, at least one privacy data storage area is added in the vehicle-mounted system based on the account information of the target account to store at least the account information of the target account and the privacy application data, including at least:

[0025] In response to an account switching or login operation of the user, obtaining a human biometric feature of the user to which the target account belongs;

[0026] Determining whether the target account already exists in the vehicle-mounted system according to the biological characteristics of the user to whom the target account belongs;

[0027] If the target account does not exist in the vehicle-mounted system, creating and activating the target account in the vehicle-mounted system based on the account information of the target account;

[0028] After the target account is activated, the privacy application is notified through a preset message delivery method to divide the privacy application data;

[0029] In response to the user's privacy application usage operation, at least one privacy data storage area is added to the in-vehicle system to store at least the account information of the target account and the privacy application data.

[0030] Optionally, if the target account does not exist in the vehicle-mounted system, creating and activating the target account in the vehicle-mounted system based on the account information of the target account includes:

[0031] If the target account does not exist in the vehicle-mounted system, determining whether the number of accounts in the vehicle-mounted system reaches an upper limit;

[0032] If the number of accounts in the vehicle-mounted system does not reach the upper limit, creating and activating the target account in the vehicle-mounted system based on the account information of the target account;

[0033] If the number of accounts in the vehicle-mounted system reaches the upper limit, at least one account that meets the preset disposal condition is deleted, and then a new target account is created and activated in the vehicle-mounted system based on the account information of the target account.

[0034] In a second aspect, an embodiment of the present invention further provides a vehicle-mounted system account management device, comprising at least:

[0035] a level determination module, at least for determining an account level of at least one account involved in the vehicle-mounted system in response to an account level configuration operation by a user;

[0036] A mapping storage module, at least for clarifying the mapping relationship between each application and the account level according to the privacy level of at least one application in the vehicle system, so as to store the account information and the privacy application data of each account in the at least one privacy data storage area of the vehicle system;

[0037] Calling a newly added module, at least for responding to the account switching or login operation of the user, directly calling the privacy application data in the privacy data storage area corresponding to the target account according to the account information of the target account, so as to realize the account switching or login, and restore the user usage trace of the target account, or, based on the account information of the target account, adding at least one of the privacy data storage areas in the vehicle-mounted system to store at least the account information and privacy application data of the target account;

[0038] A state switching module, at least for reconfiguring the account to a waiting-to-switch or logged-in state in response to a user getting off the vehicle event;

[0039] The account information includes at least one of the account name, account serial number, account level and human biometric characteristics of the user to whom the account belongs.

[0040] In a third aspect, an embodiment of the present invention further provides an electronic device, comprising a processor and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps in the vehicle-mounted system account management method as described in any one of the first aspects are executed.

[0041] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle-mounted system account management method described in any one of the first aspects.

[0042] The embodiment of the present invention provides a vehicle-mounted system account management method, device, electronic device and storage medium. First, in response to the user's account level configuration operation, the account level of at least one account involved in the vehicle-mounted system is determined; secondly, according to the privacy level of at least one application in the vehicle-mounted system, the mapping relationship between each application and the account level is clarified, so that the account information and privacy application data of each account are stored in at least one privacy data storage area of the vehicle-mounted system; then, in response to the user's account switching or login operation, the privacy application data in the privacy data storage area corresponding to the target account is directly called according to the account information of the target account, so as to realize account switching or login, and restore the user's use trace of the target account, or, based on the account information of the target account, at least one privacy data storage area is added in the vehicle-mounted system to at least store the account information and privacy application data of the target account; finally, in response to the user getting off the vehicle event, the account is reconfigured to a waiting to be switched or logged in state.

[0043] It can be seen that after the vehicle system accounts are graded, the embodiment of the present invention can divide the various applications in the vehicle system according to the account level, clarify which applications under each account with different account levels belong to privacy applications and which do not belong to privacy applications, and then store the account information and privacy application data of each account in the corresponding privacy data storage area (compared with the existing solution of storing all application data in each account, the solution of the embodiment of the present invention is more conducive to saving the data storage space of the vehicle system). In this way, on the one hand, when the user has an account, the account has a login history in the vehicle system and needs to log in again, the embodiment of the present invention can directly call the privacy application data in the corresponding privacy data storage area according to the account information, realize the switching or login of the target account, and restore the user's use traces before the current account login; on the other hand, when the user logs in to the account for the first time, the embodiment of the present invention can create one or more privacy data storage areas in the vehicle system according to the account information to store the account information of the first login account and / or the privacy application data generated by the user's first login account, so that the user can restore the use traces of the account when the user logs in to the account next time, giving the user a good riding experience and improving user favorability. After the user gets off the vehicle, the embodiment of the present invention reconfigures the account to a waiting-to-switch or waiting-to-login state. This setting can ensure user privacy and reduce the risk of privacy leakage even if the user forgets to perform operations such as account logout and account information clearing when getting off the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0045] Figure 1 is a flow chart of a vehicle system account management method provided by an embodiment of the present invention;

[0046] Figure 2 is a flow chart of another vehicle system account management method provided by an embodiment of the present invention;

[0047] Figure 3 is a flow chart of another vehicle system account management method provided by an embodiment of the present invention;

[0048] Figure 4 is a flow chart of another vehicle system account management method provided by an embodiment of the present invention;

[0049] Figure 5 It is a structural diagram of an in-vehicle system account management device provided by an embodiment of the present invention;

[0050] Figure 6 It is a structural schematic diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0052] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings, and "multiple" generally includes at least two.

[0053] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0054] It should be understood that, although the terms first, second, third, etc. may be used to describe in the embodiments of the present application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, without departing from the scope of the embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first.

[0055] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.

[0056] It should also be noted that the term "includes", "comprising" or any other variation thereof is intended to cover non-exclusive inclusion, so that a commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprising a ..." do not exclude the existence of other identical elements in the commodity or device including the elements.

[0057] It should be particularly noted that any symbols and / or numbers in the specification that are not marked in the accompanying drawings are not drawing marks.

[0058] An embodiment of the present invention provides a vehicle-mounted system account management method. Figure 1 This is a flow chart of a vehicle system account management method provided by an embodiment of the present invention. This embodiment can be applied to any vehicle system account management scenario, such as electric vehicles, tricycles, fuel vehicles, new energy vehicles, driverless vehicles, etc. The vehicle system account management method can be, but is not limited to, executed by the vehicle system account management device in the embodiment of the present invention as the execution subject, and the execution subject can be implemented in software and / or hardware. Figure 1 As shown, the vehicle-mounted system account management method includes at least the following steps:

[0059] S1. In response to an account level configuration operation by a user, determining an account level of at least one account related to an in-vehicle system.

[0060] Among them, the vehicle-mounted system can be an Android system.

[0061] It can be known that the account level can include, but is not limited to, a main account and a sub-account; the user's account level configuration operation can refer to the user clicking "Vehicle Settings" on the main page of the rear display screen of the vehicle and selecting the "Account Management" item, and then entering the "Account Level Configuration" page to set the main account and sub-account. In general, the main account can correspond to the owner or driver, and the sub-account corresponds to other persons except the owner or driver. In addition, the main account can be unique, and there can be multiple sub-accounts.

[0062] S2. According to the privacy level of at least one application in the vehicle system, a mapping relationship between each application and an account level is clarified, so that the account information and the private application data of each account are correspondingly stored in at least one private data storage area of the vehicle system.

[0063] Among them, the in-vehicle system often has multiple applications installed. The more common applications can be divided into the following categories: mobile user generated content (UGC) (such as Youku, etc.), mobile search (such as Baidu search, Google search, etc.), mobile browsers (such as QQ browser, etc.), mobile payment (such as Taobao, JD.com, Pinduoduo, Alipay, etc.), mobile advertising, mobile instant messaging (such as WeChat, QQ, DingTalk, etc.), social networking services (SNS) (such as TikTok, etc.), location-based services (LBS) (such as Amap, Baidu Maps, etc.), augmented reality (AR) and games, etc.

[0064] It can be seen that among the above types of applications, mobile advertising (users generally do not have too strong interest in advertising) and LBS (mostly used when drivers need navigation services) involve less user privacy, so mobile advertising and LBS can be attributed to main account applications. However, applications such as UGC, mobile search, SNS, etc. usually involve a large amount of user private content (such as chat records, search records, game accounts and passwords, etc.), so applications such as UGC can be divided into sub-account applications (that is, privacy applications; the data generated by users during the use of privacy applications is privacy application data); the above sub-account applications can establish their own databases (that is, the aforementioned privacy data storage area) in the vehicle system according to the account information of the sub-account to store the account information of the sub-account and the privacy application data (specifically, the privacy data storage area can be refined into an account information storage area and a privacy application data storage area, for example). Of course, the main account privacy applications involving the owner or driver's privacy can also be stored in one or more privacy data storage areas.

[0065] It is understandable that after clarifying the mapping relationship between applications and account levels, if the user creates a new sub-account, the vehicle system only needs to create a corresponding privacy application without creating a new main account application. This setting can simplify the sub-account establishment process of the vehicle system and help streamline the data storage architecture of the vehicle system.

[0066] S3. In response to the user's account switching or login operation, the privacy application data in the privacy data storage area corresponding to the target account is directly called according to the account information of the target account to realize the account switching or login and restore the user's usage traces of the target account, or, based on the account information of the target account, at least one privacy data storage area is added in the vehicle system to store at least the account information and privacy application data of the target account.

[0067] The account information includes the account level and the biometric characteristics of the user to whom the account belongs, and at least one of the account name and the account serial number.

[0068] In a commercial vehicle, account switching or login operations are usually performed by rear passengers, so the account switching or login operation in step S3 can be, for example, an operation of the user switching or logging in to a sub-account through the rear display screen. Adaptively, the target account can refer to the sub-account that the user intends to log in to on the rear display screen.

[0069] According to the changes in actual application scenarios, there may be multiple account switching or login operations for users. For example, the account switching or login operation for users may refer to the operation that the user already has an account, the account has a login history in the vehicle system, and the user needs to log in to the account again, or the operation that the user already has an account, but the account has not been logged in in the vehicle system, and the user needs to log in to the account for the first time, or the operation that the user without an account creates and logs in to an account for the first time, etc.

[0070] It is understandable that the data processing forms corresponding to the above-mentioned multiple specific user account switching or login operations are not the same. For example, when a user already has an account, the account has a login history in the vehicle system, and the user needs to log in to the account again, the privacy application data in the privacy data storage area corresponding to the existing account can be directly called based on the account information of the user's existing account to realize the login of the user's existing account and restore the user's use traces of the account; or, when the user already has an account, but the account has not been logged in to the vehicle system, and the user needs to log in to the account for the first time, at least one privacy data storage area can be added to the vehicle system based on the account information of the user's existing account to at least store the account information of the user's existing account and the privacy application data generated during the user's use of the privacy application on the existing account; or, when a user without an account establishes and logs in to an account for the first time, at least one privacy data storage area can be added to the vehicle system based on the account information of the user's newly created account to at least store the account information of the newly created account and the privacy application data generated during the user's use of the privacy application on the newly created account.

[0071] Because account information and private application data correspond to each other, the biometric characteristics of the account user in the account information (such as fingerprints, palm prints, eye prints, voice prints, facial recognition, etc.) are unique, so the call or storage of private application data is related to the biometric characteristics of the account user, which is more secure and helps to protect user privacy.

[0072] S4. In response to the user getting off the vehicle event, reconfigure the account to a waiting to be switched or logged in state.

[0073] The user getting off the vehicle event can be sensed by the vehicle itself, for example, based on a camera (i.e., identifying whether the user has gotten off the vehicle through the image captured by the camera), an infrared sensor (i.e., determining whether the user has gotten off the vehicle through infrared imaging), a pressure sensor under the vehicle seat (i.e., the pressure sensor measures a standard pressure value when there is no passenger, and if the real-time pressure value measured by the pressure sensor is greater than the standard pressure value, it means that the passenger has not gotten off the vehicle), etc. In a specific implementation, reconfiguring the account to a waiting to be switched or logged-in state can mean exiting the subaccount of the user getting off the vehicle and turning off the rear display screen.

[0074] In summary, this embodiment provides a method for managing an in-vehicle system account. First, in response to the user's account level configuration operation, the account level of at least one account involved in the in-vehicle system is determined; secondly, according to the privacy level of at least one application in the in-vehicle system, the mapping relationship between each application and the account level is clarified, so that the account information and privacy application data of each account are stored in at least one privacy data storage area of the in-vehicle system; then, in response to the user's account switching or login operation, the privacy application data in the privacy data storage area corresponding to the target account is directly called according to the account information of the target account, so as to realize the account switching or login, and restore the user's use trace of the target account, or, based on the account information of the target account, at least one privacy data storage area is added in the in-vehicle system to store at least the account information and privacy application data of the target account; finally, in response to the user getting off the vehicle event, the account is reconfigured to a waiting to be switched or logged in state.

[0075] It can be seen from this that after the vehicle-mounted system accounts are graded, this embodiment can divide the various applications in the vehicle-mounted system according to the account level, clarify which applications under each account with different account levels are privacy applications and which are not privacy applications, and then store the account information and privacy application data of each account in the corresponding privacy data storage area (compared to the existing solution of storing all application data in each account, the solution of this embodiment is more conducive to saving data storage space of the vehicle-mounted system). In this way, on the one hand, when the user already has an account, the account has a login history in the vehicle system and needs to log in again, this embodiment can directly call the privacy application data in the corresponding privacy data storage area according to the account information, realize the switching or login of the target account, and restore the user's usage traces before the current account login; on the other hand, when the user logs in to the account for the first time (that is, the aforementioned user already has an account, but the account has not been logged in to the vehicle system, the user needs to log in to this account for the first time, or the user without an account creates and logs in to the account for the first time), this embodiment can create one or more privacy data storage areas in the vehicle system according to the account information to store the account information of the first login account and / or the privacy application data generated by the user's first login account, so that the user can restore the usage traces of the account when logging in to the account next time, giving the user a good riding experience and improving the user's favorability. After the user gets off the vehicle, this embodiment reconfigures the account to be switched or logged in. In this way, even if the user forgets to perform operations such as account logout and account information clearing when getting off the vehicle, the user's privacy security can be guaranteed and the risk of user privacy leakage can be reduced.

[0076] It should be noted that the account management method provided in the embodiment of the present invention may also be applicable to other systems or application scenarios besides vehicles, such as industrial-grade field control systems, personal computers, mobile phones, etc.

[0077] Based on the above embodiments or implementation methods, the following takes the "one user corresponds to one target account" mode (that is, one user only creates one account) as an example to illustrate the judgment process of whether the target account exists in the vehicle system working condition and the data call process, but it is not intended to limit the present invention.

[0078] In a specific embodiment, optionally, it further includes:

[0079] After the target account is switched or logged in, the account information of the target account is configured to be visible, and the account information of other accounts except the target account is set to be hidden.

[0080] In another specific implementation, optionally, after the target account is switched or logged in, the account information in any application under the target account is configured to be hidden.

[0081] In another specific implementation, optionally, in response to the user's account switching or login operation, directly calling the private application data in the private data storage area corresponding to the target account according to the account information of the target account to implement the account switching or login and restore the user usage trace of the target account, at least includes:

[0082] In response to the user's account switching or login operation, obtaining the human biometric characteristics of the user to which the target account belongs;

[0083] Determine whether the target account already exists in the vehicle system based on the biometric characteristics of the user to whom the target account belongs;

[0084] If the target account already exists in the vehicle system, the private application data in the private data storage area corresponding to the target account is directly called based on the human biometric characteristics of the user to which the target account belongs, so as to realize account switching or login and restore the user usage traces of the target account.

[0085] Based on the above implementation, Figure 2 FIG. 1 is a flow chart of another vehicle system account management method provided by an embodiment of the present invention. Figure 2 As shown, the vehicle system account management method includes at least the following steps:

[0086] S1. In response to an account level configuration operation by a user, determining an account level of at least one account related to an in-vehicle system.

[0087] S2. According to the privacy level of at least one application in the vehicle system, a mapping relationship between each application and an account level is clarified, so that the account information and the private application data of each account are correspondingly stored in at least one private data storage area of the vehicle system.

[0088] S31. In response to the user's account switching or login operation, obtain the human biometric characteristics of the user to which the target account belongs.

[0089] S32. Determine whether the target account already exists in the vehicle-mounted system based on the biological characteristics of the user to which the target account belongs.

[0090] Among them, taking the fingerprint as the human biometric feature of the user to which the target account belongs, the specific implementation method of step S31 and step S32 can be that the user unlocks the rear display screen with the fingerprint and enters the fingerprint matching the target account; based on the fingerprint entered by the user and matching the target account, traverse each privacy data storage area, and then determine whether there is one or more privacy data storage areas storing account information containing the fingerprint. If so, it can be determined that the target account already exists in the vehicle system; if not, it can be determined that the target account does not exist in the vehicle system.

[0091] S33. If the target account already exists in the vehicle system, the private application data in the private data storage area corresponding to the target account is directly called according to the human biometric characteristics of the user to which the target account belongs, so as to realize account switching or login and restore the user usage traces of the target account.

[0092] S5. After the target account is switched or logged in, the account information of the target account is configured to be visible, the account information of other accounts except the target account is set to be hidden, and the account information in any application under the target account is configured to be hidden.

[0093] S4. In response to the user getting off the vehicle event, reconfigure the account to a waiting to be switched or logged in state.

[0094] Among them, the account information of the target account is configured to be visible, which means that the account information of the target account can be visually displayed to the user through the "Account Information Query" page under the "Account Management" item on the rear display screen. On the contrary, the account information of other accounts except the target account is set to be hidden, which means that the user cannot query the account information of any other account stored in the vehicle system except the target account through the aforementioned "Account Information Query" page. It is understandable that such a setting can prevent a user from arbitrarily obtaining or modifying the account information of other users, further improving the security of user privacy.

[0095] It is understandable that the account information in any application under the target account is configured to be hidden, which means that in any application, the account information of the target account corresponding to the application cannot be queried or modified by the user. After such configuration, the account information in the application is invisible to the user, and the user can query or modify the target account through the "Account Information Query" page under the "Account Management" item of the aforementioned rear display screen, which is conducive to protecting user privacy and security.

[0096] In summary, this embodiment can provide users with a good riding experience, improve user favorability, protect user privacy and reduce the risk of user privacy leakage while saving data storage space in the vehicle-mounted system.

[0097] Based on the above embodiments or implementation modes, the following takes the "one user corresponds to multiple target accounts" mode (that is, one user can establish multiple accounts, for example, a driver can establish a main account and a sub-account) as an example to illustrate the judgment process of whether the target account exists in the vehicle system working condition and the data calling process, but it is not intended to limit the present invention.

[0098] In a specific implementation, optionally, in response to the user's account switching or login operation, directly calling the private application data in the private data storage area corresponding to the target account according to the account information of the target account to implement the account switching or login and restore the user usage trace of the target account, at least includes:

[0099] In response to an account switching or login operation by a user, obtaining a human biometric feature of a user to which a target account belongs and an account level of the target account;

[0100] Determine whether the target account already exists in the vehicle system based on the biometric characteristics of the user to whom the target account belongs;

[0101] If the target account already exists in the vehicle system, continue to determine whether the number of target accounts is equal to 1;

[0102] If the number of target accounts is equal to 1, the private application data in the private data storage area corresponding to the target account is directly called to implement account switching or login, and restore the user usage traces of the target account;

[0103] If the number of target accounts is greater than 1, the privacy application data in the privacy data storage area corresponding to the target account is directly called according to the account name, account serial number and / or account level of the target account to achieve account switching or login and restore the user usage traces of the target account.

[0104] Based on the above implementation, Figure 3FIG. 1 is a flow chart of another vehicle system account management method provided by an embodiment of the present invention. Figure 3 As shown, the vehicle system account management method includes at least the following steps:

[0105] S1. In response to an account level configuration operation by a user, determine the account level of at least one account related to the in-vehicle system.

[0106] S2. According to the privacy level of at least one application in the vehicle system, a mapping relationship between each application and an account level is clarified, so that the account information and the private application data of each account are correspondingly stored in at least one private data storage area of the vehicle system.

[0107] S31′, in response to the user's account switching or login operation, obtaining the human biometric characteristics of the user to which the target account belongs and the account level of the target account.

[0108] S32', judging whether the target account already exists in the vehicle-mounted system according to the biological characteristics of the user to which the target account belongs.

[0109] Among them, taking the facial features as the human biometric features of the user to which the target account belongs as an example, the specific implementation method of step S31' and step S32' can be that the user unlocks the rear display screen through facial recognition and enters the facial features that match the target account; based on the facial features entered by the user and matching the target account, traverse each privacy data storage area, and then determine whether there is one or more privacy data storage areas storing account information containing the facial features. If so, it can be determined that the target account already exists in the vehicle system; if not, it can be determined that the target account does not exist in the vehicle system.

[0110] S33': If the target account already exists in the vehicle-mounted system, continue to determine whether the number of target accounts is equal to 1.

[0111] Some users may have created and logged in multiple accounts (i.e. the number of target accounts is greater than 1). In this case, based on the facial features entered by the user and matching the target account, the account information of multiple accounts will be queried by traversing various private data storage areas. In order to avoid confusion in user operations, it can be set that only one sub-account is in an active state at a time (i.e. the sub-account that the user can operate in real time).

[0112] S34', if the number of target accounts is equal to 1, the private application data in the private data storage area corresponding to the target account is directly called to implement account switching or login, and restore the user usage traces of the target account.

[0113] Among them, if the target account is unique, it means that the user has only created and logged in to one target account. At this time, the privacy application data in one or more privacy data storage areas corresponding to the target account can be directly called to realize the login of the target account and restore the user usage traces of the target account.

[0114] S35', if the number of target accounts is greater than 1, the privacy application data in the privacy data storage area corresponding to the target account is directly called according to the account name, account serial number and / or account level of the target account to achieve account switching or login and restore the user usage traces of the target account.

[0115] S4. In response to the user getting off the vehicle event, reconfigure the account to a waiting to be switched or logged in state.

[0116] Among them, if there are multiple target accounts and the account levels of the multiple target accounts are the same (for example, they are all sub-accounts), it is impossible to determine which target account the user intends to log in to simply based on the user's human biometrics. At this time, more detailed account information is needed to screen the above multiple target accounts to determine the target account the user intends to log in to. Specifically, the target account can be determined based on the account name and / or account serial number of the target account (in this case, the account level cannot play a role in distinguishing accounts), and then the privacy application data in the privacy data storage area corresponding to the target account can be directly called to achieve account switching or login, and restore the user's usage traces of the target account.

[0117] If there are two target accounts, one main account and one sub-account, it is impossible to determine which target account the user intends to log in to simply based on the user's biological characteristics. In this case, more detailed account information is needed to screen the two target accounts to determine the target account the user intends to log in to. Specifically, the target account can be determined based on at least one of the target account's account name, account serial number, or account level, and then the privacy application data in the privacy data storage area corresponding to the target account can be directly called to achieve account switching or login, and restore the user's usage traces of the target account.

[0118] In summary, this embodiment can provide users with a good riding experience, improve user favorability, protect user privacy and reduce the risk of user privacy leakage while saving data storage space in the vehicle-mounted system.

[0119] Based on the above embodiments or implementation modes, the following describes the process of creating, activating and storing data of a target account by taking the situation where the target account that the user intends to log in does not exist as an example, which does not limit the present invention.

[0120] In a specific implementation, optionally, in response to the user's account switching or login operation, at least one privacy data storage area is added in the vehicle system based on the account information of the target account to store at least the account information of the target account and the privacy application data, including at least:

[0121] In response to the user's account switching or login operation, obtaining the human biometric characteristics of the user to which the target account belongs;

[0122] Determine whether the target account already exists in the vehicle system based on the biometric characteristics of the user to whom the target account belongs;

[0123] If the target account does not exist in the vehicle system, creating and activating a target account in the vehicle system based on the account information of the target account;

[0124] After the target account is activated, the privacy application is notified through a preset message delivery method to divide the privacy application data;

[0125] In response to the user's privacy application usage operation, at least one privacy data storage area is added in the vehicle system to store at least the account information of the target account and the privacy application data.

[0126] In another specific implementation, optionally, if the target account does not exist in the vehicle-mounted system, creating and activating a target account in the vehicle-mounted system based on the account information of the target account includes:

[0127] If the target account does not exist in the vehicle system, determine whether the number of accounts in the vehicle system reaches the upper limit;

[0128] If the number of accounts in the vehicle system has not reached the upper limit, a new target account is created and activated in the vehicle system based on the account information of the target account;

[0129] If the number of accounts in the vehicle system reaches an upper limit, at least one account that meets the preset disposal condition is deleted, and then a new target account is created and activated in the vehicle system based on the account information of the target account.

[0130] Based on the above implementation, Figure 4 FIG. 1 is a flow chart of another vehicle system account management method provided by an embodiment of the present invention. Figure 4 As shown, the vehicle system account management method includes at least the following steps:

[0131] S1. In response to an account level configuration operation by a user, determining an account level of at least one account related to an in-vehicle system.

[0132] S2. According to the privacy level of at least one application in the vehicle system, a mapping relationship between each application and an account level is clarified, so that the account information and the private application data of each account are correspondingly stored in at least one private data storage area of the vehicle system.

[0133] S31”, in response to the user's account switching or login operation, obtaining the human biometric characteristics of the user to which the target account belongs.

[0134] S32”, judging whether the target account already exists in the vehicle system according to the biological characteristics of the user to which the target account belongs.

[0135] S33”: If the target account does not exist in the vehicle-mounted system, determine whether the number of accounts in the vehicle-mounted system reaches an upper limit.

[0136] The upper limit value may be adaptively adjusted according to the actual data storage capacity of the vehicle-mounted system, and the upper limit value may be 10, for example.

[0137] For example, the maximum number of accounts that can be created can be set in the vehicle-mounted Android system:

[0138] "maxSubAccount=10;".

[0139] It can be seen that if the number of accounts in the vehicle system has not reached the upper limit, it means that the vehicle system can still continue to store new accounts based on the existing accounts; on the contrary, if the number of accounts in the vehicle system has reached the upper limit, it means that the vehicle system can no longer continue to store new accounts based on the existing accounts.

[0140] S34”: If the number of accounts in the vehicle system has not reached the upper limit, a target account is newly created and activated in the vehicle system based on the account information of the target account.

[0141] Exemplarily, in the process of creating a new target account in the vehicle-mounted Android system, the account information can be defined in the following manner:

[0142] "subAccountInfo:Id,Name,FingerprintInfo";

[0143] And, you can define a constant to record the target account after activation:

[0144] "SYSTEM_SUBACCOUNT_KEY="persist.settings.subaccount.id";";

[0145] Set the target account id:

[0146] "SystemProperties.set(SYSTEM_SUBACCOUNT_KEY,id);";

[0147] Get the target account ID:

[0148] "SystemProperties.get(SYSTEM_SUBACCOUNT_KEY);".

[0149] S35”: If the number of accounts in the vehicle-mounted system reaches the upper limit, at least one account that meets the preset disposal condition is deleted, and then a target account is newly created and activated in the vehicle-mounted system based on the account information of the target account.

[0150] Among them, the preset handling conditions can be adaptively set according to the actual application conditions of the vehicle-mounted system. The preset handling conditions can, for example, be the account with the longest time span from the last use.

[0151] It is understandable that after an account that meets the preset disposal conditions is deleted, the vehicle system can notify each privacy application of the relevant information of the deleted account through broadcasting, so that the privacy application can clear the privacy application data and account information in the corresponding privacy data storage area based on the relevant information of the deleted account.

[0152] Specifically, define the broadcast of deleting an account, and the specific method of notifying the application of the deletion of account related information can be:

[0153] "ACTION_SUBACCOUNT_DELETED="android.action.subaccount.deleted"".

[0154] Define the broadcast of account changes. The specific method of notifying the application of account change information can be:

[0155] "ACTION_SUBACCOUNT_CHANGED="android.action.subaccount.changed"".

[0156] The specific form of sending broadcast information can be:

[0157] "Intent subAccountIntent=new Intent(ACTION_SUBACCOUNT_CHANGED);

[0158] subAccountIntent.putExtra("subAccountId" "id");

[0159] getActivity().sendBroadcast(subAccountIntent);".

[0160] S36”, after the target account is activated, the privacy application is notified through a preset message delivery method to divide the privacy application data.

[0161] Among them, the preset message delivery method can be the aforementioned broadcast method.

[0162] S37”, in response to the user's privacy application usage operation, at least one privacy data storage area is added in the vehicle system to store at least the account information of the target account and the privacy application data.

[0163] Among them, the user's privacy application usage operation may refer to, for example, the user opening a work group chat in WeChat, replying to a leader's message, etc.

[0164] S4. In response to the user getting off the vehicle event, reconfigure the account to a waiting to be switched or logged in state.

[0165] In summary, this embodiment can provide users with a good riding experience, improve user favorability, protect user privacy and reduce the risk of user privacy leakage while saving data storage space in the vehicle-mounted system.

[0166] The embodiment of the present invention also provides a vehicle-mounted system account management device. Figure 5 Schematic diagram of the structure of an in-vehicle system account management device provided by an embodiment of the present invention. This embodiment can be applied to the account management scenario of an in-vehicle system in any vehicle, such as electric vehicles, tricycles, fuel vehicles, new energy vehicles, driverless vehicles, etc. The device can be implemented in software and / or hardware. Figure 5 As shown, the vehicle-mounted system account management device provided in this embodiment at least includes:

[0167] The level determination module 110 is at least used to determine the account level of at least one account involved in the vehicle system in response to the user's account level configuration operation;

[0168] A mapping storage module 120, at least for clarifying the mapping relationship between each application and the account level according to the privacy level of at least one application in the vehicle system, so as to store the account information and the private application data of each account in the at least one private data storage area of the vehicle system;

[0169] The new module 130 is called to at least be used to directly call the private application data in the private data storage area corresponding to the target account according to the account information of the target account in response to the user's account switching or login operation, so as to realize the account switching or login and restore the user's use trace of the target account, or to add at least one private data storage area in the vehicle-mounted system based on the account information of the target account to store at least the account information and private application data of the target account;

[0170] The state switching module 140 is at least used to reconfigure the account to a waiting to switch or logged-in state in response to a user getting off the vehicle event;

[0171] The account information includes at least one of the account name, account serial number, account level and the human biometric feature of the user to whom the account belongs.

[0172] Optionally, it also includes:

[0173] The status configuration module 150 is at least used to configure the account information of the target account to be visible after the target account is switched or logged in, and the account information of other accounts except the target account is set to be hidden.

[0174] Optionally, the state configuration module 150 is also used to configure the account information in any application under the target account to be in a hidden state after the target account is switched or logged in.

[0175] Optionally, calling the new module 130 is at least specifically used for:

[0176] In response to the user's account switching or login operation, obtaining the human biometric characteristics of the user to which the target account belongs;

[0177] Determine whether the target account already exists in the vehicle system based on the biometric characteristics of the user to whom the target account belongs;

[0178] If the target account already exists in the vehicle system, the private application data in the private data storage area corresponding to the target account is directly called based on the human biometric characteristics of the user to which the target account belongs, so as to realize account switching or login and restore the user usage traces of the target account.

[0179] Optionally, calling the new module 130 is at least specifically used for:

[0180] In response to an account switching or login operation by a user, obtaining a human biometric feature of a user to which a target account belongs and an account level of the target account;

[0181] Determine whether the target account already exists in the vehicle system based on the biometric characteristics of the user to whom the target account belongs;

[0182] If the target account already exists in the vehicle system, continue to determine whether the number of target accounts is equal to 1;

[0183] If the number of target accounts is equal to 1, the private application data in the private data storage area corresponding to the target account is directly called to implement account switching or login, and restore the user usage traces of the target account;

[0184] If the number of target accounts is greater than 1, the privacy application data in the privacy data storage area corresponding to the target account is directly called according to the account name, account serial number and / or account level of the target account to achieve account switching or login and restore the user usage traces of the target account.

[0185] Optionally, calling the new module 130 is at least specifically used for:

[0186] In response to the user's account switching or login operation, obtaining the human biometric characteristics of the user to which the target account belongs;

[0187] Determine whether the target account already exists in the vehicle system based on the biometric characteristics of the user to whom the target account belongs;

[0188] If the target account does not exist in the vehicle system, creating and activating a target account in the vehicle system based on the account information of the target account;

[0189] After the target account is activated, the privacy application is notified through a preset message delivery method to divide the privacy application data;

[0190] In response to the user's privacy application usage operation, at least one privacy data storage area is added in the vehicle system to store at least the account information of the target account and the privacy application data.

[0191] Optionally, calling the new module 130 is at least specifically used for:

[0192] If the target account does not exist in the vehicle system, determine whether the number of accounts in the vehicle system reaches the upper limit;

[0193] If the number of accounts in the vehicle system has not reached the upper limit, a new target account is created and activated in the vehicle system based on the account information of the target account;

[0194] If the number of accounts in the vehicle system reaches an upper limit, at least one account that meets the preset disposal condition is deleted, and then a new target account is created and activated in the vehicle system based on the account information of the target account.

[0195] In summary, this embodiment provides an in-vehicle system account management device. First, the level determination module responds to the user's account level configuration operation to determine the account level of at least one account involved in the in-vehicle system; second, the mapping storage module clarifies the mapping relationship between each application and the account level according to the privacy level of at least one application in the in-vehicle system, so as to store the account information and privacy application data of each account in at least one privacy data storage area of the in-vehicle system; then, by calling the new module in response to the user's account switching or login operation, the privacy application data in the privacy data storage area corresponding to the target account is directly called according to the account information of the target account, so as to realize account switching or login, and restore the user's use trace of the target account, or, based on the account information of the target account, at least one privacy data storage area is added in the in-vehicle system to store at least the account information and privacy application data of the target account; finally, the state switching module responds to the user's getting off the vehicle event, and reconfigures the account to be switched or logged in.

[0196] It can be seen from this that after the vehicle-mounted system accounts are graded, this embodiment can divide the various applications in the vehicle-mounted system according to the account level, clarify which applications under each account with different account levels are privacy applications and which are not privacy applications, and then store the account information and privacy application data of each account in the corresponding privacy data storage area (compared to the existing solution of storing all application data in each account, the solution of this embodiment is more conducive to saving data storage space of the vehicle-mounted system). In this way, on the one hand, when the user already has an account, the account has a login history in the vehicle system and needs to log in again, this embodiment can directly call the privacy application data in the corresponding privacy data storage area according to the account information, realize the switching or login of the target account, and restore the user's usage traces before the current account login; on the other hand, when the user logs in to the account for the first time (that is, the aforementioned user already has an account, but the account has not been logged in to the vehicle system, the user needs to log in to this account for the first time, or the user without an account creates and logs in to the account for the first time), this embodiment can create one or more privacy data storage areas in the vehicle system according to the account information to store the account information of the first login account and / or the privacy application data generated by the user's first login account, so that the user can restore the usage traces of the account when logging in to the account next time, giving the user a good riding experience and improving the user's favorability. After the user gets off the vehicle, this embodiment reconfigures the account to be switched or logged in. In this way, even if the user forgets to perform operations such as account logout and account information clearing when getting off the vehicle, the user's privacy security can be guaranteed and the risk of user privacy leakage can be reduced.

[0197] An embodiment of the present invention further provides an electronic device, Figure 6is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention, see Figure 6 The electronic device 1000 includes a processor 1001 and a memory 1002. The memory 1002 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 1001, the steps in any one of the above vehicle-mounted system account management methods are executed. Through the above technical solution, the processor 1001 and the memory 1002 are interconnected and communicate with each other through a communication bus and / or other forms of connection mechanisms (not shown), and the memory 1002 stores a computer program executable by the processor. When the electronic device 1000 is running, the processor 1001 executes the computer program to execute the vehicle system account management method in any optional implementation of the above embodiment to achieve the following functions: in response to the user's account level configuration operation, determine the account level of at least one account involved in the vehicle system; according to the privacy level of at least one application in the vehicle system, clarify the mapping relationship between each application and the account level, so as to store the account information and privacy application data of each account in at least one privacy data storage area of the vehicle system; in response to the user's account switching or login operation, directly call the privacy application data in the privacy data storage area corresponding to the target account according to the account information of the target account, so as to achieve account switching or login, and restore the user's use trace of the target account, or, based on the account information of the target account, add at least one privacy data storage area in the vehicle system to store at least the account information and privacy application data of the target account; in response to the user getting off the vehicle event, reconfigure the account to be switched or logged in.

[0198] An embodiment of the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a vehicle-mounted system account management method as provided in all the embodiments of the invention of the present application: in response to an account level configuration operation of a user, determining the account level of at least one account involved in the vehicle-mounted system; clarifying the mapping relationship between each application and the account level according to the privacy level of at least one application in the vehicle-mounted system, so as to store the account information and privacy application data of each account in at least one privacy data storage area of the vehicle-mounted system; in response to an account switching or login operation of the user, directly calling the privacy application data in the privacy data storage area corresponding to the target account according to the account information of the target account, so as to implement account switching or login, and restore the user's usage traces of the target account, or, based on the account information of the target account, adding at least one privacy data storage area in the vehicle-mounted system to at least store the account information and privacy application data of the target account; in response to a user getting off the vehicle event, reconfiguring the account to a waiting-to-switch or login state.

[0199] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, device, or device.

[0200] Computer-readable signal media may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0201] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0202] Computer program code for performing the operations of the present invention may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0203] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A vehicle system account management method, characterized in that: At least: In response to an account level configuration operation by a user, determining an account level of at least one account related to the in-vehicle system; According to the privacy level of at least one application in the vehicle system, clarify the mapping relationship between each application and the account level, so as to store the account information and the private application data of each account in the at least one private data storage area of the vehicle system; In response to the user's account switching or login operation, directly calling the private application data in the private data storage area corresponding to the target account according to the account information of the target account to implement the account switching or login and restore the user usage trace of the target account, or, based on the account information of the target account, adding at least one of the private data storage areas in the vehicle-mounted system to store at least the account information and private application data of the target account; In response to a user exiting the vehicle, reconfiguring the account to a waiting-to-switch or logged-in state; The account information includes the account level and the biometric characteristics of the user to whom the account belongs, and at least one of the account name and the account serial number.

2. The vehicle-mounted system account management method according to claim 1, characterized in that: Also includes: After the target account is switched or logged in, the account information of the target account is configured to be visible, and the account information of other accounts except the target account is set to be hidden.

3. The vehicle-mounted system account management method according to claim 2, characterized in that: After the target account is switched or logged in, the account information in any application under the target account is configured to be hidden.

4. The vehicle-mounted system account management method according to claim 1, characterized in that: In response to the user's account switching or login operation, directly calling the private application data in the private data storage area corresponding to the target account according to the account information of the target account to implement the account switching or login and restore the user usage trace of the target account, at least comprising: In response to an account switching or login operation of the user, obtaining a human biometric feature of the user to which the target account belongs; Determining whether the target account already exists in the vehicle-mounted system according to the biological characteristics of the user to whom the target account belongs; If the target account already exists in the vehicle-mounted system, the private application data in the private data storage area corresponding to the target account is directly called according to the human biometric characteristics of the user to which the target account belongs, so as to realize account switching or login and restore the user usage traces of the target account.

5. The vehicle-mounted system account management method according to claim 1, characterized in that: In response to the user's account switching or login operation, directly calling the private application data in the private data storage area corresponding to the target account according to the account information of the target account to implement the account switching or login and restore the user usage trace of the target account, at least comprising: In response to an account switching or login operation of the user, obtaining a human biometric feature of the user to which the target account belongs and an account level of the target account; Determining whether the target account already exists in the vehicle-mounted system according to the biological characteristics of the user to whom the target account belongs; If the target account already exists in the vehicle-mounted system, continue to determine whether the number of the target account is equal to 1; If the number of the target account is equal to 1, the private application data in the private data storage area corresponding to the target account is directly called to implement account switching or login, and restore the user usage trace of the target account; If the number of target accounts is greater than 1, the privacy application data in the privacy data storage area corresponding to the target account is directly called according to the account name, account serial number and / or account level of the target account to achieve account switching or login and restore the user usage traces of the target account.

6. The vehicle-mounted system account management method according to claim 1, characterized in that: In response to the account switching or login operation of the user, at least one privacy data storage area is added to the vehicle-mounted system based on the account information of the target account to store at least the account information of the target account and the privacy application data, including at least: In response to an account switching or login operation of the user, obtaining a human biometric feature of the user to which the target account belongs; Determining whether the target account already exists in the vehicle-mounted system according to the biological characteristics of the user to whom the target account belongs; If the target account does not exist in the vehicle-mounted system, creating and activating the target account in the vehicle-mounted system based on the account information of the target account; After the target account is activated, the privacy application is notified through a preset message delivery method to divide the privacy application data; In response to the user's privacy application usage operation, at least one privacy data storage area is added to the in-vehicle system to store at least the account information of the target account and the privacy application data.

7. The vehicle-mounted system account management method according to claim 5, characterized in that: If the target account does not exist in the vehicle-mounted system, creating and activating the target account in the vehicle-mounted system based on the account information of the target account includes: If the target account does not exist in the vehicle-mounted system, determining whether the number of accounts in the vehicle-mounted system reaches an upper limit; If the number of accounts in the vehicle-mounted system does not reach the upper limit, creating and activating the target account in the vehicle-mounted system based on the account information of the target account; If the number of accounts in the vehicle-mounted system reaches the upper limit, at least one account that meets the preset disposal condition is deleted, and then a new target account is created and activated in the vehicle-mounted system based on the account information of the target account.

8. A vehicle-mounted system account management device, characterized in that: At least: a level determination module, at least for determining an account level of at least one account involved in the vehicle-mounted system in response to an account level configuration operation by a user; A mapping storage module, at least for clarifying the mapping relationship between each application and the account level according to the privacy level of at least one application in the vehicle system, so as to store the account information and the privacy application data of each account in the at least one privacy data storage area of the vehicle system; Calling a newly added module, at least for responding to the account switching or login operation of the user, directly calling the privacy application data in the privacy data storage area corresponding to the target account according to the account information of the target account, so as to realize the account switching or login, and restore the user usage trace of the target account, or, based on the account information of the target account, adding at least one of the privacy data storage areas in the vehicle-mounted system to store at least the account information and privacy application data of the target account; A state switching module, at least for reconfiguring the account to a waiting-to-switch or logged-in state in response to a user getting off the vehicle event; The account information includes at least one of the account name, account serial number, account level and human biometric characteristics of the user to whom the account belongs.

9. An electronic device, characterized in that: It includes a processor and a memory, wherein the memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the steps in the vehicle-mounted system account management method as described in any one of claims 1 to 7 are executed.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the vehicle-mounted system account management method described in any one of claims 1 to 7 is implemented.

Explore free tools for quick IP tasks

Patent Information

AI Technical Summary

Abstract

Description