Software upgrading management method and device for vehicle parts

Abstract

The invention relates to a software upgrading management method and device for vehicle parts, and the method comprises the steps: carrying out the classification and grouping operation of all parts of a target vehicle model; determining all the whole vehicle software versions of each target vehicle, binding the software versions of all the parts, and determining a part upgrading strategy and a part upgrading task based on all the whole vehicle software versions, the software versions and the part grouping result; obtaining to-be-upgraded part information of at least one to-be-upgraded part in all the parts, performing new version detection on each to-be-upgraded part to obtain a new version detection result, and generating a target upgraded part list based on the new version detection result, the part upgrading strategy and the part upgrading task, and the OTA vehicle end is controlled to execute software upgrading operation according to the upgrading software package corresponding to the target upgrading part list, so that the reliability and the upgrading efficiency of vehicle part upgrading are improved.

Description

Technical Field

[0001] The present application relates to the technical field of vehicle software upgrade management, and in particular to a method and device for software upgrade management of vehicle parts. Background Art

[0002] Currently, when managing vehicle software versions based on vehicle model dimensions, each vehicle is required to complete the upgrade of all parts included in the vehicle software version.

[0003] However, in the actual implementation process, the parts of a vehicle model can be divided into two categories: standard parts and optional parts. Even parts with the same function may be provided by multiple suppliers, and there may be multiple hardware versions as the product is iterated. Therefore, for a specific vehicle, the number of parts carried by this vehicle is generally less than the overall number of parts under the vehicle model, which affects the judgment of the upgrade result of this vehicle. For example, the optional parts that the vehicle is not equipped with, parts of other hardware versions, and parts from other suppliers cannot be upgraded, resulting in the vehicle being unable to complete the upgrade of all parts under the vehicle model required in the vehicle software version, and finally judging that the upgrade of this vehicle has failed.

[0004] In summary, the existing software upgrade method for vehicle parts is unable to manage the diversity of parts in the dimension of vehicle models, which greatly affects the reliability and efficiency of vehicle parts upgrades and needs to be solved urgently. Summary of the invention

[0005] The present application provides a software upgrade management method and device for vehicle parts to solve the problems of existing software upgrade methods for vehicle parts, which cannot manage the diversity of parts in terms of vehicle models, greatly affecting the reliability and efficiency of vehicle parts upgrades.

[0006] The first aspect of the present application provides a software upgrade management method for vehicle parts, comprising the following steps: classifying and grouping all parts of at least one target vehicle corresponding to a target vehicle model, and generating a parts grouping result for each target vehicle in the at least one target vehicle; determining all vehicle software versions of each target vehicle, and obtaining the software versions of all parts through the all vehicle software versions, and determining a parts upgrade strategy and a parts upgrade task based on all vehicle software versions, the software versions and the parts grouping results; obtaining upgraded parts information of at least one part to be upgraded among all the parts, and performing a new version detection on each part to be upgraded among the at least one part to be upgraded according to the upgraded parts information to obtain a new version detection result, and generating a target upgrade parts list based on the new version detection result, the parts upgrade strategy and the parts upgrade task to control a preset OTA vehicle end to perform corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list.

[0007] Optionally, in one embodiment of the present application, the classification and grouping operations are performed on all parts of at least one target vehicle corresponding to the target vehicle model to generate a parts grouping result for each target vehicle in the at least one target vehicle, including: classifying all parts of each target vehicle under the target vehicle model to obtain the classification results of all parts, wherein the classification results include standard parts and optional parts; grouping and managing multi-source parts with the same function in the standard parts and the optional parts to generate the parts grouping results, wherein the parts grouping results include single parts groups and multi-source parts groups.

[0008] Optionally, in one embodiment of the present application, the obtaining of the parts information to be upgraded of at least one part to be upgraded among all the parts, and performing a new version detection on each of the at least one part to be upgraded according to the parts information to be upgraded to obtain a new version detection result, includes: reading the parts information to be upgraded corresponding to each target vehicle through a preset OTA vehicle end, wherein the parts information to be upgraded includes at least one of a part number, a supplier, a hardware version number and a software version number; uploading the parts information to be upgraded to a preset OTA cloud, and sending a new version detection request to the OTA cloud, so that the OTA cloud performs a new version detection on each of the parts to be upgraded according to the new version detection request to obtain the new version detection result.

[0009] Optionally, in one embodiment of the present application, the control preset OTA vehicle-side performs corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list, including: downloading the upgrade software package corresponding to each target upgrade part in the target upgrade parts list; judging whether the upgrade software package of each target upgrade part meets the preset verification requirements, wherein, when the upgrade software package meets the preset verification requirements, performing a preset flashing operation on the upgrade software package to obtain a flashing result; judging whether the flashing results of the upgrade software packages corresponding to each target upgrade part all meet the preset flashing success requirements, if the flashing results of the upgrade software packages corresponding to each target upgrade part all meet the flashing success requirements, updating the vehicle software version number of the OTA vehicle-side; if the flashing results of the upgrade software package corresponding to at least one target upgrade part among all the target upgrade parts do not meet the flashing success requirements, rolling back all installed target upgrade parts, terminating the flashing operation, and not updating the vehicle software version number of the OTA vehicle-side.

[0010] Optionally, in one embodiment of the present application, after controlling the preset OTA vehicle-side to perform corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list, it also includes: if the upgrade software package corresponding to the single part of the single part group corresponding to the standard parts is successfully installed, and the upgrade software package corresponding to any part in the multi-source parts group is successfully installed, then it is determined that the upgrade software package corresponding to the standard parts of the target vehicle is successfully installed; if the target vehicle does not have the single part group corresponding to the optional parts and the target upgrade parts in the multi-source parts group, there is no need to install the upgrade software package corresponding to the target upgrade parts; otherwise, when the upgrade software package corresponding to the single part of the single part group corresponding to the optional parts is successfully installed, and the upgrade software package corresponding to any part in the multi-source parts group corresponding to the optional parts is successfully installed, then it is determined that the upgrade software package corresponding to the standard parts of the target vehicle is successfully installed.

[0011] The second aspect of the present application provides a software upgrade management device for vehicle parts, including: a grouping module, used to classify and group all parts of at least one target vehicle corresponding to a target vehicle model, and generate a part grouping result for each target vehicle in the at least one target vehicle; a binding module, used to determine all vehicle software versions of each target vehicle, and obtain the software versions of all parts through the all vehicle software versions, and determine the parts upgrade strategy and parts upgrade task based on all vehicle software versions, the software versions and the parts grouping results; an upgrade module, used to obtain the parts information to be upgraded of at least one part to be upgraded among all the parts, and perform a new version detection on each part to be upgraded in the at least one part to be upgraded according to the parts information to obtain a new version detection result, and generate a target upgrade parts list based on the new version detection result, the parts upgrade strategy and the parts upgrade task, so as to control the preset OTA vehicle end to perform the corresponding software upgrade operation according to the upgrade software package corresponding to the target upgrade parts list.

[0012] Optionally, in one embodiment of the present application, the grouping module includes: a classification unit, used to classify all parts of each target vehicle under the target vehicle model to obtain classification results of all the parts, wherein the classification results include standard parts and optional parts; a generation unit, used to group and manage multi-source parts with the same function in the standard parts and the optional parts, and generate the parts grouping results, wherein the parts grouping results include single part groups and multi-source part groups.

[0013] Optionally, in one embodiment of the present application, the upgrade module includes: a reading unit, used to read the parts information to be upgraded corresponding to each target vehicle through a preset OTA vehicle side, wherein the parts information to be upgraded includes at least one of a part number, a supplier, a hardware version number and a software version number; a detection unit, used to upload the parts information to be upgraded to a preset OTA cloud, and send a new version detection request to the OTA cloud, so that the OTA cloud performs a new version detection on each part to be upgraded according to the new version detection request to obtain the new version detection result.

[0014] Optionally, in one embodiment of the present application, the upgrade module also includes: a download unit, used to download the upgrade software package corresponding to each target upgrade part in the target upgrade parts list; a first judgment unit, used to judge whether the upgrade software package of each target upgrade part meets the preset verification requirements, wherein, when the upgrade software package meets the preset verification requirements, the upgrade software package is subjected to a preset flashing operation to obtain a flashing result; a second judgment unit, used to judge whether the flashing results of the upgrade software packages corresponding to each target upgrade part meet the preset flashing success requirements, if the flashing results of the upgrade software packages corresponding to each target upgrade part meet the flashing success requirements, then update the vehicle software version number of the OTA vehicle side; a processing unit, used to roll back all installed target upgrade parts, terminate the flashing operation, and do not update the vehicle software version number of the OTA vehicle side if the flashing results of the upgrade software package corresponding to at least one target upgrade part among all the target upgrade parts do not meet the flashing success requirements.

[0015] Optionally, in one embodiment of the present application, it also includes: a first judgment module, which is used to control the preset OTA vehicle side to perform a corresponding software upgrade operation according to the upgrade software package corresponding to the target upgrade parts list. If the upgrade software package corresponding to the single part of the single part group corresponding to the standard parts is successfully installed, and the upgrade software package corresponding to any part in the multi-source parts group is successfully installed, then it is determined that the upgrade software package corresponding to the standard parts of the target vehicle is successfully installed; a second judgment module, which is used to determine that if the target vehicle does not have the single part group corresponding to the optional parts and the target upgrade parts in the multi-source parts group, there is no need to install the upgrade software package corresponding to the target upgrade parts; otherwise, when the upgrade software package corresponding to the single part of the single part group corresponding to the optional parts is successfully installed, and the upgrade software package corresponding to any part in the multi-source parts group corresponding to the optional parts is successfully installed, then it is determined that the upgrade software package corresponding to the standard parts of the target vehicle is successfully installed.

[0016] A third aspect of the present application provides a vehicle, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the software upgrade management method for vehicle parts as described in the above embodiment.

[0017] The fourth aspect of the present application provides a computer-readable storage medium, which stores a computer program that, when executed by a processor, implements the above-mentioned vehicle parts software upgrade management method.

[0018] The fifth aspect of the present application provides a computer program product, including a computer program, which is executed to implement the above-mentioned vehicle parts software upgrade management method.

[0019] Therefore, the embodiments of the present application have the following beneficial effects:

[0020] The embodiment of the present application can generate the part grouping result of each target vehicle in at least one target vehicle by classifying and grouping all parts of at least one target vehicle corresponding to the target vehicle model; determine all vehicle software versions of each target vehicle, and obtain the software versions of all parts through all vehicle software versions, and determine the part upgrade strategy and part upgrade task based on all vehicle software versions, software versions and part grouping results; obtain the part information to be upgraded of at least one part to be upgraded among all parts, and perform new version detection on each part to be upgraded in at least one part to be upgraded according to the part information to be upgraded, obtain the new version detection result, and generate the target upgrade part list based on the new version detection result, part upgrade strategy and part upgrade task, so as to control the preset OTA vehicle end to perform the corresponding software upgrade operation according to the upgrade software package corresponding to the target upgrade part list. The present application classifies and groups the parts in the vehicle model, and sets the judgment criteria for successful installation to manage the vehicle software version in the vehicle model dimension, thereby improving the reliability and upgrade efficiency of vehicle part upgrades. Thus, the existing software upgrade method for vehicle parts is solved, which cannot manage the diversity of parts in the vehicle model dimension, greatly affecting the reliability and efficiency of vehicle part upgrades.

[0021] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0023] Figure 1A flowchart of a vehicle parts software upgrade management method provided according to an embodiment of the present application;

[0024] Figure 2 A schematic diagram of parts classification and grouping of a vehicle model provided for one embodiment of the present application;

[0025] Figure 3 A schematic diagram of the logical architecture of a vehicle parts software upgrade management method provided by one embodiment of the present application;

[0026] Figure 4 A schematic diagram of an upgrade task judgment standard provided for an embodiment of the present application;

[0027] Figure 5 A schematic diagram of a software installation judgment standard provided for an embodiment of the present application;

[0028] Figure 6 This is an example diagram of a software upgrade management device for vehicle parts according to an embodiment of the present application;

[0029] Figure 7 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application.

[0030] Among them, 10-software upgrade management device for vehicle parts, 100-grouping module, 200-binding module, 300-upgrade module, 701-memory, 702-processor, 703-communication interface. DETAILED DESCRIPTION

[0031] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0032] The following describes the software upgrade management method and device of vehicle parts of the embodiment of the present application with reference to the accompanying drawings. In view of the problems mentioned in the above background technology, the present application provides a software upgrade management method for vehicle parts, in which all parts of at least one target vehicle corresponding to the target vehicle model are classified and grouped to generate the part grouping result of each target vehicle in at least one target vehicle; all vehicle software versions of each target vehicle are determined, and the software versions of all parts are obtained through all vehicle software versions, and based on all vehicle software versions, software versions and part grouping results, the parts upgrade strategy and parts upgrade task are determined; the parts information to be upgraded of at least one part to be upgraded among all parts is obtained, and each part to be upgraded in at least one part to be upgraded is detected with a new version according to the parts information to be upgraded, and the new version detection result is obtained, and based on the new version detection result, the parts upgrade strategy and the parts upgrade task, a target upgrade parts list is generated to control the preset OTA vehicle end to perform the corresponding software upgrade operation according to the upgrade software package corresponding to the target upgrade parts list. The present application classifies and groups the parts in the vehicle model and sets the judgment criteria for successful installation to manage the vehicle software version in the vehicle model dimension, thereby improving the reliability and upgrade efficiency of vehicle parts upgrade. This solves the problem that the existing software upgrade method for vehicle parts is unable to manage the diversity of parts in the vehicle model dimension, which greatly affects the reliability and efficiency of vehicle parts upgrades.

[0033] Specifically, Figure 1 A flowchart of a vehicle parts software upgrade management method provided in an embodiment of the present application.

[0034] like Figure 1 As shown, the software upgrade management method of the vehicle parts includes the following steps:

[0035] In step S101, all parts of at least one target vehicle corresponding to the target vehicle model are classified and grouped to generate a part grouping result for each target vehicle in the at least one target vehicle.

[0036] The embodiments of the present application can first classify and group all parts of at least one vehicle under the corresponding model, thereby providing reliable data basis and guidance for the subsequent software upgrade management of vehicle parts.

[0037] Optionally, in one embodiment of the present application, all parts of at least one target vehicle corresponding to the target vehicle model are classified and grouped to generate a parts grouping result for each target vehicle in the at least one target vehicle, including: classifying all parts of each target vehicle under the target vehicle model to obtain classification results for all parts, wherein the classification results include standard parts and optional parts; grouping and managing multi-source parts with the same function in the standard parts and optional parts to generate a parts grouping result, wherein the parts grouping result includes a single part group and a multi-source part group.

[0038] It should be noted that the embodiments of the present application can classify all parts under the vehicle model into standard parts and optional parts, and group and manage multi-source parts with the same function in the standard parts and optional parts respectively, such as Figure 2 As shown, parts with the same function provided by different suppliers and multiple hardware versions are grouped into one group.

[0039] Therefore, the embodiment of the present application effectively improves the efficiency of software upgrade management of vehicle parts by classifying and grouping all parts of the target vehicle model.

[0040] In step S102, all vehicle software versions of each target vehicle are determined, and the software versions of all parts are obtained through all vehicle software versions. Based on all vehicle software versions, software versions and parts grouping results, the parts upgrade strategy and parts upgrade tasks are determined.

[0041] In step S103, the parts information to be upgraded of at least one part to be upgraded among all the parts is obtained, and a new version detection is performed on each of the at least one part to be upgraded according to the parts information to obtain a new version detection result, and based on the new version detection result, the parts upgrade strategy and the parts upgrade task, a target upgrade parts list is generated to control the preset OTA vehicle side to perform corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list.

[0042] Furthermore, the embodiments of the present application also need to manage all vehicle software versions under the vehicle model, and bind the software versions of all parts to the vehicle software version, so that the software version of the corresponding part and the type of part and whether it is in a certain group can be known according to the vehicle software version number.

[0043] Furthermore, based on all vehicle software versions, software versions and parts grouping results, the embodiment of the present application can determine the parts upgrade strategy and parts upgrade tasks, and obtain the target upgrade parts list. In the embodiment of the present application, the parts upgrade strategy is configured with the source vehicle software version number of the upgrade, the target vehicle software version number and other upgrade strategies, and the upgrade strategy and the vehicle range to be upgraded can be selected in the upgrade task.

[0044] Afterwards, the embodiment of the present application can receive the parts information reported by the vehicle side and process the new version detection request of the OTA vehicle side, and match the parts information on the vehicle side with the parts list corresponding to the whole vehicle software version in the upgrade strategy, and then determine the parts list that needs to be upgraded on the vehicle side (i.e., the target upgrade parts list) based on the parts classification and whether the parts are in the group, and then send the parts list and the corresponding software package to the OTA vehicle side, thereby realizing the vehicle model dimension management of diverse parts.

[0045] Optionally, in one embodiment of the present application, the parts information to be upgraded of at least one part to be upgraded among all the parts is obtained, and a new version detection is performed on each part to be upgraded among the at least one part to be upgraded according to the parts information to obtain a new version detection result, including: reading the parts information to be upgraded corresponding to each target vehicle through a preset OTA vehicle end, wherein the parts information to be upgraded includes at least one of a part number, a supplier, a hardware version number, and a software version number; uploading the parts information to be upgraded to a preset OTA cloud, and sending a new version detection request to the OTA cloud, so that the OTA cloud performs a new version detection on each part to be upgraded according to the new version detection request to obtain a new version detection result.

[0046] It should be noted that the embodiments of the present application can read all the upgradeable parts information of the current vehicle through the OTA vehicle side, including part number, supplier, hardware version number, software version number, etc., and report the parts information read by the vehicle side to the OTA cloud, and request the OTA cloud to detect the new version, thereby obtaining the new version detection result.

[0047] Therefore, the embodiments of the present application read and report part information through OTA vehicle side to detect new versions of parts to be upgraded, thereby effectively ensuring the reliability of software upgrades of vehicle parts.

[0048] Optionally, in one embodiment of the present application, the preset OTA vehicle-side is controlled to perform corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list, including: downloading the upgrade software package corresponding to each target upgrade part in the target upgrade parts list; determining whether the upgrade software package of each target upgrade part meets the preset verification requirements, wherein, when the upgrade software package meets the preset verification requirements, performing a preset flashing operation on the upgrade software package to obtain a flashing result; determining whether the flashing results of the upgrade software package corresponding to each target upgrade part all meet the preset flashing success requirements, if the flashing results of the upgrade software package corresponding to each target upgrade part all meet the flashing success requirements, then updating the vehicle software version number of the OTA vehicle-side; if the flashing results of the upgrade software package corresponding to at least one target upgrade part among all the target upgrade parts do not meet the flashing success requirements, then rolling back all installed target upgrade parts, terminating the flashing operation, and not updating the vehicle software version number of the OTA vehicle-side.

[0049] After detecting a new version of the part to be upgraded, Figure 3 As shown, the embodiment of the present application can download the parts software package and parts installation requirements that need to be upgraded, and after the software package is successfully downloaded and verified, execute the flashing of the parts software package; if all required parts are flashed successfully, the vehicle software version number on the vehicle side is updated; if a part fails to be flashed during the flashing process, all installed parts need to be rolled back, and the flashing task is terminated, and the vehicle software version number on the vehicle side is not updated.

[0050] Optionally, in one embodiment of the present application, after controlling the preset OTA vehicle side to perform corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list, it also includes: if the upgrade software package corresponding to a single part of a single part group corresponding to the standard parts is successfully installed, and the upgrade software package corresponding to any part in the multi-source parts group is successfully installed, then it is determined that the upgrade software package corresponding to the standard parts of the target vehicle is successfully installed; if the target vehicle does not have a single part group corresponding to the optional parts and the target upgrade parts in the multi-source parts group, there is no need to install the upgrade software package corresponding to the target upgrade parts; otherwise, when the upgrade software package corresponding to a single part of the single part group corresponding to the optional parts is successfully installed, and the upgrade software package corresponding to any part in the multi-source parts group corresponding to the optional parts is successfully installed, then it is determined that the upgrade software package corresponding to the standard parts of the target vehicle is successfully installed.

[0051] After executing the corresponding software upgrade operation, the embodiment of the present application can set the judgment criteria for successful software installation for the optional parts and the standard parts, such as Figure 4 The specific judgment basis is as follows:

[0052] 1. For standard parts, each vehicle must install them, and if the upgrade software package corresponding to a single part of a single parts group corresponding to the standard parts is successfully installed, and the upgrade software package corresponding to any part in the multi-source parts group is successfully installed, then it can be determined that the upgrade software package corresponding to the standard parts of the target vehicle is successfully installed;

[0053] 2. For optional parts, they must be installed after the vehicle is assembled. If the vehicle does not have the upgrade parts in the single parts group and the multi-source parts group corresponding to the optional parts, there is no need to install the upgrade software package corresponding to the upgrade parts; otherwise, when the upgrade software package corresponding to the single part of the single parts group corresponding to the optional parts is successfully installed, and the upgrade software package corresponding to any part in the multi-source parts group corresponding to the optional parts is successfully installed, it is determined that the upgrade software package corresponding to the standard parts of the vehicle is successfully installed.

[0054] For example, Figure 5 As shown, when the part assembled on the vehicle VIN1 is ECU3-A-H1, since this part type is a standard part and is a part in the multi-source part group 1, the embodiment of the present application only requires the part to be successfully installed, and other unassembled parts can be ignored; when the part assembled on the vehicle VIN1 is ECU6-A-H1, since this part type is an optional part and is a part in the multi-source part group 2, the embodiment of the present application only requires the part to be successfully installed, and other unassembled parts can be ignored.

[0055] Therefore, the embodiments of the present application can flexibly manage and upgrade diverse parts from the vehicle model dimension.

[0056] According to the software upgrade management method for vehicle parts proposed in the embodiment of the present application, by classifying and grouping all parts of at least one target vehicle corresponding to the target vehicle model, the part grouping result of each target vehicle in at least one target vehicle is generated; all vehicle software versions of each target vehicle are determined, and the software versions of all parts are obtained through all vehicle software versions, and based on all vehicle software versions, software versions and part grouping results, the parts upgrade strategy and parts upgrade task are determined; the parts information to be upgraded of at least one part to be upgraded among all parts is obtained, and each part to be upgraded in at least one part to be upgraded is detected with a new version according to the parts information to be upgraded, and the new version detection result is obtained, and based on the new version detection result, the parts upgrade strategy and parts upgrade task, a target upgrade parts list is generated to control the preset OTA vehicle end to perform the corresponding software upgrade operation according to the upgrade software package corresponding to the target upgrade parts list. The present application classifies and grouped the parts in the vehicle model, and sets the judgment criteria for successful installation to manage the vehicle software version in the vehicle model dimension, thereby improving the reliability and upgrade efficiency of vehicle parts upgrades.

[0057] Secondly, the software upgrade management device for vehicle parts proposed in accordance with the embodiment of the present application is described with reference to the accompanying drawings.

[0058] Figure 6 It is a block diagram of a software upgrade management device for vehicle parts according to an embodiment of the present application.

[0059] like Figure 6 As shown, the vehicle parts software upgrade management device 10 includes: a grouping module 100, a binding module 200 and an upgrade module 300.

[0060] The grouping module 100 is used to classify and group all parts of at least one target vehicle corresponding to the target vehicle model, and generate a part grouping result for each target vehicle in the at least one target vehicle.

[0061] The binding module 200 is used to determine all vehicle software versions of each target vehicle, and obtain the software versions of all parts through all vehicle software versions, and determine the parts upgrade strategy and parts upgrade tasks based on all vehicle software versions, software versions and parts grouping results.

[0062] The upgrade module 300 is used to obtain the part information to be upgraded of at least one part to be upgraded among all the parts, and perform new version detection on each part to be upgraded among the at least one part to be upgraded according to the part information to obtain the new version detection result, and generate a target upgrade parts list based on the new version detection result, part upgrade strategy and part upgrade task, so as to control the preset OTA vehicle side to perform corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list.

[0063] Optionally, in one embodiment of the present application, the grouping module 100 includes: a classification unit and a generation unit.

[0064] The classification unit is used to classify all parts of each target vehicle under the target model to obtain classification results of all parts, wherein the classification results include standard parts and optional parts.

[0065] The generating unit is used for grouping and managing multi-source parts with the same function in standard parts and optional parts, and generating part grouping results, wherein the part grouping results include single part groups and multi-source part groups.

[0066] Optionally, in one embodiment of the present application, the upgrade module 300 includes: a reading unit and a detection unit.

[0067] Among them, the reading unit is used to read the parts information to be upgraded corresponding to each target vehicle through the preset OTA vehicle end, wherein the parts information to be upgraded includes at least one of the part number, supplier, hardware version number and software version number.

[0068] The detection unit is used to upload the information of the parts to be upgraded to the preset OTA cloud, and send a new version detection request to the OTA cloud, so that the OTA cloud performs a new version detection on each part to be upgraded according to the new version detection request to obtain a new version detection result.

[0069] Optionally, in one embodiment of the present application, the upgrade module 300 further includes: a downloading unit, a first judgment unit, a second judgment unit and a processing unit.

[0070] The download unit is used to download the upgrade software package corresponding to each target upgrade part in the target upgrade parts list.

[0071] The first judgment unit is used to judge whether the upgrade software package of each target upgrade part meets the preset verification requirement, wherein, if the upgrade software package meets the preset verification requirement, a preset flashing operation is performed on the upgrade software package to obtain a flashing result.

[0072] The second judgment unit is used to judge whether the flashing results of the upgrade software package corresponding to each target upgrade part meet the preset flashing success requirements. If the flashing results of the upgrade software package corresponding to each target upgrade part meet the flashing success requirements, the vehicle software version number of the OTA vehicle side is updated.

[0073] A processing unit is used to roll back all installed target upgrade parts and terminate the flashing operation if the flashing result of the upgrade software package corresponding to at least one target upgrade part among all target upgrade parts does not meet the flashing success requirements, and does not update the vehicle software version number of the OTA vehicle side.

[0074] Optionally, in one embodiment of the present application, the vehicle parts software upgrade management device 10 of the embodiment of the present application further includes: a first determination module and a second determination module.

[0075] Among them, the first judgment module is used to control the preset OTA vehicle side to perform the corresponding software upgrade operation according to the upgrade software package corresponding to the target upgrade parts list. If the upgrade software package corresponding to the single part of the single part group corresponding to the standard parts is successfully installed, and the upgrade software package corresponding to any part in the multi-source parts group is successfully installed, then it is determined that the upgrade software package corresponding to the standard parts of the target vehicle is successfully installed.

[0076] The second determination module is configured to determine that if the target vehicle does not have a single part group corresponding to the optional part and a target upgrade part in the multi-source part group, there is no need to install the upgrade software package corresponding to the target upgrade part; otherwise, when the upgrade software package corresponding to a single part of the single part group corresponding to the optional part is successfully installed and the upgrade software package corresponding to any part in the multi-source part group corresponding to the optional part is successfully installed, it is determined that the upgrade software package corresponding to the standard part of the target vehicle is successfully installed.

[0077] It should be noted that the above explanation of the embodiment of the vehicle parts software upgrade management method is also applicable to the vehicle parts software upgrade management device of this embodiment, and will not be repeated here.

[0078] According to the software upgrade management device for vehicle parts proposed in the embodiment of the present application, it includes a grouping module, which is used to classify and group all parts of at least one target vehicle corresponding to the target vehicle model, and generate a part grouping result for each target vehicle in at least one target vehicle; a binding module, which is used to determine all vehicle software versions of each target vehicle, and obtain the software versions of all parts through all vehicle software versions, and determine the part upgrade strategy and part upgrade task based on all vehicle software versions, software versions and part grouping results; an upgrade module, which is used to obtain the part information to be upgraded of at least one part to be upgraded among all parts, and perform a new version detection on each part to be upgraded in at least one part to be upgraded according to the part information to be upgraded, and obtain the new version detection result, and generate a target upgrade part list based on the new version detection result, part upgrade strategy and part upgrade task, so as to control the preset OTA vehicle end to perform the corresponding software upgrade operation according to the upgrade software package corresponding to the target upgrade part list. The present application classifies and groups the parts in the vehicle model, and sets the judgment criteria for successful installation to perform vehicle software version management in the vehicle model dimension, thereby improving the reliability and upgrade efficiency of vehicle part upgrades.

[0079] Figure 7 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application. The vehicle may include:

[0080] A memory 701 , a processor 702 , and a computer program stored in the memory 701 and executable on the processor 702 .

[0081] When the processor 702 executes the program, the vehicle parts software upgrade management method provided in the above embodiment is implemented.

[0082] Furthermore, the vehicle also includes:

[0083] The communication interface 703 is used for communication between the memory 701 and the processor 702 .

[0084] The memory 701 is used to store computer programs that can be executed on the processor 702 .

[0085] The memory 701 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0086] If the memory 701, the processor 702 and the communication interface 703 are implemented independently, the communication interface 703, the memory 701 and the processor 702 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 7 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0087] Optionally, in a specific implementation, if the memory 701, the processor 702 and the communication interface 703 are integrated on a chip, the memory 701, the processor 702 and the communication interface 703 can communicate with each other through an internal interface.

[0088] The processor 702 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0089] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-mentioned method for software upgrade management of vehicle parts.

[0090] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed, is used to implement the above-mentioned vehicle parts software upgrade management method.

[0091] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0092] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0093] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or N executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0094] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or N wirings (electronic devices), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways as necessary and then storing it in a computer memory.

[0095] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above embodiment, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. If implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0096] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0097] In addition, each functional unit in each embodiment of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0098] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present application. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A software upgrade management method for vehicle parts, characterized in that: The following steps are involved: Classifying and grouping all parts of at least one target vehicle corresponding to the target vehicle model, and generating a parts grouping result for each target vehicle in the at least one target vehicle; Determine all vehicle software versions of each target vehicle, and obtain the software versions of all parts through all vehicle software versions, and determine the parts upgrade strategy and parts upgrade task based on all vehicle software versions, the software versions and the parts grouping results; Obtaining the part information of at least one part to be upgraded among all the parts, and performing a new version detection on each of the at least one part to be upgraded according to the part information to obtain a new version detection result, and generating a target upgrade parts list based on the new version detection result, the part upgrade strategy and the part upgrade task, so as to control the preset OTA vehicle end to perform corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list.

2. The method according to claim 1, characterized in that The classifying and grouping operations are performed on all parts of at least one target vehicle corresponding to the target vehicle model to generate a part grouping result for each target vehicle in the at least one target vehicle, including: Classifying all parts of each target vehicle under the target vehicle model to obtain classification results of all the parts, wherein the classification results include standard parts and optional parts; Multi-source parts with the same function in the standard parts and the optional parts are grouped and managed to generate the parts grouping result, wherein the parts grouping result includes a single parts group and a multi-source parts group.

3. The method according to claim 1, characterized in that The acquiring the part information to be upgraded of at least one part to be upgraded among all the parts, and performing a new version detection on each part to be upgraded among the at least one part to be upgraded according to the part information to be upgraded to obtain a new version detection result, includes: Reading the part information to be upgraded corresponding to each target vehicle through a preset OTA vehicle terminal, wherein the part information to be upgraded includes at least one of a part number, a supplier, a hardware version number, and a software version number; The information of the parts to be upgraded is uploaded to a preset OTA cloud, and a new version detection request is sent to the OTA cloud, so that the OTA cloud performs a new version detection on each part to be upgraded according to the new version detection request to obtain the new version detection result.

4. The method according to claim 1, characterized in that: The control preset OTA vehicle end performs corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list, including: Download the upgrade software package corresponding to each target upgrade part in the target upgrade parts list; Determining whether the upgrade software package of each target upgrade part meets a preset verification requirement, wherein, if the upgrade software package meets the preset verification requirement, performing a preset flashing operation on the upgrade software package to obtain a flashing result; Determine whether the flashing results of the upgrade software packages corresponding to each target upgrade part meet the preset flashing success requirements, and if the flashing results of the upgrade software packages corresponding to each target upgrade part meet the flashing success requirements, update the vehicle software version number of the OTA vehicle end; If the flashing result of the upgrade software package corresponding to at least one target upgrade part among all target upgrade parts does not meet the flashing success requirement, all installed target upgrade parts are rolled back, the flashing operation is terminated, and the vehicle software version number of the OTA vehicle side is not updated.

5. The method according to claim 2, characterized in that: After controlling the preset OTA vehicle end to perform corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list, the method further includes: If the upgrade software package corresponding to a single part of the single parts group corresponding to the standard parts is successfully installed, and the upgrade software package corresponding to any part in the multi-source parts group is successfully installed, it is determined that the upgrade software package corresponding to the standard parts of the target vehicle is successfully installed; If the target vehicle does not have a single part group corresponding to the optional part and a target upgrade part in the multi-source part group, there is no need to install the upgrade software package corresponding to the target upgrade part; otherwise, when the upgrade software package corresponding to a single part of the single part group corresponding to the optional part is successfully installed and the upgrade software package corresponding to any part in the multi-source part group corresponding to the optional part is successfully installed, it is determined that the upgrade software package corresponding to the standard part of the target vehicle is successfully installed.

6. A software upgrade management device for vehicle parts, characterized in that: include: A grouping module, used to classify and group all parts of at least one target vehicle corresponding to the target vehicle model, and generate a part grouping result for each target vehicle in the at least one target vehicle; A binding module, used to determine all vehicle software versions of each target vehicle, and obtain the software versions of all parts through all vehicle software versions, and determine the parts upgrade strategy and parts upgrade task based on all vehicle software versions, the software versions and the parts grouping results; An upgrade module is used to obtain the part information to be upgraded of at least one part to be upgraded among all the parts to be upgraded, and perform a new version detection on each part to be upgraded among the at least one part to be upgraded according to the part information to obtain a new version detection result, and generate a target upgrade parts list based on the new version detection result, the part upgrade strategy and the part upgrade task, so as to control the preset OTA vehicle end to perform corresponding software upgrade operations according to the upgrade software package corresponding to the target upgrade parts list.

7. The device according to claim 6, characterized in that The grouping module comprises: A classification unit, used for classifying all parts of each target vehicle under the target vehicle model to obtain classification results of all the parts, wherein the classification results include standard parts and optional parts; The generating unit is used for grouping and managing the multi-source parts with the same function in the standard parts and the optional parts, and generating the parts grouping result, wherein the parts grouping result includes a single parts group and a multi-source parts group.

8. A vehicle, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the software upgrade management method for vehicle parts as described in any one of claims 1 to 5.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement the software upgrade management method for vehicle parts as described in any one of claims 1-5.

10. A computer program product, comprising a computer program, characterized in that The computer program is executed to implement the software upgrade management method for vehicle parts as described in any one of claims 1-5.

Images