CN111614765B - Vehicle OTA (over the air) upgrading method and system - Google Patents
Vehicle OTA (over the air) upgrading method and system Download PDFInfo
- Publication number
- CN111614765B CN111614765B CN202010441209.7A CN202010441209A CN111614765B CN 111614765 B CN111614765 B CN 111614765B CN 202010441209 A CN202010441209 A CN 202010441209A CN 111614765 B CN111614765 B CN 111614765B
- Authority
- CN
- China
- Prior art keywords
- task
- upgrading
- vehicle
- cloud
- 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.)
- Active
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Stored Programmes (AREA)
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 used more and more.
The traditional vehicle OTA upgrade flow 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 arrangement 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 number is 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 problem, 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 unique vehicle end identifier and a unique task 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.
If the network card is restarted and the cloud end cannot be connected, the upgrading result is sent to the communication equipment, and then the communication equipment sends the upgrading result to the cloud end.
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 the 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 upgraded version number 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 successfully upgraded task 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
An OTA (over the air) vehicle 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 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 vehicle end is upgraded, the upgraded version number is compared with the version number obtained from the task, if the version number is consistent, the version number in the task is not filled by mistake, the upgrade is successful, otherwise, the upgrade fails, the version number in the task is filled by mistake or the upgrade is failed indeed, then, as the vehicle end reports failure information, a vehicle end unique identifier and a 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, and thus, when the local version number reported by the vehicle end is not consistent with the version number of the cloud end arrangement task after a period, the cloud end can judge whether the upgrade failure information of the vehicle end to the task exists or not through the vehicle end unique identifier, if the upgrade failure information of the vehicle end to the task exists, the task cannot be triggered again, and the problem that the cloud end triggers the task again is avoided.
And for the condition of actual upgrading failure, the upgrading is carried out again when the upgrading task needs to be arranged again next time, and the cloud end can rearrange the upgrading task aiming at the vehicle with the upgrading failure.
Preferably, in step S115, reporting the upgrade result further includes:
and judging whether the cloud terminal can be connected or not, if not, restarting the network card, and sending an upgrading result to the cloud terminal after the network card is connected to the cloud terminal. After the upgrade is completed, the network card is not started, which is usually caused by the fact that the vehicle-side network card is not driven.
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 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 again is avoided.
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 started, which is usually caused by the fact that the vehicle-side network card is not driven.
If the network card is restarted and the cloud terminal cannot be connected, the upgrading result is sent to the communication equipment firstly, and then the communication equipment sends the upgrading result to the cloud terminal, which is usually caused by 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 forwards 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 recognize that the above-described embodiments are illustrative only, and not limiting, and that changes and modifications can be made to the above-described embodiments without departing from the true spirit and scope of the invention, which is defined by the following claims.
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 upgraded version number 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 unique vehicle end identifier and a unique task 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 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.
2. The OTA upgrading method for vehicles according to claim 1, wherein the reporting the upgrading result further comprises:
and judging whether the cloud terminal can be connected or not, if not, restarting the network card, and sending an upgrading result to the cloud terminal after the network card is connected to the cloud terminal.
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 CN111614765A (en) | 2020-09-01 |
| CN111614765B true 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) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP4202645A4 (en) * | 2020-09-27 | 2023-09-27 | Huawei Technologies Co., Ltd. | Vehicle upgrading method and apparatus |
| EP4310669A4 (en) * | 2021-03-31 | 2024-04-17 | Huawei Technologies Co., Ltd. | Version management method and apparatus |
| JP2022175761A (en) * | 2021-05-14 | 2022-11-25 | 株式会社デンソー | Vehicular electronic control device, vehicular electronic control system and post-update configuration information determining 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 |
| CN114785688B (en) * | 2022-06-21 | 2022-09-06 | 深圳市华曦达科技股份有限公司 | 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 |
| WO2024197570A1 (en) * | 2023-03-28 | 2024-10-03 | 华为技术有限公司 | Upgrading detection method and device |
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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111614765A (en) | 2020-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111614765B (en) | Vehicle OTA (over the air) upgrading method and system | |
| CN109831338B (en) | Vehicle machine system upgrading method, cloud server and mobile terminal | |
| CN105094883A (en) | Module interface for vehicle updates | |
| US20050256614A1 (en) | Method and system for remote reflash | |
| US20060161314A1 (en) | Software defined radio unit and vehicular information system | |
| CN110187904B (en) | Device and method for updating vehicle controller firmware | |
| CN111399885B (en) | Vehicle component upgrading pushing method and device and computer readable storage medium | |
| CN103593208A (en) | Methods and apparatus for vehicle computing system software updates | |
| CN110377305B (en) | Application software upgrading method, terminal and system | |
| CN109803252B (en) | Secondary eSIM card logout method, eSIM server, terminal and system | |
| 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 | |
| CN113660317A (en) | Vehicle-mounted terminal remote upgrading method based on FTP protocol | |
| KR20070076201A (en) | Rom program update system and method do electron control unit in vehicles | |
| CN113791800A (en) | Automatic parking control module remote upgrading method and system and automobile | |
| CN204576141U (en) | A kind of automobile remote control system based on car networking | |
| CN112969162A (en) | Terminal device prompting method, electronic device and storage medium | |
| CN111722856B (en) | Method and device for upgrading firmware in vehicle-mounted microcontroller | |
| CN117032750A (en) | Energy storage charging pile remote upgrading method based on FOTA and related equipment | |
| CN113242276B (en) | On-line upgrading method, device, equipment and storage medium for vehicle-mounted system | |
| CN115202692A (en) | OTA (over the air) upgrading method and device for vehicle HUD | |
| CN108605211B (en) | Method for transmitting messages to a motor vehicle, processor device, display device | |
| CN115202679A (en) | ECU (electronic control Unit) upgrading method and device based on vehicle-mounted Ethernet |
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 |