Vehicle owner archive management method and system based on cloud synchronization

Abstract

The invention relates to a vehicle owner archive management method and system based on cloud synchronization. The method comprises the steps that a cloud receives user information sent after a user logs in and information of a current vehicle; the cloud judges the vehicle type X of the current vehicle based on the information of the current vehicle; when it is judged that the personalized setting information of any vehicle type of the user is not stored in the cloud, personalized setting information of the vehicle type X of the user is obtained and stored in the cloud; when it is judged that the cloud does not store the personalized setting information of the vehicle type X of the user but stores the personalized setting information of other vehicle types of the user, reusable general setting items in the personalized setting information of other vehicle types are sent to the user; receiving personalized setting information of the vehicle model X set by the user based on the received general setting item information, and storing the personalized setting information in the cloud; according to personalized data of the same user among different vehicles, the management targets of strong consistency of data of the same vehicle model and reasonable isolation and differentiated reuse of data of different vehicle models can be realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of intelligent driving, and in particular to a vehicle owner profile management method and system based on cloud synchronization. BACKGROUND

[0002] With the popularization of intelligent vehicles, the scenario of users driving multiple vehicles (such as different vehicle models or multiple vehicles of the same model) is increasingly common. The personalized settings of each vehicle (such as seat position, driving mode preference, APP usage order, and other vehicle setting data, as well as driving habits, travel regularity, and other usage behavior data) directly affect the user experience. However, the current industry user personalized data management has the following pain points: Inconsistent data between the same vehicle model: the user sets personalized parameters (such as seat memory position) on one vehicle of the same model, and needs to re-set when switching to another vehicle of the same model, which cannot be automatically synchronized, affecting the continuity of use.

[0003] Mixed use of data between different vehicle models: when the user switches between different vehicle models (such as SUV and sedan), some personalized settings (such as seat height adjustment) may not be applicable due to hardware differences between vehicle models, and direct reuse may result in a decline in experience (such as mismatched seat position), but complete isolation requires repeated settings, which is cumbersome to operate.

[0004] Data synchronization logic is chaotic: after the user modifies the personalized settings of a vehicle, the cloud does not update or synchronize the changes to other associated vehicles in time, resulting in version conflicts between multiple vehicles (such as vehicle A modifying the settings, while vehicle B still using the old settings).

[0005] Lack of differentiated reuse mechanism: although different vehicle models have different hardware configurations, some common settings (such as driving mode preference and APP order) can be reused to reduce user operations, but existing solutions do not effectively distinguish between "reusable items" and "non-reusable items". SUMMARY

[0006] The present application provides a vehicle owner profile management method and system based on cloud synchronization, which can manage the personalized data of the same user in different vehicles to achieve the management goal of "strong consistency of data between the same vehicle model, reasonable isolation of data between different vehicle models, and differentiated reuse of data between different vehicle models".

[0007] According to a first aspect of the present application, a vehicle owner profile management method based on cloud synchronization is provided, comprising: Step 1: The cloud receives user information and information of the current vehicle sent by the user after logging in; Step 2: The cloud determines the vehicle model X of the current vehicle based on the information of the current vehicle, and divides the personalized setting information input by the user into reusable common setting items and non-reusable setting items; When it is determined that the cloud does not store the personalized setting information of any vehicle model of the user, the personalized setting information of the user in the vehicle model X is stored in the cloud; When it is determined that the cloud does not store the personalized setting information of the user in the vehicle model X, but stores the personalized setting information of other vehicle models of the user except the vehicle model X, the reusable general setting items in the personalized setting information of the other vehicle models are sent to the user, and the personalized setting information of the vehicle model X set by the user based on the received general setting item information is stored in the cloud.

[0008] Based on the above technical solutions, the application can be further improved as follows.

[0009] Optionally, the personalized setting information includes seat position / angle / memory, driving mode preference, APP startup sequence, instrument panel display layout, driving habit, travel rule and entertainment preference.

[0010] Optionally, the reusable general setting items include driving mode preference, APP sequence, driving habit, travel rule and entertainment preference. The non-reusable setting items include seat position / angle / memory and instrument panel display layout.

[0011] Optionally, when it is determined in step 2 that the user is not the same as the last logged-in vehicle and the cloud stores the personalized setting information of the user in the vehicle model X, the personalized setting information of the vehicle model X is sent to the user.

[0012] Optionally, the information of the current vehicle sent in step 1 is the VIN code of the vehicle, and the vehicle model and whether it is the same vehicle are identified through the VIN code in step 2.

[0013] Optionally, after the user modifies the personalized setting information of the vehicle model X through any vehicle of the vehicle model X, the updated personalized setting information of the vehicle model X is uploaded to the cloud in real time to overwrite the original personalized setting information of the vehicle model X.

[0014] Optionally, when it is determined in step 2 that the cloud does not store the personalized setting information of the user in the vehicle model X, but stores the personalized setting information of other vehicle models of the user except the vehicle model X, the process of sending the reusable general setting items in the personalized setting information of the other vehicle models to the user includes: When the number of the personalized setting information of other vehicle models stored in the cloud is one, the reusable general setting items in the personalized setting information of the vehicle model are sent to the user. When the number of the cloud-stored personalized setting information of other vehicle models is multiple, the user is sent the reusable general setting item in the personalized setting information of the vehicle model with the latest time stamp. The vehicle-end information collection module is configured to collect user information after the user logs in and information of the current vehicle and send the information to the cloud. The cloud is configured to determine the vehicle model X of the current vehicle based on the received information of the current vehicle, divide the personalized setting information input by the user into reusable general setting items and non-reusable setting items. When it is determined that the cloud does not store the personalized setting information of any vehicle model of the user, the personalized setting information of the user in the vehicle model X is obtained and stored in the cloud. When it is determined that the cloud does not store the personalized setting information of the user in the vehicle model X but stores the personalized setting information of other vehicle models of the user except the vehicle model X, the user is sent the reusable general setting items in the personalized setting information of the other vehicle models, and the personalized setting information of the vehicle model X set by the user based on the received general setting item information is stored in the cloud.

[0015] According to a third aspect of the present application, an electronic device is provided, which includes a memory and a processor, and the processor is configured to execute the computer management program stored in the memory to implement the steps of the vehicle owner profile management method based on cloud synchronization.

[0016] According to a fourth aspect of the present application, a computer readable storage medium is provided, which stores a computer management program, and the computer management program is executed by a processor to implement the steps of the vehicle owner profile management method based on cloud synchronization.

[0017] The embodiment of the present application provides a kind of based on cloud synchronization's car owner profile management method, system, electronic equipment and storage medium, same user switches in same vehicle type (such as multiple vehicle types X), personalized setting (such as seat position, driving mode) is automatically synchronized, need not repeat configuration, improve use coherence;The personalized data of different vehicle types (such as vehicle type X and vehicle type Y) is independently stored in cloud (car owner profile A and B), avoid configuration error (such as seat structure difference) caused by hardware mismatch, guarantee experience safety;Switch between different vehicle types, automatically reuse universal personalized setting item (such as driving mode preference, APP order), reduce user manual setting step, reduce operating cost;Through cloud dynamic update car owner profile version (based on timestamp comparison), ensure that user modifies setting on any vehicle, other associated vehicles can obtain latest configuration in time, avoid version lag problem;Support user adds vehicle (same vehicle type or different vehicle type), automatically adapt existing car owner profile (same vehicle type synchronization or cross-vehicle type reuse), need not extra development logic. BRIEF DESCRIPTION OF DRAWINGS

[0018] Figure 1 The flow chart of the car owner profile management method based on cloud synchronization provided by the present application is shown in the figure. Figure 2 The flow chart of the embodiment of the car owner profile management method based on cloud synchronization provided by the present application is shown in the figure. Figure 3 The hardware structure schematic diagram of a possible electronic equipment provided by the present application is shown in the figure. Figure 4 The hardware structure schematic diagram of a possible computer readable storage medium provided by the present application is shown in the figure. DETAILED DESCRIPTION

[0019] The principles and characteristics of the present application are described below in combination with the drawings, and the examples are only used to explain the present application, and not used to limit the scope of the present application.

[0020] Figure 1 The flow chart of the car owner profile management method based on cloud synchronization provided by the present application is shown in the figure. Figure 1 As shown in the figure, the management method comprises: Step 1, cloud receives the user information and the information of current vehicle sent by user after login.

[0021] Step 2, cloud judges the vehicle type X of current vehicle based on the information of current vehicle, and divides the personalized setting information input by user into reusable universal setting item and non-reusable setting item.

[0022] When it is judged that cloud does not store the personalized setting information of any vehicle type of the user, the personalized setting information of the user in vehicle type X is stored in cloud.

[0023] When it is judged that the cloud does not store the user's individual setting information of the vehicle model X, but stores the user's individual setting information of other vehicle models except the vehicle model X, the cloud sends the user the reusable general setting items in the individual setting information of the other vehicle models, and stores the individual setting information of the vehicle model X set by the user based on the received general setting item information in the cloud.

[0024] The application provides a vehicle owner file management method based on cloud synchronization, which can realize the management goal of "strong consistency of the same vehicle model data, reasonable isolation and differentiable reuse of different vehicle model data" for the individual data of the same user in different vehicles.

[0025] Embodiment 1 Embodiment 1 provided by the application is an embodiment of the vehicle owner file management method based on cloud synchronization provided by the application, which combines Figure 1 It can be seen that the embodiment of the management method comprises: Step 1, the cloud receives the user information and the information of the current vehicle sent by the user after logging in.

[0026] In a possible embodiment, the information of the current vehicle sent in step 1 is the VIN code of the vehicle.

[0027] Step 2, the cloud judges the vehicle model X of the current vehicle based on the information of the current vehicle, and divides the individual setting information input by the user into reusable general setting items and non-reusable setting items.

[0028] When it is judged that the cloud does not store the individual setting information of any vehicle model of the user, the cloud stores the individual setting information of the vehicle model X of the user in the cloud.

[0029] When it is judged that the cloud does not store the individual setting information of the vehicle model X of the user, but stores the individual setting information of other vehicle models of the user except the vehicle model X, the cloud sends the user the reusable general setting items in the individual setting information of the other vehicle models, and stores the individual setting information of the vehicle model X set by the user based on the received general setting item information in the cloud.

[0030] In a possible embodiment, the individual setting information includes seat position / angle / memory, driving mode preference, APP startup sequence, instrument panel display layout, driving habit, travel regularity and entertainment preference.

[0031] In specific implementation, the individual setting information can be divided into vehicle setting type and use behavior type.

[0032] Vehicle setting category: including seat position / angle / memory, driving mode (e.g. economy / sport / comfort), APP start-up sequence, instrument panel display layout, and other configuration parameters directly related to vehicle hardware.

[0033] Usage behavior category: including driving habits (e.g. frequency of sudden acceleration / sudden braking, commonly used speed interval), travel regularity (e.g. commuting time / route preference, commonly used location marker), entertainment preference (e.g. commonly used radio / music type), and other abstract data reflecting user usage characteristics.

[0034] In a possible embodiment, the reusable general setting items include driving mode preference, APP sequence, driving habits, travel regularity, and entertainment preference.

[0035] The non-reusable setting items include seat position / angle / memory and instrument panel display layout.

[0036] When switching between different vehicle models, the universally applicable personalized setting items can reduce the user's manual setting steps and reduce operation costs; at the same time, the setting of non-reusable setting items can also avoid configuration errors caused by hardware mismatch (e.g. seat structure difference), and ensure experience safety.

[0037] In a possible embodiment, when it is determined in step 2 that the user is not the same as the last time the user logged in to the vehicle and that the cloud storage has the user's personalized setting information for vehicle model X, the personalized setting information for vehicle model X is sent to the user.

[0038] In a possible embodiment, in step 2, the vehicle model and whether it is the same vehicle are identified by the VIN code.

[0039] In a possible embodiment, after the user modifies the personalized setting information for vehicle model X through any vehicle of vehicle model X, the updated personalized setting information for vehicle model X is uploaded to the cloud in real time to overwrite the original personalized setting information for vehicle model X.

[0040] To ensure that the cloud storage is always up-to-date for vehicle model X, the latest personalized setting information for vehicle model X is sent to the cloud when the user logs in to other vehicles of vehicle model X, achieving real-time synchronization between multiple vehicles of the same model.

[0041] In a possible embodiment, when it is determined in step 2 that the cloud storage does not have the user's personalized setting information for vehicle model X, but has the user's personalized setting information for other vehicle models, the process of sending the reusable general setting items in the personalized setting information for other vehicle models to the user includes: When the number of personalized setting information for other vehicle models stored in the cloud is one, the reusable general setting items in the personalized setting information for that vehicle model are sent to the user.

[0042] When the number of the cloud-stored personalized setting information of other vehicle models is multiple, the reusable general setting item in the vehicle model with the latest timestamp is sent to the user.

[0043] Embodiment 2 The embodiment 1 provided by the present application is a specific application embodiment of the vehicle owner profile management method based on cloud synchronization provided by the present application, which is described as follows. Figure 2 The flowchart of the embodiment of the vehicle owner profile management method based on cloud synchronization provided by the present application is described in combination with Figure 2 It can be known that the embodiment of the management method comprises: It can be known that in the embodiment provided by the present application, the vehicle information is shown in Table 1 as follows: Figure 2

[0044] Table 1 Vehicle information table When the user 1 logs in the vehicle 1 of the vehicle model X for the first time, the personalized setting (such as adjusting the seat position, selecting the driving mode preference) is completed, and then the vehicle 1 automatically uploads all the current personalized setting data (vehicle setting type + use behavior type) to the cloud to form the initialized vehicle owner profile A.

[0045] When the user 1 modifies the personalized setting on the vehicle 1, the vehicle 1 uploads the updated data to the cloud in real time, and the original vehicle owner profile A is overwritten, so that the vehicle owner profile A stored in the cloud is always the latest configuration of the vehicle 1.

[0046] When the user 1 logs in the vehicle 2 of the vehicle model X for the first time, the cloud automatically issues the vehicle owner profile A to the vehicle 2 to complete the synchronization of the vehicle profile A. After the vehicle 2 loads the profile, the user can obtain the consistent personalized experience without re-setting.

[0047] When the user 1 modifies the personalized setting on the vehicle 2, the vehicle 2 uploads the updated data to the cloud in real time, and the original vehicle owner profile A is overwritten (at this time, the vehicle owner profile A is updated to the latest configuration of the vehicle 2). When the user logs in the vehicle 1 or the vehicle 2 later, the cloud issues the latest vehicle owner profile A, and the real-time synchronization between the vehicles of the same model is realized.

[0048] When the user logs in the vehicle 3 of the vehicle model Y which is different from the vehicle model X of the vehicle 1 / vehicle 2 for the first time, the cloud automatically issues the current vehicle owner profile A to the vehicle 3 to complete the synchronization of the vehicle owner profile A. At the same time, the cloud filters the reusable personalized setting items (such as the driving mode preference, the APP sorting, and the general parameters in the vehicle setting type which are irrelevant to the hardware) in the vehicle owner profile A based on the hardware characteristics of the vehicle model Y, and automatically applies them to the vehicle 3. The cloud initializes the independent vehicle owner profile B for the vehicle 3.​ When the user modifies the personalized settings on the vehicle 3, the vehicle 3 automatically uploads the updated data to the cloud, overwriting the original owner profile B, completely isolated from the owner profile A (vehicle model X), ensuring that the personalized data of different vehicle models is stored independently.

[0049] When the user first logs in to a vehicle 4 of a different vehicle model Z, the cloud compares the update timestamps of the owner profile A and the owner profile B, and delivers the latest updated owner profile (such as the owner profile B if it is updated later than the owner profile A, then the owner profile B is delivered; otherwise, the owner profile A is delivered) to the vehicle 4. This mechanism ensures that the user uses the most recently modified personalized configuration when switching between different vehicle models, reducing the experience difference caused by version lag.

[0050] Same vehicle model data strong consistency: All vehicles (vehicle 1, vehicle 2...) of the same vehicle model (such as vehicle model X) share the same owner profile (owner profile A), and any modification is synchronized to the cloud in real time and overwrites the original profile. The latest version is obtained when the same vehicle model vehicle logs in, ensuring that the personalized data is completely consistent.

[0051] Different vehicle model data isolation: Different vehicle models (such as vehicle models X, Y, Z) correspond to independent owner profiles (owner profiles A, B, C...), and modification operations only affect the current vehicle model profile, avoiding configuration conflicts caused by hardware differences between different vehicle models.

[0052] Differential reuse mechanism: When switching between different vehicle models, the cloud automatically identifies reusable general settings (such as driving mode preferences), reducing user repetitive operations; at the same time, strictly isolating hardware-related settings that cannot be reused (such as seat position), ensuring experience safety.

[0053] The present application solves the problems of poor consistency, cumbersome operation and synchronization lag in the management of personalized setting data across vehicles for existing smart car users through the hierarchical management and dynamic synchronization mechanism of the cloud owner profile, and the specific goals include: Ensure that the same user's personalized data is completely synchronized between the same vehicle model (such as multiple vehicle models X), maintaining experience consistency.

[0054] Implementing isolated storage of personalized data for the same user between different vehicle models (such as vehicle model X and vehicle model Y), avoiding experience degradation caused by hardware mismatch.

[0055] Supporting automatic reuse of common personalized settings (such as driving mode preferences) when switching between different vehicle models, reducing user repetitive setting operations.

[0056] Dynamically maintaining the latest version of the owner profile to ensure real-time synchronization and update of multi-vehicle data.

[0057] Embodiment 2 The embodiment 2 provided by the present application is an embodiment of the vehicle owner profile management system based on cloud synchronization provided by the present application. The vehicle owner profile management system based on cloud synchronization provided by the embodiment of the present application is based on a "cloud-vehicle terminal" collaborative architecture, and is realized through classification collection, differential synchronization and version control of personalized data. The embodiment of the management system includes a vehicle terminal information collection module and a cloud.

[0058] The vehicle terminal information collection module is used for collecting user information after user login and information of the current vehicle and sending the information to the cloud.

[0059] The cloud is used for judging the vehicle model X of the current vehicle based on the received information of the current vehicle, dividing the personalized setting information input by the user into reusable general setting items and non-reusable setting items.

[0060] When it is judged that the cloud does not store the personalized setting information of any vehicle model of the user, the personalized setting information of the user in the vehicle model X is obtained and stored in the cloud.

[0061] When it is judged that the cloud does not store the personalized setting information of the user in the vehicle model X, but stores the personalized setting information of other vehicle models of the user except the vehicle model X, the reusable general setting items in the personalized setting information of other vehicle models are sent to the user, and the personalized setting information of the vehicle model X set by the user based on the received general setting item information is stored in the cloud.

[0062] It can be understood that the vehicle owner profile management system based on cloud synchronization provided by the present application corresponds to the vehicle owner profile management method based on cloud synchronization provided by each of the foregoing embodiments. The related technical features of the vehicle owner profile management system based on cloud synchronization can refer to the related technical features of the vehicle owner profile management method based on cloud synchronization, and will not be repeated here.

[0063] Please refer to Figure 3 , Figure 3 The embodiment of the electronic device provided by the present application is shown in the schematic diagram. As shown in Figure 3As shown in the figure, the embodiment of the present application provides an electronic device, which comprises a memory 1310, a processor 1320, and a computer program 1311 stored in the memory 1310 and capable of running on the processor 1320, and the processor 1320 implements the following steps when executing the computer program 1311: sending user information and information of a current vehicle to the cloud after user login; determining a vehicle model X of the current vehicle based on the information of the current vehicle, and dividing personalized setting information input by the user into reusable general setting items and non-reusable setting items; when it is determined that the cloud does not store personalized setting information of any vehicle model of the user, storing personalized setting information of the user in the vehicle model X in the cloud; when it is determined that the cloud does not store personalized setting information of the user in the vehicle model X, but stores personalized setting information of other vehicle models of the user except the vehicle model X, sending the reusable general setting items in the personalized setting information of the other vehicle models to the user, and storing personalized setting information of the vehicle model X set by the user based on the received general setting item information in the cloud.

[0064] Please refer to Figure 4 , Figure 4 An embodiment of a computer readable storage medium provided by the present application is shown in the figure. As Figure 4 shown in the figure, the embodiment provides a computer readable storage medium 1400, which stores a computer program 1411, and the computer program 1411 implements the following steps when executed by a processor: sending user information and information of a current vehicle to the cloud after user login; determining a vehicle model X of the current vehicle based on the information of the current vehicle, and dividing personalized setting information input by the user into reusable general setting items and non-reusable setting items; when it is determined that the cloud does not store personalized setting information of any vehicle model of the user, storing personalized setting information of the user in the vehicle model X in the cloud; when it is determined that the cloud does not store personalized setting information of the user in the vehicle model X, but stores personalized setting information of other vehicle models of the user except the vehicle model X, sending the reusable general setting items in the personalized setting information of the other vehicle models to the user, and storing personalized setting information of the vehicle model X set by the user based on the received general setting item information in the cloud.

[0065] The embodiment of the present application provides a vehicle owner file management method and system based on cloud synchronization, an electronic device and a storage medium, when the same user switches between the same vehicle model (such as multiple vehicle models X), personalized settings (such as seat position and driving mode) are automatically synchronized, without the need for repeated configuration, and the use continuity is improved; the personalized data of different vehicle models (such as vehicle model X and vehicle model Y) is independently stored in the cloud (vehicle owner files A and B), so that configuration errors (such as seat structure differences) caused by hardware mismatch are avoided, and experience safety is ensured; when switching between different vehicle models, commonly used personalized setting items (such as driving mode preference and APP sorting) are automatically reused, the user manual setting steps are reduced, and the operation cost is reduced; the vehicle owner file version is dynamically updated through the cloud (based on timestamp comparison), so that after the user modifies the settings on any vehicle, other associated vehicles can timely obtain the latest configuration, and the version lag problem is avoided; when the user adds a vehicle (the same vehicle model or different vehicle models), the existing vehicle owner file (the same vehicle model is synchronized or the different vehicle models are reused) is automatically adapted, without the need for additional development logic.

[0066] It should be noted that in the above embodiments, the description of each embodiment has its own emphasis, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0067] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.

[0068] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system), and computer program product according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be realized by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing devices to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices produce a device for implementing the functions specified in the flowcharts and / or block diagrams. Figure 1 The device for implementing the functions specified in one or more flows and / or blocks. Figure 1 The device for implementing the functions specified in one or more flows and / or blocks.

[0069] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the Figure 1 function specified in the flow or flows and / or blocks Figure 1 of the block or blocks.

[0070] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the Figure 1 function specified in the flow or flows and / or blocks Figure 1 of the block or blocks.

[0071] Although preferred embodiments of the application have been described herein, substitutions and alterations are possible in view of the teachings of this application. Therefore, the appended claims are intended to encompass all such substitutions and alterations that fall within the scope of the present application. What is claimed is:

[0072] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. A method for managing vehicle owner files based on cloud synchronization, characterized in that, The management method includes: Step 1: The cloud receives user information and current vehicle information sent by the user after logging in; Step 2: The cloud determines the vehicle model X based on the current vehicle information and divides the personalized settings entered by the user into reusable general settings and non-reusable settings. If it is determined that the cloud does not store any personalized settings information for the user's vehicle model, the personalized settings information for the user in vehicle model X is obtained and stored in the cloud. If it is determined that the cloud does not store the user's personalized settings information for vehicle model X, but stores the user's personalized settings information for other vehicle models besides vehicle model X, the reusable common settings items from the personalized settings information of the other vehicle models are sent to the user, and the personalized settings information for vehicle model X set by the user based on the received common settings item information is stored in the cloud.

2. The management method according to claim 1, characterized in that, The personalized settings include: seat position / angle / memory, driving mode preference, APP launch order, instrument panel display layout, driving habits, travel patterns, and entertainment preferences.

3. The management method according to claim 1, characterized in that, The reusable general settings include: driving mode preference, APP sorting, driving habits, travel patterns, and entertainment preferences; The non-reusable settings include: seat position / angle / memory and instrument panel display layout.

4. The management method according to claim 1, characterized in that, In step 2, if it is determined that the user's vehicle is different from the vehicle they logged in with last time and the cloud stores the user's personalized settings information for vehicle model X, then the personalized settings information for vehicle model X will be sent to the user.

5. The management method according to claim 4, characterized in that, The information about the current vehicle sent in step 1 is the vehicle's VIN code. In step 2, the vehicle model and whether it is the same vehicle are identified through the VIN code.

6. The management method according to claim 4, characterized in that, After a user modifies the personalized settings of vehicle model X through any vehicle of model X, the updated personalized settings of vehicle model X are uploaded to the cloud in real time, overwriting the original personalized settings of vehicle model X.

7. The management method according to claim 1, characterized in that, In step 2, if the cloud does not store the user's personalized settings information for vehicle model X, but does store the user's personalized settings information for other vehicle models besides X, the process of sending reusable common settings from the personalized settings information of those other vehicle models to the user includes: When the number of personalized settings information for other vehicle models stored in the cloud is one, the reusable general settings items in the personalized settings information of that vehicle model are sent to the user. When there are multiple personalized settings information for other car models stored in the cloud, the reusable common settings items from the personalized settings information of the car model with the latest timestamp will be sent to the user.

8. A vehicle owner file management system based on cloud synchronization, characterized in that, The management system includes: a vehicle-side information collection module and a cloud platform; The vehicle-side information collection module is used to collect user information after login and current vehicle information and send them to the cloud; The cloud is used to determine the vehicle model X of the current vehicle based on the received information of the current vehicle, and to divide the personalized settings information input by the user into reusable general settings and non-reusable settings. If it is determined that the cloud does not store any personalized settings information for the user's vehicle model, the personalized settings information for the user in vehicle model X is obtained and stored in the cloud. If it is determined that the cloud does not store the user's personalized settings information for vehicle model X, but stores the user's personalized settings information for other vehicle models besides vehicle model X, the reusable common settings items from the personalized settings information of the other vehicle models are sent to the user, and the personalized settings information for vehicle model X set by the user based on the received common settings item information is stored in the cloud.

9. An electronic device, characterized in that, The system includes a memory and a processor, wherein the processor is used to execute computer management programs stored in the memory to implement the steps of the cloud-synchronized vehicle owner file management method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, It stores a computer management program, which, when executed by a processor, implements the steps of the cloud-based vehicle owner file management method as described in any one of claims 1-7.

Images