CN115686608A - Software version management method and device for vehicle, server and storage medium - Google Patents
Software version management method and device for vehicle, server and storage medium Download PDFInfo
- Publication number
- CN115686608A CN115686608A CN202211326908.2A CN202211326908A CN115686608A CN 115686608 A CN115686608 A CN 115686608A CN 202211326908 A CN202211326908 A CN 202211326908A CN 115686608 A CN115686608 A CN 115686608A
- Authority
- CN
- China
- Prior art keywords
- software version
- vehicle
- target
- target vehicle
- software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The application relates to the technical field of automobile software management, in particular to a software version management method, a device, a server and a storage medium for a vehicle, wherein the method comprises the following steps: acquiring a test task of a target vehicle; identifying target software versions and vehicle information of all controllers in a test task, issuing a collection request generated based on the vehicle information to a target vehicle, and receiving current software versions of all controllers collected by the target vehicle; and if the target software version is consistent with the version of the current software version, testing the target vehicle based on the test task, otherwise, aligning the test task with the software versions of all controllers in the target vehicle, and testing the target vehicle based on the test task after alignment. Therefore, the problems of resource waste, high cost, low working efficiency and the like caused by the fact that automatic management of the vehicle software version cannot be realized in the related technology are solved.
Description
Technical Field
The present application relates to the field of automotive software management technologies, and in particular, to a method, an apparatus, a server, and a storage medium for managing a software version of a vehicle.
Background
The remote communication is a communication technology for realizing remote transmission of signals by using a device with communication capability, and has a value in realizing synchronization of state information between an automobile and a cloud server and remote issuing of a control instruction, and a controller with communication capability in the automobile is generally a vehicle machine or a T-BOX (Telematics BOX).
However, in the process of developing vehicles, the behavior that a certain controller independently performs local upgrade often exists, which causes the phenomena of vehicle version confusion and management difficulty; when a research vehicle is tested, the whole vehicle software of a test vehicle is uniformly updated, and the related software version cannot be matched with the target software version due to the disordered vehicle version, so that the test failure or the invalid test is caused, the manpower and material resources are wasted, the cost is high, and the working efficiency is low.
In the related art, a tester is required to check each vehicle through a diagnostic instrument, and determine the vehicle version according to the obtained result and determine whether to update the vehicle version directly, and the processing mode has extremely low efficiency, wastes manpower and material resources, and cannot perform batch quick inspection and update.
Disclosure of Invention
The application provides a vehicle software version management method, a vehicle software version management device, a vehicle software version management server and a vehicle software version management storage medium, and aims to solve the problems that in the related art, automatic alignment and management of vehicle software versions cannot be achieved, resources are wasted, cost is high, working efficiency is low and the like.
The embodiment of the first aspect of the present application provides a software version management method for a vehicle, where the method is applied to a server, and the method includes the following steps: acquiring a test task of a target vehicle; identifying target software versions and vehicle information of all controllers in the test task, issuing a collection request generated based on the vehicle information to the target vehicle, and receiving current software versions of all controllers collected by the target vehicle; and if the versions of the target software version and the current software version are consistent, testing the target vehicle based on the test task, otherwise, aligning the test task with the software versions of all controllers in the target vehicle, and testing the target vehicle based on the test task after aligning.
According to the technical means, the method comprises the steps that a test task of the vehicle is obtained, target software versions and vehicle information of all controllers in the task are identified, a collection request generated by the vehicle information is sent to the target vehicle, the server receives current versions of all the controllers collected by the target vehicle, the target software versions are compared with the current versions, and when the versions are consistent, the target vehicle is directly tested according to the test task; if the versions are not consistent, the testing task is aligned with the software versions of all controllers in the target vehicle, then the target vehicle is tested based on the testing task, and based on the remote communication technology, the software versions of the target vehicle and the target software versions in the testing task can be automatically aligned, the automatic management of the vehicle software versions is achieved, the testing efficiency is improved, and the cost is reduced.
Optionally, the aligning the test task with the software versions of the respective controllers in the target vehicle includes: if the current software version of any controller of the target vehicle is lower than the target software version, upgrading the current software version of the corresponding controller to the target software version; and if the current software version of any controller of the target vehicle is higher than the target software version, degrading the current software version of the corresponding controller to the target software version.
According to the technical means, when the software version of any controller of the target vehicle is detected to be lower than the target version, the version of the corresponding controller is upgraded to the target software version, and if the software version of any controller of the target vehicle is higher than the target version, the version of the corresponding controller is downgraded to the target software version, so that updating failure caused by vehicle software version management chaos and related version mismatching is avoided, automatic alignment of the software version of the target vehicle and the target software version in a test task is realized, vehicles can be managed uniformly, and working efficiency is improved.
Optionally, the testing the target vehicle based on the test task after the aligning further includes: detecting whether the current software version of each aligned controller is consistent with the target software version; if the alignment is consistent with the alignment, judging that the alignment is successful, and testing the target vehicle based on the test task; otherwise, judging that the alignment fails, and realigning the current software version and the target software version of each controller until a preset stop condition is met, and stopping the alignment.
According to the technical means, whether the current software versions of the controllers are consistent with the target software versions or not is detected, whether software alignment is successful or not is judged, if so, the alignment is successful, and the target vehicle is tested according to the test task; if the software versions are inconsistent, the alignment is failed, then the versions are realigned until the realignment is successful, and the test failure caused by management confusion of the vehicle software versions due to the misalignment is avoided.
Optionally, the preset stop condition is that the alignment is successful, or the comparison failure times are greater than the preset times.
An embodiment of a second aspect of the present application provides a software version management apparatus for a vehicle, including: the acquisition module is used for acquiring a test task of a target vehicle; the receiving module is used for identifying the target software versions and the vehicle information of all controllers in the test task, issuing a collection request generated based on the vehicle information to the target vehicle, and receiving the current software versions of all the controllers collected by the target vehicle; and the test module is used for testing the target vehicle based on the test task if the target software version is consistent with the version of the current software version, otherwise, aligning the test task with the software versions of all controllers in the target vehicle, and testing the target vehicle based on the test task after alignment.
Optionally, the test module is further configured to: if the current software version of any controller of the target vehicle is lower than the target software version, upgrading the current software version of the corresponding controller to the target software version; and if the current software version of any controller of the target vehicle is higher than the target software version, degrading the current software version of the corresponding controller to the target software version.
Optionally, the test module is further configured to: detecting whether the current software version of each aligned controller is consistent with the target software version; if the alignment is consistent with the alignment, judging that the alignment is successful, and testing the target vehicle based on the test task; otherwise, judging that the alignment fails, and realigning the current software version and the target software version of each controller until a preset stop condition is met, and stopping the alignment.
Optionally, the preset stop condition is that the alignment is successful, or the comparison failure times are greater than the preset times.
An embodiment of a third aspect of the present application provides a server, including: the software version management method of the vehicle comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the software version management method of the vehicle according to the embodiment.
A fourth aspect of the present application provides a computer-readable storage medium, on which a computer program is stored, the program being executed by a processor for implementing a software version management method for a vehicle as described in the above embodiments.
Therefore, the application has at least the following beneficial effects:
(1) The method comprises the steps that a test task of a vehicle is obtained, target software versions and vehicle information of all controllers in the task are identified, a collection request generated by the vehicle information is sent to a target vehicle, a server receives current versions of all the controllers collected by the target vehicle, the target software versions are compared with the current versions, and when the versions are consistent, the target vehicle is directly tested according to the test task; if the versions are not consistent, the testing task is aligned with the software versions of all controllers in the target vehicle, then the target vehicle is tested based on the testing task, and based on the remote communication technology, the software versions of the target vehicle and the target software versions in the testing task can be automatically aligned, the automatic management of the vehicle software versions is achieved, the testing efficiency is improved, and the cost is reduced.
(2) According to the method and the device, when the fact that the software version of any controller of the target vehicle is lower than the target version is detected, the version of the corresponding controller is upgraded to the target software version, if the software version of any controller of the target vehicle is higher than the target version, the version of the corresponding controller is downgraded to the target software version, updating failure caused by vehicle software version management chaos and related version mismatching is avoided, automatic alignment of the software version of the target vehicle and the target software version in a test task is achieved, the vehicles can be managed in a unified mode, and working efficiency is improved.
(3) The method comprises the steps of detecting whether the current software version of each controller is consistent with the target software version, judging whether software alignment is successful or not, if so, representing that the alignment is successful, and testing a target vehicle according to a test task; if the software versions are inconsistent, the alignment is failed, then the versions are realigned until the realignment is successful, and the test failure caused by management confusion of the vehicle software versions due to the misalignment is avoided.
Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.
Drawings
The above and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 is a flowchart of a method for managing software versions of a vehicle according to an embodiment of the present application;
fig. 2 is a block diagram of a software version management method for a vehicle according to an embodiment of the present application;
FIG. 3 is a step diagram of a method for managing software versions of a vehicle according to an embodiment of the present application;
FIG. 4 is an exemplary diagram of a software version management apparatus for a vehicle according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a server according to an embodiment of the present application.
Description of reference numerals: the system comprises a software version management module, a vehicle identity information management module, a test task software information release module, a finished vehicle test software management system input module, a finished vehicle test software management system analysis module, a vehicle software version collection module on a target vehicle, a finished vehicle test software management system processing module, a vehicle OTA upgrading system, a finished vehicle test software management system feedback module and a test task statistics early warning module, wherein the software version management module comprises 1-a software version management module, 2-a vehicle identity information management module, 3-a test task software information release module, 4-a finished vehicle test software management system input module, 5-a finished vehicle test software management system analysis module, 6-a vehicle software version collection module on the target vehicle, 7-a finished vehicle test software management system processing module, 8-a vehicle OTA upgrading system, 9-a finished vehicle test software management system feedback module and 10-a test task statistics early warning module.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative and intended to explain the present application and should not be construed as limiting the present application.
A software version management method, apparatus, server, and storage medium for a vehicle according to an embodiment of the present application are described below with reference to the accompanying drawings. In the method, a vehicle test task is acquired, target software versions and vehicle information of all controllers in the task are identified, a vehicle information generation collection request is issued to a target vehicle, a server receives current versions of all controllers collected by the target vehicle, compares the target software versions with the current versions, and when the versions are consistent, the target vehicle is directly tested according to the test task; if the versions are not consistent, the testing task is aligned with the software versions of all controllers in the target vehicle, then the target vehicle is tested based on the testing task, and based on the remote communication technology, the software versions of the target vehicle and the target software versions in the testing task can be automatically aligned, the automatic management of the vehicle software versions is achieved, the testing efficiency is improved, and the cost is reduced. Therefore, the problems of resource waste, high cost, low working efficiency and the like caused by the fact that automatic management of the vehicle software version cannot be realized in the related technology are solved.
Specifically, fig. 1 is a flowchart illustrating a software version management method for a vehicle according to an embodiment of the present disclosure.
As shown in fig. 1, the software version management method for a vehicle, which is applied to a server, includes the following steps:
in step S101, a test task of the target vehicle is acquired.
It can be understood that the embodiment of the application prepares for the test of the subsequent vehicle by acquiring the test task of the target vehicle.
In step S102, the target software version and the vehicle information of each controller in the test task are identified, a collection request generated based on the vehicle information is issued to the target vehicle, and the current software version of each controller collected by the target vehicle is received.
It can be understood that, in the embodiment of the application, the target software versions and the vehicle information of the controllers in the test task are identified, the collection request generated according to the vehicle information is issued to the target vehicle, and the server receives the current software versions of the controllers collected by the vehicle, so that whether the software versions are updated or not is determined according to the current software versions.
In step S103, if the target software version is consistent with the current software version, the target vehicle is tested based on the test task, otherwise, the test task is aligned with the software versions of the controllers in the target vehicle, and the target vehicle is tested based on the test task after alignment.
It can be understood that, in the embodiment of the application, by comparing the target software version with the current version, when the versions are consistent, the target vehicle is directly tested according to the test task, if the versions are inconsistent, the test task is aligned with the software versions of the controllers in the target vehicle, then the target vehicle is tested based on the test task, and based on the remote communication technology, the software version of the target vehicle can be automatically aligned with the target software version in the test task, so that the automatic management of the vehicle software version is realized, the test efficiency is improved, and the cost is reduced.
In an embodiment of the present application, aligning the test task with the software versions of the respective controllers in the target vehicle includes: if the current software version of any controller of the target vehicle is lower than the target software version, upgrading the current software version of the corresponding controller to the target software version; and if the current software version of any controller of the target vehicle is higher than the target software version, degrading the current software version of the corresponding controller to the target software version.
It can be understood that, in the embodiment of the present application, when it is detected that the software version of any controller of the target vehicle is lower than the target version, the version of the corresponding controller is upgraded to the target software version, and if the software version of any controller of the target vehicle is higher than the target version, the version is downgraded to the target software version, so that update failure due to confusion of vehicle software version management and mismatch of related versions is avoided, and automatic alignment of the software version of the target vehicle and the target software version in the test task is realized, so as to facilitate uniform vehicle management and improve work efficiency.
In this application embodiment, after aligning, the target vehicle is tested based on the test task, further including: detecting whether the current software version of each aligned controller is consistent with the target software version; if the alignment is consistent with the alignment, judging that the alignment is successful, and testing the target vehicle based on the test task; otherwise, judging that the alignment fails, and realigning the current software version and the target software version of each controller until a preset stop condition is met, and stopping the alignment.
The preset stopping condition is that the alignment is successful, or the comparison failure times are larger than the preset times.
The preset number of times may be 3 times or 4 times, and is set or adjusted according to the actual situation, which is not specifically limited herein.
It can be understood that, in the embodiment of the application, whether the software alignment is successful or not is judged by detecting whether the current software versions of the controllers are consistent with the target software versions or not, if so, the alignment is successful, and the target vehicle is tested according to the test task; if the software versions are inconsistent, the alignment is failed, then the versions are realigned until the realignment is successful, and the test failure caused by management confusion of the vehicle software versions due to the misalignment is avoided.
According to the software version management method for the vehicle, a test task of the vehicle is obtained, target software versions and vehicle information of all controllers in the task are identified, a collection request generated by the vehicle information is issued to the target vehicle, a server receives current versions of all the controllers collected by the target vehicle and compares the target software versions with the current versions, and when the versions are consistent, the target vehicle is directly tested according to the test task; if the versions are not consistent, the testing task is aligned with the software versions of all controllers in the target vehicle, then the target vehicle is tested based on the testing task, and based on the remote communication technology, the software versions of the target vehicle and the target software versions in the testing task can be automatically aligned, the automatic management of the vehicle software versions is achieved, the testing efficiency is improved, and the cost is reduced. Therefore, the problems of resource waste, high cost, low working efficiency and the like caused by the fact that automatic management of the vehicle software version cannot be realized in the related technology are solved.
The following will explain the software version management method of the vehicle in detail with reference to fig. 2 and 3, specifically as follows:
the embodiment of the application comprises the following processing modules: the system comprises a software version management module, a vehicle identity information management module, a test task software information release module, a finished vehicle test software management system input module, a finished vehicle test software management system analysis module, a vehicle software version collection module on a target vehicle, a finished vehicle test software management system processing module, a vehicle OTA (Over-the-Air Technology) upgrading system, a finished vehicle test software management system feedback module and a test task statistics early warning module. Specifically, the method comprises the following steps:
as shown in fig. 2, 1 is a software version management module, and is responsible for managing pre-release software information (correspondence between an OTA large version and each controller small version, and controller software version and Bootloader version related information adapted correspondingly, and inputting the related information to the module 4.
And 2, a vehicle identity information management module, which is responsible for identifying and managing vehicle identities (basic data such as vehicle types, vehicle systems and configurations) and inputting relevant information to the module 4.
And 3, a test task software information publishing module, which is responsible for managing and publishing test task information (a software large version, vehicle identity information and Vehicle Identification Number (VIN) code which are required to be used in the test task), and inputting relevant information to the module 4.
And 4, a finished automobile test software management system input module, which is responsible for collecting all information required by the finished automobile test software management system and collecting relevant data and submitting the relevant data to the module 5.
And 5, a finished vehicle test software management system analysis module, which is responsible for analyzing and judging whether the current software version state of the target vehicle can carry out the specified test task or not, and submitting the analysis result and the subsequent processing flow to a module 7.
And 6, a vehicle software version collecting module on the target vehicle, which is responsible for collecting software version information (large version number, small version number of each controller and Bootloader information) of the current vehicle and inputting the collected result to the module 4 in a wireless network mode (4G/5G/WIFI).
And 7, a finished vehicle test software management system processing module which is responsible for carrying out corresponding processing according to the analysis result of the module 5, and carrying out appropriate processing according to different working conditions if the current software version of the target vehicle does not meet the requirement of the test task.
And 8, a vehicle OTA upgrading system which is responsible for aligning the vehicle software version with the specified software version in the test task in a whole vehicle OTA mode according to the request of the module 7 and feeding back the corresponding result to the test software management system.
And 9, a finished vehicle test software management system feedback module which is responsible for receiving and recording the alignment result of the target vehicle software and feeding the result back to the module 10.
And 10, a test task statistics and early warning module, which is used for recording and managing related information and giving an early warning to a publisher of the test task when the software version of the target vehicle does not meet the requirement of the test task and cannot be aligned successfully.
The automatic management of the software version of the vehicle is realized through the mutual cooperation of the modules, and the specific flow of the software version management method of the vehicle is explained by combining the modules, as shown in fig. 3, the specific steps are as follows:
And step 206, the whole vehicle test software management system input module is connected with the target vehicle through a remote communication technology, and local software version information of the target vehicle, including the local large version of the target vehicle and the software versions of all controllers, is collected through a vehicle software version collection module in the target vehicle.
And step 207, the whole vehicle test software management system analysis module judges whether the software version of the target vehicle meets the test requirement by comparing the software version information uploaded by the target vehicle with the software version information contained in the test task, if so, the step 208 is executed, and if not, the step 209 is executed.
And step 208, the test task system and the target test vehicle carry out tests according to the test tasks.
And step 211, the whole vehicle test software management system analysis module analyzes and judges the current software version of each ECU of the target vehicle, if the software version of a certain ECU in the target vehicle is too low, the step 213 is carried out, and if the software version of a certain ECU in the target vehicle is too high, the step 212 is carried out.
And step 212, the whole vehicle test software management system processing module uses the vehicle OTA upgrading system to downgrade the relevant ECU in the target vehicle to the target version in the test task by means of interface calling or service request.
Step 213, the whole vehicle test software management system processing module upgrades the relevant ECU in the target vehicle to the target version in the test task by means of the vehicle OTA upgrade system through interface call or service request.
In step 216, the test task statistics and early warning module records the error link and the related error condition in the process, and gives an early warning prompt to the publisher of the test task through mails, short messages and other ways.
In summary, the embodiment of the application is based on a remote communication technology, can realize automatic alignment of the software version of the target vehicle and the target software version in the test task, and record management is carried out on the relevant process, and based on the objective conditions that the test vehicle in a whole vehicle factory has wide distribution, the quality of the service of testers is uneven and the like, the software preparation efficiency before the test is greatly improved, and the economic cost is reduced; the software version of the target vehicle is controlled before the test activity starts, and the test activity failure caused by the software version error and a large amount of labor cost and time cost caused by analysis traceability are avoided; the automatic management of the vehicle software version is realized, and the market problem caused by the configuration error of the vehicle software is avoided.
Next, a software version management apparatus of a vehicle according to an embodiment of the present application is described with reference to the drawings.
Fig. 4 is a block diagram schematically illustrating a software version management apparatus for a vehicle according to an embodiment of the present application.
As shown in fig. 4, the software version management apparatus 20 for a vehicle includes: an acquisition module 210, a receiving module 220, and a testing module 230.
The obtaining module 210 is configured to obtain a test task of a target vehicle; the receiving module 220 is configured to identify a target software version and vehicle information of each controller in the test task, issue a collection request generated based on the vehicle information to the target vehicle, and receive a current software version of each controller collected by the target vehicle; the test module 230 is configured to test the target vehicle based on the test task if the target software version is consistent with the version of the current software version, otherwise align the test task with the software versions of the controllers in the target vehicle, and test the target vehicle based on the test task after alignment.
In an embodiment of the present application, the testing module 230 is further configured to: if the current software version of any controller of the target vehicle is lower than the target software version, upgrading the current software version of the corresponding controller to the target software version; and if the current software version of any controller of the target vehicle is higher than the target software version, degrading the current software version of the corresponding controller to the target software version.
In an embodiment of the present application, the testing module 230 is further configured to: detecting whether the current software version of each aligned controller is consistent with the target software version; if the alignment is consistent with the alignment, judging that the alignment is successful, and testing the target vehicle based on the test task; otherwise, judging that the alignment fails, and realigning the current software version and the target software version of each controller until a preset stop condition is met, and stopping the alignment.
In the embodiment of the present application, the preset stop condition is that the alignment is successful, or the comparison failure times are greater than the preset times.
It should be noted that the foregoing explanation of the embodiment of the software version management method for a vehicle is also applicable to the software version management device for a vehicle in this embodiment, and is not repeated herein.
According to the software version management device for the vehicle, provided by the embodiment of the application, a test task of the vehicle is obtained, target software versions and vehicle information of all controllers in the task are identified, a collection request generated by the vehicle information is issued to a target vehicle, a server receives current versions of all controllers collected by the target vehicle, the target software versions are compared with the current versions, and when the versions are consistent, the target vehicle is directly tested according to the test task; if the versions are not consistent, the testing task is aligned with the software versions of all controllers in the target vehicle, then the target vehicle is tested based on the testing task, and based on the remote communication technology, the software versions of the target vehicle and the target software versions in the testing task can be automatically aligned, the automatic management of the vehicle software versions is achieved, the testing efficiency is improved, and the cost is reduced. Therefore, the problems of resource waste, high cost, low working efficiency and the like caused by the fact that automatic management of the vehicle software version cannot be realized in the related technology are solved.
Fig. 5 is a schematic structural diagram of a server according to an embodiment of the present application. The server may include:
The processor 502, when executing the program, implements the software version management method of the vehicle provided in the above-described embodiments.
Further, the server further comprises:
a communication interface 503 for communication between the memory 501 and the processor 502.
A memory 501 for storing computer programs that can be run on the processor 502.
The Memory 501 may include a high-speed RAM (Random Access Memory) Memory, and may also include a nonvolatile Memory, such as at least one disk Memory.
If the memory 501, the processor 502 and the communication interface 503 are implemented independently, the communication interface 503, the memory 501 and the processor 502 may be connected to each other through a bus and perform communication with each other. The bus may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.
Optionally, in a specific implementation, if the memory 501, the processor 502, and the communication interface 503 are integrated on one chip, the memory 501, the processor 502, and the communication interface 503 may complete mutual communication through an internal interface.
The processor 502 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present Application.
Embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements the software version management method of the vehicle as above.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or N embodiments or examples. Moreover, various embodiments or examples and features of various embodiments or examples described in this specification can be combined and combined by one skilled in the art without being mutually inconsistent.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "N" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more N executable instructions for implementing steps of a custom logic function or process, and alternate implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a programmable gate array, a field programmable gate array, or the like.
It will be understood by those skilled in the art that all or part of the steps carried out in the method of implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and the program, when executed, includes one or a combination of the steps of the method embodiments.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (10)
1. A software version management method for a vehicle, which is applied to a server, wherein the method comprises the following steps:
acquiring a test task of a target vehicle;
identifying target software versions and vehicle information of all controllers in the test task, issuing a collection request generated based on the vehicle information to the target vehicle, and receiving current software versions of all controllers collected by the target vehicle;
and if the target software version is consistent with the version of the current software version, testing the target vehicle based on the test task, otherwise, aligning the test task with the software versions of all controllers in the target vehicle, and testing the target vehicle based on the test task after alignment.
2. The method of claim 1, wherein said aligning the test tasks with software versions of respective controllers in the target vehicle comprises:
if the current software version of any controller of the target vehicle is lower than the target software version, upgrading the current software version of the corresponding controller to the target software version;
and if the current software version of any controller of the target vehicle is higher than the target software version, degrading the current software version of the corresponding controller to the target software version.
3. The method of claim 1, wherein the testing the target vehicle based on the test task after aligning further comprises:
detecting whether the current software version of each aligned controller is consistent with the target software version;
if the alignment is consistent with the alignment, judging that the alignment is successful, and testing the target vehicle based on the test task;
otherwise, judging that the alignment fails, and realigning the current software version and the target software version of each controller until a preset stop condition is met, and stopping the alignment.
4. The method according to claim 3, wherein the predetermined stop condition is that the alignment is successful, or the number of comparison failures is greater than a predetermined number.
5. A software version management device for a vehicle, the device being applied to a server and comprising:
the acquisition module is used for acquiring a test task of a target vehicle;
the receiving module is used for identifying the target software versions and the vehicle information of all controllers in the test task, issuing a collection request generated based on the vehicle information to the target vehicle, and receiving the current software versions of all the controllers collected by the target vehicle;
and the test module is used for testing the target vehicle based on the test task if the target software version is consistent with the version of the current software version, otherwise, aligning the test task with the software versions of all controllers in the target vehicle, and testing the target vehicle based on the test task after alignment.
6. The apparatus of claim 5, wherein the testing module is further configured to:
if the current software version of any controller of the target vehicle is lower than the target software version, upgrading the current software version of the corresponding controller to the target software version;
and if the current software version of any controller of the target vehicle is higher than the target software version, degrading the current software version of the corresponding controller to the target software version.
7. The apparatus of claim 5, wherein the testing module is further configured to:
detecting whether the current software version of each aligned controller is consistent with the target software version;
if the target vehicle is consistent with the target vehicle, judging that the alignment is successful, and testing the target vehicle based on the test task;
otherwise, judging that the alignment fails, and realigning the current software version and the target software version of each controller until a preset stop condition is met, and stopping the alignment.
8. The apparatus of claim 7, wherein the predetermined stop condition is that the alignment is successful, or the number of comparison failures is greater than a predetermined number.
9. A server, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, the processor executing the program to implement the software version management method of a vehicle according to any one of claims 1 to 4.
10. A computer-readable storage medium on which a computer program is stored, characterized in that the program is executed by a processor for implementing a software version management method of a vehicle according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211326908.2A CN115686608A (en) | 2022-10-25 | 2022-10-25 | Software version management method and device for vehicle, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211326908.2A CN115686608A (en) | 2022-10-25 | 2022-10-25 | Software version management method and device for vehicle, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115686608A true CN115686608A (en) | 2023-02-03 |
Family
ID=85098743
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211326908.2A Pending CN115686608A (en) | 2022-10-25 | 2022-10-25 | Software version management method and device for vehicle, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115686608A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116148583A (en) * | 2023-04-14 | 2023-05-23 | 广汽埃安新能源汽车股份有限公司 | Complete vehicle detection method and device based on ECU edition replacement |
-
2022
- 2022-10-25 CN CN202211326908.2A patent/CN115686608A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116148583A (en) * | 2023-04-14 | 2023-05-23 | 广汽埃安新能源汽车股份有限公司 | Complete vehicle detection method and device based on ECU edition replacement |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108829593B (en) | Code coverage rate calculation and analysis method, device, equipment and storage medium | |
| CN106970880B (en) | Distributed automatic software testing method and system | |
| WO2021203604A1 (en) | Update test method and apparatus for vehicle component, and computer device and storage medium | |
| CN110908888B (en) | Server testing method and device | |
| CN105354140A (en) | Automation testing method and system | |
| CN115686608A (en) | Software version management method and device for vehicle, server and storage medium | |
| CN110990289B (en) | Method and device for automatically submitting bug, electronic equipment and storage medium | |
| CN112035348A (en) | Automatic test platform and automatic test method thereof | |
| CN111124871A (en) | Interface test method and device | |
| CN113608518A (en) | Data generation method, device, terminal equipment and medium | |
| CN111611154B (en) | Regression testing method, device and equipment | |
| CN111324540B (en) | Interface testing method and device | |
| CN107992420B (en) | Management method and system for test item | |
| CN115118577A (en) | Method and device for determining remote upgrade abnormal reason, electronic equipment and storage medium | |
| CN116257270A (en) | Vehicle, upgrading method and device of vehicle | |
| CN114647588A (en) | Interface test method and device | |
| CN115113890A (en) | Automatic deployment method, system, equipment and medium of terminal software | |
| CN116382674A (en) | Component configuration method and device of automobile diagnostic device, medium and electronic device | |
| CN114416441A (en) | Real-time database automatic testing method and system, electronic equipment and storage medium | |
| CN113360389A (en) | Performance test method, device, equipment and storage medium | |
| CN113282496A (en) | Automatic interface test method, device, equipment and storage medium | |
| CN115102856B (en) | Method and system for upgrading equipment of Internet of things | |
| CN116166303A (en) | Vehicle OTA differential software package verification method and device, electronic equipment and medium | |
| CN115422081A (en) | Multi-version software testing method and device, electronic equipment and storage medium | |
| CN116204410A (en) | Database performance test method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |