OTA refresh currently mainly implements ECU refresh condition checks, data transmission during the refresh process, and reset and restart after refresh through diagnostic communication. During the refresh process, the refreshed ECU cannot guarantee the normal operation of the application due to BOOT or other reasons (non-sensing refresh In addition to other methods), it is necessary to carry out ECU fault shielding design in advance to avoid some fault codes on the vehicle caused by the refresh process, which will mislead the subsequent remote fault diagnosis and statistical analysis. During the OTA refresh process, diagnostic fault shielding can be implemented using the 0x85 (Control DTC Setting) service in the UDS diagnostic protocol. One of the difficulties to be solved in OTA remote fault diagnosis is the conflict with local fault diagnosis. It is difficult for the OTA cloud platform to identify local diagnostic equipment. Therefore, it is necessary to integrate the arbitration judgment logic of remote diagnosis and local diagnosis at the vehicle end. The central gateway (GW) is responsible for arbitration and coordination. During the OTA refresh process, the gateway shields the local fault diagnosis routing and forwarding function; similarly, when there is a local diagnostic device, the gateway shields the remote fault diagnosis routing and forwarding function, and the shielding is only in the current ignition cycle. efficient.