Software updating system, specific data saving method and specific data saving program

The software update system addresses the loss of critical vehicle data during ECU updates by calculating save targets and temporarily storing data to ensure continuity and compliance.

JP2024157801AInactive Publication Date: 2024-11-08DENSO CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023072386
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-26
Publication Date
2024-11-08
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

When updating the software of an electronic control unit (ECU), data associated with the vehicle, such as driving records, is often initialized, leading to a loss of critical information that needs to be maintained for regulatory compliance and vehicle history.

Method used

A software update system that calculates save target information based on update contents, determines if data can be continuously used before and after the update, and temporarily saves or evacuates specific data to a vehicle-side system to ensure continuity.

Benefits of technology

Ensures the continuity of specific data before and after software updates by temporarily saving it to a vehicle-side system, allowing compliance with regulations and maintaining vehicle history.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024157801000001_ABST
    Figure 2024157801000001_ABST
Patent Text Reader

Abstract

To appropriately store specific data in a vehicle-side system when updating software of an electronic control device to be updated, and appropriately guarantee continuity of the specific data before and after the software update.SOLUTION: A software updating system 1 includes: a save target information calculation unit 10a that calculates save target information related to a save target that needs to be saved when updating software based on update contents of the update software; a continued usability determination unit 12a that determines whether or not specific data held in an electronic control device to be updated can be continuously used before and after the software update; a save target identification unit 12c that designates the specific data as the save target when it is determined that the specific data cannot be continuously used; and a data saving unit 12d that saves the specific data specified as the save target from the electronic control device to be updated to a save destination belonging to a vehicle-side system.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a software update system, a method for saving specific data, and a program for saving specific data. [Background technology]

[0002] In an on-board update device, a software update system is provided in which update software received from a server, for example, is transmitted to an electronic control device to be updated (hereinafter referred to as an ECU (Electronic Control Unit) to be updated) to update the software of the ECU to be updated. When updating the software of the ECU to be updated, there is a technique for saving data held in the ECU to be updated. For example, Patent Document 1 discloses a technique for saving vehicle identification information such as a VIN (Vehicle Identification Number) held in the ECU to be updated when updating the software of the ECU to be updated, thereby avoiding loss of the vehicle identification information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-012434 Summary of the Invention [Problem to be solved by the invention]

[0004] When updating the software of the ECU to be updated, the data stored in the non-volatile memory is generally initialized along with the software update. However, some data is associated with the vehicle itself, such as driving records for the entire vehicle life cycle. Considering the significance of such data associated with the vehicle itself, it is desirable to store it as consistent information regardless of software updates.

[0005] For example, CARB (California Air Resources Board) regulations (CCR1968,1968-2) contain provisions regarding data retention, and require that if data related to the IUMPR (In-Use Monitor Performance Ratio) specified by CARB is erased by a software update, the data must be submitted to CARB authorities.

[0006] The present invention has been made in consideration of the above-mentioned circumstances, and its purpose is to provide a software update system, a method for backing up specific data, and a program for backing up specific data that can properly store specific data in a vehicle system and properly ensure the continuity of the specific data before and after a software update when updating software of an electronic control device to be updated. [Means for solving the problem]

[0007] According to the invention described in claim 1, a software update system (1, 21) includes a distribution device (3, 9, 23) that distributes update software to an electronic control device to be updated, and an on-board update device (5, 24) that transmits the update software received from the distribution device to the electronic control device to be updated, thereby updating the software of the electronic control device to be updated. A vehicle-side system is configured including the on-board update device and the electronic control device to be updated.

[0008] The save target information calculation unit (10a, 26a) calculates save target information relating to a save target that needs to be saved when updating software, based on the update contents of the update software. The continued usability determination unit (12a, 26b) determines whether specific data held in the electronic control unit to be updated can be continuously used before and after the software update. The save target identification unit (12c, 26d) identifies the specific data as the save target when it is determined that the specific data cannot be continuously used. The data save unit (12d, 26e) saves the specific data identified as the save target from the electronic control unit to be updated to a save destination belonging to the vehicle-side system.

[0009] The system calculates information on the evacuation target that needs to be evacuated when updating software based on the update contents of the update software. When it is determined that specific data held in the electronic control device to be updated cannot be continuously used before and after the software update, the system specifies the specific data as the evacuation target, and evacuates the specific data specified as the evacuation target from the electronic control device to be updated to a destination belonging to the vehicle-side system.

[0010] By temporarily saving the specific data to the save destination, the specific data can be continuously used before and after a software update in the vehicle-side system. As a result, when updating the software of the electronic control unit to be updated, the specific data can be appropriately stored in the vehicle-side system and the continuity of the specific data can be appropriately guaranteed before and after the software update. [Brief description of the drawings]

[0011] [Figure 1] Functional block diagram showing the first embodiment [Diagram 2] Flowchart showing server processing [Diagram 3] Flowchart showing the process of the in-vehicle update device [Figure 4] Process flow diagram [Diagram 5] Functional block diagram showing a second embodiment [Figure 6] Flowchart showing server processing [Figure 7] Flowchart showing the process of the in-vehicle update device [Figure 8] Process flow diagram DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, several embodiments of the software update system will be described with reference to the drawings. In each of the embodiments described below, parts corresponding to the contents described in the preceding embodiment are given the same reference numerals, and duplicated descriptions may be omitted.

[0013] (First embodiment) The first embodiment will be described with reference to Fig. 1 to Fig. 4. In the software update system 1, a vehicle-side system 2 mounted on a vehicle and a server 3 (corresponding to a distribution device) functioning as an OTA (Over The Air) center are configured to be able to perform data communication via a communication network 4. In the vehicle-side system 2, an in-vehicle update device 5 functioning as an OTA master and a number of ECUs 6 are configured to be able to perform data communication via an in-vehicle network 7. In this embodiment, a configuration in which four ECUs are connected to the in-vehicle network 7 is illustrated, but the number of ECUs connected to the in-vehicle network 7 is arbitrary. The in-vehicle network 7 is a CAN (Controller Area Network) (registered trademark). The in-vehicle network 7 may be FLEXRAY (registered trademark), CXPI (Clock Extension Peripheral Interface) (registered trademark), Ethernet (registered trademark), or the like.

[0014] The ECU 6 may be, for example, a device that controls a drive system, a device that controls an ADAS (Advanced Driving Assistant System), or a device that controls a multimedia system, and may be an update target ECU 6 that is a target for updating software due to software modification, function improvement, etc. Note that the software includes so-called programs that instruct a computer on processing procedures to perform operations, as well as files, data, libraries, etc. that are referenced when executing a program. Also, the ECU 6 may be classified into an OS conforming to the AUTOSAR Classic Platform, which is a standard of the AUTOSAR, an OS conforming to the AUTOSAR Adaptive Platform, Automotive Grade Linux, Android Automotive OS, etc., depending on the operating system installed.

[0015] The on-board update device 5 is connected to a DCM (Data Communication Module) 8 that functions as a data communication device. The DCM 8 is wirelessly connected to the server 3 via the communication network 4, and is therefore capable of receiving a distribution package transmitted from the server 3. When the DCM 8 receives a distribution package distributed from the server 3, it transfers the received distribution package to the on-board update device 5. When the on-board update device 5 receives a distribution package transferred from the DCM 8, it extracts update software from the transferred distribution package, transmits the extracted update software to the update target ECU 6, and transmits an update instruction to the update target ECU 6, causing the update target ECU 6 to perform software update. That is, the update target ECU 6 receives the update software and the update instruction from the on-board update device 5, and writes the update software to a storage area to perform software update. The manner in which the update software received from the server 3 via the communication network 4 is written to the update target ECU 6 is called wireless repro.

[0016] When the distribution package is transferred from the DCM 8, the on-board update device 5 may transmit the distribution package to the update target ECU 6 without extracting the update software from the transferred distribution package. Alternatively, when the DCM 8 receives a distribution package distributed from the server 3, the DCM 8 may extract the update software from the received distribution package and transfer the extracted update software to the on-board update device 5. In this case, when the update software is transferred from the DCM 8, the on-board update device 5 transmits the transferred update software to the update target ECU 6.

[0017] A reprogramming tool 9 is detachably connected to the in-vehicle network 7. The reprogramming tool 9 distributes update software to the update target ECU 6 while connected to the in-vehicle network 7, and transmits an update instruction to the update target ECU 6, causing the update target ECU 6 to update the software. That is, the update target ECU 6 receives the update software and the update instruction from the reprogramming tool 9, and updates the software by writing the update software to a storage area. A mode in which the update software received from the reprogramming tool 9 without going through the communication network 4 is written to the update target ECU 6 is called a wired reprogramming. In this embodiment, a configuration in which the reprogramming tool 9 directly transmits and receives data to and from the update target ECU 6 is illustrated, but a configuration in which the reprogramming tool 9 is connected to the update target ECU 6 via the in-vehicle update device 5 may also be used. When the reprogramming tool 9 is connected to the update target ECU 6 via the in-vehicle update device 5, the reprogramming tool 9 and the update target ECU 6 may be connected via the same in-vehicle network 7, or may not be connected via the in-vehicle network 7 and may be connected only via the in-vehicle update device 5.

[0018] The server 3 includes a control unit 10 and a communication module 11. The control unit 10 is mainly configured with a microcomputer having a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and an I / O (Input / Output), etc. The control unit 10 executes a control program stored in a non-transient substantial storage medium to execute processing corresponding to the control program, and controls the overall operation of the server 3. The communication module 11 controls transmission and reception of data signals to and from the communication network 7.

[0019] The control unit 10 includes a save target information calculation unit 10a. The save target information calculation unit 10a realizes a part of the specific data save method and executes a part of the specific data save program. When updating the software of the update target ECU 6, the save target information calculation unit 10a generates update information by referring to the update software and the configuration information received from the in-vehicle update device 5. The configuration information includes version information of the software held by each ECU 6. That is, the save target information calculation unit 10a generates update information required to execute the software update by, for example, collating the version information of the update software with the version information included in the configuration information. The specific data is data such as the total engine operating time, total driving time, and fuel consumption that are generated or updated with the use of the vehicle, and is data associated with the vehicle itself, that is, data unique to each vehicle.

[0020] When the save target information calculation unit 10a generates the update information, it calculates the save target information related to the save target that needs to be saved when updating the software based on the update contents of the update software. The save target information includes information on whether the specific data held in the update target ECU 6 can be continuously used before and after the software update, and information on whether the location address of the specific data has changed before and after the software update. When the save target information calculation unit 10a calculates the save target information, it transmits the update information including the calculated save target information to the in-vehicle update device 5.

[0021] Here, an example of calculating the save target information will be described. When calculating the save target information, the save target information calculation unit 10a judges whether or not the update software includes a file including specific data. When the save target information calculation unit 10a judges that the update software includes a file including specific data, it outputs a file name including the specific data. The file name including the specific data may be a file name defined before the software update, or may be a file name defined after the software update, as long as it is consistent between the save target information calculation unit 10a and the continued use possibility determination unit 12a described later.

[0022] Alternatively, when calculating the save target information, the save target information calculation unit 10a determines whether or not the location address indicating the update software includes a location address including specific data. When the save target information calculation unit 10a determines that the location address indicating the update software includes a location address including specific data, it outputs the location address including the specific data. The location address including the specific data may be a location address defined before the software update or a location address defined after the software update, as long as there is consistency between the save target information calculation unit 10a and the continued use possibility determination unit 12a described later.

[0023] The in-vehicle update device 5 includes a control unit 12 and a CAN module 13. The control unit 12 is mainly configured with a microcomputer having a CPU, a ROM, a RAM, an I / O, etc. The control unit 12 executes a control program stored in a non-transient substantial storage medium to execute processing corresponding to the control program, and controls the overall operation of the in-vehicle update device 5. The CAN module 13 controls input and output of CAN signals to and from the in-vehicle network 7.

[0024] The control unit 12 includes a continued use determination unit 12a, an arrangement address change determination unit 12b, a save target specification unit 12c, a data save unit 12d, and a data restoration unit 12e. Each of these units 12a to 12e realizes a part of a specific data save method and executes a part of a specific data save program.

[0025] When the continued use possibility determination unit 12a receives update information from the in-vehicle update device 5, it acquires the save target information from the received update information and determines whether the specific data held in the update target ECU 6 can be continuously used before and after the software update. The continued use possibility determination unit 12a determines whether the file name specified for the update target ECU 6 before the software update matches the file name specified after the update, for example, and determines whether the specific data can be continuously used. The continued use possibility determination unit 12a determines whether the specific data whose file name matches before and after the software update can be continuously used, for example, and determines whether the specific data whose file name does not match before and after the software update cannot be continuously used.

[0026] When the continuous use permission determining unit 12a determines that the specific data cannot be continuously used, the save target specifying unit 12c specifies the specific data determined to be unable to be continuously used as a save target.

[0027] When the continued use possibility determination unit 12a determines that the specific data can be continuously used, the location address change determination unit 12b determines whether the location address of the specific data has been changed before and after the software update. The location address change determination unit 12b determines whether the location address specified for the update target ECU 6 before the software update matches the location address specified after the update.

[0028] When the continued use eligibility determination unit 12a determines that specific data can be continuously used, but the location address change determination unit 12b determines that the location address of the specific data has changed before and after the software update, the evacuation target identification unit 12c identifies the specific data whose location address has been determined to have changed before and after the software update as a target for evacuation.

[0029] The above-mentioned sharing of functions among the save target information calculation unit 10a, the continued use possibility determination unit 12a, and the location address change determination unit 12b may be modified in various ways. For example, the save target information calculation unit 10a may determine whether specific data can be continued to be used before and after a software update. In this case, the save target information includes a flag indicating whether continued use is possible, and if the data cannot be continued to be used, a file name and location address to be saved. The save target information calculation unit 10a may also determine whether the location address of the specific data has changed before and after a software update. In this case, the save target information includes a flag indicating whether the location address has changed, a file name to be saved if the location address has changed, the location address before the change, and the location address after the change.

[0030] The data saving unit 12d sets the on-board update device 5 as the save destination of the specific data, and saves the specific data specified as the save target from the update target ECU 6 to the on-board update device 5. The storage unit of the on-board update device 5 as the save destination is configured with a nonvolatile memory such as a flash memory. The save destination may be changed depending on the type of the specific data to be saved. For example, the data saving unit 12d determines whether the specific data to be saved is specific data that cannot be continuously used, or specific data that can be continuously used but the location address will be changed. When the data saving unit 12d determines that the specific data to be saved is specific data that cannot be continuously used, the data saving unit 12d may store the specific data to be saved in a nonvolatile memory. When the data saving unit 12d determines that the specific data to be saved is specific data that can be continuously used but the location address will be changed, the data saving unit 12d may store the specific data to be saved in a volatile memory such as a random access memory. In addition, the data saving unit 12d generates data recovery information to be referred to by the data recovery unit 12e.

[0031] When the specific data saved to the save destination can be continuously used before and after the software update and the location address of the specific data has changed before and after the software update, the data recovery unit 12e writes the specific data to the changed location address based on the data recovery information and restores the specific data to the update target ECU 6. In this case, the data recovery unit 12e may restore the specific data to the update target ECU 6 after the software update is completed by transmitting the specific data to the update target ECU 6 after the update software is transmitted to the update target ECU 6, or may restore the specific data to the update target ECU 6 during the software update by transmitting the specific data to the update target ECU 6 while the update software is being transmitted to the update target ECU 6.

[0032] Next, the operation of the above-mentioned configuration will be described with reference to FIGS. (1-1) Update information generation process performed by server 3 (see Figure 2) In the server 3, the control unit 10 starts the update information generation process, and when it receives configuration information from the on-board update device 5 (A1), it generates update information by referring to the update software and the received configuration information (A2). The control unit 10 calculates save target information related to the save target that needs to be saved when updating the software based on the update contents of the update software (A3, which corresponds to the save target information calculation step). The control unit 10 transmits the update information including the calculated save target information to the on-board update device 5 (A4), and ends the update information generation process.

[0033] (1-2) Software update process performed by the in-vehicle update device 5 (see FIG. 3) In the in-vehicle update device 5, the control unit 12 starts the software update process, and when it receives update information from the server 3 (B1), it acquires the save target information from the received update information (B2). The control unit 12 determines whether or not the specific data held in the update target ECU 6 can be continuously used before and after the software update (B3, which corresponds to the procedure for determining whether or not the specific data can be continuously used).

[0034] When the control unit 12 determines that the specific data cannot be continuously used before and after the software update (B3: NO), it identifies the specific data as a save target (B4, corresponding to a save target identification step), and saves the specific data identified as a save target from the update target ECU 6 to the in-vehicle update device 5 (B5, corresponding to a data save step). The control unit 12 transmits update software to the update target ECU 6 and transmits an update instruction to the update target ECU 6, causing the update target ECU 6 to update the software (B6).

[0035] When the control unit 12 determines that the specific data can be continuously used (B3: YES), it determines whether the location address of the specific data has changed before and after the software update (B7). When the control unit 12 determines that the location address of the specific data has changed before and after the software update (B7: YES), it also identifies the specific data as a target for saving (B4) in this case, and saves the specific data identified as a target for saving from the update target ECU 6 to the in-vehicle update device 5 (B5). The control unit 12 transmits update software to the update target ECU 6 and transmits an update instruction to the update target ECU 6, causing the update target ECU 6 to update the software (B6).

[0036] On the other hand, when the control unit 12 determines that the location address of the specific data has not changed before and after the software update (B7: NO), it does not identify the specific data as a target for backup, but sends the update software to the update target ECU 6 and also sends an update instruction to the update target ECU 6, and has the update target ECU 6 perform the software update (B6).

[0037] When the control unit 12 finishes the software update, it determines whether the specific data can be continuously used before and after the software update (B8). If the control unit 12 determines that the specific data can be continuously used before and after the software update (B8: YES), it determines whether the location address of the specific data has changed before and after the software update (B9). If the control unit 12 determines that the location address of the specific data has changed before and after the software update (B9: YES), it writes the specific data that was saved in the in-vehicle update device 5 to the changed location address and returns it to the update target ECU 6 (B10), and ends the software update process.

[0038] By carrying out the above-mentioned process in cooperation between the server 3 and the on-board update device 5, the software of the update target ECU 6 is updated in a state in which the specific data identified as the data to be saved is saved from the update target ECU 6 to the on-board update device 5, as shown in Fig. 4. After the specific data is saved from the update target ECU 6 to the on-board update device 5, if the specific data can be continuously used before and after the software update and the location address of the specific data has changed before and after the software update, the saved specific data is written to the changed location address and returned to the update target ECU 6. If the specific data cannot be continuously used before and after the software update, the saved specific data is not returned to the update target ECU 6 but is retained in the on-board update device 5.

[0039] The above has been an example of a configuration in which the control unit 12 returns the saved specific data to the update target ECU 6 after the software update is completed, but the specific data may be returned to the update target ECU 6 during the software update. Also, the configuration has been exemplified in which the in-vehicle update device 5 is set as the save destination of the specific data, and the specific data is saved from the update target ECU 6 to the in-vehicle update device 5, but an ECU 6 other than the in-vehicle update device 5 may be set as the save destination of the specific data, and the specific data may be saved from the update target ECU 6 to the other ECU 6. That is, the specific data may be saved from the update target ECU 6 to, for example, another ECU 6 that has a sufficient amount of free space in the memory area. Furthermore, the save destination of the specific data is not limited to one, and the specific data may be saved in a distributed manner to multiple save destinations.

[0040] The specific data saved to the save destination may be stored in association with a time stamp. By adding a time stamp, it is possible to prove that the specific data saved to the save destination existed at the time the stamp was added and has not been tampered with since then. The specific data can be output from the vehicle-side system 2 to the outside of the vehicle via the reprogramming tool 9 or the DCM 8.

[0041] As described above, according to the first embodiment, the following advantageous effects can be obtained. In the software update system 1, save target information relating to save targets that need to be saved when updating software is calculated based on the update contents of the update software. If it is determined that specific data held in the update target ECU 6 cannot be continuously used before and after the software update, the specific data is identified as a save target, and the specific data identified as a save target is saved from the update target ECU 6 to the in-vehicle update device 5.

[0042] By temporarily saving the specific data from the update target ECU 6 to the in-vehicle update device 5, the specific data can be continuously used before and after a software update in the vehicle-side system 2. This makes it possible to properly store the specific data in the vehicle-side system 2 when updating the software of the update target ECU 6, and to properly ensure the continuity of the specific data before and after the software update.

[0043] If it is determined that the specific data held in the update target ECU 6 can be continuously used before and after the software update, but it is determined that the location address of the specific data has changed before and after the software update, the specific data is identified as a target for evacuation, and the specific data identified as a target for evacuation is temporarily evacuated from the update target ECU 6 to the in-vehicle update device 5. In this case as well, it is possible to appropriately store the specific data in the vehicle-side system 2 and appropriately guarantee the continuity of the specific data before and after the software update.

[0044] The specific data saved from the update target ECU 6 to the in-vehicle update device 5 is restored to the update target ECU 6 if the specific data can be continuously used before and after the software update and the location address of the specific data has changed before and after the software update. By restoring the saved specific data to the update target ECU 6, the specific data can be used appropriately in the update target ECU 6.

[0045] The on-board update device 5 is set as the destination for saving the specific data, and the specific data is saved from the update target ECU 6 to the on-board update device 5. The specific data can be stored in the on-board update device 5, and if the processing capacity of the on-board update device 5 is higher than the processing capacity of the ECU 6, the specific data can be stored in a resource with higher processing capacity.

[0046] The save target information is calculated by the server 3. Since the processing capacity of the server 3 is higher than that of the on-board update device 5, the save target information can be calculated using resources with higher processing capacity, and the resources of the software update system 1 can be used effectively.

[0047] In the above embodiment, the save target information calculation unit 10a generates update information by referring to the update software and the configuration information received from the on-board update device 5 when updating the software of the update target ECU 6, but configuration information previously received from the on-board update device 5 and already stored may be used. When using the configuration information received from the on-board update device 5, the on-board update device 5 generates the update information in the server 3 after transmitting the configuration information to the server 3. When using the configuration information that has already been stored, the on-board update device 5 has already transmitted the configuration information to the server 3, so there is no need for the on-board update device 5 to transmit the configuration information to the server 3.

[0048] Second embodiment The second embodiment will be described with reference to Figures 5 to 8. The first embodiment is configured so that the server 3 calculates the save target, but the second embodiment is configured so that the in-vehicle update device calculates the save target.

[0049] The software update system 21 is configured so that a vehicle-side system 22 and a server 23 can communicate with each other via a communication network 4. The vehicle-side system 22 is configured so that an in-vehicle update device 24 and an ECU 6 can communicate with each other via an in-vehicle network 7.

[0050] In the server 23, the control unit 25 is similar to the control unit 10 described in the first embodiment, and controls the overall operation of the server 23. In the on-board update device 24, the control unit 26 is similar to the control unit 12 described in the first embodiment, and controls the overall operation of the on-board update device 24.

[0051] When updating the software of the ECU 6 to be updated, the control unit 26 generates update information by referring to the update software and the configuration information received from the on-board update device 24, and transmits the generated update information to the on-board update device 24.

[0052] The control unit 26 includes a save target information calculation unit 26a, a continued use permission determination unit 26b, an arrangement address change determination unit 26c, a save target specification unit 26d, a data save unit 26e, and a data restoration unit 26f. Each of these units 26a to 26f realizes a part of the specific data save method and executes a part of the specific data save program.

[0053] When the save target information calculation unit 26a receives update information from the server 23, it calculates save target information related to the save target that needs to be saved when updating the software, based on the update contents of the update software. The continued use possibility determination unit 26b, the layout address change determination unit 26c, the save target specification unit 26d, the data save unit 26e, and the data restoration unit 26f perform the same processes as the continued use possibility determination unit 12a, the layout address change determination unit 12b, the save target specification unit 12c, the data save unit 12d, and the data restoration unit 12e described in the first embodiment, respectively.

[0054] Next, the operation of the above-mentioned configuration will be described with reference to FIGS. (2-1) Update information generation process performed by the server 23 (see FIG. 6) In the server 23, the control unit 25 starts an update information generation process, and when it receives configuration information from the on-board update device 5 (A1), it generates update information by referring to the update software and the received configuration information (A2). The control unit 25 transmits the generated update information to the on-board update device 24 (A11), and ends the update information generation process.

[0055] (2-2) Software update process performed by the in-vehicle update device 5 (see FIG. 7) In the in-vehicle update device 24, the control unit 26 starts the software update process, and when it receives update information from the server 23 (B1), it calculates the evacuation targets that need to be saved during the software update based on the update contents of the update software (B11, which corresponds to the evacuation target information calculation procedure), and thereafter performs steps B3 and subsequent steps described in the first embodiment.

[0056] By carrying out the above-mentioned process in cooperation with the server 23 and the on-board update device 24, the software of the update target ECU 6 is updated in a state in which the specific data specified as the data to be saved is saved from the update target ECU 6 to the on-board update device 24 in the same manner as in the first embodiment, as shown in Fig. 8. In this case, too, after the specific data is saved from the update target ECU 6 to the on-board update device 24, if the specific data can be continuously used before and after the software update and the location address of the specific data has changed before and after the software update, the saved specific data is written to the changed location address and returned to the update target ECU 6. If the specific data cannot be continuously used before and after the software update, the saved specific data is not returned to the update target ECU 6 but is retained in the on-board update device 24.

[0057] As described above, according to the second embodiment, it is possible to obtain the same effect as the first embodiment, and when updating the software of the ECU 6 to be updated, it is possible to properly store specific data in the vehicle-side system 22 and properly ensure the continuity of the specific data before and after the software update.

[0058] The save target information is calculated by the on-board update device 25. This makes it possible to avoid concentration of the process of calculating the save target information on the server 3, and therefore makes it possible to distribute the process of calculating the save target information.

[0059] (Other embodiments) Although the present disclosure has been described based on the embodiment, it is understood that the present disclosure is not limited to the embodiment or structure. The present disclosure also includes various modifications and modifications within the equivalent range. In addition, various combinations and forms, as well as other combinations and forms including only one element, more than one element, or less than one element, are also within the scope and concept of the present disclosure.

[0060] Although the above embodiment has been described with reference to wireless reprogramming in which update software is distributed from the servers 3 and 23, the present invention can also be applied to wired reprogramming in which update software is distributed from a reprogramming tool 9.

[0061] The control unit and the method described in the present disclosure may be implemented by a special-purpose computer provided by configuring a processor and memory that are software-programmed to execute one or more functions embodied in computer software. Alternatively, the control unit and the method described in the present disclosure may be implemented by a special-purpose computer provided by configuring a processor with one or more dedicated hardware logic circuits. Alternatively, the control unit and the method described in the present disclosure may be implemented by one or more special-purpose computers configured by a combination of a processor and memory that are software-programmed to execute one or more functions and a processor configured with one or more hardware logic circuits. Furthermore, the computer software may be stored in a computer-readable non-transitory tangible recording medium as instructions executed by a computer.

[0062] In addition to the claims, the present disclosure also includes the following inventions. [1] A software update system (1, 21) comprising: a distribution device (3, 9, 23) that distributes update software to an electronic control device to be updated; and an on-board update device (5, 24) that transmits the update software received from the distribution device to the electronic control device to be updated, thereby updating software of the electronic control device to be updated, wherein a vehicle-side system is constituted including the on-board update device and the electronic control device to be updated, a save target information calculation unit (10a, 26a) that calculates save target information relating to a save target that needs to be saved when updating software based on update contents of the update software; a continuous use possibility determination unit (12a, 26b) for determining whether specific data held in the electronic control device to be updated can be continuously used before and after the software update; a save target specifying unit (12c, 26d) for specifying the specific data as the save target when it is determined that the specific data cannot be continuously used; a data saving unit (12d, 26e) that saves the specific data identified as the data to be saved from the electronic control device to be updated to a save destination belonging to the vehicle-side system.

[0063] [2] a location address change determination unit (12b, 26c) for determining whether or not a location address of the specific data has been changed before and after a software update when it is determined that the specific data can be continuously used; The software update system according to [1], wherein the backup target identification unit identifies the specific data as the backup target even if it is determined that the location address of the specific data has changed before and after a software update.

[0064] [3] The software update system described in [2] is provided with a data restoration unit (12e, 26f) that restores the specific data saved to the save destination to the electronic control device to be updated if the specific data can continue to be used before and after the software update and the location address of the specific data has changed before and after the software update.

[0065] [4] The software update system according to [3], wherein the data recovery unit recovers the specific data saved to the save destination to the electronic control device to be updated after the software update is completed.

[0066] [5] The software update system according to [3], wherein the data recovery unit recovers the specific data saved to the save destination to the electronic control device to be updated during software update.

[0067] [6] A software update system described in any one of [2] to [5], wherein the data evacuation unit does not evacuate the specific data from the electronic control device to be updated if it is determined that the location address of the specific data has not changed before and after the software update.

[0068] [7] A software update system described in any one of claims [1] to [6], wherein the data evacuation unit sets the in-vehicle update device as a destination for the specific data, and evacuates the specific data from the electronic control device to be updated to the in-vehicle update device.

[0069] [8] A software update system described in any one of claims [1] to [7], wherein the continued use determination unit determines whether specific data stored in the electronic control device to be updated can be continuously used before and after the software update based on the location address.

[0070] [9] A software update system described in any one of claims [1] to [7], wherein the continued use determination unit determines whether specific data stored in the electronic control device to be updated can be continuously used before and after the software update based on at least one of a location address or a file name.

[0071]

[10] The software update system according to any one of claims [1] to [9], wherein the evacuation target information calculation unit is provided in the distribution device.

[0072]

[11] The software update system according to any one of claims [1] to [9], wherein the save target information calculation unit is provided in the in-vehicle update device. [Explanation of symbols]

[0073] In the drawing, 1 and 21 are software update systems, 2 and 22 are vehicle-side systems, 3 and 23 are servers (distribution devices), 5 and 24 are in-vehicle update devices, 6 is an ECU (electronic control unit to be updated), 9 is a reprogramming tool (distribution device), 10a and 26a are evacuation target information calculation units, 12a and 26b are continued use eligibility determination units, 12b and 26c are placement address change determination units, 12c and 26d are evacuation target identification units, 12d and 26e are data evacuation units, and 12e and 26f are data recovery units.

Claims

1. A software update system (1, 21) comprising: a distribution device (3, 9, 23) that distributes update software to an electronic control device to be updated; and an on-board update device (5, 24) that transmits the update software received from the distribution device to the electronic control device to be updated, thereby updating software of the electronic control device to be updated, wherein a vehicle-side system is constituted including the on-board update device and the electronic control device to be updated, a save target information calculation unit (10a, 26a) that calculates save target information relating to a save target that needs to be saved when updating software based on update contents of the update software; a continuous use possibility determination unit (12a, 26b) for determining whether specific data held in the electronic control device to be updated can be continuously used before and after the software update; a save target specifying unit (12c, 26d) for specifying the specific data as the save target when it is determined that the specific data cannot be continuously used; a data saving unit (12d, 26e) that saves the specific data identified as the data to be saved from the electronic control device to be updated to a save destination belonging to the vehicle-side system.

2. a location address change determination unit (12b, 26c) for determining whether or not a location address of the specific data has been changed before and after a software update when it is determined that the specific data can be continuously used; 2. The software update system according to claim 1, wherein the save target specification unit specifies the specific data as the save target even when it is determined that the location address of the specific data has changed before and after the software update.

3. A software update system as described in claim 2, further comprising a data restoration unit (12e, 26f) that restores the specific data saved to the save destination to the electronic control device to be updated if the specific data can continue to be used before and after a software update and if the location address of the specific data has changed before and after the software update.

4. 4. The software update system according to claim 3, wherein the data recovery unit recovers the specific data saved in the save destination to the electronic control unit to be updated after the software update is completed.

5. 4. The software update system according to claim 3, wherein the data recovery unit recovers the specific data saved in the save destination to the electronic control unit to be updated during software update.

6. 3. The software update system according to claim 2, wherein the data evacuation unit does not evacuate the specific data from the electronic control device to be updated if it is determined that the location address of the specific data has not changed before and after the software update.

7. 2. The software update system according to claim 1, wherein the data saving unit sets the on-board update device as a destination for saving the specific data, and saves the specific data from the electronic control unit to be updated to the on-board update device.

8. 2. The software update system according to claim 1, wherein the continued use possibility determination unit determines whether the specific data held in the electronic control device to be updated can be continuously used before and after the software update based on a location address.

9. The software update system according to claim 1, wherein the continued use determination unit determines whether specific data stored in the electronic control device to be updated can be continuously used before and after the software update based on at least one of a location address or a file name.

10. The software update system according to claim 1 , wherein the save target information calculation unit is provided in the distribution device.

11. The software update system according to claim 1 , wherein the save target information calculation unit is provided in the in-vehicle update device.

12. A software update system (1, 21) including a distribution device (3, 9, 23) that distributes update software to an electronic control device to be updated, and an on-board update device (5, 24) that transmits the update software received from the distribution device to the electronic control device to be updated, thereby updating software of the electronic control device to be updated, wherein a vehicle-side system is constituted by the on-board update device and the electronic control device to be updated, a save target information calculation step of calculating save target information relating to a save target that needs to be saved when updating software based on update contents of the update software; a continuous usability determination step for determining whether specific data held in the electronic control device to be updated can be continuously used before and after the software update; a save target identification step of identifying the specific data as the save target when it is determined that the specific data cannot be continuously used; a data evacuation procedure for evacuating the specific data identified as the data to be saved from the electronic control unit to be updated to a save destination belonging to the vehicle-side system;

13. A software update system (1, 21) comprising a distribution device (3, 9, 23) that distributes update software to an electronic control device to be updated, and an on-board update device (5, 24) that transmits the update software received from the distribution device to the electronic control device to be updated, thereby updating the software of the electronic control device to be updated, wherein a vehicle-side system is constituted by the on-board update device and the electronic control device to be updated, a save target information calculation step of calculating save target information relating to a save target that needs to be saved when updating software based on update contents of the update software; a continuous usability determination step for determining whether specific data held in the electronic control device to be updated can be continuously used before and after the software update; a save target identification step of identifying the specific data as the save target when it is determined that the specific data cannot be continuously used; a specific data evacuation program for executing a data evacuation procedure for evacuating the specific data identified as the data to be saved from the electronic control device to be updated to a save destination belonging to the vehicle-side system;

Citation Information

Patent Citations

  • Software update apparatus, server device, software update method, and program

    JP2021012434A