OTA upgrade fault debugging and tracking method, device, vehicle gateway and new energy vehicle

Abstract

The present application relates to the field of new energy vehicles, and provides an OTA upgrade fault debugging and tracking method, device, vehicle gateway and new energy vehicle. The method includes: if it is determined that the fault debugging and tracking command code is a valid command code, and it is determined that the OBD external transmission channel needs to be opened, then the action of opening the OBD external transmission channel is executed, and the number of opening executions is recorded; if it is determined that the OBD external transmission channel is opened successfully, then the online OTA upgrade process data or simulated OTA upgrade process data is sent to the debugging and tracking end through the OBD external transmission channel, so that the debugging and tracking end can check the OTA upgrade status fault based on the online OTA upgrade process data, or check the OTA upgrade process fault based on the simulated OTA upgrade process data. The present application can monitor and troubleshoot fault problems in the OTA upgrade flashing process in real time, with high troubleshooting efficiency and good result reliability, and can realize the verification of the OTA upgrade process.

Description

Technical Field

[0001] The present application relates to the field of new energy vehicles, and in particular to an OTA upgrade fault debugging and tracking method, device, vehicle gateway and new energy vehicle. Background Art

[0002] The OTA (Over the Air Technology) upgrade process of a car usually involves communication data transmission between the car cloud and the car, as well as the interaction of the upgrade process of the ECU components in the car and troubleshooting of whether the results are correct.

[0003] In the related art, during the OTA upgrade flashing process, the OTA upgrade flashing fault problem is troubleshooted by printing functions. However, this method cannot timely troubleshoot the fault problem during the OTA upgrade flashing process, and the troubleshooting efficiency is very low, and the reliability of the troubleshooting results is poor. At the same time, it is also impossible to verify the OTA upgrade process when the hardware development of the ECU component is completed but the software version has not yet been developed. Summary of the invention

[0004] In view of this, the embodiments of the present application provide an OTA upgrade fault debugging and tracking method, device, vehicle gateway and new energy vehicle to solve the problem that the prior art is unable to timely detect faults in the OTA upgrade flashing process, and the fault detection efficiency is very low, and the reliability of the fault detection results is poor; at the same time, it is also impossible to verify the OTA upgrade process when the hardware development of the ECU component is completed but the software version has not yet been developed.

[0005] A first aspect of an embodiment of the present application provides an OTA upgrade fault debugging and tracing method, including:

[0006] Upgrade the agent:

[0007] Receive a simulated OTA upgrade message transmitted by the debugging and tracking end through the first inward transmission channel, or an online OTA upgrade message transmitted by the cloud through the second inward transmission channel;

[0008] Extract the fault debugging tracing type and the fault debugging tracing command code from the online OTA upgrade message or the simulated OTA upgrade message;

[0009] If the fault debugging and tracing command code is determined to be a valid command code based on the fault debugging and tracing type, the fault debugging and tracing mode is entered, and the OBD sending port status is read;

[0010] If it is determined that the OBD outbound transmission channel needs to be opened based on the fault debugging tracking command code and the OBD sending port status, the action of opening the OBD outbound transmission channel is executed, and the number of opening executions is recorded;

[0011] If it is determined that the OBD external transmission channel is opened successfully, the online OTA upgrade process data or the simulated OTA upgrade process data is sent to the debugging and tracking end through the OBD external transmission channel, so that the debugging and tracking end can troubleshoot the OTA upgrade status failure based on the online OTA upgrade process data, or troubleshoot the OTA upgrade process failure based on the simulated OTA upgrade process data.

[0012] A second aspect of an embodiment of the present application provides an OTA upgrade fault debugging and tracking device, including:

[0013] A receiving module is configured to receive a simulated OTA upgrade message transmitted by the debugging and tracing terminal through the first inward transmission channel, or an online OTA upgrade message transmitted by the cloud through the second inward transmission channel;

[0014] An extraction module is configured to extract a fault debugging tracing type and a fault debugging tracing command code from an online OTA upgrade message or a simulated OTA upgrade message;

[0015] The reading module is configured to read the OBD sending port state if it is determined that the fault debugging and tracing command code is a valid command code based on the fault debugging and tracing type;

[0016] The channel opening module is configured to execute the action of opening the OBD outward transmission channel if it is determined that the OBD outward transmission channel needs to be opened based on the fault debugging tracking command code and the OBD sending port status, and record the number of opening executions;

[0017] The first data sending module is configured to send online OTA upgrade process data or simulated OTA upgrade process data to the debugging and tracking end through the OBD external transmission channel if it is determined that the OBD external transmission channel is successfully opened, so that the debugging and tracking end can check the OTA upgrade status failure based on the online OTA upgrade process data, or check the OTA upgrade process failure based on the simulated OTA upgrade process data.

[0018] In a third aspect of an embodiment of the present application, a whole vehicle gateway is provided, the whole vehicle gateway includes an upgrade agent terminal; the upgrade agent terminal includes the OTA upgrade fault debugging and tracking device of the second aspect.

[0019] A fourth aspect of an embodiment of the present application provides a new energy vehicle, which includes the vehicle gateway of the third aspect.

[0020] According to a fifth aspect of an embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0021] In a sixth aspect of an embodiment of the present application, a readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0022] Compared with the prior art, the beneficial effects of the embodiments of the present application include at least the following: the technical solution of the embodiments of the present application can be applied to the upgrade agent end, receiving the simulated OTA upgrade message transmitted by the debug tracking end through the first inward transmission channel, or receiving the online OTA upgrade message transmitted by the cloud through the second inward transmission channel; then extracting the fault debug tracking type and the fault debug tracking command code from the online OTA upgrade message or the simulated OTA upgrade message, and then determining whether to open the OBD outward transmission channel according to the fault debug tracking command code and the OBD sending port status; after successfully opening the OBD outward transmission channel, sending the online OTA upgrade process to the debug tracking end through the OBD outward transmission channel Data or simulated OTA upgrade process data, so that the debugging and tracking end can collect the process data of the OTA upgrade flashing process in real time through the OBD external transmission channel, so as to timely troubleshoot the fault problems in the OTA upgrade flashing process, and the troubleshooting efficiency is high and the reliability of the troubleshooting results is high; and, in the case that the hardware development of the ECU is completed but the software version has not been developed, the debugging and tracking end can also collect the simulated OTA upgrade process data in real time through the OBD external transmission channel, so as to realize the verification of the OTA upgrade process, provide reliable verification result support for the software version development of the ECU, and help improve the efficiency of the software version development of the ECU. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0024] Figure 1 is a schematic diagram of an application scenario of an embodiment of the present application;

[0025] Figure 2 It is a flowchart of an OTA upgrade fault debugging and tracking method provided by an embodiment of the present application;

[0026] Figure 3 It is a schematic diagram of the message format of the first transmission message in the OTA upgrade fault debugging and tracing method provided in an embodiment of the present application;

[0027] Figure 4It is a message format diagram of the second transmission message in the OTA upgrade fault debugging and tracing method provided in an embodiment of the present application;

[0028] Figure 5 It is a flow chart of a vehicle gateway opening result return transmission channel in the OTA upgrade fault debugging and tracking method provided in an embodiment of the present application;

[0029] Figure 6 It is a schematic diagram of converting the DOIP message format to the CAN message format in the OTA upgrade fault debugging and tracing method provided in an embodiment of the present application;

[0030] Figure 7 It is a schematic diagram of converting the CAN message format to the DOIP message format in the OTA upgrade fault debugging and tracing method provided in an embodiment of the present application;

[0031] Figure 8 It is a schematic diagram of an OTA upgrade fault debugging and tracking device provided in an embodiment of the present application;

[0032] Fig. 9 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0034] An OTA upgrade fault debugging and tracking method, device, vehicle gateway, and new energy vehicle according to an embodiment of the present application will be described in detail below with reference to the accompanying drawings.

[0035] Figure 1 1 is a schematic diagram of an application scenario of an embodiment of the present application. The application scenario may include a debugging and tracking terminal 101, a private network (APN) 102, a cloud (TSP) 103, a vehicle-mounted VBOX (vehicle remote communication module) 104, a vehicle gateway (VGW) 105, and an ECU (electronic control unit) 106.

[0036] The debugging and tracing terminal 101, which may also be called a debugging and testing terminal, may be a diagnostic instrument or a terminal device with a vehicle diagnostic function (eg, a smart phone, a tablet computer, a laptop computer, a desktop computer, etc.).

[0037] The private network (APN) 102 can be understood as an intermediate gateway for the debugging and tracking terminal 101 and the cloud (TSP) 103 to establish a communication connection with the vehicle-mounted VBOX 104 .

[0038] The vehicle-mounted VBOX 104 includes an OTA upgrade main control (UMC) and an external interface; wherein the "OTA upgrade main control" may also be referred to as an "upgrade main control terminal", and the external interface may be a USB interface.

[0039] The vehicle gateway (VGW) 105 includes an OTA upgrade agent (UA), a control domain port 1 (PORT1), a control domain port 2 (PORT2) ... a control domain port n (PORTn), a switch chip (SWITCH) and an OBD (on-board diagnostic system) port. Among them, the control domain port can specifically be a vehicle function domain port, and the vehicle function domain port mainly includes a power domain port, a chassis domain port, a body domain port, a cockpit domain port and an autonomous driving domain port. Each control domain port is responsible for sending and receiving information of the ECU components of the corresponding functional domain (such as relevant information for OTA upgrade flashing). Among them, the "OTA upgrade agent" can also be called an "upgrade agent terminal".

[0040] The ECU (electronic control unit) 106 refers to a target ECU to be upgraded, flashed or tested. The ECU (electronic control unit) 106 may be at least one ECU in any functional domain of the vehicle, or may be at least two ECUs in at least two functional domains of the vehicle.

[0041] The debugging and tracking terminal 101 and the private network (APN) 102 can be connected via a 4G / 5G network; the private network (APN) 102 and the vehicle-mounted VBOX 104 can be connected via a 4G / 5G network; the cloud (TSP) 103 and the private network (APN) 102 can be connected via a 4G / 5G network; the debugging and tracking terminal 101 and the vehicle-mounted VBOX 104 can be connected via a 4G / 5G network; the vehicle-mounted VBOX 104 and the vehicle gateway (VGW) 105 can be connected via a 100M Ethernet (ETH); the vehicle gateway (VGW) 105 can be connected to its subordinate ECU components via a CAN bus; the vehicle gateway (VGW) 105 and the debugging and tracking terminal 101 can be connected via a CAN / ETH bus.

[0042] When the OTA upgrade master (UMC) performs OTA upgrade and flashing on the target ECU, the diagnostic message (0x7xx) sent by the external device (such as the diagnostic instrument) to the vehicle end through the OBD port of the vehicle gateway (VGW) 105 conflicts with the OTA upgrade and flashing message (the flashing message of the ECU supporting the CAN bus is also a diagnostic message) sent by the OTA upgrade master (UMC) to the vehicle gateway (VGW) 105, which will cause message disorder. Therefore, during the OTA upgrade and flashing process, the switch chip (SWITCH) of the vehicle gateway (VGW) 105 will usually close the OBD port and prohibit OBD port communication to avoid OTA upgrade and flashing failure. When the OBD port communication is prohibited, the debugging and tracking end 101 will not be able to collect the OTA upgrade and flashing message data through the OBD port, and can only troubleshoot the fault problems in the OTA upgrade and flashing process by printing functions. This troubleshooting method is very inefficient, and the reliability and real-time performance of the results are poor. At the same time, it is impossible to verify the OTA upgrade process when the hardware development of the ECU is completed but the software version is not yet completed.

[0043] To solve the above technical problems, an embodiment of the present application provides an OTA upgrade fault debugging and tracking method, by adding the definition of OTA debugging and tracking mode (also called fault debugging and tracking mode) in the communication transmission link of the cloud, OTA upgrade master control (UMC), and upgrade agent (UA), and opening the OBD port in this mode, and returning the result of OTA upgrade flashing the target ECU device to the debugging and tracking end in real time through the OBD port, so that the debugging and tracking end can quickly define the problem and troubleshoot the fault; at the same time, in this mode, the OTA upgrade process can be verified when the hardware development of the ECU device is completed but the software version has not been developed, so that R&D personnel can find faults in the upgrade process in time, which helps to improve the software development efficiency of the ECU device.

[0044] Figure 2 It is a flow chart of an OTA upgrade fault debugging and tracing method provided in an embodiment of the present application. Figure 2 The OTA upgrade fault debugging and tracking method can be Figure 1 The upgrade agent (UA) in the vehicle gateway 105 is executed. Figure 2 As shown, the OTA upgrade fault debugging and tracing method may specifically include the following steps:

[0045] Step S201: receiving a simulated OTA upgrade message transmitted from the debugging and tracking terminal through a first inward transmission channel, or an online OTA upgrade message transmitted from the cloud through a second inward transmission channel.

[0046] See also Figure 1The first inward transmission channel is a communication transmission link between an external device (debugging and tracing terminal 101) and the vehicle gateway 105. The communication transmission link can be specifically the debugging and tracing terminal 101→

[0047] Private network (APN) 102 → upgrade master terminal of vehicle VBOX 104 → upgrade agent terminal of vehicle gateway 105; it can also be debugging and tracking terminal 101 → external interface of vehicle VBOX 104 → upgrade agent terminal of vehicle gateway 105; it can also be debugging and tracking terminal 101 → upgrade master terminal of vehicle VBOX 104 →

[0048] The upgrade agent of the vehicle gateway 105.

[0049] The second inward transmission channel is a communication transmission link connecting the cloud 103 to the vehicle gateway 105. The communication transmission link can be specifically cloud (TSP) 103 → private network (APN) 102 → upgrade master terminal of vehicle VBOX 104 → upgrade agent terminal of vehicle gateway 105; it can also be cloud (TSP) 103 → upgrade master terminal of vehicle VBOX 104 → upgrade agent terminal of vehicle gateway 105; it can also be cloud (TSP) 103 → external interface of vehicle VBOX 104 → upgrade agent terminal of vehicle gateway 105.

[0050] A simulated OTA upgrade message refers to a message containing test software versions or test data used to test the OTA upgrade process of an ECU device when the hardware development of the ECU device is completed but the software version has not yet been developed.

[0051] The online OTA upgrade message refers to the message of the online software version used to perform OTA upgrade on the ECU.

[0052] When the hardware development of the ECU is completed but the software version is not, the debugging and tracking terminal 101 can transmit the simulated OTA upgrade message to the vehicle gateway 105 through the first inward transmission channel (for example, the debugging and tracking terminal 101 → the private network (APN) 102 → the upgrade master terminal of the vehicle VBOX 104 → the upgrade agent terminal of the vehicle gateway 105). By adding the access connection of the debugging and tracking terminal 101 → the private network (APN) 102, an OTA test cloud can be constructed to simulate the OTA upgrade process and run the OTA upgrade process for a specified vehicle.

[0053] During the process of OTA upgrade and flashing of the ECU, the cloud 103 can transmit the online OTA upgrade message to the vehicle gateway 105 through the second inward transmission channel.

[0054] Figure 3It is the first transmission message format used for communication and interaction between the debugging and tracing terminal 101 (or the cloud 103 ), the private network (APN) 102 , and the vehicle-mounted VBOX 104 . Figure 4 It is the second transmission message format used for communication and interaction between the vehicle-mounted VBOX 104 and the vehicle gateway 105. The first transmission message is mainly used to transmit message contents such as test scripts and test software versions. The second transmission message is mainly used to transmit message contents such as in-vehicle upgrade flashing and control.

[0055] The message frame of the online OTA upgrade message or the simulated OTA upgrade message in the embodiment of the present application includes an Ethernet header, an IP header, a TCP / UDP header, a protocol version field, a fault debugging and tracing type field, a total data length field, a source address field, a destination address field, a fault debugging and tracing command code and a data field.

[0056] See also Figure 3 , the message frame of the first transmission message includes an Ethernet header (EthHead), an IP header (IpHead), a TCP / UDP header (TCP / UDP Head), an HTTPS header, an "OTA debug type" field, a "data length" field and a data area. Among them, the IP header structure includes: version (4bit), header length (4bit), priority and service type (8bit), total length (16bit), identifier (16bit), flag (3bit), segment offset (13bit), TTL (8bit), protocol number (8bit), header checksum (16bit), source address (32bit), and destination address (32bit). Among them, the protocol number corresponds to the TCP / UDP header, such as "0x06-TCP"; the destination address corresponds to the IP address of the private network (APN).

[0057] Among them, the IP packet header structure is shown in Table 1 below:

[0058]

[0059] See also Figure 4 , the message frame of the second transmission message includes an Ethernet header (EthHead), an IP header (IpHead), a TCP / UDP header (TCP / UDP Head), a "protocol version" field, a "~ protocol version" field, an "OTA debug type" field (i.e., a fault debug tracing type field), a "total data length" field, a "source address" field, a "destination address" field, a command code field (i.e., a fault debug tracing command code) and a data field. Among them, the IP header of the second transmission message has a substantially identical structure to the IP header of the first transmission message, except that the destination address in the IP header structure of the second transmission message is the IP address of the target device.

[0060] Step S202: extracting the fault debugging tracing type and the fault debugging tracing command code from the online OTA upgrade message or the simulated OTA upgrade message.

[0061] Specifically, after receiving the online OTA upgrade message or the simulated OTA upgrade message, the upgrade agent of the vehicle gateway 105 parses the online OTA upgrade message or the simulated OTA upgrade message and locates the Figure 4 The "OTA Debug Type" field in the message frame shown in the figure is used to extract the fault debugging trace type; locate the Figure 4 The command code field in the message frame shown is used to extract the fault debugging and tracing command code.

[0062] Step S203: If the fault debugging and tracing command code is determined to be a valid command code based on the fault debugging and tracing type, the fault debugging and tracing mode is entered, and the OBD sending port status is read.

[0063] The OBD port in the vehicle gateway (VGW) 105 includes a sending port and a receiving port; the sending port refers to the port through which the vehicle gateway (VGW) 105 sends information unidirectionally to an external device (such as the debugging and tracking terminal 101); the receiving port refers to the port through which the vehicle gateway (VGW) 105 receives information unidirectionally from an external device (such as the debugging and tracking terminal 101).

[0064] The OBD sending port status is used to indicate the open / closed status of the sending port of the OBD port.

[0065] Step S204: if it is determined that the OBD outbound transmission channel needs to be opened based on the fault debugging and tracing command code and the OBD sending port status, the action of opening the OBD outbound transmission channel is executed, and the number of times the opening is performed is recorded.

[0066] Step S205, if it is determined that the OBD external transmission channel is opened successfully, the online OTA upgrade process data or the simulated OTA upgrade process data is sent to the debugging and tracking end through the OBD external transmission channel, so that the debugging and tracking end can troubleshoot the OTA upgrade status failure based on the online OTA upgrade process data, or troubleshoot the OTA upgrade process failure based on the simulated OTA upgrade process data.

[0067] OTA upgrade status failure refers to the abnormal state of the vehicle controller during the OTA upgrade flashing process.

[0068] OTA upgrade process failure refers to the failure of the upgrade process involved in the simulated OTA upgrade process. For example, whether there are abnormal situations such as message loss and message error during the simulated upgrade process.

[0069] The technical solution provided in the embodiment of the present application can timely troubleshoot faults in the OTA upgrade flashing process, and has high troubleshooting efficiency and high reliability of troubleshooting results; and, in the case that the hardware development of the ECU component is completed but the software version has not yet been developed, the debugging and tracking end can also collect the simulated OTA upgrade process data in real time through the OBD external transmission channel, thereby realizing the verification of the OTA upgrade process, providing reliable verification result support for the software version development work of the ECU component, and is conducive to improving the efficiency of the software version development work of the ECU.

[0070] In some embodiments, the above OTA upgrade fault debugging and tracing method may further include the following steps:

[0071] If it is determined that the OBD outward transmission channel fails to open, a first backup outward transmission channel or a second backup outward transmission channel is established;

[0072] The online OTA upgrade process data or the simulated OTA upgrade process data is sent to the debugging and tracking end through the first backup external transmission channel or the second backup external transmission channel, so that the debugging and tracking end can troubleshoot OTA upgrade status failures based on the online OTA upgrade process data, or troubleshoot OTA upgrade process failures based on the simulated OTA upgrade process data.

[0073] See also Figure 1 , the first standby outward transmission channel is a communication transmission link that the vehicle gateway 105 switches to connect to the debugging and tracking terminal 101, and the communication transmission link can be specifically the upgrade agent terminal UA of the vehicle gateway 105 → the upgrade master terminal UMC of the vehicle VBOX 104 → the private network (APN) 102 → the debugging and tracking terminal 101. The second standby outward transmission channel is another communication transmission link that the vehicle gateway 105 reversely connects to the debugging and tracking terminal 101, and the communication transmission link can be specifically the upgrade agent terminal UA of the vehicle gateway 105 → the external interface of the vehicle VBOX 104 → the debugging and tracking terminal 101.

[0074] As an example, when the OBD outbound transmission channel fails to open, the vehicle gateway 105 returns the result to the debugging and tracking terminal 101 through the above-mentioned first backup outbound transmission channel. Specifically, the upgrade agent (UA) of the vehicle gateway 105 sends a result feedback instruction to the switch chip (SWITCH); after receiving the result feedback instruction, the switch chip (SWITCH) transmits the result (online OTA upgrade process data or simulated OTA upgrade process data) to the upgrade master terminal (UMC) of the vehicle VBOX 104; the upgrade master terminal (UMC) then transmits the result to the private network (APN) 102; the private network (APN) 102 then transmits the result to the debugging and tracking terminal 101.

[0075] As another example, when the OBD external transmission channel fails to open, the vehicle gateway 105 returns the result to the debugging and tracking terminal 101 through the above-mentioned second backup external transmission channel. Specifically, the upgrade agent (UA) of the vehicle gateway 105 sends a result feedback instruction to the switch chip (SWITCH); after receiving the result feedback instruction, the switch chip (SWITCH) transmits the result (online OTA upgrade process data or simulated OTA upgrade process data) to the external interface of the vehicle VBOX 104; the result is transmitted to the debugging and tracking terminal 101 via the external interface.

[0076] When the OBD external transmission channel fails to open (channel abnormality), the vehicle gateway 105 can return the result to the debugging and tracking terminal 101 through the first backup external transmission channel or the second backup external transmission channel; after the OBD external transmission channel returns to normal, the first backup external transmission channel and the second backup external transmission channel are closed, and the OBD external transmission channel is restored to return the result to the debugging and tracking terminal 101. In this way, the reliability and real-time performance of the results can be guaranteed, greatly improving the efficiency of the debugging and tracking terminal 101 in analyzing problems and troubleshooting.

[0077] It is worth noting that since both the first backup outward transmission channel and the second backup outward transmission channel consume traffic, they are only used as backup channels when the OBD outward transmission channel fails to open, to ensure the real-time and reliability of result transmission, and to ensure the efficiency of debugging and tracking terminal 101 in analyzing and troubleshooting.

[0078] Compared with the first backup outward transmission channel, the second backup outward transmission channel of the embodiment of the present application directly returns the result to the debugging and tracking terminal 101 via the external interface (such as USB interface) on the vehicle-mounted VBOX 104, shortening the communication channel distance between the vehicle gateway 105 and the debugging and tracking terminal 101, reducing traffic consumption and saving communication costs.

[0079] In some embodiments, if it is determined that the OBD outbound transmission channel fails to be opened, then establishing a first backup outbound transmission channel or a second backup outbound transmission channel includes:

[0080] If the number of times the opening is executed is greater than the preset number threshold, it is determined that the opening of the OBD external transmission channel has failed;

[0081] Read the interface parameters of the external interface on the vehicle VBOX;

[0082] If it is determined based on the interface parameters that the external interface is currently in an abnormally closed state, a first standby outward transmission channel is established;

[0083] If it is determined based on the interface parameters that the external interface is currently in a normally enabled state, a second standby outward transmission channel is established.

[0084] The preset number threshold can be flexibly set according to actual conditions, for example, it can be set to 3 times, 5 times, etc.

[0085] Figure 5 It is a flow chart of a vehicle gateway opening result return transmission channel in the OTA upgrade fault debugging and tracing method provided in an embodiment of the present application.

[0086] The result return transmission channel is any one of the OBD outward transmission channel, the first backup outward transmission channel or the second backup outward transmission channel.

[0087] See also Figure 5 , (1) the upgrade agent (UA) of the vehicle gateway (VGW) 105 reads the OBD sending port status; (2) based on the OBD sending port status, it is determined whether the OBD sending port is in an open state; (3) if the OBD sending port is in an open state, it is determined that the OBD outward transmission channel is successfully opened, and the result is returned to the debugging and tracking terminal 101 through the OBD outward transmission channel; (4) if the OBD sending port is in a closed state, the operation of opening the OBD sending port is executed, and the number of opening executions is recorded, and then the process returns to the above step (2); (5) it is determined whether the number of opening executions is greater than a preset number threshold; (6) if the number of opening executions is less than or equal to the number of opening executions, If the number of times the on-board VBOX is opened exceeds the preset number of times, the process returns to the above step (4); (7) if the number of times the on-board VBOX is opened exceeds the preset number of times, the process determines that the opening of the OBD external transmission channel fails, and executes the switching command; (8) reading the interface parameters (such as interface status parameters) of the external interface on the vehicle-mounted VBOX; (9) judging whether the external interface of the vehicle-mounted VBOX is currently in a normally opened state based on the interface parameters; (10) if the external interface of the vehicle-mounted VBOX is currently in a normally opened state, establishing a second standby external transmission channel; (11) if the external interface of the vehicle-mounted VBOX is currently in an abnormally closed state (for example, the interface is damaged, etc.), establishing a first standby external transmission channel.

[0088] In some embodiments, based on the fault debugging and tracing command code and the OBD sending port status, determining that the OBD outbound transmission channel needs to be opened includes:

[0089] Determine whether the fault debugging and tracing command code is a preset sending port opening command code;

[0090] If yes, determine whether the sending port status is closed;

[0091] If so, it is determined that the OBD external transmission channel needs to be opened.

[0092] As an example, a sending port opening command code and a sending port closing command code may be preset. For example, the preset sending port opening command code may be "0x11" and the sending port closing command code may be "0x12".

[0093] After the upgrade agent (UA) of the vehicle gateway 105 extracts the fault debugging and tracking command code from the online OTA upgrade message or the simulated OTA upgrade message, the fault debugging and tracking command code is compared with the preset sending port opening command code. If the fault debugging and tracking command code is consistent with the preset sending port opening command code, it is further determined whether the sending port state is closed. If the sending port state is closed, it is determined that the OBD external transmission channel needs to be opened.

[0094] In some embodiments, sending the online OTA upgrade process data to the debugging and tracking end through the OBD external transmission channel, so that the debugging and tracking end can troubleshoot the OTA upgrade status failure based on the online OTA upgrade process data, including:

[0095] Extract the target address field from the online OTA upgrade message;

[0096] If the target address field is consistent with the local logical address, the OTA upgrade is flashed based on the online OTA upgrade message to obtain the first online OTA upgrade process data;

[0097] The first online OTA upgrade process data is sent to the debugging and tracking end through the OBD external transmission channel, so that the debugging and tracking end can troubleshoot the OTA upgrade status failure based on the first online OTA upgrade process data.

[0098] See also Figure 4 The upgrade agent (UA) of the vehicle gateway 105 is as follows: Figure 4The "destination address" field (i.e., target address field) is extracted from the online OTA upgrade message shown; the target address field is then compared with its own local logical address to see if they are consistent. If they are consistent, the online OTA upgrade message is processed locally without forwarding; the whole vehicle gateway 105 is OTA upgraded and flashed based on the online OTA upgrade message to obtain the first online OTA upgrade process data, which includes the interactive response data of the OTA upgrade flashing process of the whole vehicle gateway 105; then, a result feedback instruction is sent to the switching chip (SWITCH), and after receiving the result feedback instruction, the switching chip (SWITCH) transmits the result (i.e., the first online OTA upgrade process data) to the OBD transmitter, and then the OBD transmitter sends it to the debugging and tracking terminal 101. When the debugging and tracking terminal 101 receives the first online OTA upgrade process data, it analyzes the first online OTA upgrade process data. If the analysis result of the first online OTA upgrade process data is that the flashing is not successful, the debugging and tracking terminal 101 can send a re-flash command to the upgrade agent (UA) of the vehicle gateway 105 via the private network (APN) 102 and the upgrade master control terminal (UMC) of the vehicle VBOX 104. After receiving the re-flash command, the upgrade agent (UA) of the vehicle gateway 105 re-executes the above-mentioned flashing task. If the analysis result of the first online OTA upgrade process data is that the flashing is not successful, the cause of the upgrade flashing failure can be further investigated based on the first online OTA upgrade process data.

[0099] In some embodiments, after the step of extracting the target address field from the online OTA upgrade message, the method further includes:

[0100] If the target address field is inconsistent with the local logical address, the target ECU is determined based on the target address field;

[0101] Transmitting the online OTA upgrade message to the target ECU through the third inward transmission channel, so that the target ECU performs OTA upgrade flashing based on the online OTA upgrade message, and obtaining second online OTA upgrade process data;

[0102] Receiving second online OTA upgrade process data transmitted from the target ECU via the fourth inward transmission channel;

[0103] The second online OTA upgrade process data is transmitted to the debugging and tracking end through the OBD external transmission channel, so that the debugging and tracking end can troubleshoot the OTA upgrade status failure based on the second online OTA upgrade process data.

[0104] The third inward transmission channel is the communication transmission link between the vehicle gateway 105 and the target ECU. Figure 1For example, if the target ECU is ECU 1, then the third inward transmission channel is vehicle gateway 105 (upgrade agent) → switch chip (SWITCH) → PORTn → ECU 1.

[0105] The fourth inward transmission channel is a communication transmission link between the target ECU and the vehicle gateway 105. Figure 1 For example, if the target ECU is ECU 1, then the fourth inward transmission channel is ECU 1→PORTn→switch chip (SWITCH)→vehicle gateway 105 (upgrade agent).

[0106] The process of transmitting the second online OTA upgrade process data to the debugging and tracking end through the OBD external transmission channel is the same as the process of sending the first online OTA upgrade process data to the debugging and tracking end through the OBD external transmission channel, and will not be repeated here.

[0107] In some embodiments, see Figure 6-7 For ECUs that support Ethernet functions, the DOIP protocol is used for OTA upgrade and flashing, and for ECUs that do not support Ethernet functions, the UDS protocol is used for OTA upgrade and flashing. VBOX, VGW, and ECUs that do not support Ethernet communication perform DOIP<-->UDS conversion to be compatible with data communication between DOIP<-->UDS. Among them, the TA logical address field in the DOIP message format corresponds to the request ID in the CAN message format, that is, the request diagnostic ID (0x7xx), and the SA logical address field in the DOIP message format corresponds to the response ID in the CAN message format, that is, the response diagnostic ID (0x7xx).

[0108] See also Figure 1 The following example explains in detail how to construct an OTA test cloud under the OTA test type to simulate the OTA upgrade process:

[0109] 1) The user can use the debugging and tracing terminal 101 to log in for authentication, establish a communication connection with the private network (APN) 102, and then send a test message containing the software test version of the target ECU to the private network (APN) 102 via HTTPS (Hypertext Transfer Protocol Security) (the message format is as follows: Figure 3 shown);

[0110] 2) After receiving the test message, the private network (APN) 102 transmits the test message to the upgrade master control terminal of the vehicle-mounted VBOX 104;

[0111] 3) After receiving the test message, the upgrade control terminal of the vehicle-mounted VBOX 104 parses the test message. If the "OTA debugging type" field in the simulated OTA upgrade message is "0xf001", the message (simulated OTA upgrade message) "02fd F001 00 05 0e 88 07 01 11" is assembled, wherein the field "F001" is the OTA debugging type field (i.e., the fault debugging and tracing type), the field "0005" is the data length field, the field "0e88" is the source logical address of the upgrade control terminal of the vehicle-mounted VBOX, the field "0701" is the logical address of the vehicle gateway (VGW), and the field "11" is the fault debugging and tracing command code (instructing to open the OBD sender), and the simulated OTA upgrade message is sent to the vehicle gateway (VGW).

[0112] 4) The vehicle gateway (VGW) receives the simulated OTA upgrade message ("02fd F001 00 05 0e88 07 0111") and parses it; according to the field "F001" which is the OTA debug type field (i.e., the fault debug tracing type), it determines that the fault debug tracing command code is a valid command code; extracts the source logical address of the OTA UMC, i.e., the field "0e88", and the target address field is "0701", which is consistent with the local logical address, and then processes the simulated OTA upgrade message by itself without forwarding. The fault debug tracing command code is field "11", which means that the sending port status is currently closed, and the operation of opening the OBD sending end needs to be performed. After detecting that the OBD outbound transmission channel is successfully opened, the simulated OTA upgrade process data is sent to the debug tracing end 101 through the OBD outbound transmission channel. During this period, external data messages cannot enter the vehicle gateway (VGW) through the OBD port to avoid affecting the sending and receiving of normal data messages. That is, during this period, the OBD external transmission channel only allows the vehicle gateway (VGW) to send data to external devices.

[0113] 5) After receiving the simulated OTA upgrade process data, the debugging and tracking terminal 101 analyzes the simulated OTA upgrade process data and troubleshoots faults in the simulated OTA upgrade process.

[0114] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present application, which will not be described one by one here.

[0115] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0116] Figure 8 Schematic diagram of an OTA upgrade fault debugging and tracking device provided in an embodiment of the present application. Figure 8As shown, the OTA upgrade fault debugging and tracking device includes:

[0117] The receiving module 801 is configured to receive a simulated OTA upgrade message transmitted by the debugging and tracing terminal through the first inward transmission channel, or an online OTA upgrade message transmitted by the cloud through the second inward transmission channel;

[0118] The extraction module 802 is configured to extract the fault debugging tracing type and the fault debugging tracing command code from the online OTA upgrade message or the simulated OTA upgrade message;

[0119] The reading module 803 is configured to read the OBD sending port state if it is determined that the fault debugging and tracing command code is a valid command code based on the fault debugging and tracing type;

[0120] The channel opening module 804 is configured to execute the action of opening the OBD outward transmission channel if it is determined that the OBD outward transmission channel needs to be opened based on the fault debugging tracking command code and the OBD sending port status, and record the number of opening executions;

[0121] The first data sending module 805 is configured to send online OTA upgrade process data or simulated OTA upgrade process data to the debugging and tracking end through the OBD external transmission channel if it is determined that the OBD external transmission channel is successfully opened, so that the debugging and tracking end can check the OTA upgrade status failure based on the online OTA upgrade process data, or check the OTA upgrade process failure based on the simulated OTA upgrade process data.

[0122] In some embodiments, the above-mentioned OTA upgrade fault debugging and tracking device may further include:

[0123] A channel establishing module, configured to establish a first backup external transmission channel or a second backup external transmission channel if it is determined that the opening of the OBD external transmission channel fails;

[0124] The second data sending module is configured to send the online OTA upgrade process data or the simulated OTA upgrade process data to the debugging and tracking end through the first backup external transmission channel or the second backup external transmission channel, so that the debugging and tracking end can troubleshoot the OTA upgrade status failure based on the online OTA upgrade process data, or troubleshoot the OTA upgrade process failure based on the simulated OTA upgrade process data.

[0125] In some embodiments, the above-mentioned channel establishment module may specifically include:

[0126] A determination unit is configured to determine that the opening of the OBD external transmission channel fails if the number of opening executions is greater than a preset number threshold;

[0127] A parameter reading unit, configured to read interface parameters of an external interface on the vehicle-mounted VBOX;

[0128] A first channel establishing unit is configured to establish a first standby outward transmission channel if it is determined based on the interface parameters that the external interface is currently in an abnormally closed state;

[0129] The second channel establishing unit is configured to establish a second standby external transmission channel if it is determined based on the interface parameters that the external interface is currently in a normally open state.

[0130] In some embodiments, the channel opening module 804 includes a channel opening unit, which is configured to determine the need to open the OBD outward transmission channel based on the fault debugging tracing command code and the OBD sending port status.

[0131] The channel opening unit may specifically include:

[0132] A first judgment component is configured to judge whether the fault debugging and tracing command code is a preset sending port opening command code;

[0133] The second judgment component is configured to judge whether the sending port state is a closed state if yes;

[0134] The channel opening component is configured to determine that if yes, it is necessary to open the OBD external transmission channel.

[0135] In some embodiments, the above-mentioned first data sending module 705 includes a first data sending unit, which is configured to send the online OTA upgrade process data to the debugging and tracking end through the OBD external transmission channel, so that the debugging and tracking end can check the OTA upgrade status failure based on the online OTA upgrade process data.

[0136] The first data sending unit may specifically include:

[0137] A field extraction component is configured to extract a target address field from an online OTA upgrade message;

[0138] The flash component is configured to perform OTA upgrade flashing based on the online OTA upgrade message if the target address field is consistent with the local logical address, and obtain the first online OTA upgrade process data;

[0139] The first transmission component is configured to send the first online OTA upgrade process data to the debugging and tracking end through the OBD external transmission channel, so that the debugging and tracking end can troubleshoot the OTA upgrade status failure based on the first online OTA upgrade process data.

[0140] In some embodiments, the first data sending unit may further include:

[0141] a target ECU determination component configured to determine a target ECU based on the target address field if the target address field is inconsistent with the local logical address;

[0142] The message transmission component is configured to transmit the online OTA upgrade message to the target ECU through the third inward transmission channel, so that the target ECU performs OTA upgrade flashing based on the online OTA upgrade message to obtain second online OTA upgrade process data;

[0143] A receiving component configured to receive second online OTA upgrade process data transmitted by the target ECU through a fourth inward transmission channel;

[0144] The second transmission component is configured to transmit the second online OTA upgrade process data to the debugging and tracking end through the OBD external transmission channel, so that the debugging and tracking end can troubleshoot the OTA upgrade status failure based on the second online OTA upgrade process data.

[0145] In some embodiments, the message frame of the online OTA upgrade message or the simulated OTA upgrade message includes an Ethernet header, an IP header, a TCP / UDP header, a protocol version field, a fault debugging tracing type field, a total data length field, a source address field, a destination address field, a fault debugging tracing command code and a data field.

[0146] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0147] The embodiment of the present application also provides a vehicle gateway, which includes an upgrade agent terminal of the above-mentioned embodiment; the upgrade agent terminal includes: Figure 8 The OTA upgrade failure debugging and tracking device is shown.

[0148] The embodiment of the present application also provides a new energy vehicle, which includes the whole vehicle gateway in the above implementation mode.

[0149] The new energy vehicles in the embodiments of the present application refer to vehicles that use new energy (non-traditional petroleum and diesel energy) and have advanced technology. These vehicles use a new power system that can effectively reduce vehicle emissions, reduce the impact on the environment, and improve energy efficiency. The new energy vehicles in the embodiments of the present application include but are not limited to the following types of vehicles: electric vehicles (EV), pure electric vehicles (BEV), fuel cell electric vehicles (FCEV), plug-in hybrid electric vehicles (PHEV) and hybrid electric vehicles (HEV), etc.

[0150] Fig. 9Schematic diagram of an electronic device 9 provided in an embodiment of the present application. Fig. 9 As shown, the electronic device 9 of this embodiment includes: a processor 901, a memory 902, and a computer program 903 stored in the memory 902 and executable on the processor 901. When the processor 901 executes the computer program 903, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 901 executes the computer program 903, the functions of the modules / units in the above-mentioned device embodiments are implemented.

[0151] The electronic device 9 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 9 may include, but is not limited to, a processor 901 and a memory 902. Those skilled in the art will appreciate that Fig. 9 The electronic device 9 is merely an example and does not limit the electronic device 9 , and may include more or less components than those shown in the figure, or different components.

[0152] The processor 901 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0153] The memory 902 may be an internal storage unit of the electronic device 9, for example, a hard disk or memory of the electronic device 9. The memory 902 may also be an external storage device of the electronic device 9, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 9. The memory 902 may also include both an internal storage unit of the electronic device 9 and an external storage device. The memory 902 is used to store computer programs and other programs and data required by the electronic device.

[0154] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0155] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium (e.g., a computer-readable storage medium). Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, which may be in source code form, object code form, executable file or some intermediate form. Computer-readable storage media may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0156] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for debugging and tracing OTA upgrade faults, characterized in that: include: Upgrade the agent: Receive a simulated OTA upgrade message transmitted by the debugging and tracking end through the first inward transmission channel, or an online OTA upgrade message transmitted by the cloud through the second inward transmission channel; Extracting a fault debugging tracing type and a fault debugging tracing command code from the online OTA upgrade message or the simulated OTA upgrade message; If it is determined that the fault debugging and tracing command code is a valid command code based on the fault debugging and tracing type, then the fault debugging and tracing mode is entered, and the state of the sending port of the on-board diagnostic system is read; If it is determined that the on-board diagnostic system external transmission channel needs to be opened based on the fault debugging and tracking command code and the state of the on-board diagnostic system sending port, an action of opening the on-board diagnostic system external transmission channel is executed, and the number of opening executions is recorded; If it is determined that the on-board diagnostic system external transmission channel is successfully opened, the online OTA upgrade process data or the simulated OTA upgrade process data is sent to the debugging and tracking end through the on-board diagnostic system external transmission channel, so that the debugging and tracking end can troubleshoot the OTA upgrade status failure based on the online OTA upgrade process data, or troubleshoot the OTA upgrade process failure based on the simulated OTA upgrade process data; Based on the fault debugging and tracing command code and the state of the on-board diagnostic system sending port, determining that the on-board diagnostic system outward transmission channel needs to be opened includes: Determining whether the fault debugging and tracing command code is a preset sending port opening command code; If yes, determining whether the sending port state is closed; If so, it is determined that the on-board diagnostic system external transmission channel needs to be opened.

2. The method according to claim 1, characterized in that: The method further comprises: If it is determined that the on-board diagnostic system outward transmission channel fails to open, establishing a first backup outward transmission channel or a second backup outward transmission channel; The online OTA upgrade process data or the simulated OTA upgrade process data is sent to the debugging and tracking end through the first backup external transmission channel or the second backup external transmission channel, so that the debugging and tracking end can troubleshoot OTA upgrade status failures based on the online OTA upgrade process data, or troubleshoot OTA upgrade process failures based on the simulated OTA upgrade process data.

3. The method according to claim 2, characterized in that If it is determined that the on-board diagnostic system external transmission channel fails to be opened, a first backup external transmission channel or a second backup external transmission channel is established, including: If the number of times the opening is executed is greater than a preset number threshold, it is determined that the opening of the external transmission channel of the on-board diagnostic system fails; Read the interface parameters of the external interface on the vehicle remote communication module; If it is determined based on the interface parameters that the external interface is currently in an abnormally closed state, establishing a first standby outward transmission channel; If it is determined based on the interface parameters that the external interface is currently in a normally open state, a second standby outward transmission channel is established.

4. The method according to claim 1, characterized in that: Sending the online OTA upgrade process data to the debugging and tracking end through the external transmission channel of the on-board diagnostic system, so that the debugging and tracking end can troubleshoot the OTA upgrade status failure based on the online OTA upgrade process data, including: Extracting a target address field from the online OTA upgrade message; If the target address field is consistent with the local logical address, OTA upgrade flashing is performed based on the online OTA upgrade message to obtain first online OTA upgrade process data; The first online OTA upgrade process data is sent to the debugging and tracking end through the external transmission channel of the on-board diagnostic system, so that the debugging and tracking end can troubleshoot OTA upgrade status failure based on the first online OTA upgrade process data.

5. The method according to claim 4, characterized in that After extracting the target address field from the online OTA upgrade message, the method further includes: If the target address field is inconsistent with the local logical address, determining a target electronic control unit based on the target address field; Transmitting the online OTA upgrade message to the target electronic control unit through a third inward transmission channel, so that the target electronic control unit performs an OTA upgrade flash based on the online OTA upgrade message to obtain second online OTA upgrade process data; Receiving the second online OTA upgrade process data transmitted by the target electronic control unit through a fourth inward transmission channel; The second online OTA upgrade process data is transmitted to the debugging and tracking end through the external transmission channel of the on-board diagnostic system, so that the debugging and tracking end can troubleshoot OTA upgrade status failure based on the second online OTA upgrade process data.

6. The method according to claim 1, characterized in that The message frame of the online OTA upgrade message or the simulated OTA upgrade message includes an Ethernet header, an IP header, a TCP / UDP header, a protocol version field, a fault debugging and tracking type field, a total data length field, a source address field, a destination address field, a fault debugging and tracking command code and a data field.

7. An OTA upgrade fault debugging and tracking device, characterized in that: include: A receiving module is configured to receive a simulated OTA upgrade message transmitted by the debugging and tracing terminal through the first inward transmission channel, or an online OTA upgrade message transmitted by the cloud through the second inward transmission channel; An extraction module is configured to extract a fault debugging tracing type and a fault debugging tracing command code from the online OTA upgrade message or the simulated OTA upgrade message; a reading module configured to read a state of a sending port of an on-board diagnostic system if it is determined that the fault debugging and tracing command code is a valid command code based on the fault debugging and tracing type; a channel opening module, configured to, if it is determined that the on-board diagnostic system external transmission channel needs to be opened based on the fault debugging and tracing command code and the state of the on-board diagnostic system sending port, execute an action of opening the on-board diagnostic system external transmission channel, and record the number of opening executions; A first data sending module is configured to send online OTA upgrade process data or simulated OTA upgrade process data to the debugging and tracking end through the external transmission channel of the on-board diagnostic system if it is determined that the external transmission channel of the on-board diagnostic system is successfully opened, so that the debugging and tracking end can troubleshoot the OTA upgrade status fault based on the online OTA upgrade process data, or troubleshoot the OTA upgrade process fault based on the simulated OTA upgrade process data; Based on the fault debugging and tracing command code and the state of the on-board diagnostic system sending port, determining that the on-board diagnostic system outward transmission channel needs to be opened includes: Determining whether the fault debugging and tracing command code is a preset sending port opening command code; If yes, determining whether the sending port state is closed; If so, it is determined that the on-board diagnostic system external transmission channel needs to be opened.

8. A vehicle gateway, characterized in that: The whole vehicle gateway includes an upgrade agent terminal; the upgrade agent terminal includes the OTA upgrade fault debugging and tracking device as described in claim 7.

9. A new energy vehicle, characterized in that: The new energy vehicle includes the whole vehicle gateway as claimed in claim 8.

Images