JP2011148398A - Program update system for vehicle - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a program update system for a vehicle which can efficiently distribute an update file. <P>SOLUTION: In a program update system for a vehicle, system startup notification (vehicle ID) indicating startup of respective ECUs 2, 3 is transmitted from a vehicle 20 to a management device 10. The management device 10 has a management database 32 in which version information of a program is registered for every vehicle ID, and determines whether the update file to the vehicle 20 is prepared in the management database 32 on the basis of a vehicle ID received from the vehicle 20. Only when being prepared, the update file (containing product identification information) is transmitted to the vehicle 20. The vehicle 20 having received the update file updates control program of ECU (target ECU) corresponding to the product identification information on the basis of the update file, thereby suppressing the occurrence of unwanted communication cost when respective ECUs 2, 3 are not required to update the control program. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a vehicle program update system for updating a program installed in an electronic control device mounted on a vehicle.

  Conventionally, with respect to a program of an electronic control device (hereinafter referred to as an ECU) that is mounted on a vehicle and controls a predetermined control target device, when a function expansion or a function correction occurs, 2. Description of the Related Art A vehicle program update system that distributes an update file for updating an ECU program is known.

  Generally, in this type of vehicle program update system, the ECU uses a wireless communication function of the vehicle (specifically, a function of performing wireless communication with the outside of the vehicle), and the ECU wirelessly communicates with a management device that holds an update file. And updating the program installed in the own device based on the update file downloaded from the management device.

  Specifically, the ECU first transmits inquiry information including product identification information (for example, a model number) of its own device to the management device, and the management device that has received the inquiry information receives the latest information corresponding to the product identification information. The program version information is sent to the ECU. Then, the ECU compares the version information received from the management device with that of the program installed in the own device, and if both do not match, sends the transmission request information indicating the difference between the two to the management device, The management device distributes an update file based on transmission request information received from the ECU (see, for example, Patent Document 1).

JP 2004-249914 A

  However, in the conventional vehicle program update system, the management device must transmit version information whenever it receives inquiry information from the ECU. Therefore, the load related to the transmission processing is proportional to the number of received inquiry information. There is a possibility that it becomes enormous when inquiries are made from many vehicles at once.

  Furthermore, in the conventional vehicle program update system, even when the ECU does not need to receive an update file (specifically, when the latest program is already installed in the ECU), the management device However, there is a problem that unnecessary communication costs occur because version information must be transmitted.

  In order to solve the above problems, an object of the present invention is to provide a vehicle program update system capable of efficiently distributing an update file.

  The vehicle program update system according to claim 1, which is an invention made to achieve the above object, includes an electronic control device that controls a preset control target device mounted on the vehicle, and a program for the electronic control device Is a system that updates a program installed in an electronic control device by performing wireless communication with a management device that holds an update file for updating the software to the latest version. The electronic control device receives the update file from the management device, and updates the program installed in the own device based on the received update file.

  Here, the electronic control device transmits a vehicle ID for identifying the vehicle on which the device is mounted to the management device at a preset inquiry timing. The management device has a management database in which version information indicating the version of the program installed in the electronic control device is registered for each vehicle ID, and registers the update file in the management database in association with the vehicle ID. At the same time, when the vehicle ID is received from the electronic control device, the update file is transmitted to the electronic control device only when the update file corresponding to the vehicle ID exists in the management database.

  That is, in the vehicle program update system of the present invention, since the management device manages version information and update files for each vehicle ID, the ECU is based on the vehicle ID sent from the electronic control unit (ECU). The update file can be transmitted to the ECU only when the program installed in is not the latest version.

  Therefore, according to the vehicle program update system of the present invention, the management device sends some information (for example, the latest program version information) to all of the inquiries from the ECU (specifically, reception of the vehicle ID). Instead of sending a reply, the update file is transmitted only to the ECU in which the latest program is not installed, so that the update file can be efficiently distributed.

  The inquiry timing for transmitting the vehicle ID from the electronic control unit (ECU) to the management device is set, for example, when the vehicle ignition switch is switched from OFF to ON as described in claim 2. May be.

  In this case, since the update file can be distributed from the management device to the ECU in accordance with the start of operation of the control target device in the vehicle, the program installed in the ECU can be updated on demand. As a result, the update file can be quickly distributed without unnecessarily increasing the number of inquiries from the ECU to the management device.

  In the vehicle program update system of the present invention, as described in claim 3, after the electronic control device has updated the program installed in the device itself, the update completion notification including at least the vehicle ID is managed by the management device. The management device may update the version information corresponding to the vehicle ID in the management database to the latest version based on the update completion notification received from the electronic control device.

  In this case, the version of the program installed in the ECU is compared with the case where the management apparatus updates the version information in the management database immediately after sending the update file to the electronic control unit (ECU). It can be reflected in the inside.

  By the way, as a method of registering the version information in the management database, it may be performed through human power. However, the version information received by the management device by performing wireless communication with the ECU is automatically stored in the management database. It is more efficient to register with.

  Specifically, in the vehicle program update system of the present invention, as described in claim 4, the electronic control device has ECU information including product identification information and version information of the device itself, and is preset. When the transmission condition is satisfied, the ECU information is transmitted to the management device together with the vehicle ID. Then, based on the ECU information and the vehicle ID received from the electronic control device, the management device may register version information together with product identification information in the management database in association with the vehicle ID.

  According to the vehicle program update system configured as described above, the management device can manage version information and update files for each product identification information (that is, electronic control device) of each vehicle ID. The update file can be distributed individually to the electronic control device.

  In the vehicle program update system of the present invention, as described in claim 5, after the management device registers version information in the management database, a registration completion notification including at least product identification information is transmitted to the electronic control device. To do. When the electronic control device receives the registration completion notification from the management device, the electronic control device stores the ECU information and the registration completion notification in association with each other based on the product identification information, and the registration completion notification is not stored at the inquiry timing In addition, the above transmission condition may be satisfied.

  That is, in the vehicle program update system configured as described above, the electronic control unit (ECU) transmits unregistered ECU information to the management database at the time of inquiry (when the vehicle ID is transmitted), and the management device The ECU information received from the ECU is registered in the management database in association with the vehicle ID.

  Therefore, according to the vehicle program update system configured as described above, the ECU does not need to transmit the ECU information registered in the management database, and the ECU information not registered in the management database is transmitted together with the vehicle ID. Since transmission can be performed at the inquiry timing, it is possible to prevent unnecessary communication costs associated with registration of ECU information.

  In the vehicle program update system of the present invention, as described in claim 6, a plurality of electronic control units (ECUs) are mounted on the vehicle, and among the plurality of ECUs, for each product identification information of each ECU. An ECU having an information management table for managing version information may be a master ECU, and an ECU other than the master ECU may be a slave ECU.

  That is, the slave ECU outputs ECU information including the product identification information and version information of its own device to the master ECU, and the master ECU compares the ECU information input from the slave ECU with the information management table, and the product identification information Are the same and the version information is different, the ECU information is transmitted to the management device together with the vehicle ID. Then, the management device updates the version information in the management database based on the ECU information and the vehicle ID received from the master ECU.

  In the vehicle program update system configured in this way, for example, when the slave ECU is replaced at a repair shop or the like, and the version of the program installed in the slave ECU before and after the replacement is different, it corresponds to the slave ECU after replacement. ECU information (product identification information, version information) to be transmitted is transmitted to the management device together with the vehicle ID, and the version information in the management database corresponding to the product identification information is updated.

  Therefore, according to the vehicle program update system configured as described above, even if the slave ECU is replaced, the ECU information corresponding to the replaced slave ECU is the ECU information registered in the management database. Since the master ECU does not need to transmit the ECU information to the management device, it is possible to enhance the prevention of unnecessary communication costs related to the registration of the ECU information.

It is a conceptual diagram which shows the structure of the program update system for vehicles with which this invention was applied. It is a block diagram which shows the structure of an electronic controller (ECU). It is explanatory drawing which shows the structure of ECU information. It is a list which shows the structure of an information management table. It is a flowchart which shows the content of the program management process which MCU16 of slave ECU3 performs. It is a flowchart which shows the content of the program management process which MCU16 of master ECU2 performs. 4 is a flowchart showing the contents of main processing executed by a control unit 34 of the management apparatus 10. 3 is a list showing registered contents of a management database 32. 7 is a flowchart showing the contents of an update file distribution process executed by the control unit 34 of the management apparatus 10. 4 is a flowchart showing the contents of registration / update processing executed by a control unit 34 of the management apparatus 10. The sequence diagram which shows operation | movement of the program update system for vehicles. It is a list which shows the modification concerning the structure of an information management table. It is a block diagram which shows the structure of the electronic controller (ECU) which mounts multiple microcomputers.

Embodiments of the present invention will be described below with reference to the drawings.
<Overall configuration>
FIG. 1 is a conceptual diagram showing a configuration of a vehicle program update system to which the present invention is applied.

  As shown in FIG. 1, a vehicle program update system 1 includes electronic control devices (hereinafter referred to as ECUs) 2, 3 (3a, 3b, 3c,...) That control predetermined devices to be controlled such as engines and brakes. The in-vehicle network 6 includes a management device 10 installed in an information center, which is a facility that operates the system, and ECUs 2 and 3 (3a, 3b, 3c,...). Are constructed of a plurality of vehicles 20 (20a, 20b, 20c,...) Constructed.

  In the following, since the plurality of vehicles 20 (20a, 20b, 20c,...) Have the same configuration, each vehicle 20 (20a, 20b, 20c,...) Is simply referred to as the vehicle 20. .

  In the vehicle program update system 1, a vehicle ID for specifying the host vehicle is assigned to each vehicle 20 in advance. Further, each vehicle 20 is provided with a communication device 7 (for example, a mobile phone) for performing wireless communication with the outside of the own vehicle, and is directly or indirectly connected to the communication device 7 in the in-vehicle network 6. The ECUs 2 and 3 (3a, 3b, 3c,...) And the management device 10 are configured to be able to transmit and receive information to and from each other via the mobile communication network 8 and the Internet network 9.

  In the following, for convenience of explanation, of the ECUs 2 and 3 (3a, 3b, 3c,...) In the in-vehicle network 6, one ECU directly connected to the communication device 7 is communicated via the master ECU 2 and the master ECU 2. A plurality of ECUs connected to the machine 7 are referred to as slave ECUs 3. In addition, the master ECU 2 and the slave ECU 3 share each other via a communication bus 6a in the in-vehicle network 6 in order to share control data necessary for controlling each control target device and to perform integrated control of the vehicle. Connected for data communication. In this embodiment, the CAN (“Controller Area Network” proposed by Robert Bosch, Germany) protocol is mainly used for the data communication.

<Configuration of ECU>
Next, FIG. 2 is a block diagram showing the configuration of each ECU 2, 3.
As shown in FIG. 2, each of the ECUs 2 and 3 has basically the same configuration, and a transceiver 11 that sends data to the communication bus 6a and takes data from the communication bus 6a. The communication controller 12 that controls communication via the communication bus 6a in accordance with the CAN protocol, and the communication controller 12 that controls communication with other ECUs are assigned to the own ECU in conjunction with the other ECUs. And a power supply circuit 15 that converts an input voltage from the battery 14 into an internal voltage and supplies power to the units 11 to 13. Yes.

  Among these, the microcomputer 13 includes a microcontroller unit (hereinafter referred to as MCU) 16 that executes various processes based on the program, and a program (hereinafter referred to as control program) for controlling a control target device assigned to the ECU. Further, a flash memory 17 storing an operating system (OS) that is a program that provides a basic function for executing a control program, and a boot loader that provides a function of rewriting the program stored in the flash memory 17 are stored. ROM 18 and a volatile RAM (SRAM in this embodiment) 19 serving as a work memory when the MCU 16 executes various processes.

  In the SRAM 19 of each ECU 2, 3, product identification information assigned to the own ECU stored in advance in the ROM 18 and a program installed in the own ECU (in this embodiment, a control stored in the flash memory 17). An area (hereinafter referred to as an ECU information area) for storing ECU information 22 (see FIG. 3) including version information of a program is provided. Note that the product identification information of the present embodiment is information for identifying the product model of the ECU, and is set in advance so that at least the use of the ECU (that is, the control target device) can be specified.

  The ECU information 22 is, for example, one product identification information in an ECU in which a plurality of control programs are stored in the flash memory 17 or an ECU equipped with a plurality of microcomputers 13a and 13b (see FIG. 13). One version information is assigned (see FIG. 3A), or a plurality of version information is assigned to one product identification information (see FIG. 3B).

  In the case of an ECU equipped with the latter plurality of microcomputers 13a and 13b (see FIG. 13), the ECU information 22 is stored in the SRAM 19a of the main microcomputer 13a and the version information of the control program stored in the flash memory 17b of the sub-microcomputer 13b. Is associated with product identification information stored in the ROM 18a of the main microcomputer 13a. Further, the ECU information 22 is associated with a registration flag indicating whether or not the ECU information 22 is registered in the management apparatus 10 as will be described in detail later.

  The SRAM 19 of the master ECU 2 is also provided with an area (hereinafter referred to as a table area) for storing an information management table 23 (see FIG. 4) for managing the ECU information 22 of each slave ECU 3.

  However, the SRAM 19 of the present embodiment is connected to the battery 14 so that a backup power supply voltage is input via the power supply circuit 15, and while the battery 14 and the power supply circuit 15 are connected, the ECU information 22 and When the storage contents of the information management table 23 and the like are held and the connection between the battery 14 and the power supply circuit 15 is disconnected, these storage contents are lost.

  A hard disk (HDD) 21 as an external storage device is connected to the MCU 16, and the MCU 16 replaces various programs (tasks) and data stored in the SRAM 19 with the HDD 21 as necessary. Work memory can be virtually increased.

  Further, the MCU 16 is configured to perform processing for controlling a control target device assigned to the ECU based on a control program stored in the flash memory 17 and to execute the following program management processing. ing.

<Program management processing (slave ECU)>
Here, the contents of the program management process executed by the MCU 16 of each slave ECU 3 will be described in detail along the flowchart shown in FIG. This process is started when the ignition switch is switched from OFF to ON.

  First, when this process is started, in S110, based on the registration flag stored in the ECU information area of the SRAM 19, this registration flag indicates that the ECU information 22 is registered in the management apparatus 10. If the determination is affirmative, the process proceeds to S150. If the determination is negative, the process proceeds to S120.

  In S120, the product identification information stored in the ROM 18 and the version information of the control program stored in the flash memory 17 are used as the ECU information 22, and this ECU information 22 is stored in the ECU information area of the SRAM 19 and is communicated. The data is transmitted to the master ECU 2 via the controller 12, and the process proceeds to S130.

  In S130, it is determined whether or not a registration completion notification, which will be described later, has been received from the master ECU 2 via the communication controller 12, and if an affirmative determination is made here, the process proceeds to S140. Wait until you receive

  In S140, the registration completion notification received in S130 is stored in association with the ECU information 22 stored in the ECU information area of the SRAM 19 by setting the registration flag stored in the ECU information area of the SRAM 19 to ON. To do.

  In S150, it is determined whether or not an update file for updating the control program stored in the flash memory 17 to the latest version is received from the master ECU 2 via the communication controller 12 until the predetermined period has elapsed. If the determination is affirmative, the process proceeds to S160. If the determination is negative, the process ends.

  In S160, based on the update file received in S150, a program update process for updating the control program stored in the flash memory 17 to the latest version is executed. When the update of this control program is completed, the process proceeds to S170. . In the program update process, if an update instruction for instructing the execution timing of the program update process is given from the master ECU 2 to the update file received in S150, the control program is updated at a timing according to the update instruction. To do.

  In S170, an update completion notification indicating that the update of the control program is completed in S160 is transmitted to the master ECU 2 through the communication controller 12 together with the product identification information of the own ECU, and this process ends.

<Program management processing (master ECU)>
Next, the contents of the program management process executed by the MCU 16 of the master ECU 2 will be described in detail along the flowchart shown in FIG. This process is started when the ignition switch is switched from OFF to ON.

  First, when this process is started, in S210, it is determined whether or not the ECU information 22 has been received from the slave ECU 3 via the communication controller 12 by the time the predetermined period elapses. If not, the process proceeds to S270.

  In S220, the ECU information 22 received in S210 is compared with the ECU information 22 on the information management table 23 stored in the table area of the SRAM 19, and the ECU information 22 received in S210 is set in advance. It is determined whether the ECU information 22 corresponding to the transmission condition exists. If an affirmative determination is made here, the process proceeds to S230, and if a negative determination is made, the process proceeds to S240. In the present embodiment, when the two pieces of ECU information 22 are compared and the product identification information is the same and the version information is different, the above transmission condition is established.

  For example, when the slave ECU 3 is replaced at a repair shop or the like, if the slave ECU 3 is removed from the vehicle 20, the connection between the battery 14 and the power supply circuit 15 is disconnected, so that the stored contents of the SRAM 19 (setting of the registration flag) are lost. Is done. Therefore, the registration flag is set to OFF as an initial state in the SRAM 19 of the slave ECU 3 newly mounted on the vehicle 20 by the replacement. Therefore, when the ignition switch of the vehicle 20 is switched from OFF to ON after the replacement, the ECU information 22 is transmitted from the slave ECU 3 to the master ECU 2. In this case, the information management table 23 on the SRAM 19 of the master ECU 2 holds the ECU information 22 of the slave ECU 3 before the replacement, and the held ECU information 22 and the ECU information 22 of the slave ECU 3 after the replacement are stored. If they match, the above transmission condition is not satisfied.

  In S230, the ECU information 22 corresponding to the transmission condition of S220 is transmitted to the management device 10 through the communication device 7 together with the vehicle ID corresponding to the host vehicle, and the process proceeds to S250. Here, even when it is determined that the ECU information 22 corresponding to the own ECU (master ECU 2) is not registered in the management device 10 based on the registration flag stored in the ECU information area of the SRAM 19. The ECU information 22 is transmitted to the management apparatus 10.

On the other hand, in S240, only the vehicle ID corresponding to the host vehicle is transmitted to the management apparatus 10 via the communication device 7, and the process proceeds to S270.
In S250, it is determined whether or not a registration completion notification has been received from the management device 10 via the communication device 7. If an affirmative determination is made here, the process proceeds to S260, and if a negative determination is made, a registration completion notification is received. Wait until The registration completion notification is information that is sent to the host vehicle when the management apparatus 10 completes the registration / update process described later with respect to the ECU information 22 transmitted from the master ECU 2 in S230. At least product identification information is included.

  In S260, the registration completion notification received in S240 is transmitted to the slave ECU 3 indicated by the product identification information included in the registration completion notification via the communication controller 12, and stored in the table area of the SRAM 19. The ECU information 22 on the information management table 23 is updated, and the process proceeds to S270. When the product identification information included in the registration completion notification indicates the own ECU (master ECU 2), the registration flag stored in the ECU information area of the SRAM 19 is set to ON.

  In S270, it is determined whether or not an update file has been received from the management apparatus 10 via the communication device 7 until the predetermined period elapses. If an affirmative determination is made here, the process proceeds to S280, and a negative determination is made. This processing ends. Note that at least product identification information is given to the update file in order to identify the ECUs 2 and 3 that are targets of program update.

  In S280, the update file received in S270 is transmitted to the slave ECU 3 indicated by the product identification information given to the update file via the communication controller 12, and the process proceeds to S285. Here, an update instruction for instructing the execution timing of the program update process is transmitted together with the update file in accordance with the slave ECU 3 that is the transmission destination of the update file. Instead of transmitting the update instruction, the update file may be transmitted to the slave ECU 3 at a timing according to the update instruction. When the product identification information included in the update file indicates the own ECU (master ECU 2), a program update process for updating the control program stored in the flash memory 17 to the latest version is executed.

  In S285, it is determined whether or not an update completion notification has been received via the communication controller 12 from the slave ECU 3 that is the transmission destination of the update file in S280. If an affirmative determination is made here, the process proceeds to S290 and a negative determination is made. If this happens, it waits until it receives this update completion notification. When the control program of the own ECU is updated in S280, an update completion notification corresponding to the own ECU is generated.

  In S290, the update completion notification received (or generated) in S285 is managed through the communication device 7 together with the product identification information of the slave ECU 3 (or master ECU 2) that is the transmission destination of the update file in S280 and the vehicle ID. It transmits to the apparatus 10, and this process is complete | finished.

  That is, when the ECUs 2 and 3 execute the program management process and the vehicle 20 in which the in-vehicle network 6 is constructed by the ECUs 2 and 3 is turned on, the ECU information 22 that is not registered in the management device 10 is obtained. Is transmitted to the management apparatus 10 together with the vehicle ID of the host vehicle. Then, when an update file is downloaded from the management apparatus 10, it is possible to update the programs of the corresponding ECUs 2 and 3 based on the update file.

<Configuration of management device>
On the other hand, returning to FIG. 1, the management device 10 updates the network I / F 31 for connecting to the Internet network 9, the management database 32 in which the ECU information 22 is registered for each vehicle ID, and the control programs of the ECUs 2 and 3. An input unit 33 for inputting an update file for updating to a version of the software, and various processes are executed based on various information input via the network I / F 31 and the input unit 33, and the registered contents of the management database 32 are managed. In addition, a control unit 34 that distributes an update file to each vehicle 20 via the network I / F 31 is provided.

  Among these, the control unit 34 is configured around a known microcomputer including a CPU, a ROM, and a RAM, and executes the following main processing, update file distribution processing, and registration / update processing.

<Main processing>
Here, the contents of the main process executed by the control unit 34 will be described in detail along the flowchart shown in FIG. This process is repeatedly executed at a predetermined cycle while the power source of the management apparatus 10 is turned on.

  First, when this process is started, in S310, it is determined whether an update file has been input via the input unit 33. If an affirmative determination is made here, the process proceeds to S320, and if a negative determination is made. , The process proceeds to S330. Note that the update file includes version information (hereinafter referred to as latest version information) corresponding to the latest version of the control program.

  In S320, the ECU information 22 registered in the management database 32 is searched based on the latest version information included in the update file input in S310, and corresponds to a program that needs to be updated to the latest version. The version information is extracted, the update information is stored in association with the extracted version information (ECU information 22) (see FIG. 8), and the process proceeds to S330.

  In S330, it is determined whether or not the vehicle ID has been input via the network I / F 31. If an affirmative determination is made here, the process proceeds to S340, and if a negative determination is made, this process ends.

  In S340, based on the vehicle ID input in S330, ECU information 22 corresponding to the vehicle ID is extracted from the management database 32, and it is determined whether or not an update file is stored in association with the ECU information 22. If the determination is affirmative, the process proceeds to S350 and an update file distribution process described later is started. On the other hand, if the determination is negative, the process proceeds to S360. In S350, after the update file distribution process is activated, the process proceeds to S360.

  In S360, it is determined whether or not the ECU information 22 is given to the vehicle ID received in S330. If an affirmative determination is made here, the process proceeds to S370 to start a registration / update process described later, On the other hand, if a negative determination is made, this process is terminated. In S370, after starting the registration / update process, this process ends.

<Update file distribution processing>
Next, the contents of the update file distribution process activated in S340 will be described in detail along the flowchart shown in FIG.

  First, when this process is started, in S410, the update file corresponding to the ECU information 22 extracted in the previous S340 is added to the vehicle ID input in the previous S330 together with the product identification information constituting the ECU information 22. To the vehicle based.

  In subsequent S420, it is determined whether or not an update completion notification has been input via the network I / F 31 by the time the predetermined period elapses. If an affirmative determination is made here, the process proceeds to S430, and a negative determination is made. Waits until an update completion notification is input.

  In S430, the version information registered in the management database 32 is included in the update file transmitted in S410 based on the product identification information and the vehicle ID given to the update completion notification input in S420. In addition to updating to the latest version information, the association between the updated version information and the update file is canceled, and this process is terminated.

<Registration / update process>
Next, the contents of the registration / update process started in S370 will be described in detail with reference to the flowchart shown in FIG.

  First, when this process is started, in S510, it is determined whether or not the vehicle ID input in the previous S330 (hereinafter referred to as the target vehicle ID) exists in the management database 32, and an affirmative determination is made here. If so, the process proceeds to S530. If a negative determination is made, the process proceeds to S520.

In S520, the target vehicle ID and the ECU information 22 assigned to the target vehicle ID are newly registered in the management database 32 in association with each other, and the process proceeds to S570.
In S530, based on the ECU information 22 assigned to the target vehicle ID, the ECU information 22 corresponding to the vehicle ID is extracted in the management database 32.

  In subsequent S540, it is determined whether the ECU information 22 extracted in S530 includes product identification information (hereinafter referred to as target product identification information) that matches the ECU information 22 assigned to the target vehicle ID. If the determination is affirmative, the process proceeds to S560. If the determination is negative, the process proceeds to S550.

  In S550, ECU information 22 (product identification information, version information) assigned to the target vehicle ID is newly registered in the management database 32 in association with the target vehicle ID, and the process proceeds to S570.

  In S560, the version information corresponding to the target product identification information in the management database 32 is updated to the version information of the ECU information 22 assigned to the target vehicle ID, and the process proceeds to S570.

  In S570, a registration completion notification indicating that the ECU information 22 has been registered (or updated) in the management database 32 is transmitted to the vehicle based on the target vehicle ID together with the target product identification information, and the process ends.

<Operation>
In the vehicle program update system 1 configured as described above, as shown in FIG. 11, when the ignition switch of the vehicle 20 is turned on, the ECUs 2 and 3 on the in-vehicle network 6 are activated. A system activation notification (vehicle ID) is transmitted from the vehicle 20 to the management device 10.

  Next, the management device 10 that has received this system activation notification determines whether or not an update file for the vehicle 20 is prepared in the management database 32 based on the vehicle ID. An update file (including product identification information) is transmitted from the device 10 to the vehicle 20.

  And the vehicle 20 which received this update file updates the control program of ECU (target ECU) corresponding to product identification information based on an update file, and the update completion notification (product identification information, vehicle ID) after the update. ) Is transmitted from the vehicle 20 to the management apparatus 10. Finally, the management apparatus 10 that has received this update completion notification updates the version information for the target ECU of the vehicle 20 in the management database 32 based on the vehicle ID and product identification information.

  Further, in the vehicle program update system 1, when the ignition switch of the vehicle 20 is turned on, the management database 32 stores the flag based on the registration flag held by each ECU 2 and 3 and the information management table 23 held by the master ECU 2. It is determined whether or not unregistered ECU information 22 exists, and only when there is unregistered ECU information 22, a system activation notification including the ECU information 22 is transmitted from the vehicle 20 to the management device 10. .

  Next, the management apparatus 10 that has received this system activation notification registers the ECU information 22 in association with the vehicle ID in the management database 32 (or updates the version information), and after the registration, the registration completion notification (product identification information) ) Is transmitted from the management device 10 to the vehicle 20. Finally, the vehicle 20 that has received the registration completion notification sets the registration flag corresponding to the product identification information to ON and updates the ECU information 22 in the information management table 23.

<Effect>
As described above, in the vehicle program update system 1 of the present embodiment, when the ignition switch of the vehicle 20 is turned on, a system activation notification (vehicle ID) is transmitted from the vehicle 20, and therefore the management device 10 ( When the update file is prepared for distribution in the management database 32), the update file can be distributed to the vehicle 20 based on the vehicle ID immediately after receiving the system activation notification.

  Further, in the vehicle program update system 1, the vehicle 20 does not transmit all the ECU information 22 corresponding to each ECU 2, 3 when transmitting the system activation notification, but the ECU information 22 not registered in the management database 32. Only to the management apparatus 10. When the management apparatus 10 receives the system activation notification from the vehicle 20, it does not return the latest version information, but only when it is necessary to update the control programs of the ECUs 2 and 3 mounted on the vehicle 20. Send update files. Therefore, it is possible to suppress the occurrence of unnecessary communication costs related to the distribution of the update file.

  Further, in the vehicle program update system 1, when the slave ECU 3 in the vehicle 20 is replaced, when the ignition switch is switched from OFF to ON, the latest version of the program is already installed in the replaced slave ECU 3. If it is, the ECU information 22 of the slave ECU 3 is not transmitted, but only the system activation notification is transmitted to the management device 10. Therefore, it is possible to prevent unnecessary communication costs related to registration of the ECU information 22 in the management database 32.

[Other Embodiments]
As mentioned above, although embodiment of this invention was described, this invention is not limited to the said embodiment, In the range which does not deviate from the summary of this invention, it is possible to implement in various aspects.

  For example, in the program management process in the slave ECU 3 of the above embodiment, when a registration completion notification is received from the master ECU 2, the registration flag is set to ON, and based on this registration flag, the ECU information of the own ECU 3 is set to the master ECU 2 (and thus managed). However, the present invention is not limited to this.

  Specifically, every time the ignition switch of the vehicle 20 is turned on, the ECU information 22 of the own ECU 3 may be transmitted to the master ECU 2 regardless of the setting of the registration flag. In this case, the master ECU 2 determines that the transmission condition is satisfied when the ECU information 22 received from the slave ECU 3 is different from the ECU information 22 in the information management table 23 (or does not exist in the information management table 23). The ECU information 22 received from the slave ECU 3 may be transmitted to the management device 10.

  In the program management process in the master ECU 2 of the above embodiment, when the registration completion notification (including product identification information) is received from the management device 10, the received registration completion notification is transmitted to the slave ECU 3. Instead, a registration completion notification may be stored in association with the ECU information 22 in the information management table 23. That is, the update flag associated with the ECU information 22 in the information management table 23 may be set to ON (see FIG. 12).

  In addition, although the vehicle program update system 1 of the said embodiment is comprised as a system which updates the control program mounted in several ECU2, 3 on the vehicle-mounted network 6, it is not limited to this, For example, it may be configured as a system that updates a program installed in one specific ECU for each vehicle 20. The update target of the system 1 is not limited to the control program, and may be an OS, for example.

  DESCRIPTION OF SYMBOLS 1 ... Program update system for vehicles, 2 ... Master ECU, 3 ... Slave ECU, 6 ... In-vehicle network, 6a ... Communication bus, 7 ... Communication apparatus, 10 ... Management apparatus, 11 ... Transceiver, 12 ... Communication controller, 13 ... Microcomputer 15 ... Power supply circuit, 16 ... MPU, 17 ... Flash memory, 19 ... SRAM, 20 ... Vehicle, 22 ... ECU information, 23 ... Information management table, 31 ... Network I / F, 32 ... Management database, 33 ... Input section , 34... Control unit.

Claims (6)

Wireless communication between an electronic control device that is installed in a vehicle and controls a control target device set in advance and a management device that holds an update file for updating the program of the electronic control device to the latest version In the vehicle program update system in which the electronic control device receives the update file from the management device and updates a program installed in the electronic control device based on the received update file.
The electronic control device transmits a vehicle ID for identifying a vehicle on which the electronic control device is mounted to the management device at a preset inquiry timing,
The management device has a management database in which version information indicating a version of a program installed in the electronic control device is registered for each vehicle ID, and associates the update file with the vehicle ID in the management database. And when the vehicle ID is received from the electronic control unit, the update file is transmitted to the electronic control unit only when the update file corresponding to the vehicle ID exists in the management database. A vehicle program update system characterized by the above.   2. The vehicle program update system according to claim 1, wherein the inquiry timing is when an ignition switch of the vehicle is switched from OFF to ON. The electronic control device transmits an update completion notification including at least the vehicle ID to the management device after updating the program installed in the electronic control device,
The said management apparatus updates the said version information corresponding to the said vehicle ID in the said management database to the newest version based on the update completion notification received from the said electronic control apparatus. Item 3. The vehicle program update system according to Item 2. The electronic control device holds ECU information including product identification information of the electronic control device and the version information, and transmits the ECU information to the management device together with the vehicle ID when a preset transmission condition is satisfied. And
The management device registers the version information together with the product identification information in the management database in association with the vehicle ID based on the ECU information and the vehicle ID received from the electronic control device. The vehicle program update system according to any one of claims 1 to 3. The management device, after registering the version information in the management database, transmits a registration completion notification including at least the product identification information to the electronic control device,
Upon receiving the registration completion notification from the management device, the electronic control device stores the ECU information and the registration completion notification in association with each other based on the product identification information, and the registration completion notification at the inquiry timing. The vehicular program update system according to claim 4, wherein the transmission condition is satisfied when no is stored. The vehicle is equipped with a plurality of the electronic control devices,
Among the plurality of electronic control devices, an electronic control device having an information management table for managing the version information for each product identification information of each electronic control device is designated as a master ECU, and the electronic control device other than the master ECU. As a slave ECU,
The slave ECU outputs ECU information composed of product identification information of the slave ECU and the version information to the master ECU,
The master ECU compares the ECU information input from the slave ECU and the information management table, and when the product identification information is the same and the version information is different, the ECU information is stored together with the vehicle ID. To the management device,
The vehicle according to claim 4 or 5, wherein the management device updates the version information in the management database based on the ECU information and the vehicle ID received from the master ECU. Program update system.

Images