Vehicle electronic control devices and computer-readable non-transitory storage media
By enabling activation approval and switching instructions when the vehicle is rechargeable, the problem of increased battery power consumption when the IG is disconnected is resolved, achieving safe and reliable software updates and rapid activation processing.
Patent Information
- Application Number
- CN202280036678.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-05-24
- Filing Date
- 2022-04-27
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-04-27
AI Technical Summary
Activation approval of vehicle electronic control units while the IG is disconnected may increase vehicle battery power consumption and affect safe and reliable software updates.
Activation approval is performed when the vehicle is in an IG-enabled state capable of charging the vehicle battery, and a switching instruction is sent while the vehicle is in an IG-enabled state to ensure that activation is performed while the vehicle is in a rechargeable state.
By performing activation approval while IG is on, the power consumption of the vehicle battery is suppressed, ensuring safe and reliable software updates, and activation is completed quickly while IG is off.
Smart Images

Figure CN117396842B_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This application is based on Japanese Application No. 2021-086936, filed on May 24, 2021, the contents of which are incorporated herein by reference. Technical Field
[0003] This disclosure relates to electronic control devices for vehicles and their update procedures. Background Technology
[0004] In recent years, with the diversification of vehicle control functions such as driver assistance and autonomous driving, the scale of software, including vehicle control and diagnostic programs and data such as nodes such as electronic control units (ECUs) installed in vehicles, has increased. Furthermore, with version upgrades resulting from functional improvements, the opportunities for updating (reprogramming) the software required to update (reprogram) nodes have also increased. On the other hand, with the development of communication networks, connected car technology has become widespread. Due to this situation, the following technology has been proposed (for example, see Patent Document 1): a vehicle electronic control unit is installed on the vehicle side, functioning as a gateway ECU; within the vehicle electronic control unit, update data downloaded from a central device is distributed to the nodes to be updated, and the software of the nodes to be updated is updated via OTA (Over-The-Air).
[0005] Patent Document 1: Japanese Patent Application Publication No. 2020-27627
[0006] After sending the installation instruction to write updated data to the update target node, the vehicle's electronic control unit (ECU) receives an installation completion notification from the update target node indicating that the installation process is complete. Following a switch from ignition switch (hereinafter referred to as IG) on to IG off, the ECU prompts the user for activation approval. If the ECU confirms the user's approval, it sends a switch instruction to the update target node to perform the activation process. If the update target node receives the switch instruction from the ECU, it performs activation processing to make the updated software effective. If the ECU receives an activation completion notification from the update target node indicating that the activation process is complete, it performs a system compatibility check. If the compatibility result is incorrect, it either resends the switch instruction to the update target node or rolls back the update target node's software to its state before the installation process.
[0007] However, in a structure where activation approval is performed after switching from IG on to IG off, i.e., in the IG off state, as described above, the power consumption of the vehicle battery may increase. Summary of the Invention
[0008] The purpose of this disclosure is to suppress the power consumption of vehicle batteries and to ensure safe and reliable software updates.
[0009] According to one aspect of this disclosure, after completing the installation process in the update target node, the activation approval execution unit prompts the user for activation approval. The installation process involves writing update data and generating updated software, while the activation process makes the updated software effective. The switching instruction sending unit, upon confirming activation approval, sends a switching instruction to the update target node instructing the user to perform activation processing. The activation approval execution unit performs activation approval when the vehicle is in a rechargeable state capable of charging the vehicle battery.
[0010] By performing activation approval when the vehicle is in a rechargeable state capable of charging the vehicle battery, unlike previous methods that performed activation approval when the IG is disconnected, the power consumption of the vehicle battery can be suppressed, and safe and reliable software updates can be ensured. Attached Figure Description
[0011] The above-mentioned objects, as well as other objects, features, and advantages of this disclosure, become more apparent from the accompanying drawings and the detailed description below. The accompanying drawings are:
[0012] Figure 1 This is a diagram showing the overall structure of one implementation method.
[0013] Figure 2 This is a diagram showing the electrical structure of the CGW.
[0014] Figure 3 This is a diagram showing the electrical structure of the ECU.
[0015] Figure 4 This is the functional block diagram of CGW.
[0016] Figure 5 This is a function block diagram of the activation processing instruction unit.
[0017] Figure 6 This is a functional block diagram of the system's matching, checking, and processing execution unit.
[0018] Figure 7 This is a diagram representing the processing flow (one of them).
[0019] Figure 8 This is a diagram representing the processing flow (Part Two).
[0020] Figure 9 This is a diagram representing the processing flow (Part Three).
[0021] Figure 10This is a diagram representing the processing flow (Part Four).
[0022] Figure 11 This is a diagram showing the processing flow (Part 5).
[0023] Figure 12 It is a flowchart (one of them).
[0024] Figure 13 It is a flowchart (Part Two).
[0025] Figure 14 It is a flowchart (Part Three).
[0026] Figure 15 It is a flowchart (Part Four).
[0027] Figure 16 It is a diagram that roughly represents the process flow (one of them).
[0028] Figure 17 It is a diagram that roughly represents the process flow (Part Two). Detailed Implementation
[0029] Hereinafter, an embodiment will be described with reference to the accompanying drawings. In this embodiment, the subject is an electronic control system for a vehicle equipped with an internal combustion engine. The description is based on a structure where the IG (Inlet Gate) is engaged when the engine is running, providing a rechargeable state for charging the vehicle battery, and disengaged when the engine is stopped, providing a non-rechargeable state for charging the vehicle battery. If a vehicle can switch between the rechargeable state for charging the vehicle battery and the non-rechargeable state, then the subject can also be an electronic control system for an electric vehicle that operates via an electric motor without an engine.
[0030] A vehicle electronic control system is a system capable of updating vehicle control and diagnostic software installed in an electronic control unit (hereinafter referred to as an ECU) via OTA (Over-The-Air). The software includes programs and data used to implement vehicle control and diagnostic functions, and can also be expressed as an application program. In this embodiment, the updating of vehicle control and diagnostic software is described, but it can also be applied to updating map applications and the map data used by those applications, for example.
[0031] like Figure 1As shown, the vehicle electronic control system 1 includes a central device 3 on the communication network 2 side, a vehicle-side system 4 on the vehicle side, and a display terminal 5. The communication network 2 is configured, for example, to include a mobile communication network based on 4G lines, the Internet, WiFi (Wireless Fidelity) (registered trademark), etc.
[0032] The display terminal 5, serving as an HMI (Human Machine Interface), is a terminal capable of receiving user input and displaying various screens. Examples include a user-portable smartphone, tablet, or other mobile terminal 6, or an in-vehicle display 7 installed within the vehicle compartment. If the mobile terminal 6 is within the communication range of the mobile communication network, it can communicate with the central device 3 via the communication network 2. The in-vehicle display 7 can also be a structure connected to the vehicle-side system 4, also possessing navigation functionality. Furthermore, the in-vehicle display 7 can be an in-vehicle display ECU with ECU functionality, and can also control displays to the central display, instrument panel, etc.
[0033] If a user is outside the train carriage but within the communication range of the mobile communication network, they can use the mobile terminal 6 to simultaneously view various screens related to the software update and input operations to complete the software update procedures. If a user is inside the train carriage, they can use the onboard display 7 to simultaneously view various screens related to the software update and input operations to complete the software update procedures. In other words, users can use the mobile terminal 6 and the onboard display 7 separately, both outside and inside the train carriage, to complete software update-related procedures.
[0034] The central device 3, within the vehicle electronic control system 1, encompasses the software update functions of the communication network 2 side, functioning as an OTA (Over-The-Air) center providing OTA services. The central device 3 is configured to include a file server 8, a network server 9, and a management server 10, with each server 8-10 capable of data communication with each other. That is, the central device 3 is configured to include multiple servers with different functions. The central device 3 can also be composed of a single server.
[0035] File server 8 is a server that manages the files of the software distributed from central device 3 to vehicle-side system 4. File server 8 manages update data provided by the software provider (i.e., supplier) distributed from central device 3 to vehicle-side system 4, specification data provided by OEM (Original Equipment Manufacturer), vehicle status obtained from vehicle-side system 4, etc.
[0036] File server 8 can communicate with vehicle-side system 4 via communication network 2, sending activity information and specification data to vehicle-side system 4. Additionally, if file server 8 receives a download request for data packets from vehicle-side system 4, it sends a data packet containing updated data to vehicle-side system 4. The data packet contains a compressed zip file. Alternatively, file server 8 can also send specification data and updated data simultaneously to vehicle-side system 4 by sending a data packet containing both specification data and updated data.
[0037] Web server 9 is a server that manages web page information. Web server 9 sends the web page data it manages based on requests from web browsers on mobile terminals such as mobile terminals 6. Management server 10 is a server that manages the personal information of users registered for software update services, the software update history of each vehicle, and other such information.
[0038] The vehicle-side system 4 includes a vehicle host unit 11. The vehicle host unit 11, within the vehicle electronic control system 1, encompasses the software update functions of the vehicle side and functions as an OTA (Over-The-Air) host. The vehicle host unit 11 includes a DCM (Data Communication Module) 12 and a CGW (Central Gateway) 13.
[0039] DCM12 communicates with the central device 3 via communication network 2, essentially acting as a download processing execution unit. CGW13 functions as a gateway ECU, equivalent to a vehicle electronic control unit. DCM12 and CGW13 are connected via the first bus 14 for data communication. Figure 1 The example shown illustrates a structure where the DCM12 and the vehicle display 7 are connected to the same first bus 14, but it is also possible for the DCM12 and the vehicle display 7 to be connected to different buses. Alternatively, the CGW13 can have a portion or all of the functions of the DCM12, or the DCM12 can have a portion or all of the functions of the CGW13. That is, the functional distribution of the DCM12 and CGW13 in the vehicle host unit 11 can be arbitrarily configured. The vehicle host unit 11 can be composed of two ECUs, one for DCM12 and one for CGW13, or it can be composed of a single integrated ECU having the functions of both DCM12 and CGW13.
[0040] In CGW13, in addition to the first bus 14, there are also second bus 15, third bus 16, fourth bus 17, and fifth bus 18 as buses inside the vehicle. Various ECUs 19 are connected via buses 15 to 17, and the power management ECU 20 is connected via bus 18. ECU 19 is equivalent to a node.
[0041] The second bus 15 is, for example, a multimedia system bus, connected to an ECU 19 that controls the multimedia system. The third bus 16 is, for example, a bus for an ADAS (Advanced Driver-Assistance Systems) system used for driver assistance and autonomous driving, connected to an ECU 19 that controls the ADAS system. The fourth bus 17 is, for example, a drive system bus used for vehicle operation, connected to an ECU 19 that controls the drive system. Alternatively, buses 15-17 may be buses for systems other than the multimedia system bus, ADAS system bus, and drive system bus. Furthermore, the number of buses and the number of ECUs 19 are not limited to the illustrated structure. The power management ECU 20 manages the power supplied to the DCM 12, CGW 13, and various ECUs 19.
[0042] In CGW13, a sixth bus 21 is connected as an external bus. A DLC (Data Link Coupler) connector 22, which allows the tool 23 to function as a service tool, to be detachably connected to it, is connected to the sixth bus 21. The internal buses 14-18 and the external bus 21 are, for example, composed of a CAN (Controller Area Network) bus. CGW13 communicates with DCM12, various ECUs 19, and the tool 23 according to the CAN data communication standard and the diagnostic communication standard (UDS (Unified Diagnosis Services): ISO 14229). Alternatively, DCM12 and CGW13 can also be connected via Ethernet, as can the DLC connector 22 and CGW13.
[0043] CGW13 operates using power supplied from the vehicle battery 24. The vehicle battery 24 can be charged by power supplied from the alternator of the engine when the IG is on. That is, the IG-on state is a rechargeable state in which the vehicle can charge the vehicle battery 24, and the IG-off state is a non-rechargeable state in which the vehicle cannot charge the vehicle battery 24.
[0044] CGW13 sends a data packet download request to the central device 3 via DCM12, provided that certain conditions for downloading data packet data are met. These conditions include: download approval, CGW13's ability to communicate with the central device 3 via DCM12, the DCM12's storage capacity being at least a specified level, and the vehicle battery's remaining capacity being at least a specified level. If CGW13 downloads data packet data from the central device 3 via DCM12, it retrieves updated data from that downloaded data packet data.
[0045] CGW13 instructs the software update target ECU19 to install the acquired update data, provided that the conditions for instructing the installation of update data are met. The conditions for instructing installation include: installation approval being obtained, the vehicle status being in an installable state, the update target ECU19 being in an installable state, the update data being normal data, and the remaining capacity of the vehicle battery being above the specified capacity. If CGW13 instructs the installation of update data, the update target ECU19 executes the installation of the update data.
[0046] If the installation of the updated data in the target ECU 19 is complete, CGW 13 instructs the target ECU 19 to activate, provided that the conditions for valid activation of the installed software are met. The conditions for activation instruction include: activation approval being obtained, the vehicle status being in an activation-enabled state, the target ECU 19 being in an activation-enabled state, and the remaining capacity of the vehicle battery being at least the specified capacity. If activation is instructed from CGW 13, the target ECU 19 performs the activation.
[0047] like Figure 2As shown, the CGW13 includes a microcomputer (hereinafter referred to as a microcomputer) 25, a storage device 26, a data transfer circuit 27, a power supply circuit 28, and a power detection circuit 29 as electrical functional modules. The microcomputer 25 includes a CPU (Central Processing Unit) 25a, a ROM (Read Only Memory) 25b, a RAM (Random Access Memory) 25c, and flash memory 25d. The flash memory 25d contains a secure area from which information cannot be read from outside the CGW13. The microcomputer 25 executes various control programs stored in a non-transferable physical storage medium to perform various processes and control the operation of the CGW13. In this embodiment, a structure in which a microcomputer 25 is mounted on the CGW13 is illustrated, but the number, specifications, and combination of microcomputers mounted on the CGW13 are determined according to the processing power required by the CGW13. That is, if the CGW13 requires relatively high processing power, a relatively high-specification microcomputer is used, or multiple microcomputers are used to achieve distributed or parallel processing.
[0048] Storage device 26 is, for example, eMMC (embedded Multi Media Card) or NorFlash. Data transfer circuit 27 controls data communication with buses 14-18 and 21 according to CAN data communication standards and diagnostic communication standards. Power supply circuit 28 inputs battery power, accessory (hereinafter referred to as ACC) power, and IG power. Power detection circuit 29 detects the voltage values of the battery power, ACC power, and IG power input to power supply circuit 28, compares these detected voltage values with specified voltage thresholds, and outputs the comparison results to microcomputers 25-26. Microcomputers 25-26 determine whether the battery power, ACC power, and IG power supplied from vehicle battery 24 to CGW13 are normal or abnormal based on the comparison results input from power detection circuit 29.
[0049] like Figure 3 As shown, ECU 19 has a microcomputer 30, a data transfer circuit 31, a power supply circuit 32, and a power detection circuit 33 as electrical functional modules. Microcomputer 30 has a CPU 30a, ROM 30b, RAM 30c, and flash memory 30d. Flash memory 30d contains a secure area where information cannot be read from outside the ECU 19. Microcomputer 30 executes various control programs stored in non-transferable physical storage media to perform various processes and control the actions of ECU 19.
[0050] Data transfer circuit 31 controls data communication with buses 15-17 according to the CAN data communication standard. Power supply circuit 32 receives inputs from the battery, ACC, and IG power supplies. Power detection circuit 33 detects the voltage values of the battery, ACC, and IG power supplies input to power supply circuit 32, compares these detected voltage values with specified voltage thresholds, and outputs the comparison result to microcomputer 30. Based on the comparison result input from power detection circuit 27, microcomputer 30 determines whether the battery, ACC, and IG power supplies supplied from vehicle battery 24 to ECU 19 are normal or abnormal. Furthermore, while the loads of the connected components of ECU 19, such as sensors and actuators, differ, their structures are essentially the same.
[0051] Next, the memory structure of ECU19 will be explained. The flash memory 30d installed in ECU19 can be of various types: single-sided memory, pseudo-double-sided memory, double-sided memory, and external memory. Single-sided memory has a structure with flash memory on one side; it lacks the concept of an active side and a non-active side, and the running software cannot be updated within the executing software. ECUs equipped with single-sided memory (hereinafter referred to as single-sided memory ECUs) 19 undergo installation and activation processes with the IG disconnected. Pseudo-double-sided memory has a structure with flash memory on two pseudo-two sides; it has the concept of an active side and a non-active side. Although the non-active side software can be updated within the executing software on the active side, there are limitations in the timing of normal read and write operations. ECUs equipped with pseudo-double-sided memory (hereinafter referred to as pseudo-double-sided memory ECUs) 19 undergo installation and activation processes with the IG disconnected.
[0052] A double-sided memory is essentially a structure with flash memory on both sides. It has an active side and a non-active side, allowing software on the active side to be updated while software on the active side is running. There are no timing constraints for normal read / write operations. An ECU (hereinafter referred to as a double-sided memory ECU) 19 equipped with a double-sided memory can be installed when the I / O gate is on and activated when the I / O gate is off. An external memory has a structure with flash memory on one side and does not have an active side or a non-active side. However, by copying software stored on the flash memory to the external memory, the external memory can be used as a temporary storage area for software. An ECU (hereinafter referred to as an external memory ECU) 19 equipped with an external memory can be installed and activated when the I / O gate is off.
[0053] like Figure 4As shown, the CGW13 has a control unit 34, a downloader 35, an activity information storage unit 36, a vehicle structure information storage unit 37, an IG disconnection before and after update flag storage unit 38, and a prototype mass production flag storage unit 39 as the structure for each function. The control unit 34 has an activation processing instruction unit 40, a system matching check processing execution unit 41, and a rollback processing execution unit 42.
[0054] like Figure 5 As shown, the activation processing instruction unit 40 includes a vehicle status determination unit 40a, an activation approval execution unit 40b, a memory structure determination unit 40c, a copy instruction sending unit 40d, a switch setting instruction sending unit 40e, a vehicle disembarkation condition determination unit 40f, a switch instruction sending unit 40g, and an operation delay request unit 40h. Figure 6 As shown, the system matching check processing execution unit 41 includes a vehicle structure information acquisition unit 41a and a matching determination unit 41b. Each of the units 40-42, 40a-40h, and 41a-41b corresponds to a function executed by the update program. That is, the control unit 34 executes the update program and performs the functions of each of the units 40-42, 40a-40h, and 41a-41b.
[0055] The downloader 35, upon receiving a download execution request from the control unit 34, instructs the DCM 12 to perform download processing. The activity information storage unit 36 stores activity information downloaded from the central device 3 to the CGW 13 via the DCM 12. This activity information includes updated vehicle structure information. The updated vehicle structure information includes the target ID, updated hardware version, and updated software version of the managed object ECU 19, which can be identified. The managed object ECU 19 includes the updated object ECU 19 and non-updated object ECUs 19 that cooperate with the updated object ECU 19.
[0056] The vehicle structure information storage unit 37 stores vehicle structure information obtained from the managed object ECU 19. This vehicle structure information includes information such as the target ID that identifies the managed object ECU 19, the version of the hardware before the update, the version of the software before the update, the version of the hardware after the update, and the version of the software after the update.
[0057] The IG disconnection pre-disconnection update flag storage unit 38 stores the IG disconnection pre-disconnection update flag and the IG disconnection post-disconnection update flag. The IG disconnection pre-disconnection update flag and the IG disconnection post-disconnection update flag are selectively set and stored for each ECU 19. The IG disconnection pre-disconnection update flag is a flag that permits the execution of activation processes under IG connection; for example, it is set for ECU 19 that updates software such as the multimedia system, which does not affect vehicle driving control. The IG disconnection post-disconnection update flag is a flag that prohibits the execution of activation processes under IG connection; for example, it is set for ECU 19 that updates software such as the ADAS system or drive system, which affects vehicle driving control.
[0058] The prototype and mass production mark storage unit 39 stores a prototype mark and a mass production mark. The prototype mark and the mass production mark are selectively set. The prototype mark is set during the prototype manufacturing process before the vehicle equipped with the vehicle electronic control system 1 leaves the factory; it is equivalent to the first mark. The mass production mark is set during mass production after the vehicle equipped with the vehicle electronic control system 1 leaves the factory; it is equivalent to the second mark. When the prototype mark is set, the setting can be changed from the prototype mark to the mass production mark, provided that certification is successful. However, the setting cannot be changed from the mass production mark to the prototype mark.
[0059] The vehicle status determination unit 40a determines the vehicle status based on information such as vehicle speed and driver status monitor information. The activation approval execution unit 40b, when the update process has been completed in the target ECU 19, performs activation approval by asking the user whether to approve the activation process, provided that the vehicle status determination unit 40a determines the vehicle status to be one that does not hinder driving operation. Specifically, the activation approval execution unit 40b, for example, when the vehicle is stationary at 0 km / h and the brakes are engaged, sends an activation approval request to the vehicle display 7, causing the vehicle display 7 to show an activation approval screen where the user can choose whether to approve the activation process, thus asking the user whether to approve the activation process.
[0060] The memory structure determination unit 40c determines the memory structure of the ECU19 to be updated based on the specification data, and determines whether the flash memory 30d mounted on the ECU19 to be updated is a single-sided memory, a pseudo double-sided memory, a double-sided memory, or an external memory.
[0061] If the ECU19 to be updated is an external memory ECU19, the copy instruction sending unit 40d sends a copy instruction to the ECU19 to be updated, instructing the software stored in the memory area to be copied to the external memory.
[0062] The switching setting instruction sending unit 40e will send the switching setting instruction to the update target ECU19 to perform activation processing at the next time the timing indication for switching from IG on to IG off is executed.
[0063] The exit condition determination unit 40f determines whether the exit condition for the user to exit the vehicle has been met. For example, when it is determined that the vehicle speed is "0km / h", the vehicle location is in a parking lot, at home, the parking brake is engaged, and the seat belt is unfastened, the exit condition determination unit 40f predicts that the user has exited the vehicle after performing a switching operation from IG connection to IG disconnection, and determines that the exit condition has been met.
[0064] The switching instruction sending unit 40g sends a switching instruction to the ECU 19 to be updated. Referring to the IG disconnection pre-disconnection update flag storage unit 38 described above, the switching instruction sending unit 40g determines whether the IG disconnection pre-disconnection update flag or the IG disconnection post-disconnection update flag is set for the ECU 19 to be updated. If the IG disconnection pre-disconnection update flag is set for the ECU 19 to be updated, and the update does not affect the vehicle driving control software, and if the disembarkation condition determination unit 40f determines that the disembarkation condition is met, then the switching instruction sending unit 40g sends a switching instruction to the ECU 19 to be updated.
[0065] If the ECU19 to be updated has an IG disconnection update flag set, and the software update does not affect the vehicle driving control, and if the disembarkation condition determination unit 40f determines that the disembarkation condition is met, the operation delay request unit 40h sends an operation delay display request to the vehicle display 7, causing the vehicle display 7 to display an operation delay request screen requesting a delay in the switching operation from IG connection to IG disconnection, thereby providing the user with a delay in the switching operation from IG connection to IG disconnection.
[0066] The vehicle structure information acquisition unit 41a acquires the vehicle structure information before the update and the vehicle structure information after the update from the managed object ECU 19, and stores the acquired vehicle structure information before the update and the vehicle structure information after the update in the aforementioned vehicle structure information storage unit 37.
[0067] The matching determination unit 41b refers to the vehicle structure information storage unit 37 and the activity information storage unit 36, and compares the updated vehicle structure information obtained from the managed object ECU 19 with the updated vehicle structure information included in the activity information downloaded from the central device 3 to determine the matching of the vehicle structure information. If the matching determination unit 41b determines that the two are consistent, the matching of the vehicle structure information is correct; if the two are inconsistent, the matching of the vehicle structure information is incorrect.
[0068] Furthermore, the matching determination unit 41b compares the updated vehicle structure information obtained from the managed object ECU 19 with the vehicle structure information before the update to determine the matching of the vehicle structure information. If the matching determination unit 41b determines that the version of the updated vehicle structure information obtained from the managed object ECU 19 has increased compared to the version of the vehicle structure information before the update, then the matching of the vehicle structure information is determined to be correct; if it determines that it has not increased, then the matching of the vehicle structure information is determined to be incorrect. In addition, an increase in the version of the vehicle structure information means a version upgrade and an increase in the version number.
[0069] If the matching determination unit 41b determines that the vehicle structure information is not matched correctly, the aforementioned switching instruction sending unit 40g will perform a retry process to send the switching instruction to the update target ECU 19 again.
[0070] If the matching determination unit 41b determines that the vehicle structure information is not matched correctly, the rollback execution unit 42 performs a rollback process to revert the software of the updated ECU 19 to its state before the installation process. In this case, the rollback execution unit 42 may perform the rollback process without retrying the process by the switching instruction sending unit 40g, or it may perform the rollback process if the switching instruction sending unit 40g has retried the process but the matching determination unit 41b still determines that the vehicle structure information is not matched correctly. In addition, the rollback execution unit 42 performs the rollback process with reference to the prototype mass production mark storage unit 39, provided that the mass production mark has been set. Furthermore, the rollback execution unit 42 performs the rollback process within a predetermined period from the completion of the activation process in the updated ECU 19, and within the rollback executable period.
[0071] Next, refer to Figures 7 to 17 The function of the above structure will be explained. Additionally, in Figures 7 to 11 In this process, the first ECU 19 to be updated is an ECU with an external memory structure and an update flag set after IG disconnection. The second ECU 19 to be updated is an ECU with a memory structure other than external memory and an update flag set after IG disconnection. The third ECU 19 to be updated is an ECU with an external memory structure and an update flag set before IG disconnection. The fourth ECU 19 to be updated is an ECU with a memory structure other than external memory and an update flag set before IG disconnection.
[0072] In CGW13, for example, if an activation approval request is generated in the updated target ECU19 by completing the installation process and a request is sent to the vehicle display 7, the control unit 34 checks the vehicle status (A1) and determines whether it is a vehicle status that does not hinder driving operation (A2).
[0073] For example, when the vehicle speed is "0 km / h" and the brakes are engaged, and the vehicle is determined to be in a state that does not hinder driving operation (A2: "Yes"), the control unit 34 sends an activation approval request to the vehicle display 7 (A3, t1, equivalent to the activation approval execution step), and waits to receive the approval result from the vehicle display 7 (A4). Engaging brakes also include, for example, the state where the gear shift position is in P gear. If the vehicle display 7 receives the activation approval request from CGW13, it displays an activation approval screen (B1) allowing the user to choose whether to approve the activation process, asking the user whether to approve the activation process. When the user approves the activation, the vehicle display 7 sends the approval as an approval result to CGW13 (t2). Furthermore, in this embodiment, regardless of the memory structure of the ECU 19 being updated, the activation approval request and approval confirmation are performed when the IG is on. That is, even if the ECU 19 being updated is an external memory ECU or a single-sided memory ECU, the activation approval request and approval confirmation are performed when the IG is on.
[0074] If the control unit 34 determines that it has received an approval result from the vehicle display 7 (A4: "Yes"), it determines whether the approval result is an approval license (A5). If it determines that the approval result is an approval license (A5: "Yes"), it determines the memory structure of the ECU 19 to be updated based on the specification data (A6). The control unit 34 determines whether the ECU 19 to be updated contains an external memory ECU 19 (A7).
[0075] If the control unit 34 determines that the update target ECU 19 includes an external memory ECU 19 (A7: "Yes"), it sends a copy instruction to the update target ECU 19 (which is the external memory ECU 19) to perform the copying process of the software stored in the memory area to the external memory ECU 19 (A8, t3), and waits for the receipt of an ACK from the update target ECU 19 (which is the external memory ECU 19) (A9). If the update target ECU 19 (which is the external memory ECU 19) receives the copy instruction from CGW13, it performs the copying process of the software stored in the memory area to the external memory (C1, E1) and returns an ACK to CGW13 (t4).
[0076] If the control unit 34 determines that it has received an ACK (A9: "Yes") from the update target ECU 19, which is an external memory ECU 19, it refers to the IG disconnection before and after update flag storage unit 38 (A10) to determine whether there is an update target ECU 19 with an IG disconnection after update flag set (A11). If the control unit 34 determines that there is an update target ECU 19 with an IG disconnection after update flag set (A11: "Yes"), it sends a switching setting instruction to the update target ECU 19 with the IG disconnection after update flag set to perform activation processing at the next timing indication of switching from IG on to IG off (A12, t5), and waits for the reception of the ACK from the update target ECU 19 with the IG disconnection after update flag set (A13). If the update target ECU 19 with the IG disconnection after update flag set receives the switching setting instruction from CGW13, it performs the switching setting to perform activation processing at the next timing indication of switching from IG on to IG off (C2, D1), and returns the ACK to CGW13 (t6).
[0077] If the control unit 34 determines that it has received an ACK (A13: "Yes") from an update target ECU 19 with an IG disconnection update flag set, it then determines whether there is an update target ECU 19 with an IG disconnection pre-update flag set (A14). If the control unit 34 determines that there is an update target ECU 19 with an IG disconnection pre-update flag set (A14: "Yes"), it then determines that the exit condition for the user to exit the vehicle is met (A15).
[0078] If the control unit 34 determines that the disembarkation condition is met (A15: "Yes"), it sends an operation delay display request to the vehicle display 7 (A16, t7) and waits for the reception of the ACK from the vehicle display 7 (A17). If the vehicle display 7 receives the operation delay display request from the CGW13, it displays the operation delay request screen (B2) and returns the ACK to the CGW13 (t8).
[0079] If the control unit 34 determines that it has received an ACK from the vehicle display 7 (A17: "Yes"), it sends a switching instruction to the update target ECU 19 with the IG disconnection update flag set (A18, t9), and waits for the reception of the ACK from the update target ECU 19 with the IG disconnection update flag set (A19). If the update target ECU 19 with the IG disconnection update flag set receives a switching instruction from CGW13, it performs activation processing (E2, F1) and sends an ACK to CGW13 (t10). If the control unit 34 determines that it has received an ACK from the update target ECU 19 with the IG disconnection update flag set (A19: "Yes"), it waits for the switch from IG connection to IG disconnection (A20).
[0080] Here, if a switching operation from IG on to IG off is performed, the ECU19, which is set with the IG off update flag, has previously received the switching setting instruction from CGW13 as described above. Therefore, the activation process (C3, D2) is performed based on the switching from IG on to IG off.
[0081] If the control unit 34 determines that the switch is from IG on to IG off (A20: "Yes"), it sends a vehicle structure information request to the management object ECU 19 (A21), determines whether the updated vehicle structure information has been received from the management object ECU 19 (A22), and determines whether a certain amount of time has passed since the switch from IG on to IG off (A23).
[0082] If, before a certain period of time has elapsed since the switch from IG connection to IG disconnection, the control unit 34 determines that updated vehicle structure information has been received from the management object ECU 19 (A22: "Yes"), it compares the updated vehicle structure information received from the management object ECU 19 with the updated vehicle structure information contained in the activity information (A24) to determine the matching of the vehicle structure information (A25). If the two match and the vehicle structure information is determined to be correctly matched (A25: "Yes"), the control unit 34 refers to the prototype mass production mark storage unit 39 (A26) to determine whether a mass production mark has been set (A27).
[0083] If it is determined that a mass production flag is set (A27: "Yes"), the control unit 34 compares the updated vehicle structure information received from the managed object ECU 19 with the vehicle structure information before the update (A28) and determines the matching of the vehicle structure information (A29). If the version of the updated vehicle structure information received from the managed object ECU 19 is higher than the version of the vehicle structure information before the update, and it is determined that the vehicle structure information matches correctly (A29: "Yes"), the control unit 34 sends a sleep instruction to the managed object ECU 19 (A30, t13). If the managed object ECU 19 receives the sleep instruction from CGW13, it moves from the awake state to the sleep state (C4, D3, E3, F2).
[0084] On the other hand, if the control unit 34 determines, before receiving the updated vehicle structure information from the management object ECU 19, that a certain amount of time has elapsed since the switch from IG connection to IG disconnection (A23: "Yes"), or that the updated vehicle structure information received from the management object ECU 19 is inconsistent with the updated vehicle structure information contained in the activity information, or that the version of the updated vehicle structure information received from the management object ECU 19 has not increased from the version of the vehicle structure information before the update, and determines that the vehicle structure information is incorrectly matched (A25: "No", or A29: "No"), then it performs a retry process to resend the switch instruction to the update object ECU 19 (A31).
[0085] If the control unit 34 performs a retry process, it compares the updated vehicle structure information received from the managed object ECU 19 with the updated vehicle structure information contained in the activity information, as described above, and further compares it with the vehicle structure information before the update to determine the matching of the vehicle structure information again (A32). If the control unit 34 determines that the matching of the vehicle structure information is correct (A32: "Yes"), it sends a sleep instruction to the managed object ECU 19 (A30, t13).
[0086] On the other hand, if the control unit 34 determines that the vehicle structure information is incorrectly matched (A32: "No"), and determines that the number of retry operations has exceeded the predetermined number, it determines whether it is within a predetermined period since the completion of the activation process, and whether it is within the executable period for rollback (A33). If the control unit 34 determines that it is within a predetermined period since the completion of the activation process, and determines that it is within the executable period for rollback (A33: "Yes"), it executes the rollback process (A34).
[0087] If the control unit 34 performs a rollback process, it determines whether the rollback process was completed successfully (A35). If it determines that the rollback process was completed successfully (A35: "Yes"), it sends a sleep instruction to the managed object ECU 19 (A30, t13). On the other hand, if the control unit 34 determines that the rollback process was not completed successfully (A35: "No"), it performs error processing (A36) and sends a sleep instruction to the managed object ECU 19 (A30, t13).
[0088] Thus, in this embodiment, with Figure 16 This differs from previous methods that involved activation approval after IG disconnection, as shown in the example. Figure 17 As shown, by performing activation approval before the IG is disconnected, activation approval can be performed while the IG is on, which is capable of charging the vehicle battery 24, thereby suppressing the power consumption of the vehicle battery 24.
[0089] As explained above, the following effects can be achieved according to the implementation method.
[0090] In CGW13, activation approval is performed when the vehicle is in an IG-connected state, capable of charging the vehicle battery 24. Unlike previous methods that performed activation approval when the IG was disconnected, activating approval when the IG is connected suppresses power consumption of the vehicle battery 24 and ensures safe and reliable software updates.
[0091] In CGW13, a switching setting instruction is sent to the target ECU19 while the IG is on. This allows for rapid activation processing in the target ECU19 by using a switch from IG on to IG off as a trigger.
[0092] In CGW13, activation approval is performed while the IG is engaged, for example, based on the condition that the vehicle is in a stationary or otherwise non-obstructive driving state. This allows users to perform activation approval in a safe and reliable environment.
[0093] In CGW13, if the update target ECU19 includes an external memory ECU19, a copy instruction is sent to the update target ECU19, which is the external memory ECU19, while the IG is on. By performing the copying process from the memory area of the external memory ECU19 to the external memory while the IG is on, the power consumption of the vehicle battery 24 can be further suppressed.
[0094] In CGW13, when the update target ECU19 has an IG disconnection pre-update flag set, and the software update does not affect vehicle driving control, if the vehicle exit condition is met, an operation delay display request is sent to the vehicle display 7. The vehicle display 7 then displays an operation delay request screen requesting a delay in the IG connection to IG disconnection switching operation, thereby prompting the user to delay the IG connection to IG disconnection switching operation. By requesting a delay in the IG connection to IG disconnection switching operation, the user is encouraged to delay the IG connection to IG disconnection switching operation. Furthermore, if the vehicle exit condition is met, a switching instruction is sent to the update target node, thereby enabling appropriate activation processing in the update target ECU19 with the IG disconnection pre-update flag set.
[0095] In CGW13, updated vehicle structure information is obtained from the managed object ECU19. This updated vehicle structure information is then compared with the updated vehicle structure information contained in the activity information to determine the matching accuracy. This process effectively verifies whether the software update was completed successfully.
[0096] In CGW13, updated vehicle structure information is obtained from the managed object ECU19. This updated information is then compared with the original information to determine the compatibility of the vehicle structure information. This allows for more appropriate verification of whether the software update was completed successfully.
[0097] In CGW13, if the vehicle structure information is determined to be incorrectly matched, a retry process is initiated, resending the switching instruction to the updated ECU19. This retry process allows for appropriate handling in cases where the software update fails to complete successfully.
[0098] In CGW13, if the vehicle structure information is determined to be incorrectly matched, a rollback process is performed to revert the software of the updated ECU19 to its state before installation. In cases where the software update fails to complete properly, a retry process can be implemented to address the issue appropriately.
[0099] In CGW13, a rollback is performed after a retry. By retrying instead of immediately reverting the software of the updated ECU19 to its pre-installation state, the likelihood of a successful software update is increased.
[0100] In CGW13, rollback is performed within a specified period following the completion of activation processing in the updated object ECU19. By limiting the period during which rollback can be performed, it is possible to prevent the software from being written back to an older version through unauthorized access.
[0101] In CGW13, the specified period for determining whether to perform a rollback is dynamically determined. The limitation on the period during which a rollback can be performed can be arbitrarily changed. For example, if the software update aims to improve functionality and upgrade the version, the specified period is relatively long; if the software update aims to fix bugs, the specified period is relatively short, and so on.
[0102] In CGW13, rollback is performed only when a mass production flag is set. By preventing rollback when a trial production flag is set, it is possible to update the software to an older version only during trial production.
[0103] In CGW13, it is possible to change the setting of the prototype mark to the production mark, provided that certification is successful. This ensures the security of such changes.
[0104] In CGW13, it is not possible to change the setting from mass production flag to trial production flag. By making it impossible to change the setting from mass production flag to trial production flag, the complexity of version management can be avoided in advance.
[0105] While this disclosure has been described with reference to embodiments, it should be understood that it is not limited to those embodiments or structures. This disclosure also includes various modifications and variations within the same scope. Furthermore, various combinations and methods, even those containing only one element, more or fewer elements, are also included within the scope and spirit of this disclosure.
[0106] This example illustrates a case where the update target ECU 19 is an external memory ECU 19, and a copy instruction is sent to that update target ECU 19, which is an external memory ECU 19. However, sending a copy instruction is not mandatory, and it is also possible not to send a copy instruction. That is, it is not necessary to perform the copying process from the memory area of the external memory ECU 19 to the external memory before the IG is disconnected.
[0107] The example shown is a structure where the IG disconnection pre-update flag and the IG disconnection post-update flag are stored in the IG disconnection pre-and-post-update flag storage unit 38. However, information equivalent to the IG disconnection pre-and-post-update flags can also be stored in the specification data. In this case, the control unit 34 can also refer to the specification data to determine whether to allow or prohibit the execution of activation processing before IG disconnection. Alternatively, the IG disconnection pre-and-post-update flags can be omitted, and a switching setting instruction can be sent to all update target ECUs 19.
[0108] The retry process is explained, but it can also be omitted. That is, if the control unit 34 determines that a certain amount of time has elapsed since the switch from IG on to IG off before receiving the updated vehicle structure information from the management object ECU 19 (A22: "Yes"), or if it determines that the vehicle structure information is not matched correctly (A24: "No", A28: "No"), it may not perform the retry process of sending the switch instruction to the update object ECU 19 again, but instead perform the rollback process as a condition that the rollback is within the executable period (A33).
[0109] The control unit and its mode described herein may also be implemented by a dedicated computer consisting of a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the control unit and its mode described herein may be implemented by a dedicated computer consisting of a processor composed of one or more dedicated hardware logic circuits. Alternatively, the control unit and its mode described herein may be implemented by one or more dedicated computers consisting of a combination of a processor and memory programmed to perform one or more functions and a processor composed of one or more hardware logic circuits. Furthermore, the computer program may also be stored as instructions executable by a computer on a computer-readable non-transferable tangible recording medium.
Claims
1. A vehicle electronic control device, which is mounted on a vehicle capable of switching between a rechargeable state (capable of charging a vehicle battery) and a non-rechargeable state (capable of charging a vehicle battery), and operates using power supplied from the vehicle battery as operating power, wherein... have: The activation approval execution unit completes the installation process in the update object node and then asks the user whether to approve the activation process. The installation process is the process of writing update data and generating the updated software, and the activation process is the process of making the updated software effective. The switching instruction sending unit, provided that the activation approval permission has been determined, can send a switching instruction for executing the activation process in the rechargeable state to the update object node that is executing the activation process in the rechargeable state. as well as The switching setting instruction sending unit can, in the rechargeable state, send a switching setting instruction to the update target node that performs the activation process in the non-rechargeable state, provided that activation approval has been confirmed. The activation approval execution unit performs the activation approval in the rechargeable state.
2. The vehicle electronic control device according to claim 1, wherein, The aforementioned switching setting instruction sending unit sends the aforementioned switching setting instruction, which is used to cause the aforementioned activation process to be executed the next time it switches from the aforementioned rechargeable state to the aforementioned non-rechargeable state, to the aforementioned update target node.
3. The vehicle electronic control device according to claim 1, wherein, The system includes a vehicle status determination unit, which determines the vehicle status. The activation approval execution unit performs the activation approval in the above-mentioned rechargeable state, provided that the vehicle is determined to be in a state that does not impede driving operation.
4. The vehicle electronic control device according to claim 1, wherein, have: The memory structure determination unit determines the memory structure of the aforementioned update target node; and The copy instruction sending unit sends a copy instruction to the updated target node when the updated target node is a node with a memory structure having external memory. The copy instruction is an instruction to perform a copying process from the memory area to the external memory. The copy instruction sending unit sends the copy instruction to the update target node in the rechargeable state.
5. The vehicle electronic control device according to claim 1, wherein, have: The disembarkation condition determination unit determines whether the disembarkation condition for the user has been met; and The operation delay request unit requests a delay in the switching operation from the rechargeable state to the non-rechargeable state of the vehicle battery. When the updated target node is a node whose update does not affect the vehicle driving control, and the above-mentioned disembarkation condition is determined to be met, the above-mentioned operation delay request unit requests a delay in the above-mentioned switching operation.
6. The vehicle electronic control device according to claim 5, wherein, When the update target node is a node whose software update does not affect vehicle driving control, the switching instruction sending unit sends the switching instruction to the update target node when the above-mentioned disembarkation condition is determined to be met.
7. The electronic control device for a vehicle according to any one of claims 1 to 6, wherein, have: The vehicle structure information acquisition unit acquires the updated vehicle structure information from the management object node that contains the aforementioned updated object node; as well as The matching determination unit compares the updated vehicle structure information with the updated vehicle structure information contained in the activity information to determine the matching of the vehicle structure information.
8. The electronic control device for a vehicle according to claim 7, wherein, The aforementioned vehicle structure information acquisition unit obtains the vehicle structure information before the update from the aforementioned management object node. The matching determination unit compares the updated vehicle structure information with the vehicle structure information before the update to determine the matching of the vehicle structure information.
9. The electronic control device for a vehicle according to claim 7, wherein, If the matching determination unit determines that the vehicle structure information is not matched correctly, the switching instruction sending unit performs a retry process to resend the switching instruction to the update target node.
10. The electronic control device for a vehicle according to claim 7, wherein, It includes a rollback execution unit that performs rollback processing to restore the software of the updated object node to its state before the installation process. If the matching determination unit determines that the vehicle structure information is not matched correctly, the rollback execution unit performs the rollback process.
11. The electronic control device for a vehicle according to claim 10, wherein, If the matching determination unit determines that the vehicle structure information is not matched correctly and the switching instruction sending unit performs a retry process to resend the switching instruction to the update target node, and the matching determination unit determines again that the vehicle structure information is not matched correctly, the rollback execution unit performs the rollback process.
12. The electronic control device for a vehicle according to claim 10, wherein, The rollback execution unit performs the rollback process within a specified period starting from the completion of the activation process in the updated object node.
13. The electronic control device for a vehicle according to claim 12, wherein, The aforementioned rollback process execution department dynamically determines the specified period.
14. The electronic control device for a vehicle according to claim 10, wherein, It is possible to choose one of the first and second markers. The rollback execution unit performs the rollback process when the second flag is set.
15. The electronic control device for a vehicle according to claim 14, wherein, It is possible to change the setting of the first mark to the second mark, provided that the authentication is successful.
16. The electronic control device for a vehicle according to claim 14, wherein, It is not possible to change the setting from the second flag to the first flag.
17. A computer-readable non-transitory storage medium storing an update program, wherein, The control unit of a vehicle electronic control device, which is equipped with a vehicle capable of switching between a rechargeable state (where the vehicle battery can be charged) and a non-rechargeable state (where the battery cannot be charged), operates using power supplied from the vehicle battery as operating power. The activation approval execution step involves completing the installation process in the updated object node and, while in the aforementioned rechargeable state, asking the user whether to approve the activation process. The installation process involves writing update data and generating the updated software, while the activation process is the process of making the updated software effective. The step of sending a switching instruction to the update object node that performs the activation process in the rechargeable state, provided that activation approval has been confirmed; and the step of sending the activation process in the rechargeable state to the updated object node that performs the activation process in the rechargeable state. The step of sending a switching setting instruction to the update object node that performs the activation process in the non-rechargeable state, provided that activation approval has been confirmed, is to enable the activation process to be performed in the non-rechargeable state.
Citation Information
Patent Citations
Vehicle electronic control system, vehicle master device, and data storage surface information transmission control method and data storage surface information transmission control program
JP2020027627A
Liquid discharge device, imprint device, and article manufacturing method
JP2021086936A
Vehicle master device, installation instruction determination method, and installation instruction determination program
CN112567334A
Program update device
WO2011161778A1
