Vehicle OTA upgrading method and system

Abstract

The invention discloses a vehicle OTA upgrading method and system which are applied to a server, and the method comprises the steps: receiving a version task updating signal sent by a vehicle end, and obtaining a vehicle system to which the vehicle end belongs and the current versions of all upgradable parts of the vehicle end, the vehicle end comprising one or more vehicles; if the received single vehicle or the acquired vehicles belong to the same vehicle series, inquiring whether a version updating task corresponding to the vehicle series exists in a version task updating library or not according to the vehicle series; if yes, judging whether all upgradable parts of the vehicle end contain the to-be-upgraded parts or not; if yes, sending an upgrade package link associated with the version updating task to the vehicle end, so that the vehicle end downloads the version updating task according to the upgrade package link, and upgrades the current version of the to-be-upgraded part based on the version updating task. According to the method, the problem that the efficiency is low when a single ECU or multiple ECUs are upgraded each time is solved, and the upgrading efficiency and safety are greatly improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a vehicle OTA upgrade method and system. Background Art

[0002] Today, intelligent technologies in the automotive field continue to advance, and electric vehicles, in particular, are increasingly reliant on intelligent electronic control units (ECUs). While these technologies bring technological convenience to users, they also bring challenges with controller software updates. Modern smart cars rely on OTA (Over-The-Air) upgrade technology, a technique for remotely updating device firmware or software via wireless networks, to enable software upgrades for onboard ECUs.

[0003] OTA (Over-the-Air) update technology has brought unprecedented convenience to automakers and users. When problems with auto parts arise, manufacturers can resolve software defects online without recalls, saving significant costs associated with offline recalls. While OTA updates have become a core technology for automakers, existing configuration methods are inefficient. Summary of the Invention

[0004] The embodiments of the present application provide a vehicle OTA upgrade method and system, which centrally manages all parts of a vehicle series that need to be upgraded, determines an upgrade strategy, and completes batch and sequential upgrades of parts for the entire vehicle series, thereby solving the problem of inefficiency encountered in each upgrade of a single or multiple ECUs and greatly improving upgrade efficiency and safety.

[0005] In a first aspect, the present invention provides the following technical solutions through an embodiment of the present invention:

[0006] A vehicle OTA upgrade method, applied to a server, includes:

[0007] Receive a version task update signal sent by a vehicle end, and obtain the vehicle series to which the vehicle end belongs and the current versions of all upgradeable parts of the vehicle end, wherein the vehicle end includes a single or multiple vehicles; if the vehicle series to which the received single vehicle or the multiple vehicles obtained belong is the same, then, based on the vehicle series, query whether there is a version update task corresponding to the vehicle series in a pre-established version task update library, wherein the version task update library includes multiple vehicle series to be upgraded and the corresponding version update tasks under each vehicle series to be upgraded, and the version update tasks include the target versions of all parts to be upgraded and the installation order of all parts to be upgraded; if there is a version update task corresponding to the vehicle series, determine whether all upgradeable parts of the vehicle end include the parts to be upgraded; if they include the parts to be upgraded, send an upgrade package link associated with the version update task to the vehicle end, so that the vehicle end downloads the version update task according to the upgrade package link, and upgrades the current version of the parts to be upgraded based on the version update task.

[0008] Preferably, before sending the upgrade package link associated with the version update task to the vehicle end, it also includes: for each part to be upgraded, determining whether the current version of the part to be upgraded is the target version; if not, sending the upgrade package link associated with the version update task to the vehicle end.

[0009] Preferably, the version task update library is established according to the following steps: obtaining a parts version list for each vehicle series to be upgraded, the parts version list including the vehicle series information to be upgraded and the target versions of all parts to be upgraded; for each vehicle series to be upgraded, configuring a target main version number corresponding to each vehicle series to be upgraded based on the parts version list and the version descriptions of all parts to be upgraded, wherein the target main version number corresponds to the target version of all parts to be upgraded under the vehicle series; configuring a main version strategy for each vehicle series to be upgraded based on the preset upgrade requirements of the vehicle series to be upgraded; binding the main version strategy of each vehicle series to be upgraded with the corresponding target main version number to determine the version update task for each vehicle series to be upgraded; establishing the version task update library based on the version update task of each vehicle series to be upgraded.

[0010] Preferably, obtaining the parts version list for each vehicle series to be upgraded includes: receiving basic data of newly entered online vehicles, the basic data including the vehicle series, the current version of each upgradeable part, and the target version; determining multiple new vehicle series and all corresponding upgradeable parts under each vehicle series based on the basic data and the current database, and obtaining a target database, wherein the current database includes multiple current vehicle series and all corresponding upgradeable parts under each vehicle series; when vehicle series upgrade requirements are obtained, determining the parts version list for each vehicle series to be upgraded based on the vehicle series upgrade requirements and the target database.

[0011] Preferably, configuring the main version strategy for each vehicle series to be upgraded based on the preset upgrade requirements of the vehicle series to be upgraded includes: establishing a dependency relationship between all parts to be upgraded of each single vehicle series to be upgraded based on the preset upgrade requirements of the vehicle series to be upgraded; configuring the main version strategy for each vehicle series to be upgraded based on the dependency relationship between all parts to be upgraded of each single vehicle series to be upgraded.

[0012] Preferably, the main version policy also includes a version policy name, a version policy description, main version policy information, version information of all parts to be upgraded, and upgrade information, wherein the main version policy information includes the vehicle series to be upgraded, the target main version number, and the current main version number; the version information of all parts to be upgraded includes the upgrade method of all parts to be upgraded, the target version of all parts to be upgraded, and the current version; the upgrade information includes the upgrade prerequisites of the vehicle.

[0013] Preferably, after configuring the main version strategy for each vehicle series to be upgraded, the method further includes: selecting multiple target vehicles under a target vehicle series from the vehicle series to be upgraded as vehicles to be tested, wherein the multiple target vehicles all contain parts to be upgraded; sending the main version strategy of the target vehicle series to the vehicle to be tested, so that the vehicle to be tested upgrades the current version of the parts to be upgraded based on the main version strategy, and obtains a test result of the vehicle to be tested; and judging whether the main version strategy is qualified based on the test result.

[0014] In a second aspect, the present invention provides the following technical solution through an embodiment of the present invention:

[0015] A vehicle OTA upgrade method, applied to a vehicle side, comprises: if a power-on signal is received, sending a version task update signal of the vehicle side, the vehicle series to which the vehicle side belongs, and the current versions of all upgradeable parts of the vehicle side to a server, so that the server determines whether there is a version update task corresponding to the vehicle series and whether all upgradeable parts of the vehicle side include parts to be upgraded based on the version task update signal; if an upgrade package link associated with the version update task sent by the server is received, downloading the version update task; and upgrading the current versions of the parts to be upgraded of the vehicle based on the version update task.

[0016] Preferably, the upgrading of the current version of the parts to be upgraded of the vehicle based on the version update task includes: judging whether the current state of the vehicle meets the upgrade preconditions based on the version update task; if so, upgrading the current version of the parts to be upgraded of the vehicle.

[0017] In a third aspect, the present invention provides the following technical solution through an embodiment of the present invention:

[0018] A vehicle OTA upgrade system, comprising:

[0019] The server is configured to receive a version task update signal sent by a vehicle end, and obtain the vehicle series to which the vehicle end belongs and the current versions of all upgradeable parts of the vehicle end; based on the vehicle series, query whether a version update task corresponding to the vehicle series exists in a preset version task update library, wherein the version task update library includes different vehicle series and the corresponding version update tasks under each vehicle series, and the version update task includes the target versions of all parts to be upgraded and the installation order of all parts to be upgraded; if a version update task corresponding to the vehicle series exists, determine whether all upgradeable parts of the vehicle end include the parts to be upgraded; if the parts to be upgraded are included, send an upgrade package link associated with the version update task to the vehicle end, so that the vehicle end downloads the version update task according to the upgrade package link, and upgrades the current versions of the parts to be upgraded based on the version update task;

[0020] The vehicle side is used to send the version task update signal of the vehicle, the vehicle series to which the vehicle belongs, and the current versions of all upgradeable parts of the vehicle to the server if a power-on signal is received, so that the server can determine whether there is a version update task corresponding to the vehicle series and whether all upgradeable parts of the vehicle include parts to be upgraded based on the version task update signal; if an upgrade package link associated with the version update task sent by the server is received, the version update task is downloaded; based on the version update task, the current versions of the parts to be upgraded of the vehicle are upgraded.

[0021] One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages:

[0022] The vehicle OTA upgrade method provided by an embodiment of the present invention receives a version task update signal sent by a single vehicle or multiple vehicles. If the received single vehicle or multiple vehicles belong to the same vehicle series, the version update task corresponding to the vehicle series is queried based on the vehicle series to which the vehicles belong, and it is determined whether all upgradeable parts of the vehicle include the parts to be upgraded. If so, the version update task is sent to the vehicle end, so that the vehicle end upgrades the current version of the parts to be upgraded based on the version update task, so that all parts to be upgraded on the vehicle end are updated to the target version. By uniformly managing all parts of the vehicle series that need to be upgraded, an upgrade strategy is determined, and batch upgrades and sequential upgrades of parts of the entire vehicle series are completed, the problem of low efficiency encountered in upgrading a single or multiple ECUs each time is solved, and the upgrade efficiency and safety are greatly improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0024] Figure 1 This is a flow chart of a vehicle OTA upgrade method according to an embodiment of the present invention;

[0025] Figure 2 This is a system framework diagram for vehicle OTA upgrade in an embodiment of the present invention;

[0026] Figure 3 Schematic diagram of the process of OTA upgrade of a vehicle in an embodiment of the present invention;

[0027] Figure 4 A schematic diagram of basic vehicle data in an embodiment of the present invention;

[0028] Figure 5 This is a flow chart of another vehicle OTA upgrade method according to an embodiment of the present invention;

[0029] Figure 6 Schematic diagram of the structure of the system in an embodiment of the present invention. DETAILED DESCRIPTION

[0030] After research, the inventors discovered that the current upgrade technology has a very low upgrade efficiency because it is targeted at certain vehicle configuration upgrade tasks for specific models. If there are a large number of cars or cars of different series and models on the current market that need to be upgraded, a large number of tasks need to be configured, and each task contains a different set of parts, which requires huge manpower costs and will affect the problem repair and function update of defective vehicles, and there is a risk of inaccurate processing results. Moreover, each task is configured with a single ECU or multiple ECUs, which not only affects efficiency but also brings many safety issues, because during the upgrade process of some parts of the same or different types, they need to rely on other parts to complete the upgrade first. If the installation order of the parts is configured incorrectly, it will greatly affect the upgrade efficiency and even bring safety hazards.

[0031] The embodiments of the present application provide a vehicle OTA upgrade method and system, which centrally manages all parts of a vehicle series that need to be upgraded, determines an upgrade strategy, and completes batch and sequential upgrades of parts for the entire vehicle series, thereby solving the problem of inefficiency encountered in each upgrade of a single or multiple ECUs and greatly improving upgrade efficiency and safety.

[0032] The technical solution of the embodiment of the present application is to solve the above technical problems, and the overall idea is as follows:

[0033] A vehicle OTA upgrade method is applied to a server, the method comprising: receiving a version task update signal sent by a vehicle end, and obtaining the vehicle series to which the vehicle end belongs and the current versions of all upgradeable parts of the vehicle end, wherein the vehicle end includes a single or multiple vehicles; if the vehicle series to which the received single vehicle or the multiple acquired vehicles belong is the same, then, based on the vehicle series, querying whether there is a version update task corresponding to the vehicle series in a pre-established version task update library, wherein the version task update library includes multiple vehicle series to be upgraded and the corresponding version update tasks under each vehicle series to be upgraded, and the version update task includes the target versions of all parts to be upgraded and the installation order of all parts to be upgraded; if there is a version update task corresponding to the vehicle series, determining whether all upgradeable parts of the vehicle end include the parts to be upgraded; if the parts to be upgraded are included, sending an upgrade package link associated with the version update task to the vehicle end, so that the vehicle end downloads the version update task according to the upgrade package link, and upgrades the current version of the parts to be upgraded based on the version update task.

[0034] In order to better understand the above technical solution, the above technical solution will be described in detail below with reference to the accompanying drawings and specific implementation methods.

[0035] In the first aspect, an embodiment of the present invention provides a vehicle OTA upgrade method, which is applied to a server. Specifically, Figure 1 As shown, the method includes the following steps S101 to S104:

[0036] Step S101: receiving a version task update signal sent by a vehicle end, and obtaining the current versions of the vehicle series to which the vehicle end belongs and all upgradeable parts of the vehicle end, wherein the vehicle end includes a single vehicle or multiple vehicles;

[0037] In step S102, if the received single vehicle or the obtained multiple vehicles belong to the same vehicle series, then based on the vehicle series, a query is made in a pre-established version task update library to determine whether there is a version update task corresponding to the vehicle series, wherein the version task update library includes multiple vehicle series to be upgraded and the corresponding version update tasks for each vehicle series to be upgraded, and the version update tasks include the target versions of all parts to be upgraded and the installation order of all parts to be upgraded.

[0038] It should be noted that the parts referred to in this application can be ECU software, for example: the parts can be engine parts (such as engine control unit), steering angle parts (such as steering angle sensor), airbag parts (such as airbag controller), instrument panel parts (such as instrument panel control unit), etc. Upgradeable parts refer to parts that can be upgraded using OTA upgrade methods. The vehicle end here refers to all vehicles that send version task update signals to the server at the same time. Therefore, in actual applications, the vehicle end can be one vehicle or multiple vehicles.

[0039] like Figure 2 As shown, this is the system framework diagram of the vehicle OTA upgrade given in this application. During the specific implementation process, after the vehicle is powered on, it automatically sends a version task update signal to the server. The version task update signal is used to request to detect whether there is a version update task in the server. At the same time, the vehicle side will send the current versions of the vehicle series and all upgradeable parts of the vehicle side to the server.

[0040] If the single vehicle received by the server or the multiple vehicles obtained belong to the same vehicle series, the server will query the pre-established version task update library based on the vehicle series to which the vehicle belongs to whether there is a version update task corresponding to the vehicle series, and feedback the result to the vehicle. The version task update library includes multiple vehicle series to be upgraded and the corresponding version update tasks for each vehicle series to be upgraded. The version update tasks include the target versions of all parts to be upgraded and the installation order of all parts to be upgraded.

[0041] In a specific embodiment, before receiving the version task update signal sent by the vehicle end, the process may further include: establishing a version task update library, wherein the version task update library is established according to the following steps:

[0042] Obtain a parts version list for each vehicle series to be upgraded, which includes the vehicle series information to be upgraded and the target versions of all parts to be upgraded; for each vehicle series to be upgraded, configure the target major version number corresponding to each vehicle series to be upgraded based on the parts version list and the version descriptions of all parts to be upgraded, where the target major version number corresponds to the target version of all parts to be upgraded under the vehicle series; configure a major version strategy for each vehicle series to be upgraded based on the preset upgrade requirements of the vehicle series to be upgraded; bind the major version strategy of each vehicle series to be upgraded to the corresponding target major version number to determine the version update task for each vehicle series to be upgraded; and establish a version task update library based on the version update task of each vehicle series to be upgraded.

[0043] like Figure 3 、 Figure 4 As shown, in one embodiment, obtaining a parts version list for each vehicle series to be upgraded may include: receiving basic data of a newly entered online vehicle, the basic data including the vehicle series, the current version of each upgradeable part, and the target version; determining multiple new vehicle series and all corresponding upgradeable parts for each vehicle series based on the basic data and the current database, and obtaining a target database, wherein the current database includes multiple current vehicle series and all corresponding upgradeable parts for each vehicle series; and upon obtaining a vehicle series upgrade requirement, determining a parts version list for each vehicle series to be upgraded based on the vehicle series upgrade requirement and the target database. The vehicle series information may include the vehicle series name, vehicle series code, and brand.

[0044] In a specific embodiment, Figure 3 As shown, the basic data may also include vehicle information, vehicle model information, part type, part type, and part information, wherein the vehicle information may include the VIN code, brand, series, series, and vehicle status; the vehicle model information may include the model name, model code, market name, and series, etc.; the part type may include the type abbreviation, Chinese name, and English name; the part information may include the installation type, hardware part number, software part number, software type, diagnostic ID, response ID, function ID, etc.

[0045] Specifically, after the vehicle goes online, the vehicle's BOM (bill of materials) information will be automatically sent to the server. The server will obtain the basic data of the online vehicle based on the bill of materials. Alternatively, the operator manually enters the basic data of the target vehicle (that is, the online vehicle) on the market that is about to undergo OTA upgrade activities into the server.

[0046] The newly entered basic data is merged with the current database to obtain multiple new car series and all corresponding upgradeable parts for each car series. For example, the newly entered basic data is the basic data of multiple models under a new car series. The newly entered car series and all corresponding upgradeable parts are added to the current database.

[0047] When a vehicle series upgrade requirement is obtained, the parts version list for each vehicle series to be upgraded is determined based on the vehicle series upgrade requirement and the target database. The vehicle series upgrade requirement can be determined by the operations staff based on the needs of the vehicle series to be upgraded. For example, if the target database includes vehicle series A, B, C, D, and E, and the vehicle series upgrade requirement is to upgrade vehicle series A and B, the parts version list for vehicle series A and B will be obtained.

[0048] In another embodiment, obtaining a parts version list for each vehicle series to be upgraded may include: when a vehicle series upgrade requirement is obtained, determining a parts version list for each vehicle series to be upgraded based on the vehicle series upgrade requirement and a current database, wherein the current database includes multiple current vehicle series and all corresponding upgradeable parts for each vehicle series.

[0049] For each vehicle series to be upgraded, a target major version number is configured based on the part version list and the version descriptions of all parts to be upgraded. The target major version number corresponds to the target version of all parts to be upgraded in that vehicle series. The version description can include part type, installation type, part name, hardware part number, diagnostic ID, software part number, and part version.

[0050] Specifically, based on the requirements of the target vehicle series to be upgraded, operations personnel compile a list of the next part versions to be upgraded for that vehicle series. This new list of parts is combined with the version descriptions of all parts to be upgraded within that vehicle series to create a target major version number for the vehicle series, along with a version identifier. For example, vehicle series A has five parts: a, b, c, d, and e. Part versions for major version v1 include a-v1, b-v2, c-v1, d-v1, and e-v1, while part versions for major version v2 include a-v2, b-v3, c-v1, d-v2, and e-v3. Major version v1 is the current version, and major version v2 is the target version. This allows operations personnel to develop different target major version numbers for each vehicle series during the corresponding OTA campaign period. These target major version numbers correspond to the software versions of all parts within the entire vehicle series. In other words, each OTA campaign corresponds to a target major version number for the vehicle series.

[0051] Next, a major version policy is configured for each vehicle series to be upgraded based on the preset upgrade requirements of the vehicle series to be upgraded. In a specific embodiment, configuring a major version policy for each vehicle series to be upgraded based on the preset upgrade requirements of the vehicle series to be upgraded may include: establishing dependencies between all parts to be upgraded for each vehicle series to be upgraded based on the preset upgrade requirements of the vehicle series to be upgraded; and configuring a major version policy for each vehicle series to be upgraded based on the dependencies between all parts to be upgraded for each vehicle series to be upgraded.

[0052] In a specific embodiment, in order to effectively ensure the correct dependency order of parts during the upgrade process, in addition to configuring the current version and target version of the part, the part can also be configured with the version number that other parts in this vehicle series that it depends on must meet, thereby implementing the dependency relationship of the parts in the main version policy.

[0053] For example, the parts collection for vehicle series A includes five parts: a, b, c, d, and e. Part a currently has three software versions: a-v1, a-v2, and a-v3; part b has two software versions: b-v1 and b-v2; and part c has one software version: c-v1. To upgrade part a, the version policy sets the current version to a-v1, the target version to a-v2, and the dependent part of a to b's version b-v2. This means that part a can be upgraded from a-v1 to a-v2 only if part b has already been upgraded to b-v2; otherwise, the upgrade will fail. After obtaining the master version policy, upgrade tasks are configured, released, and batch upgrades are completed, ensuring the correct installation order of parts during the upgrade process, greatly improving upgrade efficiency and security.

[0054] In a specific embodiment, for each vehicle series target major version number corresponding to each OTA marketing campaign, the server configures a major version policy for each vehicle series to be upgraded. The major version policy may also include a version policy name, version policy description, major version policy information, version information of all parts to be upgraded, and upgrade information. The major version policy information may include the vehicle series to be upgraded, the target major version number, and the current major version number. The version information of all parts to be upgraded may include the upgrade method for all parts to be upgraded, the target version of all parts to be upgraded, and the current version. The upgrade information may include the vehicle upgrade prerequisites.

[0055] Optionally, the preconditions for upgrading the vehicle may be that the vehicle is in a stopped state, the remaining power of the vehicle is greater than a preset power value, etc., wherein the preset power value can be set according to actual needs and is not limited in this application.

[0056] Specifically, a version policy name might be: "Second upgrade for vehicle series A"; a version policy description might be: "Upgrade of parts a and b to be upgraded under vehicle series A"; current major version number V1; target major version number V2. Version information for all parts to be upgraded under the target major version might include the upgrade method (whole package upgrade, differential package upgrade), part upgrade versions (current version, target version), part upgrade dependencies, and rollback configuration (whether to rollback after an installation failure). The upgrade information can define the upgrade mode, detection and download times, installation method, vehicle upgrade prerequisites, and upgrade prompts.

[0057] Furthermore, in order to ensure the accuracy of the released version update tasks, after configuring the main version strategy for each vehicle series to be upgraded, it can also include: selecting multiple target vehicles under a target vehicle series from the vehicle series to be upgraded as test vehicles, wherein the multiple target vehicles all contain parts to be upgraded; sending the main version strategy of the target vehicle series to the vehicle to be tested, so that the vehicle to be tested upgrades the current version of the parts to be upgraded based on the main version strategy, and obtains the test results of the vehicle to be tested; based on the test results, judging whether the main version strategy is qualified.

[0058] Specifically, after creating a master version strategy, the strategy is sent to the vehicle under test, initiating the testing process and submitting it to testers for master version strategy testing. Testers verify that all components to be upgraded in the target vehicle series have been successfully upgraded (including whether the component software has reached the target version and whether the component dependency order during the upgrade is correct). Based on the test results, a test report is submitted to determine whether the master version strategy has passed the test. If all upgrades are successful, the master version strategy is considered to have passed. If one or more upgrades fail, the master version strategy is reconfigured.

[0059] In other embodiments, multiple target vehicles from multiple target vehicle series can be selected from the vehicle series to be upgraded as test vehicles. Multiple vehicles from each vehicle series are tested, and the master version policy of the target vehicle series is transmitted to the test vehicles. The test vehicles are then upgraded to the current versions of the parts to be upgraded based on the master version policy, and test results are obtained for the test vehicles. If the test results indicate that all upgrades are successful, the master version policy is considered to have passed. If one or more upgrades fail, the master version policy is reconfigured.

[0060] After the major version strategy test passes, a task is created with the target major version number and the major version strategy bound to it. This task is then generated as a version upgrade task. The task includes a task name, description, sequence number, and major version strategy. A version upgrade task update library is established based on the version upgrade tasks for each vehicle series to be upgraded. Submit the version upgrade task for review. After reviewers verify the configuration information for this version upgrade, the task is released.

[0061] Step S103: If there is a version update task corresponding to the vehicle series, it is determined whether all upgradeable parts on the vehicle side include parts to be upgraded;

[0062] Step S104: If the parts to be upgraded are included, the upgrade package link associated with the version update task is sent to the vehicle end, so that the vehicle end downloads the version update task according to the upgrade package link and upgrades the current version of the parts to be upgraded based on the version update task.

[0063] Furthermore, to avoid repeated upgrades and reduce energy consumption, before sending the upgrade package link associated with the version update task to the vehicle, the following may be included: for each part to be upgraded, determining whether the current version of the part to be upgraded is the target version; if not, sending the upgrade package link associated with the version update task to the vehicle. If it is the target version, neither the server nor the vehicle takes any action.

[0064] In a specific embodiment, since the vehicle series includes a variety of different vehicles, even if the version update task of the vehicle series exists in the version task update library, the corresponding vehicle may not contain the parts to be upgraded. Therefore, it is also necessary to determine whether all the upgradeable parts on the vehicle side include the parts to be upgraded. If the parts to be upgraded are included, the upgrade package link address is pushed to the vehicle side, so that the vehicle side downloads the upgrade package based on the upgrade package link address, and upgrades the current version of the parts to be upgraded based on the version update task, and all the parts to be upgraded are updated to the target version. After the vehicle side upgrade is completed, the server receives the upgrade results sent by the vehicle side. In order to view the upgrade status of the vehicle, the operator can view the version upgrade task status information (upgrade process and results) on the server OTA management page, and count the upgrade status.

[0065] Furthermore, if the version update task corresponding to the vehicle series does not exist in the version task update library, the vehicle will not take action.

[0066] In a specific embodiment, if the multiple vehicles obtained belong to different vehicle series, then based on the multiple vehicle series included, for each vehicle series, a query is made as to whether a version update task corresponding to the vehicle series exists in a pre-established version task update library; if a version update task corresponding to the vehicle series exists, then a determination is made as to whether all upgradeable parts of the vehicles under the vehicle series include parts to be upgraded; if parts to be upgraded are included, an upgrade package link associated with the version update task is sent to the vehicles under the vehicle series, so that the vehicles download the version update task according to the upgrade package link, and upgrade the current version of the parts to be upgraded based on the version update task.

[0067] To achieve the above-mentioned goals of improving upgrade efficiency and security, this application is divided into configuring the OTA version update task first, and then performing the OTA upgrade. When configuring the OTA version update task, the basic information is manually or automatically entered into the server, and then the target major version number and major version policy of the vehicle series are configured, the target major version number and major version policy are bound, and finally the version update task is released.

[0068] In summary, the vehicle OTA upgrade method provided by the embodiments of the present invention manages basic information such as the software version information of vehicle components before the upgrade, rationally arranges the upgrade sequence and target upgrade versions of the components, and creates a target major version number for the target vehicle series containing all the components to be upgraded. During the upgrade, the corresponding version update task of the vehicle series is retrieved to complete the upgrade. This enables the vehicle end to perform batch and sequential OTA upgrades of the entire vehicle's components according to the version update tasks, greatly improving upgrade efficiency and security.

[0069] In a second aspect, another embodiment of the present invention provides a vehicle OTA upgrade method, which is applied to the vehicle side. Specifically, Figure 5 As shown, the method includes the following steps S201 to S203:

[0070] Step S201: If a power-on signal is received, a version task update signal of the vehicle, the vehicle series to which the vehicle belongs, and the current versions of all upgradeable parts of the vehicle are sent to the server, so that the server can determine, based on the version task update signal, whether there is a version update task corresponding to the vehicle series and whether all upgradeable parts of the vehicle include parts to be upgraded.

[0071] Step S202: if the upgrade package link associated with the version update task sent by the server is received, download the version update task;

[0072] Step S203: Based on the version update task, the current version of the vehicle's parts to be upgraded is upgraded.

[0073] In a specific embodiment, after the server issues a version update task, the vehicle-side upgrade process begins. Upon powering up, the vehicle sends a version update signal to the server, along with the vehicle series and the current versions of all upgradeable components. The vehicle then requests the server to detect whether a new version update task exists. Based on this information, the server checks for any available version update tasks for the specific series and returns the result to the vehicle. If a version update task exists and the vehicle contains the corresponding components to be upgraded, the vehicle receives the version update task from the server and downloads the upgrade package using the link provided by the server.

[0074] Furthermore, in order to ensure the efficiency and completeness of the upgrade, based on the version update task, the current version of the parts to be upgraded of the vehicle is upgraded, which may include: based on the version update task, judging whether the current status of the vehicle meets the upgrade preconditions; if so, upgrading the current version of the parts to be upgraded of the vehicle.

[0075] like Figure 2 As shown, in the specific example, after downloading the upgrade package, it also includes local decryption and signature verification. After the decryption and signature verification are completed, the vehicle side determines whether the current state meets the upgrade prerequisites; if the prerequisites are not met (for example, the vehicle is in motion or the vehicle battery is low), the upgrade is stopped; if so, the current version of the vehicle's parts to be upgraded is upgraded, the installation is started, and the ECU software version is updated; after the installation is complete, the vehicle side reports the upgrade results to the server.

[0076] The present invention adopts a vehicle OTA upgrade method, in which the vehicle side actively initiates an upgrade application to the server, obtains the version update task corresponding to the vehicle series to which the vehicle side belongs, and completes the software upgrade of all parts to be upgraded on the vehicle side in batches. This method safely ensures the implementation of OTA upgrade activities in the market and solves the low efficiency problem encountered in other solutions when upgrading a single or multiple ECUs each time.

[0077] An embodiment of the present invention provides a vehicle OTA upgrade method, the implementation principle and technical effects of which are the same as those of the aforementioned first aspect embodiment. For the sake of brief description, for parts not mentioned in this embodiment, reference may be made to the corresponding contents in the aforementioned first aspect embodiment.

[0078] In the third aspect, based on the same inventive concept, this embodiment provides a vehicle OTA upgrade system, such as Figure 6 As shown, the upgrade system 500 includes:

[0079] Server 501 is configured to receive a version task update signal sent by a vehicle and obtain the vehicle series to which the vehicle belongs and the current versions of all upgradeable parts on the vehicle; based on the vehicle series, query a preset version task update library to see whether a version update task corresponding to the vehicle series exists, wherein the version task update library includes different vehicle series and corresponding version update tasks for each vehicle series, and the version update task includes the target versions of all parts to be upgraded and the installation order of all parts to be upgraded; if a version update task corresponding to the vehicle series exists, determine whether all upgradeable parts on the vehicle include the part to be upgraded; if so, send an upgrade package link associated with the version update task to the vehicle, so that the vehicle downloads the version update task according to the upgrade package link and upgrades the current versions of the parts to be upgraded based on the version update task;

[0080] The vehicle end 502 is used to send the vehicle's version task update signal, the vehicle series to which the vehicle belongs, and the current versions of all upgradeable parts of the vehicle to the server if a power-on signal is received, so that the server can determine whether there is a version update task corresponding to the vehicle series and whether all upgradeable parts of the vehicle include parts to be upgraded based on the version task update signal; if an upgrade package link associated with the version update task sent by the server is received, the version update task is downloaded; based on the version update task, the current version of the vehicle's parts to be upgraded is upgraded.

[0081] Since the system described in this embodiment is the system used to implement the vehicle OTA upgrade method in the embodiment of this application, based on the OTA upgrade method described in the embodiment of this application, those skilled in the art can understand the specific implementation of the system of this embodiment and its various variations, so how the system implements the method in the embodiment of this application will not be described in detail here. As long as those skilled in the art implement the system used in the OTA upgrade method in the embodiment of this application, it falls within the scope of protection of this application.

[0082] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0083] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A module that specifies functions in one or more boxes.

[0084] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction module, which is implemented in the process Figure 1a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0085] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0086] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0087] Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if such changes and modifications fall within the scope of the claims and their equivalents, the present invention is intended to include such changes and modifications.

Claims

1. A vehicle OTA upgrade method, characterized in that: Applied to a server, the method includes: Receiving a version task update signal sent by a vehicle end, and obtaining the current versions of the vehicle series to which the vehicle end belongs and all upgradeable parts of the vehicle end, wherein the vehicle end includes a single vehicle or multiple vehicles; If the received single vehicle or multiple vehicles belong to the same vehicle series, then the pre-established version task update library is checked for a version update task corresponding to the vehicle series. The version task update library includes multiple vehicle series to be upgraded and the corresponding version update tasks for each vehicle series to be upgraded. The version update tasks include the target versions of all parts to be upgraded and the installation order of all parts to be upgraded. If there is a version update task corresponding to the vehicle series, determining whether all upgradeable parts on the vehicle side include parts to be upgraded; If the parts to be upgraded are included, the upgrade package link associated with the version update task is sent to the vehicle end, so that the vehicle end downloads the version update task according to the upgrade package link and upgrades the current version of the parts to be upgraded based on the version update task.

2. The method according to claim 1, wherein Before sending the upgrade package link associated with the version update task to the vehicle end, the method further includes: For each part to be upgraded, determining whether the current version of the part to be upgraded is the target version; If not, the upgrade package link associated with the version update task is sent to the vehicle end.

3. The method according to claim 1, wherein The version task update library is established by following the steps below: Obtain a list of parts versions for each vehicle series to be upgraded, including the vehicle series information and the target versions of all parts to be upgraded. For each vehicle series to be upgraded, a target major version number corresponding to each vehicle series to be upgraded is configured based on the part version list and the version descriptions of all parts to be upgraded. The target major version number corresponds to the target version of all parts to be upgraded in the vehicle series. Configure the main version strategy for each vehicle series to be upgraded based on the preset upgrade requirements of the vehicle series to be upgraded; Bind the major version strategy of each vehicle series to be upgraded to the corresponding target major version number to determine the version update task for each vehicle series to be upgraded; Based on the version update tasks of each vehicle series to be upgraded, the version task update library is established.

4. The method according to claim 3, wherein Obtaining a list of parts versions for each vehicle series to be upgraded includes: Receive basic data of a newly entered online vehicle, including the vehicle series, the current version, and the target version of each upgradeable part; Determining, based on the basic data and the current database, multiple new vehicle series and all corresponding upgradeable parts for each vehicle series to obtain a target database, wherein the current database includes multiple current vehicle series and all corresponding upgradeable parts for each vehicle series; When the vehicle series upgrade requirements are obtained, a parts version list for each vehicle series to be upgraded is determined based on the vehicle series upgrade requirements and the target database.

5. The method according to claim 3, wherein The configuration of the main version strategy for each vehicle series to be upgraded based on the preset upgrade requirements of the vehicle series to be upgraded includes: According to the preset upgrade requirements of the vehicle series to be upgraded, the dependency relationship between all the parts to be upgraded for each vehicle series to be upgraded is established; A main version strategy for each vehicle series to be upgraded is configured based on the dependency relationships among all the parts to be upgraded for each vehicle series to be upgraded.

6. The method according to claim 5, wherein The main version policy also includes a version policy name, a version policy description, main version policy information, version information of all parts to be upgraded, and upgrade information. The main version policy information includes the vehicle series to be upgraded, the target main version number, and the current main version number. The version information of all parts to be upgraded includes the upgrade method of all parts to be upgraded, the target version of all parts to be upgraded, and the current version. The upgrade information includes the vehicle upgrade prerequisites.

7. The method according to claim 3, wherein After configuring the main version strategy for each vehicle series to be upgraded, the following steps are also included: From the vehicle series to be upgraded, selecting multiple target vehicles under a target vehicle series as vehicles to be tested, wherein the multiple target vehicles all contain parts to be upgraded; Sending the master version policy of the target vehicle series to the vehicle under test, so that the vehicle under test upgrades the current version of the part to be upgraded based on the master version policy, and obtaining a test result of the vehicle under test; Based on the test result, it is determined whether the major version policy is qualified.

8. A vehicle OTA upgrade method, characterized in that: Applied to the vehicle side, the method includes: If a power-on signal is received, a version task update signal of the vehicle side, the vehicle series to which the vehicle side belongs, and the current versions of all upgradeable parts of the vehicle side are sent to the server, so that the server can determine whether there is a version update task corresponding to the vehicle series and whether all upgradeable parts of the vehicle side include parts to be upgraded based on the version task update signal; If an upgrade package link associated with the version update task sent by the server is received, download the version update task; Based on the version update task, the current version of the to-be-upgraded part of the vehicle is upgraded.

9. The method according to claim 8, wherein The step of upgrading the current version of the vehicle's part to be upgraded based on the version update task includes: Based on the version update task, determining whether the current state of the vehicle meets the upgrade preconditions; If so, the current version of the to-be-upgraded part of the vehicle is upgraded.

10. A vehicle OTA upgrade system, characterized in that: include: The server is configured to receive a version task update signal sent by a vehicle end, and obtain the vehicle series to which the vehicle end belongs and the current versions of all upgradeable parts of the vehicle end; based on the vehicle series, query whether a version update task corresponding to the vehicle series exists in a preset version task update library, wherein the version task update library includes different vehicle series and the corresponding version update tasks under each vehicle series, and the version update task includes the target versions of all parts to be upgraded and the installation order of all parts to be upgraded; if a version update task corresponding to the vehicle series exists, determine whether all upgradeable parts of the vehicle end include the parts to be upgraded; if the parts to be upgraded are included, send an upgrade package link associated with the version update task to the vehicle end, so that the vehicle end downloads the version update task according to the upgrade package link, and upgrades the current versions of the parts to be upgraded based on the version update task; The vehicle side is used to send the version task update signal of the vehicle, the car series to which the vehicle belongs, and the current versions of all upgradeable parts of the vehicle to the server if a power-on signal is received, so that the server can determine whether there is a version update task corresponding to the car series and whether all upgradeable parts of the vehicle include parts to be upgraded based on the version task update signal; if the upgrade package link associated with the version update task sent by the server is received, the version update task is downloaded; based on the version update task, the current version of the parts to be upgraded of the vehicle is upgraded.

Images