Method, device, computer program and computer program product for encoding a vehicle controller and verifying a vehicle controller
By encoding vehicle parameters into the controller and additionally encoding these parameters in another controller, cross-controller verification is achieved, which solves the problem of difficulty in simply and effectively protecting the vehicle controller in the existing technology and meets the ISO standard The safety level of 26262 is ASIL B.
Patent Information
- Application Number
- CN201980025475.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-06-29
- Filing Date
- 2019-04-15
- Publication Date
- 2025-01-21
- Estimated Expiration
- 2039-04-15
AI Technical Summary
The prior art is difficult to protect vehicle controllers simply and effectively, especially when meeting the requirements of the safety level ASIL B of ISO Standard 26262.
The controller is simply protected by encoding the vehicle parameters as encoded parameters in the controller and additionally encoding these parameters in another controller, thereby enabling cross-controller verification.
It realizes simple and effective protection of vehicle controllers, meets the safety level ASIL B of ISO standard 26262:2012 or 26262:2011, and ensures the safety and reliability of the controller through cross-controller verification.
Smart Images

Figure CN111971659B_ABST
Abstract
Description
Technical Field
[0001] The invention relates to a method for encoding a vehicle control unit. The invention further relates to a device for encoding a vehicle control unit. The invention further relates to a computer program for encoding a vehicle control unit. The invention further relates to a computer program product for encoding a vehicle control unit.
[0002] The invention further relates to a method for calibrating a vehicle control unit. The invention further relates to a device for calibrating a vehicle control unit. The invention further relates to a computer program for calibrating a vehicle control unit. The invention further relates to a computer program product for calibrating a vehicle control unit. Background Art
[0003] ISO Standard 26262 is an ISO standard for safety-related electrical / electronic systems in motor vehicles. A classification in the form of safety levels ASIL A to ASIL D is used here. Summary of the invention
[0004] The invention is based on the object of protecting a control unit of a vehicle in a simple manner.
[0005] The invention is characterized by a method for encoding a vehicle control unit, wherein a certain number of vehicle parameters are encoded as encoding parameters in a control unit, wherein the certain number of vehicle parameters are additionally encoded in another control unit of the vehicle. The invention is also characterized by a device, wherein the device is designed to implement the method for encoding a vehicle control unit.
[0006] The controller is coded, in particular, during vehicle manufacturing and / or repair. In this process, coding parameters are written into a coding module of the controller, such as a so-called BAC module. Such coding parameters can then be read again, for example, with the aid of a coding wrapper. The coding parameters typically include parameters related to the respective controller, such as the model, etc.
[0007] At this time, by using the vehicle parameters as encoding parameters, which are also encoded in another controller, cross-controller / controller-independent verification (eg as described in the second aspect of the invention). In this way, the controller can be protected very simply, in particular to at least meet the safety level ASIL B of ISO standard 26262, in particular ISO standard 26262:2012 or 26262:2011.
[0008] Vehicle parameters include, for example, vehicle height, vehicle width, hood length, country code and / or steering wheel side.
[0009] The further control unit is, for example, a control unit which is connected via a vehicle bus to a plurality of control units, in particular to all or at least all safety-related control units of the vehicle.
[0010] According to an optional refinement, a corresponding checksum of a cyclic redundancy check is additionally encoded as an encoding parameter in the one control unit for one or more vehicle parameters and / or a partial quantity of vehicle parameters of the quantity of vehicle parameters.
[0011] The checksum of the cyclic redundancy check may also be referred to as a CRC checksum (Cyclic Redundancy Check in English). The checksum may in particular correspond to individual vehicle parameters and / or to a plurality of vehicle parameters, ie a group consisting of a plurality of vehicle parameters.
[0012] Since the coding of the control unit may be very old depending on the age of the vehicle, small errors, for example at the bit level, may occur in the coding modules of the control unit over time. The corresponding vehicle parameters can be checked for such errors in a simple manner by means of a checksum.
[0013] According to another optional refinement, a group of function-specific parameters is additionally encoded as encoding parameters in the one control unit, wherein the group is a subset of the function-specific parameters encoded in the other control unit of the vehicle.
[0014] Such function-specific parameters include, for example, one or more different alarm times and / or triggering times of different controller-specific functions.
[0015] By setting groups, encoding parameters adapted to each controller can be stored in a very simple manner.
[0016] According to another optional refinement, a checksum of a cyclic redundancy check corresponding to the group and / or an identification number corresponding to the group and / or a checksum of a cyclic redundancy check corresponding to the identification number are additionally encoded in the one control unit.
[0017] By means of a checksum corresponding to the group, for example, bit errors as explained above can be checked in a simple manner. By means of an identification number corresponding to the group, it can be checked in a very simple manner whether the function-specific parameters of the correct group are encoded in the controller. By means of a checksum corresponding to the identification number, for example, bit errors as explained above can be checked in a simple manner.
[0018] According to a second aspect, the invention is characterized by a method for calibrating a vehicle control unit. The invention is further characterized by a device which is designed to carry out the method for calibrating a vehicle control unit.
[0019] In the method, a first quantity of vehicle parameters is read from a controller, the first quantity of vehicle parameters being already encoded as encoded parameters in the one controller. A second quantity of vehicle parameters is provided, the second quantity of vehicle parameters being encoded in another controller of the vehicle. The first quantity of vehicle parameters is compared with the second quantity of vehicle parameters.
[0020] In this way, a safety check can be carried out in a simple manner. This is done, for example, when the vehicle is started, by the other controller sending a message formed for this purpose with the second quantity of vehicle parameters to the corresponding controller. This allows a simple check to be carried out with the other controller, regardless of the type of controller to be checked.
[0021] Reading from the controller in this context means in particular that the controller itself reads the corresponding data from its own memory. Therefore, no third unit is required for the method, but only the one controller and the other controller, which are connected, for example, via a vehicle bus.
[0022] If the check, for example, reveals differences in the corresponding vehicle parameters, suitable measures can be taken depending on the safety relevance of the control unit, such as not starting the vehicle, indicating that a vehicle search is required, deactivating the control unit and / or activating an emergency mode.
[0023] If the check shows that there are no differences in the corresponding vehicle parameters, the control unit can, for example, begin its normal operation.
[0024] According to an optional design scheme, in addition to one or more vehicle parameters and / or a partial amount of vehicle parameters among the read vehicle parameters, a corresponding checksum of a cyclic redundancy check is read from the one controller and checked, which corresponding checksum has been encoded as a coding parameter into the one controller.
[0025] As a result, for example, bit errors as described above can be checked in a simple manner.
[0026] According to an optional refinement, a plausibility check is additionally carried out for one or more of the read-out variable vehicle parameters.
[0027] The plausibility check includes, for example, a limit value comparison, for example with corresponding upper and / or lower limit values, since vehicle parameters such as the engine hood length are plausible only within a certain range.
[0028] This provides a further possibility for checking individual vehicle parameters.
[0029] According to another optional design scheme, a group of function-specific parameters that have been encoded as encoding parameters in the one controller are additionally read and verified, and / or a checksum of a cyclic redundancy check corresponding to the group and / or an identification number corresponding to the group and / or a checksum of a cyclic redundancy check corresponding to the identification number are read and verified.
[0030] By providing the groups, the coding parameters adapted to each controller can be checked in a very simple manner. By means of the checksum corresponding to the groups, for example, bit errors as explained above can be checked in a simple manner. By means of the identification number corresponding to the groups, it can be checked in a very simple manner whether the function-specific parameters of the correct group are encoded in the controller. By means of the checksum corresponding to the identification number, for example, bit errors as explained above can be checked in a simple manner.
[0031] According to a further aspect, the invention is characterized by a computer program, wherein the computer program is designed to carry out the method for encoding a vehicle control unit or the method for verifying a vehicle control unit.
[0032] According to a further aspect, the invention is characterized by a computer program product comprising an executable program code, wherein the program code, when executed by a data processing device, implements the method for encoding a vehicle control unit or the method for verifying a vehicle control unit.
[0033] The computer program product comprises, in particular, a medium which can be read by a data processing device and on which the program code is stored. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] Next, an embodiment of the present invention will be further described with the aid of a schematic diagram.
[0035] Figure 1 A flow chart showing a procedure for encoding a vehicle controller, and
[0036] Figure 2 A flow chart of a procedure for calibrating a vehicle controller is shown. DETAILED DESCRIPTION
[0037] Figure 1 A flow chart of a program for encoding a vehicle control unit is shown.
[0038] The program can be executed, for example, by a device. For this purpose, the device has, in particular, a computing unit, a program and data memory, and, for example, one or more communication interfaces. The program and data memory and / or the computing unit and / or the communication interface can be formed in one structural unit and / or can be distributed over a plurality of structural units.
[0039] The device may also be referred to as a device for encoding a vehicle controller.
[0040] For this purpose, in particular a program is stored in the program and data memory of the device.
[0041] The program begins in step S1 , in which variables can optionally be initialized.
[0042] In step S3 , a certain number of vehicle parameters are encoded as encoding parameters in a control unit, wherein the certain number of vehicle parameters are additionally encoded in another control unit of the vehicle.
[0043] Optionally, a corresponding checksum of a cyclic redundancy check is additionally encoded as an encoding parameter in the one control unit for one or more vehicle parameters and / or a partial quantity of vehicle parameters of the quantity of vehicle parameters.
[0044] Optionally, a set of function-specific parameters is additionally encoded as encoding parameters in the one control unit, wherein the set is a subset of the function-specific parameters encoded in the other control unit of the vehicle.
[0045] Optionally, a checksum of a cyclic redundancy check corresponding to the group and / or an identification number corresponding to the group and / or a checksum of a cyclic redundancy check corresponding to the identification number are additionally encoded in the one controller.
[0046] In step S5 the program ends and can optionally be started again in step S1 .
[0047] Figure 2 A flow chart of a procedure for calibrating a vehicle controller is shown.
[0048] The program can be executed, for example, by a device. For this purpose, the device has, in particular, a computing unit, a program and data memory and, for example, one or more communication interfaces. The program and data memory and / or the computing unit and / or the communication interface can be formed in one structural unit and / or can be distributed over a plurality of structural units.
[0049] The device can also be referred to as a device for calibrating a vehicle control unit. The device can be implemented, for example, in a control unit to be calibrated.
[0050] For this purpose, in particular a program is stored in the program and data memory of the device.
[0051] The program begins in step S11 , in which variables can optionally be initialized. The program begins, for example, when the vehicle is started, by another control unit sending a message formed for this purpose to the control unit to be verified.
[0052] In step S13 , a first quantity of vehicle parameters is read from the controller, where the first quantity of vehicle parameters has been encoded into the controller as encoding parameters.
[0053] In optional step S15 , a corresponding checksum of a cyclic redundancy check is additionally read from the control unit for one or more of the read vehicle parameters and / or a partial vehicle parameter, which has been encoded in the control unit as an encoding parameter.
[0054] In an optional step S17 , a checksum corresponding to one or more of the vehicle parameters of the read quantity and / or a partial quantity of vehicle parameters is checked.
[0055] If an error is detected during the check, the program continues in step S31 .
[0056] If no errors were detected during the check, the program continues in optional step S21 .
[0057] In step S21 , a plausibility check is carried out on one or more of the read-out variable vehicle parameters.
[0058] If an error is detected in the plausibility check, the program continues in step S31 .
[0059] If no error was detected in the plausibility check, the program continues in optional step S23 .
[0060] In step S23, a set of function-specific parameters that have been encoded as encoding parameters in the controller, a checksum of a cyclic redundancy check corresponding to the set, and an identification number corresponding to the set are read.
[0061] In optional step S25, a checksum corresponding to the group is checked.
[0062] If an error is detected during the check, the program continues in step S31 .
[0063] If no errors were detected during the check, the program continues in optional step S27 .
[0064] In optional step S27, the identification number corresponding to the group is checked.
[0065] If an error is detected during the check, the program continues in step S31 .
[0066] If no errors were detected during the check, the program continues in optional step S29 .
[0067] In step S29, the first amount of vehicle parameters is compared with a second amount of vehicle parameters which have been provided and encoded in another controller of the vehicle, for example vehicle type, country code and steering wheel side.
[0068] If an error is detected during the comparison, the program continues in step S31 .
[0069] If no errors were detected during the check, the program continues in optional step S30 .
[0070] All checks have been successfully performed in step S30. Therefore, the controller can send a confirmation message and start its normal operation, for example. The program then ends in step S33.
[0071] In step S31, the error is confirmed, so appropriate measures can be taken according to the safety relevance of the controller / error, such as not starting the vehicle, displaying that a workshop should be found, deactivating the function of the controller and / or activating emergency operation. The program then ends in step S33.
Claims
1. A method for encoding a controller of a vehicle, wherein: A certain amount of vehicle parameters are encoded as encoding parameters in a controller, wherein the certain amount of vehicle parameters are additionally encoded in another controller of the vehicle, wherein the certain amount of vehicle parameters in the other controller are sent to the one controller when the vehicle is started, and the certain amount of vehicle parameters in the one controller are compared with the certain amount of vehicle parameters in the other controller, so that a safety check is performed on the one controller with the aid of the other controller, wherein the vehicle is not started if an error is identified during the safety check.
2. The method according to claim 1, wherein: Additionally, a corresponding checksum of a cyclic redundancy check is encoded as an encoding parameter in the one control unit for one or more vehicle parameters of the quantity of vehicle parameters and / or a partial quantity of vehicle parameters.
3. The method according to claim 1 or 2, wherein: Additionally, a set of function-specific parameters is encoded as encoding parameters in the one control unit, wherein the set is a subset of the function-specific parameters encoded in the other control unit of the vehicle.
4. The method according to claim 3, wherein: In addition, a checksum of a cyclic redundancy check corresponding to the group and / or an identification number corresponding to the group and / or a checksum of a cyclic redundancy check corresponding to the identification number is encoded in the one control unit.
5. A method for verifying a controller to be verified of a vehicle, wherein - reading a first quantity of vehicle parameters from the controller to be verified, the first quantity of vehicle parameters having been encoded as encoding parameters in the controller to be verified, - providing a second variable vehicle parameter in that, when the vehicle is started, a further control unit sends a message formed for this purpose to the control unit to be verified, which contains the second variable vehicle parameter which is encoded in the further control unit of the vehicle, - comparing a first variable vehicle parameter with a second variable vehicle parameter, thereby carrying out a safety check of the control unit to be checked with the aid of the other control unit, - If an error is detected during the safety check described above, the vehicle is not started.
6. The method according to claim 5, wherein - Additionally, for one or more vehicle parameters and / or a partial quantity of vehicle parameters of the read quantity, a corresponding checksum of a cyclic redundancy check is read from the control unit to be verified and verified, which corresponding checksum has been encoded as an encoding parameter in the control unit to be verified.
7. The method according to claim 5 or 6, wherein: In addition, a plausibility check is carried out for one or more of the read-out quantitative vehicle parameters.
8. The method according to claim 5 or 6, wherein: Additionally, a set of function-specific parameters that have been encoded as encoding parameters in the controller to be verified are read and verified, and / or a checksum of a cyclic redundancy check corresponding to the set and / or an identification number corresponding to the set and / or a checksum of a cyclic redundancy check corresponding to the identification number are read and verified.
9. A device for encoding or verifying a controller of a vehicle, wherein: The device is designed to carry out a method for encoding a control unit of a vehicle according to any one of claims 1 to 4 or a method for calibrating a control unit of a vehicle to be calibrated according to any one of claims 5 to 8.
10. A medium readable by a data processing device, on which an executable program code is stored, wherein: When executed by a data processing device, the program code implements a method for encoding a control unit of a vehicle according to any one of claims 1 to 4 or a method for verifying a control unit of a vehicle to be verified according to any one of claims 5 to 8.
Citation Information
Patent Citations
Method for coding at least one parameter in a control unit of a motor vehicle
DE102014015445A1
Vehicle computer system with data backup
US20160176411A1