Software and hardware version determination method and device of vehicle, equipment and storage medium

Abstract

The invention relates to a software and hardware version determination method and device of a vehicle, equipment and a storage medium. The master ECU obtains software and hardware version information of the master ECU and a CAN message reported by the slave ECU in the target vehicle; determining software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU; and determining the software and hardware version information of the target vehicle according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU. According to the scheme, the software and hardware version information of the target vehicle can be determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU. Compared with the mode that a diagnostic instrument is used for obtaining the version information of the vehicle, the version information of the vehicle can be obtained more timely and efficiently, and then the timeliness of vehicle control version maintenance is improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a method, device, equipment and storage medium for determining software and hardware versions of a vehicle. Background Art

[0002] With the development of intelligent automobiles, the software functions of intelligent connected vehicles are increasing, and the number of controllers involved in the whole vehicle is also increasing. The version consistency of the controller is of great significance to the safe and stable operation of the vehicle; however, frequent version iterations have brought huge challenges to the consistency management of vehicle software.

[0003] In the conventional technology, a diagnostic instrument is usually used to obtain the version information of the vehicle to maintain the version of the vehicle controller. However, the diagnostic instrument usually needs to be connected to the vehicle through a wired connection to obtain the version information of the vehicle controller, which leads to the problem of untimely maintenance of the version information of the vehicle controller. Summary of the invention

[0004] Based on this, it is necessary to provide a method, device, equipment and storage medium for determining the software and hardware versions of a vehicle in response to the above-mentioned technical problems, which can improve the timeliness of vehicle control version maintenance.

[0005] In a first aspect, the present application provides a method for determining the software and hardware versions of a vehicle, the method being applied to a main electronic control unit ECU in a target vehicle, the method comprising:

[0006] Obtaining software and hardware version information of the master ECU and a controller area network (CAN) message reported by a slave ECU in the target vehicle; wherein the CAN message includes at least an ECU identifier and a software and hardware version identifier;

[0007] Determining software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU;

[0008] The software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0009] In one embodiment, the step of obtaining the software and hardware version information of the master ECU and the controller area network (CAN) message reported by the slave ECU in the target vehicle includes:

[0010] When the vehicle ignition switch of the target vehicle is in the on state, the software and hardware version information of the master ECU and the controller area network (CAN) message reported by the slave ECU in the target vehicle are obtained.

[0011] In one embodiment, determining the software and hardware version information of the target vehicle according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU includes:

[0012] Acquire a software and hardware version mapping relationship, wherein the software and hardware version mapping relationship includes a correspondence between software and hardware version information of an ECU in a sample vehicle and software and hardware version information of the sample vehicle, and the vehicle type of the sample vehicle is the same as the vehicle type of the target vehicle;

[0013] Based on the software and hardware version mapping relationship, the software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0014] In one of the embodiments, when the master ECU or the slave ECU has an optional part identification, the determining the software and hardware version information of the target vehicle based on the software and hardware version mapping relationship according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU includes:

[0015] Based on the mapping relationship, according to the software and hardware version information of the ECU with the optional part identification in the target vehicle, determine a first candidate mapping relationship including the software and hardware version information of the ECU with the optional part identification;

[0016] According to the first candidate mapping relationship, the software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the remaining ECUs among the slave ECUs except the ECU with the option part identification.

[0017] In one of the embodiments, when the master ECU or the slave ECU has multiple hardware version identifiers, determining the software and hardware version information of the target vehicle based on the mapping relationship according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU includes:

[0018] Based on the mapping relationship, according to the software and hardware version information of the ECU with multiple hardware version identifiers in the target vehicle, determine a second candidate mapping relationship including the software and hardware version information of the ECU with multiple hardware version identifiers;

[0019] According to the second candidate mapping relationship, the software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the remaining ECUs in the slave ECUs except the ECU with multiple hardware version identifiers.

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

[0021] Determining a software upgrade version corresponding to the software and hardware version information of the target vehicle;

[0022] Obtaining the operating status of the target vehicle;

[0023] When the running state of the target vehicle meets the upgrading condition, the target vehicle is upgraded by using the software upgrading version.

[0024] In a second aspect, the present application further provides a device for determining the software and hardware versions of a vehicle, the device being configured in a main ECU, and the device comprising:

[0025] An acquisition module, used to acquire the software and hardware version information of the main ECU and the controller area network CAN message reported by the slave ECU in the target vehicle; wherein the CAN message at least includes an ECU identifier and a software and hardware version identifier;

[0026] A first determination module, configured to determine the software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU;

[0027] The second determination module is used to determine the software and hardware version information of the target vehicle according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0028] In a third aspect, the present application further provides a computer device, the computer device comprising a memory and a processor, the memory storing a computer program, and the processor implementing the following steps when executing the computer program:

[0029] Obtaining software and hardware version information of the master ECU and a controller area network (CAN) message reported by a slave ECU in the target vehicle; wherein the CAN message includes at least an ECU identifier and a software and hardware version identifier;

[0030] Determining software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU;

[0031] The software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0032] In a fourth aspect, the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0033] Obtaining software and hardware version information of the master ECU and a controller area network (CAN) message reported by a slave ECU in the target vehicle; wherein the CAN message includes at least an ECU identifier and a software and hardware version identifier;

[0034] Determining software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU;

[0035] The software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0036] In a fifth aspect, the present application further provides a computer program product, the computer program product comprising a computer program, which implements the following steps when executed by a processor:

[0037] Obtaining software and hardware version information of the master ECU and a controller area network (CAN) message reported by a slave ECU in the target vehicle; wherein the CAN message includes at least an ECU identifier and a software and hardware version identifier;

[0038] Determining software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU;

[0039] The software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0040] The above-mentioned method, device, equipment and storage medium for determining the software and hardware version of the vehicle, the main ECU obtains the software and hardware version information of the main ECU and the CAN message reported by the slave ECU in the target vehicle; because the CAN message at least includes the ECU identification and the software and hardware version identification; thus, the software and hardware version information of the slave ECU can be determined according to the CAN message reported by the slave ECU; and the software and hardware version information of the target vehicle can be determined according to the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU. In the above scheme, each ECU reports a CAN message to the main ECU, so that the main ECU can determine the software and hardware version information of the slave ECU according to the received CAN message; and the software and hardware version information of the target vehicle can be determined according to the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU. Compared with using a diagnostic instrument to obtain the version information of the vehicle, the version information of the vehicle can be obtained more timely and efficiently, thereby improving the timeliness of vehicle control version maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A schematic diagram of a method for determining software and hardware versions of a vehicle in one embodiment;

[0042] Figure 2 A signaling diagram of a method for determining software and hardware versions of a vehicle in one embodiment;

[0043] Figure 3 A schematic flow chart of a method for determining software and hardware versions of a vehicle in one embodiment;

[0044] Figure 4 A schematic diagram of a process for determining software and hardware version information of a target vehicle in one embodiment;

[0045] Figure 5 A schematic diagram of another process of determining software and hardware version information of a target vehicle in one embodiment;

[0046] Figure 6 A schematic diagram of a process for determining software and hardware version information of a target vehicle in an embodiment;

[0047] Figure 7 A schematic diagram of a process of upgrading a software version in one embodiment;

[0048] Figure 8 A schematic flow chart of another method for determining software and hardware versions of a vehicle in one embodiment;

[0049] Fig. 9 A structural block diagram of a device for determining software and hardware versions of a vehicle in one embodiment;

[0050] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0052] The method for determining the software and hardware versions of a vehicle provided in the embodiment of the present application can be applied to application scenarios for identifying the software and hardware versions of a complete vehicle, and specifically to application scenarios for upgrading or troubleshooting a vehicle based on the software and hardware versions of the complete vehicle.

[0053] The method provided in the embodiment of the present application can be executed by any electronic control unit (ECU) in the target vehicle, with the ECU serving as the master ECU and other ECUs in the target vehicle serving as slave ECUs.

[0054] In one embodiment, see Figure 1 , Figure 1 A schematic diagram of a method for determining the software and hardware versions of a vehicle is provided, see Figure 2 , Figure 2 A signaling diagram of a method for determining the software and hardware versions of a vehicle is provided. The overall process of the method for determining the software and hardware versions of a vehicle is generally introduced below.

[0055] An Over-the-Air Technology (OTA) module can be deployed in the main ECU. Specifically, the OTA module includes a version collection module, which can regularly collect and parse the hardware version information and software version information of the vehicle ECU, for example, once every 3 seconds; and generate an ECU version cache list for caching the parsed software version information and hardware version information list of each ECU.

[0056] The OTA module also includes a vehicle version determination engine, which reads the ECU version after an ignition (IGON) event and matches the ECU's hardware version information with the software version information to determine the target vehicle's hardware and software version information. Specifically, after the car is produced, the vehicle baseline preset list will be filled, which includes a hardware preset list and a software preset list.

[0057] The hardware preset list is used to maintain the relationship between all vehicle hardware versions and ECUs. After the OTA module obtains all ECU hardware version information, it starts matching the vehicle hardware version information. After a successful match, it generates the vehicle's current vehicle hardware version information and the corresponding installed ECU list. The software preset list is used to maintain the relationship between all vehicle software version information and ECUs. Here, only the installed ECUs can be considered. After the OTA module obtains all ECU software version information, it starts matching the vehicle software version. After a successful match, it generates the vehicle's current vehicle software version information.

[0058] Furthermore, the hardware version information and software version information of the ECU, as well as the software and hardware version information of the target vehicle, can be stored in the OTA management module in the OTA module. The OTA management module can transmit the stored hardware version information and software version information of the ECU, as well as the software and hardware version information of the target vehicle to the vehicle terminal for display.

[0059] In one embodiment, Figure 3 As shown, a method for determining the software and hardware versions of a vehicle is provided, and the method is applied to a main ECU as an example for explanation, and includes the following steps:

[0060] S301, obtaining software and hardware version information of the master ECU and a controller area network (CAN) message reported by a slave ECU in a target vehicle.

[0061] Exemplarily, the master ECU can directly obtain the software and hardware version information of the master ECU, wherein the software and hardware version information of the master ECU includes the hardware version number and software version number of the master ECU. The remaining slave ECUs can upload controller area network (CAN) messages to the master ECU periodically or in real time. Among them, the CAN message includes at least the ECU identifier and the software and hardware version identifier. The software and hardware version includes the hardware version number and software version number of the slave ECU.

[0062] For example, see Table 1, which is an example of a CAN message, wherein the CAN message ID is used to identify which slave ECU sends the message, that is, it can be understood as an ECU identifier. Reserved is used to complete the length of the CAN message.

[0063] Table 1

[0064]

[0065] S302, determining the software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU.

[0066] Exemplarily, the software and hardware version information of the slave ECU may be directly determined based on the CAN message reported by the slave ECU, that is, the hardware version number and software version number of the slave ECU may be directly obtained.

[0067] S303, determining the software and hardware version information of the target vehicle according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0068] Exemplarily, the correspondence between the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU and the software and hardware version information of the target vehicle can be pre-set, and the conversion relationship between the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU and the software and hardware version information of the target vehicle can be obtained, and then based on the correspondence or conversion relationship, the software and hardware version information of the target vehicle can be determined according to the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU.

[0069] The method for determining the software and hardware version of the above-mentioned vehicle is that the main ECU obtains the software and hardware version information of the main ECU and the CAN message reported by the slave ECU in the target vehicle; since the CAN message includes at least the ECU identification and the software and hardware version identification; therefore, the software and hardware version information of the slave ECU can be determined according to the CAN message reported by the slave ECU; and the software and hardware version information of the target vehicle can be determined according to the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU. In the above scheme, each ECU reports a CAN message to the main ECU, so that the main ECU can determine the software and hardware version information of the slave ECU according to the received CAN message; and the software and hardware version information of the target vehicle can be determined according to the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU. Compared with using a diagnostic instrument to obtain the version information of the vehicle, the version information of the vehicle can be obtained more timely and efficiently, thereby improving the timeliness of vehicle control version maintenance.

[0070] In some optional implementations, the slave ECU needs to report a CAN message containing the correct version to the master ECU as soon as it is powered on and the communication function is enabled, ensuring that the master ECU can get the correct ECU version as soon as possible when the vehicle is powered on for the first time or when the ECU is upgraded and restarted. During the period when the subsequent ECU is not upgraded, the slave ECU can report CAN messages periodically; and the master ECU can also periodically obtain the version information of the master ECU to ensure that the master ECU can recognize the slave ECU version change or the master ECU version change in time.

[0071] In view of this, when the ignition switch of the target vehicle is in the on state, that is, after the IGON event, the software and hardware version information of the main ECU and the controller area network CAN message reported by the slave ECU in the target vehicle can be obtained. It should be noted that the ECU version should generally not change during an IGON to IGOFF cycle. The scenarios in which the ECU version changes generally occur are over-the-air technology (OTA) software upgrades, power-off replacement, offline diagnostic instrument flashing, etc. After the above scenarios occur, the IGON event will occur again. Therefore, when the ignition switch of the target vehicle is in the on state, the software and hardware version information of the main ECU and the controller area network CAN message reported by the slave ECU in the target vehicle can be obtained. The software and hardware version information of the ECU can be obtained as soon as the software and hardware version of the ECU is upgraded, so that the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU obtained by the main ECU are the latest software and hardware version information, thereby making the software and hardware version information of the determined target vehicle more accurate.

[0072] In some optional implementations, see Figure 4 , Figure 4A flowchart for determining the software and hardware version information of a target vehicle is provided, which specifically includes the following steps:

[0073] S401, obtaining a mapping relationship between software and hardware versions.

[0074] Exemplarily, the software-hardware mapping relationship may be pre-established. For example, a correspondence between the software version information of each ECU of the sample vehicle and the software version information of the sample vehicle may be pre-established, as may a correspondence between the hardware version information of each ECU of the sample vehicle and the hardware version information of the sample vehicle. That is, the pre-established software-hardware version mapping relationship includes a correspondence between the software-hardware version information of the ECU in the sample vehicle and the software-hardware version information of the sample vehicle, and the vehicle type of the sample vehicle is the same as the vehicle type of the target vehicle.

[0075] Exemplarily, the mapping relationship between software and hardware versions is shown in Table 2:

[0076] Table 2

[0077]

[0078] Among them, Vhw1~VhwK are the vehicle hardware versions, Vsw11~VswKN are the vehicle software versions, and the same vehicle hardware version can correspond to different vehicle software versions.

[0079] S402 , based on the software and hardware version mapping relationship, according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU, determine the software and hardware version information of the target vehicle.

[0080] Exemplarily, the vehicle hardware version and vehicle software version corresponding to the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU can be determined based on the software and hardware version mapping relationship, and then the software and hardware version information of the target vehicle can be determined.

[0081] In an embodiment of the present application, a method for determining the software and hardware version information of a target vehicle based on a software and hardware version mapping relationship is provided, which can automatically and efficiently determine the software and hardware version information of the target vehicle.

[0082] In some optional implementations, all ECUs in the vehicle hardware preset list will be set with an identification to indicate whether they are optional parts. If the target vehicle has optional parts, for example, optional parts are used to realize functions such as intelligent driving, then the ECU used to realize the corresponding functions of the optional parts will have an optional part identification. The pre-established hardware and software version mapping relationship will also include the corresponding relationship between the hardware and software versions of the ECU with the optional part identification and the hardware and software versions of other ECUs, and the hardware and software versions of the target vehicle.

[0083] Based on this, see Figure 5 , Figure 5 Another flow chart for determining the software and hardware version information of a target vehicle is provided, which specifically includes the following steps:

[0084] S501 , based on the mapping relationship and according to the software and hardware version information of the ECU with the optional part identification in the target vehicle, determine a first candidate mapping relationship including the software and hardware version information of the ECU with the optional part identification.

[0085] Exemplarily, based on the mapping relationship and according to the software and hardware version information of the ECU with the option identification in the target vehicle, a first candidate mapping relationship including the software and hardware version information of the ECU with the option identification can be screened out from the mapping relationship.

[0086] S502 , determining the software and hardware version information of the target vehicle according to the first candidate mapping relationship and the software and hardware version information of the master ECU and the remaining ECUs except the ECU having the optional component identifier among the slave ECUs.

[0087] Furthermore, based on the first candidate mapping relationship, and based on the software and hardware version information of the main ECU and the remaining ECUs except the ECU with the optional part identification from the ECU, it is possible to determine whether the software and hardware version information of the remaining ECUs satisfies the specific mapping relationship in the first candidate mapping relationship, and use the software and hardware version information of the sample vehicle in the specific mapping relationship as the software and hardware version information of the target vehicle.

[0088] In an embodiment of the present application, a method is provided for pre-building a correspondence between the software and hardware version information of the ECU used to implement the optional parts function and the software and hardware version information of the sample vehicle when the target vehicle has optional parts, thereby efficiently determining the software and hardware version information of the target vehicle with the optional parts.

[0089] Optionally, all ECUs in the vehicle hardware preset list will also be set with an identification of whether there are multiple hardware versions. If there are multiple suppliers for a certain ECU of the target vehicle, this will result in multiple hardware versions of the ECU. Such ECUs will have multiple hardware version identifications. The pre-established hardware and software version mapping relationship will also include the corresponding relationship between the hardware and software versions of the ECU with multiple hardware version identifications and other ECU hardware and software versions, and the hardware and software versions of the target vehicle.

[0090] Based on this, based on this, see Figure 6 , Figure 6 Another flow chart for determining the software and hardware version information of a target vehicle is provided, which specifically includes the following steps:

[0091] S601 , based on the mapping relationship and according to the software and hardware version information of the ECU with multiple hardware version identifiers in the target vehicle, determine a second candidate mapping relationship including the software and hardware version information of the ECU with multiple hardware version identifiers.

[0092] Exemplarily, based on the mapping relationship and according to the software and hardware version information of the ECU with multiple hardware version identifiers in the target vehicle, a second candidate mapping relationship including the software and hardware version information of the ECU with multiple hardware version identifiers can be screened out in the mapping relationship.

[0093] S602 , determining the software and hardware version information of the target vehicle according to the second candidate mapping relationship and the software and hardware version information of the master ECU and the remaining ECUs except the ECU with multiple hardware version identifiers among the slave ECUs.

[0094] Furthermore, based on the second candidate mapping relationship, according to the software and hardware version information of the main ECU and the remaining ECUs excluding the ECU with multiple hardware version identifiers from the ECU, it is possible to determine whether the software and hardware version information of the remaining ECUs satisfies the specific mapping relationship in the second candidate mapping relationship, and use the software and hardware version information of the sample vehicle in the specific mapping relationship as the software and hardware version information of the target vehicle.

[0095] In an embodiment of the present application, a method is provided for pre-building a correspondence between the software and hardware version information of the ECUs provided by multiple suppliers and the software and hardware version information of the sample vehicle in case the target vehicle has ECUs provided by multiple suppliers, thereby efficiently determining the software and hardware version information of the target vehicle with optional parts.

[0096] In some optional implementations, in the above embodiments, determining the software and hardware version information of the target vehicle can be understood as the current software and hardware version information of the target vehicle. The software version information of each ECU in the target vehicle will be continuously updated iteratively. Figure 7 , Figure 7 A flowchart of software version upgrade is provided, which specifically includes the following steps:

[0097] S701, determining a software upgrade version corresponding to the software and hardware version information of the target vehicle.

[0098] Exemplarily, the current software and hardware version information of the target vehicle can be uploaded to a cloud server. The cloud server will determine whether there is a software upgrade version corresponding to the software and hardware version information of the target vehicle. If so, an upgrade task will be sent to the vehicle, and the upgrade task will include information on the software upgrade version corresponding to the software and hardware version information of the target vehicle.

[0099] S702, obtaining the operating status of the target vehicle.

[0100] Optionally, after receiving the task to be upgraded, the target vehicle will first obtain the operating status of the target vehicle, for example, the power level and driving data of the target vehicle, so as to determine whether to perform the software version upgrade operation according to the operating status of the target vehicle.

[0101] S703: When the running state of the target vehicle meets the upgrading condition, the target vehicle is upgraded using the software upgrading version.

[0102] Exemplarily, the upgrade conditions may be that the vehicle is not in driving state, has sufficient power and is in a stable network environment. When the operating state of the target vehicle meets the upgrade conditions, the target vehicle may be upgraded using the software upgrade version.

[0103] In an embodiment of the present application, an achievable method for determining a software upgrade version based on the current software and hardware version information of a target vehicle is provided, which can quickly and accurately determine the software upgrade version corresponding to the software and hardware version information of different vehicles, and thus can timely control the vehicle's software version to be updated to the latest version.

[0104] In some optional implementations, in the scenario of troubleshooting vehicle faults, the solution provided by the embodiments of the present application can quickly determine the software and hardware version information of the target vehicle, and can further determine whether the target vehicle has a software version to be upgraded. This can update the software version of each ECU of the target vehicle to the latest version to quickly locate and solve the fault problem, thereby improving the efficiency of troubleshooting.

[0105] In some optional implementations, see Figure 8 , Figure 8 A flowchart of another method for determining the software and hardware versions of a vehicle is provided, which specifically includes the following steps:

[0106] S801, when the ignition switch of the target vehicle is in the on state, obtaining the software and hardware version information of the master ECU and the controller area network (CAN) message reported by the slave ECU in the target vehicle.

[0107] S802, determining the software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU.

[0108] S803, obtaining a mapping relationship between software and hardware versions.

[0109] S804 , based on the software and hardware version mapping relationship, according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU, determine the software and hardware version information of the target vehicle.

[0110] S805, determining a software upgrade version corresponding to the software and hardware version information of the target vehicle.

[0111] S806, obtaining the operating status of the target vehicle.

[0112] S807: When the running state of the target vehicle meets the upgrading condition, the target vehicle is upgraded using the software upgrading version.

[0113] The embodiment of the present application provides a method for determining the hardware and software versions of a vehicle. Through this method, the vehicle obtains the hardware version and software version of all ECUs of the vehicle, and matches the hardware version and software version of the vehicle. The hardware version and software version of the vehicle can be sent to the vehicle for display, which is convenient for users to check the status of their vehicles. The hardware version and software version of the vehicle can also be uploaded to the cloud to manage the version of the vehicle throughout its life cycle, ensuring that the vehicle software version is traceable. In addition, it is convenient to perform vehicle OTA upgrades, which can be performed based on the baseline dimension of the vehicle to ensure the functional consistency of the vehicle.

[0114] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0115] Based on the same inventive concept, the embodiment of the present application also provides a device for implementing the software and hardware version determination of the vehicle involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations of the embodiments of the software and hardware version determination device for one or more vehicles provided below can refer to the limitations of the software and hardware version determination method for the vehicle above, and will not be repeated here.

[0116] In one embodiment, Fig. 9 As shown, a device for determining the software and hardware versions of a vehicle is provided, the device is configured in a main ECU, and the device includes:

[0117] The acquisition module 10 is used to acquire the software and hardware version information of the main ECU and the controller area network CAN message reported by the slave ECU in the target vehicle; wherein the CAN message at least includes the ECU identification and the software and hardware version identification;

[0118] A first determination module 20, configured to determine the software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU;

[0119] The second determining module 30 is used to determine the software and hardware version information of the target vehicle according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0120] The above-mentioned device for determining the software and hardware version of the vehicle is configured such that the main ECU obtains the software and hardware version information of the main ECU and the CAN message reported by the slave ECU in the target vehicle; since the CAN message at least includes the ECU identification and the software and hardware version identification; therefore, the software and hardware version information of the slave ECU can be determined according to the CAN message reported by the slave ECU; and the software and hardware version information of the target vehicle can be determined according to the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU. In the above scheme, each ECU reports a CAN message to the main ECU, so that the main ECU can determine the software and hardware version information of the slave ECU according to the received CAN message; and the software and hardware version information of the target vehicle can be determined according to the software and hardware version information of the main ECU and the software and hardware version information of the slave ECU. Compared with obtaining the version information of the vehicle using a diagnostic instrument, the version information of the vehicle can be obtained more timely and efficiently, thereby improving the timeliness of vehicle control version maintenance.

[0121] In one embodiment, the acquisition module 10 is specifically used for:

[0122] When the ignition switch of the target vehicle is in the on state, the software and hardware version information of the master ECU and the controller area network (CAN) message reported by the slave ECU in the target vehicle are obtained.

[0123] In one embodiment, the second determining module 30 specifically includes:

[0124] An acquisition unit, used for acquiring a software and hardware version mapping relationship, wherein the software and hardware version mapping relationship includes a correspondence between software and hardware version information of an ECU in a sample vehicle and software and hardware version information of the sample vehicle, and the vehicle type of the sample vehicle is the same as the vehicle type of the target vehicle;

[0125] The determination unit is used to determine the software and hardware version information of the target vehicle based on the software and hardware version mapping relationship according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0126] In one embodiment, when the master ECU or the slave ECU has an option identification, the determination unit is specifically configured to:

[0127] Based on the mapping relationship, according to the software and hardware version information of the ECU with the optional part identification in the target vehicle, a first candidate mapping relationship including the software and hardware version information of the ECU with the optional part identification is determined; according to the first candidate mapping relationship, according to the software and hardware version information of the main ECU and the remaining ECUs except the ECU with the optional part identification in the slave ECU, the software and hardware version information of the target vehicle is determined.

[0128] In one of the embodiments, when there are multiple hardware version identifiers in the master ECU or the slave ECU, the determining unit is specifically configured to:

[0129] Based on the mapping relationship, according to the software and hardware version information of the ECU with multiple hardware version identifications in the target vehicle, a second candidate mapping relationship including the software and hardware version information of the ECU with multiple hardware version identifications is determined; according to the second candidate mapping relationship, according to the software and hardware version information of the main ECU and the remaining ECUs except the ECU with multiple hardware version identifications from the ECU, the software and hardware version information of the target vehicle is determined.

[0130] In one embodiment, the device further comprises an upgrade module, the upgrade module being configured to:

[0131] Determine the software upgrade version corresponding to the software and hardware version information of the target vehicle; obtain the operating status of the target vehicle; and when the operating status of the target vehicle meets the upgrade conditions, use the software upgrade version to upgrade the target vehicle.

[0132] Each module in the above-mentioned vehicle software and hardware version determination device can be implemented in whole or in part by software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each of the above modules.

[0133] In one embodiment, a computer device is provided. The computer device may be an ECU, and its internal structure diagram may be as follows: Fig.10As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store the mapping relationship between software and hardware versions and the software and hardware version information of the vehicle, as well as the software and hardware version information of each ECU. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for determining the software and hardware version of a vehicle is implemented.

[0134] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0135] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0136] Obtaining software and hardware version information of the master ECU and a controller area network (CAN) message reported by a slave ECU in the target vehicle; wherein the CAN message includes at least an ECU identifier and a software and hardware version identifier;

[0137] Determine the software and hardware version information of the slave ECU based on the CAN message reported by the slave ECU;

[0138] The software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0139] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0140] When the ignition switch of the target vehicle is in the on state, the software and hardware version information of the master ECU and the controller area network (CAN) message reported by the slave ECU in the target vehicle are obtained.

[0141] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0142] Obtain a software and hardware version mapping relationship, wherein the software and hardware version mapping relationship includes a correspondence between software and hardware version information of the ECU in a sample vehicle and software and hardware version information of the sample vehicle, and the vehicle type of the sample vehicle is the same as the vehicle type of the target vehicle; based on the software and hardware version mapping relationship, determine the software and hardware version information of the target vehicle according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0143] In one embodiment, when the master ECU or the slave ECU has an option component identifier, the processor further implements the following steps when executing the computer program:

[0144] Based on the mapping relationship, according to the software and hardware version information of the ECU with the optional part identification in the target vehicle, a first candidate mapping relationship including the software and hardware version information of the ECU with the optional part identification is determined; according to the first candidate mapping relationship, according to the software and hardware version information of the main ECU and the remaining ECUs except the ECU with the optional part identification in the slave ECU, the software and hardware version information of the target vehicle is determined.

[0145] In one embodiment, when there are multiple hardware version identifiers in the master ECU or the slave ECU, the processor further implements the following steps when executing the computer program:

[0146] Based on the mapping relationship, according to the software and hardware version information of the ECU with multiple hardware version identifications in the target vehicle, a second candidate mapping relationship including the software and hardware version information of the ECU with multiple hardware version identifications is determined; according to the second candidate mapping relationship, according to the software and hardware version information of the main ECU and the remaining ECUs except the ECU with multiple hardware version identifications from the ECU, the software and hardware version information of the target vehicle is determined.

[0147] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0148] Determine the software upgrade version corresponding to the software and hardware version information of the target vehicle; obtain the operating status of the target vehicle; and when the operating status of the target vehicle meets the upgrade conditions, use the software upgrade version to upgrade the target vehicle.

[0149] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0150] Obtaining software and hardware version information of the master ECU and a controller area network (CAN) message reported by a slave ECU in the target vehicle; wherein the CAN message includes at least an ECU identifier and a software and hardware version identifier;

[0151] Determine the software and hardware version information of the slave ECU based on the CAN message reported by the slave ECU;

[0152] The software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0153] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0154] When the ignition switch of the target vehicle is in the on state, the software and hardware version information of the master ECU and the controller area network (CAN) message reported by the slave ECU in the target vehicle are obtained.

[0155] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0156] Obtain a software and hardware version mapping relationship, wherein the software and hardware version mapping relationship includes a correspondence between software and hardware version information of the ECU in a sample vehicle and software and hardware version information of the sample vehicle, and the vehicle type of the sample vehicle is the same as the vehicle type of the target vehicle; based on the software and hardware version mapping relationship, determine the software and hardware version information of the target vehicle according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0157] In one embodiment, when the master ECU or the slave ECU has an option component identifier, the computer program further implements the following steps when executed by the processor:

[0158] Based on the mapping relationship, according to the software and hardware version information of the ECU with the optional part identification in the target vehicle, a first candidate mapping relationship including the software and hardware version information of the ECU with the optional part identification is determined; according to the first candidate mapping relationship, according to the software and hardware version information of the main ECU and the remaining ECUs except the ECU with the optional part identification in the slave ECU, the software and hardware version information of the target vehicle is determined.

[0159] In one embodiment, when there are multiple hardware version identifiers in the master ECU or the slave ECU, the computer program further implements the following steps when executed by the processor:

[0160] Based on the mapping relationship, according to the software and hardware version information of the ECU with multiple hardware version identifications in the target vehicle, a second candidate mapping relationship including the software and hardware version information of the ECU with multiple hardware version identifications is determined; according to the second candidate mapping relationship, according to the software and hardware version information of the main ECU and the remaining ECUs except the ECU with multiple hardware version identifications from the ECU, the software and hardware version information of the target vehicle is determined.

[0161] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0162] Determine the software upgrade version corresponding to the software and hardware version information of the target vehicle; obtain the operating status of the target vehicle; and when the operating status of the target vehicle meets the upgrade conditions, use the software upgrade version to upgrade the target vehicle.

[0163] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0164] Obtaining software and hardware version information of the master ECU and a controller area network (CAN) message reported by a slave ECU in the target vehicle; wherein the CAN message includes at least an ECU identifier and a software and hardware version identifier;

[0165] Determine the software and hardware version information of the slave ECU based on the CAN message reported by the slave ECU;

[0166] The software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0167] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0168] When the ignition switch of the target vehicle is in the on state, the software and hardware version information of the master ECU and the controller area network (CAN) message reported by the slave ECU in the target vehicle are obtained.

[0169] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0170] Obtain a software and hardware version mapping relationship, wherein the software and hardware version mapping relationship includes a correspondence between software and hardware version information of the ECU in a sample vehicle and software and hardware version information of the sample vehicle, and the vehicle type of the sample vehicle is the same as the vehicle type of the target vehicle; based on the software and hardware version mapping relationship, determine the software and hardware version information of the target vehicle according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

[0171] In one embodiment, when the master ECU or the slave ECU has an option component identifier, the computer program further implements the following steps when executed by the processor:

[0172] Based on the mapping relationship, according to the software and hardware version information of the ECU with the optional part identification in the target vehicle, a first candidate mapping relationship including the software and hardware version information of the ECU with the optional part identification is determined; according to the first candidate mapping relationship, according to the software and hardware version information of the main ECU and the remaining ECUs except the ECU with the optional part identification in the slave ECU, the software and hardware version information of the target vehicle is determined.

[0173] In one embodiment, when there are multiple hardware version identifiers in the master ECU or the slave ECU, the computer program further implements the following steps when executed by the processor:

[0174] Based on the mapping relationship, according to the software and hardware version information of the ECU with multiple hardware version identifications in the target vehicle, a second candidate mapping relationship including the software and hardware version information of the ECU with multiple hardware version identifications is determined; according to the second candidate mapping relationship, according to the software and hardware version information of the main ECU and the remaining ECUs except the ECU with multiple hardware version identifications from the ECU, the software and hardware version information of the target vehicle is determined.

[0175] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0176] Determine the software upgrade version corresponding to the software and hardware version information of the target vehicle; obtain the operating status of the target vehicle; and when the operating status of the target vehicle meets the upgrade conditions, use the software upgrade version to upgrade the target vehicle.

[0177] It should be noted that the vehicle's hardware and software information, and the software and hardware information and data of each ECU (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0178] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0179] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0180] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for determining the software and hardware versions of a vehicle, characterized in that: The method is applied to a main electronic control unit ECU in a target vehicle, and the method comprises: Obtaining software and hardware version information of the master ECU and a controller area network (CAN) message reported by a slave ECU in the target vehicle; wherein the CAN message includes at least an ECU identifier and a software and hardware version identifier; Determining software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU; The software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

2. The method according to claim 1, characterized in that The obtaining of software and hardware version information of the master ECU and a controller area network (CAN) message reported by a slave ECU in the target vehicle includes: When the vehicle ignition switch of the target vehicle is in the on state, the software and hardware version information of the master ECU and the controller area network (CAN) message reported by the slave ECU in the target vehicle are obtained.

3. The method according to claim 1, characterized in that The determining the software and hardware version information of the target vehicle according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU includes: Acquire a software and hardware version mapping relationship, wherein the software and hardware version mapping relationship includes a correspondence between software and hardware version information of an ECU in a sample vehicle and software and hardware version information of the sample vehicle, and the vehicle type of the sample vehicle is the same as the vehicle type of the target vehicle; Based on the software and hardware version mapping relationship, the software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

4. The method according to claim 3, characterized in that: In the case where the master ECU or the slave ECU has an optional part identification, the determining the software and hardware version information of the target vehicle based on the software and hardware version mapping relationship according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU includes: Based on the mapping relationship, according to the software and hardware version information of the ECU with the optional part identification in the target vehicle, determine a first candidate mapping relationship including the software and hardware version information of the ECU with the optional part identification; According to the first candidate mapping relationship, the software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the remaining ECUs among the slave ECUs except the ECU with the option part identification.

5. The method according to claim 3, characterized in that: In the case where the master ECU or the slave ECU has multiple hardware version identifiers, the determining the software and hardware version information of the target vehicle based on the mapping relationship and according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU includes: Based on the mapping relationship, according to the software and hardware version information of the ECU with multiple hardware version identifiers in the target vehicle, determine a second candidate mapping relationship including the software and hardware version information of the ECU with multiple hardware version identifiers; According to the second candidate mapping relationship, the software and hardware version information of the target vehicle is determined according to the software and hardware version information of the master ECU and the remaining ECUs in the slave ECUs except the ECU with multiple hardware version identifiers.

6. The method according to claim 1, characterized in that The method further comprises: Determining a software upgrade version corresponding to the software and hardware version information of the target vehicle; Obtaining the operating status of the target vehicle; When the running state of the target vehicle meets the upgrading condition, the target vehicle is upgraded by using the software upgrading version.

7. A device for determining the software and hardware version of a vehicle, characterized in that: The device is configured in a main ECU, and the device comprises: An acquisition module, used to acquire the software and hardware version information of the main ECU and the controller area network CAN message reported by the slave ECU in the target vehicle; wherein the CAN message at least includes an ECU identifier and a software and hardware version identifier; A first determination module, configured to determine the software and hardware version information of the slave ECU according to the CAN message reported by the slave ECU; The second determination module is used to determine the software and hardware version information of the target vehicle according to the software and hardware version information of the master ECU and the software and hardware version information of the slave ECU.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images