Whole vehicle baseline detection method, device, equipment and medium
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- BEIJING CO WHEELS TECH CO LTD
- Filing Date
- 2023-04-20
- Publication Date
- 2026-06-09
AI Technical Summary
Existing technologies cannot effectively determine the differences between two non-adjacent vehicle baseline versions, resulting in low applicability.
By determining the first baseline version number and the second baseline version number to be tested, the ECU type is identified, and the ECU version numbers of the same ECU type in the project are read to obtain the ECU version number set. By querying the different versions, the applicability of the testing method is improved.
It enables the effective identification of differences between two baseline versions under various ECU types based on the baseline version number and item to be detected, thereby improving the applicability of whole vehicle baseline detection.
Smart Images
Figure CN116909244B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of computer technology, and in particular to a method, apparatus, equipment and medium for detecting a vehicle baseline. Background Technology
[0002] With the advancement of the "electrification, connectivity, intelligence, and sharing" of automobiles, their level of electrification is increasing, their software systems are becoming more and more large and complex, and the number of software system version updates is also increasing. During the process of vehicle baseline integration and testing, relevant personnel need to frequently compare the differences between two vehicle baselines.
[0003] The relevant technology mainly involves comparing two adjacent vehicle baseline versions to determine the differences in the ECU (Electronic Control Unit) versions between the two adjacent vehicle baseline versions.
[0004] However, the above method cannot determine the difference between two non-adjacent vehicle baseline versions, resulting in low applicability. Summary of the Invention
[0005] This disclosure aims to at least partially address one of the technical problems in the aforementioned technologies.
[0006] To this end, this disclosure proposes a method, apparatus, device, and medium for detecting a vehicle baseline. This method, in response to user operation, determines a first baseline version number and a second baseline version number to be detected, as well as the item to be detected, wherein the item includes at least one of a software version, a hardware version, and a BT version; determines the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number; reads the first ECU version number and the second ECU version number under the first baseline version used for the same ECU type in the item; obtains a set of ECU version numbers for the ECU type in the item; in response to reading the first ECU version number and the second ECU version number, queries the set of ECU version numbers to obtain the difference version between the first ECU version number and the second ECU version number; and uses the difference version as the difference version between the first baseline version and the second baseline version under the ECU type. Therefore, by simply determining the two baseline version numbers to be tested and the items to be tested, the differences between the baseline versions indicated by the two baseline version numbers to be tested under each ECU type can be effectively determined based on the ECU version number used by the ECU type in the item in the baseline version indicated by the two baseline version numbers to be tested, and the set of ECU version numbers of the ECU type in the item, thereby improving the applicability of the vehicle baseline testing method.
[0007] This disclosure provides a method for detecting a vehicle baseline, comprising: in response to a user operation, determining a first baseline version number and a second baseline version number to be detected, and an item to be detected, wherein the item includes at least one of a software version, a hardware version, and a BT version; determining the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number; reading the first ECU version number and the second ECU version number under the first baseline version used for the same ECU type in the item; obtaining a set of ECU version numbers for the ECU type in the item; in response to reading the first ECU version number and the second ECU version number, querying from the set of ECU version numbers to obtain a difference version between the first ECU version number and the second ECU version number; and using the difference version as the difference version between the first baseline version and the second baseline version under the ECU type.
[0008] A second aspect of this disclosure provides a vehicle baseline detection device, comprising: a first determining module, configured to determine a first baseline version number and a second baseline version number to be detected, and an item to be detected, wherein the item includes at least one of a software version, a hardware version, and a BT version; a second determining module, configured to determine the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number; a reading module, configured to read the first ECU version number under the first baseline version and the second ECU version number under the second baseline version for the same ECU type in the item; an acquiring module, configured to acquire a set of ECU version numbers for the ECU type in the item; a querying module, configured to, in response to reading the first ECU version number and the second ECU version number, query the set of ECU version numbers to obtain the difference version between the first ECU version number and the second ECU version number; and a processing module, configured to use the difference version as the difference version between the first baseline version and the second baseline version under the ECU type.
[0009] A third aspect of this disclosure provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the vehicle baseline detection method described in the first aspect of this disclosure.
[0010] A fourth aspect of this disclosure provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle baseline detection method described in the first aspect of this disclosure.
[0011] A fifth aspect of this disclosure provides a computer program product including computer instructions having a computer program stored thereon, wherein the computer instructions, when executed by a processor, implement the vehicle baseline detection method described in the first aspect of this disclosure.
[0012] The technical solution disclosed herein determines the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number; reads the first ECU version number and the second ECU version number under the first baseline version used in the project for the same ECU type; obtains the set of ECU version numbers for the ECU type in the project; in response to reading the first ECU version number and the second ECU version number, queries the set of ECU version numbers to obtain the difference version between the first ECU version number and the second ECU version number; and uses the difference version as the difference version between the first baseline version and the second baseline version under the ECU type. Therefore, by only determining the two baseline version numbers to be detected and the project to be detected, the difference version of the baseline version indicated by the two baseline version numbers to be detected under each ECU type can be effectively determined based on the ECU version number used in the project for the ECU type in the baseline version indicated by the two baseline version numbers to be detected, and the set of ECU version numbers for the ECU type in the project, thereby improving the applicability of the vehicle baseline detection method.
[0013] Additional aspects and advantages of this disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this disclosure. Attached Figure Description
[0014] The above and / or additional aspects and advantages of this disclosure will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, in which:
[0015] Figure 1 This is a flowchart illustrating a method for detecting a vehicle baseline according to an embodiment of the present disclosure;
[0016] Figure 2 This is a flowchart illustrating a method for detecting a vehicle baseline according to another embodiment of this disclosure;
[0017] Figure 3 A flowchart illustrating the detection method for the vehicle baseline provided in this disclosure;
[0018] Figure 4This is a flowchart illustrating the method for comparing two vehicle baseline version numbers based on ECU type provided in this disclosure.
[0019] Figure 5 This is a schematic diagram of the structure of a vehicle baseline detection device provided according to another embodiment of the present disclosure;
[0020] Figure 6 This is a structural block diagram of an electronic device provided according to another embodiment of the present disclosure. Detailed Implementation
[0021] Embodiments of this disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure.
[0022] This disclosure proposes a method, apparatus, equipment, and medium for detecting the baseline of a vehicle.
[0023] The following description, with reference to the accompanying drawings, describes a method, apparatus, device, and medium for detecting a vehicle baseline according to embodiments of the present disclosure.
[0024] Figure 1 This is a schematic flowchart illustrating a method for detecting a vehicle baseline according to an embodiment of the present disclosure. It should be noted that the method for detecting a vehicle baseline according to this disclosure can be applied to a device for detecting a vehicle baseline according to this disclosure, and this device can be configured on an electronic device.
[0025] like Figure 1 As shown, the detection method for the vehicle baseline may include the following steps:
[0026] Step 101, in response to a user action, determines a first baseline version number and a second baseline version number to be detected, as well as an item to be detected, wherein the item includes at least one of a software version, a hardware version, and a BT (BitTorrent) version.
[0027] In the embodiments of this disclosure, user operations can be touch input (such as swiping, clicking, etc.), keyboard input, voice input, etc., and this disclosure does not limit them.
[0028] In this embodiment of the disclosure, the baseline version number can be used to uniquely identify the baseline version of the vehicle baseline.
[0029] In this embodiment of the disclosure, the project may include at least one of a software version, a hardware version, and a BT version.
[0030] In this embodiment of the disclosure, in response to a user operation, a first baseline version number and a second baseline version number to be detected, as well as the item to be detected, can be determined.
[0031] For example, in response to user input, the first baseline version number to be detected can be determined as S1, the second baseline version number as S2, and the items to be detected are software version and BT version.
[0032] It should be noted that the examples of the baseline version number and the item to be detected mentioned above are merely illustrative. In practical applications, the baseline version number to be detected can also be other, such as the first baseline version to be detected being K0931 and the second baseline version number being S2030. This disclosure does not impose any restrictions on this. Furthermore, in practical applications, the item to be detected can also be other, such as the hardware version or the BT version. The item to be detected can be set according to the needs, and this disclosure does not impose any restrictions on this either.
[0033] It should be noted that the first baseline version number and the second baseline version number may be the same or different, and this disclosure does not impose any restrictions on this.
[0034] In one possible implementation of this disclosure, after determining the first baseline version number and the second baseline version number to be detected, the first baseline version number and the second baseline version number can be compared. If it is determined that the first baseline version number and the second baseline version number are the same, a prompt message can be generated and sent. The prompt message can be used to indicate that the first baseline version number and the second baseline version number to be detected are the same. Therefore, relevant personnel can be prompted in a display manner to promptly modify the input first baseline version number and the second baseline version number to be detected.
[0035] Understandably, if the first baseline version number and the second baseline version number are determined to be different, the subsequent detection process for the vehicle baseline can continue.
[0036] In another possible implementation of the present disclosure, after determining the first baseline version number and the second baseline version number to be detected, the first baseline version number and the second baseline version number can be verified; specifically, it can be determined by querying the target database whether the first baseline version number and the second baseline version number both exist in the target database, wherein the baseline version number can be pre-stored in the target database.
[0037] Understandably, when both the first baseline version number and the second baseline version number exist in the target database, it indicates that both the first baseline version number and the second baseline version number to be detected meet the requirements, and the subsequent detection process can continue.
[0038] This allows for the verification of the first and second baseline version numbers to be tested, so that if both the first and second baseline version numbers meet the requirements, the subsequent testing process can continue.
[0039] In another possible implementation of the present disclosure, items can be preset; after determining the items to be detected, the items to be detected can be verified to determine whether the items to be detected exist in the preset items; when the items to be detected exist in the preset items, it indicates that the items to be detected meet the requirements, and the subsequent detection process can continue.
[0040] This allows for the verification of the items to be tested, so that if the items to be tested are found to meet the requirements, the subsequent testing process can continue.
[0041] Step 102: Determine the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number.
[0042] In this embodiment of the disclosure, a first baseline version number can be used to indicate a first baseline version, while a second baseline version number can be used to indicate a second baseline version.
[0043] In this embodiment of the disclosure, the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number can be determined.
[0044] It should be noted that the ECU types corresponding to the first baseline version and the ECU types corresponding to the second baseline version may be the same or different; this disclosure does not impose any restrictions on this.
[0045] As an example, the first baseline version number is S1, and the second baseline version number is S2. S1 indicates the ECU types corresponding to the first baseline version, including A and B, and S2 indicates the ECU types corresponding to the second baseline version, including A and D. There are ECU types A that are the same, and there are also ECU types B and D that are different.
[0046] As another example, the first baseline version number is S1, and the second baseline version number is S2. S1 indicates that the ECU type corresponding to the first baseline version includes B and C, and S2 indicates that the ECU type corresponding to the second baseline version includes B and C. There are ECU types B and C that are the same.
[0047] In one possible implementation of this disclosure, a relationship table can be queried to determine the first vehicle model corresponding to the first baseline version number and the second vehicle model corresponding to the second baseline version number. The relationship table can pre-store the correspondence between baseline version numbers and vehicle models. Therefore, the ECU type associated with the first vehicle model can be used as the ECU type corresponding to the first baseline version, and the ECU type associated with the second vehicle model can be used as the ECU type corresponding to the second baseline version. This allows for the effective determination of the ECU type corresponding to a baseline version number based on the vehicle model using that baseline version number.
[0048] Step 103: Read the first ECU version number and the second ECU version number of the same ECU type under the first baseline version used in the project and the second baseline version.
[0049] In this embodiment of the disclosure, the first ECU version number under the first baseline version and the second ECU version number under the second baseline version of the same ECU type are read.
[0050] It should be noted that the first ECU version number under the first baseline version used in the project for the same ECU type may or may not exist. That is to say, the first ECU version number under the first baseline version used in the project for the same ECU type may be read, or it may not be read. This disclosure does not impose any restrictions on this.
[0051] Similarly, the second ECU version number under the second baseline version used in the project for the same ECU type may or may not exist. That is, the second ECU version number under the second baseline version used in the project for the same ECU type may be read, or it may not be read. This disclosure does not impose any restrictions on this.
[0052] As an example, suppose the first baseline version number is S1, the second baseline version number is S2, and the item to be detected is the software version. S1 indicates the ECU types corresponding to the first baseline version, which include A and B; S2 indicates the ECU types corresponding to the second baseline version, which include A and D. When reading the first ECU version number and the second ECU version number of ECU type A under the first baseline version and the second baseline version, respectively, for example, we can read that the first ECU version number of ECU type A under the first baseline version and the second ECU version number of the second baseline version are A2 and A4, respectively. When reading the software version... When reading the first ECU version number under the first baseline version and the second ECU version number under the second baseline version used in the project, for example, the first ECU version number of ECU type B under the first baseline version used in the software version is B1, and the second ECU version number under the second baseline version is not read; when reading the first ECU version number of ECU type D under the first baseline version and the second ECU version number under the second baseline version used in the software version project, for example, the second ECU version number of ECU type D under the second baseline version used in the software version is D3, and the first ECU version number under the first baseline version is not read.
[0053] Step 104: Obtain the set of ECU version numbers for the ECU type in the project.
[0054] In this embodiment of the disclosure, an ECU type may have a corresponding set of ECU version numbers on the project, wherein the set of ECU version numbers may include the version number of the starting version of the corresponding ECU type on the project to the version number of the ending version.
[0055] In this embodiment of the disclosure, the set of ECU version numbers corresponding to the ECU type in the project can be obtained. For example, the set of ECU version numbers corresponding to the ECU type in the project can be obtained by querying a database; or, in response to user input, the set of ECU version numbers corresponding to the ECU type in the project can be obtained.
[0056] As an example, suppose the first baseline version number is S1, the second baseline version number is S2, and the item to be detected is the software version. The ECU types corresponding to the first baseline version indicated by S1 include A and B, and the ECU types corresponding to the second baseline version indicated by S2 include A and D. Therefore, since the ECU types include A, B, and D, the set of ECU version numbers for ECU type A in the software version item can be obtained as {A2, A1, A3}. This set of version numbers {A2, A1, A3} includes the version number of the initial version of ECU type A in the software version item. The version number can be obtained up to the termination version; it can also obtain the version number set of ECU type B in the software version project as {B1,B2}, where the version number set {B1,B2} includes the version number of the start version of ECU type B in the software version project to the version number of the termination version; it can also obtain the version number set of ECU type D in the software version project as {D3,D2,D1,D4}, where the version number set {D3,D2,D1,D4} includes the version number of the start version of ECU type D in the software version project to the version number of the termination version.
[0057] Step 105: In response to reading the first ECU version number and the second ECU version number, query the ECU version number set to obtain the difference version between the first ECU version number and the second ECU version number.
[0058] Step 106: Use the difference version as the difference version of the first baseline version and the second baseline version under the ECU type.
[0059] The vehicle baseline detection method of this disclosure, in response to user operation, determines a first baseline version number and a second baseline version number to be detected, as well as an item to be detected, wherein the item includes at least one of a software version, a hardware version, and a BT version; determines the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number; reads the first ECU version number and the second ECU version number under the first baseline version used for the same ECU type in the item; obtains the set of ECU version numbers for the ECU type in the item; in response to reading the first ECU version number and the second ECU version number, queries the set of ECU version numbers to obtain the difference version between the first ECU version number and the second ECU version number; and uses the difference version as the difference version of the first baseline version and the second baseline version under the ECU type. Therefore, by only determining the two baseline version numbers to be detected and the item to be detected, the difference version of the baseline version indicated by the two baseline version numbers to be detected under each ECU type can be effectively determined based on the ECU version number used for the ECU type in the item in the baseline version indicated by the two baseline version numbers to be detected, and the set of ECU version numbers for the ECU type in the item, thereby improving the applicability of the vehicle baseline detection method.
[0060] To clearly illustrate how the above embodiments retrieve the difference between the first ECU version number and the second ECU version number from the ECU version number set, this disclosure also proposes a method for detecting the vehicle baseline.
[0061] Figure 2 This is a schematic flowchart of a method for detecting a vehicle baseline according to another embodiment of the present disclosure.
[0062] like Figure 2 As shown, the detection method for the vehicle baseline may include the following steps:
[0063] Step 201: In response to a user action, determine the first baseline version number and the second baseline version number to be detected, as well as the item to be detected, wherein the item includes at least one of the software version, hardware version, and BT version.
[0064] Step 202: Determine the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number.
[0065] Step 203: Read the first ECU version number and the second ECU version number of the same ECU type under the first baseline version used in the project and the second baseline version.
[0066] Step 204: Obtain the set of ECU version numbers for the ECU type in the project.
[0067] The explanation of steps 201 to 204 can be found in the relevant description in any embodiment of this application, and will not be repeated here.
[0068] Step 205: In response to reading the first ECU version number and the second ECU version number, sort the ECU version numbers in the ECU version number set to obtain the first sorted sequence.
[0069] In this embodiment of the disclosure, when the first ECU version number and the second ECU version number are read, the ECU version numbers in the ECU version number set can be sorted to obtain a first sorting sequence.
[0070] As an example, assume the first baseline version number is S1, the second baseline version number is S2, and the item to be detected is the software version. The ECU types corresponding to the first baseline version indicated by S1 include A and B, and the ECU types corresponding to the second baseline version indicated by S2 include A and D. Read the first ECU version number of ECU type A under the first baseline version used in the software version as A2, and the second ECU version number under the second baseline version as A4. And obtain the set of ECU version numbers of ECU type A in the software version item as {A2, A1, A3}. At this time, the first ECU version number of ECU type A under the first baseline version used in the software version item and the second ECU version number under the second baseline version both exist. Therefore, the ECU version numbers in the set of ECU version numbers of ECU type A in the software version item {A2, A1, A3} can be sorted to obtain the first sorting sequence.
[0071] In one possible implementation of the embodiments of this disclosure, the ECU version numbers in the ECU version number set can be sorted in ascending order; or, the ECU version numbers in the ECU version number set can be sorted in descending order. This disclosure does not limit this.
[0072] For example, suppose the ECU type is B, and the ECU version numbers in the set of ECU version numbers corresponding to this ECU type are B1, B2, B3, and B4. If the ECU version numbers in the set of ECU version numbers corresponding to this ECU type are sorted in ascending order, the first sorting sequence is [B1, B2, B3, B4].
[0073] For example, suppose the ECU type is C, and the ECU version numbers in the set of ECU version numbers corresponding to this ECU type are C1 and C2. If the ECU version numbers in the set of ECU version numbers corresponding to this ECU type are sorted in descending order, the first sorted sequence is [C2, C1].
[0074] Step 206: Based on the first sorting sequence, determine the difference version between the first ECU version number and the second ECU version number.
[0075] As one possible implementation, when the first ECU version number and the second ECU version number are different, the smallest version number can be determined from the first ECU version number and the largest version number. Based on the smallest version number, the first sequence number corresponding to the ECU version number matching the smallest version number can be determined from the first sorting sequence. Based on the largest version number, the second sequence number corresponding to the ECU version number matching the largest version number can be determined from the first sorting sequence. Thus, the difference version between the first sequence number and the second sequence number can be determined from the first sorting sequence, and the difference version between the first sequence number and the second sequence number can be used as the difference version between the first ECU version number and the second ECU version number.
[0076] As an example, suppose the ECU type is B, the first ECU version number is B4, the second ECU version number is B2, and the first sorting sequence is [B1, B2, B3, B4]. In this case, the first ECU version number and the second ECU version number are different. Given this difference, we can determine the smallest version number from B4 and B2 as B2, and the largest version number as B4. Based on the smallest version number B2, we can determine the first sequence number (2) of the ECU version number matching the smallest version number from the first sorting sequence. Based on the largest version number B4, we can determine the second sequence number (4) of the ECU version number matching the largest version number from the first sorting sequence. Therefore, we can extract and obtain the difference version [B2, B3, B4] from the first sorting sequence, and this difference version [B2, B3, B4] can be used as the difference version between the first ECU version number and the second ECU version number.
[0077] It is understandable that when the first ECU version number and the second ECU version number are the same, it can be determined that there is no difference between the first ECU version number and the second ECU version number.
[0078] In another possible implementation of the embodiments of this disclosure, when the first ECU version number is read but the second ECU version number is not read, the first ECU version number can be determined as a different version between the first ECU version number and the second ECU version number; or, when the first ECU version number is not read but the second ECU version number is read, the second ECU version number can be determined as a different version between the first ECU version number and the second ECU version number.
[0079] As an example, suppose the ECU type is C, the first sorting sequence is [C1, C2], and the first ECU version number is read as C2, but the second ECU version number is not read. In this case, the first ECU version number C2 can be identified as the difference between the first ECU version number and the second ECU version number.
[0080] As another example, suppose the ECU type is C, the first sorting sequence is [C1, C2], and the second ECU version number is read as C1, but the first ECU version number is not read. In this case, the second ECU version number C1 can be identified as the difference between the first ECU version number and the second ECU version number.
[0081] Step 207: Use the difference version as the difference version of the first baseline version and the second baseline version under the ECU type.
[0082] The explanation of step 207 can be found in the relevant description in any embodiment of this application, and will not be repeated here.
[0083] The vehicle baseline detection method of this disclosure sorts the ECU version numbers in the ECU version number set to obtain a first sorting sequence; based on the first sorting sequence, it determines the difference version between the first ECU version number and the second ECU version number. Thus, it is possible to effectively obtain the difference version between the first ECU version number and the second ECU version number.
[0084] In any embodiment of this disclosure, such as Figure 3 As shown, the vehicle baseline detection method of this disclosure embodiment can also be implemented based on the following steps:
[0085] 310. Obtain the first vehicle baseline version number (hereinafter referred to as the first baseline version number) and the second vehicle baseline version number (hereinafter referred to as the second baseline version number) to be detected, as well as the difference items to be detected (hereinafter referred to as items).
[0086] It should be noted that, in response to user operations, the system can obtain the first and second vehicle baseline version numbers to be detected, as well as the items to be detected, which may include at least one of the software version, hardware version, and BT version.
[0087] 320. Verify whether the input vehicle baseline version number and difference items meet the requirements.
[0088] The system can verify the input vehicle baseline version number by querying the target database to determine if all input vehicle baseline version numbers exist in the target database. It can also verify the differences to determine if the differences belong to the pre-set settings. When all input vehicle baseline version numbers exist in the target database and the differences belong to the pre-set settings, it indicates that the input vehicle baseline version number and differences meet the requirements, and the subsequent testing process can continue.
[0089] 330. Load the ECU type associated with the first vehicle model corresponding to the first vehicle baseline version number, and use the ECU type associated with the first vehicle model as the ECU type corresponding to the first baseline version indicated by the first vehicle baseline version number; and load the ECU type associated with the second vehicle model corresponding to the second vehicle baseline version number, and use the ECU type associated with the second vehicle model as the ECU type corresponding to the second baseline version indicated by the second vehicle baseline version number.
[0090] It should be noted that the relationship table can be queried to determine the first vehicle model corresponding to the first vehicle baseline version number and the second vehicle model corresponding to the second vehicle baseline version number; the relationship table stores the correspondence between the vehicle baseline version number and the vehicle model in advance.
[0091] 340. Obtain the set of ECU version numbers used for the ECU type in the difference item.
[0092] It should be noted that the ECU version number set can include the version number of the starting version and the version number of the ending version of the corresponding ECU type in the difference item.
[0093] It should also be noted that the set of ECU version numbers used by the ECU types corresponding to the two vehicle baseline version numbers in the difference items can be obtained by searching the database; or the set of ECU version numbers used by the ECU types corresponding to the two vehicle baseline version numbers in the difference items can be obtained through user input.
[0094] 350. Based on the ECU version number set, the differences between two vehicle baseline versions can be compared according to ECU type for the differences that need to be detected.
[0095] Specifically, such as Figure 4As shown, a method for comparing two vehicle baseline version numbers based on ECU type can also be implemented based on the following steps.
[0096] 351. Read the first ECU version number and the second ECU version number under the first vehicle baseline version and the second vehicle baseline version for the same ECU type in the project;
[0097] 352. In response to reading the first ECU version number and the second ECU version number, sort the ECU version numbers in the ECU version number set corresponding to the ECU type in ascending order to obtain the first sorting sequence;
[0098] 353. Based on the first sorting sequence, determine the difference version between the first ECU version number and the second ECU version number;
[0099] For example, if the first ECU version number and the second ECU version number are different, determine the smallest version number from the first ECU version number and the largest version number from the second ECU version number; based on the smallest version number, determine the first sequence number corresponding to the ECU version number that matches the smallest version number from the first sorting sequence; based on the largest version number, determine the second sequence number corresponding to the ECU version number that matches the largest version number from the first sorting sequence; determine the difference version between the first sequence number and the second sequence number from the first sorting sequence; and take the difference version between the first sequence number and the second sequence number as the difference version between the first ECU version number and the second ECU version number.
[0100] For example, if the first ECU version number and the second ECU version number are the same, it can be determined that there is no difference between the first ECU version number and the second ECU version number.
[0101] It should be noted that when the first ECU version number is read but the second ECU version number is not read, the first ECU version number can be identified as the difference between the first ECU version number and the second ECU version number; or, when the first ECU version number is not read but the second ECU version number is read, the second ECU version number can be identified as the difference between the first ECU version number and the second ECU version number.
[0102] 354. Use the difference version as the difference version between the first baseline version and the second baseline version under the ECU type.
[0103] This allows for the comparison or detection of differences between two input vehicle baseline version numbers.
[0104] 360. Send the difference version of each ECU type in the difference item for the input vehicle baseline version number.
[0105] For example, the user inputs the vehicle baseline version numbers to be detected as S1 and S2, and the difference to be detected is the software version. This can be achieved by loading ECU types A and B associated with the first vehicle model that uses S1, and using these ECU types A and B as the ECU types corresponding to the first baseline version indicated by S1; and by loading ECU types A and B associated with the second vehicle model that uses S2, and using these ECU types A and B as the ECU types corresponding to the first baseline version indicated by S2. The system can then read the first ECU version number under the first baseline version and the second ECU version number under the second baseline version for the same ECU type. For example:
[0106] The first ECU version number of ECU type A under the first baseline version in terms of software version is A1, and the first ECU version number under the first baseline version is A3;
[0107] The first ECU version number of ECU type B under the first baseline version in terms of software version is B1, and the first ECU version number under the first baseline version is B1;
[0108] Then, obtain the set of ECU version numbers for the ECU type in the difference item, and sort the ECU version numbers in the set, for example:
[0109] For ECU type A, the set of ECU version numbers corresponding to the software version difference includes versions A1, A2, and A3, which are sorted in ascending order of ECU version number as [A1, A2, A3].
[0110] The ECU version number set corresponding to the software version difference item for ECU type B includes B1 and B2, which are sorted in ascending order of ECU version number as [B1,B2].
[0111] Finally, based on the sorted set of ECU version numbers and the ECU version numbers of each ECU type under the two baseline versions, the difference version is determined:
[0112] The first baseline version indicated by S1 and the second baseline version indicated by S2 have different versions [A1,A2,A3] under ECU type A, but no different versions exist under ECU type B.
[0113] The vehicle baseline detection method disclosed herein, in response to user operation, determines a first baseline version number and a second baseline version number to be detected, as well as items to be detected, wherein the items include at least one of software version, hardware version, and BT version; determines the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number; reads the first ECU version number and the second ECU version number under the first baseline version used for the same ECU type in the item; obtains the set of ECU version numbers for the ECU type in the item; in response to reading the first ECU version number and the second ECU version number, queries the set of ECU version numbers to obtain the difference version between the first ECU version number and the second ECU version number; and uses the difference version as the difference version of the first baseline version and the second baseline version under the ECU type. Therefore, by only determining the two baseline version numbers to be detected and the items to be detected, the difference version of the baseline version indicated by the two baseline version numbers to be detected under each ECU type can be effectively determined based on the ECU version number used for the ECU type in the item in the baseline version indicated by the two baseline version numbers to be detected, and the set of ECU version numbers for the ECU type in the item, thus improving the applicability of the vehicle baseline detection method.
[0114] To implement the above embodiments, this disclosure proposes a detection device for the vehicle baseline.
[0115] Figure 5 This is a schematic diagram of the structure of a vehicle baseline detection device provided according to another embodiment of the present disclosure.
[0116] like Figure 5 As shown, the vehicle baseline detection device 500 includes: a first determination module 510, a second determination module 520, a reading module 530, an acquisition module 540, a query module 550, and a processing module 560.
[0117] The first determining module 510 is used to determine the first baseline version number and the second baseline version number to be detected, as well as the item to be detected, wherein the item includes at least one of software version, hardware version and BT version.
[0118] The second determining module 520 is used to determine the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number.
[0119] The reading module 530 is used to read the first ECU version number under the first baseline version and the second ECU version number under the second baseline version for the same ECU type in the project.
[0120] Module 540 is used to obtain the set of ECU version numbers for the ECU type in the project.
[0121] The query module 550 is used to, in response to reading the first ECU version number and the second ECU version number, query the difference version between the first ECU version number and the second ECU version number from the ECU version number set.
[0122] Processing module 560 is used to treat the difference version as a difference version of the first baseline version and the second baseline version under the ECU type.
[0123] As one possible implementation of this disclosure, the second determining module 520 is specifically used to: query a setting relationship table to determine the first vehicle model corresponding to the first baseline version number and the second vehicle model corresponding to the second baseline version number; wherein, the setting relationship table stores the correspondence between the baseline version number and the vehicle model; taking the ECU type associated with the first vehicle model as the ECU type corresponding to the first baseline version, and taking the ECU type associated with the second vehicle model as the ECU type corresponding to the second baseline version.
[0124] As one possible implementation of this disclosure, the query module 550 is specifically used to: sort the ECU version numbers in the ECU version number set to obtain a first sorting sequence; and based on the first sorting sequence, determine the difference version between the first ECU version number and the second ECU version number.
[0125] As one possible implementation of this disclosure, the query module 550 is further configured to: sort the ECU version numbers in the ECU version number set in ascending order; or, sort the ECU version numbers in the ECU version number set in descending order.
[0126] As a possible implementation of this disclosure, the query module 550 is further configured to: determine the smallest version number from the first ECU version number and the second ECU version number when the first ECU version number and the second ECU version number are different, and determine the largest version number; determine the first sequence number corresponding to the ECU version number matching the smallest version number from the first sorting sequence based on the smallest version number; determine the second sequence number corresponding to the ECU version number matching the largest version number from the first sorting sequence based on the largest version number; determine the difference version between the first sequence number and the second sequence number from the first sorting sequence; and use the difference version between the first sequence number and the second sequence number as the difference version between the first ECU version number and the second ECU version number.
[0127] As one possible implementation of this disclosure, the vehicle baseline detection device 500 further includes:
[0128] The third determining module is used to determine that there is no difference between the first ECU version number and the second ECU version number when both the first ECU version number and the second ECU version number are the same.
[0129] As one possible implementation of this disclosure, the vehicle baseline detection device 500 further includes a fourth determination module.
[0130] The fourth determining module is used to determine the first ECU version number as a different version between the first ECU version number and the second ECU version number in response to reading the first ECU version number but not reading the second ECU version number; or, in response to not reading the first ECU version number but reading the second ECU version number, to determine the second ECU version number as a different version between the first ECU version number and the second ECU version number.
[0131] As one possible implementation of this disclosure, the vehicle baseline detection device 500 further includes a verification module.
[0132] The fifth determining module is used to query the target database to determine that both the first baseline version number and the second baseline version number exist in the target database; the target database stores the baseline version number.
[0133] The vehicle baseline detection device of this disclosure determines, in response to user operation, a first baseline version number and a second baseline version number to be detected, as well as an item to be detected, wherein the item includes at least one of a software version, a hardware version, and a BT version; determines the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number; reads the first ECU version number and the second ECU version number under the first baseline version used for the same ECU type in the item; obtains a set of ECU version numbers for the ECU type in the item; in response to reading the first ECU version number and the second ECU version number, queries the ECU version number set to obtain the difference version between the first ECU version number and the second ECU version number; and uses the difference version as the difference version between the first baseline version and the second baseline version under the ECU type. Therefore, by simply determining the two baseline version numbers to be tested and the items to be tested, the differences between the baseline versions indicated by the two baseline version numbers to be tested under each ECU type can be effectively determined based on the ECU version number used by the ECU type in the item in the baseline version indicated by the two baseline version numbers to be tested, and the set of ECU version numbers of the ECU type in the item, thereby improving the applicability of the vehicle baseline testing method.
[0134] It should be noted that the foregoing explanation of the method embodiments also applies to the apparatus of this embodiment, and will not be repeated here.
[0135] To implement the above embodiments, this disclosure also proposes an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the vehicle baseline detection method described in the above embodiments.
[0136] To implement the above embodiments, this disclosure also proposes a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the vehicle baseline detection method described in the above embodiments.
[0137] To implement the above embodiments, this disclosure also proposes a computer program product having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the vehicle baseline detection method described in the above embodiments.
[0138] Figure 6 This is a structural block diagram of an electronic device provided according to another embodiment of the present disclosure. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.
[0139] like Figure 6 As shown, the electronic device 600 includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from memory 606 into a random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the electronic device 600. The processor 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.
[0140] The following components are connected to I / O interface 605: memory 606 including hard disk; and communication section 607 including network interface card such as LAN (Local Area Network) card, modem, etc., which performs communication processing via a network such as the Internet; and driver 608 is also connected to I / O interface 605 as needed.
[0141] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 607. When the computer program is executed by processor 601, it performs the functions defined in the methods of this disclosure.
[0142] In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory 606 including instructions, which can be executed by a processor 601 of an electronic device 600 to perform the above-described method. Optionally, the storage medium may be a non-transitory computer-readable storage medium, such as a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device.
[0143] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this disclosure. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.
[0144] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.
[0145] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of preferred embodiments of this disclosure includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as will be understood by those skilled in the art to which embodiments of this disclosure pertain.
[0146] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.
[0147] It should be understood that various parts of this disclosure can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.
[0148] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.
[0149] Furthermore, the functional units in the various embodiments of this disclosure can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.
[0150] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present disclosure.
Claims
1. A method for detecting the baseline of a vehicle, characterized in that, The method includes: In response to a user action, a first baseline version number and a second baseline version number to be detected, as well as an item to be detected, wherein the item includes at least one of a software version, a hardware version, and a bitstream BT version; Determine the type of electronic control unit (ECU) corresponding to the first baseline version indicated by the first baseline version number and the type of ECU corresponding to the second baseline version indicated by the second baseline version number; Read the first ECU version number and the second ECU version number of the same ECU type under the first baseline version and the second baseline version used in the project; Obtain the set of ECU version numbers corresponding to the ECU type in the project; In response to reading the first ECU version number and the second ECU version number, the difference version between the first ECU version number and the second ECU version number is retrieved from the ECU version number set; The difference version is used as the difference version between the first baseline version and the second baseline version under the ECU type.
2. The method according to claim 1, characterized in that, The step of determining the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number includes: The relationship table is queried to determine the first vehicle model corresponding to the first baseline version number and the second vehicle model corresponding to the second baseline version number; wherein, the relationship table stores the correspondence between baseline version numbers and vehicle models; The ECU type associated with the first vehicle model is used as the ECU type corresponding to the first baseline version, and the ECU type associated with the second vehicle model is used as the ECU type corresponding to the second baseline version.
3. The method according to claim 1, characterized in that, The step of retrieving the difference version between the first ECU version number and the second ECU version number from the ECU version number set includes: Sort the ECU version numbers in the ECU version number set to obtain a first sorting sequence; Based on the first sorting sequence, the difference version between the first ECU version number and the second ECU version number is determined.
4. The method according to claim 3, characterized in that, The step of sorting the ECU version numbers in the ECU version number set includes: The ECU version numbers in the set of ECU version numbers are sorted in ascending order. or, The ECU version numbers in the set of ECU version numbers are sorted in descending order.
5. The method according to claim 3, characterized in that, The step of determining the difference version between the first ECU version number and the second ECU version number based on the first sorting sequence includes: If the first ECU version number and the second ECU version number are different, determine the smallest version number from the first ECU version number and the largest version number from the second ECU version number; Based on the minimum version number, determine the first sequence number corresponding to the ECU version number that matches the minimum version number from the first sorting sequence; Based on the maximum version number, determine the second sequence number corresponding to the ECU version number that matches the maximum version number from the first sorting sequence; Determine the difference version between the first sequence number and the second sequence number from the first sorting sequence; The version that differs between the first serial number and the second serial number is taken as the version that differs between the first ECU version number and the second ECU version number.
6. The method according to claim 5, characterized in that, The method further includes: If the first ECU version number and the second ECU version number are the same, it is determined that there is no difference between the first ECU version number and the second ECU version number.
7. The method according to claim 5, characterized in that, The method further includes: In response to reading the first ECU version number but not reading the second ECU version number, the first ECU version number is determined to be the difference version between the first ECU version number and the second ECU version number; or, In response to the failure to read the first ECU version number, the second ECU version number is read and determined to be the difference version between the first ECU version number and the second ECU version number.
8. The method according to any one of claims 1-5, characterized in that, After determining at least two baseline version numbers to be detected, the method further includes: Query the target database to determine whether both the first baseline version number and the second baseline version number exist in the target database; wherein, the target database stores the baseline version number.
9. A detection device for a vehicle baseline, characterized in that, The device includes: The first determining module is used to determine the first baseline version number and the second baseline version number to be detected, as well as the item to be detected, wherein the item includes at least one of software version, hardware version and BT version; The second determining module is used to determine the ECU type corresponding to the first baseline version indicated by the first baseline version number and the ECU type corresponding to the second baseline version indicated by the second baseline version number. The reading module is used to read the first ECU version number under the first baseline version and the second ECU version number under the second baseline version for the same ECU type in the project. The acquisition module is used to acquire the set of ECU version numbers of the ECU type in the project; The query module is used to, in response to reading the first ECU version number and the second ECU version number, query the difference version between the first ECU version number and the second ECU version number from the ECU version number set; A processing module is configured to use the difference version as the difference version between the first baseline version and the second baseline version under the ECU type.
10. An electronic device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the vehicle baseline detection method according to any one of claims 1-8.
11. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform a method for detecting a vehicle baseline as described in any one of claims 1-8.
12. A computer program product comprising computer program instructions that, when executed by a processor, implement the method for detecting a vehicle baseline as described in any one of 1-8.