CN117806672A

CN117806672A - OTA upgrading method, system, device, server and vehicle end

Info

Publication number: CN117806672A
Application number: CN202311619869.XA
Authority: CN
Inventors: 许皓羽
Original assignee: Contemporary Amperex Intelligence Technology Shanghai Ltd
Current assignee: Contemporary Amperex Intelligence Technology Shanghai Ltd
Priority date: 2023-11-29
Filing date: 2023-11-29
Publication date: 2024-04-02

Abstract

The application discloses an OTA upgrading method, an OTA upgrading system, an OTA upgrading device, a OTA upgrading server and an OTA terminal, and belongs to the technical field of software upgrading. The method comprises the following steps: receiving a current version of the vehicle end reported by the vehicle end in response to an upgrade task, wherein the upgrade task is used for indicating the vehicle end to upgrade to a target version of the vehicle end; determining a current version and a target version of a control unit to be upgraded of a vehicle end according to the current version and the target version of the vehicle end; generating a target upgrade package and an upgrade strategy of a vehicle end according to the version dependency relationship between the current version and the target version of the control unit to be upgraded and the corresponding version file packages of the control unit to be upgraded; and issuing the target upgrade package and the upgrade strategy to the vehicle end so that the vehicle end uses the target upgrade package to upgrade according to the upgrade strategy. The method realizes the generation of the target upgrade package according to the requirement, improves the suitability of the upgrade package, the vehicle end and the upgrade requirement, and improves the upgrade success rate.

Description

OTA upgrading method, system, device, server and vehicle end

Technical Field

The present disclosure relates to the field of software upgrade technologies, and in particular, to an OTA upgrade method, system, device, server, and vehicle side.

Background

OTA (Over The Air) provides an online upgrade mode, and can click upgrade on The interface to complete upgrade of upgrade equipment like upgrade of mobile phone system. However, the upgrade method is to communicate with the server and download the upgrade package in an online networking mode, the upgrade package needs to be downloaded, the size of the upgrade package is possibly different from tens KB to several G according to different upgrade contents, but for upgrade equipment, the upgrade package can be generally hundreds M to several G, and the overlarge upgrade package can cause high mobile data flow demand cost and long download time, so that the user experience is affected.

Disclosure of Invention

Therefore, the application provides an OTA upgrading method, an OTA upgrading device, an OTA upgrading system, a server, a vehicle end and a computer readable storage medium, and aims to solve the technical problem of upgrading success rate reduction in the related technology at least to a certain extent.

In order to achieve the above objective, an embodiment of a first aspect of the present application provides an OTA upgrading method, applied to a server, including:

receiving a current version of the vehicle end reported by the vehicle end in response to an upgrade task, wherein the upgrade task is used for indicating the vehicle end to upgrade to a target version of the vehicle end;

Determining a current version and a target version of a control unit to be upgraded of a vehicle end according to the current version and the target version of the vehicle end;

generating a target upgrade package and an upgrade strategy of a vehicle end according to the version dependency relationship between the current version and the target version of the control unit to be upgraded and the corresponding version file packages of the control unit to be upgraded;

and issuing the target upgrade package and the upgrade strategy to the vehicle end so that the vehicle end uses the target upgrade package to upgrade according to the upgrade strategy.

In the embodiment of the application, the server generates the target upgrade package according to the current version of the vehicle end and the target version of the vehicle end as required, so that the personalized customization of the upgrade package is realized, and the suitability of the upgrade package and the vehicle end is improved; in addition, the version dependency relationship is considered in the process of generating the target upgrade package, so that the target upgrade package is further ensured to meet the upgrade requirement of the vehicle end, the suitability of the generated target upgrade package and the upgrade requirement is improved, and the upgrade success rate is further improved.

According to one embodiment of the present application, generating a target upgrade package and an upgrade policy of a vehicle end according to a version dependency relationship between a current version and a target version of a to-be-upgraded control unit and each version file package corresponding to the to-be-upgraded control unit includes:

Determining an intermediate version and an upgrading strategy according to the version dependency relationship, wherein the intermediate version has a front dependency relationship with a target version and has a rear dependency relationship with a current version, and the upgrading strategy comprises a version upgrading sequence;

acquiring a middle version file packet corresponding to a middle version of a control unit to be upgraded and a target version file packet corresponding to a target version;

and generating a target upgrading packet according to the intermediate version file packet and the target version file packet corresponding to the control unit to be upgraded.

In the embodiment of the application, the control unit to be upgraded is determined to be upgraded from the current version to the intermediate version depending on the target version according to the version dependency relationship, and then the target upgrading package is generated according to the intermediate version package and the target version package, so that the proper upgrading package can be accurately generated as required, and the accuracy of the generated target upgrading package is improved.

According to one embodiment of the present application, when the number of control units to be upgraded is plural, generating a target upgrade package according to an intermediate version package and a target version package corresponding to the control units to be upgraded, includes:

combining the intermediate version file package and the target version file package of the same control unit to be upgraded to obtain a control unit upgrading package of each control unit to be upgraded;

And combining the control unit upgrade packages of the plurality of control units to be upgraded to generate a target upgrade package.

In the embodiment of the application, the control unit to be upgraded is required to be upgraded from the current version to the target version depending on the intermediate version, so that the target upgrading package meeting the requirements can be accurately generated according to the intermediate version package and the target version package of each control unit to be upgraded, and the upgrading success rate is further improved.

According to one embodiment of the present application, in the case that the number of control units to be upgraded is plural, the upgrade policy further includes a control unit upgrade order, and the control unit upgrade order is determined according to a control unit dependency relationship between the plural control units to be upgraded.

In the embodiment of the application, the plurality of control units to be upgraded of the vehicle end have a dependency relationship when the control of the vehicle end is realized, so that the vehicle end is required to be upgraded according to the control unit upgrading sequence included in the upgrading strategy, the upgrading failure caused by the problem of upgrading the control units to be upgraded can be avoided, and the upgrading success rate is improved.

According to one embodiment of the present application, before the target upgrade package and the upgrade policy are issued to the vehicle end, the method further includes:

And receiving an upgrade package acquisition strategy reported by the vehicle end so as to send the target upgrade package to the vehicle end based on the upgrade package acquisition strategy, wherein the upgrade package acquisition strategy is determined by the vehicle end.

In the embodiment of the application, the server issues the target upgrade package to the vehicle end according to the upgrade package acquisition strategy reported by the vehicle end, so that the on-demand downloading of the upgrade package can be realized, and the situation that the downloading of the upgrade package fails due to insufficient residual space capacity of the vehicle end is avoided.

According to one embodiment of the present application, determining a current version and a target version of a control unit to be upgraded of a vehicle end according to the current version and the target version of the vehicle end includes:

determining the current version of each control unit of the vehicle end according to the current version of the vehicle end;

determining a target version of each control unit according to the target version of the vehicle end;

and determining the control unit to be upgraded and the current version and the target version of the control unit to be upgraded from a plurality of control units at the vehicle end according to the current version and the target version of each control unit.

In the embodiment of the application, the target version of the vehicle end is usually released when the new version is released, and the versions of the control units in different target versions of the vehicle end may be different, so that the control unit to be upgraded and the current version and the target version of the control unit to be upgraded are determined according to the difference between the current version and the target version of the control unit to be upgraded, the control unit to be upgraded in the vehicle end and the target version to which the control unit to be upgraded is required to be upgraded can be accurately determined, the subsequent generation of the target upgrade package is facilitated, and the generation efficiency and the accuracy of the target upgrade package are improved.

According to one embodiment of the present application, before receiving the current version of the vehicle end reported by the vehicle end in response to the upgrade task, the method further includes:

receiving a vehicle end target version release notice of a vehicle end aiming at a target model;

and responding to the release notice of the target version of the vehicle end, and issuing an upgrading task to the vehicle end of the target model.

In the embodiment of the application, under the condition that the target version of the vehicle end needs to be released, the server receives the release notice, and the release notice indicates that the vehicle end of the target model is upgraded, so that the server can accurately determine the vehicle end to be upgraded, and issue an upgrade task to the vehicle end, and can accurately issue the upgrade task.

According to one embodiment of the present application, after receiving the vehicle-end target version release notification for the vehicle end of the target model, the method further includes:

analyzing the release notice of the target version of the vehicle end to obtain a version file package of the target version of the vehicle end and configuration description files of the version file packages;

analyzing configuration description files of the version file packages, and determining target tenants and target suppliers to which the version file packages belong;

and according to the target tenant and the target provider, different version file packages are stored in an isolated mode.

In the embodiment of the application, the version upgrade may be to upgrade part of or all of the control units of the vehicle end, and then the version file package of the control unit is carried in the release notification of the target version of the vehicle end, and different version file packages are isolated and stored to different positions according to different tenants and suppliers, so that the normalized storage of the version file package is realized, and the subsequent use is convenient.

In order to achieve the above objective, an embodiment of a second aspect of the present application provides an OTA upgrading method, applied to a vehicle end, the method including:

receiving an upgrade task issued by a server, wherein the upgrade task is used for indicating a vehicle end to upgrade to a vehicle end target version;

reporting a current version of a vehicle end to a server in response to an upgrade task, so that the server determines a current version and a target version of a control unit to be upgraded of the vehicle end according to the current version and the target version of the vehicle end, and generates a target upgrade package and an upgrade strategy of the vehicle end according to a version dependency relationship between the current version and the target version and each version file package corresponding to the control unit to be upgraded;

receiving a target upgrade package and an upgrade strategy issued by a server;

and upgrading according to the upgrading strategy by using the target upgrading package.

In the embodiment of the application, the vehicle end reports the current version of the vehicle end to the server so that the server can generate the target upgrade package according to the current version of the vehicle end and the target version of the vehicle end as required, thereby realizing personalized customization of the upgrade package and improving the suitability of the upgrade package and the vehicle end; and in addition, the version dependency relationship is considered in the process of generating the target upgrade package, so that the target upgrade package is further ensured to meet the upgrade requirement of the vehicle end, the suitability of the generated target upgrade package and the upgrade requirement is improved, and the success rate of the vehicle end for upgrading by using the target upgrade package is further improved.

According to one embodiment of the application, the upgrade strategy comprises a control unit upgrade order and a version upgrade order, the vehicle end comprises a plurality of control units to be upgraded, and the target upgrade package comprises a control unit upgrade package of each control unit to be upgraded;

using the target upgrade package to upgrade according to the upgrade strategy, comprising:

and in the process of upgrading each control unit to be upgraded, according to the version upgrading sequence of the control unit to be upgraded, using a control unit upgrading packet of the control unit to be upgraded to upgrade.

In the embodiment of the application, the vehicle end upgrades a plurality of control units to be upgraded according to the upgrading sequence of the control units and the version upgrading sequence of the control units to be upgraded, so that the influence of the upgrading of some control units to be upgraded on the control units to be upgraded depending on the control units to be upgraded is avoided, and the upgrading success rate is improved.

According to one embodiment of the present application, before receiving the target upgrade package and the upgrade policy issued by the server, the method further includes:

and determining an upgrade package acquisition strategy according to the residual space capacity of the vehicle end and reporting the upgrade package acquisition strategy to the server so that the server can send the target upgrade package to the vehicle end based on the upgrade package acquisition strategy.

In the embodiment of the application, the vehicle end determines an upgrade package acquisition strategy, namely how to download the target upgrade package according to the residual space capacity of the vehicle end, so that the on-demand downloading of the upgrade package can be realized, and the situation that the upgrade package is failed to download due to insufficient residual space capacity of the vehicle end is avoided.

According to one embodiment of the present application, before reporting the current version of the headend to the server in response to the upgrade task, the method further includes:

and determining the current state of the vehicle end so as to report the current version of the vehicle end to the server under the condition that the current state meets the upgrading condition, wherein the current state comprises one or more of a motion state, a network state and an electric quantity state.

In the embodiment of the application, before the vehicle end reports the current version of the vehicle end to the server, the vehicle end judges whether the current state of the vehicle end can be upgraded or not, and reports the current state of the vehicle end under the condition that the upgrading condition is met, so that useless information reporting is avoided, and resources are wasted.

According to one embodiment of the present application, before the upgrade is performed using the target upgrade package according to the upgrade policy, the method further includes:

and carrying out integrity check on the target upgrade package so as to carry out upgrade by using the target upgrade package under the condition that the target upgrade package is complete.

In the embodiment of the application, after the vehicle end downloads the target upgrade package, whether the target upgrade package is complete or not needs to be checked, so that the integrity of the target upgrade package used for upgrading can be ensured, and the upgrading success rate is further improved.

In order to achieve the above objective, an embodiment of a third aspect of the present application provides an OTA upgrade system, where the OTA upgrade system includes a server and a vehicle end;

the server issues an upgrade task to the vehicle end, wherein the upgrade task is used for indicating the vehicle end to upgrade to a target version of the vehicle end;

the vehicle end responds to the upgrading task and reports the current version of the vehicle end to the server;

the server determines the current version and the target version of the control unit to be upgraded of the vehicle end according to the current version and the target version of the vehicle end; generating a target upgrade package and an upgrade strategy of a vehicle end according to the version dependency relationship between the current version and the target version of the control unit to be upgraded and the corresponding version file packages of the control unit to be upgraded; issuing a target upgrade package and an upgrade strategy to a vehicle end;

And the vehicle end uses the target upgrade package to upgrade according to the upgrade strategy.

To achieve the above object, an embodiment of a fourth aspect of the present application provides an OTA upgrading device, applied to a server, where the device includes:

the first receiving module is configured to receive a current version of the vehicle end reported by the vehicle end in response to an upgrade task, wherein the upgrade task is used for indicating the vehicle end to upgrade to a target version of the vehicle end;

the determining module is configured to determine the current version and the target version of the control unit to be upgraded of the vehicle end according to the current version and the target version of the vehicle end;

the generation module is configured to generate a target upgrade package and an upgrade strategy of the vehicle end according to the version dependency relationship between the current version and the target version of the control unit to be upgraded and the version file packages corresponding to the control unit to be upgraded;

the issuing module is configured to issue the target upgrade package and the upgrade strategy to the vehicle end so that the vehicle end uses the target upgrade package to upgrade according to the upgrade strategy.

In order to achieve the above object, an embodiment of a fifth aspect of the present application provides an OTA upgrading device, applied to a vehicle end, where the device includes:

the second receiving module is configured to receive an upgrade task issued by the server, wherein the upgrade task is used for indicating the vehicle end to upgrade to a vehicle end target version;

The reporting module is configured to report a current version of the vehicle end in response to the upgrading task, so that the server determines the current version and the target version of the control unit to be upgraded of the vehicle end according to the current version and the target version of the vehicle end, and generates a target upgrading packet and an upgrading strategy of the vehicle end according to the version dependency relationship between the current version and the target version and the version file packets corresponding to the control unit to be upgraded;

the third receiving module is configured to receive the target upgrade package and the upgrade strategy issued by the server;

and the upgrading module is configured to upgrade by using the target upgrading package according to the upgrading strategy.

To achieve the above object, an embodiment of a sixth aspect of the present application provides a server, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the OTA upgrade method of any one of the first aspects above when the computer program is executed.

To achieve the above object, an embodiment of a seventh aspect of the present application provides a vehicle end, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the OTA upgrade method of any one of the second aspects above when the computer program is executed.

To achieve the above object, an eighth aspect of the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the OTA upgrading method of any one of the first aspect or the second aspect.

The foregoing description is only an overview of the technical solutions of the present application, and may be implemented according to the content of the specification in order to make the technical means of the present application more clearly understood, and in order to make the above-mentioned and other objects, features and advantages of the present application more clearly understood, the following detailed description of the present application will be given.

Drawings

Fig. 1 is a flowchart of a first OTA upgrade method provided according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a memory structure provided in accordance with an embodiment of the present application;

fig. 3 is a flowchart of a second OTA upgrade method provided according to an embodiment of the present application;

fig. 4 is a flowchart of a third OTA upgrade method provided according to an embodiment of the present application;

fig. 5 is a flowchart of a fourth OTA upgrade method provided according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an OTA upgrade system according to an embodiment of the present application;

fig. 7 is a flowchart for implementing OTA upgrade in an OTA upgrade system according to an embodiment of the present application;

Fig. 8 is an OTA upgrading device provided according to an embodiment of the present application;

fig. 9 is another OTA upgrading device provided according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a server according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a vehicle end according to an embodiment of the present application.

Detailed Description

Embodiments of the technical solutions of the present application will be described in detail below with reference to the accompanying drawings. The following examples are only for more clearly illustrating the technical solutions of the present application, and thus are only examples, and are not intended to limit the scope of protection of the present application.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having" and any variations thereof in the description and claims of the present application and in the description of the figures above are intended to cover non-exclusive inclusions.

In the description of the embodiments of the present application, the technical terms "first," "second," etc. are used merely to distinguish between different objects and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated, a particular order or a primary or secondary relationship. In the description of the embodiments of the present application, the meaning of "plurality" is two or more unless explicitly defined otherwise.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.

In the description of the embodiments of the present application, the term "and/or" is merely an association relationship describing an association object, which means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

In the description of the embodiments of the present application, the term "plurality" refers to two or more (including two), and similarly, "plural sets" refers to two or more (including two), and "plural sheets" refers to two or more (including two).

In the description of the embodiments of the present application, the orientation or positional relationship indicated by the technical terms "center", "longitudinal", "transverse", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", "axial", "radial", "circumferential", etc. are based on the orientation or positional relationship shown in the drawings, and are merely for convenience of describing the embodiments of the present application and for simplifying the description, rather than indicating or implying that the apparatus or element referred to must have a specific orientation, be configured and operated in a specific orientation, and therefore should not be construed as limiting the embodiments of the present application.

In the description of the embodiments of the present application, unless explicitly specified and limited otherwise, the terms "mounted," "connected," "secured" and the like are to be construed broadly and may be, for example, fixedly connected, detachably connected, or integrally formed; or may be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communicated with the inside of two elements or the interaction relationship of the two elements. The specific meaning of the above terms in the embodiments of the present application will be understood by those of ordinary skill in the art according to the specific circumstances.

In the prior art, the OTA cloud-based upgrade management method can respectively manage OTA objects, OTA firmware and OTA firmware software. The method specifically comprises the following steps: the version of the OTA packet is managed, an OTA plan is created according to the version update of the OTA packet, and the OTA is monitored in real time, so that the OTA can be managed in a multi-dimensional manner, and the smooth realization of the upgrading of the OTA terminal is ensured.

Therefore, the conventional OTA system is extremely strong in customization and basically has no suitability, and each manufacturer is designed according to the own traffic volume, does not have portability and cannot be widely used. Moreover, the cloud end user-defined customization of the differential packet is not provided, and the cloud end stores a large number of differential packets among different versions, so that resource waste and nonstandard management of the differential packets are caused.

According to the OTA upgrading method provided by the embodiment of the application, the to-be-upgraded control unit of the vehicle terminal is determined according to the current version of the vehicle terminal and the target version of the vehicle terminal to be upgraded, and the target upgrading package is generated according to the version dependency relationship among versions of the to-be-upgraded control unit and the file packages of the versions corresponding to the to-be-upgraded control unit, so that the on-demand customization of the upgrading package of the server is realized, and the suitability of the upgrading package and the vehicle terminal is improved; and the version dependency relationship is considered in the process of generating the target upgrade package, so that the target upgrade package is further ensured to meet the upgrade requirement of the vehicle end, the suitability of the generated target upgrade package and the upgrade requirement is improved, the upgrade success rate is further improved, and the target upgrade package is generated according to the requirement, so that the data volume of the target upgrade package is small, and the data volume and the resource occupation transmitted in the upgrade process are reduced.

Fig. 1 is a flowchart of a first OTA upgrading method according to an embodiment of the present application, where the method is applied to a server, such as a cloud server, and may specifically include the following steps.

Step 101: and receiving the current version of the vehicle end reported by the vehicle end in response to the upgrading task, wherein the upgrading task is used for indicating the vehicle end to upgrade to the target version of the vehicle end.

In this embodiment of the present application, the current version of the vehicle end is the current version of the entire vehicle end, and the target version of the vehicle end is the version that needs to be reached after the entire vehicle end is upgraded. The upgrade task is issued to the vehicle end by the server, the vehicle end can determine that the vehicle end needs to be upgraded from the current version of the vehicle end to the target version of the vehicle end after receiving the upgrade task, and the current version of the vehicle end can be reported to the server in order to facilitate the generation of an upgrade package by the server according to the need.

As an example, since a vehicle end may include a plurality of control units, different control units may be developed to different extents, and may have different versions, a vehicle end current version may include a current version of each control unit, and a vehicle end target version may include a target version of each control unit. In the present embodiment, the control unit may be an ECU (Electronic Control Unit ).

In a specific implementation, after a developer develops a new version, the new version is sent to a server, and after the server receives the new version, the vehicle end is considered to be updated, so that an updating task is issued to the vehicle end. Because the vehicle end can record the updated vehicle end version every time the vehicle end is updated, the vehicle end can acquire the current vehicle end version of the vehicle end and report the current vehicle end version to the server after receiving the upgrading task.

In some embodiments, after receiving the upgrade task, the vehicle end first determines whether the current state meets an upgrade condition, that is, whether the vehicle end can be upgraded at present, if so, the current version of the vehicle end is reported to the server, and if not, upgrade failure information is reported to the server. Therefore, the situation that the vehicle end fails to upgrade and resources and time are wasted due to the fact that the vehicle end does not meet the upgrading conditions can be avoided.

As one example, the current state of the vehicle end may include one or more of a motion state, a network state, and a power state. Wherein the motion state comprises stationary or motion, the network state comprises networking or non-networking, and the electric quantity state comprises an electric quantity value. The upgrade conditions may include that the vehicle end is stationary, networked, and full of power.

In the embodiment of the application, the server issues the upgrade task to the vehicle end, the vehicle end responds to the upgrade task to judge whether the current state meets the upgrade condition, if yes, the target version of the vehicle end is reported to the server, unnecessary operations can be reduced, and the upgrade efficiency and the success rate are improved.

Further, since the server may correspond to a plurality of different vehicle ends, and upgrade conditions of different vehicle ends may be different, after receiving a target version of the vehicle end sent by a developer, it needs to determine which new version of the vehicle end is the target version of the vehicle end, and therefore, before receiving the current version of the vehicle end reported by the vehicle end in response to an upgrade task, the server further includes: receiving a vehicle end target version release notice of a vehicle end aiming at a target model; and responding to the release notice of the target version of the vehicle end, and issuing an upgrading task to the vehicle end of the target model.

The target model is the model of the vehicle end to be upgraded and is used for uniquely indicating one or one vehicle end.

In a specific implementation, after a developer develops a new version for a vehicle end of a certain model, a server receives a vehicle end target version release notice, and the vehicle end target version release notice aims at a vehicle end of a target model, so that the server can determine that the vehicle end to be upgraded is the vehicle end of the target model and issue an upgrading task to the vehicle end of the target model. Thus, the accurate issuing of the upgrading task can be realized.

The OTA upgrading method provided by the embodiment of the invention can be applied to the OTA warehouse of the Internet of things, and the OTA warehouse of the Internet of things can be provided for each provider to carry out OTA upgrading, so that each provider can configure a target model corresponding to a new version of a vehicle end when releasing the new version, and the object of upgrading, namely the vehicle end, can be conveniently determined with a server.

Further, to avoid the packages of different suppliers from interfering with each other, the packages of each supplier may be stored separately. Therefore, after receiving the vehicle-end target version release notification for the vehicle end of the target model, it further includes: analyzing the release notice of the target version of the vehicle end to obtain a version file package of the target version of the vehicle end and configuration description files of the version file packages; analyzing configuration description files of the version file packages, and determining target tenants and target suppliers to which the version file packages belong; and according to the target tenant and the target provider, different version file packages are stored in an isolated mode.

The version file package corresponds to the control unit, is an atomic level file package of the control unit, and corresponds to a version of one control unit.

In the specific implementation, the release notice of the target version of the vehicle end is analyzed, the version file package of each control unit and the configuration description file of each version file package can be obtained, the configuration description file of each version file package is analyzed, and the target tenant and the target provider to which each version file package belongs can be determined. And for any version file package, determining a first storage position corresponding to the version file package according to a target tenant to which the version file package belongs, and storing the version file package to a second storage position corresponding to a target provider if a second storage position corresponding to the target provider is determined in the first storage position. Thus, the standardized management of the version file package can be realized.

In some embodiments, after developing the new version, the server receives a notification of the target version of the vehicle end, where the notification may be issued in the form of a target file packet, and since the version upgrade may be to upgrade some or all of the control units of the vehicle end, the target file packet may include the version file packet of each control unit and its version number, the configuration description file of each version file packet, and the hash code. Furthermore, the configuration description file of each version package may include the provider and tenant to which the version package belongs, and further, the configuration description file may further include package identifier, version number, package mode, package type, adapted control unit, dependent version number, and the like of the version package. Therefore, by analyzing the configuration description file, the target tenant and the target provider to which the version file package belongs can be determined.

As an example, the structure of the target package is as follows:

ecu_release-release version

Version package, version number

Hash code of ecu. Xxx. Hash-version package

Config. Json- -configuration description file

The ecu, xxx, version is a file package of a certain control unit at the vehicle end, the ecu, xxx, hash is a unique hash code of the version file package, and the config, json is a configuration description file of the version file package.

As an example, the format of the configuration description file is as follows:

the above-mentioned wasePackage is a configuration description file of a version package corresponding to a certain control unit to be upgraded, where the configuration description file reflects a storage structure of the version package, an identification of a home tenant and an adapted control unit, and includes a package ID of the version package corresponding to the control unit, a target version, description information of the package, a package mode, a package type, a vendor, a tenant, an identification of the control unit, a dependency package ID of the package relied by the control unit, a dependency package version, and a vendor affiliated by the dependency package. In the embodiment of the application, the file packages can be stored in an isolated manner for different tenants and operators without interference.

As an example, the storage structure of the package may be stored according to tenant ID, vendor, unique identification of the package and version number, and the physical storage directory is as follows:

root path

Referring to fig. 2, fig. 2 is a schematic diagram of a storage structure according to an embodiment of the present application. Firstly, determining a first storage position of a version file package according to the current tenant of the version file package, further determining a second storage position in the first storage position according to the current provider of the version file package, determining a third storage position in the second storage position according to the file package identifier of the version file package, determining a fourth storage position in the third storage position according to the version number of the version file package, and storing the version file package, the configuration description file, the hash code of the version file package and the like in the fourth storage position.

In the embodiment of the application, after a new version of a vehicle end aiming at a target model is developed, uploading each version file package of the new version (the target version of the vehicle end) and version numbers thereof, configuration description files and hash codes of each version file package to a server, and isolating and storing version file packages of different suppliers according to catalogues planned by a system according to tenants and suppliers to which the version file package recorded in the configuration description files belongs, so that mutual interference is avoided, standardized management is realized, and the requirements of each supplier are conveniently adapted. After receiving the upgrading notification of the target version of the vehicle end, the server generates an upgrading task and transmits the upgrading task to the vehicle end of the target model, and the vehicle end reports the current version of the vehicle end to the server under the condition that the current state meets the upgrading condition, so that the server can generate a target upgrading packet according to the current version of the vehicle end, and the on-demand generation of the target upgrading packet is realized.

Step 102: and determining the current version and the target version of the control unit to be upgraded of the vehicle end according to the current version and the target version of the vehicle end.

In this embodiment of the present application, the current version of the vehicle end may include a current version of each control unit of the vehicle end, and the target version of the vehicle end may include a target version that needs to be reached after each control unit of the vehicle end is upgraded. And the server can record the corresponding relation between the current version of the vehicle end and the single version of each control unit of the vehicle end, so that the current version of each control unit of the vehicle end can be determined according to the current version of the vehicle end, and the target version of each control unit of the vehicle end can be determined according to the target version of the vehicle end.

According to an embodiment of the present application, determining, according to a current version of a vehicle end and a target version of the vehicle end, a specific implementation of the current version and the target version of a control unit to be upgraded of the vehicle end may include: determining the current version of each control unit of the vehicle end according to the current version of the vehicle end; determining a target version of each control unit according to the target version of the vehicle end; and determining the control unit to be upgraded and the current version and the target version of the control unit to be upgraded from a plurality of control units at the vehicle end according to the current version and the target version of each control unit.

In a specific implementation, the server may record a correspondence between the current version of the vehicle end and a single version of each control unit of the vehicle end, so that the current version of each control unit of the vehicle end may be determined according to the current version of the vehicle end, and the target version of each control unit of the vehicle end may be determined according to the target version of the vehicle end. Comparing the current version of each control unit with the target version, if the current version of each control unit is different from the target version, determining that the control unit is the control unit to be upgraded, and further determining the current version and the target version of the control unit to be upgraded.

For example, assuming that the current version of the vehicle end is version 3, the target version of the vehicle end is version 4, the vehicle end includes 3 control units, the current version of the first control unit is v1.2, the current version of the second control unit is v2.0, the current version of the third control unit is v1.2, the target version of the first control unit is v1.5, the target version of the second control unit is v2.0, and the target version of the third control unit is v1.3, it may be determined that the control unit to be upgraded includes the first control unit and the third control unit.

In the embodiment of the application, since the release of the new version is usually the target version of the vehicle end, and the versions of the control units in different target versions of the vehicle end may be different, the control unit to be upgraded and the current version and the target version of the control unit to be upgraded can be determined according to the difference between the current version and the target version of each control unit, the control unit to be upgraded in the vehicle end and the target version to be achieved after the control unit to be upgraded in the vehicle end are accurately determined, the subsequent generation of the target upgrade package is facilitated, and the generation efficiency and the accuracy of the target upgrade package are improved.

Step 103: and generating a target upgrade package and an upgrade strategy of the vehicle end according to the version dependency relationship between the current version and the target version of the control unit to be upgraded and the corresponding version file packages of the control unit to be upgraded.

In the embodiment of the present application, the version dependency refers to a dependency between different versions of the same control unit. For example, version 3 depends on version 2, i.e. version 3 is an improvement on version 2, version 2 depends on version 1, i.e. version 2 is an improvement on version 1, if the current version is version 1 and the target version is version 3, it is necessary to determine the differential package between version 3 and version 2 and the differential package between version 2 and version 1, and then implement a version upgrade based on these two differential packages. Wherein the differential packet is a package generated from a difference between two versions of the package.

In some embodiments, a version dependency relationship may be parsed from the configuration description file of each version package, and a dependency package version on which each version package depends may be determined according to the version dependency relationship.

As an example, the server stores version file packages of each control unit under each version, for any control unit to be upgraded, whether an intermediate version exists between the current version and the target version or not can be determined according to the version dependency relationship, if yes, the intermediate version file package corresponding to the intermediate version and the target version file package corresponding to the target version are obtained, and according to the intermediate version file package and the target version file package, a control unit upgrade package of the control unit to be upgraded can be generated, and further, the control unit upgrade package of each control unit to be upgraded can be obtained, and the target upgrade package of the vehicle end is obtained through combination.

According to an embodiment of the present application, according to a version dependency relationship between a current version and a target version of a to-be-upgraded control unit and each version file packet corresponding to the to-be-upgraded control unit, the specific implementation of generating the target upgrade packet and the upgrade policy of the vehicle end may include:

determining an intermediate version and an upgrading strategy according to the version dependency relationship, wherein the intermediate version has a front dependency relationship with a target version and has a rear dependency relationship with a current version, and the upgrading strategy comprises a version upgrading sequence; acquiring a middle version file packet corresponding to a middle version of a control unit to be upgraded and a target version file packet corresponding to a target version; and generating a target upgrading packet according to the intermediate version file packet and the target version file packet corresponding to the control unit to be upgraded.

In a specific implementation, for each control unit to be upgraded, according to the version dependency relationship of each control unit to be upgraded, the version upgrading sequence can be determined, whether an intermediate version exists between the current version and the target version or not can also be determined, if yes, the intermediate version and the target version have a front dependency relationship and a rear dependency relationship with the current version. The method comprises the steps of obtaining a middle version file package and a target version file package, wherein each version file package can be a differential package or a full package, and then combining the middle version file package and the target version file package based on the middle version file package and the target version file package to obtain a target upgrading package, and the target upgrading package can be the differential package or the full package.

Illustratively, if each version of the package is a differential package, the generated target upgrade package is also a differential package. If the file package of each version is a full package, the intermediate version file package and the target version file package can be directly combined to obtain the target upgrade package which is the full package, or the differential package of each version can be determined according to the full package of each version, and then the differential package is combined to obtain the target upgrade package which is also the differential package. For example, taking the example that the target upgrade package is a differential package,where i denotes an ith ecu, i.e., an ith control unit to be upgraded, n denotes the number of control units to be upgraded, and ecu (i) denotes a control unit upgrade package of the ith control unit to be upgraded.

As an example, the number of intermediate versions may be one or more, and in case the number of intermediate versions is a plurality, the version-up sequence determined according to the version-dependency relationship may include version-up sequences of the plurality of intermediate versions and the target version, i.e. the up-scaling policy includes a version-up sequence capable of indicating that the control unit to be up-scaled from the current version to the target version.

In some embodiments, in the case that the number of the control units to be upgraded is one, the intermediate version package and the target version package of the control units to be upgraded are obtained, and the intermediate version package and the target version package are combined to obtain the target upgrade package.

In other embodiments, in the case that the number of the to-be-upgraded control units is plural, generating the target upgrade package according to the intermediate version package and the target version package corresponding to the to-be-upgraded control units may include: combining the intermediate version file package and the target version file package of the same control unit to be upgraded to obtain a control unit upgrading package of each control unit to be upgraded; and combining the control unit upgrade packages of the plurality of control units to be upgraded to generate a target upgrade package.

In a specific implementation, if the number of the control units to be upgraded is multiple, the intermediate version file package and the target version file package of each control unit to be upgraded can be combined according to the version upgrading sequence of each control unit to be upgraded to generate the control unit upgrading package of each control unit to be upgraded, and in order to distinguish, the corresponding identification of the control unit to be upgraded can be marked on each control unit upgrading package, and then the control unit upgrading packages of the control units to be upgraded are combined to obtain the target upgrading package. Illustratively, each control unit upgrade package may be a differential package or a full package.

In the embodiment of the application, the control unit to be upgraded is required to be upgraded from the current version to the target version depending on the intermediate version, so that according to the intermediate version file packet and the target version file packet of each control unit to be upgraded, a control unit upgrading packet conforming to the upgrading logic of the control unit to be upgraded can be generated, further, a target upgrading packet conforming to the upgrading requirement of a vehicle end can be generated, and the upgrading success rate is improved.

Further, since the plurality of control units at the vehicle end are mutually restricted when the vehicle end control is realized, there is a control unit dependency relationship, and therefore, in the case that the number of control units to be upgraded is plural, the upgrade policy may further include a control unit upgrade order, and the control unit upgrade order is determined according to the control unit dependency relationship among the plurality of control units to be upgraded. Therefore, the vehicle-end upgrade can be realized according to the upgrade sequence of the control units, the failure of the vehicle-end upgrade caused by the problem of the upgrade of the control units to be upgraded can be avoided, and the upgrade success rate is improved.

As an example, in the process of combining the control unit upgrade packages of a plurality of control units to be upgraded, the control unit upgrade packages may be combined according to the control unit upgrade order, so that the control unit upgrade packages can be used in order in the subsequent upgrade.

It should be noted that, in the process of generating the target upgrade package, if the problem of file package deletion occurs, the method can automatically early warn, notify the administrator to timely complement the file package so as to obtain the complete target upgrade package. Therefore, the self-checking of the target upgrade package is realized in the server, rather than in the upgrade process, the target upgrade package issued to the vehicle end by the missing package is correct and complete, and the upgrade efficiency can be improved.

Further, the target upgrade package may include a plurality of control unit upgrade packages of the control units to be upgraded, and for convenience of transmission, an upgrade description file of the target upgrade package may be generated according to an upgrade policy, in which a version upgrade order and a control unit upgrade order are recorded.

As an example, the structures of the target upgrade package and the upgrade description file are as follows:

ecu_release—packet name of target upgrade packet

ECU1- -control Unit 1 upgrade package

ECU2- -control Unit 2 upgrade package

ECU 3-control unit 3 upgrade package

ECU 4-control unit 4 upgrade package

Config. Json upgrade description file

As an example, the upgrade description file config.

/>

In the above example, the upgrade description file includes a hash code of the target upgrade package, a version number, the target upgrade package, a pre-upgrade package of the target upgrade package, a required version of the pre-upgrade package, an upgrade pre-condition, a type of the target upgrade package such as a full-scale upgrade package or a patch upgrade package, and an ECU to which the target upgrade package is adapted. The upgrade description file also includes an upgrade order in which, in the above example, the ECU2 is first upgraded to v1.2 with the target upgrade package of the ECU2, which is dependent on the upgrade package of the ECU1 of version v1.2, and then the ECU3 is upgraded to v1.3 with the target upgrade package of the ECU3, which is dependent on the upgrade package of the ECU1 of version v 1.2.

It should be noted that, in one possible implementation manner, before the server generates the target upgrade package and the upgrade policy, an upgrade manner of using full upgrade or differential upgrade may be determined according to the current version of the vehicle end and the target version of the vehicle end. Specifically, under the condition that no intermediate version exists between the current version and the target version of each control unit to be upgraded, the control units to be upgraded can be considered to be directly upgraded from the current version to the target version, so that a full-scale upgrading mode can be adopted, and a server generates a full-scale target upgrading packet; in the case that each control unit to be upgraded spans multiple versions from the current version to the target version, a differential upgrading mode can be adopted, and the server generates a differential target upgrading packet. And the upgrade mode can be determined by the vehicle end and informed to the server, and can also be determined by the server. Therefore, a proper upgrading mode can be selected according to actual conditions, and an adaptive upgrading packet is generated, so that the upgrading efficiency and the upgrading success rate can be improved to a certain extent.

In the embodiment of the application, the server analyzes the version dependency relationship of each control unit to be upgraded from the configuration description file of each version file packet, determines whether an intermediate version exists between the current version and the target version of each control unit to be upgraded according to the version dependency relationship of each control unit to be upgraded, if so, obtains the target version file packet and the intermediate version file packet, combines the control unit upgrade packets of each control unit to be upgraded, combines the control unit upgrade packets to obtain the target upgrade packet, realizes the on-demand generation of the target upgrade packet, improves the suitability of the generated target upgrade packet and the upgrade requirement, and further improves the upgrade success rate. And the version upgrading sequence of each control unit to be upgraded can be determined according to the version dependency relationship of each control unit to be upgraded, the control unit upgrading sequence of each control unit to be upgraded can be determined according to the control unit dependency relationship, and an upgrading description file is generated according to the version upgrading sequence and the control unit upgrading sequence, so that subsequent upgrading can be realized according to the control unit upgrading sequence and the version upgrading sequence, upgrading failure caused by the occurrence of the problem of upgrading the control unit to be upgraded can be avoided, and the upgrading success rate is further improved.

Step 104: and issuing the target upgrade package and the upgrade strategy to the vehicle end so that the vehicle end uses the target upgrade package to upgrade according to the upgrade strategy.

In the embodiment of the application, the target upgrade package is obtained by combining the atomic-level version packages of the control units to be upgraded according to the needs, namely, the atomic-level version packages of the control units are stored in the server, and when the upgrade is needed, the atomic-level version packages of different control units are combined according to the upgrade needs, so that the upgrade package meeting various upgrade needs can be generated, the storage space of the server is saved, and the flexibility and the efficiency of the upgrade package generation are improved.

In a specific implementation, a server provides a standard internet of things API (Application Programming Interface ) for communication with a vehicle end, the internet of things API comprises a unified authentication encryption protocol, after a target upgrade package and an upgrade strategy are generated, an upgrade description file is generated according to the upgrade strategy, and the server issues the target upgrade package and the upgrade description file to the vehicle end through the internet of things API. In addition, in the embodiment of the application, the communication between the server and the vehicle end is realized through the API of the Internet of things.

In one possible implementation manner, since the computing resources and the storage resources of the vehicle end are limited, if the target upgrade package is too large, the upgrade may not be completed at one time and needs to be implemented in stages, so that the vehicle end can select an appropriate upgrade package acquisition strategy according to the situation of the vehicle end to acquire the target upgrade package from the server.

That is, before the target upgrade package is issued to the vehicle end, it further includes: and receiving an upgrade package acquisition strategy reported by the vehicle end so as to send the target upgrade package to the vehicle end based on the upgrade package acquisition strategy, wherein the upgrade package acquisition strategy is determined by the vehicle end.

As an example, the upgrade package acquisition policy may be determined according to a remaining space capacity of the vehicle end. Alternatively, the determination may be further based on the remaining space capacity of the vehicle end and the network transmission rate between the vehicle end and the server, for example, in the case where the network transmission rate is slow, the upgrade package acquisition policy is obtained in stages, and the slower the network transmission rate, the smaller the file package per stage may be.

In a specific implementation, the upgrade package acquisition strategy includes complete acquisition or staged acquisition. After the server generates the target upgrade package and the upgrade policy, the target upgrade package and the upgrade policy can be packaged, a temporary encryption remote download address is generated for the packaged file package, and key parameters are issued to the vehicle end, wherein the key parameters comprise an encryption protocol, an MD5 check code and the file size of the target upgrade package. The vehicle end judges the validity and the correctness of the file package according to the encryption protocol and the MD5 check code, judges whether the file package can be stored in the vehicle end according to the size of the file and the self residual space capacity, generates an upgrade package acquisition strategy according to a judging result, reports the upgrade package acquisition strategy to the server, and the server issues the packaged file package to the vehicle end according to the upgrade package acquisition strategy.

As an example, if the size of the file package is determined to be suitable according to the size of the file and the residual space capacity of the file, a completely acquired upgrade package acquisition strategy is selected, otherwise, a staged upgrade package acquisition strategy is selected. In addition, when the staged acquisition is determined, the size of the upgrade package downloaded in several stages and each stage can be determined according to the file size and the residual space capacity.

In some embodiments, the vehicle end downloads the target upgrade package from the temporary encrypted download address according to the upgrade package acquisition policy. If the upgrade package acquisition strategy is complete acquisition, after the vehicle end acquires the target upgrade package, the integrity and the correctness of the target upgrade package can be checked, after the verification is successful, the control unit to be upgraded is upgraded according to the control unit upgrade order and the version upgrade order in the upgrade strategy, the upgrade of the vehicle end is realized, upgrade completion information is generated and reported to the server, after the server determines that the upgrade of the vehicle end is completed, the target upgrade package can be directly deleted to reduce the storage burden, or after a period of time of upgrade completion, the target upgrade package is deleted, so that the problem of the upgrade can be solved in time, and the occupation of storage resources can be reduced.

In the embodiment of the application, the server stores the atomic-level version file packages of each control unit in an isolated manner according to different tenants and different suppliers, so that standardized storage of the file packages is realized, and under the condition that upgrading is required, the atomic-level version file packages of each control unit to be upgraded are combined as required to generate a target upgrading package, so that self-adaptive manufacturing of the upgrading package is realized, and the suitability of the upgrading package and a vehicle end is improved; and the version dependency relationship is considered in the process of generating the target upgrade package, so that the target upgrade package meets the upgrade requirement of the vehicle end, the suitability of the generated target upgrade package and the upgrade requirement is improved, the upgrade package is subjected to self-checking, the integrity of the upgrade package is ensured, the investigation of the unsuccessful problem of the vehicle end upgrade is reduced, and the upgrade success rate is improved. In addition, the upgrade strategy comprises a control unit upgrade sequence and a version upgrade sequence, so that the influence of the upgrade of some control units to be upgraded on the control units to be upgraded which depend on the upgrade strategy can be avoided, and the upgrade success rate is improved.

Fig. 3 is a flowchart of a second method for upgrading OTA according to an embodiment of the present application, where the method is applied to a server, such as a cloud server, and may include the following steps.

Step 301: and issuing an upgrade task to the vehicle end, wherein the upgrade task is used for indicating the vehicle end to upgrade to the target version of the vehicle end.

Step 302: and receiving the current version of the vehicle end, which is reported by the vehicle end in response to the upgrading task.

Step 303: and determining the current version of each control unit of the vehicle end according to the current version of the vehicle end.

Step 304: and determining the target version of each control unit according to the target version of the vehicle end.

Step 305: and determining the control unit to be upgraded and the current version and the target version of the control unit to be upgraded from a plurality of control units at the vehicle end according to the current version and the target version of each control unit.

Step 306: determining the intermediate version and the version upgrading sequence of each control unit to be upgraded according to the version dependency relationship between the current version and the target version of each control unit to be upgraded; and determining the upgrading sequence of the control units according to the control unit dependency relationship among the plurality of control units to be upgraded.

Step 307: and obtaining a middle version file packet and a target version file packet corresponding to each control unit to be upgraded.

Step 308: and generating a control unit upgrading packet of each control unit to be upgraded according to the intermediate version file packet and the target version file packet corresponding to each control unit to be upgraded.

Step 309: and combining the control unit upgrade packages of the plurality of control units to be upgraded to obtain a target upgrade package of the vehicle end.

Step 310: and receiving an upgrade package acquisition strategy reported by the vehicle end.

Step 311: and according to the upgrade package acquisition strategy, the target upgrade package, the version upgrade order and the control unit upgrade order are issued to the vehicle end, so that the vehicle end uses the target upgrade package to upgrade according to the version upgrade order and the control unit upgrade order.

Step 312: and receiving upgrading completion information reported by the vehicle end, deleting the target upgrading packet and reserving an atomic-level version file packet of each control unit.

According to the OTA upgrading method provided by the embodiment of the application, the server stores the atomic-level version file packages of all the control units in an isolated mode according to different suppliers of different tenants, standardized storage of the file packages is achieved, under the condition that upgrading is required, the atomic-level version file packages of all the control units to be upgraded are combined as required to generate a target upgrading package, self-adaptive manufacturing of the upgrading package is achieved, and adaptability of the upgrading package and a vehicle end is improved; and in addition, the version dependency relationship is considered in the process of generating the target upgrade package, so that the target upgrade package meets the upgrade requirement of the vehicle end, namely, the suitability of the generated target upgrade package and the upgrade requirement is improved, and the upgrade package is subjected to self-checking so as to ensure the integrity of the upgrade package, and the upgrade success rate of the vehicle end is improved. In addition, the upgrade strategy comprises a control unit upgrade sequence and a version upgrade sequence, so that the influence of the upgrade of some control units to be upgraded on the control units to be upgraded which depend on the upgrade strategy can be avoided, and the upgrade success rate is improved.

Fig. 4 is a flowchart of a third method for OTA upgrade provided according to an embodiment of the present application, where the method is applied to a vehicle end, and may include the following steps.

Step 401: and receiving an upgrade task issued by the server, wherein the upgrade task is used for indicating the vehicle end to upgrade to the target version of the vehicle end.

Step 402: and reporting the current version of the vehicle end to a server in response to the upgrading task.

In the specific implementation, after receiving a current version of a vehicle end reported by the vehicle end, a server determines a current version and a target version of a control unit to be upgraded according to the current version of the vehicle end and the target version of the vehicle end, and generates a target upgrade package and an upgrade strategy of the vehicle end according to a version dependency relationship between the current version and the target version and each version file package corresponding to the control unit to be upgraded.

According to one embodiment of the present application, before reporting the current version of the vehicle end to the server in response to the upgrade task, the method further includes: and determining the current state of the vehicle end so as to report the current version of the vehicle end to the server under the condition that the current state meets the upgrading condition, wherein the current state comprises one or more of a motion state, a network state and an electric quantity state.

Step 403: and receiving a target upgrade package and an upgrade strategy issued by the server.

According to one embodiment of the present application, before receiving the target upgrade package and the upgrade policy issued by the server, the method further includes: and determining an upgrade package acquisition strategy according to the residual space capacity of the vehicle end and reporting the upgrade package acquisition strategy to the server so that the server can send the target upgrade package to the vehicle end based on the upgrade package acquisition strategy.

In a specific implementation, the upgrade package acquisition strategy comprises complete acquisition or segmented acquisition. For example, assuming that the upgrade package acquisition strategy is segment acquisition, the target upgrade package is obtained by segment from V1.0 to V2.0 by a dichotomy, the upgrade package of V1.0- > V1.5 is acquired first, the upgrade package is used for upgrade, and then the upgrade package of V1.5- > V2.0 is acquired after the upgrade package is completed, and the upgrade package is used for upgrade.

Step 404: and upgrading according to the upgrading strategy by using the target upgrading package.

According to one embodiment of the application, the upgrade strategy comprises a control unit upgrade order and a version upgrade order, the vehicle end comprises a plurality of control units to be upgraded, and the target upgrade package comprises a control unit upgrade package of each control unit to be upgraded; specific implementations of using the target upgrade package for upgrades according to the upgrade policies may include: and in the process of upgrading each control unit to be upgraded, according to the version upgrading sequence of the control unit to be upgraded, using a control unit upgrading packet of the control unit to be upgraded to upgrade.

According to one embodiment of the present application, before the target upgrade package is used for upgrade according to the upgrade policy, the method further includes: and carrying out integrity check on the target upgrade package so as to carry out upgrade by using the target upgrade package under the condition that the target upgrade package is complete.

For example, if the current version of a certain ECU is V1.0, the target version is V2.0, and V1.0 to V2.0 include nine versions of V1.1-V1.9, the control unit upgrade package of the ECU may include 10 version packages, and the version upgrade order of the version packages is marked, for example, the patch.v1.0- > v1.1 is the first version package, the marked version upgrade order is 1, the patch.v1.1- > v1.2, the marked version upgrade order is 2..patch.v1.9- > v2.0, and the marked version upgrade order is 10. After receiving the control unit upgrade package, the vehicle end upgrades the ECU by using the 10 version file packages according to the version upgrade sequence of each version file package.

It should be noted that, the specific implementation of the steps 401 to 404 is similar to the implementation process of the steps 101 to 104, and the specific implementation thereof may be referred to the related description of the above embodiment, which is not repeated herein.

According to the OTA upgrading method provided by the embodiment of the application, the vehicle end reports the current version of the vehicle end to the server, so that the server can generate the target upgrading packet according to the current version of the vehicle end and the target version of the vehicle end as required, and the suitability of the upgrading packet and the vehicle end is improved; and the version dependency relationship is considered in the process of generating the target upgrade package, so that the target upgrade package meets the upgrade requirement of the vehicle end, namely the suitability of the generated target upgrade package and the upgrade requirement is improved, and the success rate of the vehicle end for upgrading by using the target upgrade package is further improved. In addition, the upgrade strategy comprises a control unit upgrade sequence and a version upgrade sequence, so that the influence of the upgrade of some control units to be upgraded on the control units to be upgraded which depend on the upgrade strategy can be avoided, and the upgrade success rate is further improved.

Fig. 5 is a flowchart of a fourth OTA upgrading method provided according to an embodiment of the present application, where the method is applied to a vehicle end, and may include the following steps.

Step 501: and receiving an upgrade task issued by the server, wherein the upgrade task is used for indicating the vehicle end to upgrade to the target version of the vehicle end.

Step 502: a current state of the vehicle end is determined, the current state including one or more of a motion state, a network state, and a power state.

Step 503: and reporting the current version of the vehicle end to the server under the condition that the current state meets the upgrading condition.

Step 504: and determining an upgrade package acquisition strategy according to the residual space capacity, and reporting the upgrade package acquisition strategy to the server.

Step 505: and the receiving server acquires a target upgrade package and an upgrade strategy issued by the strategy according to the upgrade package.

Step 506: and carrying out integrity check on the target upgrade package.

Step 507: and under the condition that the target upgrade package is complete, upgrading the plurality of control units to be upgraded according to the upgrade sequence of the control units, and in the process of upgrading each control unit to be upgraded, using the control unit upgrade package of the control unit to be upgraded according to the version upgrade sequence.

Step 508: after the upgrading is finished, generating upgrading finishing information and reporting the upgrading finishing information to the server.

Fig. 6 is a schematic structural diagram of an OTA upgrade system according to an embodiment of the present application, where the OTA upgrade system includes a server 601 and a plurality of vehicle ends 602, and in this embodiment, any vehicle end to be upgraded in the plurality of vehicle ends 602 may perform an upgrade task. In addition, the OTA upgrading system can also be called as an OTA warehouse SaaS system of the Internet of things, and the OTA warehouse is constructed by the concept of SaaS products. The universal OTA warehouse can adapt to different vehicle ends and solve the problem that each upgrade package lacks a dependency relationship and cannot accurately construct an adapted upgrade package for issuing according to the requirements of the vehicle ends.

Fig. 7 is a flowchart for implementing OTA upgrade in an OTA upgrade system according to an embodiment of the present application.

Referring to fig. 7, a server 601 issues an upgrade task to a vehicle end 602, where the upgrade task is used to instruct the vehicle end 602 to upgrade to a target version of the vehicle end; the vehicle end 602 reports the current vehicle end version of the vehicle end 602 to the server 601 in response to the upgrade task; the server 601 determines a current version and a target version of a control unit to be upgraded of a vehicle end according to the current version and the target version of the vehicle end; generating a target upgrade package and an upgrade strategy of the vehicle end 602 according to the version dependency relationship between the current version and the target version of the control unit to be upgraded and the corresponding version file packages of the control unit to be upgraded; issuing a target upgrade package and an upgrade strategy to the vehicle end 602; the vehicle end 602 uses the target upgrade package to upgrade according to the upgrade policy.

According to one embodiment of the application, the server 601 determines an intermediate version and an upgrade policy according to a version dependency relationship, wherein the intermediate version has a pre-dependency relationship with a target version and a post-dependency relationship with a current version, and the upgrade policy includes a version upgrade order; acquiring a middle version file packet corresponding to a middle version of a control unit to be upgraded and a target version file packet corresponding to a target version; and generating a target upgrading packet according to the intermediate version file packet and the target version file packet corresponding to the control unit to be upgraded.

According to one embodiment of the present application, when the number of control units to be upgraded is plural, the server 601 combines the intermediate version file package and the target version file package of each control unit to be upgraded to obtain a control unit upgrade package of each control unit to be upgraded; and combining the control unit upgrade packages of the plurality of control units to be upgraded to generate a target upgrade package. And the upgrade strategy also comprises a control unit upgrade sequence, and the control unit upgrade sequence is determined according to the control unit dependency relationship among the plurality of control units to be upgraded.

According to one embodiment of the present application, the server 601 receives a vehicle end target version release notification for the vehicle end 602 of the target model; analyzing the release notice of the target version of the vehicle end to obtain a version file package of the target version of the vehicle end and configuration description files of the version file packages; analyzing configuration description files of the version file packages, and determining target tenants and target suppliers to which the version file packages belong; and according to the target tenant and the target provider, different version file packages are stored in an isolated mode. And, the server 601 issues an upgrade task to the target model's vehicle end 602 in response to the vehicle end target version issue notification.

According to one embodiment of the present application, after the vehicle end 602 receives the upgrade task issued by the server 601, the current state is determined, and if the current state meets the upgrade condition, the vehicle end current version of the vehicle end 602 is reported to the server 601, where the current state includes one or more of a motion state, a network state, and an electric quantity state.

According to one embodiment of the present application, the vehicle end 602 determines an upgrade package acquisition policy according to the remaining space capacity and reports the upgrade package acquisition policy to the server 601, and the server 601 issues a target upgrade package to the vehicle end 602 based on the upgrade package acquisition policy.

According to one embodiment of the present application, the vehicle end 602 performs integrity check on the received target upgrade package, upgrades the plurality of to-be-upgraded control units according to the control unit upgrade order under the condition that the target upgrade package is complete, and uses the control unit upgrade package of the to-be-upgraded control unit to perform upgrade according to the version upgrade order of each to-be-upgraded control unit in the process of upgrading each to-be-upgraded control unit.

It should be noted that, the implementation process of the embodiment of the present application is similar to the above embodiment, and the specific implementation of the implementation process may be referred to the related description of the above embodiment, which is not repeated herein.

According to the OTA upgrading system provided by the embodiment of the application, the OTA warehouse is built by using the concept of the SaaS product, and different vehicle ends can be adapted. The server only stores the version file packages with the minimum granularity and the atomic level, is convenient for subsequent free combination to form the upgrade package meeting the requirement, and stores the version file packages of different tenants and different suppliers in an isolated manner, so that the storage of the file packages is standardized, and the storage space of the server can be saved. And the server automatically calculates a file package required by upgrading according to the current version of the vehicle terminal, combines the version file package of the atomic level and the file package relied on by the file package, generates a target upgrade package and issues the target upgrade package, and solves the problem that each upgrade package lacks a dependency relationship and cannot accurately construct an adaptive upgrade package for issuing according to the requirements of the vehicle. And according to the requirements of the vehicle end, the existing proper file package is automatically perceived, the effect of uniform resource reusability is achieved, the target upgrade package is stored for a period of time and then deleted after the upgrade is finished, the solution of the subsequent problem of the upgrade can be ensured, and the waste of storage resources can be reduced.

Fig. 8 is an OTA upgrading device provided according to an embodiment of the present application, applied to a server, where the device may include:

A first receiving module 801, configured to receive a current version of a vehicle end reported by the vehicle end in response to an upgrade task, where the upgrade task is used to instruct the vehicle end to upgrade to a target version of the vehicle end;

a determining module 802, configured to determine a current version and a target version of a control unit to be upgraded of a vehicle end according to the current version and the target version of the vehicle end;

the generating module 803 is configured to generate a target upgrade package and an upgrade policy of the vehicle end according to the version dependency relationship between the current version and the target version of the control unit to be upgraded and the version file packages corresponding to the control unit to be upgraded;

the issuing module 804 is configured to issue the target upgrade package and the upgrade policy to the vehicle end, so that the vehicle end uses the target upgrade package to upgrade according to the upgrade policy.

According to one embodiment of the present application, the generating module 803 is further configured to:

acquiring a middle version file package of a middle version and a target version file package of a target version corresponding to a control unit to be upgraded;

According to one embodiment of the present application, in case the number of control units to be upgraded is a plurality, the generating module 803 is further configured to:

According to one embodiment of the present application, the issuing module 804 is further configured to:

According to one embodiment of the present application, the determining module 802 is further configured to:

According to one embodiment of the present application, the first receiving module 801 is further configured to:

By applying the OTA upgrading method provided by the embodiment of the application, the server stores the atomic-level version file packages of all the control units in an isolated manner according to different suppliers of different tenants, so that standardized storage of the file packages is realized, and under the condition that upgrading is required, the atomic-level version file packages of all the control units to be upgraded are combined as required to generate a target upgrading package, so that self-adaptive production of the upgrading package is realized, and the suitability of the upgrading package and a vehicle end is improved; and the version dependency relationship is considered in the process of generating the target upgrade package, so that the target upgrade package meets the upgrade requirement of the vehicle end, namely the suitability of the generated target upgrade package and the upgrade requirement is improved, the upgrade package is subjected to self-checking, the integrity of the upgrade package is ensured, the investigation of the unsuccessful problem of the vehicle end upgrade is reduced, and the upgrade success rate is improved. In addition, the upgrade strategy comprises a control unit upgrade sequence and a version upgrade sequence, so that the influence of the upgrade of some control units to be upgraded on the control units to be upgraded which depend on the upgrade strategy can be avoided, and the upgrade success rate is improved.

The above is a schematic solution of an OTA upgrading device applied to a server according to an embodiment of the present application. It should be noted that, the technical solution of the OTA upgrading device applied to the server and the technical solution of the above-mentioned OTA upgrading method applied to the server belong to the same concept, and details of the technical solution of the OTA upgrading device applied to the server, which are not described in detail, can be referred to the description of the technical solution of the above-mentioned OTA upgrading method applied to the server.

Fig. 9 is a schematic diagram of another OTA upgrading device provided according to an embodiment of the present application, applied to a vehicle end, where the device may include:

the second receiving module 901 is configured to receive an upgrade task issued by the server, where the upgrade task is used to instruct the vehicle end to upgrade to the vehicle end target version;

the reporting module 902 is configured to report a current version of a vehicle end in response to an upgrade task, so that a server determines a current version and a target version of a control unit to be upgraded of the vehicle end according to the current version and the target version of the vehicle end, and generates a target upgrade package and an upgrade strategy of the vehicle end according to a version dependency relationship between the current version and the target version and each version file package corresponding to the control unit to be upgraded;

A third receiving module 903 configured to receive the target upgrade package and the upgrade policy issued by the server;

an upgrade module 904 configured to upgrade using the target upgrade package according to an upgrade policy.

the upgrade module 904 is further configured to:

According to one embodiment of the present application, the third receiving module 903 is further configured to:

the upgrade package acquisition strategy can be selectively determined according to the residual space capacity of the vehicle end and reported to the server, so that the server can send the target upgrade package to the vehicle end based on the upgrade package acquisition strategy.

According to one embodiment of the present application, the reporting module 902 is further configured to:

According to one embodiment of the application, the apparatus further comprises a verification module configured to:

By applying the OTA upgrading method provided by the embodiment of the application, the vehicle end reports the current version of the vehicle end to the server, so that the server can generate a target upgrading packet according to the current version of the vehicle end and the target version of the vehicle end as required, and the suitability of the upgrading packet and the vehicle end is improved; and the version dependency relationship is considered in the process of generating the target upgrade package, so that the target upgrade package meets the upgrade requirement of the vehicle end, namely the suitability of the generated target upgrade package and the upgrade requirement is improved, and the success rate of the vehicle end for upgrading by using the target upgrade package is further improved. In addition, the upgrade strategy comprises a control unit upgrade sequence and a version upgrade sequence, so that the influence of the upgrade of some control units to be upgraded on the control units to be upgraded which depend on the upgrade strategy can be avoided, and the upgrade success rate is further improved.

The above is an exemplary scheme of an OTA upgrading device applied to a vehicle end in an embodiment of the present application. It should be noted that, the technical solution of the OTA upgrading device applied to the vehicle end and the technical solution of the OTA upgrading method applied to the vehicle end belong to the same concept, and details of the technical solution of the OTA upgrading device applied to the vehicle end, which are not described in detail, can be referred to the description of the technical solution of the OTA upgrading method applied to the vehicle end.

Fig. 10 is a schematic structural diagram of a server according to an embodiment of the present application. The server 1000 includes: the memory 1001, the processor 1002 and the computer program stored in the memory 1001 and capable of running on the processor 1002, when the processor 1002 executes the computer program, implement the OTA upgrading method applied to the server provided in any of the above embodiments.

Fig. 11 is a schematic structural diagram of a vehicle end according to an embodiment of the present application. The vehicle end 1100 includes: the memory 1101, the processor 1102, and a computer program stored in the memory 1101 and executable on the processor 1102, when the processor 1102 executes the computer program, the OTA upgrading method applied to the vehicle end provided in any one of the embodiments is implemented.

The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements an OTA upgrade method as provided in any of the embodiments described above.

It should be noted that the logic and/or steps represented in the flowcharts or otherwise described herein, for example, may be considered as a ordered listing of executable instructions for implementing logical functions, and may be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: electrical connections (electronic devices) with one or more wires, portable computer cartridges (magnetic devices), random access Memory (RAM, random Access Memory), read-Only Memory (ROM), erasable programmable Read-Only Memory (EPROM, erasable Programmable Read-Only Memory or flash Memory), optical fiber devices, and portable compact disc Read-Only Memory (CDROM, compact Disk Read Only Memory). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits with logic gates for implementing logic functions on data signals, application specific integrated circuits with appropriate combinational logic gates, programmable gate arrays (PGA, programmable Gate Array), field programmable gate arrays (FPGA, field Programmable Gate Array), and the like.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the embodiments, and are intended to be included within the scope of the claims and description. In particular, the technical features mentioned in the respective embodiments may be combined in any manner as long as there is no structural conflict. The present application is not limited to the specific embodiments disclosed herein, but encompasses all technical solutions falling within the scope of the claims.

Claims

1. An OTA upgrade method, applied to a server, comprising:

receiving a current version of a vehicle end reported by the vehicle end in response to an upgrade task, wherein the upgrade task is used for indicating the vehicle end to upgrade to a target version of the vehicle end;

determining the current version and the target version of the control unit to be upgraded of the vehicle end according to the current version and the target version of the vehicle end;

generating a target upgrading packet and an upgrading strategy of the vehicle end according to the version dependency relationship between the current version and the target version of the control unit to be upgraded and each version file packet corresponding to the control unit to be upgraded;

2. The method of claim 1, wherein the generating the target upgrade package and the upgrade policy of the vehicle end according to the version dependency relationship between the current version and the target version of the to-be-upgraded control unit and the version packages corresponding to the to-be-upgraded control unit includes:

determining an intermediate version and an upgrade strategy according to the version dependency relationship, wherein the intermediate version has a front dependency relationship with the target version and a rear dependency relationship with the current version, and the upgrade strategy comprises a version upgrade sequence;

Acquiring a middle version file packet corresponding to the middle version of the control unit to be upgraded and a target version file packet corresponding to the target version;

and generating a target upgrading packet according to the intermediate version file packet and the target version file packet corresponding to the to-be-upgraded control unit.

3. The method according to claim 2, wherein, in the case that the number of the to-be-upgraded control units is plural, the generating the target upgrade package according to the intermediate version package and the target version package corresponding to the to-be-upgraded control units includes:

4. A method according to any of claims 1-3, wherein in case the number of control units to be upgraded is plural, the upgrade policy further comprises a control unit upgrade order, the control unit upgrade order being determined according to control unit dependencies between the plurality of control units to be upgraded.

5. A method according to any of claims 1-3, wherein prior to issuing the target upgrade package and upgrade policy to the vehicle end, the method further comprises:

6. A method according to any one of claims 1-3, wherein said determining the current version and the target version of the control unit to be upgraded of the vehicle end from the current version and the target version of the vehicle end comprises:

determining the target version of each control unit according to the target version of the vehicle end;

and determining a control unit to be upgraded and the current version and the target version of the control unit to be upgraded from the plurality of control units at the vehicle end according to the current version and the target version of each control unit.

7. A method according to any of claims 1-3, wherein prior to receiving a current version of the headend reported by the headend in response to the upgrade task, the method further comprises:

8. The method of claim 7, further comprising, after receiving the vehicle end target version release notification for the vehicle end of the target model:

9. An OTA upgrading method, which is characterized by being applied to a vehicle end, the method comprises the following steps:

receiving an upgrade task issued by a server, wherein the upgrade task is used for indicating the vehicle end to upgrade to a vehicle end target version;

reporting a current version of a vehicle end to the server in response to the upgrading task, so that the server determines a current version and a target version of a control unit to be upgraded of the vehicle end according to the current version of the vehicle end and the target version of the vehicle end, and generates a target upgrading packet and an upgrading strategy of the vehicle end according to a version dependency relationship between the current version and the target version and each version file packet corresponding to the control unit to be upgraded;

Receiving a target upgrade package and an upgrade strategy issued by the server;

and upgrading by using the target upgrading package according to the upgrading strategy.

10. The method of claim 9, wherein the upgrade policy includes a control unit upgrade order and a version upgrade order, the headend includes a plurality of control units to be upgraded, and the target upgrade package includes a control unit upgrade package for each control unit to be upgraded;

the step of upgrading by using the target upgrade package according to the upgrade policy comprises the following steps:

and upgrading the plurality of control units to be upgraded according to the control unit upgrading sequence, and in the process of upgrading each control unit to be upgraded, upgrading by using a control unit upgrading packet of the control unit to be upgraded according to the version upgrading sequence of the control unit to be upgraded.

11. The method of claim 9, wherein prior to receiving the target upgrade package and upgrade policy issued by the server, the method further comprises:

and determining an upgrade package acquisition strategy according to the residual space capacity of the vehicle end and reporting the upgrade package acquisition strategy to the server so that the server can issue the target upgrade package to the vehicle end based on the upgrade package acquisition strategy.

12. The method of any of claims 9-11, wherein prior to reporting the current version of the headend to the server in response to the upgrade task, the method further comprises:

13. The method of any of claims 9-11, wherein prior to using the target upgrade package for upgrades in accordance with the upgrade policy, the method further comprises:

14. An OTA upgrading system is characterized by comprising a server and a vehicle end;

the server issues an upgrade task to the vehicle end, wherein the upgrade task is used for indicating the vehicle end to upgrade to a vehicle end target version;

The server determines the current version and the target version of the control unit to be upgraded of the vehicle end according to the current version and the target version of the vehicle end; generating a target upgrading packet and an upgrading strategy of the vehicle end according to the version dependency relationship between the current version and the target version of the control unit to be upgraded and each version file packet corresponding to the control unit to be upgraded; issuing the target upgrade package and the upgrade strategy to the vehicle end;

15. An OTA upgrading device, applied to a server, comprising:

the system comprises a first receiving module, a second receiving module and a first updating module, wherein the first receiving module is configured to receive a current version of a vehicle end reported by the vehicle end in response to an updating task, and the updating task is used for indicating the vehicle end to update to a target version of the vehicle end;

the generation module is configured to generate a target upgrade package and an upgrade strategy of the vehicle end according to the version dependency relationship between the current version and the target version of the control unit to be upgraded and each version file package corresponding to the control unit to be upgraded;

And the issuing module is configured to issue the target upgrade package and the upgrade strategy to the vehicle end so that the vehicle end uses the target upgrade package to upgrade according to the upgrade strategy.

16. An OTA upgrading device, characterized in that it is applied to a vehicle end, said device comprising:

the reporting module is configured to report a current version of a vehicle end in response to the upgrading task, so that the server determines the current version and the target version of a control unit to be upgraded of the vehicle end according to the current version and the target version of the vehicle end, and generates a target upgrading packet and an upgrading strategy of the vehicle end according to the version dependency relationship between the current version and the target version and each version file packet corresponding to the control unit to be upgraded;

17. A server, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which processor, when executing the computer program, implements the OTA upgrade method according to any one of claims 1-8.

18. A vehicle end, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which processor, when executing the computer program, implements the OTA upgrade method according to any one of claims 9-13.

19. A computer readable storage medium having stored thereon a computer program, which when executed by a processor implements an OTA upgrade method according to any one of claims 1-8 or claims 9-13.