Program update control system and program update control procedure
The system updates vehicle control device security programs only when the vehicle is in a safe state, addressing security risks during updates by ensuring security functions are active, thus preventing theft and incorrect operations.
Patent Information
- Application Number
- DE102017220367
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2016-11-16
- Filing Date
- 2017-11-15
- Publication Date
- 2024-12-05
- Estimated Expiration
- 2037-11-15
AI Technical Summary
Existing program update methods for vehicle control devices expose vehicles to security risks during updates, as security measures are inactive when the engine is stopped or running, making them vulnerable to theft and incorrect operations.
A system and method for updating security programs in vehicle control devices that involve a first control device collecting and transmitting data to determine the vehicle's operating condition, ensuring updates only occur when the vehicle is in a safe state, such as being stopped, thereby activating security functions during updates.
Ensures that vehicle control devices can be updated with security programs at appropriate times, preventing abnormal operations and protecting against theft and incorrect operations during the update process.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
BACKGROUND OF THE INVENTION 1. Field of the invention
[0001] The invention relates to a program update control system and a program update control method for updating a program that implements a safety function to prevent incorrect operations from being implemented on a control device installed in a vehicle. 2. Description of related prior art
[0002] A vehicle contains a number of control devices known as electronic control units (ECUs), and the ECUs are connected to each other via a wireless or wired vehicle network.
[0003] The ECUs each execute programs according to their assigned functions. These programs can be rewritten to updated versions supplied to the vehicle via cable from a service station or similar device, or to updated versions distributed from a service center that communicates wirelessly with the vehicle.
[0004] In a conventional technique, when a program rewrite request is made, a master control unit stops the vehicle and then transmits a program update, sent from a service terminal connected to it via a network, to a subject control unit (see, for example, JP 2007-230 317 A).
[0005] DE 10 2014 008 479 A1 relates to a motor vehicle control unit with a power-saving mode for the parking phase. In this case, the operating software is updated during the parking phase via the peripherals, i.e., via a processor core, RAM memory modules, and a memory controller. DE 10 2014 219 322 A1 relates to an update of a vehicle control unit via Car2X. In this case, at least part of a control device is updated based on a received update message. JP 2014 - 168 219 A relates to an access restriction device, an in-vehicle communication system, and a communication restriction procedure. In this case, a security controller can add or update a program by incorporating the transmission and reception processing of information. JP 2014 - 106 875 A relates to an in-vehicle program update device.In this context, a gateway ECU has an update condition table that individually displays a vehicle load or charge state to allow an update of an ECU program from any of a multitude of ECUs that form an in-vehicle network system. JP 2010-243339A relates to a program management device capable of updating a program of a controller that manages the operation of equipment located in a vehicle in a user-preferred environment. US 6222-207B1 relates to a method and mechanism for synchronously updating inter-operational software. US 5828977A relates to a program / data overwrite control after a machine stop. SUMMARY OF THE INVENTION
[0006] However, when the state of the art described in this document is applied, the following problem arises.
[0007] In any ECU, a program designed to ensure security against incorrect operation can be easily updated when the vehicle's engine is stopped or running while the vehicle is parked. In this case, a necessary security measure at that time (such as an anti-theft device) will not function, and as a result, the vehicle is exposed to a security risk such as theft while the program is being updated.
[0008] This invention is designed to solve the problem described above, and one of its objectives is to provide a program update control system and a program update control method with which a program for implementing a safety function against incorrect operation of a vehicle network system can be updated at an appropriate time, according to a characteristic of an ECU.
[0009] The above problem is solved according to the invention by the subject matter of the independent claims. The dependent claims describe further preferred embodiments, and this document describes how the invention can be carried out.
[0010] A program update control system according to this invention is applied to a vehicle in which a first control device and one or more second control devices are installed, which are communicatively connected to the first control device to perform update processing on a safety program implemented in the second control device for the purpose of preventing incorrect operations, wherein: the first control device comprises a data processing control that generates information indicating a current operating condition of the first control device and information indicating a current operating condition of the vehicle, based on data detected by the first control device and data received from another control device, collects data requested by the other control device and sends the collected data to the other control device.And if a latest version of the safety program to which the safety program is to be updated exists in relation to the second control device, it transmits the latest version of the safety program to the second control device; and the second control device, which has received the latest version of the safety program from the first control device, receives from the first control device the information specifying the current operating condition of the first control device, and information specifying the current operating condition of the vehicle, specifies the current operating condition of the vehicle based on the consistency between the information specifying the current operating condition of the first control device and the information specifying the current operating condition of the vehicle, and if the specified current operating condition matches a vehicle operating condition,If processing to update the security program to the latest version is possible, it executes the processing to update the security program to the latest version.
[0011] Furthermore, a program update control method according to this invention is applied to a vehicle in which a first control device and one or more second control devices are installed, which are communicatively connected to the first control device in order to perform an update processing on a safety program that is implemented in the second control device for the purpose of preventing incorrect operations, and includes: a first step for generating information indicating a current operating condition of the first control device and information indicating a current operating condition of the vehicle, based on data detected by the first control device and data transmitted from another control device;a second step to collect data required by the other control device from the information generated in the first step and to transmit the collected data to the other control device; and a third step to transmit a latest version of the security program, to which the security program is to be updated, to the second control device, if the latest version of the security program exists in relation to the second control device, wherein the first, second and third steps are implemented by the first control device;a fourth step to determine the information specifying the current operating condition of the first control device and the information specifying the current operating condition of the vehicle from the first control device after receiving the latest version of the safety program from the first control device and specifying the current operating condition of the vehicle from a consistency between the information specifying the current operating condition of the first control device and the information specifying the current operating condition of the vehicle;and a fifth step to execute the processing to update the safety program to the latest version of the safety program if the current operating condition specified in the fourth step matches a vehicle operating condition in which processing to update the safety program to the latest version of the safety program is possible, wherein the fourth and fifth steps are implemented by the second control device.
[0012] In the program update control system and program update control method according to this invention, a safety function implemented to ensure that the vehicle does not operate abnormally as a result of an incorrect operation can be updated at a time when incorrect operations are not being performed. As a result, it is possible to obtain a program update control system and a program update control method with which a program implementing a safety function against incorrect operations in a vehicle network system can be updated at an appropriate time, according to the characteristics of an ECU, and so on. BRIEF DESCRIPTION OF THE DRAWINGS Fig. Figure 1 is a schematic view showing a network configuration inside and outside a vehicle in which a program update control system according to a first embodiment of this invention is installed; Fig. Figure 2 is a flowchart showing a series of processes of a program update control procedure, which is executed by the program update control system according to the first embodiment of this invention; Fig. Figure 3 is a flowchart showing a series of processes of the program update control procedure, which is carried out by the program update control system according to the first embodiment of this invention; Fig. Figure 4 is a flowchart showing a series of processes relating to a program update time, executed by a program update control system according to a second embodiment of this invention; and Fig. Figure 5 is a flowchart showing a series of processes relating to a message display, which is executed by a program update control system according to a third embodiment of this invention. DESCRIPTION OF PREFERRED EXECUTION FORMS
[0013] Preferred embodiments of a program update control system and a program update control method according to this invention are described below with reference to the drawings. First embodiment
[0014] Fig. Figure 1 is a schematic view showing a network configuration inside and outside a vehicle 202 in which a program update control system according to a first embodiment of this invention is installed. The vehicle 202 includes, as individual control devices, a head unit ECU 101, a gateway ECU 102, a powertrain system ECU 103, a sensor ECU 104, and a body system ECU 105.
[0015] A server 201 is located outside the vehicle 202. The server 201 is connected to the head unit ECU 101 via radio communication 301. The head unit ECU 101 and the gateway ECU 102 are connected via a high-speed communication line 401. The gateway ECU 102 is connected to the powertrain system ECU 103, the sensor ECU 104, and the body system ECU 105 via a low-speed communication line 402.
[0016] Security measures 151 to 155, such as authentication of messages traveling on the various communication lines and access restrictions, are implemented by the corresponding ECUs 101 to 105 in accordance with ECUs 101 to 105. It should be noted that the in Fig. The network configuration shown is an example and other configurations can be used.
[0017] Next, operations and functions of the in Fig. The component elements shown in section 1 are described.
[0018] First, Server 201 is described. Server 201 contains programs for the corresponding ECU1 101 to 105. Each program includes not only the currently installed version, but also an older version and a newer version to which the current version must be updated. The programs are stored on Server 201 by a manager, administration system, or similar system for managing Server 201.
[0019] In a program update control system such as the one in Fig. As shown in Figure 1, the program of each ECU can be updated to the new version as needed to address new challenges and vulnerabilities. When an ECU program needs updating, a program update for the ECU is sent from server 201 via radio communication 301 to the vehicle's head unit ECU 101 202.
[0020] Next, the head unit ECU 101 will be described.
[0021] The head unit ECU 101 receives the program update for the ECU from server 201 via radio communication 301. The head unit ECU 101 then transmits the received program update to the gateway ECU 102. At this time, the head unit ECU 101 does not transmit any program updates relating to the head unit ECU 101 itself.
[0022] Next, the Gateway ECU 102 will be described.
[0023] The gateway ECU 102 collects data required by the head unit ECU 101, the powertrain system ECU 103, the sensor ECU 104 and the body system ECU 105 from data determined by the respective ECUs and transmits the collected data to them.
[0024] For example, while driving, the gateway ECU 102 transmits information received from the sensor ECU 104 via the low-speed line 402 to the powertrain ECU 103. In response, the powertrain ECU 103 determines the values transmitted from the gateway ECU 102 and implements operational changes.
[0025] Gateway ECU 102 then receives a program update from head unit ECU 101 via high-speed communication line 401. Gateway ECU 102 then transmits this program update to the associated update subject ECU via low-speed communication line 402. At this time, Gateway ECU 102 does not transmit any program updates related to Gateway ECU 102 itself.
[0026] Next, the drive system ECU 103 will be described.
[0027] The powertrain ECU 103 is an ECU for controlling steering, braking, and so on. Furthermore, a safety program 153 is implemented in the powertrain ECU 103 to prevent operations not intended by a driver or control device, such as sudden acceleration or abrupt steering, from occurring on the vehicle 202 as a result of an incorrect operation.
[0028] When the safety program 153 of the drive system ECU 103 needs to be updated, the drive system ECU 103 updates the safety program 153 to a program update received from the gateway ECU 102 via the low-speed line 402.
[0029] Next, the sensor ECU 104 will be described.
[0030] The Sensor-ECU 104 is an ECU for detecting conditions inside and outside the vehicle using cameras, radar, and other technologies. Furthermore, a security program 154 is implemented in the Sensor-ECU 104, which prevents the detection of manipulated images, reflection waves, and other such phenomena resulting from incorrect operation.
[0031] When the security program 154 of the sensor ECU 104 needs to be updated, the sensor ECU 104 updates the security program 154 to a program update received from the gateway ECU 102 via the low-speed line 402.
[0032] Next, the body system ECU 105 will be described.
[0033] The body system ECU 105 is an ECU for controlling door locks, an immobilizer, windows, and so on. Furthermore, a security program 155 is implemented in the body system ECU 105 to prevent theft of the vehicle 202 or to ensure that an invalid key for the vehicle 202 is not authenticated.
[0034] When the body system ECU 105's security program 155 needs updating, the body system ECU 105 updates the security program 155 to a program update received from the gateway ECU 102 via the low-speed line 402.
[0035] Next, the program update control procedure executed by the program update control system according to the first embodiment, which has the above configuration, will be described in detail using flowcharts. Fig. 2 and Fig. Figure 3 are flowcharts showing a series of processes of the program update control procedure performed by the program update control system according to the first embodiment of this invention.
[0036] A case in which the program of the body system ECU 105 is updated is given as a specific example using the in Fig. The process is described in the flowchart shown in Figure 2. A program update for the body system ECU 105 is stored in server 201. In step S101, server 201 starts the program update processing. It is assumed here that the program update is specifically an updated version of the safety program 155 implemented in the body system ECU 105 to respond to incorrect operations.
[0037] In step S201, server 201 sends the updated version of security program 155 to the head unit ECU 101 to update the program of the body system ECU 105. In step S202, the head unit ECU 101 receives security program 155 sent to it from server 201.
[0038] Next, in step S301, the head unit ECU 101 sends the updated version of the security program 155 to the gateway ECU 102 to update the program of the body system ECU 105. In step S302, the gateway ECU 102 receives the security program 155 sent to it from the head unit ECU 101.
[0039] Next, in step S401, the gateway ECU 102 sends the latest version of the security program 155 to the body system ECU 105 to update its program. In step S402, the body system ECU 105 receives the security program 155 sent to it from the gateway ECU 102.
[0040] In step S501, the body system ECU 105 determines whether the safety program 155 implemented in the body system ECU 105 can be updated. If an update is possible, the routine proceeds to step S601, and if an update is not possible, the routine proceeds to step S102.
[0041] Next, the processing performed in step S501 will be described in detail using the data provided in Fig. The flowchart shown in section 3 describes the process. It should be noted that the flowchart in Fig. The 3 steps shown are identified by sub-numbers appended to S501 via a hyphen.
[0042] In step S501-11, the body control system ECU 105 checks the operating conditions to determine whether the security program 155 can be updated. Here, the functions of the body control system ECU 105, namely authenticating the validity of the vehicle 202 key and preventing theft of the vehicle 202, are executed while the vehicle 202 is stopped.
[0043] Therefore, the safety program 155 can be set to activate only when the vehicle 202 is stopped. In other words, the safety program 155 does not need to be activated while driving and can therefore be updated.
[0044] Next, in step S501-21, the body system ECU 105 sends a request to the gateway ECU 102, which is connected to the other ECUs via the high-speed communication line 401 or the low-speed line 402, to send the vehicle's operating condition 202. Here, the operating condition specifically refers to conditions such as driving, stopping, and charging.
[0045] The gateway ECU 102 can determine a vehicle speed from the powertrain system ECU 103 and predetermine the operating condition from the determined vehicle speed in steps S501-101 and S501-102 before receiving the request from the body system ECU 105. Then, after receiving the request from the body system ECU 105, the gateway ECU 102 sends the operating condition determined in step S501-102 to the body system ECU 105 in step S501-22.
[0046] Next, in step S501-23, the body system ECU 105 receives the operating condition sent to it from the gateway ECU 102, whereupon the routine advances to step S501-31.
[0047] Next, in step S501-31, the body system ECU 105 sends a request to the gateway ECU 102 to send the operating condition of the gateway ECU 102 itself.
[0048] Next, in step S501-32, the gateway ECU 102 sends the operating condition of this to the body system ECU 105 in response to the request from the body system ECU 105.
[0049] Next, in step S501-33, the body system ECU 105 determines the operating condition of the gateway ECU 102 from the gateway ECU 102.
[0050] It should be noted that the operating condition of the Gateway ECU 102, which is sent in step S501-32, is different information than the operating condition of the vehicle, which is sent in step S501-22.
[0051] During driving, the gateway ECU 102 processes and transmits information received from the sensor ECU 104 to the powertrain ECU 103. At this time, radar detection values received by the gateway ECU 102 via the sensor ECU 104 change successively.
[0052] Therefore, in addition to the operating condition of the vehicle 202, the gateway ECU 102 can successively receive the conditions of the ECUs that are operational at that time. As a result, the output port 102 can send the most recent information received from the other ECUs at any given time to the body system ECU 105 as the operating condition of the gateway ECU 102 itself.
[0053] Next, in step S501-41, the body system ECU 105 determines whether the safety program 155 can be updated or not by determining whether the vehicle 202 is moving or not, based on the results received in relation to the operating condition of the vehicle 202 and the operating condition of the gateway ECU 102.
[0054] More specifically, the body system ECU 105 determines whether the operating condition of vehicle 202, obtained in step S501-23, is consistent with the operating condition of gateway ECU 102, determined in step S501-33. If the information relating to the two operating conditions is consistent, the body system ECU 105 determines from the result whether vehicle 202 is moving or not.
[0055] However, if the two sets of information are inconsistent, the body system ECU 105 cannot accurately determine whether the vehicle 202 is moving or not, and therefore the update processing is interrupted. The routine then proceeds to step S102, where the sequence of processes is terminated.
[0056] If the information is determined to be consistent and vehicle 202 is determined to be moving, safety program 155 can be updated, and therefore the routine advances to step S601. Conversely, if the information is determined to be consistent, but vehicle 202 is determined to be stopped, safety program 155 cannot be updated, and therefore the routine advances to step S102, where the sequence of processes is terminated.
[0057] Next, returning to Fig. 2. In step S601, the body system ECU 105 updates the safety program 155. It should be noted that the pre-update safety program remains inoperative during the update.
[0058] Next, in step S701, the body system ECU 105 informs the gateway ECU 102 that the update of the safety program 155 of the body system ECU 105 is complete. In step S702, the gateway ECU 102 receives the update completion message from the body system ECU 105.
[0059] Next, in step S801, the gateway ECU 102 informs the head unit ECU 101 that the update of the safety program 155 of the body system ECU 105 is complete. In step S802, the head unit ECU 101 receives the update completion message from the gateway ECU 102.
[0060] Next, in step S901, the head unit ECU 101 informs server 201 that the update of security program 155 of the body system ECU 105 is complete. In step S902, server 201 receives the update completion message from head unit ECU 101.
[0061] In step S102, server 201 terminates the series of processes following the completion or interruption of the program update processing.
[0062] By executing this series of processes, an implemented safety program can ensure that vehicle 202 does not operate abnormally as a result of an incorrect operation. This update can be performed in the respective ECUs at a time when incorrect operations are not being carried out. As a result, vehicle 202 can be protected from incorrect operations during the safety program update, should vehicle 202 be vulnerable to such operations.
[0063] It should be noted that the first embodiment describes a case in which the safety program 155 of the body system ECU 105 is updated to the program update received via the head unit ECU 101. However, this invention is not limited to program updates via this route.
[0064] Another configuration, such as a configuration in which the body system ECU 105 is rewritten by direct access to the low-speed communication line 402 via a DLC connector or the like, or a configuration in which the program update is sent directly to the body system ECU 105 from the server 201, can be used to update the program.
[0065] Furthermore, in the first embodiment an example was described in which the safety program of the body system ECU 105 was updated, but similar update procedures can be applied to the other ECUs.
[0066] For example, functions that are activated while the vehicle 202 is moving are implemented in the powertrain system ECU 103. Therefore, using means to confirm that the vehicle 202 is not moving, or in other words, that the vehicle 202 is stopped, a safety program that is implemented to ensure that the vehicle 202 does not operate abnormally while moving as a result of an incorrect operation can be updated at a time when incorrect operations are not being performed.
[0067] Furthermore, in the first embodiment, the Fig. The specific example shown is described as the network configuration, but this invention can be applied to a different network configuration than the one shown. Fig. The features of this invention can be applied to any network configuration in which a security program is rewritten.
[0068] Furthermore, in the first embodiment, the determination of whether an update is possible or not is made after the body system ECU 105, serving as the update subject ECU, receives the program update; however, this invention is not limited to this procedure and instead the program update can be received after determining whether an update is possible or not. Second embodiment
[0069] Reference numerals in the drawings, which are identical to those of the first and third embodiments, denote components with identical basic functions. The following description focuses on additional functions of the second embodiment.
[0070] The head unit ECU 101 according to the second embodiment is able to receive the information relating to the gateway ECU 102 and the information relating to the respective ECUs, which can be obtained by the gateway ECU 102 via the low-speed communication line 402 of the gateway ECU 102, via the high-speed communication line 401.
[0071] Accordingly, the head unit ECU 101 generates drive-course information relating to the driver or the vehicle itself by associating the information relating to the respective ECUs 102 to 105 with position information indicating the position of the vehicle 202, peripheral device information and time information detected by the head unit ECU 101 itself, and stores the drive-course information in a storage unit.
[0072] Furthermore, the head unit ECU 101 predicts a subsequent route and operation to be undertaken by the driver or the vehicle itself, based on past driving history information, as well as position and peripheral equipment information obtained in relation to vehicle 202 using the current time and map information. For example, if the driver returns to the vicinity of their home several hours after leaving for a destination away from home, it can be assumed that vehicle 202 will be parked.
[0073] Furthermore, if a security program update exists in server 201 for one of the ECUs provided in the vehicle 202, the head unit ECU 101 sends the security program update to the update subject ECU.
[0074] A program update control procedure executed by the program update control system according to the second embodiment, which has the above configuration, will now be described in detail using a flowchart. Fig. Figure 4 is a flowchart showing a series of processes relating to the program update time, which is executed by the program update control system according to the second embodiment of this invention.
[0075] In step S1101, the head unit ECU 101 starts the control procedure according to the second embodiment.
[0076] Next, in step S1201, the head unit ECU 101 checks whether any updates for the security programs of the ECUs provided in the vehicle 202 exist in server 201 or not.
[0077] Next, in step S1202, server 201 checks whether any program updates to be applied to the security programs of the ECUs provided in vehicle 202 exist or not, and sends the result of the check to the head unit ECU 101.
[0078] Next, in step S1203, the head unit ECU 101 receives the test result. Then, in step S1301, the head unit ECU 101, which received the test result in step S1203, determines whether any of the security programs need to be updated.
[0079] If the head unit ECU 101 determines that an update is required, the routine advances to step S1401. If, on the other hand, an update is not required, the route advances to step S1102, where the sequence of processes ends.
[0080] Next, in step S1401, the head unit ECU 101 predicts the subsequent route and the operation to be undertaken by the driver or the vehicle itself, based on past driving information as well as position information and peripheral equipment information obtained in relation to the vehicle 202, using current time and map information.
[0081] Next, in step S1501, the head unit ECU 101 predicts the condition of vehicle 202, that is, whether vehicle 202 will be stopped or moving at a preset time t in the future, based on the prediction result obtained in step S1401.
[0082] Here, the head unit ECU 101 selects either that vehicle 202 is stopped or that vehicle 202 is moving, at time t and thereafter. If the state of vehicle 202, which requires the safety program to be updated, matches the selected condition, the routine advances to step S1601. If the conditions do not match, the routine returns to step S1401, where the head unit ECU 101 again predicts the vehicle operation.
[0083] In other words, if the head unit ECU 101 predicts that the vehicle 202 is moving at time t and thereafter, the head unit ECU 101 determines whether the safety program to be updated is a safety program that can be updated while moving and is required while stationary.
[0084] Furthermore, if the head unit ECU 101 predicts that the vehicle 202 is stopped at time t and thereafter, the head unit ECU 101 determines whether the safety program to be updated is a safety program that can be updated while stopped and while driving.
[0085] Furthermore, at this time the head unit ECU 101 calculates a time t update , at which point the rewriting of the ECU, for which a security program update exists, must be started. The time t update is earlier than the aforementioned time t and is calculated based on a time quantity required to update the program as a time to complete an update preparation operation before time t.
[0086] Next, in step S1601, the head unit ECU 101 checks whether the current time is at time t updateIt determines whether the timings match or not, and if they do, it determines that the update time has arrived. The routine then proceeds to step S1701.
[0087] Next, in step S1701, the head unit ECU 101, which predicted that the vehicle 202 would stop at time t2 upon receiving a prediction result obtained in step S1501, will select an ECU with a safety program that can be updated while stopped. The powertrain system ECU 103 and so on can be cited as examples of ECUs with a safety program that is required while driving but can be updated while stopped.
[0088] Furthermore, after predicting that vehicle 202 will be moving at time t when receiving the prediction result in step S1501, the head unit ECU 101 selects an ECU with a safety program that can be updated while driving. The body system ECU 105 can be cited as an example of an ECU that has a safety program required while stopped, but which can be updated while driving.
[0089] At this time, the head unit ECU 101 confirms that the ECU selected in step S1701 matches the ECU that has the security program to be updated, as verified in step S1201. Following this confirmation, the head unit ECU 101 receives the latest version of the security program relating to the selected ECU from server 201.
[0090] The routine then moves to step S301 in Fig. 2 before, where the head unit ECU 101 sends the latest version of the security program, received from server 201, to the selected ECU before time t. From step S301 onwards, identical processing to that of Fig. 2 carried out. Fig. Figure 2 shows a case where the body system ECU 105 is selected.
[0091] By controlling the timing of the download of the latest version of the security program as described above, each ECU can be updated to the latest security program version at a time when an update is possible and immediately before transitioning to a condition where incorrect operations could be performed. Once the latest version of the security program has been downloaded, it is possible to address vulnerabilities not covered by the previous version.
[0092] It should be noted that in the second embodiment a case was described in which the safety program 155 of the body system ECU 105 is updated to the program update obtained via the head unit ECU 101, but this invention is not limited to program updates via this route.
[0093] Another configuration, such as a configuration in which the body system ECU 105 is rewritten by directly accessing the low-speed communication line 402 via a DLC connector or the like, or a configuration in which the program update is sent directly to the body system ECU 105 from the server 201, can be used to update the program.
[0094] Furthermore, in the second embodiment, an example was described in which the safety program of the body system ECU 105 is updated, but similar update procedures can be applied to the other ECUs.
[0095] Furthermore, in the second embodiment, the Fig. The example shown is described as the network configuration, but this invention can be applied to a different network configuration than the one shown. Fig. The features of this invention can be applied to any network configuration in which a security program is rewritten.
[0096] Furthermore, in the second embodiment, a case was described in which the head unit ECU 101 first checks in the server 201 for any security program updates in step S1201, but this invention is not limited to this procedure and instead the server 201 can detect the existence of a security program update and notify the head unit ECU 101. Third embodiment
[0097] Reference numerals in the drawings, which are identical to those of the first and second embodiments, denote components with identical basic functions. The following description will focus on additional functions of the third embodiment.
[0098] The head unit ECU 101 according to the third embodiment is configured to be able to send a display instruction to an instrument panel 106, which is formed by installing an LED to communicate a predetermined condition to the driver in an instrument panel.
[0099] The instrument panel 106 is controlled by the head unit ECU 101. The head unit ECU 101 is capable of displaying either a condition in which a safety program can be updated, or a condition in which the safety program cannot be recognizably updated.
[0100] A program update control procedure, which is executed by the program update control system according to the third embodiment, which has the configuration described above, will now be described in detail using a flowchart. Fig. Figure 5 is a flowchart showing a series of processes related to message display performed by the program update control system according to the third embodiment of this invention. It should be noted that circled letters A and B in Fig. 5 connections to circled characters A and B, which are in Fig. 4 are shown.
[0101] In step S1301, the head unit ECU 101 determines whether it is impossible to implement the determination processing of step S1501 of the second embodiment, which is described in Fig. Figure 4 shows a predetermined number of times that is preset. If the head unit ECU 101 determines that the determination processing for the predetermined number of times has not been implemented, the routine advances to step S3201.
[0102] In step S3102, the head unit ECU 101 determines whether the time t used in step S1501 of the second embodiment, in Fig. 4 shown, earlier or later than a time t limit is. Time t limit The head unit ECU 101 sets this based on the probability that a presented threat would materialize as a result of an incorrect operation, or the degree to which vehicle 202 would be affected by such a threat if the latest version of the security program were not installed. The time t limit is considered constant and closer to a current time t current It is set when the probability or degree of threat increases.
[0103] If the head unit ECU 101 determines that time t is later than time t limit If this is the case, the routine advances to step S3201. If the head unit ECU 101 determines that time t is no later than time tlimit On the other hand, the routine for processing step S1601 continues into Fig. 4 before.
[0104] When the routine advances to step S3201, the head unit ECU 101 informs the instrument panel LED 106 that the security program cannot be updated because either the update timing cannot be determined or the update timing is later than time t limit is.
[0105] Next, in step S3202, a predetermined LED of the instrument panel LED 106 is switched on to indicate the fact that the safety program cannot be recognizably updated, and as a result, this is communicated to the driver of vehicle 202.
[0106] In step S3203, the driver confirms the content of the displayed message. Then, in step S3301, the driver communicates the vehicle's condition (202) based on the confirmation of the message content so that the safety program can be updated. For example, if the program update for the powertrain system ECU's safety program is 103, and the driver learns from the displayed content that the safety program cannot be updated, the driver stops the vehicle (202) so that the safety program can be updated.
[0107] By involving the driver in the processing as described above, the safety program can be updated earlier in cases where it is not clear from the driving history when the safety program update will be applied, or in cases where the application of the safety program update is delayed. As a result, the latest version of the safety program can be applied earlier, thus providing protection against malicious incorrect operations.
[0108] It should be noted that in the third embodiment, the driver is notified of a condition in which an update is impossible, but the communication subject is not limited to the driver. For example, in the case of a self-driving vehicle or the like, in which a driver is not present, the communication subject may be another ECU (in other words, a vehicle information management device) provided within the vehicle to manage and manipulate the vehicle's driving condition, or a management device (in other words, an external information management device) such as a server that can monitor and manipulate the vehicle's driving condition from outside the vehicle.
Claims
[1] A program update control system applied to a vehicle (202) in which a first control device (102) and one or more second control devices (103, 104, 105) are installed, which are communicatively connected to the first control device (102), for performing update processing on a security program implemented in one of the one or more second control devices (103, 104, 105) for the purpose of preventing incorrect operations, wherein: the first control device (102) comprises a data processing controller which: information indicating a current operating condition of the first control device (102) and information indicating a current operating condition of the vehicle (202) are generated based on data detected by the first control device (102) and data obtained from another of the one or more second control devices (103, 104, 105), collects data requested by the other of the one or more second control devices (103, 104, 105) and transmits the collected data to the one of the one or more second control devices (103, 104, 105), and if a most recent version of the safety program to which the safety program is to be updated exists in relation to one of the one or more second control devices (103, 104, 105), transmits the most recent version of the safety program to the one of the one or more second control devices (103, 104, 105); and the one of the one or more second control devices (103, 104, 105) which has received the latest version of the security program from the first control device (102): receives from the first control device (102) the information indicating the current operating condition of the first control device (102) and the information indicating the current operating condition of the vehicle (202), the current operating condition of the vehicle (202) is specified based on the consistency between the information indicating the current operating condition of the first control device (102) and the information indicating the current operating condition of the vehicle (202), and if the specified current operating condition is matched with a vehicle operating condition such that processing for updating the safety program to the latest version of the safety program is possible, executes the processing for updating the safety program to the latest version of the safety program. [2] A program update control system according to claim 1, wherein the data processing controller of the first control device (102): further generates and stores driving history information based on the data detected by the first control device (102) and the data obtained from the other of the one or more second control devices (103, 104, 105), predicts a first time operating condition, which is an operating condition of the vehicle (202) at a first time following the lapse of a preset time from a current time, based on the travel history information, the information indicating the current operating condition of the first control device (102), and the information indicating the current operating condition of the vehicle (202), and when the first time operating condition is matched with the vehicle operating condition in which the processing for updating the safety program to the latest version of the safety program is possible at a second time set at a time before the first time, transmits the latest version of the safety program to the one of the one or more second control devices (103, 104, 105) so that the transmission of the latest version of the safety program to the one of the one or more second control devices (103, 104, 105) is completed before the first time. [3] A program update control system according to claim 2, wherein, when a state in which the first time operating condition does not match the vehicle operating condition in which the processing for updating the security program to the latest version of the security program is possible occurs at least according to a preset consecutive number of times, the data processing control of the first control device (102): either announces via a warning device provided in the vehicle (202) that the security program cannot be updated to the latest version of the security program, or informs an information management device provided inside or outside the vehicle (202) for monitoring the driving condition of the vehicle (202) that the safety program cannot be updated to the latest version of the safety program. [4] A program update control system according to claim 2, wherein the data processing controller of the first control device (102): a time limit at which the processing for updating the security program to the latest version of the security program is to be performed is determined based on a degree to which the vehicle (202) is affected by an incorrect operation in a case where the processing for updating the security program to the latest version of the security program is not performed, and if the first time is later than the time limit: either announces via a warning device provided in the vehicle (202) that the security program cannot be updated to the latest version of the security program, or notifies an information management device provided inside or outside the vehicle (202) for monitoring a driving condition of the vehicle (202) that the safety program cannot be updated to the latest version of the safety program. [5] A program update control method applied to a vehicle (202) in which a first control device (102) and one or more second control devices (103, 104, 105) communicatively connected to the first control device (102) are installed, for performing update processing on a security program implemented in one of the one or more second control devices (103, 104, 105) for the purpose of preventing incorrect operations, the method comprising: a first step of generating information indicative of a current operating condition of the first control device (102) and information indicative of a current operating condition of the vehicle (202) based on data detected by the first control device (102) and data transmitted from another of the one or more second control devices (103, 104, 105); a second step: for collecting data required by the other of the one or more second control devices (103, 104, 105) from the information generated in the first step and for transmitting the collected data to one of the one or more second control devices (103, 104, 105); and a third step of transmitting a latest version of the safety program to which the safety program is to be updated to one of the one or more second control devices (103, 104, 105) if the latest version of the safety program exists in relation to the one of the one or more second control devices (103, 104, 105), wherein the first, second and third steps are implemented by the first control device (102); a fourth step: for determining the information indicating the current operating condition of the first control device (102) and the information indicating the current operating condition of the vehicle (202) from the first control device (102) after receiving the latest version of the security program from the first control device (102), and for specifying the current operating condition of the vehicle (202) based on a consistency between the information indicating the current operating condition of the first control device (102) and the information indicating the current operating condition of the vehicle (202); and a fifth step for executing processing for updating the safety program to the latest version of the safety program when the current operating condition specified in the fourth step is matched with a vehicle operating condition in which processing for updating the safety program to the latest version of the safety program is possible, wherein the fourth and fifth steps are implemented by the one of the one or more second control devices (103, 104, 105).
Citation Information
Patent Citations
Brake control system, and its program updating method
JP2007230317A
Vehicle control unit with power saving mode for a parking phase
DE102014008479A1
Update of a vehicle control via Car2X
DE102014219322A1
Program management apparatus
JP2010243339A
On-vehicle program update device
JP2014106875A
