CN117931236A - OTA operation policy automatic generation method, system, equipment and readable storage medium - Google Patents
OTA operation policy automatic generation method, system, equipment and readable storage medium Download PDFInfo
- Publication number
- CN117931236A CN117931236A CN202410090240.9A CN202410090240A CN117931236A CN 117931236 A CN117931236 A CN 117931236A CN 202410090240 A CN202410090240 A CN 202410090240A CN 117931236 A CN117931236 A CN 117931236A
- Authority
- CN
- China
- Prior art keywords
- version
- upgraded
- comparison result
- software
- content
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000003860 storage Methods 0.000 title claims description 29
- 238000013486 operation strategy Methods 0.000 claims abstract description 17
- 238000012217 deletion Methods 0.000 claims description 26
- 230000037430 deletion Effects 0.000 claims description 26
- 230000004048 modification Effects 0.000 claims description 16
- 238000012986 modification Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 15
- 238000004364 calculation method Methods 0.000 claims description 11
- 230000015654 memory Effects 0.000 claims description 10
- 230000008859 change Effects 0.000 claims description 8
- 238000012545 processing Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 102100034112 Alkyldihydroxyacetonephosphate synthase, peroxisomal Human genes 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 2
- 238000003491 array Methods 0.000 description 2
- 229910052802 copper Inorganic materials 0.000 description 2
- 239000010949 copper Substances 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 238000009472 formulation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000153 supplemental effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses an automatic generation method of an OTA operation strategy, which comprises the following steps: selecting a first version to obtain vehicle information to be upgraded; selecting a second version, calculating a difference item between the first version and the second version, and converting the difference item into content to be upgraded; acquiring a hardware version number compatible with vehicle information to be upgraded and content to be upgraded; generating a version combination comprising the first version and the hardware version number; matching the vehicle information to be upgraded with the version combination, and delineating a target upgrading vehicle; automatically generating an OTA operation strategy according to the content to be upgraded and the target upgrading vehicle; the method has the advantages that the problem that the coverage of the target upgrading vehicle is incomplete in the existing OTA strategy is solved through multiple comparison of the first version and the second version to generate the content to be upgraded, the problem that the existing target vehicle is manually marked is solved through the fact that the upgrading content and the hardware version number are marked, the OTA operation strategy can be automatically generated, upgrading efficiency is improved, and automatic management is achieved.
Description
Technical Field
The present invention relates to OTA technologies, and in particular, to a method, a system, a device, and a readable storage medium for automatically generating an OTA operation policy.
Background
An Over-the-Air Technology (OTA) is a Technology for implementing remote management of mobile terminal equipment and SIM card data through an Air interface of mobile communication, and the OTA Technology is also applied to the automotive industry and is used for implementing mass automobile upgrades.
In the process of using OTA, a large number of automobiles are often required to be upgraded, but the software versions of all the automobiles are inconsistent, a reasonable formulation strategy is required in OTA operation, and the target vehicles are defined according to the updated content, in the prior art, operators are usually required to manually define the target vehicles, and besides the efficiency is low, the condition that the defined vehicles cannot cover all the target upgrade vehicles is caused, so that the upgrade vehicles are omitted, and sometimes, the condition that the vehicles are repeatedly upgraded is caused, so that a method capable of automatically generating the OTA operation strategy is needed, and the automatic definition of the target vehicles is realized.
Disclosure of Invention
In view of the problem that the existing OTA operation manual-defined target upgrading vehicle is inaccurate, the invention provides an OTA operation strategy automatic generation method, and according to the acquired first version and second version, the content to be upgraded and the hardware version number are obtained, so that the target upgrading vehicle is further automatically matched, and the OTA operation strategy is automatically generated.
In order to achieve the above purpose, the embodiment of the present invention adopts the following technical scheme:
An automatic generation method of OTA operation strategy comprises the following steps:
selecting a first version to obtain vehicle information to be upgraded;
Selecting a second version, calculating a difference item between the first version and the second version, and converting the difference item into content to be upgraded;
acquiring a hardware version according to the content to be upgraded, and generating a version combination comprising the first version and the hardware version;
and matching the vehicle information to be upgraded with the version combination, and delineating a target upgrading vehicle.
According to one aspect of the invention, the acquiring the vehicle information to be upgraded includes: and acquiring vehicle information with the software version being the first version from all vehicles, and taking the acquired vehicle information as vehicle information to be upgraded.
According to one aspect of the invention, the computing the difference term of the first version and the second version includes:
Acquiring attribute information of a first version and a second version;
comparing the first version attribute information with the second version attribute information to obtain a comparison result;
and obtaining a difference item according to the comparison result.
According to one aspect of the invention, the attribute information includes: BOM row number, BOM row attribute, software part number, and software version number.
According to one aspect of the present invention, the comparing the first version attribute information with the second version attribute information to obtain a comparison result includes:
Acquiring BOM line numbers, software part numbers, software version numbers and BOM line attributes of the first version and the second version;
sequentially comparing the BOM line number, the software part number, the software version number and the BOM line attribute of the first version with the second version;
if any item of attribute information of the first version is different from that of the attribute information of the second version, the obtained preliminary comparison results are different;
and if the attribute information of the first version is completely consistent with that of the second version, obtaining a comparison result without change.
According to one aspect of the invention, the preliminary comparison result includes:
if the content of the BOM line number of the second version does not appear in the first version, obtaining a comparison result to be newly increased;
if the content of the BOM line number of the first version is no longer appeared in the second version, the comparison result is obtained to be deleted;
If any one of the software part numbers and the software version numbers of the first version and the second version is different, the comparison result is obtained to be replaced;
If the BOM line attributes of the first version and the second version are inconsistent, the comparison result is modified.
According to one aspect of the present invention, the obtaining the difference term according to the comparison result includes:
if the comparison result is new, taking the new addition item of the second version relative to the first version as a difference item;
If the comparison result is replacement, taking a replacement item of the second version relative to the first version as a difference item;
if the comparison result is modification, taking a modification item of the second version relative to the first version as a difference item;
And if the comparison result is deletion, taking the deletion item of the second version relative to the first version as a difference item.
According to one aspect of the invention, the converting the difference item into the content to be upgraded includes:
judging whether the comparison result corresponding to the difference item is deletion or not;
if the comparison result is not deletion, acquiring all version contents of the second version corresponding to the difference item, and generating the content to be upgraded according to the acquired version contents;
If the comparison result is deletion, the content to be upgraded is not generated.
In accordance with one aspect of the invention, the generating a version combination comprising a first version and a hardware version number comprises:
Calculating a first version of the MD5 value;
combining the MD5 value with the obtained hardware version number one by one;
and removing incompatible version combinations to obtain a final version combination.
In accordance with one aspect of the invention, the method of calculating the MD5 value of the first version comprises:
acquiring all software part numbers of the first version;
ordering all software part numbers of the first version according to a Request ID rule;
and calculating the value of the ordered software part number to obtain the MD5 value.
An OTA operation policy automatic generation system, comprising:
the vehicle information module is used for acquiring vehicle information to be upgraded according to the first version;
the difference calculation module is used for calculating a difference item between the first version and the second version and converting the difference item into content to be upgraded;
The version combination module is used for acquiring a hardware version according to the content to be upgraded and generating a version combination comprising the first version and the hardware version;
and the vehicle matching module is used for matching the vehicle information to be upgraded with the version combination and delineating a target upgrading vehicle.
An OTA operation policy automatic generation device, comprising:
a memory for storing a computer program;
and the processor is used for realizing the steps of the OTA operation strategy automatic generation method when executing the computer program.
An OTA operation policy automatic generation readable storage medium having stored thereon a computer program to be executed to implement the steps of the OTA operation policy automatic generation method as described above.
The implementation of the invention has the advantages that: the invention discloses an automatic generation method of an OTA operation strategy, which comprises the following steps: selecting a first version to obtain vehicle information to be upgraded; selecting a second version, calculating a difference item between the first version and the second version, and converting the difference item into content to be upgraded; acquiring a hardware version number compatible with vehicle information to be upgraded and content to be upgraded; generating a version combination comprising the first version and the hardware version number; matching the vehicle information to be upgraded with the version combination, and delineating a target upgrading vehicle; automatically generating an OTA operation strategy according to the content to be upgraded and the target upgrading vehicle; the method has the advantages that the problem that the coverage of the target upgrading vehicle is incomplete in the existing OTA strategy is solved through multiple comparison of the first version and the second version to generate the content to be upgraded, the problem that the existing target vehicle is manually marked is solved through the fact that the upgrading content and the hardware version number are marked, the OTA operation strategy can be automatically generated, upgrading efficiency is improved, and automatic management is achieved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of an automatic generation method of an OTA operation policy according to an embodiment of the invention;
fig. 2 is a flowchart of an automatic generation method of an OTA operation policy according to a second embodiment of the present invention;
FIG. 3 is a supplemental illustration of a version of a software component according to the present invention;
FIG. 4 is a schematic diagram of a version of a software component according to the present invention;
fig. 5 is a schematic diagram of an automatic generation system of an OTA operation policy according to a third embodiment of the present invention;
Fig. 6 is an automatic generation device diagram of an OTA operation policy according to a fourth embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Example 1
As shown in fig. 1, an automatic generation method for an OTA operation policy includes the following steps:
Step S1: selecting a first version to obtain vehicle information to be upgraded;
In practical application, a first version of software is selected, attribute information of the first version is obtained, and all vehicle information is called through a platform, a system or a database.
In practical application, acquiring software versions of all the called vehicle information, judging whether the software versions are consistent with the first version, and taking the vehicle with the software versions consistent with the first version as the vehicle information to be upgraded.
In this embodiment, the first version is a version to be upgraded, that is, a software version that needs to be upgraded and is specified by the OTA operation policy at this time.
Step S2: selecting a second version, calculating a difference item between the first version and the second version, and converting the difference item into content to be upgraded;
In practical application, the second version of the software upgrade needs to be determined by specifying the OTA operation policy, and the difference item between the first version and the second version is calculated.
In this embodiment, the second version is the target version, that is, the software version after the vehicle is upgraded in the present OTA operation policy.
In this embodiment, calculating the difference term for the first version and the second version includes the steps of,
Step S21: acquiring attribute information of a first version and a second version;
In practical applications, the attribute information includes a BOM line number, a software part number, a software version number, and a BOM line attribute.
Wherein, a single assembly relation is displayed as a BOM line in the structure manager, and the BOM line number is used for representing, and the BOM line attribute refers to the attribute of the object associated with the BOM line.
As shown in fig. 3 and fig. 4, the vehicle to be upgraded includes a controller, such as an ADAS software product, where different software is included in the controller, and the different software is used as software parts forming the controller, for example, the bottom layer software, the application software and the calibration software can be regarded as software parts of the controller, and all the above software parts have respective corresponding versions.
In this embodiment, the application software is further divided into an after-sales software package and an OTA upgrade package, where the after-sales software package and the OTA upgrade package are software file entities, and the formed software part is the application software.
Step S22: comparing the first version attribute information with the second version attribute information to obtain a comparison result;
Specifically, acquiring attribute information of a first version and a second version, wherein the attribute information at least comprises a BOM line number, a software part number, a software version number and a BOM line attribute;
sequentially comparing the BOM line number, the software part number, the software version number and the BOM line attribute of the first version with the second version;
if any item of attribute information of the first version is different from that of the attribute information of the second version, the obtained preliminary comparison results are different;
and if the attribute information of the first version is completely consistent with that of the second version, obtaining a comparison result without change.
In practical application, the preliminary comparison results are different, and various possible comparison results exist, including new addition, deletion, replacement and modification, and the different comparison results are all difference items.
In this embodiment, the BOM line numbers of the original version and the second version are compared preferentially, and it is determined whether the BOM line number of the controller under the first version is consistent with the second version, and the same controller generally has a plurality of BOM line numbers, and the BOM line numbers may change as follows after version update:
If the BOM line number content of the second version does not appear in the first version, acquiring the content which does not appear and a controller corresponding to the content, wherein the controller and the related content appear after being updated, namely the controller and the content which does not appear are newly added, and the comparison result is newly added.
If the BOM line number content of the first version is not appeared in the second version, obtaining the content which is not appeared in the second version in the first version and a controller corresponding to the content, and indicating that the controller and related content are deleted after the version is updated, and obtaining a comparison result to be deletion.
In this embodiment, if the second version is consistent with the BOM line number of the first version, the next step is performed to compare whether the software part numbers of the first version and the second version are consistent with each other, and if any one of the software part numbers of the first version and the second version is different from the software part number of the first version, the controller is illustrated to change, and the comparison result is obtained as a replacement.
Specifically, a single controller includes a plurality of software parts, each software part has a respective software version, so that software part numbers and software version numbers of all controllers need to be compared one by one, and the following situations may exist:
If any software part number of the controller changes, the software part of the controller is changed, and a comparison result is obtained to be replaced;
If all the software part numbers of the controller are unchanged, continuously comparing the software version numbers of the software parts in the controller, and if the software version number of any one of the software parts is changed, obtaining a comparison result to be replaced;
in practical application, if the software part number of the controller is changed, the software version numbers of all the software parts of the controller can be further judged, and if any software version number is changed, the comparison result is replaced.
Further, if the comparison result is replacement, specific content of the replacement needs to be obtained, and information of all software parts and software version numbers of the replacement is obtained.
If the software part number and the software version number of the controller are not changed, the BOM line attribute of the first version and the BOM line attribute of the second version are required to be compared, if the BOM line attribute of the first version and the BOM line attribute of the second version are inconsistent, the comparison result is modified, and if the BOM line attribute of the first version and the BOM line attribute of the second version are consistent, the attribute information of the first version and the attribute information of the second version are completely consistent, and the comparison result is unchanged.
In practical application, if the comparison result is modification, acquiring the BOM line attribute of the second version modified relative to the first version and the software information corresponding to the BOM line attribute.
In practical application, if the comparison result is modified or the comparison result is unchanged, the comparison process is ended.
Step S23: obtaining a difference item according to the comparison result;
in practical application, if the comparison result is newly added, taking a newly added item of the second version relative to the first version as a difference item;
If the comparison result is replacement, taking a replacement item of the second version relative to the first version as a difference item;
if the comparison result is modification, taking a modification item of the second version relative to the first version as a difference item;
And if the comparison result is deletion, taking the deletion item of the second version relative to the first version as a difference item.
In this embodiment, if the comparison result is new, the difference item is a new item, that is, the BOM line number that does not appear in the first version but appears in the second version, and the controller corresponding to the BOM line number;
Similarly, if the comparison result is deletion, the difference item is a deletion item, namely a BOM line number which appears in the first version but does not appear in the second version, and a controller corresponding to the BOM line number;
if the comparison result is replacement, the difference item is a replacement item, namely all software parts and relevant information of software version numbers of the second version are replaced relative to the first version;
If the comparison result is modification, the difference item is modification item, namely BOM line attribute modified by the second version relative to the first version, and software information corresponding to the BOM line attribute.
Step S24: and converting the difference item into content to be upgraded.
In practical application, after the difference item between the first version and the second version is obtained by calculation, judging whether the comparison result corresponding to the difference item is deletion, if so, indicating that the second version deletes the BOM line number in the first version, and the BOM line number in the first version does not appear in the second version any more, so that the content to be upgraded is not generated.
In practical application, if the comparison result is not deletion, all version contents of the second version corresponding to the difference item are obtained, and the content to be upgraded is generated according to the obtained version contents.
In this embodiment, the content to be upgraded may be:
The system comprises a newly added BOM line number, a controller corresponding to the BOM line number, and contents of all corresponding software versions under the controller;
the software part corresponding to the replaced software part number, the software version corresponding to the software version number, the software part and the controller corresponding to the software version, and the content of all the corresponding software versions under the controller;
And the modified BOM line attribute corresponds to a controller, and the controller is used for controlling the content of all corresponding software versions.
In practical applications, the content to be upgraded may be any one or any combination of the above upgrade contents.
Step S3: acquiring a hardware version according to the content to be upgraded, and generating a version combination comprising the first version and the hardware version;
in practical applications, each vehicle to be upgraded has its corresponding hardware version number, which is typically managed by a platform according to a control domain based on an existing vehicle hardware configuration, and the platform typically contains one or even more control domains.
In this embodiment, the platform includes five control domains, and a new hardware version combination is generated by ordering the five control domains in a fixed order, and the ordering of each control domain in the large hardware version is fixed as a large hardware version, so that the version numbers of each control domain are used for representing, the available hardware version of the vehicle to be upgraded is limited, and compatibility problems still exist between different hardware versions, so that the large hardware version is limited.
Further, matching the vehicle information to be upgraded with the obtained hardware large version to obtain a set of hardware large versions compatible with the vehicle information to be upgraded and the content to be upgraded, wherein the set is as follows: [ HW1, HW2, HW3], wherein HW1, HW2 and HW3 represent three different large versions of hardware.
In this embodiment, the five control domains of the large hardware version include: chassis domain, body domain, power domain, recreational domain, and auxiliary driving domain.
In this embodiment, the hardware version numbers of the five control domains corresponding to the large hardware version HW1 are respectively: 01. 01, 0G, 0H, FF; likewise, HW2: 01. 02, 0G, 02, FF; HW3: 02. 02, 0G, 0H, FF.
In an actual application, generating a version combination including a first version and a hardware version includes the following steps:
step S31: calculating a first version of the MD5 value;
In practical application, the MD5 value of the first version needs to be calculated, all software part numbers of the first version need to be obtained, the software part numbers of the first version are ordered according to rules, and the ordered software part numbers are subjected to value calculation to obtain the MD5 value of the first version.
In this embodiment, all software part numbers of the first version are ordered according to the Request ID rule, and V1.0 and V1.1 are selected for the first version of this embodiment, resulting in software MD5 values of 14r35431t51y43 and f315yghy u65.
Step S32: combining the MD5 value with the obtained hardware large version one by one;
in practical application, the MD5 value is combined with the large hardware version one by one, and the large hardware version generated in step S3 is used, and the corresponding combination of the versions is as follows:
14r35431t51y43+HW1(01、01、0G、0H、FF)；
14r35431t51y43+HW2(01、02、0G、02、FF)；
14r35431t51y43+HW3(02、02、0G、0H、FF)；
f315yghy24u65+HW1(01、01、0G、0H、FF)；
f315yghy24u65+HW2(01、02、0G、02、FF)；
f315yghy24u65+HW3(02、02、0G、0H、FF)。
step S33: and removing incompatible version combinations to obtain a final version combination.
In practical application, the software MD5 value is not fully compatible with the large hardware version, and if an incompatible version combination exists in the obtained version combination, the incompatible version combination needs to be removed to obtain a final version combination, i.e. a version combination for matching to obtain the target upgrade vehicle.
In this embodiment, the MD5 value f315yghy u65 is not compatible with the hardware large version HW3, and therefore, the version combination is rejected to obtain the final version combination as follows:
14r35431t51y43+HW1(01、01、0G、0H、FF)；
14r35431t51y43+HW2(01、02、0G、02、FF)；
14r35431t51y43+HW3(02、02、0G、0H、FF)；
f315yghy24u65+HW1(01、01、0G、0H、FF)；
f315yghy24u65+HW2(01、02、0G、02、FF)。
Step S4: and matching the vehicle information to be upgraded with the version combination, and delineating a target upgrading vehicle.
In practical application, the MD5 value corresponding to the version combination needs to be calculated according to the first version, the hardware version number corresponding to the large hardware version is a combination of hardware version numbers of the vehicle to be upgraded, and the large hardware version is compatible with the content to be upgraded, so that the target upgrade vehicle of the OTA upgrade can be matched and defined according to the obtained final version combination.
In the embodiment, vehicle information to be upgraded is obtained by obtaining the upgraded first version; obtaining a second version, calculating a difference item between the first version and the second version, generating a content to be upgraded, obtaining a large hardware version through the content to be upgraded and vehicle information to be upgraded, and jointly matching a target upgrading vehicle by combining with the calculated MD5 value of the first version, thereby solving the problem of low efficiency of manually delineating the target vehicle in the existing OTA operation strategy; the content to be upgraded is generated through multiple comparison of the first version and the second version, and the problem that the coverage of the target upgrading vehicle in the existing OTA strategy is incomplete is solved.
Example two
As shown in fig. 2, an automatic generation method for an OTA operation policy includes the following steps:
Step S1: selecting a first version to obtain vehicle information to be upgraded;
In practical application, a first version of software is selected, attribute information of the first version is obtained, and all vehicle information is called through a platform, a system or a database.
In practical application, acquiring software versions of all the called vehicle information, judging whether the software versions are consistent with the first version, and taking the vehicle with the software versions consistent with the first version as the vehicle information to be upgraded.
In this embodiment, the first version is a version to be upgraded, that is, a software version that needs to be upgraded and is specified by the OTA operation policy at this time.
Step S2: selecting a second version, calculating a difference item between the first version and the second version, and converting the difference item into content to be upgraded;
In practical application, the second version of the software upgrade needs to be determined by specifying the OTA operation policy, and the difference item between the first version and the second version is calculated.
In this embodiment, the second version is the target version, that is, the software version after the vehicle is upgraded in the present OTA operation policy.
In this embodiment, calculating the difference term for the first version and the second version includes the steps of,
Step S21: acquiring attribute information of a first version and a second version;
In practical applications, the attribute information includes a BOM line number, a software part number, a software version number, and a BOM line attribute.
Wherein, a single assembly relation is displayed as a BOM line in the structure manager, and the BOM line number is used for representing, and the BOM line attribute refers to the attribute of the object associated with the BOM line.
As shown in fig. 3 and fig. 4, the vehicle to be upgraded includes a controller, such as an ADAS software product, where different software is included in the controller, and the different software is used as software parts forming the controller, for example, the bottom layer software, the application software and the calibration software can be regarded as software parts of the controller, and all the above software parts have respective corresponding versions.
In this embodiment, the application software is further divided into an after-sales software package and an OTA upgrade package, where the after-sales software package and the OTA upgrade package are software file entities, and the formed software part is the application software.
Step S22: comparing the first version attribute information with the second version attribute information to obtain a comparison result;
Specifically, acquiring attribute information of a first version and a second version, wherein the attribute information at least comprises a BOM line number, a software part number, a software version number and a BOM line attribute;
sequentially comparing the BOM line number, the software part number, the software version number and the BOM line attribute of the first version with the second version;
if any item of attribute information of the first version is different from that of the attribute information of the second version, the obtained preliminary comparison results are different;
and if the attribute information of the first version is completely consistent with that of the second version, obtaining a comparison result without change.
In practical application, the preliminary comparison results are different, and various possible comparison results exist, including new addition, deletion, replacement and modification, and the different comparison results are all difference items.
In this embodiment, the BOM line numbers of the original version and the second version are compared preferentially, and it is determined whether the BOM line number of the controller under the first version is consistent with the second version, and the same controller generally has a plurality of BOM line numbers, and the BOM line numbers may change as follows after version update:
If the BOM line number content of the second version does not appear in the first version, acquiring the content which does not appear and a controller corresponding to the content, wherein the controller and the related content appear after being updated, namely the controller and the content which does not appear are newly added, and the comparison result is newly added.
If the BOM line number content of the first version is not appeared in the second version, obtaining the content which is not appeared in the second version in the first version and a controller corresponding to the content, and indicating that the controller and related content are deleted after the version is updated, and obtaining a comparison result to be deletion.
In this embodiment, if the second version is consistent with the BOM line number of the first version, the next step is performed to compare whether the software part numbers of the first version and the second version are consistent with each other, and if any one of the software part numbers of the first version and the second version is different from the software part number of the first version, the controller is illustrated to change, and the comparison result is obtained as a replacement.
Specifically, a single controller includes a plurality of software parts, each software part has a respective software version, so that software part numbers and software version numbers of all controllers need to be compared one by one, and the following situations may exist:
If any software part number of the controller changes, the software part of the controller is changed, and a comparison result is obtained to be replaced;
If all the software part numbers of the controller are unchanged, continuously comparing the software version numbers of the software parts in the controller, and if the software version number of any one of the software parts is changed, obtaining a comparison result to be replaced;
in practical application, if the software part number of the controller is changed, the software version numbers of all the software parts of the controller can be further judged, and if any software version number is changed, the comparison result is replaced.
Further, if the comparison result is replacement, specific content of the replacement needs to be obtained, and information of all software parts and software version numbers of the replacement is obtained.
If the software part number and the software version number of the controller are not changed, the BOM line attribute of the first version and the BOM line attribute of the second version are required to be compared, if the BOM line attribute of the first version and the BOM line attribute of the second version are inconsistent, the comparison result is modified, and if the BOM line attribute of the first version and the BOM line attribute of the second version are consistent, the attribute information of the first version and the attribute information of the second version are completely consistent, and the comparison result is unchanged.
In practical application, if the comparison result is modification, acquiring the BOM line attribute of the second version modified relative to the first version and the software information corresponding to the BOM line attribute.
In practical application, if the comparison result is modified or the comparison result is unchanged, the comparison process is ended.
Step S23: obtaining a difference item according to the comparison result;
in practical application, if the comparison result is newly added, taking a newly added item of the second version relative to the first version as a difference item;
If the comparison result is replacement, taking a replacement item of the second version relative to the first version as a difference item;
if the comparison result is modification, taking a modification item of the second version relative to the first version as a difference item;
And if the comparison result is deletion, taking the deletion item of the second version relative to the first version as a difference item.
In this embodiment, if the comparison result is new, the difference item is a new item, that is, the BOM line number that does not appear in the first version but appears in the second version, and the controller corresponding to the BOM line number;
Similarly, if the comparison result is deletion, the difference item is a deletion item, namely a BOM line number which appears in the first version but does not appear in the second version, and a controller corresponding to the BOM line number;
if the comparison result is replacement, the difference item is a replacement item, namely all software parts and relevant information of software version numbers of the second version are replaced relative to the first version;
If the comparison result is modification, the difference item is modification item, namely BOM line attribute modified by the second version relative to the first version, and software information corresponding to the BOM line attribute.
Step S24: and converting the difference item into content to be upgraded.
In practical application, after the difference item between the first version and the second version is obtained by calculation, judging whether the comparison result corresponding to the difference item is deletion, if so, indicating that the second version deletes the BOM line number in the first version, and the BOM line number in the first version does not appear in the second version any more, so that the content to be upgraded is not generated.
In practical application, if the comparison result is not deletion, all version contents of the second version corresponding to the difference item are obtained, and the content to be upgraded is generated according to the obtained version contents.
In this embodiment, the content to be upgraded may be:
The system comprises a newly added BOM line number, a controller corresponding to the BOM line number, and contents of all corresponding software versions under the controller;
the software part corresponding to the replaced software part number, the software version corresponding to the software version number, the software part and the controller corresponding to the software version, and the content of all the corresponding software versions under the controller;
And the modified BOM line attribute corresponds to a controller, and the controller is used for controlling the content of all corresponding software versions.
In practical applications, the content to be upgraded may be any one or any combination of the above upgrade contents.
Step S3: acquiring a hardware version according to the content to be upgraded, and generating a version combination comprising the first version and the hardware version;
in practical applications, each vehicle to be upgraded has its corresponding hardware version number, which is typically managed by a platform according to a control domain based on an existing vehicle hardware configuration, and the platform typically contains one or even more control domains.
In this embodiment, the platform includes five control domains, and a new hardware version combination is generated by ordering the five control domains in a fixed order, and the ordering of each control domain in the large hardware version is fixed as a large hardware version, so that the version numbers of each control domain are used for representing, the available hardware version of the vehicle to be upgraded is limited, and compatibility problems still exist between different hardware versions, so that the large hardware version is limited.
Further, matching the vehicle information to be upgraded with the obtained hardware large version to obtain a set of hardware large versions compatible with the vehicle information to be upgraded and the content to be upgraded, wherein the set is as follows: [ HW1, HW2, HW3], wherein HW1, HW2 and HW3 represent three different large versions of hardware.
In this embodiment, the five control domains of the large hardware version include: chassis domain, body domain, power domain, recreational domain, and auxiliary driving domain.
In this embodiment, the hardware version numbers of the five control domains corresponding to the large hardware version HW1 are respectively: 01. 01, 0G, 0H, FF; likewise, HW2: 01. 02, 0G, 02, FF; HW3: 02. 02, 0G, 0H, FF.
In an actual application, generating a version combination including a first version and a hardware version includes the following steps:
step S31: calculating a first version of the MD5 value;
In practical application, the MD5 value of the first version needs to be calculated, all software part numbers of the first version need to be obtained, the software part numbers of the first version are ordered according to rules, and the ordered software part numbers are subjected to value calculation to obtain the MD5 value of the first version.
In this embodiment, all software part numbers of the first version are ordered according to the Request ID rule, and V1.0 and V1.1 are selected for the first version of this embodiment, resulting in software MD5 values of 14r35431t51y43 and f315yghy u65.
Step S32: combining the MD5 value with the obtained hardware large version one by one;
in practical application, the MD5 value is combined with the large hardware version one by one, and the large hardware version generated in step S3 is used, and the corresponding combination of the versions is as follows:
14r35431t51y43+HW1(01、01、0G、0H、FF)；
14r35431t51y43+HW2(01、02、0G、02、FF)；
14r35431t51y43+HW3(02、02、0G、0H、FF)；
f315yghy24u65+HW1(01、01、0G、0H、FF)；
f315yghy24u65+HW2(01、02、0G、02、FF)；
f315yghy24u65+HW3(02、02、0G、0H、FF)。
step S33: and removing incompatible version combinations to obtain a final version combination.
In practical application, the software MD5 value is not fully compatible with the large hardware version, and if an incompatible version combination exists in the obtained version combination, the incompatible version combination needs to be removed to obtain a final version combination, i.e. a version combination for matching to obtain the target upgrade vehicle.
In this embodiment, the MD5 value f315yghy u65 is not compatible with the hardware large version HW3, and therefore, the version combination is rejected to obtain the final version combination as follows:
14r35431t51y43+HW1(01、01、0G、0H、FF)；
14r35431t51y43+HW2(01、02、0G、02、FF)；
14r35431t51y43+HW3(02、02、0G、0H、FF)；
f315yghy24u65+HW1(01、01、0G、0H、FF)；
f315yghy24u65+HW2(01、02、0G、02、FF)。
Step S4: and matching the vehicle information to be upgraded with the version combination, and delineating a target upgrading vehicle.
In practical application, the MD5 value corresponding to the version combination needs to be calculated according to the first version, the hardware version number corresponding to the large hardware version is a combination of hardware versions of the vehicle to be upgraded, and the large hardware version is compatible with the content to be upgraded, so that the target upgrading vehicle of the current OTA upgrade can be matched according to the obtained final version combination, and the OTA operation policy is automatically generated according to the content to be upgraded and the target upgrading vehicle.
Step S5: and automatically generating an OTA operation strategy according to the content to be upgraded and the target upgrading vehicle.
In practical applications, the automatically generated OTA operation policy should at least include: the system comprises a first version, a second version, a target upgrading vehicle and content to be upgraded.
Preferably, after the OTA operation policy is formulated, the version combination used in the current OTA operation activity is stored, and when the OTA operation policy is formulated later, the selected first version and the second version are matched with the stored version combination, and if the selected first version and the second version are consistent with the first version and the second version corresponding to the existing version combination, the version combination is directly obtained.
According to the method, the target vehicle is marked, the OTA operation strategy is automatically generated according to the first version, the second version and the content to be upgraded, the target vehicle which needs to be upgraded is selected to carry out version upgrading, the OTA strategy formulated each time is stored, the version combination is directly obtained when the same result is encountered later, the time of repeated calculation is shortened, and the matching efficiency and the strategy generation efficiency are improved.
Example III
An OTA operation policy automatic generation system 2 includes:
A vehicle information module 21, configured to obtain vehicle information to be upgraded according to the first version;
the difference calculation module 22 is configured to calculate a difference term between the first version and the second version, and convert the difference term into upgrade content;
The version combination module 23 is configured to obtain a hardware version according to the content to be upgraded, and generate a version combination including the first version and the hardware version;
The vehicle matching module 24 is configured to match the vehicle information to be upgraded with the version combination, and delineate a target upgrade vehicle.
The OTA operation policy automatic generation system should further include a version management module 25, configured to store version information and release a new version.
The version information should include at least: version attribute information and version compatible hardware information; version attribute information includes a BOM row number, a software part number, a software version number, and a BOM row attribute.
Wherein the variance calculation module 22 includes: the difference judging module and the content generating module.
The difference judging module is used for judging the difference type of the second version relative to the first version, such as adding, deleting, replacing, modifying, unchanged and the like.
The content generation module is connected with the difference judgment module, and generates corresponding content to be upgraded, such as a controller corresponding to the newly added/deleted BOM line number, a software part/software version number replaced, a controller corresponding to the modified BOM line attribute and related software version information by acquiring a judgment result of the difference judgment module.
The version combination module 23 is further provided with an MD5 calculation module, which is configured to calculate an MD5 value of the first version, specifically, perform value calculation after ordering all software part numbers of the first version according to a Request ID rule.
And the compatible computing module judges whether the version is compatible with the obtained large hardware version according to the version compatible hardware information, and if the version is not compatible with the obtained large hardware version, the incompatible version combination is removed.
The system for automatically generating the OTA operation policy further comprises a policy generation module 26, configured to automatically generate the OTA operation policy according to the content to be upgraded and the target upgrade vehicle.
Example IV
An OTA operation policy automatic generation device, comprising:
a memory 100 for storing a computer program;
the processor 200 is configured to implement the steps of the method for automatically generating an OTA operation policy according to the first and second embodiments when executing the computer program.
Example five
An automatic generation readable storage medium for OTA operation policy, the readable storage medium storing a computer program, the computer program being executed to implement the steps of the automatic generation method for OTA operation policy according to the first and second embodiments.
The present invention may be a system, method, and/or computer program product. The computer program product may include a computer-readable storage medium (or media) having computer-readable program instructions thereon for causing a processor to perform aspects of the invention.
The readable storage medium is a computer readable storage medium that can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: portable computer disks, hard disks, random Access Memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), static Random Access Memories (SRAM), portable compact disc read-only memories (CD-ROM), digital Versatile Discs (DVD), memory sticks, floppy disks, mechanical coding devices such as punch cards or a protruding structure in a groove with instructions recorded thereon, and any suitable combination of the foregoing. Computer readable storage media as used herein should not be construed as vehicle information itself, such as vehicle hardware versions, vehicle software versions, and/or vehicle upgradeable software versions.
The computer readable program instructions described herein may be downloaded from a computer readable storage medium to a corresponding computing/processing device or to an external computer or external storage device via a network (e.g., the internet, a local area network, a wide area network, and/or a wireless network). The network may include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
The computer programs described herein are computer readable program instructions that can be downloaded from a computer readable storage medium to a corresponding computing/processing device or to an external computer or external storage device via a network (e.g., the internet, a local area network, a wide area network, and/or a wireless network). The network may include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for performing the operations of the present invention can be assembly instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented SMALLTALK, C ++ or the like programming language and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, electronic circuitry, including, for example, programmable logic circuitry, field Programmable Gate Arrays (FPGAs), or Programmable Logic Arrays (PLAs), may be personalized by executing computer-readable program instructions using state information of the computer-readable program instructions in order to perform aspects of the invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems, apparatus, and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having the instructions stored therein includes an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any changes or substitutions easily contemplated by those skilled in the art within the technical scope of the present invention should be included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (14)
1. An automatic generation method of an OTA operation strategy is characterized by comprising the following steps:
selecting a first version to obtain vehicle information to be upgraded;
Selecting a second version, calculating a difference item between the first version and the second version, and converting the difference item into content to be upgraded;
acquiring a hardware version according to the content to be upgraded, and generating a version combination comprising the first version and the hardware version;
and matching the vehicle information to be upgraded with the version combination, and delineating a target upgrading vehicle.
2. The method of claim 1, wherein the obtaining the vehicle information to be upgraded comprises: and acquiring vehicle information with the software version being the first version from all vehicles, and taking the acquired vehicle information as vehicle information to be upgraded.
3. The method of claim 1, wherein the calculating the difference term between the first version and the second version comprises:
Acquiring attribute information of a first version and a second version;
comparing the first version attribute information with the second version attribute information to obtain a comparison result;
and obtaining a difference item according to the comparison result.
4. The OTA operation policy automatic generation method of claim 3 wherein the attribute information includes: BOM row number, BOM row attribute, software part number, and software version number.
5. The method of claim 4, wherein comparing the first version attribute information with the second version attribute information to obtain a comparison result comprises:
Acquiring BOM line numbers, software part numbers, software version numbers and BOM line attributes of the first version and the second version;
sequentially comparing the BOM line number, the software part number, the software version number and the BOM line attribute of the first version with the second version;
if any item of attribute information of the first version is different from that of the attribute information of the second version, the obtained preliminary comparison results are different;
and if the attribute information of the first version is completely consistent with that of the second version, obtaining a comparison result without change.
6. The method for automatically generating OTA operation policy according to claim 5 wherein the preliminary comparison result includes:
if the content of the BOM line number of the second version does not appear in the first version, obtaining a comparison result to be newly increased;
if the content of the BOM line number of the first version is no longer appeared in the second version, the comparison result is obtained to be deleted;
If any one of the software part numbers and the software version numbers of the first version and the second version is different, the comparison result is obtained to be replaced;
If the BOM line attributes of the first version and the second version are inconsistent, the comparison result is modified.
7. The method of claim 6, wherein the obtaining the difference term according to the comparison result comprises:
if the comparison result is new, taking the new addition item of the second version relative to the first version as a difference item;
If the comparison result is replacement, taking a replacement item of the second version relative to the first version as a difference item;
if the comparison result is modification, taking a modification item of the second version relative to the first version as a difference item;
And if the comparison result is deletion, taking the deletion item of the second version relative to the first version as a difference item.
8. The method of claim 7, wherein the converting the difference term into the content to be upgraded comprises:
judging whether the comparison result corresponding to the difference item is deletion or not;
if the comparison result is not deletion, acquiring all version contents of the second version corresponding to the difference item, and generating the content to be upgraded according to the acquired version contents;
If the comparison result is deletion, the content to be upgraded is not generated.
9. The method of claim 4, wherein generating a version combination comprising a first version and a hardware version comprises:
Calculating a first version of the MD5 value;
Combining the MD5 value with the obtained hardware versions one by one;
and removing incompatible version combinations to obtain a final version combination.
10. The method of claim 10, wherein the method of calculating the MD5 value of the first version comprises:
acquiring all software part numbers of the first version;
ordering all software part numbers of the first version according to a Request ID rule;
and calculating the value of the ordered software part number to obtain the MD5 value.
11. The method for automatically generating an OTA operation policy according to claim 1 wherein said method for automatically generating an OTA operation policy further comprises: and automatically generating an OTA operation strategy according to the first version, the second version, the delineated target upgrading vehicle and the content to be upgraded.
12. An automatic generation system for OTA operation strategy, which is characterized by comprising
The vehicle information module is used for acquiring vehicle information to be upgraded according to the first version;
the difference calculation module is used for calculating a difference item between the first version and the second version and converting the difference item into upgrading content;
The version combination module is used for acquiring a hardware version according to the content to be upgraded and generating a version combination comprising the first version and the hardware version;
and the vehicle matching module is used for matching the vehicle information to be upgraded with the version combination and delineating a target upgrading vehicle.
13. An OTA operation policy automatic generation device, characterized by comprising:
a memory for storing a computer program;
a processor, configured to implement the steps of the method for automatically generating OTA operation policies according to any one of claims 1 to 11 when executing the computer program.
14. An OTA operation policy automatic generation readable storage medium, characterized in that a computer program is stored on the readable storage medium, the computer program being executed to implement the steps of the OTA operation policy automatic generation method according to any one of claims 1 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410090240.9A CN117931236A (en) | 2024-01-23 | 2024-01-23 | OTA operation policy automatic generation method, system, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410090240.9A CN117931236A (en) | 2024-01-23 | 2024-01-23 | OTA operation policy automatic generation method, system, equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117931236A true CN117931236A (en) | 2024-04-26 |
Family
ID=90755102
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410090240.9A Pending CN117931236A (en) | 2024-01-23 | 2024-01-23 | OTA operation policy automatic generation method, system, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117931236A (en) |
-
2024
- 2024-01-23 CN CN202410090240.9A patent/CN117931236A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11048493B2 (en) | Computer system, method of updating software with computer system, and program therefor | |
| US9648059B2 (en) | System and methods for multi-user CAx editing conflict management | |
| WO2019056540A1 (en) | Test case automation management method and apparatus, device, and storage medium | |
| CN101730099B (en) | Terminal management method based on authority control and device | |
| KR101738647B1 (en) | Data maintenance system | |
| CN111158674A (en) | Component management method, system, device and storage medium | |
| Quinton et al. | Evolution in dynamic software product lines: challenges and perspectives | |
| US9471608B2 (en) | Method, apparatus and computer program for migrating records in a database from a source database schema to a target database schema | |
| CN113535225B (en) | Environment configuration file processing method, device, equipment and medium of application software | |
| CN112380170B (en) | File updating operation association method and device and computer equipment | |
| US20230384750A1 (en) | Efficient controller data generation and extraction | |
| CN112363984A (en) | In-vehicle safety rule file generation method and device | |
| CN113741923A (en) | Application updating method, device, equipment and medium | |
| CN112540995B (en) | Data updating method, electronic device and storage medium | |
| CN112948099A (en) | Task issuing flow method and device, computer equipment and storage medium | |
| CN117931236A (en) | OTA operation policy automatic generation method, system, equipment and readable storage medium | |
| CN111427863A (en) | Data migration method, device and equipment based on domain model | |
| US20140088732A1 (en) | Methods and systems for configuration and management of electronic control unit | |
| CN114491195A (en) | Feature data identification method and device, electronic equipment and storage medium | |
| CN112118298A (en) | Configuration management method and device for distributed service | |
| CN117938906A (en) | Vehicle upgradeable version matching method, system, equipment and readable storage medium | |
| EP3404599A1 (en) | Information processing apparatus, method and program | |
| CN112346961A (en) | Debugging method and device for client | |
| CN109739544B (en) | Method and device for generating application installation package and electronic equipment | |
| JP2021189879A (en) | Version management device, version management method and software development device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |