Method, system, medium and product for judging upgrade state of vehicle end module

Abstract

The invention relates to the field of vehicles, in particular to a method and system for judging the upgrade state of a vehicle end module, a computer readable storage medium and a computer program product. The method comprises the following steps: determining a part number of a vehicle end module; determining the name of an electronic control unit associated with the vehicle end module based on a preset rule; determining a target part number of a vehicle end module corresponding to the name of the electronic control unit according to the vehicle configuration and the module version information; and comparing the part number of the vehicle end module with the target part number to judge the upgrading state of the vehicle end module.

Description

Technical Field

[0001] The present application relates to the field of vehicles, and more particularly, to a method, a system, a computer-readable storage medium, and a computer program product for determining the upgrade status of in-vehicle modules. Background Art

[0002] During the process of vehicle R & D and testing, the versions of in-vehicle modules on the vehicle are continuously upgraded (for example, iterated, replaced) with the progress of development. These modules are connected to different electronic control units (ECUs, Electronic Control Unit), enabling drivers or vehicle systems to control the operation of these modules. During the test cycle, some modules on the test vehicle are also upgraded according to the actual test scenarios. R & D testers need to understand the information of the currently used modules to judge the effect of module upgrades. During the process of obtaining the information of these modules, due to the different sources of various modules and the corresponding acquisition devices, data of different formats, quantities, and types may be obtained, making it difficult for R & D testers to quickly and accurately review the situation and effect of module upgrades to evaluate the status of the test vehicle.

[0003] It should be noted that the information disclosed in the above background art section is only used to enhance the understanding of the background of the present application, and thus may include information that does not constitute the prior art known to those of ordinary skill in the art. Summary of the Invention

[0004] To solve or at least alleviate one or more of the above problems, the following technical solutions are provided. Embodiments of the present application provide a method, a system, a computer-readable storage medium, and a computer program product for determining the upgrade status of in-vehicle modules, thereby enabling a simple, fast, and reliable evaluation of the upgrade status of the current in-vehicle modules.

[0005] According to a first aspect of the present application, there is provided a method for determining the upgrade status of in-vehicle modules, the method including: determining the part number of the in-vehicle module; determining the name of the ECU associated with the in-vehicle module based on a preset rule; determining the target part number of the in-vehicle module corresponding to the name of the ECU according to vehicle configuration and module version information; comparing the part number of the in-vehicle module with the target part number to determine the upgrade status of the in-vehicle module.

[0006] As an alternative or supplement to the above solution, in the status determination method according to an embodiment of the present application, determining the part number of the in-vehicle module includes: determining the data type of the part number of the in-vehicle module according to the data characteristics of the part number of the in-vehicle module; and adjusting the part number of the in-vehicle module according to the data type.

[0007] As an alternative or supplement to the above solution, in the status determination method according to an embodiment of the present application, the part number of the vehicle end module is the part number before the upgrade of the vehicle end module, and wherein, determining the upgrade status of the vehicle end module includes determining whether the vehicle end module needs to be upgraded.

[0008] As an alternative or supplement to the above solution, in the status determination method according to an embodiment of the present application, the part number of the vehicle end module is the part number after the upgrade of the vehicle end module, and wherein, determining the upgrade status of the vehicle end module includes determining whether the vehicle end module meets the requirements after the upgrade.

[0009] As an alternative or supplement to the above solution, in the status determination method according to an embodiment of the present application, the preset rules include: determining whether the part number of the vehicle end module includes an ECU identifier; and if the part number of the vehicle end module includes an ECU identifier, determining the name of the ECU as the name of the ECU corresponding to the ECU identifier in the custom library.

[0010] As an alternative or supplement to the above solution, in the status determination method according to an embodiment of the present application, the preset rules include: determining whether the part number of the vehicle end module includes the name of the module; and if the part number of the vehicle end module includes the name of the module, determining the name of the ECU as the name of the ECU corresponding to the name of the module in the vehicle configuration.

[0011] As an alternative or supplement to the above solution, in the status determination method according to an embodiment of the present application, the preset rules include: determining whether the part number of the vehicle end module includes the name of the ECU; and if the part number of the vehicle end module includes the name of the ECU, determining the name of the ECU as the name of the ECU included in the part number of the vehicle end module.

[0012] As an alternative or supplement to the above solution, in the status determination method according to an embodiment of the present application, the preset rules include: if the part number of the vehicle end module does not include the name of the ECU, determining the name of the ECU as the name of the default ECU.

[0013] As an alternative or supplement to the above solution, in the status determination method according to an embodiment of the present application, the method further includes: determining the pre-upgrade abnormal diagnosis code and the post-upgrade abnormal diagnosis code; classifying and summarizing the pre-upgrade abnormal diagnosis code and the post-upgrade abnormal diagnosis code; comparing the classified and summarized pre-upgrade abnormal diagnosis code and the post-upgrade abnormal diagnosis code to determine the effect of the upgrade.

[0014] As an alternative or supplement to the above solution, in the status determination method according to an embodiment of the present application, the custom library includes key-value pairs of pre-set ECU identifiers and ECU names, and wherein, the method further includes updating the key-value pairs of the ECU identifiers and ECU names in the custom library based on an external input.

[0015] According to a second aspect of the present application, there is provided a system for determining the upgrade status of a vehicle-end module, the system including: a processor; a memory; and a computer program, the computer program being stored on the memory and being executable on the processor, the execution of the computer program causing any one of the methods described in the first aspect of the present application to be executed.

[0016] According to a third aspect of the present application, there is provided a computer-readable storage medium, the computer-readable storage medium including instructions that, when running, execute any one of the methods described in the first aspect of the present application.

[0017] According to a fourth aspect of the present application, there is provided a computer program product, the computer program product including instructions that, when running, execute any one of the methods described in the first aspect of the present application.

[0018] The method for determining the upgrade status of a vehicle-end module according to one or more embodiments of the present application uses the name of the ECU as a bridge to associate the actually collected part number with the target part number, so as to perform accurate comparison subsequently. In the case of a large number of vehicle part numbers, the calculation amount and time required for associating part numbers are reduced, thereby reducing the burden on the reviewers and realizing a simple, fast, and reliable evaluation of the upgrade status of all vehicle modules, so as to avoid handing over vehicles with abnormal status. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and / or other aspects and advantages of the present application will become clearer and easier to understand through the following description of various aspects in conjunction with the drawings, where the same or similar units are denoted by the same reference numerals. In the said drawings:

[0020] Figure 1 is a schematic flowchart of a method for determining the upgrade status of a vehicle-end module according to one or more embodiments of the present application;

[0021] Figure 2 is a flowchart of a preset rule for determining the name of an ECU associated with a vehicle-end module according to one or more embodiments of the present application;

[0022] Figure 3 is a schematic block diagram of a system for determining the upgrade status of a vehicle-end module according to one or more embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0023] The description of the following specific embodiments is merely exemplary in nature and is not intended to limit the disclosed technology or the application and use of the disclosed technology. In addition, it is not intended to be bound by any express or implied theory presented in the aforementioned technical field, background technology or the following specific embodiments.

[0024] In the following detailed description of the embodiments, many specific details are set forth in order to provide a more thorough understanding of the disclosed technology. However, it is apparent to one of ordinary skill in the art that the disclosed technology can be practiced without these specific details. In other instances, well-known features are not described in detail to avoid unnecessarily complicating the description.

[0025] Terms such as "having" and "including" indicate that in addition to the units (modules) and steps that are directly and clearly stated in the specification and claims, the technical solution of the present application does not exclude the situation where there are other units (modules) and steps that are not directly or clearly stated. Terms such as "first" and "second" do not indicate the order of units in terms of time, space, size, etc., but are only used to distinguish each unit. Moreover, the steps in this article are not limited to being implemented in the order of writing, but the steps written later can also be implemented at the same time as the steps written earlier, or before the steps written earlier.

[0026] The vehicle-side module is an important part of the vehicle. During the vehicle development and testing process, the vehicle-side module may undergo multiple rounds of upgrades, and each upgrade of the vehicle-side module needs to be recorded for process management and quality control. These vehicle-side modules are connected to various ECUs, which are responsible for controlling and monitoring various functions of the vehicle, such as engine management, braking system, body control, etc. In order to be able to identify and reference these ECUs during vehicle development, testing and maintenance, these ECUs have corresponding names (for example, named by function, by location, etc.). In addition, each ECU has a unique ECU identifier (ID). Similarly, during the vehicle-side module upgrade process, each vehicle-side module has a unique part number (PN, PartNumber). In addition to playing the role of identification, these PNs may also explicitly or implicitly express other information, such as production date, manufacturer, module name, ECU connected to the module, etc. If the original vehicle-side module is replaced with a new vehicle-side module during the upgrade process, the new vehicle-side module will retain the same name as the original vehicle-side module, but correspond to a new PN. In other words, the name of the vehicle-side module is fixed, while the PN will change as the module is upgraded. Therefore, PN is an important reference when judging the upgrade status and version information of the vehicle-side module.

[0027] The name of the vehicle-end module and which ECUs these modules are associated with can be included in the vehicle configuration. The target PN of the vehicle-end module associated with the ECU can be included in the module version information. By comparing the current actual PN and the target PN of the vehicle-end module, the upgrade status of the vehicle-end module can be understood. For example, before the upgrade, if the actual PN of the vehicle-end module is the same as the target PN, it indicates that the vehicle-end module does not need to be upgraded. If the actual PN of the vehicle-end module is different from the target PN, it indicates that the vehicle-end module may need to be upgraded. Or after the upgrade, if the actual PN of the vehicle-end module is the same as the target PN, it indicates that the upgrade of the vehicle-end module meets the requirements. If the actual PN of the vehicle-end module is different from the target PN, it indicates that the upgrade of the vehicle-end module does not meet the requirements.

[0028] Figure 1 is a schematic flowchart of a method for judging the upgrade status of a vehicle-end module according to one or more embodiments of the present application. As Figure 1 shown, in step S1, the information of the vehicle-end module is imported through the acquisition device to determine the PN of the vehicle-end module. These PNs will then be used as the actual PNs of the vehicle-end module and compared with the corresponding target PNs to determine the upgrade status of the vehicle-end module. Since the sources of vehicle-end modules are extensive, there may be huge format differences between the PNs of different vehicle-end modules. In some embodiments, some processing can be performed on these PNs. For example, the validity of the PN can be judged. For PN data with a null value, it can be marked, an error warning can be issued, or it can be filled with a default value to ensure the integrity of the PN data. In addition, in some embodiments, the data type of the PN of the vehicle-end module can be determined according to the data characteristics of the PN of the vehicle-end module, and the PN of the vehicle-end module can be adjusted according to this data type, such as padding, assignment, or order adjustment, etc., to generate templatized PN data with a unified format, thereby avoiding data anomalies caused by different formats.

[0029] In step S1, the PNs of a large number of vehicle-end modules are determined. These PNs usually include numbers and letters and are unclassified data. Compared with the number of vehicle-end modules in the whole vehicle, the number of vehicle-end modules connected to the same ECU is much smaller. Therefore, if the name of the ECU associated with these vehicle-end modules is known, it will be much easier to compare the actual PN and the target PN of the vehicle-end module subsequently.

[0030] Then, in step S2, based on the preset rules, the name of the ECU associated with the vehicle-end module is determined. Through step S2, the PNs of the vehicle-end modules determined in step S1 can be classified and aggregated according to the name of the ECU associated with the vehicle-end module. After determining the name of the ECU associated with the vehicle-end module, with the name of the ECU as the limit, the number of target PNs to be compared subsequently can be reduced, and the matching accuracy can be improved.

[0031] In step S3, according to the vehicle configuration and module version information, determine the target PN of the vehicle-end module corresponding to the name of the ECU. For a specific vehicle, the names of all ECUs included in the vehicle and the target PNs of all vehicle-end modules can be found.

[0032] In step S4, compare the PN of the vehicle-end module determined in step S1 with the target PN determined in step S3 to judge the upgrade status of the vehicle-end module. If the PN of the vehicle-end module is inconsistent with the target PN, report an error or issue a warning to remind that the vehicle-end module needs to be upgraded or the upgrade of the vehicle-end module does not meet the requirements, so as to facilitate the engineer to quickly review the upgrade status of the vehicle-end module. Optionally, the situation of abnormal upgrade of the vehicle-end module can be recorded and displayed through an output device.

[0033] In some embodiments, in addition to the upgrade of the vehicle-end module, the software of the vehicle can also be upgraded. Whether the software can be accurately released is directly related to the effectiveness of the test. When the software runs abnormally, the value of the abnormal diagnostic code (DTC, Diagnostic Trouble Code) can be read through a diagnostic tool to determine what specific faults have occurred. In addition, after the module changes, new software faults may occur, or the original faults may be eliminated. By comparing the DTCs before and after the module change, it can be judged which faults are introduced or eliminated by the module upgrade and whether the effect of the module upgrade meets the expectation.

[0034] Similarly, the method can also help reviewers quickly and accurately judge whether the states of all vehicle modules meet the requirements of the target version and conduct vehicle quality control by processing and matching the DTC files before and after the upgrade. Specifically, the method further includes determining the DTC before the upgrade and the DTC after the upgrade. In this step, the DTCs of different file types and different file formats need to be uniformly set to the built-in template format for subsequent automatic recognition and acquisition of the DTC content. Subsequently, the method includes classifying and summarizing the DTCs before the upgrade and the DTCs after the upgrade. During the classification and summarization process, these DTCs can also be associated with the names of the corresponding ECUs, so as to more intuitively reflect the upgrade situation of each part. Subsequently, the method includes comparing the classified and summarized DTCs before the upgrade and the DTCs after the upgrade to judge the effect of the upgrade. If many original DTCs are eliminated after the upgrade or the number of DTCs after the upgrade is small, this upgrade may be successful.

[0035] However, due to the high variability during the development process, there may be no authoritative specification or basis for naming the ECUs. This makes it difficult to determine the name of the ECU associated with the vehicle-end module in step S2. Specifically, there may be multiple sources for determining the name of the ECU associated with the vehicle-end module, and the names of the ECUs in these multiple sources may not be standardized or unified; or the ECU may not be found based on the name of the ECU in some sources in the vehicle configuration and module version information. Therefore, on the one hand, the preset rule in step S2 should consider accurately setting the priorities of multiple sources to avoid conflicts when the names in multiple sources are inconsistent; on the other hand, it should also consider the comprehensiveness of the coverage of the ECU name to prevent the situation where the name of the ECU associated with the vehicle-end module cannot be determined.

[0036] Figure 2 is a flowchart of a preset rule for determining the name of the ECU associated with the vehicle-end module according to one or more embodiments of the present application. As mentioned above, the PN of the vehicle-end module may indicate information about the ECU connected to the module. For example, the PN may contain the ECU ID, the name of the module, the name of the ECU, and the like. Based on this information, the name of the ECU associated with the vehicle-end module can be determined directly or indirectly from multiple sources. The multiple sources include a preset custom library, vehicle configuration and module version information, the PN itself, and default values, etc.

[0037] However, the reliability of these multiple sources is different from each other, and the potential matching probabilities also vary. By setting appropriate priorities, the association efficiency and accuracy of the PN and the name of the ECU can be improved, and the computational amount during the association process can be reduced. For example, as mentioned above, the vehicle-end modules may come from different suppliers (especially for newly developed vehicle models), and the naming rules for ECUs by each supplier vary greatly. Therefore, the name of the ECU included in the PN of the vehicle-end module itself is not standardized, and the non-standardized name of the ECU cannot play an accurate limiting role. In contrast, the names of the ECUs in the vehicle configuration and module version information are usually more standardized. Further, for the reviewers, the custom library can be customized by themselves and can be updated and modified according to external inputs as the development progresses. The custom library may include key-value pairs of the ECU ID and the name of the ECU. For different vehicle models or naming rules, the name of the ECU corresponding to the ECU ID can be modified based on external inputs. Therefore, using the custom library as a source for determining the name of the ECU is flexible and convenient.

[0038] In some embodiments, the preset rule may be in the order illustrated in Figure 2 In step S210, first, it is judged whether in Figure 1Whether the ECU ID is included in the PN of the vehicle end module determined in step S1. If the ECU ID is included in the PN, proceed to step S220; otherwise, proceed to step S240. In step S220, determine whether the ECU ID is included in the custom library. If so, proceed to step S230; otherwise, also proceed to step S240. In step S230, determine the name of the ECU associated with the vehicle end module as the name of the ECU corresponding to the ECU ID in the custom library. In this way, the priority of the custom library is set to the highest when determining the name of the ECU associated with the vehicle end module. In step S240, determine whether the name of the module is included in the PN. If so, proceed to step S250; otherwise, proceed to step S270. In step S250, determine whether the name of the module exists in the vehicle configuration. If so, proceed to step S260; otherwise, also proceed to step S270. In step S260, determine the name of the ECU as the name of the ECU corresponding to the name of the module in the vehicle configuration. In step S270, determine whether the name of the ECU is included in the PN. If so, proceed to step S290; otherwise, proceed to step S280. In step S290, determine the name of the ECU as the name of the ECU included in the PN. In step S280, determine the name of the ECU as the name of the default ECU. Note that in this way, the priority of the default value is set to the lowest. This can ensure that the name of the ECU associated with the vehicle end module in step S2 is not null when none of the above cases match the standard ECU name, and finally manually match the PN of these vehicle end modules and the target PN separately.

[0039] The scalability and compatibility of the system are improved by setting multiple sources for the name of the ECU (especially the setting of the custom library). In some embodiments, various different situations can be handled by adjusting the priorities of multiple sources. For example, for traditional and mature vehicle platforms and conventional modules, the determined PN may already be relatively standardized. At this time, the priority of the name of the ECU included in the PN can be increased; while for newly developed vehicle models and newly introduced modules, the priority of the name of the ECU in the custom library can be increased, thereby further improving the method.

[0040] Figure 3 is a schematic block diagram of a system 30 for determining the upgrade status of a vehicle end module according to one or more embodiments of the present application. In Figure 3 it, the system 30 includes a memory 310, a processor 320, and a computer program 330. The computer program 330 is stored on the memory 310 and can be run by the processor 320. The running of the computer program 330 enables as Figure 1In some embodiments, the state judgment system 30 further includes an output device, such as a display, to output the state judgment method shown in FIG. Figure 1 In some embodiments, the memory 310 may be an external storage medium connected to the state judgment system 30 through an interface, such as a computer storage device in various forms such as a disk (e.g., a magnetic disk, an optical disk, etc.), a card (e.g., a memory card, an optical card, etc.), a semiconductor memory (e.g., a ROM, a non-volatile memory, etc.), a tape (e.g., a magnetic tape, a cassette tape, etc.), etc.

[0041] Software according to the present application may be stored on one or more computer-readable storage media or made into one or more computer program products. It is also contemplated that the software identified herein may be implemented using one or more general or special-purpose computers and / or computer systems networked and / or otherwise. Where applicable, the order of the various steps described herein may be changed, combined into composite steps and / or divided into sub-steps to provide the features described herein.

[0042] The embodiments and examples set forth herein are provided to best illustrate embodiments according to the present application and its specific applications, and thereby enable those skilled in the art to implement and use the present application. However, those skilled in the art will appreciate that the above description and examples are provided only for ease of illustration and example. The description set forth is not intended to cover all aspects of the present application or to limit the present application to the precise form disclosed.

Claims

1. A method for determining an upgrade status of a vehicle-side module, the method comprising: Determine the part number of the vehicle-side module; Determining, based on a preset rule, a name of an electronic control unit associated with the vehicle-side module; Determining a target part number of a vehicle-side module corresponding to the name of the electronic control unit according to the vehicle configuration and the module version information; The part number of the vehicle-end module is compared with the target part number to determine the upgrade status of the vehicle-end module.

2. The method of claim 1, wherein: Determining the part number of the vehicle-end module includes: Determining the data type of the part number of the vehicle-end module according to the data characteristics of the part number of the vehicle-end module; and The part number of the vehicle-side module is adjusted according to the data type.

3. The method of claim 1, wherein: The part number of the vehicle-end module is the part number of the vehicle-end module before being upgraded, and wherein determining the upgrade status of the vehicle-end module includes determining whether the vehicle-end module needs to be upgraded.

4. The method of claim 1, wherein: The part number of the vehicle-end module is the part number of the vehicle-end module after upgrading, and wherein, determining the upgrade status of the vehicle-end module includes determining whether the vehicle-end module meets the requirements after upgrading.

5. The method of claim 1, wherein: The preset rules include: determining whether the part number of the vehicle-side module includes an electronic control unit identifier; and If the part number of the vehicle-side module includes an electronic control unit identifier, the name of the electronic control unit is determined to be a name of an electronic control unit corresponding to the electronic control unit identifier in a custom library.

6. The method of claim 5, wherein: The preset rules include: Determining whether the part number of the vehicle-side module includes the name of the module; and If the part number of the vehicle-side module includes the name of the module, the name of the electronic control unit is determined to be the name of the electronic control unit corresponding to the name of the module in the vehicle configuration.

7. The method of claim 6, wherein: The preset rules include: Determining whether the part number of the vehicle-side module includes the name of the electronic control unit; and If the part number of the vehicle-end module includes the name of the electronic control unit, the name of the electronic control unit is determined to be the name of the electronic control unit included in the part number of the vehicle-end module.

8. The method of claim 7, wherein: The preset rules include: The name of the electronic control unit is determined as the name of a default electronic control unit.

9. The method of claim 1, further comprising: Determine the abnormal diagnostic code before the upgrade and the abnormal diagnostic code after the upgrade; Classify and summarize the abnormal diagnosis codes before and after the upgrade; The classified and summarized abnormal diagnosis codes before the upgrade are compared with the abnormal diagnosis codes after the upgrade to determine the effect of the upgrade.

10. The method of claim 5, wherein: The custom library includes preset key-value pairs of electronic control unit identifiers and names of electronic control units, and wherein the method further includes updating the key-value pairs of the electronic control unit identifiers and names of electronic control units in the custom library based on external input.

11. A system for determining the upgrade status of a vehicle-side module, the system comprising processor; Memory; as well as A computer program is stored on the memory and can be run on the processor, and the execution of the computer program causes the method according to any one of claims 1 to 10 to be performed.

12. A computer-readable storage medium, the computer-readable storage medium comprising instructions, the instructions executing the method according to any one of claims 1 to 10.

13. A computer program product, comprising instructions, which when executed, execute the method according to any one of claims 1 to 10.

Images