In-vehicle system, update control device, and program update control method

By segmenting the update data and combining the data of the target vehicle-mounted device and the selected vehicle-mounted device, the problem of insufficient storage capacity in the vehicle-mounted update device is solved, and the update data download and program update without backoff are achieved, which improves the efficiency and reliability of the update process. sex.

CN118922813APending Publication Date: 2024-11-08AUTONETWORKS TECH LTD +2
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380029337.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-04
Filing Date
2023-03-17
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In the vehicle-mounted update device, it is difficult to ensure the storage area of ​​the update program by sending back data, especially when the storage capacity of the update control device is insufficient.

Method used

By dividing the updated data into two parts, receiving and storing it from the external device, and generating update data by combining the target vehicle-mounted device with the selected vehicle-mounted device, ensuring the storage and transmission of the updated data and avoiding data backing. The selected vehicle-mounted device is appropriately selected to support the update process based on multiple conditions such as processing load, safety strength and storage capacity.

Benefits of technology

Even if the storage unit of the update control device is insufficient, the update data can be downloaded without backoff, ensuring the smooth progress of program updates, and optimizing the efficiency and reliability of the update process through appropriate selected conditions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118922813A_ABST
    Figure CN118922813A_ABST
Patent Text Reader

Abstract

An update control device is provided with: a reception unit that receives first partial data, which is partial data of update data used for updating a program, from an external device disposed outside a vehicle; a storage unit that stores the first partial data received by the reception unit; and a transmission unit that transmits the first partial data stored in the storage unit to a target vehicle-mounted device in order to cause the target vehicle-mounted device to combine the first partial data and second partial data and generate the update data, and that transmits the second partial data stored in the storage unit to the target vehicle-mounted device. The second partial data is partial data of the update data transmitted from a selected in-vehicle device that stores the second partial data transmitted from the external device, and is different from the first partial data, and the selected in-vehicle device stores the second partial data transmitted from the external device on the basis of a selected condition relating to each of the plurality of in-vehicle devices. A selection is made from the plurality of non-target in-vehicle devices.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to an in-vehicle system, an update control device, and a program update control method. This application claims priority based on Japanese application No. 2022-062429 filed on April 4, 2022, and all the contents described in the Japanese application are cited. Background Art

[0002] In a vehicle, an on-board ECU (Electronic Control Unit) for controlling on-board devices such as a powertrain system such as engine control and a body system such as air conditioning control is installed. Patent document 1 discloses an on-board update device, which temporarily stores (caches) an update program downloaded from an external server in a storage unit when updating the program of the on-board ECU, and sends the update program to the on-board ECU that is the update target. Before downloading the update program from the external server, the on-board update device disclosed in patent document 1 sends the back-off data stored in the storage unit to the external server or the on-board ECU that is not the update target, thereby ensuring the storage area for the update program.

[0003] Prior art literature Patent Literature Patent Document 1: Japanese Patent Application Publication No. 2021-015618 Summary of the invention

[0004] A vehicle-mounted system of a scheme of the present disclosure comprises: a target vehicle-mounted device, which is a vehicle-mounted device that is a target of program update; a plurality of non-target vehicle-mounted devices, which are vehicle-mounted devices that are not targets of program update; and an update control device, which controls the update of the program in the target vehicle-mounted device, the update control device comprising: a first receiving unit, which receives a first portion of data from an external device arranged outside the vehicle, the first portion of data being partial data of update data used in updating the program; a first storage unit, which stores the first portion of data received by the first receiving unit; and a first sending unit, which sends the first portion of data stored in the first storage unit to the target vehicle-mounted device, the selected vehicle-mounted device selected from the plurality of non-target vehicle-mounted devices comprising: a second receiving unit, which receives a second portion of data from the external device, the first portion of data being partial data of update data used in updating the program; a first storage unit, which stores the first portion of data received by the first receiving unit; and a first sending unit, which sends the first portion of data stored in the first storage unit to the target vehicle-mounted device, The second part of data is part of the update data and is different from the first part of data; a second storage unit, storing the second part of data received by the second receiving unit; and a second sending unit, sending the second part of data stored in the second storage unit to the target vehicle-mounted device, the target vehicle-mounted device includes: a third receiving unit, receiving the first part of data from the update control device and receiving the second part of data from the selected vehicle-mounted device; a generating unit, combining the first part of data and the second part of data received by the third receiving unit, and generating the update data; and an updating unit, using the update data generated by the generating unit to update the program, the selected vehicle-mounted device is selected from the multiple non-target vehicle-mounted devices based on the selection conditions related to each device of the multiple vehicle-mounted devices.

[0005] An update control device of a scheme of the present disclosure controls the update of a program in a target vehicle-mounted device, the target vehicle-mounted device being a vehicle-mounted device that is the update target of the program, wherein the update control device comprises: a receiving unit that receives first partial data from an external device arranged outside a vehicle, the first partial data being partial data of update data used in updating the program; a storage unit that stores the first partial data received by the receiving unit; and a sending unit that sends the first partial data stored in the storage unit to the target vehicle-mounted device so that the target vehicle-mounted device combines the first partial data and second partial data and generates the update data, the second partial data being partial data of the update data sent from a selected vehicle-mounted device and being different from the first partial data, the selected vehicle-mounted device being a vehicle-mounted device that stores the second partial data sent from the external device, and being selected from the plurality of non-target vehicle-mounted devices based on a selection condition related to each of the plurality of vehicle-mounted devices.

[0006] A program update control method according to one aspect of the present disclosure is performed by an update control device, the update control device controlling the updating of a program in a target vehicle-mounted device, the target vehicle-mounted device being a vehicle-mounted device to be updated with the program, wherein the program update control method comprises the following steps: the update control device receiving first partial data from an external device arranged outside a vehicle, the first partial data being partial data of update data used in updating the program; the update control device storing the received first partial data; and the update control device sending the stored first partial data to the target vehicle-mounted device in order to cause the target vehicle-mounted device to combine the first partial data with second partial data and generate the update data, the second partial data being partial data of the update data sent from a selected vehicle-mounted device and being different from the first partial data, the selected vehicle-mounted device being a vehicle-mounted device storing the second partial data sent from the external device, the selected vehicle-mounted device being selected from the plurality of non-target vehicle-mounted devices based on a selection condition associated with each of the plurality of vehicle-mounted devices.

[0007] The present disclosure can be implemented not only as an update control device having the characteristic structure as described above and a vehicle-mounted system including the update control device, but can also be implemented as a program update control method in which the characteristic processing in the update control device is set as a step, or as a program for enabling the update control device to perform the above-mentioned characteristic processing, or a part or all of the update control device can be implemented as a semiconductor integrated circuit. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 This is a schematic diagram for explaining an example of a program updating system according to an embodiment. Figure 2 This is a block diagram showing an example of the configuration of the vehicle-mounted system according to the embodiment. Figure 3 This is a block diagram showing an example of the structure of the OTA host according to the embodiment. Figure 4 This is a block diagram showing an example of the configuration of the ECU according to the embodiment. Figure 5 This is a functional block diagram showing an example of the functions of the vehicle-mounted system according to the embodiment. Figure 6 This is a diagram for explaining an example of the weight and score of each item in the selection condition according to the embodiment. Figure 7 This is a diagram for explaining an example of the structure of update data. Figure 8 This is a diagram for explaining an example of division of update data. Fig. 9AIt is a diagram showing an example of the structure of the first update data. Fig. 9B It is a diagram showing an example of the structure of the second update data. Fig.10 This is a timing chart for explaining an example of memory free capacity confirmation processing. Fig.11 This is a sequence diagram for explaining an example of split download processing. Fig.12 This is a flowchart showing an example of the selection process. Fig.13 This is a sequence diagram for explaining an example of program update processing. Fig.14A This is a flowchart showing a part of an example of selection processing according to a modification. Fig. 14B 1 is a flowchart showing another part of an example of the selection process of the modification. DETAILED DESCRIPTION

[0009] [Problems to be Solved by the Present Disclosure]

[0010] Sometimes, for example, when the back-off data is data that is essential for the operation of the on-vehicle update device, it may be difficult to secure a storage area for the update program by transmitting the back-off data.

[0011] [Effects of the present disclosure]

[0012] According to the present disclosure, even if the free capacity of the storage unit of the update control device is insufficient, update data can be downloaded without saving the data in the storage unit of the update control device.

[0013] <Overview of Embodiments of the Present Disclosure>

[0014] Hereinafter, embodiments of the present disclosure will be described in outline.

[0015] (1) The vehicle-mounted system of the present embodiment comprises: a target vehicle-mounted device, which is a vehicle-mounted device that is a target of program update; a plurality of non-target vehicle-mounted devices, which are vehicle-mounted devices that are not targets of program update; and an update control device, which controls the update of the program in the target vehicle-mounted device, the update control device comprising: a first receiving unit, which receives first partial data from an external device arranged outside the vehicle, the first partial data being partial data of update data used in updating the program; a first storage unit, which stores the first partial data received by the first receiving unit; and a first sending unit, which sends the first partial data stored in the first storage unit to the target vehicle-mounted device, the selected vehicle-mounted device selected from the plurality of non-target vehicle-mounted devices comprising: a first receiving unit, which receives first partial data from an external device arranged outside the vehicle, the first partial data being partial data of update data used in updating the program; a first storage unit, which stores the first partial data received by the first receiving unit; and a first sending unit, which sends the first partial data stored in the first storage unit to the target vehicle-mounted device, the selected vehicle-mounted device selected from the plurality of non-target vehicle-mounted devices comprising: A second receiving unit receives second partial data from the external device, the second partial data being partial data of the update data and different from the first partial data; a second storage unit stores the second partial data received by the second receiving unit; and a second sending unit sends the second partial data stored in the second storage unit to the target vehicle-mounted device, the target vehicle-mounted device comprising: a third receiving unit receives the first partial data from the update control device and receives the second partial data from the selected vehicle-mounted device; a generating unit combines the first partial data and the second partial data received by the third receiving unit and generates the update data; and an updating unit updates the program using the update data generated by the generating unit. Thus, the update control device stores a part of the update data and the selected vehicle-mounted device stores the other part of the update data, so that even if the free capacity of the storage unit of the update control device is insufficient, the update data can be downloaded without backing up the data in the storage unit of the update control device.

[0016] (2) In the above (1), the selected vehicle-mounted device may be selected from the plurality of non-target vehicle-mounted devices based on a selection condition related to each of the plurality of vehicle-mounted devices. Thus, the selected vehicle-mounted device can be selected from the plurality of non-target vehicle-mounted devices based on the selection condition.

[0017] (3) In the above (2), the selection condition may be a condition related to at least one of a processing load of the vehicle-mounted device when the vehicle is in a driving state, a processing load of the vehicle-mounted device when a passenger is on the vehicle, a security strength of the vehicle-mounted device, communication accessibility of the vehicle-mounted device, a free capacity of a storage unit provided in the vehicle-mounted device, a writing and reading speed of the storage unit, and a number of logical structure units in the storage unit of the vehicle-mounted device. Thus, the vehicle-mounted device can be appropriately selected by using the above conditions.

[0018] (4) In the above (3), the vehicle-mounted system may include an external communication device capable of communicating with the external device, and the security strength of the vehicle-mounted device connected to the same bus as the external communication device is lower than the security strength of the vehicle-mounted device connected to a bus different from the external communication device. Thus, the vehicle-mounted device can be appropriately selected according to the bus connected to the vehicle-mounted device in the vehicle-mounted system.

[0019] (5) In the above (3) or (4), the communication accessibility of the vehicle-mounted device connected to the same bus as the target vehicle-mounted device is higher than the communication accessibility of the vehicle-mounted device connected to a bus different from the target vehicle-mounted device. Thus, the selected vehicle-mounted device can be appropriately selected according to the bus connected to the vehicle-mounted device in the vehicle-mounted system.

[0020] (6) In any of the above (3) to (5), the number of logical structural units in the storage unit of the vehicle-mounted device may include a case where the non-volatile memory of the vehicle-mounted device is a single-bank memory or a case where the non-volatile memory of the vehicle-mounted device is a dual-bank memory. Thus, the vehicle-mounted device can be appropriately selected according to whether the storage unit of the vehicle-mounted device is a single-bank memory or a dual-bank memory.

[0021] (7) In any of the above (3) to (6), the update control device may also include: a selection unit that selects the selected vehicle-mounted device from the plurality of non-target vehicle-mounted devices based on the selection condition; and a notification unit that notifies the external device of the selected vehicle-mounted device selected by the selection unit. In this way, the selected vehicle-mounted device can be selected by the update control device mounted on the vehicle.

[0022] (8) In the above (7), the selection unit may assign a score to each of the plurality of non-target vehicle-mounted devices with respect to at least one of a processing load of the vehicle-mounted device when the vehicle is in a driving state, a processing load of the vehicle-mounted device when a passenger is on board the vehicle, a security strength of the vehicle-mounted device, communication accessibility of the vehicle-mounted device, a free capacity of a storage unit provided in the vehicle-mounted device, a writing and reading speed of the storage unit, and a number of logical structure units in the storage unit of the vehicle-mounted device, and select the selected vehicle-mounted device from the plurality of non-target vehicle-mounted devices based on the score. In this way, the non-target vehicle-mounted devices can be quantitatively evaluated with respect to the above items, and the selected vehicle-mounted device can be appropriately selected based on the evaluation result.

[0023] (9) In the above (8), the selection unit may set a weight for each of a plurality of items, namely, a processing load of the onboard device when the vehicle is in a driving state, a processing load of the onboard device when a passenger is on the vehicle, a security strength of the onboard device, communication accessibility of the onboard device, a free capacity of a storage unit provided in the onboard device, a writing and reading speed of the storage unit, and a number of logical structure units in the storage unit of the onboard device, and select the selected onboard device from the plurality of non-target onboard devices based on a result obtained by multiplying the weight by the score. In this way, the non-target onboard devices can be quantitatively evaluated according to the importance of the above items, and the selected onboard device can be appropriately selected according to the evaluation result.

[0024] (10) In the above (7), the selection condition may include a plurality of conditions related to the following plurality of items, the plurality of items being selected from the processing load of the onboard device when the vehicle is in a driving state, the processing load of the onboard device when a passenger is on the vehicle, the security strength of the onboard device, the communication accessibility of the onboard device, the free capacity of a storage unit provided in the onboard device, the writing and reading speed of the storage unit, and the number of logical structure units in the storage unit of the onboard device, and the selection unit selects the selected onboard device by sequentially determining the onboard device that meets the conditions from the plurality of non-target onboard devices. Thus, by sequentially determining the onboard devices that meet the plurality of conditions, it is possible to narrow down the onboard devices that are candidates for the selected onboard device.

[0025] (11) In any one of the above (1) to (10), the first receiving unit receives first update data from the external device, the first update data including the first partial data and first verification data for verifying the first partial data, the update control device includes a first verification unit, the first verification unit verifies the first partial data included in the first update data using the first verification data included in the first update data, the first sending unit sends the first partial data to the target vehicle-mounted device when verification of the first partial data by the first verification unit succeeds, the second receiving unit receives second update data from the external device, the second update data including the second partial data and second verification data for verifying the second partial data, the selected vehicle-mounted device includes a second verification unit, the second verification unit verifies the second partial data included in the second update data using the second verification data included in the second update data, and the second sending unit sends the second partial data to the target vehicle-mounted device when verification of the second partial data by the second verification unit succeeds. Thus, the first partial data and the second partial data can be verified separately.

[0026] (12) In any one of the above (1) to (11), the update data includes: an update program, which is an updated program; and program verification data, which is used to verify the update program, and the program verification data is included in either the first partial data or the second partial data. Thus, the update program included in the update data obtained by combining the first partial data and the second partial data can be verified.

[0027] (13) An update control device of this embodiment controls the updating of a program in a target vehicle-mounted device, the target vehicle-mounted device being a vehicle-mounted device to be updated with the program, wherein the update control device comprises: a receiving unit that receives first partial data from an external device disposed outside a vehicle, the first partial data being partial data of update data used in updating the program; a storage unit that stores the first partial data received by the receiving unit; and a sending unit that sends the first partial data stored in the storage unit to the target vehicle-mounted device so that the target vehicle-mounted device combines the first partial data with second partial data and generates the update data, the second partial data being partial data of the update data sent from a selected vehicle-mounted device and different from the first partial data, the selected vehicle-mounted device being a vehicle-mounted device storing the second partial data sent from the external device. Thus, the update control device stores a part of the update data and the selected vehicle-mounted device stores the other part of the update data, so that even if the free capacity of the storage unit of the update control device is insufficient, the update data can be downloaded without backing up the data in the storage unit of the update control device.

[0028] (14) A program update control method according to the present embodiment is performed by an update control device that controls the updating of a program in a target vehicle-mounted device, the target vehicle-mounted device being a vehicle-mounted device to be updated with the program, wherein the program update control method comprises the following steps: the update control device receives first partial data from an external device disposed outside a vehicle, the first partial data being partial data of update data used in updating the program; the update control device stores the received first partial data; and the update control device transmits the stored first partial data to the target vehicle-mounted device so that the target vehicle-mounted device combines the first partial data with second partial data and generates the update data, the second partial data being partial data of the update data transmitted from a selected vehicle-mounted device and being different from the first partial data, the selected vehicle-mounted device being a vehicle-mounted device storing the second partial data transmitted from the external device. Thus, the update control device stores a part of the update data and the selected vehicle-mounted device stores the other part of the update data, so that even if the free capacity of the storage unit of the update control device is insufficient, the update data can be downloaded without backing up the data in the storage unit of the update control device.

[0029] <Details of the embodiments of the present disclosure>

[0030] The following describes the details of the embodiments of the present disclosure with reference to the accompanying drawings. In addition, at least a part of the embodiments described below may be arbitrarily combined.

[0031] [1. Program update system]

[0032] Figure 1 This is a schematic diagram for explaining an example of the program updating system according to the present embodiment.

[0033] The program update system is a system for updating a control program of an onboard device mounted on the vehicle 10. The program update system includes the vehicle 10 and an OTA (Over The Air) server 50. The vehicle 10 is equipped with an onboard system as described below.

[0034] The vehicle 10 can communicate with a device outside the vehicle through wireless communication. The vehicle 10 has a wireless communication terminal that complies with, for example, the fifth generation mobile communication system (5G) or the fourth generation mobile communication system (4G), and can perform wireless communication with the base station 20. The base station 20 is connected to the Internet 30. The OTA server 50 is also connected to the Internet 30. With such a structure, the vehicle 10 and the OTA server 50 can communicate with each other.

[0035] The OTA server 50 can provide data for program update to the vehicle 10. The OTA server 50 is an example of an “external device”.

[0036] [2. In-vehicle system]

[0037] Figure 2 This is a block diagram showing an example of the configuration of the vehicle-mounted system according to the present embodiment.

[0038] The vehicle-mounted system 100 of the present embodiment includes an integrated ECU (Electronic Control Unit) 200 and individual ECUs 300A, 300B, 300C, 300D, and 300E. The vehicle-mounted system 100 is composed of the integrated ECU 200, the individual ECUs 300A, 300B, 300C, 300D, and 300E and a communication cable (communication bus) connecting them.

[0039] The integrated ECU 200 is a gateway that relays communications between a plurality of individual ECUs. The integrated ECU 200 is an OTA host that controls updates of control programs of the individual ECUs 300A, 300B, 300C, 300D, and 300E. The integrated ECU 200 is an example of an "update control device." Hereinafter, the integrated ECU 200 is also referred to as the "OTA host 200."

[0040] A plurality of individual ECUs 300A, 300B, 300C, 300D, and 300E are disposed in various parts of the vehicle 10. Individual ECUs 300A, 300B, 300C, 300D, and 300E individually control the hardware of each part of the vehicle 10, or monitor the status of the hardware of each part of the vehicle 10. For example, individual ECUs 300A, 300B, 300C, 300D, and 300E are ECUs for a powertrain system, a body system, and an information and entertainment system. Individual ECUs 300A, 300B, 300C, 300D, and 300E are examples of "vehicle-mounted devices." In addition, in the following description, individual ECUs are also referred to as "ECUs," and individual ECUs 300A, 300B, 300C, and 300D are also collectively referred to as "ECUs 300."

[0041] The OTA host 200 is connected to the ECU 300A, 300B, 300C, 300D, and 300E via the vehicle buses 400A, 400B, and 400C such as the CAN (Controller Area Network) bus. Specifically, the ECU 300A and 300B are connected to the bus 400A. The ECU 300C and 300D are connected to the bus 400B. The ECU 300E is connected to the bus 400C. The OTA host 200 can communicate with the ECU 300A, 300B, 300C, 300D, and 300E.

[0042] The OTA host 200 is connected to the external communication device 500 via the bus 400C. The external communication device 500 is a wireless communication terminal compliant with, for example, 5G or 4G, such as a TSU (Telematics Control Unit). The external communication device 500 can communicate with the OTA server 50. The external communication device 500 relays the communication between the OTA host 200 and the OTA server 50.

[0043] The bus 400C connected to the external communication device 500 is an external vehicle communication bus used not only for communication within the vehicle but also for communication with a device outside the vehicle. The buses 400A and 400B are internal vehicle communication buses used only for communication within the vehicle.

[0044] [3. OTA host structure]

[0045] Figure 3 2 is a block diagram showing an example of the structure of the OTA host according to the present embodiment. The OTA host 200 includes a processor 201 , a nonvolatile memory 202 , a volatile memory 203 , and a communication interface (I / F) 204 .

[0046] The volatile memory 203 is, for example, a semiconductor memory such as SRAM (Static Random Access Memory) or DRAM (Dynamic Random Access Memory). The non-volatile memory 202 is, for example, a flash memory, a hard disk, etc. The non-volatile memory 202 is capable of reading and writing data. In the non-volatile memory 202, an update control program 205 as a computer program and data used in the execution of the update control program 205 are stored. The OTA host 200 is capable of saving the first update data downloaded from the OTA server 50 to the non-volatile memory 202. The OTA host 200 is configured with a computer, and each function of the OTA host 200 is performed by executing the update control program 205, which is a computer program stored in the storage device of the computer.

[0047] The update control program 205 is a program for controlling the update of the control program of the ECU 300. More specifically, the update control program 205 is a program for selecting a storage target of a part (second partial data) of the update data of the control program from the ECUs 300A, 300B, 300C, 300D, and 300E, and notifying the selected ECU, i.e., the selected ECU, to the OTA server 50. The update control program 205 is a program for downloading first update data including first partial data of the update data from the OTA server 50, saving the first partial data included in the downloaded first update data to the nonvolatile memory 202, and sending the first partial data to the ECU that is the update target, i.e., the target ECU.

[0048] The nonvolatile memory 202 stores key data 206 . The key data 206 is used to verify the update data (first update data) downloaded from the OTA server 50 .

[0049] The processor 201 is, for example, a CPU (Central Processing Unit). However, the processor 201 is not limited to a CPU. The processor 201 may also be a GPU (Graphics Processing Unit). The processor 201 is configured to be able to execute a computer program. However, the processor 201 may include, for example, an ASIC (Application Specific Integrated Circuit) in part or a programmable logic device such as an FPGA (Field Programmable Gate Array) in part.

[0050] The communication I / F 204 is, for example, a communication interface that complies with the CAN (Controller Area Network) communication protocol used as an in-vehicle network. The communication I / F 204 may also be a communication interface that complies with protocols such as CAN FD (CAN with Flexible Data rate), Ethernet (Ethernet is a registered trademark), and LIN (Local Interconnect Network). The communication I / F 204 includes a plurality of communication ports, which are respectively connected to buses 400A, 400B, and 400C. The communication I / F 204 is respectively connected to ECUs 300A, 300B, 300C, 300D, and 300E via buses 400A, 400B, and 400C. The OTA host 200 can communicate with ECUs 300A, 300B, 300C, 300D, and 300E through the communication I / F 204. Furthermore, the OTA host 200 can communicate with the OTA server 50 via the external communication device 500 through the communication I / F 204 .

[0051] [4. OTA Server]

[0052] The OTA server 50 is composed of a processor, a storage device (a non-volatile memory and a volatile memory), a communication I / F, etc. The OTA server 50 provides an updated program (hereinafter referred to as “update program”) to the ECU 300 .

[0053] The OTA server 50 can download update data as a data packet including an update program and verification data (hereinafter also referred to as "PG verification data") used in verifying the update program to the OTA host 200. When the OTA server 50 receives a request to split the update data from the OTA host 200, it can split the update data to generate a first partial data and a second partial data, and separately download the first update data including the first partial data and the second update data including the second partial data.

[0054] [5. ECU structure]

[0055] Figure 4 ECU 300 is a block diagram showing an example of the configuration of the ECU according to the present embodiment. ECU 300 includes a processor 301 , a nonvolatile memory 302 , a volatile memory 303 , a communication I / F 304 , and an input / output I / F (I / O) 305 .

[0056] The volatile memory 303 is, for example, a semiconductor memory such as SRAM or DRAM. The nonvolatile memory 302 is, for example, a flash memory, a hard disk, or a ROM. The nonvolatile memory 302 is managed by a memory controller in units of a memory bank composed of one or more flash memory chips. That is, a memory bank is a logical structural unit of the nonvolatile memory 302. The memory bank is defined for each surface of a memory module that constitutes the nonvolatile memory 302. A nonvolatile memory 302 that is equipped with a flash memory chip only on one side of a memory module is a single-bank memory, and a nonvolatile memory 302 that is equipped with flash memory chips on both sides of a memory module is a dual-bank memory. In the nonvolatile memory 302, a control program 306 as a computer program and data used in the execution of the control program 306 are stored. The individual ECU 300 is configured with a computer, and each function of the individual ECU 300 is performed by executing a computer program stored in a storage device of the computer, namely, a control program 306. The control program 306 is, for example, a program for controlling a part of the hardware of the vehicle 10.

[0057] In the nonvolatile memory 302, an update program 308 and data used in executing the update program 308 are stored. The update program 308 is a program for receiving update data from the OTA host 200 and using the received update data to update the control program 306. In the nonvolatile memory 302, key data 307 is also stored. The key data 307 is used to decode the PG verification data included in the update program.

[0058] The nonvolatile memory 302 also stores an update assisting program 309 and data used in executing the update assisting program 309. The update assisting program 309 is a program for receiving second update data transmitted from the OTA server 50 via the OTA host 200, storing the second partial data included in the received second update data in the nonvolatile memory 302, and transmitting the second partial data to the target ECU.

[0059] The processor 301 is, for example, a CPU. However, the processor 301 is not limited to a CPU. The processor 301 may also be a GPU. The processor 301 may include, for example, an ASIC in part or a programmable logic device such as an FPGA in part.

[0060] The communication I / F 304 is, for example, a communication interface in accordance with CAN. The communication I / F 304 may also be a communication interface in accordance with protocols such as CAN FD, Ethernet, and LIN. The communication I / F 304 includes at least one communication port, which is connected to any one of the buses 400A, 400B, and 400C. The communication I / F 304 is connected to the OTA host 200 via any one of the buses 400A, 400B, and 400C. The ECU 300 can communicate with the OTA host 200 through the communication I / F 304.

[0061] The I / O 305 is connected to, for example, a sensor or an actuator (not shown). The I / O 305 can receive sensor data output from a sensor or output a control signal to an actuator.

[0062] [5. Functions of the in-vehicle system]

[0063] Figure 5 300B is a functional block diagram showing an example of the functions of the vehicle-mounted system of the present embodiment. In the following description, the following example is described: the control program 306 of ECU 300A is updated, that is, ECU 300A is the target ECU, and ECU 300B is selected as the storage target of a part of the update data, that is, ECU 300B is the selected ECU. The target ECU is an example of a "target vehicle-mounted device", and the selected ECU is an example of a "selected vehicle-mounted device".

[0064] The processor 201 of the OTA host 200 executes the update control program 205, thereby realizing the functions of the selection unit 211, the notification unit 212, the first receiving unit 213, the first storage unit 214, the first verification unit 215, and the first sending unit 216. The processor 301 of the selected ECU 310 (ECU 300B in this example) among the ECUs 300A, 300B, 300C, 300D, and 300E executes the update support program 309, thereby realizing the functions of the second receiving unit 311, the second storage unit 312, the second verification unit 313, and the second sending unit 314. Furthermore, the processor 301 of the target ECU 320 (ECU 300A in this example) among ECUs 300A, 300B, 300C, 300D, and 300E executes the update program 308, thereby realizing the functions of the third receiving unit 321, the third storage unit 322, the generating unit 323, the third verifying unit 324, and the updating unit 325.

[0065] The selection unit 211 selects the selected ECU 310 from the ECU 300B, 300C, 300D, 300E (non-target vehicle-mounted devices) other than the target ECU 320, i.e., the ECU 300A, based on the selection condition. The selection condition is a condition related to the plurality of ECUs 300B, 300C, 300D, 300E, respectively. In a specific example, the selection condition is a condition related to at least one of the processing load of the ECU 300 when the vehicle 10 is in a driving state, the processing load of the ECU 300 when a passenger is riding in the vehicle 10, the security strength of the ECU 300, the communication accessibility of the ECU 300, the free capacity of the non-volatile memory 302 provided in the ECU 300, the writing and reading speed of the non-volatile memory 302, and the number of logical structure units in the non-volatile memory 302 of the ECU 300.

[0066] For example, the security strength of ECU 300 is determined by buses 400A, 400B, and 400C connected to ECU 300. Specifically, the security strength of ECU 300E connected to external communication bus 400C is lower than that of ECU 300A, 300B, 300C, and 300D connected to internal communication buses 400A and 400B.

[0067] For example, the communication accessibility of ECU 300 is determined by buses 400A, 400B, and 400C connected to ECU 300. Specifically, the communication accessibility of ECU 300B connected to the same bus 400A as the target ECU 320 is higher than the communication accessibility of ECU 300C, 300D, and 300E connected to buses 400B and 400C different from the target ECU 320.

[0068] For example, according to the number of logical structural units in the nonvolatile memory 302 included in the ECU 300 , there is a classification into an ECU having a storage unit with a single bank and an ECU having a storage unit with two banks.

[0069] For example, the selection unit 211 assigns a score to each ECU300B, 300C, 300D, 300E with respect to at least one of the processing load of ECU300 when the vehicle 10 is in a driving state, the processing load of ECU300 when a passenger is riding in the vehicle 10, the security strength of ECU300, the communication accessibility of ECU300, the free capacity of the non-volatile memory 302 provided in ECU300, the writing and reading speed of the non-volatile memory 302, and the number of logical structure units in the non-volatile memory 302 possessed by ECU300, and selects ECU310 from ECU300B, 300C, 300D, 300E based on the score. Furthermore, in a specific example, the selection unit 211 sets a weight for each of multiple items including the processing load of ECU300 when the vehicle 10 is in a driving state, the processing load of ECU300 when a passenger is riding in the vehicle 10, the security strength of ECU300, the communication accessibility of ECU300, the free capacity of the non-volatile memory 302 provided in ECU300, the writing and reading speeds of the non-volatile memory 302, and the number of logical structure units in the non-volatile memory 302 possessed by ECU300, and selects ECU310 from ECU300B, 300C, 300D, and 300E based on the result obtained by multiplying the score by the weight.

[0070] Figure 6 FIG. 1 is a diagram for explaining an example of the weight and score of each item in the selection condition of the present embodiment. Figure 6 In the example of FIG. 1 , the processing load of ECU 300 when vehicle 10 is in the driving state (in Figure 6 The weight of item x1 is 15%. The score (value) of item x1 of ECU 300 with high processing load during driving of vehicle 10 (hereinafter referred to as "driving state") is 0, and the score of item x1 of ECU 300 with low processing load in the driving state is 1. That is, since ECU 300B and 300C have high processing load in the driving state, the score of item x1 of ECU 300B and 300C is 0. Since ECU 300D and 300E have low processing load in the driving state, the score of item x1 of ECU 300D and 300E is 1.

[0071] Regarding the processing load of ECU 300 when a passenger is on board vehicle 10 (in Figure 6The weight of item x2 is 15%. When the passenger is on the vehicle 10 (hereinafter referred to as "on-board state"), the score of item x2 of ECU 300 with high processing load is 0, and the score of item x2 of ECU 300 with low processing load in the on-board state is 1. That is, since ECU 300C and 300E have high processing load in the on-board state, the score of item x2 of ECU 300C and 300E is 0. Since ECU 300B and 300D have low processing load in the on-board state, the score of item x2 of ECU 300B and 300D is 1.

[0072] The weight of the security strength x3 of ECU 300 is 20%. The score of item x3 of ECU 300 with low security strength, i.e., ECU 300E connected to the external communication bus 400C, is 0, and the score of item x3 of ECU 300 with high security strength, i.e., ECU 300B, 300C, 300D connected to the internal communication buses 400A, 400B, is 1.

[0073] The weight of communication accessibility x4 of ECU 300 is 10%. The score of item x4 of ECU 300 with low communication accessibility, i.e., ECU 300C, 300D, 300E connected to buses 400B, 400C different from target ECU 320, is 0, and the score of item x4 of ECU 300 with high communication accessibility, i.e., ECU 300B connected to the same bus 400A as target ECU 320, is 1.

[0074] Regarding the available capacity of the nonvolatile memory 302 provided in the ECU 300 (in Figure 6 The weight of item "memory free capacity") x5 is 10%. The score for item x5 is assigned as a real value corresponding to the free capacity of non-volatile memory 302. For example, the score is calculated by free capacity (MB) of non-volatile memory 302 × 0.01. However, if the calculation result obtained by the above formula is 1 or more, the score is set to 1. Figure 6 In the example, the free memory capacity of ECU 300B is 10MB, so the score of item x5 of ECU 300B is 0.1. The free memory capacity of ECU 300C is 2MB, so the score of item x5 of ECU 300C is 0.02. The free memory capacity of ECU 300D is 50MB, so the score of item x5 of ECU 300D is 0.5. The free memory capacity of ECU 300E is 150MB, so the score of item x5 of ECU 300B is 1.

[0075] Regarding the writing and reading speed of the nonvolatile memory 302 provided in the ECU 300 (in Figure 6The weight of item "memory write / read speed") x6 is 10%. The score for item x6 is assigned as a real value corresponding to the write and read speed of the non-volatile memory 302. For example, the score is calculated by write speed (kbps) × 0.001 + read speed (kbps) × 0.001. However, if the calculation result obtained by the above formula is 1 or more, the score is set to 1. Figure 6 In the example, the memory write speed of ECU300B is 500 kbps and the read speed is 500 kbps, so the score of item x6 of ECU300B is 1. The memory write speed of ECU300C is 100 kbps and the read speed is 200 kbps, so the score of item x6 of ECU300C is 0.3. The memory write speed of ECU300D is 200 kbps and the read speed is 500 kbps, so the score of item x6 of ECU300D is 0.7. The memory write speed of ECU300E is 1 Mbps and the read speed is 1 Mbps, so the score of item x6 of ECU300E is 1.

[0076] Regarding the number of logical structural units (memory banks) in the nonvolatile memory 302 of the ECU 300 (in Figure 6 The weight of item x7 is 20%. The score of item x7 of ECU 300B and 300E having the non-volatile memory 302 with two banks is 1. The score of item x7 of ECU 300C and 300D having the non-volatile memory 302 with one bank is 0.

[0077] Back to Figure 5The selection unit 211 calculates the evaluation value E of each ECU 300 by E=15x1+15x2+20x3+10x4+10x5+10x6+20x7. The calculation formula of the evaluation value E represents the selection condition. The selection unit 211 selects the ECU 300 with the largest evaluation value E as the storage target of a part of the update data (selecting the ECU 310) from among the candidate ECUs 300 (excluding the target ECU 320 from the candidates). In this example, the selection condition is set as a condition related to each of the items of the processing load of the ECU 300 when the vehicle 10 is in the driving state, the processing load of the ECU 300 when the passenger is on the vehicle 10, the security strength of the ECU 300, the communication accessibility of the ECU 300, the free capacity of the nonvolatile memory 302 provided in the ECU 300, the writing and reading speed of the nonvolatile memory 302, and the number of logical structural units in the nonvolatile memory 302 of the ECU 300, but the present invention is not limited thereto. It may also be a condition related to one or more items selected from the processing load of the ECU 300 when the vehicle 10 is in the driving state, the processing load of the ECU 300 when the passenger is on the vehicle 10, the security strength of the ECU 300, the communication accessibility of the ECU 300, the free capacity of the nonvolatile memory 302 provided in the ECU 300, the writing and reading speed of the nonvolatile memory 302, and the number of logical structural units in the nonvolatile memory 302 of the ECU 300.

[0078] The notification unit 212 notifies the OTA server 50 of the selected ECU 310 selected by the selection unit 211. For example, the notification unit 212 can notify the OTA server 50 of the identification information of the selected ECU 310.

[0079] The OTA server 50 divides the update data into a first portion of data and a second portion of data. The OTA server 50 sends the first update data including the first portion of data, and sends the second update data including the second portion of data.

[0080] Figure 7610 is a diagram for explaining an example of the structure of update data. The update data 610 is data used in updating the control program 306 performed by the object ECU 320. The update data 610 includes an update program 601 (binary data of the update program in executable form) and program verification data (hereinafter referred to as "PG verification data") 602. The PG verification data 602 is data used in the verification of the update program 601 performed by the object ECU 320. The OTA server 50 encrypts the hash value of the update program 601 using the key data to generate the PG verification data 602. The OTA server 50 combines the update program 601 with the PG verification data 602 and generates the update data 610.

[0081] Figure 7 The update data packet 600 shown includes update data 610 and OTA host verification data 603. The OTA host verification data 603 is data used in the verification of the update data 610 by the OTA host 200. The OTA server 50 encrypts the hash value of the update data 610 by the key data to generate the OTA host verification data 603. The OTA server 50 combines the update data 610 with the OTA host verification data 603 and generates the update data packet 600.

[0082] When there is a free area of ​​a size capable of storing the update data packet 600 in the nonvolatile memory 202 of the OTA host 200, the OTA server 50 downloads the update data packet 600 to the OTA host 200. The OTA host 200 stores the downloaded update data packet 600 in the nonvolatile memory 202. The OTA host 200 decodes the OTA host verification data 603 included in the update data packet 600 using the key data 206 stored in the nonvolatile memory 202. The OTA host 200 verifies the update data 610 by calculating a hash value of the update data 610 included in the update data packet 600 and comparing the calculated hash value with the hash value obtained by synthesizing the OTA host verification data 603.

[0083] When the two hash values ​​match, the OTA host 200 sends the update data 610 to the target ECU 320. The target ECU 320 stores the received update data 610 in the non-volatile memory 302. The target ECU 320 decodes the PG verification data 602 included in the update data 610 using the key data 307 stored in the non-volatile memory 302. The target ECU 320 calculates the hash value of the update program 601 included in the update data 610, and compares the calculated hash value with the hash value obtained by synthesizing the PG verification data 602, thereby verifying the update program 601. When the verification of the update program 601 succeeds, that is, when the two hash values ​​match, the target ECU 320 installs the update program 601 and updates the control program 306.

[0084] When there is no free area of ​​a size that can store the update data packet 600 in the nonvolatile memory 202 of the OTA host 200, the selection unit 211 selects the selected ECU 310. The OTA host 200 requests the OTA server 50 to divide the update data 610. The request includes information of the selected ECU 310. That is, the OTA host 200 notifies the OTA server 50 of the selected ECU 310 by requesting the OTA server 50 to divide the update data 610.

[0085] Upon receiving the request to divide the update data 610 , the OTA server 50 divides the update data 610 . Figure 8 1 is a diagram for explaining an example of division of the update data 610. In the present embodiment, the OTA server 50 divides the update data 610 into two parts, the first partial data 611 and the second partial data 612. However, the update data 610 may be divided into three or more partial data.

[0086] The update data 610 is composed of the update program 601 and the PG verification data 602. The PG verification data 602 is included in either the first partial data 611 or the second partial data 612. However, a part of the PG verification data 602 may be included in the first partial data 611, and the rest of the PG verification data 602 may be included in the second partial data 612.

[0087] Fig. 9A It is a diagram showing an example of the structure of the first update data. Fig. 9AThe first update data 620 shown includes the first partial data 611 and the OTA host verification data 621. The OTA host verification data 621 is data used in the verification of the first partial data 611 by the OTA host 200, and is an example of the “first verification data”. The OTA server 50 encrypts the hash value of the first partial data 611 by the key data to generate the OTA host verification data 621. The OTA server 50 combines the first partial data 611 with the OTA host verification data 621 and generates the first update data 620.

[0088] Fig. 9B It is a diagram showing an example of the structure of the second update data. Fig. 9B The second update data 630 shown includes the second partial data 612 and the ECU verification data 631. The ECU verification data 631 is data used in the verification of the second partial data 612 by the selected ECU 310 and is an example of the “second verification data”. The OTA server 50 encrypts the hash value of the second partial data 612 by the key data to generate the ECU verification data 631. The OTA server 50 combines the second partial data 612 with the ECU verification data 631 and generates the second update data 630.

[0089] Back to Figure 5 , the OTA server 50 sends the first update data 620 to the OTA host 200. The first receiving unit 213 of the OTA host 200 receives the first update data 620 sent from the OTA server 50. The first storage unit 214 stores the first update data 620 received by the first receiving unit 213.

[0090] The first verification unit 215 decodes the OTA host verification data 621 included in the first update data 620 using the key data 206 stored in the nonvolatile memory 202. The first verification unit 215 calculates a hash value of the first partial data 611 included in the first update data 620, and compares the calculated hash value with a hash value obtained by synthesizing the OTA host verification data 621, thereby verifying the first partial data 611.

[0091] When verification of the first partial data 611 succeeds, that is, when the two hash values ​​match, the first transmitting unit 216 transmits the first partial data 611 to the target ECU 320 .

[0092] The OTA server 50 transmits the second update data 630 to the OTA host 200. The OTA host 200 transmits the received second update data 630 to the selected ECU 310. The second receiving unit 311 of the selected ECU 310 receives the second update data 630 transmitted from the OTA server 50. The second storage unit 312 stores the second update data 630 received by the second receiving unit 311.

[0093] The second verification unit 313 decodes the ECU verification data 631 included in the second update data 630 using the key data 307 stored in the nonvolatile memory 302. The second verification unit 313 calculates a hash value of the second partial data 612 included in the second update data 630, and compares the calculated hash value with a hash value obtained by synthesizing the ECU verification data 631, thereby verifying the second partial data 612.

[0094] When verification of second partial data 612 succeeds, that is, when the two hash values ​​match, second transmitting unit 314 transmits second partial data 612 to target ECU 320 .

[0095] The third receiving section 321 of the target ECU 320 receives the first partial data 611 transmitted from the OTA host 200. The third storage section 322 stores the received first partial data 611. The third receiving section 321 receives the second partial data 612 transmitted from the selected ECU 310. The third storage section 322 stores the received second partial data 612.

[0096] The generating unit 323 combines the first partial data 611 and the second partial data 612 received by the third receiving unit and generates (restores) the update data 610 .

[0097] The third verification unit 324 decodes the PG verification data 602 included in the update data 610 using the key data 307 stored in the non-volatile memory 302. The third verification unit 324 calculates a hash value of the update program 601 included in the update data 610, and compares the calculated hash value with the hash value obtained by synthesizing the PG verification data 602, thereby verifying the update program 601.

[0098] When the verification of the update program 601 succeeds, that is, when the two hash values ​​match, the update unit 325 installs the update program 601 and updates the control program 306 .

[0099] [6. Operation of the program update system]

[0100] Next, the operation of the program updating system according to the present embodiment will be described.

[0101] [6-1. Memory free capacity confirmation process]

[0102] OTA host 200 executes a memory available capacity confirmation process for confirming the available capacity of nonvolatile memory 302 of ECU 300A, 300B, 300C, 300D, 300E in order to collect information used for selecting a storage target of a part of update data. Fig.10 This is a timing chart for explaining an example of memory free capacity confirmation processing.

[0103] The OTA host 200 sends a confirmation request for the free capacity of the non-volatile memory 302 to the ECUs 300A, 300B, 300C, 300D, and 300E (steps S11 to S13). Upon receiving the request, each of the ECUs 300A, 300B, 300C, 300D, and 300E obtains information indicating the free capacity of the non-volatile memory 302 and sends the information, thereby notifying the OTA host 200 of the free capacity of the non-volatile memory (steps S21 to S23). The OTA host 200 receives the information sent from the ECUs 300A, 300B, 300C, 300D, and 300E, and obtains the free capacity of the non-volatile memory 302 of each of the ECUs 300A, 300B, 300C, 300D, and 300E.

[0104] OTA host 200 transmits a request to check the available capacity of nonvolatile memory 302 at regular intervals, for example. Thus, the available capacity of nonvolatile memory 302 of each ECU 300A, 300B, 300C, 300D, 300E is regularly updated, and OTA host 200 can select a storage target for a portion of update data.

[0105] [6-2. Split download processing]

[0106] As described above, when there is no free area large enough to store update data packet 600 in nonvolatile memory 202 of OTA host 200 , the program update system executes the divided download process of dividing the update data and downloading the divided update data. Fig.11 This is a sequence diagram for explaining an example of split download processing.

[0107] If a new version of the control program 306 is released for a certain ECU 300, the update data 610 including the update program 601 of the new version is stored in the OTA server 50. In this case, the OTA server 50 sends an update request for the control program 306 to the OTA host 200. Upon receiving the update request for the control program 306, the OTA host 200 sends a response to the OTA server 50 (step S31).

[0108] Next, the OTA host 200 sends authentication data for authenticating that the OTA host 200 is a genuine host to the OTA server 50, and the OTA server 50 performs authentication. If the authentication is successful, the OTA server 50 notifies the OTA host 200 of the authentication success (step S32).

[0109] The OTA host 200 sends a size confirmation request for the update data packet 600 to the OTA server 50 (step S33 ). Upon receiving the size confirmation request for the update data packet 600 , the OTA server 50 notifies the OTA host 200 of the size of the update data packet 600 (step S34 ).

[0110] The OTA host 200 compares the free capacity of the non-volatile memory 202 with the size of the update data packet 600 to determine whether the update data packet 600 can be saved in the non-volatile memory 202, that is, whether the update data packet 600 can be downloaded (step S35). If the update data packet 600 can be downloaded, the update data packet 600 is downloaded from the OTA server 50 as described above. Fig.11 In FIG. 1 , the processing when the update package 600 can be downloaded is omitted, and only the processing when the update package 600 cannot be downloaded is shown.

[0111] If OTA host 200 determines that update data package 600 cannot be downloaded, OTA host 200 executes a process of selecting a storage target for a portion of the update data (step S36 ).

[0112] Fig.12 1 is a flowchart showing an example of the selection process. The processor 201 of the OTA host 200 confirms the state of the power supply of the vehicle 10 and determines the ECU 300 in operation (supplying power). When the ignition switch (IG) of the vehicle 10 is turned on, power is supplied to all ECUs 300, and all ECUs 300 operate. When the IG of the vehicle 10 is turned off, power is supplied only to ECUs 300 driven by the battery power supply, and these ECUs 300 operate. The processor 201 determines the ECUs 300 in operation other than the target ECU 320 as candidates for the storage object of a part of the update data (step S101).

[0113] Next, the processor 201 calculates the evaluation values ​​E of all candidates using the above-mentioned evaluation value E formula (step S102 ). The processor 201 selects the candidate with the largest evaluation value E as the storage target of a part of the update data (selects the ECU 310 ) (step S103 ). The selection process ends here.

[0114] Back to Fig.11 , the OTA host 200 sends a request to split the update data to the OTA server 50 (step S37). The split request includes the identification information of the selected ECU 310. In addition, instead of the identification information of the selected ECU 310, the OTA server 50 may be notified of the free capacity of the nonvolatile memory 302 of the selected ECU 310.

[0115] If the OTA server 50 receives the request, it divides the update data 610 into sizes corresponding to the OTA host 200 and the selected ECU 310 (step S38). The OTA server 50 generates the OTA host verification data 621, and combines the first part of the data 611 with the OTA host verification data 621 to produce the first update data 620. The OTA server 50 generates the ECU verification data 631, and combines the second part of the data 612 with the ECU verification data 631 to produce the second update data 630 (step S39).

[0116] The OTA server 50 sends the first update data 620 to the OTA host 200 (step S40). Upon receiving the first update data 620, the OTA host 200 saves the first update data 620 to the non-volatile memory 202 (step S41). The OTA host 200 uses the OTA host verification data 621 to verify the first partial data 611 included in the first update data 620 (step S42).

[0117] The OTA server 50 sends the second update data 630 to the OTA host 200 (step S43). If the OTA host 200 receives the second update data 630, it transfers the received second update data 630 to the selected ECU 310 (step S44). If the selected ECU 310 receives the second update data 630, it saves the second update data 630 in the non-volatile memory 302 (step S45). The selected ECU 310 verifies the second partial data 612 included in the second update data 630 using the ECU verification data 631 (step S46). At this point, the split download process ends.

[0118] [6-3. Program update processing]

[0119] The program updating system executes a program updating process for updating the control program of the target ECU 320 after the divided download process. Fig.13 This is a sequence diagram for explaining an example of program update processing.

[0120] If verification of the first partial data 611 succeeds, the OTA host 200 transmits the first partial data 611 to the target ECU 320 (step S51 ). If the target ECU 320 receives the first partial data 611 , it stores the received first partial data 611 in the nonvolatile memory 302 (step S52 ).

[0121] The OTA host 200 transmits a transmission instruction of the second partial data 612 to the selected ECU 310 (step S53). The selected ECU 310, which has successfully verified the second partial data 612, receives the transmission instruction of the second partial data 612, and transmits the second partial data 612 to the target ECU 320 (step S54). The target ECU 320, which receives the second partial data 612, saves the received second partial data 612 in the non-volatile memory 302 (step S55).

[0122] The target ECU 320 combines the received first partial data 611 with the received second partial data 612 and restores the update data 610 (step S56). The target ECU 320 uses the PG verification data 602 to verify the update program 601 included in the update data 610 (step S57). If the verification is successful, the target ECU 320 installs the update program 601 into the non-volatile memory 302 and updates the control program 306 (step S58). At this point, the program update process ends.

[0123] [7. Modifications]

[0124] The selection unit 211 may select the selected ECU 310 by sequentially determining an ECU 300 that meets the conditions from among the ECUs 300B, 300C, 300D, and 300E with respect to a plurality of conditions included in the selection condition.

[0125] Fig.14A and Fig. 14B 2 is a flowchart showing an example of the selection process of this modification. In this modification, the processor 201 of the OTA host 200 executes the following selection process (step S36 ).

[0126] Processor 201 determines whether vehicle 10 is in the IG-on state (step S201). When vehicle 10 is in the IG-on state ("Yes" in step S201), processor 201 determines all ECUs 300 other than target ECU 320 as candidates for saving a portion of update data 610 (step S202). When vehicle 10 is in the IG-off state ("No" in step S201), processor 201 determines ECUs 300 other than ECUs 300 that receive power supply from an IG power supply (i.e., ECUs 300 that receive power supply from a battery power supply) as candidates for saving a portion of update data 610 (step S203). After step S202 or S203, processor 201 proceeds to step S204.

[0127] Processor 201 determines whether the passenger is in vehicle 10 (step S204). If the passenger is in vehicle 10 ("Yes" in step S204), processor 201 removes ECU 300 with a high processing load in the vehicle state from the candidate (step S205). After step S205, processor 201 proceeds to step S206. If the passenger is not in vehicle 10 ("No" in step S204), processor 201 also proceeds to step S206.

[0128] Processor 201 determines whether vehicle 10 is in driving (traveling) (step S206). If vehicle 10 is in driving (“Yes” in step S206), processor 201 removes ECU 300 with high processing load in driving state from candidates (step S207). After step S207, processor 201 proceeds to step S208. If vehicle 10 is not in driving, that is, in a stopped state (“No” in step S206), processor 201 also proceeds to step S208.

[0129] The processor 201 determines whether the security strength of the target ECU 320 is high or low (step S208). If the target ECU 320 is connected to the in-vehicle communication bus 400A, 400B, the processor 201 determines that the security strength of the target ECU 320 is high ("Yes" in step S201). In this case, the processor 201 deletes the ECU 300 on the in-vehicle communication bus 400A, 400B from the candidate (step S209). After step S209, the processor 201 transfers to step S212.

[0130] If the target ECU 320 is connected to the external vehicle communication bus 400C, the processor 201 determines that the security strength of the target ECU 320 is low ("No" in step S201). In this case, the processor 201 determines whether the ECU 300 connected to the same bus as the target ECU 320 is included in the candidate (step S210). When the ECU 300 connected to the same bus as the target ECU 320 is included in the candidate ("Yes" in step S210), the processor 201 deletes the ECU 300 connected to a bus different from the target ECU 320 from the candidate (step S211). After step S211, the processor 201 transfers to step S212. When the ECU 300 connected to the same bus as the target ECU 320 is not included in the candidate ("No" in step S210), the processor 201 also transfers to step S212.

[0131] Processor 201 selects ECU 300 having the largest available capacity in nonvolatile memory 302 among the candidates as a target for storing a part of update data 610 (step S212 ). The selection process ends here.

[0132] [8. Other variations]

[0133] In the above embodiment, the integrated ECU 200 is used as the OTA master, but the present invention is not limited thereto and the individual ECU 300 may be the OTA master.

[0134] In the above embodiment, the OTA host 200 selects a storage target of a part of the update data 610, but the present invention is not limited thereto. For example, the OTA server 50 may select a storage target of a part of the update data 610. In this case, the OTA host 200 may also notify the OTA server 50 of the free capacity of the non-volatile memory 302 of each ECU 300A, 300B, 300C, 300D, 300E.

[0135] [9. Effects of implementation methods]

[0136] The vehicle-mounted system 100 includes a target ECU 320 (target vehicle-mounted device) which is an ECU 300 to be updated for the control program 306, a plurality of ECUs 300B, 300C, 300D, and 300E (non-target vehicle-mounted devices) which are ECUs 300 not to be updated for the control program 306, and an OTA host 200 (update control device) which controls the update of the control program 306 in the target ECU 320. The OTA host 200 includes a first receiving unit 213, a first storage unit 214, and a first transmitting unit 216. The first receiving unit 213 receives first partial data 611 from an OTA server 50 (external device) arranged outside the vehicle 10. The first partial data 611 is partial data of the update data 610 used for updating the control program 306. The first storage unit 214 stores the first partial data 611 received by the first receiving unit 213. The first transmitting unit 216 transmits the first partial data 611 stored in the first storage unit 214 to the target ECU 320. The selected ECU 310 (selected on-vehicle device) selected from the plurality of ECUs 300B, 300C, 300D, and 300E includes a second receiving unit 311, a second storage unit 312, and a second transmitting unit 314. The second receiving unit 311 receives the second partial data 612 from the OTA server 50. The second partial data 612 is partial data of the update data 610, and is data different from the first partial data 611. The second storage unit 312 stores the second partial data 612 received by the second receiving unit 311. The second transmitting unit 314 transmits the second partial data 612 stored in the second storage unit 312 to the target ECU 320. The target ECU 320 includes a third receiving unit 321, a generating unit 323, and an updating unit 325. The third receiving unit 321 receives the first partial data 611 from the OTA host 200, and receives the second partial data 612 from the selected ECU 310. The generator 323 combines the first partial data 611 and the second partial data 612 received by the third receiver 321 to generate the update data 610. The updater 325 updates the control program 306 using the update data 610 generated by the generator 323. Thus, the OTA host 200 stores a part of the update data 610, and the selected ECU 310 stores the other part of the update data 610. Therefore, even if the free capacity of the non-volatile memory 202 of the OTA host 200 is insufficient, the update data 610 can be downloaded without backing up the data in the non-volatile memory 202 of the OTA host 200.

[0137] The selected ECU 310 may be selected from the ECUs 300B, 300C, 300D, and 300E based on the selection conditions related to the plurality of ECUs 300A, 300B, 300C, 300D, and 300E. Thus, the selected ECU 310 can be selected from the ECUs 300B, 300C, 300D, and 300E according to the selection conditions.

[0138] The selection condition may also be a condition related to at least one of the processing load of the ECU 300 when the vehicle 10 is in a driving state, the processing load of the ECU 300 when a passenger is riding in the vehicle 10, the security strength of the ECU 300, the communication accessibility of the ECU 300, the free capacity of the nonvolatile memory 302 provided in the ECU 300, the writing and reading speed of the nonvolatile memory 302 provided in the ECU 300, and the number of logical structural units in the nonvolatile memory 302 of the ECU 300. Thus, the selected ECU 310 can be appropriately selected by the above-mentioned conditions.

[0139] The in-vehicle system 100 may also include an external communication device 500 capable of communicating with the OTA server 50. The security strength of the ECU 300 connected to the same bus 400C as the external communication device 500 may be lower than the security strength of the ECU 300 connected to the buses 400A and 400B different from the external communication device 500. Thus, the selected ECU 310 can be appropriately selected according to the bus connected to the ECU 300 in the in-vehicle system 100.

[0140] The communication accessibility of ECU 300 connected to the same bus 400A as the target ECU 320 may be higher than that of ECU 300 connected to buses 400B and 400C different from the target ECU 320. Thus, the selected ECU 310 can be appropriately selected according to the bus connected to the ECU 300 in the vehicle-mounted system 100.

[0141] The number of logical structural units in the nonvolatile memory 302 of the ECU 300 may include the case where the nonvolatile memory 302 of the ECU 300 is a single bank memory or a dual bank memory. Thus, the selected ECU 310 can be appropriately selected according to whether the nonvolatile memory 302 of the ECU 300 is a single bank memory or a dual bank memory.

[0142] The OTA host 200 may include a selection unit 211 and a notification unit 212. The selection unit 211 selects a selected ECU 310 from the plurality of ECUs 300B, 300C, 300D, and 300E based on the selection condition. The notification unit 212 notifies the OTA server 50 of the selected ECU 310 selected by the selection unit 211. Thus, the selected ECU 310 can be selected by the OTA host 200 mounted on the vehicle 10.

[0143] The selection unit 211 may assign a score to each of the ECUs 300B, 300C, 300D, and 300E with respect to at least one of the processing load of the ECU 300 when the vehicle 10 is in the driving state, the processing load of the ECU 300 when the passenger is on the vehicle 10, the security strength of the ECU 300, the communication accessibility of the ECU 300, the free capacity of the nonvolatile memory 302 provided in the ECU 300, the writing and reading speed of the nonvolatile memory 302 provided in the ECU 300, and the number of logical structural units in the nonvolatile memory 302 provided in the ECU 300, and select the selected ECU 310 from the ECUs 300B, 300C, 300D, and 300E based on the score. Thus, the ECUs 300B, 300C, 300D, and 300E can be quantitatively evaluated with respect to the above items, and the selected ECU 310 can be appropriately selected based on the evaluation results.

[0144] The selection unit 211 may set a weight for each of a plurality of items, including the processing load of the ECU 300 when the vehicle 10 is in the driving state, the processing load of the ECU 300 when the passenger is on the vehicle 10, the security strength of the ECU 300, the communication accessibility of the ECU 300, the free capacity of the nonvolatile memory 302 provided in the ECU 300, the writing and reading speed of the nonvolatile memory 302 provided in the ECU 300, and the number of logical structure units in the nonvolatile memory 302 of the ECU 300, and select the selected ECU 310 from the ECU 300B, 300C, 300D, and 300E based on the result obtained by multiplying the score by the weight. Thus, the ECU 300B, 300C, 300D, and 300E can be quantitatively evaluated according to the importance of the above items, and the selected ECU 310 can be appropriately selected according to the evaluation result.

[0145] (9) The selection condition may include a plurality of conditions related to a plurality of items, the plurality of items being selected from the processing load of the ECU 300 when the vehicle 10 is in the driving state, the processing load of the ECU 300 when the passenger is on the vehicle 10, the security strength of the ECU 300, the communication accessibility of the ECU 300, the free capacity of the nonvolatile memory 302 provided in the ECU 300, the writing and reading speed of the nonvolatile memory 302 provided in the ECU 300, and the number of logical structure units in the nonvolatile memory 302 of the ECU 300. The selection unit 211 may select the selected ECU 310 by sequentially determining the ECU 300 that meets the conditions from the ECU 300B, 300C, 300D, and 300E with respect to the plurality of conditions. Thus, by sequentially determining the ECU 300 that meets the plurality of conditions, the ECU 300 that is a candidate for the selected ECU 310 can be narrowed down.

[0146] The first receiving unit 213 may also receive first update data 620 from the OTA server 50, the first update data 620 including first partial data 611 and OTA host verification data 621 (first verification data) for verifying the first partial data 611. The OTA host 200 may also include a first verification unit 215. The first verification unit 215 verifies the first partial data 611 included in the first update data 620 using the OTA host verification data 621 included in the first update data 620. The first sending unit 216 may also send the first partial data 611 to the target ECU 320 when the verification of the first partial data 611 by the first verification unit 215 is successful. The second receiving unit 311 may also receive second update data 630 from the OTA server 50, the second update data 630 including second partial data 612 and ECU verification data 631 (second verification data) for verifying the second partial data 612. The selected ECU 310 may also include a second verification unit 313. The second verification unit 313 verifies the second partial data 612 included in the second update data 630 using the ECU verification data 631 included in the second update data 630. The second transmission unit 314 may transmit the second partial data 612 to the target ECU 320 when the verification of the second partial data 612 by the second verification unit 313 succeeds. In this way, the first partial data 611 and the second partial data 612 can be verified separately.

[0147] The update data 610 may also include the updated program, that is, the update program 601, and the PG verification data 602 used in verifying the update program 601. The PG verification data 602 may also be included in either the first partial data 611 or the second partial data 612. Thus, the update program 601 included in the update data 610 obtained by combining the first partial data 611 and the second partial data 612 can be verified.

[0148] [10. Notes]

[0149] An update control program is used in an update control device, the update control device controlling the update of a program in a target vehicle-mounted device, the target vehicle-mounted device being a vehicle-mounted device to be updated by the program, wherein: The update control program causes the computer to function as the following units: a receiving unit that receives first partial data from an external device disposed outside the vehicle, the first partial data being partial data of update data used in updating the program; a storage unit, storing the first portion of data received by the receiving unit; and a transmitting unit, wherein the transmitting unit transmits the first partial data stored in the storage unit to the target vehicle-mounted device, so that the target vehicle-mounted device combines the first partial data with the second partial data and generates the update data, wherein the second partial data is partial data of the update data transmitted from the selected vehicle-mounted device and is different from the first partial data, The selected in-vehicle device is an in-vehicle device storing the second partial data transmitted from the external device.

[0150] [11. Supplementary Note]

[0151] The embodiments disclosed herein are illustrative in all aspects and are not restrictive. The scope of rights of the present invention is indicated by the claims rather than the embodiments described above, and includes all modifications within the meaning and scope equivalent to the claims.

[0152] Description of symbols 10 Vehicles 20 base stations 30 Internet 50OTA server (external device) 100 Car Systems 200 integrated ECU (OTA host, update control device) 201 processor 202 Non-volatile memory 203 Volatile Memory 204 communication interface (communication I / F) 205 Update control program 206 Key Data 211 Selected Department 212 Notification Department 213 First receiving unit 214 first storage unit 215 First Verification Department 216 First Sending Unit 300, 300A, 300B, 300C, 300D, 300E single ECU (ECU, vehicle-mounted device) 301 processor 302 Non-volatile memory 303 Volatile Memory 304 communication interface (communication I / F) 305 Input and output interface (I / O) 306 Control Program 307 Key Data 308 Updater 309 Update auxiliary program 310 Select ECU (Select vehicle device) 311 Second receiving unit 312 Second storage unit 313 Second Verification Department 314 Second sending unit 320 Target ECU (target vehicle-mounted device) 321 Third Receiving Department 322 third storage unit 323 Generation Department 324 Third Verification Department 325 Update Department 400A, 400B in-vehicle communication bus 400C off-board communication bus 500 external communication device 600 Update Data Packet 601 Updater 602 Program verification data (PG verification data) 603OTA host verification data 610 Update Data 611 Part 1 Data 612 Part 2 Data 620 First Update Data 621OTA host verification data (first verification data) 630 Second Update Data 631ECU verification data (second verification data).

Claims

1. A vehicle-mounted system comprising: The target vehicle-mounted device is a vehicle-mounted device to which the program is to be updated; The plurality of non-target vehicle-mounted devices are vehicle-mounted devices that are not targets of program update; as well as an update control device for controlling the update of the program in the target vehicle-mounted device, The update control device comprises: a first receiving unit receiving first partial data from an external device disposed outside the vehicle, the first partial data being partial data of update data used in updating the program; a first storage unit, storing the first portion of data received by the first receiving unit; as well as a first transmitting unit, configured to transmit the first portion of data stored in the first storage unit to the target vehicle-mounted device; The selected vehicle-mounted device selected from the plurality of non-target vehicle-mounted devices includes: a second receiving unit, receiving second partial data from the external device, wherein the second partial data is partial data of the update data and is different from the first partial data; a second storage unit, storing the second portion of data received by the second receiving unit; and a second transmitting unit, transmitting the second partial data stored in the second storage unit to the target vehicle-mounted device; The target vehicle-mounted device comprises: a third receiving unit, receiving the first portion of data from the update control device, and receiving the second portion of data from the selected vehicle-mounted device; a generating unit that combines the first partial data and the second partial data received by the third receiving unit and generates the update data; and An updating unit updates the program using the update data generated by the generating unit.

2. The vehicle-mounted system according to claim 1, wherein: The selected in-vehicle device is selected from the plurality of non-target in-vehicle devices based on a selection condition related to each of the plurality of in-vehicle devices.

3. The vehicle-mounted system according to claim 2, wherein: The selected condition is a condition related to at least one of the processing load of the vehicle-mounted device when the vehicle is in a driving state, the processing load of the vehicle-mounted device when a passenger is riding in the vehicle, the security strength of the vehicle-mounted device, the communication accessibility of the vehicle-mounted device, the free capacity of a storage unit provided in the vehicle-mounted device, the writing and reading speeds of the storage unit, and the number of logical structure units in the storage unit of the vehicle-mounted device.

4. The vehicle-mounted system according to claim 3, wherein: The in-vehicle system includes an external communication device capable of communicating with the external device. The security strength of an on-vehicle device connected to the same bus as the external communication device is lower than the security strength of an on-vehicle device connected to a bus different from the external communication device.

5. The vehicle-mounted system according to claim 3, wherein: The communication accessibility of an on-vehicle device connected to the same bus as the target on-vehicle device is higher than the communication accessibility of an on-vehicle device connected to a bus different from the target on-vehicle device.

6. The vehicle-mounted system according to claim 3, wherein: The number of logical structural units in the storage unit included in the vehicle-mounted device includes a case where the nonvolatile memory included in the vehicle-mounted device has a single bank and a case where the nonvolatile memory has a dual bank.

7. The vehicle-mounted system according to any one of claims 3 to 6, wherein: The update control device comprises: a selecting unit that selects the selected vehicle-mounted device from among the plurality of non-target vehicle-mounted devices based on the selection condition; and The notifying unit notifies the external device of the selected vehicle-mounted device selected by the selecting unit.

8. The vehicle-mounted system according to claim 7, wherein: The selection unit assigns a score to each of the multiple non-target vehicle-mounted devices with respect to at least one of a processing load of the vehicle-mounted device when the vehicle is in a driving state, a processing load of the vehicle-mounted device when a passenger is riding in the vehicle, a security strength of the vehicle-mounted device, communication accessibility of the vehicle-mounted device, a free capacity of a storage unit provided in the vehicle-mounted device, a writing and reading speed of the storage unit, and the number of logical structure units in the storage unit possessed by the vehicle-mounted device, and selects the selected vehicle-mounted device from the multiple non-target vehicle-mounted devices based on the score.

9. The vehicle-mounted system according to claim 8, wherein: The selection unit sets a weight for each of a plurality of items, namely, a processing load of the vehicle-mounted device when the vehicle is in a driving state, a processing load of the vehicle-mounted device when a passenger is riding in the vehicle, a security strength of the vehicle-mounted device, communication accessibility of the vehicle-mounted device, free capacity of a storage unit provided in the vehicle-mounted device, writing and reading speeds of the storage unit, and the number of logical structure units in the storage unit of the vehicle-mounted device, and selects the selected vehicle-mounted device from the plurality of non-target vehicle-mounted devices based on a result obtained by multiplying the score by the weight.

10. The vehicle-mounted system according to claim 7, wherein: The selected conditions include a plurality of conditions related to the following items, the plurality of items being selected from a processing load of the onboard device when the vehicle is in a driving state, a processing load of the onboard device when an occupant is riding in the vehicle, a security strength of the onboard device, communication accessibility of the onboard device, a free capacity of a storage unit provided in the onboard device, a writing and reading speed of the storage unit, and a number of logical structure units in the storage unit of the onboard device, The selection unit selects the selected vehicle-mounted device by sequentially determining a vehicle-mounted device that satisfies the conditions from among the plurality of non-target vehicle-mounted devices with respect to the plurality of conditions.

11. The vehicle-mounted system according to claim 1, wherein: The first receiving unit receives first update data from the external device, the first update data including the first partial data and first verification data for verifying the first partial data. The update control device includes a first verification unit that verifies the first partial data included in the first update data using the first verification data included in the first update data. The first transmitting unit transmits the first partial data to the target vehicle-mounted device when verification of the first partial data by the first verifying unit succeeds. The second receiving unit receives second update data from the external device, the second update data including the second partial data and second verification data for verifying the second partial data, the selected in-vehicle device includes a second verification section that verifies the second partial data included in the second update data using the second verification data included in the second update data, The second transmitting unit transmits the second partial data to the target vehicle-mounted device when verification of the second partial data by the second verifying unit succeeds.

12. The vehicle-mounted system according to claim 1, wherein: The update data includes: an update program, which is an updated program; and program verification data, which is used in the verification of the update program. The program verification data is included in either the first portion of data or the second portion of data.

13. An update control device for controlling the update of a program in a target vehicle-mounted device, the target vehicle-mounted device being a vehicle-mounted device to be updated with the program, wherein: The update control device comprises: a receiving unit that receives first partial data from an external device disposed outside the vehicle, the first partial data being partial data of update data used in updating the program; a storage unit, storing the first part of data received by the receiving unit; as well as a transmitting unit, wherein the transmitting unit transmits the first partial data stored in the storage unit to the target vehicle-mounted device, so that the target vehicle-mounted device combines the first partial data with the second partial data and generates the update data, wherein the second partial data is partial data of the update data transmitted from the selected vehicle-mounted device and is different from the first partial data, The selected in-vehicle device is an in-vehicle device storing the second partial data transmitted from the external device.

14. A program update control method, performed by an update control device, the update control device controlling the update of a program in a target vehicle-mounted device, the target vehicle-mounted device being a vehicle-mounted device to be updated by the program, wherein: The program update control method comprises the following steps: The update control device receives first partial data from an external device disposed outside the vehicle, the first partial data being partial data of update data used in updating the program; The update control device stores the received first portion of data; as well as The update control device transmits the stored first partial data to the target vehicle-mounted device in order to cause the target vehicle-mounted device to combine the first partial data with second partial data and generate the update data, wherein the second partial data is partial data of the update data transmitted from the selected vehicle-mounted device and is different from the first partial data, The selected in-vehicle device is an in-vehicle device storing the second partial data transmitted from the external device.