Vehicle software version alignment method and system, computer equipment, medium and program

Abstract

The invention relates to the technical field of vehicle upgrading, and discloses a vehicle software version alignment method and system, computer equipment, a medium and a program. And after the cloud receives a version consistency detection instruction of the terminal equipment and the information of the to-be-detected vehicle, the cloud performs version consistency detection on the to-be-detected vehicle and identifies the vehicle which does not correspond to the baseline version information of each vehicle type. Afterwards, after receiving the version consistency alignment instruction of the terminal device, the cloud end formulates a version consistency alignment task and sends the version consistency alignment task to the corresponding vehicle of the vehicle end, so that the corresponding vehicle is subjected to software version alignment, the consistency of software versions on different vehicles of the same vehicle type is realized, and the difficulty of vehicle software version management is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle upgrade, and in particular to a vehicle software version alignment method, system, computer equipment, medium and program. Background Art

[0002] The automotive industry has begun to widely use Over-The-Air (OTA) technology to directly iterate and update the vehicle software system. In order to standardize the management of vehicle software upgrades, car companies have set corresponding controller software version numbers for different software versions of each controller, and the software version set of each controller corresponds to a major version number of the entire vehicle.

[0003] Usually, manufacturers will set the vehicle major version number to a certain initial value when the vehicle leaves the factory. In fact, during the pre-delivery inspection (PDI) of passenger vehicles, the software versions of each controller have been switched at the factory. Only after an OTA iteration upgrade will the initial vehicle major version number be updated to the correct vehicle major version number. If there is no OTA iteration requirement for the model, the vehicle major version number displayed after the vehicle is sold will always be the initial value, which will cause users to be unclear about the real software version of the vehicle, and even doubt the reliability of the vehicle software information and the authenticity of the software version.

[0004] Based on the existing software version of the vehicle, the existing technology uses the vehicle hardware information to determine whether the vehicle is compatible with the hardware version associated with the software baseline version, and pushes the appropriate upgradeable software version to the vehicle, solving the problem of version incompatibility when there are too many software versions of a controller of the same model on the market, and reducing the cost of manual judgment. However, this method cannot guarantee the consistency of software versions of different vehicles of the same model after upgrading during PDI detection. Summary of the invention

[0005] In view of this, the present invention provides a vehicle software version alignment method, system, computer device, medium and program to solve the problem in the prior art that when there are too many software versions of the same controller of a certain model during PDI detection, the software versions on different vehicles of the model cannot be aligned.

[0006] In a first aspect, the present invention provides a vehicle software version alignment method, which is applied to the cloud, and the method comprises:

[0007] Obtain the baseline version information of each vehicle model and receive the controller version information sent by the vehicle end;

[0008] After receiving the version consistency detection instruction and the vehicle information to be detected sent by the terminal device, based on the baseline version information of each vehicle model, the controller version information and the vehicle information to be detected, the version consistency detection is performed on the vehicle to be detected, and the detection result is obtained and sent to the terminal device;

[0009] After receiving the version consistency alignment instruction sent by the terminal device based on the detection results, a version consistency alignment task is formulated based on the detection results and sent to the vehicle side, so that the vehicle side executes the version consistency alignment task and aligns the software version of the corresponding vehicle.

[0010] Beneficial effects: The cloud is used to obtain the baseline version information of each vehicle model and the controller version information of the vehicle end, so that after receiving the version consistency detection instruction of the terminal device and the vehicle information to be detected, the cloud performs version consistency detection on the vehicle to be detected, and identifies the vehicle that does not correspond to the baseline version information of each vehicle model. Afterwards, after receiving the version consistency alignment instruction of the terminal device, the cloud formulates a version consistency alignment task and sends it to the corresponding vehicle on the vehicle end, so that the corresponding vehicle performs software version alignment, achieves consistency of software versions on different vehicles of the same model, and thus reduces the difficulty of vehicle software version management.

[0011] In an optional implementation, based on the baseline version information of each vehicle type, the controller version information and the information of the vehicle to be detected, a version consistency test is performed on the vehicle to be detected to obtain a test result, including:

[0012] According to the information of the vehicles to be detected, the model information and identification code information of each vehicle to be detected are obtained;

[0013] Based on the vehicle model information and identification code information, query the controller version information and the baseline version information of each vehicle model to obtain the software version information and baseline version information of each vehicle to be tested;

[0014] For each vehicle to be detected, the baseline version information and software version information corresponding to the current vehicle to be detected are compared to obtain a detection result corresponding to the current vehicle to be detected.

[0015] Beneficial effect: According to the model information and identification code information of the vehicle to be tested, the software version information and baseline version information of each vehicle to be tested are obtained, and then the software version information and baseline version information of each vehicle to be tested are compared to obtain the test result of each vehicle to be tested, so as to realize the software version consistency detection of different vehicles of the same model.

[0016] In an optional implementation, the baseline version information includes the baseline major version number of the vehicle and the baseline software version of each controller, and the software version information includes the current major version number of the vehicle and the current software version of each controller; the baseline version information and the software version information corresponding to the current vehicle to be detected are compared to obtain a detection result corresponding to the current vehicle to be detected, including:

[0017] Determine whether the current software version of each controller on the current vehicle to be tested is consistent with the baseline software version and whether the current major version number of the entire vehicle to be tested is consistent with the baseline major version number of the entire vehicle;

[0018] If the current software version of each controller on the current vehicle to be tested is consistent with the baseline software version, and the current major version number of the entire vehicle of the current vehicle to be tested is consistent with the major version number of the entire vehicle baseline, then the test result of the current vehicle to be tested is determined to be that both the controller software version and the vehicle major version number are aligned;

[0019] If the current software version of each controller on the current vehicle to be tested is inconsistent with the baseline software version, and / or the current major version number of the entire vehicle to be tested is inconsistent with the baseline major version number of the entire vehicle, then the test result of the current vehicle to be tested is determined to be that the controller software version and / or the vehicle major version number are not aligned.

[0020] Beneficial effect: It is possible to determine whether the current software version of each controller on the vehicle to be tested is consistent with the baseline software version and whether the current major version number of the vehicle is consistent with the baseline major version number of the vehicle, thereby realizing vehicle software version consistency detection and obtaining the test results to facilitate subsequent software version alignment.

[0021] In an optional implementation, based on the detection result, a version consistency alignment task is formulated and sent to the vehicle end, including:

[0022] Based on the detection results corresponding to the vehicles to be detected, determine the first target vehicle with misaligned controller software versions and / or the second target vehicle with misaligned vehicle major version numbers;

[0023] Formulate a first alignment task based on the baseline version information of each vehicle model, wherein the task scope of the first alignment task is the first target vehicle, and the task type of the first alignment task is controller software version alignment;

[0024] And / or, formulating a second alignment task based on the baseline version information of each vehicle model, wherein the task scope of the second alignment task is the second target vehicle, and the task type of the second alignment task is the whole vehicle major version number alignment;

[0025] According to the first alignment task and / or the second alignment task, a version consistency alignment task is obtained and sent to the vehicle side, so that the vehicle side performs version consistency alignment on the corresponding vehicle according to the task type and task scope of the version consistency alignment task.

[0026] Beneficial effect: Vehicles that fail the consistency test are divided into first target vehicles with misaligned controller software versions and / or second target vehicles with misaligned vehicle major version numbers, and corresponding alignment tasks are formulated and sent to the vehicle side, so that the vehicle side can align the versions of the corresponding vehicles according to the task type and task scope of the alignment task, thereby achieving controller software version alignment and vehicle major version alignment of multiple vehicles.

[0027] In an optional embodiment, the method further includes:

[0028] Receive the execution status and results of the vehicle-side version consistency alignment task sent by the vehicle-side, and send the execution status and results to the terminal device.

[0029] Beneficial effect: The execution status and results of the vehicle-side version consistency alignment task are sent to the terminal device, which is convenient for users to view and improves the user experience.

[0030] In a second aspect, the present invention provides a vehicle software version alignment method, which is applied to a vehicle side, and the method includes:

[0031] Send the controller version information to the cloud, so that after receiving the version consistency detection instruction and the vehicle information to be detected sent by the terminal device, the cloud performs version consistency detection on the vehicle to be detected based on the baseline version information of each vehicle model, the controller version information and the vehicle information to be detected, obtains the detection result and sends it to the terminal device;

[0032] Receive the version consistency alignment task sent by the cloud; wherein the version consistency alignment task is formulated by the cloud based on the test results and the baseline version information of each vehicle model after receiving the version consistency alignment instruction sent by the terminal device based on the test results;

[0033] Perform version consistency alignment tasks and align software versions for corresponding vehicles.

[0034] Beneficial effects: The cloud is used to obtain the baseline version information of each vehicle model and the controller version information of the vehicle end, so that after receiving the version consistency detection instruction of the terminal device and the vehicle information to be detected, the cloud performs version consistency detection on the vehicle to be detected, and identifies the vehicle that does not correspond to the baseline version information of each vehicle model. Afterwards, after receiving the version consistency alignment instruction of the terminal device, the cloud formulates a version consistency alignment task and sends it to the corresponding vehicle on the vehicle end, so that the corresponding vehicle performs software version alignment, achieves consistency of software versions on different vehicles of the same model, and thus reduces the difficulty of vehicle software version management.

[0035] In an optional implementation, the baseline version information includes the baseline major version number of the vehicle and the baseline software version of each controller; the controller version information includes the software version information of the vehicle, and the software version information includes the current major version number of the vehicle and the current software version of each controller; executing the version consistency alignment task to align the software version of the corresponding vehicle includes:

[0036] According to the version consistency alignment task, a first alignment task and / or a second alignment task is obtained;

[0037] Identify the first alignment task, determine the first target vehicle whose controller software version is not aligned, control the first target vehicle to download a software package corresponding to the baseline software version of each controller from the cloud, and control the first target vehicle to flash the controller based on the software package to update the current software version of each controller;

[0038] And / or, the second alignment task is identified, a second target vehicle whose vehicle major version number is not aligned is determined, and the second target vehicle is controlled to update the current major version number of the vehicle to the baseline major version number of the vehicle.

[0039] Beneficial effect: The vehicle side performs version alignment for the corresponding vehicles according to the task type and task scope of the alignment task, thereby achieving controller software version alignment for multiple vehicles and overall vehicle version alignment.

[0040] In an optional implementation, before controlling the first target vehicle to flash the controller based on the software package, the method further includes:

[0041] The first target vehicle is controlled to detect whether the whole vehicle installation condition meets the calibration installation condition corresponding to the software package. If the whole vehicle installation condition meets the calibration installation condition, the step of controlling the first target vehicle to flash the controller based on the software package is executed.

[0042] Beneficial effect: Before flashing the controller based on the software package, the safety of software installation is improved by detecting whether the installation conditions of the entire vehicle meet the calibration installation conditions corresponding to the software package.

[0043] In an optional embodiment, the method further includes:

[0044] Feedback the execution status and results of the version consistency alignment task to the cloud, so that the cloud can send the execution status and results to the terminal device.

[0045] Beneficial effects: Task progress and results are reported to the cloud in real time so that the cloud can send them to the terminal device for users to view, improving user experience.

[0046] In a third aspect, the present invention provides a vehicle software version alignment system, including: a cloud and a vehicle;

[0047] The vehicle sends the controller version information to the cloud;

[0048] In the cloud, the baseline version information of each vehicle model is obtained, and the controller version information sent by the vehicle end is received; after receiving the version consistency detection instruction sent by the terminal device and the vehicle information to be detected, based on the baseline version information of each vehicle model, the controller version information and the vehicle information to be detected, the version consistency detection is performed on the vehicle to be detected, and the detection results are obtained and sent to the terminal device; after receiving the version consistency alignment instruction sent by the terminal device based on the detection results, the version consistency alignment task is formulated based on the detection results and sent to the vehicle end;

[0049] On the vehicle side, receive the version consistency alignment task sent by the cloud, execute the version consistency alignment task, and align the software version of the corresponding vehicle.

[0050] In a fourth aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the vehicle software version alignment method of the first aspect or any corresponding embodiment thereof by executing the computer instructions, or executes the vehicle software version alignment method of the second aspect or any corresponding embodiment thereof.

[0051] In a fifth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the vehicle software version alignment method of the first aspect or any corresponding embodiment thereof, or to execute the vehicle software version alignment method of the second aspect or any corresponding embodiment thereof.

[0052] In a sixth aspect, the present invention provides a computer program product, comprising computer instructions, wherein the computer instructions are used to enable a computer to execute the vehicle software version alignment method of the above-mentioned first aspect or any corresponding embodiment thereof, or to execute the vehicle software version alignment method of the above-mentioned second aspect or any corresponding embodiment thereof.

[0053] The beneficial effects of the present invention are:

[0054] The cloud is used to obtain the baseline version information of each vehicle model and the controller version information of the vehicle side, so that after receiving the version consistency detection instruction of the terminal device and the vehicle information to be detected, the cloud can perform version consistency detection on the vehicle to be detected and identify the vehicle that does not correspond to the baseline version information of each vehicle model. After that, after receiving the version consistency alignment instruction of the terminal device, the cloud formulates the version consistency alignment task and sends it to the corresponding vehicle on the vehicle side, so that the corresponding vehicle can align the software version and achieve the consistency of the software version on different vehicles of the same model, thereby reducing the difficulty of vehicle software version management. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0056] Figure 1 is a structural block diagram of a vehicle software version alignment system according to an embodiment of the present invention;

[0057] Figure 2 is a schematic diagram of a vehicle software version consistency detection system according to an embodiment of the present invention;

[0058] Figure 3 is a module schematic diagram of a consistency detection system according to an embodiment of the present invention;

[0059] Figure 4 is a schematic diagram of a vehicle software version consistency alignment system according to an embodiment of the present invention;

[0060] Figure 5 is a module schematic diagram of a consistency alignment system according to an embodiment of the present invention;

[0061] Figure 6 is an interactive flow chart of a vehicle software version alignment system according to an embodiment of the present invention;

[0062] Figure 7 is an interaction flow chart of another vehicle software version alignment system according to an embodiment of the present invention;

[0063] Figure 8 is a schematic diagram of a vehicle software version consistency detection method according to an embodiment of the present invention;

[0064] Fig. 9is a schematic diagram of a process of version consistency comparison according to an embodiment of the present invention;

[0065] Fig.10 is a schematic diagram of a version consistency comparison rule according to an embodiment of the present invention;

[0066] Fig.11 is a schematic diagram of a vehicle software version consistency alignment method according to an embodiment of the present invention;

[0067] Fig.12 is a schematic diagram of controller software version alignment according to an embodiment of the present invention;

[0068] Fig.13 is a schematic diagram of aligning a major version number of a whole vehicle according to an embodiment of the present invention;

[0069] Fig.14 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0070] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0071] With the rapid development of intelligent connected car technology, in order to meet users' needs for various new functions, vehicles can directly iterate and update the vehicle software system through OTA technology without going to the service center. This greatly improves service efficiency and brings convenience to users.

[0072] Generally speaking, the software versions of vehicles produced in the same batch are not completely unified. This may be caused by the following factors: 1) Vehicle software development is a dynamic process. The development of new functions, improvements to existing functions, and security updates are continuously carried out during the vehicle production process. In other words, some vehicles are produced after the new version of the software is developed and tested, while other vehicles are produced based on the old version of the software. 2) Customers can customize software application requirements and vehicle configurations, resulting in differences in software versions from production line vehicles. 3) The complex vehicle production and logistics process results in the failure to update the software of some vehicles to the latest version in a timely manner.

[0073] In order to standardize the management of vehicle software upgrades, car companies have set corresponding controller software version numbers for different software versions of each vehicle controller, and the software version set of each controller corresponds to a major version number of the entire vehicle. It is understandable that different software versions of the controller have different functional implementations, and there may be compatibility issues between different software versions. When there are too many software versions of the same controller of a certain model on the market, the management of vehicle software upgrades on the market by car companies will become chaotic. This requires car companies to consider the compatibility of different versions when pushing OTA upgrades, which increases the complexity of OTA upgrades. If the OTA upgrade plan is not well considered, it may increase the failure rate of vehicle OTA upgrades.

[0074] In addition, before the vehicle leaves the factory, the manufacturer does not know which major vehicle version the vehicle will be integrated into, and after the vehicle is off the factory line, a certain controller may be flashed separately, which will cause the software version set of each controller to be inconsistent with the major vehicle version number. Taking all the above factors into consideration, manufacturers usually set the major vehicle version number of the vehicle when it leaves the factory to a certain initial value, but in fact the software versions of each controller have been switched at the factory. Only after an OTA iterative upgrade will the initial major vehicle version number be updated to the correct major vehicle version number. If the model has no OTA iteration requirements, the major vehicle version number displayed after the vehicle is sold will always be the initial value, which will cause users to be unclear about the actual software version of their vehicles, doubt the reliability of the vehicle software information and the authenticity of the software version, and thus trigger market complaints.

[0075] Therefore, it is of great significance to conduct PDI inspection on vehicles. The so-called PDI inspection refers to the comprehensive inspection and testing of new vehicles by professional technicians before they are delivered to customers to ensure that the vehicle performance and safety meet the manufacturer's standards. After completing the PDI inspection, the vehicle can be legally delivered to the customer. This process is crucial to ensuring the quality of new cars, customer satisfaction and compliance with relevant regulations.

[0076] Based on the existing software version of the vehicle, the relevant technology determines whether the vehicle is compatible with the major hardware version associated with the software baseline version through the vehicle hardware information, and formulates an effective upgrade strategy. The appropriate upgradeable software version is then pushed to the vehicle through the vehicle's software information. This solves the problem of version incompatibility when manual judgment of the vehicle's upgradeable version is prone to occur when there are too many software versions of a controller of the same model on the market, thereby reducing the cost of manual judgment and improving the stability of OTA operation activities.

[0077] However, the above vehicle software upgrade method only solves the compatibility problem when the vehicle software is upgraded, and cannot guarantee the consistency of software versions for different vehicles in the same series after the upgrade. It does not take into account how to directly align the software versions on different vehicles online to maintain the consistency of software versions when there are too many software versions of the same controller of a certain model. In addition, the above method does not take into account how to correct the vehicle major version number information displayed by the vehicle online when the vehicle major version number and the software version set of each controller do not match and cannot be updated through the normal OTA upgrade task, and align the vehicle major version number and the controller software version set to maintain consistency.

[0078] In addition, the relevant PDI detection technology does not involve the detection of the vehicle software version information, nor does it involve how to use online methods to correct the vehicle software version information after PDI detection.

[0079] Therefore, an embodiment of the present invention provides a vehicle software version alignment solution. When performing PDI detection before the vehicle is sold, the software version of the entire vehicle is checked and aligned for consistency, ensuring that the software versions of different vehicles in the same series and batch are unified, thereby reducing software differences in the same model on the market and reducing the difficulty of vehicle software version management for vehicle companies; and ensuring the consistency of the vehicle's major version number and controller software version set, to ensure the accuracy and authenticity of the software information displayed on the vehicle.

[0080] According to an embodiment of the present invention, a vehicle software version alignment system is provided. Figure 1 As shown, the system mainly includes a cloud end 101 and a vehicle end 102, wherein the cloud end 101 and the vehicle end 102 are specifically used for:

[0081] The vehicle end 102 sends the controller version information to the cloud.

[0082] The cloud 101 obtains the baseline version information of each vehicle model and receives the controller version information sent by the vehicle end 102; after receiving the version consistency detection instruction and the vehicle information to be detected sent by the terminal device 103, based on the baseline version information of each vehicle model, the controller version information and the vehicle information to be detected, the version consistency detection is performed on the vehicle to be detected, and the detection result is obtained and sent to the terminal device; after receiving the version consistency alignment instruction sent by the terminal device 103 based on the detection result, a version consistency alignment task is formulated based on the detection result and sent to the vehicle end 102.

[0083] The vehicle end 102 receives the version consistency alignment task sent by the cloud end 101, executes the version consistency alignment task, and aligns the software version of the corresponding vehicle.

[0084] Exemplarily, the cloud 101 may be a cloud server; the vehicle side 102 may include vehicle-mounted information terminals or body domain controllers of multiple vehicles, each vehicle may communicate with the cloud 101 through its own vehicle-mounted information terminal or body domain controller and receive a series of instructions or information from the cloud 101; the terminal device 103 may be a mobile phone or a PC device.

[0085] The vehicle software version alignment system provided by the embodiment of the present invention uses the cloud 101 to obtain the baseline version information of each vehicle model and the controller version information of the vehicle end 102, so that after receiving the version consistency detection instruction and the vehicle information to be detected from the terminal device 103, the cloud 101 performs version consistency detection on the vehicle to be detected, and identifies the vehicle that does not correspond to the baseline version information of each vehicle model. Afterwards, after receiving the version consistency alignment instruction from the terminal device 103, the cloud 101 formulates a version consistency alignment task and sends it to the corresponding vehicle on the vehicle end 102, so that the corresponding vehicle performs software version alignment, achieves consistency of software versions on different vehicles of the same model, and reduces the difficulty of vehicle software version management.

[0086] In some optional embodiments, such as Figure 2 As shown, an embodiment of the present invention provides a vehicle software version consistency detection system, which mainly includes a detection operation module, a software information collection module and a software information detection module, wherein the detection operation module can be deployed in Figure 1 The terminal device 103 shown in FIG. 104 may be deployed in a software information collection module such as Figure 1 The vehicle end 102 shown in FIG. 104 , the software information detection module can be deployed in Figure 1 Cloud 101 is shown.

[0087] Furthermore, if Figure 3 As shown, Figure 2 The detection operation module shown mainly includes a detection task initiation submodule and a detection task monitoring submodule. When performing PDI detection on a vehicle, the relevant detection personnel can send a version consistency detection instruction to the software information detection module through the detection task initiation submodule, and the detection task initiation submodule will pass the vehicle model information to be detected and the specific vehicle identification code (VIN) information to the software information detection module. Afterwards, when the software information detection module receives the version consistency detection instruction and starts to execute the detection process, the detection task monitoring submodule will automatically query the software information detection module for the execution status of the detection task and the final detection result. After the detection is completed, the relevant detection personnel can view the detection results of the version consistency detection through the detection task monitoring submodule.

[0088] Further, see again Figure 3 , Figure 2The software information collection module shown mainly includes a controller, a controller information collection submodule and an information upload submodule. Each time the vehicle is started, the information of each controller of the vehicle will be collected through the controller information collection submodule to generate the controller version information. The collected information includes the major version number of the vehicle and the hardware part number, hardware version number, software part number and software version number of each controller. The information upload submodule will cyclically query the controller information collection submodule whether the collection of controller information is completed. When the controller information collection submodule completes the collection of controller information, the information upload submodule can automatically report the major version number of the vehicle and the hardware part number, hardware version number, software part number and software version number of each controller to the software information detection module.

[0089] Further, see again Figure 3 , Figure 2 The software information detection module shown is responsible for the execution of the vehicle software version consistency detection function, which mainly includes the information management submodule, information interaction submodule, detection execution submodule and data statistics submodule. Relevant maintenance personnel can access the information management submodule in the software information detection module through the network, and configure the baseline version information of each vehicle model through the information management submodule, including the information of each controller, the baseline software version of each controller and the vehicle baseline major version number.

[0090] In addition, the software information detection module can automatically receive the controller version information reported by the software information collection module, automatically receive the version consistency detection instruction initiated by the detection operation module, and the model information and VIN information of the vehicle to be detected through the information interaction submodule; after the detection is completed, the information interaction submodule can automatically feedback the execution status and execution results of the detection task to the detection operation module. When the information interaction submodule receives the version consistency detection instruction, it will notify the detection execution submodule, and the detection execution submodule will automatically initiate the version consistency detection task process. When the detection execution submodule completes the detection, the data statistics submodule will automatically store the detection results and related statistical data, and the relevant maintenance personnel can view the detection results and related statistical data of the version consistency detection through the data statistics submodule.

[0091] This embodiment uses the above-mentioned vehicle software version consistency detection system to detect whether the software versions of each controller on the vehicle side are consistent with the software baseline version maintained in the software information detection module, and can detect whether the major version number of the vehicle on the vehicle side is consistent with the major version number of the baseline, and obtain detection results to facilitate subsequent alignment.

[0092] In some optional embodiments, such as Figure 4 As shown, an embodiment of the present invention provides a vehicle software version consistency alignment system, which mainly includes a software update module, a task management module and an alignment operation module, wherein the alignment operation module can be deployed in Figure 1 The terminal device 103 shown in FIG. 104 may be deployed in a software update module such as Figure 1 As shown in the vehicle side 102, the task management module can be deployed in Figure 1 Cloud 101 is shown.

[0093] Furthermore, if Figure 5 As shown, the alignment operation module mainly includes the alignment task initiation submodule and the alignment task monitoring submodule. Relevant inspection personnel can send version consistency alignment instructions to the task management module through the alignment task initiation submodule. It should be noted that the alignment operation module can only initiate the version consistency alignment process after the version consistency detection process is completed and the detection result information is received. Its scope of action is all vehicles that have not passed the version consistency detection this time. When the version consistency alignment task starts to execute, the alignment task monitoring submodule will automatically query the task management module for the execution status and results of the alignment task. Relevant inspection personnel can view the execution status and results of the task through this module.

[0094] Further, see again Figure 5 The task management module mainly includes the information management submodule, the information interaction submodule, the task activation submodule and the task monitoring submodule. Relevant maintenance personnel can configure the alignment task information of each vehicle model through the information management submodule. It should be noted that the alignment task information needs to configure and store the basic information and strategy information of the controllers in each vehicle model (when the version consistency alignment task is issued, this information will be issued to the software update module); it is necessary to select the baseline major version number of each vehicle model and the baseline software version of each controller, and upload the software package corresponding to each software version. Among them, the "task status" of the task defaults to "disabled", and the "task type" and "task scope" information are empty by default.

[0095] In addition, the information interaction submodule can automatically receive the version consistency alignment instruction initiated by the alignment operation module. After the task is enabled, the information interaction submodule automatically sends the version consistency alignment task to the software update module. When the information interaction submodule receives the version consistency alignment instruction, it will notify the task enabling submodule, which will automatically enable the version consistency alignment task, configure the task scope, and divide the task type. When executing the task, the task monitoring submodule will receive and store the task execution progress and execution results reported by the software update module; when receiving the task query instruction sent by the alignment operation module, it will feedback the task execution status and result information to the alignment operation module.

[0096] Further, see again Figure 5, the software update module mainly includes a task execution submodule, a download / deployment submodule, an installation control submodule and an information reporting submodule. When the vehicle is in the startup state, the task execution submodule can receive the version consistency alignment task issued by the task management module. After receiving the task, the task process can be automatically initiated, and the execution instruction can be automatically sent to the download / deployment submodule and the installation control submodule according to the task information. After receiving the instruction from the task execution submodule, the download / deployment submodule will first initiate the download process to download the software package of each controller to the storage space of the submodule, and then initiate the deployment process to deploy the software package to the storage path of the installation control submodule. Before flashing the controller, the installation control submodule will first detect the installation conditions of the whole vehicle. After the detection passes, the installation control process will be initiated and the flashing steps will be executed. During the flashing execution process, the installation control submodule will monitor the installation status and progress of each controller. When the software update module is executing the version consistency alignment task, it will report the task execution progress and execution results to the task management module through the information reporting submodule.

[0097] This embodiment uses the above-mentioned vehicle software version consistency alignment system to achieve consistency alignment between the software versions of each controller on the vehicle side and the software baseline version in the task management module, and can also achieve consistency alignment between the vehicle-side major version number and the baseline major version number.

[0098] According to an embodiment of the present invention, an embodiment of a vehicle software version alignment method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0099] In this embodiment, a vehicle software version alignment method is provided. The vehicle software version alignment method can be used as follows: Figure 1 The cloud 101 and the vehicle 102 are shown. Figure 6 1 is a schematic diagram of the interaction process of the vehicle software version alignment system according to an embodiment of the present invention, wherein the cloud 101 is used to execute steps S101 to S103, and the vehicle 102 is used to execute steps S201 to S202. The specific interaction process between the cloud 101 and the vehicle 102 is as follows:

[0100] Step S201, sending controller version information to the cloud.

[0101] Specifically, the controller version information includes the vehicle's software version information, which mainly includes the vehicle's major version number and each controller's hardware part number, hardware version number, software part number, and software version number. Each time the vehicle is started, the controller version information is automatically collected and uploaded to the cloud.

[0102] Step S101, obtain the baseline version information of each vehicle model, and receive the controller version information sent by the vehicle end.

[0103] Specifically, users can configure the baseline version information of each vehicle model through the terminal device. The baseline version information includes the baseline major version number of the vehicle, the information of each controller, and the baseline software version of each controller. After the configuration is completed, the user can send the baseline version information of each vehicle model to the cloud through the terminal device. The cloud will automatically update and store the latest controller version information on the vehicle side, and save the latest software version information of the vehicle, including the current major version number of the vehicle and the current software version of each controller.

[0104] Step S102, after receiving the version consistency detection instruction and the vehicle information to be detected sent by the terminal device, based on the baseline version information of each vehicle model, the controller version information and the vehicle information to be detected, the version consistency detection is performed on the vehicle to be detected, and the detection result is obtained and sent to the terminal device.

[0105] Specifically, when a vehicle requires PDI inspection, the relevant inspection personnel can initiate and send a version consistency inspection instruction to the cloud through the terminal device. At the same time, the relevant inspection personnel need to send the vehicle information to be inspected to the cloud through the terminal device, where the vehicle information to be inspected includes the vehicle model information and VIN (identification code) information of all vehicles to be inspected.

[0106] Furthermore, after receiving the version consistency detection instruction, the cloud will automatically compare the latest software version information reported by the vehicle to be tested (that is, the current major version number of the vehicle and the current software version of each controller) with the vehicle baseline major version number and the baseline software version information of each controller corresponding to the vehicle model to be tested in accordance with the software version consistency comparison rules, obtain the detection results and send them to the terminal device.

[0107] Step S103, after receiving the version consistency alignment instruction sent by the terminal device based on the detection result, a version consistency alignment task is formulated based on the detection result and sent to the vehicle end.

[0108] Specifically, after completing the version consistency test, the relevant testers can initiate and send a version consistency alignment instruction to the cloud through the terminal device. The cloud will configure the task status, task scope, task type and other parameters of the version consistency alignment task based on the VIN information and vehicle model information of the vehicle that failed the version consistency test, and send the version consistency alignment task to the corresponding vehicle on the vehicle side for execution.

[0109] Step S202: receiving a version consistency alignment task sent by the cloud.

[0110] Step S203, executing the version consistency alignment task, aligning the software versions of the corresponding vehicles.

[0111] Specifically, after the vehicle receives the version consistency alignment task, it will align the software version of the corresponding vehicle based on its task status, task scope, task type and other parameters.

[0112] The vehicle software version alignment method provided in this embodiment uses the cloud to obtain the baseline version information of each vehicle model and the controller version information of the vehicle end, so that after receiving the version consistency detection instruction of the terminal device and the vehicle information to be detected, the cloud performs version consistency detection on the vehicle to be detected, and identifies the vehicle that does not correspond to the baseline version information of each vehicle model. Afterwards, after receiving the version consistency alignment instruction of the terminal device, the cloud formulates a version consistency alignment task and sends it to the corresponding vehicle on the vehicle end, so that the corresponding vehicle performs software version alignment, achieves the consistency of software versions on different vehicles of the same model, and thus reduces the difficulty of vehicle software version management.

[0113] In this embodiment, a vehicle software version alignment method is provided. The vehicle software version alignment method can be used as follows: Figure 1 The cloud 101 and the vehicle 102 are shown. Figure 7 1 is a schematic diagram of the interaction process of the vehicle software version alignment system according to an embodiment of the present invention, wherein the cloud 101 is used to execute steps S301 to S309, and the vehicle end 102 is used to execute steps S401 to S406. The specific interaction process between the cloud 101 and the vehicle end 102 is as follows:

[0114] Step S401: Send controller version information to the cloud. For details, see Figure 6 Step S201 of the illustrated embodiment will not be described in detail here.

[0115] Step S301, obtain the baseline version information of each vehicle model, and receive the controller version information sent by the vehicle end. For details, please refer to Figure 6 Step S101 of the illustrated embodiment will not be described in detail here.

[0116] Step S302, after receiving the version consistency detection instruction and the vehicle information to be detected sent by the terminal device, the model information and identification code information of each vehicle to be detected are obtained according to the vehicle information to be detected.

[0117] Specifically, the vehicle model information and VIN information of each vehicle to be detected are obtained from the vehicle information to be detected.

[0118] Step S303, based on the vehicle model information and the identification code information, query the controller version information and the baseline version information of each vehicle model to obtain the software version information and baseline version information of each vehicle to be detected.

[0119] Specifically, according to the model of the vehicle to be tested, the baseline version information of each model can be queried to obtain the baseline version information of each vehicle to be tested, including the baseline major version number of the whole vehicle and the baseline software version of each controller.

[0120] Specifically, the controller version information can be queried according to the VIN code of the vehicle to be tested to obtain the software version information of each vehicle to be tested, including the current major version number of the vehicle and the current software version of each controller.

[0121] Step S304: for each vehicle to be detected, the baseline version information and the software version information corresponding to the current vehicle to be detected are compared to obtain a detection result corresponding to the current vehicle to be detected.

[0122] In some optional implementations, it is determined whether the current software version of each controller on the current vehicle to be detected is consistent with the baseline software version and whether the current major version number of the entire vehicle to be detected is consistent with the baseline major version number of the entire vehicle.

[0123] Furthermore, if the current software version of each controller on the current vehicle to be tested is consistent with the baseline software version, and the current major version number of the entire vehicle of the current vehicle to be tested is consistent with the baseline major version number of the entire vehicle, then the test result of the current vehicle to be tested is determined to be that both the controller software version and the vehicle major version number are aligned.

[0124] If the current software version of each controller on the current vehicle to be tested is inconsistent with the baseline software version, and / or the current major version number of the entire vehicle to be tested is inconsistent with the baseline major version number of the entire vehicle, then the test result of the current vehicle to be tested is determined to be that the controller software version and / or the vehicle major version number are not aligned.

[0125] This embodiment determines whether the current software version of each controller on the vehicle to be tested is consistent with the baseline software version and whether the current major version number of the entire vehicle is consistent with the baseline major version number of the entire vehicle, thereby realizing vehicle software version consistency detection and obtaining the detection results to facilitate subsequent software version alignment.

[0126] Step S305, sending the detection result of each vehicle to be detected to the terminal device.

[0127] In an embodiment of the present invention, a query is performed based on the vehicle model information and identification code information of the vehicle to be tested to obtain the software version information and baseline version information of each vehicle to be tested. The software version information and baseline version information of each vehicle to be tested are then compared to obtain the test result of each vehicle to be tested, thereby realizing software version consistency detection of different vehicles of the same model.

[0128] Step S306, after receiving the version consistency alignment instruction sent by the terminal device based on the test results, determine the first target vehicle with misaligned controller software versions and / or the second target vehicle with misaligned vehicle major version numbers based on the test results corresponding to each vehicle to be tested.

[0129] Specifically, users can send version consistency alignment instructions to the cloud through terminal devices, and upload vehicle information that fails the version consistency test.

[0130] Specifically, the cloud identifies the test results of each vehicle to be tested, and divides the vehicles that fail the consistency test into first target vehicles and / or second target vehicles. The controller software version of the first target vehicle is not aligned, and the whole vehicle major version number of the second target vehicle is not aligned.

[0131] Step S307: formulating a first alignment task based on the baseline version information of each vehicle model, and / or formulating a second alignment task based on the baseline version information of each vehicle model.

[0132] Specifically, the task scope of the first alignment task is the first target vehicle, the task type of the first alignment task is controller software version alignment, the task scope of the second alignment task is the second target vehicle, and the task type of the second alignment task is vehicle major version number alignment.

[0133] In some optional embodiments, based on the version consistency test results, for vehicles whose current software versions of each controller on the vehicle side are inconsistent with the baseline software version, the task type is set to controller software version alignment; for vehicles whose software versions of each controller on the vehicle side are consistent with the baseline software version, but whose current major version number of the entire vehicle on the vehicle side is inconsistent with the baseline major version number, the task type is set to vehicle major version number alignment.

[0134] Step S308: According to the first alignment task and / or the second alignment task, a version consistency alignment task is obtained and sent to the vehicle end.

[0135] Specifically, a version consistency alignment task is formulated, including a first alignment task and / or a second alignment task.

[0136] In an embodiment of the present invention, vehicles that fail the consistency test are divided into first target vehicles with misaligned controller software versions and / or second target vehicles with misaligned whole vehicle major version numbers, and corresponding alignment tasks are formulated and sent to the vehicle side, so that the vehicle side performs version alignment on the corresponding vehicles according to the task type and task scope of the alignment task, thereby achieving controller software version alignment and whole vehicle major version alignment of multiple vehicles.

[0137] Step S402: Receive the version consistency alignment task sent by the cloud. Figure 6Step S202 of the illustrated embodiment will not be described in detail here.

[0138] Step S403: obtaining a first alignment task and / or a second alignment task according to the version consistency alignment task.

[0139] Specifically, the version consistency alignment task is identified and parsed to obtain the first alignment task and / or the second alignment task.

[0140] Step S404, identifying the first alignment task, determining the first target vehicle whose controller software version is not aligned, controlling the first target vehicle to download a software package corresponding to the baseline software version of each controller from the cloud, and controlling the first target vehicle to flash the controller based on the software package to update the current software version of each controller.

[0141] Specifically, when the vehicle side identifies the first alignment task of controller software version alignment as the task type, it controls the first target vehicle to automatically download and deploy the software packages of each controller, then detects the vehicle installation conditions and initiates the flash installation process of each controller. When the task type is controller software version alignment, the software package will be downloaded, deployed and installed, and the vehicle major version number and each controller software version will be updated to the baseline major version number and baseline software version.

[0142] In some optional embodiments, before controlling the first target vehicle to flash the controller based on the software package, the first target vehicle is controlled to detect whether the whole vehicle installation conditions meet the calibration installation conditions corresponding to the software package. If the whole vehicle installation conditions meet the calibration installation conditions, the step of controlling the first target vehicle to flash the controller based on the software package is executed to improve the security of software installation.

[0143] Step S405, identifying the second alignment task, determining the second target vehicle whose vehicle major version number is not aligned, and controlling the second target vehicle to update the current major version number of the vehicle to the baseline major version number of the vehicle.

[0144] Specifically, when the task type is to align the major version number of the entire vehicle, the current major version number of the entire vehicle can be directly updated to the baseline major version number, keeping the software version of each controller of the current vehicle unchanged.

[0145] In an embodiment of the present invention, the vehicle side performs version alignment on the corresponding vehicles according to the task type and task scope of the alignment task, thereby realizing the controller software version alignment of multiple vehicles and the overall version alignment of the entire vehicle.

[0146] Step S406: Feedback the execution status and results of the version consistency alignment task to the cloud.

[0147] Specifically, when the task is being executed, the vehicle will report the task progress and results to the cloud in real time.

[0148] Step S309, receiving the execution status and execution result of the vehicle-side version consistency alignment task sent by the vehicle-side, and sending the execution status and execution result to the terminal device.

[0149] Specifically, the cloud receives and stores the task execution progress and results on the vehicle side, and also sends them to the terminal device for the user to view.

[0150] The vehicle software version alignment method provided in this embodiment detects and aligns the consistency of the controller software versions of different vehicles, thereby achieving consistency in the controller software versions on the same vehicle series, the same batch, and different vehicles, and at the same time achieving consistency between the vehicle major version number displayed on the vehicle and the actual vehicle major version number of each controller software version set.

[0151] Based on the vehicle whole vehicle software version consistency detection system and vehicle whole vehicle software version consistency alignment system in the above-mentioned embodiments, the vehicle software version alignment method of the present invention is described in detail in combination with a specific application example.

[0152] like Figure 8 As shown, the vehicle software version consistency detection method includes the following steps:

[0153] In step a1, the relevant maintenance personnel configure and maintain the baseline version information of each vehicle model through the information management submodule of the software information detection module. The baseline version information includes the baseline major version number, the information of each controller, and the baseline software version of each controller.

[0154] Step a2: After each vehicle startup, the software information collection module will automatically collect information about each controller of the vehicle through the controller information collection submodule, including the vehicle major version number and the hardware part number, hardware version number, software part number and software version number of each controller. After the information collection is completed, the controller information collection submodule will notify the information upload submodule, and the information upload submodule will automatically report the controller information to the software information detection module.

[0155] Step a3: After the software information detection module receives the information reported by the software information collection module, the information management submodule automatically updates and stores the latest major version number of the vehicle and the latest software version information of each controller.

[0156] Step a4: When a vehicle needs to be inspected, the relevant inspectors can use the inspection operation module to send a version consistency inspection instruction to the software information inspection module through the inspection task initiation submodule. The inspectors need to upload the vehicle model information and VIN code data of all vehicles to be inspected. This submodule will pass the vehicle model to be inspected and the specific vehicle VIN information to the software information inspection module.

[0157] Step a5: After receiving the detection instruction through the information interaction submodule, the software information detection module will notify the detection execution submodule, which will automatically compare the latest vehicle major version number and controller software version information reported by the detected vehicle with the baseline major version number and controller baseline software version information of the vehicle model maintained by the information management submodule according to the software version consistency comparison rules.

[0158] Specifically, Fig. 9 As shown, the detection execution submodule queries the vehicle model from the information management submodule according to the VIN code, and obtains the baseline version information of the vehicle model, including the hardware part number, software part number, baseline software version, and baseline major version number of each controller; the detection execution submodule queries the current software version information of the vehicle according to the VIN code, including the hardware part number, software part number, vehicle-side software version, and vehicle major version number of each controller. Then, the baseline version information of the vehicle model and the current software version information of the vehicle are compared according to the rules, including the comparison of the vehicle major version number and the baseline major version number, and the comparison of the vehicle-side software version of each controller and the baseline software version.

[0159] For example, Fig.10 As shown, the rules for version consistency comparison are:

[0160] 1) When the baseline major version number of the vehicle model and the baseline software version of each controller are completely consistent with the current vehicle major version number and the software version of each controller reported by the software information collection module, the test result is recorded as "passed";

[0161] 2) When the baseline major version number of the vehicle model is consistent with the current vehicle major version number reported by the software information collection module, but the baseline software version of each controller is different from the current software version, the test result is recorded as "failed";

[0162] 3) When the baseline major version number of the vehicle model is different from the current vehicle major version number reported by the software information collection module, but the baseline software version of each controller is exactly the same as the current software version, the test result is recorded as "failed";

[0163] 4) When the baseline major version number of the vehicle model is different from the current vehicle major version number reported by the software information collection module, and the baseline software version of each controller is different from the current software version, the test result is recorded as "failed".

[0164] Step a6: After the detection execution submodule completes the consistency detection, it automatically stores the results and detailed information of this detection, and feeds back the consistency detection results and version details to the detection operation module through the information interaction submodule for result display.

[0165] like Fig.11 As shown, the vehicle software version consistency alignment method includes the following steps:

[0166] Step b1: Relevant maintenance personnel configure and maintain version consistency alignment task information through the information management submodule of the task management module. The task information includes the baseline major version number and the software version of each controller, task status, task scope, and task type.

[0167] It should be noted that when configuring the version consistency alignment task information in step b1, its "task status" defaults to "disabled", and the "task type" and "task scope" information default to empty.

[0168] Step b2: After the software version consistency test is completed, the relevant testers use the alignment operation module to send a version consistency alignment instruction to the task management module through the alignment task initiation submodule, and upload the VIN code data and vehicle model information of the vehicle that failed the version consistency test.

[0169] Step b3: After the task management module receives the version consistency alignment instruction sent by the alignment operation module, the task enabling submodule automatically configures the task status, task scope, and task type of the version consistency alignment task.

[0170] It should be noted that in step b3, when the task management module receives the alignment instruction sent by the alignment operation module, it will automatically set the "task status" of the version consistency alignment task to "enabled" through the task enabling submodule, and set the "task scope" to vehicles that "failed" the version consistency test according to the version consistency test data stored in the information management submodule.

[0171] Step b4: After the task is enabled, the task management module automatically sends the version consistency alignment task to the software update module through the information interaction submodule.

[0172] It should be noted that the "task type" of the version consistency alignment task sent by the task management module to the software update module in step b3 and step b4 includes "vehicle major version number alignment" and "controller software version alignment". According to the version consistency detection results, for vehicles whose vehicle-side controller software versions are inconsistent with the baseline software versions of each controller in the task management module, the "task type" is set to controller software version alignment; for vehicles whose vehicle-side controller software versions are consistent with the baseline software versions of each controller in the task management module, but the vehicle-side major version number is inconsistent with the baseline major version number, the "task type" is set to vehicle major version number alignment.

[0173] Step b5: When the vehicle is in the startup state, the software update module can receive the version consistency alignment task issued by the task management module through the task execution submodule, automatically identify its "task type" after receiving the task, and initiate the task process.

[0174] It should be noted that in step b5, the task execution submodule will identify the "task type" of the version consistency task. Fig.12 As shown, when the "Task Type" is "Controller Software Version Alignment", the task process will be initiated to the download / deployment submodule and the installation control submodule, and steps b6 and b7 will be executed to update the vehicle's major version number and each controller software version to the baseline major version number and baseline software version maintained in the task management module.

[0175] like Fig.13 As shown, when the "Task Type" is "Vehicle Major Version Number Alignment", the vehicle major version number of the vehicle can be directly updated to the baseline major version number maintained in the task management module through the task execution module, keeping the software versions of the current vehicle controllers unchanged.

[0176] Step b6: When the "Task Type" is "Controller Software Version Alignment", the software update module sends instructions to the download / deployment submodule through the task execution module. The download / deployment submodule automatically downloads the software package of each controller to the task management module and deploys the software package to the installation control submodule.

[0177] Step b7: When the "Task Type" is "Controller Software Version Alignment", after the download / deployment submodule completes the download and deployment of the software package, the software update module sends instructions to the installation control submodule through the task execution submodule. The installation control submodule will automatically start detecting the vehicle installation conditions and initiate the flash installation process of each controller.

[0178] Step b8: When the task is being executed, the software update module will report the task progress and results to the task management module through the information reporting submodule; the task management module receives and stores the task execution progress and results reported by the software update module; at the same time, the alignment operation module will query the task management module for the task progress and results.

[0179] This application example provides a method and system for consistency detection and alignment of different vehicle software versions, which can be applied to the PDI detection link before vehicle sales.

[0180] The present invention can detect and align the consistency of controller software versions of different vehicles, ensure the consistency of controller software versions on the same model, the same batch, and different vehicles, avoid the sale of vehicles of non-target versions, reduce software differences of the same model on the market, and alleviate the current situation where there are too many controller software versions of a certain model on the market, making it difficult for car companies to manage vehicle software versions.

[0181] The present invention can detect and align the consistency of the vehicle's major version number and the actual software version set of the controller, ensure that the vehicle's major version number and the controller software version set match, and avoid the vehicle displaying incorrect vehicle major version information; avoid the vehicle's inability to detect upgrade tasks normally, ensure the accuracy and authenticity of the vehicle's major version number information displayed by the vehicle, and improve the user experience.

[0182] The present invention provides the capability of online automatic detection and alignment for the consistency of vehicle software versions, thereby reducing the market action costs caused by inconsistent vehicle software versions.

[0183] The embodiment of the present invention also provides a computer device, see Fig.14 , Fig.14 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Fig.14 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Fig.14 A processor 10 is taken as an example.

[0184] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0185] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0186] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0187] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0188] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Fig.14 The example of connecting through bus is taken in the following.

[0189] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0190] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0191] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0192] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A vehicle software version alignment method, characterized in that: Applied to the cloud, the method includes: Obtain the baseline version information of each vehicle model and receive the controller version information sent by the vehicle end; After receiving the version consistency detection instruction and the vehicle information to be detected sent by the terminal device, based on the baseline version information of each vehicle model, the controller version information and the vehicle information to be detected, the version consistency detection is performed on the vehicle to be detected, and the detection result is obtained and sent to the terminal device; After receiving the version consistency alignment instruction sent by the terminal device based on the detection result, a version consistency alignment task is formulated based on the detection result and sent to the vehicle side, so that the vehicle side executes the version consistency alignment task and aligns the software version of the corresponding vehicle.

2. The method according to claim 1, characterized in that Based on the baseline version information of each vehicle model, the controller version information and the vehicle information to be detected, the version consistency detection is performed on the vehicle to be detected to obtain the detection result, including: According to the information of the vehicles to be detected, obtaining the vehicle model information and identification code information of each vehicle to be detected; Based on the vehicle model information and the identification code information, query the controller version information and the baseline version information of each vehicle model to obtain the software version information and the baseline version information of each vehicle to be detected; For each vehicle to be detected, the baseline version information and software version information corresponding to the current vehicle to be detected are compared to obtain a detection result corresponding to the current vehicle to be detected.

3. The method according to claim 2, characterized in that The baseline version information includes the baseline major version number of the vehicle and the baseline software version of each controller, and the software version information includes the current major version number of the vehicle and the current software version of each controller; The comparison of the baseline version information and the software version information corresponding to the current vehicle to be detected to obtain the detection result corresponding to the current vehicle to be detected includes: Determine whether the current software version of each controller on the current vehicle to be tested is consistent with the baseline software version and whether the current major version number of the entire vehicle to be tested is consistent with the baseline major version number of the entire vehicle; If the current software version of each controller on the current vehicle to be tested is consistent with the baseline software version, and the current major version number of the entire vehicle of the current vehicle to be tested is consistent with the major version number of the entire vehicle baseline, then the test result of the current vehicle to be tested is determined to be that both the controller software version and the vehicle major version number are aligned; If the current software version of each controller on the current vehicle to be tested is inconsistent with the baseline software version, and / or the current major version number of the entire vehicle to be tested is inconsistent with the baseline major version number of the entire vehicle, then the test result of the current vehicle to be tested is determined to be that the controller software version and / or the vehicle major version number are not aligned.

4. The method according to claim 3, characterized in that Based on the detection result, a version consistency alignment task is formulated and sent to the vehicle end, including: Based on the detection results corresponding to the vehicles to be detected, determine the first target vehicle with misaligned controller software versions and / or the second target vehicle with misaligned vehicle major version numbers; Formulate a first alignment task based on the baseline version information of each vehicle model, wherein the task scope of the first alignment task is the first target vehicle, and the task type of the first alignment task is controller software version alignment; And / or, formulating a second alignment task based on the baseline version information of each vehicle model, wherein the task scope of the second alignment task is the second target vehicle, and the task type of the second alignment task is the whole vehicle major version number alignment; According to the first alignment task and / or the second alignment task, a version consistency alignment task is obtained and sent to the vehicle end, so that the vehicle end performs version consistency alignment on the corresponding vehicle according to the task type and task scope of the version consistency alignment task.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: Receive the execution status and execution result of the vehicle-side version consistency alignment task sent by the vehicle-side, and send the execution status and execution result to the terminal device.

6. A vehicle software version alignment method, characterized in that: Applied to the vehicle side, the method includes: Send the controller version information to the cloud, so that after receiving the version consistency detection instruction and the vehicle information to be detected sent by the terminal device, the cloud performs version consistency detection on the vehicle to be detected based on the baseline version information of each vehicle model, the controller version information and the vehicle information to be detected, obtains the detection result and sends it to the terminal device; Receiving a version consistency alignment task sent by the cloud; wherein the version consistency alignment task is formulated by the cloud based on the detection result and the baseline version information of each vehicle model after receiving the version consistency alignment instruction sent by the terminal device based on the detection result; The version consistency alignment task is executed to align the software versions of the corresponding vehicles.

7. The method according to claim 6, characterized in that The baseline version information includes the baseline major version number of the whole vehicle and the baseline software version of each controller; the controller version information includes the software version information of the vehicle, and the software version information includes the current major version number of the whole vehicle and the current software version of each controller; The executing the version consistency alignment task to align the software versions of the corresponding vehicles includes: According to the version consistency alignment task, a first alignment task and / or a second alignment task is obtained; Identify the first alignment task, determine the first target vehicle whose controller software version is not aligned, control the first target vehicle to download a software package corresponding to the baseline software version of each controller from the cloud, and control the first target vehicle to flash the controller based on the software package to update the current software version of each controller; And / or, the second alignment task is identified, a second target vehicle whose vehicle major version number is not aligned is determined, and the second target vehicle is controlled to update the current major version number of the vehicle to the baseline major version number of the vehicle.

8. The method according to claim 7, characterized in that Before controlling the first target vehicle to flash the controller based on the software package, the method further includes: The first target vehicle is controlled to detect whether the whole vehicle installation condition meets the calibration installation condition corresponding to the software package. If the whole vehicle installation condition meets the calibration installation condition, the step of controlling the first target vehicle to flash the controller based on the software package is executed.

9. The method according to any one of claims 6 to 8, characterized in that: The method further comprises: Feedback the execution status and execution result of the version consistency alignment task to the cloud, so that the cloud sends the execution status and execution result to the terminal device.

10. A vehicle software version alignment system, characterized in that: include: Cloud and vehicle side; The vehicle sends the controller version information to the cloud; The cloud obtains the baseline version information of each vehicle model and receives the controller version information sent by the vehicle end; after receiving the version consistency detection instruction sent by the terminal device and the vehicle information to be detected, based on the baseline version information of each vehicle model, the controller version information and the vehicle information to be detected, performs version consistency detection on the vehicle to be detected, obtains the detection result and sends it to the terminal device; after receiving the version consistency alignment instruction sent by the terminal device based on the detection result, formulates a version consistency alignment task based on the detection result and sends it to the vehicle end; The vehicle side receives the version consistency alignment task sent by the cloud, executes the version consistency alignment task, and performs software version alignment on the corresponding vehicle.

11. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the vehicle software version alignment method described in any one of claims 1 to 5, or executes the vehicle software version alignment method described in any one of claims 6 to 9 by executing the computer instructions.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the vehicle software version alignment method described in any one of claims 1 to 5, or to execute the vehicle software version alignment method described in any one of claims 6 to 9.

13. A computer program product, characterized in that It comprises computer instructions, and the computer instructions are used to make a computer execute the vehicle software version alignment method described in any one of claims 1 to 5, or execute the vehicle software version alignment method described in any one of claims 6 to 9.

Images