The main architecture includes OTA master control nodes (TBOX and GW) and refreshed ECU. TBOX is mainly responsible for the safe and reliable connection channel between the external and cloud platforms, which integrates security modules such as PKI authentication and identity authentication; GW is mainly responsible for the connection channel to the internal network and the integrated diagnosis refresh machine function. Refresh the ECU According to the size of the software package and the theoretical refresh time (for example, no more than 20 minutes), an Ethernet interface design is added to the CAN bus topology, and the DoIP protocol is used for ECU diagnostic refresh.
Before the OTA refresh, the ECU software upgrade package is delivered by the cloud platform to the OTA main control node of the car for storage, and the file storage module is responsible for the storage of the vehicle software upgrade package and the management and control of the backup package. The upgrade management module is mainly responsible for the refresh strategy control of the refresh machine. OTA refresh needs to design multiple redundant refresh strategies, that is, after the OTA background initiates an upgrade task, the refresh machine of the OTA master control node in the same vehicle usually performs multiple executions on the same ECU. Refresh attempt requests, reduce occasional failure factors, and improve OTA refresh success rate.