CN111478897A - OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) - Google Patents

OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) Download PDF

Info

Publication number
CN111478897A
CN111478897A CN202010259275.2A CN202010259275A CN111478897A CN 111478897 A CN111478897 A CN 111478897A CN 202010259275 A CN202010259275 A CN 202010259275A CN 111478897 A CN111478897 A CN 111478897A
Authority
CN
China
Prior art keywords
vehicle
upgrading
ota
upgrade
client
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
Application number
CN202010259275.2A
Other languages
Chinese (zh)
Inventor
姚君
王锡玉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Infotech Shanghai Co ltd
Original Assignee
Infotech Shanghai Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Infotech Shanghai Co ltd filed Critical Infotech Shanghai Co ltd
Priority to CN202010259275.2A priority Critical patent/CN111478897A/en
Publication of CN111478897A publication Critical patent/CN111478897A/en
Pending legal-status Critical Current

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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12—Protecting executable software
    • 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
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0869—Network architectures or network communication protocols for network security for authentication of entities for achieving mutual authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • 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/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Technology Law (AREA)
  • Multimedia (AREA)
  • Power Engineering (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Stored Programmes (AREA)

Abstract

An OTA (over the air) upgrading method for a vehicle ECU (electronic control unit) comprises the steps that a cloud OTA management platform receives an upgrading request of an accessed vehicle OTA client, a corresponding upgrading task is inquired from a pre-established upgrading task according to the upgrading request, the upgrading task is sent to the vehicle OTA client, the vehicle OTA client is accessed to the cloud OTA management platform, and the vehicle OTA client receives the upgrading task and carries out upgrading according to the upgrading task. The invention has high safety and improves the upgrading efficiency.

Description

OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit)
Technical Field
The invention relates to the technical field of vehicle ECU upgrading, in particular to an OTA (over the air) upgrading method and system of a vehicle ECU.
Background
With the development of the current car networking technology, the functions and complexity of the vehicle are higher and higher, and more Electronic Control Units (ECUs) with embedded software are mounted on the vehicle, and the versions of the ECUs are updated throughout the whole life cycle of the vehicle. The traditional upgrading mode can only be used for off-line flash through a 4S shop, namely, 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 upgrading cannot be guaranteed in the traditional upgrading mode, so that in order to deal with more and more upgrading scenes, the upgrading mode of Over The Air (OTA) is increasingly used.
The traditional OTA upgrading mode is low in safety and efficiency.
Disclosure of Invention
Based on the above, the OTA upgrading method of the vehicle ECU and the method thereof are provided for solving the technical problems.
In order to solve the technical problems, the invention adopts the following technical scheme:
an OTA upgrading method of a vehicle ECU is characterized in that an accessed vehicle OTA client is received by a cloud OTA management platform, a corresponding upgrading task is inquired from a pre-established upgrading task according to the upgrading request, the upgrading task is sent to the vehicle OTA client, the vehicle OTA client is accessed to the cloud OTA management platform, the vehicle OTA client receives the upgrading task and upgrades according to the upgrading task, and the upgrading task comprises a download address of an upgrading packet, and the OTA upgrading method further comprises the following steps:
when the vehicle-end OTA client accesses the cloud OTA management platform, bidirectional authentication is carried out;
when the upgrade task is created, combining a plurality of upgrade packages into an upgrade package set, wherein the upgrade task further comprises a download address of the upgrade package set and an upgrade sequence of the upgrade packages which is set according to dependency and atomicity;
and when the cloud OTA management platform inquires a plurality of corresponding upgrading tasks of the same ECU according to the upgrading request, if the upgrading tasks are not set with priorities, only the latest upgrading task is sent to the vehicle-end OTA client, if the upgrading tasks are set with priorities, the upgrading tasks are sent to the vehicle-end OTA client from high to low according to the priorities, and for the upgrading tasks with the same priorities, only the latest upgrading task is sent to the vehicle-end OTA client.
This scheme still includes:
the vehicle-end OTA client side:
downloading an upgrading packet according to a downloading strategy in the upgrading task;
checking the signature according to the signature information in the upgrade package;
after the signature verification is finished, reporting the downloading and signature verification results to the cloud OTA management platform;
upgrading according to an upgrading strategy in the upgrading task;
after upgrading is completed, reporting an upgrading result;
the cloud OTA management platform:
receiving the downloading and signature checking result;
and receiving the upgrading result, and performing state statistics display on the upgrading task according to the upgrading result.
The bidirectional authentication includes:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
the certificate information in the message header is analyzed to obtain the unique identification information of the vehicle-end OTA client or the unique identification information of the vehicle-end OTA client is directly obtained from the message header;
and matching the unique identification information of the vehicle-end OTA client with the locally stored unique identification information of the vehicle-end OTA client, and if the matching is successful, allowing the vehicle-end OTA client to access.
The vehicle-end OTA client side:
and carrying the certificate information of the user or the unique identification information of the vehicle-end OTA client in a message header, and sending a message to the cloud OTA management platform.
The bidirectional authentication includes:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
the certificate information in the message header is analyzed to obtain the unique identification information of the vehicle-end OTA client or the unique identification information of the vehicle-end OTA client is directly obtained from the message header;
and matching the unique identification information of the vehicle-end OTA client with the unique identification information of the vehicle-end OTA client in the message body, and if the matching is successful, allowing the vehicle-end OTA client to access.
The vehicle-end OTA client side:
and carrying the certificate information of the user or the unique identification information of the vehicle-end OTA client in a message header, and sending a message to the cloud OTA management platform.
The bidirectional authentication includes:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
obtaining an encrypted certificate serial number from the message;
the encrypted certificate serial number is sent to a remote certificate verification server for verification, and if the verification is passed, the vehicle-end OTA client is allowed to access;
the vehicle-end OTA client side:
encrypting the certificate sequence number through a public key distributed by the remote certificate verification server;
and sending a message to the cloud OTA management platform by carrying the encrypted certificate serial number.
This scheme still relates to a vehicle ECU's OTA upgrade system, including high in the clouds OTA management platform and car end OTA client, high in the clouds OTA management platform receives the upgrade request of the car end OTA client that inserts, according to corresponding upgrade task is inquired in the upgrade task that the upgrade request is established in advance, and send this upgrade task for car end OTA client, car end OTA client inserts high in the clouds OTA management platform, car end OTA client receives the upgrade task, and according to upgrade the task carries out the upgrade, the upgrade task includes the download address of upgrading the package, its characterized in that still includes:
when the vehicle-end OTA client accesses the cloud OTA management platform, bidirectional authentication is carried out;
when the upgrade task is created, combining a plurality of upgrade packages into an upgrade package set, wherein the upgrade task further comprises a download address of the upgrade package set and an upgrade sequence of the upgrade packages which is set according to dependency and atomicity;
and when the cloud OTA management platform inquires a plurality of corresponding upgrading tasks of the same ECU according to the upgrading request, if the upgrading tasks are not set with priorities, only the latest upgrading task is sent to the vehicle-end OTA client, if the upgrading tasks are set with priorities, the upgrading tasks are sent to the vehicle-end OTA client from high to low according to the priorities, and for the upgrading tasks with the same priorities, only the latest upgrading task is sent to the vehicle-end OTA client.
This scheme still includes:
the vehicle-end OTA client side:
downloading an upgrading packet according to a downloading strategy in the upgrading task;
checking the signature according to the signature information in the upgrade package;
after the signature verification is finished, reporting the downloading and signature verification results to the cloud OTA management platform;
upgrading according to an upgrading strategy in the upgrading task;
after upgrading is completed, reporting an upgrading result;
the cloud OTA management platform:
receiving the downloading and signature checking result;
and receiving the upgrading result, and performing state statistics display on the upgrading task according to the upgrading result.
The bidirectional authentication includes:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
the certificate information in the message header is analyzed to obtain the unique identification information of the vehicle-end OTA client or the unique identification information of the vehicle-end OTA client is directly obtained from the message header;
and matching the unique identification information of the vehicle-end OTA client with the locally stored unique identification information of the vehicle-end OTA client, and if the matching is successful, allowing the vehicle-end OTA client to access.
The vehicle-end OTA client side:
and carrying the certificate information of the user or the unique identification information of the vehicle-end OTA client in a message header, and sending a message to the cloud OTA management platform.
The bidirectional authentication includes:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
the certificate information in the message header is analyzed to obtain the unique identification information of the vehicle-end OTA client or the unique identification information of the vehicle-end OTA client is directly obtained from the message header;
and matching the unique identification information of the vehicle-end OTA client with the unique identification information of the vehicle-end OTA client in the message body, and if the matching is successful, allowing the vehicle-end OTA client to access.
The vehicle-end OTA client side:
and carrying the certificate information of the user or the unique identification information of the vehicle-end OTA client in a message header, and sending a message to the cloud OTA management platform.
The bidirectional authentication includes:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
obtaining an encrypted certificate serial number from the message;
the encrypted certificate serial number is sent to a remote certificate verification server for verification, and if the verification is passed, the vehicle-end OTA client is allowed to access;
the vehicle-end OTA client side:
encrypting the certificate sequence number through a public key distributed by the remote certificate verification server;
and sending a message to the cloud OTA management platform by carrying the encrypted certificate serial number.
The invention has high safety and improves the upgrading efficiency.
Drawings
The invention is described in detail below with reference to the following figures and detailed description:
FIG. 1 is a schematic diagram of the system of the present invention.
Detailed Description
As shown in fig. 1, an OTA upgrading method of a vehicle ECU includes:
the cloud OTA management platform 110 receives an upgrade request of an accessed vehicle-end OTA client, queries a corresponding upgrade task from pre-established upgrade tasks according to the upgrade request, and sends the upgrade task to the vehicle-end OTA client 120.
The vehicle-side OTA client 120 accesses the cloud-side OTA management platform 110, receives the upgrade task, and performs upgrade according to the upgrade task, where the upgrade task includes a download address of an upgrade package.
When the vehicle-side OTA client 120 is accessed to the cloud OTA management platform 110, bidirectional authentication is performed, and the safety is high.
When an upgrade task is created, merging the plurality of upgrade packages into an upgrade package set, where the upgrade task further includes a download address of the upgrade package set and an upgrade order of the plurality of upgrade packages set according to dependency and atomicity. Different versions of different ECUs are independent upgrade packages, sometimes the upgrade sequence among different ECUs needs to be dependent, one ECU needs to be upgraded first, and then the other ECU needs to be upgraded; sometimes, when upgrading is carried out among a plurality of ECUs, the ECUs are required to be atomic, and are either all successful or all failed, if one is successful and one is failed, the successful ECU needs to be rolled back to the original version, so that a plurality of independent upgrading packages are required to be logically combined and combined into a set, and the upgrading sequence of each upgrading package is set for the set. When an upgrade task is created, one or more upgrade package sets may be selected, and the order may also be set between the upgrade package sets. Therefore, the upgrading is flexibly carried out according to the constraint relation among the ECUs, and the upgrading efficiency is improved.
When the cloud OTA management platform 110 inquires a plurality of corresponding upgrading tasks of the same ECU according to the upgrading request, if the plurality of upgrading tasks are not set with priorities, only the latest upgrading task is sent to the vehicle-end OTA client 120, and the task scheduling mode can enable the vehicle ECU to be upgraded to the latest version directly from an old version by skipping upgrading for a plurality of times in the middle; if the priorities are set for the plurality of upgrading tasks, the plurality of upgrading tasks are sent to the vehicle-end OTA client 120 from high to low according to the priorities, and for the upgrading tasks with the same priorities, only the latest upgrading task is sent to the vehicle-end OTA client 120. The invention adopts two task scheduling modes for a plurality of upgrading tasks of each ECU, and improves the upgrading efficiency.
Preferably, the method of the present invention further comprises the following steps:
first, the implementation process of the vehicle-side OTA client 120:
downloading the upgrading package according to the downloading strategy in the upgrading task, checking the signature according to the signature information in the upgrading package, reporting the downloading and signature checking results to the cloud OTA management platform 110 after the signature checking is finished, upgrading according to the upgrading strategy in the upgrading task, and reporting the upgrading results after the upgrading is finished.
Second, the execution process of the cloud OTA management platform 110:
and receiving the downloading and signature checking results, receiving the upgrading results, and performing state statistics display on the upgrading tasks according to the upgrading results.
Example 1
In this embodiment, the bidirectional authentication process is as follows:
firstly, the execution process of the cloud OTA management platform 110:
1. a message is received from the vehicle-side OTA client 120.
2. And analyzing the certificate information in the message header to obtain the unique identification information of the vehicle-end OTA client or directly obtaining the unique identification information of the vehicle-end OTA client from the message header.
3. And matching the unique identification information of the vehicle-end OTA client with the locally stored unique identification information of the vehicle-end OTA client, and if the matching is successful, allowing the vehicle-end OTA client to access.
Second, the execution process of the car-end OTA client 120:
and carrying the certificate information of the vehicle or the unique identification information of the vehicle OTA client in a message header, and sending the message to the cloud OTA management platform 110.
Example 2
In this embodiment, the bidirectional authentication process is as follows:
firstly, the execution process of the cloud OTA management platform 110:
1. a message is received from the vehicle-side OTA client 120.
2. And analyzing the certificate information in the message header to obtain the unique identification information of the vehicle-end OTA client or directly obtaining the unique identification information of the vehicle-end OTA client from the message header.
3. And matching the unique identification information of the vehicle-end OTA client 120 with the unique identification information of the vehicle-end OTA client in the message body, and if the matching is successful, allowing the vehicle-end OTA client 120 to access, wherein the message body is provided with the vehicle-end OTA client identification information.
Second, the execution process of the car-end OTA client 120:
and carrying the certificate information of the vehicle or the unique identification information of the vehicle OTA client in a message header, and sending the message to the cloud OTA management platform 110.
Example 3
In this embodiment, the bidirectional authentication process is as follows:
firstly, the execution process of the cloud OTA management platform 110:
1. a message is received from the vehicle-side OTA client 120.
2. The encrypted certificate serial number is obtained from the message.
3. And sending the encrypted certificate serial number to a remote certificate verification server for verification, and allowing the vehicle-end OTA client 120 to access if the verification is passed.
Second, the execution process of the car-end OTA client 120:
1. and encrypting the certificate sequence number through a public key distributed by the remote certificate verification server.
2. The encrypted certificate serial number is carried to send a message to the cloud OTA management platform 110.
Specifically, the cloud OTA management platform 110 includes:
and the vehicle data management module 111 is used for acquiring vehicle data from the MES/TSP system 2 or providing a user interface for a user to manually add the vehicle data, wherein the vehicle data comprises the unique identification information of the OTA client at the vehicle end, the information of all ECUs at the vehicle end and the vehicle information.
The unique identification information of the vehicle-end OTA client is a Vehicle Identification Number (VIN), or a TBOX serial number, or a combination of the VIN, the TBOX serial number and a special symbol. The vehicle information includes vehicle type information, vehicle family information, and OEM information.
Tsp (telematics service provider) refers to an automobile remote service provider, and mes (manufacturing execution system) refers to a manufacturing enterprise production process execution system.
The vehicle data management module 111 can actively pull vehicle data from the MES/TSP system 2, and the active pull process can be periodic, manually triggered, or both. The data pulled may be full or incremental.
The user interface can be a web interface, and the user can add the vehicle data in a batch import or single input mode on the web interface.
The vehicle data management module 111 may also receive vehicle data passively from the MES/TSP system 2, either periodically or manually triggered, or both. The passively received data may be full or incremental.
The upgrade package management module 112 is configured to provide a user interface for a user to manually upload the upgrade package, receive upgrade package information manually input by the user, or automatically parse the upgrade package to obtain the upgrade package information, and sign the upgrade package. The upgrade package information is associated with the upgrade package.
The upgrading package information comprises a software version number, a part number of the ECU to be upgraded, hardware information of the ECU to be upgraded, a file type of the upgrading package and a software version number range of the ECU which can be upgraded by using the upgrading package file.
And the upgrading package is uploaded by adopting an HTTP/HTTPS/FTP/FTPS/SFTP protocol, and is a full upgrading package file or a differential upgrading package.
Only one full upgrade package file of the same software version number of the same ECU is allowed to exist. The full package files of different software version numbers of the same ECU are allowed to exist in plurality. The full package of different software version numbers of different ECUs allows for a plurality. The full package of the same software version number of different ECUs allows for a plurality. The differential upgrade package files with the same software version number and the same upgrade source version number of the same ECU only allow to exist one. The differential upgrade package files of the same software version number and different upgrade source version numbers of the same ECU are allowed to exist in a plurality. The number of the differential upgrade package files with different software version numbers, the same or different upgrade source version numbers of the same ECU is allowed to exist.
And the upgrade task management module 113 is configured to create an upgrade task and manage the upgrade task.
Managing upgrade tasks includes deploying tasks, terminating tasks, suspending tasks, re-running tasks, prioritizing between tasks, and task merging.
The upgrading task comprises a unique task identifier, a characteristic expression of a vehicle to be upgraded, a unique identifier range of a vehicle OTA client to be upgraded, an identifier of upgrading package file information, the size of an upgrading package, the sha value of the upgrading package, the encryption mode of the upgrading package, key information for decrypting the upgrading package, a downloading strategy, an upgrading strategy, a rollback strategy, an upgrading sequence of a plurality of upgrading packages arranged according to dependency and atomicity, the starting time and the ending time of the task, the starting time of scheduling, the ending time of scheduling and the priority.
And a communication management module 114, configured to send or receive a message to the vehicle-side OTA client 120.
The vehicle-side OTA client 120 includes:
the communication management module 121 is configured to send or receive a message to the cloud OTA management platform 110.
And the ECU upgrading management module 122 is used for upgrading according to the upgrading task.
Wherein, the message may be: reporting ECU version information, notifying a message of an upgrade task currently, inquiring whether the message of the upgrade task exists or not, upgrading task information, a message of reporting a downloading progress, upgrading result information, details of an upgrading process, reporting hardware information and the like. The bearer mode can be HTTP/HTTPS protocol, or WS/WSS protocol, or adopt the message format meeting OMA specification or JSON specification.
As shown in fig. 1, the present invention further relates to an OTA upgrading system for a vehicle ECU, which includes a cloud OTA management platform 110 and a vehicle OTA client 120.
The cloud OTA management platform 110 receives an upgrade request of an accessed vehicle-end OTA client, queries a corresponding upgrade task from pre-established upgrade tasks according to the upgrade request, and sends the upgrade task to the vehicle-end OTA client 120.
The vehicle-side OTA client 120 accesses the cloud-side OTA management platform 110, receives the upgrade task, and performs upgrade according to the upgrade task, where the upgrade task includes a download address of an upgrade package.
When the vehicle-side OTA client 120 is accessed to the cloud OTA management platform 110, bidirectional authentication is performed, and the safety is high.
When an upgrade task is created, merging the plurality of upgrade packages into an upgrade package set, where the upgrade task further includes a download address of the upgrade package set and an upgrade order of the plurality of upgrade packages set according to dependency and atomicity. Different versions of different ECUs are independent upgrade packages, sometimes the upgrade sequence among different ECUs needs to be dependent, one ECU needs to be upgraded first, and then the other ECU needs to be upgraded; sometimes, when upgrading is carried out among a plurality of ECUs, the ECUs are required to be atomic, and are either all successful or all failed, if one is successful and one is failed, the successful ECU needs to be rolled back to the original version, so that a plurality of independent upgrading packages are required to be logically combined and combined into a set, and the upgrading sequence of each upgrading package is set for the set. When an upgrade task is created, one or more upgrade package sets may be selected, and the order may also be set between the upgrade package sets. Therefore, the upgrading is flexibly carried out according to the constraint relation among the ECUs, and the upgrading efficiency is improved.
When the cloud OTA management platform 110 inquires a plurality of corresponding upgrading tasks of the same ECU according to the upgrading request, if the plurality of upgrading tasks are not set with priorities, only the latest upgrading task is sent to the vehicle-end OTA client 120, and the task scheduling mode can enable the vehicle ECU to be upgraded to the latest version directly from an old version by skipping upgrading for a plurality of times in the middle; if the priorities are set for the plurality of upgrading tasks, the plurality of upgrading tasks are sent to the vehicle-end OTA client 120 from high to low according to the priorities, and for the upgrading tasks with the same priorities, only the latest upgrading task is sent to the vehicle-end OTA client 120. The invention adopts two task scheduling modes for a plurality of upgrading tasks of each ECU, and improves the upgrading efficiency.
Preferably, the invention also has the following process:
first, the implementation process of the vehicle-side OTA client 120:
downloading the upgrading package according to the downloading strategy in the upgrading task, checking the signature according to the signature information in the upgrading package, reporting the downloading and signature checking results to the cloud OTA management platform 110 after the signature checking is finished, upgrading according to the upgrading strategy in the upgrading task, and reporting the upgrading results after the upgrading is finished.
Second, the execution process of the cloud OTA management platform 110:
and receiving the downloading and signature checking results, receiving the upgrading results, and performing state statistics display on the upgrading tasks according to the upgrading results.
Example 1
In this embodiment, the bidirectional authentication process is as follows:
firstly, the execution process of the cloud OTA management platform 110:
1. a message is received from the vehicle-side OTA client 120.
2. And analyzing the certificate information in the message header to obtain the unique identification information of the vehicle-end OTA client or directly obtaining the unique identification information of the vehicle-end OTA client from the message header.
3. And matching the unique identification information of the vehicle-end OTA client with the locally stored unique identification information of the vehicle-end OTA client, and if the matching is successful, allowing the vehicle-end OTA client to access.
Second, the execution process of the car-end OTA client 120:
and carrying the certificate information of the vehicle or the unique identification information of the vehicle OTA client in a message header, and sending the message to the cloud OTA management platform 110.
Example 2
In this embodiment, the bidirectional authentication process is as follows:
firstly, the execution process of the cloud OTA management platform 110:
1. a message is received from the vehicle-side OTA client 120.
2. And analyzing the certificate information in the message header to obtain the unique identification information of the vehicle-end OTA client or directly obtaining the unique identification information of the vehicle-end OTA client from the message header.
3. And matching the unique identification information of the vehicle-end OTA client 120 with the unique identification information of the vehicle-end OTA client in the message body, and if the matching is successful, allowing the vehicle-end OTA client 120 to access, wherein the message body is provided with the vehicle-end OTA client identification information.
Second, the execution process of the car-end OTA client 120:
and carrying the certificate information of the vehicle or the unique identification information of the vehicle OTA client in a message header, and sending the message to the cloud OTA management platform 110.
Example 3
In this embodiment, the bidirectional authentication process is as follows:
firstly, the execution process of the cloud OTA management platform 110:
1. a message is received from the vehicle-side OTA client 120.
2. The encrypted certificate serial number is obtained from the message.
3. And sending the encrypted certificate serial number to a remote certificate verification server for verification, and allowing the vehicle-end OTA client 120 to access if the verification is passed.
Second, the execution process of the car-end OTA client 120:
1. and encrypting the certificate sequence number through a public key distributed by the remote certificate verification server.
2. The encrypted certificate serial number is carried to send a message to the cloud OTA management platform 110.
Specifically, the cloud OTA management platform 110 includes:
and the vehicle data management module 111 is used for acquiring vehicle data from the MES/TSP system 2 or providing a user interface for a user to manually add the vehicle data, wherein the vehicle data comprises the unique identification information of the OTA client at the vehicle end, the information of all ECUs at the vehicle end and the vehicle information.
The unique identification information of the vehicle-end OTA client is a Vehicle Identification Number (VIN), or a TBOX serial number, or a combination of the VIN, the TBOX serial number and a special symbol. The vehicle information includes vehicle type information, vehicle family information, and OEM information.
Tsp (telematics service provider) refers to an automobile remote service provider, and mes (manufacturing execution system) refers to a manufacturing enterprise production process execution system.
The vehicle data management module 111 can actively pull vehicle data from the MES/TSP system 2, and the active pull process can be periodic, manually triggered, or both. The data pulled may be full or incremental.
The user interface can be a web interface, and the user can add the vehicle data in a batch import or single input mode on the web interface.
The vehicle data management module 111 may also receive vehicle data passively from the MES/TSP system 2, either periodically or manually triggered, or both. The passively received data may be full or incremental.
The upgrade package management module 112 is configured to provide a user interface for a user to manually upload the upgrade package, receive upgrade package information manually input by the user, or automatically parse the upgrade package to obtain the upgrade package information, and sign the upgrade package. The upgrade package information is associated with the upgrade package.
The upgrading package information comprises a software version number, a part number of the ECU to be upgraded, hardware information of the ECU to be upgraded, a file type of the upgrading package and a software version number range of the ECU which can be upgraded by using the upgrading package file.
And the upgrading package is uploaded by adopting an HTTP/HTTPS/FTP/FTPS/SFTP protocol, and is a full upgrading package file or a differential upgrading package.
Only one full upgrade package file of the same software version number of the same ECU is allowed to exist. The full package files of different software version numbers of the same ECU are allowed to exist in plurality. The full package of different software version numbers of different ECUs allows for a plurality. The full package of the same software version number of different ECUs allows for a plurality. The differential upgrade package files with the same software version number and the same upgrade source version number of the same ECU only allow to exist one. The differential upgrade package files of the same software version number and different upgrade source version numbers of the same ECU are allowed to exist in a plurality. The number of the differential upgrade package files with different software version numbers, the same or different upgrade source version numbers of the same ECU is allowed to exist.
And the upgrade task management module 113 is configured to create an upgrade task and manage the upgrade task.
Managing upgrade tasks includes deploying tasks, terminating tasks, suspending tasks, re-running tasks, prioritizing between tasks, and task merging.
The upgrading task comprises a unique task identifier, a characteristic expression of a vehicle to be upgraded, a unique identifier range of a vehicle OTA client to be upgraded, an identifier of upgrading package file information, the size of an upgrading package, the sha value of the upgrading package, the encryption mode of the upgrading package, key information for decrypting the upgrading package, a downloading strategy, an upgrading strategy, a rollback strategy, an upgrading sequence of a plurality of upgrading packages arranged according to dependency and atomicity, the starting time and the ending time of the task, the starting time of scheduling, the ending time of scheduling and the priority.
And a communication management module 114, configured to send or receive a message to the vehicle-side OTA client 120.
The vehicle-side OTA client 120 includes:
the communication management module 121 is configured to send or receive a message to the cloud OTA management platform 110.
And the ECU upgrading management module 122 is used for upgrading according to the upgrading task.
Wherein, the message may be: reporting ECU version information, notifying a message of an upgrade task currently, inquiring whether the message of the upgrade task exists or not, upgrading task information, a message of reporting a downloading progress, upgrading result information, details of an upgrading process, reporting hardware information and the like. The bearer mode can be HTTP/HTTPS protocol, or WS/WSS protocol, or adopt the message format meeting OMA specification or JSON specification.
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 (10)

1. An OTA upgrading method of a vehicle ECU, a cloud OTA management platform receives an upgrading request of an accessed vehicle OTA client, a corresponding upgrading task is inquired from a pre-established upgrading task according to the upgrading request, the upgrading task is sent to the vehicle OTA client, the vehicle OTA client is accessed to the cloud OTA management platform, the vehicle OTA client receives the upgrading task and upgrades according to the upgrading task, the upgrading task comprises a download address of an upgrading packet, and the OTA upgrading method is characterized by further comprising the following steps:
when the vehicle-end OTA client accesses the cloud OTA management platform, bidirectional authentication is carried out;
when the upgrade task is created, combining a plurality of upgrade packages into an upgrade package set, wherein the upgrade task further comprises a download address of the upgrade package set and an upgrade sequence of the upgrade packages which is set according to dependency and atomicity;
and when the cloud OTA management platform inquires a plurality of corresponding upgrading tasks of the same ECU according to the upgrading request, if the upgrading tasks are not set with priorities, only the latest upgrading task is sent to the vehicle-end OTA client, if the upgrading tasks are set with priorities, the upgrading tasks are sent to the vehicle-end OTA client from high to low according to the priorities, and for the upgrading tasks with the same priorities, only the latest upgrading task is sent to the vehicle-end OTA client.
2. The OTA upgrade method for a vehicle ECU according to claim 1, further comprising:
the vehicle-end OTA client side:
downloading an upgrading packet according to a downloading strategy in the upgrading task;
checking the signature according to the signature information in the upgrade package;
after the signature verification is finished, reporting the downloading and signature verification results to the cloud OTA management platform;
upgrading according to an upgrading strategy in the upgrading task;
after upgrading is completed, reporting an upgrading result;
the cloud OTA management platform:
receiving the downloading and signature checking result;
and receiving the upgrading result, and performing state statistics display on the upgrading task according to the upgrading result.
3. The OTA upgrade method for a vehicle ECU according to claim 1 or 2, wherein the mutual authentication comprises:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
the certificate information in the message header is analyzed to obtain the unique identification information of the vehicle-end OTA client or the unique identification information of the vehicle-end OTA client is directly obtained from the message header;
and matching the unique identification information of the vehicle-end OTA client with the locally stored unique identification information of the vehicle-end OTA client, and if the matching is successful, allowing the vehicle-end OTA client to access.
The vehicle-end OTA client side:
and carrying the certificate information of the user or the unique identification information of the vehicle-end OTA client in a message header, and sending a message to the cloud OTA management platform.
4. The OTA upgrade method for a vehicle ECU according to claim 1 or 2, wherein the mutual authentication comprises:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
the certificate information in the message header is analyzed to obtain the unique identification information of the vehicle-end OTA client or the unique identification information of the vehicle-end OTA client is directly obtained from the message header;
and matching the unique identification information of the vehicle-end OTA client with the unique identification information of the vehicle-end OTA client in the message body, and if the matching is successful, allowing the vehicle-end OTA client to access.
The vehicle-end OTA client side:
and carrying the certificate information of the user or the unique identification information of the vehicle-end OTA client in a message header, and sending a message to the cloud OTA management platform.
5. The OTA upgrade method for a vehicle ECU according to claim 1 or 2, wherein the mutual authentication comprises:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
obtaining an encrypted certificate serial number from the message;
the encrypted certificate serial number is sent to a remote certificate verification server for verification, and if the verification is passed, the vehicle-end OTA client is allowed to access;
the vehicle-end OTA client side:
encrypting the certificate sequence number through a public key distributed by the remote certificate verification server;
and sending a message to the cloud OTA management platform by carrying the encrypted certificate serial number.
6. The utility model provides a vehicle ECU's OTA upgrade system, includes high in the clouds OTA management platform and car end OTA client, high in the clouds OTA management platform receives the upgrade request of the car end OTA client that inserts, according to corresponding upgrade task is inquired from the upgrade task of establishing in advance to with this upgrade task send for car end OTA client, car end OTA client inserts high in the clouds OTA management platform, car end OTA client receives the upgrade task, and according to the upgrade task upgrades, the upgrade task includes the download address of upgrading the package, its characterized in that still includes:
when the vehicle-end OTA client accesses the cloud OTA management platform, bidirectional authentication is carried out;
when the upgrade task is created, combining a plurality of upgrade packages into an upgrade package set, wherein the upgrade task further comprises a download address of the upgrade package set and an upgrade sequence of the upgrade packages which is set according to dependency and atomicity;
and when the cloud OTA management platform inquires a plurality of corresponding upgrading tasks of the same ECU according to the upgrading request, if the upgrading tasks are not set with priorities, only the latest upgrading task is sent to the vehicle-end OTA client, if the upgrading tasks are set with priorities, the upgrading tasks are sent to the vehicle-end OTA client from high to low according to the priorities, and for the upgrading tasks with the same priorities, only the latest upgrading task is sent to the vehicle-end OTA client.
7. The OTA upgrade system for a vehicle ECU according to claim 6, further comprising:
the vehicle-end OTA client side:
downloading an upgrading packet according to a downloading strategy in the upgrading task;
checking the signature according to the signature information in the upgrade package;
after the signature verification is finished, reporting the downloading and signature verification results to the cloud OTA management platform;
upgrading according to an upgrading strategy in the upgrading task;
after upgrading is completed, reporting an upgrading result;
the cloud OTA management platform:
receiving the downloading and signature checking result;
and receiving the upgrading result, and performing state statistics display on the upgrading task according to the upgrading result.
8. An OTA upgrade system for a vehicle ECU according to claim 6 or claim 7 wherein the mutual authentication comprises:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
the certificate information in the message header is analyzed to obtain the unique identification information of the vehicle-end OTA client or the unique identification information of the vehicle-end OTA client is directly obtained from the message header;
and matching the unique identification information of the vehicle-end OTA client with the locally stored unique identification information of the vehicle-end OTA client, and if the matching is successful, allowing the vehicle-end OTA client to access.
The vehicle-end OTA client side:
and carrying the certificate information of the user or the unique identification information of the vehicle-end OTA client in a message header, and sending a message to the cloud OTA management platform.
9. An OTA upgrade system for a vehicle ECU according to claim 6 or claim 7 wherein the mutual authentication comprises:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
the certificate information in the message header is analyzed to obtain the unique identification information of the vehicle-end OTA client or the unique identification information of the vehicle-end OTA client is directly obtained from the message header;
and matching the unique identification information of the vehicle-end OTA client with the unique identification information of the vehicle-end OTA client in the message body, and if the matching is successful, allowing the vehicle-end OTA client to access.
The vehicle-end OTA client side:
and carrying the certificate information of the user or the unique identification information of the vehicle-end OTA client in a message header, and sending a message to the cloud OTA management platform.
10. An OTA upgrade system for a vehicle ECU according to claim 6 or claim 7 wherein the mutual authentication comprises:
the cloud OTA management platform:
receiving a message from a vehicle-end OTA client;
obtaining an encrypted certificate serial number from the message;
the encrypted certificate serial number is sent to a remote certificate verification server for verification, and if the verification is passed, the vehicle-end OTA client is allowed to access;
the vehicle-end OTA client side:
encrypting the certificate sequence number through a public key distributed by the remote certificate verification server;
and sending a message to the cloud OTA management platform by carrying the encrypted certificate serial number.
CN202010259275.2A 2020-04-03 2020-04-03 OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) Pending CN111478897A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010259275.2A CN111478897A (en) 2020-04-03 2020-04-03 OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010259275.2A CN111478897A (en) 2020-04-03 2020-04-03 OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit)

Publications (1)

Publication Number Publication Date
CN111478897A true CN111478897A (en) 2020-07-31

Family

ID=71750634

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010259275.2A Pending CN111478897A (en) 2020-04-03 2020-04-03 OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit)

Country Status (1)

Country Link
CN (1) CN111478897A (en)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112015489A (en) * 2020-09-18 2020-12-01 华人运通(江苏)技术有限公司 Management method, device, storage medium and system for vehicle-mounted software
CN112256310A (en) * 2020-11-13 2021-01-22 上海伟世通汽车电子系统有限公司 Vehicle instrument OTA upgrading system and method
CN112579125A (en) * 2020-12-10 2021-03-30 四川虹微技术有限公司 Firmware upgrading method and device, electronic equipment and storage medium
CN113110850A (en) * 2021-05-12 2021-07-13 宝能(广州)汽车研究院有限公司 Vehicle upgrading method, device, equipment, vehicle and storage medium
CN113590164A (en) * 2021-08-31 2021-11-02 重庆长安汽车股份有限公司 Method and system for upgrading vehicle control unit software
CN113778498A (en) * 2021-08-23 2021-12-10 武汉中海庭数据技术有限公司 Vehicle data updating method, OTA cloud and vehicle data updating system
CN113992516A (en) * 2021-10-21 2022-01-28 远景智能国际私人投资有限公司 Firmware updating method and device for equipment of Internet of things and Internet of things
CN114745369A (en) * 2022-04-08 2022-07-12 北京汽车集团越野车有限公司 Remote upgrading method and device
CN115333937A (en) * 2022-06-27 2022-11-11 中国第一汽车股份有限公司 Data downloading method and device and electronic equipment
CN115567496A (en) * 2022-09-21 2023-01-03 润芯微科技(江苏)有限公司 OTA (over the air) upgrading method and system
CN117032764A (en) * 2023-10-08 2023-11-10 富钛字节车载软件(长春)有限公司 Vehicle OTA task scheduling method based on MQTT protocol
EP4310669A4 (en) * 2021-03-31 2024-04-17 Huawei Tech Co Ltd Version management method and apparatus

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102387165A (en) * 2010-08-27 2012-03-21 腾讯科技（深圳）有限公司 System and method for upgrading software
WO2013078951A1 (en) * 2011-12-01 2013-06-06 腾讯科技（深圳）有限公司 Method and system for upgrading software
CN104991796A (en) * 2015-06-19 2015-10-21 青岛海信移动通信技术股份有限公司 Method and apparatus for continuous upgrade
CN105159724A (en) * 2015-09-15 2015-12-16 青岛海信移动通信技术股份有限公司 Cross-version upgrade method for software, client and server
CN105933150A (en) * 2016-04-20 2016-09-07 努比亚技术有限公司 OTA upgrade method, device and system
CN106603311A (en) * 2017-01-18 2017-04-26 北京洋浦伟业科技发展有限公司 OTA upgrade method, client, server and system
CN107193612A (en) * 2014-06-27 2017-09-22 青岛海信移动通信技术股份有限公司 The version upgrading method and device of a kind of mobile terminal
CN107844343A (en) * 2017-11-24 2018-03-27 税友软件集团股份有限公司 The upgrade-system and method of a kind of complex services end application system
CN109032912A (en) * 2018-07-25 2018-12-18 北京首汽智行科技有限公司 The method for testing pressure of car-mounted terminal firmware upgrade
CN109062598A (en) * 2018-06-26 2018-12-21 珠海全志科技股份有限公司 A kind of safe OTA upgrade method and system
CN109495307A (en) * 2018-11-27 2019-03-19 北京车和家信息技术有限公司 Method for upgrading system, OTA upgrade package encryption method, terminal device and vehicle
CN109491681A (en) * 2018-10-19 2019-03-19 北京经纬恒润科技有限公司 The upgrade method and device of MCU in a kind of automobile
CN110086885A (en) * 2019-05-10 2019-08-02 上海擎感智能科技有限公司 The upgrade package method for down loading and device of space download technology, storage medium and terminal
CN110134418A (en) * 2019-05-10 2019-08-16 上海擎感智能科技有限公司 Vehicle upgrade method and device, storage medium and terminal based on space download technology
CN110378123A (en) * 2019-07-18 2019-10-25 上海擎感智能科技有限公司 A kind of method for upgrading software and system for car-mounted terminal
CN110378153A (en) * 2019-07-18 2019-10-25 上海擎感智能科技有限公司 A kind of upgrade package safety downloading method and system
CN110535941A (en) * 2019-08-29 2019-12-03 湖北亿咖通科技有限公司 Onboard system update method, electronic equipment and storage medium
CN110865842A (en) * 2018-08-28 2020-03-06 成都鼎桥通信技术有限公司 OTA (over the air) upgrading method and device

Patent Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102387165A (en) * 2010-08-27 2012-03-21 腾讯科技（深圳）有限公司 System and method for upgrading software
WO2013078951A1 (en) * 2011-12-01 2013-06-06 腾讯科技（深圳）有限公司 Method and system for upgrading software
CN107193612A (en) * 2014-06-27 2017-09-22 青岛海信移动通信技术股份有限公司 The version upgrading method and device of a kind of mobile terminal
CN104991796A (en) * 2015-06-19 2015-10-21 青岛海信移动通信技术股份有限公司 Method and apparatus for continuous upgrade
CN105159724A (en) * 2015-09-15 2015-12-16 青岛海信移动通信技术股份有限公司 Cross-version upgrade method for software, client and server
CN105933150A (en) * 2016-04-20 2016-09-07 努比亚技术有限公司 OTA upgrade method, device and system
CN106603311A (en) * 2017-01-18 2017-04-26 北京洋浦伟业科技发展有限公司 OTA upgrade method, client, server and system
CN107844343A (en) * 2017-11-24 2018-03-27 税友软件集团股份有限公司 The upgrade-system and method of a kind of complex services end application system
CN109062598A (en) * 2018-06-26 2018-12-21 珠海全志科技股份有限公司 A kind of safe OTA upgrade method and system
CN109032912A (en) * 2018-07-25 2018-12-18 北京首汽智行科技有限公司 The method for testing pressure of car-mounted terminal firmware upgrade
CN110865842A (en) * 2018-08-28 2020-03-06 成都鼎桥通信技术有限公司 OTA (over the air) upgrading method and device
CN109491681A (en) * 2018-10-19 2019-03-19 北京经纬恒润科技有限公司 The upgrade method and device of MCU in a kind of automobile
CN109495307A (en) * 2018-11-27 2019-03-19 北京车和家信息技术有限公司 Method for upgrading system, OTA upgrade package encryption method, terminal device and vehicle
CN110086885A (en) * 2019-05-10 2019-08-02 上海擎感智能科技有限公司 The upgrade package method for down loading and device of space download technology, storage medium and terminal
CN110134418A (en) * 2019-05-10 2019-08-16 上海擎感智能科技有限公司 Vehicle upgrade method and device, storage medium and terminal based on space download technology
CN110378123A (en) * 2019-07-18 2019-10-25 上海擎感智能科技有限公司 A kind of method for upgrading software and system for car-mounted terminal
CN110378153A (en) * 2019-07-18 2019-10-25 上海擎感智能科技有限公司 A kind of upgrade package safety downloading method and system
CN110535941A (en) * 2019-08-29 2019-12-03 湖北亿咖通科技有限公司 Onboard system update method, electronic equipment and storage medium

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112015489A (en) * 2020-09-18 2020-12-01 华人运通(江苏)技术有限公司 Management method, device, storage medium and system for vehicle-mounted software
CN112256310A (en) * 2020-11-13 2021-01-22 上海伟世通汽车电子系统有限公司 Vehicle instrument OTA upgrading system and method
CN112579125A (en) * 2020-12-10 2021-03-30 四川虹微技术有限公司 Firmware upgrading method and device, electronic equipment and storage medium
EP4310669A4 (en) * 2021-03-31 2024-04-17 Huawei Tech Co Ltd Version management method and apparatus
CN113110850B (en) * 2021-05-12 2022-09-20 宝能(广州)汽车研究院有限公司 Vehicle upgrading method, device, equipment, vehicle and storage medium
CN113110850A (en) * 2021-05-12 2021-07-13 宝能(广州)汽车研究院有限公司 Vehicle upgrading method, device, equipment, vehicle and storage medium
CN113778498A (en) * 2021-08-23 2021-12-10 武汉中海庭数据技术有限公司 Vehicle data updating method, OTA cloud and vehicle data updating system
CN113590164A (en) * 2021-08-31 2021-11-02 重庆长安汽车股份有限公司 Method and system for upgrading vehicle control unit software
CN113590164B (en) * 2021-08-31 2024-03-22 重庆长安汽车股份有限公司 Method and system for upgrading software of whole vehicle controller
CN113992516A (en) * 2021-10-21 2022-01-28 远景智能国际私人投资有限公司 Firmware updating method and device for equipment of Internet of things and Internet of things
CN114745369A (en) * 2022-04-08 2022-07-12 北京汽车集团越野车有限公司 Remote upgrading method and device
CN115333937A (en) * 2022-06-27 2022-11-11 中国第一汽车股份有限公司 Data downloading method and device and electronic equipment
CN115333937B (en) * 2022-06-27 2023-09-01 中国第一汽车股份有限公司 Data downloading method and device and electronic equipment
CN115567496A (en) * 2022-09-21 2023-01-03 润芯微科技(江苏)有限公司 OTA (over the air) upgrading method and system
CN117032764A (en) * 2023-10-08 2023-11-10 富钛字节车载软件(长春)有限公司 Vehicle OTA task scheduling method based on MQTT protocol
CN117032764B (en) * 2023-10-08 2023-12-05 富钛字节车载软件(长春)有限公司 Vehicle OTA task scheduling method based on MQTT protocol

Similar Documents

Publication Publication Date Title
CN111478897A (en) OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit)
CN111190633B (en) OTA (over the air) upgrading system and method for whole electric control unit
US10592231B2 (en) Vehicle information communication system
CN111385191B (en) Vehicle-mounted interconnection gateway, vehicle OTA upgrading system and method, and computer storage medium
CN111061499B (en) ECU updating method and system based on file system
JP6219301B2 (en) System and corresponding method for providing telematic services
CN109787774B (en) Upgrade downloading method and device based on digital signature verification, server and terminal
US20170344355A1 (en) Updating vehicle system modules
CN111277477B (en) FOTA system supporting simultaneous upgrading of vehicle-mounted multiple network segments
US20140282470A1 (en) Remote transfer of electronic images to a vehicle
US20120167071A1 (en) Software update apparatus and method of vehicle
CN112134940A (en) OTA upgrade task life cycle strategy management method
US20220012043A1 (en) Vehicle information communication system
CN113778498A (en) Vehicle data updating method, OTA cloud and vehicle data updating system
CN102622705A (en) Terminal management system for automatic management of POS terminal upgrading and upgrading management method thereof
US20130167119A1 (en) Apparatus and method for supporting software development for vehicle
CN113268257A (en) Vehicle-mounted application upgrading system, method and computer storage medium
CN116366636A (en) Vehicle software upgrading method and device and automobile
CN109862108B (en) Service scheduling method based on card, service terminal, vehicle terminal and client terminal
CN114721691B (en) Method for updating preassembled application of vehicle terminal
US11706207B1 (en) Application programming interface for certificate management systems
CN116088913B (en) Integrated device, method and computer program product for whole vehicle upgrade software
JP7239025B2 (en) Center equipment and vehicle information communication system
CN114138306A (en) Vehicle FOTA rapid upgrading method and system supporting distributed downloading
CN116974613A (en) Upgrading method and device, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20200731

RJ01 Rejection of invention patent application after publication