Vehicle OTA upgrading method, device and equipment and storage medium

Abstract

The invention discloses a vehicle OTA upgrading method, device and equipment and a storage medium, and relates to the technical field of vehicle communication, and the vehicle OTA upgrading method comprises the steps that software version information of a target vehicle is obtained, and a vehicle software baseline is obtained according to the software version information; obtaining upgradable domain software version information according to the target software baseline and the vehicle software baseline; obtaining a target OTA upgrade package according to the upgradable domain software version information, and sending the target OTA upgrade package to the target vehicle; according to the method, version information of a target vehicle is compared with current latest vehicle version information, whether the vehicle needs to be subjected to OTA upgrading or not is judged, if upgrading is needed, domain version information needing to be upgraded is obtained through a comparison result, and an OTA upgrading package is obtained for a software version needing to be upgraded of the vehicle based on a domain; the target vehicle is enabled to carry out domain software version upgrading on the vehicle through the OTA upgrading package, other domain software baselines of the vehicle are not influenced, and the workload of frequent whole vehicle OTA upgrading is reduced.

Description

Technical Field

[0001] The present application relates to the field of vehicle communication technology, and in particular to a vehicle OTA upgrade method, device, equipment and storage medium. Background Art

[0002] Currently, most OEMs have the ability to perform vehicle OTA (Over-the-Air Technology) upgrades. However, as the number of ECUs that support OTA upgrades increases and the frequency of software iterations accelerates, some vehicles may have an older version of their ECU before they leave the factory. In addition, vehicles that leave the factory together may also have different version statuses, making upgrade tasks difficult to determine and control.

[0003] Currently, most OEMs have the ability to OTA upgrade the entire vehicle. However, with the compatibility issues caused by hardware changes and software iterations, there are many vehicles with different versions on the market. For these vehicles, if OTA upgrades are to be performed, there will be complex baseline version matching relationships. N baseline versions need to be manually created to meet the N vehicle versions, and N upgrade tasks will be created. This will increase the load on the cloud, reduce task deployment efficiency, and increase task error rates. Currently, OTA upgrades are performed when a single ECU of a vehicle is iterated, and the vehicle software baseline changes accordingly, resulting in frequent adjustments to OTA strategy deployment, which seriously increases the workload.

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

[0005] The main purpose of this application is to provide a vehicle OTA upgrade method, device, equipment and storage medium, aiming to solve the technical problem that OTA upgrades are currently performed when a single ECU of a vehicle is iterated, and the software baseline of the entire vehicle changes accordingly, resulting in frequent adjustments to OTA strategy deployment and a serious increase in workload.

[0006] To achieve the above objectives, the present application proposes a vehicle OTA upgrade method, the vehicle OTA upgrade method comprising:

[0007] Acquire software version information of a target vehicle, and obtain a vehicle software baseline according to the software version information, wherein the vehicle software baseline includes at least one domain software baseline;

[0008] Obtaining upgradeable domain software version information according to the target software baseline and the vehicle software baseline;

[0009] A target OTA upgrade package is obtained according to the upgradeable domain software version information and the target OTA upgrade package is sent to the target vehicle, so that the target vehicle performs an OTA upgrade according to the target OTA upgrade package.

[0010] In one embodiment, the step of obtaining software version information of the target vehicle and obtaining a vehicle software baseline according to the software version information includes:

[0011] Obtaining software version information of the target vehicle, and obtaining version information of the reference domain according to the software version information;

[0012] Obtaining the domain software baseline of each reference domain according to the version information of each reference domain and the domain software baseline configuration;

[0013] A vehicle software baseline is obtained according to the domain software baseline and the vehicle software baseline configuration.

[0014] In one embodiment, the step of obtaining the software version information of the target vehicle, before obtaining the vehicle software baseline according to the software version information, further includes:

[0015] Acquire a reference domain of a target vehicle and software version information of the reference domain;

[0016] Determine a domain software baseline configuration of a reference domain according to the software version information;

[0017] A vehicle software baseline configuration is obtained according to the domain software baseline configuration.

[0018] In one embodiment, obtaining the upgradeable domain software version information according to the target software baseline and the vehicle software baseline includes:

[0019] Comparing the target software baseline with the vehicle software baseline to obtain a software baseline to be upgraded;

[0020] Obtain target version information according to the software baseline to be upgraded and the domain software baseline configuration;

[0021] When the target version information meets a preset precondition, the target version information is used as the upgradeable domain software version information.

[0022] In one embodiment, before obtaining the upgradeable domain software version information according to the target software baseline and the vehicle software baseline, the method further includes:

[0023] Get the latest software version;

[0024] Updating the domain software baseline according to the latest software version to obtain an updated domain software baseline;

[0025] The target software baseline is obtained according to the updated domain software baseline.

[0026] In one embodiment, when the target version information meets a preset precondition, using the target version information as the upgradeable domain software version information includes:

[0027] Get the previous version information of the target version information;

[0028] When the pre-version information and the software version information of the target vehicle match each other, the target version information satisfies the preset pre-condition and the target version information is used as the upgradeable domain software version information.

[0029] In one embodiment, obtaining a target OTA upgrade package according to the upgradeable domain software version information and sending the target OTA upgrade package to the target vehicle includes:

[0030] Query the target OTA upgrade package according to the upgradeable domain software version information;

[0031] Sending upgradeable domain software version information to the target vehicle to obtain an upgrade instruction fed back by the target vehicle;

[0032] Send the target OTA upgrade package to the target vehicle according to the upgrade instruction.

[0033] In addition, to achieve the above purpose, the present application also proposes a vehicle OTA upgrade device, the vehicle OTA upgrade device comprising:

[0034] An information acquisition module, used to acquire software version information of a target vehicle, and obtain a vehicle software baseline according to the software version information, wherein the vehicle software baseline includes at least one domain software baseline;

[0035] An OTA upgrade module, used to obtain upgradeable domain software version information according to a target software baseline and the vehicle software baseline;

[0036] The OTA upgrade module is also used to obtain a target OTA upgrade package according to the upgradeable domain software version information and send the target OTA upgrade package to the target vehicle, so that the target vehicle performs OTA upgrade according to the target OTA upgrade package.

[0037] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle OTA upgrade device, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, and the computer program is configured to implement the steps of the vehicle OTA upgrade method described above.

[0038] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the vehicle OTA upgrade method described above are implemented.

[0039] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the vehicle OTA upgrade method described above are implemented.

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

[0041] By comparing the version information of the target vehicle with the current latest vehicle version information, it is determined whether the vehicle needs to be upgraded through OTA. If an upgrade is required, the domain version information that needs to be upgraded is obtained through the comparison result, and the OTA upgrade package is obtained based on the domain software version that needs to be upgraded for the vehicle. The target vehicle can upgrade the domain software version of the vehicle through the OTA upgrade package without affecting the baseline of other domain software of the vehicle, thereby reducing the workload of frequent OTA upgrades of the entire vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0044] Figure 1 A flow chart of the first embodiment of the vehicle OTA upgrade method of the present application;

[0045] Figure 2 A schematic diagram of a domain-based OTA upgrade process provided in Embodiment 1 of the vehicle OTA upgrade method of the present application;

[0046] Figure 3 A flow chart of the second embodiment of the vehicle OTA upgrade method of the present application;

[0047] Figure 4 A schematic diagram of the OTA upgrade principle provided in Example 2 of the vehicle OTA upgrade method of this application;

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

[0049] Figure 6 This is a schematic diagram of the device structure of the hardware operating environment involved in the vehicle OTA upgrade method in the embodiment of the present application. DETAILED DESCRIPTION

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

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

[0052] The main solution of the embodiment of the present application is: obtain the software version information of the target vehicle, obtain the vehicle software baseline according to the software version information, the vehicle software baseline includes at least one domain software baseline; obtain the upgradeable domain software version information according to the target software baseline and the vehicle software baseline; obtain the target OTA upgrade package according to the upgradeable domain software version information and send the target OTA upgrade package to the target vehicle, so that the target vehicle performs OTA upgrade according to the target OTA upgrade package.

[0053] In this embodiment, for ease of description, the following description is made by taking identification of a vehicle OTA upgrade device as the execution subject.

[0054] Due to the existing technology, most OEMs currently have the ability to upgrade the entire vehicle via OTA (Over-the-Air Technology). However, as the number of ECUs that support OTA upgrades increases and the frequency of software iterations accelerates, the version corresponding to the ECU of some vehicles may already be in a low version state before they are shipped out of the factory. In addition, the version status of vehicles shipped out of the same factory may also be different, making upgrade tasks difficult to determine and control.

[0055] Currently, most OEMs have the ability to OTA upgrade the entire vehicle. However, with the compatibility issues caused by hardware changes and software iterations, there are many vehicles with different versions on the market. For these vehicles, if OTA upgrades are to be performed, there will be complex baseline version matching relationships. N baseline versions need to be manually created to meet the N vehicle versions, and N upgrade tasks will be created. This will increase the load on the cloud, reduce task deployment efficiency, and increase task error rates. Currently, OTA upgrades are performed when a single ECU of a vehicle is iterated, and the vehicle software baseline changes accordingly, resulting in frequent adjustments to OTA strategy deployment, which seriously increases the workload.

[0056] The present application provides a solution, which determines whether the vehicle needs to be upgraded OTA by comparing the version information of the target vehicle with the current latest vehicle version information. If an upgrade is required, the domain version information that needs to be upgraded is obtained through the comparison result, and an OTA upgrade package is obtained based on the domain software version that needs to be upgraded for the vehicle. The target vehicle can upgrade the domain software version of the vehicle through the OTA upgrade package without affecting the baseline of other domain software of the vehicle, thereby reducing the workload of frequent OTA upgrades of the entire vehicle.

[0057] It can be seen from the above embodiments that the present application discloses a vehicle OTA upgrade method, device, equipment and storage medium, which relates to the field of vehicle communication technology, and discloses a vehicle OTA upgrade method: obtaining the software version information of the target vehicle, and obtaining the vehicle software baseline according to the software version information; obtaining the upgradeable domain software version information according to the target software baseline and the vehicle software baseline; obtaining the target OTA upgrade package according to the upgradeable domain software version information and sending the target OTA upgrade package to the target vehicle; the method compares the version information of the target vehicle with the current latest vehicle version information to determine whether the vehicle needs to be upgraded via OTA. If an upgrade is required, the domain version information that needs to be upgraded is obtained through the comparison result, and the OTA upgrade package is obtained based on the domain software version that needs to be upgraded for the vehicle, so that the target vehicle can upgrade the domain software version of the vehicle through the OTA upgrade package, without affecting the software baselines of other domains of the vehicle, thereby reducing the workload of frequent OTA upgrades of the entire vehicle.

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

[0059] Based on this, the embodiment of the present application provides a vehicle OTA upgrade method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the vehicle OTA upgrade method of the present application.

[0060] In this embodiment, the vehicle OTA upgrade method includes steps S10 to S40:

[0061] Step S10, obtaining software version information of the target vehicle, and obtaining a vehicle software baseline according to the software version information, wherein the vehicle software baseline includes at least one domain software baseline.

[0062] It is understandable that the automotive ECUs are intertwined, dividing the vehicle's electronic and electrical architecture into five domains: cockpit domain I, power domain P, chassis domain C, body domain B, and autonomous driving domain A. Each domain has a master domain controller DomainMaster; according to the division of labor, the master domain is equipped with multiple slavery node ECUs.

[0063] It is understandable that the formal release of software versions and information collection tables of each ECU in the vehicle forms a snapshot, defines a vehicle software version identifier, and can also be understood as the vehicle software baseline. Based on the vehicle software baseline, extract the ECU software information with OTA (Over The Air) capabilities, define an OTA software version identifier, and facilitate the alignment of the vehicle OTA software version identifier, that is, the OTA software baseline.

[0064] It should be noted that the software version information can be understood as version information composed of the versions of different ECU software of the vehicle. The software version information includes the version information of each software of the vehicle. For example, the version of software A is version 4, and the version of software B is version 2.

[0065] It should be noted that the vehicle software baseline can be manually defined and composed of software baselines of various domains. For example, the vehicle software baseline can be expressed as D11.2-D22.3-D35.7-D43.2···D i 1.2. Among them, D i Indicates the domain name of the vehicle. For example, if the vehicle's software baseline is divided into five domains, the domain name corresponding to each domain is D1 to D5, where 1.2 means that in the domain with the domain name D1, the main controller software version is the first version and the sub-controller software version is the second version. D11.2 can be understood as the domain software baseline.

[0066] It is understandable that the vehicle software baseline is composed of domain software baselines. The number of domain software baselines can be obtained according to the division situation, and can be one or more. This embodiment does not limit this.

[0067] In a feasible implementation manner, step S10 may include steps A101 to A103:

[0068] Step A101, obtaining a reference domain of a target vehicle and software version information of the reference domain.

[0069] It is understandable that the reference domain of the target vehicle may be the domains into which the software of the target vehicle is divided, and the software version information of the reference domain may be the software version information of the main controller and each sub-controller in the reference domain.

[0070] Step A102: determining a domain software baseline configuration of a reference domain according to the software version information.

[0071] It is understood that the software baseline configuration can be understood as a pre-set format, such as D11.2-D22.3-D35.7-D43.2···D i 1.2, where D represents the domain name, and 1.2.3.3 represent the software versions of the four sub-controllers respectively.

[0072] It should be understood that the domain software baseline configuration may be an expression format of the versions of the main controller and each sub-controller under the domain.

[0073] Step A103, obtaining a vehicle software baseline configuration according to the domain software baseline configuration.

[0074] It should be noted that it is predetermined that the controller software of the target vehicle is divided into several reference domains, and it is further determined that each reference domain has a main controller and several sub-controllers, thereby determining the software configuration of the reference domain. Based on the software configuration of each reference domain, a priority order is defined for each domain, and the software configuration of each reference domain is arranged based on the priority order of each domain to obtain the vehicle software configuration.

[0075] In this implementation, the software baseline of each domain is configured according to the division of the domains of the target vehicle and the division of the controllers and sub-controllers of each domain. At the same time, the configuration of the vehicle software baseline is obtained based on the order of each encountered software configuration and each domain in the vehicle software baseline. The configuration based on the vehicle software baseline can more clearly represent the vehicle version, which is convenient for locating the vehicle software version according to the domain.

[0076] The above are merely feasible implementations before step S10 provided in this embodiment, and this embodiment does not specifically limit the specific implementations before step S10.

[0077] Step S20, obtaining upgradeable domain software version information according to the target software baseline and the vehicle software baseline.

[0078] It is understandable that the target software baseline may be a vehicle software baseline composed of the latest vehicle software version information.

[0079] It should be understood that the upgradeable domain version information can be understood as the version information corresponding to the vehicle's upgradeable software. It should be emphasized that if each software is divided into different domains, the upgradeable domain software version information may also include the domain name, and the upgradeable software (i.e., controller) under the domain name, and the version information of the software that can be upgraded. For example, the upgradeable domain software version information may be that the software of the main controller of the domain name D3 can be upgraded to version 7.

[0080] In a feasible implementation, step S20 may include steps A21 to A23:

[0081] Step A21, comparing the target software baseline with the vehicle software baseline to obtain the software baseline to be upgraded.

[0082] It is understandable that by comparing the target software baseline and the vehicle software baseline, the differences in the software calculations between the two can be obtained.

[0083] In a specific implementation, for example, if the target baseline is D11.2-D22.3-D35.7-D43.2-D51.2, and the vehicle software baseline is D11.2-D22.3-D35.6-D42.2-D51.2, it can be understood that the software baselines to be upgraded are D35.7 and D43.2.

[0084] It should be noted that before obtaining the upgradeable domain software version information based on the target software baseline and the vehicle software baseline, it also includes: obtaining the latest software version; updating the domain software baseline according to the latest software version to obtain an updated domain software baseline; and obtaining the target software baseline based on the updated domain software baseline.

[0085] Among them, it is understandable that the latest software version information can be the automatic detection engineer updating the various software of the vehicle and the updated software version.

[0086] Among them, it should be understood that the domain software baseline is updated according to the latest software version, and the updated domain software baseline can be obtained by querying the version information of each vehicle software, and obtaining the vehicle sub-software after updating, and the updated version is the third version. Then, for the software belonging to the domain with the domain name D2, the domain software baseline is updated from D21.2 to D21.3.

[0087] It is understandable that the target software baseline obtained according to the updated domain software baseline is an updated iteration of the target software baseline, and the updated domain software baseline replaces the same software baseline in the original target software baseline to obtain the target software baseline.

[0088] Step A22, obtaining target version information according to the software baseline to be upgraded and the domain software baseline configuration.

[0089] It can be understood that the target version information may be the latest version information of the software that can be upgraded for the target vehicle.

[0090] In a specific implementation, if the software baseline to be upgraded is D35.7 and the current version information is D35.6, according to the pre-set domain software configuration, it can be obtained that the sub-controller A software can be upgraded, and the sub-software can be upgraded to the 7th version.

[0091] Furthermore, the target version information may be that software A can be upgraded to version 7.

[0092] Step A23: When the target version information meets a preset precondition, the target version information is used as the upgradeable domain software version information.

[0093] It is understandable that the prerequisite can be understood as determining whether the current version information of the vehicle meets the version upgrade conditions. During the upgrade process of some software, the latter software version requires part of the content of the previous software version as support for upgrading. There may also be other situations where it is necessary to first determine whether the prerequisites for the upgrade are met.

[0094] It should be noted that when the target version information meets the preset prerequisite, the target version information is used as the upgradeable domain software version information, including: obtaining the predecessor version information of the target version information; when the predecessor version information and the software version information of the target vehicle match, the target version information meets the preset prerequisite and the target version information is used as the upgradeable domain software version information.

[0095] It is understandable that obtaining the predecessor version information of the target version information may be obtaining the predecessor version required to upgrade the software to be upgraded to the target version. For example, if software A is to be upgraded to version 7, the prerequisite is that at least the predecessor version is version 5.

[0096] Among them, it should be noted that when the previous version information and the software version information of the target vehicle match each other, the target version information satisfies the preset prerequisite and using the target version information as the upgradeable domain software version information can be to match the version information of the upgradeable software with the previous version information, and if they match, it is considered to meet the preset prerequisite information; if not, no upgrade is performed.

[0097] It should be emphasized that the reason why the vehicle cannot meet the prerequisite version information may be that the vehicle has been offline for a long time and the version has not been updated in time, resulting in a large overlap between the vehicle software version and the latest vehicle software version, which cannot meet the preset prerequisites and thus cannot be upgraded.

[0098] In the specific implementation, for example, if you want to upgrade software A to version 7, the prerequisite is that at least the previous version is version 5. If the current version of the vehicle is version 6, it is considered to be a match; if the current version is version 4, it is considered that the vehicle cannot meet the previous version information.

[0099] It is understandable that when the previous version information cannot be met, the previous version information of the target version can be obtained, and the previous version information can be used as the new target version information. The vehicle is first upgraded to the previous version and then upgraded.

[0100] In this implementation, the vehicle software baseline and the target software baseline are compared to determine whether a domain software baseline is needed. The specific software that needs to be upgraded and the software version to be upgraded are further determined based on the domain software machine selection. At the same time, it is pre-determined whether the software to be upgraded meets the upgrade conditions. While ensuring the success of the software upgrade, the software version in each domain is upgraded, and repeated updates of other OTA software version deployments are reduced.

[0101] The above are merely feasible implementations before step S20 provided in this embodiment, and this embodiment does not specifically limit the specific implementations before step S20.

[0102] Step S30, obtaining a target OTA upgrade package according to the upgradeable domain software version information and sending the target OTA upgrade package to the target vehicle, so that the target vehicle performs OTA upgrade according to the target OTA upgrade package.

[0103] It is understandable that OTA upgrade package refers to a method of sending software updates directly to devices via wireless networks. It is widely used in electronic devices with embedded systems such as smartphones, tablets, smart TVs, and cars to provide system updates, security patches, new function additions and other services without the need for users to connect to a computer or visit a service center.

[0104] It should be understood that the target OTA upgrade package may be an application program or other files including software updates corresponding to the upgradeable domain software version information.

[0105] In a feasible implementation, step S30 may include steps A31 to A33:

[0106] Step A11, querying a target OTA upgrade package according to the upgradeable domain software version information.

[0107] It is understandable that when upgrading vehicle software, multiple vehicle software may be upgraded at the same time, multiple upgrade programs may exist at the same time, and the same software may include multiple upgrade programs.

[0108] It should be understood that the upgradeable domain software version includes the software corresponding to the upgradeable software and the corresponding upgrade package version.

[0109] It should be understood that the target OTA upgrade package can be an upgrade package that includes the latest version of the upgradeable software. If the vehicle software needs to be upgraded to a predecessor version that meets the latest version first, the target OTA upgrade package can also be an upgrade package corresponding to the predecessor version.

[0110] Step A12, sending the upgradeable domain software version information to the target vehicle to obtain the upgrade instruction fed back by the target vehicle.

[0111] It is understandable that after the upgradeable domain version information is fed back to the vehicle side, the user can determine whether to upgrade. If the user is sure to upgrade, a signal confirming the upgrade can be fed back based on the upgradeable domain version information.

[0112] It should be understood that the upgrade instruction may be an instruction generated after the user confirms that an upgrade is required according to the upgradeable domain software version information, and an upgrade package is sent to the user based on the instruction.

[0113] Step A13: sending the target OTA upgrade package to the target vehicle according to the upgrade instruction.

[0114] It is understandable that the upgrade package is sent when it is determined that the user needs to upgrade, so as to avoid autonomous upgrades causing inconvenience to the user during use and affecting the user experience.

[0115] In the specific implementation, the domain-based OTA upgrade process can refer to Figure 2 In the figure, the cloud is used as the execution subject of this embodiment. The cloud obtains the vehicle software baseline according to the defined domain, and extracts the domain-based OTA software baseline through the vehicle software baseline, that is, extracts the upgradeable software baseline, and obtains the OTA target software baseline based on the domain corresponding to the upgradeable software baseline; the vehicle-side computer determines the vehicle's software baseline, and the computer queries the OTA platform for the latest OTA baseline and sends it to the cloud. The computer actively performs OTA upgrades based on the OTA target software baseline fed back by the cloud.

[0116] In this implementation, the software baselines of various domains on the vehicle side are obtained to determine whether an upgrade is possible. If the upgrade is possible, the latest software version will be sent to the user. After the user confirms, the upgrade package will be sent to perform the software upgrade. There is no need to deploy OTA policies and perform OTA push. OTA operations only need to maintain OTA baseline information. OTA operating costs are lower, and users and after-sales do not need to wait for OTA operation task deployment, and can directly query and upgrade OTA baselines on the vehicle side.

[0117] The above are only feasible implementations of step S30 provided in this embodiment, and this embodiment does not specifically limit the specific implementation of step S30.

[0118] This embodiment provides a vehicle OTA upgrade method, which compares the version information of the target vehicle with the current latest vehicle version information to determine whether the vehicle needs to be upgraded via OTA. If an upgrade is required, the domain version information that needs to be upgraded is obtained through the comparison result, and an OTA upgrade package is obtained based on the domain software version that needs to be upgraded for the vehicle. The target vehicle can upgrade the domain software version of the vehicle through the OTA upgrade package without affecting the software baselines of other domains of the vehicle, thereby reducing the workload of frequent OTA upgrades of the entire vehicle.

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

[0120] Step S11, obtaining software version information of the target vehicle, and obtaining version information of the reference domain according to the software version information.

[0121] It is understandable that the software version information of the target vehicle may be the software version information of the entire vehicle, and the version information of each domain is determined based on the domain to which each software belongs.

[0122] It is understandable that the reference domain may be any domain of the target vehicle's domain.

[0123] Step S12, obtaining the domain software baseline of each reference domain according to the version information of each reference domain and the domain software baseline configuration.

[0124] It is understandable that the domain software baseline can be the software version information of each controller (main controller, sub-controller) in the domain expressed in a fixed format, for example I5.1, which means that the main controller version in the domain with domain name I is version 5, and the sub-controller is version 1.

[0125] It should be understood that the version information of each reference domain includes the version information of each software in the reference domain.

[0126] It should be understood that the domain software baseline configuration can be understood as the meaning represented by each symbol of each domain software baseline. For example, in I5.1, I represents the cockpit domain, 5 represents that the version of the main controller in the cockpit domain is the 5th version, and 1 represents that the version of the first sub-controller pre-set in the domain is the 1st version.

[0127] It should be noted that, in the present invention, after the operation engineer deploys the OTA software baseline based on the domain concept definition, there is no need to deploy push tasks according to the VIN list. The car owner can directly and actively query and select the required OTA target baselines for each domain on the vehicle computer, complete the software upgrade, and report the latest vehicle software baseline in real time.

[0128] It should be noted that the software baseline is defined based on the concept of "domain", that is, the software baseline version is composed of sub-baselines of the five major domains, and the domain baseline is defined by the snapshot table of the software information of each sub-controller in the domain. For example, the vehicle software baseline released on August 14, 2014 is I5.1_P4.3_C3.2_B3.1_A4.8, which means: the cockpit domain sub-baseline is I5.1; the power domain sub-baseline is P4.2; the chassis domain sub-baseline is C3.2; the body domain sub-baseline is B3.1; and the autonomous driving domain sub-baseline is P4.3.

[0129] It is worth noting that the domain-based vehicle software baseline is different from the vehicle with a large number of ECUs. As long as one ECU software has an iteration, the entire vehicle software baseline will change, and the change point of the baseline cannot be intuitively identified; it is also different from the OTA real-time determination of the vehicle software baseline. When the software of a certain ECU is in an old version, the entire vehicle software baseline information cannot be updated, resulting in a large deviation in the vehicle software baseline determination; it is also different from the traditional OTA upgrade, which requires the operation engineer to first deploy the OTA strategy on the OTA platform with ECU as the unit, and then lock the vehicle VIN list. After pushing to the vehicles within the locked range, the vehicles in the vehicle VIN list can be upgraded for OTA.

[0130] It should be further explained that operation engineers do not need to deploy OTA policies first to automatically obtain the latest OTA software upgrade package for upgrade; the deployed combined package OTA policy is based on changes in the domain baseline, and OTA policy deployment is performed on a single domain without the need to adjust other domains.

[0131] Step S13, obtaining a vehicle software baseline according to the domain software baseline and the vehicle software baseline configuration.

[0132] It is understandable that the vehicle software baseline configuration can be composed of all domain software baselines. For example, the whole vehicle software baseline is I5.1_P4.3_C3.2_B3.1_A4.8, where I5.1 represents the cockpit domain sub-baseline; P4.2 represents the power domain sub-baseline; C3.2 represents the chassis domain sub-baseline; B3.1 represents the body domain sub-baseline; and P4.3 represents the autonomous driving domain sub-baseline.

[0133] It should be understood that the vehicle software baseline configuration is obtained by predefining the position of each domain in the vehicle software baseline.

[0134] It should be noted that the present invention has changed the traditional OTA push and upgrade method. According to the concept of domain, the software baseline of each domain is defined to form a large software baseline for the whole vehicle. The whole vehicle uses the concept of domain to determine the software baseline version of the vehicle in real time, with a smaller granularity and more accurate baseline information.

[0135] It should be understood that the OTA platform uses the domain-based baseline to deploy the latest target OTA baseline. Once deployed, it is applicable to all related vehicles. When a certain ECU software is updated, only the ECU information needs to be updated, and there is no need to redeploy the entire strategy. This facilitates the overall alignment of vehicle software and reduces the workload of OTA operation deployment strategy.

[0136] It should be emphasized that car owners can actively query the OTA platform for the latest target baseline on the car computer and directly perform OTA upgrades. They no longer rely on task deployment on the platform side, making OTA upgrades more convenient to use.

[0137] In specific implementation, the implementation of the vehicle OTA upgrade method may include defining a domain-based software baseline, deploying the OTA baseline on the OTA platform, querying the latest software baseline on the vehicle machine, and performing OTA active upgrades. The implementation principle can be mainly referred to Figure 4 In the figure, the domain-based vehicle software baseline is first defined, the OTA software baseline is extracted and deployed in the cloud, and the vehicle computer determines the current software baseline of the vehicle. The vehicle computer queries the latest OTA baseline of the OTA platform, and compares the latest OTA baseline with the current vehicle software baseline. If an upgrade is required, an upgrade request and the current vehicle software baseline are sent to the cloud. The cloud further determines the software version information that needs to be upgraded and sends it to the vehicle, and the user decides whether to upgrade.

[0138] This embodiment provides a vehicle OTA upgrade method, which compares the versions of each sub-controller by domain, generates a software baseline for each domain, and then combines the software baselines of each domain to generate a vehicle software baseline. The software baseline information is more intuitive, has a smaller granularity, and the software version data is more accurate.

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

[0140] This application also provides a vehicle OTA upgrade device, please refer to Figure 5 , the vehicle OTA upgrade device comprises:

[0141] An information acquisition module 10 is used to acquire software version information of a target vehicle, and obtain a vehicle software baseline according to the software version information, wherein the vehicle software baseline includes at least one domain software baseline;

[0142] An OTA upgrade module 20, configured to obtain upgradeable domain software version information according to a target software baseline and the vehicle software baseline;

[0143] The OTA upgrade module 20 is further used to obtain a target OTA upgrade package according to the upgradeable domain software version information and send the target OTA upgrade package to the target vehicle, so that the target vehicle performs OTA upgrade according to the target OTA upgrade package.

[0144] The vehicle OTA upgrade device provided by the present application adopts the vehicle OTA upgrade method in the above embodiment, which can solve the technical problem that OTA upgrade will be performed when a single ECU of the vehicle is iterated, and the software baseline of the whole vehicle changes accordingly, resulting in frequent adjustment of OTA strategy deployment and serious increase in workload. Compared with the prior art, the beneficial effects of the vehicle OTA upgrade device provided by the present application are the same as the beneficial effects of the vehicle OTA upgrade method provided by the above embodiment, and the other technical features in the vehicle OTA upgrade device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0145] In one implementation, the information acquisition module 10 is further used to acquire software version information of the target vehicle, and obtain version information of the reference domain according to the software version information;

[0146] Obtaining the domain software baseline of each reference domain according to the version information of each reference domain and the domain software baseline configuration;

[0147] A vehicle software baseline is obtained according to the domain software baseline and the vehicle software baseline configuration.

[0148] In one implementation, the information acquisition module 10 is further used to acquire a reference domain of the target vehicle and software version information of the reference domain;

[0149] Determine a domain software baseline configuration of a reference domain according to the software version information;

[0150] A vehicle software baseline configuration is obtained according to the domain software baseline configuration.

[0151] In one implementation, the OTA upgrade module 20 is further used to compare the target software baseline with the vehicle software baseline to obtain the software baseline to be upgraded;

[0152] Obtain target version information according to the software baseline to be upgraded and the domain software baseline configuration;

[0153] When the target version information meets a preset precondition, the target version information is used as the upgradeable domain software version information.

[0154] In one implementation, the OTA upgrade module 20 is also used to obtain the latest software version;

[0155] Updating the domain software baseline according to the latest software version to obtain an updated domain software baseline;

[0156] The target software baseline is obtained according to the updated domain software baseline.

[0157] In one implementation, the OTA upgrade module 20 is further used to obtain the pre-version information of the target version information;

[0158] When the pre-version information and the software version information of the target vehicle match each other, the target version information satisfies the preset pre-condition and the target version information is used as the upgradeable domain software version information.

[0159] In one implementation, the OTA upgrade module 20 is further used to query the target OTA upgrade package according to the upgradeable domain software version information;

[0160] Sending upgradeable domain software version information to the target vehicle to obtain an upgrade instruction fed back by the target vehicle;

[0161] Send the target OTA upgrade package to the target vehicle according to the upgrade instruction.

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

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

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

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

[0166] The vehicle OTA upgrade device provided by the present application adopts the vehicle OTA upgrade method in the above embodiment, which can solve the technical problem that OTA upgrade will be performed when a single ECU of the vehicle is iterated, and the software baseline of the whole vehicle changes accordingly, resulting in frequent adjustment of OTA strategy deployment and serious increase in workload. Compared with the prior art, the beneficial effects of the vehicle OTA upgrade device provided by the present application are the same as the beneficial effects of the vehicle OTA upgrade method provided by the above embodiment, and the other technical features in the vehicle OTA upgrade device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

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

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

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

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

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

[0172] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the vehicle OTA upgrade device, the vehicle OTA upgrade device: obtains the software version information of the target vehicle, obtains the vehicle software baseline according to the software version information, and the vehicle software baseline includes at least one domain software baseline; obtains the upgradeable domain software version information according to the target software baseline and the vehicle software baseline; obtains the target OTA upgrade package according to the upgradeable domain software version information and sends the target OTA upgrade package to the target vehicle, so that the target vehicle performs OTA upgrade according to the target OTA upgrade package.

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

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

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

[0176] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned vehicle OTA upgrade method, and can solve the technical problem that OTA upgrades are performed when a single ECU of the vehicle is iterated, and the software baseline of the whole vehicle changes accordingly, resulting in frequent adjustments to OTA strategy deployment, which seriously increases the workload. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the vehicle OTA upgrade method provided by the above-mentioned embodiment, and will not be repeated here.

[0177] The present application also provides a computer program product, including a computer program, which implements the steps of the vehicle OTA upgrade method as described above when executed by a processor.

[0178] The computer program product provided by this application can solve the technical problem that OTA upgrades are performed when a single ECU of a vehicle is iterated, and the software baseline of the entire vehicle changes accordingly, resulting in frequent adjustments to OTA strategy deployment and a serious increase in workload. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the vehicle OTA upgrade method provided in the above embodiment, and will not be repeated here.

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

Claims

1. A vehicle OTA upgrade method, characterized in that: The vehicle OTA upgrade method comprises: Acquire software version information of a target vehicle, and obtain a vehicle software baseline according to the software version information, wherein the vehicle software baseline includes at least one domain software baseline; Obtaining upgradeable domain software version information according to the target software baseline and the vehicle software baseline; A target OTA upgrade package is obtained according to the upgradeable domain software version information and the target OTA upgrade package is sent to the target vehicle, so that the target vehicle performs an OTA upgrade according to the target OTA upgrade package.

2. The vehicle OTA upgrade method according to claim 1, characterized in that: The step of obtaining software version information of the target vehicle and obtaining a vehicle software baseline according to the software version information includes: Obtaining software version information of the target vehicle, and obtaining version information of the reference domain according to the software version information; Obtaining the domain software baseline of each reference domain according to the version information of each reference domain and the domain software baseline configuration; A vehicle software baseline is obtained according to the domain software baseline and the vehicle software baseline configuration.

3. The vehicle OTA upgrade method according to claim 2, characterized in that: The step of acquiring the software version information of the target vehicle and obtaining the version information of the reference domain according to the software version information further includes: Acquire a reference domain of a target vehicle and software version information of the reference domain; Determine a domain software baseline configuration of a reference domain according to the software version information; A vehicle software baseline configuration is obtained according to the domain software baseline configuration.

4. The vehicle OTA upgrade method according to claim 1, characterized in that: The obtaining the upgradeable domain software version information according to the target software baseline and the vehicle software baseline includes: Comparing the target software baseline with the vehicle software baseline to obtain a software baseline to be upgraded; Obtain target version information according to the software baseline to be upgraded and the domain software baseline configuration; When the target version information meets a preset precondition, the target version information is used as the upgradeable domain software version information.

5. The vehicle OTA upgrade method according to claim 1, characterized in that: Before obtaining the upgradeable domain software version information according to the target software baseline and the vehicle software baseline, the method further includes: Get the latest software version; Updating the domain software baseline according to the latest software version to obtain an updated domain software baseline; The target software baseline is obtained according to the updated domain software baseline.

6. The vehicle OTA upgrade method according to claim 4, characterized in that: When the target version information meets the preset precondition, using the target version information as the upgradeable domain software version information includes: Get the previous version information of the target version information; When the pre-version information and the software version information of the target vehicle match each other, the target version information satisfies the preset pre-condition and the target version information is used as the upgradeable domain software version information.

7. The vehicle OTA upgrade method according to claim 1, characterized in that: The step of obtaining a target OTA upgrade package according to the upgradeable domain software version information and sending the target OTA upgrade package to the target vehicle includes: Query the target OTA upgrade package according to the upgradeable domain software version information; Sending upgradeable domain software version information to the target vehicle to obtain an upgrade instruction fed back by the target vehicle; Send the target OTA upgrade package to the target vehicle according to the upgrade instruction.

8. A vehicle OTA upgrade device, characterized in that: The vehicle OTA upgrade device comprises: An information acquisition module, used to acquire software version information of a target vehicle, and obtain a vehicle software baseline according to the software version information, wherein the vehicle software baseline includes at least one domain software baseline; An OTA upgrade module, used to obtain upgradeable domain software version information according to a target software baseline and the vehicle software baseline; The OTA upgrade module is also used to obtain a target OTA upgrade package according to the upgradeable domain software version information and send the target OTA upgrade package to the target vehicle, so that the target vehicle performs OTA upgrade according to the target OTA upgrade package.

9. A vehicle OTA upgrade device, characterized in that: The device comprises: a memory, a processor, and a vehicle OTA upgrade program stored in the memory and executable on the processor, wherein the vehicle OTA upgrade program is configured to implement the vehicle OTA upgrade method according to any one of claims 1 to 7.

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

Images