Automobile OTA combination upgrading method, device and equipment and storage medium

Abstract

The invention discloses an automobile OTA combination upgrading method, device and equipment and a storage medium, and relates to the technical field of automobile intelligent upgrading, and the method comprises the steps: responding to an upgrading instruction, and obtaining upgrading information and preset upgrading retry times of all controllers; the controllers are upgraded in sequence based on the upgrading information; and when the upgrade of the controller fails, the upgrade retry processing is performed on the controller based on the preset upgrade retry times corresponding to the controller until the upgrade of the controller is completed, so that the reliability of OTA upgrade and the user experience are improved.

Description

Technical Field

[0001] The present invention relates to the field of automobile intelligent upgrade technology, and in particular to an automobile OTA combined upgrade method, device, equipment and storage medium. Background Art

[0002] With the development of intelligent and connected cars, OTA upgrades have become an important means of updating and maintaining car software. However, during the process of combined OTA upgrades (i.e., upgrading multiple controllers or modules at the same time), upgrade failures may occur due to network fluctuations, hardware compatibility issues, or software defects.

[0003] The traditional approach is to configure a retry count for this combined upgrade task on the OTA management platform, and execute the same retry count for each controller upgrade failure in the combined task. This retry mechanism is relatively rigid and mechanical, resulting in low upgrade efficiency and poor user experience.

[0004] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of the present invention is to provide an automobile OTA combined upgrade method, device, equipment and storage medium, aiming to solve the technical problem of low upgrade efficiency of OTA upgrade.

[0006] To achieve the above object, the present invention provides a vehicle OTA combined upgrade method, the vehicle OTA combined upgrade method comprising the following steps:

[0007] In response to the upgrade instruction, obtain upgrade information and preset upgrade retry times of all controllers;

[0008] Upgrading each of the controllers in sequence based on the upgrade information;

[0009] When the controller upgrade fails, the controller is retried based on a preset upgrade retry number corresponding to the controller until the controller upgrade is completed.

[0010] In one embodiment, the step of obtaining upgrade information and preset upgrade retry times of all controllers in response to the upgrade instruction includes:

[0011] In response to the upgrade instruction, acquiring upgrade information, the upgrade information including controller information;

[0012] The upgrade retry times of each controller are configured based on the controller information to obtain the preset upgrade retry times of all controllers.

[0013] In one embodiment, the step of configuring the upgrade retry times of each controller based on the controller information to obtain the preset upgrade retry times of all controllers includes:

[0014] Acquire the upgrade duration, historical upgrade data, and historical failure information of each controller according to the controller information;

[0015] The upgrade retry times of each controller are configured based on the upgrade duration, the historical upgrade data, and the historical failure information to obtain a preset upgrade retry times of all controllers.

[0016] In one embodiment, the step of sequentially upgrading each of the controllers based on the upgrade information includes:

[0017] Obtaining a preset upgrade time based on the upgrade instruction, and performing upgrade timing;

[0018] When the timing reaches the preset upgrade time, the vehicle is controlled to be powered on;

[0019] When the vehicle is powered on, each of the controllers is upgraded in sequence based on the upgrade information.

[0020] In one embodiment, when the vehicle is powered on, the step of upgrading each controller in sequence based on the upgrade information includes:

[0021] When the vehicle is powered on, the upgrade condition check is performed on the vehicle, and the upgrade condition check includes task validity check, installation package decryption and signature check, controller version information check and precondition check;

[0022] When the vehicle upgrade condition verification is passed, each of the controllers is upgraded in sequence based on the upgrade information.

[0023] In one embodiment, when the controller upgrade fails, the step of performing upgrade retry processing on the controller based on a preset upgrade retry number corresponding to the controller until the controller upgrade is completed includes:

[0024] After the controller upgrade fails, determining whether the number of upgrade retries of the controller exceeds a preset number of upgrade retries corresponding to the controller;

[0025] When the upgrade retry number exceeds the preset upgrade retry number, the upgrade process of the controller is terminated, and the upgrade process of the next controller is executed;

[0026] When the upgrade retry times do not exceed the preset upgrade retry times, the controller continues to be upgraded and retried.

[0027] In one embodiment, the method further comprises:

[0028] Get the upgrade status and results of all controllers in the vehicle;

[0029] The upgrade status and the upgrade result are sent to the user end for real-time display.

[0030] In addition, to achieve the above-mentioned purpose, the present invention also proposes an automobile OTA combined upgrade device, the device comprising:

[0031] An information acquisition module, used to obtain upgrade information and preset upgrade retry times of all controllers in response to an upgrade instruction;

[0032] An upgrade module, used for upgrading each of the controllers in sequence based on the upgrade information;

[0033] The upgrade retry module is used to perform upgrade retry processing on the controller based on a preset upgrade retry number corresponding to the controller when the controller upgrade fails, until the controller upgrade is completed.

[0034] In addition, to achieve the above-mentioned objectives, the present invention also proposes an automobile OTA combination upgrade device, which includes: a memory, a processor, and an automobile OTA combination upgrade program stored on the memory and runnable on the processor, and the automobile OTA combination upgrade program is configured to implement the steps of the automobile OTA combination upgrade method described above.

[0035] In addition, to achieve the above-mentioned purpose, the present invention also proposes a storage medium, on which a car OTA combination upgrade program is stored. When the car OTA combination upgrade program is executed by a processor, the steps of the car OTA combination upgrade method described above are implemented.

[0036] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the automobile OTA combined upgrade method described above.

[0037] One or more technical solutions proposed in this application have at least the following technical effects:

[0038] In response to the upgrade instruction, the upgrade information and the preset upgrade retry times of all controllers are obtained; each controller is upgraded in turn based on the upgrade information; when the controller upgrade fails, the controller is retried based on the preset upgrade retry times corresponding to the controller until the controller upgrade is completed. By retrying the controller based on the preset upgrade retry times when the upgrade fails, it is ensured that each controller can complete the upgrade, thereby improving the overall upgrade success rate. The user does not need to operate personally, the system automatically upgrades and retries, reducing user intervention and providing a more convenient and smoother upgrade experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

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

[0041] Figure 1 A flowchart of the first embodiment of the automobile OTA combined upgrade method of the present application is provided;

[0042] Figure 2 An upgrade retry flow chart provided for the first embodiment of the automobile OTA combined upgrade method of this application;

[0043] Figure 3 A flow chart of the second embodiment of the automobile OTA combined upgrade method of the present application;

[0044] Figure 4 A flowchart diagram of the third embodiment of the automobile OTA combined upgrade method of the present application;

[0045] Figure 5 This is a schematic diagram of the module structure of the automobile OTA combination upgrade device according to an embodiment of the present application;

[0046] Figure 6 This is a schematic diagram of the device structure of the hardware operating environment involved in the automobile OTA combined upgrade method in the embodiment of the present application.

[0047] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0048] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0049] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0050] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a car OTA combination upgrade device, etc. The following takes the car OTA combination upgrade device as an example to illustrate this embodiment and the following embodiments.

[0051] Based on this, the embodiment of the present application provides a method for automobile OTA combination upgrade, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the automobile OTA combined upgrade method of the present application.

[0052] In this embodiment, the automobile OTA combined upgrade method includes steps S10 to S30:

[0053] Step S10, in response to the upgrade instruction, obtaining upgrade information and preset upgrade retry times of all controllers;

[0054] It should be noted that the upgrade instruction can be the upgrade information input by the user. When responding to the upgrade instruction, it is necessary to first obtain the upgrade information of the current system, then obtain the list of all controllers in the system, and for each controller, obtain its preset upgrade retry times.

[0055] It should be understood that the preset number of upgrade retries may be set by the user or obtained through analysis of this strategy.

[0056] In the specific implementation, in addition to downloading the controller software for this upgrade, other information of this upgrade (number of download retries, number of controller upgrade retries, preconditions, etc.) is sent to UC-Master through the OTA task when the version is released. UC-Master refers to a key component or service in the OTA (Over-The-Air) upgrade process in the automotive industry. In the OTA upgrade, UC-Master is responsible for managing and coordinating the update process of the vehicle software. UC-Master parses the OTA task package to obtain the installation information for this time; UC-Master is the core program for the OTA upgrade of the whole vehicle, which implements the main control logic of OTA. It calls DM-Client to realize business communication and software package download with the server, and realizes the control and installation of other physical ECUs or virtual ECUs through the control and management of UC-Slave. DM-Client (device management client) is a component in the operating system used to manage device configuration and security functions. UC-Slave is the control program of the upgraded ECU, which mainly realizes the management and control of a single ECU or upgrade object. OTA is (Over-The-Air) or air download technology, which is a method of remotely upgrading device firmware or software through a wireless network.

[0057] Step S20, upgrading each controller in turn based on the upgrade information;

[0058] In a specific implementation, within a predetermined upgrade window, the first controller is upgraded. If the controller upgrade is successful, it is determined whether it is the last controller to be upgraded. If it is, the upgrade ends. If not, the next controller upgrade begins until all controller upgrades are completed.

[0059] Step S30: When the controller upgrade fails, the controller is retried based on a preset upgrade retry number corresponding to the controller until the controller upgrade is completed.

[0060] In the specific implementation, if the controller upgrade fails, it is determined whether the number of controller upgrades exceeds the number of retries configured by the OTA platform. If not, the controller upgrade is retried, and the number of upgrades is +1; if the number of retries overflows, the controller upgrade is terminated and the next controller upgrade is started until the controller upgrade is completed.

[0061] In a feasible implementation, step S30 may include steps A11 to A13:

[0062] Step A11: after the controller upgrade fails, determining whether the controller upgrade retry count exceeds a preset upgrade retry count corresponding to the controller;

[0063] It should be noted that this step is performed after the controller upgrade fails. The system will check the upgrade retry count of the controller, that is, the number of times it attempts to upgrade again after failure. The system will compare the current retry count with the preset upgrade retry count for the controller. This preset retry count is a pre-set value to prevent resource waste and system instability caused by infinite retries.

[0064] Step A12: When the number of upgrade retries exceeds the preset number of upgrade retries, the upgrade process of the controller is terminated, and the upgrade process of the next controller is executed;

[0065] It should be noted that if it is determined in step A11 that the number of retries has exceeded the preset number of retries, the system will consider that the upgrade of the controller has failed. At this time, the system will stop further upgrade attempts on the controller to avoid unnecessary attempts and possible consumption of system resources. The system will record the status of the failed upgrade and may notify the user or technician for further manual intervention or troubleshooting. Then, the system will move to the next controller and start its upgrade process.

[0066] Step A13: When the upgrade retry times do not exceed the preset upgrade retry times, the controller continues to be upgraded and retried.

[0067] It should be noted that if the comparison result in step A11 shows that the number of retries has not exceeded the preset number of retries, then the system will consider that there is still a chance to successfully upgrade the controller.

[0068] The next upgrade attempt is scheduled and the retry count is incremented.

[0069] In the specific implementation, when the number of upgrade retries exceeds the preset number of upgrade retries, regardless of whether the current controller is successful, the next controller in the upgrade list will be upgraded. Through this process, it can be ensured that when the controller upgrade fails, it can be operated according to the preset retry strategy, and if necessary, the current controller can be skipped to continue the entire upgrade process, which helps to maintain the continuity and efficiency of the entire system upgrade.

[0070] like Figure 2 As shown, Figure 2 For the upgrade retry flow chart, first obtain the controller part number, version, etc., download the upgrade package after verification, and the upgrade retry count of each controller, then trigger the upgrade task, and perform the upgrade steps on n controllers in turn. If the upgrade is successful, the next controller will be upgraded. If the upgrade fails, the controller will be retried to upgrade. When the retry count of the controller overflows, skip the controller and upgrade the next controller until all the controllers in the combined task have been upgraded.

[0071] Furthermore, after the step of upgrading each controller in sequence based on the upgrade information, the method further includes:

[0072] Step A21: Obtain the upgrade status and upgrade results of all vehicle controllers;

[0073] It should be noted that this step is to ensure that the upgrade process of each controller of the vehicle is properly handled and can provide necessary information for subsequent steps. Obtaining the upgrade status and results of all controllers is for unified management and recording, which is essential for maintaining the stability and performance of the vehicle system. By collecting this information, a comprehensive evaluation of the upgrade process can be conducted, and possible problems can be discovered and resolved in a timely manner.

[0074] Step A22: Send the upgrade status and upgrade result to the user end for real-time display.

[0075] It should be noted that the upgrade status and results are sent to the user end in real time to improve transparency and user experience. Users can instantly understand the upgrade status of vehicle controllers, including which controllers have been successfully upgraded and which may require additional attention or intervention. This real-time feedback mechanism enables users to stay informed of the status of the vehicle so that they can respond to user inquiries or concerns in a timely manner during the upgrade process.

[0076] It should be understood that the user end can be a mobile phone or a car display screen.

[0077] In the specific implementation, the upgrade results will be pushed to the mobile phone through TSP to display the upgrade status and results.

[0078] This embodiment provides an automobile OTA combined upgrade method, which responds to an upgrade instruction, obtains upgrade information and preset upgrade retry times of all controllers; upgrades each controller in turn based on the upgrade information; when a controller upgrade fails, retry upgrades the controller based on the preset upgrade retry times corresponding to the controller until the controller upgrade is completed, thereby improving the reliability of OTA upgrades and user experience.

[0079] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 3 , step S10 includes steps S101 to S102:

[0080] Step S101, in response to an upgrade instruction, obtaining upgrade information, the upgrade information including controller information;

[0081] It should be noted that the number of retries for the same upgrade task is fixed and is not flexibly configured according to the actual upgrade situation of each controller. For example, the upgrade of intelligent components such as car computers and TBOX takes a long time, and even if the upgrade fails, it will not affect the controller function. If the number of upgrade retries is configured too much, it will affect the efficiency of this task upgrade and give users the illusion that the upgrade is stuck; however, some CAN controllers upgrade quickly, mostly between 30S and 5min, which is generally caused by the vehicle responsible or the vehicle status. The number of upgrade retries can be appropriately increased to improve the upgrade success rate. Therefore, this strategy avoids the waste of resources caused by unlimited retries, or the missed opportunity for successful upgrade due to insufficient retries, but sets intelligent retries for each controller according to the actual situation.

[0082] In the specific implementation, when the vehicle is powered on and an upgrade task is detected, and the network status, storage space, task validity period, etc. meet the download conditions, the upgrade task will be downloaded;

[0083] In addition to downloading the controller software for this upgrade, other information of this upgrade (number of download retries, number of controller upgrade retries, prerequisites, etc.) is sent to UC-Master through the OTA task when the version is released. UC-Master parses the OTA task package to obtain the installation information, namely the controller information.

[0084] Step S102: configuring the upgrade retry times of each controller based on the controller information to obtain the preset upgrade retry times of all controllers.

[0085] It should be noted that the configuration process sets a reasonable number of retries for each controller based on the historical upgrade success rate, failure reasons, and upgrade duration.

[0086] In a feasible implementation manner, step S102 includes steps A31 to A32:

[0087] Step A31: Obtaining the upgrade duration, historical upgrade data, and historical failure information of each controller according to the controller information;

[0088] It should be noted that this step is to collect key data to gain a deeper understanding of the upgrade process for each controller. Upgrade duration can help determine the time required for the upgrade operation, historical upgrade data can reveal general trends and patterns of upgrade operations, and historical failure information provides information about possible problems that may occur during the upgrade process.

[0089] By analyzing this data, it is possible to identify which controllers may need more attention or if there are specific controllers that experience repeated issues when upgrading. Such analysis is critical to optimizing upgrade strategies and preventing potential upgrade failures.

[0090] Step A32: Based on the upgrade duration, historical upgrade data, and historical failure information, the upgrade retry times of each controller are configured to obtain the preset upgrade retry times of all controllers.

[0091] It should be noted that in this step, the data collected in step A31 is used to configure the number of upgrade retries for each controller. This configuration is based on an assessment of the difficulty and risk of upgrading each controller.

[0092] For example, if a controller's upgrade history shows frequent failures, you might want to set a higher retry count for it. Conversely, if a controller's upgrades usually go smoothly, you might want to set a lower retry count.

[0093] The upgrade duration will also affect the configuration of the number of retries. If the upgrade is expected to take longer, you may need to consider additional time buffers in the retry strategy to avoid unnecessary retries. In this way, you can customize a reasonable retry strategy for each controller to improve the efficiency and success rate of the overall upgrade process.

[0094] It should be understood that the following aspects need to be considered when specifying the number of upgrade retries for each upgrade controller, including upgrade time, historical upgrade data, and historical failure reasons:

[0095] For controllers that take a long time to upgrade, avoid configuring too many retries, which will reduce the upgrade efficiency. Consider the number of times the upgrade was successful in the past, and use this as a reference for configuring the number of retries for this upgrade. Analyze the specific reasons for historical failures, such as server load, hardware problems, etc., so as to set different retry strategies for different reasons.

[0096] It is understandable that during the upgrade process, the system should remain stable to avoid resource exhaustion or system crash due to frequent retries.

[0097] When configuring the upgrade strategy on the OTA management platform, select the vehicle model and controller information for this upgrade, and configure the number of upgrade retries for each controller, as shown in Table 1 below:

[0098] Table 1

[0099]

[0100] This embodiment provides an automobile OTA combined upgrade method, which responds to an upgrade instruction and obtains upgrade information, wherein the upgrade information includes controller information; the upgrade retry times of each controller are configured based on the controller information to obtain a preset upgrade retry times of all controllers, thereby ensuring that when an upgrade instruction is issued, the upgrade retry times can be reasonably configured according to the specific circumstances of each controller, which helps to optimize the upgrade process, reduce system interruption time caused by upgrade failure, and improve the overall upgrade success rate.

[0101] Based on the first and second embodiments of the present application, in the third embodiment of the present application, the same or similar contents as those in the above embodiments can be referred to the above introduction, and will not be described in detail later. Figure 4 , step S20 includes steps S201 to S203:

[0102] Step S201, obtaining a preset upgrade time based on the upgrade instruction, and performing upgrade timing;

[0103] In the specific implementation, the vehicle side sets the appointment task by operating the HMI interface, UC-Slave synchronizes the appointment setting to TBOX, which performs appointment clock maintenance, and TBOX receives and processes it.

[0104] It should be noted that UC-Slave is the control program of the upgraded ECU, which mainly realizes the control of a single ECU or the upgrade object. HMI is an interactive interface used to interact with users. Users can operate the APP on the page to perform OTA detection, download, installation, scheduled installation, release instructions, disclaimer display, disclaimer reading and other functions.

[0105] Step S202, when the timing reaches the preset upgrade time, the vehicle is controlled to be powered on;

[0106] It should be noted that the power-on process refers to providing power to the vehicle's electronic system in order to start the upgrade process. During the power-on process, the system will manage the vehicle's power supply to ensure a stable power supply during the upgrade process.

[0107] In the specific implementation, TBOX maintains the clock timing and attempts to power on the vehicle when the time is reached. After the power-on is successful, the upgrade command is sent to UC-Master.

[0108] Step S203: when the vehicle is powered on, each controller is upgraded in sequence based on the upgrade information.

[0109] It should be noted that after power-on is completed, the vehicle is checked for upgrade conditions, including task validity, installation package decryption and signature verification, controller version information, and prerequisites. After passing the verification, the upgrade program is started, including downloading the upgrade package, transmitting data, flashing the controller, and other steps.

[0110] In a feasible implementation manner, step S203 includes steps A41 to A42:

[0111] Step A41: When the vehicle is powered on, the upgrade condition check is performed on the vehicle, and the upgrade condition check includes task validity check, installation package decryption and signature check, controller version information check and precondition check;

[0112] It should be noted that this step is performed after the vehicle is powered on. The purpose is to ensure that all upgrade conditions are met to avoid problems during the upgrade process. Specific checks include: Task validity check: confirm whether the current upgrade task is still valid and ensure that there are no expired or canceled tasks; Installation package decryption and signature verification: decrypt and verify the signature of the upgrade package to ensure the integrity of the package and the credibility of the source, and prevent malware or damaged packages from affecting the vehicle system; Controller version information check: Check the version information of the current controller to ensure that the upgrade is necessary and the target version is suitable; Precondition check: Confirm whether other relevant conditions are met, such as whether the battery power is sufficient, whether the network connection is stable, etc., to ensure that the upgrade process can proceed smoothly.

[0113] Through these checks, the risk of upgrade failure can be effectively reduced, ensuring that the vehicle is upgraded in a safe state.

[0114] Step A42: When the vehicle upgrade condition verification is passed, each controller is upgraded in sequence based on the upgrade information.

[0115] It should be noted that before UC-Master executes the upgrade action, it needs to pass the task validity, installation package decryption and signature verification, controller version information and prerequisites before starting the controller upgrade.

[0116] It should be understood that after confirming that all upgrade conditions have been passed, the system will start upgrading each controller; this process will be based on the previously collected upgrade information to ensure that each controller is upgraded in a predetermined order; the sequential upgrade method can ensure that after each controller is upgraded, the system can check its status in time to ensure that the upgrade is successful. If a controller has a problem during the upgrade process, measures can be taken immediately to deal with it without affecting the upgrade of other controllers.

[0117] This embodiment provides a vehicle OTA combined upgrade method, which can ensure that the upgrade process of the vehicle controller is orderly and controllable, and minimize the impact on vehicle operation. Each link in the upgrade process has clear verification and monitoring to ensure the smooth progress of the upgrade, significantly improve the success rate and efficiency of OTA upgrades, reduce user troubles and resource waste caused by upgrade failures, and at the same time, optimize user experience and improve the level of vehicle intelligence through intelligent retry management strategies.

[0118] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the automotive OTA combination upgrade method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0119] This application also provides a car OTA combination upgrade device, please refer to Figure 5 , the automobile OTA combined upgrade device comprises:

[0120] An information acquisition module 10, for acquiring upgrade information and preset upgrade retry times of all controllers in response to an upgrade instruction;

[0121] An upgrade module 20, used to upgrade each controller in sequence based on the upgrade information;

[0122] The upgrade retry module 30 is used to perform upgrade retry processing on the controller based on a preset upgrade retry number corresponding to the controller when the controller upgrade fails, until the controller upgrade is completed.

[0123] The automobile OTA combination upgrade device provided by the present application adopts the automobile OTA combination upgrade method in the above embodiment, which can solve the technical problem of low upgrade efficiency of OTA upgrade. Compared with the prior art, the beneficial effects of the automobile OTA combination upgrade device provided by the present application are the same as the beneficial effects of the automobile OTA combination upgrade method provided by the above embodiment, and the other technical features in the automobile OTA combination upgrade device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0124] In one embodiment, the information acquisition module 10 is further used to obtain upgrade information in response to the upgrade instruction, and the upgrade information includes controller information;

[0125] The upgrade retry times of each controller are configured based on the controller information to obtain the preset upgrade retry times of all controllers.

[0126] In one embodiment, the information acquisition module 10 is further used to acquire the upgrade duration, historical upgrade data and historical failure information of each controller according to the controller information;

[0127] The upgrade retry times of each controller are configured based on the upgrade duration, historical upgrade data, and historical failure information to obtain the preset upgrade retry times of all controllers.

[0128] In one embodiment, the upgrade module 20 is further used to obtain a preset upgrade time based on the upgrade instruction and perform upgrade timing;

[0129] When the timing reaches the preset upgrade time, the vehicle is controlled to power on;

[0130] When the vehicle is powered on, each controller is upgraded in sequence based on the upgrade information.

[0131] In one embodiment, the upgrade module 20 is further used to perform upgrade condition verification on the vehicle when the vehicle is powered on, and the upgrade condition verification includes task validity verification, installation package decryption signature verification, controller version information verification and precondition verification;

[0132] When the vehicle upgrade condition verification is passed, each controller is upgraded in sequence based on the upgrade information.

[0133] In one embodiment, the upgrade retry module 30 is further used to determine whether the controller upgrade retry count exceeds the preset upgrade retry count corresponding to the controller after the controller upgrade fails;

[0134] When the number of upgrade retries exceeds the preset number of upgrade retries, the upgrade process of the controller is terminated and the upgrade process of the next controller is executed;

[0135] When the upgrade retry times do not exceed the preset upgrade retry times, the controller continues to be upgraded and retried.

[0136] In one embodiment, the upgrade retry module 30 is further used to obtain the upgrade status and upgrade results of all controllers of the vehicle;

[0137] The upgrade status and upgrade results are sent to the user end for real-time display.

[0138] The present application provides an automobile OTA combination upgrade device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the automobile OTA combination upgrade method in the above-mentioned embodiment one.

[0139] Reference below Figure 6, which shows a schematic diagram of the structure of an automobile OTA combination upgrade device suitable for implementing the embodiment of the present application. The automobile OTA combination upgrade device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The automotive OTA combination upgrade device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0140] like Figure 6 As shown, the automobile OTA combination upgrade device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM: Read Only Memory) 1002 or the program loaded from the storage device 1003 to the random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the automobile OTA combination upgrade device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. The input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the automobile OTA combination upgrade device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows an automobile OTA combination upgrade device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0141] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0142] The automobile OTA combination upgrade device provided by this application adopts the automobile OTA combination upgrade method in the above embodiment, which can solve the technical problem of low upgrade efficiency of OTA upgrade. Compared with the prior art, the beneficial effects of the automobile OTA combination upgrade device provided by this application are the same as the beneficial effects of the automobile OTA combination upgrade method provided by the above embodiment, and the other technical features in the automobile OTA combination upgrade device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0143] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0144] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0145] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the automobile OTA combined upgrade method in the above-mentioned embodiment.

[0146] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0147] The above-mentioned computer-readable storage medium may be included in the automobile OTA combination upgrade device; or it may exist independently without being assembled into the automobile OTA combination upgrade device.

[0148] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the automobile OTA combination upgrade device, the automobile OTA combination upgrade device: responds to the upgrade instruction, obtains the upgrade information and the preset upgrade retry times of all controllers; upgrades each controller in turn based on the upgrade information; when the controller upgrade fails, the controller is retried based on the preset upgrade retry times corresponding to the controller until the controller upgrade is completed.

[0149] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0150] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0151] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0152] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned automobile OTA combined upgrade method, and can solve the technical problem of low upgrade efficiency of OTA upgrade. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the automobile OTA combined upgrade method provided in the above-mentioned embodiment, and will not be repeated here.

[0153] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned automobile OTA combined upgrade method when executed by a processor.

[0154] The computer program product provided by this application can solve the technical problem of low upgrade efficiency of OTA upgrade. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the automobile OTA combined upgrade method provided by the above embodiment, which will not be repeated here.

[0155] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A vehicle OTA combined upgrade method, characterized in that: The automobile OTA combined upgrade method comprises the following steps: In response to the upgrade instruction, obtain upgrade information and preset upgrade retry times of all controllers; Upgrading each of the controllers in sequence based on the upgrade information; When the controller upgrade fails, the controller is retried based on a preset upgrade retry number corresponding to the controller until the controller upgrade is completed.

2. The automobile OTA combined upgrade method according to claim 1, characterized in that: The step of obtaining upgrade information and preset upgrade retry times of all controllers in response to the upgrade instruction includes: In response to the upgrade instruction, acquiring upgrade information, the upgrade information including controller information; The upgrade retry times of each controller are configured based on the controller information to obtain the preset upgrade retry times of all controllers.

3. The automobile OTA combined upgrade method as claimed in claim 2, characterized in that: The step of configuring the upgrade retry times of each controller based on the controller information to obtain the preset upgrade retry times of all controllers includes: Acquire the upgrade duration, historical upgrade data, and historical failure information of each controller according to the controller information; The upgrade retry times of each controller are configured based on the upgrade duration, the historical upgrade data, and the historical failure information to obtain a preset upgrade retry times of all controllers.

4. The automobile OTA combined upgrade method according to claim 1, characterized in that: The step of sequentially upgrading each of the controllers based on the upgrade information comprises: Obtaining a preset upgrade time based on the upgrade instruction, and performing upgrade timing; When the timing reaches the preset upgrade time, the vehicle is controlled to be powered on; When the vehicle is powered on, each of the controllers is upgraded in sequence based on the upgrade information.

5. The automobile OTA combined upgrade method as claimed in claim 4, characterized in that: The step of upgrading each of the controllers in sequence based on the upgrade information when the vehicle is powered on includes: When the vehicle is powered on, the upgrade condition check is performed on the vehicle, and the upgrade condition check includes task validity check, installation package decryption and signature check, controller version information check and precondition check; When the vehicle upgrade condition verification is passed, each of the controllers is upgraded in sequence based on the upgrade information.

6. The automobile OTA combined upgrade method according to claim 1, characterized in that: When the controller upgrade fails, the step of performing an upgrade retry process on the controller based on a preset upgrade retry number corresponding to the controller until the controller upgrade is completed includes: After the controller upgrade fails, determining whether the number of upgrade retries of the controller exceeds a preset number of upgrade retries corresponding to the controller; When the upgrade retry number exceeds the preset upgrade retry number, the upgrade process of the controller is terminated, and the upgrade process of the next controller is executed; When the upgrade retry times do not exceed the preset upgrade retry times, the controller continues to be upgraded and retried.

7. The automobile OTA combined upgrade method according to any one of claims 1 to 6, characterized in that: The method further comprises: Get the upgrade status and results of all controllers in the vehicle; The upgrade status and the upgrade result are sent to the user end for real-time display.

8. An automobile OTA combined upgrade device, characterized in that: The device comprises: An information acquisition module, used to obtain upgrade information and preset upgrade retry times of all controllers in response to an upgrade instruction; An upgrade module, used for upgrading each of the controllers in sequence based on the upgrade information; The upgrade retry module is used to perform upgrade retry processing on the controller based on a preset upgrade retry number corresponding to the controller when the controller upgrade fails, until the controller upgrade is completed.

9. An automobile OTA combined upgrade device, characterized in that: The device comprises: a memory, a processor, and an automobile OTA combination upgrade program stored in the memory and executable on the processor, wherein the automobile OTA combination upgrade program is configured to implement the steps of the automobile OTA combination upgrade method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium stores an automobile OTA combination upgrade program, and when the automobile OTA combination upgrade program is executed by the processor, the steps of the automobile OTA combination upgrade method according to any one of claims 1 to 7 are implemented.

Images