Center, update management method, and update management program

Abstract

To provide a center, an update management method, and an update management program that, in updating software of an ECU through OTA, can update to software of an appropriate version conforming to a target ECU to be updated.SOLUTION: A center according to the present disclosure comprises: a communication section that receives, from an OTA master, first identification information for identifying a plurality of electronic control units; a storage section that, for every electronic control unit, stores conformity information defining a version conforming to corresponding software; a specification section that, by using the conformity information, specifies a conforming version in regard to a target electronic control unit being a software update target from among the plurality of electronic control units identified by the first identification information; and a control section that communicates with the OTA master to perform control of updating the software of the target electronic control unit to the conforming version specified by the specification section.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present disclosure relates to a center for controlling software updates of an ECU (electronic control unit), an update management method, an update management program, and the like. [Background technology]

[0002] A vehicle is equipped with multiple ECUs (electronic control units) for controlling the operation of the vehicle. The ECU includes a processor, a temporary storage unit such as RAM, and a non-volatile storage unit such as flash ROM, and the processor executes software stored in the non-volatile storage unit to realize the control functions of the ECU. The software stored in each ECU is rewritable, and by updating the software to a newer version, it is possible to improve the functions of each ECU or add new vehicle control functions.

[0003] One known technology for updating ECU software is OTA (Over The Air) technology, which wirelessly connects an in-vehicle communication device connected to an in-vehicle network to a communication network such as the Internet, downloads software from an OTA center (sometimes simply called the "center") via wireless communication, and installs the downloaded software to update or add programs to the ECU (see, for example, Patent Document 1).

[0004] Software updates by OTA are triggered when a campaign, which is an event for performing a software update, is registered on the server and then the vehicle requests the OTA center to check whether update data is available. If a campaign is available, the vehicle updates the software of the target ECU, which is the ECU to be updated, by sequentially downloading the update data, installing the update data, and activating the updated software. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2004-326689 A Summary of the Invention [Problem to be solved by the invention]

[0006] Even for the same vehicle model, the design of the installed ECU changes depending on the production period, etc. Also, in the market, ECUs may be replaced with new or old models due to part replacement, etc. In this way, even for the same vehicle model, there are vehicles equipped with ECUs of various generations (versions). Also, depending on the ECU version, there may be incompatible software versions. For this reason, when updating ECU software via OTA, it is necessary to update to a software version that is compatible with the target ECU that is to be updated.

[0007] Therefore, an object of the present disclosure is to provide a center, an update management method, an update management program, etc. that can update ECU software to an appropriate version that is compatible with the target ECU to be updated when updating ECU software via OTA. [Means for solving the problem]

[0008] The center according to the present disclosure includes an OTA master that controls software updates of multiple electronic control units installed in a vehicle, a center capable of communicating via a network and including a communication unit that receives first identification information that identifies the multiple electronic control units from the OTA master, a memory unit that stores compatibility information that defines a compatible version for corresponding software for each electronic control unit, an identification unit that uses the compatibility information to identify a compatible version for a target electronic control unit that is the subject of a software update among the multiple electronic control units identified by the first identification information, and a control unit that communicates with the OTA master to control the updating of the software of the target electronic control unit to the compatible version identified by the identification unit.

[0009] The update management method disclosed herein is a method executed by a computer having a processor, a memory, and a communication device capable of communicating via a network with an OTA master that controls software updates of multiple electronic control units mounted on a vehicle, and includes the steps of receiving identification information that identifies the multiple electronic control units from the OTA master, using compatibility information that defines a compatible version for the corresponding software for each electronic control unit to identify a compatible version for a target electronic control unit that is the subject of a software update among the multiple electronic control units identified by the identification information, and communicating with the OTA master to control updating the software of the target electronic control unit to the identified compatible version.

[0010] The update management program of the present disclosure is a program executed by a computer having a processor, a memory, and a communication device capable of communicating via a network with an OTA master that controls software updates of multiple electronic control units installed in a vehicle, and includes the steps of receiving identification information that identifies the multiple electronic control units from the OTA master, using compatibility information that defines a compatible version for the corresponding software for each electronic control unit to identify a compatible version for a target electronic control unit that is the subject of a software update among the multiple electronic control units identified by the identification information, and communicating with the OTA master to control updating the software of the target electronic control unit to the identified compatible version. Effect of the Invention

[0011] According to the present disclosure, it is possible to provide a center, an update management method, an update management program, and the like that can update software to an appropriate version compatible with a target ECU that is the object of the update when updating ECU software by OTA. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram showing an example of an overall configuration of a network system according to an embodiment; [Diagram 2] A block diagram showing an example of a schematic configuration of the OTA center shown in FIG. [Diagram 3] A block diagram showing an example of the schematic configuration of the OTA master shown in Figure 1. [Figure 4] A functional block diagram showing an example of the OTA center shown in FIG. 1. [Diagram 5] Functional block diagram showing an example of the OTA master shown in Figure 1. [Figure 6] A flowchart showing an example of a control process executed by an OTA master according to an embodiment. [Figure 7] A flowchart showing an example of a control process executed by an OTA master according to an embodiment. [Figure 8] A flowchart showing an example of a control process executed by an OTA center according to an embodiment. [Figure 9] FIG. 5 is a diagram for explaining an example of compatibility information stored in advance in the OTA center shown in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] (One embodiment) Fig. 1 is a block diagram showing an example of an overall configuration of a network system according to an embodiment. Fig. 2 is a block diagram showing an example of a schematic configuration of an OTA center shown in Fig. 1. Fig. 3 is a block diagram showing an example of a schematic configuration of an OTA master shown in Fig. 1.

[0014] The network system shown in FIG. 1 is a system for updating software of ECUs (Electronic Control Units) 13a to 13d installed in a vehicle, and includes an OTA center (e.g., a server; sometimes simply referred to as the "center") 1 and an in-vehicle network 2 installed in the vehicle.

[0015] The OTA center 1 is capable of wirelessly communicating with an OTA master 11 mounted on a vehicle via a communication network 5 such as the Internet, and manages software updates for ECUs 13a to 13d mounted on the vehicle.

[0016] 2, the OTA center 1 includes a CPU 21, a RAM 22, a storage device 23, and a communication device 24. The storage device 23 includes a readable / writable storage medium such as a hard disk or SSD, and stores a program for performing software update management, information used for the update management, and update data for the ECU. The CPU 21 executes the program read from the storage device 23 by using the RAM 22 as a working area, thereby executing a control process, which will be described later. The communication device 24 communicates with the OTA master 11 via the communication network 5.

[0017] The in-vehicle network 2 includes an OTA master 11, a communication module 12, a plurality of ECUs 13a to 13d, and an HMI (Human Machine Interface; for example, a display device of a car navigation system that allows input operations) 14. The OTA master 11 is connected to the communication module 12 via a bus 15a, to the ECUs 13a and 13b via a bus 15b, to the ECUs 13c and 13d via a bus 15c, and to the HMI 14 via a bus 15d. The OTA master 11 can wirelessly communicate with the OTA center 1 via the communication module 12. The OTA master 11 controls software update of an ECU (sometimes referred to as a "target ECU") to be updated among the ECUs 13a to 13d based on update data acquired from the OTA center 1. The communication module 12 is a communication device that connects the in-vehicle network 2 and the OTA center 1. The ECUs 13a to 13d control the operation of each part of the vehicle. The HMI 14 is used to perform various displays during software update processing of the ECUs 13a to 13d, such as displaying the presence of update data, displaying a consent request screen for requesting consent to the software update from a user or administrator, displaying update results, etc. Note that, although four ECUs 13a to 13d are illustrated in FIG. 1, the number of ECUs is not limited.

[0018] Each of the ECUs 13a to 13d includes a CPU, a RAM, a non-volatile memory, and a communication device. The CPU executes software (programs) read from the non-volatile memory (data storage area) using the RAM as a working area, and communicates with other devices via a bus as necessary using the communication device, thereby implementing the functions of the ECU.

[0019] 3, the OTA master 11 includes a microcomputer 35 including a CPU 31, a RAM 32, a ROM 33, and a storage device 34, and a communication device 36. The CPU 31 executes a program read from the ROM 33 by using the RAM 32 as a working area, thereby executing a control process, which will be described later. The communication device 36 communicates with the communication module 12, the ECUs 13a to 13d, and the HMI 14 via the buses 15a to 15d shown in FIG.

[0020] Here, the software update process consists of a phase of downloading update data from the OTA center 1, a phase of transferring the downloaded update data to the target ECU to be updated and installing the update data in the memory area of ​​the target ECU, and an activation phase of enabling the updated version of the software installed in the target ECU.

[0021] Downloading is a process of receiving update data for updating the software of the ECU, transmitted from the OTA center 1, and storing it in the storage device 34. The downloading phase includes not only receiving the update data but also controlling a series of processes related to the download, such as judging whether the download can be performed and verifying the update data. Installing is a process of writing an updated program (update software) to the non-volatile memory of the target ECU to be updated, based on the downloaded update data. The installing phase includes not only executing the installation but also controlling a series of processes related to the installation, such as judging whether the installation can be performed, transferring the update data, and verifying the updated program. Activating is a process of activating (enabling) the installed updated program. The activating phase includes not only executing the activation but also controlling a series of processes related to the activation, such as judging whether the activation can be performed and verifying the execution result.

[0022] The update data transmitted from the OTA center 1 to the OTA master 11 may include any of update software for the ECU, compressed data obtained by compressing the update software, and divided data obtained by dividing the update software or the compressed data. The update data may also include an identifier (ECU ID) that identifies the target ECU to be updated, and an identifier (ECU software ID) that identifies the software before the update. The update data is downloaded as a distribution package, and the distribution package includes update data for a single or multiple ECUs.

[0023] If the update data includes the update software itself, in the installation phase, the OTA master 11 transfers the update data (i.e., the update software) to the target ECU. Also, if the update data includes compressed data, difference data, or divided data of the update software, the OTA master 11 may transfer the update data to the target ECU and the target ECU may generate the update software from the update data, or the OTA master 11 may generate the update software from the update data and then transfer the update software to the target ECU. Here, the update software can be generated by decompressing the compressed data and assembling the difference data or divided data.

[0024] The target ECU can install the update software based on an installation request from the OTA master 11. Alternatively, the target ECU that receives the update data can autonomously install the software without receiving an explicit instruction from the OTA master 11.

[0025] The activation of the update software can be performed by the target ECU based on an activation request from the OTA master 11. Alternatively, the target ECU that has received the update data may autonomously activate the software without receiving an explicit instruction from the OTA master 11.

[0026] Fig. 4 is an example of a functional block diagram of the OTA center 1 shown in Fig. 1. As shown in Fig. 4, the OTA center 1 includes a storage unit 26, a communication unit 27, an identification unit 28, and a control unit 29. The communication unit 27, the identification unit 28, and the control unit 29 are realized by the CPU 21 shown in Fig. 2 executing a program stored in the storage device 23 using the RAM 22. The storage unit 26 is realized by the storage device 23 shown in Fig. 2.

[0027] Fig. 5 is an example of a functional block diagram of the OTA master 11 shown in Fig. 1. As shown in Fig. 5, the OTA master 11 includes a storage unit 37, a communication unit 38, and a control unit 39. The communication unit 38 and the control unit 39 are realized by the CPU 31 shown in Fig. 3 executing a program stored in the ROM 33 using the RAM 32. The storage unit 37 is realized by the storage device 34 shown in Fig. 3.

[0028] Fig. 6 and Fig. 7 are flowcharts showing an example of a control process executed by the OTA master 11 according to the present embodiment. Fig. 8 is a flowchart showing an example of a control process executed by the OTA center 1 according to the present embodiment. The control process according to the present embodiment will be described below with reference to the flowcharts shown in Figs. 6 to 8.

[0029] First, an example of a control process of the OTA master 11 will be described with reference to FIGS.

[0030] In step S1 of FIG. 6, the control unit 39 waits until it is detected that the ignition (IG) of the vehicle is turned on, and when it is detected that the ignition is turned on, the control unit 39 moves the process to step S2.

[0031] In step S2, the control unit 39 acquires, from each of the ECUs of the vehicle, an ECU ID that identifies the type and version of the ECU, and an ECU software ID that identifies the type and version of the software (sometimes called "SW"). Then, the process proceeds to step S3.

[0032] In step S3, the control unit 39 creates vehicle configuration information using the ECU ID and ECU software ID acquired in step S2. The vehicle configuration information includes a VIN (Vehicle Identification Number) that identifies the vehicle, an ECU ID, and an ECU software ID. Then, the process proceeds to step S4.

[0033] In step S4, the control unit 39 stores the vehicle configuration information created in step S3 in the storage unit 37. Here, the vehicle configuration information may be stored as only the latest vehicle configuration information, or may be stored as history information including previous vehicle configuration information. After that, the process proceeds to step S5.

[0034] In step S5, the control unit 39 transmits the vehicle configuration information created in step S3 to the OTA center 1 using the communication unit 38, and ends the series of processes shown in Fig. 6. The OTA center 1 receives the vehicle configuration information from the OTA master 11 and stores it in the storage unit 26.

[0035] Through the above processing, vehicle configuration information is created and stored by the OTA master 11 each time the ignition is turned ON, and the vehicle configuration information is transmitted to and stored in the OTA center 1, so that the vehicle configuration information is shared between the OTA master 11 and the OTA center 1.

[0036] 7, the control unit 39 waits until it determines that there is a campaign to be executed (an event to update the software of the ECU), and when it determines that there is a campaign to be executed, it moves the process to step S12. For example, when the control unit 39 detects that a campaign applicable to the vehicle has occurred by inquiring (for example, periodically) to the OTA center 1, notifies the user of the occurrence, and the user performs an operation to accept the application of the campaign, it is determined that there is a campaign to be executed.

[0037] In step S12, the control unit 39 transmits a download request for update data for applying the campaign to the OTA center 1 using the communication unit 38. After that, the process proceeds to step S13. The download request includes a VIN that can identify the vehicle that has made the download request.

[0038] In step S13, the control unit 39 waits until reception of the update data requested in step S12 starts, and when reception of the update data starts, the process proceeds to step S14.

[0039] In step S14, the control unit 39 executes a download process for storing the update data that began to be received in step S13 in the storage unit 37, and when this process ends, the series of processes shown in FIG. 7 ends.

[0040] Through the above process, update data for applying the campaign to be executed is downloaded by the OTA master 11. After that, using the downloaded update data, updated software is installed in one or more target ECUs, which are ECUs subject to software update, and then activated, completing the application of the campaign.

[0041] Next, an example of a control process of the OTA center 1 will be described with reference to FIG.

[0042] 8, the control unit 29 waits until it receives a download request (see S12 in FIG. 7) from the OTA master 11, and when it receives the download request, it moves the process to step S22. Note that the control unit 29 starts waiting for the reception of a download request when it receives from the OTA master 11 a notification of acceptance of the application of a campaign, which is executed in response to a user's operation of accepting the application of the campaign.

[0043] In step S22, the identification unit 28 identifies the SW version compatible with the target ECU for the vehicle that has made the download request, based on the vehicle configuration information and compatibility information stored in the storage unit 26. The vehicle configuration information is information stored in the storage unit 26 in response to the processing by the OTA master 11 described with reference to FIG. 6, and includes the VIN, ECU ID ("first identification information"), and ECU software ID ("second identification information") of each vehicle. The compatibility information is information that specifies the type and version of the ECU and the type and version of the software installed in each vehicle, and specifies the compatibility (compatibility) between the ECU and the software.

[0044] Fig. 9 is a diagram for explaining the compatibility information. As shown in Fig. 9, the compatibility information specifies, for each VIN that identifies a vehicle, an ECU to be installed and the version of that ECU, and software that is compatible with the ECU and the version of that software. Note that Fig. 9 shows the compatibility information related to a vehicle with a VIN of "1001", and the description of compatibility information related to other vehicles is omitted. A specific description will be given below with reference to Fig. 9.

[0045] As shown in Fig. 9, it is specified that ECU1, ECU2, and ECU3 are installed in a vehicle with a VIN of "1001", that software 1 (SW1) is used in ECU1, software 2 (SW2) is used in ECU2, and software 3 (SW3) is used in ECU3. It is also specified that ECU1 has versions 1 to 3 (ECU1_Ver1 to 3), that ECU2 has versions 1 to 3 (ECU2_Ver1 to 3), and that ECU3 has version 1 (ECU3_Ver1). It is also specified that software 1 has versions 1.0 to 3.1 (SW1_Ver1.0 to 3.1), that software 2 has versions 1.0 to 4.2 (SW2_Ver1.0 to 4.2), and that software 3 has versions 1.0 to 2.5 (SW3_Ver1.0 to 2.5). And only software 1 versions 1.0 to 1.5 (SW1_Ver1.0 to 1.5) are compatible with ECU1 version 1 (ECU1_Ver1), only software 1 versions 2.0 to 3.1 (SW1_Ver2.0 to 3.1) are compatible with ECU1 versions 2 and 3 (ECU1_Ver2 and 3), and only software 2 versions 1.0 to 1.2 (SW2_Ver1.0 to 1.2) are compatible with ECU2 version 1 (ECU2_Ver1), It is specified that only software 2 versions 2.0 to 2.3 (SW2_Ver2.0 to 2.3) are compatible with ECU2 version 2 (ECU2_Ver2), only software 2 versions 3.0 to 4.2 (SW2_Ver3.0 to 4.2) are compatible with ECU2 version 3 (ECU2_Ver3), and only software 2 versions 1.0 to 2.5 (SW3_Ver1.0 to 2.5) are compatible with ECU3 version 1 (ECU3_Ver1).

[0046] In step S22, the identification unit 28 refers to the compatibility information and vehicle configuration information related to the VIN included in the download request received in step S21. For example, when the VIN included in the download request received in step S21 is "1001", the identification unit 28 refers to the compatibility information (see FIG. 9) and vehicle configuration information related to the VIN "1001". Next, the identification unit 28 identifies the version of the target ECU based on the ECU ID included in the vehicle configuration information, and identifies the software and the software version compatible with the target ECU based on the compatibility information. For example, in the case of FIG. 9, when the identification unit 28 identifies that the target ECU1 is version 1 (ECU1_Ver1), it identifies versions 1.0 to 1.5 (SW1_Ver1.0 to 1.5) of the software 1 as the software compatible with the target ECU1. After that, the process proceeds to step S23.

[0047] In step S23, the identification unit 28 identifies the latest version of the software compatible with the target ECU identified in step S22. For example, in the case of Fig. 9, the identification unit 28 identifies SW1_Ver1.5 as the latest software version compatible with the target ECU1_Ver1. Then, the process proceeds to step S24.

[0048] In step S24, the control unit 29 determines whether or not the latest version of the software identified in step S23 is already installed in the target ECU based on the ECU software ID included in the vehicle configuration information stored in the storage unit 26. For example, in the case of Fig. 9, when the control unit 29 determines that SW1_Ver1.5 is installed in the target ECU1_Ver1 based on the ECU software ID included in the vehicle configuration information, it determines that the latest version of the software is already installed in the target ECU1_Ver1. If the determination in step S24 is YES, the process proceeds to step S26, and if the determination is NO, the process proceeds to step S25.

[0049] In step S25, the control unit 29 decides to update the target ECU with the latest version identified in step S23. After that, the process proceeds to step S27.

[0050] On the other hand, in step S26, the control unit 29 determines not to update the software of the target ECU because the software of the target ECU is already the latest version identified in step S23. Then, the process proceeds to step S27.

[0051] In step S27, the control unit 29 determines whether the determination in step S25 or S26 has been performed for all target ECUs. If the determination in step S27 is YES, the process proceeds to step S28, and if the determination is NO, the process returns to step S22 and the process is performed for the next target ECU.

[0052] In step S28, the control unit 29 determines update data (update data for updating the software of the target ECU) to be transmitted to the OTA master 11 that has made the download request (see S12 in FIG. 7) received in step S21, based on the determination in step S25 and / or step S26. For example, in the case of FIG. 9, consider a case where the target ECUs are ECU1_Ver1 and ECU2_Ver2. In this case, if it is determined that SW1_Ver1.5 is implemented in ECU1_Ver1 and SW1_Ver2.1 is implemented in ECU2_Ver2, the control unit 29 determines update data for updating ECU2_Ver2 to SW1_Ver2.3 as the update data to be transmitted. Thereafter, the process proceeds to step S29. Note that, if it is determined in step S26 that all of the target ECUs are not updated, the update data to be transmitted is not determined in step S28.

[0053] In step S29, the control unit 29 transmits the update data determined in step S28 to the OTA master 11 (the OTA master 11 that made the download request) using the communication unit 27, and ends the series of processes. If there is a target ECU determined not to be updated in step S26, information indicating this may be transmitted to the OTA master 11. If all of the target ECUs are determined not to be updated in step S26, the update data is not transmitted. In that case, information indicating this may be transmitted to the OTA master 11.

[0054] As described above, the OTA center 1 according to this embodiment identifies the version of software that is compatible with the target ECU by using the compatibility information described with reference to Fig. 9, and transmits update data to the OTA master 11 (vehicle). This allows the software to be updated to an appropriate version that is compatible with the target ECU.

[0055] Moreover, the OTA center 1 according to the present embodiment identifies the latest version of the software compatible with the target ECU and transmits update data to the OTA master 11 (vehicle). This allows the software to be updated to the latest version compatible with the target ECU.

[0056] Furthermore, when the latest version of software compatible with the target ECU is already installed in the target ECU, the OTA center 1 according to this embodiment does not transmit update data for updating to the latest version to the OTA master 11 (vehicle), thereby making it possible to omit unnecessary processing.

[0057] In the above embodiment, a control example has been given in which the OTA master 11 creates and holds vehicle configuration information and transmits the vehicle configuration information to the OTA center 1 when the ignition is turned on, and the vehicle configuration information is shared between the OTA master 11 and the OTA center 1 (see FIG. 6). However, the trigger for creating the vehicle configuration information and sharing it between the OTA master 11 and the OTA center 1 is not limited to this. For example, when the OTA center 1 receives a download request from the OTA master 11 (when YES is determined in step S21 in FIG. 8), the OTA center 1 may request the vehicle configuration information from the OTA master 11, and in response, the OTA master 11 creates the vehicle configuration information and transmits it to the OTA center 1, and the OTA center 1 receives the vehicle configuration information and uses it in the process of step S22. In this way, the OTA center 1 can obtain the latest vehicle configuration information immediately before using the vehicle configuration information in the process of FIG. 8.

[0058] The functions of the OTA center 1 exemplified in the above embodiment can also be realized as an update management method executed by a computer having a processor (CPU), memory, and communication device, or an update management program executed by the computer, or a computer-readable non-transient storage medium storing the update management program. Similarly, the functions of the OTA master 11 exemplified in the above embodiment can also be realized as an update control method executed by an in-vehicle computer having a processor (CPU), memory, and communication device, or an update control program executed by the in-vehicle computer, or a computer-readable non-transient storage medium storing the update control program. [Industrial Applicability]

[0059] The disclosed technology can be used in a network system for updating programs in an ECU (electronic control unit). [Explanation of symbols]

[0060] 1 OTA Center 2. In-vehicle network 5. Communication Network 11 OTA Master 12 Communication Module 13a~13d ECU 14 Human Machine Interface 15a~15d Bus 26, 37 Storage section 27, 38 Communications Department 28 Specific section 29, 39 Control section

Claims

1. An OTA master that controls software updates of a plurality of electronic control units mounted on a vehicle and a center that can communicate with each other via a network, a communication unit that receives, from the OTA master, identification information that identifies the plurality of electronic control units as a first electronic control unit and a second electronic control unit; a storage unit that stores compatibility information that defines a compatible version for each version of the plurality of electronic control units and corresponding software; an identification unit that uses the compatibility information to identify a latest version among the compatible versions for a target electronic control unit that is a software update target among the plurality of electronic control units identified by the identification information; a control unit that controls transmission of a distribution package for updating software of the target electronic control unit to the latest version identified by the identification unit by communicating with the OTA master; The compatibility information is information indicative of at least one version of a first software compatible with each version of the first electronic control unit; and information indicating at least one version of the second software compatible with each version of the second electronic control unit; The distribution package includes: information identifying the target electronic control unit; and information identifying software to be implemented in the target electronic control unit prior to the software update using the distribution package.

2. The control unit is determining whether the latest version of the software identified by the identifying unit is installed in the target electronic control unit based on the identification information; 2. The center according to claim 1, wherein control for updating software is not executed for the target electronic control unit for which the determination is a positive determination.

3. An update management method executed by a computer including a processor, a memory, and a communication device capable of communicating with an OTA master that controls software updates of a plurality of electronic control units mounted on a vehicle, the method comprising: receiving, from the OTA master, identification information identifying the plurality of electronic control units as a first electronic control unit and a second electronic control unit; A step of identifying a latest version of a target electronic control unit that is a software update target among the plurality of electronic control units identified by the identification information, using compatibility information that defines a compatible version for each version of the corresponding software of the plurality of electronic control units; and controlling the transmission of a distribution package for updating the software of the target electronic control unit to the identified latest version by communicating with the OTA master; The compatibility information is information indicative of at least one version of a first software compatible with each version of the first electronic control unit; and information indicating at least one version of the second software compatible with each version of the second electronic control unit; The distribution package includes: information identifying the target electronic control unit; and information identifying software to be implemented in the target electronic control unit prior to the software update using the distribution package.

4. A computer including a processor, a memory, and a communication device capable of communicating with an OTA master that controls software updates of a plurality of electronic control units mounted on a vehicle via a network, receiving, from the OTA master, identification information identifying the plurality of electronic control units as a first electronic control unit and a second electronic control unit; A step of identifying a latest version of a target electronic control unit that is a software update target among the plurality of electronic control units identified by the identification information, using compatibility information that defines a compatible version for each version of the corresponding software of the plurality of electronic control units; and controlling the transmission of a distribution package for updating the software of the target electronic control unit to the identified latest version by communicating with the OTA master. The compatibility information is information indicative of at least one version of a first software compatible with each version of the first electronic control unit; and information indicating at least one version of the second software compatible with each version of the second electronic control unit; The distribution package includes: information identifying the target electronic control unit; and information identifying software to be implemented in the target electronic control unit prior to the software update using the distribution package.

Images