CN117075939A - Controller list management method and system for vehicle OTA upgrade - Google Patents
Controller list management method and system for vehicle OTA upgrade Download PDFInfo
- Publication number
- CN117075939A CN117075939A CN202311039285.5A CN202311039285A CN117075939A CN 117075939 A CN117075939 A CN 117075939A CN 202311039285 A CN202311039285 A CN 202311039285A CN 117075939 A CN117075939 A CN 117075939A
- Authority
- CN
- China
- Prior art keywords
- controller
- information
- software
- ota
- controller information
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 39
- 238000000034 method Methods 0.000 claims abstract description 26
- 238000012795 verification Methods 0.000 claims description 55
- 230000010354 integration Effects 0.000 claims description 6
- 230000008569 process Effects 0.000 abstract description 9
- 238000013461 design Methods 0.000 description 6
- 230000007547 defect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the field of intelligent vehicle upgrading, and discloses a controller list management method and system for vehicle OTA upgrading, wherein the method comprises the following steps: s1: checking whether a controller information list exists after the vehicle is powered on; s2: information reading is carried out on a controller of the intelligent OS system and a controller of the micro-controller unit; s3: carrying out validity check on the read controller information according to the controller information list; s4: recording the verified controller information in a controller information list; s5: integrating the trusted information item and the verified controller information into a software and hardware part number and software and hardware version number information set of the OTA upgrade controller; s6: and uploading the software and hardware part number and the software and hardware version number information set to the OTA cloud. The invention solves the problem that the controller information can not be obtained correctly during OTA upgrading in the prior art, and has the characteristics of reducing the upgrading failure probability and repeated upgrading time in the whole vehicle upgrading process and improving the user experience.
Description
Technical Field
The invention relates to the field of intelligent upgrading of vehicles, in particular to a method and a system for managing a controller list for upgrading an OTA (over the air) of a vehicle.
Background
In recent years, the use of the automobile OTA technology is more and more frequent, and more controllers need to be upgraded by using the OTA technology, and each controller needs to manage and use more controller information, such as software and hardware part numbers, software and hardware versions, boot version numbers, calibration version numbers and the like. In the process of OTA upgrading, the controller information is required to be used for acquiring an upgrading task and a software upgrading packet from the OTA cloud.
Because the magnitude of the controller information which needs to be subjected to OTA upgrading is increased, when the controller information of the whole vehicle OTA is read, the probability of failure in reading is increased gradually, so that the controller information is not read in response, the controller information is wrong, the controller information is partially lost, the validity of the information cannot be checked, and the controller information and the OTA cloud can not be normally compared and OTA upgrading tasks can not be obtained.
From the phenomenon of upgrading a certain large version of the whole vehicle, the following problems are caused because part of OTA controllers cannot acquire OTA upgrading tasks: 1. multiple associated or wanted controllers under the same large version cannot be upgraded or successively upgraded due to the dependence of the multiple controllers on the same large version, so that a major software defect occurs in the system; 2. some controllers which wish to be able to succeed in the current large-version OTA upgrade fail, so that significant software defects of part of controllers in the last large version cannot be repaired, which does not meet the requirements of developers and users; 3. the information management of the vehicle OTA controller is confused, and then an error software upgrading packet is obtained from the OTA server, so that the controller cannot be upgraded into a correct software version all the time.
Most of vehicle OTA upgrades in the market at present are all identified and acquired tasks through software and hardware part numbers and software and hardware version numbers of controllers, a small number of patents are optimally managed by using simple list information, but the problems of the hardware and the software upgrading method are that the controller information can not be acquired through the hundred percent of assurance, validity check is not carried out on the read controller information, correctness and validity of the controller information can not be guaranteed through the hundred percent of recording of the read controller information, the probability of success of the read information is increased through the multiple times of reading at present, and the probability of failure is still very large, so that the upgrading times are increased, and the automatic upgrading recovery cannot be carried out after the upgrading failure. Thereby bringing bad experience to users and reducing user satisfaction.
An existing driving platform OTA upgrading flow control method, system, equipment and medium, the method comprises the following steps: the intelligent driving domain controller acquires the address of the upgrade package based on the central gateway, downloads the OTA upgrade package from the cloud, judges the current vehicle state, and closes the current application message communication of the vehicle; shutting down the vehicle diagnostic trouble code system; performing first verification and decompression on the OTA upgrade package; performing signature verification and second verification on the obtained file; analyzing the obtained script file, extracting and reading data of the script file, and upgrading a sensor program hung under the domain controller in parallel; the plurality of sensors are identified by serial numbers; the sensor programs are all upgraded 1, and the domain controller programs are upgraded; and resetting and updating the domain controller program of the upgrade 1 based on the upgrade activation flag bit of the domain controller program.
However, the problem that the controller information cannot be obtained correctly during the OTA upgrade still exists in the prior art, so how to invent a controller list management method capable of enabling the controller to be upgraded correctly is a technical problem to be solved in the technical field.
Disclosure of Invention
The invention provides a controller list management method and a system for vehicle OTA upgrading, which are used for solving the problem that the controller information cannot be ensured to be correctly acquired during OTA upgrading in the prior art.
In order to achieve the above purpose of the present invention, the following technical scheme is adopted:
a controller inventory management method for vehicle OTA upgrades, comprising the steps of:
s1: checking whether a controller information list exists after the vehicle is electrified, if not, creating the controller information list and then executing the step S2, and if so, directly executing the step S2;
s2: information reading is carried out on a controller of the intelligent OS system and a controller of the microcontroller unit, so that controller information is obtained;
s3: carrying out validity check on the read controller information according to the controller information list;
s4: recording the verified controller information in a controller information list;
s5: extracting a trusted information item of the controller information which does not pass the verification, and integrating the trusted information item and the controller information which passes the verification into a software and hardware part number and a software and hardware version number information set of the OTA upgrading controller;
s6: and uploading the software and hardware part number and the software and hardware version number information set to the OTA cloud.
Preferably, after the software and hardware part number and the software and hardware version number information are assembled and uploaded to the OTA cloud, an upgrade task and a software upgrade package are also obtained from the OTA cloud, and vehicle OTA upgrade is performed through the upgrade task and the software upgrade package.
Further, the controller information list records the controller name, the basic format, the software and hardware part number and format, the software and hardware version number and format, and the reading result of the controller information item.
Further, in the step S3, validity verification is performed on the read controller information, specifically: by comparing the basic format in the controller information list, checking whether the length of the controller information piece number, the special character in the piece number information, the digit corresponding to the number, the digit corresponding to the letter and the distinction of the case letter meet the format requirement.
Further, in the step S3, validity verification is performed on the read software and hardware part number, specifically: and comparing the software and hardware part number formats in the controller information list, and comparing the part number length, special characters in the part number information, the number corresponding to digits, the number corresponding to letters and the distinction of case letters, so as to carry out validity check on the read software and hardware part numbers.
Further, in the step S3, validity verification is performed on the read software and hardware version number, specifically: by comparing the format of the version numbers of the software and hardware in the information list of the controller, the length of the version number of the software, the bit number corresponding to the special character in the version number information, the bit number corresponding to the number, the bit number corresponding to the letter and the distinction of the case letter are compared.
Further, in the step S4, the verified controller information is recorded in the controller information list, specifically:
comparing the verified controller information with the controller information list, if the verified controller information is the same as the information in the controller information list, not replacing the information in the controller information list, and recording that the reading result of the controller information item is 1; if the verified controller information is different from the information in the controller information list, replacing the information in the controller information list with the verified controller information, and recording that the reading result of the controller information item is 1;
and recording the read result of the controller information which fails to pass the verification as 0.
Further, the trusted information item of the controller information which does not pass the verification is extracted, specifically: and searching an information item corresponding to the controller information which does not pass through verification from the controller information list according to the controller name, carrying out trusted verification on the searched information item, and merging the information item which passes through trusted verification into a software and hardware part number and a software and hardware version number information set of the OTA upgrading controller.
Furthermore, the trusted verification of the searched information items comprises the following specific steps:
searching the latest N-M controller information item reading results corresponding to the information searched in the controller information list;
if the last 2 times of reading result is 0, directly judging that the searched information item is not trusted;
if more than or equal to 30% of all the reading results are 0, judging that the searched information item is not trusted;
if the reading result of less than or equal to 20% of all the reading results is 0 and the last 2 times of reading results are not 0, judging that the searched information item is trusted;
if the number of times of reading the controller information item corresponding to the searched information is smaller than N:
if the reading times are less than or equal to 30% N and the reading results are all 1, judging that the searched information item is trusted;
if the number of readings is greater than 30% N and less than or equal to 60% N, and the number of readings is less than or equal to 10% N and is 0, then determining that the searched information item is trusted;
if the number of readings is greater than 60% N and less than or equal to 90% N, and the number of readings is less than or equal to 20% N and is 0, then determining that the searched information item is trusted; otherwise, the searched information item is not trusted.
A controller list management system for vehicle OTA upgrade comprises an initialization module, a reading module, a validity checking module, a recording module, an information integration module and an OTA upgrade module;
the initialization module is used for checking whether a controller information list exists after the vehicle is electrified, if not, the step S2 is executed after the controller information list is created, and if so, the step S2 is directly executed;
the reading module is used for reading information of a controller of the intelligent OS system and a controller of the microcontroller unit to obtain controller information;
the validity checking module is used for checking the validity of the software and hardware part numbers and the software and hardware version numbers of the read controller information;
the recording module is used for recording the verified controller information in the controller information list;
the information integration module is used for extracting a trusted information item of the controller information which does not pass the verification, and integrating the trusted information item and the controller information which passes the verification into a software and hardware part number and a software and hardware version number information set of the OTA upgrading controller;
the OTA upgrading module is used for collecting software and hardware part numbers and software and hardware version number information, uploading the information to the OTA cloud end, obtaining an upgrading task and a software upgrading package, and upgrading the vehicle OTA through the upgrading task and the software upgrading package.
The beneficial effects of the invention are as follows:
the invention discloses a controller list management method for vehicle OTA upgrading. The invention integrates the trusted information item and the verified controller information into the software and hardware part number and the software and hardware version number information set of the OTA upgrading controller by creating the controller information list, verifying the validity of the software and hardware part number and the software and hardware version number of the read controller information and extracting the trusted information item of the controller information which does not pass the verification, thereby solving the problem that the controller information cannot be ensured to be correctly acquired when the OTA is upgraded in the prior art. The invention relates to a vehicle controller information reading management method, a vehicle controller information validity verification method and a vehicle controller information use method in an OTA upgrading process, which can reduce the upgrading failure probability and repeated upgrading time in the whole vehicle upgrading process to a great extent and improve the user experience.
Drawings
Fig. 1 is a flow chart of a method for managing a list of controllers for OTA upgrades of a vehicle according to the present invention.
Fig. 2 is a schematic flow chart of a method for managing a list of controllers for OTA upgrade of a vehicle according to embodiment 2 of the present invention.
Fig. 3 is an exemplary diagram of a complete vehicle OTA controller information list for a controller list management method for OTA upgrade of a vehicle according to the present invention.
Fig. 4 is a flow chart of the controller information reading and storing method for a controller inventory management method for vehicle OTA upgrades of the present invention.
Fig. 5 is a schematic flow chart of a controller list management method for OTA upgrade of a vehicle according to the present invention for acquiring upgrade tasks according to controller information.
Fig. 6 is a flow chart of a controller information item validity check for a controller inventory management method for vehicle OTA upgrades of the present invention.
Fig. 7 is a flow chart of a trusted verification of information items in a controller information list of a controller list management method for OTA upgrades of a vehicle in accordance with the present invention.
Fig. 8 is a system block diagram of a controller inventory management system for vehicle OTA upgrades of the present invention.
Detailed Description
The invention is described in detail below with reference to the drawings and the detailed description.
Example 1
As shown in fig. 1, a controller inventory management method for OTA upgrade of a vehicle includes the following steps:
s1: checking whether a controller information list exists after the vehicle is electrified, if not, creating the controller information list and then executing the step S2, and if so, directly executing the step S2;
s2: information reading is carried out on a controller of the intelligent OS system and a controller of the microcontroller unit, so that controller information is obtained;
s3: carrying out validity check on the read controller information according to the controller information list;
s4: recording the verified controller information in a controller information list;
s5: extracting a trusted information item of the controller information which does not pass the verification, and integrating the trusted information item and the controller information which passes the verification into a software and hardware part number and a software and hardware version number information set of the OTA upgrading controller;
s6: and uploading the software and hardware part number and the software and hardware version number information set to the OTA cloud.
In a specific embodiment, after the software and hardware part number and the software and hardware version number information are assembled and uploaded to the OTA cloud, an upgrade task and a software upgrade package are further obtained from the OTA cloud, and vehicle OTA upgrade is performed through the upgrade task and the software upgrade package.
In this embodiment, the controller information list is shown in fig. 3, where "objName" is a controller name, "hardwareNum" is a hardware part number, "softWareNum" is a software part number, "NumFormat" is a digital format, "hardWVersion" is a hardware version number, "softWVersion" is a software part number, "softWVerFormat" is a software part number format, and "result" is a controller information item reading result.
In a specific embodiment, the controller information list records the controller name, the basic format, the software and hardware part number and format, the software and hardware version number and format, and the reading result of the controller information item.
In this embodiment, for the software part number: 9212201-DY01, its corresponding controller inventory format is: 1111111-AA11, wherein:
the exemplary piece number is fixed in length, then the piece number length is checked first; the first 7 bits and the last 2 bits are digital, so that when checking, the number of bits is responded to the part number to be checked, and the ascll code is required to be checked to be between 0 and 9; letters; special characters;
example 2
More specifically, as shown in fig. 2, the present controller list management method for OTA upgrade of a vehicle is implemented by a master control on a local vehicle; the main control is in wireless connection with the OTA cloud server through an MQTT/HTTPS protocol; the main control comprises an OS which is connected with the MCU and the OS through a private protocol.
In this embodiment, the OS is a controller of the intelligent OS system, the MCU is a microcontroller unit, and the OTA cloud server is used as a controller software upgrade package and a task information warehouse management platform, and is responsible for pushing an upgrade task and a software upgrade package downward;
in this embodiment, the master control reads the software and hardware part number and the software and hardware version number of the MCU controller by reading the OS system file information or by a diagnostic command;
in this embodiment, the MCU is an FBL controller.
In this embodiment, the master control is configured to centrally control the entire OTA upgrade procedure, including reading the controller information downward, obtaining an upgrade task and a software upgrade package from the OTA server, managing a controller information manifest file, checking the controller information, and so on;
in a specific embodiment, the controller information list records the controller name, the basic format, the software and hardware part number and format, the software and hardware version number and format, and the reading result of the controller information item.
In the embodiment, the main control obtains an upgrade task from the OTA server through the software and hardware part number and the software and hardware version number of the controller;
in this embodiment, in the method for managing a controller list for OTA upgrade of a vehicle, a local vehicle generates, creates and manages a controller information list, and records the controller name, the software and hardware part number and format, the software and hardware version number and format, and the result of 10 times of reading of the controller information.
In a specific embodiment, as shown in fig. 6, in the step S3, validity verification is performed on the read controller information, specifically: by comparing the basic format in the controller information list, checking whether the length of the controller information piece number, the special character in the piece number information, the digit corresponding to the number, the digit corresponding to the letter and the distinction of the case letter meet the format requirement.
In a specific embodiment, in the step S3, validity verification is performed on the read software and hardware part number, which specifically includes: and comparing the software and hardware part number formats in the controller information list, and comparing the part number length, special characters in the part number information, the number corresponding to digits, the number corresponding to letters and the distinction of case letters, so as to carry out validity check on the read software and hardware part numbers.
In a specific embodiment, in the step S3, validity verification is performed on the read software and hardware version number, which specifically includes: by comparing the format of the version numbers of the software and hardware in the information list of the controller, the length of the version number of the software, the bit number corresponding to the special character in the version number information, the bit number corresponding to the number, the bit number corresponding to the letter and the distinction of the case letter are compared.
As shown in fig. 4, for the controller information, first, whether the local vehicle has a controller information list is judged, and a list is created; receiving information of the finishing controller, and checking the validity of the read software and hardware part numbers; in a specific embodiment, in the step S4, the verified controller information is recorded in the controller information list, specifically:
comparing the verified controller information with the controller information list, if the verified controller information is the same as the information in the controller information list, not replacing the information in the controller information list, and recording that the reading result of the controller information item is 1; if the verified controller information is different from the information in the controller information list, replacing the information in the controller information list with the verified controller information, and recording that the reading result of the controller information item is 1;
and recording the read result of the controller information which fails to pass the verification as 0.
In a specific embodiment, the trusted information item of the controller information which does not pass the verification is extracted, specifically: and searching an information item corresponding to the controller information which does not pass through verification from the controller information list according to the controller name, carrying out trusted verification on the searched information item, and merging the information item which passes through trusted verification into a software and hardware part number and a software and hardware version number information set of the OTA upgrading controller.
In a specific embodiment, as shown in fig. 7, the trusted verification is performed on the searched information item, and the specific steps are as follows:
searching the latest 10 controller information item reading results corresponding to the information searched in the controller information list;
if the last 2 times of reading result is 0, directly judging that the searched information item is not trusted;
if the reading result which is more than or equal to 3 in all the reading results is 0, judging that the searched information item is not trusted;
if the reading result less than or equal to 2 in all the reading results is 0 and the last 2 reading results are not 0, judging that the searched information item is trusted;
in this embodiment, the latest ten version information collection results are "result"; recording all collected results, such as 1110110101, wherein '1' represents that one version information reading is successful, and '0' represents that one version information reading is failed, and the number of bits in the results corresponds to the number of times; whether the information item in the controller information list is valid or not is indicated by using a 'verValid', false is not trusted, and true is trusted;
in a specific embodiment, if the number of readings of the controller information item corresponding to the found information is less than n=10:
if the reading times are less than or equal to 3 and the reading results are all 1, judging that the searched information item is trusted;
if the reading times are less than or equal to 6 and the reading result is less than or equal to 1 time and is 0, the searched information item is judged to be trustable;
if the reading times are less than or equal to 9 and the reading result is less than or equal to 2 times and is 0, the searched information item is judged to be trustable; otherwise, the searched information item is not trusted.
In this embodiment, the trusted verification rule is as shown in table 1:
TABLE 1
In this embodiment, as shown in fig. 5, the process of acquiring the upgrade task according to the controller information is as follows:
initiating a controller information collection request;
finishing controller information;
checking controller information;
if the verification is passed, the controller information is directly integrated into the controller information set;
if the verification is not passed, the corresponding information item in the controller information list is searched, whether the information item is trusted or not is judged, if the information item is trusted, the part number and the version information in the controller information use list are integrated into the controller information set, the controller information set is uploaded to the object information with response to the OTA server, and the upgrading task is acquired.
The invention discloses a controller list management method for vehicle OTA (over the air) upgrading, which relates to vehicle controller information reading management, vehicle controller information validity verification and a using method of vehicle controller information in the OTA upgrading process; the management method disclosed by the invention solves the system defects that the upgrade task and the software upgrade package cannot be normally acquired from the cloud because of abnormality, the information of the single read controller is not responded, or the information format of the read controller is wrong, or the information of part of the controller is lost when the application is invalid, so that the upgrade of a large version fails or the upgrade cannot be completely performed.
The invention provides a controller list management design method for vehicle OTA upgrading, which is suitable for vehicles with OTA technology, can obviously reduce the failure probability of vehicle upgrading and the time of vehicle upgrading, and improves the satisfaction of users.
The invention relates to a controller list management method for vehicle OTA upgrade, which designs a controller information list, wherein the list comprises software and hardware part numbers, format examples of the part numbers and the part numbers, and a result of reading the controller information for many times;
the invention designs a format validity checking method of controller information, which prevents the situation that the updating is failed for many times and the controller is not recovered due to the fact that the updating task is not obtained or the task which does not belong to the current software part number controller is obtained because the new controller information is read in a format error, the information belongs to other controllers and the information is incomplete;
the invention discloses a controller list management method for vehicle OTA upgrading, which designs a list information trustworthiness verification method and prevents the failure of acquiring OTA upgrading tasks caused by the fact that the existing controller information in a read list file is not trusted.
Example 3
As shown in fig. 8, a controller list management system for OTA upgrade of a vehicle includes an initialization module, a reading module, a validity checking module, a recording module, an information integration module, and an OTA upgrade module;
the initialization module is used for checking whether a controller information list exists after the vehicle is electrified, if not, the step S2 is executed after the controller information list is created, and if so, the step S2 is directly executed;
the reading module is used for reading information of a controller of the intelligent OS system and a controller of the microcontroller unit to obtain controller information;
the validity checking module is used for checking the validity of the software and hardware part numbers and the software and hardware version numbers of the read controller information;
the recording module is used for recording the verified controller information in the controller information list;
the information integration module is used for extracting a trusted information item of the controller information which does not pass the verification, and integrating the trusted information item and the controller information which passes the verification into a software and hardware part number and a software and hardware version number information set of the OTA upgrading controller;
the OTA upgrading module is used for uploading the software and hardware part number and the software and hardware version number information set to the OTA cloud.
In the OTA upgrading process, the controller information is read to acquire an OTA upgrading task and a controller software upgrading package, the controller list management system for vehicle OTA upgrading can conduct validity verification on the read controller information, if the controller list management system is invalid or has no corresponding condition, the controller list management system can use the effective controller information instead of the effective controller information, and conduct trusted verification on the existing controller information.
Some designs existing in the market at present also have some modes of using a vehicle to a table to manage, and more are the whole vehicle controller information, but in the processes of acquiring tasks and OTA upgrading, better use is not carried out on the information in the current list, validity verification is not carried out on the newly read controller information, and trusted verification is not carried out on the existing controller information.
The invention is suitable for the technical field of vehicle OTA, adds two verification designs for controller information, and is more used in the functions of closed loop requirement for OTA upgrading, thereby increasing the control degree of the controller information, reducing more possible OTA upgrading problems, greatly reducing systematic errors caused by OTA upgrading and greatly increasing the satisfaction degree of users.
The invention is applicable to all OTA upgrading processes of using controller information to obtain upgrading tasks and software upgrading.
It is to be understood that the above examples of the present invention are provided by way of illustration only and not by way of limitation of the embodiments of the present invention. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the invention are desired to be protected by the following claims.
Claims (10)
1. A controller inventory management method for vehicle OTA upgrades, characterized by: the method comprises the following steps:
s1: checking whether a controller information list exists after the vehicle is electrified, if not, creating the controller information list and then executing the step S2, and if so, directly executing the step S2;
s2: information reading is carried out on a controller of the intelligent OS system and a controller of the microcontroller unit, so that controller information is obtained;
s3: carrying out validity check on the read controller information according to the controller information list;
s4: recording the verified controller information in a controller information list;
s5: extracting a trusted information item of the controller information which does not pass the verification, and integrating the trusted information item and the controller information which passes the verification into a software and hardware part number and a software and hardware version number information set of the OTA upgrading controller;
s6: and uploading the software and hardware part number and the software and hardware version number information set to the OTA cloud.
2. The controller inventory management method for vehicle OTA upgrades of claim 1, wherein: and after the software and hardware part number and the software and hardware version number information are assembled and uploaded to the OTA cloud, an upgrade task and a software upgrade package are also obtained from the OTA cloud, and vehicle OTA upgrade is carried out through the upgrade task and the software upgrade package.
3. The controller inventory management method for vehicle OTA upgrades of claim 1, wherein: the controller information list records the controller name, the basic format, the software and hardware part number and format, the software and hardware version number and format and the reading result of the controller information item.
4. The controller inventory management method for vehicle OTA upgrades of claim 3, wherein: in the step S3, validity verification is performed on the read controller information, specifically: by comparing the basic format in the controller information list, checking whether the length of the controller information piece number, the special character in the piece number information, the digit corresponding to the number, the digit corresponding to the letter and the distinction of the case letter meet the format requirement.
5. The controller inventory management method for vehicle OTA upgrades of claim 3, wherein: in the step S3, validity verification is further performed on the read software and hardware part number, specifically: and comparing the software and hardware part number formats in the controller information list, and comparing the part number length, special characters in the part number information, the number corresponding to digits, the number corresponding to letters and the distinction of case letters, so as to carry out validity check on the read software and hardware part numbers.
6. The controller inventory management method for vehicle OTA upgrades of claim 3, wherein: in the step S3, validity verification is further performed on the read software and hardware version number, specifically: by comparing the format of the version numbers of the software and hardware in the information list of the controller, the length of the version number of the software, the bit number corresponding to the special character in the version number information, the bit number corresponding to the number, the bit number corresponding to the letter and the distinction of the case letter are compared.
7. The controller inventory management method for vehicle OTA upgrades of claim 3, wherein: in the step S4, the verified controller information is recorded in the controller information list, specifically:
comparing the verified controller information with the controller information list, if the verified controller information is the same as the information in the controller information list, not replacing the information in the controller information list, and recording that the reading result of the controller information item is 1; if the verified controller information is different from the information in the controller information list, replacing the information in the controller information list with the verified controller information, and recording that the reading result of the controller information item is 1;
and recording the read result of the controller information which fails to pass the verification as 0.
8. The controller inventory management method for vehicle OTA upgrades of claim 7, wherein: the trusted information item of the controller information which does not pass the verification is extracted, specifically: and searching an information item corresponding to the controller information which does not pass through verification from the controller information list according to the controller name, carrying out trusted verification on the searched information item, and merging the information item which passes through trusted verification into a software and hardware part number and a software and hardware version number information set of the OTA upgrading controller.
9. The controller inventory management method for vehicle OTA upgrades of claim 8, wherein: the trusted verification of the searched information items comprises the following specific steps:
searching the latest N-M controller information item reading results corresponding to the information searched in the controller information list;
if the last 2 times of reading result is 0, directly judging that the searched information item is not trusted;
if more than or equal to 30% of all the reading results are 0, judging that the searched information item is not trusted;
if the reading result of less than or equal to 20% of all the reading results is 0 and the last 2 times of reading results are not 0, judging that the searched information item is trusted;
if the number of times of reading the controller information item corresponding to the searched information is smaller than N:
if the reading times are less than or equal to 30% N and the reading results are all 1, judging that the searched information item is trusted;
if the number of readings is greater than 30% N and less than or equal to 60% N, and the number of readings is less than or equal to 10% N and is 0, then determining that the searched information item is trusted;
if the number of readings is greater than 60% N and less than or equal to 90% N, and the number of readings is less than or equal to 20% N and is 0, then determining that the searched information item is trusted; otherwise, the searched information item is not trusted.
10. A controller inventory management system for vehicle OTA upgrades, characterized by: the system comprises an initialization module, a reading module, a validity checking module, a recording module and an information integration module;
the initialization module is used for checking whether a controller information list exists after the vehicle is electrified, if not, the step S2 is executed after the controller information list is created, and if so, the step S2 is directly executed;
the reading module is used for reading information of a controller of the intelligent OS system and a controller of the microcontroller unit to obtain controller information;
the validity checking module is used for checking the validity of the software and hardware part numbers and the software and hardware version numbers of the read controller information;
the recording module is used for recording the verified controller information in the controller information list;
the information integration module is used for extracting a trusted information item of the controller information which does not pass the verification, and integrating the trusted information item and the controller information which passes the verification into a software and hardware part number and a software and hardware version number information set of the OTA upgrading controller;
the OTA upgrading module is used for uploading the software and hardware part number and the software and hardware version number information set to the OTA cloud.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311039285.5A CN117075939A (en) | 2023-08-17 | 2023-08-17 | Controller list management method and system for vehicle OTA upgrade |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311039285.5A CN117075939A (en) | 2023-08-17 | 2023-08-17 | Controller list management method and system for vehicle OTA upgrade |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117075939A true CN117075939A (en) | 2023-11-17 |
Family
ID=88703666
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311039285.5A Pending CN117075939A (en) | 2023-08-17 | 2023-08-17 | Controller list management method and system for vehicle OTA upgrade |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117075939A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117472035A (en) * | 2023-12-27 | 2024-01-30 | 东方电气风电股份有限公司 | Verification method for software and hardware of main control system |
-
2023
- 2023-08-17 CN CN202311039285.5A patent/CN117075939A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117472035A (en) * | 2023-12-27 | 2024-01-30 | 东方电气风电股份有限公司 | Verification method for software and hardware of main control system |
| CN117472035B (en) * | 2023-12-27 | 2024-03-08 | 东方电气风电股份有限公司 | Verification method for software and hardware of main control system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106843957B (en) | System firmware upgrading method and device | |
| EP1770512A2 (en) | Method and system for updating software | |
| CN117075939A (en) | Controller list management method and system for vehicle OTA upgrade | |
| CN112328294A (en) | OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) | |
| CN110007941B (en) | MCU firmware and upgrading method of intelligent garbage classification recycling system | |
| CN103188668A (en) | Security protection method and security protection system for mobile terminal application | |
| US20100106784A1 (en) | Electronic device with automatic software update function and method thereof | |
| CN105512044A (en) | Method and system for updating object base used for keyword drive test | |
| CN108108193A (en) | A kind of easy-to-use firmware upgrade method of safety and system | |
| CN111813436B (en) | Method and system for updating configuration files in batch | |
| CN117391099B (en) | Data downloading and checking method and system for smart card and storage medium | |
| CN103365684B (en) | Updating method and multi-domain embedded system | |
| US20220035621A1 (en) | Software query information management system and software query information management method | |
| KR20080083512A (en) | Firmware over the air system | |
| Shi et al. | A vehicle electric control unit over-the-air reprogramming system | |
| CN104182416A (en) | File downloading system and method | |
| CN116820528A (en) | Firmware version upgrading method and device, chip and electronic equipment | |
| CN111538542A (en) | System configuration method and related device | |
| CN110795129A (en) | Data flashing method, device and equipment | |
| CN107247904B (en) | Safety baseline item synchronization method and device | |
| CN108572948B (en) | Doorplate information processing method and device | |
| CN113592109B (en) | Method, system, device and storage medium for binding vehicle-mounted terminal and vehicle networking platform | |
| CN115168217A (en) | Defect discovery method and device for source code file | |
| CN114691174A (en) | Vehicle-mounted software upgrading method, device and equipment | |
| CN112527565A (en) | Data recovery method based on big data and cloud computing and big data service platform |
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 |