Method for determining program upgrading version number of vehicle-mounted controller

Abstract

The invention relates to a method for determining a program upgrading version number of a vehicle-mounted controller, and belongs to the technical field of vehicle-mounted controllers. According to the method, the relationship between the upgrade version number parameter and the old version number parameter of the vehicle-mounted controller program is introduced, and the upgrade version number determined through the relationship can reflect the parameters related to the change under the program change; the unique upgrading version number is determined through the relationship between the upgrading version number parameter of the upgrading version and the old version number parameter of the old version which are unique, one-to-one corresponding and capable of reflecting the change parameters and the known old version number parameter, and the relationship endows the underlying logic behind the upgrading version number to be unique and clear. According to the scheme, the unique and accurate upgrading version number can be obtained through the known relation and the known old version number parameter, the unique and accurate old version number can also be obtained through the known relation and the known upgrading version number parameter, the accurate upgrading version number can be efficiently obtained based on the scheme, and the program updating efficiency and accuracy are improved.

Description

Technical Field

[0001] The invention relates to a method for determining an upgraded version number of a vehicle-mounted controller program, and belongs to the technical field of vehicle-mounted controllers. Background Art

[0002] Due to the complex and diverse operating conditions of new energy mining vehicles (such as heavy-load uphill or heavy-load downhill conditions) and the diverse needs of customers (such as power, economy, etc.), there is a great demand for various on-board controller program upgrades after the vehicle is sold. In the past, when encountering such needs, technicians or after-sales personnel were required to go on-site to upgrade the on-board controller program of the actual vehicle. This method not only failed to meet customer needs in a timely manner, but also increased the company's operating costs. Therefore, applying OTA (Over-the-Air Technology) to on-board controller upgrades, such as in new energy mining vehicles, can provide customers and car companies with a more convenient upgrade method.

[0003] Remote upgrade of vehicle controllers is one of the emerging technologies in automobiles in recent years. It can complete the upgrade of vehicle controller software by downloading upgrade packages through mobile networks, thereby fixing vulnerabilities in vehicle controller software, improving existing functions, and enhancing performance.

[0004] However, there is a key technical issue between the mature on-board controller remote upgrade solutions currently on the market and traditional on-board controller upgrade solutions. The upgrade version number of the on-board controller program is A1A2.B1B2.C1C2D1D2E1E2 (each parameter in the upgrade version number is in hexadecimal, where A1A2 is the major version number of the upgrade version, B1B2 is the minor version number of the upgrade version, C1C2 is the application layer program code of the upgrade version, D1D2 is the modification information number of the upgrade version, and E1E2 is the bottom layer version number of the upgrade version). The known parameters of the old version number of the on-board controller program currently in use are as follows:

[0005] Major version number: a1a2 (major version number is in hexadecimal, range: 0-FF); minor version number: b1b2 (minor version number is in hexadecimal, range: 0-FF); application layer program code: c1c2 (application layer program code is in hexadecimal, range: 0-FF); modification information number: d1d2 (modification information number is in hexadecimal, range: 0-3C); bottom layer version number: e0e1e2 (bottom layer version number is in hexadecimal, range: 0-0xFFF) ); Application layer version date number: t1t2t3t4t5t6 (after the application layer version date is converted to hexadecimal, t1t2 corresponds to the hexadecimal range: 0-63, t3t4 corresponds to the hexadecimal range: 0-C, t5t6 corresponds to the hexadecimal range: 0-1F; among them: t1t2 is the year, corresponding to the decimal range: 0-99, t3t4 is the month, corresponding to the decimal range: 0-12; t5t6 is the day, corresponding to the decimal range: 0-31).

[0006] The relationship between the old version number parameters of the currently used vehicle controller program and the upgraded version number parameters of the vehicle controller program upgrade is as follows:

[0007] A1A2=a1a2

[0008] B1B2=b1b2

[0009] C1C2=c1c2

[0010] D1D2=4*d1d2+e0

[0011] E1E2=e1e2

[0012] Currently, the vehicle controller controls the vehicle controller program primarily through the application layer program code c1c2, the underlying version number e0e1e2, and the application layer version date t1t2t3t4t5t6. Other parameters are not involved when the program is changed, and the application layer version date is not reflected in the version number of the existing program upgrade version. The existing program naming method conflicts with the existing program management method. Therefore, when the vehicle controller program needs to be upgraded, the corresponding upgrade version number is found by entering the old version number of the program in use on the platform. However, the version number obtained based on the existing naming rules cannot reflect the application layer version date. In other words, there is a lack of an inherent logical relationship between the application layer version date and the version number. As a result, the upgrade version number found may be incorrect, making it difficult to efficiently find the correct upgrade version number, which in turn reduces the efficiency and accuracy of program updates. Summary of the Invention

[0013] The purpose of the present invention is to provide a method for determining the upgrade version number of a vehicle-mounted controller program, so as to solve the problem of low accuracy of the found upgrade version number.

[0014] To achieve the above object, the solution of the present invention includes:

[0015] A method for determining an upgrade version number of a vehicle-mounted controller program according to the present invention comprises the following steps:

[0016] Determine the upgrade version number according to the relationship between the upgrade version number parameter and the old version number parameter of the vehicle controller program and the old version number parameter;

[0017] The relationships include the following:

[0018] A1A2=a1a2+t1t2

[0019] B1B2=b1b2+t3t4

[0020] C1C2=c1C2+t5t6

[0021] E1E2=e1e2+O

[0022] O takes any 8 values ​​in the same base range as the old version number parameter, representing the 8 combinations of overflow states of a1a2+t1t2, b1b2+t3t4, and c1c2+t5t6, and when any of their overflow states and the overflow state of e1e2+O is an overflow, the corresponding highest carry is removed;

[0023] In the formula, A1A2 is the major version number of the upgraded version, B1B2 is the minor version number of the upgraded version, C1C2 is the application layer program code name of the upgraded version, E1E2 is the underlying version number of the upgraded version, a1a2 is the major version number of the old version, b1b2 is the minor version number of the old version, c1c2 is the application layer program code name of the old version, e1e2 is the underlying version number of the old version, and t1t2, t3t4, and t5t6 are the year, month, and day of the application layer finalization date of the old version, respectively.

[0024] Furthermore, the relationship between the modification information number in the relationship is as follows:

[0025] D1D2=4*d1d2+e0

[0026] Where D1D2 is the modification information number of the upgraded version, d1d2 is the modification information number of the old version, and e0 is the underlying version number of the old version.

[0027] Furthermore, the expression of O is:

[0028]

[0029] In the formula, y1, y2, y3, y4, y5, y6, y7 and y8 are 8 values ​​of O, O1=1, O2=1 and O3=1 respectively indicate that the overflow status of a1a2+t1t2, b1b2+t3t4 and c1c2+t5t6 is overflow, and O1=0, O2=0 and O3=0 respectively indicate that the overflow status of a1a2+t1t2, b1b2+t3t4 and c1c2+t5t6 is not overflow.

[0030] Furthermore, the method further comprises the following steps:

[0031] Determine the old version number based on the relationship and upgrade version number parameters.

[0032] A system for determining an upgrade version number of a vehicle-mounted controller program of the present invention includes a processor configured to execute a computer program to implement the following steps:

[0033] Determine the upgrade version number according to the relationship between the upgrade version number parameter and the old version number parameter of the vehicle controller program and the old version number parameter;

[0034] The relationships include the following:

[0035] A1A2=a1a2+t1t2

[0036] B1B2=b1b2+t3t4

[0037] C1C2=c1C2+t5t6

[0038] E1E2=e1e2+O

[0039] O takes any 8 values ​​in the same base range as the old version number parameter, representing the 8 combinations of overflow states of a1a2+t1t2, b1b2+t3t4, and c1c2+t5t6, and when any of their overflow states and the overflow state of e1e2+O is an overflow, the corresponding highest carry is removed;

[0040] In the formula, A1A2 is the major version number of the upgraded version, B1B2 is the minor version number of the upgraded version, C1C2 is the application layer program code name of the upgraded version, E1E2 is the underlying version number of the upgraded version, a1a2 is the major version number of the old version, b1b2 is the minor version number of the old version, c1c2 is the application layer program code name of the old version, e1e2 is the underlying version number of the old version, and t1t2, t3t4, and t5t6 are the year, month, and day of the application layer finalization date of the old version, respectively.

[0041] Furthermore, the relationship between the modification information number in the relationship is as follows:

[0042] D1D2=4*d1d2+e0

[0043] Where D1D2 is the modification information number of the upgraded version, d1d2 is the modification information number of the old version, and e0 is the underlying version number of the old version.

[0044] Furthermore, the expression of O is:

[0045]

[0046] In the formula, y1, y2, y3, y4, y5, y6, y7 and y8 are 8 values ​​of O, O1=1, O2=1 and O3=1 respectively indicate that the overflow status of a1a2+t1t2, b1b2+t3t4 and c1c2+t5t6 is overflow, and O1=0, O2=0 and O3=0 respectively indicate that the overflow status of a1a2+t1t2, b1b2+t3t4 and c1c2+t5t6 is not overflow.

[0047] Furthermore, the method further comprises the following steps:

[0048] Determine the old version number based on the relationship and upgrade version number parameters.

[0049] Beneficial effects of the present invention:

[0050] The present invention is a pioneering invention, which provides a method for determining the upgraded version number of a vehicle-mounted controller program. The method introduces the relationship between the upgraded version number parameters and the old version number parameters of the vehicle-mounted controller program. The upgraded version number determined by the relationship can reflect the parameters involved in the change under the program change (application layer program code c1c2, bottom layer version number e0e1e2 and application layer finalization date number t1t2t3t4t5t6). That is, the present invention determines a unique upgraded version number through a unique, one-to-one correspondence and the relationship between the upgraded version number parameters and the old version number parameters of the old version that can reflect the changed parameters and the known old version number parameters. The relationship makes the underlying logic behind the upgraded version number unique and clear. A unique and accurate upgraded version number can be obtained through the known relationship and the known old version number parameters, and a unique and accurate old version number can also be obtained through the known relationship and the known upgraded version number parameters. Based on this scheme, an accurate upgraded version number can be obtained efficiently to improve the efficiency and accuracy of program updates. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 This is a flowchart for determining the upgrade version number. DETAILED DESCRIPTION

[0052] In order to solve the problems in the background technology, the present invention uses a version number naming rule that reflects the relationship between the version number parameters of the upgraded version and the version number parameters of the old version, so that the obtained upgraded version number can reflect all the old version number parameters involved in the changes, that is, the obtained upgraded version number can reflect the application layer program code c1c2, the underlying version number e0e1e2 and the application layer version date number t1t2t3t4t5t6 of the old version involved in the changes, effectively resolving the conflict between the existing program naming method and the existing program management method, and efficiently obtaining a unique and accurate upgraded version number through the known relationship and the known old version number parameters, so as to improve the efficiency and accuracy of program updates.

[0053] In order to make the objectives, technical solutions and advantages of the present invention more clear, the present invention is further described in detail below with reference to the accompanying drawings and embodiments.

[0054] An embodiment of a system for determining an upgrade version number of a vehicle controller program:

[0055] A system for determining an upgraded version number of an on-vehicle controller program includes a processor for executing a computer program to implement the steps of a method for determining an upgraded version number of an on-vehicle controller program.

[0056] A method for determining an upgrade version number of a vehicle controller program comprises the following steps:

[0057] like Figure 1 As shown, a unique and accurate upgrade version number is determined based on the relationship between the upgrade version number parameters and the old version number parameters of the vehicle controller program (referred to as relationship) and the old version number parameters. This determination method is efficient and accurate and can improve the efficiency and accuracy of program updates.

[0058] The relationship between the upgraded version number parameter and the old version number parameter of the vehicle controller program is as follows:

[0059] A1A2=a1a2+t1t2

[0060] B1B2=b1b2+t3t4

[0061] C1C2=c1C2+t5t6

[0062] E1E2=e1e2+O

[0063] In the formula, A1A2 is the major version number of the upgraded version, B1B2 is the minor version number of the upgraded version, C1C2 is the application layer program code name of the upgraded version, E1E2 is the underlying version number of the upgraded version, a1a2 is the major version number of the old version, b1b2 is the minor version number of the old version, c1c2 is the application layer program code name of the old version, e1e2 is the underlying version number of the old version, and t1t2, t3t4, and t5t6 are the year, month, and day of the application layer finalization date of the old version, respectively.

[0064] The eight possible values ​​of O represent the eight possible overflow combinations of a1a2+t1t2, b1b2+t3t4, and c1c2+t5t6, respectively. These eight values ​​are arbitrarily selected within the same base range as the old version number parameter. The overflow state of a1a2+t1t2 is to discard the highest carry bit upon overflow, the overflow state of b1b2+t3t4 is to discard the highest carry bit upon overflow, the overflow state of c1c2+t5t6 is to discard the highest carry bit upon overflow, and the overflow state of e1e2+O is to discard the highest carry bit upon overflow. The old version number parameter can be in any base, generally hexadecimal. Based on the calculation rules, the above parameters operate in the same base. Overflow refers to exceeding the range of the corresponding base.

[0065] Among them, the relationship between the upgraded version number parameter and the old version number parameter of the vehicle controller program adopts the existing relationship of the modified information number, which is as follows:

[0066] D1D2=4*d1d2+e0

[0067] Where D1D2 is the modification information number of the upgraded version, d1d2 is the modification information number of the old version, and e0 is the underlying version number of the old version.

[0068] When the old version number is lost, the old version number can be determined based on the relationship between the known upgraded version number parameters and the old version number parameters of the vehicle controller program and the known upgraded version number parameters. The old version number can be determined efficiently and accurately.

[0069] Specifically, the expression of O is:

[0070]

[0071] In the formula, y1, y2, y3, y4, y5, y6, y7 and y8 are 8 values ​​of O, O1=1 indicates that the overflow state of a1a2+t1t2 is overflow, O2=1 indicates that the overflow state of b1b2+t3t4 is overflow, O3=1 indicates that the overflow state of c1c2+t5t6 is overflow, O1=0 indicates that the overflow state of a1a2+t1t2 is not overflow, O2=0 indicates that the overflow state of b1b2+t3t4 is not overflow, and O3=0 indicates that the overflow state of c1c2+t5t6 is not overflow.

[0072] As another embodiment, the expression of O is:

[0073]

[0074] In the formula, y1, y2, y3, y4, y5, y6, y7 and y8 are 8 values ​​of O, O1=1 indicates that the overflow state of a1a2+t1t2 is overflow, O2=1 indicates that the overflow state of b1b2+t3t4 is overflow, O3=1 indicates that the overflow state of c1c2+t5t6 is overflow, O1=0 indicates that the overflow state of a1a2+t1t2 is not overflow, O2=0 indicates that the overflow state of b1b2+t3t4 is not overflow, and O3=0 indicates that the overflow state of c1c2+t5t6 is not overflow.

[0075] Specifically, y1=0, y2=1, y3=2, y4=3, y5=4, y6=5, y7=6, and y8=7.

[0076] As another embodiment, y1=5, y2=8, y3=6, y4=1, y5=9, y6=2, y7=4, and y8=3.

[0077] The following is a more detailed introduction to the relationship between the upgraded version number parameters and the old version number parameters of the vehicle controller program:

[0078] The relationship between the upgraded version number parameters and the old version number parameters of the vehicle controller program is as follows:

[0079] (1) The calculation formula for A1A2 is:

[0080] A1A2=a1a2+t1t2

[0081] Where A1A2 is the major version number of the upgraded version, a1a2 is the major version number of the old version, and t1t2 is the year of the application layer finalization date of the old version.

[0082] O1 represents the overflow state of a1a2+t1t2. From the maximum value range of t1t2, we can know that if a1a2+t1t2 overflows, O1=1; if a1a2+t1t2 does not overflow, O1=0.

[0083] (2) The calculation formula for B1B2 is:

[0084] B1B2=b1b2+t3t4

[0085] Where B1B2 is the minor version number of the upgraded version, b1b2 is the minor version number of the old version, and t3t4 is the month of the application layer finalization date of the old version.

[0086] O2 represents the overflow state of b1b2+t3t4. From the maximum value range of t3t4, we can know that if b1b2+t3t4 overflows, O2=1; if b1b2+t3t4 does not overflow, O2=0.

[0087] (3) The calculation formula of C1C2 is:

[0088] C1C2=c1C2+t5t6

[0089] In the formula, C1C2 is the application layer program code of the upgraded version, c1c2 is the application layer program code of the old version, and t5t6 are the dates of the application layer version number of the old version.

[0090] O3 represents the overflow state of c1c2+t5t6. From the maximum value range of t5t6, we can know that if c1c2+t5t6 overflows, O3=1; if c1c2+t5t6 does not overflow, O3=0.

[0091] (4) The calculation formula of D1D2 is the same as the existing one, and the calculation formula of D1D2 is:

[0092] D1D2=4*d1d2+e0

[0093] Where D1D2 is the modification information number of the upgraded version, d1d2 is the modification information number of the old version, and e0 is the underlying version number of the old version.

[0094] (5) The calculation formula of E1E2 is:

[0095] E1E2=e1e2+O

[0096] Where E1E2 is the underlying version number of the upgraded version, e1e2 is the underlying version number of the old version, and the eight values ​​of O represent the eight combinations of overflow states of a1a2+t1t2, b1b2+t3t4, and c1c2+t5t6, respectively. The eight values ​​of O are eight numbers arbitrarily selected within the same base range as the old version number parameters.

[0097] Taking hexadecimal as an example, the relationship between O and O1, O2, and O3 can be seen in Table 1 below:

[0098] Table 1

[0099]

[0100] Among them, if a1a2+t1t2 overflows, record O1=1, otherwise record O1=0; if b1b2+t3t4 overflows, record O2=1, otherwise record O2=0; if c1c2+t5t6 overflows, record O3=1, otherwise record O3=0.

[0101] Among them, the overflow state of a1a2+t1t2 is to discard the highest carry when overflowing, the overflow state of b1b2+t3t4 is to discard the highest carry when overflowing, the overflow state of c1c2+t5t6 is to discard the highest carry when overflowing, and the overflow state of e1e2+O is to discard the highest carry when overflowing.

[0102] Specifically, O(O1, O2, O3), a1a2, b1b2 and d1d2 can be calculated based on the known c1c2, t1t2t3t4t5t6, e0e1e2 and the upgraded version number A1A2.B1B2.C1C2D1D2E1E2 of the vehicle controller program.

[0103] If e1e2+O overflows, then O=Z+E1E2-e1e2; otherwise, e1e2+O does not overflow, and O=E1E2-e1e2.

[0104] If a1a2+t1t2 overflows, O1=1, then a1a2=Z+A1A2-t1t2, otherwise a1a2+t1t2 does not overflow, O1=0, a1a2=A1A2-t1t2;

[0105] If b1b2+t3t4 overflows, O2=1, then b1b2=Z+B1B2-t3t4, otherwise b1b2+t3t4 does not overflow, O2=0, b1b2=B1B2-t3t4;

[0106] If c1c2+t5t6 overflows, O3=1, then c1c2=Z+C1C2-t5t6; otherwise, c1c2+t5t6 does not overflow, O3=0, and c1c2=C1C2-t5t6.

[0107] Wherein, Z is the maximum value of the same base as the old version number parameter. For example, if the old version number parameter is in hexadecimal, Z=FF.

[0108] The overflow status of e1e2+O can be determined based on the difference between E1E2 and e1e2. If E1E2-e1e2 is not equal to any of y1, y2, y3, y4, y5, y6, y7, and y8, then e1e2+O overflows. Otherwise, e1e2+O does not overflow.

[0109] If E1E2 and e1e2 are known, determine whether A1A2, B1B2 and C1C2 overflow based on the unique corresponding O1, O2, O3 obtained from the difference between E1E2 and e1e2.

[0110] If y1=0, y2=1, y3=2, y4=3, y5=4, y6=5, y7=6 and y8=7 are set, since the value range of O is 0-7, e1e2+O may overflow. If E1E2 and e1e2 are known quantities, the difference between E1E2 and e1e2 can be used to determine whether e1e2+O overflows. If E1E2-e1e2 is between 0 and 7, then e1e2+O does not overflow. At this time, the value of O can be calculated according to O=E1E2-e1e2. The values ​​of O1, O2, and O can be found in Table 1. 3, and then determine whether a1a2+t1t2, b1b2+t3t4, c1c2+t5t6 overflow (that is, determine whether A1A2, B1B2, C1C2 overflow); if the value of O calculated is not between 0 and 7, then e1e2+O overflows, and O=FF+E1E2-e1e2, and then remove the highest carry of the overflow, and query the values ​​of O1, O2, O3 through Table 1 according to the value obtained by O=E1E2-e1e2, and then determine whether A1A2, B1B2, C1C2 overflow.

[0111] According to the relationship between the upgraded version number parameters and the old version number parameters of the vehicle controller program, when the controller program needs to be changed, the application layer program code c1c2, the underlying version number e0e1e2 and the application layer finalization date t1t2t3t4t5t6 are first determined according to the existing management method, and then a1a2, b1b2 and d1d2 are determined according to the existing management method, and finally the program remote upgrade version number A1A2.B1B2.C1C2D1D2E1E2 is determined.

[0112] If the controller front-end program is lost, the upgraded program version number A1A2.B1B2.C1C2D1D2E1E2 can be found through the monitoring platform upgrade record, and then the application layer program version number c1c2, application layer version date number t1t2t3t4t5t6, and bottom layer version number e0e1e2 can be checked through the lathe number. Then, based on the calculated value of O(O1, O2, O3), the major version number a1a2, minor version number b1b2 and modification information number d1d2 can be reversely calculated to determine the old version number a1a2.b1b2.c1c2d1d2e0e1e2.

[0113] The method for determining the vehicle-mounted controller program upgrade version number of the present invention reflects all program change-related parameters through the upgrade version number, thereby resolving the conflict between the existing program naming method and the existing program management method. The determination method can be applied to new energy mining vehicles to ensure that the vehicle-mounted controller OTA upgrade version number can include all program change-related parameters, so that the OTA upgrade of new energy mining vehicles can be smoothly implemented, which can meet the diverse needs of customers, while improving the environmental adaptability and product competitiveness of new energy mining equipment and reducing the operating costs of the enterprise.

[0114] An embodiment of a method for determining an upgrade version number of a vehicle controller program:

[0115] A method for determining an upgrade version number of a vehicle-mounted controller program has been described in detail in an embodiment of a system for determining an upgrade version number of a vehicle-mounted controller program, and will not be repeated here.

Claims

1. A method for determining the upgrade version number of a vehicle controller program, characterized in that: The steps include: Determine the upgrade version number according to the relationship between the upgrade version number parameter and the old version number parameter of the vehicle controller program and the old version number parameter; The relationships include the following: A1A2=a1a2+t1t2 B1B2=b1b2+t3t4 C1C2=c1C2+t5t6 E1E2=e1e2+O The eight values ​​of O in the same base range as the old version number parameter represent the eight combinations of overflow states of a1a2+t1t2, b1b2+t3t4, and c1c2+t5t6, and when any of the overflow states and the overflow state of e1e2+O is an overflow, the corresponding highest carry is removed; In the formula, A1A2 is the major version number of the upgraded version, B1B2 is the minor version number of the upgraded version, C1C2 is the application layer program code name of the upgraded version, E1E2 is the underlying version number of the upgraded version, a1a2 is the major version number of the old version, b1b2 is the minor version number of the old version, c1c2 is the application layer program code name of the old version, e1e2 is the underlying version number of the old version, and t1t2, t3t4, and t5t6 are the year, month, and day of the application layer finalization date of the old version, respectively.

2. The method for determining the vehicle controller program upgrade version number according to claim 1, characterized in that: The relationship between the modification information numbers in the above relationship is as follows: D1D2=4*d1d2+e0 Where D1D2 is the modification information number of the upgraded version, d1d2 is the modification information number of the old version, and e0 is the underlying version number of the old version.

3. The method for determining the vehicle controller program upgrade version number according to claim 1, characterized in that: The expression of O is: In the formula, y1, y2, y3, y4, y5, y6, y7 and y8 are 8 values ​​of O, O1=1, O2=1 and O3=1 respectively indicate that the overflow status of a1a2+t1t2, b1b2+t3t4 and c1c2+t5t6 is overflow, and O1=0, O2=0 and O3=0 respectively indicate that the overflow status of a1a2+t1t2, b1b2+t3t4 and c1c2+t5t6 is not overflow.

4. The method for determining the vehicle controller program upgrade version number according to any one of claims 1 to 3, characterized in that: The following steps are also included: The old version number is determined according to the relationship and the upgrade version number parameter.

Images