Vehicle OTA upgrade management method and device, electronic equipment and storage medium

Abstract

The invention provides an OTA upgrade management method and device of a vehicle, electronic equipment and a storage medium. The method comprises the following steps: acquiring a multi-branch upgrade route of the vehicle; determining an OTA upgrading strategy from the multi-branch upgrading route based on the vehicle basic information of the to-be-upgraded vehicle; on the basis of the OTA upgrading strategy and the upgrading precondition, managing an OTA upgrading task; the vehicle basic information comprises at least one of a vehicle identification code, ECU basic information, a vehicle model and a current version number of the vehicle. According to the method provided by the invention, the vehicle basic information is determined through at least one of the vehicle identification code, the ECU basic information, the vehicle model and the current version number of the vehicle, and diversified upgrade range determination is realized. Through the vehicle basic information of the to-be-upgraded vehicle, the OTA upgrading strategy is determined from the multi-branch upgrading route, and more efficient, detailed and accurate vehicle OTA upgrading configuration is realized based on the OTA upgrading strategy and the upgrading preconditions, so that accurate pushing is realized, and the vehicle upgrading safety is guaranteed.

Description

Technical Field

[0001] The present invention relates to the technical field of automobiles, and in particular to an OTA upgrade management method, device, electronic device and storage medium for a vehicle. Background Art

[0002] The networking process of automotive component ECUs (Electronic Control Units) is developing rapidly. More and more ECUs support networking communication with terminals, approaching advanced intelligent vehicles, enabling the platform system to remotely obtain various status information of ECUs and remotely diagnose, and OTA remote upgrade provides convenience for the software program iteration of vehicle ECUs. Currently, ECUs are mainly upgraded in batches according to vehicle models.

[0003] However, in the face of an increasing number of dozens of ECUs, and dozens of ECUs containing hundreds of versions, the existing configuration upgrade process is inefficient. Summary of the Invention

[0004] The present invention provides an OTA upgrade management method, device, electronic device and storage medium for a vehicle to solve the defect of low efficiency in the existing configuration upgrade process.

[0005] The present invention provides an OTA upgrade management method for a vehicle, including: Obtaining a multi-branch upgrade route of the vehicle; Determining an OTA upgrade strategy for the to-be-upgraded vehicle from the multi-branch upgrade route based on the vehicle basic information of the to-be-upgraded vehicle; Managing an OTA upgrade task based on the OTA upgrade strategy and upgrade preconditions; The vehicle basic information includes at least one of a vehicle identification code, ECU basic information, vehicle model, and vehicle current version number.

[0006] According to the OTA upgrade management method for a vehicle provided by the present invention, the obtaining of the multi-branch upgrade route of the vehicle includes: Entering the vehicle basic information and a basic upgrade route of the vehicle; Performing version maintenance on the basic upgrade route based on the vehicle basic information to obtain the multi-branch upgrade route.

[0007] According to the OTA upgrade management method for a vehicle provided by the present invention, the managing of the OTA upgrade task based on the OTA upgrade strategy and upgrade preconditions includes: Receiving an upgrade mode selection of the to-be-upgraded vehicle; When the pre-upgrade conditions are met, generate an OTA upgrade task based on the selected upgrade mode and the OTA upgrade policy; Execute the OTA upgrade task and monitor the progress of the OTA upgrade task.

[0008] According to an OTA upgrade management method for a vehicle provided by the present invention, the step of generating an OTA upgrade task based on the selected upgrade mode and the OTA upgrade policy when the pre-upgrade conditions are met includes: Receive a user input operation, where the user input operation includes an input of pre-upgrade conditions and an input of an upgrade mode; When the input of the pre-upgrade conditions is met, generate an OTA upgrade task based on the input of the upgrade mode and the OTA upgrade policy.

[0009] According to an OTA upgrade management method for a vehicle provided by the present invention, the selected upgrade mode includes at least one of a normal mode, a silent mode, a forced mode, and a dynamic mode; The dynamic mode is used to determine the selected upgrade mode from candidate modes based on the vehicle state of the vehicle to be upgraded; The candidate modes include at least two of a normal mode, a silent mode, and a forced mode.

[0010] According to an OTA upgrade management method for a vehicle provided by the present invention, the step of executing the OTA upgrade task and monitoring the progress of the OTA upgrade task includes: Determine the historical OTA upgrade information of the vehicle to be upgraded; Analyze the historical OTA upgrade information to determine an OTA upgrade recommendation for the vehicle to be upgraded; The historical OTA upgrade information includes a historical OTA upgrade policy, a historical OTA upgrade task, and a historical OTA push record; The OTA upgrade recommendation is used to adjust the OTA upgrade task.

[0011] The present invention also provides an OTA upgrade management device for a vehicle, including: An acquisition unit that acquires a multi-branch upgrade route of the vehicle; A policy maintenance unit that determines the OTA upgrade policy of the vehicle to be upgraded from the multi-branch upgrade route based on the vehicle basic information of the vehicle to be upgraded; A task management unit that manages the OTA upgrade task based on the OTA upgrade policy and the pre-upgrade conditions; The vehicle basic information includes at least one of a vehicle identification code, ECU basic information, a vehicle model, and a current vehicle version number.

[0012] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the OTA upgrade management method of the vehicle as described in any one of the above is implemented.

[0013] The present invention also provides a non-transitory computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the OTA upgrade management method of the vehicle as described in any one of the above is implemented.

[0014] The present invention also provides a computer program product, including a computer program. When the computer program is executed by a processor, the OTA upgrade management method of the vehicle as described in any one of the above is implemented.

[0015] The OTA upgrade management method, device, electronic device, and storage medium of the vehicle provided by the present invention determine the vehicle basic information through at least one of the vehicle identification code, ECU basic information, vehicle model, and vehicle current version number, realizing diversified determination of the upgrade scope. In addition, for the vehicle basic information of the vehicle to be upgraded, the OTA upgrade strategy of the vehicle to be upgraded is determined from multiple branch upgrade routes, and the OTA upgrade task is managed based on the OTA upgrade strategy and the upgrade preconditions, realizing a more efficient, detailed, and accurate vehicle OTA upgrade configuration, thereby achieving precise push and ensuring vehicle upgrade safety. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0017] Figure 1 is one of the schematic flowcharts of the OTA upgrade management method of the vehicle provided by the present invention; Figure 2 is another schematic flowchart of the OTA upgrade management method of the vehicle provided by the present invention; Figure 3 is the schematic structural diagram of the OTA upgrade management device of the vehicle provided by the present invention; Figure 4 is the schematic structural diagram of the electronic device provided by the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0018] To make the objectives, technical solutions, and advantages of the present invention clearer, the technical solutions in the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present invention without creative efforts shall fall within the protection scope of the present invention.

[0019] OTA, the full name is "Over-The-Air technology", that is, the over-the-air download technology, which realizes remote management of software through the interface of mobile communication. With the development of vehicle intelligent networking, over-the-air upgrade technology has become an essential function of vehicles, so as to achieve rapid market iteration of sold vehicles, solve market problems, improve the performance of the whole vehicle, and achieve the goal of adding new functions. From the previous distributed ECU vehicle architecture to the current domain controller centralized vehicle architecture and the future central computing unit architecture, multiple software modules that were previously independent of each other are gradually associated and combined into a functional combination. For the update and iteration of the vehicle function version, the previous single or multi-component upgrade solutions are inefficient and no longer adapt to the development of the times on the road of intelligent vehicle networking. The OTA vehicle version upgrade came into being, which can establish a standard vehicle upgrade system, further greatly enrich the user experience, improve the operation and development efficiency of enterprises, and realize the marketability of automotive software. The current vehicle version upgrade mainly upgrades ECUs in batches according to vehicle models.

[0020] However, in the face of the increasing number of ECUs gradually reaching dozens, and dozens of ECUs containing hundreds of versions, the existing configuration upgrade process is inefficient, and there are repetitions and excessive pushes during the upgrade process. To solve this problem, the present invention provides an OTA upgrade management method for vehicles to achieve efficient and accurate upgrade configuration, so as to achieve precise push and ensure the safety of vehicle upgrades. Figure 1 is one of the schematic flowcharts of the OTA upgrade management method for vehicles provided by the present invention, as Figure 1 shown, the method includes: Step 110, obtaining the multi-branch upgrade route of the vehicle; Specifically, a communication connection can be established between the built-in communication module in the vehicle to be upgraded and the cloud vehicle management system to synchronize the vehicle basic information of the vehicle to be upgraded, synchronously obtain the current vehicle version information and store it. Then, multiple upgrade paths can be designed for each ECU of the vehicle according to different vehicle models, configurations, and requirements. For example, cross-version upgrades of the same series can be designed for any ECU; for another example, one-by-one version upgrades of the same series can be designed for any ECU; for another example, cross-series version upgrades can be designed for any ECU, and then the multi-branch upgrade route of the entire vehicle can be obtained.

[0021] It should be noted that the multi-branch upgrade route here can be pre-designed. For example, it can be optimized by managers based on the basic upgrade route.

[0022] Step 120: Based on the vehicle basic information of the vehicle to be upgraded, determine the OTA upgrade strategy of the vehicle to be upgraded from the multi-branch upgrade route. Here, the vehicle basic information includes at least one of vehicle identification code, ECU basic information, vehicle model, and vehicle current version number. Among them, the vehicle identification code can be the VIN code, and the current version number of the vehicle to be upgraded can be determined. The ECU basic information refers to the version and model information of the ECU.

[0023] Specifically, the upgrade scope of the vehicle to be upgraded can be determined through at least one of the vehicle identification code, ECU basic information, vehicle model, and vehicle current version number of the vehicle to be upgraded, realizing the selection of diverse upgrade target scopes. The upgrade scope here can include the ECUs to be upgraded in the vehicle and the corresponding upgrade version information of the ECUs.

[0024] Then, data analysis can be performed on the upgrade scope, and the upgrade route that meets the upgrade scope of the vehicle to be upgraded can be screened from the pre-determined multi-branch upgrade route as the OTA upgrade strategy. It should be noted that the OTA upgrade strategy here also includes information such as upgrade sequence and upgrade time.

[0025] It can be understood that the OTA upgrade strategy obtained here can be regarded as the upgrade result based on big data analysis and algorithm optimization. On this basis, it is possible that the administrator may need to fine-tune the OTA upgrade strategy according to the actual situation. Then, only simple adjustments need to be made to the versions or upgrade objects that do not need to be upgraded, improving the efficiency of vehicle configuration OTA upgrade, and also improving the accuracy of the upgrade strategy, thereby avoiding the problem of repeated and excessive pushing during the upgrade process.

[0026] Step 130: Manage the OTA upgrade task based on the OTA upgrade strategy and upgrade preconditions.

[0027] Here, the upgrade preconditions can refer to the conditions that the vehicle needs to meet before the vehicle performs OTA upgrade. For example, it can be that the battery power of the vehicle is greater than the preset threshold, or the vehicle is powered on but not moving, or the network communication of the vehicle is in a good state. The upgrade preconditions here can be configured based on the user.

[0028] Specifically, the current vehicle status of the vehicle to be upgraded can be compared with the pre-upgrade conditions. When the current vehicle status of the vehicle to be upgraded meets the pre-upgrade conditions, the vehicle can be upgraded according to the OTA upgrade strategy of the vehicle to be upgraded, and the upgrade process can be monitored and pushed, that is, the detailed upgrade progress is displayed and the satisfaction of the current vehicle status and the pre-upgrade conditions of the vehicle is monitored.

[0029] The method provided by the embodiment of the present invention determines the vehicle basic information through at least one of the vehicle identification code, ECU basic information, vehicle model, and vehicle current version number, realizing a diversified determination of the upgrade scope. In addition, the vehicle basic information of the vehicle to be upgraded is used to determine the OTA upgrade strategy of the vehicle to be upgraded from the multi-branch upgrade routes. Based on the OTA upgrade strategy and the pre-upgrade conditions, the OTA upgrade task is managed, realizing a more efficient, detailed, and accurate vehicle OTA upgrade configuration, thereby achieving precise push and ensuring vehicle upgrade safety.

[0030] Based on any of the above embodiments, step 110 includes: Enter the vehicle basic information and the basic upgrade route of the vehicle; Based on the vehicle basic information, perform version maintenance on the basic upgrade route to obtain the multi-branch upgrade route.

[0031] Specifically, a communication connection can be established between the built-in communication module in the vehicle to be upgraded and the cloud vehicle management system, the vehicle basic information of the vehicle to be upgraded is entered, and the current vehicle version information is synchronously obtained and stored. In addition, the basic upgrade route of the vehicle is obtained. The basic upgrade route here can be the upgrade route in which each ECU in the vehicle is upgraded version by version, which is suitable for the upgrade of most vehicles.

[0032] Then, at least one of the vehicle identification code, ECU basic information, vehicle model, and vehicle current version number of the vehicle can be used as the vehicle basic information. Then, through the vehicle basic information, version maintenance can be performed on the basic upgrade route. For example, cross-version upgrades of the same series can be designed for any ECU; for another example, version-by-version upgrades of the same series can be designed for any ECU; for another example, cross-series version upgrades can be designed for any ECU, and then the multi-branch upgrade route of the entire vehicle can be obtained.

[0033] The method provided by the embodiment of the present invention greatly improves the configuration efficiency of the vehicle upgrade strategy by pre-entering the vehicle basic information and the basic upgrade route of the vehicle; and performing version maintenance on the basic upgrade route based on the vehicle basic information to obtain the multi-branch upgrade route.

[0034] Based on any of the above embodiments, step 130 includes: Receive the upgrade mode selection of the vehicle to be upgraded; When the pre - conditions for the upgrade are met, an OTA upgrade task is generated based on the selected upgrade mode and the OTA upgrade strategy. Execute the OTA upgrade task and monitor the progress of the OTA upgrade task.

[0035] Specifically, first, the user's selection of the upgrade mode for the vehicle to be upgraded can be received. When the current vehicle status of the vehicle to be upgraded meets the pre - conditions for the upgrade, an OTA upgrade task is generated for the vehicle to be upgraded according to the selected upgrade mode and the OTA upgrade strategy. Here, the selected upgrade mode includes at least one of a normal mode, a silent mode, a forced mode, and a dynamic mode. The selected upgrade mode can affect the execution mode of the OTA upgrade strategy, and thus affect the overall execution time of the OTA upgrade strategy. Therefore, the OTA upgrade task here refers to the OTA upgrade strategy that conforms to the selected upgrade mode, that is, the OTA upgrade strategy starts to be executed at the time point corresponding to the selected upgrade mode.

[0036] Furthermore, execute the OTA generation task and monitor the progress of the OTA upgrade task. For example, it can list the upgrade records and progress details and perform message pushing.

[0037] The method provided by the embodiments of the present invention, through the selection of the upgrade mode of the vehicle to be upgraded, when the pre - conditions for the upgrade are met, generates an OTA upgrade task based on the selected upgrade mode and the OTA upgrade strategy, realizing the implementation method of OTA upgrade tasks in multiple modes, and improving the diversity and flexibility of OTA upgrades.

[0038] Based on any of the above embodiments, the generating of the OTA upgrade task based on the selected upgrade mode and the OTA upgrade strategy when the pre - conditions for the upgrade are met includes: Receiving a user input operation, where the user input operation includes an input of pre - conditions for the upgrade and an input of the upgrade mode; When the input of the pre - conditions for the upgrade is met, an OTA upgrade task is generated based on the input of the upgrade mode and the OTA upgrade strategy.

[0039] Specifically, when pushing the execution of the OTA upgrade task to the user, a user input operation can be received. Here, the user input operation can include an input of pre - conditions for the upgrade and an input of the upgrade mode. It can be understood that for changing the pre - conditions for the upgrade, the preset power threshold can be modified. For example, the preset power threshold can be changed from 11% to 20%, or from 20% to 11%.

[0040] Then, it is possible to re-judge the current vehicle state of the vehicle to be upgraded. When the pre-upgrade condition input is met, the vehicle to be upgraded is input in the upgrade mode, and an OTA upgrade task is generated according to the OTA upgrade strategy to further improve the flexibility of the vehicle upgrade task.

[0041] It should be noted that during the execution of the OTA upgrade task, for example, after sending the push for executing any OTA upgrade subtask, the pre-upgrade condition input and upgrade mode input of the user for any OTA upgrade subtask are received. Then, when the vehicle meets the pre-upgrade condition input, the remaining OTA upgrade subtasks to be executed are executed in the mode of input in the upgrade mode. In addition, the satisfaction of the pre-upgrade conditions can be displayed to facilitate troubleshooting the reasons for the vehicle not being upgraded. The upgrade progress of each OTA upgrade subtask is displayed. Among them, the historical upgrade records of the corresponding parts or vehicles can be expanded and viewed, including the software version iteration records through non-OTA remote upgrade means.

[0042] Thus, according to the vehicle upgrade environment, relevant configurations such as pre-upgrade conditions and upgrade modes can be dynamically switched, improving the security and reliability of the vehicle's OTA upgrade.

[0043] Based on any of the above embodiments, the upgrade mode selection includes at least one of a normal mode, a silent mode, a forced mode, and a dynamic mode; The dynamic mode is used to determine the upgrade mode selection from the candidate modes based on the vehicle state of the vehicle to be upgraded; The candidate modes include at least two of a normal mode, a silent mode, and a forced mode.

[0044] Specifically, the upgrade mode selection includes at least one of a normal mode, a silent mode, a forced mode, and a dynamic mode. Among them, the normal mode can be used to perform OTA upgrade and push according to the OTA upgrade strategy on the basis of meeting the pre-upgrade conditions. The silent mode can be used to perform OTA upgrade according to the OTA upgrade strategy on the basis of meeting the pre-upgrade conditions, and no push is performed during the upgrade process. The forced mode can be used to directly perform OTA upgrade and push according to the OTA upgrade strategy without meeting the pre-upgrade conditions. The dynamic mode is used to determine the upgrade mode selection from the candidate modes based on the vehicle state of the vehicle to be upgraded, that is, according to the vehicle state of the vehicle, the upgrade mode selection corresponding to the vehicle state of the vehicle is determined, realizing a more flexible vehicle OTA upgrade.

[0045] Based on any of the above embodiments, executing the OTA upgrade task and monitoring the progress of the OTA upgrade task includes: Determining the historical OTA upgrade information of the vehicle to be upgraded; Analyze the historical OTA upgrade information to determine the OTA upgrade suggestions for the vehicle to be upgraded; The historical OTA upgrade information includes historical OTA upgrade strategies, historical OTA upgrade tasks, and historical OTA push records; The OTA upgrade suggestions are used to adjust the OTA upgrade tasks.

[0046] Specifically, during the execution of the OTA upgrade task, based on the vehicle basic information of the vehicle to be upgraded and the statistical time period, the historical OTA upgrade strategies, historical OTA upgrade tasks, and historical OTA push records of the vehicle to be upgraded within the statistical time period can be screened from the historical OTA upgrade information of all vehicles to obtain the historical OTA upgrade information of the vehicle to be upgraded. Then, analyze the existing operation risks, push risks, etc. in the historical OTA upgrade information to obtain the OTA upgrade suggestions for the vehicle to be upgraded. The OTA upgrade suggestions here can be suggestions such as suspending the upgrade. When the system suggestions are adopted, the OTA upgrade tasks can be modified based on the administrator's confirmation of this OTA upgrade suggestion, and the modification details of this time can be recorded.

[0047] The method provided by the embodiments of the present invention analyzes the historical OTA upgrade strategies, historical OTA upgrade tasks, and historical OTA push records, provides more statistical perspective analysis, uses the OTA upgrade suggestions as a reference, gives suggestions and corrections to the current OTA upgrade management, so as to improve the security and reliability of the OTA upgrade.

[0048] Based on any of the above embodiments, Figure 2 is the second flow diagram of the OTA upgrade management method for vehicles provided by the present invention. As Figure 2 shown, the method includes: information entry, version maintenance, strategy maintenance, task maintenance, push monitoring, and statistical analysis. Among them, in the information entry stage, the vehicle information is synchronized through the vehicle management system, the current vehicle version information is synchronously obtained and stored. In addition, synchronizing the off-line vehicle information of the vehicle and storing the vehicle version is faster and more accurate, which is convenient for subsequent data analysis.

[0049] In the version maintenance stage, the administrator maintains and supplements the new version, and maintains the upgrade routes of multiple branch versions. For example, dozens of ECUs of the vehicle are named A, B, C..., and the upgrade routes of multiple branch versions can be (A1 to An, B1 to Bn...).

[0050] Next, in the strategy maintenance stage, the vehicle upgrade scope can be selected. Specifically, single / multi-selection can be performed through conditions such as vehicle (VIN code), ECU, vehicle model, and version number to determine the vehicle upgrade scope. Then, the system generates strategies according to the vehicle upgrade scope and the upgrade routes of multiple branch versions.

[0051] Furthermore, during the task maintenance phase, an upgrade mode can be configured through preconditions and upgrade modes, that is, one upgrade mode can be selected from the normal mode, silent mode, forced mode, and dynamic mode. Then, the system generates a task.

[0052] Next, during the push monitoring phase, the upgrade task is managed. Specifically, the preconditions and mode settings are adjusted automatically or manually. Then, during the task maintenance phase, the system-generated task is updated according to the adjusted preconditions and mode settings. Next, the adjustment situation, upgrade records, and upgrade progress are listed in detail and presented in a well-organized manner. Finally, the system generates a push record.

[0053] In addition, during the statistical analysis phase, statistics and analysis can be performed based on multi-condition filtering, presenting statistical tables and analysis results, and providing suggestions. Then, the management personnel confirm the feasibility of the analysis suggestions and decide whether to adopt the automatic adjustment by the system.

[0054] Based on any of the above embodiments, Figure 3 is a schematic structural diagram of the OTA upgrade management device for a vehicle provided by the present invention, as Figure 3 shown, the device includes: An acquisition unit 310 that acquires the multi-branch upgrade route of the vehicle; A policy maintenance unit 320 that determines the OTA upgrade policy of the vehicle to be upgraded from the multi-branch upgrade route based on the vehicle basic information of the vehicle to be upgraded; A task management unit 330 that manages the OTA upgrade task based on the OTA upgrade policy and upgrade preconditions; The vehicle basic information includes at least one of a vehicle identification code, ECU basic information, vehicle model, and vehicle current version number.

[0055] The device provided by the embodiment of the present invention determines the vehicle basic information through at least one of a vehicle identification code, ECU basic information, vehicle model, and vehicle current version number, realizing a diversified determination of the upgrade scope. In addition, based on the vehicle basic information of the vehicle to be upgraded, the OTA upgrade policy of the vehicle to be upgraded is determined from the multi-branch upgrade route, and the OTA upgrade task is managed based on the OTA upgrade policy and upgrade preconditions, realizing a more efficient, detailed, and accurate vehicle OTA upgrade configuration, thereby achieving precise push and ensuring vehicle upgrade safety.

[0056] Based on any of the above embodiments, the acquisition unit is specifically configured to: Enter the vehicle basic information and the basic upgrade route of the vehicle; Based on the vehicle basic information, perform version maintenance on the basic upgrade route to obtain the multi-branch upgrade route.

[0057] Based on any of the above embodiments, the task management unit is specifically configured to: Receive the upgrade mode selection of the vehicle to be upgraded; When the pre-upgrade conditions are met, generate an OTA upgrade task based on the upgrade mode selection and the OTA upgrade policy; Execute the OTA upgrade task and monitor the progress of the OTA upgrade task.

[0058] Based on any of the above embodiments, the task management unit is also specifically configured to: Receive user input operations, where the user input operations include pre-upgrade condition input and upgrade mode input; When the pre-upgrade condition input is met, generate an OTA upgrade task based on the upgrade mode input and the OTA upgrade policy.

[0059] Based on any of the above embodiments, the upgrade mode selection includes at least one of a normal mode, a silent mode, a forced mode, and a dynamic mode; The dynamic mode is used to determine the upgrade mode selection from candidate modes based on the vehicle state of the vehicle to be upgraded; The candidate modes include at least two of a normal mode, a silent mode, and a forced mode.

[0060] Based on any of the above embodiments, the task management unit is also specifically configured to: Determine the historical OTA upgrade information of the vehicle to be upgraded; Analyze the historical OTA upgrade information to determine the OTA upgrade suggestions for the vehicle to be upgraded; The historical OTA upgrade information includes a historical OTA upgrade policy, a historical OTA upgrade task, and a historical OTA push record; The OTA upgrade suggestions are used to adjust the OTA upgrade task.

[0061] Figure 4 Illustrates a schematic diagram of the physical structure of an electronic device, as Figure 4As shown in the figure, the electronic device may include: a processor 410, a communications interface 420, a memory 430, and a communication bus 440. Among them, the processor 410, the communications interface 420, and the memory 430 complete communication with each other through the communication bus 440. The processor 410 may call the logical instructions in the memory 430 to execute the OTA upgrade management method for vehicles, and this method includes: obtaining the multi-branch upgrade route of the vehicle; determining the OTA upgrade strategy for the vehicle to be upgraded from the multi-branch upgrade route based on the vehicle basic information of the vehicle to be upgraded; managing the OTA upgrade task based on the OTA upgrade strategy and the preconditions for upgrade; the vehicle basic information includes at least one of vehicle identification code, ECU basic information, vehicle model, and vehicle current version number.

[0062] In addition, when the logical instructions in the above-mentioned memory 430 can be implemented in the form of software functional units and sold or used as an independent product, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks, or optical discs that can store program codes.

[0063] On the other hand, the present invention also provides a computer program product. The computer program product includes a computer program. The computer program can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the OTA upgrade management method for vehicles provided by the above-mentioned various methods. This method includes: obtaining the multi-branch upgrade route of the vehicle; determining the OTA upgrade strategy for the vehicle to be upgraded from the multi-branch upgrade route based on the vehicle basic information of the vehicle to be upgraded; managing the OTA upgrade task based on the OTA upgrade strategy and the preconditions for upgrade; the vehicle basic information includes at least one of vehicle identification code, ECU basic information, vehicle model, and vehicle current version number.

[0064] In another aspect, the present invention also provides a non-transitory computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the OTA upgrade management method for a vehicle provided by the above-mentioned various methods. The method includes: obtaining a multi-branch upgrade route of the vehicle; determining an OTA upgrade strategy for the vehicle to be upgraded from the multi-branch upgrade route based on the vehicle basic information of the vehicle to be upgraded; managing an OTA upgrade task based on the OTA upgrade strategy and pre-upgrade conditions; the vehicle basic information includes at least one of a vehicle identification code, ECU basic information, a vehicle model, and a current vehicle version number.

[0065] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative effort.

[0066] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course also by hardware. Based on such an understanding, the essence of the above technical solution, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disc, etc., and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0067] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some of the technical features. And these modifications 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.

Claims

1. A vehicle OTA upgrade management method, characterized in that: include: Get multi-branch upgrade routes for vehicles; Based on the basic vehicle information of the vehicle to be upgraded, determining the OTA upgrade strategy of the vehicle to be upgraded from the multi-branch upgrade route; Manage OTA upgrade tasks based on the OTA upgrade strategy and upgrade preconditions; The vehicle basic information includes at least one of a vehicle identification code, ECU basic information, a vehicle model, and a current version number of the vehicle.

2. The vehicle OTA upgrade management method according to claim 1, characterized in that: The multi-branch upgrade route for obtaining a vehicle includes: Enter the basic vehicle information and basic upgrade route of the vehicle; Based on the basic vehicle information, version maintenance is performed on the basic upgrade route to obtain the multi-branch upgrade route.

3. The vehicle OTA upgrade management method according to claim 1, characterized in that: The managing the OTA upgrade task based on the OTA upgrade strategy and upgrade preconditions includes: receiving an upgrade mode selection of the vehicle to be upgraded; When the upgrade precondition is met, generating an OTA upgrade task based on the upgrade mode selection and the OTA upgrade strategy; Execute the OTA upgrade task and monitor the progress of the OTA upgrade task.

4. The vehicle OTA upgrade management method according to claim 3, characterized in that: The step of generating an OTA upgrade task based on the upgrade mode selection and the OTA upgrade strategy when the upgrade precondition is met includes: Receiving user input operations, wherein the user input operations include upgrade precondition input and upgrade mode input; When the upgrade precondition input is met, an OTA upgrade task is generated based on the upgrade mode input and the OTA upgrade strategy.

5. The vehicle OTA upgrade management method according to claim 4, characterized in that: The upgrade mode selection includes at least one of a normal mode, a silent mode, a forced mode and a dynamic mode; The dynamic mode is used to determine the upgrade mode selection from candidate modes based on the vehicle state of the vehicle to be upgraded; The candidate modes include at least two of a normal mode, a silent mode, and a forced mode.

6. The vehicle OTA upgrade management method according to any one of claims 3 to 5, characterized in that: The executing the OTA upgrade task and monitoring the progress of the OTA upgrade task includes: Determine the historical OTA upgrade information of the vehicle to be upgraded; Analyze the historical OTA upgrade information to determine OTA upgrade suggestions for the vehicle to be upgraded; The historical OTA upgrade information includes historical OTA upgrade strategies, historical OTA upgrade tasks, and historical OTA push records; The OTA upgrade suggestion is used to adjust the OTA upgrade task.

7. A vehicle OTA upgrade management device, characterized in that: include: Get the unit and get the multi-branch upgrade route of the vehicle; A strategy maintenance unit, based on basic vehicle information of the vehicle to be upgraded, determines an OTA upgrade strategy of the vehicle to be upgraded from the multi-branch upgrade route; A task management unit, which manages OTA upgrade tasks based on the OTA upgrade strategy and upgrade preconditions; The vehicle basic information includes at least one of a vehicle identification code, ECU basic information, a vehicle model, and a current version number of the vehicle.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the OTA upgrade management method for the vehicle as described in any one of claims 1 to 6 is implemented.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the OTA upgrade management method for a vehicle as described in any one of claims 1 to 6 is implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the OTA upgrade management method for a vehicle as described in any one of claims 1 to 6 is implemented.

Images