A method, apparatus and equipment for synchronizing vehicle usage habit data
By storing the original vehicle usage habit data on the cloud server and confirming the data writing to the execution controller, the vehicle-side account identifier is switched uniformly, which solves the problem of loss and inconsistency of vehicle usage habit data when switching accounts, and achieves complete data synchronization and consistency.
Patent Information
- Application Number
- CN202611277858.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-21
- Publication Date
- 2026-11-17
AI Technical Summary
Due to limited storage space in the vehicle's actuator controller and insufficient number of vehicle-side account identifiers, user habit data is easily lost or inconsistent when switching accounts, affecting data integrity and vehicle functional status.
After the original driving habit data is associated and stored on the cloud server, the target driving habit data is retrieved and distributed. After all execution controllers have completed the data writing, the accounts are switched uniformly to ensure the consistency of data synchronization and account switching.
This reduces the possibility of vehicle usage data being lost due to overwriting and improves the consistency of vehicle usage data synchronization and account switching among multiple execution controllers.
Smart Images

Figure CN123123364A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle networking technology, and in particular to a method, apparatus and device for synchronizing vehicle usage habit data. Background Technology
[0002] With the increasing personalization features of intelligent connected vehicles, vehicles can save usage habit data such as function on / off status and operating modes according to different users' account. In related technologies, vehicles typically have multiple actuator controllers that store usage habit data for corresponding vehicle functions, and distinguish the data of different users through vehicle account identifiers.
[0003] However, due to storage space limitations on the actuator controllers, the number of vehicle-side account identifiers that can be configured is typically limited. When the number of cloud-based vehicle accounts exceeds the number of vehicle-side account identifiers, it is necessary to delete or overwrite the data corresponding to existing vehicle-side account identifiers. Simultaneously, vehicle usage habit data is stored across multiple actuator controllers, and the data upload, download, and write processes may be affected by communication delays, network interruptions, and differences in controller processing progress. When reusing vehicle-side account identifiers or switching vehicle accounts, issues such as incomplete saving of original user data leading to overwriting, write failures on some controllers, and inconsistencies in account data used by different controllers can easily arise, affecting the integrity of vehicle usage habit data and the vehicle's functional status after account switching. Summary of the Invention
[0004] The purpose of this application is to provide a method, apparatus, and device for synchronizing vehicle usage habit data, so as to solve the problems of easy loss of vehicle usage habit data and inconsistency in switching accounts of multiple execution terminal controllers during the reuse of vehicle-side account identifiers.
[0005] In a first aspect, embodiments of this application provide a method for synchronizing vehicle usage habit data. The method includes: responding to a login operation of a target cloud-based vehicle usage account; when the target cloud-based vehicle usage account is not bound to a vehicle-side account identifier and a preset number of vehicle-side account identifiers are all bound; determining a vehicle-side account identifier to be reused from the already bound vehicle-side account identifiers, and determining the original cloud-based vehicle usage account currently bound to the vehicle-side account identifier to be reused; acquiring the original vehicle usage habit data stored under the vehicle-side account identifier to be reused by each execution controller in the vehicle, and uploading the original vehicle usage habit data to a cloud server so that the cloud server associates and stores the original vehicle usage habit data with the original cloud-based vehicle usage account; after receiving data storage confirmation information returned by the cloud server; acquiring the target vehicle usage habit data corresponding to the target cloud-based vehicle usage account, and sending the target vehicle usage habit data and the vehicle-side account identifier to be reused to the corresponding target execution controllers respectively; and receiving data writing results returned by each target execution controller. Once it is confirmed that all data writing results meet the account switching conditions, the vehicle terminal account identifier to be reused is bound to the target cloud vehicle account, and an account activation command is sent to each target execution controller so that each target execution controller switches the vehicle terminal account identifier to be reused to the currently used vehicle terminal account identifier.
[0006] The method for synchronizing vehicle usage habit data provided in this application, when all vehicle-side account identifiers are in a bound state, first determines the vehicle-side account identifier to be reused and its currently bound original cloud-based vehicle usage account, and obtains the original vehicle usage habit data stored under the vehicle-side account identifier to be reused by each execution controller. Only after the cloud server completes the associated storage of the original vehicle usage habit data is the target vehicle usage habit data corresponding to the target cloud-based vehicle usage account obtained and distributed. This allows the data corresponding to the original cloud-based vehicle usage account to be saved before the vehicle-side account identifier is reused, reducing the possibility of loss of the original vehicle usage habit data due to overwriting. At the same time, after the target vehicle usage habit data is distributed, the data writing results returned by each target execution controller are obtained. Only when all data writing results meet the account switching conditions is the binding relationship of the vehicle-side account identifier to be reused updated and an account activation command sent. This avoids switching accounts before some target execution controllers have completed data writing, and ensures that each target execution controller uniformly activates the vehicle-side account identifier to be reused after completing the target vehicle usage habit data writing, improving the consistency of vehicle usage habit data synchronization and account switching among multiple execution controllers.
[0007] One possible implementation involves determining the vehicle-side account identifier to be reused from the already bound vehicle-side account identifiers, including: obtaining the account activation status corresponding to each vehicle-side account identifier; determining the vehicle-side account identifier to be reused from vehicle-side account identifiers that are not currently activated; generating an account reuse task based on the vehicle-side account identifier to be reused, the original cloud-based vehicle-use account, and the target cloud-based vehicle-use account; assigning an account reuse task identifier to the account reuse task; and setting the vehicle-side account identifier to be reused to a pending reuse status.
[0008] One possible implementation involves acquiring the original vehicle usage habit data stored by each execution controller in the vehicle under the vehicle-side account identifier to be reused, including: sending an account reuse preparation instruction to each execution controller. The account reuse preparation instruction includes an account reuse task identifier and the vehicle-side account identifier to be reused. The implementation also involves receiving data collection responses carrying the account reuse task identifier from each execution controller. The data collection response is the corresponding execution controller's response to the account reuse preparation instruction, setting the storage area corresponding to the vehicle-side account identifier to be reused to a locked state, reading the original vehicle usage habit data from the storage area, and then returning the data. Finally, a snapshot of the original vehicle usage habit data is generated based on the original vehicle usage habit data in each data collection response.
[0009] One possible implementation involves uploading the original car usage habit data to a cloud server, including: sending a data synchronization request to the cloud server carrying an account reuse task identifier, the original cloud-based car usage account, and a snapshot of the original car usage habit data. The cloud server associates the snapshot of the original car usage habit data with the original cloud-based car usage account and returns data storage confirmation information carrying the account reuse task identifier after completing the storage of the snapshot. If the account reuse task identifier in the data storage confirmation information matches the current account reuse task, and the data storage confirmation information indicates that the storage of the original car usage habit data snapshot is complete, the processing stage of the account reuse task is updated to the data writing stage.
[0010] One possible implementation involves sending the target vehicle usage habit data and the vehicle-end account identifier to be reused to the corresponding target execution controllers. This includes: determining the target execution controller corresponding to each piece of data based on the vehicle function corresponding to each piece of data in the target vehicle usage habit data; sending a data pre-write instruction to each target execution controller; the data pre-write instruction including the account reuse task identifier, the vehicle-end account identifier to be reused, and the corresponding target vehicle usage habit data; and each target execution controller responding to the data pre-write instruction by writing the received target vehicle usage habit data to the storage area corresponding to the vehicle-end account identifier to be reused, keeping the written target vehicle usage habit data in an inactive state, and returning a data writing result carrying the account reuse task identifier.
[0011] One possible implementation, the method for synchronizing vehicle usage habit data provided in this application embodiment, further includes: after receiving the data writing results returned by each target execution terminal controller, reading the written data corresponding to the target vehicle usage habit data stored in the corresponding storage area of each target execution terminal controller. The written data is compared with the received target vehicle usage habit data to obtain the data writing results. The data writing results include one or more of the following: account reuse task identifier, data writing status, and corresponding comparison results. Based on the account reuse task identifier in each data writing result, the account reuse task corresponding to each data writing result is determined. If it is determined that each data writing result corresponds to the current account reuse task, each data writing status indicates that data writing is complete, and each comparison result indicates that the written data is consistent with the corresponding target vehicle usage habit data, then it is determined that each data writing result meets the account switching conditions.
[0012] One possible implementation involves sending account activation instructions to each target execution controller, including: if all data write results meet the account switching conditions, setting the binding relationship between the vehicle-end account identifier to be reused and the target cloud-based vehicle account to a pending activation state; determining the target activation time corresponding to the vehicle-end account identifier to be reused, and generating an account activation instruction carrying the account reuse task identifier and the target activation time; sending the account activation instruction to each target execution controller, so that if the account reuse task identifier matches successfully, each target execution controller switches the vehicle-end account identifier to be reused to the currently used vehicle-end account identifier at the corresponding target activation time and returns the account activation result; if all account activation results are successful, removing the binding relationship between the vehicle-end account identifier to be reused and the original cloud-based vehicle account, updating the binding relationship between the vehicle-end account identifier to be reused and the target cloud-based vehicle account to an active state, and updating the account reuse task to a completed state.
[0013] One possible implementation, the method for synchronizing vehicle usage habit data provided in this application embodiment, further includes: generating an account reuse rollback instruction carrying an account reuse task identifier and a snapshot of the original vehicle usage habit data when it is determined that there is a data writing result that does not meet the account switching conditions, or an account activation result that failed. The account reuse rollback instruction is sent to the target execution controller that has already written the target vehicle usage habit data, so that the corresponding target execution controller restores the original vehicle usage habit data under the vehicle-side account identifier to be reused based on the original vehicle usage habit data snapshot. The binding relationship between the vehicle-side account identifier to be reused and the original cloud-based vehicle usage account is maintained, the binding relationship between the vehicle-side account identifier to be reused and the target cloud-based vehicle usage account that is in a pending state is deleted, and the account reuse task is updated to a rollback completed state.
[0014] Secondly, embodiments of this application provide a device for synchronizing vehicle usage habit data, the device comprising: a determining module, an acquiring module, a sending module, and a binding module.
[0015] The determination module is used to respond to the login operation of the target cloud-based car-hailing account. When the target cloud-based car-hailing account is not bound to a vehicle-end account identifier and a preset number of vehicle-end account identifiers are all bound, it determines the vehicle-end account identifier to be reused from the already bound vehicle-end account identifiers, and determines the original cloud-based car-hailing account currently bound to the vehicle-end account identifier to be reused.
[0016] The acquisition module is used to acquire the original vehicle usage habit data stored by each actuator controller in the vehicle under the account identifier of the vehicle to be reused, and to upload the original vehicle usage habit data to the cloud server so that the cloud server can associate and store the original vehicle usage habit data with the original cloud vehicle account.
[0017] The sending module is used to obtain the target car usage habit data corresponding to the target cloud car use account after receiving the data storage confirmation information returned by the cloud server, and to send the target car usage habit data and the car use terminal account identifier to the corresponding target execution terminal controller, and to receive the data writing results returned by each target execution terminal controller.
[0018] The binding module is used to bind the vehicle-end account identifier to be reused with the target cloud-based vehicle account when all data writing results meet the account switching conditions, and to send account activation instructions to each target execution controller so that each target execution controller switches the vehicle-end account identifier to be reused with the currently used vehicle-end account identifier.
[0019] Thirdly, embodiments of this application provide a device for synchronizing vehicle usage data. This device has the function of implementing the method for synchronizing vehicle usage data according to the first aspect or any possible implementation of the first aspect. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function.
[0020] Fourthly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a computer, enable the computer to perform the method for synchronizing vehicle usage data according to the first aspect or any possible implementation thereof.
[0021] Fifthly, embodiments of this application provide a computer program product containing instructions that, when run on a computer, enable the computer to execute the method for synchronizing vehicle usage data as described in the first aspect or any possible implementation thereof.
[0022] The technical effects of any of the design methods in aspects two through five can be found in aspect one or in different possible implementations of aspect one, and will not be repeated here. Attached Figure Description
[0023] To more clearly illustrate the technical solutions in the specific embodiments of this application or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0024] Figure 1 A system architecture diagram of a vehicle usage habit data synchronization system provided in this application embodiment; Figure 2 A flowchart illustrating a method for synchronizing vehicle usage habit data, as provided in this application embodiment; Figure 3 A schematic diagram of a device for synchronizing vehicle usage habit data provided in an embodiment of this application; Figure 4 Another system architecture diagram of a vehicle usage habit data synchronization system provided in this application embodiment. Detailed Implementation
[0025] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of 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. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.
[0026] Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.
[0027] In related technologies, vehicles typically configure corresponding vehicle-side account identifiers for each user account. Each execution controller stores user habit data such as function on / off status and operating mode based on the vehicle-side account identifier. Due to the limited storage space of the execution controller, the number of vehicle-side account identifiers that a vehicle can set is usually less than the number of cloud-based user accounts that may log in to the vehicle. For example, all vehicle-side account identifiers configured in the vehicle are already bound to existing cloud-based user accounts. When a new cloud-based user account logs in to the vehicle, one of the already used vehicle-side account identifiers needs to be released. However, the user habit data of the original cloud-based user accounts is scattered across multiple execution controllers. If a vehicle-side account identifier is reused directly before the original user habit data has been completely uploaded to the cloud server, the original user habit data may be overwritten or lost. At the same time, the data writing progress of different execution controllers may be different. If some execution controllers have not completed writing the target user habit data before switching accounts, it may also cause different execution controllers to use the data corresponding to the original cloud-based user account and the target cloud-based user account respectively, affecting the consistency of the vehicle's functional status after the account switch.
[0028] Based on this, this application provides a method for synchronizing vehicle usage habit data. The method includes: responding to a login operation of a target cloud-based vehicle usage account; when the target cloud-based vehicle usage account is not bound to a vehicle-side account identifier and a preset number of vehicle-side account identifiers are all bound; determining the vehicle-side account identifier to be reused from the already bound vehicle-side account identifiers, and determining the original cloud-based vehicle usage account currently bound to the vehicle-side account identifier to be reused; acquiring the original vehicle usage habit data stored under the vehicle-side account identifier to be reused by each execution controller in the vehicle, and uploading the original vehicle usage habit data to a cloud server so that the cloud server associates the original vehicle usage habit data with the original cloud-based vehicle usage account; after receiving data storage confirmation information returned by the cloud server; acquiring the target vehicle usage habit data corresponding to the target cloud-based vehicle usage account; sending the target vehicle usage habit data and the vehicle-side account identifier to be reused to the corresponding target execution controllers respectively; and receiving the data writing results returned by each target execution controller. Once it is confirmed that all data writing results meet the account switching conditions, the vehicle terminal account identifier to be reused is bound to the target cloud vehicle account, and an account activation command is sent to each target execution controller so that each target execution controller switches the vehicle terminal account identifier to be reused to the currently used vehicle terminal account identifier.
[0029] The method for synchronizing vehicle usage habit data provided in this application, when all vehicle-side account identifiers are in a bound state, first determines the vehicle-side account identifier to be reused and its currently bound original cloud-based vehicle usage account, and obtains the original vehicle usage habit data stored under the vehicle-side account identifier to be reused by each execution controller. Only after the cloud server completes the associated storage of the original vehicle usage habit data is the target vehicle usage habit data corresponding to the target cloud-based vehicle usage account obtained and distributed. This allows the data corresponding to the original cloud-based vehicle usage account to be saved before the vehicle-side account identifier is reused, reducing the possibility of loss of the original vehicle usage habit data due to overwriting. At the same time, after the target vehicle usage habit data is distributed, the data writing results returned by each target execution controller are obtained. Only when all data writing results meet the account switching conditions is the binding relationship of the vehicle-side account identifier to be reused updated and an account activation command sent. This avoids switching accounts before some target execution controllers have completed data writing, and ensures that each target execution controller uniformly activates the vehicle-side account identifier to be reused after completing the target vehicle usage habit data writing, improving the consistency of vehicle usage habit data synchronization and account switching among multiple execution controllers.
[0030] The methods provided in the embodiments of this application will now be described in conjunction with the specific accompanying drawings.
[0031] On the one hand, embodiments of this application provide a system for synchronizing vehicle usage habit data. For example... Figure 1 As shown, the vehicle usage habit data synchronization system 100 may include: a vehicle-side controller 101, multiple execution-side controllers 102, and a cloud 103.
[0032] The vehicle-side controller 101 can be used to manage vehicle user accounts, establish the correspondence between cloud-based user accounts and vehicle-side account identifiers, and transmit vehicle usage habit data between the various execution-side controllers 102 and the cloud 103. For example, the vehicle-side controller 101 can be a controller in an in-vehicle infotainment system. The vehicle-side controller 101 communicates with the various execution-side controllers 102 via a controller area network or in-vehicle Ethernet, and communicates with the cloud 103 via a wireless communication network.
[0033] Each actuator controller 102 can correspond to different control functions in the vehicle. It is used to store or read corresponding vehicle usage data based on the vehicle account identifier, and to execute corresponding vehicle function control based on the read vehicle usage data. The vehicle usage data is used to represent the user's personalized settings for vehicle functions, such as the on / off status, working mode, and setting parameters of vehicle functions.
[0034] Cloud 103 can be used to manage various cloud-based vehicle accounts and associate and store the vehicle usage data uploaded by different vehicles with the corresponding cloud-based vehicle accounts. Cloud 103 can also send the vehicle usage data stored under the corresponding cloud-based vehicle account to the vehicle controller 101 according to the data request sent by the vehicle controller 101, so as to support the synchronization of vehicle usage data between the vehicle and Cloud 103.
[0035] It should be noted that, Figure 1 The vehicle usage habit data synchronization system 100 shown is merely an example of a usage scenario of the method provided in the embodiments of this application, and is not intended to limit the scenario of the method provided in the embodiments of this application.
[0036] On the one hand, embodiments of this application provide a method for synchronizing vehicle usage habit data, which can be achieved by... Figure 1 The system 100, which synchronizes the vehicle usage habit data shown, is executed. For example... Figure 2 As shown, the method may include the following steps.
[0037] S201, in response to the login operation of the target cloud-based car-hailing account, if the target cloud-based car-hailing account is not bound to a vehicle-end account identifier and all of the preset number of vehicle-end account identifiers are in a bound state, determine the vehicle-end account identifier to be reused from the already bound vehicle-end account identifiers, and determine the original cloud-based car-hailing account currently bound to the vehicle-end account identifier to be reused.
[0038] Among them, the target cloud car account can be the cloud car account of the user's currently logged-in vehicle.
[0039] The vehicle-side account identifier can be a pre-configured identifier locally on the vehicle, used to distinguish different users. Each actuator controller can allocate corresponding storage areas according to the vehicle-side account identifier, and store the different users' vehicle usage habit data in the corresponding storage areas. The number of vehicle-side account identifiers can be pre-set according to the storage space of each actuator controller, and its number is usually less than the number of cloud-based vehicle accounts that can log in to the vehicle.
[0040] The vehicle-end account identifier to be reused refers to a vehicle-end account identifier that is already bound to a cloud-based vehicle-use account, but needs to be reassigned to the target cloud-based vehicle-use account during the current account switching process. The original cloud-based vehicle-use account refers to the cloud-based vehicle-use account that the vehicle-end account identifier to be reused was bound to before it was reused.
[0041] Specifically, the user logs into the target cloud user account through the vehicle-side interface. After receiving the login request from the target cloud user account, the vehicle controller can send the login request to the cloud server for account verification. After the account verification is successful on the cloud server, the vehicle controller obtains the unique identification information of the target cloud user account. The vehicle controller queries the account binding relationships stored locally in the vehicle based on the unique identification information. If it is determined that the target cloud user account is not bound to a vehicle-side account identifier and that a preset number of vehicle-side account identifiers are all bound, the vehicle controller determines the vehicle-side account identifier to be reused from the already bound vehicle-side account identifiers, as well as the original cloud user account currently bound to the vehicle-side account identifier to be reused.
[0042] It should be noted that the login operation can be the user's first login to the target cloud-based car-hailing account, or the user's switch from another cloud-based car-hailing account to the target cloud-based car-hailing account.
[0043] One possible implementation involves determining the vehicle-side account identifier to be reused from the already bound vehicle-side account identifiers, including: obtaining the account activation status corresponding to each vehicle-side account identifier; determining the vehicle-side account identifier to be reused from vehicle-side account identifiers that are not currently activated; generating an account reuse task based on the vehicle-side account identifier to be reused, the original cloud-based vehicle-use account, and the target cloud-based vehicle-use account; assigning an account reuse task identifier to the account reuse task; and setting the vehicle-side account identifier to be reused to a pending reuse status.
[0044] The account activation status indicates whether the corresponding vehicle-side account identifier is currently being used by the vehicle. A vehicle-side account identifier that is currently active can be used by each execution controller when reading vehicle usage data. A vehicle-side account identifier that is not currently active, although bound to a cloud-based vehicle account, is not currently being used by any execution controller to control vehicle functions.
[0045] The account reuse task records the process of transferring the vehicle-side account identifier to be reused from the original cloud-based vehicle-use account to the target cloud-based vehicle-use account. The account reuse task identifier distinguishes account reuse tasks initiated at different times, enabling the vehicle-side controller to identify the account reuse task corresponding to each response message. The "pending reuse" status indicates that the corresponding vehicle-side account identifier has been occupied by the current account reuse task, but a valid binding relationship has not yet been established with the target cloud-based vehicle-use account.
[0046] Specifically, upon receiving a login request from a target cloud-based vehicle account, the vehicle controller can retrieve the unique identification information corresponding to that cloud-based vehicle account from the cloud server and query the account binding relationships stored locally in the vehicle. If the unique identification information corresponding to the target cloud-based vehicle account does not exist in the account binding relationships, and all vehicle-side account identifiers are already bound to cloud-based vehicle accounts, it can be determined that the already bound vehicle-side account identifiers need to be reused.
[0047] Furthermore, the vehicle-side controller can also read the account activation status corresponding to each vehicle-side account identifier and exclude currently used vehicle-side account identifiers. If multiple vehicle-side account identifiers are not currently active, the vehicle-side controller can display the cloud-based vehicle-use accounts currently bound to each vehicle-side account identifier in the account management interface and prompt the user to select the cloud-based vehicle-use account to be unbound. The vehicle-side controller can then identify the vehicle-side account identifier bound to the cloud-based vehicle-use account selected by the user as the vehicle-side account identifier to be reused.
[0048] For example, the vehicle is pre-configured with a first vehicle-side account identifier, a second vehicle-side account identifier, and a third vehicle-side account identifier, all of which are already bound to a cloud-based vehicle user account. The second vehicle-side account identifier is currently active. When a new target cloud-based vehicle user account logs into the vehicle, the vehicle controller can determine the vehicle-side account identifier to be reused from the first and third vehicle-side account identifiers. If the user chooses to delete the cloud-based vehicle user account currently bound to the first vehicle-side account identifier, the first vehicle-side account identifier can be identified as the vehicle-side account identifier to be reused, and an account reuse task can be generated based on the first vehicle-side account identifier, the original cloud-based vehicle user account currently bound to the first vehicle-side account identifier, and the target cloud-based vehicle user account.
[0049] S202, obtain the original vehicle usage habit data stored under the vehicle-end account identifier of each actuator controller in the vehicle, and upload the original vehicle usage habit data to the cloud server so that the cloud server associates and stores the original vehicle usage habit data with the original cloud vehicle account.
[0050] Among them, the original vehicle usage habit data refers to the vehicle usage habit data belonging to the original cloud-based vehicle usage account stored in the storage area corresponding to the account identifier of the vehicle to be reused by each execution terminal controller.
[0051] Specifically, before reusing the vehicle-side account identifier to be reused, the vehicle-side controller first obtains the original driving habit data currently stored in each execution controller, and then uploads the latest driving habit data modified by the user to the original cloud-based driving account, so as to avoid missing the updated data that has not yet been uploaded locally by only saving the original data in the cloud server.
[0052] One possible implementation involves acquiring the original vehicle usage habit data stored by each execution controller in the vehicle under the vehicle-side account identifier to be reused, including: sending an account reuse preparation instruction to each execution controller. The account reuse preparation instruction includes an account reuse task identifier and the vehicle-side account identifier to be reused. The implementation also involves receiving data collection responses carrying the account reuse task identifiers from each execution controller. The data collection response is the corresponding execution controller's response to the account reuse preparation instruction, setting the storage area corresponding to the vehicle-side account identifier to be reused to a locked state, reading the original vehicle usage habit data from the storage area, and then returning the data. Finally, a snapshot of the original vehicle usage habit data is generated based on the original vehicle usage habit data in each data collection response.
[0053] Specifically, the vehicle-side controller can send account reuse preparation instructions to each execution-side controller via the controller area network (CLAN) or the vehicle Ethernet, instructing the corresponding execution-side controller to prepare the original driving habit data for the current account reuse task. Upon receiving the account reuse preparation instruction, the execution-side controller locates the corresponding storage area based on the vehicle-side account identifier to be reused, and locks that storage area to prevent the original driving habit data corresponding to the vehicle-side account identifier from being overwritten or modified during data collection. It then reads the stored original driving habit data and sends the read original driving habit data, the corresponding account reuse task identifier, and the data collection status to the vehicle-side controller. After receiving the original vehicle usage habit data, the corresponding account reuse task identifier, and the data collection status from the execution controller, the vehicle controller excludes data collection responses belonging to historical account reuse tasks based on the account reuse task identifier. After receiving the data collection responses returned by each execution controller for the current account reuse task, the vehicle controller can summarize the collected original vehicle usage habit data according to the vehicle functions corresponding to each execution controller to obtain a snapshot of the original vehicle usage habit data.
[0054] For example, after a user changes the on / off status or operating mode of a vehicle function, the corresponding actuator controller can first store the changed data in the storage area corresponding to the vehicle account identifier to be reused. When it is determined that the vehicle account identifier needs to be reused, the vehicle controller can read the latest on / off status and operating mode from each actuator controller, and summarize the read data into a snapshot of the original driving habit data.
[0055] One possible implementation involves uploading the original car usage habit data to a cloud server, including: sending a data synchronization request to the cloud server carrying an account reuse task identifier, the original cloud-based car usage account, and a snapshot of the original car usage habit data. The cloud server associates the snapshot of the original car usage habit data with the original cloud-based car usage account and returns data storage confirmation information carrying the account reuse task identifier after completing the storage of the snapshot. If the account reuse task identifier in the data storage confirmation information matches the current account reuse task, and the data storage confirmation information indicates that the storage of the original car usage habit data snapshot is complete, the processing stage of the account reuse task is updated to the data writing stage.
[0056] Specifically, after the vehicle-side controller generates a snapshot of the original driving habit data, it encapsulates the account reuse task identifier corresponding to the current account reuse task, the original cloud-based vehicle account currently bound to the vehicle-side account to be reused, and the original driving habit data snapshot into a data synchronization request, and sends the data synchronization request to the cloud server. Upon receiving the data synchronization request, the cloud server determines the cloud storage space corresponding to the original cloud-based vehicle account based on the original cloud-based vehicle account in the data synchronization request, and stores the original driving habit data snapshot in the determined cloud storage space, thereby establishing a correspondence between the latest original driving habit data collected locally by the vehicle and the original cloud-based vehicle account.
[0057] After storing the original driving habit data snapshot, the cloud server generates data storage confirmation information based on the account reuse task identifier carried in this data synchronization request, and returns the data storage confirmation information to the vehicle controller. By including the account reuse task identifier in the data storage confirmation information, the vehicle controller can associate the data storage confirmation information returned by the cloud server with the currently executed account reuse task, avoiding the use of the storage results corresponding to historical account reuse tasks as the storage results of the current account reuse task.
[0058] After receiving the data storage confirmation information, the vehicle-side controller matches the account reuse task identifier in the confirmation information with the account reuse task identifier of the current account reuse task, and determines the storage status of the original driving habit data snapshot in the cloud server based on the data storage confirmation information. If the account reuse task identifier matches and the original driving habit data snapshot has been stored, the vehicle-side controller updates the account reuse task from the data upload stage to the data write stage, allowing the driving habit data corresponding to the target cloud driving account to continue being written to the storage area corresponding to the vehicle-side account identifier to be reused. If the account reuse task identifier does not match, or if the data storage confirmation information indicates that the original driving habit data snapshot has not been stored, the vehicle-side controller maintains the binding relationship between the vehicle-side account identifier to be reused and the original cloud driving account, and does not enter the data write stage.
[0059] For example, the vehicle controller summarizes the vehicle function switch status and operating mode corresponding to the original cloud-based vehicle account into a snapshot of the original vehicle usage data and uploads it to the cloud server. After the cloud server stores the vehicle function switch status and operating mode in the cloud storage space corresponding to the original cloud-based vehicle account, it returns a storage success message to the vehicle controller. Only after the vehicle controller confirms that this information corresponds to the current account reuse task will it continue to obtain the target vehicle usage data corresponding to the target cloud-based vehicle account.
[0060] S203, after receiving the data storage confirmation information returned by the cloud server, obtains the target car usage habit data corresponding to the target cloud car usage account, and sends the target car usage habit data and the car usage terminal account identifier to the corresponding target execution terminal controller, and receives the data writing results returned by each target execution terminal controller.
[0061] Specifically, after confirming that the original driving habit data has been associated and stored with the original cloud-based driving account, the vehicle controller can send a data retrieval request to the cloud server for the target cloud-based driving account. The cloud server, based on the target cloud-based driving account in the data retrieval request, queries the driving habit data associated with and stored with the target cloud-based driving account, and sends the retrieved driving habit data as the target driving habit data to the vehicle controller.
[0062] Since different data points in the target vehicle usage habit data can correspond to different vehicle functions, and each vehicle function can be controlled by a different execution controller, the vehicle-side controller can send each target vehicle usage habit data point to the corresponding target execution controller based on the vehicle function corresponding to that data point. After receiving the target vehicle usage habit data, the target execution controller can write the data to the storage area corresponding to the vehicle-side account identifier to be reused, and then feed back the data writing status to the vehicle-side controller.
[0063] One possible implementation involves sending the target vehicle usage habit data and the vehicle-end account identifier to be reused to the corresponding target execution controllers. This includes: determining the target execution controller corresponding to each piece of data based on the vehicle function corresponding to each data point in the target vehicle usage habit data; sending a data pre-write instruction to each target execution controller; the data pre-write instruction including the account reuse task identifier, the vehicle-end account identifier to be reused, and the corresponding target vehicle usage habit data; and each target execution controller responding to the data pre-write instruction by writing the received target vehicle usage habit data to the storage area corresponding to the vehicle-end account identifier to be reused, keeping the written target vehicle usage habit data in an inactive state, and returning a data writing result carrying the account reuse task identifier.
[0064] Specifically, the vehicle-side controller can determine the execution controller responsible for controlling the corresponding vehicle function based on the vehicle function corresponding to each data point in the target driving habit data, and use the determined execution controller as the target execution controller for the corresponding data. The vehicle-side controller can divide the target driving habit data according to the target execution controller, so that the data sent to any target execution controller is the driving habit data corresponding to the vehicle function controlled by that target execution controller.
[0065] The vehicle-side controller generates a data pre-write instruction for each target execution controller, and carries the account reuse task identifier of the current account reuse task, the vehicle-side account identifier to be reused, and the corresponding target vehicle usage habit data in the data pre-write instruction. The data pre-write instruction is used to instruct the target execution controller to first write the target vehicle usage habit data into the corresponding storage area, but does not change the current vehicle function status based on the newly written data.
[0066] After receiving the data pre-write instruction, the target execution controller first matches the account reuse task identifier in the instruction with the locally recorded account reuse task identifier. If the account reuse task identifier matches, it locates the corresponding storage area based on the vehicle-side account identifier to be reused and writes the received target driving habit data into that storage area. After completing the data writing, the target execution controller does not immediately switch the vehicle-side account identifier to be reused to the currently used vehicle-side account identifier, keeping the newly written target driving habit data inactive. The target execution controller continues to perform vehicle function control based on the vehicle-side account identifier used before the account switch until it receives an account activation instruction from the vehicle-side controller.
[0067] For example, the target vehicle usage habit data includes the on / off status of the first vehicle function and the operating mode of the second vehicle function. The vehicle-side controller can send the on / off status to the target execution controller that controls the first vehicle function and the operating mode to the target execution controller that controls the second vehicle function. Each target execution controller writes the corresponding data into the storage area corresponding to the vehicle-side account identifier to be reused, but before the account is activated, the first and second vehicle functions remain in the state before the account switch.
[0068] One possible implementation method further includes: after each target execution controller completes the writing of target vehicle usage habit data, reading the written data corresponding to the target vehicle usage habit data stored in the corresponding storage area of each target execution controller. The written data is compared with the received target vehicle usage habit data to obtain the data writing result. The data writing result includes an account reuse task identifier, a data writing status, and the corresponding comparison result. Based on the account reuse task identifier in each data writing result, the account reuse task corresponding to each data writing result is determined. If each data writing result corresponds to the current account reuse task, each data writing status indicates that data writing is complete, and each comparison result indicates that the written data is consistent with the corresponding target vehicle usage habit data, then each data writing result is determined to meet the account switching conditions.
[0069] Specifically, after each target execution controller completes the writing of the target vehicle usage habit data, it can reread the data written this time from the storage area corresponding to the account identifier of the vehicle to be reused, and compare the reread written data with the target vehicle usage habit data carried in the data pre-write instruction. The target execution controller can determine the data writing status based on the completion of this data writing operation, and determine the comparison result based on the consistency between the written data and the target vehicle usage habit data. Then, it encapsulates the account reuse task identifier, data writing status, and comparison result into a data writing result and sends it to the vehicle controller.
[0070] After receiving the data write results from each target execution controller, the vehicle-side controller first excludes data write results belonging to historical account reuse tasks or other account reuse tasks based on the account reuse task identifier in the data write results. For each data write result corresponding to the current account reuse task, the vehicle-side controller further determines whether each target execution controller has completed the data write, and whether the data written by each target execution controller is consistent with the corresponding target vehicle usage habit data.
[0071] Once all target execution controllers corresponding to the current account reuse task have completed data writing, and the data reread by each target execution controller is consistent with the target vehicle usage habit data issued by the vehicle controller, the vehicle controller determines that all data writing results meet the account switching conditions. These account switching conditions are not pre-set isolated judgment conditions, but are jointly determined based on the data writing range corresponding to the current account reuse task, the data writing status of each target execution controller, and the consistency of the written data. This indicates that each target execution controller has the conditions to uniformly switch to the vehicle account identifier to be reused.
[0072] For example, if the first target execution controller has completed writing the vehicle function switch state, and the second target execution controller has completed writing the vehicle operating mode, and the data reread by both the first and second target execution controllers is consistent with the received data, then the vehicle-side controller can determine that all data writing results meet the account switching conditions. If the second target execution controller has not completed data writing, or the reread vehicle operating mode is inconsistent with the received vehicle operating mode, then the vehicle-side controller is unsure whether all data writing results meet the account switching conditions.
[0073] S204, after confirming that all data writing results meet the account switching conditions, bind the vehicle terminal account identifier to be reused with the target cloud vehicle account, and send an account activation instruction to each target execution terminal controller so that each target execution terminal controller switches the vehicle terminal account identifier to be reused to the currently used vehicle terminal account identifier.
[0074] Specifically, once all target execution controllers have completed writing the target vehicle usage habit data and the written data has passed consistency comparison, the vehicle-side controller can establish a binding relationship between the vehicle-side account identifier to be reused and the target cloud-based vehicle usage account, and control each target execution controller to enable the vehicle-side account identifier to be reused through account activation commands. By separating the process of writing the target vehicle usage habit data from the process of making the target vehicle usage habit data effective, the corresponding vehicle-side account identifier can be switched uniformly after each target execution controller has completed data preparation.
[0075] One possible implementation involves sending account activation instructions to each target execution controller, including: if all data write results meet the account switching conditions, setting the binding relationship between the vehicle-end account identifier to be reused and the target cloud-based vehicle account to a pending activation state; determining the target activation time corresponding to the vehicle-end account identifier to be reused, and generating an account activation instruction carrying the account reuse task identifier and the target activation time; sending the account activation instruction to each target execution controller, so that if the account reuse task identifier matches successfully, each target execution controller switches the vehicle-end account identifier to be reused to the currently used vehicle-end account identifier at the target activation time and returns the account activation result; if all account activation results are successful, removing the binding relationship between the vehicle-end account identifier to be reused and the original cloud-based vehicle account, updating the binding relationship between the vehicle-end account identifier to be reused and the target cloud-based vehicle account to an active state, and updating the account reuse task to a completed state.
[0076] Specifically, after the vehicle-side controller confirms that all data write results meet the account switching conditions, it can first establish a binding relationship between the vehicle-side account identifier to be reused and the target cloud-based vehicle account, and set this binding relationship to a pending-effective state. In the pending-effective state, the target cloud-based vehicle account has already established a correspondence with the vehicle-side account identifier to be reused, but this correspondence is not used to control the reading of target usage habit data by the various target execution controllers. Simultaneously, the vehicle-side controller can continue to retain the original binding relationship between the vehicle-side account identifier to be reused and the original cloud-based vehicle account, so as to restore the state before account reuse in the event of account activation failure.
[0077] The vehicle-side controller can determine the target activation time for unified account switching by all target execution controllers based on the shared vehicle time, and generate an account activation command carrying an account reuse task identifier and the target activation time. The target activation time can be a preset time after the account activation command is sent, so that after receiving the account activation command and completing the switching preparation, each target execution controller will activate the vehicle-side account identifier to be reused at the same time.
[0078] Upon receiving the account activation command, each target execution controller matches the account reuse task identifier in the command with the locally recorded account reuse task identifier. If the account reuse task identifier matches, each target execution controller waits for the target activation time. When the target activation time arrives, it switches the vehicle-side account identifier to be reused to the currently used vehicle-side account identifier, reads the target vehicle usage habit data from the storage area corresponding to the vehicle-side account identifier to be reused, and adjusts the corresponding vehicle functions based on the target vehicle usage habit data.
[0079] After each target execution controller completes the account switch, it returns the account activation result to the vehicle controller. When the vehicle controller receives the account activation results from all target execution controllers, and all account activation results indicate successful account activation, it releases the binding relationship between the vehicle account identifier to be reused and the original cloud-based vehicle account, updates the binding relationship between the vehicle account identifier to be reused and the target cloud-based vehicle account from the pending activation state to the activated state, and updates the processing stage of the account reuse task to the completed state.
[0080] For example, after both the first and second target execution controllers have completed writing the target vehicle usage habit data, the vehicle-side controller can determine a common target activation time. Upon reaching the target activation time, the first and second target execution controllers respectively enable the vehicle function switch status and vehicle operating mode stored under the vehicle-side account identifier to be reused. After confirming that both the first and second target execution controllers have completed account activation, the vehicle-side controller then decouples the vehicle-side account identifier to be reused from the original cloud-based vehicle usage account.
[0081] Furthermore, the method also includes: in cases where it is determined that there are data writing results that do not meet the account switching conditions, or account activation results that have failed, generating an account reuse rollback instruction carrying an account reuse task identifier and a snapshot of the original vehicle usage data. The account reuse rollback instruction is sent to the target execution controller that has already written the target vehicle usage data, so that the corresponding target execution controller can restore the original vehicle usage data under the account identifier to be reused based on the original vehicle usage data snapshot. The binding relationship between the account identifier to be reused and the original cloud-based vehicle usage account is maintained, the binding relationship between the account identifier to be reused and the target cloud-based vehicle usage account that is in a pending state is deleted, and the account reuse task is updated to a rollback completed state.
[0082] Specifically, during the target vehicle usage habit data writing phase, if some target execution controllers fail to complete data writing, or if the reread data is inconsistent with the received target vehicle usage habit data, the vehicle controller can determine the target execution controllers that have already written the target vehicle usage habit data based on the data writing results, and extract the original vehicle usage habit data stored by these target execution controllers before account reuse from the original vehicle usage habit data snapshot.
[0083] The vehicle-side controller can generate an account reuse rollback instruction based on the extracted original driving habit data and the account reuse task identifier of the current account reuse task, and send the account reuse rollback instruction to the target execution controller that has already written the target driving habit data. After confirming that the account reuse rollback instruction corresponds to the current account reuse task based on the account reuse task identifier, the corresponding target execution controller rewrites the original driving habit data into the storage area corresponding to the vehicle-side account identifier to be reused, thereby restoring the stored content before the data was pre-written.
[0084] During the account activation phase, if some target execution controllers return an account activation failure result, the vehicle controller can send an account reuse rollback instruction to the target execution controllers that have completed account activation. This will cause the target execution controllers that have completed account activation to stop using the target vehicle usage habit data and restore the vehicle account identifier and the corresponding original vehicle usage habit data before account reuse.
[0085] After data recovery is complete, the vehicle-side controller continues to maintain the binding relationship between the vehicle-side account identifier to be reused and the original cloud-based vehicle account. If a binding relationship has already been established between the vehicle-side account identifier to be reused and the target cloud-based vehicle account and is in a pending state, the binding relationship will be deleted, and the account reuse task will be updated to a rollback completed state to indicate that the account reuse has not been completed and the vehicle has been restored to its state before the account reuse.
[0086] For example, if the first target execution controller has successfully written the target vehicle usage habit data, and the second target execution controller fails to complete the writing due to a communication error, the vehicle-side controller can extract the original vehicle usage habit data corresponding to the first target execution controller from the original vehicle usage habit data snapshot and send it to the first target execution controller. The first target execution controller uses the original vehicle usage habit data to overwrite the already written target vehicle usage habit data, ensuring that the vehicle-side account identifier to be reused continues to correspond to the original cloud-based vehicle usage account.
[0087] The above primarily describes the solutions provided in this application from the perspective of the device's working principle. It is understood that the vehicle usage habit data synchronization device, in order to achieve the above functions, includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware 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 this application.
[0088] This application embodiment can divide the vehicle usage habit data synchronization device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module.
[0089] It should be noted that the module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. When dividing functional modules according to their respective functions, Figure 3 A schematic diagram of a possible configuration of the vehicle usage habit data synchronization device involved in the above and embodiment is shown. Figure 3 As shown, the vehicle usage habit data synchronization device 300 may include: a determination module 301, an acquisition module 302, a sending module 303, and a binding module 304.
[0090] The determining module 301 is used to support the execution of the vehicle usage habit data synchronization device 300. Figure 2 S201 is an example of the method for synchronizing vehicle usage habit data.
[0091] The acquisition module 302 is used to support the synchronization device 300 for vehicle usage habit data. Figure 2 S202 is an example of the method for synchronizing vehicle usage habit data.
[0092] The sending module 303 is used to support the synchronization device 300 for vehicle usage habit data. Figure 2 S203 is an example of the method for synchronizing vehicle usage habit data.
[0093] Binding module 304 is used to support the execution of the vehicle usage habit data synchronization device 300. Figure 2 S204 is an example of the method for synchronizing vehicle usage habit data.
[0094] One possible implementation involves a determination module used to identify vehicle-side account identifiers to be reused from already bound vehicle-side account identifiers. Specifically, this module: obtains the account activation status corresponding to each vehicle-side account identifier; identifies vehicle-side account identifiers to be reused from those not currently active; generates an account reuse task based on the vehicle-side account identifier to be reused, the original cloud-based vehicle-use account, and the target cloud-based vehicle-use account; assigns an account reuse task identifier to the account reuse task; and sets the vehicle-side account identifier to be reused to a pending reuse status.
[0095] One possible implementation involves an acquisition module that, when acquiring the original vehicle usage habit data stored by each execution controller in the vehicle under the vehicle-side account identifier to be reused, specifically: sending an account reuse preparation instruction to each execution controller. The account reuse preparation instruction includes an account reuse task identifier and the vehicle-side account identifier to be reused. It also receives data collection responses carrying the account reuse task identifier from each execution controller. The data collection response is the corresponding execution controller's response to the account reuse preparation instruction, setting the storage area corresponding to the vehicle-side account identifier to be reused to a locked state, reading the original vehicle usage habit data from the storage area, and then returning. Finally, it generates a snapshot of the original vehicle usage habit data based on the original vehicle usage habit data in each data collection response.
[0096] One possible implementation involves an acquisition module that, when uploading original driving habit data to the cloud server, specifically sends a data synchronization request to the cloud server carrying an account reuse task identifier, the original cloud-based driving account, and a snapshot of the original driving habit data. The cloud server associates the snapshot of the original driving habit data with the original cloud-based driving account and, after completing the storage of the snapshot, returns data storage confirmation information carrying the account reuse task identifier. If the account reuse task identifier in the data storage confirmation information matches the current account reuse task, and the data storage confirmation information indicates that the storage of the original driving habit data snapshot is complete, the processing stage of the account reuse task is updated to the data writing stage.
[0097] One possible implementation involves a sending module that, when sending target vehicle usage habit data and the vehicle-end account identifier to be reused to the corresponding target execution controller, specifically: determining the target execution controller corresponding to each piece of data based on the vehicle function corresponding to each piece of data in the target vehicle usage habit data; sending a data pre-write instruction to each target execution controller; the data pre-write instruction including the account reuse task identifier, the vehicle-end account identifier to be reused, and the corresponding target vehicle usage habit data; and each target execution controller responding to the data pre-write instruction by writing the received target vehicle usage habit data to the storage area corresponding to the vehicle-end account identifier to be reused, keeping the written target vehicle usage habit data in an inactive state, and returning the data writing result carrying the account reuse task identifier.
[0098] In one possible implementation, the vehicle usage habit data synchronization device provided in this application embodiment is further configured to: after receiving the data writing results returned by each target execution terminal controller, read the written data corresponding to the target vehicle usage habit data stored in the corresponding storage area of each target execution terminal controller. The written data is compared with the received target vehicle usage habit data to obtain the data writing results. The data writing results include one or more of the following: account reuse task identifier, data writing status, and corresponding comparison results. Based on the account reuse task identifier in each data writing result, the account reuse task corresponding to each data writing result is determined. If it is determined that each data writing result corresponds to the current account reuse task, each data writing status indicates that data writing is complete, and each comparison result indicates that the written data is consistent with the corresponding target vehicle usage habit data, then it is determined that each data writing result meets the account switching conditions.
[0099] One possible implementation involves a sending module that, when sending account activation instructions to various target execution controllers, specifically: If all data write results meet the account switching conditions, set the binding relationship between the vehicle-end account identifier to be reused and the target cloud-based vehicle account to a pending activation state. Determine the target activation time corresponding to the vehicle-end account identifier to be reused, and generate an account activation instruction carrying the account reuse task identifier and the target activation time. Send the account activation instruction to each target execution controller, so that if the account reuse task identifier matches successfully, each target execution controller switches the vehicle-end account identifier to be reused to the currently used vehicle-end account identifier at the corresponding target activation time and returns the account activation result. If all account activation results are successful, remove the binding relationship between the vehicle-end account identifier to be reused and the original cloud-based vehicle account, update the binding relationship between the vehicle-end account identifier to be reused and the target cloud-based vehicle account to an active state, and update the account reuse task to a completed state.
[0100] In one possible implementation, the vehicle usage habit data synchronization device provided in this application embodiment is further configured to: generate an account reuse rollback instruction carrying an account reuse task identifier and a snapshot of the original vehicle usage habit data when it is determined that there is a data writing result that does not meet the account switching conditions or an account activation result that fails to activate the account. The account reuse rollback instruction is sent to the target execution controller that has already written the target vehicle usage habit data, so that the corresponding target execution controller restores the original vehicle usage habit data under the vehicle-side account identifier to be reused based on the original vehicle usage habit data snapshot. The binding relationship between the vehicle-side account identifier to be reused and the original cloud-based vehicle usage account is maintained, the binding relationship between the vehicle-side account identifier to be reused and the target cloud-based vehicle usage account that is in a pending state is deleted, and the account reuse task is updated to a rollback completed state.
[0101] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.
[0102] The vehicle usage habit data synchronization device 300 provided in this application embodiment is used to perform the above-mentioned... Figure 2 The method for synchronizing vehicle usage data shown can achieve the same effect as the method for synchronizing vehicle usage data described above.
[0103] This application also provides a device for synchronizing vehicle usage data, which can execute the vehicle usage data synchronization method and related steps in the above method embodiments.
[0104] This application also provides a computer-readable storage medium storing instructions that, when executed, perform the vehicle usage habit data synchronization method and related steps in the above method embodiments.
[0105] This application also provides a computer program product that, when run on a computer, causes the computer to execute the method and related steps for synchronizing vehicle usage habit data as described in the above method embodiments.
[0106] In some embodiments, the methods shown in this application can be implemented as computer program instructions encoded in a machine-readable format on a computer-readable storage medium or on other non-transitory media or articles of art.
[0107] This application also provides a vehicle usage habit data synchronization system 100, such as... Figure 4 As shown, the vehicle usage habit data synchronization system 100 includes at least one processor 401 and at least one interface circuit 402.
[0108] As an example, when the vehicle usage habit data synchronization system 100 includes a processor and an interface circuit, the processor can be... Figure 4 The processor 401 shown in the solid box (or the processor 401 shown in the dashed box) can be an interface circuit. Figure 4 The interface circuit 402 is shown in the solid box (or the dashed box). When the vehicle usage data synchronization system 100 includes two processors and two interface circuits, then the two processors include... Figure 4 The processor 401 shown in the solid box and the processor 401 shown in the dashed box, these two interface circuits include Figure 4 Interface circuit 402 is shown in both solid and dashed boxes. No limitations are imposed on this.
[0109] Processor 401 and interface circuit 402 can be interconnected via a line. For example, interface circuit 402 can be used to receive signals. Alternatively, interface circuit 402 can be used to send signals to other devices (e.g., processor 401). For instance, interface circuit 402 can read computer instructions stored in memory and send those instructions to processor 401. Processor 401 executes the instructions and, in conjunction with input / output devices, implements the various steps in the above embodiments, such as implementing... Figure 2 The methods illustrated are the steps performed in the embodiments shown. Of course, the system for synchronizing vehicle usage data may also include other discrete components, and this application does not specifically limit this.
[0110] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.
[0111] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.
[0112] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0113] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0114] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to it, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0115] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A method for synchronizing vehicle usage habit data, characterized in that, The method includes: In response to the login operation of the target cloud-based car-hailing account, if the target cloud-based car-hailing account is not bound to a vehicle-end account identifier and a preset number of vehicle-end account identifiers are all bound, the vehicle-end account identifier to be reused is determined from the already bound vehicle-end account identifiers, and the original cloud-based car-hailing account currently bound to the vehicle-end account identifier to be reused is determined. The original vehicle usage habit data stored under the account identifier of the vehicle to be reused by each actuator controller in the vehicle is obtained, and the original vehicle usage habit data is uploaded to the cloud server so that the cloud server associates and stores the original vehicle usage habit data with the original cloud vehicle account; After receiving the data storage confirmation information returned by the cloud server, the system obtains the target car usage habit data corresponding to the target cloud car usage account, and sends the target car usage habit data and the car usage terminal account identifier to the corresponding target execution terminal controller, and receives the data writing results returned by each of the target execution terminal controllers. If all the data writing results meet the account switching conditions, the vehicle terminal account identifier to be reused is bound to the target cloud vehicle account, and an account activation instruction is sent to each of the target execution terminal controllers so that each of the target execution terminal controllers switches the vehicle terminal account identifier to be reused to the currently used vehicle terminal account identifier.
2. The method according to claim 1, characterized in that, The step of determining the vehicle-end account identifier to be reused from the already bound vehicle-end account identifiers includes: Obtain the account activation status corresponding to each of the vehicle-side account identifiers; The vehicle account identifier to be reused is determined from vehicle account identifiers that have never been in a currently active state; An account reuse task is generated based on the vehicle-end account identifier to be reused, the original cloud-based vehicle-use account, and the target cloud-based vehicle-use account. An account reuse task identifier is assigned to the account reuse task, and the vehicle-end account identifier to be reused is set to a pending reuse status.
3. The method according to claim 2, characterized in that, The acquisition of the original vehicle usage habit data stored by each actuator controller in the vehicle under the account identifier of the vehicle to be reused includes: Send an account reuse preparation instruction to each of the execution terminal controllers; the account reuse preparation instruction includes: the account reuse task identifier and the vehicle terminal account identifier to be reused; Receive data collection responses carrying the account reuse task identifier returned by each of the execution terminal controllers; the data collection response is the corresponding execution terminal controller responding to the account reuse preparation instruction, setting the storage area corresponding to the vehicle terminal account identifier to be reused to a locked state, reading the original vehicle usage habit data in the storage area and returning; A snapshot of the original vehicle usage habits data is generated based on the original vehicle usage habits data in each of the aforementioned data collection responses.
4. The method according to claim 3, characterized in that, Uploading the original car usage habit data to the cloud server includes: Send a data synchronization request to the cloud server, carrying the account reuse task identifier, the original cloud-based car account, and a snapshot of the original car usage data; The cloud server associates and stores the original car usage habit data snapshot with the original cloud car usage account, and returns data storage confirmation information carrying the account reuse task identifier after completing the storage of the original car usage habit data snapshot; If the account reuse task identifier in the data storage confirmation information matches the current account reuse task, and the data storage confirmation information indicates that the original car usage habit data snapshot has been stored, the processing stage of the account reuse task will be updated to the data writing stage.
5. The method according to claim 4, characterized in that, The step of sending the target vehicle usage habit data and the vehicle-to-use account identifier to the corresponding target execution controller includes: Based on the vehicle function corresponding to each data point in the target vehicle usage habit data, determine the target execution terminal controller corresponding to each data point; Each of the target execution terminal controllers is sent a data pre-writing instruction; the data pre-writing instruction includes the account reuse task identifier, the vehicle terminal account identifier to be reused, and the corresponding target vehicle usage habit data. Each of the target execution terminal controllers responds to the data pre-writing instruction by writing the received target vehicle usage habit data into the storage area corresponding to the vehicle reuse terminal account identifier, keeping the written target vehicle usage habit data in an inactive state, and returning the data writing result carrying the account reuse task identifier.
6. The method according to claim 1, characterized in that, The method further includes: After receiving the data writing results returned by each of the target execution terminal controllers, read the written data corresponding to the target vehicle usage habit data stored in the corresponding storage area of each of the target execution terminal controllers; The written data is compared with the received target vehicle usage habit data to obtain the data writing result; the data writing result includes one or more of the following: account reuse task identifier, data writing status and corresponding comparison result; Based on the account reuse task identifier in each of the data writing results, determine the account reuse task corresponding to each of the data writing results; If each of the data writing results corresponds to the current account reuse task, each of the data writing statuses indicates that the data writing is complete, and each of the comparison results indicates that the written data is consistent with the corresponding target driving habit data, then each of the data writing results satisfies the account switching conditions.
7. The method according to claim 6, characterized in that, Sending account activation instructions to each of the target execution terminal controllers includes: If it is determined that all the data writing results meet the account switching conditions, the binding relationship between the vehicle terminal account identifier to be reused and the target cloud vehicle account is set to a pending state. Determine the target activation time corresponding to the vehicle-end account identifier to be reused, and generate an account activation instruction carrying the account reuse task identifier and the target activation time; The account activation instruction is sent to each of the target execution terminal controllers, so that when the account reuse task identifier is successfully matched, each of the target execution terminal controllers switches the vehicle terminal account identifier to be reused to the currently used vehicle terminal account identifier at the corresponding target activation time, and returns the account activation result. If all account activation results are confirmed to be successful, the binding relationship between the vehicle-to-use account identifier and the original cloud-based vehicle-use account is released, the binding relationship between the vehicle-to-use account identifier and the target cloud-based vehicle-use account is updated to active status, and the account reuse task is updated to complete status.
8. The method according to claim 6, characterized in that, The method further includes: If it is determined that there is a data writing result that does not meet the account switching conditions, or an account activation result that fails, an account reuse rollback instruction carrying the account reuse task identifier and the original vehicle usage habit data snapshot is generated. The account reuse rollback instruction is sent to the target execution controller that has already written the target vehicle usage habit data, so that the corresponding target execution controller can restore the original vehicle usage habit data under the vehicle-to-be-reused account identifier according to the original vehicle usage habit data snapshot; Maintain the binding relationship between the vehicle-end account identifier to be reused and the original cloud-based vehicle-use account, delete the binding relationship between the vehicle-end account identifier to be reused and the target cloud-based vehicle-use account that is in a pending state, and update the account reuse task to a rollback completed state.
9. A device for synchronizing vehicle usage habit data, characterized in that, The device includes: The determination module is used to respond to the login operation of the target cloud car-use account. When the target cloud car-use account is not bound to the vehicle-end account identifier and a preset number of vehicle-end account identifiers are all bound, the module determines the vehicle-end account identifier to be reused from the already bound vehicle-end account identifiers and determines the original cloud car-use account currently bound to the vehicle-end account identifier to be reused. The acquisition module is used to acquire the original vehicle usage habit data stored under the account identifier of the vehicle to be reused by each execution terminal controller in the vehicle, and to upload the original vehicle usage habit data to the cloud server so that the cloud server associates and stores the original vehicle usage habit data with the original cloud vehicle account. The sending module is used to, after receiving the data storage confirmation information returned by the cloud server, obtain the target car usage habit data corresponding to the target cloud car usage account, and send the target car usage habit data and the car usage terminal account identifier to be reused to the corresponding target execution terminal controller, and receive the data writing results returned by each of the target execution terminal controllers; The binding module is used to bind the vehicle terminal account identifier to be reused to the target cloud vehicle account when it is determined that all the data writing results meet the account switching conditions, and to send an account activation instruction to each of the target execution terminal controllers so that each of the target execution terminal controllers switches the vehicle terminal account identifier to be reused to the currently used vehicle terminal account identifier.
10. A device for synchronizing vehicle usage habit data, characterized in that, The device for synchronizing vehicle usage data includes a processor and a memory. The memory stores machine-executable instructions that can be executed by the processor. The processor executes the machine-executable instructions to implement the method for synchronizing vehicle usage data according to any one of claims 1 to 8.
