OTA manager, update control method, non-transitory storage medium, and vehicle

By implementing the maintenance and rapid retry mechanism of update data in the OTA manager, the vehicle unavailability problem caused by the failure of the software update of the electronic control unit is solved, ensuring rapid recovery and stable operation in the case of single-store memory.

CN119011555APending Publication Date: 2024-11-22TOYOTA JIDOSHA KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202410957190.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2021-02-02
Filing Date
2021-11-26
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

During the software update process of the electronic control unit, especially in the case of single-store memory, it is impossible to recover quickly when the update fails, resulting in the vehicle being unable to use normally in an emergency and the update process takes a long time when the communication environment is poor.

Method used

An OTA manager is designed, including a reception, storage and control unit, which can delete update data after the software update processing of the target electronic control unit is completed normally, and maintain update data when the update fails to facilitate quick retry of the update processing, ensuring that Software updates can be completed quickly in single-store memory.

Benefits of technology

By keeping the update data until the software update is completed normally and then deleting it, it is possible to quickly retry the update when the communication is poor or the update fails, ensuring the stable operation of the electronic control unit, especially in the case of single-store memory, effectively avoiding the failure of the update caused by the failure of the update. unavailable vehicle.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119011555A_ABST
    Figure CN119011555A_ABST
Patent Text Reader

Abstract

The invention relates to an OTA manager, an update control method, a non-transitory storage medium, and a vehicle. The OTA manager includes: a receiving unit configured to receive update data of software of a target electronic control unit from a center; a storage unit configured to store the update data; and a control unit configured to control a software update process of the target electronic control unit on the basis of the update data, so that a storage unit holds the update data until the software update process of the target electronic control unit is normally completed, after the processing of the software update by the target electronic control unit is normally completed, the update data is deleted from the storage unit.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is filed with the China National Patent Office on November 26, 2021 with application number

[0002] 202111420796.2, divisional application of the application with the invention name “OTA manager, update control method, non-temporary storage medium and vehicle”. Technical Field

[0003] The present disclosure relates to an OTA manager, an update control method, a non-transitory storage medium, and a vehicle. Background Art

[0004] The vehicle is equipped with multiple electronic control units (ECUs) for controlling the operation of the vehicle. The ECU has a processor, a temporary storage unit such as RAM, and a non-volatile storage unit such as a flash ROM. The processor executes the software stored in the non-volatile storage unit to realize the control function of the ECU. The software stored in each ECU can be rewritten. By updating to a newer version of the software, the function of each ECU can be improved and new vehicle control functions can be added.

[0005] As an example of a technology for updating ECU software, there is known an OTA (Over The Air) technology for updating and adding ECU programs by wirelessly connecting an in-vehicle communication device connected to an in-vehicle network and a communication network such as the Internet, downloading software from a server via wireless communication, and installing the downloaded software (see, for example, Japanese Patent Application Laid-Open No. 2004-326689).

[0006] In addition, as types of non-volatile storage units mounted on the ECU, there are memories having one data storage area for storing data such as programs (single-bank memories) and memories having two data storage areas for storing data such as programs (dual-bank memories), which are used in a differentiated manner depending on the specifications of the ECU, etc.

[0007] In the case of software update failure in the ECU to be updated, it is required to be able to execute the software update again and complete the update quickly. However, it is considered that the communication environment deteriorates during the re-execution of the software update, and the software update takes a long time. In particular, in the case of an ECU with a single bank memory, if the software update process fails midway, the ECU cannot be operated, and a bad situation occurs when the vehicle needs to be used urgently, so there is room for improvement. Summary of the invention

[0008] The present disclosure provides an OTA manager, an update control method, a non-transitory storage medium, and a vehicle capable of improving software update in an electronic control unit.

[0009] The OTA manager involved in the first method of the present disclosure includes: a receiving unit, configured to receive update data of the software of the target electronic control unit from a center; a storage unit, configured to store the above-mentioned update data; and a control unit, configured to control the processing of the software update of the above-mentioned target electronic control unit based on the above-mentioned update data, so that the storage unit retains the above-mentioned update data until the processing of the above-mentioned software update of the above-mentioned target electronic control unit is normally completed, and after the processing of the above-mentioned software update of the above-mentioned target electronic control unit is normally completed, the above-mentioned update data is deleted from the above-mentioned storage unit.

[0010] The update control method involved in the second mode of the present disclosure is executed by a computer having a processor, a memory, and a storage device. The update control method includes: receiving update data of the software of the target electronic control unit from a center; storing the update data in the storage device; controlling the processing of the software update of the target electronic control unit based on the update data; maintaining the update data until the processing of the software update of the target electronic control unit is completed normally; and after the processing of the software update of the target electronic control unit is completed normally, deleting the update data from the storage device.

[0011] The non-transitory storage medium involved in the third aspect of the present disclosure stores a software update control program that can be executed by a computer having a processor, a memory, and a storage device, and causes the computer to perform the following functions. The above functions include: receiving update data of the software of the target electronic control unit from a center; storing the above update data in the above storage device; controlling the processing of the software update of the above target electronic control unit based on the above update data; maintaining the above update data until the processing of the software update of the above target electronic control unit is completed normally; and deleting the above update data from the above storage device after the processing of the software update of the above target electronic control unit is completed normally.

[0012] A vehicle according to a fourth aspect of the present disclosure may include the OTA manager according to the first aspect.

[0013] The present disclosure may provide an OTA manager, an update control method, a non-transitory storage medium, and a vehicle capable of improving software update in an electronic control unit. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Hereinafter, features, advantages, technical and industrial significance of exemplary embodiments of the present invention will be described with reference to the accompanying drawings, in which like reference numerals represent like components, wherein:

[0015] Figure 1 It is a block diagram showing the overall configuration of a network system according to an embodiment.

[0016] Figure 2 This is a functional block diagram of the OTA manager involved in the implementation scheme.

[0017] Figure 3 This is a flowchart showing a software update control process executed by the OTA manager according to the embodiment. DETAILED DESCRIPTION

[0018] Figure 1 It is a block diagram showing the overall configuration of a network system according to an embodiment.

[0019] Figure 1 The network system shown is a system for updating software of electronic control units 13a to 13d mounted in a vehicle, and includes a server 1 (center) and an in-vehicle network 2 mounted in the vehicle.

[0020] The server 1 can communicate with an OTA manager 11 mounted in the vehicle via the network 5 , and manages software updates of electronic control units 13 a to 13 d mounted in the vehicle.

[0021] The server 1 includes a CPU, a RAM, a storage device having a readable and writable storage medium such as a hard disk or an SSD, and a communication device for communicating with the OTA manager 11 via the network 5. The storage device stores a program for executing software update management, information used in update management, and update data of the electronic control unit. In the server 1, the CPU uses the RAM as a work area to execute a program read from the storage device to control the transmission of update data to the OTA manager 11.

[0022] The in-vehicle network 2 includes an OTA manager 11, a communication module 12, a plurality of electronic control units (ECUs) 13a to 13d, and a display device 14. The OTA manager 11 is connected to the communication module 12 via a bus 15a, to the electronic control units 13a and 13b via a bus 15b, to the electronic control units 13c and 13d via a bus 15c, and to the display device 14 via a bus 15d. The communication module 12 is a communication device that connects the in-vehicle network 2 to the server 1.

[0023] The OTA manager 11 includes a microcomputer and a communication device. The microcomputer includes a CPU, RAM, ROM, and a storage device. In the OTA manager 11, the CPU of the microcomputer uses the RAM as a work area to execute a program read from the ROM or the storage device to perform the control processing described below. The communication device is connected via Figure 1The buses 15a to 15d shown are devices that communicate with the communication module 12, the electronic control units 13a to 13d, and the display device 14. The OTA manager 11 can realize wireless communication with the server 1 via the communication module 12. The OTA manager 11 controls the software update of the electronic control unit (target electronic control unit) of the electronic control unit 13a to 13d that is the target of the software update based on the update data obtained from the server 1. The OTA manager 11 may also be called a manager device or a central gateway.

[0024] The electronic control units 13a to 13d control actuators, sensors and other devices installed in the vehicle. When the software of the electronic control units 13a to 13d is updated, a display device 14 (HMI) is used to display various displays such as the existence of update data, the display of a consent request screen for requesting the user or administrator to agree to the software update, and the display of the update results. As the display device 14, a display device of a car navigation system can typically be used, but it is not particularly limited as long as it can display the information required for the program update process. In addition, in Figure 1 Although four electronic control units 13a to 13d are illustrated in FIG. 1 , the number of electronic control units is not particularly limited. Figure 1 The bus 15 d shown may also connect electronic control units other than the display device 14 .

[0025] The electronic control units 13a to 13d are equipped with a CPU, a RAM, a nonvolatile memory (storage), and a communication device. The CPU realizes the functions of each electronic control unit by executing the software (program) read from the nonvolatile memory using the RAM as a work area. Here, the electronic control unit has a structure having one data storage area for storing software and a structure having two data storage areas for storing software. Sometimes, in addition to storing the software for realizing the functions of the electronic control unit, the data storage area (library) of the electronic control unit also stores version information, parameter data, a startup program for startup, a program for software update, etc. In an electronic control unit having one data storage area (one surface, single library memory), the software of the electronic control unit is affected by installing update data in the data storage area. On the other hand, in an electronic unit having two data storage areas (two surfaces, dual library memory), any one of the two data storage areas is used as the storage area (operation surface) of the read object, and the software stored in the storage area of ​​the read object is executed. In the other storage area (non-operation surface, writing surface) that is not the read target, the update data can be written in the background during the execution of the program in the storage area (operation surface) of the read target. When the software update process is activated, the updated version of the software can be validated by switching the storage area of ​​the CPU program to read the target.

[0026] Among them, in the present disclosure, an electronic control unit with two data storage areas includes: an electronic control unit having a memory structure called "single-sided suspended memory" that virtually divides one data storage area of ​​a non-volatile memory into two surfaces and can write a program to the other surface during the execution of a program on one surface; and an electronic control unit that, in addition to the non-volatile memory having a data storage area on one surface, also has an extended non-volatile memory having a data storage area on one surface, and can use these two non-volatile memories as an operating surface and a non-operating surface.

[0027] Here, the software update process consists of a stage of downloading update data from server 1, a stage of transferring the downloaded update data to the electronic control unit of the update object and installing the update data in the storage area of ​​the electronic control unit of the update object, and a stage of activating the installed updated version of the software in the electronic control unit of the update object.

[0028] Downloading is the process of receiving and storing update data for updating the software of the electronic control unit from the server 1. In the downloading stage, it includes not only the reception of the update data, but also the control of a series of processes related to the download, such as the judgment of whether the download can be executed, the verification of the update data, etc. Installation is the process of writing an updated version of the program (updated software) to the storage area of ​​the vehicle-mounted device in the electronic control unit of the update object based on the downloaded update data. In the installation stage, it includes not only the installation execution, but also the control of a series of processes related to the installation, such as the judgment of whether the installation can be executed, the transfer of the update data, and the verification of the updated version of the program. Activation is the process of validating (activating) the installed updated version of the program. The activation stage includes not only the activation execution, but also the control of a series of processes related to the activation, such as the judgment of whether the activation can be executed, the verification of the execution result, etc.

[0029] The update data sent from the server 1 to the OTA manager 11 may include any one of update software for the electronic control unit, compressed data that compresses the update software, and segmented data that segments the update software or compressed data. In addition, the update data may include an identifier (ECUID) for identifying the electronic control unit to be updated, and an identifier (ECU software ID) for identifying the software before the update. The update data is downloaded as a release data package, which includes update data for a single or multiple electronic control units.

[0030] When the update data includes the update software itself, during the installation phase, the OTA manager 11 transfers the update data (update software) to the electronic control unit of the update object. In addition, when the update data includes compressed data, differential data or segmented data of the update software, the OTA manager 11 can transfer the update data to the electronic control unit of the update object, and the electronic control unit of the update object generates the update software based on the update data. After the OTA manager 11 generates the update software based on the update data, the update software can be transferred to the electronic control unit of the update object. Here, the generation of the update software can be performed by decompressing the compressed data and assembling the differential data or segmented data.

[0031] The installation of the update software can be performed by the update target electronic control unit based on the installation request from the OTA manager 11. Alternatively, the update target electronic control unit that has received the update data can autonomously perform the installation without receiving an explicit instruction from the OTA manager 11.

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

[0033] The software update process can be performed on a plurality of electronic control units successively or in parallel.

[0034] In addition, the "program update process" in this specification includes not only the whole process of downloading, installing, and activating in succession, but also the process of only performing a part of downloading, installing, and activating.

[0035] Figure 2 This is a functional block diagram of the OTA manager involved in the implementation scheme.

[0036] The OTA manager 11 includes a transmission unit 21 , a reception unit 22 , a storage unit 23 , and a control unit 24 .

[0037] The sending unit 21 sends an update confirmation request for confirming whether there is software update data to the server 1, for example, when the power supply or ignition of the vehicle is turned on. The update confirmation request includes a vehicle ID (VIN) for identifying the vehicle and the version of the software of the electronic control units 13a to 13d connected to the vehicle network 2. The vehicle ID and the version of the software of the electronic control units 13a to 13d are used in order for the server 1 to determine whether there is software update data for the electronic control units 13a to 13d by comparing with the latest software version maintained for each vehicle ID or for each vehicle model determined according to the vehicle ID. In addition, when it is determined that there is software update data for any one of the electronic control units 13a to 13d based on the response to the update confirmation request, the sending unit 21 sends a download request for the update data to the server 1.

[0038] The receiving unit 22 receives a confirmation result indicating the presence or absence of update data from the server 1 as a response to the update confirmation request. In addition, after the sending unit 21 sends the download request to the server 1, the receiving unit 22 receives the update data of the software of the electronic control unit (target electronic control unit) to be updated from the server 1. The update data is sent from the server 1 as a release data packet. In addition to the update data, the release data packet may also include verification data for verifying the authenticity of the update data, the number of update data, the installation order, various control information used when updating the software, etc. The receiving unit 22 stores the received release data packet in the storage unit 23.

[0039] The storage unit 23 stores the distribution data packet received by the receiving unit 22. The storage unit 23 can be used to store data related to other control functions executed by the OTA manager 11 in addition to update data (distribution data packet) during software update by OTA.

[0040] The control unit 24 determines whether there is update data for the software of the electronic control unit based on the confirmation result of the update confirmation request received by the receiving unit 22 from the server 1. If the receiving unit 22 receives a release data packet including update data from the server 1, the control unit 24 verifies the reliability of the received release data packet. Here, the reliability verification refers to the integrity and legality of the confirmation data. The reliability verification can be performed, for example, using the vehicle ID (VIN) and the digital signature. In addition, the control unit 24 controls the software update processing of the target electronic control unit. The details of the software update processing performed by the control unit 24 will be described later.

[0041] Figure 3 The flowchart is a flowchart showing the software update control process executed by the OTA manager involved in the embodiment. Figure 3 The control process shown.

[0042] In step S11, the transmission unit 21 transmits a confirmation request whether there is update data of the electronic control unit software to the server 1. The update data confirmation request includes a combination of the vehicle ID and the version of the electronic control unit software. Then, the process proceeds to step S12.

[0043] In step S12, the receiving unit 22 receives the confirmation result of the update data confirmation request from the server 1. Then, the process proceeds to step S13.

[0044] In step S13, the control unit 24 determines whether there is software update data for any of the electronic control units 13a to 13d based on the confirmation result received in step S12. If the determination in step S13 is "yes", the process proceeds to step S14, and otherwise the process ends.

[0045] In step S14, the update data is downloaded. In more detail, the sending unit 21 sends a download request for a release data packet to the server 1, and the receiving unit 22 receives the release data packet sent in response to the download request. The receiving unit 22 stores the received release data packet in the storage unit 23. The control unit 24 verifies the reliability of the update data included in the received release data packet. Among them, in step S14, the control unit 24 can also determine whether the download can be executed before downloading. In addition, in step S14, after the download is completed, the sending unit 21 can send a notification of download completion to the server 1. Then, the processing enters step S15.

[0046] In step S15, the control unit 24 performs installation processing and activation processing on the target electronic control unit. In more detail, the control unit 24 transfers the update data included in the release data packet to the target electronic control unit and instructs the installation. The target electronic control unit writes the update data received from the OTA manager 11 to the data storage area. Next, the control unit 24 instructs the target electronic control unit to activate the updated version of the software. The target electronic control unit restarts when a specific operation such as power or ignition disconnection is performed, and executes the updated software. Then, the process enters step S16.

[0047] In the case where the target electronic control unit has a single bank memory, the software of the electronic control unit will be affected when the update data is installed in the data storage area, so the installation and activation can be performed continuously. In addition, in this case, if the target electronic control unit is a structure with one data storage area, the consent request processing for the installation and activation can be performed before the installation is performed, and the consent request processing before the activation is performed can be omitted.

[0048] In addition, before the execution of the installation, the control unit 24 can perform a determination process of whether the installation can be performed and a consent request process for the installation. As a consent request process for the installation, the control unit 24, for example, causes the display device 14 to display the content of starting the software update of the electronic control unit, and the content of requesting the user to agree to the software update, and causes the display device 14 to display the time required for the installation of the update data, the restrictions in the installation, and the display of precautions as needed, and accepts the user's operation input using an input mechanism such as a touch panel and an operation button. Then, the control unit 24 determines whether an operation input of the content of agreeing to the software update (installation) has been performed. For example, it is possible to determine the operation input of the content of agreeing to the installation based on whether a button such as "Agree" or "Start Update" displayed on the display device 14 is pressed. In addition, in the case where the user does not immediately agree to the start (installation) of the software update and wants to start (install) the software update later, the intention can be accepted by pressing a button such as "Do it later".

[0049] Similarly, before the execution of activation, the control unit 24 can perform a determination process on whether the activation can be performed and a consent request process for the activation. As a consent request process for the activation, the control unit 24, for example, causes the display device 14 to display that the software update of the electronic control unit is ready, and that the program is updated by performing a specific operation such as disconnecting the power supply or the ignition device, and causes the display device 14 to display the time required for activation, restrictions during activation, and precautions as needed, and accepts the user's operation input using an input mechanism such as a touch panel and an operation button. Then, the control unit 24 determines whether an operation input for agreeing to the software update (activation) has been performed. The operation input for agreeing to the activation can be determined based on, for example, whether a button such as "Agree" or "Update" displayed on the display device 14 is pressed. In addition, in the case where the user does not immediately agree to the software update (activation) and wishes to perform the software update later, the intention can be accepted by pressing a button such as "Do it later".

[0050] In step S16, the control unit 24 determines whether the software update process in the target electronic control unit has been completed normally. The control unit 24 makes the determination in step S16 based on the notification from the target electronic control unit. For example, the control unit 24 obtains the notification that the updated software has been successfully activated and the identification information of the software activated in the target electronic control unit from the target electronic control unit, and determines that the software update process in the target electronic control unit has been completed normally when it is confirmed that the software has been upgraded to the appropriate software based on the obtained information. If the determination in step S16 is "yes", the process proceeds to step S17, and otherwise, the process proceeds to step S18.

[0051] In step S17, the control unit 24 deletes the update data stored in the storage unit 23. The control unit 24 may delete the corresponding update data for each target electronic control unit in sequence, or may delete the entire distribution data package when the software update process is normally completed in all target electronic control units. Then, the process ends.

[0052] In step S18, the control unit 24 re-executes the installation process and the activation process for the target electronic control unit for which the software update process has not been completed normally. In the case where the software update process of the target electronic control unit has not been completed normally, the control unit 24 causes the storage unit 23 to retain the update data of the software of the target electronic control unit without deleting it. Therefore, the software update process can be quickly retried based on the update data retained in the storage unit 23 without downloading the update data of the software of the target electronic control unit from the server 1 again.

[0053] In step S18, similar to the process of step S15, the control unit 24 transfers the update data included in the release data packet to the target electronic control unit and instructs the installation. The target electronic control unit writes the update data received from the OTA manager 11 to the data storage area. Next, the control unit 24 instructs the target electronic control unit to activate the updated version of the software. The target electronic control unit restarts when a specific operation such as power or ignition disconnection is performed, and executes the updated software. Then, the process enters step S19.

[0054] In step S19, the control unit 24 determines whether the software update process in the target electronic control unit has been completed normally. As in step S16, the control unit 24 obtains from the target electronic control unit a notification that the updated software has been successfully activated and identification information of the software activated in the target electronic control unit. If it is confirmed based on the obtained information that the software has been upgraded to the appropriate software, the control unit 24 determines that the software update process in the target electronic control unit has been completed normally. If the determination in step S19 is "yes", the process proceeds to step S17, and otherwise, the process proceeds to step S20.

[0055] In step S20, the control unit 24 performs error processing. As error processing, the control unit 24 may perform any of, for example, a software rollback process of the target electronic control unit, a notification that the software update of the electronic control unit has failed, or a notification urging a dealer or a repair shop to respond. Then, the processing ends.

[0056] exist Figure 3In the example shown, the installation process and activation process (S18) are executed again, and when the software update is not normally completed (No in S19), error processing (S20) is performed, but the processes of S18 and S19 may be repeatedly executed multiple times.

[0057] As described above, the OTA manager 11 according to the present embodiment stores the update data in the storage unit 23 until the software update process of the target electronic control unit is normally completed, and after the software update process of the target electronic control unit is normally completed, the update data is deleted from the storage unit 23. Therefore, when the software update process of the target electronic control unit is not normally completed, the update data stored in the storage unit 23 can be reused.

[0058] In this embodiment, if the software update process of the target ECU is not completed normally, the control unit 24 executes the software update process again based on the update data stored in the storage unit 23. This control enables the target ECU to be updated quickly regardless of the communication status.

[0059] The memory of the target electronic control unit may be any one of a single-bank memory and a dual-bank memory, but the OTA manager 11 involved in the present embodiment is particularly effective when the target electronic control unit has a single-bank memory. When the memory of the target electronic control unit is a dual-bank memory, even if the software update fails, the software before the update can be used to operate the electronic control unit. In contrast, when the memory of the target electronic control unit is a single-bank memory, since the software before the update is overwritten by the installation of the updated version of the software, the software before the update cannot be used to operate the electronic control unit when the software update process fails. That is, when the software update of the target electronic control unit of the single-bank memory fails, it is preferred to retry the software update process as early as possible. When the software update of the target electronic control unit fails, the OTA manager 11 involved in the present embodiment can quickly achieve recovery because it can use the update data stored in the storage unit 23 to execute the software update process again in the shortest time.

[0060] As described above, in the event that the software update of an electronic control unit with a dual-bank memory fails, the electronic control unit can continue to operate using the software before the update. In view of this, in the event that the target electronic control unit has a dual-bank memory, the control unit 24 can delete the update data from the storage unit 23 after the update data is transferred to the target electronic control unit during the installation process. The control unit 24 can keep the update data of the target electronic control unit with a single-bank memory in the storage unit 23 until the software update process is normally completed. On the other hand, after the software update process is started, the storage capacity of the storage unit 23 of the OTA manager 11 can be ensured by deleting the update data of the software of the target electronic control unit with a dual-bank memory that can operate using the software before the update, thereby reducing the impact on other control processes.

[0061] (Other Modifications)

[0062] The functions of the OTA manager 11 shown in the above-mentioned embodiments can also be implemented as a software update control method executed by a vehicle-mounted computer having a processor (CPU), a memory, and a storage device, or a software update control program executed by the computer, or a computer-readable non-transitory storage medium storing the update control program. In addition, the functions of the OTA manager 11 shown in the above-mentioned embodiments can also be implemented as a microcomputer installed with a software update control method, or a microcomputer installed with an update control program in a storage device.

[0063] In the above-mentioned embodiments, an example is described in which the OTA manager 11 provided in the vehicle network controls the program update of all the electronic control units 13a to 13d on the vehicle side. However, instead of providing the OTA manager 11, any one of the electronic control units 13a to 13d may have a Figure 3 The update control function shown in the figure controls the software update of other electronic control units. In addition, it is also possible to replace the setting of OTA manager 11 and Figure 3 The update control function shown is provided in an external device that can be connected to the in-vehicle network 2 by wire, and the program update process of the electronic control units 13 a to 13 d is performed using the external device.

[0064] The disclosed technology can be utilized in a network system for updating a program of an electronic control unit.

Claims

1. An OTA manager, wherein: have: a receiving unit that receives information related to the update of software of a target electronic control unit having a single bank memory from a center; A storage unit for storing the information related to the above update; and a control unit that controls the software update process of the target electronic control unit based on the information related to the update, The control unit obtains, from the target electronic control unit, a notification that the software update process is completed and identification information of the software of the target electronic control unit after the software update process. The control unit determines that the software update process of the target electronic control unit is normally completed based on the acquired identification information, After receiving the notification, the control unit causes the storage unit to retain the information related to the update until it determines that the software update process of the target electronic control unit is normally completed.

2. The OTA manager according to claim 1, wherein: When the software update process of the target electronic control unit is not normally completed, the control unit re-executes the software update of the target electronic control unit based on the information related to the update stored in the storage unit.

3. The OTA manager of claim 1, wherein: In the software update process, the control unit causes the storage unit to store the information related to the update after transferring the information related to the update to the target electronic control unit.

4. A software update control method, executed by a device mounted on a vehicle, wherein: include: The step of receiving information related to the update of the software of the target electronic control unit having a single bank memory from the center; The step of storing the information involved in the above update; and The step of controlling the software update process of the target electronic control unit based on the information related to the update, The steps of controlling the software update process of the target electronic control unit include: A step of obtaining, from the target electronic control unit, a notification that the software update process is completed and identification information of the software after the software update process of the target electronic control unit; A step of determining that the software update process of the target electronic control unit is normally completed based on the acquired identification information; and After receiving the notification, the information related to the update is retained until it is determined that the software update process of the target electronic control unit is normally completed.

5. A software update control program executed by a device mounted on a vehicle, wherein: Make the above device execute: The step of receiving information related to the update of the software of the target electronic control unit having a single bank memory from the center; The step of storing the information involved in the above update; and The step of controlling the software update process of the target electronic control unit based on the information related to the update, The steps of controlling the software update process of the target electronic control unit include: A step of obtaining, from the target electronic control unit, a notification that the software update process is completed and identification information of the software after the software update process of the target electronic control unit; A step of determining that the software update process of the target electronic control unit is normally completed based on the acquired identification information; and After receiving the notification, the information related to the update is retained until it is determined that the software update process of the target electronic control unit is normally completed.

6. A vehicle, wherein: A method comprising the OTA manager according to any one of claims 1 to 3.

Citation Information

Patent Citations

  • Method for rewriting software of on-vehicle equipment, system of telematics system, and telematics device

    JP2004326689A