Vehicle software upgrading method and device based on OTA and computer equipment

Abstract

The invention relates to the technical field of vehicle software upgrading, in particular to an OTA-based vehicle software upgrading method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: determining a current whole vehicle software version of a vehicle according to an effective node of a newly added vehicle software part number in a vehicle software list; acquiring a unique identifier of the current whole vehicle software version; acquiring vehicle file data according to the unique identifier; according to the vehicle file data, analyzing whether there is an inevitably upgraded version between the current whole vehicle software version and a target whole vehicle software version, and obtaining an analysis result; and determining a software upgrading scheme of the vehicle according to the analysis result. By adopting the method, the error rate can be reduced under the condition of vehicle cross-version upgrading.

Description

Technical Field

[0001] The present application relates to the technical field of vehicle software upgrade, and in particular to a vehicle software upgrade method, apparatus, computer equipment, computer-readable storage medium and computer program product based on OTA. Background Art

[0002] At present, in the field of new energy vehicles, OEMs push software updates to the vehicle side through OTA to implement new functions or solve after-sales problems. After releasing multiple software versions, the software versions of vehicles on the market will be uneven. When the OEM launches a new round of OTA activities, it may face two problems: 1. The software version on the vehicle side is higher than the software version to be pushed. If software updates continue to be pushed to users, the user's vehicle software version will be rolled back, causing vehicle malfunctions and even damage to the vehicle hardware; 2. Due to software compatibility and other reasons, some vehicles cannot be directly upgraded to the target version, but must first be upgraded to a certain intermediate version before continuing to upgrade the target version. If the specified version is skipped and the target version is upgraded directly, it may cause vehicle malfunctions or hardware damage, causing irreparable losses and leading to batch market accidents.

[0003] The current upgrade scheme mainly involves manually comparing the vehicle version with the target version, or manually determining whether there is an intermediate version that must be upgraded. However, these methods require manpower to identify vehicles with the required version, resulting in a waste of human resources, involving a large number of personnel, complex usage scenarios, and the software version number is prone to maintenance errors; secondly, for vehicles that must upgrade the required version before upgrading the target version, a large amount of manual intervention is still required, and the risk of error still exists.

[0004] Therefore, there is an urgent need for an OTA-based vehicle software upgrade method, apparatus, computer equipment, computer-readable storage medium and computer program product that can reduce the error rate when the vehicle is upgraded across versions. Summary of the invention

[0005] Based on this, it is necessary to provide an OTA-based vehicle software upgrade method, device, computer equipment, computer-readable storage medium and computer program product that can reduce the error rate when the vehicle is upgraded across versions to address the above technical problems.

[0006] In a first aspect, the present application provides a vehicle software upgrade method based on OTA, comprising:

[0007] Determine the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list;

[0008] Obtaining a unique identifier for the current vehicle software version;

[0009] Obtain vehicle file data according to the unique identifier;

[0010] Analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version according to the vehicle file data, and obtain an analysis result;

[0011] A software upgrade plan for the vehicle is determined based on the analysis results.

[0012] In one embodiment, before determining the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list, the method further includes:

[0013] When the software information of the vehicle control system is changed, a vehicle software part number is created and added to the vehicle software list.

[0014] In one embodiment, determining the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list includes:

[0015] Associating the effective node of the newly added vehicle software part number in the vehicle software list with the date;

[0016] Extracting a set of software part number data at different date stages from the vehicle software list by using the effective node after the associated date;

[0017] The current vehicle software version of the vehicle is determined based on the software part number data set.

[0018] In one embodiment, determining a software upgrade plan for the vehicle according to the analysis result includes:

[0019] In the case where there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, a dependency relationship between the historical vehicle software version and the target vehicle software version is established, and a prompt message is sent to prioritize the upgrade of the necessary upgrade version.

[0020] In one embodiment, determining a software upgrade plan for the vehicle according to the analysis result includes:

[0021] In the case that there is no required upgrade version between the current vehicle software version and the target vehicle software version, the current vehicle software version is upgraded to the target vehicle software version by using the over-the-air download method OTA.

[0022] In one embodiment, after determining the vehicle software upgrade solution according to the analysis result, the method further includes:

[0023] After the vehicle software is successfully upgraded, the unique identifier of the target vehicle software version is transmitted back to the vehicle file data.

[0024] In a second aspect, the present application also provides a vehicle software upgrade device based on OTA, comprising:

[0025] A version determination module, used to determine the current vehicle software version of the vehicle according to the effective node of the vehicle software part number newly added in the vehicle software list;

[0026] An acquisition module, used to acquire a unique identifier of the current vehicle software version;

[0027] The acquisition module is further used to acquire vehicle file data according to the unique identifier;

[0028] An analysis module is used to analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version according to the vehicle file data, and obtain an analysis result;

[0029] A solution determination module is used to determine a vehicle software upgrade solution based on the analysis results.

[0030] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0031] Determine the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list;

[0032] Obtaining a unique identifier for the current vehicle software version;

[0033] Obtain vehicle file data according to the unique identifier;

[0034] Analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version according to the vehicle file data, and obtain an analysis result;

[0035] A software upgrade plan for the vehicle is determined based on the analysis results.

[0036] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0037] Determine the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list;

[0038] Obtaining a unique identifier for the current vehicle software version;

[0039] Obtain vehicle file data according to the unique identifier;

[0040] Analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version according to the vehicle file data, and obtain an analysis result;

[0041] A software upgrade plan for the vehicle is determined based on the analysis results.

[0042] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0043] Determine the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list;

[0044] Obtaining a unique identifier for the current vehicle software version;

[0045] Obtain vehicle file data according to the unique identifier;

[0046] Analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version according to the vehicle file data, and obtain an analysis result;

[0047] A software upgrade plan for the vehicle is determined based on the analysis results.

[0048] The above-mentioned OTA-based vehicle software upgrade method, device, computer equipment, computer-readable storage medium and computer program product determine the current vehicle software version of the vehicle through the effective node of the newly added vehicle software part number in the vehicle software list, ensuring the accurate grasp of the vehicle software version status. Obtaining the unique identifier of the current vehicle software version helps to accurately identify and manage the status of the vehicle software, and provides a reliable basis for subsequent version analysis and upgrades. Using vehicle archive data, it automatically analyzes whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, reducing the need for manual comparison and reducing the error rate. According to the results of the automated analysis, the vehicle's software upgrade plan is intelligently determined to avoid the risk of vehicle function abnormality or hardware damage due to manual judgment errors. Through the automated and intelligent upgrade process, the reliance on human resources is reduced, and the cost and error risk caused by human resource investment are reduced. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0050] Figure 1 FIG. 1 is an application environment diagram of a vehicle software upgrade method based on OTA in one embodiment;

[0051] Figure 2 A schematic diagram of a process of a vehicle software upgrade method based on OTA in one embodiment;

[0052] Figure 3 It is a flowchart of a vehicle software upgrade method based on OTA in another embodiment;

[0053] Figure 4 is a structural block diagram of a vehicle software upgrade device based on OTA in one embodiment;

[0054] Figure 5 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0056] The vehicle software upgrade method based on OTA provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown, the terminal 102 communicates with the server 104 through a network. The data storage system can store data that the server 104 needs to process. The data storage system can be integrated on the server 104, or placed on the cloud or other network servers.

[0057] Server 104 determines the current vehicle software version of the vehicle based on the effective node of the newly added vehicle software part number in the vehicle software list; obtains the unique identifier of the current vehicle software version; obtains the vehicle file data based on the unique identifier; analyzes whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version based on the vehicle file data, and obtains the analysis result; determines the vehicle software upgrade plan based on the analysis result.

[0058] Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.

[0059] In an exemplary embodiment, Figure 2 As shown, a vehicle software upgrade method based on OTA is provided, and the method is applied to Figure 1 The server in the example is used to illustrate, including the following steps S202 to S210. Among them:

[0060] Step S202, determining the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list.

[0061] Specifically, before step S202, SWBOM needs to be built: SWBOM (Software Bill of Materials) is a collection of all software part numbers in the entire life cycle of a vehicle model. Each part number has a corresponding effective node (EventIn) and an invalid node (EventOut). The vehicle software inventory is a list that records all software components of the vehicle and their versions. It may include detailed information on software such as operating systems, drivers, and applications. Each software component has a unique identifier in the inventory, namely the part number. This part number is used to track and identify specific software components.

[0062] The effective node refers to the time point or condition when the software part number is officially adopted and becomes effective in the vehicle software system. This can be the time when the software is released, the time when the installation is completed, or the time when it is automatically activated after meeting certain conditions.

[0063] By checking the effective nodes of each software part number in the vehicle software list, the software version currently installed and running on the vehicle can be determined. The vehicle software version is usually a combination of multiple software component versions, and the version of each component together defines the software status of the vehicle. Correctly determining the current software version of the vehicle is essential for effective software management and subsequent upgrades. It ensures the consistency and compatibility of vehicle software and is the basis for developing upgrade plans and solving software-related problems.

[0064] Step S204, obtaining the unique identifier of the current vehicle software version.

[0065] Specifically, the vehicle software version refers to the collection of all relevant software components on the vehicle, including operating systems, drivers, applications, etc., which together constitute the vehicle's software environment. For each software version, there is a unique identifier, usually a specific code or digital sequence, which is used to distinguish different software versions. Obtaining the unique identifier of the current vehicle software version means retrieving the unique code representing the currently installed software version from the vehicle's system. This process can be completed automatically through the vehicle's diagnostic system or vehicle infotainment system, usually involving connecting to the vehicle's communication interface (such as OBD-II) and sending specific query instructions.

[0066] The unique identifier is used in vehicle software management, version control, OTA upgrades, etc. to ensure that the vehicle's software status can be accurately identified, tracked and updated.

[0067] Step S206, obtaining vehicle file data according to the unique identifier.

[0068] Specifically, the unique identifier is usually a vehicle's software version number or vehicle identification number (VIN), which serves as the key to query vehicle file data. Vehicle file data usually includes multi-dimensional data such as basic vehicle information, maintenance records, insurance information, and violation records. Through the vehicle file management system or related vehicle information platform, the unique identifier is used to retrieve and query the detailed file data of the vehicle. The acquired vehicle file data may be scattered in different systems and need to be integrated to form a system for comprehensive vehicle management. It is used in various links such as vehicle scheduling, maintenance, and scrapping to provide decision support and ensure the timeliness and accuracy of information.

[0069] Step S208, analyzing whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version based on the vehicle file data, and obtaining an analysis result.

[0070] Specifically, the vehicle file data contains the basic information of the vehicle, maintenance records, software version history, etc. These data are the basis for analyzing the software version upgrade path. A system is needed to manage the vehicle's software version, including recording the detailed information of each version and the dependencies between versions. By analyzing the vehicle's current software version and the target version, determine whether there are intermediate versions that must be passed. This usually involves considerations of vehicle configuration and software and hardware compatibility. When determining the upgrade path, it is necessary to evaluate the impact of each version on the vehicle system to ensure that the upgrade does not introduce security risks or affect the normal operation of the vehicle. Based on the above analysis, a report is generated to indicate whether there are necessary versions and provide specific steps and precautions for the upgrade.

[0071] Step S210, determining a vehicle software upgrade plan based on the analysis results.

[0072] Specifically, first, the analysis results provide information on whether there are necessary upgrade versions between vehicle software versions, as well as other factors that may affect the upgrade, such as compatibility, security, etc. Based on the analysis results, a detailed upgrade plan is formulated, including selecting the upgrade path, determining the upgrade sequence and time point, and evaluating the required resources and potential risks. The upgrade plan needs to ensure that the new software is compatible with the vehicle's hardware and other software components to avoid system instability or functional abnormalities caused by version mismatch.

[0073] In the above-mentioned OTA-based vehicle software upgrade method, the current vehicle software version of the vehicle is determined by the effective node of the newly added vehicle software part number in the vehicle software list, ensuring the accurate grasp of the vehicle software version status. Obtaining the unique identifier of the current vehicle software version helps to accurately identify and manage the status of the vehicle software, and provides a reliable basis for subsequent version analysis and upgrades. Using vehicle archive data, it is automatically analyzed whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, reducing the need for manual comparison and reducing the error rate. According to the results of the automated analysis, the vehicle's software upgrade plan is intelligently determined to avoid the risk of vehicle malfunction or hardware damage due to manual judgment errors. Through the automated and intelligent upgrade process, the reliance on human resources is reduced, and the cost and error risk caused by human resource investment are reduced.

[0074] In an exemplary embodiment, before determining the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list, the method further includes:

[0075] In the event that the software information of the vehicle control system is changed, a vehicle software part number is created and added to the vehicle software list.

[0076] Specifically, when the software information of the vehicle control system (such as ECU firmware, application programs, etc.) changes, it needs to be monitored and recorded. For each software change, a new vehicle software part number is created. This part number is a unique identifier used to track and manage software changes. The newly created software part number is added to the vehicle software inventory. The vehicle software inventory is a database or document that records all the software components and versions of the vehicle.

[0077] In this embodiment, through this process, it can be ensured that every change of the vehicle software is systematically recorded and managed, providing accurate data support for vehicle maintenance, upgrades and problem solving. At the same time, it ensures the accuracy and timeliness of vehicle software version updates and avoids potential risks caused by inconsistent software versions.

[0078] In an exemplary embodiment, Figure 3 As shown, according to the effective node of the newly added vehicle software part number in the vehicle software list, the current vehicle software version of the vehicle is determined, including:

[0079] Step S302, associating the effective node of the newly added vehicle software part number in the vehicle software list with the date;

[0080] Step S304, using the effective node after the associated date, extracting the software part number data set of different date stages from the vehicle software list;

[0081] Step S306, determining the current vehicle software version of the vehicle according to the software part number data set.

[0082] Specifically, whenever a vehicle software part number is added to the vehicle software list, this part number will have a corresponding effective node, which is usually a specific date or event, marking the start of the part number. This effective node is associated with a specific date to ensure that each part number has a clear effective time point, so that the history and current status of software changes can be tracked. Using the effective node associated with the date, the software part numbers that are effective at different date stages can be extracted from the vehicle software list. This means that the software version that should be running on the vehicle on a specific date or time period can be obtained. Based on the extracted software part number data set, the vehicle software version of the vehicle on a specific date can be determined. The vehicle software version is defined by all related ECU software versions and reflects the software configuration status of the vehicle at a specific point in time. When it is necessary to trace back the historical version of the vehicle software, the software part number data set of the historical date can be extracted by the same method to determine the software version of the vehicle at the historical time point.

[0083] In this embodiment, through this process, the version of the vehicle software can be accurately managed to ensure the consistency and maintainability of the software throughout the life cycle of the vehicle.

[0084] In an exemplary embodiment, determining a vehicle software upgrade solution based on the analysis result includes:

[0085] In the case where there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, a dependency relationship between the historical vehicle software version and the target vehicle software version is established, and a prompt message is sent to prioritize the necessary upgrade version.

[0086] Specifically, all upgrade paths between the current vehicle software version and the target vehicle software version are analyzed to identify whether there are any necessary intermediate versions. In the software management system, clear dependencies are established between the historical vehicle software versions and the target vehicle software versions. This indicates that certain versions must be installed before the target version is reached. The system automatically generates prompt information to inform users and maintenance personnel that there are necessary upgrade versions and emphasizes the need to prioritize the upgrade of these necessary versions. If there are multiple necessary versions, determine their upgrade order so that they can be upgraded in the correct order. Send notifications to users through the vehicle information system, mobile application or other communication channels, clearly indicating the version that needs to be upgraded first, and provide details and instructions for the upgrade. Create an upgrade task in the vehicle management system, including the upgraded software version, the target vehicle group, the time frame for the upgrade, and any specific user instructions.

[0087] In this embodiment, through this process, the orderly progress of vehicle software upgrades can be ensured, technical risks can be reduced, and user satisfaction can be improved. At the same time, the vehicle can be ensured to maintain optimal performance and safety throughout the upgrade process.

[0088] In an exemplary embodiment, determining a vehicle software upgrade solution based on the analysis result includes:

[0089] When there is no required upgrade version between the current vehicle software version and the target vehicle software version, the current vehicle software version is upgraded to the target vehicle software version using OTA (Over-the-Air) download.

[0090] Specifically, first confirm that there is no intermediate version between the current vehicle software version and the target version that must be upgraded first. This means that the vehicle can be upgraded directly from the current version to the target version. Before upgrading, it is necessary to ensure that the target software version is compatible with the vehicle's hardware and other software components to avoid functional anomalies or system instability after the upgrade. According to the current status of the vehicle and the target version requirements, a detailed OTA upgrade plan is formulated, including the upgrade schedule, the required network bandwidth, and possible user operations.

[0091] Then, generate an upgrade package for the target software version and test it thoroughly to ensure the integrity and functionality of the upgrade package. Ensure that the OTA system can handle the upgrade task, including allocating server resources, network resources, and preparing for system monitoring and logging. Notify users in advance of the upcoming upgrade, including the upgrade time, estimated duration, precautions during the upgrade, etc., through vehicle information systems, emails, mobile applications, etc. Distribute the upgrade package to the target vehicle through the OTA system. This is usually done when the vehicle is connected to the Internet, which may be when the vehicle is parked or at a time specified by the user.

[0092] In this embodiment, through this process, the smooth progress of the vehicle software upgrade can be ensured, while ensuring the performance of the vehicle and the user experience. OTA upgrade provides an efficient and user-friendly upgrade method, reducing the need for users to upgrade in stores and improving upgrade efficiency.

[0093] In an exemplary embodiment, after determining the software upgrade plan for the vehicle according to the analysis result, the method further includes:

[0094] After the vehicle software is successfully upgraded, the unique identifier of the target vehicle software version is transmitted back to the vehicle file data.

[0095] Specifically, ensure that the vehicle software upgrade has been successfully completed. By sending back the identifier of the target version, the software version currently running on the vehicle can be confirmed. Update the software version information recorded in the vehicle file to ensure that the vehicle's electronic file reflects the actual software configuration of the current vehicle. Provide a record of the vehicle's software version history to facilitate tracking the change process and status of the vehicle software. Complete the closed loop of the OTA upgrade process, from upgrade push to version confirmation, and then to data update, to form a complete management and feedback mechanism. In the case where the software upgrade may involve security patches, the return of the version identifier ensures that vehicle safety is enhanced.

[0096] In this embodiment, through this process, each update of the vehicle software can be properly recorded and managed, providing important data support for the full life cycle management of the vehicle.

[0097] The most detailed embodiment of this application is:

[0098] 1. Build SWBOM and extract the vehicle software version through EventIn:

[0099] When the software of an ECU (electronic control unit) changes, a new part number is created and built into the SWBOM (vehicle software bill of materials). SWBOM is a collection of software part numbers that have existed in a vehicle model throughout its life cycle. Each part number has a corresponding effective node (EventIn) and an invalid node (Eventout). EventIn and Eventout are both associated with dates. The BOM data extracted through EventIn that takes effect on different dates is called VSV (vehicle software version).

[0100] EventIn and Eventout examples:

[0101] EventIn 24RC01 24RC01 Bugfix 24RC02 24RC02 Bugfix 24RC03 …… …… Related Date 20240101 20240115 20240201 20240215 20240301 …… …… EventOut 24RC01 24RC01 Bugfix 24RC02 24RC02 Bugfix 24RC03 …… UP Related Date 20240101 20240115 20240201 20240215 20240301 …… ∞

[0102] Example of how to extract the vehicle software version:

[0103] After associating with the date, EventIn can be used to extract the effective BOM lines of different stages. The set of effective BOM lines in the current stage software BOM extracted by EventIn is called the vehicle software version of the current stage, that is, VSV.

[0104] Example:

[0105]

[0106]

[0107] The above table is a simplified software BOM. At this time, 24RC03 is used to extract valid BOM rows. The extracted set is [Part A', Part B, Part C, Part D].

[0108] 2.VSVID generation rules:

[0109] After completing the VSV extraction, the TC system assigns a VSVID (a unique identification code for the vehicle software version) to the VSV version to characterize the software maturity, version, release time and other attributes of the VSV version.

[0110] The composition rules of VSVID are:

[0111] EventIn associated date Major version number Minor version number release date 8-bit encoding 2-digit code 2-digit code 8-bit encoding

[0112] According to the above rules, the first version of VSV of 24RC03 drawn on June 15, 2024 has a VSVID of 202403010100_20240615; the second version of VSV of 24RC03 drawn on June 15, 2024 has a VSVID of 202403010200_20240615; the third version of VSV of 24RC05 drawn on June 16, 2024 has a VSVID of 202405010200_20240616; the software maturity of VSV can be judged by comparing the size of the first 10 digits of VSVID. The larger the first ten digits, the higher the maturity of the software.

[0113] 3. Maintain the required version attributes of VSV:

[0114] After the VSV is created, the VSV data is pushed to the LVIP system through the system interface of the TC management platform and the vehicle information platform. Determine whether the VSV version is a required version based on software compatibility. If so, establish a dependency relationship between the historical VSV version and the target VSV version in the LVIP system; if not, no operation is required.

[0115] VSV dependency example: If there is a dependency between the historical version and the current version, check the corresponding VSVID. If there is no dependency between the historical version and the current version, do not check it.

[0116] 4. Create a vehicle profile in LVIP:

[0117] When the vehicle rolls off the assembly line, the VSVID on the vehicle is read through the production line and uploaded to the vehicle information platform and stored in the vehicle file. If the vehicle subsequently undergoes a software upgrade via OTA, the VSVID is sent back to the vehicle information platform after the OTA is successful, and the VSVID in the vehicle file is updated.

[0118] 5. Push software upgrade tasks on the OTA platform and determine whether the target vehicle meets the upgrade conditions.

[0119] 1) Traverse the vehicle list, match the current VSVID with the vehicle VIN, and compare the size with the target VSVID. If the current VSVID is greater than the target VSVID, the OTA task will not be created, and a prompt will pop up: The current VSVID is greater than the target VSVID, and the task creation fails; if the current VSVID is less than the target VSVID, proceed to the next step;

[0120] 2) Check whether there is a required version between the vehicle-side VSVID and the target VSVID. If not, send the software upgrade task to the target vehicle normally; if so, proceed to the next step of judgment.

[0121] 3) Check whether there is a dependency relationship between the vehicle-side VSVID and the required version VSVID. If not, the software upgrade task is sent to the vehicle normally; if so, the OTA task is not created, and a prompt is popped up: The following vehicles have a required version, please upgrade the required version first;

[0122] 4) After-sales engineers push the required version to the user and remind the user to upgrade through the after-sales service phone. After the user completes the upgrade, the upgrade task of the target version is pushed again.

[0123] In this embodiment, SWBOM is used to manage the software versions of all ECUs on the vehicle, and the effective time of the BOM line is used as one of the naming elements of VSVID to distinguish the maturity of the software version; the concepts of required upgrade versions and version dependencies are introduced to automatically avoid cross-version upgrades of the vehicle.

[0124] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0125] Based on the same inventive concept, the embodiment of the present application also provides an OTA-based vehicle software upgrade device for implementing the above-mentioned OTA-based vehicle software upgrade method. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above-mentioned method, so the specific limitations in one or more OTA-based vehicle software upgrade device embodiments provided below can refer to the limitations of the OTA-based vehicle software upgrade method above, and will not be repeated here.

[0126] In an exemplary embodiment, Figure 4 As shown, a vehicle software upgrade device based on OTA is provided, comprising:

[0127] A version determination module 402, for determining the current vehicle software version of the vehicle according to the effective node of the vehicle software part number newly added in the vehicle software list;

[0128] The acquisition module 404 is used to obtain the unique identifier of the current vehicle software version;

[0129] The acquisition module 404 is further used to acquire vehicle file data according to the unique identifier;

[0130] The analysis module 406 is used to analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version according to the vehicle file data, and obtain an analysis result;

[0131] The solution determination module 408 is used to determine the vehicle software upgrade solution according to the analysis results.

[0132] In an exemplary embodiment, the processing module is used to create a vehicle software part number and add the vehicle software part number to a vehicle software list when software information of a vehicle control system changes.

[0133] In an exemplary embodiment, the version determination module 402 is also used to associate the effective node of the newly added vehicle software part number in the vehicle software list with the date; using the effective node after the associated date, extract the software part number data set of different date stages from the vehicle software list; and determine the current vehicle software version of the vehicle based on the software part number data set.

[0134] In an exemplary embodiment, the solution determination module 408 is also used to establish a dependency relationship between the historical vehicle software version and the target vehicle software version when there is a required upgrade version between the current vehicle software version and the target vehicle software version, and send a prompt message to prioritize the upgrade of the required upgrade version.

[0135] In an exemplary embodiment, the solution determination module 408 is also used to upgrade the current vehicle software version to the target vehicle software version using an over-the-air download method OTA when there is no required upgrade version between the current vehicle software version and the target vehicle software version.

[0136] In an exemplary embodiment, the feedback module is used to feedback the unique identifier of the target vehicle software version to the vehicle file data after the vehicle software is successfully upgraded.

[0137] Each module in the above-mentioned OTA-based vehicle software upgrade device can be implemented in whole or in part by software, hardware, or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above modules.

[0138] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 5As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store a vehicle software list and vehicle file data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a vehicle software upgrade method based on OTA is implemented.

[0139] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0140] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0141] Determine the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list;

[0142] Get the unique identifier of the current vehicle software version;

[0143] Obtain vehicle profile data based on the unique identifier;

[0144] According to the vehicle file data, analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, and obtain the analysis result;

[0145] Based on the analysis results, determine the vehicle's software upgrade plan.

[0146] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0147] In the event that the software information of the vehicle control system is changed, a vehicle software part number is created and added to the vehicle software list.

[0148] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0149] Associating the effective node and date of the newly added vehicle software part number in the vehicle software list;

[0150] By using the effective node after the associated date, a data set of software part numbers at different date stages is extracted from the vehicle software list;

[0151] Based on the software part number data set, determine the current vehicle software version of the vehicle.

[0152] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0153] In the case where there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, a dependency relationship between the historical vehicle software version and the target vehicle software version is established, and a prompt message is sent to prioritize the necessary upgrade version.

[0154] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0155] When there is no required upgrade version between the current vehicle software version and the target vehicle software version, the current vehicle software version is upgraded to the target vehicle software version using OTA (Over-the-Air) download.

[0156] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0157] After the vehicle software is successfully upgraded, the unique identifier of the target vehicle software version is transmitted back to the vehicle file data.

[0158] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0159] Determine the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list;

[0160] Get the unique identifier of the current vehicle software version;

[0161] Obtain vehicle profile data based on the unique identifier;

[0162] According to the vehicle file data, analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, and obtain the analysis result;

[0163] Based on the analysis results, determine the vehicle's software upgrade plan.

[0164] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0165] In the event that the software information of the vehicle control system is changed, a vehicle software part number is created and added to the vehicle software list.

[0166] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0167] Associating the effective node and date of the newly added vehicle software part number in the vehicle software list;

[0168] By using the effective node after the associated date, a data set of software part numbers at different date stages is extracted from the vehicle software list;

[0169] Based on the software part number data set, determine the current vehicle software version of the vehicle.

[0170] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0171] In the case where there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, a dependency relationship between the historical vehicle software version and the target vehicle software version is established, and a prompt message is sent to prioritize the necessary upgrade version.

[0172] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0173] When there is no required upgrade version between the current vehicle software version and the target vehicle software version, the current vehicle software version is upgraded to the target vehicle software version using OTA (Over-the-Air) download.

[0174] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0175] After the vehicle software is successfully upgraded, the unique identifier of the target vehicle software version is transmitted back to the vehicle file data.

[0176] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0177] Determine the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list;

[0178] Get the unique identifier of the current vehicle software version;

[0179] Obtain vehicle profile data based on the unique identifier;

[0180] According to the vehicle file data, analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, and obtain the analysis result;

[0181] Based on the analysis results, determine the vehicle's software upgrade plan.

[0182] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0183] In the event that the software information of the vehicle control system is changed, a vehicle software part number is created and added to the vehicle software list.

[0184] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0185] Associating the effective node and date of the newly added vehicle software part number in the vehicle software list;

[0186] By using the effective node after the associated date, a data set of software part numbers at different date stages is extracted from the vehicle software list;

[0187] Based on the software part number data set, determine the current vehicle software version of the vehicle.

[0188] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0189] In the case where there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, a dependency relationship between the historical vehicle software version and the target vehicle software version is established, and a prompt message is sent to prioritize the necessary upgrade version.

[0190] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0191] When there is no required upgrade version between the current vehicle software version and the target vehicle software version, the current vehicle software version is upgraded to the target vehicle software version using OTA (Over-the-Air) download.

[0192] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0193] After the vehicle software is successfully upgraded, the unique identifier of the target vehicle software version is transmitted back to the vehicle file data.

[0194] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0195] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0196] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0197] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A vehicle software upgrade method based on OTA, characterized in that: The method comprises: Determine the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list; Obtaining a unique identifier for the current vehicle software version; Obtain vehicle file data according to the unique identifier; Analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version according to the vehicle file data, and obtain an analysis result; A software upgrade plan for the vehicle is determined based on the analysis results.

2. The method according to claim 1, characterized in that Before determining the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list, the method further includes: When the software information of the vehicle control system is changed, a vehicle software part number is created and added to the vehicle software list.

3. The method according to claim 1, characterized in that The determining of the current vehicle software version of the vehicle according to the effective node of the newly added vehicle software part number in the vehicle software list includes: Associating the effective node of the newly added vehicle software part number in the vehicle software list with the date; Extracting a set of software part number data at different date stages from the vehicle software list by using the effective node after the associated date; The current vehicle software version of the vehicle is determined based on the software part number data set.

4. The method according to claim 1, characterized in that: Determining a vehicle software upgrade solution according to the analysis result includes: In the case where there is a necessary upgrade version between the current vehicle software version and the target vehicle software version, a dependency relationship between the historical vehicle software version and the target vehicle software version is established, and a prompt message is sent to prioritize the upgrade of the necessary upgrade version.

5. The method according to claim 1, characterized in that: Determining a vehicle software upgrade solution according to the analysis result includes: In the case that there is no required upgrade version between the current vehicle software version and the target vehicle software version, the current vehicle software version is upgraded to the target vehicle software version by using the over-the-air download method OTA.

6. The method according to claim 1, characterized in that After determining the vehicle software upgrade solution according to the analysis result, the method further includes: After the vehicle software is successfully upgraded, the unique identifier of the target vehicle software version is transmitted back to the vehicle file data.

7. A vehicle software upgrade device based on OTA, characterized in that: The device comprises: A version determination module, used to determine the current vehicle software version of the vehicle according to the effective node of the vehicle software part number newly added in the vehicle software list; An acquisition module, used to acquire a unique identifier of the current vehicle software version; The acquisition module is further used to acquire vehicle file data according to the unique identifier; An analysis module is used to analyze whether there is a necessary upgrade version between the current vehicle software version and the target vehicle software version according to the vehicle file data, and obtain an analysis result; A solution determination module is used to determine a vehicle software upgrade solution based on the analysis results.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images