ECU version management method

Abstract

The present invention discloses an ECU version management method, which is applied to an upgrade path management library and includes: obtaining new vehicle baseline version basic information of a specified vehicle model; adding the ECU version basic information of the new ECU version to a target ECU version list; updating the ECU version upgrade information of the old ECU version according to the ECU version upgrade information, ECU version upgrade type and differential file path of the old ECU version in the target ECU version list; obtaining the vehicle baseline version number of the new vehicle baseline version, and updating the vehicle baseline version reference information of the latest ECU version in each ECU version list of the ECU version summary table according to the vehicle baseline version number of the new vehicle baseline version and the vehicle version upgrade type of the new vehicle baseline version; determining the new vehicle baseline version according to the latest ECU version in each ECU version list, the vehicle version upgrade type of the new vehicle baseline version and the vehicle baseline version number of the new vehicle baseline version, and adding the new vehicle baseline version to the vehicle baseline version list corresponding to the specified vehicle model.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to an ECU version management method. Background Art

[0002] With the advancement of the new four trends of automobiles, namely, electrification, networking, intelligence, and sharing, the degree of electrification is getting higher and higher, and the complexity of automobile software is also increasing. It is difficult to provide users with the best experience by only upgrading through 4S stores to repair software faults and update personalized customization needs. Therefore, OTA upgrade has become a trend in automobile development. The most important and most upgraded component in automobiles is ECU (Electronic Control Unit). ECU is a controller used to control a certain part of the vehicle system. After the whole vehicle product is launched on the market, it will be necessary to upgrade the ECU software for various reasons to update and correct problems. In this field, the process of upgrading the software in ECU is referred to as ECU upgrade. However, at present, a car often includes multiple types of ECUs to control different parts. The update time of different types of ECU software versions (hereinafter referred to as ECU versions) may be different, resulting in different version levels of different types of ECU versions in the same time period, which makes it increasingly difficult to manage ECU versions efficiently and accurately. Summary of the invention

[0003] The embodiment of the present invention provides an ECU version management method, which can manage ECU versions efficiently and accurately.

[0004] The specific technical solutions are as follows:

[0005] In a first aspect, an embodiment of the present invention provides an ECU version management method, the method is used to upgrade a path management library, the method comprising:

[0006] Get the new vehicle baseline version basic information of the specified vehicle model, wherein the new vehicle baseline version basic information includes the ECU version basic information of the new ECU version of at least one electronic control unit ECU type, the differential file path between the new ECU version and the old ECU version of the same ECU type, and the vehicle version upgrade type of the new vehicle baseline version, wherein the ECU version basic information includes the ECU type, ECU version number, original image file path, and ECU version upgrade type;

[0007] Add the ECU version basic information of the new ECU version to the target ECU version list, wherein the target ECU version list is the ECU version list of the ECU type corresponding to the new ECU version in the ECU version summary table corresponding to the specified vehicle model, the ECU version summary table includes the ECU version list of all ECU types included in the specified vehicle model, each ECU version list includes different ECU versions of the same ECU type, each ECU version includes ECU version basic information, ECU version upgrade information, vehicle baseline version reference information, the ECU version upgrade information is the reference information for controlling each ECU version to be upgraded according to the ECU version upgrade type, and the vehicle baseline version reference information is the reference information for controlling each ECU version to be upgraded according to the vehicle baseline version upgrade type;

[0008] According to the ECU version upgrade information, ECU version upgrade type and the differential file path of the old ECU version in the target ECU version list, the ECU version upgrade information of the old ECU version is updated;

[0009] Obtaining the vehicle baseline version number of the new vehicle baseline version, and updating the vehicle baseline version reference information of the latest ECU version in each ECU version list of the ECU version summary table according to the vehicle baseline version number of the new vehicle baseline version and the vehicle version upgrade type of the new vehicle baseline version;

[0010] The new vehicle baseline version is determined according to the latest ECU version in the ECU version lists, the vehicle version upgrade type of the new vehicle baseline version and the vehicle baseline version number of the new vehicle baseline version, and the new vehicle baseline version is added to the vehicle baseline version list corresponding to the specified vehicle model, wherein the vehicle baseline version list includes different vehicle baseline versions of the specified vehicle model, each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type.

[0011] In one embodiment, the vehicle version upgrade type and the ECU version upgrade type both include whether the ECU version upgrade information can be skipped or not, including a target ECU version number and a differential information table, wherein the target ECU version number is an ECU version number determined according to the ECU version upgrade type so that each ECU version can be successfully upgraded to, and the differential information table includes the ECU version number of the ECU upgrade version corresponding to each ECU version and the differential file path between each ECU version and the ECU upgrade version, and the ECU upgrade version is an ECU version with an ECU version level higher than that of each ECU version, and according to the ECU version upgrade information, ECU version upgrade type and differential file path of the old ECU version in the target ECU version list, the ECU version upgrade information of the old ECU version is updated, including:

[0012] Determine whether the target ECU version number of the old ECU version to be updated in the target ECU version list is empty;

[0013] If it is empty, the ECU version number of the new ECU version is used as the target ECU version number of the old ECU version to be updated;

[0014] If it is not empty, determine whether the ECU version upgrade type in the ECU version corresponding to the target ECU version number of the old ECU version to be updated in the target ECU version list is skippable; if it is skippable, change the target ECU version number of the old ECU version to be updated to the ECU version number of the new ECU version;

[0015] The ECU version number of the new ECU version of the same ECU type and the differential file path between the new ECU version and each old ECU version are added to the differential information table of each old ECU version in the target ECU version list.

[0016] In one implementation, the vehicle baseline version reference information includes a target vehicle baseline version serial number and a vehicle baseline version number list, wherein the target vehicle baseline version serial number is the vehicle baseline version serial number of the latest vehicle baseline version in the vehicle baseline version to which each ECU version belongs, and the vehicle baseline version number list includes all vehicle baseline version numbers of the vehicle version upgrade type that cannot be skipped in the vehicle baseline version to which each ECU version belongs, and according to the vehicle baseline version number of the new vehicle baseline version and the vehicle version upgrade type of the new vehicle baseline version, the vehicle baseline version reference information of the latest ECU version in each ECU version list of the ECU version summary table is updated, including:

[0017] Update the target vehicle baseline version serial number of the latest ECU version in each ECU version list in the ECU version summary table to the vehicle baseline version number of the new vehicle baseline version;

[0018] When the vehicle version upgrade type of the new vehicle baseline version is non-skippable, the vehicle version upgrade type of the new vehicle baseline version is added to the vehicle baseline version number list of the latest ECU version in the ECU version lists.

[0019] In one embodiment, the method further comprises:

[0020] Obtain the vehicle baseline version to be modified and the vehicle version upgrade type to be modified;

[0021] Modify the vehicle version upgrade type of the vehicle baseline version to be modified in the vehicle baseline version list to the modified vehicle version upgrade type;

[0022] For the ECU version to be modified in the ECU version list corresponding to the vehicle baseline version to be modified, if the upgrade type of the modified vehicle version is non-skippable and the vehicle baseline version number list of the ECU version to be modified is not empty, then the ECU version upgrade type of the ECU version to be modified is kept as non-skippable, and the vehicle baseline version number of the vehicle baseline version to be modified is added to the vehicle baseline version number list of the ECU version to be modified;

[0023] If the modified vehicle version upgrade type is non-skippable and the vehicle baseline version number list of the ECU version to be modified is empty, then the ECU version upgrade type of the ECU version to be modified is modified to non-skippable, and if the target ECU version number of the ECU version to be modified is not empty, then determine the ECU version in the ECU version list where the ECU version to be modified is located, using the ECU version number of the ECU version with a higher ECU version level than the ECU version to be modified as the target ECU version number, and modify the target ECU version number of the determined ECU version to the ECU version number of the ECU version to be modified, and add the vehicle baseline version number of the vehicle baseline version to be modified to the vehicle baseline version number list of the ECU version to be modified;

[0024] If the modified vehicle version upgrade type is skippable, the vehicle baseline version number of the to-be-modified vehicle baseline version is deleted from the vehicle baseline version number list of the to-be-modified ECU version, and if the modified vehicle baseline version number list changes from non-empty to empty, the ECU version upgrade type of the to-be-modified ECU version is modified to skippable, and if the target ECU version number of the to-be-modified ECU version is not empty, then the ECU version in the ECU version list where the to-be-modified ECU version is located is determined with the ECU version number of the to-be-modified ECU version as the target ECU version number, and the target ECU version number of the determined ECU version is modified to the ECU version number of the ECU version whose ECU version upgrade type is non-skippable for the first time in the ECU version with an ECU version level higher than that of the to-be-modified ECU version.

[0025] In one embodiment, the method further comprises:

[0026] Obtain the ECU type to be upgraded and the ECU version number to be upgraded in the ECU version to be upgraded corresponding to all ECU types in the vehicle to be upgraded, wherein the ECU type to be upgraded is the ECU type included in the ECU version to be upgraded, and the ECU version number to be upgraded is the ECU version number included in the ECU version to be upgraded;

[0027] If the ECU versions to be upgraded corresponding to all ECU types belong to the same vehicle baseline version, then according to the ECU type to be upgraded and the ECU version number to be upgraded, the ECU version to be upgraded is searched from the ECU version summary table corresponding to the vehicle to be upgraded;

[0028] After all ECU versions to be upgraded are found, a target ECU version to be upgraded corresponding to the target vehicle baseline version number with the lowest vehicle version level is selected from all ECU versions to be upgraded;

[0029] Using the differential file path corresponding to the target ECU version number of the target ECU version to be upgraded stored in the differential information table of the target ECU version to be upgraded as the upgrade path of the target ECU version to be upgraded, and using the original image file path of the target ECU version to be upgraded as the rollback path;

[0030] The ECU type, upgrade path and rollback path corresponding to the target ECU version to be upgraded are sent to the vehicle to be upgraded, so that the vehicle to be upgraded upgrades the target ECU version to be upgraded according to the upgrade path and the rollback path.

[0031] In one embodiment, after searching the ECU version to be upgraded from the ECU version table corresponding to the vehicle to be upgraded according to the ECU type to be upgraded and the ECU version number to be upgraded, the method further includes:

[0032] If at least one ECU version to be upgraded is not found, a warning message indicating that the upgrade is impossible is sent to the vehicle to be upgraded.

[0033] In one embodiment, the method further comprises:

[0034] If there are at least two vehicle baseline versions to which the ECU versions to be upgraded corresponding to all ECU types belong, then the upgrade path and rollback path corresponding to the ECU versions to be upgraded are sent to the vehicles to be upgraded in sequence according to the vehicle version level order from low to high, until all ECU versions to be upgraded are upgraded to the same vehicle baseline version, and then the step of searching the ECU version to be upgraded from the ECU version master table corresponding to the vehicle to be upgraded according to the ECU type to be upgraded and the ECU version number to be upgraded is executed.

[0035] In one implementation, obtaining basic information of a new vehicle baseline version of a specified vehicle model includes:

[0036] Receive the new vehicle baseline version basic information sent by the vehicle baseline version management system through the operation handle corresponding to the specified vehicle model, wherein the operation handle is a pointer to the storage path of the ECU version master table and the vehicle baseline version list of the specified vehicle model in the upgrade path management library.

[0037] In a second aspect, an embodiment of the present invention provides an ECU version management method, which is applied to a vehicle baseline version management system, and the method includes:

[0038] Receive uploaded ECU version basic information of a new ECU version of at least one ECU type of a specified vehicle model, an ECU version file of the new ECU version, and a vehicle version upgrade type of a new vehicle baseline version, wherein the ECU version basic information includes ECU type, ECU version number, original image file path, and ECU version upgrade type;

[0039] Calculating a differential file between the new ECU version and the old ECU version of the same ECU type according to the ECU version file of the new ECU version and the ECU version file of the old ECU version of the same ECU type, and determining a differential file path between the new ECU version and the old ECU version of the same ECU type based on the differential file;

[0040] The ECU version basic information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version are sent to the upgrade path management library, so that the upgrade path management library updates the ECU version summary table and the vehicle baseline version list corresponding to the specified vehicle model according to at least one of the ECU version basic information of the new ECU version, the differential file path and the vehicle version upgrade type of the new vehicle baseline version, wherein the ECU version summary table includes the ECU version list of all ECU types included in the specified vehicle model, each ECU version list includes different ECU versions of the same ECU type, each ECU version includes ECU version basic information, ECU version upgrade information, and vehicle baseline version reference information, the ECU version upgrade information is reference information for controlling each ECU version to be upgraded according to the ECU version upgrade type, the vehicle baseline version reference information is reference information for controlling each ECU version to be upgraded according to the vehicle baseline version upgrade type, the vehicle baseline version list includes different vehicle baseline versions of the specified vehicle model, each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type.

[0041] In one embodiment, before receiving uploaded ECU version basic information of a new ECU version of at least one ECU type of a specified vehicle model, an ECU version file of a new ECU version, and a vehicle version upgrade type of a new vehicle baseline version, the method further includes: obtaining a data file of the specified vehicle model, wherein the data file is a serialized string of a storage path of a total list of ECU versions of the specified vehicle model and a list of vehicle baseline versions in an upgrade path management library, deserializing the data file to obtain the storage path, and generating an operation handle of the specified vehicle model according to the storage path, wherein the operation handle is a pointer to a storage path of a total list of ECU versions of the specified vehicle model and a list of vehicle baseline versions in the upgrade path management library;

[0042] The ECU version basic information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version are sent to the upgrade path management library, including: sending the ECU version basic information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version to the upgrade path management library through the operation handle.

[0043] In a third aspect, an embodiment of the present invention provides an ECU version management device, the device is used to upgrade a path management library, and the device includes:

[0044] A first acquisition unit is used to acquire basic information of a new vehicle baseline version of a specified vehicle model, wherein the basic information of the new vehicle baseline version includes basic information of an ECU version of a new ECU version of at least one electronic control unit ECU type, a differential file path between the new ECU version and an old ECU version of the same ECU type, and a vehicle version upgrade type of the new vehicle baseline version, wherein the basic information of the ECU version includes an ECU type, an ECU version number, an original image file path, and an ECU version upgrade type;

[0045] A first adding unit is used to add the ECU version basic information of the new ECU version to a target ECU version list, wherein the target ECU version list is an ECU version list of the ECU type corresponding to the new ECU version in the ECU version summary table corresponding to the specified vehicle model, the ECU version summary table includes an ECU version list of all ECU types included in the specified vehicle model, each ECU version list includes different ECU versions of the same ECU type, each ECU version includes ECU version basic information, ECU version upgrade information, and vehicle baseline version reference information, the ECU version upgrade information is reference information for controlling each ECU version to be upgraded according to the ECU version upgrade type, and the vehicle baseline version reference information is reference information for controlling each ECU version to be upgraded according to the vehicle baseline version upgrade type;

[0046] A first updating unit, configured to update the ECU version upgrade information of the old ECU version according to the ECU version upgrade information, the ECU version upgrade type and the differential file path of the old ECU version in the target ECU version list;

[0047] A second acquisition unit is used to acquire a vehicle baseline version number of the new vehicle baseline version;

[0048] A second updating unit is used to update the vehicle baseline version reference information of the latest ECU version in each ECU version list of the ECU version summary table according to the vehicle baseline version number of the new vehicle baseline version and the vehicle version upgrade type of the new vehicle baseline version;

[0049] The second adding unit is used to determine the new vehicle baseline version according to the latest ECU version in the ECU version lists, the vehicle version upgrade type of the new vehicle baseline version and the vehicle baseline version number of the new vehicle baseline version, and add the new vehicle baseline version to the vehicle baseline version list corresponding to the specified vehicle model, wherein the vehicle baseline version list includes different vehicle baseline versions of the specified vehicle model, each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type.

[0050] In one implementation, the first updating unit includes:

[0051] A first judgment module is used for, when both the vehicle version upgrade type and the ECU version upgrade type include skippable or non-skippable, the ECU version upgrade information includes a target ECU version number and a differential information table, the target ECU version number is an ECU version number determined according to the ECU version upgrade type so that each ECU version can be successfully upgraded to, the differential information table includes the ECU version number of the ECU upgrade version corresponding to each ECU version and the differential file path between each ECU version and the ECU upgrade version, and when the ECU upgrade version is an ECU version with a higher ECU version level than each ECU version, judging whether the target ECU version number of the old ECU version to be updated in the target ECU version list is empty;

[0052] A first updating module, configured to use the ECU version number of the new ECU version as the target ECU version number of the old ECU version to be updated when the judgment result is empty;

[0053] The second judgment module is used to judge whether the ECU version upgrade type in the ECU version corresponding to the target ECU version number of the old ECU version to be updated in the target ECU version list is skippable when the judgment result is not empty;

[0054] A second updating module is used for changing the target ECU version number of the old ECU version to be updated to the ECU version number of the new ECU version when the judgment result is that it can be skipped;

[0055] An adding module is used to add the ECU version number of the new ECU version of the same ECU type and the differential file path between the new ECU version and each old ECU version in the differential information table of each old ECU version in the target ECU version list.

[0056] In one implementation, the second updating unit includes:

[0057] A third updating module is used for updating the target vehicle baseline version serial number of the latest ECU version in the list of each ECU version in the ECU version summary table to the vehicle baseline version number of the new vehicle baseline version, when the vehicle baseline version reference information includes a target vehicle baseline version serial number and a vehicle baseline version number list, the target vehicle baseline version serial number is the vehicle baseline version serial number of the latest vehicle baseline version in the vehicle baseline version to which each ECU version belongs, and the vehicle baseline version number list includes all vehicle baseline version numbers of the vehicle version upgrade type that cannot be skipped in the vehicle baseline version to which each ECU version belongs;

[0058] An adding module is used to add the vehicle version upgrade type of the new vehicle baseline version to the vehicle baseline version number list of the latest ECU version in the ECU version list when the vehicle version upgrade type of the new vehicle baseline version is non-skippable.

[0059] In one embodiment, the device further comprises:

[0060] A third obtaining unit is used to obtain the vehicle baseline version to be modified and the modified vehicle version upgrade type;

[0061] A modification unit, configured to modify the vehicle version upgrade type of the vehicle baseline version to be modified in the vehicle baseline version list to the modified vehicle version upgrade type;

[0062] A third updating unit is used for, for the ECU version to be modified in the ECU version list corresponding to the vehicle baseline version to be modified, if the upgrade type of the modified vehicle version is non-skippable and the vehicle baseline version number list of the ECU version to be modified is not empty, then the ECU version upgrade type of the ECU version to be modified is kept as non-skippable, and the vehicle baseline version number of the vehicle baseline version to be modified is added to the vehicle baseline version number list of the ECU version to be modified;

[0063] a fourth updating unit, for, when the modified vehicle version upgrade type is non-skippable and the vehicle baseline version number list of the ECU version to be modified is empty, modifying the ECU version upgrade type of the ECU version to be modified to non-skippable, and if the target ECU version number of the ECU version to be modified is not empty, determining an ECU version in the ECU version list where the ECU version to be modified is located, with the ECU version number of an ECU version with a higher ECU version level than the ECU version to be modified as the target ECU version number, modifying the target ECU version number of the determined ECU version to the ECU version number of the ECU version to be modified, and adding the vehicle baseline version number of the vehicle baseline version to be modified to the vehicle baseline version number list of the ECU version to be modified;

[0064] The fifth updating unit is used to delete the vehicle baseline version number of the to-be-modified vehicle baseline version from the vehicle baseline version number list of the to-be-modified ECU version when the modified vehicle version upgrade type is skippable, and if the modified vehicle baseline version number list changes from non-empty to empty, modify the ECU version upgrade type of the to-be-modified ECU version to skippable, and if the target ECU version number of the to-be-modified ECU version is not empty, determine the ECU version in the ECU version list where the to-be-modified ECU version is located that uses the ECU version number of the to-be-modified ECU version as the target ECU version number, and modify the target ECU version number of the determined ECU version to the ECU version number of the ECU version whose ECU version upgrade type is non-skippable for the first time among the ECU versions with ECU version levels higher than the to-be-modified ECU version.

[0065] In one embodiment, the device further comprises:

[0066] a fourth acquisition unit, configured to acquire the ECU type to be upgraded and the ECU version number to be upgraded in the ECU version to be upgraded corresponding to all ECU types in the vehicle to be upgraded, wherein the ECU type to be upgraded is the ECU type included in the ECU version to be upgraded, and the ECU version number to be upgraded is the ECU version number included in the ECU version to be upgraded;

[0067] A search unit, configured to search for the ECU version to be upgraded from the ECU version master table corresponding to the vehicle to be upgraded according to the ECU type to be upgraded and the ECU version number to be upgraded when the ECU versions to be upgraded corresponding to all ECU types belong to the same vehicle baseline version;

[0068] A selection unit is used to select a target ECU version to be upgraded corresponding to a target vehicle baseline version number with the lowest vehicle version level from among all the ECU versions to be upgraded after finding all the ECU versions to be upgraded;

[0069] a path determination unit, configured to use the differential file path corresponding to the target ECU version number of the target ECU version to be upgraded stored in the differential information table of the target ECU version to be upgraded as the upgrade path of the target ECU version to be upgraded, and use the original image file path of the target ECU version to be upgraded as the rollback path;

[0070] The first sending unit is used to send the ECU type, upgrade path and rollback path corresponding to the target ECU version to be upgraded to the vehicle to be upgraded, so that the vehicle to be upgraded upgrades the target ECU version to be upgraded according to the upgrade path and the rollback path.

[0071] In one embodiment, the device further comprises:

[0072] The second sending unit is used to search for the ECU version to be upgraded from the ECU version summary table corresponding to the vehicle to be upgraded according to the ECU type to be upgraded and the ECU version number to be upgraded. If at least one ECU version to be upgraded is not found, a warning prompt message indicating that the upgrade cannot be performed is sent to the vehicle to be upgraded.

[0073] In one embodiment, the device further comprises:

[0074] The third sending unit is used to send the upgrade path and rollback path corresponding to the ECU version to be upgraded to the vehicle to be upgraded in sequence according to the vehicle version level order from low to high when there are at least two vehicle baseline versions to which the ECU versions to be upgraded corresponding to all ECU types belong, until all ECU versions to be upgraded are upgraded to the same vehicle baseline version, and then execute the search unit.

[0075] In one embodiment, a first acquisition unit is used to receive the basic information of the new vehicle baseline version sent by the vehicle baseline version management system through the operation handle corresponding to the specified vehicle model, wherein the operation handle is a pointer to the storage path of the ECU version summary table and the vehicle baseline version list of the specified vehicle model in the upgrade path management library.

[0076] In a fourth aspect, an embodiment of the present invention provides an ECU version management device, which is applied to a vehicle baseline version management system, and includes:

[0077] A receiving unit is used to receive uploaded ECU version basic information of a new ECU version of at least one ECU type of a specified vehicle model, an ECU version file of the new ECU version, and a vehicle version upgrade type of a new vehicle baseline version, wherein the ECU version basic information includes ECU type, ECU version number, original image file path, and ECU version upgrade type;

[0078] a calculation unit, configured to calculate a difference file between the new ECU version and the old ECU version of the same ECU type according to the ECU version file of the new ECU version and the ECU version file of the old ECU version of the same ECU type;

[0079] a determining unit, configured to determine a differential file path between the new ECU version and an old ECU version of the same ECU type based on the differential file;

[0080] A sending unit is used to send the ECU version basic information of the new ECU version of the at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version to the upgrade path management library, so that the upgrade path management library updates the ECU version summary table and the vehicle baseline version list corresponding to the specified vehicle model according to at least one of the ECU version basic information of the new ECU version, the differential file path and the vehicle version upgrade type of the new vehicle baseline version, wherein the ECU version summary table includes the ECU version list of all ECU types included in the specified vehicle model, each ECU version list includes different ECU versions of the same ECU type, each ECU version includes the ECU version basic information, ECU version upgrade information, and vehicle baseline version reference information, the ECU version upgrade information is the reference information used to control each ECU version to be upgraded according to the ECU version upgrade type, the vehicle baseline version reference information is the reference information used to control each ECU version to be upgraded according to the vehicle baseline version upgrade type, the vehicle baseline version list includes different vehicle baseline versions of the specified vehicle model, each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type.

[0081] In one embodiment, the device further comprises:

[0082] an acquisition unit, used for acquiring a data file of the specified vehicle model before receiving uploaded ECU version basic information of a new ECU version of at least one ECU type of the specified vehicle model, an ECU version file of the new ECU version, and a vehicle version upgrade type of a new vehicle baseline version, wherein the data file is a serialized string of a storage path of a total table of ECU versions of the specified vehicle model and a list of vehicle baseline versions in an upgrade path management library, deserializing the data file to obtain the storage path, and generating an operation handle of the specified vehicle model according to the storage path, wherein the operation handle is a pointer for pointing to a storage path of a total table of ECU versions of the specified vehicle model and a list of vehicle baseline versions in the upgrade path management library;

[0083] The sending unit is used to send the ECU version basic information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version to the upgrade path management library through the operation handle.

[0084] In a fifth aspect, an embodiment of the present invention provides a storage medium having executable instructions stored thereon, which, when executed by a processor, enables the processor to implement the method described in any one of the embodiments of the first aspect or the second aspect.

[0085] In a sixth aspect, an embodiment of the present invention provides an electronic device, including:

[0086] one or more processors;

[0087] a storage device for storing one or more programs,

[0088] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the first aspect or the second aspect.

[0089] It can be seen from the above content that the ECU version management method provided by the embodiment of the present invention can, after obtaining the new vehicle baseline version basic information of the specified vehicle model, first add the ECU version basic information of the new ECU version in the new vehicle baseline version basic information to the target ECU version list (that is, the ECU version list of the ECU type corresponding to the new ECU version in the ECU version summary table corresponding to the specified vehicle model), and then update the ECU version upgrade information of the old ECU version according to the ECU version upgrade information, ECU version upgrade type and differential file path of the old ECU version in the target ECU version list, and then obtain the vehicle baseline version number of the new vehicle baseline version, and update the vehicle baseline version reference information of the latest ECU version in each ECU version list of the ECU version summary table according to the vehicle baseline version number of the new vehicle baseline version and the vehicle version upgrade type of the new vehicle baseline version, and finally determine the new vehicle baseline version according to the latest ECU version in each ECU version list, the vehicle version upgrade type of the new vehicle baseline version and the vehicle baseline version number of the new vehicle baseline version, and add the new vehicle baseline version to the vehicle baseline version list corresponding to the specified vehicle model. It can be seen that the embodiment of the present invention organizes the relevant information of all ECU versions of a vehicle model into an ECU version summary table and a vehicle baseline version list. When a new vehicle baseline version needs to be added, the ECU version summary table and the vehicle baseline version list are updated, thereby improving the management efficiency and accuracy of ECU versions.

[0090] The embodiments of the present invention can also achieve at least the following technical effects:

[0091] 1. When the vehicle version upgrade type of a vehicle baseline version needs to be modified, the embodiment of the present invention can efficiently and accurately modify and update the ECU version summary table and the vehicle baseline version list.

[0092] 2. In the embodiment of the present invention, the vehicle can report the information related to the currently installed ECU version to the server through OTA technology. The server can determine whether the ECU version of the vehicle needs to be upgraded based on the information reported by the vehicle, and when an upgrade is required, send the upgrade path and rollback path to the vehicle so that the vehicle can be upgraded to the existing vehicle baseline version.

[0093] 3. When the vehicle is currently in an intermediate version of the vehicle, the embodiment of the present invention can allow the vehicle to be upgraded multiple times by issuing upgrade tasks multiple times until it is upgraded to a usable vehicle baseline version.

[0094] 4. The embodiment of the present invention can divide the server or server cluster into two parts: a vehicle baseline version management system and an upgrade path management library. The vehicle baseline version management system is used to provide the upgrade path management library with new vehicle baseline version basic information through human-computer interaction with the administrator, and to provide the upgrade path management library with the ECU version of each ECU type in the vehicle through interaction with the vehicle. The upgrade path management library is used to update the ECU version master table and the vehicle baseline version list through the new vehicle baseline version basic information provided by the vehicle baseline version management system, and to provide the vehicle with the upgrade path and rollback path required for ECU version upgrade through the ECU version of each ECU type in the vehicle. It can be seen that the implementation of the present invention can further improve the efficiency and accuracy of ECU version management through the division of labor and cooperation between the vehicle baseline version management system and the upgrade path management library.

[0095] Of course, it is not necessary to achieve all of the advantages described above at the same time to implement any product or method of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0096] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative work.

[0097] Figure 1 A schematic diagram of the structure of an ECU version management system provided by an embodiment of the present invention;

[0098] Figure 2 A flowchart of an ECU version management method provided by an embodiment of the present invention;

[0099] Figure 3 An example diagram of an ECU version and a vehicle baseline version provided by an embodiment of the present invention;

[0100] Figure 4 A flowchart of another ECU version management method provided by an embodiment of the present invention;

[0101] Figure 5 A flowchart of another ECU version management method provided by an embodiment of the present invention;

[0102] Figure 6 A flowchart of another ECU version management method provided by an embodiment of the present invention;

[0103] Figure 7 A schematic diagram of a process for adding a new vehicle baseline version provided by an embodiment of the present invention;

[0104] Figure 8 A block diagram of a device for managing ECU versions provided by an embodiment of the present invention;

[0105] Fig. 9 A block diagram of another ECU version management device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0106] The following will be combined with the accompanying drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0107] It should be noted that the terms "including" and "having" and any variations thereof in the embodiments of the present invention and the accompanying drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.

[0108] The embodiment of the present invention provides an ECU version management system, such as Figure 1 As shown, the ECU version management system includes a vehicle 11, a vehicle baseline version management system 12 and an upgrade path management library 13. The vehicle baseline version management system 12 and the upgrade path management library 13 can be located on the same server or on different servers in a server cluster. The vehicle baseline version management system 12 is used to provide the upgrade path management library 13 with new vehicle baseline version basic information (see the following embodiment for details) through human-computer interaction with the administrator, and to provide the upgrade path management library 13 with the ECU version of each ECU type in the vehicle 11 through interaction with the vehicle 11. The upgrade path management library 13 is used to update the ECU version master table and the vehicle baseline version list through the new vehicle baseline version basic information provided by the vehicle baseline version management system 12, query the upgrade path and rollback path through the ECU version of each ECU type in the vehicle 11, and provide the vehicle 11 with the upgrade path and rollback path required for ECU version upgrade through the vehicle baseline version management system 12.

[0109] The following describes in detail the methods applied to the upgrade path management library and the vehicle baseline version management system respectively.

[0110] Figure 2A flowchart of an ECU version management method provided by an embodiment of the present invention is provided. The method is applied to an upgrade path management library. The method may include the following steps:

[0111] S100: Obtain basic information of a new vehicle baseline version of a specified vehicle model.

[0112] The basic information of the new vehicle baseline version includes the basic ECU version information of a new ECU version of at least one ECU type, the differential file path between the new ECU version and the old ECU version of the same ECU type, and the vehicle version upgrade type of the new vehicle baseline version. The basic ECU version information includes the ECU type, ECU version number, original image file path, and ECU version upgrade type. The vehicle version upgrade type and the ECU version upgrade type both include skippable or non-skippable.

[0113] The specific implementation method of obtaining the new vehicle baseline version basic information of the specified vehicle model includes: receiving the new vehicle baseline version basic information of the specified vehicle model sent by the vehicle baseline version management system through the operation handle corresponding to the specified vehicle model, wherein the operation handle is a pointer to the storage path of the ECU version summary table and the vehicle baseline version list of the specified vehicle model in the upgrade path management library. The meaning of the ECU version summary table and the vehicle baseline version list is detailed in the detailed explanation of steps S110 and S140.

[0114] The vehicle version upgrade type is determined by the administrator, and the ECU version upgrade type is determined based on the vehicle version upgrade type. When a vehicle baseline version is upgraded, not all ECU versions contained in it will be upgraded, and only some ECU versions may be upgraded. Therefore, there may be multiple vehicle baseline versions belonging to the same ECU version. For an ECU version, as long as there is a vehicle baseline version in the vehicle baseline version to which the vehicle version upgrade type is non-skippable, then the ECU version upgrade type of this ECU version is non-skippable. Only when the vehicle version upgrade types of all vehicle baseline versions to which it belongs are skippable, the ECU version upgrade type of this ECU version is skippable.

[0115] It should be added that, when the designated vehicle model is a new model, the basic information of the new vehicle baseline version includes the ECU version basic information of the new ECU version of at least one ECU type and the vehicle version upgrade type of the new vehicle baseline version, but does not include the differential file path because there is no old ECU version of the new model.

[0116] S110: Add the ECU version basic information of the new ECU version to the target ECU version list.

[0117] The target ECU version list is an ECU version list of the ECU type corresponding to the new ECU version in the ECU version summary table corresponding to the specified vehicle model. The ECU version summary table corresponding to the specified vehicle model includes an ECU version list of all ECU types included in the specified vehicle model. Each ECU version list includes different ECU versions of the same ECU type. Each ECU version includes ECU version basic information, ECU version upgrade information, and vehicle baseline version reference information. The ECU version upgrade information is reference information for controlling each ECU version to be upgraded according to the ECU version upgrade type. The vehicle baseline version reference information is reference information for controlling each ECU version to be upgraded according to the vehicle baseline version upgrade type. The ECU version upgrade information in each ECU version includes a target ECU version number and a differential information table. The target ECU version number is an ECU version number determined according to the ECU version upgrade type so that each ECU version can be successfully upgraded to. The differential information table includes the ECU version number of the ECU upgrade version corresponding to each ECU version and the differential file path between each ECU version and the ECU upgrade version. The ECU upgrade version corresponding to each ECU version is an ECU version with a higher ECU version level than each ECU version. The differential information table can be specifically a Delta hash table, and each differential information can be called a Delta. The vehicle baseline version reference information in each ECU version includes a target vehicle baseline version serial number and a vehicle baseline version number list, wherein the target vehicle baseline version serial number is the vehicle baseline version serial number of the latest vehicle baseline version in the vehicle baseline version to which each ECU version belongs, and the vehicle baseline version number list includes all vehicle baseline version numbers of the vehicle version upgrade type that cannot be skipped in the vehicle baseline version to which each ECU version belongs.

[0118] When the designated vehicle model is a new vehicle model, it is necessary to create an ECU version summary table and a vehicle baseline version list for the new vehicle model, and add the ECU version basic information of the new ECU version to the corresponding ECU version list in the newly created ECU version summary table. The vehicle baseline version list includes different vehicle baseline versions of the designated vehicle model, each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type.

[0119] For example, Figure 3As shown, it is assumed that the specified vehicle model includes three ECU types, A, B and C, and the old ECU version of ECU type A includes two, and the ECU version numbers from low to high are A1 and A2 respectively; the old ECU version of ECU type B includes three, and the ECU version numbers from low to high are B1, B2, and B3 respectively; the old ECU version of ECU type C includes two, and the ECU version numbers from low to high are C1 and C2 respectively; the existing vehicle baseline versions include three, and the vehicle baseline version numbers from low to high are S1, S2, and S3 respectively, wherein each vehicle baseline version includes 3 ECU versions of different ECU types, the vehicle baseline version S1 includes ECU version A1, ECU version B1 and ECU version C1, the vehicle baseline version S2 includes ECU version A1, ECU version B2 and ECU version C1, and the vehicle baseline version S3 includes ECU version A2, ECU version B3 and ECU version C2. The ECU version summary table includes three ECU version lists, ECU version list 1 includes two ECU versions of ECU type A, ECU version list 2 includes three ECU versions of ECU type B, and ECU version list 3 includes two ECU versions of ECU type C. It can be seen that the ECU version list includes different ECU versions of the same ECU type, and the vehicle baseline version list includes ECU versions of different ECU types in each vehicle baseline version.

[0120] The vehicle baseline version S4 is the new vehicle baseline version to be generated. The basic information of the new vehicle baseline version obtained includes the ECU version basic information of the new ECU version of ECU type A and C, the differential file path between the new ECU version and the old ECU version of the same ECU type, and the vehicle version upgrade type of the new vehicle baseline version. Among them, the new ECU versions are ECU version A3 and ECU version C3.

[0121] The following uses the vehicle baseline version list and ECU version list 1 as examples to explain the vehicle baseline version and ECU version respectively:

[0122] As shown in Table 1, the vehicle baseline version list includes three vehicle baseline versions, each of which includes a vehicle baseline version number, a vehicle version upgrade type, an ECU type, and an ECU version number.

[0123] Table 1

[0124]

[0125] As shown in Table 2, ECU version list 1 is the ECU version list corresponding to ECU type A, including 2 ECU versions, each ECU version includes ECU type, ECU version number, original image file path, ECU version upgrade type, target vehicle baseline version number, vehicle baseline version number list, target ECU version number and differential information table, and the differential information table includes the ECU version number and differential file path of the ECU upgrade version. Among them, the ECU version upgrade type is determined according to Table 1. For example, the vehicle baseline versions to which ECU version A1 (i.e., the ECU version with ECU version number A1) belongs are S1 and S2. The vehicle version upgrade type of S1 is skippable, and the vehicle version upgrade type of S2 is non-skippable, so the ECU version upgrade type of ECU version A1 is non-skippable. Since the vehicle baseline version number list is a list of vehicle baseline version numbers whose vehicle version upgrade type is non-skippable, the vehicle baseline version number lists of these two ECU versions are S2 and empty respectively. The target vehicle baseline version number is the vehicle baseline version serial number of the latest vehicle baseline version in the vehicle baseline version to which each ECU version belongs, so the target vehicle baseline version numbers of these two ECU versions are S2 and S3 respectively. The target ECU version number is the version number determined according to the ECU version upgrade type so that the ECU version can be successfully upgraded. According to the order of ECU version levels from low to high, the advanced EUC version of ECU version A1 is ECU version A2. Since the ECU version upgrade type of ECU version A2 is skippable but ECU version A2 is the latest ECU version before this update, ECU version A1 can be upgraded to ECU version A2, and the target ECU version number of ECU version A1 is A2. This step S110 can add the ECU version basic information of ECU version A3 to Table 2, so that Table 2 is updated to Table 3. ECU version C3 is the same as ECU version A3, and will not be repeated here.

[0126] Table 2

[0127]

[0128] Table 3

[0129]

[0130] S120: updating the ECU version upgrade information of the old ECU version according to the ECU version upgrade information, ECU version upgrade type and differential file path of the old ECU version in the target ECU version list.

[0131] The specific implementation method of this step includes: judging whether the target ECU version number of the old ECU version to be updated in the target ECU version list is empty; if it is empty, taking the ECU version number of the new ECU version as the target ECU version number of the old ECU version to be updated; if it is not empty, judging whether the ECU version upgrade type in the ECU version corresponding to the target ECU version number of the old ECU version to be updated in the target ECU version list is skippable, if it is skippable, changing the target ECU version number of the old ECU version to be updated to the ECU version number of the new ECU version; adding the ECU version number of the new ECU version of the same ECU type and the differential file path between the new ECU version and each old ECU version in the differential information table of each old ECU version in the target ECU version list. In addition, if the judgment result is non-skippable, the target ECU version number of the old ECU version to be updated remains unchanged.

[0132] Undertake Figure 3 As shown in Table 4, after adding the ECU version basic information of ECU version A3 to Table 2 to obtain Table 3, it is possible to continue to determine whether the target ECU version number of the old ECU version to be updated (ECU version A1 and A2) in Table 3 is empty. If the target ECU version number of ECU version A2 is empty, then the ECU version number A3 of the new ECU version is added to the target ECU version number of ECU version A2. If the target ECU version number of ECU version A1 is not empty, it is further determined whether the ECU version upgrade type in the ECU version corresponding to the target ECU version number A2 of ECU version A1 is skippable. If the result is skippable, then the target ECU version number A2 of ECU version A1 is changed to the ECU version number of the new ECU version, i.e., A3. After the target ECU version number is updated, the differential information between ECU version A3 and ECU versions A1 and A2 can be added to the differential information table.

[0133] Table 4

[0134]

[0135] S130: Obtain the vehicle baseline version number of the new vehicle baseline version, and update the vehicle baseline version reference information of the latest ECU version in each ECU version list of the ECU version summary table according to the vehicle baseline version number of the new vehicle baseline version and the vehicle version upgrade type of the new vehicle baseline version.

[0136] The vehicle baseline version number of the new vehicle baseline version can be generated by the vehicle baseline version management system according to the vehicle baseline version number generation method and then sent to the upgrade path management library, or it can be generated by the upgrade path management library according to the vehicle baseline version number generation method after receiving the new vehicle baseline version basic information. The vehicle baseline version number generation method can be determined according to actual needs, for example, 1 can be added to the old vehicle baseline version number.

[0137] Update the target vehicle baseline version serial number of the latest ECU version in each ECU version list of the ECU version summary table corresponding to the specified vehicle model to the vehicle baseline version number of the new vehicle baseline version; when the vehicle version upgrade type of the new vehicle baseline version is non-skippable, add the vehicle version upgrade type of the new vehicle baseline version to the vehicle baseline version number list of the latest ECU version in each ECU version list.

[0138] Undertake Figure 3 As in the example of Table 1-4, the latest ECU versions in the three ECU version lists of ECU types A, B, and C are ECU version A3, ECU version B3, and ECU version C3, respectively. These three ECU versions can be combined into a new vehicle baseline version S4. Then, the target vehicle baseline version serial numbers of these three ECU versions are updated to the vehicle baseline version number S4 of the new vehicle baseline version, and when the vehicle version upgrade type of the new vehicle baseline version is non-skippable, the vehicle version upgrade type of the new vehicle baseline version is added to the vehicle baseline version number list of the latest ECU version in each ECU version list. Taking the ECU version list of ECU type A as an example, assuming that the vehicle version upgrade type of vehicle baseline version S4 is non-skippable, the updated Table 4 becomes Table 5.

[0139] Table 5

[0140]

[0141] S140: Determine the new vehicle baseline version according to the latest ECU version in the ECU version list, the vehicle version upgrade type of the new vehicle baseline version and the vehicle baseline version number of the new vehicle baseline version, and add the new vehicle baseline version to the vehicle baseline version list corresponding to the specified vehicle model.

[0142] The vehicle baseline version list includes different vehicle baseline versions of the specified vehicle model, and each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type. Figure 3 As shown in the examples in Tables 1-5, after executing this step, the vehicle baseline version list changes from Table 1 to Table 6.

[0143] Table 6

[0144]

[0145] The ECU version management method provided by the embodiment of the present invention can, after obtaining the new vehicle baseline version basic information of the specified vehicle model, first add the ECU version basic information of the new ECU version in the new vehicle baseline version basic information to the target ECU version list (that is, the ECU version list of the ECU type corresponding to the new ECU version in the ECU version summary table corresponding to the specified vehicle model), and then update the ECU version upgrade information of the old ECU version according to the ECU version upgrade information, ECU version upgrade type and differential file path of the old ECU version in the target ECU version list, and then obtain the vehicle baseline version number of the new vehicle baseline version, and update the vehicle baseline version reference information of the latest ECU version in each ECU version list of the ECU version summary table according to the vehicle baseline version number of the new vehicle baseline version and the vehicle version upgrade type of the new vehicle baseline version, and finally determine the new vehicle baseline version according to the latest ECU version in each ECU version list, the vehicle version upgrade type of the new vehicle baseline version and the vehicle baseline version number of the new vehicle baseline version, and add the new vehicle baseline version to the vehicle baseline version list corresponding to the specified vehicle model. It can be seen that the embodiment of the present invention organizes the relevant information of all ECU versions of a vehicle model into an ECU version summary table and a vehicle baseline version list. When a new vehicle baseline version needs to be added, the ECU version summary table and the vehicle baseline version list are updated, thereby improving the management efficiency and accuracy of ECU versions.

[0146] In actual applications, the administrator may modify the vehicle version upgrade type according to the needs, and the vehicle version upgrade type is related to the changes in the relevant information in the ECU version. The scheme for modifying the vehicle version upgrade type is described in detail below. It should be noted that the scheme for modifying the vehicle version upgrade type in the embodiment of the present invention is to modify (or switch) the vehicle version upgrade type from non-skippable to skippable, or from skippable to non-skippable, and does not involve the situation where there is no change before and after the modification. Figure 4 As shown, this method is mainly used for upgrading the path management library, and specifically includes:

[0147] S200: Obtain the vehicle baseline version to be modified of the vehicle version upgrade type to be modified and the modified vehicle version upgrade type.

[0148] The administrator can input the vehicle model of the vehicle version upgrade type to be modified through the vehicle baseline version management system so that the vehicle baseline version management system can obtain the operation handle corresponding to the vehicle model. The administrator also needs to input the information of the vehicle baseline version to be modified of the vehicle version upgrade type to be modified (for example, only a vehicle baseline version number can be input), as well as the modified vehicle version upgrade type, so that the vehicle baseline version management system can send the information of the vehicle baseline version to be modified and the modified vehicle version upgrade type to the upgrade path management library through the operation handle of the vehicle model. Of course, the administrator can also directly specify the information of the vehicle baseline version to be switched on the vehicle version upgrade type switching page, so that the vehicle baseline version management system can switch the current vehicle version upgrade type to another vehicle version upgrade type after finding the specified vehicle baseline version and the current vehicle version upgrade type of the specified vehicle baseline version.

[0149] S210: Modify the vehicle version upgrade type of the vehicle baseline version to be modified in the vehicle baseline version list to the modified vehicle version upgrade type.

[0150] Undertake Figure 3 As in the examples in Tables 1-6, assuming that the vehicle baseline version to be modified is vehicle baseline version S3, its vehicle version upgrade type needs to be changed from skippable to non-skippable, and the modified vehicle baseline version list changes from Table 6 to Table 7.

[0151] Table 7

[0152]

[0153] S220: Determine whether the modified vehicle version upgrade type is non-skippable; if it is non-skippable, execute step S230; if it is skippable, execute step S260.

[0154] S230: Determine whether the vehicle baseline version number list of the ECU version to be modified in the ECU version list corresponding to the vehicle baseline version to be modified is empty; if it is not empty, keep the ECU version upgrade type of the ECU version to be modified as non-skippable, and execute step S240; if it is empty, execute step S250.

[0155] S240: Add the vehicle baseline version number of the to-be-modified vehicle baseline version to the vehicle baseline version number list of the to-be-modified ECU version.

[0156] The ECU version list corresponding to the vehicle baseline version to be modified includes the lists of each ECU version in the ECU version list corresponding to the vehicle baseline version to be modified. The ECU version to be modified includes the various ECU versions included in the vehicle baseline version to be modified, that is, it is necessary to make corresponding modifications to the various ECU versions included in the vehicle baseline version to be modified in the corresponding ECU version list. For example, the vehicle baseline version S3 to be modified includes ECU version A2, ECU version B3 and ECU version C2. Then, it is necessary to determine whether ECU version A2 in the ECU version list of ECU type A, ECU version B3 in the ECU version list of ECU type B, and ECU version C2 in the ECU version list of ECU type C need to be modified. If the modified vehicle version upgrade type is non-skippable and the vehicle baseline version number list of the ECU version to be modified is not empty, it means that before the modification, there is a vehicle baseline version with a vehicle version upgrade type that is non-skippable in the vehicle baseline version to which the ECU version to be modified belongs. Therefore, the ECU version upgrade type of the ECU version to be modified is kept as non-skippable, but the vehicle baseline version number of the vehicle baseline version to be modified needs to be added to the vehicle baseline version number list of the ECU version to be modified.

[0157] S250: Change the ECU version upgrade type of the ECU version to be modified to non-skippable. If the target ECU version number of the ECU version to be modified is not empty, determine the ECU version in the ECU version list where the ECU version to be modified is located, using the ECU version number of an ECU version with a higher ECU version level than the ECU version to be modified as the target ECU version number, and change the target ECU version number of the determined ECU version to the ECU version number of the ECU version to be modified; then execute step S240.

[0158] If the modified vehicle version upgrade type is non-skippable and the vehicle baseline version number list of the ECU version to be modified is empty, it means that before the modification, there was no vehicle baseline version with a vehicle version upgrade type that is non-skippable in the vehicle baseline version to which the ECU version to be modified belongs, but after the modification, there is a vehicle baseline version with a vehicle version upgrade type that is non-skippable, so the ECU version upgrade type of the ECU version to be modified needs to be modified to non-skippable.

[0159] After modifying the ECU version upgrade type of the ECU version to be modified, if the target ECU version number of the ECU version to be modified is not empty, it means that the ECU version to be modified is not the latest ECU version. When the ECU version upgrade type to be modified is skippable, the upgrade target of the ECU version with a lower level than the ECU version to be modified may skip the ECU version to be modified. When the ECU version upgrade type to be modified is modified to non-skippable, the upgrade target of the ECU version with a lower level than the ECU version to be modified cannot skip the ECU version to be modified. Therefore, it is necessary to modify the target ECU version number of the ECU version determined above to the ECU version number of the ECU version to be modified, and add the vehicle baseline version number of the vehicle baseline version to be modified to the vehicle baseline version number list of the ECU version to be modified.

[0160] Undertake Figure 3 As shown in Table 8, the ECU version to be modified includes ECU version A2, and the modified vehicle version upgrade type is non-skippable and the vehicle baseline version number list of ECU version A2 is empty, then the ECU version upgrade type of ECU version A2 is modified to non-skippable. If the target ECU version number of ECU version A2 is not empty, the ECU version number of the ECU version with a higher ECU version level than ECU version A2 (i.e. A3) is used as the ECU version of the target ECU version number, that is, ECU version A1 uses ECU version A3 as the target ECU version number, then the target ECU version number of ECU version A1 needs to be modified from A3 to A2, so that ECU version A1 cannot skip ECU version A2 and upgrade directly to ECU version A3. Finally, the vehicle baseline version number S3 of the vehicle baseline version to be modified is added to the vehicle baseline version number list of ECU version A2.

[0161] It should be added that, according to Table 5, the target ECU version number of the ECU version determined in this step according to "the ECU version number of the ECU version in the ECU version list where the ECU version to be modified is located, with the ECU version number of the ECU version with a higher ECU version level than the ECU version to be modified as the target ECU version number" is generally the same as the target version number of the ECU version to be modified. Therefore, it is also possible to directly search for the ECU version whose target ECU version number is the same as the target version number of the ECU version to be modified as the determined ECU version.

[0162] Table 8

[0163]

[0164] S260: Delete the vehicle baseline version number of the vehicle baseline version to be modified from the vehicle baseline version number list of the ECU version to be modified.

[0165] S270: Determine whether the modified vehicle baseline version number list changes from non-empty to empty; if so, execute step S280; if not, terminate the execution.

[0166] S280: Modify the ECU version upgrade type of the ECU version to be modified to skippable, and if the target ECU version number of the ECU version to be modified is not empty, determine the ECU version in the ECU version list where the ECU version to be modified is located that uses the ECU version number of the ECU version to be modified as the target ECU version number, and modify the target ECU version number of the determined ECU version to the ECU version number of the ECU version whose ECU version upgrade type is non-skippable for the first time among the ECU versions whose ECU version level is higher than that of the ECU version to be modified.

[0167] Since the vehicle baseline version number list is used to store vehicle baseline version numbers whose vehicle version upgrade type is non-skippable, when the modified vehicle version upgrade type is skippable, the vehicle baseline version number of the vehicle baseline version to be modified needs to be deleted from the vehicle baseline version number list of the ECU version to be modified. Since the ECU version upgrade type of the ECU version to be modified is skippable only when all vehicle version upgrade types in the vehicle baseline version to which the ECU version to be modified belongs are skippable, when the modified vehicle baseline version number list changes from non-empty to empty, the ECU version upgrade type of the ECU version to be modified needs to be modified to skippable.

[0168] If the target ECU version number of the ECU version to be modified is not empty, it means that the ECU version to be modified is not the latest version. When the upgrade type of the ECU version to be modified is non-skippable, the upgrade target of the ECU version with a lower level than the ECU version to be modified may be the ECU version to be modified. When the upgrade type of the ECU version to be modified is changed to skippable, the upgrade target of the ECU version with a lower level than the ECU version to be modified can skip the ECU version to be modified and directly upgrade to a higher ECU version. Therefore, it is necessary to modify the target ECU version number of the ECU version determined in step S240 to the ECU version number of the ECU version whose ECU version upgrade type is non-skippable for the first time in the ECU version with a higher ECU version level than the ECU version to be modified. In general, the ECU version number of the ECU version whose ECU version upgrade type is non-skippable for the first time in the ECU version with a higher ECU version level than the ECU version to be modified is also the target ECU version number of the ECU version to be modified, so the target ECU version number of the determined ECU version can also be directly modified to the target ECU version number of the ECU version to be modified.

[0169] For example, it is known that the ECU version levels from low to high are ECU version E1, ECU version E2, ECU version E3, ECU version E4, and ECU version E5, and their ECU version upgrade types are skippable, non-skippable, skippable, non-skippable, and skippable, respectively. The target ECU version number of ECU version E1 is E2, and the ECU versions higher than ECU version E2 are ECU version E3, ECU version E4, and ECU version E5. However, the ECU version upgrade type of ECU version E3 is skippable, and the ECU version upgrade type of ECU version E4 is non-skippable. Therefore, after the ECU version upgrade type of ECU version E2 is changed from non-skippable to skippable, the target ECU version number of ECU version E1 becomes E4, because ECU version 2 and ECU version 3 can be directly skipped for upgrade.

[0170] In one implementation, in order to upgrade the vehicle's ECU in a timely manner, the vehicle can periodically or irregularly send its current ECU version information to the vehicle baseline version management system, so that the vehicle baseline version management system can send the ECU version information to the upgrade path management library, so that the upgrade path management library can provide upgrade information, thereby realizing ECU version upgrade. Figure 5 As shown, the method is mainly applied to the upgrade path management library, and the method includes:

[0171] S300: Obtain the ECU type to be upgraded and the ECU version number to be upgraded in the ECU version to be upgraded corresponding to all ECU types in the vehicle to be upgraded.

[0172] Among them, the ECU type to be upgraded is the ECU type included in the ECU version to be upgraded, and the ECU version number to be upgraded is the ECU version number included in the ECU version to be upgraded. The upgrade path management library can obtain the ECU type to be upgraded and the ECU version number to be upgraded of the vehicle to be upgraded through the vehicle baseline version management system. In addition, all ECU types in the above-mentioned vehicle to be upgraded refer to ECU types with OTA functions, so that the upgrade path and rollback path for upgrading can be downloaded from the vehicle baseline version management system through OTA technology.

[0173] S310: If the ECU versions to be upgraded corresponding to all ECU types belong to the same vehicle baseline version, then according to the ECU type to be upgraded and the ECU version number to be upgraded, the ECU version to be upgraded is searched from the ECU version summary table corresponding to the vehicle to be upgraded.

[0174] If at least one ECU version to be upgraded is not found (such as the ECU type to be upgraded or the ECU version number to be upgraded is not found), it means that the ECU versions currently owned by the vehicle to be upgraded are not all safe, stable and available ECU versions. Therefore, a warning message indicating that the upgrade cannot be performed can be sent to the vehicle to be upgraded through the vehicle baseline version management system. For example, the warning message may be "No upgrade path, including non-existent accessories".

[0175] S320: After all ECU versions to be upgraded are found, a target ECU version to be upgraded corresponding to the target vehicle baseline version number with the lowest vehicle version level is selected from all ECU versions to be upgraded.

[0176] In order to ensure that the upgraded vehicle baseline version is aligned with the existing vehicle baseline version, after obtaining all ECU versions to be upgraded, it is necessary to compare their target vehicle baseline version numbers, and only retain the vehicle baseline version number (one or more) with the lowest corresponding vehicle version level as the target ECU version to be upgraded. The vehicle baseline version number may be in positive order or in reverse order. When it is in positive order,

[0177] S330: Using the differential file path corresponding to the target ECU version number of the target ECU version to be upgraded stored in the differential information table of the target ECU version to be upgraded as the upgrade path of the target ECU version to be upgraded, and using the original image file path of the target ECU version to be upgraded as the rollback path.

[0178] S340: Sending the ECU type, upgrade path, and rollback path corresponding to the target ECU version to be upgraded to the vehicle to be upgraded, so that the vehicle to be upgraded upgrades the target ECU version to be upgraded according to the upgrade path and the rollback path.

[0179] The upgrade path management library can first send the ECU type, upgrade path and rollback path corresponding to the target ECU version to be upgraded to the vehicle baseline version management system, and then the vehicle baseline version management system forwards this information to the vehicle to be upgraded, so that the vehicle to be upgraded can upgrade the target ECU version to be upgraded according to the upgrade path and the rollback path.

[0180] In one embodiment, if there are at least two vehicle baseline versions to which the ECU versions to be upgraded corresponding to all ECU types belong, the upgrade path and rollback path corresponding to the ECU versions to be upgraded are sent to the vehicles to be upgraded in order of the vehicle version levels from low to high, until all ECU versions to be upgraded are upgraded to the same vehicle baseline version, and step S310 is executed. The method for obtaining the upgrade path and rollback path of the ECU versions to be upgraded in this step can be referred to step S330.

[0181] If there are at least two vehicle baseline versions to which the ECU versions to be upgraded corresponding to all the ECU types belong, it means that the target vehicle to be upgraded is in the intermediate version of the vehicle. The intermediate version of the vehicle means that the version information of each ECU of the vehicle to be upgraded cannot be completely matched with the baseline version of the vehicle in any server. For example, some ECU versions belong to the A vehicle baseline version, some ECU versions belong to the B vehicle baseline version, and some ECU versions belong to the C vehicle baseline version. In the embodiment of the present invention, the ECU versions in the non-skippable version usually have functional connections. If upgraded to an intermediate version of the vehicle, it may be functionally unusable. The embodiment of the present invention believes that the available version must be a non-skippable version or the latest version. In this case, according to the method of finding the upgrade path, it may not be possible to achieve a complete match with the available version through a single upgrade. At this time, the server will create multiple upgrade tasks (collect version information after the upgrade is successful and create again) until it is upgraded to an available version. The vehicle engine cannot be started before upgrading to an available version.

[0182] Corresponding to the above method embodiment, the embodiment of the present invention provides a flow chart of an ECU version management method, which is applied to a vehicle baseline version management system, such as Figure 6 and Figure 7 As shown, the method may include the following steps:

[0183] S400: Receive uploaded ECU version basic information of a new ECU version of at least one ECU type of a specified vehicle model, an ECU version file of the new ECU version, and a vehicle version upgrade type of a new vehicle baseline version.

[0184] Among them, the ECU version basic information includes ECU type, ECU version number, original image file path, ECU version upgrade type, and the vehicle version upgrade type and the ECU version upgrade type both include skippable or non-skippable. The ECU version basic information of the new ECU version of at least one ECU type of the specified vehicle model, the ECU version file of the new ECU version, and the vehicle version upgrade type of the new vehicle baseline version can be called the information required for the new vehicle baseline version.

[0185] Before receiving the uploaded ECU version basic information of a new ECU version of at least one ECU type of a specified vehicle model, the ECU version file of the new ECU version and the vehicle version upgrade type of a new vehicle baseline version, it also includes: obtaining a data file of the specified vehicle model, wherein the data file is a serialized string of the storage path of the ECU version master table and the vehicle baseline version list of the specified vehicle model in the upgrade path management library, deserializing the data file to obtain the storage path, and generating an operation handle of the specified vehicle model according to the storage path, wherein the operation handle is a pointer to the storage path of the ECU version master table and the vehicle baseline version list of the specified vehicle model in the upgrade path management library.

[0186] The embodiment of the present invention assumes that vehicles of the same model have the same version history and can use the same data files. Therefore, for a new model, you first need to create a new model in the vehicle baseline version management system, enter the model name and other information, and the vehicle baseline version management system will initialize the data file and operation handle for the model. Maintaining different data files and operation handles for different models is conducive to multiple threads operating on the storage paths of different models at the same time. In addition, the embodiment of the present invention uses a thread lock to ensure the mutual exclusion of adding a new vehicle baseline version and searching for storage paths. The mutex library provided by C++ is used here to implement thread mutual exclusion. When the same operation handle is used in different threads to perform addition or search operations respectively, the thread that performs the operation first can obtain the operation qualification. After the operation is completed, the next thread can obtain the operation qualification and operate, which can avoid data confusion.

[0187] For existing models, the vehicle baseline version management system will read the existing data file to initialize the corresponding operation handle when it starts. During initialization, the data file will be deserialized and the operation handle of the upgrade path will be created. After adding or modifying the vehicle baseline version, the upgrade path will be serialized and stored in the data file. The serialization technology here uses the existing protobuf serialization technology, which can also be replaced by other similar technologies, such as json, xml, etc.

[0188] S410: Calculate the differential file between the new ECU version and the old ECU version of the same ECU type according to the ECU version file of the new ECU version and the ECU version file of the old ECU version of the same ECU type, and determine the differential file path between the new ECU version and the old ECU version of the same ECU type based on the differential file.

[0189] The vehicle baseline version management system stores ECU version files of various ECU versions. When a user uploads the ECU version file of a new ECU version, the differential file between the ECU version file of the new ECU version and the ECU version file of the old ECU version can be calculated, and the differential file can be stored in a designated storage space. The path corresponding to the designated storage space is used as the differential file path between the new ECU version and the old ECU version of the same ECU type.

[0190] S420: Send the ECU version basic information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version to the upgrade path management library, so that the upgrade path management library updates the ECU version summary table and the vehicle baseline version list corresponding to the specified vehicle model according to at least one of the ECU version basic information of the new ECU version, the differential file path and the vehicle version upgrade type of the new vehicle baseline version.

[0191] The basic ECU version information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version are the basic information of the new vehicle baseline version. The ECU version summary table includes the ECU version list of all ECU types included in the specified vehicle model, each ECU version list includes different ECU versions of the same ECU type, each ECU version includes the basic ECU version information, ECU version upgrade information, and vehicle baseline version reference information. The ECU version upgrade information is the reference information used to control each ECU version to be upgraded according to the ECU version upgrade type, and the vehicle baseline version reference information is the reference information used to control each ECU version to be upgraded according to the vehicle baseline version upgrade type. The vehicle baseline version list includes different vehicle baseline versions of the specified vehicle model, and each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type.

[0192] The vehicle baseline version management system can send the ECU version basic information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version to the upgrade path management library through the operation handle. After the upgrade path management library completes adding the new vehicle baseline version, it can feed back the addition result to the vehicle baseline version management system.

[0193] Based on the above method embodiment, another embodiment of the present invention provides an ECU version management device, such as Figure 8 As shown, the device is applied to the upgrade path management library, and the device includes:

[0194] The first acquisition unit 50 is used to acquire the basic information of the new vehicle baseline version of the specified vehicle model, wherein the basic information of the new vehicle baseline version includes the basic information of the ECU version of a new ECU version of at least one electronic control unit ECU type, the differential file path between the new ECU version and the old ECU version of the same ECU type, and the vehicle version upgrade type of the new vehicle baseline version, wherein the basic information of the ECU version includes the ECU type, the ECU version number, the original image file path, and the ECU version upgrade type;

[0195] A first adding unit 51 is used to add the ECU version basic information of the new ECU version to a target ECU version list, wherein the target ECU version list is an ECU version list of the ECU type corresponding to the new ECU version in the ECU version summary table corresponding to the specified vehicle model, the ECU version summary table includes ECU version lists of all ECU types included in the specified vehicle model, each ECU version list includes different ECU versions of the same ECU type, each ECU version includes ECU version basic information, ECU version upgrade information, and vehicle baseline version reference information, the ECU version upgrade information is reference information for controlling each ECU version to be upgraded according to the ECU version upgrade type, and the vehicle baseline version reference information is reference information for controlling each ECU version to be upgraded according to the vehicle baseline version upgrade type;

[0196] A first updating unit 52, configured to update the ECU version upgrade information of the old ECU version according to the ECU version upgrade information, the ECU version upgrade type and the differential file path of the old ECU version in the target ECU version list;

[0197] The second acquisition unit 53 is used to acquire the vehicle baseline version number of the new vehicle baseline version;

[0198] A second updating unit 54 is used to update the vehicle baseline version reference information of the latest ECU version in each ECU version list of the ECU version summary table according to the vehicle baseline version number of the new vehicle baseline version and the vehicle version upgrade type of the new vehicle baseline version;

[0199] The second adding unit 55 is used to determine the new vehicle baseline version according to the latest ECU version in the ECU version lists, the vehicle version upgrade type of the new vehicle baseline version and the vehicle baseline version number of the new vehicle baseline version, and add the new vehicle baseline version to the vehicle baseline version list corresponding to the specified vehicle model, wherein the vehicle baseline version list includes different vehicle baseline versions of the specified vehicle model, each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type.

[0200] In one implementation, the first updating unit 52 includes:

[0201] A first judgment module is used for, when both the vehicle version upgrade type and the ECU version upgrade type include skippable or non-skippable, the ECU version upgrade information includes a target ECU version number and a differential information table, the target ECU version number is an ECU version number determined according to the ECU version upgrade type so that each ECU version can be successfully upgraded to, the differential information table includes the ECU version number of the ECU upgrade version corresponding to each ECU version and the differential file path between each ECU version and the ECU upgrade version, and when the ECU upgrade version is an ECU version with a higher ECU version level than each ECU version, judging whether the target ECU version number of the old ECU version to be updated in the target ECU version list is empty;

[0202] A first updating module, configured to use the ECU version number of the new ECU version as the target ECU version number of the old ECU version to be updated when the judgment result is empty;

[0203] The second judgment module is used to judge whether the ECU version upgrade type in the ECU version corresponding to the target ECU version number of the old ECU version to be updated in the target ECU version list is skippable when the judgment result is not empty;

[0204] A second updating module is used for changing the target ECU version number of the old ECU version to be updated to the ECU version number of the new ECU version when the judgment result is that it can be skipped;

[0205] An adding module is used to add the ECU version number of the new ECU version of the same ECU type and the differential file path between the new ECU version and each old ECU version in the differential information table of each old ECU version in the target ECU version list.

[0206] In one implementation, the second updating unit 54 includes:

[0207] A third updating module is used for updating the target vehicle baseline version serial number of the latest ECU version in the list of each ECU version in the ECU version summary table to the vehicle baseline version number of the new vehicle baseline version, when the vehicle baseline version reference information includes a target vehicle baseline version serial number and a vehicle baseline version number list, the target vehicle baseline version serial number is the vehicle baseline version serial number of the latest vehicle baseline version in the vehicle baseline version to which each ECU version belongs, and the vehicle baseline version number list includes all vehicle baseline version numbers of the vehicle version upgrade type that cannot be skipped in the vehicle baseline version to which each ECU version belongs;

[0208] An adding module is used to add the vehicle version upgrade type of the new vehicle baseline version to the vehicle baseline version number list of the latest ECU version in the ECU version list when the vehicle version upgrade type of the new vehicle baseline version is non-skippable.

[0209] In one embodiment, the device further comprises:

[0210] A third obtaining unit is used to obtain the vehicle baseline version to be modified and the modified vehicle version upgrade type;

[0211] A modification unit, configured to modify the vehicle version upgrade type of the vehicle baseline version to be modified in the vehicle baseline version list to the modified vehicle version upgrade type;

[0212] A third updating unit is used for, for the ECU version to be modified in the ECU version list corresponding to the vehicle baseline version to be modified, if the upgrade type of the modified vehicle version is non-skippable and the vehicle baseline version number list of the ECU version to be modified is not empty, then the ECU version upgrade type of the ECU version to be modified is kept as non-skippable, and the vehicle baseline version number of the vehicle baseline version to be modified is added to the vehicle baseline version number list of the ECU version to be modified;

[0213] a fourth updating unit, for, when the modified vehicle version upgrade type is non-skippable and the vehicle baseline version number list of the ECU version to be modified is empty, modifying the ECU version upgrade type of the ECU version to be modified to non-skippable, and if the target ECU version number of the ECU version to be modified is not empty, determining an ECU version in the ECU version list where the ECU version to be modified is located, with the ECU version number of an ECU version with a higher ECU version level than the ECU version to be modified as the target ECU version number, modifying the target ECU version number of the determined ECU version to the ECU version number of the ECU version to be modified, and adding the vehicle baseline version number of the vehicle baseline version to be modified to the vehicle baseline version number list of the ECU version to be modified;

[0214] The fifth updating unit is used to delete the vehicle baseline version number of the to-be-modified vehicle baseline version from the vehicle baseline version number list of the to-be-modified ECU version when the modified vehicle version upgrade type is skippable, and if the modified vehicle baseline version number list changes from non-empty to empty, modify the ECU version upgrade type of the to-be-modified ECU version to skippable, and if the target ECU version number of the to-be-modified ECU version is not empty, determine the ECU version in the ECU version list where the to-be-modified ECU version is located that uses the ECU version number of the to-be-modified ECU version as the target ECU version number, and modify the target ECU version number of the determined ECU version to the ECU version number of the ECU version whose ECU version upgrade type is non-skippable for the first time among the ECU versions with ECU version levels higher than the to-be-modified ECU version.

[0215] In one embodiment, the device further comprises:

[0216] a fourth acquisition unit, configured to acquire the ECU type to be upgraded and the ECU version number to be upgraded in the ECU version to be upgraded corresponding to all ECU types in the vehicle to be upgraded, wherein the ECU type to be upgraded is the ECU type included in the ECU version to be upgraded, and the ECU version number to be upgraded is the ECU version number included in the ECU version to be upgraded;

[0217] A search unit, configured to search for the ECU version to be upgraded from the ECU version master table corresponding to the vehicle to be upgraded according to the ECU type to be upgraded and the ECU version number to be upgraded when the ECU versions to be upgraded corresponding to all ECU types belong to the same vehicle baseline version;

[0218] A selection unit is used to select a target ECU version to be upgraded corresponding to a target vehicle baseline version number with the lowest vehicle version level from among all the ECU versions to be upgraded after finding all the ECU versions to be upgraded;

[0219] a path determination unit, configured to use the differential file path corresponding to the target ECU version number of the target ECU version to be upgraded stored in the differential information table of the target ECU version to be upgraded as the upgrade path of the target ECU version to be upgraded, and use the original image file path of the target ECU version to be upgraded as the rollback path;

[0220] The first sending unit is used to send the ECU type, upgrade path and rollback path corresponding to the target ECU version to be upgraded to the vehicle to be upgraded, so that the vehicle to be upgraded upgrades the target ECU version to be upgraded according to the upgrade path and the rollback path.

[0221] In one embodiment, the device further comprises:

[0222] The second sending unit is used to search for the ECU version to be upgraded from the ECU version summary table corresponding to the vehicle to be upgraded according to the ECU type to be upgraded and the ECU version number to be upgraded. If at least one ECU version to be upgraded is not found, a warning prompt message indicating that the upgrade cannot be performed is sent to the vehicle to be upgraded.

[0223] In one embodiment, the device further comprises:

[0224] The third sending unit is used to send the upgrade path and rollback path corresponding to the ECU version to be upgraded to the vehicle to be upgraded in sequence according to the vehicle version level order from low to high when there are at least two vehicle baseline versions to which the ECU versions to be upgraded corresponding to all ECU types belong, until all ECU versions to be upgraded are upgraded to the same vehicle baseline version, and then execute the search unit.

[0225] In one embodiment, the first acquisition unit 50 is used to receive the new vehicle baseline version basic information sent by the vehicle baseline version management system through the operation handle corresponding to the specified vehicle model, wherein the operation handle is a pointer to the storage path of the ECU version summary table and the vehicle baseline version list of the specified vehicle model in the upgrade path management library.

[0226] Based on the above method embodiment, another embodiment of the present invention provides an ECU version management device, such as Fig. 9 As shown, the device is applied to a vehicle baseline version management system, and the device includes:

[0227] The receiving unit 60 is used to receive the uploaded ECU version basic information of a new ECU version of at least one ECU type of a specified vehicle model, the ECU version file of the new ECU version, and the vehicle version upgrade type of the new vehicle baseline version, wherein the ECU version basic information includes the ECU type, the ECU version number, the original image file path, and the ECU version upgrade type;

[0228] A calculation unit 61, configured to calculate a difference file between the new ECU version and the old ECU version of the same ECU type according to the ECU version file of the new ECU version and the ECU version file of the old ECU version of the same ECU type;

[0229] A determination unit 62, configured to determine a differential file path between the new ECU version and an old ECU version of the same ECU type based on the differential file;

[0230] The sending unit 63 is used to send the ECU version basic information of the new ECU version of the at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version to the upgrade path management library, so that the upgrade path management library updates the ECU version summary table and the vehicle baseline version list corresponding to the specified vehicle model according to at least one of the ECU version basic information of the new ECU version, the differential file path and the vehicle version upgrade type of the new vehicle baseline version, wherein the ECU version summary table includes the ECU version list of all ECU types included in the specified vehicle model, each ECU version list includes different ECU versions of the same ECU type, each ECU version includes the ECU version basic information, ECU version upgrade information, and vehicle baseline version reference information, the ECU version upgrade information is reference information for controlling each ECU version to be upgraded according to the ECU version upgrade type, the vehicle baseline version reference information is reference information for controlling each ECU version to be upgraded according to the vehicle baseline version upgrade type, the vehicle baseline version list includes different vehicle baseline versions of the specified vehicle model, each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type.

[0231] In one embodiment, the device further comprises:

[0232] an acquisition unit, used for acquiring a data file of the specified vehicle model before receiving uploaded ECU version basic information of a new ECU version of at least one ECU type of the specified vehicle model, an ECU version file of the new ECU version, and a vehicle version upgrade type of a new vehicle baseline version, wherein the data file is a serialized string of a storage path of a total table of ECU versions of the specified vehicle model and a list of vehicle baseline versions in an upgrade path management library, deserializing the data file to obtain the storage path, and generating an operation handle of the specified vehicle model according to the storage path, wherein the operation handle is a pointer for pointing to a storage path of a total table of ECU versions of the specified vehicle model and a list of vehicle baseline versions in the upgrade path management library;

[0233] The sending unit is used to send the ECU version basic information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version to the upgrade path management library through the operation handle.

[0234] Based on the above method embodiment, another embodiment of the present invention provides a storage medium having executable instructions stored thereon, which, when executed by a processor, enables the processor to implement the above method.

[0235] Based on the above method embodiment, another embodiment of the present invention provides an electronic device, including:

[0236] one or more processors;

[0237] a storage device for storing one or more programs,

[0238] When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described above.

[0239] The above-mentioned system and device embodiments correspond to the method embodiments and have the same technical effects as the method embodiments. For specific descriptions, please refer to the method embodiments. The device embodiments are obtained based on the method embodiments. For specific descriptions, please refer to the method embodiment part, which will not be repeated here. It can be understood by those of ordinary skill in the art that the accompanying drawings are only schematic diagrams of one embodiment, and the modules or processes in the accompanying drawings are not necessarily necessary for implementing the present invention.

[0240] Those skilled in the art can understand that the modules in the device in the embodiment can be distributed in the device in the embodiment according to the description of the embodiment, or can be changed accordingly and located in one or more devices different from the embodiment. The modules in the above embodiment can be combined into one module, or can be further divided into multiple sub-modules.

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

Claims

1. An ECU version management method, characterized in that: The method is applied to the upgrade path management library, and the method comprises: Get the new vehicle baseline version basic information of the specified vehicle model, wherein the new vehicle baseline version basic information includes the ECU version basic information of the new ECU version of at least one electronic control unit ECU type, the differential file path between the new ECU version and the old ECU version of the same ECU type, and the vehicle version upgrade type of the new vehicle baseline version, wherein the ECU version basic information includes the ECU type, ECU version number, original image file path, and ECU version upgrade type; Add the ECU version basic information of the new ECU version to the target ECU version list, wherein the target ECU version list is the ECU version list of the ECU type corresponding to the new ECU version in the ECU version summary table corresponding to the specified vehicle model, the ECU version summary table includes the ECU version list of all ECU types included in the specified vehicle model, each ECU version list includes different ECU versions of the same ECU type, each ECU version includes ECU version basic information, ECU version upgrade information, vehicle baseline version reference information, the ECU version upgrade information is the reference information for controlling each ECU version to be upgraded according to the ECU version upgrade type, and the vehicle baseline version reference information is the reference information for controlling each ECU version to be upgraded according to the vehicle baseline version upgrade type; According to the ECU version upgrade information, ECU version upgrade type and the differential file path of the old ECU version in the target ECU version list, the ECU version upgrade information of the old ECU version is updated; Obtaining the vehicle baseline version number of the new vehicle baseline version, and updating the vehicle baseline version reference information of the latest ECU version in each ECU version list of the ECU version summary table according to the vehicle baseline version number of the new vehicle baseline version and the vehicle version upgrade type of the new vehicle baseline version; The new vehicle baseline version is determined according to the latest ECU version in the ECU version lists, the vehicle version upgrade type of the new vehicle baseline version and the vehicle baseline version number of the new vehicle baseline version, and the new vehicle baseline version is added to the vehicle baseline version list corresponding to the specified vehicle model, wherein the vehicle baseline version list includes different vehicle baseline versions of the specified vehicle model, each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type.

2. The method according to claim 1, characterized in that: The vehicle version upgrade type and the ECU version upgrade type both include skippable or non-skippable, the ECU version upgrade information includes a target ECU version number and a differential information table, the target ECU version number is an ECU version number determined according to the ECU version upgrade type so that each ECU version can be successfully upgraded to, the differential information table includes the ECU version number of the ECU upgrade version corresponding to each ECU version and the differential file path between each ECU version and the ECU upgrade version, the ECU upgrade version is an ECU version with an ECU version level higher than that of each ECU version, and according to the ECU version upgrade information of the old ECU version in the target ECU version list, the ECU version upgrade type and the differential file path, the ECU version upgrade information of the old ECU version is updated, including: Determine whether the target ECU version number of the old ECU version to be updated in the target ECU version list is empty; If it is empty, the ECU version number of the new ECU version is used as the target ECU version number of the old ECU version to be updated; If it is not empty, determine whether the ECU version upgrade type in the ECU version corresponding to the target ECU version number of the old ECU version to be updated in the target ECU version list is skippable; if it is skippable, change the target ECU version number of the old ECU version to be updated to the ECU version number of the new ECU version; The ECU version number of the new ECU version of the same ECU type and the differential file path between the new ECU version and each old ECU version are added to the differential information table of each old ECU version in the target ECU version list.

3. The method according to claim 2, characterized in that The vehicle baseline version reference information includes a target vehicle baseline version serial number and a vehicle baseline version number list, wherein the target vehicle baseline version serial number is the vehicle baseline version serial number of the latest vehicle baseline version in the vehicle baseline version to which each ECU version belongs, and the vehicle baseline version number list includes all vehicle baseline version numbers of the vehicle version upgrade type that cannot be skipped in the vehicle baseline version to which each ECU version belongs, and according to the vehicle baseline version number of the new vehicle baseline version and the vehicle version upgrade type of the new vehicle baseline version, the vehicle baseline version reference information of the latest ECU version in the list of each ECU version in the ECU version summary table is updated, including: Update the target vehicle baseline version serial number of the latest ECU version in each ECU version list in the ECU version summary table to the vehicle baseline version number of the new vehicle baseline version; When the vehicle version upgrade type of the new vehicle baseline version is non-skippable, the vehicle version upgrade type of the new vehicle baseline version is added to the vehicle baseline version number list of the latest ECU version in the ECU version lists.

4. The method according to claim 3, characterized in that The method further comprises: Obtain the vehicle baseline version to be modified and the vehicle version upgrade type to be modified; Modify the vehicle version upgrade type of the vehicle baseline version to be modified in the vehicle baseline version list to the modified vehicle version upgrade type; For the ECU version to be modified in the ECU version list corresponding to the vehicle baseline version to be modified, if the upgrade type of the modified vehicle version is non-skippable and the vehicle baseline version number list of the ECU version to be modified is not empty, then the ECU version upgrade type of the ECU version to be modified is kept as non-skippable, and the vehicle baseline version number of the vehicle baseline version to be modified is added to the vehicle baseline version number list of the ECU version to be modified; If the modified vehicle version upgrade type is non-skippable and the vehicle baseline version number list of the ECU version to be modified is empty, then the ECU version upgrade type of the ECU version to be modified is modified to non-skippable, and if the target ECU version number of the ECU version to be modified is not empty, then determine the ECU version in the ECU version list where the ECU version to be modified is located, using the ECU version number of the ECU version with a higher ECU version level than the ECU version to be modified as the target ECU version number, and modify the target ECU version number of the determined ECU version to the ECU version number of the ECU version to be modified, and add the vehicle baseline version number of the vehicle baseline version to be modified to the vehicle baseline version number list of the ECU version to be modified; If the modified vehicle version upgrade type is skippable, the vehicle baseline version number of the to-be-modified vehicle baseline version is deleted from the vehicle baseline version number list of the to-be-modified ECU version, and if the modified vehicle baseline version number list changes from non-empty to empty, the ECU version upgrade type of the to-be-modified ECU version is modified to skippable, and if the target ECU version number of the to-be-modified ECU version is not empty, then the ECU version in the ECU version list where the to-be-modified ECU version is located is determined with the ECU version number of the to-be-modified ECU version as the target ECU version number, and the target ECU version number of the determined ECU version is modified to the ECU version number of the ECU version whose ECU version upgrade type is non-skippable for the first time in the ECU version with an ECU version level higher than that of the to-be-modified ECU version.

5. The method according to claim 3, characterized in that: The method further comprises: Obtain the ECU type to be upgraded and the ECU version number to be upgraded in the ECU version to be upgraded corresponding to all ECU types in the vehicle to be upgraded, wherein the ECU type to be upgraded is the ECU type included in the ECU version to be upgraded, and the ECU version number to be upgraded is the ECU version number included in the ECU version to be upgraded; If the ECU versions to be upgraded corresponding to all ECU types belong to the same vehicle baseline version, then according to the ECU type to be upgraded and the ECU version number to be upgraded, the ECU version to be upgraded is searched from the ECU version summary table corresponding to the vehicle to be upgraded; After all ECU versions to be upgraded are found, a target ECU version to be upgraded corresponding to the target vehicle baseline version number with the lowest vehicle version level is selected from all ECU versions to be upgraded; Using the differential file path corresponding to the target ECU version number of the target ECU version to be upgraded stored in the differential information table of the target ECU version to be upgraded as the upgrade path of the target ECU version to be upgraded, and using the original image file path of the target ECU version to be upgraded as the rollback path; The ECU type, upgrade path and rollback path corresponding to the target ECU version to be upgraded are sent to the vehicle to be upgraded, so that the vehicle to be upgraded upgrades the target ECU version to be upgraded according to the upgrade path and the rollback path.

6. The method according to claim 5, characterized in that After searching the ECU version to be upgraded from the ECU version list corresponding to the vehicle to be upgraded according to the ECU type to be upgraded and the ECU version number to be upgraded, the method further includes: If at least one ECU version to be upgraded is not found, a warning message indicating that the upgrade is impossible is sent to the vehicle to be upgraded.

7. The method according to claim 5, characterized in that The method further comprises: If there are at least two vehicle baseline versions to which the ECU versions to be upgraded corresponding to all ECU types belong, then the upgrade path and rollback path corresponding to the ECU versions to be upgraded are sent to the vehicles to be upgraded in sequence according to the vehicle version level order from low to high, until all ECU versions to be upgraded are upgraded to the same vehicle baseline version, and then the step of searching the ECU version to be upgraded from the ECU version master table corresponding to the vehicle to be upgraded according to the ECU type to be upgraded and the ECU version number to be upgraded is executed.

8. The method according to claim 1, characterized in that Get the new vehicle baseline version basic information of the specified model, including: Receive the new vehicle baseline version basic information sent by the vehicle baseline version management system through the operation handle corresponding to the specified vehicle model, wherein the operation handle is a pointer to the storage path of the ECU version master table and the vehicle baseline version list of the specified vehicle model in the upgrade path management library.

9. An ECU version management method, characterized in that: The method is applied to a vehicle baseline version management system, and the method comprises: Receive uploaded ECU version basic information of a new ECU version of at least one ECU type of a specified vehicle model, an ECU version file of the new ECU version, and a vehicle version upgrade type of a new vehicle baseline version, wherein the ECU version basic information includes ECU type, ECU version number, original image file path, and ECU version upgrade type; Calculating a differential file between the new ECU version and the old ECU version of the same ECU type according to the ECU version file of the new ECU version and the ECU version file of the old ECU version of the same ECU type, and determining a differential file path between the new ECU version and the old ECU version of the same ECU type based on the differential file; The ECU version basic information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version are sent to the upgrade path management library, so that the upgrade path management library updates the ECU version summary table and the vehicle baseline version list corresponding to the specified vehicle model according to at least one of the ECU version basic information of the new ECU version, the differential file path and the vehicle version upgrade type of the new vehicle baseline version, wherein the ECU version summary table includes the ECU version list of all ECU types included in the specified vehicle model, each ECU version list includes different ECU versions of the same ECU type, each ECU version includes ECU version basic information, ECU version upgrade information, and vehicle baseline version reference information, the ECU version upgrade information is reference information for controlling each ECU version to be upgraded according to the ECU version upgrade type, the vehicle baseline version reference information is reference information for controlling each ECU version to be upgraded according to the vehicle baseline version upgrade type, the vehicle baseline version list includes different vehicle baseline versions of the specified vehicle model, each vehicle baseline version includes the vehicle baseline version number, the ECU type and ECU version number involved in each vehicle baseline version, and the vehicle version upgrade type.

10. The method according to claim 9, characterized in that Before receiving uploaded ECU version basic information of a new ECU version of at least one ECU type of a specified vehicle model, an ECU version file of a new ECU version, and a vehicle version upgrade type of a new vehicle baseline version, the method further includes: obtaining a data file of the specified vehicle model, wherein the data file is a serialized string of a storage path of a total list of ECU versions of the specified vehicle model and a list of vehicle baseline versions in an upgrade path management library, deserializing the data file to obtain the storage path, and generating an operation handle of the specified vehicle model according to the storage path, wherein the operation handle is a pointer to a storage path of a total list of ECU versions of the specified vehicle model and a list of vehicle baseline versions in the upgrade path management library; The ECU version basic information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version are sent to the upgrade path management library, including: sending the ECU version basic information of the new ECU version of at least one ECU type, the differential file path and the vehicle version upgrade type of the new vehicle baseline version to the upgrade path management library through the operation handle.

Images