Control method and system of vehicle-mounted device, electronic device and computer storage medium

Abstract

Embodiments of the present application provide a vehicle-mounted device control method and system, electronic equipment and computer storage medium. The vehicle-mounted device control method comprises: obtaining login information for logging in a co-driver cloud account; verifying the login information through a co-driver cloud account management module; if the verification is successful, the co-driver mode is activated, and a state variable of the vehicle-mounted device in the co-driver mode sent by the co-driver cloud account management module is received, so that the co-driver control module controls the vehicle-mounted device according to the state variable. The present application increases the independent authentication and management system of the co-driver cloud account, gives the co-driver cloud account exclusive matching function, and stores the state variable of the related vehicle-mounted device in the co-driver cloud account management module, thereby protecting the privacy of the control function of the co-driver related vehicle-mounted device in the co-driver mode, reducing the repeated processing of the state variable of the control function of the traditional cloud account management, and improving the efficiency of the cloud account management.

Description

Technical Field

[0001] This application relates to the field of vehicle networking technology, and in particular to a control method, system, electronic device, and computer storage medium for in-vehicle equipment. Background Technology

[0002] With the rapid development of connected and intelligent vehicle technologies, personalized and secure cloud account management experiences are gaining popularity among users.

[0003] In existing technologies, vehicle cloud account management is controlled by a unified cloud account management and control system. Typically, this unified cloud account is registered and authenticated by the vehicle owner. The unified cloud account management module stores data parameters related to the owner's preferences and habits. The vehicle management module manages the state variables of in-vehicle devices based on these data parameters. After the owner logs in with their unified cloud account, the vehicle management module adjusts the state variables of the in-vehicle devices to match their preferences and habits, and the cockpit environment changes accordingly. However, when other users are present in the vehicle, such as the front passenger, left rear passenger, and right rear passenger, these users must adapt to the control functions of the in-vehicle devices matched with their unified cloud account. If other users are not accustomed to the current state of the in-vehicle devices, readjustment is required. This results in frequent data parameter operations corresponding to the state variables of the in-vehicle devices under the unified cloud account management mode, leading to repetitive processing and reduced efficiency in cloud account management, thus degrading the user experience. Summary of the Invention

[0004] In view of this, embodiments of this application provide a control method, system, electronic device, and computer storage medium for vehicle-mounted equipment, in order to overcome the shortcomings of traditional cloud account management control functions in the prior art, such as repetitive processing of state variables and low efficiency of cloud account management.

[0005] In a first aspect, embodiments of this application provide a control method for an in-vehicle device, the method comprising: obtaining login information for logging into a co-pilot cloud account; verifying the login information through a co-pilot cloud account management module; if the verification is successful, activating the co-pilot mode, and receiving a status variable of the in-vehicle device in the co-pilot mode sent by the co-pilot cloud account management module, so that the co-pilot control module controls the in-vehicle device according to the status variable.

[0006] Optionally, in one embodiment of this application, the co-driver control module controls the in-vehicle equipment according to the state variables, including: each sub-control module in the co-driver control module controls the in-vehicle equipment related to the sub-control module according to the state variables, wherein the in-vehicle equipment includes at least one of the following: a co-driver seat, a co-driver footrest, a co-driver area ambient light, a co-driver area automatic air conditioner, and a co-driver area electric air vent.

[0007] Optionally, in one embodiment of this application, the login information includes voiceprint feature information. The login information is verified by the Co-pilot Cloud Account Management Module, which includes: verifying the voiceprint feature information by the Co-pilot Cloud Account Management Module; if the voiceprint feature information matches the preset voiceprint feature information used for valid login to the Co-pilot Cloud Account in the Co-pilot Cloud Account Management Module, the verification is successful.

[0008] Optionally, in one embodiment of this application, before obtaining the login information for logging into the co-driver cloud account, the method includes: obtaining verification information for logging into the vehicle owner cloud account; identifying the verification information through the vehicle owner cloud account management module; and if the identification is successful, synchronizing the data information related to the co-driver cloud account in the vehicle owner cloud account.

[0009] Optionally, in one embodiment of this application, the verification information includes at least one of facial recognition information, voiceprint feature information, fingerprint information, and username information that characterize the vehicle owner's identity information.

[0010] Optionally, in one embodiment of this application, the method further includes: during the co-pilot mode activation period, if the user adjusts the in-vehicle device, receiving the adjusted state variables of the in-vehicle device related to the sub-control module; storing the adjusted state variables of the in-vehicle device related to the sub-control module locally; and sending the adjusted state variables of the in-vehicle device related to the sub-control module to the co-pilot cloud account management module.

[0011] Optionally, in one embodiment of this application, the method further includes: the co-pilot cloud account management module receiving the adjusted status variables of the vehicle-mounted devices related to the sub-control module; and the co-pilot cloud account management module updating the status variables of the vehicle-mounted devices related to each sub-control module stored in the historical status variables through cloud synchronization based on the adjusted status variables of the vehicle-mounted devices related to the sub-control module.

[0012] Optionally, in one embodiment of this application, the method further includes: during the co-pilot mode activation period, the co-pilot control module sends a prohibition command to the vehicle owner cloud account management module, the prohibition command being used to prohibit the use of the control functions bound to the co-pilot area in the control functions corresponding to the vehicle owner cloud account.

[0013] Secondly, embodiments of this application provide a control system for an in-vehicle device. The system includes a co-pilot cloud account management module, a communication module, and a co-pilot control module. The co-pilot cloud account management module verifies login information. If the verification is successful, the co-pilot mode is activated. The co-pilot cloud account management module sends the status variables of the in-vehicle device in co-pilot mode to the co-pilot control module through the communication module. The co-pilot control module receives the status variables of the in-vehicle device in co-pilot mode sent by the co-pilot cloud account management module and controls the in-vehicle device according to the status variables.

[0014] Optionally, in one embodiment of this application, the co-driver control module includes multiple sub-control modules; each sub-control module in the co-driver control module is used to control the vehicle-mounted equipment related to the sub-control module according to the state variables, and the vehicle-mounted equipment includes at least one of the following: co-driver seat, co-driver footrest, co-driver area ambient lighting, co-driver area automatic air conditioning, and co-driver area electric air vents.

[0015] Optionally, in one embodiment of this application, the system further includes a vehicle owner cloud account management module; the vehicle owner cloud account management module is used to identify verification information; if the identification is successful, the data information related to the passenger's cloud account in the vehicle owner cloud account is synchronized.

[0016] Optionally, in one embodiment of this application, the co-pilot control module is further configured to acquire the adjusted status variables of the vehicle-mounted equipment related to the sub-control module, and store the adjusted status variables of the vehicle-mounted equipment related to the sub-control module locally; the co-pilot control module sends the adjusted status variables of the vehicle-mounted equipment related to the sub-control module to the co-pilot cloud account management module through the communication module.

[0017] Optionally, in one embodiment of this application, the co-pilot cloud account management module receives the adjusted status variables of the vehicle-mounted devices related to the sub-control module; the co-pilot cloud account management module is further configured to perform cloud synchronization updates of the status variables of the vehicle-mounted devices related to each sub-control module stored in the historical status variables according to the adjusted status variables of the vehicle-mounted devices related to the sub-control module.

[0018] Optionally, in one embodiment of this application, during the co-pilot mode activation period, the co-pilot control module sends a prohibition command to the vehicle owner cloud account management module through the communication module. The prohibition command is used to prohibit the use of the control functions bound to the co-pilot area in the control functions corresponding to the vehicle owner cloud account.

[0019] Thirdly, embodiments of this application provide an electronic device, including: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other through the communication bus; the memory is used to store at least one executable instruction, which causes the processor to perform an operation corresponding to the control method of the vehicle-mounted device as described in the first aspect or any embodiment of the first aspect.

[0020] Fourthly, embodiments of this application provide a computer storage medium storing a computer program thereon, which, when executed by a processor, implements the control method for the vehicle-mounted device as described in the first aspect or any embodiment of the first aspect.

[0021] This application provides a control method, system, electronic device, and computer storage medium for an in-vehicle device. The control method includes: acquiring login information for logging into a co-pilot cloud account; verifying the login information through a co-pilot cloud account management module; if verification is successful, activating the co-pilot mode and receiving status variables in co-pilot mode sent by the co-pilot cloud account management module, so that the co-pilot control module controls the in-vehicle device according to the status variables. This application adds an independent authentication and management system for the co-pilot cloud account, giving the co-pilot cloud account a dedicated matching function. The status variables of the relevant in-vehicle devices are stored in the co-pilot cloud account management module, protecting the privacy of the control functions of the co-pilot-related in-vehicle devices in co-pilot mode, reducing the repetitive processing of status variables in traditional cloud account management control functions, and improving the efficiency of cloud account management. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0023] Figure 1 A flowchart illustrating a control method for an in-vehicle device provided in this application embodiment;

[0024] Figure 2 A schematic diagram of a unified cloud account management and control system provided in an embodiment of this application;

[0025] Figure 3 A schematic diagram of a co-pilot cloud account management and control system provided in an embodiment of this application;

[0026] Figure 4 A structural block diagram of a control system for an on-board device provided in an embodiment of this application;

[0027] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

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

[0029] It should be noted that in this application, "multiple" refers to two or more, such as multiple sub-control modules.

[0030] The specific implementation of the embodiments of this application will be further described below with reference to the accompanying drawings.

[0031] Example 1

[0032] Embodiment 1 of this application provides a control method for an in-vehicle device, such as... Figure 1 As shown, Figure 1 A flowchart illustrating a control method for an in-vehicle device provided in this application embodiment, the control method for the in-vehicle device including the following steps:

[0033] Step S101: Obtain login information for logging into the co-pilot cloud account.

[0034] The login information may include at least one of the following: facial recognition information, voiceprint information, fingerprint information, and username information that represents the identity of the co-pilot.

[0035] The co-pilot cloud account is the account that the co-pilot needs to log in and verify when accessing the status variables of multiple in-vehicle devices in their vehicle.

[0036] Step S102: Verify the login information through the co-pilot cloud account management module.

[0037] The Co-pilot Cloud Account Management Module can verify login information. During verification, it can check whether the login information matches the preset valid login information related to the co-pilot. The Co-pilot Cloud Account Management Module is associated with the status variables of multiple in-vehicle devices in the user's vehicle.

[0038] Taking voiceprint information as the login information as an example, the Co-pilot Cloud account management module verifies the voiceprint information to validate the co-pilot's identity. It's understandable that login information could also be facial recognition information; by scanning and recognizing the user's face, the Co-pilot Cloud account management module verifies the facial recognition information to validate the co-pilot's identity. Login information could also be fingerprint information; by collecting the user's fingerprint, the Co-pilot Cloud account management module verifies the fingerprint information to validate the co-pilot's identity. Login information could also be an account and password; by obtaining the user's entered account and password, the Co-pilot Cloud account management module verifies the account and password to validate the co-pilot's identity. In this example, the Co-pilot Cloud account management module verifies the login information, improving the security of logging into the Co-pilot Cloud account. Furthermore, this example does not restrict the specific form of the login information, as long as it can represent the co-pilot's identity information. This diversity of login information meets the needs of different users and improves the user experience.

[0039] Step S103: If the verification is successful, the co-pilot mode is activated, and the co-pilot cloud account management module sends the status variables of the in-vehicle equipment in co-pilot mode, so that the co-pilot control module can control the in-vehicle equipment according to the status variables.

[0040] It should be noted that in-vehicle equipment refers to in-vehicle equipment related to the adjustment of the passenger seat or passenger area environment, such as passenger seat, passenger footrest, passenger area ambient lighting, passenger area automatic air conditioning, and passenger area electric air vents, etc.

[0041] If verification is successful, it indicates that the user corresponding to the login information is the co-pilot user belonging to the co-pilot cloud account, meaning the user identity corresponding to the login information is a legitimate registered identity of the co-pilot cloud account. Upon successful verification, co-pilot mode is activated. The co-pilot cloud account management module sends the status variables of the in-vehicle devices in co-pilot mode to the co-pilot control module. In other words, the co-pilot cloud account management module sends the status variables of the in-vehicle devices stored in the cloud during the last co-pilot mode activation period to the co-pilot control module. The co-pilot control module controls the in-vehicle devices based on these status variables; that is, the co-pilot control module adjusts the status of the in-vehicle devices in the vehicle to match the status variables stored in the cloud.

[0042] If verification fails, the user will be logged out of the co-pilot cloud account and enter the vehicle's general control mode, i.e., a state without account management. At this time, the user needs to adjust the status of the vehicle's onboard devices to suit the user's habits and preferences.

[0043] In this embodiment, the control method for the in-vehicle device can be executed by the control system of the in-vehicle device. By adding an independent authentication and management system for the co-pilot cloud account and giving the co-pilot cloud account a unique matching function, the status variables of the relevant in-vehicle device are stored in the co-pilot cloud account management module. The co-pilot cloud account management module verifies the user's login information, ensuring the security of logging into the co-pilot cloud account. If the verification is successful, the co-pilot control module controls the in-vehicle device according to the status variables of the in-vehicle device sent by the co-pilot cloud account management module. This protects the privacy of the control functions of the in-vehicle device related to the co-pilot in co-pilot mode, allowing the status of the in-vehicle device to follow the co-pilot user's preferences and habits. The status variables of the in-vehicle device in the co-pilot cloud account management module are adapted to the co-pilot user, eliminating the need for the co-pilot user to readjust the status of the in-vehicle device. This reduces the repetitive processing of status variables in traditional cloud account management and control functions, improving the efficiency of cloud account management.

[0044] Example 2

[0045] This application's second embodiment is based on the solution of the first embodiment. Optionally, the login information includes voiceprint feature information, and step S102 can be implemented as follows: verifying the voiceprint feature information through the co-pilot cloud account management module; if the voiceprint feature information matches the preset voiceprint feature information used for valid login of the co-pilot cloud account in the co-pilot cloud account management module, then the verification is successful.

[0046] Using login information as voiceprint signature, the Co-pilot Cloud account management module verifies the voiceprint signature to validate the Co-pilot's exclusive user identity. If the voiceprint signature matches the preset voiceprint signature for a valid Co-pilot Cloud account, the user identity corresponding to the voiceprint signature is considered legitimately registered, and the verification is successful. Similarly, if the login information is facial recognition data, and it matches the preset facial recognition data for a valid Co-pilot Cloud account, the user identity is considered legitimately registered, and the verification is successful. If the login information is fingerprint data, and it matches the preset fingerprint data for a valid Co-pilot Cloud account, the user identity is considered legitimately registered, and the verification is successful. Finally, if the login information is an account password, and it matches the preset account password for a valid Co-pilot Cloud account, the user identity is considered legitimately registered, and the verification is successful. This example demonstrates how the Co-pilot Cloud account management module verifies voiceprint signature information, thus improving the security of Co-pilot Cloud account logins.

[0047] This application's second embodiment is based on the solution of the first embodiment. Optionally, in step S103, the co-driver control module controls the in-vehicle equipment according to the state variables. This can be achieved by the following steps: each sub-control module in the co-driver control module controls the in-vehicle equipment related to the sub-control module according to the state variables. The in-vehicle equipment includes at least one of the following: co-driver seat, co-driver footrest, co-driver area ambient lighting, co-driver area automatic air conditioning, and co-driver area electric air vents.

[0048] In this example, the passenger control module includes multiple sub-control modules. There can be multiple in-vehicle devices, such as the passenger seat, passenger footrest, passenger area ambient lighting, passenger area automatic air conditioning, and passenger area electric air vents. When controlling in-vehicle devices based on state variables, the sub-control modules control the related in-vehicle devices according to the state variables. One in-vehicle device corresponds to one sub-control module. Compared to using only the passenger control module to control the passenger seat, passenger footrest, passenger area ambient lighting, passenger area automatic air conditioning, and passenger area electric air vents, this improves the control efficiency of the in-vehicle devices.

[0049] Example 3

[0050] This application's third embodiment is based on the solutions of embodiments one and two. Optionally, before step S101, the control method of the vehicle-mounted device further includes the following steps: obtaining verification information for logging into the vehicle owner's cloud account; identifying the verification information through the vehicle owner's cloud account management module; and if the identification is successful, synchronizing the data information related to the passenger's cloud account in the vehicle owner's cloud account.

[0051] In this example, the verification information used to log in to the vehicle owner's cloud account is first identified through the vehicle owner's cloud account management module. If the identification is successful, the vehicle owner's cloud account is logged in, and the data information related to the passenger's cloud account in the vehicle owner's cloud account is synchronized. Then, the login information used to log in to the passenger's cloud account is obtained, and the login information is verified through the passenger's cloud account management module. This achieves a quick login with seamless switching after a single login, ensuring the uniformity of vehicle owner's cloud account login and realizing a multi-user, multi-modal login mode. It is a brand-new method for managing multiple accounts in vehicle devices.

[0052] The verification information includes at least one of the following: facial recognition information, voiceprint feature information, fingerprint information, and username information that represents the vehicle owner's identity.

[0053] This example does not restrict the specific form of the verification information. The verification information can be facial recognition information, voiceprint feature information, fingerprint information, or username information, as long as it can represent the vehicle owner's identity information. The diversity of verification information meets the needs of different users and improves the user experience.

[0054] This application's third embodiment is based on the solutions of embodiments one and two. Optionally, the control method for the vehicle-mounted device further includes the following steps: during the co-pilot mode activation period, if the user adjusts the vehicle-mounted device, the user receives the adjusted state variables of the vehicle-mounted device related to the sub-control module; the user stores the adjusted state variables of the vehicle-mounted device related to the sub-control module locally; and the user sends the adjusted state variables of the vehicle-mounted device related to the sub-control module to the co-pilot cloud account management module.

[0055] In this example, during the co-pilot mode activation period, if the user adjusts the in-vehicle equipment, the system receives the adjusted status variables of the in-vehicle equipment related to the sub-control module and stores them locally. This allows the adjusted status variables to be retrieved directly from local storage during co-pilot mode, enabling multiple sub-control modules to control the in-vehicle equipment using the adjusted status variables, thus improving control efficiency. Furthermore, the co-pilot control module also sends the adjusted status variables of the in-vehicle equipment related to the sub-control module to the co-pilot cloud account management module.

[0056] Optionally, in one embodiment of this application, the co-pilot cloud account management module receives the adjusted status variables of the vehicle-mounted devices related to the sub-control module; the co-pilot cloud account management module updates the status variables of the vehicle-mounted devices related to each sub-control module stored in the historical status variables through cloud synchronization based on the adjusted status variables of the vehicle-mounted devices related to the sub-control module.

[0057] In this example, the co-driver cloud account management module receives the adjusted status variables of the in-vehicle devices related to the sub-control module. The co-driver cloud account management module then performs cloud synchronization updates on the status variables of the in-vehicle devices related to each sub-control module stored in the historical status variables. In other words, the historical status variables of the co-driver cloud account management module store the latest status variables of the in-vehicle devices related to the sub-control modules. This allows the co-driver control module to send the latest status variables of the in-vehicle devices related to the sub-control modules to the co-driver control module the next time the co-driver mode is activated. This enables the co-driver control module to control the in-vehicle devices based on the latest status variables, reducing the need for repeated adjustments to the status variables of the in-vehicle devices and eliminating the need for the co-driver to manually adjust the status of the in-vehicle devices, thus improving the user experience.

[0058] Optionally, in one embodiment of this application, the control method of the vehicle device further includes the following steps: during the co-pilot mode activation period, the co-pilot control module sends a prohibition command to the vehicle owner cloud account management module. The prohibition command is used to prohibit the use of the control functions bound to the co-pilot area in the control functions corresponding to the vehicle owner cloud account.

[0059] In this example, the vehicle owner cloud account management module is bound to control functions related to the passenger seat area. In owner mode, the unified control functions corresponding to the vehicle owner cloud account are used to control the entire vehicle. However, during the passenger seat mode activation period, the passenger seat control module sends a prohibition command to the vehicle owner cloud account management module to prohibit the use of the control functions bound to the passenger seat area within the control functions corresponding to the vehicle owner cloud account. In other words, when passenger seat mode is activated, the unified control functions corresponding to the vehicle owner cloud account are no longer used to control the in-vehicle devices in the passenger seat area. Instead, the control functions corresponding to the passenger seat cloud account are used to control the in-vehicle devices in the passenger seat area. This makes the in-vehicle devices in the passenger seat area controlled by the passenger seat control module, adapting to the passenger's habits and preferences, and improving the management efficiency of the cloud account.

[0060] Furthermore, one or two specific examples are provided to illustrate the unified cloud account management system and the co-pilot cloud account management system in the embodiments of this application, as detailed below.

[0061] The first example uses a unified cloud account to control the vehicle's onboard devices, such as... Figure 2 As shown, Figure 2 This is a schematic diagram of a unified cloud account management and control system provided in an embodiment of this application. In this example, the unified cloud account management and control system for vehicles and information synchronization are implemented, including the unified cloud account authentication system for vehicles and its related functional binding. The unified cloud account authentication system for vehicles and its functional binding can be implemented through steps S201-S205.

[0062] Step S201: The user logs in to the unified cloud account by verifying the information. The vehicle unified cloud account management module identifies the validity of the vehicle owner's identity to verify the legal registration identity of the vehicle user. If the identification is successful, proceed to step S202; if the identification fails, log out of the unified cloud account and enter the vehicle's general control mode, i.e., the state without account management.

[0063] It should be noted that the verification information can be voiceprint features, facial recognition information, fingerprint information, username and password, or QR code scanning, etc. This example does not impose any restrictions, as long as it can represent the user's identity information.

[0064] Step S202: After successful recognition, the vehicle intelligent mode is activated. The vehicle unified cloud account management module sends the latest status variables of the vehicle equipment related to each sub-control module stored in the cloud during the previous vehicle intelligent mode to the vehicle intelligent control module. The vehicle intelligent control module receives the latest status variables of the vehicle equipment related to each sub-control module stored in the cloud during the intelligent mode from the vehicle unified cloud account management module.

[0065] It should be noted that in this example, the vehicle intelligent control module and the vehicle unified cloud account management module can communicate via a communication module. The access module can be configured by those skilled in the art as needed, as long as it ensures communication between the vehicle intelligent control module and the vehicle unified cloud account management module. In-vehicle equipment includes seats, footrests, ambient lighting throughout the vehicle, automatic air conditioning throughout the vehicle, and electric air vents throughout the vehicle.

[0066] Step S203: After activating the vehicle intelligent mode, the vehicle intelligent control module executes the latest status variables of the vehicle-mounted devices related to each sub-control module stored in the cloud under the vehicle intelligent mode, which are issued by the vehicle unified cloud account management module, and sends the relevant control execution instructions to each sub-control module in the vehicle intelligent control module.

[0067] Step S204: During the vehicle intelligent mode activation period, the user adjusts the status of the in-vehicle equipment through a switch or voice, that is, adjusts the status variables of the sub-control devices related to the in-vehicle equipment. The vehicle intelligent control module and the local storage module receive the latest status variables of the in-vehicle equipment related to each sub-control module. In other words, the local storage module stores the current status variables of the in-vehicle equipment related to each sub-control module locally and sends the latest status variables of the in-vehicle equipment related to each sub-control module to the vehicle unified cloud account management module.

[0068] Step S205: The vehicle unified cloud account management module receives the latest status variables of the vehicle-mounted devices related to each sub-control module sent by the vehicle intelligent control module, and updates the status variables of the vehicle-mounted devices related to each sub-control module stored in the historical status variables in the cloud.

[0069] In the second example, the vehicle's onboard devices are controlled via the co-pilot's cloud account, such as... Figure 3 As shown, Figure 3 This is a schematic diagram of a co-pilot cloud account management and control system provided in an embodiment of this application. Figure 3 This example provides a new method for managing passenger cloud accounts, distinguishing a dedicated passenger cloud account from the unified vehicle cloud account management system in the first example, and synchronizing the status variables of in-vehicle devices within the passenger cloud account management system. This example improves upon the unified vehicle cloud account management method, creating a separate passenger-specific cloud account system, thus providing an independent passenger cloud account system with related dedicated functional settings and management. The dedicated passenger cloud account authentication system and its functional binding can be implemented through steps S301-S305.

[0070] Step S301: The user logs into the co-driver cloud account using login information, and the co-driver cloud account management module verifies the validity of the co-driver's identity; alternatively, the user first logs into the owner cloud account using verification information. Specifically, the owner cloud account management module identifies the verification information used to log into the owner cloud account. If the identification is successful, the data information related to the co-driver cloud account in the owner cloud account is synchronized, and then the login information used to log into the co-driver cloud account is obtained. The co-driver cloud account management module verifies the validity of the co-driver's identity; if the verification is successful, proceed to step S302; if the verification fails, log out of the unified cloud account and enter the vehicle's general control mode, i.e., the state without account management.

[0071] It should be noted that login information can be voiceprint features, facial recognition information, fingerprint information, username and password, or QR code scanning, etc. This example does not impose any restrictions, as long as it can identify the passenger's identity information; verification information can be voiceprint features, facial recognition information, fingerprint information, username and password, or QR code scanning, etc. This example does not impose any restrictions, as long as it can identify the vehicle owner's identity information.

[0072] Step S302: After successful authentication, the co-pilot mode is activated. The co-pilot cloud account management module sends the latest status variables of the vehicle equipment related to each sub-control module stored in the cloud during the previous co-pilot mode to the co-pilot control module through the communication module. The co-pilot control module receives the latest status variables of the vehicle equipment related to each sub-control module stored in the cloud during the co-pilot mode from the co-pilot cloud account management module.

[0073] It should be noted that in this example, the co-pilot control module and the co-pilot cloud account management module can communicate with each other through a communication module. The access module can be configured by those skilled in the art as needed, as long as it can ensure that the co-pilot control module and the co-pilot cloud account management module can communicate.

[0074] Step S303: After activating the co-pilot mode, the co-pilot control module executes the latest status variables of the vehicle-mounted devices related to each sub-control module stored in the cloud under the co-pilot mode, which are issued by the co-pilot cloud account management module, and sends the relevant control execution instructions to each sub-control module in the co-pilot control module.

[0075] Step S304: During the co-pilot mode activation period, the user adjusts the status of the in-vehicle equipment via a switch or voice command, i.e., adjusts the status variables of the related sub-control devices. The co-pilot control module and the local storage module receive the adjusted status variables of the in-vehicle equipment related to each sub-control module. In other words, the local storage module stores the current status variables of the in-vehicle equipment related to each sub-control module locally, and the co-pilot control module sends the latest status variables of the in-vehicle equipment related to each sub-control module to the co-pilot cloud account management module. At the same time, the co-pilot control module sends a prohibition command to the co-pilot cloud account management module, prohibiting the use of the control functions bound to the co-pilot area in the control functions corresponding to the owner's cloud account.

[0076] Step S305: The co-pilot cloud account management module receives the latest status variables of the vehicle-mounted devices related to each sub-control module sent by the co-pilot control module, and updates the status variables of the vehicle-mounted devices related to each sub-control module stored in the historical status variables in the cloud.

[0077] The second example, building upon the unified in-vehicle account system authentication management and information synchronization of the first example, adds an independent authentication and management system for the co-pilot cloud account, assigning it exclusive function matching, status settings, and storage. This example, through the independent authentication and establishment of the co-pilot cloud account system, enhances the protection of user privacy regarding co-pilot area function control. By activating the co-pilot mode, it provides multi-user, multi-modal function control for the entire vehicle's cockpit system, representing a novel method for managing multiple accounts for in-vehicle devices. This example's method of controlling in-vehicle devices through the co-pilot cloud account ensures both the legitimacy of the vehicle owner's and co-pilot's registered accounts and the independence and privacy of the cockpit environment for multiple users simultaneously using functions. Upon successful login to the owner's cloud account, data related to the co-pilot cloud account is synchronized, ensuring the consistency of the owner's cloud account and enabling multi-user, multi-modal login modes. It also provides a one-time login, seamless switching for quick login, meeting the needs of multiple user function modes and states. Meanwhile, the status of the in-vehicle device follows the preferences and habits of the co-driver. The status variables of the in-vehicle device in the co-driver cloud account management module are adapted to the co-driver, eliminating the need for the co-driver to readjust the status of the in-vehicle device. This reduces the repetitive processing of status variables in traditional cloud account management and control functions, and improves the efficiency of account management.

[0078] Example 4

[0079] This application provides a control system for an in-vehicle device, such as... Figure 4 As shown, Figure 4This application provides a control system for an in-vehicle device. The control system 40 includes a co-pilot cloud account management module 401, a communication module 402, and a co-pilot control module 403. The co-pilot cloud account management module 401 verifies login information. If the verification is successful, the co-pilot mode is activated. The co-pilot cloud account management module 401 sends the status variables of the in-vehicle device in co-pilot mode to the co-pilot control module 403 through the communication module 402. The co-pilot control module 403 receives the status variables of the in-vehicle device in co-pilot mode sent by the co-pilot cloud account management module 401 and controls the in-vehicle device according to the status variables.

[0080] Optionally, in one embodiment of this application, the co-driver control module 403 includes multiple sub-control modules; each sub-control module in the co-driver control module 403 is used to control the vehicle-mounted equipment related to the sub-control module according to state variables, and the vehicle-mounted equipment includes at least one of the following: co-driver seat, co-driver footrest, co-driver area ambient lighting, co-driver area automatic air conditioning, and co-driver area electric air vent.

[0081] Optionally, in one embodiment of this application, the co-pilot cloud account management module 401 is used to verify the voiceprint feature information; if the voiceprint feature information matches the preset voiceprint feature information used for valid login of the co-pilot cloud account in the co-pilot cloud account management module, the verification is successful.

[0082] Optionally, in one embodiment of this application, the control system 40 of the vehicle-mounted device further includes a vehicle owner cloud account management module; the vehicle owner cloud account management module is used to identify verification information; if the identification is successful, the data information related to the passenger's cloud account in the vehicle owner cloud account is synchronized.

[0083] Optionally, in one embodiment of this application, the co-driver control module 403 is further configured to obtain the adjusted state variables of the vehicle-mounted equipment related to the sub-control module and store the adjusted state variables of the vehicle-mounted equipment related to the sub-control module locally; the co-driver control module 403 sends the adjusted state variables of the vehicle-mounted equipment related to the sub-control module to the co-driver cloud account management module 401 through the communication module 402.

[0084] Optionally, in one embodiment of this application, the verification information includes at least one of facial recognition information, voiceprint feature information, fingerprint information, and username information that represents the vehicle owner's identity information. Optionally, in one embodiment of this application, the control system 40 of the in-vehicle device further includes a local storage module. During the co-pilot mode activation period, if the user adjusts the in-vehicle device, the co-pilot control module 403 is further used to receive the adjusted state variables of the in-vehicle device related to the sub-control module; the local storage module is used to locally store the adjusted state variables of the in-vehicle device related to the sub-control module; and the co-pilot control module 403 sends the adjusted state variables of the in-vehicle device related to the sub-control module to the co-pilot cloud account management module 401.

[0085] Optionally, in one embodiment of this application, the co-pilot cloud account management module 401 receives the adjusted status variables of the vehicle-mounted devices related to the sub-control module; the co-pilot cloud account management module 401 is also used to perform cloud synchronization updates of the status variables of the vehicle-mounted devices related to each sub-control module stored in the historical status variables according to the adjusted status variables of the vehicle-mounted devices related to the sub-control module.

[0086] Optionally, in one embodiment of this application, during the co-pilot mode activation period, the co-pilot control module 403 sends a prohibition command to the vehicle owner cloud account management module through the communication module 402. The prohibition command is used to prohibit the use of the control functions bound to the co-pilot area in the control functions corresponding to the vehicle owner cloud account.

[0087] The control system of the vehicle-mounted device in this embodiment is used to implement the corresponding control methods of the vehicle-mounted device in the foregoing method embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here. Furthermore, the functional implementation of each module in the control system of the vehicle-mounted device in this embodiment can be referred to the description of the corresponding part in the foregoing method embodiments, which will also not be repeated here.

[0088] Example 5

[0089] Based on any of the vehicle-mounted device control methods described in Embodiments 1 to 3 above, this application provides an electronic device. It should be noted that the vehicle-mounted device control method of this embodiment can be executed by any suitable electronic device with data processing capabilities, including but not limited to: servers, mobile terminals (such as mobile phones, PADs, etc.), and PCs. Figure 5 As shown, Figure 5This is a structural diagram of an electronic device provided in an embodiment of this application. The specific embodiments of this application do not limit the specific implementation of the electronic device. The electronic device 50 may include: a processor 502, a communications interface 504, a memory 506, and a communication bus 508.

[0090] The processor 502, communication interface 504, and memory 506 communicate with each other via communication bus 508.

[0091] Communication interface 504 is used to communicate with other electronic devices or servers.

[0092] The processor 502 is used to execute the computer program 510, specifically the relevant steps in the above-described vehicle-mounted device control method embodiment.

[0093] Specifically, computer program 510 may include computer program code, which includes computer operation instructions.

[0094] The processor 502 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. The smart device includes one or more processors, which may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0095] Memory 506 is used to store computer program 510. Memory 506 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0096] The specific implementation of each step in computer program 510 can be found in the corresponding steps and units described in the above-described embodiments of the control method for vehicle-mounted equipment, and will not be repeated here. Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the devices and modules described above can be referred to the corresponding process descriptions in the aforementioned method embodiments, and will not be repeated here.

[0097] Example 6

[0098] Based on the control method of the vehicle-mounted device described in Embodiments 1 to 3 above, this application provides a computer storage medium storing a computer program, which, when executed by a processor, implements the control method of the vehicle-mounted device as described in Embodiments 1 to 3.

[0099] It should be noted that, depending on the implementation needs, the various components / steps described in the embodiments of this application can be broken down into more components / steps, or two or more components / steps or parts of the operation of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of this application.

[0100] The methods described in the embodiments of this application can be implemented in hardware, firmware, or as software or computer code that can be stored in a recording medium (such as CD ROM, RAM, floppy disk, hard disk, or magneto-optical disk), or as computer code downloaded over a network that is originally stored in a remote recording medium or a non-transitory machine-readable medium and will be stored in a local recording medium. Thus, the methods described herein can be stored on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware (such as an ASIC or FPGA) for such software processing. It is understood that the computer, processor, microprocessor controller, or programmable hardware includes storage components (e.g., RAM, ROM, flash memory, etc.) capable of storing or receiving software or computer code. When the software or computer code is accessed and executed by the computer, processor, or hardware, the control methods of the vehicle-mounted device described herein are implemented. Furthermore, when a general-purpose computer accesses code used to implement the control methods of the vehicle-mounted device shown herein, the execution of the code transforms the general-purpose computer into a dedicated computer for executing the control methods of the vehicle-mounted device shown herein.

[0101] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0102] Those skilled in the art will recognize that the units and method steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0103] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0104] The above embodiments are only used to illustrate the embodiments of this application, and are not intended to limit the embodiments of this application. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the embodiments of this application. Therefore, all equivalent technical solutions also fall within the scope of the embodiments of this application, and the patent protection scope of the embodiments of this application should be defined by the claims.

Claims

1. A control method for an on-board device, characterized in that, The method includes: Obtain login information used to log in to the co-pilot cloud account; The login information is verified through the co-pilot cloud account management module; If the verification is successful, the co-pilot mode is activated, and the co-pilot cloud account management module sends the status variables of the in-vehicle devices in the co-pilot mode, so that the co-pilot control module controls the in-vehicle devices according to the status variables. The co-pilot control module controls the in-vehicle devices according to the status variables, including: each sub-control module in the co-pilot control module controls the in-vehicle devices related to the sub-control module according to the status variables. During the co-pilot mode activation period, the co-pilot control module sends a prohibition command to the vehicle owner cloud account management module. The prohibition command is used to prohibit the use of the control functions bound to the co-pilot area in the control functions corresponding to the vehicle owner cloud account, so that the in-vehicle equipment in the co-pilot area is controlled by the co-pilot control module. During the co-pilot mode activation period, if the user adjusts the in-vehicle device, the system receives the adjusted status variables of the in-vehicle device related to the sub-control module; stores the adjusted status variables of the in-vehicle device related to the sub-control module locally so that the sub-control module can directly retrieve the adjusted status variables of the in-vehicle device from the local storage during this co-pilot mode; and sends the adjusted status variables of the in-vehicle device related to the sub-control module to the co-pilot cloud account management module.

2. The method according to claim 1, characterized in that, The in-vehicle equipment includes at least one of the following: passenger seat, passenger footrest, passenger area ambient lighting, passenger area automatic air conditioning, and passenger area electric air vents.

3. The method according to claim 1, characterized in that, The login information includes voiceprint feature information, which is verified through the co-pilot cloud account management module, including: Voiceprint feature information is verified through the Co-pilot Cloud Account Management module; If the voiceprint feature information matches the preset voiceprint feature information used for valid login to the Co-pilot Cloud account in the Co-pilot Cloud account management module, then the verification is successful.

4. The method according to claim 1, characterized in that, Before obtaining the login information used to log in to the co-pilot cloud account, the method includes: Obtain verification information used to log in to the vehicle owner's cloud account; The verification information is identified through the vehicle owner cloud account management module; If the identification is successful, the data information related to the co-driver's cloud account in the owner's cloud account will be synchronized.

5. The method according to claim 4, characterized in that, The verification information includes at least one of the following: facial recognition information, voiceprint feature information, fingerprint information, and username information, which represent the identity information of the vehicle owner.

6. The method according to claim 1, characterized in that, The method further includes: The co-pilot cloud account management module receives the adjusted status variables of the vehicle-mounted equipment related to the sub-control module; The co-pilot cloud account management module updates the status variables of the vehicle devices related to each sub-control module stored in the historical status variables through cloud synchronization based on the adjusted status variables of the vehicle devices related to the sub-control modules.

7. A control system for a vehicle-mounted device, characterized in that, The system includes a co-pilot cloud account management module, a communication module, and a co-pilot control module; The co-pilot cloud account management module is used to verify login information. If the verification is successful, the co-pilot mode is activated. The co-pilot cloud account management module sends the status variables of the in-vehicle devices in co-pilot mode to the co-pilot control module through the communication module. The co-pilot control module includes multiple sub-control modules. Each sub-control module in the co-pilot control module is used to control the in-vehicle devices related to the sub-control module according to the status variables. The co-pilot control module receives the status variables of the in-vehicle device in co-pilot mode sent by the co-pilot cloud account management module, and the co-pilot control module is used to control the in-vehicle device according to the status variables; During the co-pilot mode activation period, the co-pilot control module sends a prohibition command to the vehicle owner cloud account management module. The prohibition command is used to prohibit the use of the control functions bound to the co-pilot area in the control functions corresponding to the vehicle owner cloud account, so that the in-vehicle equipment in the co-pilot area is controlled by the co-pilot control module. The co-pilot control module is also used to acquire the adjusted status variables of the vehicle equipment related to the sub-control module, and store the adjusted status variables of the vehicle equipment related to the sub-control module locally, so that in this co-pilot mode, the sub-control module can directly retrieve the adjusted status variables of the vehicle equipment from the local storage; the co-pilot control module sends the adjusted status variables of the vehicle equipment related to the sub-control module to the co-pilot cloud account management module through the communication module.

8. The system according to claim 7, characterized in that, The in-vehicle equipment includes at least one of the following: passenger seat, passenger footrest, passenger area ambient lighting, passenger area automatic air conditioning, and passenger area electric air vents.

9. The system according to claim 7, characterized in that, The system also includes a vehicle owner cloud account management module; The vehicle owner cloud account management module is used to identify verification information; If the identification is successful, the data information related to the co-driver's cloud account in the owner's cloud account will be synchronized.

10. The system according to claim 7, characterized in that, The co-pilot cloud account management module receives the adjusted status variables of the vehicle-mounted equipment related to the sub-control module; The co-pilot cloud account management module is also used to update the status variables of the vehicle devices related to each sub-control module stored in the historical status variables through cloud synchronization, based on the adjusted status variables of the vehicle devices related to the sub-control module.

11. An electronic device, characterized in that, include: The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus. The memory is used to store at least one executable instruction, which causes the processor to perform the operation corresponding to the control method of the vehicle-mounted device as described in any one of claims 1-6.

12. A computer storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the control method of the vehicle-mounted device as described in any one of claims 1-6.

Images