Vehicle account management method and device, vehicle and storage medium
By combining driver identity authentication and vehicle status information in the vehicle account management system, precise access control is achieved, solving the problem of difficulty in coordinating security and convenience in traditional systems, and improving authorization efficiency and security in multi-account scenarios.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHERY AUTOMOBILE CO LTD
- Filing Date
- 2026-01-06
- Publication Date
- 2026-04-24
AI Technical Summary
Traditional vehicle account management systems suffer from poor adaptability to multi-account scenarios, coarse access control, an imbalance between security and convenience, and low authorization efficiency. They are unable to meet the needs of immediate and short-term sharing, and cannot achieve fine-grained control over specific functions.
By matching the driver's identity verification information with a preset database and combining the vehicle's power and gear status information, the vehicle's safety status is determined, and the driver's corresponding account management interface is activated, supporting precise permission management and efficient authorization.
It achieves efficient and accurate permission management while ensuring vehicle safety, avoiding insufficient authorization and accidental triggering, and improving security and convenience in multi-account scenarios.
Smart Images
Figure CN121923883A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle technology, and in particular to a vehicle account management method, a vehicle account management device, a computer-readable storage medium, and a vehicle. Background Technology
[0002] As new energy vehicles develop towards intelligence, connectivity, and sharing, the interaction mode between accounts and vehicles has shifted from traditional physical key control to a digital identity interaction mode centered on accounts. Account management systems have become the core hub connecting accounts, vehicles, and cloud services, responsible for functions such as identity authentication, access control, personalized settings, and data synchronization.
[0003] Currently, vehicle account management systems typically employ a static hierarchical architecture of a single main account plus sub-accounts. This architecture suffers from significant drawbacks, including poor adaptability to multi-account scenarios, coarse-grained access control, an imbalance between security and convenience, and low authorization efficiency. In increasingly common scenarios such as family sharing, vehicle sharing, or fleet management, switching accounts requires re-login via the vehicle's infotainment system or mobile application, a cumbersome process. Sub-account permission settings often present a binary state of "all or nothing," such as only being able to start the vehicle but not being able to adjust the closely related charging strategy, or vice versa. This rigid architecture cannot support the need for dynamically allocating precise permissions based on specific scenarios, such as temporarily authorizing a friend to only perform charging operations but prohibiting them from starting the vehicle or viewing location information. In other words, permission management mostly remains at a coarse-grained level of starting or disabling the entire vehicle, lacking fine-grained control over specific components or functions. This can lead to over-authorization, such as inadvertently granting vehicle control to a third party, potentially resulting in the leakage of private data such as driving trajectory and battery health; or under-authorization, such as the difficulty in achieving fine-grained control in fleet management, granting charging permissions only to the driver while restricting their high-speed driving capabilities. In addition, the authorization process often relies on manual operation by the main account and multiple verification steps, resulting in slow response and difficulty in meeting the needs of immediate and short-term sharing. Summary of the Invention
[0004] This application aims to at least partially address one of the technical problems in related technologies. To this end, the first objective of this application is to propose a vehicle account management method. The method includes: obtaining the current driver's identity authentication information and matching it with a preset identity database; if the current driver's identity authentication information matches the preset identity database, obtaining vehicle power status information and vehicle gear status information; and if the vehicle is determined to be in a safe state based on the vehicle power status information and vehicle gear status information, displaying the account management interface corresponding to the current driver to respond to account management commands issued by the current driver through the account management interface. This application activates the driver's corresponding account management interface when the driver's identity authentication is successful and the vehicle is determined to be in a safe state based on the vehicle power status information and vehicle gear status information. This ensures that high-privilege operations such as account configuration are not mistakenly triggered during driving, and supports independent authorization and management of specific functions in safe scenarios to avoid insufficient authorization. Furthermore, it provides efficient and accurate permission management capabilities for multi-account scenarios while ensuring vehicle physical security, thereby fundamentally solving the technical contradiction of difficulty in coordinating security and convenience in traditional static account architectures.
[0005] The second objective of this application is to provide a vehicle account management device.
[0006] The third objective of this application is to provide a computer-readable storage medium.
[0007] The fourth objective of this application is to propose a vehicle.
[0008] To achieve the above objectives, the first aspect of this application proposes a vehicle account management method, which includes: obtaining the current driver's identity authentication information and matching and authenticating the current driver's identity authentication information with a preset identity database; if the current driver's identity authentication information matches the preset identity database, obtaining vehicle power status information and vehicle gear status information; if it is determined that the vehicle is in a safe state based on the vehicle power status information and vehicle gear status information, displaying the account management interface corresponding to the current driver to respond to account management instructions issued by the current driver through the account management interface.
[0009] According to one embodiment of this application, the account management instructions include one or more of the following: vehicle function call instructions, vehicle function editing instructions, and vehicle function deletion instructions.
[0010] According to one embodiment of this application, determining that a vehicle is in a safe state based on vehicle power status information and vehicle gear status information includes: determining that the vehicle is in a safe state when the vehicle power status information indicates that the vehicle is powered on and the vehicle gear status information indicates that the vehicle is in the parking gear.
[0011] According to one embodiment of this application, the vehicle includes multiple accounts, and the method further includes: obtaining account information for each account when the current driver's identity authentication information does not match a preset identity database; and displaying an account registration interface to respond to an account registration instruction issued by the current driver through the account registration interface when it is determined that there is an idle account based on the account information of each account.
[0012] According to one embodiment of this application, the account registration instruction includes an account information setting instruction and an identity authentication information setting instruction.
[0013] According to one embodiment of this application, the method further includes: if it is determined from the account information of each account that there is no idle account, invoking the vehicle functions before the last time the vehicle was powered off.
[0014] According to one embodiment of this application, the identity authentication information includes biometric information and / or digital credential information.
[0015] To achieve the above objectives, a second aspect of this application provides a vehicle account management device, comprising: a first acquisition module for acquiring the current driver's identity authentication information; a matching authentication module for matching and authenticating the current driver's identity authentication information with a preset identity database; a second acquisition module for acquiring vehicle power status information and vehicle gear status information when the current driver's identity authentication information matches the preset identity database; and a management module for displaying an account management interface to respond to account management instructions issued by the current driver through the account management interface when it is determined that the vehicle is in a safe state based on the vehicle power status information and vehicle gear status information.
[0016] To achieve the above objectives, a third aspect of this application provides a computer-readable storage medium storing a vehicle account management program that, when executed by a processor, implements the aforementioned vehicle account management method.
[0017] To achieve the above objectives, a fourth aspect of this application provides a vehicle including a memory, a processor, and a vehicle account management program stored in the memory and executable on the processor. When the processor executes the vehicle account management program, it implements the aforementioned vehicle account management method.
[0018] According to the vehicle account management method, device, vehicle, and storage medium of this application embodiment, the current driver's identity authentication information is obtained and matched with a preset identity database for authentication. If the current driver's identity authentication information matches the preset identity database, vehicle power status information and vehicle gear status information are obtained. If the vehicle is determined to be in a safe state based on the vehicle power status information and vehicle gear status information, the account management interface corresponding to the current driver is displayed to respond to account management instructions issued by the current driver through the account management interface. This application activates the driver's corresponding account management interface when the driver's identity authentication is successful and the vehicle is determined to be in a safe state based on the vehicle power status information and vehicle gear status information. This ensures that high-privilege operations such as account configuration are not mistakenly triggered during driving, and supports independent authorization and management of specific functions in safe scenarios to avoid insufficient authorization. Furthermore, it provides efficient and accurate permission management capabilities for multi-account scenarios while ensuring vehicle physical security, thereby fundamentally solving the technical contradiction of difficulty in coordinating security and convenience in traditional static account architectures. Attached Figure Description
[0019] Figure 1 A flowchart of a vehicle account management method according to some embodiments of this application; Figure 2 Here is a flowchart of a vehicle account management method according to other embodiments of this application; Figure 3 This is a block diagram of a vehicle account management device according to some embodiments of this application; Figure 4 This is a block diagram of a vehicle according to some embodiments of this application. Detailed Implementation
[0020] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.
[0021] The vehicle account management method, apparatus, vehicle, and storage medium of this application are described in detail below with reference to the accompanying drawings.
[0022] Figure 1 This is a flowchart illustrating a vehicle account management method according to some embodiments of this application. (Refer to...) Figure 1 The vehicle account management method of this application embodiment may include the following steps: S110: Obtain the current driver's identity authentication information and match and authenticate the current driver's identity authentication information with the preset identity database.
[0023] Specifically, the preset identity database includes one or more preset identity authentication information. After obtaining the current driver's identity authentication information, the current driver's identity authentication information can be compared and matched with multiple preset identity authentication information to complete the current driver's identity verification.
[0024] To further illustrate the above embodiments, in this application embodiment, the identity authentication information includes biometric information and / or digital credential information.
[0025] Specifically, the current driver's identity authentication information may include biometric information, digital credential information, or a combination of both. Biometric information may include the current driver's facial features and fingerprints, while digital credential information may be a pre-set username and password for the current driver.
[0026] Among them, facial feature information can be collected by a camera set above the dashboard or on the A-pillar; fingerprint feature information can be collected by a fingerprint recognition module set in the dashboard or in-vehicle terminal; digital credential information can be entered by the driver through virtual buttons on the in-vehicle terminal display, or it can be wirelessly connected to an APP on the driver's smartphone to synchronize or request confirmation of the bound digital credential information.
[0027] It should be noted that there are no specific restrictions on how biometric information and digital credential information are obtained.
[0028] In the following description, facial feature information is used as the current driver's identity authentication information as an example, but this is not intended to limit this application.
[0029] S120, when the current driver's identity authentication information matches the preset identity database, obtains the vehicle power status information and the vehicle gear status information.
[0030] Specifically, when the current driver's identity authentication information is facial feature information, the corresponding preset identity database includes multiple registered and encrypted stored preset facial feature templates for legitimate drivers. After obtaining the current driver's facial feature information, it is converted into a standardized digital feature template. Then, the digital feature template is compared with the registered and encrypted stored legitimate driver feature templates in the preset identity database. For example, the similarity value between the two is calculated and compared with a preset similarity threshold. If the similarity value is greater than or equal to the preset similarity threshold, it is determined that the facial feature information matches the preset identity database, i.e., the current driver's authentication is successful. If the similarity value is less than the preset similarity threshold, it is determined that the facial feature information does not match the preset identity database, i.e., the current driver's authentication fails. The preset similarity threshold can be set according to the actual situation; for example, the preset similarity threshold can be 99%, without specific limitations. Finally, if it is determined that the facial feature information matches the preset identity database, the vehicle's power status information and vehicle gear status information are obtained. Among them, vehicle power status information can be collected through vehicle networks such as CAN bus or LIN bus. Vehicle power status information includes power-off status, accessory power supply status, power-on status, drivable ready status, start status, and charging status. Vehicle gear status information can be collected through gear position sensors. Vehicle gear status information includes parking gear, reverse gear, neutral gear, and drive gear.
[0031] S130, after determining that the vehicle is in a safe state based on the vehicle power status information and the vehicle gear status information, displays the account management interface corresponding to the current driver in response to the account management instructions issued by the current driver through the account management interface.
[0032] Specifically, after obtaining the vehicle power status information and vehicle gear status information, the vehicle's safe state can be determined based on these information. For example, the current vehicle state can be determined by looking up a preset relationship mapping table between the vehicle power status information, vehicle gear status information, and vehicle state. This preset relationship mapping table includes multiple vehicle power status information-vehicle gear status information and the vehicle state corresponding to each vehicle power status information-vehicle gear status information. The current vehicle state includes a safe state and an unsafe state.
[0033] To further illustrate the above embodiments, in this application embodiment, determining that the vehicle is in a safe state based on the vehicle power status information and the vehicle gear status information includes: determining that the vehicle is in a safe state when the vehicle power status information indicates that the vehicle is powered on and the vehicle gear status information indicates that the vehicle is in the parking gear.
[0034] For example, if the obtained vehicle power status information is "power on" and the vehicle gear status information is "park", then the vehicle is determined to be in a safe state; if the obtained vehicle power status information is not "power on", or the vehicle gear status information is not "park", or the vehicle power status information is not "power on" and the vehicle gear status information is not "park", then the vehicle is determined to be in an unsafe state.
[0035] Furthermore, when the vehicle is determined to be in a safe state based on the vehicle's power status information and gear status information, the vehicle terminal will display the account management interface. The driver can issue account management commands through the account management interface. After receiving the account management commands, the vehicle will perform corresponding account management operations and persistently store personalized data based on the account management commands.
[0036] To further illustrate the above embodiments, in this application embodiment, the account management instructions include one or more of the following: vehicle function call instructions, vehicle function editing instructions, and vehicle function deletion instructions.
[0037] Specifically, vehicle functions include, but are not limited to, human-machine interface settings that the driver prefers, such as layout and time display methods; media and content preferences, such as boot animations, frequently listened playlists and radio stations, and commonly used apps; intelligent service configurations, such as custom wake words and schedule reminders; cabin environment settings, such as ambient lighting, fragrance, and air conditioning modes; and hardware device status, such as seat and rearview mirror positions, welcome light effects, and dual-screen interaction rules.
[0038] Once the driver successfully completes identity authentication via facial recognition and confirms that the vehicle is in a safe state (e.g., powered on and parked), the in-vehicle terminal will display the account management interface. The driver can then use this interface to issue commands to invoke, edit, or delete vehicle functions.
[0039] Specifically, when the vehicle receives a vehicle function call command, it will load and apply the complete personalized vehicle functions pre-stored by the current driver based on the vehicle function call command; when the vehicle receives a vehicle function editing command, it will perform the corresponding vehicle function editing operation based on the vehicle function editing command, such as changing the boot animation, adjusting the ambient light color, or updating the welcome light display content, and save the changes; when the vehicle receives a vehicle function deletion command, it will perform the corresponding vehicle function deletion operation based on the vehicle function deletion command, such as clearing a schedule reminder.
[0040] In addition, if the vehicle does not receive an account management instruction within a preset time (e.g., 20 seconds), the vehicle will directly invoke and execute the full set of personalized vehicle functions pre-stored by the current driver.
[0041] This application activates the driver's account management interface after successful driver authentication and confirmation that the vehicle is in a safe state based on vehicle power status and gear position information. This ensures that high-privilege operations such as account configuration are not accidentally triggered during driving, while also supporting independent authorization and management of specific functions in safe scenarios to avoid insufficient authorization. Furthermore, it provides efficient and accurate permission management capabilities for multi-account scenarios while ensuring the physical safety of the vehicle, thereby fundamentally resolving the technical contradiction between security and convenience in traditional static account architectures.
[0042] In some embodiments, the vehicle includes multiple accounts, and the method further includes: obtaining account information for each account when the current driver's identity authentication information does not match the preset identity database; and displaying an account registration interface to respond to an account registration instruction issued by the current driver through the account registration interface when it is determined that there is an idle account based on the account information of each account.
[0043] Specifically, if the current driver's identity authentication information does not match the preset identity database, it indicates that the current driver has not pre-created an account and configured vehicle functions, and the in-vehicle terminal cannot display the account management interface corresponding to the current driver. In this case, account information for each account can be read from the account information database, and the existence of an idle account can be determined based on this information. Account information includes, but is not limited to, account ID, mobile phone number, and account name. The following explanation uses determining the existence of an idle account based on a mobile phone number as an example, but this is not intended to limit this application. For example, if each account is bound to a verified mobile phone number, it is determined that no idle account exists; if one account is not bound to a verified mobile phone number, it is determined that an idle account exists.
[0044] Furthermore, if it is determined that there are idle accounts based on the account information of each account, the vehicle terminal will display the account registration interface. The current driver can issue an account registration command through the account registration interface. After receiving the account registration command, the vehicle will perform the corresponding account registration operation based on the account registration command to register the account corresponding to the current driver. If it is determined that there are no idle accounts based on the account information of each account, the vehicle functions before the last power-off can be directly invoked.
[0045] To further illustrate the above embodiments, in this application embodiment, the account registration instruction includes an account information setting instruction and an identity authentication information setting instruction.
[0046] Specifically, firstly, the current driver issues an account information setting command through the account registration interface. For example, the driver enters and submits basic personal information on the account registration interface, such as account name, account ID, bound mobile phone number, and vehicle functions (such as seat position adjustment, air conditioning preset, entertainment theme adjustment, etc.). The vehicle saves the above information and generates the corresponding configuration file. Then, guided by the account registration interface, the current driver issues an identity authentication information setting command. For example, the driver enters an account name and password on the account registration interface, or enters biometric information (such as fingerprint or facial feature information). The vehicle generates an identity authentication credential based on the identity authentication information setting command and binds the identity authentication credential to the account. At this point, the corresponding account for the current driver is successfully created.
[0047] In some embodiments, where the authentication information includes biometric information and digital credential information, the biometric information has a higher priority than the digital credential information. That is, after obtaining the current driver's biometric information, if the current driver's biometric information does not match the corresponding preset identity database, the current driver's digital credential information can be used for authentication. If the current driver's digital credential information also does not match the corresponding preset identity database, authentication fails, and the in-vehicle central control screen does not display the account management interface; that is, the current driver cannot access, edit, or delete vehicle functions.
[0048] As a concrete example, refer to Figure 2 The vehicle account management method of this application is based on the ICM (Integrated Cockpit Module), using the OMS (Occupant Monitoring System) for identity recognition, the ZCU_R (Zone Control Unit Right) for vehicle status perception, and the TCP (Telematics Control Unit) for cross-terminal synchronization to achieve a closed-loop logic of "identity verification - status judgment - multi-terminal display". Specifically, the OMS, as the identity recognition source, uses cameras, infrared sensors, etc., to achieve current driver facial recognition and outputs the facial recognition result, providing identity verification for account activation. The ZCU_R, as the vehicle status source, is responsible for collecting vehicle power status information and vehicle gear status information, providing security scenario judgment conditions for account operation. The ICM, as the account management master controller, receives the identity information from the OMS and the vehicle status information from the ZCU_R, performs a dual-condition judgment of "identity + status", and triggers subsequent account display and synchronization logic. As a cross-terminal synchronization module, TCP receives account status instructions from the ICM and synchronizes account information (such as avatar, nickname, and function settings) to the mobile APP, achieving consistency between the vehicle system and the mobile terminal.
[0049] The vehicle account management method in this application embodiment may further include the following steps: The first step, OMS, performs identity authentication: OMS collects occupant facial information using the in-cabin camera and compares it with the user facial information database in the account, outputting the authentication result. "Yes" indicates successful authentication; "No" indicates authentication failure. If authentication fails, the process terminates, preventing subsequent account operations and avoiding unauthorized user access; if authentication succeeds, the process proceeds to the next step, vehicle status assessment.
[0050] The second step involves the ICM acquiring vehicle status information and determining if the vehicle is in a safe state. The ICM obtains two key vehicle statuses from the ZCU_R: vehicle power status information (must be powered on, indicating the vehicle is running and ready for cockpit operation); and vehicle gear status information (must be in park, indicating the vehicle is stationary to avoid distracting the driver). The ICM performs logical checks on these two statuses: if either status is not met, the process terminates and account display is not triggered (ensuring operational safety); if both are met, the process proceeds to the next step: account status output.
[0051] The third step involves multi-terminal account status display: When identity authentication is successful and the vehicle status is secure, the ICM triggers output from both the vehicle-mounted system and the mobile terminal. Specifically, on the vehicle-mounted system: the current driver's account management interface (including account avatar, nickname, and vehicle function settings on the main interface) prompts the current driver to access personalized account operations (such as adjusting seat memory or setting charging strategies); on the mobile terminal: the account status is synchronized to the mobile app via the TCP module (such as "Account logged in" and "Current vehicle status"), ensuring consistency between the vehicle-mounted system and the mobile terminal and avoiding information fragmentation.
[0052] This application ensures operational security by setting up dual-condition verification, combining identity authentication with vehicle status information. Account operations are triggered only when the user's identity is legitimate and the vehicle is in a safe state, avoiding the risk of accidental operation or unauthorized user access while driving, and meeting the safety requirements of the vehicle's high-voltage system and smart cockpit. By integrating ZCU_R, OMS, and TCP information through ICM, it achieves inter-domain linkage of vehicle status, identity information, and cross-terminal synchronization, solving the problems of module isolation and information fragmentation in traditional account management, and supporting the intelligent and connected architecture characteristics of vehicles. It optimizes the user experience by synchronizing the account status to the mobile APP through the TCP module, achieving consistency between the "vehicle system and mobile terminal" status, avoiding operational confusion caused by inconsistent information across devices, such as the mobile APP showing "not logged in" but the vehicle system having entered the account interface, improving the continuity of intelligent interaction. It can support personalized function processes. The power status and gear status provided by ZCU_R are the core status of the vehicle's high-voltage system and chassis control, ensuring deep adaptation between account operations and the vehicle's security and functional logic.
[0053] Corresponding to the above embodiments, this application also proposes a vehicle account management device.
[0054] Reference Figure 3 The vehicle account management device 200 includes: a first acquisition module 210, a matching and authentication module 220, a second acquisition module 230, and a management module 240.
[0055] The first acquisition module 210 is used to acquire the current driver's identity authentication information. The matching and authentication module 220 is used to match and authenticate the current driver's identity authentication information with a preset identity database. The second acquisition module 230 is used to acquire vehicle power status information and vehicle gear status information when the current driver's identity authentication information matches the preset identity database. The management module 240 is used to display an account management interface to respond to account management instructions issued by the current driver through the account management interface when it is determined that the vehicle is in a safe state based on the vehicle power status information and vehicle gear status information.
[0056] According to one embodiment of this application, the account management instructions include one or more of the following: vehicle function call instructions, vehicle function editing instructions, and vehicle function deletion instructions.
[0057] According to one embodiment of this application, if it is determined that the vehicle is in a powered-on state based on the vehicle power status information and the vehicle gear status information indicates that the vehicle is in the parking gear, then the vehicle is determined to be in a safe state.
[0058] According to one embodiment of this application, the vehicle includes multiple accounts. If the current driver's identity authentication information does not match the preset identity database, the account information of each account is obtained. If it is determined that there is an idle account based on the account information of each account, an account registration interface is displayed to respond to the account registration instruction issued by the current driver through the account registration interface.
[0059] According to one embodiment of this application, the account registration instruction includes an account information setting instruction and an identity authentication information setting instruction.
[0060] According to one embodiment of this application, if it is determined from the account information of each account that there is no idle account, the vehicle functions before the last time the vehicle was powered off are invoked.
[0061] According to one embodiment of this application, the identity authentication information includes biometric information and / or digital credential information.
[0062] It should be noted that the above explanation of the embodiments and beneficial effects of the vehicle account management method also applies to the vehicle account management device of the embodiments of this application. To avoid redundancy, it will not be elaborated in detail here.
[0063] Corresponding to the above embodiments, this application also proposes a computer-readable storage medium.
[0064] The present application provides a computer-readable storage medium storing a vehicle account management program that, when executed by a processor, implements the aforementioned vehicle account management method.
[0065] It should be noted that the above explanation of the embodiments and beneficial effects of the vehicle account management method also applies to the computer-readable storage medium of the embodiments of this application. To avoid redundancy, it will not be elaborated in detail here.
[0066] Corresponding to the above embodiments, this application also proposes a vehicle.
[0067] See Figure 4 As shown, the vehicle 300 of this application includes a memory 310, a processor 320, and a vehicle account management program stored on the memory 310 and capable of running on the processor 320. When the processor executes the vehicle account management program, it implements the aforementioned vehicle account management method.
[0068] It should be noted that the above explanation of the embodiments and beneficial effects of the vehicle account management method also applies to the vehicles in the embodiments of this application. To avoid redundancy, they will not be elaborated in detail here.
[0069] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.
[0070] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.
[0071] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.
[0072] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.
[0073] In this application, unless otherwise expressly specified and limited, the terms "installation," "connection," "joining," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise expressly limited. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.
[0074] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.
Claims
1. A vehicle account management method, characterized in that, The method includes: Obtain the current driver's identity authentication information and match and authenticate the current driver's identity authentication information with a preset identity database; If the current driver's identity authentication information matches the preset identity database, obtain the vehicle power status information and the vehicle gear status information; If the vehicle is determined to be in a safe state based on the vehicle power status information and the vehicle gear status information, the account management interface corresponding to the current driver is displayed to respond to the account management instructions issued by the current driver through the account management interface.
2. The vehicle account management method according to claim 1, characterized in that, The account management instructions include one or more of the following: vehicle function call instructions, vehicle function editing instructions, and vehicle function deletion instructions.
3. The vehicle account management method according to claim 1, characterized in that, The step of determining that the vehicle is in a safe state based on the vehicle power status information and the vehicle gear status information includes: If the vehicle is determined to be powered on based on the vehicle power status information and the vehicle is in parking gear based on the vehicle gear status information, then the vehicle is determined to be in a safe state.
4. The vehicle account management method according to claim 1, characterized in that, The vehicle includes multiple accounts, and the method further includes: If the current driver's identity authentication information does not match the preset identity database, obtain the account information for each account; If an idle account is determined based on the account information of each account, an account registration interface is displayed in response to the account registration instruction issued by the current driver through the account registration interface.
5. The vehicle account management method according to claim 4, characterized in that, The account registration instructions include instructions for setting account information and instructions for setting identity authentication information.
6. The vehicle account management method according to claim 4, characterized in that, The method further includes: If no idle account is found based on the account information of each account, the vehicle functions from the last time the vehicle was powered off are invoked.
7. The vehicle account management method according to any one of claims 1-6, characterized in that, Identity authentication information includes biometric information and / or digital credential information.
8. A vehicle account management device, characterized in that, The device includes: The first acquisition module is used to acquire the current driver's identity authentication information; The matching and authentication module is used to match and authenticate the current driver's identity authentication information with a preset identity database; The second acquisition module is used to acquire vehicle power status information and vehicle gear status information when the current driver's identity authentication information matches the preset identity database. The management module is used to display the account management interface when the vehicle is determined to be in a safe state based on the vehicle power status information and the vehicle gear status information, in response to the account management instructions issued by the current driver through the account management interface.
9. A computer-readable storage medium, characterized in that, It stores a vehicle account management program, which, when executed by a processor, implements the vehicle account management method according to any one of claims 1-7.
10. A vehicle, characterized in that, The system includes a memory, a processor, and a vehicle account management program stored in the memory and executable on the processor. When the processor executes the vehicle account management program, it implements the vehicle account management method according to any one of claims 1-7.