Vehicle software update system

The vehicle software update system addresses the challenge of managing complex vehicle settings by selectively updating essential functions, reducing update time and memory usage, thereby enhancing user convenience and system longevity.

WO2024247088A1PCT designated stage expired Publication Date: 2024-12-05ASTEMO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2023/020038
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-30
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

As autonomous driving and advanced driving support functions become more complex, users face challenges in personalizing vehicle settings and software updates, leading to increased memory depletion, longer update times, and reduced memory lifespan due to the need to manage numerous functions and updates across various electronic control units.

Method used

A vehicle software update system that includes a server and vehicle control device, which acquires and compares function information before and after transfer, allowing users to selectively update only necessary functions, thereby prioritizing updates and optimizing memory usage.

Benefits of technology

This approach reduces software update time, conserves non-volatile memory capacity, and extends the memory lifespan by ensuring only required functions are updated, improving user convenience and system reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023020038_05122024_PF_FP_ABST
    Figure JP2023020038_05122024_PF_FP_ABST
Patent Text Reader

Abstract

A server of this vehicle software update system that manages the software updates of a plurality of function-specific ECUs in a vehicle after a transfer comprises: an acquisition unit A that acquires installed function information on the vehicle before the transfer; an acquisition unit B that acquires installed function information on the vehicle after the transfer; an acquisition unit C that acquires user selection function information from a user terminal; a differential extraction unit that extracts differences between the installed function information on the vehicle before the transfer, the installed function information on the vehicle after the transfer, and user selection function information; and an update process determination unit that selects a necessary software update process and generates update function information according to the contents of the differences. A vehicle control device of the vehicle after the transfer includes a software update determination unit that controls the software update and the priority in the plurality of function-specific EUs according to the update function information delivered from the server. Each of the plurality of function-specific ECUs of the vehicle after the transfer has a software update processing unit that executes a software update method delivered by the vehicle control device of the vehicle after the transfer.
Need to check novelty before this filing date? Find Prior Art

Description

Vehicle Software Update System

[0001] The present disclosure relates to a vehicle software update system.

[0002] As autonomous driving and advanced driver assistance functions become more multifunctional and sophisticated, there is a desire for users to continue using the functions and settings that are important to them when driving a newly purchased vehicle, a rental car, or a vehicle that has been driven by someone else. Also, driving a new vehicle without being familiar with it can lead to accidents. Car personalization is an effective way to solve this problem.

[0003] A technique is known, for example, from Japanese Patent Application Laid-Open No. 2003-144990, in which user-customized settings are transmitted to an in-vehicle electronic control unit to be rewritten, and the in-vehicle electronic control unit operates according to the user-customized settings.

[0004] JP 2014-182571 A

[0005] In Patent Document 1, differences in user preference settings are extracted by comparing the new user's preference settings with the old user's preference settings, but there is no mention of functional differences between the vehicle before and after the vehicle change. Furthermore, the user preference settings are only data, and no consideration is given to updating functions implemented by software.

[0006] An object of the present disclosure is to provide a vehicle software update system that allows users to selectively set functions that they value and that can accommodate personalization to improve user convenience.

[0007] When personalizing a device, if many functions are installed in advance and then user-selectable functions are added, problems arise such as memory exhaustion due to the increased memory capacity and increased update time.Furthermore, frequent memory updates can shorten the memory lifespan (causing breakdowns).

[0008] The present disclosure provides a vehicle software update system comprising a vehicle control device mounted on a vehicle and a server communicating via a network, the vehicle including a pre-transfer vehicle and a post-transfer vehicle, the system managing software updates of a plurality of functional electronic control devices in the post-transfer vehicle, the server comprising: an acquisition unit A that acquires onboard function information of the pre-transfer vehicle; an acquisition unit B that acquires onboard function information of the post-transfer vehicle; an acquisition unit C that acquires user-selected function information from a user terminal; a difference extraction unit that extracts differences between the onboard function information of the pre-transfer vehicle, the onboard function information of the post-transfer vehicle, and the user-selected function information; and an update process determination unit that selects a required software update process according to the content of the difference and generates update function information based on the required software update process, and in the post-transfer vehicle, the vehicle control device has a software update determination unit that controls software updates and priorities in the plurality of functional electronic control devices according to the update function information distributed from the server, and each of the plurality of functional electronic control devices has a software update processing unit that executes a software update method notified by the vehicle control device of the post-transfer vehicle.

[0009] Functions that are important to the user can be acquired by acquisition unit C. Difference information can be acquired by acquisition units A and B. By comparing this difference information with the information on functions that are important to the user acquired by acquisition unit C (by comparing the two pieces of information), the software update determination unit determines the software that should be updated.

[0010] According to the present disclosure, software updates are performed only for the functions and differences that the user needs, making it possible to personalize the vehicle after switching vehicles, thereby reducing the time required for software updates, reducing the capacity of the non-volatile memory of the functional electronic control devices, and extending the memory life of the non-volatile memory of the functional electronic control devices.

[0011] 1 is a block diagram showing the overall configuration of a vehicle software update system according to a first embodiment. 2 is a sequence diagram of the vehicle software update system according to the first embodiment. 3 is a data flow diagram illustrating a software update method of the vehicle software update system according to the first embodiment. 4 is a flowchart illustrating a difference extraction process according to the first embodiment. 5 is a flowchart illustrating an update process determination according to the first embodiment. 6 is an example of priority setting for each functional ECU according to a second embodiment. 7 is a flowchart illustrating a priority setting process according to the second embodiment. 8 is a flowchart illustrating an ECU update process according to the second embodiment. 9 is a diagram showing a typical configuration example of a control device included in a functional ECU.

[0012] Hereinafter, the present embodiment will be described with reference to the accompanying drawings. In the accompanying drawings, functionally identical elements may be designated by the same numerals. Note that the accompanying drawings show embodiments and implementation examples according to the principles of the present disclosure, but these are for understanding the present disclosure and are not to be used to interpret the present disclosure in a limiting manner. The descriptions in this specification are merely typical examples and are not intended to limit the scope or application of the present disclosure in any way.

[0013] Although the present embodiment has been described in sufficient detail to enable those skilled in the art to practice the present disclosure, it should be understood that other implementations and forms are possible, and that changes in configuration and structure and substitutions of various elements are possible without departing from the scope and spirit of the technical ideas of the present disclosure. Therefore, the following description should not be interpreted as being limited thereto.

[0014] Embodiments of the present disclosure will now be described with reference to FIGS.

[0015] First Embodiment Fig. 1 is a block diagram showing the overall configuration of a vehicle software update system according to a first embodiment. The vehicle software update system 10 shown in Fig. 1 includes a center 100, which is an over-the-air (OTA) server, a post-transfer vehicle (vehicle B, second vehicle) 200, a pre-transfer vehicle (vehicle A, first vehicle) 300, and a user terminal 400, all of which are connected to one another via a network 20. The network 20 may be, for example, a mobile phone network or the Internet. The vehicle software update system 10 is a system that manages software updates for a plurality of functional electronic control units (ECUs: Electronic Control Units) 206, 208, and 210 in the post-transfer vehicle 200.

[0016] The center 100, which is a server, can communicate with the vehicle control devices 301, 201 installed in the vehicles 300, 200 via the network 20. The center 100 receives installed function information from the post-transfer vehicle 200, the pre-transfer vehicle 300, and the user terminal 400 via the network 20, and transmits (distributes) update function information for updating the software of each functional ECU 206, 208, 210 in the post-transfer vehicle 200. The center 100 includes a vehicle / user authentication processing unit 101, a vehicle installed function information receiving unit 102, a user-selected function receiving unit 103, a difference extraction unit 104, an update processing determination unit 105, and an update function information transmitting unit 106.

[0017] The post-transfer vehicle 200 includes a vehicle control device 201 that controls software updates and multiple functional ECUs 206, 208, and 210. In this example, the multiple functional ECUs 206, 208, and 210 are an automatic driving ECU 206, a brake ECU 208, and an engine ECU 210. Each of the functional ECUs 206, 208, and 210 includes an update processing unit (also referred to as a software update processing unit) 207, 209, and 211, respectively. The ECUs installed in the post-transfer vehicle 200 are not limited to those shown in FIG. 1 , and other ECUs may also be installed. FIG. 9 is a diagram showing a typical configuration example of the control devices included in the functional ECUs. In this example, a processor PRO serving as a control device included in the functional ECUs, such as the automatic driving ECU 206, the brake ECU 208, and the engine ECU 210, is formed on a single semiconductor substrate SUB made of a single crystal, such as silicon, as shown in FIG. 9 . The processor PRO includes a central processing unit CPU capable of executing software, a random access memory RAM consisting of volatile memory used as a temporary work area for the central processing unit CPU, a flash read-only memory FROM consisting of nonvolatile memory for storing the software PROG executed by the central processing unit CPU as data, a peripheral function circuit PRI, and a bus BUS. The flash read-only memory FROM is a semiconductor memory in which the data, which is the software PROG, can be rewritten. In this embodiment, the flash read-only memory FROM is a memory in which updated software is stored. The bus BUS interconnects the central processing unit CPU, the random access memory RAM, the flash read-only memory FROM, and the peripheral function circuit PRI.

[0018] The vehicle control device 201 includes a vehicle authentication processing unit 202 , an installed function information transmitting unit 203 , an update function information receiving unit 204 , and a software update determining unit 205 .

[0019] The pre-transfer vehicle 300 includes a vehicle authentication processing unit 301 and an on-board function information transmission unit 302. The pre-transfer vehicle 300 also includes one or more ECUs, but these are not relevant to the present invention and are therefore not shown in FIG.

[0020] The user terminal 400 is composed of a user authentication processing unit 401, a user-selected function information input unit 402, and a user setting data area 403. The user terminal 400 is a dedicated terminal or a mobile terminal (such as a tablet PC or smartphone) carried by the user. After user authentication, the user terminal 400 is connected to the center 100 and becomes available for use. The user setting data area 403 also stores seat and mirror position information, brake and steering sensitivity information, function priority setting data (see FIG. 6), and the like, which are transmitted to the center 100 as user-selected function information.

[0021] 2 is a sequence diagram of the vehicle software update system according to the first embodiment. The pre-transfer vehicle 300 transmits an authentication request from the vehicle authentication processing unit 301 to the center 100 (P1). The center 100 performs authentication using the vehicle / user authentication processing unit 101 and returns a completion notification after authentication is complete (P2). The post-transfer vehicle 200 transmits an authentication request from the vehicle authentication processing unit 202 to the center 100 (P3). The vehicle / user authentication processing unit 101 performs authentication and returns a completion notification after authentication is complete (P4). Thereafter, the pre-transfer vehicle 300 and the post-transfer vehicle 200 transmit on-board function information to the vehicle on-board function information receiving unit 102 of the center 100 (P5, P6). In other words, the vehicle-mounted function information receiving unit 102 has a first acquisition unit (acquisition unit A) that acquires the mounted function information of the pre-transfer vehicle 300 from the mounted function information transmitting unit 302, and a second acquisition unit (acquisition unit B) that acquires the mounted function information of the post-transfer vehicle 200 from the mounted function information transmitting unit 203.

[0022] The user terminal 400 transmits a user authentication request to the center 100 from the user authentication processing unit 401 (P7). The center 100 performs user authentication in the vehicle / user authentication processing unit 101 and returns a completion notification after authentication is complete (P8). After authentication is complete, the user inputs the user-selected function on the user-selected function information input unit 402 of the user terminal 400 (P9). After this input, the user terminal 400 transmits the user-selected function information to the user-selected function receiving unit 103 of the center 100 (P10). In other words, the user-selected function receiving unit 103 has a third acquisition unit (acquisition unit C) that acquires the user-selected function information (information on the installed functions selected by the user) from the user-selected function information input unit 402. Note that the order of authentication of the pre-transfer vehicle 300, post-transfer vehicle 200, and user terminal 400 is not limited to the above example, and the order can be reversed. Furthermore, authentication of each vehicle 300, 200 can be performed continuously or periodically.

[0023] In the center 100, the vehicle-mounted function information receiving unit 102 and the user-selected function receiving unit 103 receive function information (installed function information of the vehicle 300, installed function information of the vehicle 200, and user-selected function information) transmitted from the pre-transfer vehicle 300, the post-transfer vehicle 200, and the user terminal 400, and then the difference extracting unit 104 extracts differences (P11). The update process determining unit 105 then determines whether an update process is required (P12), and the update function information transmitting unit 106 transmits (distributes) the update function information to the post-transfer vehicle 200 (P13). The update process determining unit 105 determines whether an update process is required based on the content of the differences, selects a required software update process, and generates update function information based on the required software update process. The update function information transmitting unit 106 transmits the update function information from the update process determining unit 105 to the update function information receiving unit 204 of the post-transfer vehicle 200.

[0024] In the vehicle 200 after the vehicle transfer, the update function information receiving unit 204 receives the update function information, and the software update determining unit 205 determines the software update content based on the update function information (P14). After determining the software update method, the software update determining unit 205 transmits an update instruction to each functional ECU (in the example of FIG. 2, the software update processing unit 207 of the autonomous driving ECU 206) (P15). As described in Example 2 below, the software update determining unit 205 can be configured to control software updates and priorities within multiple functional electronic control units 206, 208, and 210. For details about priorities, see the description of Example 2. Software update methods include new addition (Install), deletion (Remove), update (Update), and no processing (Skip). For details about software update methods, see the description of FIG. 3 below.

[0025] The autonomous driving ECU 206 performs update processing using the update processing unit 207 of the autonomous driving ECU 206 in accordance with the instruction received from the software update determination unit 205 in the vehicle control device 201 of the post-transfer vehicle 200 (P16). That is, each of the multiple functional electronic control devices 206, 208, 210 has a software update processing unit 207, 209, 211 that executes the software update method received from the software update determination unit 205 of the vehicle control device 201 of the post-transfer vehicle 200.

[0026] After the update is complete, the vehicle control device 201 is notified of the update completion (P17). The vehicle control device 201 notifies the center 100 of the update completion (P18), and the center 100 notifies the user terminals 400 of the update completion in turn (P19).

[0027] 3 is a data flow diagram illustrating the software update method of the vehicle software update system according to the first embodiment. User selected function information and the update method will be described with reference to FIG.

[0028] For example, assume that the autonomous driving assistance functions in the autonomous driving ECU 206 are four functions: function A (FA), function B (FB), function C (FC), and function D (FD). The pre-transfer vehicle 300 is equipped with function A (FA), function B (FB), and function D (new version) (FDNE). The post-transfer vehicle 200 is equipped with function A (FA), function C (FC), and function D (old version) (FDOL). If the user selects function A (FA), function B (FB), or function D (new version) (FDNE) as the required functions, the center 100 determines the required functions and update method for the post-transfer vehicle 200 using the difference extraction unit 104 and the update process determination unit 105.

[0029] After the vehicle transfer, vehicle 200 updates the software in autonomous driving ECU 206 in accordance with instructions from center 100 (ECU update process: P16). In the example of FIG. 3 , function A (FA) remains unchanged, so no processing is performed (Skip), function B (FB) is newly added (Install), function C (FC) is deleted (Remove), and function D (FD) is updated (Update) from the old version (FDOL) to the new version (FDNE). By using the difference information in this manner, the increase in the rewrite time and storage capacity (software PROG capacity) of the software PROG in the flash read-only memory FROM can be suppressed. Therefore, according to this embodiment, effects such as a reduction in the storage capacity of the flash read-only memory FROM, a shortened update time, and an extension of the memory life of the flash read-only memory FROM can be obtained. A flash read-only memory FROM has the characteristic that its lifespan is shortened if its stored contents are frequently rewritten, so by reducing the number of rewrites (updates), the lifespan of the flash read-only memory FROM can be extended.

[0030] The operation of the differential extraction unit 104 (steps S401 to S409 in FIG. 4) and the operation of the update process determination unit 105 (steps S501 to S511 in FIG. 5) will be described with reference to the flowcharts of FIGS.

[0031] First, in FIG. 4, the difference extraction unit 104 starts the difference extraction process (S401).

[0032] Next, the difference extraction unit 104 acquires vehicle-mounted function information (S402). Examples of vehicle-mounted function information include the type of ECU by function, ECU function information, inter-ECU dependency, manufacturer name, vehicle model name, and platform generation. Note that in this embodiment, the platform is recommended to use SOTA (Software Over the Air) of the Adaptive Platform (AP) standardized by the standardization organization AUTOSAR, and the compatible version of the Adaptive Platform is included in the determination items.

[0033] In S403, the difference extraction unit 104 determines the manufacturer, vehicle model, and platform generation, and if compatible (OK) (YES), the process of the difference extraction unit 104 proceeds to S404. If not compatible (NG) (NO), the process of the difference extraction unit 104 proceeds to S408.

[0034] In S404, the difference extraction unit 104 compares the built-in functions with the user-selected functions and extracts them. The specific extraction method is as described with reference to FIG.

[0035] In S405, the difference extraction unit 104 selects the functional ECUs and software associated with the extracted function.

[0036] Next, in S406, the update process determination unit 105 performs resource determination. Examples of resources include hardware resources required to execute the extraction function, such as the sensor configuration, and software resources, such as the software version and required memory size. Note that the information used for resource determination is assumed to be included as part of the vehicle function installation information. If the resource determination is OK (YES), the process of the difference extraction unit 104 proceeds to S407. If the resource determination is NG (NO), the process of the difference extraction unit 104 proceeds to S408.

[0037] In S407, the difference extraction unit 104 determines the target ECU and update software.

[0038] In S408, the differential extraction unit 104 determines that the determination condition is not satisfied and issues a non-processing notification. That is, in S408, the update process is stopped. Then, a non-processing notification is sent to the user to inform them that the update process has been stopped.

[0039] Thus, the difference extraction process by the difference extraction unit 104 ends (S409).

[0040] Next, the update process determination will be described with reference to Fig. 5. In Fig. 5, the update process determination unit 105 starts the update process determination (S501).

[0041] The update process determination unit 105 acquires the target ECU and function information from the result of the difference extraction process described in FIG. 4 (S502), and acquires function information of the post-transfer vehicle 200 (S503). In S504, the update process determination unit 105 checks whether the function is not yet installed in the post-transfer vehicle 200. If the function is not yet installed (YES), the process of the update process determination unit 105 proceeds to S507. If the result of S504 is NO (installed), the process of the update process determination unit 105 proceeds to S505. In S505, the update process determination unit 105 checks whether the function is unnecessary for the post-transfer vehicle 200. If the result of S505 is NO (necessary function), the process of the update process determination unit 105 proceeds to S508. If the result of S505 is NO (necessary function), the process of the update process determination unit 105 proceeds to S506. In S506, the update process determination unit 105 checks whether an update such as a version upgrade is necessary, and if an update is necessary (YES), the process of the update process determination unit 105 proceeds to S509. If an update is not necessary (NO) in S506, the process of the update process determination unit 105 proceeds to S510.

[0042] The update process determination unit 105 selects new addition (Install) in S507 and selects removal (Remove) in S508. The update process determination unit 105 selects update (Update) in S509 and selects no processing (Skip) in S510. Thereafter, the update process determination by the update process determination unit 105 ends (S511). In other words, the update process determination unit 105 is configured to be able to select the type of software update process from addition (Install), update (Update), removal (Remove), and skip (Skip).

[0043] Therefore, each functional ECU (e.g., automatic driving ECU 206, brake ECU 208, engine ECU 210) installed in vehicle 200 after vehicle transfer performs software update processing using each update processing unit (207, 209, 211) in accordance with instructions from software update determination unit 205. That is, each update processing unit (207, 209, 211) can perform new addition (Install), deletion (Remove), update (Update), or no processing (Skip). Each update processing unit (207, 209, 211) performs one of the instructed operations of new addition (Install), deletion (Remove), update (Update), and no processing (Skip) in accordance with instructions from software update determination unit 205.

[0044] Second Embodiment A vehicle software update system according to a second embodiment will be described with reference to FIGS.

[0045] In the first embodiment, the case where only the autonomous driving ECU 206 is the ECU to be updated is described, but in the second embodiment, an example in which multiple ECUs are updated is shown. Note that the vehicle software update system of the second embodiment can utilize the vehicle software update system of the first embodiment described with reference to Figures 1 to 5. Furthermore, since the vehicle software update system of the second embodiment operates in the same manner as the vehicle software update system of the first embodiment described with reference to Figures 1 to 5, duplicated description will be omitted.

[0046] FIG. 6 shows an example of priority setting for each functional ECU according to the second embodiment. FIG. 6 illustrates an example of priority setting for functional ECUs installed in a vehicle 200 after vehicle transfer, and includes examples of ECU types 600, setting functions 610, update targets 620, and various priorities 630. In this example, the ECU types 600 include an engine ECU 60A (corresponding to 210 in FIG. 1 ), a brake ECU 60B (corresponding to 208 in FIG. 1 ), a steering ECU 60C ​​(corresponding to 206 in FIG. 1 ), an automatic driving ECU 60D, a mechanical system control ECU 60E, and an information system ECU 60F. In this example, the setting functions 610 include an engine control ECU 61A, a brake sensitivity ECU 61B, a steering sensitivity ECU 61C, a driving assistance / automatic driving ECU 61D, a seat position and mirror position 61E, and a car navigation / air conditioner (car navigation system / air conditioner) 61F. In this example, the update target 620 includes data and programs 62A, programs 62B, and data 62C.

[0047] The various priorities 630 can be classified by the factors that are emphasized, such as vehicle function emphasis 63A, safety emphasis 63B, update size emphasis 63C, and user setting emphasis 63D. The numbers (1-6) listed in the various priorities 630 indicate increasing priority (priority: 1>2>3>4>5>6). As shown in FIG. 6 , it can be seen that the appropriate priority changes depending on the factors that are emphasized (63A, 63B, 63C, 63D). The priority numbers (1-6) listed in FIG. 6 are provided as a representative example to explain this embodiment, and are not limited to these.

[0048] In the second embodiment, as shown in FIG. 6, a priority setting method 640 can be selected from among initial setting (1) 641, initial setting (2) 642, automatic determination 643, and user setting 644.

[0049] The priority setting process (steps S701 to S710 in FIG. 7) will be described with reference to the flowchart in FIG. 7. The priority setting is performed by software update determination unit 205 of post-transfer vehicle 200.

[0050] The software update determination unit 205 starts the priority setting process (S701). Next, the software update determination unit 205 acquires update target ECU information (S702). In S703, the software update determination unit 205 checks whether there are multiple ECUs to be updated. If there are multiple ECUs to be updated (YES) in S703, the software update determination unit 205 proceeds to S704. If there are not multiple ECUs to be updated (NO) in S703, the software update determination unit 205 terminates the process because priority determination is not necessary (S710). In S704, the software update determination unit 205 checks whether the user setting data area 403 contains priority settings. If there are user settings (YES) in S704, the software update determination unit 205 proceeds to S707. If there are no user settings (NO) in S704, the software update determination unit 205 proceeds to S705.

[0051] In S705, the software update determination unit 205 calculates the update size of each ECU to be updated. If the difference in update size is small, there is little benefit to prioritizing the update size, so the software update determination unit 205 checks whether the difference is equal to or greater than a preset threshold (e.g., 1 Mbyte or greater) (S706). If the difference in update size is equal to or greater than the threshold (YES), the software update determination unit 205 proceeds to S708. If the difference in update size is within the threshold (NO), the software update determination unit 205 proceeds to S709.

[0052] In S707, the software update determining unit 205 sets the priority setting method 640 to the user setting 644.

[0053] In S708, the software update determination unit 205 sets the priority setting method 640 to automatic determination 643. In automatic determination 643, update priorities are set in descending order of update size. The reason for setting priorities based on update size is to reduce the probability of update failure.

[0054] In S709, the software update determination unit 205 sets the priority setting method 640 to the initial value (2) 642 (safety-oriented 63B). Note that the initial value (2) 642 can be changed to the initial value (1) 641 or another initial value setting. In this embodiment, in order to ensure the safety of vehicle functions in the event that the update fails midway, the initial value of the priority setting method 640 is set to the initial value (2) 642 of safety-oriented 63B.

[0055] After each setting is completed, the priority setting process by the software update determining unit 205 ends (S710).

[0056] Therefore, the software update determining unit 205 is configured to be able to control software updates and priorities in the multiple functional electronic control units 206, 208, and 210, as explained in P15 of FIG.

[0057] 8 is a flowchart illustrating the ECU update process according to the second embodiment. The ECU update process (steps S801 to S812) will be described with reference to FIG. 8. The ECU update process is performed by software update determination unit 205 of post-transfer vehicle 200.

[0058] The software update determination unit 205 starts the ECU update process (S801). First, the software update determination unit 205 acquires information about ECUs to be updated (S802). The order in which each ECU is updated follows the priority setting determined in the flowchart of FIG. 7. For example, if the ECUs to be updated are the autonomous driving ECU 206, the brake ECU 208, and the engine ECU 210 shown in FIG. 1, and the priority setting method 640 in FIG. 6 is automatic determination 643 (priority on update size 63C), the autonomous driving ECU 206 will be updated first, followed by the engine ECU 210, and finally the brake ECU 208.

[0059] In S803, the software update determination unit 205 checks the ECU to be updated. If there is an ECU that has not been updated (YES in S803), the process of the software update determination unit 205 proceeds to S804. If there is no ECU that has not been updated (NO in S803), the process of the software update determination unit 205 proceeds to S811.

[0060] In S804, each functional ECU (autonomous driving ECU 206, brake ECU 208, engine ECU 210) executes update processing using each update processing unit (207, 209, 211) in accordance with instructions from the software update determination unit 205. In S805, the software update determination unit 205 checks whether the update processing is successful. If the update processing is successful in S805 (YES), the processing of the software update determination unit 205 returns to S803. If the update processing is unsuccessful in S805 (NO), the processing of the software update determination unit 205 proceeds to S806. Normally, when multiple ECUs are updated, there is a high possibility that the update will fail.

[0061] In S806, the software update determination unit 205 updates the retry counter to execute a retry process (a second update process) for the functional ECU for which the update process has failed. That is, the retry counter counts the number of retries. Then, the process of the software update determination unit 205 proceeds to S807. In S807, the software update determination unit 205 checks the counter value of the retry counter. If the counter value of the retry counter exceeds a preset counter value (e.g., 2) (YES), the process of the software update determination unit 205 proceeds to S808. If the counter value of the retry counter does not exceed the preset counter value (e.g., 2) (NO), the process of the software update determination unit 205 returns to S803. As a result, the retry process is executed for the functional ECU for which the update process has failed.

[0062] In S808, if the retry count exceeds a predetermined number (in this example, this means that the counter value of the retry counter exceeds 2), the software update determination unit 205 checks for inconsistencies between the multiple functional ECUs. Specifically, checking for inconsistencies between the multiple functional ECUs is a process of confirming whether updates for all dependent functional ECUs have been completed. In other words, when an update fails for one of the multiple functional ECUs, by confirming whether updates for all dependent functional ECUs have been completed, it is possible to determine inconsistencies between all dependent functional ECUs, whether they have been updated or not (update failure). If an inconsistency is found in S808 (YES), the software update determination unit 205 proceeds to S810. If an inconsistency is not found in S808 (NO), the software update determination unit 205 proceeds to S809. The dependency between the functional ECUs can be acquired from the installed function information. For example, if there are three ECUs to be updated, namely, the automatic driving ECU 206, the brake ECU 208, and the engine ECU 210, the automatic driving ECU 206 and the brake ECU 208 are dependent on each other, while the engine ECU 210 is not dependent on the other ECUs (206, 208). In this case, an inconsistency occurs when the update of either the automatic driving ECU 206 or the brake ECU 208 fails.

[0063] In S809, the software update determination unit 205 transmits an update failure notification. In this case, the update of some ECUs is not completed.

[0064] In S810, the software update determination unit 205 executes a rollback process to return all dependent ECUs to their original software states (software states before the update). By executing the rollback process, it is possible to avoid an inconsistency between all dependent ECUs.

[0065] In S811, the software update determination unit 205 transmits an update completion notification when the update of all ECUs has been successful.

[0066] This completes the ECU update process (S812).

[0067] Third Embodiment A vehicle software update system according to a third embodiment will be described.

[0068] The user terminal 400 does not have to be a dedicated terminal or a portable terminal, but can be an in-vehicle terminal or a navigation terminal having a panel unit mounted inside the post-transfer vehicle 200 or the pre-transfer vehicle 300. The panel unit of the in-vehicle terminal or the navigation terminal can be used as an input unit. By using these, it is possible to input user-selected function information inside the post-transfer vehicle 200 or the pre-transfer vehicle 300. For example, an input / output device such as a panel unit of a navigation terminal mounted in a vehicle can be used as the user-selected function information input unit 402 described in FIG. 1. Because an in-vehicle terminal or a navigation terminal provided in the vehicle (300, 200) can be used, there is no need to separately purchase a dedicated terminal or a portable terminal, and therefore a vehicle software update system can be constructed at a relatively low cost.

[0069] In the software update system of the present disclosure, the functions of the server 100 (101-106), the functions of the vehicle 200 (202-205, 207, 209, 211), the functions of the vehicle 300 (301, 302), and the functions of the user terminal 400 (401-403) may be configured as hardware circuits formed on a semiconductor substrate. They may also be configured as software executed by a CPU. Alternatively, they may be configured using both hardware circuits and software.

[0070] (Modifications) The present disclosure is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present disclosure, and are not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0071] 10: Vehicle software update system, 20: Network, 100: Center (OTA server), 101: Vehicle / user authentication processing unit, 102: Vehicle-mounted function information receiving unit, 103: User-selected function receiving unit, 104: Difference extraction unit, 105: Update processing determination unit, 106: Update function information transmitting unit, 200: Transferred vehicle, 201: Vehicle control device (software update control device), 202: Vehicle authentication processing unit, 203: Mounted function information transmitting unit, 204: Update function information receiving unit, 205: Software update determination unit, 206: Autonomous driving ECU, 207: Autonomous driving ECU update processing unit, 208: brake ECU, 209: brake ECU update processing unit, 210: engine ECU, 211: engine ECU update processing unit, 300: previous vehicle, 301: vehicle authentication processing unit, 302: installed function information transmission unit, 400: user terminal, 401: user authentication processing unit, 402: user selected function information input unit, 403: user setting data area, 600: ECU type, 610: setting function, 620: update target, 630: various priorities, 640: priority setting method, 641: initial setting (1), 642: initial setting (2), 643: automatic determination, 644: user setting

Claims

1. A vehicle software update system comprising a vehicle control device mounted on a vehicle and a server communicating via a network, the vehicle including a pre-transfer vehicle and a post-transfer vehicle, the system managing software updates of a plurality of functional electronic control devices in the post-transfer vehicle, the server comprising: an acquisition unit A for acquiring on-board function information of the pre-transfer vehicle; an acquisition unit B for acquiring on-board function information of the post-transfer vehicle; an acquisition unit C for acquiring user-selected function information from a user terminal; a difference extraction unit for extracting differences between the on-board function information of the pre-transfer vehicle, the on-board function information of the post-transfer vehicle and the user-selected function information; and an update process determination unit for selecting a required software update process according to the content of the difference and generating update function information based on the required software update process, in the post-transfer vehicle, the vehicle control device comprising a software update determination unit for controlling software updates and priorities in the plurality of functional electronic control devices according to the update function information distributed from the server, and each of the plurality of functional electronic control devices comprising a software update processing unit for executing a software update method notified from the vehicle control device of the post-transfer vehicle. Vehicle software update system.

2. A vehicle software update system according to claim 1, wherein the difference extraction unit judges the platform, and if the judgment conditions are not met, stops the update process and notifies the user.

3. A vehicle software update system according to claim 1, wherein the difference extraction unit performs a resource judgment of the ECU, and if a judgment condition is not satisfied, stops the update process and notifies the user.

4. A vehicle software update system according to claim 1, wherein the update process determination unit selects the type of the software update process from among add, update, delete, and skip.

5. A vehicle software update system according to claim 1, wherein the user terminal is a mobile terminal carried by a user.

6. A vehicle software update system as described in claim 1, wherein the user terminal is capable of performing input operations inside the pre-transfer vehicle or the post-transfer vehicle.

7. A vehicle software update system as described in claim 1, wherein, when the update targets are multiple of the multiple functional electronic control devices in the vehicle control device of the switched vehicle, the software update determination unit allows the user to select from user setting, automatic determination, and a safety-oriented initial setting in setting the priority.

8. A vehicle software update system as described in claim 7, wherein the automatic judgment sets update priorities among the target electronic control devices in descending order of update size, and if the difference in update size is within a preset threshold, enables the selection of the initial setting that prioritizes safety.

9. A vehicle software update system according to claim 1, wherein the software update processing unit of each of the plurality of functional electronic control units is capable of executing add, update, delete, and skip as the software update process.

10. A vehicle software update system as described in claim 1, wherein, when an update fails in any of the plurality of functional electronic control devices, the software update determination unit of the vehicle control device of the post-transfer vehicle checks whether updates have been completed for all dependent functional electronic control devices, determines inconsistencies between updated and unupdated functional electronic control devices among all dependent functional electronic control devices, executes a retry process to re-update the functional electronic control device whose update has failed, and, if the retry process exceeds a predetermined number of retries, executes a rollback process to return all dependent functional electronic control devices to their original software states.

Citation Information

Patent Citations

  • On-vehicle terminal device, server device, and terminal device

    JP2019182231A

  • Vehicle setting inheritance system

    JP2020158003A

  • Vehicle setting device and vehicle setting method

    JP2023022577A