CN111614765A - Vehicle OTA (over the air) upgrading method and system - Google Patents
Vehicle OTA (over the air) upgrading method and system Download PDFInfo
- Publication number
- CN111614765A CN111614765A CN202010441209.7A CN202010441209A CN111614765A CN 111614765 A CN111614765 A CN 111614765A CN 202010441209 A CN202010441209 A CN 202010441209A CN 111614765 A CN111614765 A CN 111614765A
- Authority
- CN
- China
- Prior art keywords
- task
- upgrading
- cloud
- vehicle
- version number
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Abstract
In the vehicle end step, after the parts to be upgraded are upgraded, the upgraded version number is compared with the version number acquired from the task, if the version numbers are consistent, the upgrading is successful, otherwise, the upgrading is failed. The invention can avoid the problem that the task which is successfully upgraded is triggered again.
Description
Technical Field
The invention relates to the technical field of OTA (over the air) upgrading, in particular to a vehicle OTA upgrading method and a vehicle OTA upgrading system.
Background
At present, in the field of automobiles, electromotion, intellectualization, networking and sharing become a new direction and a new trend of automobile development, the functions of an Electronic Control Unit (ECU) of an automobile are more and more powerful, the research and development time of the whole automobile is more and more tight, the firmware upgrade and iteration of the ECU become the core requirements of a whole automobile factory, and the ECU is also the key work content of after-sale maintenance.
In the past, the upgrade mode can only be performed by a 4S shop for off-line flash, so that the time of a client is delayed, the cost of upgrading a batch of software in a whole car factory is greatly increased, sometimes some versions related to safety need to be installed on a client car as soon as possible, and the timeliness of upgrade cannot be guaranteed in the traditional upgrade mode, so that in order to deal with more and more upgrade scenes, the upgrade mode of Over The Air (OTA) is increasingly used.
The traditional vehicle OTA upgrade process is generally as follows:
the cloud end arranges a task, the vehicle end reports the local version number, if the version number is not consistent with the version number of the cloud end arranged task (the version number filled in the task arrangement), the task is triggered, the vehicle end downloads the upgrade package for OTA upgrade, and if the version numbers are consistent, the cloud end directly displays that the upgrade is successful. The vehicle end usually judges whether the upgrade is successful according to the following modes: before a certain part of an automobile is upgraded, a current version number, namely the version number before upgrading, is recorded and is stored in a partition which is not erased during upgrading, after the upgrading is completed, the part is automatically restarted, the version number of the part is firstly read (the version number is contained in an upgrading packet and is written in during the upgrading process), if the version number is consistent with the stored version number, the upgrading is failed, and if the version number is inconsistent with the stored version number, the upgrading is successful.
If the cloud end is used for arranging the task, the version number in the task is wrongly filled due to some reason, the task is triggered, after the OTA upgrading is carried out on the vehicle end, according to the judging mode, the task is considered to be successfully upgraded, but the version number is the version number in the upgrading packet or is different from the version number in the cloud end task, and after a period, the task is triggered again.
Disclosure of Invention
Based on the above, the vehicle OTA upgrading method and the vehicle OTA upgrading system are provided for the technical problems.
In order to solve the technical problems, the invention adopts the following technical scheme:
a vehicle OTA upgrading method comprises a vehicle end step and a cloud end step, wherein the vehicle end step comprises the steps of reporting a local version number of a part to be upgraded, synchronizing a triggered task and downloading a corresponding upgrading packet to upgrade the part to be upgraded; the cloud step comprises an upgrade task, if the local version number is not consistent with the version number of the cloud arrangement task, the task is triggered, and the method is characterized in that the vehicle end step further comprises the following steps:
reporting the unique identifier of the vehicle end;
after the task is synchronized, acquiring a version number from the task;
after the parts to be upgraded are upgraded, comparing the version number after the upgrading is completed with the version number obtained from the task, if the version numbers are consistent, the upgrading is successful, otherwise, the upgrading is failed;
reporting an upgrading result, wherein the upgrading result comprises success or failure information, a vehicle end unique identifier and a task unique identifier;
the cloud step further comprises:
when the local version number is not consistent with the version number of the cloud-end arrangement task, judging whether upgrade failure information of the vehicle end to the task exists or not through the unique vehicle-end identifier, if so, not triggering the task, and if not, triggering the task;
and according to the upgrading result reported by the vehicle end, storing the unique identifier of the vehicle end and corresponding information of the corresponding task upgrading failure.
The reporting the upgrade result further comprises:
and judging whether the cloud can be connected, if not, restarting the network card, and sending an upgrading result to the cloud after the network card is connected to the cloud.
And if the network card is restarted and the cloud terminal cannot be connected, firstly sending the upgrading result to the communication equipment, and then sending the upgrading result to the cloud terminal by the communication equipment.
The unique identification of the vehicle end is a vehicle VIN number, and the unique identification of the task is a task ID.
This scheme still relates to a vehicle OTA upgrading system, includes:
the vehicle end is used for executing the following steps:
reporting a local version number of the part to be upgraded and a unique identifier of a vehicle end;
synchronizing the triggered tasks;
after the tasks are synchronized, acquiring a version number from the tasks, and downloading a corresponding upgrade package to upgrade the parts to be upgraded;
after the parts to be upgraded are upgraded, comparing the version number after the upgrading is completed with the version number obtained from the task, if the version numbers are consistent, the upgrading is successful, otherwise, the upgrading is failed;
reporting an upgrading result, wherein the upgrading result comprises success or failure information, a vehicle end unique identifier and a task unique identifier;
the cloud end is used for executing the following steps:
arranging an upgrading task;
if the local version number is not consistent with the version number of the cloud-end arrangement task, judging whether upgrade failure information of the vehicle end to the task exists or not through the unique identifier of the vehicle end, if so, not triggering the task, and if not, triggering the task;
and according to the upgrading result reported by the vehicle end, storing the unique identifier of the vehicle end and corresponding information of the corresponding task upgrading failure.
The reporting the upgrade result further comprises:
and judging whether the cloud can be connected, if not, restarting the network card, and sending an upgrading result to the cloud after the network card is connected to the cloud.
And if the network card is restarted and the cloud terminal cannot be connected, firstly sending the upgrading result to the communication equipment, and then sending the upgrading result to the cloud terminal by the communication equipment.
The unique identification of the vehicle end is a vehicle VIN number, and the unique identification of the task is a task ID.
The invention can avoid the problem that the task which is successfully upgraded is triggered again.
Drawings
The invention is described in detail below with reference to the following figures and detailed description:
FIG. 1 is a flow chart of the vehicle end steps of the present invention;
FIG. 2 is a flow chart of the cloud steps of the present invention.
Detailed Description
A vehicle OTA upgrading method comprises a vehicle end step and a cloud end step.
The vehicle end is a vehicle-mounted terminal, and the cloud end is a cloud server.
As shown in fig. 1, the vehicle end step includes:
and S111, reporting the local version number of the part to be upgraded and the unique identifier of the vehicle end.
And S112, synchronizing the tasks triggered by the cloud.
And S113, after the task is synchronized, acquiring the version number from the task, and downloading a corresponding upgrade package to upgrade the parts to be upgraded. The version number obtained from the task is saved in the partition where the upgrade is not erased.
And S114, after the parts to be upgraded are upgraded, comparing the version number after the upgrading is completed with the version number obtained from the task, if the version numbers are consistent, the upgrading is successful, otherwise, the upgrading is failed.
And S115, reporting an upgrading result, wherein the upgrading result comprises success or failure information, a unique vehicle end identifier and a unique task identifier.
As shown in fig. 2, the cloud end step includes:
and S121, arranging an upgrading task.
And S122, if the local version number reported by the vehicle end is not consistent with the version number of the cloud-end arrangement task, judging whether the upgrade failure information of the vehicle end to the task exists or not through the unique identifier of the vehicle end, if so, not triggering the task, and if not, triggering the task.
And S123, storing the unique identifier of the vehicle end and corresponding information of the corresponding task upgrading failure according to the upgrading result reported by the vehicle end. Through the information, the cloud end can judge whether the upgrading failure information of the vehicle end to a certain task exists through the unique vehicle end identification.
After the upgrade of the vehicle end is finished, the invention compares the version number after the upgrade with the version number obtained from the task, if the version numbers in the representative tasks are consistent, the version numbers in the representative tasks are not filled in by mistake, the upgrading is successful, otherwise, the upgrading fails, the version numbers in the representative tasks are filled in by mistake or the upgrading fails, and then, because the vehicle end reports the failure information, the unique vehicle end identifier and the unique task identifier to the cloud end, the cloud end stores the unique vehicle end identifier and corresponding information of the corresponding task upgrading failure, thus, when the cloud finds that the local version number reported by the vehicle end is inconsistent with the version number of the cloud arrangement task again after a period, whether the upgrade failure information of the vehicle end to the task exists or not can be judged through the unique identifier of the vehicle end, if the task exists, the cloud end cannot trigger the task again, and the problem that the task is triggered again is avoided.
And for the condition of actual upgrade failure, the upgrade is performed again when the next upgrade task is required to be arranged, and the cloud end can rearrange the upgrade task for the vehicle with the upgrade failure.
Preferably, in step S115, the reporting the upgrade result further includes:
and judging whether the cloud can be connected, if not, restarting the network card, and sending an upgrading result to the cloud after the network card is connected to the cloud. After the upgrade is completed, the network card is not connected to the cloud generally because the vehicle-side network card is not driven, so the network card is restarted.
If the network card cannot be connected to the cloud after being restarted, the upgrading result is sent to the communication equipment firstly, and then the communication equipment sends the upgrading result to the cloud generally because of insufficient flow.
The communication device is a device with wireless functionality, such as a handset. The vehicle end firstly transmits the upgrading result to the mobile phone of the user through the Bluetooth, and the mobile phone transmits the upgrading result to the cloud end through the 4G network.
In this embodiment, the unique identifier of the vehicle end is a vehicle VIN number, and the unique identifier of the task is a task ID.
This scheme still relates to a vehicle OTA upgrading system, includes:
the vehicle end, as shown in fig. 1, is configured to perform the following steps:
and S111, reporting the local version number of the part to be upgraded and the unique identifier of the vehicle end.
And S112, synchronizing the tasks triggered by the cloud.
And S113, after the task is synchronized, acquiring the version number from the task, and downloading a corresponding upgrade package to upgrade the parts to be upgraded. The version number obtained from the task is saved in the partition where the upgrade is not erased.
And S114, after the parts to be upgraded are upgraded, comparing the version number after the upgrading is completed with the version number obtained from the task, if the version numbers are consistent, the upgrading is successful, otherwise, the upgrading is failed.
And S115, reporting an upgrading result, wherein the upgrading result comprises success or failure information, a unique vehicle end identifier and a unique task identifier.
The cloud, as shown in fig. 2, is configured to perform the following steps:
and S121, arranging an upgrading task.
And S122, if the local version number reported by the vehicle end is not consistent with the version number of the cloud-end arrangement task, judging whether the upgrade failure information of the vehicle end to the task exists or not through the unique identifier of the vehicle end, if so, not triggering the task, and if not, triggering the task.
And S123, storing the unique identifier of the vehicle end and corresponding information of the corresponding task upgrading failure according to the upgrading result reported by the vehicle end. Through the information, the cloud end can judge whether the upgrading failure information of the vehicle end to a certain task exists through the unique vehicle end identification.
After the vehicle end is upgraded, the upgraded version number is compared with the version number acquired from the task, if the version number is consistent, the version number in the task is not filled in by mistake, the upgrade is successful, otherwise, the version number in the task is filled in by mistake, the upgrade is failed, and after the upgrade is failed, because the vehicle end reports failure information, the vehicle end unique identifier and the task unique identifier to the cloud end, the cloud end stores the vehicle end unique identifier and corresponding information of the corresponding task upgrade failure, so that when the local version number reported by the vehicle end is found to be inconsistent with the version number of the task arranged at the cloud end again by the cloud end after a period, whether the upgrade failure information of the vehicle end to the task exists or not can be judged by the vehicle end unique identifier, and if the upgrade failure information of the vehicle end to the task exists, the cloud end can not trigger the task again, and the problem that the task is triggered.
Preferably, in step S115, the reporting the upgrade result further includes:
and judging whether the cloud can be connected, if not, restarting the network card, and sending an upgrading result to the cloud after the network card is connected to the cloud. After the upgrade is completed, the network card is not connected to the cloud generally because the vehicle-side network card is not driven, so the network card is restarted.
If the network card cannot be connected to the cloud after being restarted, the upgrading result is sent to the communication equipment firstly, and then the communication equipment sends the upgrading result to the cloud generally because of insufficient flow.
The communication device is a device with wireless functionality, such as a handset. The vehicle end firstly transmits the upgrading result to the mobile phone of the user through the Bluetooth, and the mobile phone transmits the upgrading result to the cloud end through the 4G network.
In this embodiment, the unique identifier of the vehicle end is a vehicle VIN number, and the unique identifier of the task is a task ID.
However, those skilled in the art should realize that the above embodiments are illustrative only and not limiting to the present invention, and that changes and modifications to the above described embodiments are intended to fall within the scope of the appended claims, provided they fall within the true spirit of the present invention.
Claims (8)
1. A vehicle OTA upgrading method comprises a vehicle end step and a cloud end step, wherein the vehicle end step comprises the steps of reporting a local version number of a part to be upgraded, synchronizing a triggered task and downloading a corresponding upgrading packet to upgrade the part to be upgraded; the cloud step comprises an upgrade task, if the local version number is not consistent with the version number of the cloud arrangement task, the task is triggered, and the method is characterized in that the vehicle end step further comprises the following steps:
reporting the unique identifier of the vehicle end;
after the task is synchronized, acquiring a version number from the task;
after the parts to be upgraded are upgraded, comparing the version number after the upgrading is completed with the version number obtained from the task, if the version numbers are consistent, the upgrading is successful, otherwise, the upgrading is failed;
reporting an upgrading result, wherein the upgrading result comprises success or failure information, a vehicle end unique identifier and a task unique identifier;
the cloud step further comprises:
when the local version number is not consistent with the version number of the cloud-end arrangement task, judging whether upgrade failure information of the vehicle end to the task exists or not through the unique vehicle-end identifier, if so, not triggering the task, and if not, triggering the task;
and according to the upgrading result reported by the vehicle end, storing the unique identifier of the vehicle end and corresponding information of the corresponding task upgrading failure.
2. The OTA upgrading method for vehicles according to claim 1, wherein the reporting the upgrading result further comprises:
and judging whether the cloud can be connected, if not, restarting the network card, and sending an upgrading result to the cloud after the network card is connected to the cloud.
3. The OTA vehicle upgrading method according to claim 2, wherein if the network card is restarted and the cloud cannot be connected, the upgrading result is sent to the communication device first, and then the communication device sends the upgrading result to the cloud.
4. The OTA vehicle upgrade method according to claim 1 or 3 wherein the vehicle end unique identifier is a vehicle VIN number and the task unique identifier is a task ID.
5. A vehicle OTA upgrade system, comprising:
the vehicle end is used for executing the following steps:
reporting a local version number of the part to be upgraded and a unique identifier of a vehicle end;
synchronizing the triggered tasks;
after the tasks are synchronized, acquiring a version number from the tasks, and downloading a corresponding upgrade package to upgrade the parts to be upgraded;
after the parts to be upgraded are upgraded, comparing the version number after the upgrading is completed with the version number obtained from the task, if the version numbers are consistent, the upgrading is successful, otherwise, the upgrading is failed;
reporting an upgrading result, wherein the upgrading result comprises success or failure information, a vehicle end unique identifier and a task unique identifier;
the cloud end is used for executing the following steps:
arranging an upgrading task;
if the local version number is not consistent with the version number of the cloud-end arrangement task, judging whether upgrade failure information of the vehicle end to the task exists or not through the unique identifier of the vehicle end, if so, not triggering the task, and if not, triggering the task;
and according to the upgrading result reported by the vehicle end, storing the unique identifier of the vehicle end and corresponding information of the corresponding task upgrading failure.
6. The OTA upgrade system for a vehicle of claim 5, wherein the reporting the upgrade result further comprises:
and judging whether the cloud can be connected, if not, restarting the network card, and sending an upgrading result to the cloud after the network card is connected to the cloud.
7. The OTA vehicle upgrade system according to claim 6, wherein if the network card is restarted and the cloud cannot be connected, the upgrade result is sent to the communication device first, and then the communication device sends the upgrade result to the cloud.
8. The vehicle OTA upgrade system according to claim 5 or 7 wherein the vehicle end unique identifier is a vehicle VIN number and the task unique identifier is a task ID.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010441209.7A CN111614765B (en) | 2020-05-22 | 2020-05-22 | Vehicle OTA (over the air) upgrading method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010441209.7A CN111614765B (en) | 2020-05-22 | 2020-05-22 | Vehicle OTA (over the air) upgrading method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111614765A true CN111614765A (en) | 2020-09-01 |
| CN111614765B CN111614765B (en) | 2022-11-18 |
Family
ID=72199524
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010441209.7A Active CN111614765B (en) | 2020-05-22 | 2020-05-22 | Vehicle OTA (over the air) upgrading method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111614765B (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112640500A (en) * | 2020-09-27 | 2021-04-09 | 华为技术有限公司 | Vehicle upgrading method and device |
| CN114035856A (en) * | 2021-09-30 | 2022-02-11 | 黄冈普赫氢能商用车有限公司 | Control method and storage medium for peripheral devices during batch updating of ECU application layer software |
| CN114785688A (en) * | 2022-06-21 | 2022-07-22 | 深圳市华曦达科技股份有限公司 | Terminal equipment upgrading method and system |
| CN114980073A (en) * | 2022-05-26 | 2022-08-30 | 重庆长安汽车股份有限公司 | Vehicle OTA state intelligent analysis processing method, system and storage medium |
| WO2022205200A1 (en) * | 2021-03-31 | 2022-10-06 | 华为技术有限公司 | Version management method and apparatus |
| WO2022239613A1 (en) * | 2021-05-14 | 2022-11-17 | 株式会社デンソー | Vehicular electronic control device, vehicular electronic control system, and updated configuration information determination program |
| CN115442234A (en) * | 2022-08-25 | 2022-12-06 | 东风悦享科技有限公司 | E2E system and method for realizing OTA (over-the-air technology) upgrade of ECU (electronic control unit) gray scale of L4-level vehicle |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016086654A1 (en) * | 2014-12-03 | 2016-06-09 | 广州广电运通金融电子股份有限公司 | Remote upgrade method and system for software on self-service terminal, and upgrade package creation method |
| CN109062598A (en) * | 2018-06-26 | 2018-12-21 | 珠海全志科技股份有限公司 | A kind of safe OTA upgrade method and system |
| CN109240722A (en) * | 2018-08-30 | 2019-01-18 | 百度在线网络技术（北京）有限公司 | Application upgrade method, apparatus, system and storage medium |
| CN110633092A (en) * | 2019-09-09 | 2019-12-31 | 北京方研矩行科技有限公司 | Server for OTA (over the air) upgrading and embedded equipment upgrading method and device |
-
2020
- 2020-05-22 CN CN202010441209.7A patent/CN111614765B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016086654A1 (en) * | 2014-12-03 | 2016-06-09 | 广州广电运通金融电子股份有限公司 | Remote upgrade method and system for software on self-service terminal, and upgrade package creation method |
| CN109062598A (en) * | 2018-06-26 | 2018-12-21 | 珠海全志科技股份有限公司 | A kind of safe OTA upgrade method and system |
| CN109240722A (en) * | 2018-08-30 | 2019-01-18 | 百度在线网络技术（北京）有限公司 | Application upgrade method, apparatus, system and storage medium |
| CN110633092A (en) * | 2019-09-09 | 2019-12-31 | 北京方研矩行科技有限公司 | Server for OTA (over the air) upgrading and embedded equipment upgrading method and device |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112640500A (en) * | 2020-09-27 | 2021-04-09 | 华为技术有限公司 | Vehicle upgrading method and device |
| CN112640500B (en) * | 2020-09-27 | 2022-05-10 | 华为技术有限公司 | Vehicle upgrading method and device |
| WO2022205200A1 (en) * | 2021-03-31 | 2022-10-06 | 华为技术有限公司 | Version management method and apparatus |
| WO2022239613A1 (en) * | 2021-05-14 | 2022-11-17 | 株式会社デンソー | Vehicular electronic control device, vehicular electronic control system, and updated configuration information determination program |
| CN114035856A (en) * | 2021-09-30 | 2022-02-11 | 黄冈普赫氢能商用车有限公司 | Control method and storage medium for peripheral devices during batch updating of ECU application layer software |
| CN114980073A (en) * | 2022-05-26 | 2022-08-30 | 重庆长安汽车股份有限公司 | Vehicle OTA state intelligent analysis processing method, system and storage medium |
| CN114785688A (en) * | 2022-06-21 | 2022-07-22 | 深圳市华曦达科技股份有限公司 | Terminal equipment upgrading method and system |
| CN115442234A (en) * | 2022-08-25 | 2022-12-06 | 东风悦享科技有限公司 | E2E system and method for realizing OTA (over-the-air technology) upgrade of ECU (electronic control unit) gray scale of L4-level vehicle |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111614765B (en) | 2022-11-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111614765B (en) | Vehicle OTA (over the air) upgrading method and system | |
| US9841970B2 (en) | Vehicle control update methods and systems | |
| CA2502113C (en) | Method and system for remote reflash | |
| CN105094883A (en) | Module interface for vehicle updates | |
| CN109831338B (en) | Vehicle machine system upgrading method, cloud server and mobile terminal | |
| CN109413134B (en) | Vehicle-mounted application upgrading method, device, system and storage medium | |
| US20060161314A1 (en) | Software defined radio unit and vehicular information system | |
| US8423017B2 (en) | Automatic updating of a preferred roaming list stored in a vehicle telematics unit | |
| CN103593208A (en) | Methods and apparatus for vehicle computing system software updates | |
| CN112202920B (en) | Vehicle-mounted system upgrading method and device | |
| CN115344281A (en) | Finished automobile OTA (over the air) upgrading method, system, storage medium and equipment | |
| CN112615747B (en) | Method and device for automatically deploying and configuring network equipment | |
| CN115567496A (en) | OTA (over the air) upgrading method and system | |
| CN110795124A (en) | Remote upgrading method, device, equipment and storage medium for automobile safety part | |
| CN104317564A (en) | Method and device for updating feature phone software | |
| CN110187904B (en) | Device and method for updating vehicle controller firmware | |
| CN112188434A (en) | OTA (over the air) upgrading method and system | |
| KR20070076201A (en) | Rom program update system and method do electron control unit in vehicles | |
| CN204576141U (en) | A kind of automobile remote control system based on car networking | |
| CN113660317A (en) | Vehicle-mounted terminal remote upgrading method based on FTP protocol | |
| CN112969162A (en) | Terminal device prompting method, electronic device and storage medium | |
| CN110377305B (en) | Application software upgrading method, terminal and system | |
| CN114691174A (en) | Vehicle-mounted software upgrading method, device and equipment | |
| CN115202679A (en) | ECU (electronic control Unit) upgrading method and device based on vehicle-mounted Ethernet | |
| CN114979116B (en) | Vehicle-mounted software upgrading method, system, terminal equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |