ECU upgrading method and device based on Tbox and server

Abstract

The invention provides an ECU upgrading method and device based on Tbox and a server, and relates to the technical field of OTA vehicle end ECU flashing, the method is applied to the Tbox, the Tbox is a vehicle-mounted communication terminal, the vehicle-mounted communication terminal comprises a rollback package storage catalog, the method comprises the steps that information of an ECU to be upgraded of a vehicle is obtained, updating version information is obtained from a peripheral OTA server, and the information of the ECU to be upgraded is stored in the rollback package storage catalog; the to-be-upgraded ECU information comprises an ECU type and current operation version information; when the ECU type is a non-A / B side ECU, the current operation version information of the non-A / B side ECU is stored in a rollback package storage directory, and the non-A / B side ECU is an ECU with only one storage area; and performing version upgrading processing on the non-A / B-side ECU by using the updated version information when the version of the non-A / B-side ECU is updated, and performing version rollback processing on the non-A / B-side ECU by using the current running version information stored in the rollback package storage directory when upgrading fails so as to flash the non-A / B-side ECU back to the version before upgrading. According to the method, the ECU upgrading stability can be remarkably improved while the cost is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of OTA vehicle-side ECU flashing for Internet of Vehicles, and in particular to a Tbox-based ECU upgrade method, device and server. Background Art

[0002] When upgrading the non-A / B side ECU of the vehicle, the current program needs to be overwritten and flashed. Once it fails, the non-A / B side ECU will be unusable and can only be diagnosed and flashed offline. At present, relevant technologies have proposed that the A / B side ECU can be used. When the A / B side ECU is upgraded OTA, the current version can be run on the A side and the new version can be flashed on the B side. If successful, the B side program will be restarted and executed. If it fails, the stable program on the A side will be switched, so as not to affect the normal use of the ECU. However, it is too costly for car companies to do all the A / B side ECUs, which will increase the cost of buying cars for users and is not conducive to the long-term development of car companies in the Internet of Vehicles OTA project. Summary of the invention

[0003] In view of this, the purpose of the present invention is to provide an ECU upgrade method, device and server based on Tbox, which can significantly improve the stability of ECU upgrade while reducing costs.

[0004] In the first aspect, an embodiment of the present invention provides an ECU upgrade method based on Tbox, and the method is applied to Tbox, where Tbox is a vehicle-mounted communication terminal, and the vehicle-mounted communication terminal includes: a rollback package storage directory, and the method includes: obtaining the vehicle's ECU information to be upgraded, and obtaining updated version information from an external OTA server, wherein the ECU information to be upgraded includes: ECU type and current running version information; when the ECU type is a non-A / B side ECU, storing the current running version information of the non-A / B side ECU in the rollback package storage directory, wherein the non-A / B side ECU is an ECU with only one storage area; using the updated version information, performing version upgrade processing on the non-A / B side ECU, and when the upgrade fails, using the current running version information stored in the rollback package storage directory, performing version rollback processing on the non-A / B side ECU, so as to flash the non-A / B side ECU back to the version before the upgrade.

[0005] In one embodiment, the vehicle communication terminal also includes: an updated version storage directory, after the step of obtaining the updated version information from the external OTA server, including: storing the updated version information in the updated version storage directory, so that when performing the version upgrade process, the updated version information stored in the updated version storage directory is called to perform a version upgrade on the ECU.

[0006] In one embodiment, before the step of storing the current running version information of the non-A / B side ECU in the rollback package storage directory, it includes: comparing the updated version information with the current running version information, if the versions are inconsistent, storing the current running version information of the non-A / B side ECU in the rollback package storage directory to update the rollback package storage directory.

[0007] In one implementation, after the step of comparing the update version information with the current running version information, the following step is included: if the update version information is consistent with the current running version information, the update version information is re-acquired from the external device OTA server.

[0008] In one embodiment, the step of performing version upgrade processing on the non-A / B side ECU using the updated version information includes: erasing the current program in the non-A / B side ECU, and overwriting and flashing the non-A / B side ECU using the updated version information to complete the version upgrade processing of the non-A / B side ECU.

[0009] In one embodiment, after the step of overwriting and flashing the non-A / B side ECU with the updated version information to complete the version upgrade processing of the non-A / B side ECU, the following steps are included: if the successful reporting information and log sent by the non-A / B side ECU are received, it is determined that the ECU version upgrade is successful; if the failed rollback upload information sent by the non-A / B side ECU is received, a version rollback instruction is sent to the non-A / B side ECU, and the current running version information stored in the rollback package storage directory is used to perform version rollback processing on the non-A / B side ECU to flash the non-A / B side ECU back to the version before the upgrade.

[0010] In one embodiment, the method includes: when the ECU type is an A / B side ECU, directly calling the updated version information stored in the updated version storage directory, and performing version upgrade processing on the A side storage area of ​​the A / B side ECU, wherein the A / B side ECU includes: an A side storage area and a B side storage area, the A side storage area is used to store the main application and data, and the B side storage area is used to back up the version information before the update.

[0011] In one implementation, after the step of performing version update processing on the A-side storage area of ​​the A / B-side ECU, the following step is included: if successful reporting information and logs sent by the A / B-side ECU are received, it is determined that the ECU version upgrade is successful.

[0012] In one embodiment, after the step of performing version update processing on the A-side storage area of ​​the A / B-side ECU, the following step is included: if failed rollback upload information sent by the A / B-side ECU is received, a version rollback instruction is sent to the A / B-side ECU, so as to use the version information stored in the B-side storage area of ​​the A / B-side ECU to flash the A-side storage area of ​​the A / B-side ECU back to the version before the upgrade.

[0013] In the second aspect, an embodiment of the present invention also provides an ECU upgrade device based on Tbox, and the device is applied to Tbox, where Tbox is a vehicle-mounted communication terminal, and the vehicle-mounted communication terminal includes: a rollback package storage directory, and the device includes: an information acquisition module, which acquires the ECU information to be upgraded of the vehicle, and acquires the updated version information from an external OTA server, wherein the ECU information to be upgraded includes: ECU type and current running version information; a version information backup module, when the ECU type is a non-A / B side ECU, stores the current running version information of the non-A / B side ECU in the rollback package storage directory, wherein the non-A / B side ECU is an ECU with only one storage area; an ECU upgrade module, which uses the updated version information to perform version upgrade processing on the non-A / B side ECU, and when the upgrade fails, uses the current running version information stored in the rollback package storage directory to perform version rollback processing on the non-A / B side ECU, so as to flash the non-A / B side ECU back to the version before the upgrade.

[0014] In a third aspect, an embodiment of the present invention further provides a server, comprising a processor and a memory, wherein the memory stores computer executable instructions that can be executed by the processor, and the processor executes the computer executable instructions to implement any one of the methods provided in the first aspect.

[0015] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement any one of the methods provided in the first aspect.

[0016] The embodiments of the present invention bring the following beneficial effects: An embodiment of the present invention provides an ECU upgrade method, device and server based on Tbox. The method is applied to Tbox, where Tbox is a vehicle-mounted communication terminal. The vehicle-mounted communication terminal includes: a rollback package storage directory. The method first obtains the ECU information to be upgraded of the vehicle, and obtains the update version information from the external OTA server. Then, when the ECU type is a non-A / B side ECU, the current running version information of the non-A / B side ECU is stored in the rollback package storage directory. Finally, the non-A / B side ECU is upgraded using the updated version information. When the upgrade fails, the non-A / B side ECU is rolled back using the current running version information stored in the rollback package storage directory, so that the non-A / B side ECU can be flashed back to the version before the upgrade. The embodiment of the present invention can significantly improve the stability of ECU upgrades while reducing costs.

[0017] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention are realized and obtained by the structures particularly pointed out in the description, claims and drawings.

[0018] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0020] Figure 1 A schematic diagram of a flow chart of an existing BCM upgrade method provided by an embodiment of the present invention; Figure 2 A schematic diagram of a flow chart of an ECU upgrade method based on Tbox provided in an embodiment of the present invention; Figure 3 A schematic diagram of a specific process of an ECU upgrade method based on Tbox provided in an embodiment of the present invention; Figure 4 A schematic diagram of the structure of an ECU upgrade device based on Tbox provided in an embodiment of the present invention; Figure 5 A schematic diagram of the structure of a server provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution of the present invention will be clearly and completely described in combination with the embodiments below. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0022] At present, the storage architecture of vehicles mainly includes non-A / B side ECU and A / B side ECU. A / B side ECU has two independent storage areas, usually stored in solid-state storage media. A side stores the main application and data, and B side can be used for backup, update or storage of a reliable, previous stable state. Non-A / B side ECU cannot be stored and cannot be rolled back to the previous version. See Figure 1 The flowchart of an existing BCM upgrade method is shown in the figure. Only the ECU on the AB side has the storage rollback function, and the non-AB side ECU cannot store the rollback function. For the ECU that supports rollback, if the upgrade is successful, it will restart. If the restart fails, it will enter the rollback. If the upgrade fails, it also needs to enter the rollback. For the ECU that does not support rollback, if the upgrade is successful but the restart fails, or the upgrade fails, the car cannot be used normally and needs to be towed to the 4S shop for re-burning.

[0023] Therefore, when upgrading the non-A / B side ECU of the vehicle, the current program needs to be overwritten and flashed. Once it fails, the non-A / B side ECU will be unusable and can only be diagnosed and flashed offline. If the A / B side ECU is used, the A / B side ECU can run the current version on the A side and flash the new version on the B side during the OTA upgrade. If successful, the B side program will be restarted and executed. If it fails, the stable program on the A side will be switched, so as not to affect the normal use of the ECU. However, it is too costly for car companies to make all A / B side ECUs, which will increase the user's car purchase cost and is not conducive to the long-term development of car companies in the Internet of Vehicles OTA project. Based on this, the ECU upgrade method, device and server based on Tbox provided by the present invention are implemented, and Tbox is used as the backup storage unit of the non-AB side ECU to help the non-AB side ECU store backups and realize that the non-AB side ECU has the functions of the AB side ECU, so that the stability of the ECU upgrade can be significantly improved while reducing costs.

[0024] See also Figure 2 The flowchart of a Tbox-based ECU upgrade method is shown, the method is applied to Tbox, Tbox is a vehicle-mounted communication terminal, the vehicle-mounted communication terminal includes: a rollback package storage directory, the method mainly includes the following steps S202 to S206: Step S202, obtain the vehicle's ECU information to be upgraded, and obtain the updated version information from the external OTA server, wherein the ECU information to be upgraded includes: ECU type and current running version information, and the on-board communication terminal also includes: updated version storage directory. In one embodiment, after the step of obtaining the updated version information from the external OTA server, the updated version information can be stored in the updated version storage directory, so that when performing the version upgrade process, the updated version information stored in the updated version storage directory can be called to upgrade the ECU version.

[0025] Step S204, when the ECU type is a non-A / B side ECU, the current running version information of the non-A / B side ECU is stored in the rollback package storage directory, wherein the non-A / B side ECU is an ECU with only one storage area. In one embodiment, the ECU type can also be an A / B side ECU, and the A / B side ECU includes: an A side storage area and a B side storage area, the A side storage area is used to store the main application and data, and the B side storage area is used to back up the version information before the update. In other words, the rollback package storage directory in the Tbox is used to execute the B side storage area function of the A / B side ECU, and the updated version storage directory in the Tbox is used to execute the A side storage area function of the A / B side ECU.

[0026] Step S206, using the updated version information, perform version upgrade processing on the non-A / B side ECU, and when the upgrade fails, use the current running version information stored in the rollback package storage directory to perform version rollback processing on the non-A / B side ECU, so as to flash the non-A / B side ECU back to the version before the upgrade. In one embodiment, the updated version information and the current running version information can be compared first, and then the non-AB side ECU is updated. There are two directories in tbox, namely the rollback package storage directory and the updated version storage directory. First, the new version (i.e., the updated version information) is downloaded from the OTA server and stored in the updated version storage directory of tbox, and then the updated version information is compared with the current running version information. If they are different, the current running version information is stored in the rollback package storage directory of tbox, and then the updated version information in the updated version storage directory is used to update the current version of the ECU. After the update fails, there is no need to perform version comparison again, and the current running version information in the rollback package storage directory can be directly used for version rollback processing.

[0027] The above-mentioned Tbox-based ECU upgrade method provided in the embodiment of the present invention only needs to pre-set the corresponding directory in tbox to store the rollback package. When the upgrade fails, the backup rollback package is re-written back to the old version through TOBX, which saves the development cost of the ECU A / B side, can reduce the cost and significantly improve the stability of ECU upgrade.

[0028] See also Figure 3 The specific process diagram of a Tbox-based ECU upgrade method is shown. The embodiment of the present invention also provides an implementation method of TBOX assisting non-AB surface ECU to implement the rollback function. For details, see (1) to (2) as follows: (1) The updated version information is compared with the current running version information. If the versions are inconsistent, the current running version information of the non-A / B side ECU is stored in the rollback package storage directory to update the rollback package storage directory. If the updated version information is consistent with the current running version information, the updated version information is obtained again from the peripheral OTA server. By performing the above comparison before updating, it is possible to effectively prevent the update version information from lagging (the current running version information is compared with the current running version information, and the versions are consistent) or to prevent repeated updates to the updated ECU (the updated version information is compared with the updated version information, and the versions are consistent). In addition, when the versions are inconsistent, the current running version information of the non-A / B side ECU is effectively stored in the rollback package storage directory for backup through this mechanism.

[0029] In one implementation, the difference between the update version information and the current running version information may be calculated using a binary difference algorithm, thereby determining whether the update version information is consistent with the current running version information.

[0030] (2) Erasing the current program in the non-A / B side ECU, and overwriting the non-A / B side ECU with the updated version information to complete the version upgrade process of the non-A / B side ECU. In one embodiment, if the successful reporting information and log sent by the non-A / B side ECU are received, it is determined that the ECU version upgrade is successful; if the failed rollback upload information sent by the non-A / B side ECU is received, a version rollback instruction is sent to the non-A / B side ECU, and the current running version information stored in the rollback package storage directory is used to perform version rollback processing on the non-A / B side ECU, so as to flash the non-A / B side ECU back to the version before the upgrade.

[0031] In addition, an embodiment of the present invention also provides an implementation method for TBOX to assist the AB side ECU to realize the rollback function. When the ECU type is the A / B side ECU, the updated version information stored in the updated version storage directory is directly called to perform version upgrade processing on the A side storage area of ​​the A / B side ECU: if the successful reporting information and log sent by the A / B side ECU are received, it is determined that the ECU version upgrade is successful; if the failed rollback upload information sent by the A / B side ECU is received, a version rollback instruction is sent to the A / B side ECU to use the version information stored in the B side storage area of ​​the A / B side ECU to flash the A side storage area of ​​the A / B side ECU back to the version before the upgrade.

[0032] To sum up, if the ECU has AB side, its use will not be affected no matter how the upgrade fails. If the ECU does not have AB side, the vehicle will be unusable except when the upgrade and restart are successful, which has a negative impact on the enterprise and a poor user experience. In the current OTA link, there are multiple ECUs without AB side functions. The present invention targets these ECUs that do not have the ability to store rollback packages. tbox will help complete the storage. If the rollback package information stored in tbox is inconsistent with the software version currently running on the ECU, tbox will request the OTA server to download the update rollback package, and then rewrite the ECU without A / B side back to the old version. In this way, the A / B side function of the ECU will be realized at the lowest cost, which can greatly reduce the development cost of the OTA project. When the upgrade fails, the backup rollback package can be rewritten back to the old version through TOBX, eliminating the development cost of the A / B side of the ECU, which can significantly improve the stability of the ECU upgrade while reducing the cost.

[0033] For the ECU upgrade method based on Tbox provided in the above embodiment, an embodiment of the present invention provides an ECU upgrade device based on Tbox, which is applied to Tbox, where Tbox is a vehicle-mounted communication terminal, and the vehicle-mounted communication terminal includes: a rollback package storage directory, see Figure 4 The schematic diagram of the structure of a Tbox-based ECU upgrade device is shown, and the device includes the following parts: The information acquisition module 402 acquires the ECU information to be upgraded of the vehicle and acquires the update version information from the external OTA server, wherein the ECU information to be upgraded includes: ECU type and current running version information; The version information backup module 404 stores the current running version information of the non-A / B-side ECU in the rollback package storage directory when the ECU type is a non-A / B-side ECU, wherein the non-A / B-side ECU is an ECU with only one storage area; The ECU upgrade module 406 uses the updated version information to perform version upgrade processing on the non-A / B side ECU, and when the upgrade fails, uses the current running version information stored in the rollback package storage directory to perform version rollback processing on the non-A / B side ECU, so as to flash the non-A / B side ECU back to the version before the upgrade.

[0034] The Tbox-based ECU upgrade device provided in the embodiment of the present application can significantly improve the stability of ECU upgrade while reducing costs.

[0035] In one embodiment, the vehicle-mounted communication terminal also includes: an updated version storage directory. After performing the step of obtaining the updated version information from the external OTA server, the above-mentioned information acquisition module 402 is also used to: store the updated version information in the updated version storage directory, so that when performing the version upgrade process, the updated version information stored in the updated version storage directory is called to perform a version upgrade on the ECU.

[0036] In one embodiment, before performing the step of storing the current running version information of the non-A / B side ECU in the rollback package storage directory, the version information backup module 404 is also used to: compare the updated version information with the current running version information; if the versions are inconsistent, the current running version information of the non-A / B side ECU is stored in the rollback package storage directory to update the rollback package storage directory.

[0037] In one implementation, after the step of comparing the updated version information with the currently running version information, the version information backup module 404 is further used to: if the updated version information is consistent with the currently running version information, then reacquire the updated version information from the external OTA server.

[0038] In one embodiment, when performing the step of performing version upgrade processing on the non-A / B side ECU using the updated version information, the above-mentioned ECU upgrade module 406 is also used to: erase the current program in the non-A / B side ECU, and overwrite and flash the non-A / B side ECU using the updated version information to complete the version upgrade processing of the non-A / B side ECU.

[0039] In one embodiment, after the step of overwriting and flashing the non-A / B side ECU with the updated version information to complete the version upgrade process of the non-A / B side ECU, the ECU upgrade module 406 is further used to: if successful reporting information and logs sent by the non-A / B side ECU are received, determine that the ECU version upgrade is successful; if failed rollback upload information sent by the non-A / B side ECU is received, send a version rollback instruction to the non-A / B side ECU, and use the current running version information stored in the rollback package storage directory to perform version rollback processing on the non-A / B side ECU to flash the non-A / B side ECU back to the version before the upgrade.

[0040] In one embodiment, the ECU upgrade module 406 is also used to: when the ECU type is an A / B side ECU, directly call the updated version information stored in the updated version storage directory, and perform version upgrade processing on the A side storage area of ​​the A / B side ECU, wherein the A / B side ECU includes: an A side storage area and a B side storage area, the A side storage area is used to store the main application and data, and the B side storage area is used to back up the version information before the update.

[0041] In one implementation, after the step of performing version update processing on the A-side storage area of ​​the A / B-side ECU, the ECU upgrade module 406 is further used to: if successful reporting information and logs sent by the A / B-side ECU are received, determine that the ECU version upgrade is successful.

[0042] In one embodiment, after the step of performing version update processing on the A-side storage area of ​​the A / B-side ECU, the above-mentioned ECU upgrade module 406 is also used to: if a failed rollback upload information sent by the A / B-side ECU is received, a version rollback instruction is sent to the A / B-side ECU, so as to use the version information stored in the B-side storage area of ​​the A / B-side ECU to flash the A-side storage area of ​​the A / B-side ECU back to the version before the upgrade.

[0043] The device provided in the embodiment of the present invention has the same implementation principle and technical effects as those of the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference may be made to the corresponding contents in the aforementioned method embodiment.

[0044] An embodiment of the present invention provides a server. Specifically, the server includes a processor and a storage device. The storage device stores a computer program, and when the computer program is executed by the processor, it executes the method described in any one of the above-mentioned embodiments.

[0045] Figure 5 A structural diagram of a server provided in an embodiment of the present invention, the server 100 includes: a processor 50, a memory 51, a bus 52 and a communication interface 53, wherein the processor 50, the communication interface 53 and the memory 51 are connected via the bus 52; the processor 50 is used to execute an executable module stored in the memory 51, such as a computer program.

[0046] The memory 51 may include a high-speed random access memory (RAM), and may also include a non-volatile memory, such as at least one disk memory. The communication connection between the system network element and at least one other network element is realized through at least one communication interface 53 (which may be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc. may be used.

[0047] The bus 52 may be an ISA bus, a PCI bus, or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0048] Among them, the memory 51 is used to store programs, and the processor 50 executes the program after receiving the execution instruction. The method executed by the device for flow process definition disclosed in any embodiment of the above-mentioned embodiment of the present invention can be applied to the processor 50 or implemented by the processor 50.

[0049] The processor 50 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the processor 50. The above processor 50 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiments of the present invention can be directly embodied as a hardware decoding processor to be executed, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 51, and the processor 50 reads the information in the memory 51 and completes the steps of the above method in combination with its hardware.

[0050] The computer program product of the readable storage medium provided in the embodiment of the present invention includes a computer-readable storage medium storing program code, and the instructions included in the program code can be used to execute the methods described in the previous method embodiments. The specific implementation can be referred to the previous method embodiments, which will not be repeated here.

[0051] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc., which can store program codes.

[0052] Finally, it should be noted that the above-described embodiments are only specific implementations of the present invention, which are used to illustrate the technical solutions of the present invention, rather than to limit them. The protection scope of the present invention is not limited thereto. Although the present invention is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed by the present invention, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A Tbox-based ECU upgrade method, characterized in that: The method is applied to a Tbox, the Tbox being a vehicle-mounted communication terminal, the vehicle-mounted communication terminal comprising: a rollback package storage directory, and the method comprising: Obtain the ECU information to be upgraded of the vehicle, and obtain the updated version information from the external OTA server, wherein the ECU information to be upgraded includes: ECU type and current running version information; When the ECU type is a non-A / B surface ECU, storing the current running version information of the non-A / B surface ECU in the rollback package storage directory, wherein the non-A / B surface ECU is an ECU with only one storage area; The updated version information is used to perform version upgrade processing on the non-A / B side ECU, and when the upgrade fails, the current running version information stored in the rollback package storage directory is used to perform version rollback processing on the non-A / B side ECU, so as to flash the non-A / B side ECU back to the version before the upgrade.

2. The ECU upgrade method based on Tbox according to claim 1, characterized in that: The vehicle-mounted communication terminal further includes: an update version storage directory, after the step of obtaining update version information from the external OTA server, including: The updated version information is stored in the updated version storage directory, so that when performing version upgrade processing, the updated version information stored in the updated version storage directory is called to perform version upgrade on the ECU.

3. The ECU upgrade method based on Tbox according to claim 1, characterized in that: Before the step of storing the current running version information of the non-A / B side ECU in the rollback package storage directory, the method includes: The updated version information is compared with the currently running version information. If the versions are inconsistent, the currently running version information of the non-A / B side ECU is stored in the rollback package storage directory to update the rollback package storage directory.

4. The ECU upgrade method based on Tbox according to claim 2, characterized in that: After the step of comparing the updated version information with the currently running version information, the following steps are included: If the updated version information is consistent with the currently running version information, the updated version information is obtained again from the external OTA server.

5. The ECU upgrade method based on Tbox according to claim 1, characterized in that: The step of performing version upgrade processing on the non-A / B side ECU using the updated version information includes: The current program in the non-A / B side ECU is erased, and the non-A / B side ECU is overwritten and rewritten with the updated version information to complete the version upgrade process of the non-A / B side ECU.

6. The Tbox-based ECU upgrade method according to claim 5, characterized in that: After the step of overwriting the non-A / B side ECU with the updated version information to complete the version upgrade process of the non-A / B side ECU, the method further comprises: If the successful reporting information and log sent by the non-A / B side ECU are received, it is determined that the ECU version is successfully upgraded; If a failed rollback upload information is received from the non-A / B side ECU, a version rollback instruction is sent to the non-A / B side ECU, and the current running version information stored in the rollback package storage directory is used to perform version rollback processing on the non-A / B side ECU to flash the non-A / B side ECU back to the version before the upgrade.

7. The ECU upgrade method based on Tbox according to claim 1, characterized in that: The method comprises: When the ECU type is an A / B side ECU, the updated version information stored in the updated version storage directory is directly called to perform version upgrade processing on the A side storage area of ​​the A / B side ECU, wherein the A / B side ECU includes: the A side storage area and the B side storage area, the A side storage area is used to store the main application and data, and the B side storage area is used to back up the version information before the update.

8. The Tbox-based ECU upgrade method according to claim 7, characterized in that: After the step of performing version update processing on the A-side storage area of ​​the A / B-side ECU, the method further comprises: If the successful reporting information and log sent by the A / B side ECU are received, it is determined that the ECU version upgrade is successful.

9. The Tbox-based ECU upgrade method according to claim 7, characterized in that: After the step of performing version update processing on the A-side storage area of ​​the A / B-side ECU, the method further comprises: If a failed rollback upload information is received from the A / B side ECU, a version rollback instruction is sent to the A / B side ECU to use the version information stored in the B side storage area of ​​the A / B side ECU to flash the A side storage area of ​​the A / B side ECU back to the version before the upgrade.

10. An ECU upgrade device based on Tbox, characterized in that: The device is applied to a Tbox, which is a vehicle-mounted communication terminal. The vehicle-mounted communication terminal includes a rollback package storage directory. The device includes: An information acquisition module is used to acquire the ECU information to be upgraded of the vehicle and acquire the updated version information from the external OTA server, wherein the ECU information to be upgraded includes: ECU type and current running version information; a version information backup module, which, when the ECU type is a non-A / B-side ECU, stores the current running version information of the non-A / B-side ECU in the rollback package storage directory, wherein the non-A / B-side ECU is an ECU with only one storage area; The ECU upgrade module uses the updated version information to perform version upgrade processing on the non-A / B side ECU, and when the upgrade fails, uses the current running version information stored in the rollback package storage directory to perform version rollback processing on the non-A / B side ECU, so as to flash the non-A / B side ECU back to the version before the upgrade.

11. A server, characterized in that: The method comprises a processor and a memory, wherein the memory stores computer executable instructions that can be executed by the processor, and the processor executes the computer executable instructions to implement the method according to any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called and executed by a processor, the computer-executable instructions prompt the processor to implement the method according to any one of claims 1 to 9.

Images