Vehicle information communication system and vehicle information communication method
By using hash values to determine the need for full data transmission, the system reduces server load and optimizes data communication in vehicle information systems, addressing the challenge of managing ECU configurations efficiently.
Patent Information
- Application Number
- JP2023114466
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-08-10
- Filing Date
- 2023-07-12
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2039-07-12
AI Technical Summary
The existing vehicle information communication systems face a heavy load on the server when multiple vehicles transmit configuration information simultaneously, as they need to collect and manage the configuration of each electronic control unit (ECU) for OTA updates, leading to increased data communication demands.
The system employs in-vehicle devices to collect configuration information, generate a hash value, and transmit it to the center device. If the hash values do not match, the device sends all configuration information, reducing the overall data transmitted by only sending full data when necessary.
This approach reduces the amount of data communicated, alleviating server load and optimizing data transmission even with a large number of vehicles, ensuring efficient management of configuration information.
Smart Images

Figure 0007593444000001 
Figure 0007593444000002 
Figure 0007593444000003
Abstract
Description
[Technical Field]
[0001] The present invention relates to a vehicle information and communication system including a center device that manages data to be written to a plurality of electronic control devices mounted on a vehicle, and an on-board device mounted on the vehicle. and Vehicle information communication method By law Regarding. [Background technology]
[0002] In recent years, with the diversification of vehicle control, such as driving assistance functions and autonomous driving functions, the scale of application programs for vehicle control, diagnosis, etc., installed in vehicle electronic control units (hereinafter referred to as ECUs (Electronic Control Units)) is increasing. Furthermore, with version upgrades for functional improvements, etc., opportunities to rewrite (reprogram) ECU application programs are also increasing. Meanwhile, with the advancement of communication networks, connected car technology is also becoming widespread. In light of these circumstances, for example, Patent Document 1 discloses a technology in which an ECU update program is distributed from a center to an in-vehicle device via OTA (Over The Air) and the update program is rewritten on the vehicle side. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-224503 Summary of the Invention [Problem to be solved by the invention]
[0004] As described above, in order for the update program distributed via OTA to be rewritten on the vehicle side, the server distributing the program needs to know information about the configuration of the vehicle to which the program is being distributed, including, for example, the type of ECU installed and the version of the application program for each ECU.
[0005] Therefore, assuming a system in which each vehicle sends configuration information to a center device at a predetermined timing and the center device manages the information, there is a concern that if a large amount of data is sent from a large number of vehicles at once, it will place a heavy load on the server on the center device side.
[0006] The present invention has been made in view of the above circumstances, and its object is to provide a vehicle information communication system that can reduce the amount of data in communication between a center device and an in-vehicle device in order for the center device to manage the configuration information of each vehicle. and Vehicle information communication method The law The purpose is to provide. [Means for solving the problem]
[0007] According to the vehicle information communication system of claim 1, In-vehicle The device is Upon receiving a synchronization start request from the center device, Collect configuration information about the configuration of each device from multiple electronic control devices. , collection When a hash value is generated based on the data values of the collected configuration information, the center device transmits the hash value to the center device. In-vehicle The hash value sent from the device Vehicle side configuration The hash value of the vehicle configuration information stored in the information storage unit is compared, and if the two do not match, In-vehicle notifying the device of a full data transmission request requesting transmission of all data values of the configuration information; In-vehicle Upon receiving the transmission request, the device transmits all data values of the configuration information to the center device. Upon receiving all data values, the center device performs the following operations based on the data values: Vehicle side configuration Update the configuration information stored in the information storage unit. New do.
[0008] If you configure it like this, In-vehicle The device initially transmits the hash value of the configuration information to the center device, and only when the comparison result of the hash values at the center device shows a mismatch, does it transmit all the data values of the configuration information to the center device. In-vehicle This reduces the size of the data sent by the device, In-vehicleEven if the device is installed in a large number of vehicles, the overall amount of communication traffic can be reduced. [Brief explanation of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a vehicle information communication system in a first embodiment. [Figure 2] Diagram showing the electrical configuration of the CGW [Figure 3] Diagram showing the electrical configuration of the ECU [Figure 4] A diagram showing the connection of power lines [Figure 5] FIG. 10 is a diagram showing how reblog data and distribution specification data are packaged. [Figure 6] FIG. 1 illustrates unpackaging a distribution package. [Figure 7] FIG. 1 is a block diagram showing the parts of the center device that are primarily related to the functions of the server. [Figure 8] An image showing the processing flow in the center device [Figure 9] FIG. 10 is a diagram showing an example of vehicle configuration information registered in a configuration information DB. [Figure 10] A diagram showing an example of programs and data registered in the ECU repro data database [Figure 11] A diagram showing an example of specification data registered in the ECU metadata DB [Figure 12] FIG. 10 is a diagram showing an example of vehicle configuration information registered in the individual vehicle information DB. [Figure 13] FIG. 10 is a diagram showing an example of distribution package data registered in a package DB. [Figure 14] FIG. 10 is a diagram showing an example of campaign data registered in a campaign DB. [Figure 15] A flowchart showing the process of generating programs and data to be registered in the ECU repro data database [Figure 16] A flowchart showing a process for generating an example of specification data to be registered in the ECU metadata DB. [Figure 17] A diagram showing an example of specification data [Figure 18] FIG. 10 is a diagram showing an example of a bus load table. [Figure 19] A flowchart showing the process of generating a distribution package to be registered in the package DB. [Figure 20] A diagram showing the contents of a package file [Figure 21] FIG. 10 is a sequence diagram illustrating a processing procedure executed between the center device and the vehicle-side system in the second embodiment. [Figure 22] Flowchart showing processing performed by the center device [Figure 23] FIG. 23 is a diagram conceptually illustrating the processing contents performed in steps D6 and D7 of the flowchart shown in FIG. 22. [Figure 23A] 10 is a flowchart showing a process for transmitting a hash value from a vehicle-side system to a center device. [Figure 24] FIG. 10 is a sequence diagram illustrating a processing procedure executed between the center device and the vehicle-side system in the third embodiment. [Figure 25] Flowchart showing processing performed by the center device [Figure 26] A sequence diagram showing how the center device notifies electric vehicles and conventional vehicles via SMS. [Figure 27] FIG. 10 is a sequence diagram illustrating a processing procedure executed between the center device and the vehicle-side system in the fourth embodiment. [Figure 28] FIG. 13 is a diagram conceptually illustrating processing performed between a supplier, a center device, and a vehicle-side system in the fifth embodiment. [Figure 29] Sequence diagram showing the processing procedures between the supplier, center device, and vehicle system (part 1) [Figure 30] Sequence diagram showing the processing procedures between the supplier, center device, and vehicle system (part 2) [Figure 31] Sequence diagram showing the processing procedures between the supplier, center device, and vehicle system (part 3) [Figure 32]FIG. 10 is a diagram showing a data format of a package DB in a case where a plurality of packages are associated with one campaign, according to a first modification of the first embodiment. [Figure 33] A diagram showing the data format of the campaign DB when multiple packages correspond to one campaign. [Figure 34] Figure equivalent to Figure 16 when generating specification data for each group [Figure 35] Figure 19 (equivalent to Figure 19) when generating distribution packages for each group [Figure 36] FIG. 2 is a second modification of the first embodiment, showing the processing performed by the package generation tool; [Figure 37] FIG. 10 is a diagram showing the overall configuration of a sixth embodiment. [Figure 38] Diagram showing the electrical configuration of the CGW [Figure 39] Electrical configuration of a DCM [Figure 40] Diagram showing the electrical configuration of the ECU [Figure 41] A diagram showing the connection of power lines [Figure 42] FIG. 10 is a diagram showing how re-log data and distribution specification data are packaged. [Figure 43] Figure showing rewrite specification data for DCM [Figure 44] Figure showing rewritten specification data for CGW [Figure 45] Diagram showing distribution specification data [Figure 46] FIG. 1 illustrates unpackaging a distribution package. [Figure 47] A diagram showing the state of an embedded single-sided memory during normal operation. [Figure 48] A diagram showing the state of a rewrite operation in an embedded single-sided memory. [Figure 49] FIG. 10 is a diagram showing the state of a download-type single-sided independent memory during normal operation. [Figure 50] FIG. 10 is a diagram showing a state during a rewrite operation in a download-type single-sided independent memory. [Figure 51]FIG. 1 shows the state of a built-in single-plane suspend memory during normal operation. [Figure 52] FIG. 1 is a diagram showing the state of a built-in single-plane suspend memory during a rewrite operation. [Figure 53] FIG. 1 shows a state of a download-type one-sided suspend memory during normal operation. [Figure 54] FIG. 10 is a diagram showing a state during a rewrite operation in a download-type one-side suspend memory; [Figure 55] A diagram showing the state of an embedded two-sided memory during normal operation. [Figure 56] A diagram showing the state of a built-in two-sided memory during a rewrite operation. [Figure 57] FIG. 1 shows a state of a download-type two-sided memory during normal operation. [Figure 58] FIG. 10 is a diagram showing the state of a download-type two-sided memory during a rewrite operation. [Figure 59] FIG. 10 is a diagram showing a manner in which an application program is rewritten; [Figure 60] FIG. 10 is a diagram showing a manner in which an application program is rewritten; [Figure 61] FIG. 10 is a diagram showing a manner in which an application program is rewritten; [Figure 62] A timing chart showing how an application program is rewritten by power control. [Figure 63] A timing chart showing how an application program is rewritten by power control. [Figure 64] A timing chart showing how an application program is rewritten by self-maintaining power supply. [Figure 65] A timing chart showing how an application program is rewritten by self-maintaining power supply. [Figure 66] Diagram showing phases [Figure 67] A diagram showing the normal screen [Figure 68] A diagram showing the screen when a campaign notification occurs [Figure 69] Diagram showing the campaign notification screen [Figure 70]Figure showing the screen when download is accepted [Figure 71] Figure showing the screen when download is accepted [Figure 72] Figure showing the screen while downloading is in progress [Figure 73] Figure showing the screen while downloading is in progress [Figure 74] Figure showing the screen when download is complete [Figure 75] Figure showing the screen when you agree to the installation [Figure 76] Figure showing the screen when you agree to the installation [Figure 77] Figure showing the screen during installation [Figure 78] Figure showing the screen during installation [Figure 79] Figure showing the screen when activation is accepted [Figure 80] Diagram showing the screen when IG is on [Figure 81] Figure showing the confirmation screen [Figure 82] Figure showing the confirmation screen [Figure 83] Functional block diagram of the central device [Figure 84] DCM Functional Block Diagram [Figure 85] CGW functional block diagram [Figure 86] CGW functional block diagram [Figure 87] ECU functional block diagram [Figure 88] Functional block diagram of in-vehicle display [Figure 89] Functional block diagram of the distribution package transmission decision unit [Figure 90] Flowchart showing distribution package transmission determination processing [Figure 91] Functional block diagram of distribution package download determination unit [Figure 92] Flowchart showing distribution package download determination processing [Figure 93] Functional block diagram of the write data transfer determination unit [Figure 94] Flowchart showing write data transfer determination processing [Figure 95] Functional block diagram of the write data acquisition determination unit [Figure 96] Flowchart showing write data acquisition determination processing [Figure 97] Functional block diagram of the installation instruction determination unit [Figure 98] Flowchart showing installation instruction determination processing [Figure 99] FIG. 10 shows an example of an installation instruction. [Figure 100] FIG. 10 shows an example of an installation instruction. [Figure 101] FIG. 10 shows how random numbers are generated. [Figure 102] Functional block diagram of the security access key management unit [Figure 103] 10 is a flowchart showing a process for generating a security access key. [Figure 104] FIG. 1 illustrates how a security access key is generated. [Figure 105] 10 is a flowchart showing a process for erasing a security access key. [Figure 106] A diagram showing the process flow involved in verifying write data. [Figure 107] Functional block diagram of the write data verification unit [Figure 108] Flowchart showing verification processing of write data [Figure 109] FIG. 1 illustrates a distributed manner in which processes involved in verifying write data are performed. [Figure 110] FIG. 1 illustrates a distributed manner in which processes involved in verifying write data are performed. [Figure 111] FIG. 1 illustrates a distributed manner in which processes involved in verifying write data are performed. [Figure 112] FIG. 1 illustrates a distributed manner in which processes involved in verifying write data are performed. [Figure 113] A diagram showing the flow of verifying write data and rewriting application programs [Figure 114]A diagram showing the flow of verifying write data and rewriting application programs [Figure 115] Functional block diagram of the data storage surface information transmission control unit [Figure 116] Flowchart showing the data storage surface information transmission control process [Figure 117] A sequence diagram showing how to notify two-side rewrite information [Figure 118] Functional block diagram of the power management unit that is not subject to rewriting [Figure 119] Flowchart showing power management processing for non-rewrite targets [Figure 120] Diagram showing transitions between active, stopped, and sleep states [Figure 121] Diagram showing transitions between active, stopped, and sleep states [Figure 122] A diagram showing the connection of power lines [Figure 123] Flowchart showing the remaining battery charge monitoring process [Figure 124] Functional block diagram of the file transfer control unit [Figure 125] Flowchart showing file transfer control processing [Figure 126] FIG. 1 shows how files are exchanged. [Figure 127] FIG. 1 shows how files are exchanged. [Figure 128] A diagram showing divided files and written files. [Figure 129] FIG. 10 illustrates how the CGW sends a transfer request to the DCM. [Figure 130] FIG. 10 illustrates how the CGW sends a transfer request to the DCM. [Figure 131] FIG. 10 is a diagram showing how the CGW distributes write data to the ECU to be rewritten. [Figure 132] FIG. 10 is a diagram showing how the CGW distributes write data to the ECU to be rewritten. [Figure 133] FIG. 10 is a diagram showing how the CGW distributes write data to the ECU to be rewritten. [Figure 134] Diagram showing the connection state of ECU [Figure 135] Functional block diagram of the write data distribution control unit [Figure 136] Figure showing the bus load table [Figure 137] Figure showing the ECU belonging table to be rewritten [Figure 138] Flowchart showing write data distribution control processing [Figure 139] FIG. 10 is a diagram showing how write data is distributed; [Figure 140] FIG. 10 is a diagram showing how write data is distributed; [Figure 141] FIG. 10 is a diagram showing a manner in which write data is distributed while a vehicle is running. [Figure 142] FIG. 10 is a diagram showing a mode of distributing written data while parking; [Figure 143] Diagram showing the amount of written data distributed [Figure 144] Diagram showing the amount of written data distributed [Figure 145] Functional block diagram of the activation request instruction unit [Figure 146] Flowchart showing activation request instruction processing [Figure 147] FIG. 10 is a diagram showing a mode of issuing an activation request. [Figure 148] Functional block diagram of the Activate execution control unit [Figure 149] Flowchart showing rewrite processing [Figure 150] Flowchart showing the execution control process of activation [Figure 151] Functional block diagram of the grouping unit to be rewritten [Figure 152] Flowchart showing group management processing to be rewritten [Figure 153] Flowchart showing group management processing to be rewritten [Fig. 154] FIG. 10 is a diagram showing a mode of grouping rewrite targets; [Figure 155] Functional block diagram of the rollback execution control unit [Figure 156] Flowchart showing a process for identifying a rollback method [Figure 157] Flowchart showing a cancellation request determination process [Figure 158] Flowchart showing a cancellation request determination process [Figure 159] Flowchart showing a cancellation request determination process [Figure 160] Flowchart showing a cancellation request determination process [Figure 161] Flowchart showing a cancellation request determination process [Figure 162] FIG. 10 illustrates a manner in which a rollback is performed. [Figure 163] FIG. 10 illustrates a manner in which a rollback is performed. [Fig. 164] FIG. 10 illustrates a manner in which a rollback is performed. [Figure 165] FIG. 10 illustrates a manner in which a rollback is performed. [Figure 166] FIG. 10 illustrates a manner in which a rollback is performed. [Figure 167] Functional block diagram of the display control unit for the rewrite progress status [Figure 168] Flowchart showing display control process of rewriting progress status [Figure 169] Flowchart showing display control process of rewriting progress status [Figure 170] Figure showing the rewrite progress screen [Figure 171] Figure showing the rewrite progress screen [Fig. 172] Figure showing the rewrite progress screen [Figure 173] Figure showing the rewrite progress screen [Fig. 174] Figure showing the rewrite progress screen [Figure 175] A diagram showing the transition of the progress graph display [Figure 176] A diagram showing the transition of the progress graph display [Figure 177] A diagram showing the transition of the progress graph display [Figure 178] A diagram showing the transition of the progress graph display [Figure 179] Figure showing the rewrite progress screen [Figure 180] Functional block diagram of the differential data consistency check unit [Figure 181] Flowchart showing the process of determining consistency of differential data [Figure 182] FIG. 10 is a diagram showing a mode of determining consistency of differential data; [Figure 183] FIG. 10 is a diagram showing a mode of determining consistency of differential data; [Figure 184] Functional block diagram of the rewrite execution control unit [Figure 185] Flowchart showing normal operation processing [Figure 186] Flowchart showing rewrite operation processing [Figure 187] Flowchart showing information notification processing [Figure 188] Flowchart showing verification processing of a rewrite program [Figure 189] FIG. 10 is a diagram showing a mode of transmitting identification information and write data. [Figure 190] FIG. 10 is a diagram showing a mode of transmitting identification information and write data. [Figure 191] Flowchart showing installation instruction processing [Figure 192] Functional block diagram of the session establishment unit [Figure 193] Program structure diagram [Figure 194] State transition diagram [Figure 195] State transition diagram [Figure 196] State transition diagram [Figure 197] Diagram showing session arbitration [Figure 198] Diagram showing session arbitration [Figure 199] Flowchart showing state transition management processing of the first state [Figure 200] Flowchart showing state transition management processing of the first state [Figure 201] Flowchart showing state transition management processing of the first state [Figure 202]Flowchart showing state transition management processing of the second state [Figure 203] Flowchart showing state transition management processing of the second state [Figure 204] Program structure diagram [Figure 205] State transition diagram [Figure 206] Functional block diagram of the retry point identification section [Figure 207] Diagram showing the configuration of flash memory [Figure 208] Flowchart showing processing flag setting processing [Figure 209] Flowchart showing processing flag determination processing [Figure 210] Flowchart showing processing flag determination processing [Figure 211] Functional block diagram of the progress status synchronization control unit [Figure 212] Functional block diagram of the progress status synchronization control unit [Figure 213] FIG. 10 is a diagram showing a mode of transmitting and receiving a progress status signal; [Figure 214] Flowchart showing progress status synchronization control process [Figure 215] Flowchart showing progress status synchronization control process [Figure 216] Flowchart showing progress status display processing [Figure 217] Functional block diagram of a display control information transmission control unit [Figure 218] Flowchart showing a transmission control process for display control information [Figure 219] Functional block diagram of the display control information reception control unit [Figure 220] Flowchart showing reception control processing of display control information [Figure 221] A diagram showing the information included in the distribution specification data [Figure 222] Functional block diagram of the progress display screen control unit [Figure 223] Diagram showing rewritten specification data [Figure 224] Figure showing the screen when selecting a menu [Figure 225] Figure showing the screen when selecting a user [Figure 226] Figure showing the screen for user registration [Figure 227] Flowchart showing progress display screen display control process [Figure 228] Flowchart showing progress display screen display control process [Figure 229] Message frame diagram [Figure 230] Figure showing the screen when activation is accepted [Figure 231] Figure showing whether to display an item [Figure 232] Figure showing whether to display an item [Figure 233] Figure showing the screen when activation is accepted [Figure 234] FIG. 1 shows a data communication mode. [Figure 235] Figure showing the message frame when a campaign is notified [Figure 236] Figure showing the message frame when download is accepted [Figure 237] Figure showing the message frame when installation is accepted [Figure 238] Figure showing the message frame when activation is accepted [Figure 239] Diagram showing screen transitions [Figure 240] A diagram showing the screen when a campaign notification occurs [Figure 241] Figure showing the screen when download is accepted [Figure 242] Figure showing the screen when download is accepted [Figure 243] Figure showing the screen while downloading is in progress [Figure 244] Figure showing the screen when download is complete [Figure 245] Figure showing the screen when you agree to the installation [Figure 246] Figure showing the screen when activation is accepted [Figure 247] Functional block diagram of the program update notification control unit [Figure 248] Flowchart showing program update notification control processing [Figure 249] FIG. 10 is a diagram showing a notification mode of an indicator. [Figure 250] FIG. 10 is a diagram showing the transition of notification modes when the rewrite target is a two-sided memory; [Figure 251] FIG. 10 is a diagram showing the transition of notification modes when the rewrite target is one-side suspend memory; [Figure 252] FIG. 10 is a diagram showing the transition of notification modes when the rewrite target is a single-sided memory. [Figure 253] A diagram showing a connection mode [Figure 254] Functional block of the execution control unit for self-maintaining power supply in CGW [Figure 255] Functional block of the execution control unit for self-maintaining power supply in the ECU [Figure 256] Flowchart showing the execution control process of power self-maintenance in CGW [Figure 257] Flowchart showing the execution control process of the power supply self-maintenance in the ECU [Figure 258] Diagram showing the period when the power supply needs to be self-maintained [Figure 259] An overall sequence diagram showing how an application program is rewritten [Figure 260] An overall sequence diagram showing how an application program is rewritten [Figure 261] An overall sequence diagram showing how an application program is rewritten [Figure 262] An overall sequence diagram showing how an application program is rewritten [Figure 263] An overall sequence diagram showing how an application program is rewritten [Figure 264] An overall sequence diagram showing how an application program is rewritten [Figure 265] An overall sequence diagram showing how an application program is rewritten [Figure 266] An overall sequence diagram showing how an application program is rewritten [Figure 267]An overall sequence diagram showing how an application program is rewritten [Figure 268] An overall sequence diagram showing how an application program is rewritten [Figure 269] An overall sequence diagram showing how an application program is rewritten DETAILED DESCRIPTION OF THE INVENTION
[0010] (First embodiment) A first embodiment of the present invention will be described below with reference to Fig. 1 to Fig. 20. The vehicle program rewriting system is a system capable of rewriting application programs for vehicle control, diagnosis, etc. of an ECU mounted on a vehicle via OTA. As shown in Fig. 1, the vehicle program rewriting system 1 includes a center device 3 on the communication network 2 side, a vehicle-side system 4 on the vehicle side, and a display terminal 5. The communication network 2 includes, for example, a mobile communication network using a 4G line or the like, the Internet, WiFi (Wireless Fidelity) (registered trademark), etc.
[0011] The display terminal 5 is a terminal having a function to receive operation inputs from the user and a function to display various screens, and is, for example, a mobile terminal 6 such as a smartphone or tablet that can be carried by the user, or an in-vehicle display 7 such as a display that also functions as a navigation system or a meter display that is located inside the vehicle. The mobile terminal 6 can be connected to the communication network 2 as long as it is within the communication range of the mobile communication network. The in-vehicle display 7 is connected to the vehicle-side system 4.
[0012] When the user is outside the vehicle cabin and within the communication range of the mobile communication network, the user can perform procedures related to the rewriting of the application program by making operational inputs while checking various screens related to the rewriting of the application program on the mobile terminal 6. When the user is inside the vehicle cabin, the user can perform procedures related to the rewriting of the application program by making operational inputs while checking various screens related to the rewriting of the application program on the in-vehicle display 7. In other words, the user can perform procedures related to the rewriting of the application program by selectively using the mobile terminal 6 and the in-vehicle display 7 outside and inside the vehicle cabin.
[0013] The center device 3 controls the OTA functions on the communication network 2 side in the vehicle program rewriting system 1 and functions as an OTA center. The center device 3 has a file server 8, a web server 9, and a management server 10, and the servers 8 to 10 are configured to be able to communicate data with each other.
[0014] The file server 8 has a function for managing application programs transmitted from the center device 3 to the vehicle-side system 4, and is a server that manages ECU programs and associated information provided by suppliers or other providers of application programs, distribution specification data provided by OEMs (Original Equipment Manufacturers), vehicle status information acquired from the vehicle-side system 4, and the like. The file server 8 is capable of data communication with the vehicle-side system 4 via the communication network 2, and when a request for downloading a distribution package is made, it transmits a distribution package that packages reprogramming data and distribution specification data to the vehicle-side system 4. The web server 9 is a server that manages web information, and provides various screens related to rewriting application programs to the mobile terminal 6. The management server 10 manages personal information, etc. of users registered for the application program rewriting service, and manages the rewrite history of application programs for each vehicle.
[0015] The vehicle-side system 4 has a master device 11. The master device 11 has a DCM 12 and a CGW 13, which are connected to each other so as to be able to perform data communications via a first bus 14. The DCM 12 is an in-vehicle communication device that performs data communications with the center device 3 via the communication network 2, and upon downloading a distribution package from the file server 8, extracts write data from the distribution package and transfers it to the CGW 13.
[0016] The CGW 13 is a vehicle gateway device with a data relay function, and upon receiving write data from the DCM 12, distributes the write data to the target ECU for rewriting the application program. The master device 11 controls the vehicle-side OTA functions in the vehicle program rewriting system 1 and functions as an OTA master. Note that while FIG. 1 illustrates a configuration in which the DCM 12 and the in-vehicle display 7 are connected to the same first bus 14, the DCM 12 and the in-vehicle display 7 may be connected to separate buses.
[0017] In addition to the first bus 14, the second bus 15, the third bus 16, the fourth bus 17, and the fifth bus 18 are connected to the CGW 13 as buses inside the vehicle, and various ECUs 19 are connected via buses 15 to 17, and a power management ECU 20 is connected via bus 18.
[0018] The second bus 15 is, for example, a bus for a body system network. The ECUs 19 connected to the second bus 15 are ECUs that control body systems, such as a door ECU that controls door locking / unlocking, a meter ECU that controls meter displays, an air conditioner ECU that controls air conditioner operation, and a window ECU that controls window opening and closing. The third bus 16 is, for example, a bus for a driving system network. The ECUs 19 connected to the third bus 16 are ECUs that control driving systems, such as an engine ECU that controls engine operation, a brake ECU that controls brake operation, an ECT (Electronic Toll Collection System, registered trademark) ECU that controls automatic transmission operation, and a power steering ECU that controls power steering operation.
[0019] The fourth bus 17 is, for example, a bus for a multimedia network. The ECU 19 connected to the fourth bus 17 is, for example, an ECU that controls a multimedia system, such as a navigation ECU for controlling a navigation system, or an ETC ECU for controlling an electronic toll collection system (ECT system). The buses 15 to 17 may be buses of a system other than a body system network bus, a driving system network bus, or a multimedia system network bus. Furthermore, the number of buses and the number of ECUs 19 are not limited to the configuration illustrated.
[0020] The power supply management ECU 20 is an ECU that has a function of managing the power supplies of the DCM 12, the CGW 13, the various ECUs 19, and the like.
[0021] A sixth bus 21 is connected to the CGW 13 as a bus outside the vehicle. A DLC (Data Link Coupler) connector 22 to which a tool 23 is detachably connected is connected to the sixth bus 21. The buses 14 to 18 inside the vehicle and the bus 21 outside the vehicle are configured, for example, by a CAN (Controller Area Network, registered trademark) bus, and the CGW 13 performs data communication between the DCM 12, various ECUs 19, and the tool 23 in accordance with the CAN data communication standard and the diagnostic communication standard (UDS: ISO14229). Note that the DCM 12 and CGW 13 may be connected via Ethernet, and the DLC connector 22 and CGW 13 may be connected via Ethernet.
[0022] When the rewrite target ECU 19 receives the write data from the CGW 13, it writes the write data to its flash memory to rewrite the application program. In the above configuration, when the CGW 13 receives a request to obtain write data from the rewrite target ECU 19, it functions as a reprogram master that distributes the write data to the rewrite target ECU 19. When the rewrite target ECU 19 receives the write data from the CGW 13, it functions as a reprogram slave that writes the write data to its flash memory to rewrite the application program.
[0023] There are two modes for rewriting an application program: a wired rewriting mode and a wireless rewriting mode. In the wired rewriting mode, when the tool 23 is connected to the DLC connector 22, the tool 23 transfers write data to the CGW 13. The CGW 13 relays or distributes the write data transferred from the tool 23 to the rewriting target ECU 19. In the wireless rewriting mode for an application program, as described above, when the DCM 12 downloads a distribution package from the file server 8, it extracts write data from the distribution package and transfers the write data to the CGW 13.
[0024] 2, the CGW 13 has, as electrical functional blocks, a microcomputer (hereinafter referred to as "mc") 24, a data transfer circuit 25, a power supply circuit 26, and a power supply detection circuit 27. The mc 24 has a CPU (Central Processing Unit) 24a, a ROM (Read Only Memory) 24b, a RAM (Random Access Memory) 24c, and a flash memory 24d. The mc 24 executes various control programs stored in a non-transitory physical storage medium to perform various processes and control the operation of the CGW 13.
[0025] The data transfer circuit 25 controls data communication between the buses 14 to 18, 21 in accordance with the CAN data communication standard and the diagnostic communication standard. The power supply circuit 26 receives inputs of a battery power supply (hereinafter referred to as the +B power supply), an accessory power supply (hereinafter referred to as the ACC power supply), and an ignition power supply (hereinafter referred to as the IG power supply). The power supply detection circuit 27 detects the voltage values of the +B power supply, the ACC power supply, and the IG power supply input by the power supply circuit 26, compares these detected voltage values with predetermined voltage thresholds, and outputs the comparison results to the microcomputer 24. Based on the comparison results input from the power supply detection circuit 27, the microcomputer 24 determines whether the +B power supply, the ACC power supply, and the IG power supply supplied from the outside to the CGW 13 are normal or abnormal.
[0026] 3, the ECU 19 has, as electrical functional blocks, a microcomputer 28, a data transfer circuit 29, a power supply circuit 30, and a power supply detection circuit 31. The microcomputer 28 has a CPU 28a, a ROM 28b, a RAM 28c, and a flash memory 28d. The microcomputer 28 executes various control programs stored in a non-transitory physical storage medium to perform various processes and control the operation of the ECU 19.
[0027] The data transfer circuit 29 controls data communication between the buses 15 to 17 in accordance with the CAN data communication standard. The power supply circuit 30 receives inputs of the +B power supply, the ACC power supply, and the IG power supply. The power supply detection circuit 31 detects the voltage values of the +B power supply, the ACC power supply, and the IG power supply input by the power supply circuit 30, compares these detected voltage values with predetermined voltage thresholds, and outputs the comparison result to the microcomputer 28. The microcomputer 28 determines whether the +B power supply, the ACC power supply, and the IG power supply supplied from the outside to the ECU 19 are normal or abnormal based on the comparison result input from the power supply detection circuit 27. The ECU 19 has a fundamentally similar configuration, although the connected loads, such as sensors and actuators, are different. The DCM 12, the in-vehicle display 7, and the power management ECU also have the same basic configuration as the ECU 19 shown in FIG. 3.
[0028] As shown in Fig. 4, the power management ECU 20, CGW 13, and ECU 19 are connected to a +B power line 32, an ACC power line 33, and an IG power line 34. The +B power line 32 is connected to the positive electrode of a vehicle battery 35. The ACC power line 33 is connected to the positive electrode of the vehicle battery 35 via an ACC switch 36. When a user performs an ACC operation, the ACC switch 36 is switched from OFF to ON, and the output voltage of the vehicle battery 35 is applied to the ACC power line 33. For example, in a vehicle in which the key is inserted into a socket, the ACC operation is an operation of inserting the key into the socket and turning it from the "OFF" position to the "ACC" position, or in a vehicle in which the start button is pressed, an operation of pressing the start button once.
[0029] The IG power line 34 is connected to the positive terminal of the vehicle battery 35 via an IG switch 37. When the user performs an IG operation, the IG switch 37 switches from OFF to ON, and the output voltage of the vehicle battery 35 is applied to the IG power line 34. For example, in a vehicle where the key is inserted into a socket, the IG operation is an operation of inserting the key into the socket and turning it from the "OFF" position to the "ON" position, or in a vehicle where the start button is pressed, an operation of pressing the start button twice. The negative terminal of the vehicle battery 35 is grounded.
[0030] When both the ACC switch 36 and the IG switch 37 are off, only the +B power is supplied to the vehicle-side system 4. The state in which only the +B power is supplied to the vehicle-side system 4 is referred to as the +B power state. When the ACC switch 36 is on and the IG switch 37 is off, the ACC power and the +B power are supplied to the vehicle-side system 4. The state in which the ACC power and the +B power are supplied to the vehicle-side system 4 is referred to as the ACC power state. When both the ACC switch 36 and the IG switch 37 are on, the +B power, the ACC power, and the IG power are supplied to the vehicle-side system 4. The state in which the +B power, the ACC power, and the IG power are supplied to the vehicle-side system 4 is referred to as the IG power state.
[0031] The ECU 19 has different activation conditions depending on the power supply state, and is classified into +B system ECUs that activate in the +B power supply state, ACC system ECUs that activate in the ACC power supply state, and IG system ECUs that activate in the IG power supply state. For example, an ECU 19 that operates for purposes such as vehicle theft is a +B system ECU. An ECU 19 that operates for non-driving purposes such as audio is an ACC system ECU. An ECU 19 that operates for driving purposes such as engine control is an IG system ECU.
[0032] The CGW 13 transmits a wake-up request to an ECU 19 in a sleep state, thereby causing the ECU 19 to which the wake-up request is sent to transition from the sleep state to the wake-up state. The CGW 13 also transmits a sleep request to an ECU 19 in an wake-up state, thereby causing the ECU 19 to which the sleep request is sent to transition from the wake-up state to the sleep state. The CGW 13 selects the ECU 19 to which the wake-up request or sleep request is sent from among a plurality of ECUs, for example, by varying the waveform of the transmission signal sent to the buses 15 to 17.
[0033] A power supply control circuit 38 is connected in parallel to the ACC switch 36 and the IG switch 37. The CGW 13 transmits a power supply control request to the power supply management ECU 20, causing the power supply management ECU 20 to control the power supply control circuit 38. That is, the CGW 13 transmits a power supply start request as a power supply control request to the power supply management ECU 20, causing the ACC power line 33 and the IG power line 34 to be connected to the positive terminal of the vehicle battery 35 inside the power supply control circuit 38. In this state, even if the ACC switch 36 and the IG switch 37 are off, the ACC power and the IG power are supplied to the vehicle-side system 4. The CGW 13 transmits a power supply stop request as a power supply control request to the power supply management ECU 20, causing the ACC power line 33, the IG power line 34, and the positive terminal of the vehicle battery 35 to be disconnected inside the power supply control circuit 38.
[0034] The DCM 12, CGW 13, and ECU 19 have a power supply self-maintenance function. That is, when the vehicle power supply switches from the ACC power supply or the IG power supply to the +B power supply while the DCM 12, CGW 13, and ECU 19 are in an activated state, they do not immediately transition from the activated state to a sleep state or a stopped state after the switch, but rather continue to remain in the activated state for a predetermined time even after the switch, thereby self-maintaining the drive power supply. The DCM 12, CGW 13, and ECU 19 transition from the activated state to a sleep state or a stopped state after a predetermined time (e.g., several seconds) has elapsed since the vehicle power supply switched from the ACC power supply or the IG power supply to the +B power supply.
[0035] Next, the distribution package distributed from the center device 3 to the master device 11 will be described with reference to FIGS. 5 and 6. In the vehicle program rewriting system 1, reprogramming data is generated from programming data provided by a supplier, which is a provider of an application program, and reprogramming specification data provided primarily by the OEM. The programming data provided by the supplier includes differential data corresponding to the difference between the old application program and the new application program, and all data corresponding to the entire new application program. The differential data and all data may be compressed using well-known data compression techniques. FIG. 5 illustrates an example in which differential data is provided as programming data from suppliers A to C, and reprogramming data is generated from the encrypted differential data and authenticator for the ECU (ID1) provided by supplier A, the encrypted differential data and authenticator for the ECU (ID2) provided by supplier B, the encrypted differential data and authenticator for the ECU (ID3) provided by supplier C, and the reprogramming specification data provided by the OEM. An authenticator is assigned to each programming data.
[0036] 5 shows the difference data when updating from the old application program to the new application program, the reprogram data may also include rollback difference data for rewriting from the new application program to the old application program. For example, if the ECU 19 to be rewritten has a single memory, the rollback difference data may be included in the reprogram data.
[0037] The rewrite specification data provided by the OEM includes information related to the rewrite of the application program, such as information for identifying the ECU 19 to be rewritten, information for identifying the rewrite order when there are multiple ECUs 19 to be rewritten, and information for identifying a rollback method (described later), and defines operations related to the rewrite in the DCM 12, CGW 13, and ECU 19 to be rewritten. The rewrite specification data is divided into DCM rewrite specification data used by the DCM 12 and CGW rewrite specification data used by the CGW 13. The DCM rewrite specification data contains information necessary for reading files corresponding to the ECU 19 to be rewritten. The CGW rewrite specification data contains information necessary for controlling the rewrite in the ECU 19 to be rewritten, as described above.
[0038] When the DCM 12 acquires the rewrite specification data for the DCM, it analyzes the rewrite specification data for the DCM and, according to the analysis results, controls operations related to rewriting, such as transferring write data to the CGW 13. When the CGW 13 acquires the rewrite specification data for the CGW, it analyzes the rewrite specification data for the CGW and, according to the analysis results, controls operations related to rewriting, such as acquiring write data from the DCM 12 and distributing the write data to the ECU 19 to be rewritten.
[0039] The file server 8 registers the above-mentioned re-log data as well as distribution specification data provided by the OEM. The distribution specification data provided by the OEM is data that defines operations related to the display of various screens on the display terminal 5.
[0040] When the relog data and distribution specification data are registered, the file server 8 encrypts the relog data and generates a distribution package that packages the encrypted relog data, distribution specification data, a package authenticator for authenticating the package, and a single file. When the file server 8 receives a download request for a distribution package from an external device, it transmits the distribution package to the DCM 12. While FIG. 5 illustrates an example in which the file server 8 generates a distribution package that stores the relog data and distribution specification data and transmits the relog data and distribution specification data simultaneously to the DCM 12, the relog data and distribution specification data may be transmitted separately to the DCM 12. That is, the file server 8 may transmit the distribution specification data to the DCM 12 first, and then transmit the relog data to the DCM 12 later. Alternatively, the file server 8 may combine the relog data and distribution specification data into a single file, which is a distribution package, and transmit the distribution package and package authenticator to the DCM 12.
[0041] When the DCM 12 downloads a distribution package from the file server 8, it verifies the package authenticator stored in the distribution package against the encrypted reprogram data, and if the verification result is positive, it decrypts the encrypted reprogram data. After decrypting the encrypted reprogram data, the DCM 12 unpackages the decrypted reprogram data to generate encrypted difference data and authenticators for each ECU, reprogram specification data for the DCM, and reprogram specification data for the CGW. Figure 6 illustrates an example in which encrypted difference data and authenticators for ECU (ID1), encrypted difference data and authenticators for ECU (ID2), and encrypted difference data and authenticators for ECU (ID3), and reprogram specification data are generated.
[0042] FIG. 7 is a block diagram showing the parts of the center device 3 that are mainly related to the functions of the servers 8 to 10. FIG. 8 shows an overview of the processing performed by the center device 3 regarding ECU program updates. Note that hereinafter, "database" may be abbreviated as "DB." As shown in FIG. 7, the center device 3 includes a package management unit 3A, a configuration information management unit 3B, an individual vehicle information management unit 3C, and a campaign management unit 3D. The package management unit 3A includes a specification data generation unit 201, a package generation unit 202, and a package distribution unit 203, as well as an ECU repro data DB 204, an ECU metadata DB 205, and a package DB 206. The configuration information management unit 3B includes a configuration information registration unit 207 and a configuration information DB 208.
[0043] The supplier registers ECU-specific data using the input unit 218 and display unit 219, which are user interface (UI) functions of the management server 10. The ECU-specific data includes program files such as new programs and difference data, program file-related information such as verification data, size, and encryption method of the program files, and ECU attribute information such as the memory structure of the ECU 19. The program files are stored in the ECU repro data DB 204. The ECU attribute information is stored in the ECU metadata DB 205. The program file-related information may be stored in the ECU repro data DB 204 or the ECU metadata DB 205. The ECU repro data DB 204 is an example of an update data storage unit. The ECU metadata DB 205 is an example of a device-related information storage unit.
[0044] The OEM registers the official configuration information for each vehicle model in the configuration information DB 208 via the configuration information registration unit 207. Official configuration information is vehicle configuration information approved by a public institution. The configuration information is identification information related to the hardware and software of the ECU 19 installed in the vehicle and is an example of vehicle-related information. The configuration information also includes identification information for a system configuration consisting of multiple ECUs 19 and identification information for a vehicle configuration consisting of multiple systems. Vehicle constraint information related to program updates may also be registered as configuration information. For example, ECU group information, bus load table, information related to battery load, etc., which are written in the rewrite specification data, may also be registered. The ECU metadata DB 205 is an example of a device-related information storage unit. The configuration information DB 208 is an example of a vehicle information storage unit.
[0045] The specification data generation unit 201 references each DB and generates rewritten specification data. The package generation unit 202 generates a distribution package including the rewritten specification data and reprogrammed data, and registers it in the package DB 206. The package generation unit 202 may generate a distribution package including the distribution specification data. The package distribution unit 203 distributes the registered distribution package to the vehicle-side system 4. The distribution package corresponds to a file.
[0046] The individual vehicle information management unit 3C includes an individual vehicle information registration unit 209, a configuration information confirmation unit 210, an update confirmation unit 211, an SMS transmission control unit 212, and an individual vehicle information DB 213. The individual vehicle information registration unit 209 registers individual vehicle information uploaded from each vehicle in the individual vehicle information DB 213. The individual vehicle information registration unit 209 may register individual vehicle information at the time of vehicle production or sales as the initial value in the individual vehicle information DB 213. When registering the uploaded individual vehicle information, the configuration information confirmation unit 210 compares the individual vehicle information with the configuration information of the same model vehicle registered in the configuration information DB 208. The update confirmation unit 211 checks whether the individual vehicle information has been updated with a new program, i.e., whether there is a campaign. If the individual vehicle information has been updated, the SMS transmission control unit 212 sends a message regarding the update to the corresponding vehicle via SMS (Short Message Service).
[0047] The campaign management unit 3D includes a campaign generation unit 214, a campaign distribution unit 215, an instruction notification unit 216, and a campaign DB 217. The OEM generates campaign information, which is information related to program updates, using the campaign generation unit 214 and registers it in the campaign DB 217. The campaign information here corresponds to the aforementioned "distribution specification data" and is mainly information related to the update contents to be displayed on the vehicle-side system 4. The campaign distribution unit 215 distributes the campaign information to the vehicle. The instruction notification unit 216 notifies the vehicle of necessary instructions related to the program update. In the vehicle-side system 4, based on the campaign information transmitted from the center device 3, for example, the user determines whether to download the update program, and if necessary, the download is performed. The functions of the management units 3A to 3D, excluding the databases, are realized by computer hardware and software. The vehicle communication unit 222 is a functional block for wirelessly communicating data between the center device 3 and the vehicle-side system 4.
[0048] The above processing will be explained in more detail below, but first the contents of the data registered in each database will be explained. As shown in FIG. 9, the following data is registered in the configuration information DB 208 as an example. "Vehicle model" indicates the vehicle model. "Vehicle SW ID" is a software ID for the entire vehicle, and corresponds to the vehicle software ID. Only one "Vehicle SW ID" is assigned to each vehicle, and is updated whenever the version of the application program for one or more ECUs is updated. "Sys ID" is the ID of a system, assuming that a group of multiple ECUs 19 installed in each vehicle is called a "system."
[0049] For example, in FIG. 1, the group of body ECUs 19 is the body system, and the group of driving system ECUs 19 is the driving system. The "Sys ID" is updated whenever the version of the application program of one or more ECUs constituting the system is updated. The "ECU ID" is an ID for device identification indicating the type of each ECU. The "ECU SW ID" is a software ID for each ECU, equivalent to the ECU software ID. For convenience, the "ECU ID" is shown here with the software version added. The "ECU SW ID" is updated whenever the version of the application program of the ECU is updated. Furthermore, even if the "ECU ID" and program version are the same, different "ECU SW IDs" are used if the hardware configuration is different. In other words, the "ECU SW ID" is also information indicating the ECU's product number.
[0050] 9 shows configuration information for a vehicle with "vehicle model" = "aaa." Of the ECUs 19 installed in the vehicle, the following are shown as examples: an autonomous driving ECU (ADS), an engine ECU (ENG), a brake ECU (BRK), and an electric power steering ECU (EPS). For example, the "ECU SW IDs" for "Vehicle SW ID" = "0001" are "ads_001," "eng_010," "brk_001," and "eps_010," whereas the "ECU SW IDs" for "Vehicle SW ID" = "0002" are "ads_002," "eng_010," "brk_005," and "eps_011," resulting in three software version updates. Accordingly, "Sys ID" = "SA01" is updated to "SA02," and "Sys ID" = "SA02" is updated to "SA03." In this way, initial values are registered in the configuration information DB 208 at the time of vehicle production or sales, and are subsequently updated whenever the version of the application program of one or more ECUs is updated. In other words, the configuration information DB 208 indicates the configuration information that is officially available on the market for each vehicle model.
[0051] As shown in FIG. 10, the ECU repro data DB 204 registers the following programs and data as examples. FIG. 10 illustrates an autonomous driving ECU (ADS), a brake ECU (BRK), and an electric power steering ECU (EPS) as examples of ECUs 19 installed in a certain vehicle model whose application programs are to be updated. For the latest "ECU SW ID" of each of these ECUs 19 to be updated, the following data is registered: the ECU's old program and new program files, integrity verification data for the new program, an update data file that is differential data between the new program and the old program, integrity verification data for the update data, a rollback data file that is also differential data, and integrity verification data for the rollback data. The integrity verification data is a hash value obtained by applying a hash function to the data value. When the update data is replaced with the differential data and replaced with all the data of the new program, the integrity verification data for the update data becomes equal to the same data for the new program.
[0052] 10 shows the data structure for the latest "ECU SW ID", but if data for an older "ECU SW ID" is stored, the old program file may be configured to refer to the new program file for the "ECU SW ID" that is one step older. Also, each integrity verification data may be in a format in which a value calculated by the supplier is registered, or in which the center device 3 calculates and registers the value.
[0053] 11, the ECU metadata DB 205 stores the following ECU-specific specification data, for example: For the latest "ECU SW ID," the size of the update data file, the size of the rollback data file, if the flash memory 28d provided in the ECU 19 has two or more planes, the side information indicating which side the program is for (side A, side B, side C, etc.), the transfer size, the read address of the program file, etc. These are examples of update data-related information.
[0054] The ECU metadata DB 205 also registers attribute information indicating the attributes of the ECU 19. The attribute information is information indicating the hardware attributes and software attributes of the ECU. The "transfer size" is the transfer size when rewrite data is divided and transferred from the CGW 13 to the ECU 19, and the "key" is the key used by the CGW 13 to securely access the ECU 19. These are examples of software attribute information. The "vehicle model" and "ECU ID" also include the memory configuration of the flash memory 28d provided in the ECU 19, the type of bus to which the ECU 19 is connected, the type of power supply connected to the ECU 19, and the like. These are examples of hardware attribute information.
[0055] Here, the memory configuration "1 side" is a single-side standalone memory having one flash side, "2 side" is a dual-side memory having two flash sides, and "suspend" is a single-side suspend memory having two pseudo-flash sides. The hardware attribute information and software attribute information are information used to control the rewriting of each ECU 19 in the vehicle-side system 4. Although the hardware attribute information can be stored in advance by the CGW 13, in this embodiment, it is managed by the center device 3 to reduce the management load on the vehicle-side system 4. Furthermore, the software attribute information is data that directly specifies the rewriting operation of each ECU 19. It is managed by the center device 3 to enable flexible control in the vehicle-side system 4.
[0056] As shown in FIG. 12, the individual vehicle information DB 213 registers the following data for each individual vehicle, for example. Mainly, configuration information for each individual vehicle and status information for each individual vehicle regarding program updates are registered. Specifically, for the "VIN" which is the ID of each vehicle, configuration information such as "Vehicle SW ID," "Sys ID," "ECU ID," and "ECU SW ID" are registered. "Digest" values, which are hash values for this configuration information, are also calculated and stored by the center device 3. When the memory configuration is two-sided, the "operational side" is the side on which the program currently being operated by the ECU 19 is written, and values uploaded together with the configuration information are registered.
[0057] The "access log" is the date and time when the vehicle uploaded the individual vehicle information to the center device 3. The "reprogramming status" indicates the status of the reprogramming in the vehicle, such as "campaign issued," "activation completed," and "download completed." In other words, this progress status indicates to what phase the reprogramming in the vehicle has progressed and in what phase it is stagnating. When configuration information, etc. is uploaded from the vehicle-side system 4 to the center device 3, the "VIN" of each vehicle is attached to the information, etc.
[0058] As shown in FIG. 13, the package DB 206 registers distribution package IDs, distribution package files, and data for verifying the integrity of the distribution packages. As shown in Fig. 14, the following data is registered in the campaign DB 217: campaign information ID, distribution package ID, message information such as text indicating specific update contents as campaign contents, a list of "VIN" which is the ID of the vehicle that is the target of the campaign, "Vehicle SW ID" before and after the update, a list of "ECU SW ID" before and after the update, etc. The "target VIN" list can be registered by comparing the individual vehicle information DB 213 and the campaign DB 217. Note that this campaign information may also be registered together with the package DB 206.
[0059] Next, the operation of this embodiment will be described. Referring to FIG. 15, the process of registering the ECU repro data DB 204 in the package management unit 3A will be described. As shown in FIG. 15, the display unit 219 and input unit 218 launch a screen for registering repro data in the management server 10, and receive input of old and new program files for the ECU 19 from a supplier's worker (A1). For example, a UI or the like may be used that registers a file containing configuration information in CSV format or the like. Next, the package management unit 3A generates integrity verification data for the new program (A2), and generates a difference data file and integrity verification data for the update difference data as update difference data when updating to a new program based on the old program (A3, A4).
[0060] Next, a differential data file for updating the old program based on the new program is generated as differential data for rollback, along with integrity verification data for that data (A5, A6). These program files and verification data are registered in the ECU repro data DB 204, and a new "ECU SW ID" is generated and registered based on the previous "ECU SW ID" (A7). If all data is distributed instead of just the differences, the steps related to the differential data can be omitted.
[0061] The integrity verification data is, for example, a hash value generated by applying a hash function. For example, if SHA-256 (Secure Hash Algorithm 256-bit) is used as the hash function, the data value is divided into message blocks of 64 bytes each. Then, the data value of the first message block is applied to the initial hash value to obtain a 32-byte hash value. The data value of the next message block is then applied to this hash value, and similar 32-byte hash values are obtained, and this process is repeated sequentially.
[0062] 16, a description will be given of the process of generating rewritten specification data in specification data generating unit 201. Here, the process of generating rewritten specification data for a vehicle with "vehicle model"="aaa" will be described, but the process is similar for other vehicles. The center device 3 starts the specification data generation program of the specification data generation unit 201 and receives input from the OEM worker via the display unit 219 and the input unit 218. First, the specification data generation unit 201 determines the ECU 19 to be updated. As shown in FIG. 16 , the specification data generation unit 201 accesses the ECU repro data DB 204 and outputs to the display unit 219 a display screen that allows the user to select an ECU SW ID to be updated from among the registered ECU SW IDs. The specification data generation unit 201 stores one or more ECU SW IDs selected by the OEM worker via the input unit 218 in a specific ECU order (B1). Here, the ECU order indicates the rewrite order of the ECUs 19 in the vehicle-side system 4. The specification data generation unit 201 sets the order specified by the OEM worker as the specific ECU order.
[0063] Furthermore, the specification data generation unit 201 may access the configuration information DB 208 and determine the ECU 19 to be updated without receiving input from an OEM worker. The specification data generation unit 201 references the "ECU SW ID" for the latest "Vehicle SW ID" and the "ECU SW ID" for the immediately older "Vehicle SW ID" to extract the ECU 19 that has been updated. For example, in FIG. 9, "ADS," "BRK," and "EPS" are the ECUs 19 to be updated. The specification data generation unit 201 sets the order registered in the configuration information DB 208 as the specific ECU order.
[0064] Then, the specification data generation unit 201 generates group information for ECUs having multiple "ECU SW IDs" to be updated (B2). Here, the configuration information DB 208 is referenced, and "Sys ID" is used. For example, group 1 is grouped by "ECU ID" whose "Sys ID" is "SA01_02," and group 2 is grouped by "ECU ID" whose "Sys ID" is "SA02_02." For example, in FIG. 9, group 1 is set to "ADS," and the first in group 2 is set to "BRK," and the second is set to "EPS." In this way, the specification data generation unit 201 determines the ECUs to be updated, the groups to which the ECUs belong, and the order of the ECUs within the groups.
[0065] Next, the specification data generation unit 201 accesses the ECU metadata DB 205 to acquire update data-related information, hardware attribute information, and software attribute information as specification data related to the ECU 19 to be updated (B3). For example, as shown in FIG. 17, the update data-related information includes "update program version," "update program acquisition address," "update program size," "rollback program version," "rollback program acquisition address," "rollback program size," "write data type," and "write surface." The hardware attribute information includes "connection bus," "connected power supply," and "memory type." The software attribute information includes "rewrite surface information," "security access key information," "rewrite method," and "transfer size." The "rewrite method" indicates whether rewrite is performed with the power supply self-holding circuit enabled when the IG is switched from on to off (power supply self-holding), or whether rewrite is performed according to the IG on and IG off states (power supply control). The "security access key information" may include information other than a key.
[0066] Each piece of information will be explained below. "Write data type" indicates whether the program is differential data or all data. The write data type for the update program and the write data type for the rollback program may be written separately. The "write side" is information indicating to which side of the dual-sided memory the program is to be written to the ECU 19. "Connection bus" is information for identifying the bus to which the ECU 19 is connected. "Connected power source" is information indicating the power source state to which the ECU 19 is connected, and a value indicating one of the battery power source (+B power source), accessory power source (ACC power source), and ignition power source (IG power source) is recorded. "Memory type" is information for identifying the memory configuration of the ECU 19, and a value indicating a dual-plane memory, a single-plane suspend-type memory (pseudo dual-plane memory), a single-plane memory, etc. is recorded. The "rewrite surface information" is information indicating which surface of the ECU 19 is the startup surface (operational surface) and which surface is the rewrite surface (non-operational surface). "Security access key information" is information for authenticating access to the ECU 19 using a key, and includes information on a key derivation key, a key pattern, and a decryption operation pattern. "Transfer size" is the data size when the program is divided and transferred to the ECU 19.
[0067] As shown in FIG. 17, for example, this information is stored in the specific ECU order described above, using "ECU ID" as a key. After acquiring information for all ECUs (B4; YES), the specification data generation unit 201 specifies "reprogramming environment information" for the vehicle to be updated (B5). "Reprogramming environment information" is information used for reprogramming control in the vehicle-side system 4 for a group of ECUs or the entire vehicle, and is data that directly specifies the reprogramming operation. For example, examples of reprogramming environment information for the entire vehicle include "vehicle state" indicating whether the program update in the vehicle-side system 4 is performed while the vehicle is running (IG switch is on) or while the vehicle is parked (IG switch is off), "battery load (remaining battery capacity)" indicating the constraints on the remaining battery capacity that allows the program update in the vehicle-side system 4 to be performed, and bus load table information indicating the constraints on the bus load that allows the vehicle-side system 4 to transfer write data.
[0068] The rewriting environment information for a group includes the ECUs 19 belonging to the group and the order of the ECUs within the group. The vehicle-side system 4 controls program updates so that they are synchronized on a group-by-group basis, and writes the information to the ECUs 19 in the specified ECU order. The specification data generation unit 201 starts a screen for registering rewriting environment information and receives input from an OEM worker. Alternatively, the rewriting environment information may be imported from Excel (registered trademark). Alternatively, the specification data generation unit 201 may extract constraint information registered in the configuration information DB 208. The specification data generation unit 201 uses the results of generation in step B2 described above as the rewriting environment information for a group.
[0069] The bus load table is a table showing the correspondence between the power supply state and the bus transmission capacity. As shown in FIG. 18, the transmission capacity is the sum of the transmission capacity of vehicle control data and write data that can be transmitted relative to the maximum transmission capacity. In this example, since the transmission capacity for the first bus is 80% of the maximum transmission capacity, the CGW 13 allows 50% of the maximum transmission capacity for vehicle control data and 30% of the maximum transmission capacity for write data in the IG power supply state. Furthermore, the CGW 13 allows 30% of the maximum transmission capacity for vehicle control data and 50% of the maximum transmission capacity for write data in the ACC power supply state. Furthermore, the CGW 13 allows 20% of the maximum transmission capacity for vehicle control data and 60% of the maximum transmission capacity for write data in the +B power supply state. The same applies to the second and third buses.
[0070] Finally, the specification data generation unit 201 arranges the generated or acquired data in a predetermined data structure to generate rewritten specification data as shown in FIG. 17 (B6). That is, the specification data generation unit 201 generates rewritten specification data in a data structure that can be interpreted by the vehicle-side system 4. It is advisable to write the ECU information for each ECU in the rewritten specification data in order of the youngest group and in the order of the ECUs within the group. For example, in FIG. 9, if group 1 is "ADS" and group 2 has the first ECU "BRK" and the second ECU "EPS," the ECU information column of the specification data will list the ECU information for "ADS" first, then the ECU information for "BRK," and finally the ECU information for "EPS."
[0071] In the specification data shown in FIG. 17, the ECU information "ECU ID" to "Transfer Size" are an example of target device related information including the type of target ECU 19, and correspond to the hardware attribute information and software attribute information described above. Also, "Update Program Version" to "Writing Side" are an example of update data related information. Also, the "Rewrite Environment" for a group of ECUs or the entire vehicle is an example of update process information that specifies the update process in the vehicle.
[0072] FIG. 19 illustrates the package generation process in the package generation unit 202. As described above, the package generation process for a vehicle with "vehicle model" = "aaa" will be described here. As shown in FIG. 19, the center device 3 starts the package generation unit 202 of the package management unit 3A in response to an instruction from an operator. The package generation unit 202 determines the "ECU SW ID" to be updated, as in step B1 (C1). The package generation unit 202 acquires each piece of data corresponding to the "ECU SW ID" to be updated from the ECU reprogram data DB 204 and generates one piece of reprogram data (C2). For example, in FIG. 10, the package generation unit 201 acquires the integrity verification data of the new program, the update data which is the difference data, the integrity verification data of the update data, the integrity verification data of the old program, the rollback data which is the difference data, and the integrity verification data of the rollback data, and generates the reprogram data. Then, the generated reprogram data and the corresponding rewrite specification data described in steps B1 to B6 are integrated to generate a single distribution package file (C3). Next, integrity verification data for the generated package file is generated (C4), and is registered together with the package file in package DB 206 (C5).
[0073] Figure 20 shows an image of the contents of the package file generated as described above. The update data and integrity verification data corresponding to the "ADS," "BRK," and "EPS" to be updated are integrated into one reprogramming data in ECU order, and then integrated with the reprogramming specification data to generate one distribution package file. Here, rollback data may be included in the reprogramming data only if the memory configuration of the ECU 19 to be updated is one plane. If the memory configuration is two planes or suspended, rewriting of the operational plane is not performed, so the rollback data, which is the old program, can be omitted.
[0074] As described above, according to this embodiment, the ECU repro data DB 204 of the center device 3 stores data on update programs for ECUs 19, among the multiple ECUs 19 mounted on a vehicle, whose application programs are to be updated. The configuration information DB 208 stores vehicle-related information, such as the "ECU ID" for each of the multiple ECUs 19 mounted on the vehicle and the "ECU SW ID" of the application programs stored in the ECUs 19, along with the vehicle type. The ECU metadata DB 205 stores update data-related information relating to the attributes and update data of the ECUs 19 to be rewritten.
[0075] The specification data generation unit 201 then generates specification data to be transmitted to the vehicle together with the update data to be written to the target ECU 19, based on the information stored in the configuration information DB 208 and the ECU metadata DB 205, so that the specification data includes the type, attributes, update data-related information, and information indicating the rewriting environment for the data update for the target ECU 19. Furthermore, the package generation unit 202 generates a distribution package including the specification data and reprogramming data, and registers the package in the package DB 206. The package distribution unit 203 then distributes the registered distribution package to the vehicle-side system 4. As a result, by receiving the specification data transmitted together with the update data, the vehicle-side system 4 can appropriately select the target ECU 19 based on the specification data and appropriately control the writing process using the update data.
[0076] The specification data generation unit 201 generates specification data for multiple ECUs 19 as a single file, and the package generation unit 202 further packages this together with reprogramming data for multiple ECUs 19 as a single file, so that the vehicle-side system 4 can write update data to multiple ECUs 19 by receiving a single distribution package.
[0077] Furthermore, the vehicle-related information as specification data includes group information that groups some of the multiple ECUs 19, so the vehicle-side system 4 can select the target ECUs 19 in the order defined by the group information and write the update data to them. For example, if there are many ECUs 19 that are the target of a certain function improvement, the vehicle-side system 4 can execute the program update in three batches by assigning group 1 to the body-related ECUs 19, group 2 to the driving-related ECUs 19, and group 3 to the MM-related ECUs 19. This reduces the user's waiting time for each update compared to when the program update is executed for all ECUs at once.
[0078] Furthermore, the rewriting environment information includes the "vehicle state (IG on state)" and "battery load" related to the vehicle, and the "bus load table" related to the ECU 19, so the vehicle-side system 4 can determine the timing of writing update data based on this information. In other words, the OEM or a service provider using the center device 3 can operate a flexible program update by specifying execution constraint conditions for the vehicle as the rewriting environment information.
[0079] In addition, the specification data generator 201 generates specification data according to a predetermined data structure, starting with information about the ECU 19 with the earliest predefined rewrite order. This allows the vehicle-side system 4 to write update data according to the arrangement order of the ECU IDs in the specification data. In other words, by grouping ECUs 19 that have mutually linked processes into one group and defining the ECU order in consideration of the content of the linked processes, the vehicle-side system 4 can complete the program update without any problems even if the update timing to the new program is not perfectly synchronized. For example, if the new program for ECU (ID1) has a process for sending a predetermined message to ECU (ID2), and the new program for ECU (ID2) has a process for causing a timeout error if the predetermined message sent from ECU (ID1) cannot be received, the ECU order can be defined so that ECU (ID1) is updated first and ECU (ID2) is updated later.
[0080] (Second embodiment) As shown in FIG. 21 , the second embodiment relates to the “vehicle configuration information synchronization” that the vehicle-side system 4 first transmits to the center device 3 in FIG. 8 . When the IG switch 37 is turned on on the vehicle side, this triggers the CGW 13 to transmit a “synchronization start request” to the DCM 12. In response, the DCM 12 replies to the CGW 13 with a “configuration information collection request.” The CGW 13 then queries each ECU 19 about its program version. Each ECU 19 replies with its “ECU SW ID” to the CGW 13. Furthermore, an ECU 19 with a two-plane or suspended memory configuration also replies with plane information indicating which of its multiple planes is operational and which is non-operational. Furthermore, each ECU 19 may also transmit to the CGW 13 calibration information for the actuators to be controlled, license information for receiving a program update service, and fault codes occurring in the ECU 19.
[0081] Upon receiving all of the "ECU SW IDs" from each ECU 19, the CGW 13 transmits them to the DCM 12 along with the "VIN." At this time, the CGW 13 may also transmit the "Vehicle SW IDs" and "Sys IDs" managed by the CGW 13 to the DCM 12. The DCM 12 then generates a single hash value, which is a digest value, for all of the "ECU SW IDs," using, for example, a hash function. As described above, when using the SHA-256 hash function, the data values of all of the "ECU SW IDs" are serially concatenated into message blocks of 64 bytes each. The data value of the first message block is applied to the initial hash value to obtain a 32-byte hash value. The data values of subsequent message blocks are then sequentially applied to this hash value to obtain a final 32-byte hash value. Here, the DCM 12 may generate a single hash value for all of the "ECU SW IDs," including the "Vehicle SW IDs," "Sys IDs," surface information, and calibration information.
[0082] The DCM 12 transmits the digest value of the "ECU SW ID" obtained as described above to the center device 3 together with the "VIN." The DCM 12 may also transmit a fault code or license information together with the digest value. Hereinafter, the digest value will be referred to as a "configuration information digest," and all data values of the "ECU SW ID" that is the source of the digest value will be referred to as "all configuration information." The "all configuration information" may include the "Vehicle SW ID," "Sys ID," surface information, and calibration information.
[0083] As will be described later, the center device 3 compares digest values and updates the individual vehicle information DB 213. After synchronizing the configuration information, the center device 3 checks whether there is a program update, and if there is an update, notifies the vehicle-side system 4 of campaign information. The vehicle-side system 4 then downloads the distribution package, installs it in the target ECU 19, and activates the new program. Upon completion of these update processes, the CGW 13 transmits a "synchronization start request" to the DCM 12, and thereafter performs the same processing as described above until the synchronization completion notification is received. The above-mentioned processing, which is performed when the IG switch 37 is turned on, may also be performed after a program update.
[0084] As shown in FIG. 22, when the individual vehicle information management unit 3C of the center device 3 receives a "configuration information digest" from the vehicle-side system 4 (D1), it compares it with the "configuration information digest" of the corresponding vehicle registered in the individual vehicle information DB 213 at that time and determines whether the two match (D2). The "individual vehicle information digest" may be a pre-calculated value registered in the individual vehicle information DB 213, or the digest value may be calculated using the configuration information registered in the individual vehicle information DB 213 at the time of receiving it from the vehicle-side system 4. If the two match (YES), it determines whether the individual vehicle information of the vehicle matches the regular combination registered in the configuration information DB 208 (D6). Note that since the configuration information DB 208 may be updated at a predetermined timing, the determination in step D6 is made whether the two match in step D2 (YES) or if they do not match (NO).
[0085] 23, for example, the determination of compatibility is made by checking whether the combination of "Vehicle SW ID" and "ECU SW ID" in the configuration information uploaded from the vehicle-side system 4 is legitimate. In the list shown in the figure, the "ECU SW ID" of "ECU ID=ADS" corresponding to "Vehicle SW ID=0001" registered in the configuration information DB 208 is "ads_001," the "ECU SW ID" of "ECU ID=BRK" is "brk_001," and the "ECU SW ID" of "ECU ID=EPS" is "eps_010."
[0086] In contrast, vehicle C with VIN=300 also has "Vehicle SW ID=0001," but the "ECU SW ID" of "ECU ID=ADS" is "ads_002," and the "ECU SW ID" of "ECU ID=BRK" is "brk_003." These two ECUs 19 differ from the configuration information registered in the configuration information DB 208. Therefore, in step D6, the result is "NO," meaning the vehicle is non-genuine and the result is "NG." The configuration information confirmation unit 210 notifies the management device 220 shown in FIG. 8, which manages information on the vehicle-side system 4 and vehicles manufactured by OEMs, etc., of the abnormality (D12). The abnormality notification is performed, for example, by the SMS transmission control unit 212 using SMS. The SMS transmission control unit 212 is an example of a communication unit. Even if these two ECUs 19 are not ECUs to be updated with the new program, the center device 3 determines that the vehicle is non-genuine and does not perform the processes from step D7 onward.
[0087] On the other hand, vehicle A with VIN=100 has "Vehicle SW ID=0001," the "ECU SW ID" of "ECU ID=ADS" is "ads_001," and the "ECU SW ID" of "ECU ID=BRK" is "brk_001," all of which match the configuration information registered in the configuration information DB 208. Therefore, in step D6, the result is "YES," meaning that the vehicle is authentic and "OK," and the process proceeds to step D7. Here, the configuration information confirmation unit 210 may determine whether the vehicle is authentic or not based on whether the combination of "ECU SW ID" of vehicle C exists in the configuration information DB 208. Furthermore, in addition to the "Vehicle SW ID," the "Sys ID" may also be used as a basis for the determination.
[0088] Next, the update presence / absence confirmation unit 211 accesses the campaign DB 217 via the campaign management unit 3D to confirm whether an update with a new program has been made (D7). The presence / absence of an update is determined by comparing the "Vehicle SW ID" uploaded from the vehicle-side system 4 with the "Vehicle SW ID before update" in the campaign DB 217. For example, as shown in FIG. 23, vehicle A with VIN=100 has a "Vehicle SW ID=0001" before the update, so it is determined that an update has been made (YES). In this case, the update presence / absence confirmation unit 211 notifies the vehicle-side system 4 of vehicle A of the corresponding campaign ID "Cpn_001" (D8). The campaign information corresponds to update notification information, and the campaign DB 217 is an example of an update notification information storage unit.
[0089] If the campaign DB 217 is configured to store "Sys IDs" before and after the update, it is also possible to check whether an update has been performed by using the "Sys ID." Alternatively, instead of using the "Vehicle SW ID," the uploaded "ECU SW ID" list may be compared with the "ECU SW ID list before update" in the campaign DB 217 to determine whether an update has been performed.
[0090] The vehicle-side system 4 acquires a campaign file corresponding to the notified campaign ID from the center device 3 using the notified campaign ID as a key (D9). The campaign file includes text describing the campaign content and restrictions on executing the program update. The restrictions are conditions for executing downloads and installations, such as the remaining battery level, the free RAM space required to download the distribution package, and the current location of the vehicle. The vehicle-side system 4 analyzes the campaign file and displays the campaign content, etc., on the in-vehicle display 7. The user refers to the message displayed on the in-vehicle display 7 according to the campaign content and decides whether to update the application program in the ECU 19. Upon receiving the user's consent via the in-vehicle display 7, the CGW 13 notifies the center device 3 via the DCM 12 that the update is accepted. The center device 3 then transmits the distribution package file with the package ID corresponding to the campaign ID and integrity verification data to the vehicle-side system 4 (D10).
[0091] If there is no update in step D7 (NO), the vehicle-side system 4 is notified of "no update" (D11). For example, as shown in Fig. 23, vehicle A with VIN=200 has an updated "Vehicle SW ID=0002", which does not match any of the "Vehicle SW IDs before update" in the campaign DB 217, and is therefore determined to have no update.
[0092] On the other hand, if the comparison result of the "configuration information digest" in step D2 is a mismatch (NO), the center device 3 requests the vehicle-side system 4 to send "configuration information all" (D3). This transmission corresponds to a "notification of a request to send all data." In response, the vehicle-side system 4 transmits "configuration information all," which the center device 3 receives (D4). Then, the individual vehicle information management unit 3C of the center device 3 updates the information of the vehicle registered in the individual vehicle information DB 213 (D4). Then, the process proceeds to step D6. The individual vehicle information DB 213 is an example of a vehicle-side configuration information storage unit. The CGW 13 may transmit the "synchronization start request" when the IG switch 37 is turned off.
[0093] As described above, according to the second embodiment, when the vehicle-side system 4 receives configuration information relating to the configuration of each ECU 19 from a plurality of ECUs 19, it generates a hash value based on the data values of the plurality of pieces of configuration information and transmits the hash value to the center device 3. The center device 3 has an individual vehicle information DB 213 and compares the hash value transmitted from the vehicle-side system 4 with the hash value of the vehicle's configuration information stored in the individual vehicle information DB 213. If the hash values do not match, the center device 3 requests the vehicle-side system 4 to transmit "all configuration information." In response to this transmission, the vehicle-side system 4 transmits the "all configuration information" to the center device 3, and upon receiving the "all configuration information," the center device 3 updates the configuration information stored in the individual vehicle information DB 213 based on the data values.
[0094] With this configuration, the vehicle-side system 4 initially transmits a hash value of the configuration information to the center device 3, and transmits all data values of the configuration information to the center device 3 only when the comparison result of the hash values at the center device 3 indicates a mismatch. This reduces the size of data transmitted by the vehicle-side system 4, thereby reducing the overall communication volume even when the vehicle-side system 4 is installed in a large number of vehicles. In particular, when the vehicle-side system 4 uploads configuration information at a predetermined timing, such as when the IG is on, there may be times when communication is concentrated. Therefore, by using a hash value to reduce the amount of transmitted data, the communication load can be reduced.
[0095] Furthermore, the CGW 13 receives configuration information from all ECUs 19 to be rewritten with the update data, generates a hash value based on all of the data values, and the DCM 12 transmits the hash value when the ignition switch 37 of the vehicle is turned on or off, so that the hash value can be transmitted to the center device 3 when the vehicle starts or stops traveling. Therefore, the center device 3 can appropriately synchronize the configuration information of the individual vehicle information DB 213 with the vehicle.
[0096] Furthermore, when the vehicle-side system 4 receives the "ECU SW ID" of each ECU 19 from the plurality of ECUs 19, it transmits a configuration information list combining the "ECU SW ID" with a "Vehicle SW ID" to the center device 3. The center device 3 compares the "ECU SW ID" list transmitted from the vehicle-side system 4 with the "regular ECU SW ID" list of the corresponding vehicle stored in the configuration information DB 208, and if it determines that the combination of the transmitted list is irregular, it transmits an abnormality detection to the vehicle-side system 4 and the management device 220.
[0097] With this configuration, the center device 3 can detect an abnormality when a combination of vehicle configuration information causes a state in which multiple ECUs 19 cannot cooperate and impedes vehicle driving, and notify the vehicle-side system 4. This enables the vehicle-side system 4 to take action such as prohibiting the vehicle from driving.
[0098] The center device 3 does not perform the process (D7) to check whether an update is necessary for a vehicle with an unauthorized combination of vehicle configuration information. This makes it possible to prevent a program update from being performed on an unauthorized vehicle. Even if the unauthorized ECU 19 is not an ECU to be updated with a new program, the center device 3 does not perform the process (D7) to check whether an update is necessary. When the vehicle-side system 4 performs a program update, control is also performed on the ECU 19 that is not the target of the update. Therefore, in a vehicle having an unauthorized ECU 19, there is a possibility that the program update will not be completed normally, and therefore the center device 3 prevents the program update from being performed on the vehicle.
[0099] The center device 3 also includes a campaign DB 217 that stores campaign information used to notify the vehicle of the occurrence of an update with a new program, and for a vehicle determined to be authentic, checks whether or not there is campaign information for the corresponding vehicle. If there is an update, the center device 3 transmits the campaign information to the vehicle-side system 4. This allows the user to be presented with the campaign information and encouraged to update the application program. The center device 3 synchronizes the configuration information, determines whether the configuration information is authentic, and checks whether an update has been made as a series of processes triggered by the upload of the configuration information from the vehicle, thereby enabling the appropriate vehicle to be promptly notified of the program update.
[0100] The second embodiment may be modified as follows. The "synchronization start request" may be transmitted by the center device 3 to the vehicle-side system 4, and upon receiving the "synchronization start request," the DCM 12 may transmit a "configuration information collection request" to the CGW 13. For example, when the configuration information DB 208 for "vehicle model=aaa" is updated, the center device 3 transmits a "synchronization start request" to vehicles of that vehicle model. Furthermore, the hash value may be transmitted to the center device 3 at the timing when the rewriting of the ECU 19 that has been the target of rewriting with the update data is completed. That is, even at the timing when the program update of all the ECUs 19 that have been the target of rewriting is completed, the flowchart of steps D1 to D12 shown in FIG. 22 is executed. If the comparison result of both hash values indicates a match, the center device 3 requests the vehicle-side system 4 to transmit a combination list of the configuration information of each ECU 16. Then, upon receiving the combination list, the center device 3 may perform the processes of steps D6 to D12. Even when the comparison result of both hash values shows a match, the center device 3 may refer to the campaign DB 217 to check whether or not there is campaign information for the corresponding vehicle.
[0101] The transmission of hash values from the vehicle-side system 4 to the center device 3 may be performed as shown in FIG. 23A. FIG. 23A is a flowchart showing the processing of the CGW 13. For example, when the IG switch 37 is turned on, the CGW 13 collects configuration information from each ECU 19 (D21) and generates a hash value for the data value of the collected configuration information (D22). The generated hash value is then compared with the hash value (previously generated value) stored in the flash memory 24d to determine whether there is a difference (D23). If there is a difference (YES), the newly generated hash value is stored in the flash memory 24d (D24), and the hash value is transmitted to the center device 3. If there is no difference between the two hash values in step D23 (NO), the processing ends. Note that the hash value for the initial value of the configuration information is pre-stored in the flash memory 24d. This reduces the number of times the vehicle-side system 4 uploads configuration information to the center device 3.
[0102] (Third embodiment) The third embodiment relates to a function executed by the campaign management unit 3D of the center device 3 to improve the update rate of application programs in the vehicle-side system 4. As shown in FIG. 24 , for example, in the vehicle-side system 4, a user sets the HTTP polling interval to about three days using a Config file, which causes the vehicle-side system 4 to periodically check with the center device 3 whether or not an application program has been updated. As a result, when an update check is performed after campaign information for a vehicle / VIN corresponding to the campaign DB 217 is set, the center device 3 notifies the vehicle-side system 4 that an update has been made. That is, as described in the second embodiment, the process of the center device 3 checking for an update when the vehicle-side system 4 uploads configuration information using HTTP is triggered and is executed when the IG is turned on three days later.
[0103] If the center device 3 is configured to check for updates in response to a notification from a vehicle, the center device 3 does not need to transmit campaign information to all vehicles that are the target of the campaign when the campaign information is set. However, if a user does not use the vehicle for a long period of time, the center device 3 does not check for updates using HTTP during that time. Therefore, it is expected that the user will not know that a new campaign has been issued, and some vehicles will not have their application programs updated.
[0104] 25, the SMS transmission control unit 212 of the center device 3 periodically or at a predetermined timing checks the access log of each vehicle by referring to the individual vehicle information DB 213 (E1). Then, it is determined whether there is a vehicle that has not accessed the center device 3, that is, has not transmitted configuration information for checking for update of the application program, for a predetermined period of time (E2). The predetermined period is, for example, about seven days, starting from the day when a new campaign is set in the campaign DB 217. In other words, the SMS transmission control unit 212 identifies vehicles for which update check has not been performed for seven days, targeting vehicles whose "Vehicle SW ID" in the individual vehicle information DB 213 matches the "Vehicle SW ID before update" in the campaign DB 217. Note that the SMS transmission control unit 212 may target all vehicles and identify vehicles for which update check has not been performed for a predetermined period of time.
[0105] Note that initial data is registered in the individual vehicle information DB 213 by the OEM when the vehicle is produced at the factory, but the first access log is subsequently entered upon notification from the OEM, for example, when the vehicle is sold. This access log essentially corresponds to a notification for enabling subsequent program updates. Vehicles for which no access log has been entered are not subject to the judgment in step E2.
[0106] If there is a vehicle for which update check has not been performed for a predetermined period of time (YES), the SMS transmission control unit 212 determines the characteristics of the vehicle from the model, equipment information, etc. in the individual vehicle information DB 213 (E3). In terms of characteristics, the SMS transmission control unit 212 determines whether the vehicle is an electric vehicle (EV) capable of receiving SMS (Short Message Service), a conventional gasoline engine vehicle capable of receiving SMS (i.e., a conventional engine vehicle), or a vehicle that has difficulty receiving SMS. For example, if the DCM 12 installed in the vehicle does not have the function to receive SMS or if there is no contract to receive SMS, the vehicle is determined to have difficulty receiving SMS.
[0107] If it is an EV, an SMS is sent to start the vehicle's ECU 19 and initiate the configuration information transmission sequence (see E5, FIG. 26). When the DCM 12 receives the SMS and executes the command described in the SMS, the CGW 13 switches to the IG-on power state and transmits the configuration information to the center device 3 via the DCM 12. Thereafter, as shown in steps D1 to D12 in FIG. 22, an update check is performed and the download of the distribution package is executed. In the case of an EV, since the battery capacity is large, it is considered possible to download a program while the vehicle is parked with the IG-on power state. Therefore, the ECU 19 is started using the SMS to automatically start the update check, download, and subsequent sequences.
[0108] If the remaining battery charge of the EV is low, the vehicle-side system 4 refers to the rewrite specification data shown in Fig. 17, and if the remaining battery charge is below a specified level, the vehicle-side system 4 is controlled not to start installation. Alternatively, the center device 3 refers to the remaining battery charge described as a constraint in the campaign file sent in step D9, and if the remaining battery charge is below a specified level, the vehicle-side system 4 is controlled not to start downloading the distribution package.
[0109] For conventional vehicles that are in a state where they can receive SMS during the period when the DCM 12 is intermittently activated, the SMS transmission control unit 212 transmits an SMS that can be displayed on the in-vehicle display 7 (see E4, FIG. 26). For example, the CGW 13 instructs the in-vehicle display 7 to display the text contained in the received SMS the next time the IG is turned on. Also, if information about the user's mobile terminal 6 is registered in the individual vehicle information DB 213, an SMS may be sent to the mobile terminal 6. For example, a text message such as "Campaign information is available. Please turn on the IG." may be displayed. The individual vehicle information DB 213 is an example of a user information storage unit. On the other hand, for vehicles that are in a state where it is difficult to receive SMS, no action is taken, and a separate message may be sent to the user by mail or the like (E6).
[0110] As described above, according to the third embodiment, the vehicle-side system 4 transmits the configuration information of the plurality of ECUs 19 to the center device 3, and the individual vehicle information DB 213 stores the configuration information transmitted from each vehicle together with the transmission date. Furthermore, the campaign DB 217 stores, as campaign information, a campaign ID and a target VIN list that can identify vehicles subject to data update. The center device 3 then refers to the individual vehicle configuration DB 213, and if no configuration information is transmitted within a predetermined period from the transmission date associated with the subject vehicle, transmits a message via SMS to the vehicle-side system 4 of the subject vehicle to prompt it to perform a data update.
[0111] With this configuration, even if the situation continues in which the configuration information is not transmitted to the center device 3 because the user has no opportunity to board the vehicle, the center device 3 transmits a message to the vehicle-side system 4 of the target vehicle to urge the vehicle to update data when a predetermined period has elapsed since the transmission date stored in the individual vehicle information DB 213. Therefore, the user can recognize that a data update is necessary by referring to the message.
[0112] The center device 3 then determines the target vehicle for the program update by referring to the individual vehicle information DB 213 and the campaign DB 217. That is, the individual vehicle information DB 213 stores the date on which configuration information was transmitted from each vehicle, and the campaign DB 217 stores the target VIN list. Therefore, the center device 3 can determine the target vehicle for the program update based on the transmission date of the configuration information from each vehicle and the target VIN list.
[0113] Furthermore, when the ignition switch 37 of the vehicle is turned on, the vehicle-side system 4 receives the respective configuration information from the ECUs 19 and transmits the configuration information to the center device 3. Therefore, when the user gets into the vehicle, the configuration information can be reliably transmitted to the center device 3.
[0114] If the target vehicle is an electric vehicle, the center device 3 transmits a message containing a command to start the ECU of the target vehicle, and the vehicle-side system 4, upon receiving the message, starts the ECU 19 and causes it to execute processing related to the data update. That is, since an electric vehicle has a relatively large battery capacity, it is possible to cause the ECU 19 to execute processing related to the data update without waiting for a user operation. Therefore, the data update can be executed efficiently.
[0115] Furthermore, if the target vehicle is a conventional vehicle, the center device 3 transmits, as a message, at least text information that can be displayed on the in-vehicle display 7 of the target vehicle. Therefore, the user of the conventional vehicle can recognize that a data update is required by referring to the text information displayed on the in-vehicle display 7.
[0116] Furthermore, when the destination of the user's mobile terminal 6 is stored in the individual vehicle information DB 213, the center device 3 transmits text information that can be displayed on the mobile terminal 6 as a message. This allows the user to recognize that a data update is required by referring to the text information displayed on the mobile terminal 6 even if the user does not have an opportunity to board the vehicle.
[0117] Furthermore, when the user transmits the campaign transmission date and transmission destination to the center device 3 in advance via the mobile terminal 6, the center device 3 stores the transmission date and transmission destination in the individual vehicle information DB 213. For example, the user specifies the day after the campaign issuance as the transmission date, and specifies the mobile terminal 6 instead of the in-vehicle display 7 as the transmission destination. The user also specifies a predetermined time when the user will not be riding as the transmission date, specifies the vehicle as the transmission destination, and performs an operation to consent to automatic program updating. As a result, the center device 3 transmits the campaign information to the transmission destination on the transmission date, regardless of whether configuration information is transmitted. Therefore, when the user knows in advance that he or she will not have an opportunity to ride the vehicle for some time, the user can set the campaign information to be received on the transmission date set by the user.
[0118] The third embodiment may be modified as follows. The user information storage unit may be provided separately from the individual vehicle information DB 213. Campaign information may be sent using methods other than SMS. Instead of storing the transmission date in the individual vehicle information DB 213, the center device 3 may store, for example, the days on which no transmission was received from the vehicle, and send a message urging a data update when such days occur for seven consecutive days.
[0119] (Fourth embodiment) The fourth embodiment illustrates a case where a user specifies a notification method for campaign information and messages. For example, assume that the user will not be riding for about a month and has determined in advance that there will be no opportunity to turn on the IG switch 37. As shown in FIG. 27, the user transmits settings for the notification destination and notification date and time when a campaign occurs to the center device 3 using the mobile terminal 6. For example, the user sets a setting to notify the mobile terminal 6 of campaign information one month later. As a result, the individual vehicle information management unit 3C stores the information on the notification destination and notification date and time in the individual vehicle information DB 213 and notifies the user according to the settings. For example, if two campaigns (1, 2) are set during that one month, the SMS transmission control unit 212 notifies the user's mobile terminal 6 of the information on campaigns (1, 2) one month later to prompt a program update.
[0120] As described above, according to the fourth embodiment, when a user transmits the transmission date and transmission destination of campaign information to the center device 3 via the mobile terminal 6, the center device 3 stores the transmission date and transmission destination in the individual vehicle information DB 213. Then, the center device 3 transmits the campaign information to the transmission destination on the stored transmission date. This allows the center device 3 to stop transmitting unnecessary campaign information when it is determined that the user will not be riding in a vehicle for a certain period of time.
[0121] (Fifth embodiment) The fifth embodiment illustrates a function of adding verification data used by the vehicle-side system 4 to verify the integrity of data when the center device 3 transmits data of an update program to the vehicle-side system 4. As shown in FIGS. 28 and 29 , a supplier uses a package management unit 3A to create data to be registered in the ECU repro data DB 204. Specifically, the package management unit 3A creates new difference data for rewriting an old program with a new program as update data (Y1), and creates a hash value that is integrity verification data for the new program in the ECU 19 and a hash value for the new difference data (Y2). Here, if the ECU has a single memory, old difference data for rewriting the new program with the old program as rollback data may be created, and a hash value for the old program in the ECU 19 and a hash value for the old difference data may be created.
[0122] The package management unit 3A applies encryption using a key value, which is a predetermined key, to each hash value to generate an authenticator (Y3).The package management unit 3A then transmits the update data and the integrity verification data with each authenticator, and stores them in the ECU repro data DB 204 (Y4).As described above, the package management unit 3A generates a package, generates integrity verification data for the package, and transmits it to the vehicle-side system 4 (Y5).
[0123] The master device (OTA master) 11 calculates integrity verification data for the package, compares the calculated value with the received package integrity verification data, and verifies the package integrity (Y6). If the package integrity verification is successful, the master device 11 transmits the ECU update data and integrity verification data to the reprogramming target ECU 19 (Y7).
[0124] The rewrite target ECU 19 calculates integrity verification data for the update data, compares the calculated value with the integrity verification data of the received update data, and verifies the integrity of the update data (Y8). If the integrity verification of the update data is successful, the rewrite target ECU 19 restores the difference data, which is the update data, and writes it to the flash memory 28d (Y9). Once the writing is complete, the rewrite target ECU 19 calculates integrity verification data for the data written to the flash memory 28d, compares the calculated value with the integrity verification data of the received new program, and verifies the integrity of the flash memory 28d (Y10). The rewrite target ECU 19 transmits the verification result to the master device 11 (Y11), and the master device 11 transmits the received verification result to the center device 3 as an installation result notification (Y12).
[0125] For example, as shown in Fig. 10, the package management unit 3A generates the following integrity verification data for the latest "ECU SW ID." If the memory configuration of the ECU is dual memory or suspend, the following (3) and (4) can be omitted. (1) A hash value is generated as integrity verification data for the new program of the ECU. The functional part that performs this process is an example of a first verification value generation unit (step A1). (2) Generate update data, which is differential data for updating the ECU's old program to a new program, and a hash value, which is data for verifying the integrity of the update data. The functional part that performs this process is an example of the second verification value generation unit (step A4). (3) A hash value is generated as integrity verification data for the old program of the ECU. The functional part that performs this process is an example of a fourth verification value generation unit (step A5). (4) Generate update data, which is differential data for updating the old program based on the new program of the ECU, and a hash value, which is data for verifying the integrity of the update data. The functional part that performs this process is an example of a fifth verification value generation unit (step A7).
[0126] Note that the "program" also includes constant data used in the program. If "ECU SW ID=ads_002", a hash value x1 is generated for the update data "Adsfile001-002". As mentioned above, for example, SHA-256 is used as the hash function. The hash value corresponds to the verification value. Here, the package management unit 3A may be configured to generate integrity verification data with an authenticator by applying encryption to the hash value using a key value, which is a predetermined key, to generate an authenticator.
[0127] Next, the supplier generates an authenticator-attached integrity verification data by encrypting the integrity verification data using a predetermined key value, and provides the update data and the authenticator-attached integrity verification data in association with each other to the OEM. In other words, the package management unit 3A registers each program and its corresponding authenticator-attached integrity verification data in the ECU repro data DB 204, thereby providing the update data to the OEM. In response to an instruction from the OEM, the package management unit 3A generates rewrite specification data as described above using the ECU repro data DB 204, etc., generates a distribution package, and registers it in the package DB 206. When a download request for update data is issued from the vehicle-side system 4, the center device 3 distributes a distribution package including the update data and the authenticator-attached integrity verification data to the vehicle-side system 4 in accordance with the download request. It should be noted that the "integrity verification data" in the claims includes both hash values alone and integrity verification data with an authenticator that includes encryption using a key.
[0128] When the master device 11 of the vehicle-side system 4 receives the distribution package, it verifies the validity of the distribution package using the integrity verification data (third verification value) attached to the distribution package. Specifically, it compares the integrity verification data calculated using the distribution package with the received integrity verification data, and if they match, it determines that the distribution package is normal. If the verification confirms that the distribution package is normal, the master device 11 unpackages the distribution package into data for each ECU (see FIG. 6). Then, the master device 11 transfers the update data and the integrity verification data with the authenticator to the ECU 19 to which the data is to be written.
[0129] The ECU 19 verifies the validity of the update data using the authenticator-attached integrity verification data (second verification value). Specifically, the ECU 19 compares the integrity verification data calculated using the received update data with the received integrity verification data, and if they match, the update data is deemed normal. If the verification confirms normality, the CPU 28a of the ECU 19 performs a write process to the flash memory 28d. After the write process is completed, the ECU 19 reads the data written to the flash memory 28d using the authenticator-attached integrity verification data (first verification value) and verifies its validity. Specifically, the ECU 19 compares the integrity verification data calculated using the read data with the received integrity verification data, and if they match, the update data is deemed normal. Note that this integrity verification data is also used when the ECU 19 starts up, so it is stored in a predetermined area of the flash memory 28d. After completing these processes, the ECU 19 transmits a write response, including the verification result, to the master device 11. The master device 11 notifies the center device 3 of the installation result. In the drawing, "target ECU" is synonymous with "target ECU," and "OTA master" is synonymous with "DCM." The CPU 28a is an example of a write processing unit.
[0130] If the program update is canceled during installation, the ECU 19 will perform rollback processing. While writing the update data, the ECU 19 verifies the validity of the rollback differential data using the authenticator-attached integrity verification data (fifth verification value). Specifically, the ECU 19 compares the integrity verification data calculated using the rollback differential data with the received integrity verification data, and if they match, determines that the data is normal. If the verification confirms normality, the ECU 19 completes writing of the update data and then starts writing using the rollback differential data. After completing the writing, the ECU 19 reads the data written to the flash memory 28d and verifies its validity using the authenticator-attached integrity verification data (fourth verification value). The master device 11 may be configured to verify the integrity of the received differential data (update data, rollback differential data) instead of the ECU 19.
[0131] As shown in FIG. 30, when the IG switch 37 of the vehicle is subsequently turned on, the ECU 19 performs data verification at startup. The ECU 19 verifies the integrity of programs and the like to be started using the authenticator-attached integrity verification data (first verification value or fourth verification value). First, a hash function is applied to the data values in the evaluation target area in the flash memory 28d, where updated programs and constant data are written, to obtain a hash value. Next, the authenticator-attached integrity verification data is decrypted, and the hash value (expected value) included in the decryption result is compared with the obtained hash value (calculated value) to determine whether the programs and the like written in the flash memory 28d have been tampered with. If the two hash values match and are "OK," the ECU 19 performs startup processing as usual. Similar processing is performed for each ECU 19, and if the results for all evaluation target ECUs 19 are "OK," the processing ends.
[0132] On the other hand, if the verification result for any of the ECUs 19 is abnormal (NG), the ECU 19 saves a log of the process and notifies the master device 11 of the error. The master device 11 similarly saves a log and notifies the center device 3 of the error. The center device 3 similarly saves a log and notifies the management device 220 of the OEM or the like of the error. The management device 220 is notified, for example, by using SMS by the SMS transmission control unit 212 or by sending an email via the Internet.
[0133] In the above-described embodiment, the vehicle-side system 4 is configured to perform integrity verification. Fig. 31 illustrates a case where the integrity verification (comparison with an expected value) is performed by the center device 3. In Fig. 31, when the IG is turned on, for example, the ECU 19 generates and transmits, together with the version information of an updated application program to the master device 11, integrity verification data with an authenticator in the same manner as described above (X1). The ECU 19 calculates the integrity verification data for the data in the flash memory 28d and transmits the calculated value to the master device 11. The master device 11 transmits the integrity verification data with the authenticator as configuration information to the center device 3 (X2).
[0134] The center device 3 accesses the ECU repro data DB 204, obtains the integrity verification data with the authenticator that matches the "ECU SW ID" of the target ECU 19 (X3, X4), and compares it with the integrity verification data uploaded from the vehicle side (X5). Specifically, it obtains the integrity verification data of the new program that corresponds to the "ECU SW ID" from the ECU repro data DB and compares it. If the comparison result is a mismatch (NG) (X6; NG), it notifies the OEM's management device 220 of an abnormality (X7). The function of this processing part corresponds to the abnormality notification part.
[0135] The center device 3 transmits the verification result to the master device 11 (X8), and the master device 11 transmits the received verification result to the rewrite target ECU 19 (X9). If the verification result is OK, the rewrite target ECU 19 runs the application program as usual, and if the verification result is NG, the rewrite target ECU 19 does not run the application program. Note that in this embodiment, the package management unit 3A can omit generating integrity verification data for the new program (step A1) and generating integrity verification data for the old ECU program (step A5).
[0136] In the above description, the ECU 19 verifies the integrity of the update data when the vehicle's IG switch 37 is turned on after writing the update data, but instead, the ECU 19 may verify the integrity immediately after writing the update data.
[0137] In the above embodiment, the authenticator-attached integrity verification data is added only to the update data, but this may be implemented as follows. The new program and the corresponding update data are acquired from the ECU repro data DB 204 (data acquisition procedure; step A1). The first verification value generation unit generates a first hash value for the new program (first verification value generation procedure; step A2). The second verification value generation unit generates a second hash value for the update data (second verification value generation procedure; step A4). The package generation unit 202 includes the update data, specification data, and the first and second hash values in a distribution package (distribution package generation procedure). The update data corresponds to the new differential data. The third verification value generation unit generates a third hash value for the distribution package (third verification value generation procedure; step C4). The package distribution unit 203 transmits the distribution package and the third hash value to the vehicle-side system 4 (transmission procedure). The authenticator may be assigned only to the distribution package and the third hash value, or may be assigned at each stage of generating each hash value. The package distribution unit 203 corresponds to a transmission unit.
[0138] In this case, the vehicle-side system 4: The DCM 12, which is a receiving processor, receives the distribution package and the third hash value. The third verification processing unit compares a hash value generated from the distribution package data with the received third hash value to verify the integrity of the distribution package data. The second verification processing unit compares a hash value generated from the update data with the received second hash value to verify the integrity of the update data. The CPU 28a, which is an example of a write processing unit, writes the update data to the flash memory 28d. The first verification processing unit generates a hash value for the data values in the flash memory 28d that have become the new program by writing the update data, and compares it with the received first hash value to verify the integrity of the new program. If the verification result of the update data is NG, writing to the flash memory 28d is stopped. Also, if the verification result of the new program written to the flash memory 28d is NG, the new program is invalidated and rollback processing is performed as necessary. Note that the first to third verification processing units may be realized by the CPU 28a. Also, if the verification result of any of the first to third verification processing units is NG, the DCM 12 as a transmission processing unit notifies the center device 3 of an abnormality.
[0139] Furthermore, in addition to the above, as shown in FIG. 10, when rollback data exists for restoring the old program to the state before the update data was added, the following may be carried out. The fourth verification value generation unit generates a fourth hash value for the old program (fourth verification value generation procedure; step A5). The fifth verification value generation unit generates a fifth hash value for rollback data for reverting the new program to the old program (fifth verification value generation procedure; step A7). The rollback data indicates differential data for rollback and corresponds to the old differential data. The package generation unit 202 includes the update data, the rollback differential data, the rewrite specification data, and the first, second, third, and fourth hash values in the distribution package (distribution package generation procedure).
[0140] In this case, if the user issues an instruction to stop the rewriting while the update data is being rewritten to the flash memory 28d in the vehicle-side system 4, the rewriting is canceled and the old program is restored, i.e., rolled back. This applies only when the memory configuration of the ECU 19 is a single-plane memory. The second verification processing unit calculates a hash value for the rollback data included in the distribution package, and compares the calculated hash value with the fifth hash value to verify the integrity of the rollback data. The CPU 28a writes the rollback data to the flash memory 28d. The first verification processing unit calculates a hash value for the old program restored by writing it to the flash memory 28d, and compares the calculated hash value with the fourth hash value to verify the integrity of the old program.
[0141] As described above, according to the fifth embodiment, the ECU repro data DB 204 stores the new program, the old program, and the update data, which is new difference data for updating the old program to the new program, for the target ECU 19 to be rewritten. The first verification value generation unit generates a first hash value using the new program, and the second verification value generation unit generates a second hash value using the update data. The package generation unit 202 generates a package including update data for multiple target ECUs 19, the first and second verification values, and specification data. The third verification value generation unit generates a third hash value using the distribution package, and the package distribution unit 203 transmits the distribution package together with the third hash value to the vehicle-side system 4.
[0142] When the vehicle-side system 4 receives the distribution package and the third hash value, the third verification processing unit calculates a hash value for the distribution package and compares it with the third hash value to verify the integrity of the distribution package. The second verification processing unit calculates a hash value for update data corresponding to the target ECU 19 included in the distribution package and compares it with the second hash value included in the distribution package to verify the integrity of the update data.
[0143] The CPU 28a writes the update data to the flash memory 28d, and the first verification processing unit calculates a hash value for the updated new program data in the flash memory 28d and compares it with the first hash value to verify the integrity of the new program data. In this way, the integrity of each data value can be verified in multiple stages using each hash value. This allows the integrity of the new program to be verified three times, preventing the vehicle-side system 4 from writing an incomplete new program or operating with an unauthorized new program.
[0144] Furthermore, when rollback data exists in the ECU repro data DB 204, the fourth verification value generation unit generates a fourth hash value for the old program, and the fifth verification value generation unit generates a fifth hash value for the rollback data. The package generation unit 202 includes the update data, the first and second hash values, the rollback data, and the fourth and fifth hash values in a distribution package.
[0145] When a rollback is performed in the vehicle-side system 4, the second verification processing unit calculates a hash value for the rollback data included in the distribution package and compares it with the fifth hash value to verify the integrity of the rollback data. The CPU 28a uses the rollback data to write to the flash memory 28d. The first verification processing unit calculates a hash value for the old program restored by writing to the flash memory 28d and compares it with the fourth hash value to verify the integrity of the old program. This makes it possible to verify the integrity of the rewritten old program as well. In the above, the first to fifth verification value generation units are function blocks in the package management unit 3A of the center device 3. The first, second, fourth, and fifth verification processing units are function blocks in the target ECU 19 of the vehicle-side system 4. The third verification processing unit is a function block in the master device 11 (OTA master 11) of the vehicle-side system 4.
[0146] (Modification 1 of the first embodiment) As shown in Figures 32 and 33, multiple packages "pkg_001_1" and "pkg_001_2" may correspond to one campaign "cpn_001." Multiple packages may also be organized into multiple groups. In the above-described embodiment, one package includes multiple groups. In this modified example, one package is generated for each group, and multiple packages are distributed for one campaign. For example, package "pkg_001_1" includes ECUs "ADS" and "BRK" that belong to group 1, and package "pkg_001_2" includes ECU "EPS" that belongs to group 2.
[0147] In this case, as shown in Figures 34 and 35, specification data and distribution packages are generated separately for each group. In Figure 34, the specification data generation unit 201 generates first specification data describing ECU information for, for example, "ADS" and "BRK" as specification data for group 1. The specification data generation unit 201 generates second specification data describing ECU information for, for example, "EPS" as specification data for group 2. Then, in Figure 35, the package generation unit 202 generates reprogram data by integrating update data for, for example, "ADS" and "BRK" belonging to group 1 in ECU order, and integrates the data with the first specification data to generate a package file "pkg001_1.dat." The package generation unit 202 generates reprogram data using update data for "EPS" belonging to group 2, and integrates the data with the second specification data to generate a package file "pkg001_2.dat."
[0148] (Modification 2 of the first embodiment) 36 shows the processing contents when the functions of the specification data generation unit 201 and the package generation unit 202 are integrated into one package generation tool 221. Each processing will be explained below. In the specification data generation process, values input by an operator as specification data information are output in a data structure with a predetermined number of bits and order, thereby generating specification data. Specification data information may be, for example, values such as those shown in FIG. 17, where information on an ECU basis, such as ECU (ID1), ECU (ID2), and ECU (ID3), as well as information on a vehicle basis or a system (group) basis is input. Vehicle-based information is, for example, the rewriting environment information shown in FIG. 17, and system-based information is, for example, the group information and ECU order information shown in FIG. 17. The input information on a vehicle basis and a system basis may each be stored as separate files. The specification data generation process may be provided with a function to automatically calculate some values, such as the file size of the update data, and reflect them in the specification data. In the package generation process, the generated specification data, update data for each ECU, and values and files entered as integrity verification data for each ECU are output in a data structure with a predetermined number of bits and order, generating a distribution package file. The update data and integrity verification data for each ECU are sorted in ascending order of group and ECU order. Here, in addition to the update data (new difference data), rollback data (old difference data) can also be added to the input. As integrity verification data, "integrity verification data for the ECU program (new)" and "integrity verification data for the update data" are input. If rollback data is also added, "integrity verification data for the ECU old program" and "integrity verification data for the old difference data" are also added to the input. In the integrity verification data generation process, as described in step C4 of FIG. 19, integrity verification data is generated for the generated package file. The generated package file and the integrity verification data generated for the package file are registered in the package DB 206 by the operator.
[0149] (Other embodiments) The functions executed by the center device 3 may be realized by hardware or software, or may be realized by a combination of hardware and software. The data to be rewritten is not limited to application programs, but may also be data such as maps, control parameters, and the like. The contents of the configuration information are not limited to the examples given above, and may be selected appropriately according to individual designs. The content of the specification data is not limited to the examples given. The campaign information and distribution specification data may be included in the distribution package and transmitted to the vehicle, or may be transmitted to the vehicle separately from the distribution package. In the fifth embodiment, the distribution package and the third verification value may be stored in advance in the package memory unit, and the package sending unit 213 may send the distribution package and the third verification value associated with the request to the vehicle-mounted system 4 in response to a request from the vehicle-mounted system 4.
[0150] A sixth embodiment will be described below with reference to the drawings, focusing on the operation of the vehicle program rewriting system 1. The vehicle program rewriting system (corresponding to a vehicle electronic control system) is a system that can rewrite application programs for vehicle control, diagnosis, etc., installed in an electronic control unit (hereinafter referred to as an ECU (Electronic Control Unit)) over the air (OTA). This embodiment describes a case where application programs are rewritten via a wired or wireless connection, but the present invention can also be applied to a case where data used in various applications, such as map data used in a map application or control parameters used in an ECU, is rewritten via a wired or wireless connection.
[0151] Rewriting an application program via a wired connection includes not only obtaining and rewriting the application program via a wired connection from outside the vehicle but also obtaining and rewriting various data used when the application program is executed via a wired connection from outside the vehicle. Rewriting an application program via a wireless connection includes not only obtaining and rewriting the application program via a wireless connection from outside the vehicle but also obtaining and rewriting various data used when the application program is executed via a wireless connection from outside the vehicle.
[0152] 37, the vehicle program rewriting system 1 includes a center device 3 on the communication network 2 side, a vehicle-side system 4 on the vehicle side, and a display terminal 5. The communication network 2 includes, for example, a mobile communication network using a 4G line or the like, the Internet, WiFi (Wireless Fidelity) (registered trademark), and the like.
[0153] The display terminal 5 is a terminal having a function of receiving operation input from a user and a function of displaying various screens, and is, for example, a mobile terminal 6 such as a smartphone or tablet that can be carried by the user, or an in-vehicle display 7 arranged in the vehicle cabin. The mobile terminal 6 can communicate data with the center device 3 via the communication network 2 as long as it is within the communication range of the mobile communication network. The in-vehicle display 7 is connected to the vehicle-side system 4 and may also have a navigation function. Furthermore, the in-vehicle display 7 may be an in-vehicle display ECU having the functions of an ECU, or may have a function of controlling the display on the center display, meter display, etc.
[0154] When the user is outside the vehicle cabin and within the communication range of the mobile communication network, the user can perform procedures related to the rewriting of the application program by making operational inputs while checking various screens related to the rewriting of the application program on the mobile terminal 6. When the user is inside the vehicle cabin, the user can perform procedures related to the rewriting of the application program by making operational inputs while checking various screens related to the rewriting of the application program on the in-vehicle display 7. In other words, the user can perform procedures related to the rewriting of the application program by selectively using the mobile terminal 6 and the in-vehicle display 7 outside and inside the vehicle cabin.
[0155] The center device 3 controls the program update function on the communication network 2 side in the vehicle program rewriting system 1 and functions as an OTA center. The center device 3 has a file server 8, a web server 9, and a management server 10, and the servers 8 to 10 are configured to be able to communicate data with each other. In other words, the center device 3 is configured to include multiple servers that differ for each function.
[0156] The file server 8 is a server that manages files of application programs distributed from the center device 3 to the vehicle-side system 4. The file server 8 manages update data (hereinafter also referred to as reprogram data or write data) provided by suppliers or the like who are providers of the application programs distributed from the center device 3 to the vehicle-side system 4, distribution specification data provided by OEMs (Original Equipment Manufacturers), vehicle status information acquired from the vehicle-side system 4, etc. The file server 8 is capable of data communication with the vehicle-side system 4 via the communication network 2, and when a download request for a distribution package is made, it transmits a distribution package in which the reprogram data and distribution specification data are packaged into a single file to the vehicle-side system 4.
[0157] Web server 9 is a server that manages web information. Web server 9 transmits web data that it manages in response to a request from a web browser of mobile terminal 6 or the like. Management server 10 is a server that manages personal information of users who have registered for the application program rewriting service, the rewriting history of application programs for each vehicle, and the like.
[0158] The vehicle-side system 4 has a master device 11 (corresponding to a vehicle master device). The master device 11 has a DCM (Data Communication Module) 12 (corresponding to an in-vehicle communication device) and a CGW (Central Gate Way) 13 (corresponding to a vehicle gateway device). The DCM 12 and CGW 13 are connected to be able to communicate data via a first bus 14. The DCM 12 performs data communication with the center device 3 via a communication network 2. When the DCM 12 downloads a distribution package from the file server 8, it extracts write data from the downloaded distribution package and transfers the extracted write data to the CGW 13.
[0159] The CGW 13 has a data relay function, and when it acquires write data from the DCM 12, it instructs the rewrite target ECU, which is the target of rewriting the application program, to write the acquired write data and distributes the write data to the rewrite target ECU. Furthermore, when writing of the write data is completed in the rewrite target ECU and rewriting of the application program is completed, the CGW 13 instructs the rewrite target ECU to activate the rewrite target ECU, making the rewritten application program valid.
[0160] The master device 11 controls the vehicle-side program update function in the vehicle program rewriting system 1 and functions as an OTA master. While FIG. 37 illustrates a configuration in which the DCM 12 and the in-vehicle display 7 are connected to the same first bus 14, the DCM 12 and the in-vehicle display 7 may be connected to separate buses. The CGW 13 may have some or all of the functions of the DCM 12, or the DCM 12 may have some or all of the functions of the CGW 13. That is, the master device 11 is not limited to any particular functional division between the DCM 12 and the CGW 13. The master device 11 may be configured with two ECUs, the DCM 12 and the CGW 13, or may be configured with a single integrated ECU having the functions of the DCM 12 and the CGW 13.
[0161] In addition to the first bus 14, the second bus 15, the third bus 16, the fourth bus 17, and the fifth bus 18 are connected to the CGW 13 as buses inside the vehicle, and various ECUs 19 are connected via the buses 15 to 17, and the power management ECU 20 is connected via the bus 18.
[0162] The second bus 15 is, for example, a bus for a body system network. The ECU 19 connected to the second bus 15 is an ECU that controls the body system. Examples of ECUs that control the body system include a door ECU that controls door locking / unlocking, a meter ECU that controls the display on a meter display, an air conditioner ECU that controls the operation of an air conditioner, a window ECU that controls the opening and closing of windows, and a security ECU that operates to prevent the vehicle from being stolen.
[0163] The third bus 16 is, for example, a bus for a driving system network. The ECU 19 connected to the third bus 16 is an ECU that controls the driving system. Examples of ECUs that control the driving system include an engine ECU that controls the operation of the engine, a brake ECU that controls the operation of the brakes, an ECT (Electronic Controlled Transmission) ECU that controls the operation of the automatic transmission, and a power steering ECU that controls the operation of the power steering.
[0164] The fourth bus 17 is, for example, a bus for a multimedia network. The ECU 19 connected to the fourth bus 17 is an ECU that controls the multimedia system. The ECU that controls the multimedia system is, for example, a navigation ECU for controlling a navigation system, or an ETC ECU that controls an Electronic Toll Collection System (ETC, registered trademark). The buses 15 to 17 may be buses of a system other than a bus for a body system network, a bus for a driving system network, or a bus for a multimedia system network. Furthermore, the number of buses and the number of ECUs 19 are not limited to the configuration illustrated. The power management ECU 20 is an ECU that manages power supplied to the DCM 12, the CGW 13, the various ECUs 19, and the like.
[0165] A sixth bus 21 is connected to the CGW 13 as a bus outside the vehicle. A DLC (Data Link Coupler) connector 22 to which a tool 23 (corresponding to a service tool) is detachably connected is connected to the sixth bus 21. The buses 14 to 18 inside the vehicle and the bus 21 outside the vehicle are configured, for example, by a CAN (Controller Area Network, registered trademark) bus, and the CGW 13 performs data communication between the DCM 12, various ECUs 19, and the tool 23 in accordance with the CAN data communication standard and the diagnostic communication standard (UDS (Unified Diagnosis Services): ISO14229). Note that the DCM 12 and CGW 13 may be connected via Ethernet, and the DLC connector 22 and CGW 13 may be connected via Ethernet.
[0166] When the rewrite target ECU 19 receives write data from the CGW 13, it writes the received write data to a flash memory (corresponding to a non-volatile memory) to rewrite the application program. In the above configuration, when the CGW 13 receives a request to obtain write data from the rewrite target ECU 19, it functions as a reprogram master that distributes the write data to the rewrite target ECU 19. When the rewrite target ECU 19 receives write data from the CGW 13, it functions as a reprogram slave that writes the received write data to a flash memory to rewrite the application program.
[0167] There are two ways to rewrite an application program: via a wired connection and via a wireless connection. The way to rewrite an application program via a wired connection is to rewrite the rewrite target ECU 19 using an application program acquired via a wired connection from outside the vehicle. Specifically, when the tool 23 is connected to the DLC connector 22, the tool 23 transfers write data to the CGW 13. The CGW 13 functions as a gateway, transmits a wired rewrite request to the rewrite target ECU 19, instructs the rewrite target ECU 19 to write (install) the write data, and distributes the write data transferred from the tool 23 to the rewrite target ECU 19. Distributing the write data to the rewrite target ECU 19 means relaying the write data.
[0168] The mode of wirelessly rewriting an application program is a mode of rewriting the rewriting target ECU 19 using an application program wirelessly acquired from outside the vehicle. Specifically, when the DCM 12 downloads a distribution package from the file server 8, it extracts write data from the downloaded distribution package and transfers the write data to the CGW 13. The CGW 13 functions as a rewriting tool, instructs the rewriting target ECU 19 to write (install) the write data, and distributes the write data transferred from the DCM 12 to the rewriting target ECU 19.
[0169] The ECU 19 can be diagnosed via a wired connection or a wireless connection. The wired connection is a connection in which the ECU 19 is diagnosed via a wire from outside the vehicle. Specifically, when the tool 23 is connected to the DLC connector 22, the tool 23 transfers a diagnosis request to the CGW 13. The CGW 13 functions as a gateway, transmits the diagnosis request to the diagnosis target ECU 19, and distributes the diagnosis command transferred from the tool 23 to the diagnosis target ECU 19. The diagnosis target ECU 19 performs a diagnosis process in accordance with the diagnosis command received from the CGW 13.
[0170] The wireless diagnosis mode is a mode in which the ECU 19 is diagnosed wirelessly from outside the vehicle. Specifically, when a diagnostic command is transmitted from the center device 3 to the DCM 12 as a diagnostic request, the DCM 12 transfers the diagnostic command to the CGW 13. The CGW 13 functions as a gateway and distributes the diagnostic command as a diagnostic request to the diagnosis target ECU 19. The diagnosis target ECU performs diagnostic processing in accordance with the diagnostic command received from the CGW 13.
[0171] As shown in Figure 38, the CGW 13 has, as electrical functional blocks, a microcomputer (hereinafter referred to as "mc") 24, a data transfer circuit 25, a power supply circuit 26, and a power supply detection circuit 27. The mc 24 has a CPU (Central Processing Unit) 24a, a ROM (Read Only Memory) 24b, a RAM (Random Access Memory) 24c, and a flash memory 24d. The flash memory 24d includes a secure area in which information cannot be read from outside the CGW 13. The mc 24 executes various control programs stored in a non-transitory physical storage medium to perform various processes and control the operation of the CGW 13.
[0172] The data transfer circuit 25 controls data communication between the buses 14 to 18, 21 in accordance with the CAN data communication standard and the diagnostic communication standard. The power supply circuit 26 receives inputs of a battery power supply (hereinafter referred to as the +B power supply), an accessory power supply (hereinafter referred to as the ACC power supply), and an ignition power supply (hereinafter referred to as the IG power supply). The power supply detection circuit 27 detects the voltage values of the +B power supply, the ACC power supply, and the IG power supply input by the power supply circuit 26, compares these detected voltage values with predetermined voltage thresholds, and outputs the comparison results to the microcomputer 24. Based on the comparison results input from the power supply detection circuit 27, the microcomputer 24 determines whether the +B power supply, the ACC power supply, and the IG power supply supplied from the outside to the CGW 13 are normal or abnormal.
[0173] As shown in FIG. 39, the DCM 12 has, as electrical functional blocks, a microcomputer 28, a radio circuit 29, a data transfer circuit 30, a power supply circuit 31, and a power supply detection circuit 32. The microcomputer 28 has a CPU 28a, a ROM 28b, a RAM 28c, and a flash memory 28d. The flash memory 28d includes a secure area in which information cannot be read from outside the DCM 12. The microcomputer 28 executes various control programs stored in a non-transitory physical storage medium to perform various processes and control the operation of the DCM 12. The flash memory for saving data downloaded from the center device 3 may be located in the CGW 13.
[0174] The radio circuit 29 controls data communication with the center device 3 via the communication network 2. The data transfer circuit 30 controls data communication with the bus 14 in accordance with the CAN data communication standard. The power supply circuit 31 inputs the +B power supply, the ACC power supply, and the IG power supply. The power supply detection circuit 32 detects the voltage values of the +B power supply, the ACC power supply, and the IG power supply input by the power supply circuit 31, compares these detected voltage values with predetermined voltage thresholds, and outputs the comparison result to the microcomputer 28. Based on the comparison result input from the power supply detection circuit 32, the microcomputer 28 determines whether the +B power supply, the ACC power supply, and the IG power supply supplied from the outside to the DCM 12 are normal or abnormal.
[0175] Furthermore, the DCM 12 has a vehicle position detection function that detects the vehicle position using, for example, a GPS (Global Positioning System). The flash memory 28d of the DCM 12 has a sufficient memory capacity to store distribution packages downloaded from the center device 3, and has a larger memory capacity than the flash memory 24d of the CGW 13. In other words, because the flash memory 28d of the DCM 12 is configured to have a sufficient memory capacity, even if the flash memory 24d of the CGW 13 is not configured to have a sufficient memory capacity, the master device 11 can download distribution packages from the center device 3 and store the downloaded distribution packages in the DCM 12.
[0176] As shown in Figure 40, the ECU 19 has, as electrical functional blocks, a microcomputer 33, a data transfer circuit 34, a power supply circuit 35, and a power supply detection circuit 36. The microcomputer 33 has a CPU 28a, a ROM 28b, a RAM 33c, and a flash memory 28d. The flash memory 28d includes a secure area in which information cannot be read from outside the ECU 19. The microcomputer 33 executes various control programs stored in a non-transitory physical storage medium to perform various processes and control the operation of the ECU 19.
[0177] The data transfer circuit 34 controls data communication between the buses 15 to 17 in accordance with the CAN data communication standard. The power supply circuit 35 receives inputs of the +B power supply, the ACC power supply, and the IG power supply. The power supply detection circuit 36 detects the voltage values of the +B power supply, the ACC power supply, and the IG power supply input by the power supply circuit 35, compares these detected voltage values with predetermined voltage thresholds, and outputs the comparison result to the microcomputer 33. The microcomputer 33 determines whether the +B power supply, the ACC power supply, and the IG power supply supplied from the outside to the ECU 19 are normal or abnormal based on the comparison result input from the power supply detection circuit 27. The ECUs 19 are basically configured the same, except for the loads, such as sensors and actuators, connected to them.
[0178] The in-vehicle display 7 has a configuration similar to that of the ECU 19 shown in Fig. 40. The power supply management ECU 20 has a configuration similar to that of the ECU 19 shown in Fig. 40. The power supply management ECU 20 is connected to a power supply control circuit 43, which will be described later, so as to be able to communicate data with it.
[0179] As shown in FIG. 41 , the power management ECU 20, CGW 13, and ECU 19 are connected to power supply lines: a +B power line 37, an ACC power line 38, and an IG power line 39. The +B power line 37 is connected to the positive electrode of a vehicle battery 40. The ACC power line 38 is connected to the positive electrode of the vehicle battery 40 via an ACC switch 41. When a user operates the ACC switch, the ACC switch 41 switches from off to on, and the output voltage of the vehicle battery 40 is applied to the ACC power line 38. The ACC operation is, for example, an operation of inserting the key into the socket and turning the key from the "OFF" position to the "ACC" position in a vehicle in which the key is inserted into a socket, or an operation of pressing the start button once in a vehicle in which the start button is pressed.
[0180] The IG power line 39 is connected to the positive electrode of the vehicle battery 40 via an IG switch 42. When the user performs an IG operation, the IG switch 42 switches from OFF to ON, and the output voltage of the vehicle battery 40 is applied to the IG power line 39. For example, in a vehicle where the key is inserted into a socket, the IG operation is an operation of inserting the key into the socket and turning it from the "OFF" position to the "ON" position, or in a vehicle where the start button is pressed, an operation of pressing the start button twice. The negative electrode of the vehicle battery 40 is grounded.
[0181] When both the ACC switch 41 and the IG switch 42 are off, only the +B power is supplied to the vehicle-side system 4. The state in which only the +B power is supplied to the vehicle-side system 4 is referred to as the +B power state. When the ACC switch 41 is on and the IG switch 42 is off, the ACC power and +B power are supplied to the vehicle-side system 4. The state in which the ACC power and +B power are supplied to the vehicle-side system 4 is referred to as the ACC power state. When both the ACC switch 41 and the IG switch 42 are on, the +B power, ACC power, and IG power are supplied to the vehicle-side system 4. The state in which the +B power, ACC power, and IG power are supplied to the vehicle-side system 4 is referred to as the IG power state. In addition to the above-mentioned power states, other power states may be considered, such as a power state that provides power suitable for wireless program updates.
[0182] The ECU 19 has different activation conditions depending on the power supply state, and is classified into +B power supply system ECUs that activate in the +B power supply state, ACC system ECUs that activate in the ACC power supply state, and IG system ECUs that activate in the IG power supply state. For example, an ECU 19 that is operated for purposes such as vehicle theft prevention is classified as a +B power supply system ECU. An ECU 19 that is operated for non-driving purposes such as audio is classified as an ACC system ECU. An ECU 19 that is operated for driving purposes such as engine control is classified as an IG system ECU.
[0183] The +B power supply system ECU is connected to +B power supply line 37, ACC power supply line 38, and IG power supply line 39, and is configured to select +B power supply line 37 in the +B power supply state, select ACC power supply line 38 in the ACC power supply state, and select IG power supply line 39 in the IG power supply state. The ACC system ECU is connected to ACC power supply line 38 and IG power supply line 39, and is configured to select ACC power supply line 38 in the ACC power supply state, and select IG power supply line 39 in the IG power supply state. The IG system ECU is connected to IG power supply line 39.
[0184] The CGW 13 transmits a wake-up request to an ECU 19 in a sleep state, thereby transitioning the ECU 19 to which the wake-up request was sent from the sleep state to the wake-up state. The CGW 13 also transmits a sleep request to an ECU 19 in an wake-up state, thereby transitioning the ECU 19 to which the sleep request was sent from the wake-up state to the sleep state. The CGW 13 can transition a specific ECU 19 to the wake-up state or the sleep state by, for example, varying the waveform of the signal transmitted to the buses 15 to 17. That is, the wake-up request waveform and the sleep request waveform are predetermined for each ECU 19. When an ECU 19 receives a wake-up request waveform that suits it, it transitions from the sleep state to the wake-up state, and when an ECU 19 receives a sleep request waveform that suits it from the CGW 13, it transitions from the wake-up state to the sleep state.
[0185] For example, when the ECU (ID1) and the ECU (ID2) are in an activated state, the CGW 13 transmits a first waveform to cause the ECU (ID1) to transition from the activated state to a sleep state and maintain the ECU (ID2) in an activated state.Further, when the ECU (ID1) and the ECU (ID2) are in an activated state, the CGW 13 transmits a second waveform to maintain the ECU (ID1) in an activated state and cause the ECU (ID2) to transition from the activated state to a sleep state.
[0186] A power supply control circuit 43 is connected in parallel to the ACC switch 41 and the IG switch 42. The CGW 13 transmits a power supply control request to the power supply management ECU 20, causing the power supply management ECU 20 to control the power supply control circuit 43. That is, the CGW 13 transmits a power supply activation request as a power supply control request to the power supply management ECU 20, thereby connecting the ACC power line 38 and the IG power line 39 to the positive electrode of the vehicle battery 40 within the power supply control circuit 43. In this state, even if the ACC switch 41 and the IG switch 42 are off, the ACC power and the IG power are supplied to the vehicle-side system 4. Furthermore, the CGW 13 transmits a power supply stop request as a power supply control request to the power supply management ECU 20, thereby disconnecting the ACC power line 38, the IG power line 39, and the positive electrode of the vehicle battery 40 within the power supply control circuit 43.
[0187] The DCM 12, CGW 13, ECU 19, and power management ECU 20 each have a power self-holding circuit and a power self-holding function that maintains the power supply from the vehicle battery 40. That is, when the vehicle power supply switches from the ACC power supply or the IG power supply to the +B power supply while the DCM 12, CGW 13, and ECU 19 are in an activated state, the DCM 12, CGW 13, and ECU 19 do not immediately transition from the activated state to a stopped state or a sleep state after the switch, but instead maintain the activated state for a predetermined time (e.g., several minutes) using the power supply from the vehicle battery 40 to self-hold the drive power. The DCM 12, CGW 13, ECU 19, and power management ECU 20 transition from the activated state to a stopped state or a sleep state after a predetermined time has elapsed since the vehicle power supply switched from the ACC power supply or the IG power supply to the +B power supply. For example, in the case of ECU 19 of an engine control system, the power self-holding function is activated after the vehicle power supply switches from the ACC power supply or the IG power supply to the +B power supply, and various data related to engine control acquired while the vehicle was running are stored as a log.
[0188] Next, a description will be given of a distribution package distributed from the center device 3 to the master device 11. As shown in FIG. 41, in the vehicle program rewriting system 1, reprogramming data is generated from programming data provided by a supplier, which is a provider of an application program, and reprogramming specification data (corresponding to specification data) provided by the OEM. The reprogramming specification data may be generated by the center device 3. The programming data provided by the supplier includes differential data corresponding to the difference between the old application program and the new application program, and all data corresponding to the entire new application program. The differential data and all data may be compressed using a well-known data compression technique. FIG. 42 illustrates an example in which differential data is provided as programming data from suppliers A to C, and reprogramming data is generated from the encrypted differential data and authenticator of the ECU (ID1) provided by supplier A, the encrypted differential data and authenticator of the ECU (ID2) provided by supplier B, the encrypted differential data and authenticator of the ECU (ID3) provided by supplier C, and the reprogramming specification data provided by the OEM.
[0189] The authenticator is data that is assigned to each write data to verify the integrity of the differential data, and is generated from, for example, an ECU (ID), key information associated with the ECU (ID), and the differential data. Here, in case the rewrite of the application program is canceled midway, write data for writing back (rollback) to the old version may be included in the rewrite data.
[0190] The rewrite specification data provided by the OEM includes information related to the rewriting of the application program, such as information for identifying the ECU 19 to be rewritten, information for identifying the rewrite order when there are multiple ECUs 19 to be rewritten, and information for identifying a rollback method (described later). The rewrite specification data is data that defines operations related to rewriting in the DCM 12, CGW 13, ECU 19 to be rewritten, etc. The rewrite specification data is divided into rewrite specification data for the DCM used by the DCM 12 and rewrite specification data for the CGW used by the CGW 13.
[0191] As shown in FIG. 43, the rewrite specification data for the DCM includes specification data information and ECU information. The specification data information includes address information and a file name. The ECU information includes address information and the like referenced when transmitting the update program (write data) for each rewrite target ECU 19 to the CGW 13, the number of pieces of information corresponding to the number of rewrite target ECUs 19. Specifically, the ECU information includes at least an ID (ECU(ID)) for identifying the ECU, a reference address when acquiring the update program (update program acquisition address), the update program size, a reference address when acquiring the rollback program (rollback program acquisition address), and the rollback program size. The rollback program is a program (write data) for restoring the application program to its original version when rewriting of the application program is canceled midway.
[0192] As shown in FIG. 44, the rewrite specification data for the CGW includes group information, a bus load table, a battery load, a vehicle state at the time of rewrite, and ECU information. The rewrite specification data for the CGW may also include rewrite procedure information, display scene information, and the like. The group information indicates the group to which the ECU 19 to be rewritten belongs and the rewrite order. For example, first group information specifies that the application programs are to be rewritten in the order of ECU (ID1), ECU (ID2), and ECU (ID3), and second group information specifies that the application programs are to be rewritten in the order of ECU (ID4), ECU (ID5), and ECU (ID6). The bus load table is a table shown in FIG. 136, which will be described later in detail. The battery load is information indicating the lower limit of the remaining battery capacity of the vehicle battery 40 that is allowable in the vehicle. The vehicle state at the time of rewrite is information indicating the vehicle state under which rewrite is performed.
[0193] The ECU information is information about the ECU 19 to be rewritten, and includes at least the ECU_ID (corresponding to device identification information), the connection bus (corresponding to bus identification information), the connected power supply, the security access key information, the memory type, the rewriting method, the power supply self-holding time, the rewriting surface information, the update program version, the update program acquisition address, the update program size, the rollback program version, the rollback program acquisition address, the rollback program size, and the write data type.
[0194] The connection bus indicates the bus to which the ECU 19 is connected. The connection power source indicates the power line to which the ECU 19 is connected. The security access key information indicates key information used by the CGW 13 for authentication when accessing the rewrite target ECU 19, and includes a random value or unique information, a key pattern, and a decryption operation pattern. The memory type indicates whether the memory installed in the rewrite target ECU 19 is a single-plane stand-alone memory, a single-plane suspend memory (also called a pseudo-dual-plane memory), or a dual-plane memory. The rewrite method indicates whether the rewrite is by power self-holding or by power control. The power self-holding time indicates the time for which power self-holding continues when the rewrite method is power self-holding. The rewrite side information indicates which side is the operational side and which side is the non-operational side. The operational side is also called the startup side, and the non-operational side is also called the rewrite side.
[0195] The update program version indicates the version of the update program. The update program acquisition address indicates the address of the update program. The update program size indicates the data size of the update program. The rollback program version indicates the version of the rollback program. The rollback program acquisition address indicates the address of the rollback program. The rollback program size indicates the data size of the rollback program. The write data type indicates whether the write data is differential data or all data. In addition to this information, the rewrite specification data can also include information that is uniquely defined by the system.
[0196] When the DCM 12 acquires the rewrite specification data for the DCM, the DCM 12 analyzes the acquired rewrite specification data for the DCM. After analyzing the rewrite specification data for the DCM, the DCM 12 acquires write data from an address where an update program for the ECU 19 to be rewritten is stored, and controls operations related to the rewrite, such as transferring the acquired write data to the CGW 13.
[0197] When the CGW 13 acquires the rewrite specification data for the CGW, the CGW 13 analyzes the acquired rewrite specification data for the CGW. After analyzing the rewrite specification data for the CGW, the CGW 13 controls operations related to the rewrite, such as requesting the DCM 12 to transfer a predetermined size of an update program for the rewrite target ECU 19 according to the analysis result, and delivering the write data to the rewrite target ECU 19 in a specified order.
[0198] The file server 8 registers the above-mentioned re-program data as well as distribution specification data provided by the OEM. The distribution specification data provided by the OEM is data that defines operations related to the display of various screens on the display terminal 5. As shown in Fig. 45, the distribution specification data includes language information, display wording, package information, image data, display patterns, a display control program, etc.
[0199] When the display terminal 5 acquires the distribution specification data from the CGW 13, it analyzes the acquired distribution specification data and controls the display of various screens according to the analysis results. For example, the display terminal 5 superimposes display text acquired from the distribution specification data on a display frame stored in advance, or executes a display control program acquired from the distribution specification data. In addition to this information, the distribution specification data can also include information uniquely defined by the system.
[0200] When the reprogram data and distribution specification data are registered, the file server 8 encrypts the registered reprogram data and generates a distribution package that stores a package authenticator for authenticating the package, the encrypted reprogram data, and the distribution specification data. The authenticator is data assigned to verify the integrity of the reprogram data and distribution specification data, and is generated, for example, from key information associated with the CGW 13, the reprogram data, and the distribution specification data. When the file server 8 receives a download request for a distribution package from an external device, it transmits the distribution package to the DCM 12. Note that FIG. 42 illustrates an example in which the file server 8 generates a distribution package that stores the reprogram data and the distribution specification data and transmits the reprogram data and the distribution specification data simultaneously to the DCM 12 as a single file. However, the reprogram data and the distribution specification data may be transmitted to the DCM 12 as separate files. That is, the file server 8 may transmit the distribution specification data to the DCM 12 first, and then transmit the reprogram data to the DCM 12 later. In this case, it is advisable to assign an authenticator to each of the distribution specification data and the re-log data.
[0201] As shown in Figure 46, when the DCM 12 downloads a distribution package from the file server 8, it verifies the integrity of the encrypted reprogram data using the package authenticator stored in the downloaded distribution package. If the verification result is positive, the DCM 12 decrypts the encrypted reprogram data. After decrypting the encrypted reprogram data, the DCM 12 unpacks (hereinafter also referred to as unpackaging) the decrypted reprogram data and divides and extracts the encrypted difference data and authenticator, rewrite specification data for the DCM, and rewrite specification data for the CGW. Figure 46 illustrates an example in which the encrypted difference data and authenticator for ECU (ID1), the encrypted difference data and authenticator for ECU (ID2), the encrypted difference data and authenticator for ECU (ID3), rewrite specification data for the DCM, and rewrite specification data for the CGW are divided and extracted.
[0202] Next, the flash memory 33d of the ECU 19 will be described with reference to Figures 47 to 58. Depending on the memory configuration, the flash memory 33d of the ECU 19 can be classified into a single-plane independent memory having one flash plane, a single-plane suspend memory having two pseudo-planes, or a dual-plane memory having two actual planes. Hereinafter, an ECU 19 equipped with a single-plane independent memory will be referred to as a single-plane independent memory ECU, an ECU 19 equipped with a single-plane suspend memory will be referred to as a single-plane suspend memory ECU, and an ECU 19 equipped with a dual-plane memory will be referred to as a dual-plane memory ECU.
[0203] Single-plane independent memory has a configuration with one flash plane, so there is no concept of an operational side and a non-operational side, and the application program cannot be rewritten while it is running. On the other hand, single-plane suspend memory and dual-plane memory have a configuration with two flash planes, so there is a concept of an operational side and a non-operational side, and the application program on the non-operational side can be rewritten while the application program on the operational side is running. Dual-plane memory has two completely separate flash planes, so the application program can be rewritten at any time, such as while the vehicle is moving. Single-plane suspend memory has a configuration in which a single-plane independent memory is virtually divided into two planes, so there are restrictions on when reading and writing can be done normally, so the application program cannot be rewritten while the vehicle is moving, but it can be rewritten while the vehicle is parked with the IG power turned off.
[0204] Furthermore, the single-sided standalone memory, single-sided suspend memory, and dual-sided memory are each available in two types: a reprogramming firmware built-in type (hereinafter referred to as the built-in type), in which reprogramming firmware is built in, and a reprogramming firmware download type (hereinafter referred to as the download type), in which reprogramming firmware is downloaded from an external device. Reprogramming firmware is firmware for rewriting application programs.
[0205] The configuration of each flash memory will be explained below in order. (A) Single memory (A-1) Embedded single-sided memory The embedded single-sided standalone memory will be described with reference to Figures 47 and 48. The embedded single-sided standalone memory has a difference engine work area, an application program area, and a boot program area. The application program area contains version information, parameter data, an application program, firmware, and a normal vector table. The boot area contains a boot program, progress status point 2, progress status point 1, boot determination information, wireless reprogram firmware, wired reprogram firmware, a boot determination program, and a boot vector table.
[0206] As shown in Figure 47, during normal operation when executing application processing such as vehicle control processing and diagnostic processing, the microcontroller 33 executes a startup determination program, searches for the starting address by referring to the boot vector table and the normal vector table, and executes a specified address of the application program.
[0207] During a rewrite operation to rewrite an application program, the microcomputer 33 executes wireless or wired reprogramming firmware instead of the application program. Figure 48 shows the operation of rewriting an application program using difference data as an update program. As shown in Figure 48, the microcomputer 33 temporarily saves the application program as old data in the difference engine work area. The microcomputer 33 reads the old data temporarily saved in the difference engine work area and restores new data from the read old data and the difference data stored in RAM 33c using a difference engine included in the built-in reprogramming firmware. After generating new data from the old data and the difference data, the microcomputer 33 writes the new data to a specified address in memory and rewrites the application program.
[0208] (A-2) Downloadable single-sided memory The download-type single-sided independent memory will be described with reference to Figures 49 and 50. The download-type differs from the embedded type described above in that wireless reprogramming firmware or wired reprogramming firmware is downloaded from an external device, and after the application program is rewritten, the wireless reprogramming firmware or wired reprogramming firmware is deleted. When updating the application program wirelessly, for example, the wireless reprogramming firmware to be executed by each ECU 19 is included in the reprogramming data shown in Figure 42. The ECU 19 receives the wireless reprogramming firmware for its own ECU from the CGW 13 and stores the received wireless reprogramming firmware for its own ECU in RAM.
[0209] As shown in Figure 49, during normal operation when executing application processing such as vehicle control processing and diagnostic processing, the microcontroller 33 executes a startup determination program, similar to the embedded type, searches for the starting address by referring to the boot vector table and the normal vector table, and executes a specified address of the application program.
[0210] 50, during a rewrite operation in which the microcomputer 33 executes a rewrite process for an application program, the microcomputer 33 temporarily saves the application program as old data in a difference engine work area. The microcomputer 33 reads the old data temporarily saved in the difference engine work area, and restores new data from the read old data and the difference data stored in RAM 33c using a difference engine included in reprogramming firmware downloaded from an external device. The microcomputer 33 generates new data from the old data and the difference data, then writes the new data and rewrites the application program.
[0211] (B) 1-side suspend memory (B-1) Embedded single-plane suspend memory The embedded single-plane suspend memory will be described with reference to Figures 51 and 52. The embedded single-plane suspend memory has a difference engine work area, an application program area, and a boot program area. The reprogramming firmware that performs program updates is located in the boot program area, just like in single-plane standalone memory, and is not subject to program updates. The application program area that is subject to program updates has pseudo-sides A and B, and sides A and B each contain version information, an application program, and a normal vector table. The boot area contains a boot program, reprogramming firmware, a reprogramming vector table, a boot plane determination function, boot plane determination information, and a boot vector table.
[0212] As shown in FIG. 51, during normal operation when executing application processing such as vehicle control processing and diagnostic processing, the microcomputer 33 executes a boot program and uses a boot side determination function to determine which of side A and side B is the operational side from the boot side determination information for side A and side B. When the microcomputer 33 determines that side A is the operational side, it references the normal mode vector table for side A to search for the start address and executes the application program for side A. Similarly, when the microcomputer 33 determines that side B is the operational side, it references the normal mode vector table for side B to search for the start address and executes the application program for side B. Note that while the reprogramming firmware is located in the boot program area in FIG. 51, the reprogramming firmware may also be subject to program updates and may be located in either the A or B side area.
[0213] As shown in Figure 52, during a rewrite operation in which the microcomputer 33 executes a rewrite process for the application program on the non-operational side, the microcomputer 33 temporarily saves the application program on the non-operational side as old data in a difference engine work area. The microcomputer 33 reads the old data temporarily saved in the difference engine work area and restores new data from the read old data and the difference data stored in RAM 33c using a difference engine in the built-in reprogramming firmware. After generating new data from the old data and the difference data, the microcomputer 33 writes the new data to the non-operational side to rewrite the application program on the non-operational side. Figure 52 illustrates a case in which side A is the operational side and side B is the non-operational side.
[0214] (B-2) Downloadable single-sided suspend memory The download type single-surface suspend memory will be described with reference to Figures 53 and 54. The download type differs from the built-in type described above in that the reprogramming firmware and the reprogramming vector table are downloaded from an external device, and after the application program is rewritten, the reprogramming firmware and the reprogramming vector table are deleted.
[0215] 53, during normal operation when executing application processing such as vehicle control processing and diagnostic processing, the microcomputer 33 executes a boot program, similar to an embedded type, and uses a boot side determination function to determine whether side A or side B is new or old based on the boot side determination information for each side, and determines which of side A or side B is the operational side. If the microcomputer 33 determines that side A is the operational side, it references the normal mode vector table for side A to search for the start address and executes the application program for side A. Similarly, if the microcomputer 33 determines that side B is the operational side, it references the normal mode vector table for side B to search for the start address and executes the application program for side B.
[0216] As shown in FIG. 54, during a rewrite operation in which the microcomputer 33 executes a rewrite process for an application program, the microcomputer 33 temporarily saves the application program on the non-operational side as old data in the difference engine work area. The microcomputer 33 reads the old data temporarily saved in the difference engine work area and restores new data from the read old data and the difference data stored in RAM 33c using the difference engine in the reprogram firmware downloaded from the outside. The microcomputer 33 generates new data from the old data and the difference data and writes the new data to rewrite the application program. FIG. 54 illustrates an example in which side A is the active side and side B is the non-operational side. In this way, with a single-side suspend memory, the application program on side A can be executed while the application program on side B is rewritten in the background.
[0217] (C) 2-sided memory (C-1) Built-in dual-sided memory An embedded dual-sided memory will be described with reference to Figures 55 and 56. An embedded single-sided memory has an application program area and a rewrite program area on side A, and an application program area, a rewrite program area, and a boot program area on side B. A boot program is placed in the boot area as a non-rewritable program. The boot program includes a boot swap function and a boot vector table. Each application program area contains version information, parameter data, an application program, firmware, and a normal vector table. Each rewrite program area contains a program for controlling rewriting, reprogramming progress management information 2, reprogramming progress management information 1, boot side determination information, wireless reprogramming firmware, wired reprogramming firmware, and a boot vector table. The boot area contains a boot program, a boot swap function, and a boot vector table.
[0218] 55, during normal operation when executing application processing such as vehicle control processing and diagnostic processing, and during rewrite operation when executing rewrite processing of an application program on the non-operational side, the microcomputer 33 executes a boot program and uses a boot swap function to determine whether side A or side B is the new or old side based on the boot side determination information for each side, and determines which of side A and side B is the operational side. When the microcomputer 33 determines that side A is the operational side, it references the boot time vector table of side A and the normal time vector table of side A to search for a starting address and executes the application program on side A. Similarly, when the microcomputer 33 determines that side B is the operational side, it references the boot time vector table of side B and the normal time vector table of side B to search for a starting address and executes the application program on side B.
[0219] As shown in FIG. 56, during a rewrite operation in which the microcomputer 33 executes a rewrite process for the application program on the non-operational side, the microcomputer 33 temporarily saves the application program on the non-operational side as old data in the difference engine work area. The microcomputer 33 reads the old data temporarily saved in the difference engine work area and, using the difference engine in the built-in reprogramming firmware, restores new data from the read old data and the difference data stored in the RAM 33c. The microcomputer 33 generates new data from the old data and the difference data and writes the new data to the non-operational side to rewrite the application program on the non-operational side. Note that the old data temporarily saved in the difference engine work area may be for the application program on the operational side or for the application program on the non-operational side. In this case, if the application program on the operational side is the application program, the data on the non-operational side is erased before writing the new data. Here, if the reprogramming data acquired from outside the vehicle is not difference data but full data, the acquired reprogramming data is written to the non-operational side as new data. 56 illustrates an example in which side A is the operational side and side B is the non-operational side. Note that the old data temporarily saved to the difference engine work area may be for application programs on the operational side or for application programs on the non-operational side. If it is necessary to match the execution addresses of the application programs, the application programs on the non-operational side are saved as old data.
[0220] (C-2) Downloadable two-sided memory The download type dual-sided memory will be described with reference to Figures 57 and 58. The download type differs from the embedded type described above in that wireless reprogramming firmware or wired reprogramming firmware is downloaded from an external device, and after the application program is rewritten, the wireless reprogramming firmware or wired reprogramming firmware is deleted.
[0221] As shown in FIG. 57, during normal operation in which application processing such as vehicle control processing and diagnostic processing is performed, and during rewrite operation in which rewrite processing of the application program on the non-operational side is performed, the microcontroller 33 executes the boot program and determines whether it is new or old based on the boot side determination information for side A and side B using the boot swap function, as with the embedded type, determines which of side A and side B is the operational side, and executes the application program on the operational side to perform application processing.
[0222] As shown in FIG. 58, during a rewrite operation in which the microcomputer 33 executes a rewrite process for an application program, the microcomputer 33 temporarily saves the application program on the non-operational side as old data in the differential engine work area. The microcomputer 33 reads the old data temporarily saved in the differential engine work area and restores new data from the read old data and the differential data stored in the RAM 33c by the reprogramming firmware downloaded from the outside. The microcomputer 33 generates new data from the old data and the differential data and writes the new data to the non-operational side to rewrite the application program on the non-operational side. Note that the old data temporarily saved in the differential engine work area may be for the application program on the operational side or for the application program on the non-operational side. In this case, if the application program on the operational side is targeted, the data on the non-operational side is erased before writing the new data. Here, if the reprogramming data acquired from outside the vehicle is not differential data but full data, the acquired reprogramming data is written to the non-operational side as new data. FIG. 58 illustrates an example in which side A is the operational side and side B is the non-operational side. The old data temporarily saved in the difference engine work area may be for the application program on the operational side or for the application program on the non-operational side. In this way, with dual-side memory, the application program on side A can be executed while the application program on side B is rewritten in the background.
[0223] As described above, in both the embedded and download configurations, an application program and a rewrite program for rewriting the application program are placed in each application area. While FIGS. 56 and 58 show the application program as being subject to reprogramming, the rewrite program may also be subject to reprogramming. If it is desired to make the rewrite program unrewritable, the rewrite program may be placed in the boot area. For example, a program for wired rewriting may be placed in the boot area so that wired rewriting can be reliably performed via tool 23 at a dealer or the like.
[0224] Next, the overall sequence for rewriting an application program will be described with reference to Figs. 59 to 61. Here, a case where a user operates the mobile terminal 6 as the display terminal 5 to rewrite an application program while the vehicle is parked will be described. However, the same applies to a case where an application program is rewritten by operating the in-vehicle display 7 while the vehicle is parked. The distribution package transmitted from the center device 3 to the DCM 12 stores write data for one or more rewrite target ECUs 19. That is, if there is one rewrite target ECU 19, the distribution package stores one write data for that one rewrite target ECU 19. If there are multiple rewrite target ECUs 19, the distribution package stores multiple write data for each of the multiple rewrite target ECUs 19. Here, there are two rewrite target ECUs 19, and the two rewrite target ECUs 19 are referred to as rewrite target ECU (ID1) and rewrite target ECU (ID2). Moreover, ECUs 19 other than the reprogramming target ECU (ID1) and the reprogramming target ECU (ID2) are referred to as other ECUs.
[0225] When the rewrite target ECU (ID1) and the rewrite target ECU (ID2) determine that they have received a request to transmit a version notification signal from the master device 11, they each determine that a condition for transmitting a version notification signal has been met. When the condition for transmitting a version notification signal has been met, the rewrite target ECU (ID1) transmits a version notification signal to the master device 11, the version notification signal including version information of the application program stored therein and an ECU (ID) that can identify the rewrite target ECU. When the master device 11 receives a version notification signal from the rewrite target ECU (ID1), it transmits the received version notification signal to the center device 3. Similarly, when the condition for transmitting a version notification signal has been met, the rewrite target ECU (ID2) transmits a version notification signal to the master device 11, the version notification signal including information on the version of the application program stored therein and an ECU (ID) that can identify the rewrite target ECU. When the master device 11 receives a version notification signal from the rewrite target ECU (ID2), it transmits the received version notification signal to the center device 3.
[0226] When the center device 3 receives the version notification signals from the rewrite target ECU (ID1) and the rewrite target ECU (ID2), it identifies the version and ECU (ID) of the application program included in the received version notification signals, and determines whether there is write data to be distributed to the rewrite target ECU 19 that is the sender of the version notification signals. The center device 3 identifies the current version of the application program of the rewrite target ECU 19 from the version notification signals received from the rewrite targets, and compares the current version of the application program with the latest version it manages.
[0227] If the version identified from the version notification signal has the same value as the latest version under its management, the center device 3 determines that there is no write data to be distributed to the rewrite target ECU 19 that is the sender of the version notification signal, and that there is no need to update the application program stored in the rewrite target ECU 19. On the other hand, if the version identified from the version notification signal has a smaller value than the latest version under its management, the center device 3 determines that there is write data to be distributed to the rewrite target ECU 19 that is the sender of the version notification signal, and that there is a need to update the application program stored in the rewrite target ECU 19.
[0228] When the center device 3 determines that the application program stored in the rewrite target ECU 19 needs to be updated, it notifies the mobile terminal 6 that the update is needed. When the mobile terminal 6 is notified that the update is needed, it displays a delivery availability screen (A1). The delivery availability screen is the same as a campaign notification screen, which will be described later. The user can confirm that the update is needed from the delivery availability screen displayed on the mobile terminal 6, and can select whether or not to update.
[0229] When the user selects to update on the mobile terminal 6 (A2), the mobile terminal 6 notifies the center device 3 of a download request for the distribution package. When the center device 3 receives the download request for the distribution package from the mobile terminal 6, it transmits the distribution package to the master device 11.
[0230] When the master device 11 downloads a distribution package from the center device 3, it starts a package authentication process for the downloaded distribution package (B1). The master device 11 authenticates the distribution package, and when the package authentication process is complete, it starts a write data extraction process (B2). The master device 11 extracts the write data from the distribution package, and when the write data extraction process is complete, it transmits a download completion notification signal to the center device 3.
[0231] When the center device 3 receives the download completion notification signal from the master device 11, it notifies the mobile terminal 6 of the completion of the download. When the mobile terminal 6 is notified of the completion of the download from the center device 3, it displays a download completion notification screen (A3). The user can confirm that the download has been completed from the download completion notification screen displayed on the mobile terminal 6, and can set the start time for rewriting the application program on the vehicle side.
[0232] When the user sets the rewrite start time for the application program on the vehicle side on the mobile terminal 6 (A4), the mobile terminal 6 notifies the center device 3 of the rewrite start time. When the center device 3 is notified of the rewrite start time from the mobile terminal 6, it stores the rewrite start time set by the user as the set start time. When the current time reaches the set start time (A5), the center device 3 transmits a rewrite instruction signal to the master device 11.
[0233] When the master device 11 receives a rewrite instruction signal from the center device 3, it sends a power startup request to the power management ECU 20, and transitions the rewrite target ECU (ID1), the rewrite target ECU (ID2), and other ECUs from a stopped state or a sleep state to an activated state (X1).
[0234] The master device 11 starts distributing write data to the rewrite target ECU (ID1) and instructs the rewrite target ECU (ID1) to write the write data. The rewrite target ECU (ID1) starts receiving the write data from the master device 11, and when instructed to write the write data, starts writing the write data and starts the program rewrite process (C1). When the rewrite target ECU (ID1) completes receiving the write data from the master device 11, completing the writing of the write data, and completing the program rewrite process, it transmits a rewrite completion notification signal to the master device 11.
[0235] When the master device 11 receives a rewrite completion notification signal from the rewrite target ECU (ID1), it starts distributing write data to the rewrite target ECU (ID2) and instructs the rewrite target ECU (ID2) to write the write data. The rewrite target ECU (ID2) starts receiving the write data from the master device 11, and when instructed to write the write data, starts writing the write data and starts the program rewrite process (D1). When the rewrite target ECU (ID2) completes receiving the write data from the master device 11, completes writing the write data, and completes the program rewrite process, it transmits a rewrite completion notification signal to the master device 11. When the master device 11 receives the rewrite completion notification signal from the rewrite target ECU (ID2), it transmits the rewrite completion notification signal to the center device 3.
[0236] When the center device 3 receives a rewrite completion notification signal from the master device 11, it notifies the mobile terminal 6 that rewriting of the application program has been completed. When the mobile terminal 6 is notified by the center device 3 that rewriting of the application program has been completed, it displays a rewrite completion notification screen (A6). The user can confirm that rewriting of the application program has been completed from the rewrite completion notification screen displayed on the mobile terminal 6, and can set the execution of synchronization as activation.
[0237] When the user sets the execution of synchronization on the mobile terminal 6 (A7), that is, when the user sets consent to the activation of the new program, the mobile terminal 6 notifies the center device 3 of the execution of synchronization. When the center device 3 is notified of the execution of synchronization from the mobile terminal 6, it transmits a synchronization switch instruction signal to the master device 11. When the master device 11 receives the synchronization switch instruction signal from the center device 3, it distributes the received synchronization switch instruction signal to the rewrite target ECU (ID1) and the rewrite target ECU (ID2).
[0238] When the rewrite target ECU (ID1) and the rewrite target ECU (ID2) receive the synchronous switching instruction signal from the master device 11, they each start a program switching process to switch the application program to be launched next from the old application program to the new application program (C2, D2). When the rewrite target ECU (ID1) and the rewrite target ECU (ID2) each complete the program switching process, they each transmit a switching completion notification signal to the master device 11.
[0239] When the master device 11 receives switching completion notification signals from the rewrite target ECU (ID1) and the rewrite target ECU (ID2), it distributes version read signals to the rewrite target ECU (ID1) and the rewrite target ECU (ID2). When the rewrite target ECU (ID1) and the rewrite target ECU (ID2) receive the version read signals from the master device 11, they read the versions of the application programs to be used thereafter (C3, D3) and transmit latest version notification signals including the read versions to the master device 11. By receiving the version notification signals from the rewrite target ECU (ID1) and the rewrite target ECU (ID2), the master device 11 checks the software versions and performs rollback if necessary.
[0240] When the master device 11 receives a version notification signal from the ECU (ID1) to be rewritten and the ECU (ID2) to be rewritten, it sends a power stop request to the power management ECU 20, and transitions the ECU (ID1), the ECU (ID2), and other ECUs from an activated state to a stopped state or a sleep state (X2).
[0241] The master device 11 transmits a latest version notification signal to the center device 3. When the center device 3 receives the latest version notification signal from the master device 11, it identifies the latest versions of the application programs of the rewrite target ECU (ID1) and the rewrite target ECU (ID2) from the received latest version notification signal, and notifies the mobile terminal 6 of the identified latest versions. When the mobile terminal 6 is notified of the latest version from the center device 3, it displays a latest version notification screen on the mobile terminal 6 indicating the notified latest version (A8). The user can check the latest version on the latest version notification screen displayed on the mobile terminal 6, and can confirm that activation has been completed.
[0242] Next, timing charts of the operations of the DCM 12, CGW 13, and rewrite target ECU 19 when rewriting an application program will be described with reference to Figures 62 to 65. Here, the case where the application program in the dual memory ECU is rewritten while the IG switch 42 is turned on by a user operation, i.e., while the vehicle is capable of running, and the case where the application program in the single suspend memory ECU and the single single memory ECU is rewritten while the vehicle is parked after the IG switch 42 is turned off by a user operation, will be described. Also, the case where the application program is rewritten by power supply control and the case where the application program is rewritten by power supply self-holding will be described.
[0243] (A) When rewriting an application program by power control Rewriting an application program by power control will be described with reference to Figures 62 and 63. Rewriting an application program by power control means a configuration in which the rewriting operation is controlled in response to switching of the power supply, without using a power supply self-holding circuit. When the user switches the IG switch from off to on, switching the vehicle power supply from the +B power supply to the IG power supply, the DCM 12, CGW 13, dual memory ECU, single suspend memory ECU, and single standalone memory ECU each begin normal operation (t1).
[0244] When the DCM 12 is notified by the center device 3 that the download has started, it transitions from normal operation to download operation and starts downloading the distribution package from the center device 3 (t2). The DCM 12 may download the distribution package in the background while performing normal operation. When the DCM 12 completes downloading the distribution package from the center device 3, it returns from download operation to normal operation (t3).
[0245] When the DCM 12 receives a rewrite instruction signal (installation instruction signal) from the center device 3 or CGW 13, it shifts from normal operation to data transfer / center communication operation and starts the data transfer / center communication operation (t4). That is, the DCM 12 extracts the write data from the distribution package and starts transferring the write data to the CGW 13, and also acquires the progress status of the rewrite from the CGW 13 and starts notifying the center device 3 of the progress status of the rewrite.
[0246] When the CGW 13 starts receiving write data from the DCM 12, it transitions from normal operation to reprogramming master operation, starts reprogramming master operation, starts distributing write data to the dual memory ECU, and instructs it to write the write data. When the dual memory ECU starts receiving write data from the CGW 13, it starts the programming phase (hereinafter also referred to as the installation phase) in normal operation. That is, the dual memory ECU installs the application program in the background while performing normal operation. The dual memory ECU starts writing the received write data to the flash memory, and starts rewriting the application program.
[0247] If the user switches the IG switch from on to off while the application program is being rewritten in the dual memory ECU, causing the vehicle power supply to switch from the IG power supply to the +B power supply, the DCM 12 will suspend data transfer / center communication operations, the CGW 13 will suspend reprogramming master operations, the dual memory ECU will suspend the install phase, and the rewriting of the application program will be suspended (t5).
[0248] Thereafter, when the user switches the IG switch from off to on and the vehicle power supply switches from the +B power supply to the IG power supply, the DCM 12 resumes data transfer / center communication operations, the CGW 13 resumes reprogramming master operations, and the dual memory ECU resumes the installation phase and rewrites the application program (t6). That is, when the user switches the IG switch from on to off and the vehicle power supply switches from the IG power supply to the +B power supply, and then when the user switches the IG switch from off to on and the vehicle power supply switches from the +B power supply to the IG power supply, the dual memory ECU repeatedly suspends and resumes rewriting the application program every time a trip occurs (t7, t8).
[0249] When the dual memory ECU has finished writing the write data and rewriting the application program, it ends the installation phase and transitions from normal operation to activation waiting. In other words, while the dual memory ECU is not performing the activation phase, it does not start up on the new side (side B) where the application program has been rewritten, but rather remains running on the old side (side A) (t9).
[0250] After the user switches the IG switch from on to off, switching the vehicle power supply from the IG power supply to the +B power supply (t10), if the dual memory ECU has completed rewriting the application program at that time, the CGW 13 sends a power startup request to the power management ECU 20. When the vehicle power supply switches from the +B power supply to the IG power supply as a result of the CGW 13 sending the power startup request to the power management ECU 20, the DCM 12 resumes data transfer / center communication operations, and the CGW 13 resumes reprogramming master operation and begins distributing write data to the single suspend memory ECU and the single single memory ECU. When the single suspend memory ECU and the single single memory ECU each begin receiving write data from the CGW 13, they transition from normal operation to boot processing and begin the installation phase of the boot processing (t11). That is, the single suspend memory ECU and the single single memory ECU do not perform installation in parallel with normal operation, but perform installation during boot processing when the application program is not running.
[0251] When a single-plane suspend memory ECU starts rewriting an application program, it suspends the rewriting of the application program if the user switches the IG switch 42 from off to on before the rewriting of the application program is completed. The single-plane suspend memory ECU resumes rewriting of the application program using the active plane (A plane) as the startup plane, rather than the inactive plane (B plane) where the rewriting of the application program was suspended. When a single-plane single memory ECU starts rewriting of the application program, it continues rewriting of the application program even if the user switches the IG switch 42 from off to on before the rewriting of the application program is completed. This is because a single-plane single memory ECU cannot resume normal operation if the rewriting of the application program is suspended midway. Preferably, after rewriting of the application program of the single-plane single memory ECU starts, user operation of the IG switch 42 is disabled until the rewriting of the application program is completed.
[0252] When the single-surface suspend memory ECU has completed writing the write data and rewriting the application program, it ends the install phase of the boot process and transitions from boot process to activation wait. In other words, the single-surface suspend memory ECU does not start up on the new surface (surface B) where the application program has been rewritten, but remains activated on the old surface (surface A) until it is in the activation phase. When the single-surface standalone memory ECU has completed writing the write data and rewriting the application program, it ends the install phase of the boot process and transitions to activation wait (t12).
[0253] When the power management ECU 20 switches the vehicle power supply from the IG power supply to the +B power supply in response to an activate command from the CGW 13, the dual-plane memory ECU and single-plane suspend memory ECU each switch from the old plane to the new plane, start up on the new plane, and start the post-programming phase (hereinafter also referred to as the activate phase) when the new plane starts up. The single-plane memory ECU starts restarting, and starts the activate phase when restarted after installation is complete (t13, t14). During activation, it is confirmed that the new program starts up correctly and version information is notified to the CGW 13.
[0254] When activation is complete and the power management ECU 20 switches the vehicle power supply from the IG power supply to the +B power supply in response to an activation completion instruction from the CGW 13, the DCM 12 transitions from data transfer / center communication operation to sleep / stop operation and starts the sleep / stop operation. The CGW 13 transitions from reprogramming master operation to sleep / stop operation and starts the sleep / stop operation. The dual memory ECU, single suspend memory ECU, and single standalone memory ECU each transition from new startup to sleep / stop operation (t15).
[0255] After this, when the user switches the IG switch from off to on and the vehicle power supply switches from the +B power supply to the IG power supply, the dual-side memory ECU and single-side suspend memory ECU each start up the new application program using the new side (side B) as the start up side, and the single-side single memory ECU starts up the new application program (t16).
[0256] (a) When rewriting an application program using self-maintaining power Rewriting an application program using power supply self-holding will be described with reference to Figures 64 and 65. Rewriting an application program using power supply self-holding means controlling the rewrite operation using a power supply self-holding circuit. When the user switches the IG switch from off to on, switching the vehicle power supply from the +B power supply to the IG power supply, the DCM 12, CGW 13, dual memory ECU, single suspend memory ECU, and single standalone memory ECU each begin normal operation (t21).
[0257] When the DCM 12 is notified by the center device 3 that downloading has started, i.e., when it is notified that an update with a new program is available, it shifts from normal operation to downloading operation and starts downloading the distribution package from the center device 3 (t22). When the DCM 12 completes downloading the distribution package from the center device 3, it returns from downloading operation to normal operation (t23).
[0258] When the DCM 12 receives a rewrite instruction signal (installation instruction signal) from the center device 3 or CGW 13, it shifts from normal operation to data transfer / center communication operation and starts the data transfer / center communication operation (t24). That is, the DCM 12 extracts the write data from the distribution package and starts transferring the write data to the CGW 13, and also acquires the progress status of the rewrite from the CGW 13 and starts notifying the center device 3 of the progress status of the rewrite.
[0259] When the CGW 13 starts receiving write data from the DCM 12, it transitions from normal operation to reprogramming master operation, starts reprogramming master operation, starts distributing write data to the dual memory ECU, and instructs it to write the write data. When the dual memory ECU starts receiving write data from the CGW 13, it starts the programming phase (hereinafter also referred to as the installation phase) in normal operation. That is, the dual memory ECU installs the application program in the background while performing normal operation. The dual memory ECU starts writing the received write data to the flash memory, and starts rewriting the application program.
[0260] If the user switches the IG switch from on to off, causing the vehicle power supply to switch from the IG power supply to the +B power supply (t25) while the dual memory ECU is rewriting an application program, immediately after the vehicle power supply switches from the IG power supply to the +B power supply, the DCM 12 continues data transfer and center communication operations, the CGW 13 continues reprogramming master operations, and the dual memory ECU continues the installation phase and continues rewriting the application program. When a preset self-hold period elapses after the vehicle power supply switches from the IG power supply to the +B power supply, the DCM 12 suspends data transfer and center communication operations, the CGW 13 suspends reprogramming master operations, and the dual memory ECU suspends the installation phase and rewriting the application program (t26). That is, installation continues using power supplied from the vehicle battery 40 until a predetermined time has elapsed since the IG switch 42 was turned off.
[0261] Thereafter, when the user switches the IG switch from off to on, switching the vehicle power supply from the +B power supply to the IG power supply, the DCM 12 resumes data transfer / center communication operations, the CGW 13 resumes reprogramming master operation, and the dual memory ECU resumes the install phase and reprograms the application program (t27). That is, when the user switches the IG switch from on to off, switching the vehicle power supply from the IG power supply to the +B power supply, and then when the user switches the IG switch from off to on, switching the vehicle power supply from the +B power supply to the IG power supply, the dual memory ECU repeatedly suspends and resumes reprogramming of the application program every time a trip occurs (t28 to t30). However, until the self-holding period has elapsed since the vehicle power supply switched from the IG power supply to the +B power supply, the DCM 12 continues data transfer / center communication operations, the CGW 13 continues reprogramming master operation, and the dual memory ECU continues the install phase and reprograms the application program.
[0262] When the dual memory ECU has finished writing the write data and rewriting the application program, it ends the installation phase and transitions from normal operation to activation waiting. In other words, while the dual memory ECU is not performing the activation phase, it does not start up on the new side (side B) where the application program has been rewritten, but rather remains running on the old side (side A) (t31).
[0263] When the user switches the IG switch from on to off, the vehicle power supply switches from the IG power supply to the +B power supply. If the dual memory ECU has completed rewriting the application program at that point, the single suspend memory ECU and the single stand-alone memory ECU each transition from normal operation to boot processing, start the boot processing, and begin the installation phase of the boot processing (t32).
[0264] When the single-surface suspend memory ECU and the single-memory ECU have completed writing the write data and rewriting the application program, the installation phase of the boot process ends (t33). When the CGW 13 sends a power startup request to the power management ECU 20, the vehicle power source is switched from the +B power source to the IG power source, and the DCM 12 resumes data transfer / center communication operations (t34).
[0265] When the single-surface suspend memory ECU has completed writing the write data and rewriting the application program, it transitions from boot processing to waiting for activation. In other words, while the single-surface suspend memory ECU is not performing the activation phase, it does not start up on the new surface (surface B) where the application program has been rewritten, but remains running on the old surface (surface A). When the single-surface standalone memory ECU has completed writing the write data and rewriting the application program, it ends the install phase of the boot processing and enters waiting for activation (t35).
[0266] When the power management ECU 20 switches the vehicle power supply from the IG power supply to the +B power supply in response to an activation command from the CGW 13, the dual-side memory ECU and the single-side suspend memory ECU each switch from the old side to the new side, start up on the new side, and start the activation phase when the new side starts up. The single-side single-side memory ECU starts restarting, and starts the activation phase when restarted after the installation is complete (t36, t37).
[0267] When activation is complete and the power management ECU 20 switches the vehicle power supply from the IG power supply to the +B power supply in response to an activation completion instruction from the CGW 13, the DCM 12 transitions from data transfer / center communication operation to sleep / stop operation and starts the sleep / stop operation. The CGW 13 transitions from reprogramming master operation to sleep / stop operation and starts the sleep / stop operation. The dual memory ECU, single suspend memory ECU, and single standalone memory ECU each transition from new startup to sleep / stop operation (t38).
[0268] After this, when the user switches the IG switch from off to on and the vehicle power supply switches from the +B power supply to the IG power supply, the dual-side memory ECU and single-side suspend memory ECU each start up the new application program using the new side (side B) as the start up side, and the single-side single memory ECU starts up the new application program (t39).
[0269] The CGW 13 performs the following checks before downloading a distribution package from the center device 3 and before distributing the write data to the rewrite target ECU 19. Before downloading a distribution package from the center device 3, the CGW 13 checks the radio wave environment, the remaining battery charge of the vehicle battery 40, and the memory capacity of the DCM 12 to ensure that the download can be performed normally. Before distributing the write data to the rewrite target ECU 19, the CGW 13 checks the presence of personnel to prevent the installation environment from becoming unstable so that the write data can be distributed normally by detecting an intrusion sensor, door lock, curtain, and IG off, and also checks the version and whether an abnormality has occurred to determine whether the rewrite target ECU 19 is writable. In addition, the CGW 13 checks the write data to be delivered to the ECU 19 to be rewritten by performing tamper checks, access authentication, version checks, etc. before starting installation, and performs communication interruption checks, abnormality checks, etc. while the installation is in progress, and after completing the installation, performs version checks, integrity checks, DTC (Diagnostic Trouble Code, error code) checks, etc.
[0270] Next, the screens displayed by the display terminal 5 will be described with reference to Fig. 66 to Fig. 82. As shown in Fig. 66, in a configuration in which the application program of the rewrite target ECU 19 is rewritten by OTA, there are phases of campaign notification, download, installation, and activation. The campaign notification is a notice of a program update. For example, the campaign notification occurs when the master device 11 downloads distribution specification data and the like in response to the determination in the center device 3 that an application program update is available. The display terminal 5 displays a screen in each phase as the rewriting of the application program progresses. Here, the screens displayed by the in-vehicle display 7 will be described.
[0271] As shown in Fig. 67, in normal operation before a campaign notification is issued, the CGW 13 displays a navigation screen 501, such as a well-known route guidance screen, which is one of the navigation functions, on the in-vehicle display 7. When a campaign notification is issued from this state, the CGW 13 displays a campaign notification icon 501a, indicating the occurrence of a campaign notification, in the lower right corner of the navigation screen 501, as shown in Fig. 32. The user can recognize the occurrence of a campaign notification regarding an update of an application program by checking the display of the campaign notification icon 501a.
[0272] When the user operates the campaign notification icon 501a in this state, the CGW 13 pops up a campaign notification screen 502 on the navigation screen 501, as shown in FIG. 69. The CGW 13 is not limited to popping up the campaign notification screen 502, and may adopt other display modes. The CGW 13 notifies the user of the occurrence of a campaign notification by displaying, for example, a message such as "Software updates are available" on the campaign notification screen 502, and also displays a "Confirm" button 502a and a "Later" button 502b, and waits for a user operation. In this case, the user can proceed to the next screen for starting the rewriting of the application program by operating the "Confirm" button 502a. When the user operates the "Later" button 502b, the CGW 13 closes the pop-up display of the campaign notification screen 502 and returns to the screen displaying the campaign notification icon 501a shown in FIG. 32.
[0273] When the user operates the "Confirm" button 502a in this state, the CGW 13 switches the display from the navigation screen 501 to a download consent screen 503, as shown in FIG. 70, and displays the download consent screen 503 on the in-vehicle display 7. On the download consent screen 503, the CGW 13 notifies the user of the campaign ID and update name, displays a "Start Download" button 503a, a "Check Details" button 503b, and a "Back" button 503c, and waits for a user operation. In this case, the user can start the download by operating the "Start Download" button 503a, display the download details by operating the "Check Details" button 503b, and reject the download and return to the previous screen by displaying the "Back" button 503c. When the "Back" button 503c is operated, the user can proceed to a screen for starting the download by operating the campaign notification icon 501a.
[0274] When the user operates the "Check Details" button 503b while this download consent screen 503 is displayed, the CGW 13 switches the display content of the download consent screen 503 and displays download details on the in-vehicle display 7, as shown in FIG. 71. The CGW 13 uses the received distribution specification data to display the update details, such as the update content, the time required for the update, and vehicle function restrictions associated with the update. Furthermore, when the user operates the "Start Download" button 503a, the CGW 13 starts downloading the distribution package via the DCM 12. In parallel with starting the download of the distribution package, the CGW 13 switches the display from the download consent screen 503 to the navigation screen 501, as shown in FIG. 72, and displays the navigation screen 501 again on the in-vehicle display 7, displaying a download in progress icon 501b in the lower right corner of the navigation screen 501, indicating that the download is in progress. The user can understand that the download of the distribution package is in progress by checking the display of the download in progress icon 501b.
[0275] When the user operates the download in progress icon 501b in this state, the CGW 13 switches the display from the navigation screen 501 to a download in progress screen 504, as shown in Fig. 73, and displays the download in progress screen 504 on the in-vehicle display 7. On the download in progress screen 504, the CGW 13 notifies the user that a download is in progress, displays a "Check details" button 504a, a "Back" button 504b, and a "Cancel" button 504c, and waits for a user operation. In this case, the user can display details of the download in progress by operating the "Check details" button 504a, and can interrupt the download by operating the "Cancel" button 504c.
[0276] When the download is complete, the CGW 13 pops up a download completion notification screen 505 on the navigation screen 501, as shown in Fig. 74. On the download completion notification screen 505, the CGW 13 notifies the user of the completion of the download by displaying guidance such as "Download completed. Software update is now possible.", and also displays a "Confirm" button 505a and a "Later" button 505b, and waits for a user operation. In this case, the user can proceed to a screen for starting the installation by operating the "Confirm" button 505a.
[0277] When the user operates the "Confirm" button 505a in this state, the CGW 13 switches the display from the navigation screen 501 to an installation consent screen 506, as shown in FIG. 75, and displays the installation consent screen 506 on the in-vehicle display 7. On the installation consent screen 506, the CGW 13 notifies the user of the required time, restrictions, and schedule settings for the installation, displays an "Update Now" button 506a, a "Schedule and Update" button 506b, and a "Back" button 506c, and waits for a user operation. In this case, the user can start the installation immediately by operating the "Update Now" button 506a. Alternatively, the user can set the desired time for installation and schedule and start the installation by operating the "Schedule and Update" button 506b. Alternatively, the user can reject the installation and return to the previous screen by operating the "Back" button 506c. When the "Back" button 506c is operated, the user can proceed to a screen for starting the installation by operating the download in progress icon 501b.
[0278] When the user operates the "Update Now" button 506a in this state, the CGW 13 switches the display content of the installation consent screen 506 as shown in Fig. 76, and displays details of the installation on the in-vehicle display 7. In this installation consent screen 506, the CGW 13 accepts the installation request and notifies the user that the installation will begin.
[0279] When the installation starts, the CGW 13 switches the display from the installation consent screen 506 to the navigation screen 501, as shown in Fig. 77, causes the navigation screen 501 to be displayed again on the in-vehicle display 7, and displays an installation in progress icon 501c, which indicates that installation is in progress, in the lower right corner of the navigation screen 501. The user can understand that installation is in progress by checking the display of the installation in progress icon 501c.
[0280] When the user operates the installation in progress icon 501c in this state, the CGW 13 switches the display from the navigation screen 501 to the installation in progress screen 507 as shown in Fig. 78, and displays the installation in progress screen 507 on the in-vehicle display 7. The CGW 13 notifies the user that the installation is in progress on the installation in progress screen 507. The CGW 13 may also display, for example, the remaining time required for the installation and the progress percentage on the installation in progress screen 507.
[0281] When the installation is complete, the CGW 13 switches the display from the navigation screen 501 to an activation consent screen 508, as shown in FIG. 79, and displays the activation consent screen 508 on the in-vehicle display 7. On the activation consent screen 508, the CGW 13 notifies the user of the details of the activation, displays a "Back" button 508a and an "OK" button 508b, and waits for a user operation. In this case, the user can reject the activation and return to the previous screen by operating the "Back" button 508a. Alternatively, the user can accept the activation by operating the "OK" button 508b. Note that, even if the "Back" button 508a is operated, the user can proceed to a screen for executing the activation by operating the installation in progress icon 501c. Note that these displays and consents may be omitted depending on the user's settings or the program scene.
[0282] When the user turns on the IG power supply after operating the "OK" button 508b, the CGW 13 pops up an activation completion notification screen 509 on the navigation screen 501, as shown in FIG. 80. On the activation completion notification screen 509, the CGW 13 notifies the user of the completion of activation by displaying guidance such as "Software update completed," and also displays an "OK" button 509a and a "Confirm details" button 509b, and waits for a user operation. In this case, the user can dismiss the pop-up display of the activation completion notification screen 509 by operating the "OK" button 509a, and can display details of the completion of activation by operating the "Confirm details" button 509b.
[0283] When the user operates the "OK" button 509a in this state, the CGW 13 switches the display from the navigation screen 501 to a confirmation operation screen 510, as shown in Fig. 81, and displays the confirmation operation screen 510 on the in-vehicle display 7. On the confirmation operation screen 510, the CGW 13 notifies the user that activation has been completed, displays a "Check details" button 510a and an "OK" button 510b, and waits for a user operation. In this case, the user can display details of the completion of activation by operating the "Check details" button 510a.
[0284] When the user operates the "Confirm Details" button 510a in this state, the CGW 13 switches the display content of the confirmation operation screen 510 as shown in Fig. 82, and displays details of the completion of activation on the in-vehicle display 7. The CGW 13 displays the functions added or changed by the update as update details, and also displays the "OK" button 510b. When the user operates the "OK" buttons 509a, 510b, the CGW 13 determines that the user has confirmed the completion of the software update.
[0285] As described above, the vehicle-side system 4 controls each operation phase, such as campaign notification, download, installation, activation, and update completion, and presents a display to the user that corresponds to each operation phase. Note that, in the above description, the CGW 13 is configured to control the display, but the in-vehicle display 7 may be configured to receive the operation phase and distribution specification data from the CGW 13 and display it.
[0286] Next, characteristic processes performed by the vehicle program rewriting system 1 will be described with reference to Figures 83 to 269. The vehicle program rewriting system 1 performs the following characteristic processes. (1) Distribution package sending decision process (2) Download decision process for distribution packages (3) Write data transfer decision process (4) Write data acquisition determination process (5) Installation instruction determination process (6) Management of security access keys (7) Verification of written data (8) Data storage surface information transmission control process (9) Power management process for non-rewrite targets (10) File transfer control processing (11) Write data distribution control process (12) Activation request instruction processing (13) Activate execution control process (14) Group management process for rewriting (15) Rollback execution control process (16) Display control process for rewriting progress (17) Consistency check process for differential data (18) Rewrite execution control process (19) Session establishment process (20) Identifying retry points (21) Progress status synchronization control process (22) Display control information transmission control process (23) Display control information reception control process (24) Progress display screen control process (25) Program update notification control process (26) Power supply self-maintenance execution control process
[0287] The center device 3, the DCM 12, the CGW 13, the ECU 19, and the in-vehicle display 7 each have the following functional blocks as a configuration for performing the characteristic processes (1) to (26) described above.
[0288] As shown in FIG. 83, the center device 3 includes a distribution package transmitter 51. Upon receiving a download request for a distribution package from the DCM 12, the distribution package transmitter 51 transmits the distribution package to the DCM 12. In addition to the above-described configuration, the center device 3 also includes a distribution package transmission determination unit 52, a progress status synchronization control unit 53, a display control information transmission control unit 54, and a write data selection unit 55 (corresponding to an update data selection unit) as components for performing characteristic processing. Upon receiving data storage surface information from the master device 11, the write data selection unit 55 (corresponding to an update data selection unit) selects write data suitable for the non-operational surface based on the software version and operational surface identified by the received data storage surface information. That is, the distribution package transmitter 51 transmits a distribution package including the write data selected by the write data selection unit 55 to the DCM 12. Functional blocks that perform characteristic processing will be described later.
[0289] 84, the DCM 12 has a download request sending unit 61, a distribution package downloading unit 62, a write data extracting unit 63, a write data transferring unit 64, a rewrite specification data extracting unit 65, and a rewrite specification data transferring unit 66. The download request sending unit 61 sends a download request for a distribution package to the center device 3. The distribution package downloading unit 62 downloads the distribution package from the center device 3. When the distribution package downloading unit 62 downloads the distribution package from the center device 3, the write data extracting unit 63 extracts write data from the downloaded distribution package.
[0290] When the write data extraction unit 63 extracts write data from the distribution package, the write data transfer unit 64 transfers the extracted write data to the CGW 13. When the distribution package download unit 62 downloads a distribution package from the center device 3, the rewrite specification data extraction unit 65 extracts rewrite specification data from the downloaded distribution package. When the rewrite specification data extraction unit 56 extracts rewrite specification data from the distribution package, the rewrite specification data transfer unit 66 transfers the extracted rewrite specification data to the CGW 13. In addition to the above configuration, the DCM 12 has a distribution package download determination unit 67 and a write data transfer determination unit 68 as components that perform characteristic processing. The functional blocks that perform characteristic processing will be described later.
[0291] As shown in Figures 85 and 86, the CGW 13 has an acquisition request sending unit 71, a write data acquisition unit 72 (corresponding to an update data storage unit), a write data distribution unit 73 (corresponding to an update data distribution unit), a rewrite specification data acquisition unit 74, and a rewrite specification data analysis unit 75. The write data acquisition unit 72 acquires write data from the DCM 12 when the write data is transferred from the DCM 12. When the write data acquisition unit 72 acquires the write data, the write data distribution unit 73 distributes the acquired write data to the rewrite target ECU 19 at the timing to distribute the write data. When the rewrite specification data is transferred from the DCM 12, the rewrite specification data acquisition unit 74 acquires the rewrite specification data from the DCM 12. When the rewrite specification data acquisition unit 74 acquires the rewrite specification data, the rewrite specification data analysis unit 75 analyzes the acquired rewrite specification data.
[0292] In addition to the above components, the CGW 13 has the following components for performing characteristic processing: a write data acquisition determination unit 76, an installation instruction determination unit 77, a security access key management unit 78, a write data verification unit 79, a data storage surface information transmission control unit 80, a power management unit 81 for non-rewrite targets, a file transfer control unit 82, a write data distribution control unit 83, an activation request instruction unit 84, a rewrite target group management unit 85, a rollback execution control unit 86, a rewrite progress display control unit 87, a progress status synchronization control unit 88, a display control information reception control unit 89, a progress display screen display control unit 90, a program update notification control unit 91, and a power self-maintenance execution control unit 92. The functional blocks that perform characteristic processing will be described later.
[0293] As shown in FIG. 87, the ECU 19 has a write data receiving unit 101 and a program rewriting unit 102. The write data receiving unit 101 receives write data from the CGW 13. When the write data receiving unit 101 receives the write data from the CGW 13, the program rewriting unit 102 writes the received write data into the flash memory to rewrite the application program. In addition to the above-mentioned configuration, the ECU 19 has the following configuration for performing characteristic processing: a difference data consistency determining unit 103, a rewriting execution control unit 104, a session establishing unit 105, a retry point identifying unit 106, an activate execution control unit 107, and a power self-maintaining execution control unit 108. The functional blocks that perform characteristic processing will be described later.
[0294] As shown in Fig. 88, the in-vehicle display 7 has a distribution specification data reception control unit 111. The distribution specification data reception control unit 111 controls the reception of distribution specification data. Below, each of the above processes (1) to (26) will be explained in order.
[0295] (1) Processing to determine whether a distribution package should be sent, (2) Processing to determine whether a distribution package should be downloaded The process of determining whether to transmit a distribution package in the center device 3 will be described with reference to FIGS. 89 and 90, and the process of determining whether to download a distribution package in the master device 11 will be described with reference to FIGS.
[0296] As shown in FIG. 89, the center device 3 includes a distribution package transmission determination unit 52 that includes a software information acquisition unit 52a, an update presence / absence determination unit 52b, an update appropriateness determination unit 52c, and a campaign information transmission unit 52d. The software information acquisition unit 52a acquires software information for each ECU 19 from the vehicle. Specifically, the software information acquisition unit 52a acquires ECU configuration information from the vehicle, including software information such as the version and writing surface, and hardware information. In addition to the ECU configuration information, the software information acquisition unit 52a may also acquire vehicle status information from the vehicle, such as fault codes, anti-theft alarm function settings, and license contract information.
[0297] When software information is acquired by software information acquisition unit 52a, update presence / absence determination unit 52b determines whether or not update data for the vehicle exists based on the acquired software information. That is, update presence / absence determination unit 52b compares the version of the acquired software information with the version of the latest software information managed by itself, determines whether the two match, and determines whether or not update data for the vehicle exists. If update presence / absence determination unit 52b determines that the two match, it determines that there is no update data for the vehicle, and if it determines that the two do not match, it determines that there is update data for the vehicle.
[0298] When the update presence / absence determination unit 52b determines that update data for the vehicle is available, the update suitability determination unit 52c determines whether the vehicle state is suitable for updating programs, etc., using a distribution package. Specifically, the update suitability determination unit 52c determines whether a license agreement has been established, whether the vehicle location is within a predetermined range registered in advance by the user, whether the vehicle's alarm function setting is enabled, and whether malfunction information has been generated for the ECU 19, and determines whether the vehicle state is suitable for downloading a distribution package. In other words, the update suitability determination unit 52c determines whether the vehicle is one for which an update may be contrary to the user's wishes, or one for which installation may fail after the download, even if the download is successful.
[0299] The update suitability determination unit 52c determines that the vehicle state is suitable for updating programs, etc. using a distribution package when it determines that a license agreement has been established, the vehicle location is within a predetermined range registered in advance by the user, the setting of the vehicle's alarm function has been enabled, and no malfunction information has been generated for the ECU 19. The update suitability determination unit 52c determines that the vehicle state is not suitable for updating programs, etc. using a distribution package when it determines that at least one of the following conditions has been met: a license agreement has not been established, the vehicle location is not within a predetermined range registered in advance by the user, the setting of the vehicle's alarm function has not been enabled, or malfunction information has been generated for the ECU 19.
[0300] When the update suitability determination unit 52c determines that the vehicle state is suitable for updating programs, etc. using a distribution package, the campaign information transmission unit 52d transmits the campaign information to the master device 11. When the update suitability determination unit 52c determines that the vehicle state is not suitable for updating programs, etc. using a distribution package, the campaign information transmission unit 52d does not transmit the campaign information to the master device 11. By making the above-mentioned determination, the campaign information transmission unit 52d stores information about vehicles for which campaign information was not transmitted to the master device 11. Note that the center device 3 may display information about vehicles for which campaign information was not transmitted to the master device 11.
[0301] Next, the operation of the distribution package transmission determination unit 52 in the center device 3 will be described with reference to Fig. 90. The center device 3 executes a distribution package transmission determination program and performs a distribution package transmission determination process.
[0302] When the center device 3 starts the distribution package transmission determination process, it acquires software information from the vehicle (S101, corresponding to the software information acquisition procedure). That is, the center device 3 determines whether or not there is a software update for the vehicle. The center device 3 determines whether or not there is update data for the vehicle based on the acquired software information (S102, corresponding to the update presence / absence determination procedure). If the center device 3 determines that there is update data for the vehicle (S102: YES), it determines whether or not the vehicle state is suitable for updating programs, etc. using the distribution package (S103, corresponding to the update suitability determination procedure). If the center device 3 determines that the vehicle state is suitable for updating programs, etc. using the distribution package (S103: YES), it transmits campaign information to the master device 11 (S104, corresponding to the campaign information transmission procedure), and ends the distribution package transmission determination process.
[0303] If the center device 3 determines that there is no update data for the vehicle (S102: NO), it transmits to the master device 11 a message indicating that the vehicle is not a target for transmission of a distribution package, i.e., that there is no update of the application program (S105), and ends the distribution package transmission determination process. If the center device 3 determines that the vehicle state is not suitable for updating programs, etc. using a distribution package (S103: NO), it transmits to the master device 11 a message indicating that the vehicle is not suitable for updating programs, etc., and the reason for this (S106), and ends the distribution package transmission determination process. In this case, the master device 11 displays on the in-vehicle display 7 a message indicating that the vehicle is not suitable for updating programs, etc., and the reason for this. If, for example, a license contract has not been established, the master device 11 displays on the in-vehicle display 7, for example, "Program update is not possible because the license is invalid. Please consult your dealer." This allows the user to be informed of the reason why the vehicle is not suitable for updating programs, etc., and provides appropriate information to the user.
[0304] As described above, the center device 3 can determine whether the state is suitable for updating a program or the like using the distribution package by performing the distribution package transmission determination process before transmitting the distribution package to the master device 11 and before transmitting the campaign information. Then, the center device 3 can transmit the campaign information to the master device 11 so as to transmit the distribution package to the master device 11 only when it is determined that the state is suitable for updating a program or the like using the distribution package.
[0305] The center device 3 can transmit campaign information to the master device 11 when a license agreement has been concluded, the vehicle location is within a predetermined range registered in advance by the user, the vehicle alarm function setting is enabled, and no malfunction information has occurred in the ECU 19, as being suitable cases for updating a program or the like using a distribution package. That is, the center device 3 can avoid transmitting campaign information to the master device 11 when a license agreement has not been concluded, the vehicle location is outside the predetermined range, such as a location far from the user's home, the vehicle alarm function setting is disabled, or malfunction information has occurred in the ECU 19. In this way, the center device 3 can prevent the transmission of campaign information to the master device 11 for vehicles for which an update may be contrary to the user's intention or for vehicles for which installation may fail even if downloading is successful.
[0306] The center device 3 may perform a distribution package transmission determination process while transmitting the distribution package. In this case, if the center device 3 determines that the vehicle state is suitable for updating programs, etc. using the distribution package while transmitting the distribution package, it continues transmitting the distribution package. However, if the center device 3 determines that the vehicle state is not suitable for updating programs, etc. using the distribution package while transmitting the distribution package, it suspends transmitting the distribution package. In other words, if, for example, failure information about the ECU 19 occurs while transmitting the distribution package, the center device 3 suspends transmitting the distribution package.
[0307] Next, the processing of the master device 11 that receives campaign information transmitted from the center device 3 will be described. The distribution package download determination processing in the master device 11 will be described with reference to Figs. 91 and 92. The vehicle program rewriting system 1 performs distribution package download determination processing in the master device 11. The above-mentioned (1) distribution package transmission determination processing is a determination processing performed by the center device 3 in the campaign notification phase before the download phase, but the distribution package download determination processing is a determination processing performed by the master device 11 in the download phase. Note that in this embodiment, a case will be described in which the DCM 12 performs the distribution package download determination processing in the master device 11, but if the CGW 13 has the functions of the DCM 12, the CGW 13 may also perform the distribution package download determination processing.
[0308] As shown in FIG. 91, the DCM 12 has a distribution package download determination unit 67 that includes a campaign information receiving unit 67a, a download availability determination unit 67b, and a download execution unit 67c. The campaign information receiving unit 67a receives campaign information from the center device 3. When the campaign information is received from the center device 3, the campaign notification icon 501a shown in FIG. 68 is displayed. When the campaign information receiving unit 67a receives the campaign information, the download availability determination unit 67b determines whether the vehicle state is such that the distribution package can be downloaded. That is, the download availability determination unit 67b determines whether the radio wave environment for communicating with the center device 3 is good, whether the remaining battery charge of the vehicle battery 40 is equal to or greater than a predetermined capacity, and whether the available memory capacity of the DCM 12 is equal to or greater than a predetermined capacity, and determines whether the vehicle state is such that the distribution package can be downloaded.
[0309] The download possibility determination unit 67b determines that the vehicle state is in a state where a distribution package can be downloaded if it determines that the radio wave environment is good, the remaining battery charge of the vehicle battery 40 is equal to or greater than a predetermined capacity, and the available memory capacity of the DCM 12 is equal to or greater than a predetermined capacity.The download possibility determination unit 67b determines that the vehicle state is not in a state where a distribution package can be downloaded if it determines that at least one of the radio wave environment is not good, the remaining battery charge of the vehicle battery 40 is less than a predetermined capacity, and the available memory capacity of the DCM 12 is less than a predetermined capacity.
[0310] In this way, the download possibility determination unit 67b determines whether or not there is a possibility that the download cannot be completed normally. Note that the determination by the download possibility determination unit 67b is made on the condition that the user operates the "Start download" button 503a on the download consent screen 503 shown in FIGS. 70 and 71. The download possibility determination unit 67b may also be configured to determine the determination items in the center device 3. That is, the download possibility determination unit 67b determines that the download is possible when, for example, the setting of the alarm function of the vehicle is enabled or no malfunction information has been generated in the ECU 19.
[0311] When the download possibility determination unit 67b determines that the vehicle state is in a state in which the distribution package can be downloaded, the download execution unit 67c downloads the distribution package from the center device 3. That is, the download execution unit 67c executes the download of the distribution package after confirming that the download can be completed normally.
[0312] If the download possibility determination unit 67b determines that the vehicle state is not in a state in which the distribution package can be downloaded, the download execution unit 67c does not download the distribution package from the center device 3. In other words, if there is a possibility that the download cannot be completed successfully, the download execution unit 67c does not download the distribution package. In this case, the download execution unit 67c instructs the in-vehicle display 7 to display a pop-up screen on the navigation screen 501 to the effect that the download could not be started and to indicate the reason for the failure.
[0313] Next, the operation of the distribution package download determination section 67 in the master device 11 will be described with reference to Fig. 92. The master device 11 executes a distribution package download determination program and performs a distribution package download determination process.
[0314] When the master device 11 starts the distribution package download determination process, it receives campaign information from the center device 3 (S201, corresponding to the campaign information reception procedure). The master device 11 determines whether the vehicle state is in a state where the distribution package can be downloaded (S202, corresponding to the download possibility determination procedure). If the master device 11 determines that the vehicle state is in a state where the distribution package can be downloaded (S202: YES), it downloads the distribution package corresponding to the campaign from the center device 3 (S203, corresponding to the download execution procedure) and ends the distribution package download determination process. If the master device 11 determines that the vehicle state is not in a state where the distribution package can be downloaded (S202: NO), it does not download the distribution package from the center device 3 and ends the distribution package download determination process.
[0315] As described above, the master device 11 can determine whether the vehicle state is in a state where the distribution package can be downloaded by performing the distribution package download determination process before downloading the distribution package from the center device 3. Then, the master device 11 can download the distribution package only when the vehicle state is in a state where the distribution package can be downloaded.
[0316] The master device 11 can download a distribution package from the center device 3 when the radio wave environment is good, the remaining battery charge of the vehicle battery 40 is equal to or greater than a predetermined capacity, and the available memory capacity of the DCM 12 is equal to or greater than a predetermined capacity, which are considered to be suitable for downloading the distribution package. In other words, it is possible to avoid a situation where the radio wave environment is not good, the remaining battery charge of the vehicle battery 40 is less than a predetermined capacity, or the available memory capacity of the DCM 12 is less than a predetermined capacity.
[0317] The master device 11 may perform a distribution package download determination process while the distribution package is being downloaded. In this case, if the master device 11 determines that the vehicle state is in a state where the distribution package can be downloaded while the distribution package is being downloaded, the master device 11 continues downloading the distribution package from the center device 3, but if the master device 11 determines that the vehicle state is not in a state where the distribution package can be downloaded while the distribution package is being downloaded, the master device 11 suspends downloading the distribution package from the center device 3. In other words, the master device 11 If, for example, the radio wave environment becomes poor during download of the distribution package, the remaining battery capacity of the vehicle battery 40 falls below a predetermined capacity, or the free memory capacity of the DCM 12 falls below a predetermined capacity, the download of the distribution package is interrupted.
[0318] In this way, the center device 3 determines whether the vehicle is one for which an update may be made against the user's will or for which installation may fail, and the master device 11 determines whether the download may fail, thereby preventing the center device 3 from sending unnecessary campaign information or distribution packages to the master device 11.
[0319] The center device 3 has the following configuration: a software information acquisition unit 52a that acquires software information of the electronic control unit from the vehicle side, an update presence / absence determination unit 52b that determines whether or not update data for the vehicle exists based on the software information acquired by the software information acquisition unit, an update suitability determination unit 52c that determines whether or not the vehicle state is suitable for an update when the update presence / absence determination unit determines that update data exists, and a campaign information transmission unit 52d that transmits campaign information related to the update to the vehicle master device when the update suitability determination unit determines that the vehicle state is suitable for an update.
[0320] The master device 11 has the following configuration: a campaign information receiving unit 67a that receives campaign information from a center device, a download possibility determining unit 67b that determines whether the vehicle state is in a state where a distribution package can be downloaded when campaign information is received by the campaign information receiving unit, and a download executing unit 67c that downloads the distribution package from the center device when the download possibility determining unit determines that the vehicle state is in a state where a distribution package can be downloaded.
[0321] (3) Processing to determine whether to transfer the write data, (4) Processing to determine whether to acquire the write data, and (5) Processing to determine whether to issue an installation instruction. The write data transfer determination process will be described with reference to Figures 93 and 94, the write data acquisition determination process will be described with reference to Figures 95 and 96, and the installation instruction determination process will be described with reference to Figures 97 to 100. The vehicle program rewriting system 1 performs the write data transfer determination process in the DCM 12. Here, it is assumed that the distribution package transmitted from the center device 3 to the DCM 12 has been unpackaged and the write data has been extracted from the distribution package.
[0322] As shown in FIG. 93, the DCM 12 has an acquisition request receiving unit 68a and a communication status determining unit 68b in the write data transfer determining unit 68. The acquisition request receiving unit 68a receives an acquisition request for write data from the CGW 13. When the acquisition request for write data is received by the acquisition request receiving unit 68a, the communication status determining unit 68b determines the status of data communication between the center device 3 and the DCM 12, for example, when a transfer feasibility determination flag preset by the user is a first predetermined value. The transfer feasibility determination flag is, for example, 1 (first predetermined value) when a predetermined condition is checked during installation, or 0 (second predetermined value) when the check is omitted. The write data transferring unit 64 transfers the write data to the CGW 13 on the condition that the communication status determining unit 68b determines that data communication between the center device 3 and the DCM 12 is in a connected state.
[0323] Next, the operation of the write data transfer determination unit 68 in the DCM 12 will be described with reference to Fig. 94. The DCM 12 executes a write data transfer determination program and performs write data transfer determination processing. Here, the processing when the CGW 13 requests the DCM 12 to acquire write data in accordance with an installation instruction from the center device 3 will be described.
[0324] When the DCM 12 determines that it has received a request to obtain write data from the CGW 13, it starts a write data transfer determination process. When the DCM 12 starts the write data transfer determination process, it determines the transfer possibility determination flag (S301, S302). When the DCM 12 determines that the transfer possibility determination flag is a first predetermined value (S301: YES), it determines the state of data communication between the center device 3 and itself (S303). When the DCM 12 determines that data communication between the center device 3 and itself is in a connected state (S303: YES), it transfers the write data to the CGW 13 (S304) and ends the write data transfer determination process. When the DCM 12 determines that data communication between the center device 3 and itself is not in a connected state but in a disconnected state (S303: NO), it does not transfer the write data to the CGW 13 and ends the write data transfer determination process.
[0325] Furthermore, when the DCM 12 determines that the transfer possibility determination flag is a second predetermined value (S302: YES), it transfers the write data to the CGW 13 without determining the state of data communication between the center device 3 and itself, and terminates the write data transfer determination process.
[0326] As described above, the DCM 12 performs a write data transfer determination process before transferring the write data to the CGW 13, thereby determining the state of data communication between itself and the center device 3 when the transfer possibility determination flag is a first predetermined value. If the DCM 12 determines that data communication is connected, it starts transferring the write data, and if it determines that data communication is interrupted, it waits without starting to transfer the write data. When data communication with the center device 3 is possible, the write data can be transferred to the CGW 13, and installation can be performed in the rewriting target ECU 19.
[0327] For example, if there are multiple ECUs 19 to be rewritten and installation takes time, the in-vehicle system 4 can notify the center device 3 of the progress of the installation, and the progress can be displayed one by one on the mobile terminal 6. The DCM 12 may perform the write data transfer determination process while transferring the write data. In this case, if the DCM 12 determines that data communication is connected during the transfer of the write data, it continues the transfer of the write data, but if it determines that data communication is interrupted during the transfer of the write data, it interrupts the transfer of the write data.
[0328] Next, the write data acquisition determination process will be described. The vehicle program rewriting system 1 performs the write data acquisition determination process in the CGW 13. The above-mentioned (3) write data transfer determination process is a determination process performed by the DCM 12 in the installation phase, and the write data acquisition determination process is a determination process performed by the CGW 13 in the installation phase.
[0329] As shown in FIG. 95, the CGW 13 includes an event occurrence determination unit 76a and a communication state determination unit 76b in the write data acquisition determination unit 76. The event occurrence determination unit 76a determines the occurrence of an event of a write data acquisition request (installation instruction) from the center device 3. When the event occurrence determination unit 76a determines the occurrence of an event of the write data acquisition request, the communication state determination unit 76b determines the state of data communication between the center device 3 and the DCM 12, for example, when an acquisition possibility determination flag preset by the user is a first predetermined value. The acquisition possibility determination flag is, for example, 1 (first predetermined value) when a predetermined condition is checked during installation, or 0 (second predetermined value) when the check is omitted. Here, the event occurrence determination unit 76a may determine the occurrence of an event based on a user's instruction to install. For example, when the event occurrence determination unit 76a receives a notification that the user has performed an installation instruction operation (see FIG. 75) on the in-vehicle display 7, the event occurrence determination unit 76a determines that an event of a write data acquisition request has occurred.
[0330] Next, the operation of the write data acquisition determination unit 76 in the CGW 13 will be described with reference to Fig. 96. The CGW 13 executes a write data acquisition determination program and performs write data acquisition determination processing.
[0331] When the CGW 13 determines that an event of a write data acquisition request has occurred, the CGW 13 starts the write data acquisition determination process. When the CGW 13 starts the write data acquisition determination process, the CGW 13 determines the acquisition possibility determination flag (S401, S402). When the CGW 13 determines that the acquisition possibility determination flag is equal to the first predetermined value (S401: YES), it determines the state of data communication between the center device 3 and the DCM 12 (S403: If the CGW 13 determines that the data communication between the center device 3 and the DCM 12 is connected (S403: YES), it sends a write data acquisition request to the DCM 12 (S404) and ends the write data acquisition determination process. After this, when write data is transferred from the DCM 12, the CGW 13 distributes the transferred write data to the rewriting target ECU 19. When the CGW 13 determines that the data communication between the center device 3 and the DCM 12 is not connected but interrupted (S403: NO), it does not send a write data acquisition request to the DCM 12 and ends the write data acquisition determination process.
[0332] Also, when the CGW13 determines that the acquisition possibility determination flag is a second predetermined value (S402: YES), it sends a request to acquire the write data to the DCM12 without determining the state of data communication between the center device 3 and the DCM12, and terminates the write data acquisition determination process.
[0333] As described above, the CGW 13 performs the write data acquisition determination process before acquiring the write data from the DCM 12, and thereby determines the state of data communication between the center device 3 and the DCM 12 when the acquisition possibility determination flag is equal to the first predetermined value. If the CGW 13 determines that data communication is connected, it starts acquiring the write data, and if it determines that data communication is interrupted, it waits without starting to acquire the write data. Under conditions where communication with the center device 3 is possible, the CGW 13 can acquire the write data from the DCM 12 and can install the data in the rewriting target ECU 19.
[0334] For example, if there are multiple ECUs 19 to be rewritten and installation takes time, the in-vehicle system 4 can notify the center device 3 of the progress of the installation, and the progress can be displayed one by one on the mobile terminal 6. The CGW 13 may perform the write data acquisition determination process while acquiring the write data. In this case, if the CGW 13 determines that data communication is connected while acquiring the write data, it continues acquiring the write data, but if it determines that data communication is interrupted while acquiring the write data, it interrupts acquiring the write data.
[0335] Next, the aforementioned determination of whether to acquire the write data will be described in more detail. The acquisition of the write data is one of the processes related to installation. Here, the installation instruction determination process will be described with reference to FIGS. 97 to 100. The vehicle program rewriting system 1 performs the installation instruction determination process in the CGW 13. The aforementioned (1) distribution package transmission determination process and (2) distribution package download determination process are determination processes performed in the download phase, (3) write data transfer determination process and (4) write data acquisition determination process are processes performed in the install phase after download completion, and (5) installation instruction determination process is processes performed in the install phase and activate phase. Here, it is assumed that the distribution package is downloaded to the DCM 12, and the write data (update data, difference data) for the write target ECU 19 is unpackaged as shown in FIG. 46.
[0336] As shown in FIG. 97, the CGW 13 has an installation instruction determination unit 77 that includes an installation condition determination unit 77a, an installation instruction unit 77b, a vehicle state information acquisition unit 77c, an activation condition determination unit 77d, and an activation instruction unit 77e. The installation condition determination unit 77a determines whether a first condition, a second condition, a third condition, a fourth condition, and a fifth condition are met. The first condition is that user consent to the installation has been obtained. User consent to the installation refers to, for example, a user consent operation for the installation (e.g., pressing the "Update Now" button 506a) on the screen shown in FIG. 75. Alternatively, the process from download to activation may be considered as one update, and the user consent operation for the update may be considered as an operation for consent.
[0337] The second condition is that the CGW 13 is capable of data communication with the center device 3. The third condition is that the vehicle state is such that installation is possible. The fourth condition is that the rewrite target ECU 19 is capable of installation. Here, the fourth condition includes not only that the rewrite target ECU 19 to be installed is capable of installation, but also that the rewrite target ECU 19 that cooperates with the rewrite target ECU 19 to be installed is capable of installation. The fifth condition is that the write data is normal data. Here, normal data includes data that is suitable for the rewrite target ECU 19, data that has not been tampered with, etc.
[0338] When the installation condition determination unit 77a determines that all of the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are satisfied, the installation instructing unit 77b instructs the rewriting target ECU 19 to install the application program. That is, when the installation condition determination unit 77a determines that user consent to the installation has been obtained, that the CGW 13 is capable of data communication with the center device 3, that the vehicle state is in a state in which installation is possible, that the rewriting target ECU 19 is in a state in which installation is possible, and that the write data is normal data, the installation instructing unit 77b instructs the rewriting target ECU 19 to install the application program. Specifically, the installation instructing unit 77b obtains the write data from the DCM 12 and transfers the obtained write data to the rewriting target ECU 19. When the installation condition determination unit 77a determines that at least one of the first condition, the second condition, the third condition, the fourth condition, and the fifth condition is not satisfied, the installation instruction unit 77b does not instruct the rewriting target ECU 19 to install the application program, and presents to the user the fact that it is not possible to wait or start installation and the reason for this.
[0339] The vehicle state information acquisition unit 77c acquires vehicle state information from the center device 3. The activation condition determination unit 77d determines whether the sixth, seventh, and eighth conditions are met when installation of the application programs is completed in all of the rewriting target ECUs 19. The sixth condition is that user consent to activation has been obtained. User consent to activation indicates, for example, a user consent operation for activation (e.g., pressing the "OK" button 508b) on the screen shown in FIG. 79. Alternatively, the process from download to activation may be considered as one update, and the user consent operation for the update may be considered. The seventh condition is that the vehicle state is in a state where activation is possible. The eighth condition is that the rewriting target ECUs 19 are in a state where activation is possible.
[0340] When the activation condition determination unit 77d determines that all of the sixth condition, the seventh condition, and the eighth condition are satisfied, the activation instruction unit 77e instructs the rewriting target ECU 19 to activate the application program. This will be described in detail in (12) Activation Request Instruction Processing, which will be described later. That is, when the activation condition determination unit 77d determines that user consent to activation has been obtained, the vehicle state is in a state in which activation is possible, and the rewriting target ECU 19 is in a state in which activation is possible, the activation instruction unit 77e instructs the rewriting target ECU 19 to activate the application program. By activating the application program, the updating program written in the rewriting target ECU 19 is validated. When the activation condition determination unit 77d determines that at least one of the sixth condition, the seventh condition, and the eighth condition is not satisfied, the activation instruction unit 77e does not instruct the rewriting target ECU 19 to activate the application program, and notifies the user that waiting or activation cannot be started and the reason for this.
[0341] Next, the operation of the installation instruction determination unit 77 in the CGW 13 will be described with reference to Figures 98 to 100. The CGW 13 executes an installation instruction determination program and performs installation instruction determination processing.
[0342] When the CGW 13 starts the installation instruction determination process, it determines whether a first condition is met and determines whether user consent to the installation has been obtained (S501, which corresponds to part of the installation condition determination procedure). If the CGW 13 determines that user consent to the installation has been obtained (S501: YES), it determines whether a second condition is met and determines whether data communication with the center device 3 is possible (S502, which corresponds to part of the installation condition determination procedure). The CGW 13 determines whether data communication with the center device 3 is possible based on the communication radio wave conditions in the DCM 12.
[0343] When the CGW 13 determines that data communication with the center device 3 is possible (S502: YES), it determines whether a third condition is met and determines whether the vehicle state allows installation (S503, which corresponds to part of the installation condition determination procedure). The CGW 13 determines whether the vehicle state allows installation by determining, for example, whether the remaining battery charge of the vehicle battery 40 is equal to or greater than a predetermined capacity, or whether the vehicle is in a parked state (IG off state) if the memory configuration of the reprogramming target ECU 19 is a single-plane memory. These vehicle state conditions may be determined by referring to the received reprogramming specification data (see FIG. 44). The CGW 13 determines that the vehicle state allows installation when, for example, the remaining battery charge of the vehicle battery 40 is equal to or greater than a predetermined capacity specified in the reprogramming specification data and the vehicle state matches the vehicle state specified in the reprogramming specification data (only parked state, only running state, or both parked and running states).
[0344] When the CGW 13 determines that the vehicle condition allows installation (S503: YES), it determines whether a fourth condition is met and determines whether the rewrite target ECU 19 is installable (S504, which corresponds to part of the installation condition determination procedure). The CGW 13 determines that the rewrite target ECU 19 is installable, for example, if no fault code has occurred in the rewrite target ECU 19 and security access to the rewrite target ECU 19 has been successful. Here, it is preferable to check whether a fault code has occurred not only in the rewrite target ECU 19 to which write data is written, but also in the ECU 19 that performs cooperative control with the rewrite target ECU 19. That is, the CGW 13 determines whether a fault code has occurred not only in the rewrite target ECU 19 but also in the ECU 19 that performs cooperative control with the rewrite target ECU 19.
[0345] If the CGW 13 determines that the rewrite target ECU 19 is installable (S504: YES), it determines whether the fifth condition is met and whether the write data is normal (S505, which corresponds to part of the installation condition determination procedure). The CGW 13 determines that the write data is normal if the write data matches the write side (non-operational side) of the rewrite target ECU 19 and the integrity of the write data is normal. If the CGW 13 determines that the write data is normal (S505: YES), it instructs the rewrite target ECU 19 to install the application program (S506, which corresponds to the installation instruction procedure). In this way, the CGW 13 performs determinations for the second and subsequent conditions, provided that the first condition is met. Finally, the CGW 13 determines whether the fifth condition is met. If the CGW 13 determines that all of the first to fifth conditions are met, it instructs the rewrite target ECU 19 to install the application program.
[0346] On the other hand, if the CGW 13 determines that user consent for installation has not been obtained (S501: NO), if it determines that data communication with the center device 3 is not possible (S502: NO), if it determines that the vehicle state does not allow installation (S503: NO), if it determines that the rewriting target ECU 19 does not allow installation (S504: NO), or if it determines that the write data is not normal data (S505: NO), it does not instruct the rewriting target ECU 19 to install the application program. Note that in the above process, a configuration has been described in which the condition that user consent for installation has been obtained is determined before other conditions, but a configuration in which the condition is determined after other conditions may also be used.
[0347] When the CGW 13 instructs the rewrite target ECU 19 to install the application program, it distributes write data to the rewrite target ECU 19 (S507) and determines whether the installation is complete (S508). When the CGW 13 determines that the installation is complete (S508: YES), it determines whether a sixth condition is met and determines whether user consent to activation has been obtained (S509). When the CGW 13 determines that user consent to activation has been obtained (S509: YES), it determines whether a seventh condition is met and determines whether the vehicle state is in a state where activation is possible (S510).
[0348] When the CGW 13 determines that the vehicle state is in a state where activation is possible (S510: YES), it determines whether or not the eighth condition is satisfied, and determines whether or not the rewriting target ECU 19 is in a state where activation is possible (S511). When the CGW 13 determines that the rewriting target ECU 19 is in a state where activation is possible (S511: YES), it instructs the rewriting target ECU 19 to activate (S512). In this way, when the CGW 13 determines that all of the sixth to eighth conditions are satisfied, it instructs the rewriting target ECU 19 to activate.
[0349] Furthermore, when there are multiple reprogramming target ECUs 19, the CGW 13 may instruct the installation individually or collectively. When the reprogramming target ECUs 19 are ECU(ID1) and ECU(ID2), instructing the installation individually, the CGW 13 determines whether the installation conditions are met for ECU(ID1), as shown in FIG. 99. If the CGW 13 determines that the installation conditions are met for ECU(ID1), it instructs ECU(ID1) to perform installation. Next, the CGW 13 determines whether the installation conditions are met for ECU(ID2). Here, the CGW 13 may determine whether the fourth and fifth conditions are met for ECU(ID2) as the installation conditions. If the CGW 13 determines that the installation conditions are met for ECU(ID2), it instructs ECU(ID2) to perform installation.
[0350] When the reprogramming target ECUs 19 are ECU(ID1) and ECU(ID2), in a configuration in which installation is instructed collectively, the CGW 13 determines whether the installation conditions for ECU(ID1) are met, as shown in FIG. 100 . That is, the CGW 13 determines whether the first to third conditions and the fourth and fifth conditions for ECU(ID1) are met. If the CGW 13 determines that the installation conditions for ECU(ID1) are met, it determines whether the installation conditions for ECU(ID2) are met. That is, the CGW 13 determines whether the fourth and fifth conditions for ECU(ID2) are met. If the installation conditions for ECU(ID2) are met, the CGW 13 instructs ECU(ID1) and ECU(ID2) to perform installation. For example, the CGW 13 simultaneously transfers the reprogramming data to ECU(ID1) and ECU(ID2) in parallel. In this manner, in the mode in which the CGW 13 issues a collective installation instruction, the CGW 13 determines whether the first to third conditions, as well as the fourth and fifth conditions for all the ECUs to be rewritten, and then issues an installation instruction only after all of these conditions are satisfied.
[0351] As described above, by performing the installation instruction determination process before instructing the rewriting target ECU 19 to install the application program, the CGW 13 instructs the rewriting target ECU 19 to install the application program when it determines that all of the following conditions are met: the first condition that user consent for installation has been obtained, the second condition that data communication with the center device 3 is possible, the third condition that the vehicle state is in a state where installation is possible, the fourth condition that the rewriting target ECU 19 is in a state where installation is possible, and the fifth condition that the write data is normal data. This allows the CGW 13 to appropriately instruct the rewriting target ECU 19 to install the application program.
[0352] (6) Management of security access keys The security access key management process will be described with reference to Figures 101 to 105. The security access key is a key used for device authentication when the CGW 13 accesses the rewriting target ECU 19 before installing the write data. The vehicle program rewriting system 1 performs security access key management process in the CGW 13. Here, the description is based on the premise that the CGW 13 is in a state where it can acquire the write data from the DCM 12 by the above-mentioned (3) write data transfer determination process or (4) write data acquisition determination process. Device authentication using the security access key corresponds to the fourth condition (step S505) in the above-mentioned (5) installation instruction determination process.
[0353] When the CGW 13 distributes write data to the rewrite target ECU 19, the CGW 13 needs to perform security access (device authentication) with the rewrite target ECU 19 using a security access key. In this case, a conceivable method is for the CGW 13 to request the rewrite target ECU 19 to generate a random number value, obtain the random number value generated by the rewrite target ECU 19 from the rewrite target ECU 19, and calculate the obtained random number value to generate the security access key. However, with this method, the security access key can be held by obtaining the random number value from the rewrite target ECU 19 even when the application program is not being rewritten, which may result in a risk of the security access key being leaked.
[0354] Furthermore, if the CGW 13 is configured to transmit a random number value acquired from the rewrite target ECU 19 to the center device 3, and the center device 3 calculates the random number value and generates a security access key, it becomes unnecessary to store the security access key, thereby reducing the risk of the security access key being leaked. However, if the center device 3 calculates the random number value, the waiting time until the rewrite target ECU 19 acquires the random number value from the center device 3 becomes long, making it difficult to satisfy the time regulation for diagnostic communication. For these reasons, the following configuration is adopted in this embodiment.
[0355] As shown in Figure 101, the supplier encrypts the security access key for each ECU 19 to be rewritten using the encryption and decryption key for the security access key to generate a random number value. The random number value here means a random value, including both values that are different from values used in the past and values that are the same as values used in the past. The random number value is the encrypted security access key. The supplier provides the generated random number value together with the reprogramming data. The security access key, encryption and decryption key for the security access key, and random number value are keys unique to each ECU 19.
[0356] When the OEM receives a random number value from the supplier along with the reprogramming data, the OEM associates the provided random number value with the ECU (ID) that identifies the ECU 19 and stores the associated random number value in the reprogramming specification data for CGW shown in FIG. 44. The OEM also stores a key pattern and a decryption operation pattern required to decrypt the random number value in the reprogramming specification data for CGW. The key pattern stores the method (symmetric key / public key, etc.) and key length, and the decryption operation pattern stores the type of algorithm used for the decryption operation. After storing the random number value, key pattern, and decryption operation pattern in the reprogramming specification data for CGW, the OEM provides the reprogramming specification data for CGW containing the random number value together with the reprogramming data to the center device 3. This information provided by the supplier is stored in an ECU reprogramming data DB and an ECU metadata DB, which will be described later.
[0357] When the center device 3 receives rewrite specification data (rewrite specification data for DCM and rewrite specification data for CGW) together with reprogramming data from the OEM, the center device 3 transmits a distribution package including the provided rewrite specification data and reprogramming data to the master device 11. In the master device 11, the DCM 12 downloads the distribution package from the center device 3 and transfers the rewrite specification data and programming data to the CGW 13.
[0358] As shown in FIG. 102, the CGW 13 includes a security access key management unit 78 having a secure area 78a (corresponding to a decryption key storage unit), a random value extraction unit 78b (corresponding to a key derivation value extraction unit), a key pattern extraction unit 78c, a decryption operation pattern extraction unit 78d, a key generation unit 78e, a security access execution unit 78f, a session transition request unit 78g, and a key deletion unit 78h. The secure area 78a is not accessible from outside the ECU 19, and stores encryption and decryption keys and decryption operation algorithms for the security access key. The random value extraction unit 78b extracts a random value (key derivation value) included in the rewrite specification data for the CGW from the analysis result of the rewrite specification data. The random value is an encrypted value associated with the ECU (ID) of the ECU 19 to be rewritten.
[0359] The key pattern extraction unit 78c extracts a key pattern included in the rewrite specification data for CGW from the analysis result of the rewrite specification data. The decryption operation pattern extraction unit 78d extracts a decryption operation pattern included in the rewrite specification data for CGW from the analysis result of the rewrite specificati...
Claims
1. A center device (3) that manages data to be written to a plurality of electronic control devices (19) mounted on a vehicle; A vehicle information and communication system including an on-board device (4) that is mounted on a vehicle and has an external communication device (12) that wirelessly communicates with the center device and an internal communication device (13) that communicates with the plurality of electronic control devices, the center device transmits a synchronization start request to the in-vehicle device; the in-vehicle device, upon receipt of the synchronization start request, collects configuration information relating to the configuration of each of the electronic control devices from the plurality of electronic control devices, generates a hash value based on data values of the collected plurality of pieces of configuration information, and transmits the hash value to the center device; the center device has a vehicle-side configuration information storage unit (213) in which configuration information relating to the vehicle in which the in-vehicle device is mounted is stored, compares the hash value received from the in-vehicle device with the hash value of the vehicle configuration information stored in the vehicle-side configuration information storage unit, and if the hash value does not match, notifies the in-vehicle device of a full data transmission request for requesting transmission of all data values of the configuration information; the in-vehicle device transmits all data values of the configuration information to the center device upon receiving the full data transmission request; A vehicle information and communication system, wherein the center device, upon receiving all of the data values, updates the configuration information stored in the vehicle-side configuration information storage unit based on the data values.
2. A vehicle information and communication system as described in claim 1, wherein the center device transmits the synchronization start request to the in-vehicle device on the condition that no transmission of the configuration information has been made from the in-vehicle device for a predetermined period of time.
3. A center device (3) that manages data to be written to a plurality of electronic control devices (19) mounted on a vehicle; A vehicle information and communication system including an on-board device (4) that is mounted on a vehicle and has an external communication device (12) that wirelessly communicates with the center device and an internal communication device (13) that communicates with the plurality of electronic control devices, the in-vehicle device has a storage unit (24d, 28d) that stores a hash value generated based on configuration information relating to the configuration of each device received from the plurality of electronic control devices; when the configuration information is received from the plurality of electronic control units when an ignition is turned on for the vehicle, a first hash value is generated which is a hash value based on data values of the plurality of configuration information, and a second hash value is compared with the first hash value which is a hash value stored in the storage unit, and if there is a difference between the first hash value and the second hash value, the first hash value is transmitted to the center device and stored in the storage unit; the center device has a vehicle-side configuration information storage unit (213) in which configuration information relating to the vehicle in which the in-vehicle device is mounted is stored, and compares a first hash value received from the in-vehicle device with a hash value of the vehicle configuration information stored in the vehicle-side configuration information storage unit, and if the first hash value and the hash value do not match, notifies the in-vehicle device of a full data transmission request for requesting transmission of all data values of the configuration information; the in-vehicle device transmits all data values of the configuration information to the center device upon receiving the full data transmission request; A vehicle information and communication system, wherein the center device, upon receiving all of the data values, updates the configuration information stored in the vehicle-side configuration information storage unit based on the data values.
4. A vehicle information communication method executed between a center device that manages data to be written to a plurality of electronic control devices mounted in a vehicle and an on-board device mounted in the vehicle, comprising: the center device transmits a synchronization start request to the in-vehicle device; the in-vehicle device, upon receipt of the synchronization start request, collects configuration information relating to the configuration of each of the electronic control devices from the plurality of electronic control devices, generates a hash value based on data values of the collected plurality of pieces of configuration information, and transmits the hash value to the center device; the center device stores configuration information regarding the vehicle in which the on-board device is mounted, compares the hash value received from the on-board device with the hash value of the stored vehicle configuration information, and if the hash value does not match, notifies the on-board device of a full data transmission request for requesting transmission of all data values of the configuration information; the in-vehicle device transmits all data values of the configuration information to the center device upon receiving the full data transmission request; When the center device receives all of the data values, the center device updates the stored configuration information based on the data values.
5. A vehicle information communication method executed between a center device that manages data to be written to a plurality of electronic control devices mounted in a vehicle and an in-vehicle device mounted in the vehicle, comprising: the in-vehicle device stores a hash value generated based on configuration information relating to the configuration of each of the electronic control devices received from the plurality of electronic control devices; when the configuration information is received from the plurality of electronic control units when an ignition of the vehicle is turned on, a first hash value is generated which is a hash value based on data values of the plurality of configuration information, and the first hash value is compared with the second hash value which is the stored hash value, and if there is a difference between the first hash value and the second hash value, the first hash value is transmitted to the center device and stored therein; the center device stores configuration information regarding the vehicle in which the in-vehicle device is mounted, compares the first hash value received from the in-vehicle device with a hash value of the stored vehicle configuration information, and if the first hash value and the hash value do not match, notifies the in-vehicle device of a full data transmission request for requesting transmission of all data values of the configuration information; the in-vehicle device transmits all data values of the configuration information to the center device upon receiving the full data transmission request; When the center device receives all of the data values, the center device updates the configuration information stored in the vehicle-side configuration information storage unit based on the data values.
Citation Information
Patent Citations
Method for updating software units
CN102301332A
Configuration information management device and configuration information management method
JP2014191120A
Correction program confirmation method, correction program confirmation program, and information processing apparatus
JP2015079440A
Software distribution management system, software distribution management method
JP2016224503A
Gateway device, firmware update method, and control program
JP2017059210A
