CN116594657A - OTA upgrading method and device, vehicle and storage medium - Google Patents
OTA upgrading method and device, vehicle and storage medium Download PDFInfo
- Publication number
- CN116594657A CN116594657A CN202310721972.9A CN202310721972A CN116594657A CN 116594657 A CN116594657 A CN 116594657A CN 202310721972 A CN202310721972 A CN 202310721972A CN 116594657 A CN116594657 A CN 116594657A
- Authority
- CN
- China
- Prior art keywords
- verification information
- information
- version
- configuration
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses an OTA upgrading method, an OTA upgrading device, a vehicle and a storage medium. The method comprises the following steps: analyzing the upgrade data packet to determine a target upgrade type; extracting compatibility verification information corresponding to the target upgrading type from the upgrading data packet, and determining reference information corresponding to the compatibility verification information, wherein the compatibility verification information comprises product verification information, software verification information, hardware verification information and/or configuration verification information; comparing the corresponding compatibility verification information with the reference information to obtain a compatibility verification result, wherein the compatibility verification result comprises that the compatibility verification passes and fails; and when the compatibility verification result is that the compatibility verification is passed, finishing OTA upgrading based on the upgrading data packet. The invention solves the problems that the ECU of the vehicle is suspended during the OTA upgrading of the vehicle due to incompatibility among upgrading software, configuration files and hardware, and the ECU needs to be replaced again, thereby wasting manpower and material resources and realizing the effectiveness of OTA upgrading of vehicle-end software.
Description
Technical Field
The present invention relates to the field of internet applications, and in particular, to an OTA upgrading method, device, vehicle and storage medium.
Background
Currently, most of the on-board software is based on UDS (Unified Diagnostic Services, unified diagnostic service) when OTA (Over-the-Air Technology) upgrade is performed, and the application software program upgrade can be mainly divided into three parts: pre-Programming Step Pre-Programming phase, programming Step Programming phase, post-Programming Step Post-Programming phase.
In the OTA upgrade, an OEM (whole vehicle manufacturer) server transmits a soft package, and in the programming stage, an on-vehicle ECU performs integrity verification of downloaded data to ensure the reliability of the data. However, the OEM server may have a situation that the faulty software package is issued by a faulty operation, if the downloaded and upgraded software is not compatible with the vehicle, when the vehicle is restarted, the new software is run, and the ECU may be suspended for running due to the incompatibility of the new software and other parts of the vehicle, or the Bootloader cannot be re-entered for the next OTA upgrade. For example: the hardware 1 and the hardware 2 both run the same Bootloader, the upgrade flow is consistent, but the hardware 1 can only run the application software 1, the hardware 2 can only run the application software 2, and because the upgrade flow is consistent, the hardware 1 can upgrade the application software 2, when the hardware 1 runs the application software 2, the ECU can hang and become brick, the vehicle can only recall and replace the ECU, and a large amount of manpower and material resources are wasted.
Disclosure of Invention
The invention provides an OTA upgrading method, an OTA upgrading device, a vehicle and a storage medium, so that compatibility detection is carried out on upgrading software, configuration files and hardware at a vehicle end, and effective upgrading of the vehicle end software is ensured.
According to an aspect of the present invention, there is provided an OTA upgrading method, including:
analyzing the upgrade data packet to determine a target upgrade type;
extracting compatibility verification information corresponding to the target upgrading type from the upgrading data packet, and determining reference information corresponding to the compatibility verification information, wherein the compatibility verification information comprises product verification information, software verification information, hardware verification information and/or configuration verification information;
comparing the corresponding compatibility verification information with the reference information to obtain a compatibility verification result, wherein the compatibility verification result comprises that the compatibility verification passes and fails;
and when the compatibility verification result is that the compatibility verification is passed, finishing OTA upgrading based on the upgrading data packet.
Optionally, the target upgrade type includes a software upgrade, a configuration file upgrade, and a software configuration simultaneous upgrade.
Optionally, the extracting the compatibility verification information corresponding to the target upgrade type from the upgrade data packet, and determining the reference information corresponding to the compatibility verification information, includes:
When the target upgrading type is software upgrading, extracting compatibility verification information from a software version file of the upgrading data packet, and determining reference information corresponding to the compatibility verification information from a vehicle end;
when the target upgrading type is configuration file upgrading, extracting compatibility verification information from a version configuration file of the upgrading data packet, and determining reference information corresponding to the compatibility verification information from a vehicle end;
when the target upgrading type is software configuration and is simultaneously upgraded, extracting compatibility verification information from a software version file and a version configuration file of the upgrading data packet, and determining reference information corresponding to the compatibility verification information which cannot be matched and verified from a vehicle side.
Optionally, the extracting compatibility verification information from the software version file of the upgrade data packet, and determining, from a vehicle end, reference information corresponding to the compatibility verification information includes:
extracting product basic information from a software version file of the upgrade data packet as product verification information, and determining product reference information corresponding to the product verification information from a boot loader of a vehicle end;
Extracting software version information from a software version file of the upgrading data packet as software verification information, and determining software reference information corresponding to the software verification information from a boot loader of a vehicle end;
extracting hardware version information from a software version file of the upgrade data packet as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of a vehicle side;
and extracting configuration version information from the software version file of the upgrade data packet as configuration verification information, and determining configuration reference information corresponding to the configuration verification information from the configuration file of the vehicle end.
Optionally, the extracting the compatibility verification information from the version configuration file of the upgrade data packet, and determining the reference information corresponding to the compatibility verification information from the vehicle end includes:
extracting product basic information from the version configuration file of the upgrade data packet as product verification information, and determining product reference information corresponding to the product verification information from a boot loader of a vehicle end;
extracting hardware version information from the version configuration file of the upgrade data packet as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of a vehicle side;
And extracting configuration version information from the version configuration file of the upgrade data packet as configuration verification information, and determining configuration reference information corresponding to the configuration verification information from the current software version file of the vehicle end.
Optionally, the extracting the compatibility verification information from the software version file and the version configuration file of the upgrade data packet, and determining, from the vehicle end, the reference information corresponding to the compatibility verification information that cannot be matched and verified, includes:
product basic information is extracted from a software version file and a version configuration file of the upgrading data packet respectively to serve as product verification information, and product reference information corresponding to the product verification information is determined from a boot loader of a vehicle end;
extracting hardware version information from a software version file and a version configuration file of the upgrading data packet respectively to serve as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of a vehicle end;
extracting software version information from a software version file of the upgrading data packet as software verification information, and determining software reference information corresponding to the software verification information from a boot loader of a vehicle end;
Extracting configuration version information from a software version file of the upgrade data packet as first configuration verification information, extracting configuration version information from a version configuration file of the upgrade data packet as second configuration verification information, taking the first configuration verification information as reference information of the second configuration verification information, and taking the second configuration verification information as reference information of the first configuration verification information.
Optionally, before comparing the corresponding compatibility verification information with the reference information, the method further includes:
and performing cyclic redundancy check on the upgrading data packet, and stopping OTA upgrading operation if the cyclic redundancy check does not pass.
According to another aspect of the present invention, there is provided an OTA upgrading apparatus, including:
the upgrade type determining module is used for analyzing the upgrade data packet and determining a target upgrade type;
the verification information extraction module is used for extracting compatibility verification information corresponding to the target upgrading type from the upgrading data packet and determining reference information corresponding to the compatibility verification information, wherein the compatibility verification information comprises product verification information, software verification information, hardware verification information and/or configuration verification information;
The verification information comparison module is used for comparing the corresponding compatibility verification information with the reference information to obtain a compatibility verification result, wherein the compatibility verification result comprises that the compatibility verification passes and fails;
and the OTA upgrading module is used for finishing OTA upgrading based on the upgrading data packet when the compatibility verification result is that the compatibility verification is passed.
According to another aspect of the present invention, there is provided a vehicle including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the OTA upgrade method of any one of the embodiments of the present invention.
According to another aspect of the present invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to execute an OTA upgrade method according to any one of the embodiments of the present invention.
According to the technical scheme, the target upgrading type is determined by analyzing the upgrading data packet; extracting compatibility verification information corresponding to the target upgrading type from the upgrading data packet, and determining reference information corresponding to the compatibility verification information, wherein the compatibility verification information comprises product verification information, software verification information, hardware verification information and/or configuration verification information; comparing the corresponding compatibility verification information with the reference information to obtain a compatibility verification result, wherein the compatibility verification result comprises that the compatibility verification passes and fails; when the compatibility verification result is that the compatibility verification is passed, OTA upgrading is completed based on the upgrading data packet, so that the problems that when a vehicle is in OTA upgrading, the vehicle ECU is suspended due to incompatibility among upgrading software, configuration files and hardware, the ECU needs to be replaced again and manpower and material resources are wasted are solved, compatibility detection is carried out on the vehicle end among the upgrading software, the configuration files and the vehicle hardware, and effective upgrading of the vehicle end software is ensured.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of an OTA upgrading method according to a first embodiment of the present invention;
fig. 2 is a schematic structural diagram of an OTA upgrading device according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a vehicle implementing an OTA upgrade method according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," "target," and the like in the description and claims of the present invention and in the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
Fig. 1 is a flowchart of an OTA upgrading method according to an embodiment of the present invention, where the method may be performed by an OTA upgrading device, the OTA upgrading device may be implemented in hardware and/or software, and the OTA upgrading device may be configured in a vehicle. As shown in fig. 1, the method includes:
S110, analyzing the upgrade data packet to determine the target upgrade type.
In the embodiment, after the upgrade data packet is downloaded at the vehicle end, compatibility detection is performed on the upgrade data packet so as to prevent the situation that the vehicle ECU is suspended due to incompatibility among upgrade software, configuration files and hardware. Therefore, the embodiment can analyze the upgrade data packet after the upgrade data packet is downloaded at the vehicle end, and determine the target upgrade type of the current OTA upgrade.
In one embodiment, the target upgrade types may include a software upgrade, a profile upgrade, and a software configuration simultaneous upgrade.
Specifically, the software upgrading can be understood as only performing version upgrading on the application software, and the upgrading data packet is an upgrading software packet of the application software without upgrading the configuration file; the configuration file upgrading can be understood as upgrading only the configuration file, and version upgrading is not performed on application software, and an upgrading data packet is an upgrading configuration file packet; the software configuration simultaneous upgrade can be understood as both version upgrade and upgrade configuration file of application software, and the upgrade data packet includes an upgrade software packet and an upgrade configuration file packet.
S120, extracting compatibility verification information corresponding to the target upgrading type from the upgrading data packet, and determining reference information corresponding to the compatibility verification information, wherein the compatibility verification information comprises product verification information, software verification information, hardware verification information and/or configuration verification information.
The compatibility verification information may be understood as information for verifying compatibility problems of the upgrade data packet, and the reference information may be understood as comparison information at the time of verification. In this embodiment, the compatibility verification information may include product verification information, software verification information, hardware verification information, and/or configuration verification information, that is, the compatibility of the OTA upgrade in this embodiment is verified from multiple dimensions, so that the validity of the OTA upgrade can be ensured.
In one embodiment, the implementation of S120 may be divided into the following cases:
a1, when the target upgrading type is software upgrading, extracting compatibility verification information from a software version file of an upgrading data packet, and determining reference information corresponding to the compatibility verification information from a vehicle end.
Specifically, when the OTA upgrade is only performed on the software part, the compatibility verification information can be extracted from the software version file of the upgrade data packet, and the compatibility verification information can include product verification information, software verification information, hardware verification information and configuration verification information. And, each piece of compatibility verification information may extract the corresponding reference information from the vehicle side.
Further, A1 may be implemented by the following specific steps:
a11, extracting product basic information from the software version file of the upgrade data packet as product verification information, and determining product reference information corresponding to the product verification information from a boot loader of the vehicle end.
Specifically, the product verification information may include information such as a car manufacturer name, a project name, a car model, and the like. The software version file of the upgrade data packet stores basic information of products such as car names, project names, car types and the like, is used for recording the type of the products applicable to the upgrade software version, and can be extracted to serve as product verification information; the BootLoader of the vehicle end also stores information such as a vehicle name, a project name, a vehicle type and the like of the vehicle end, and can determine product reference information corresponding to the product verification information from the BootLoader of the vehicle end for verifying the product compatibility of the upgrade data packet.
A12, extracting software version information from the software version file of the upgrade data packet as software verification information, and determining software reference information corresponding to the software verification information from a boot loader of the vehicle side.
Specifically, the software version information is stored in the software version file of the upgrade data packet, and can be extracted to be used as software verification information; the BootLoader of the vehicle end also stores related information of compatible software versions, and can determine software reference information corresponding to the software verification information from the BootLoader of the vehicle end, so as to be used for carrying out software version compatibility verification on the upgrade data packet.
A13, extracting hardware version information from the software version file of the upgrade data packet as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of the vehicle side.
Specifically, the software version file of the upgrade data packet stores hardware version information, which is used for recording the hardware type applicable to the upgrade software version, and the hardware version information can be extracted to be used as hardware verification information; the shared storage area of the vehicle end also stores the hardware information of the vehicle, and the hardware reference information corresponding to the hardware verification information can be determined from the shared storage area of the vehicle end and used for carrying out hardware compatibility verification on the upgrade data packet.
A14, extracting configuration version information from the software version file of the upgrade data packet as configuration verification information, and determining configuration reference information corresponding to the configuration verification information from the configuration file of the vehicle end.
Specifically, the software version file of the upgrade data packet stores configuration version information, which is used for recording configuration file information applicable to the upgrade software version, and the configuration version information can be extracted to be used as configuration verification information; configuration information is also stored in the configuration file of the vehicle end, and configuration reference information corresponding to the configuration verification information can be determined from the configuration file of the vehicle end and used for carrying out configuration compatibility verification on the upgrade data packet.
A2, when the target upgrading type is configuration file upgrading, extracting compatibility verification information from a version configuration file of an upgrading data packet, and determining reference information corresponding to the compatibility verification information from a vehicle end.
Specifically, when the OTA upgrade is only performed on the configuration file part, the compatibility verification information can be extracted from the version configuration file of the upgrade data packet, and the compatibility verification information can include product verification information, hardware verification information and configuration verification information. And, each piece of compatibility verification information may extract the corresponding reference information from the vehicle side.
Further, A2 may be implemented by the following specific steps:
a21, extracting product basic information from the version configuration file of the upgrade data packet as product verification information, and determining product reference information corresponding to the product verification information from a boot loader of the vehicle end.
Specifically, the product verification information may include information such as a car manufacturer name, a project name, a car model, and the like. The version configuration file of the upgrade data packet stores basic information of products such as car names, project names, car types and the like, is used for recording the type of the products applicable to the upgrade configuration file, and can be extracted to serve as product verification information; the BootLoader of the vehicle end also stores information such as a vehicle name, a project name, a vehicle type and the like of the vehicle end, and can determine product reference information corresponding to the product verification information from the BootLoader of the vehicle end for verifying the product compatibility of the upgrade data packet.
A22, extracting hardware version information from the version configuration file of the upgrade data packet as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of the vehicle side.
Specifically, the version configuration file of the upgrade data packet stores hardware version information, which is used for recording the hardware type applicable to the upgrade configuration file, and the hardware version information can be extracted to be used as hardware verification information; the shared storage area of the vehicle end also stores the hardware information of the vehicle, and the hardware reference information corresponding to the hardware verification information can be determined from the shared storage area of the vehicle end and used for carrying out hardware compatibility verification on the upgrade data packet.
A23, extracting configuration version information from the version configuration file of the upgrade data packet to serve as configuration verification information, and determining configuration reference information corresponding to the configuration verification information from the current software version file of the vehicle end.
Specifically, the version configuration file of the upgrade data packet stores configuration version information, and the configuration version information can be extracted to be used as configuration verification information; the current software version file of the vehicle end also stores applicable configuration file information, and configuration reference information corresponding to the configuration verification information can be determined from the current software version file of the vehicle end and used for carrying out configuration compatibility verification on the upgrade data packet.
A3, when the target upgrading type is software configuration and upgrading is performed simultaneously, extracting compatibility verification information from a software version file and a version configuration file of an upgrading data packet, and determining reference information corresponding to the compatibility verification information which cannot be matched and verified from a vehicle side.
Specifically, when the current OTA upgrade is to upgrade the software part and the configuration file part at the same time, the compatibility verification information may be extracted from the software version file and the version configuration file of the upgrade data packet, where the compatibility verification information may include product verification information, software verification information, hardware verification information, and configuration verification information. The partial compatibility verification information can mutually verify the reference information of other compatibility verification information, and for the compatibility verification information which cannot be matched and verified, the corresponding reference information can be extracted from the vehicle side.
Further, A3 may be implemented by the following specific steps:
a31, extracting product basic information from the software version file and the version configuration file of the upgrade data packet respectively to serve as product verification information, and determining product reference information corresponding to the product verification information from a boot loader of the vehicle end.
Specifically, the product verification information may include information such as a car manufacturer name, a project name, a car model, and the like. The software version file of the upgrade data packet is stored with basic information of products such as a car name, a project name, a car type and the like, and is used for recording the type of the products applicable to the upgrade software version, the version configuration file of the upgrade data packet is also stored with basic information of products such as the car name, the project name, the car type and the like, and is used for recording the type of the products applicable to the upgrade configuration file, and the basic information of the products can be respectively extracted to serve as product verification information; the BootLoader of the vehicle end also stores information such as a vehicle name, a project name, a vehicle type and the like of the vehicle end, and can determine product reference information corresponding to the product verification information from the BootLoader of the vehicle end for verifying the product compatibility of the upgrade data packet.
A32, extracting hardware version information from the software version file and the version configuration file of the upgrading data packet respectively to serve as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of the vehicle end.
Specifically, the software version file of the upgrade data packet stores hardware version information for recording the hardware type applicable to the upgrade software version, the version configuration file of the upgrade data packet stores hardware version information for recording the hardware type applicable to the upgrade configuration file, and the hardware version information can be respectively extracted to be used as hardware verification information; the shared storage area of the vehicle end also stores the hardware information of the vehicle, and the hardware reference information corresponding to the hardware verification information can be determined from the shared storage area of the vehicle end and used for carrying out hardware compatibility verification on the upgrade data packet.
A33, extracting software version information from the software version file of the upgrade data packet as software verification information, and determining software reference information corresponding to the software verification information from a boot loader of the vehicle side.
Specifically, the software version information is stored in the software version file of the upgrade data packet, and can be extracted to be used as software verification information; the BootLoader of the vehicle end also stores related information of compatible software versions, and can determine software reference information corresponding to the software verification information from the BootLoader of the vehicle end, so as to be used for carrying out software version compatibility verification on the upgrade data packet.
A34, extracting configuration version information from a software version file of the upgrade data packet as first configuration verification information, extracting configuration version information from the version configuration file of the upgrade data packet as second configuration verification information, taking the first configuration verification information as reference information of the second configuration verification information, and taking the second configuration verification information as reference information of the first configuration verification information.
Specifically, the software version file of the upgrade data packet stores configuration version information, which is used for recording configuration file information applicable to the upgrade software version, and the configuration version information can be extracted to be used as first configuration verification information; configuration version information is stored in a version configuration file of the upgrade data packet, and can be extracted to serve as second configuration verification information. The first configuration verification information and the second configuration verification information may be related to each other as reference information for performing configuration compatibility verification on the upgrade data packet.
S130, comparing the corresponding compatibility verification information with the reference information to obtain a compatibility verification result, wherein the compatibility verification result comprises that the compatibility verification passes and the compatibility verification fails.
In this embodiment, the compatibility verification information and the corresponding reference information may be compared, and if they are consistent, it may be determined that the compatibility verification result is that the compatibility verification passes; otherwise, the compatibility verification result may be determined to be a compatibility verification failure.
And S140, when the compatibility verification result is that the compatibility verification is passed, finishing OTA upgrading based on the upgrading data packet.
In this embodiment, if the compatibility verification result is that the compatibility verification is passed, the OTA upgrade is continuously completed based on the upgrade data packet, and after the upgrade is successfully reset, the new software after the upgrade can be run; if the compatibility verification result is that the compatibility verification fails, the OTA upgrading is stopped, the upgrading fails and the server failure reason is fed back.
In one embodiment, before S120, the OTA upgrading method provided in this embodiment may further include: and performing cyclic redundancy check on the upgrading data packet, and stopping OTA upgrading operation if the cyclic redundancy check does not pass.
It can be understood that, before the OTA upgrading method provided in this embodiment is applied, an iteration rule of software, hardware, and a configuration file version number needs to be formulated, and corresponding information is added in an upgrade data packet and a vehicle-end memory according to the rule for compatibility verification.
For example, the data block may be divided in the nonvolatile memory Flash at the vehicle end, and the information shown in table 1 is stored.
Table 1 data store partitioning table
The definition of the information in the software Version file app_version_info_header can be as shown in table 2.
Table 2 software version file information table
The definition of the information in the Version profile config_file_version_info_header may be as shown in table 3.
Table 3 version profile information table
When the script is used for compiling software, the version_info_header can be added to the front of the corresponding executable file and the front of the configuration file to be combined into a data packet, so that the downloading is convenient when the OTA is upgraded.
In order not to affect compatibility in subsequent version upgrade and to distinguish different versions, the version number iteration rule may be as follows:
a. when the release application software version is compatible with BootLoader, only the primary and secondary sub-version numbers (maximum 255) in the software version information are increased.
b. When the release application software version is not compatible with BootLoader, the major version number in the software version information is increased (max 65535).
c. When the release profile version is compatible with the application software, only the primary and secondary sub-version numbers (255 max) of the profile are increased.
d. When the release profile version is not compatible with the application software, the major version number in the profile version information is increased (max 65535).
e. When the modified hardware is compatible with the application software, only the primary and secondary sub-version numbers (255 max) in the hardware version are increased.
h. When the modified hardware is not compatible with the application software, the major version number in the hardware version information is increased (maximum 65535).
If the hardware version information of the shared storage area is all 0, the hardware version information of the shared storage area can pass through by default in verification, and the hardware version information of the shared storage area can be written into the flash shared storage area by an EOL instruction in production. In general, bootLoader updating requires a special method, and is fixed after production is completed.
After the vehicle downloads the upgrade data packet, the upgrade data packet may be parsed, CRC information may be extracted from the APP_version_info_header or the config_file_version_info_header, and CRC check may be performed. After the CRC check passes, the target upgrade type may be determined.
When the software package is upgraded alone, the following information can be extracted for compatibility verification:
extracting information such as OEM_name, project_name and vehicle model from a software Version file APP_version_info_header as product verification information, extracting information such as a vehicle name, a project name and a vehicle type from a boot loader BootLoader at a vehicle end as product reference information corresponding to the product verification information, and comparing the product verification information with the product reference information;
Extracting the first 4bytes of application Version information from the software Version file app_version_info_header: SW Part Number and main Version as software verification information, extracting Supported application Version information from the vehicle side BootLoader: SW Part Number and main Version are used as software reference information corresponding to the software verification information, and the software verification information is compared with the software reference information;
extracting the first 4bytes of required hardware Version info from the software Version file app_version_info_header: HW Part Number and main Version are used as hardware verification information, hardware Version info is extracted from a shared storage area of a vehicle end and used as hardware reference information corresponding to the hardware verification information, and the hardware verification information is compared with the hardware reference information;
extracting the first 4bytes of Supported Config file Version info from the software Version file app_version_info_header: config file Part Number and main Version, as configuration verification information, extract the first 4bytes in config file Version info from the configuration file config_file_version_info_header currently existing at the vehicle end as configuration reference information corresponding to the configuration verification information, and compare the configuration verification information with the configuration reference information.
When the configuration file is upgraded alone, the following information can be extracted for compatibility verification:
extracting information such as OEM_name, project_name and vehicle model from a Version configuration file config_file_version_info_header to serve as product verification information, extracting information such as a vehicle factory name, a project name and a vehicle type from a BootLoader at a vehicle end to serve as product reference information corresponding to the product verification information, and comparing the product verification information with the product reference information;
the first 4bytes of required hardware Version info are extracted from the Version profile config_file_version_info_header: HW Part Number and main Version are used as hardware verification information, hardware Version info is extracted from a shared storage area of a vehicle end and used as hardware reference information corresponding to the hardware verification information, and the hardware verification information is compared with the hardware reference information;
the first 4bytes of config file Version info are extracted from the Version profile config_file_version_info_header: config file Part Number and main Version as configuration verification information, extracting the first 4bytes in Supported config_ file Version info from a software Version file APP_version_info_header currently existing at the vehicle end as configuration reference information corresponding to the configuration verification information, and comparing the configuration verification information with the configuration reference information.
When the software package and the configuration file are upgraded simultaneously, the following information can be extracted for compatibility verification:
extracting information such as OEM_name, project_name and vehicle model from a software Version file APP_version_info_header as product verification information; extracting information such as OEM_name, project_name and vecile model from a Version configuration file config_file_version_info_header as product verification information; extracting information such as a vehicle factory name, a project name, a vehicle type and the like from a BootLoader at a vehicle end as product reference information corresponding to the product verification information, and comparing the product verification information with the product reference information;
extracting the first 4bytes of application Version information from the software Version file app_version_info_header: SW Part Number and main Version as software verification information, extracting Supported application Version information from the vehicle side BootLoader: SW Part Number and main Version are used as software reference information corresponding to the software verification information, and the software verification information is compared with the software reference information;
extracting the first 4bytes of required hardware Version info from the software Version file app_version_info_header: HW Part Number and main Version as hardware verification information; the first 4bytes of required hardware Version info are extracted from the Version profile config_file_version_info_header: HW Part Number and main Version as hardware verification information; extracting hardware version info from a shared storage area of a vehicle end as hardware reference information corresponding to the hardware verification information, and comparing the hardware verification information with the hardware reference information;
Extracting the first 4bytes of Supported Config file Version info from the software Version file app_version_info_header: config file Part Number and main Version as configuration verification information; the first 4bytes of config file Version info are extracted from the Version profile config_file_version_info_header: config file Part Number and main Version are used as configuration verification information, and the two sets of configuration verification information are respectively used as reference information of each other for comparison.
If the information is consistent in comparison, the compatibility of the upgrade data packet can be indicated to pass; otherwise, the compatibility verification may be considered to fail.
According to the embodiment of the invention, the target upgrading type is determined by analyzing the upgrading data packet; extracting compatibility verification information corresponding to the target upgrading type from the upgrading data packet, and determining reference information corresponding to the compatibility verification information, wherein the compatibility verification information comprises product verification information, software verification information, hardware verification information and/or configuration verification information; comparing the corresponding compatibility verification information with the reference information to obtain a compatibility verification result, wherein the compatibility verification result comprises that the compatibility verification passes and fails; when the compatibility verification result is that the compatibility verification is passed, OTA upgrading is completed based on the upgrading data packet, so that the problems that when a vehicle is in OTA upgrading, the vehicle ECU is suspended due to incompatibility among upgrading software, configuration files and hardware, the ECU needs to be replaced again and manpower and material resources are wasted are solved, compatibility detection is carried out on the vehicle end among the upgrading software, the configuration files and the vehicle hardware, and effective upgrading of the vehicle end software is ensured.
Example two
Fig. 2 is a schematic structural diagram of an OTA upgrading device according to a second embodiment of the present invention. As shown in fig. 2, the apparatus includes:
the upgrade type determining module 210 is configured to parse the upgrade data packet to determine a target upgrade type.
The verification information extraction module 220 is configured to extract compatibility verification information corresponding to the target upgrade type from the upgrade data packet, and determine reference information corresponding to the compatibility verification information, where the compatibility verification information includes product verification information, software verification information, hardware verification information, and/or configuration verification information.
The verification information comparison module 230 is configured to compare the corresponding compatibility verification information with the reference information to obtain a compatibility verification result, where the compatibility verification result includes that the compatibility verification passes and that the compatibility verification fails.
And the OTA upgrade module 240 is configured to complete OTA upgrade based on the upgrade data packet when the compatibility verification result is that the compatibility verification is passed.
Optionally, the target upgrade type includes a software upgrade, a configuration file upgrade, and a software configuration simultaneous upgrade.
Optionally, the verification information extracting module 220 includes:
The first information extraction unit is used for extracting compatibility verification information from a software version file of the upgrading data packet when the target upgrading type is software upgrading, and determining reference information corresponding to the compatibility verification information from a vehicle end;
the second information extraction unit is used for extracting compatibility verification information from a version configuration file of the upgrade data packet when the target upgrade type is configuration file upgrade, and determining reference information corresponding to the compatibility verification information from a vehicle end;
and the third information extraction unit is used for extracting compatibility verification information from the software version file and the version configuration file of the upgrade data packet when the target upgrade type is the software configuration and upgrade at the same time, and determining reference information corresponding to the compatibility verification information which cannot be matched and verified from a vehicle side.
Optionally, the first information extraction unit is specifically configured to:
extracting product basic information from a software version file of the upgrade data packet as product verification information, and determining product reference information corresponding to the product verification information from a boot loader of a vehicle end;
extracting software version information from a software version file of the upgrading data packet as software verification information, and determining software reference information corresponding to the software verification information from a boot loader of a vehicle end;
Extracting hardware version information from a software version file of the upgrade data packet as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of a vehicle side;
and extracting configuration version information from the software version file of the upgrade data packet as configuration verification information, and determining configuration reference information corresponding to the configuration verification information from the configuration file of the vehicle end.
Optionally, the second information extraction unit is specifically configured to:
extracting product basic information from the version configuration file of the upgrade data packet as product verification information, and determining product reference information corresponding to the product verification information from a boot loader of a vehicle end;
extracting hardware version information from the version configuration file of the upgrade data packet as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of a vehicle side;
and extracting configuration version information from the version configuration file of the upgrade data packet as configuration verification information, and determining configuration reference information corresponding to the configuration verification information from the current software version file of the vehicle end.
Optionally, the third information extraction unit is specifically configured to:
product basic information is extracted from a software version file and a version configuration file of the upgrading data packet respectively to serve as product verification information, and product reference information corresponding to the product verification information is determined from a boot loader of a vehicle end;
extracting hardware version information from a software version file and a version configuration file of the upgrading data packet respectively to serve as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of a vehicle end;
extracting software version information from a software version file of the upgrading data packet as software verification information, and determining software reference information corresponding to the software verification information from a boot loader of a vehicle end;
extracting configuration version information from a software version file of the upgrade data packet as first configuration verification information, extracting configuration version information from a version configuration file of the upgrade data packet as second configuration verification information, taking the first configuration verification information as reference information of the second configuration verification information, and taking the second configuration verification information as reference information of the first configuration verification information.
Optionally, the apparatus further includes a cyclic redundancy check module configured to:
and before comparing the corresponding compatibility verification information with the reference information, performing cyclic redundancy check on the upgrading data packet, and if the cyclic redundancy check does not pass, stopping OTA upgrading operation.
The OTA upgrading device provided by the embodiment of the invention can execute the OTA upgrading method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example III
Fig. 3 shows a schematic structural diagram of a vehicle 10 that may be used to implement an embodiment of the present invention. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 3, the vehicle 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the vehicle 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
Various components in the vehicle 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the vehicle 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunications networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as the OTA upgrade method.
In some embodiments, the OTA upgrade method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the vehicle 10 via the ROM 12 and/or the communication unit 19. One or more of the steps of the OTA upgrade method described above may be performed when the computer program is loaded into RAM 13 and executed by processor 11. Alternatively, in other embodiments, the processor 11 may be configured to perform the OTA upgrade method in any other suitable way (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a vehicle having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or a trackball) by which a user can provide input to the vehicle. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (10)
1. An OTA upgrade method, comprising:
analyzing the upgrade data packet to determine a target upgrade type;
extracting compatibility verification information corresponding to the target upgrading type from the upgrading data packet, and determining reference information corresponding to the compatibility verification information, wherein the compatibility verification information comprises product verification information, software verification information, hardware verification information and/or configuration verification information;
Comparing the corresponding compatibility verification information with the reference information to obtain a compatibility verification result, wherein the compatibility verification result comprises that the compatibility verification passes and fails;
and when the compatibility verification result is that the compatibility verification is passed, finishing OTA upgrading based on the upgrading data packet.
2. The method of claim 1, wherein the step of determining the position of the substrate comprises,
the target upgrade type comprises software upgrade, configuration file upgrade and software configuration simultaneous upgrade.
3. The method according to claim 2, wherein extracting compatibility verification information corresponding to the target upgrade type from the upgrade data packet, and determining reference information corresponding to the compatibility verification information, comprises:
when the target upgrading type is software upgrading, extracting compatibility verification information from a software version file of the upgrading data packet, and determining reference information corresponding to the compatibility verification information from a vehicle end;
when the target upgrading type is configuration file upgrading, extracting compatibility verification information from a version configuration file of the upgrading data packet, and determining reference information corresponding to the compatibility verification information from a vehicle end;
When the target upgrading type is software configuration and is simultaneously upgraded, extracting compatibility verification information from a software version file and a version configuration file of the upgrading data packet, and determining reference information corresponding to the compatibility verification information which cannot be matched and verified from a vehicle side.
4. The method of claim 3, wherein the extracting compatibility verification information from the software version file of the upgrade data packet and determining the reference information corresponding to the compatibility verification information from the vehicle side includes:
extracting product basic information from a software version file of the upgrade data packet as product verification information, and determining product reference information corresponding to the product verification information from a boot loader of a vehicle end;
extracting software version information from a software version file of the upgrading data packet as software verification information, and determining software reference information corresponding to the software verification information from a boot loader of a vehicle end;
extracting hardware version information from a software version file of the upgrade data packet as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of a vehicle side;
And extracting configuration version information from the software version file of the upgrade data packet as configuration verification information, and determining configuration reference information corresponding to the configuration verification information from the configuration file of the vehicle end.
5. The method of claim 3, wherein the extracting compatibility verification information from the version configuration file of the upgrade data packet and determining the reference information corresponding to the compatibility verification information from the vehicle side include:
extracting product basic information from the version configuration file of the upgrade data packet as product verification information, and determining product reference information corresponding to the product verification information from a boot loader of a vehicle end;
extracting hardware version information from the version configuration file of the upgrade data packet as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of a vehicle side;
and extracting configuration version information from the version configuration file of the upgrade data packet as configuration verification information, and determining configuration reference information corresponding to the configuration verification information from the current software version file of the vehicle end.
6. The method of claim 3, wherein extracting compatibility verification information from the software version file and the version configuration file of the upgrade data package, and determining, from the vehicle side, reference information corresponding to the compatibility verification information that cannot be matched for verification, comprises:
Product basic information is extracted from a software version file and a version configuration file of the upgrading data packet respectively to serve as product verification information, and product reference information corresponding to the product verification information is determined from a boot loader of a vehicle end;
extracting hardware version information from a software version file and a version configuration file of the upgrading data packet respectively to serve as hardware verification information, and determining hardware reference information corresponding to the hardware verification information from a shared storage area of a vehicle end;
extracting software version information from a software version file of the upgrading data packet as software verification information, and determining software reference information corresponding to the software verification information from a boot loader of a vehicle end;
extracting configuration version information from a software version file of the upgrade data packet as first configuration verification information, extracting configuration version information from a version configuration file of the upgrade data packet as second configuration verification information, taking the first configuration verification information as reference information of the second configuration verification information, and taking the second configuration verification information as reference information of the first configuration verification information.
7. The method of claim 1, further comprising, prior to extracting compatibility verification information corresponding to the target upgrade type from the upgrade data package:
And performing cyclic redundancy check on the upgrading data packet, and stopping OTA upgrading operation if the cyclic redundancy check does not pass.
8. An OTA upgrading device, comprising:
the upgrade type determining module is used for analyzing the upgrade data packet and determining a target upgrade type;
the verification information extraction module is used for extracting compatibility verification information corresponding to the target upgrading type from the upgrading data packet and determining reference information corresponding to the compatibility verification information, wherein the compatibility verification information comprises product verification information, software verification information, hardware verification information and/or configuration verification information;
the verification information comparison module is used for comparing the corresponding compatibility verification information with the reference information to obtain a compatibility verification result, wherein the compatibility verification result comprises that the compatibility verification passes and fails;
and the OTA upgrading module is used for finishing OTA upgrading based on the upgrading data packet when the compatibility verification result is that the compatibility verification is passed.
9. A vehicle, characterized in that the vehicle comprises:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
The memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the OTA upgrade method of any one of claims 1-7.
10. A computer readable storage medium storing computer instructions for causing a processor to perform the OTA upgrade method of any one of claims 1-7 when executed.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310721972.9A CN116594657A (en) | 2023-06-16 | 2023-06-16 | OTA upgrading method and device, vehicle and storage medium |
| PCT/CN2023/141357 WO2024255194A1 (en) | 2023-06-16 | 2023-12-25 | Ota update method and apparatus, electronic device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310721972.9A CN116594657A (en) | 2023-06-16 | 2023-06-16 | OTA upgrading method and device, vehicle and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116594657A true CN116594657A (en) | 2023-08-15 |
Family
ID=87608340
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310721972.9A Pending CN116594657A (en) | 2023-06-16 | 2023-06-16 | OTA upgrading method and device, vehicle and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN116594657A (en) |
| WO (1) | WO2024255194A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118034740A (en) * | 2024-03-04 | 2024-05-14 | 北京铭企国际科技集团有限公司 | A remote upgrade method for power consumption information management terminal |
| WO2024255194A1 (en) * | 2023-06-16 | 2024-12-19 | 惠州市德赛西威汽车电子股份有限公司 | Ota update method and apparatus, electronic device, and storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7640423B2 (en) * | 2005-02-14 | 2009-12-29 | Red Hat, Inc. | System and method for verifying compatibility of computer equipment with a software product |
| CN114116459A (en) * | 2021-11-05 | 2022-03-01 | 浙江吉利控股集团有限公司 | Software compatibility verification method and computer-readable storage medium |
| CN114915554B (en) * | 2022-04-08 | 2024-03-19 | 一汽解放汽车有限公司 | Remote upgrade method, device, computer equipment and storage medium |
| CN115373710A (en) * | 2022-08-23 | 2022-11-22 | 重庆长安汽车股份有限公司 | Vehicle OTA upgrade control method and device, vehicle and storage medium |
| CN116594657A (en) * | 2023-06-16 | 2023-08-15 | 惠州市德赛西威汽车电子股份有限公司 | OTA upgrading method and device, vehicle and storage medium |
-
2023
- 2023-06-16 CN CN202310721972.9A patent/CN116594657A/en active Pending
- 2023-12-25 WO PCT/CN2023/141357 patent/WO2024255194A1/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024255194A1 (en) * | 2023-06-16 | 2024-12-19 | 惠州市德赛西威汽车电子股份有限公司 | Ota update method and apparatus, electronic device, and storage medium |
| CN118034740A (en) * | 2024-03-04 | 2024-05-14 | 北京铭企国际科技集团有限公司 | A remote upgrade method for power consumption information management terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024255194A1 (en) | 2024-12-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114064208B (en) | Method, device, electronic device and storage medium for detecting application service status | |
| CN109510742B (en) | Server network card remote test method, device, terminal and storage medium | |
| US10042744B2 (en) | Adopting an existing automation script to a new framework | |
| US20120191963A1 (en) | BIOS Updating System, BIOS Updating Method, and Related Computer Program Product | |
| CN116594657A (en) | OTA upgrading method and device, vehicle and storage medium | |
| CN110554938B (en) | BIOS (basic input output System) testing method, system, terminal and storage medium based on script set | |
| CN103970564A (en) | Automatic repairing and upgrading method of embedded operating system and embedded operating system with automatic repairing and upgrading functions | |
| CN115794257B (en) | System starting method, device, electronic equipment and storage medium | |
| CN109814877A (en) | Project deployment method and device based on environmental management | |
| CN106843947B (en) | Method and device for processing code defects | |
| CN111629200A (en) | A method, device and readable storage medium for rapidly detecting the reliability of differential packets | |
| CN109032873A (en) | A kind of server delivery detection method and device | |
| CN111090537B (en) | Cluster starting method and device, electronic equipment and readable storage medium | |
| CN113434353A (en) | Server testing method and device, electronic equipment and storage medium | |
| CN109582334B (en) | Upgrading method and device for programmable logic device | |
| CN113656322B (en) | Data processing method, device, electronic equipment and computer storage medium | |
| CN112328288A (en) | Method, system, equipment and storage medium for updating server component | |
| CN117008837A (en) | Partition mounting method, device and equipment of magnetic disk and storage medium | |
| CN115373901A (en) | Terminal data recovery method, device, equipment and storage medium | |
| CN115237441A (en) | A cloud platform-based upgrade testing method, device and medium | |
| CN117520080B (en) | Server testing method, device, equipment and medium | |
| CN112817620A (en) | Controller terminal program updating method, device, computer equipment and storage medium | |
| CN113472611A (en) | Method and device for acquiring WiFi signal strength and readable storage medium | |
| CN116303074B (en) | A server testing method, device, equipment and medium | |
| CN112994907A (en) | Network configuration method and device of virtual machine, storage medium and equipment |
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 |