CN116437337A - Multi-communication type OTA upgrading system and method for vehicle-mounted bus and vehicle - Google Patents
Multi-communication type OTA upgrading system and method for vehicle-mounted bus and vehicle Download PDFInfo
- Publication number
- CN116437337A CN116437337A CN202310696961.XA CN202310696961A CN116437337A CN 116437337 A CN116437337 A CN 116437337A CN 202310696961 A CN202310696961 A CN 202310696961A CN 116437337 A CN116437337 A CN 116437337A
- Authority
- CN
- China
- Prior art keywords
- ota
- upgrading
- upgrade
- vehicle
- software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004891 communication Methods 0.000 title claims abstract description 70
- 238000000034 method Methods 0.000 title claims abstract description 45
- 230000006837 decompression Effects 0.000 claims abstract description 4
- 238000012795 verification Methods 0.000 claims abstract description 4
- 238000004806 packaging method and process Methods 0.000 claims description 6
- 230000005540 biological transmission Effects 0.000 claims description 4
- 238000003745 diagnosis Methods 0.000 claims description 3
- 238000011010 flushing procedure Methods 0.000 description 3
- 230000001680 brushing effect Effects 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
- H04W8/245—Transfer of terminal data from a network towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/40267—Bus for use in transportation systems
- H04L2012/40273—Bus for use in transportation systems the transportation system being a vehicle
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Small-Scale Networks (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to the technical field of automobile electronics, in particular to a vehicle-mounted bus multi-communication type OTA upgrading system and method and a vehicle. Uploading a target software package to an OTA upgrading cloud to finish the deployment of an upgrading task; the upgrading component downloads a software upgrading packet after receiving an upgrading task, performs signature verification and decompression, and the vehicle-mounted remote control terminal sends message data to the gateway according to a communication mode defined in file information; the target ECU module receives the message data and responds to the refreshing request, executes the refreshing task on the message data, and feeds back the refreshing progress to the upgrading component; the communication mode in the configuration file is identified and selected through the vehicle-mounted remote control terminal, so that the time is shorter in time complexity. Meanwhile, the frame loss risk caused by gateway routing is completely avoided, the success rate of upgrading is improved, and the cost of changing parts and labor cost of lifting and hanging the ECU module caused by frame loss is reduced.
Description
Technical Field
The invention relates to the technical field of automobile electronics, in particular to a vehicle-mounted bus multi-communication type OTA upgrading system and method and a vehicle.
Background
In recent years, the industrialization of automobiles in China is gradually improved, the technology of Internet of vehicles is becoming more and more popular, and the method of controlling the vehicles by using remote communication is no longer fresh. Meanwhile, an Over-the-Air (OTA) upgrading function provides a mode of updating software of a vehicle ECU (ElectronicControl Unit ) so as to greatly facilitate a vehicle owner.
However, with the complexity and diversification of the whole vehicle architecture, the process of performing OTA upgrade by the vehicle module involves multiple communication modes, and the switching of the multiple communication modes requires a gateway to be responsible for routing, but in practice, due to different communication rates of different communication modes, the problem of frame loss occurs in the gateway routing, which results in failure of OTA upgrade.
Disclosure of Invention
The present invention aims to at least ameliorate one of the technical problems of the prior art. Therefore, the invention provides a vehicle-mounted bus multi-communication type OTA upgrading system, a method and a vehicle.
An embodiment of the present invention provides an on-vehicle bus multi-communication type OTA upgrade system, including:
the OTA cloud end is used for deploying upgrading tasks;
the vehicle-mounted remote control Terminal (TBOX) is communicated with the OTA cloud through a 4G network, and comprises an OTA component which is used for downloading, checking and decompressing a software upgrading package and realizing internal transmission of the vehicle-mounted remote control terminal through a configuration file and a data package in the software package;
the gateway is in communication connection with the vehicle-mounted remote control terminal;
and the target ECU module is in communication connection with the gateway.
In a possible implementation manner of the first aspect, the upgrading task of the OTA cloud deployment includes packaging, encrypting, signing, uploading a software package and upgrading the task.
According to the OTA upgrading system for the vehicle-mounted bus multi-communication type, the communication mode for sending the upgrading packet data is informed through the configuration file, and the sending communication mode is identified and selected by the TBOX, so that compared with the existing gateway switching protocol, the OTA upgrading system for the vehicle-mounted bus multi-communication type is shorter in time complexity. The method for distinguishing the refreshing communication mode by adopting the configuration file mode completely avoids the frame loss risk caused by gateway routing, improves the success rate of upgrading, and reduces the cost of changing the parts and the labor cost of lifting the ECU module caused by frame loss.
According to the embodiment of the second aspect of the invention, the method for upgrading the vehicle-mounted bus multi-communication type OTA comprises the following steps:
step S100, building the vehicle-mounted bus multi-communication type OTA upgrading system;
step S200, a vehicle operator uploads a software package of a target ECU module to an OTA cloud end, and the OTA cloud end completes deployment of an upgrading task;
step S300, after receiving the upgrade task, the OTA component downloads a software upgrade package of the OTA cloud end, and performs signature verification and decompression;
step S400, the OTA component transmits the configuration file information and the upgrade data packet after the software upgrade packet is decompressed in the TBOX;
step S500, after the TBOX receives the configuration file information and the upgrade data packet, message data is sent to the gateway according to a communication mode defined in the configuration file information;
step S600, the gateway receives the message data sent by the TBOX and forwards the message data to the target ECU module;
step S700, the target ECU module responds to the refreshing request and executes the refreshing task on the received message data and feeds back the refreshing progress to the OTA component;
step S800, after receiving the instruction after finishing the writing, the OTA component reports the writing result to the OTA cloud;
step S900, the multi-communication type OTA upgrading process for the vehicle bus is ended.
In a possible implementation manner of the second aspect, the step S200 further includes updating a configuration file, packaging a data packet and the configuration file.
In a possible implementation manner of the second aspect, the step S300 further includes, before the OTA component receives the upgrade task, the OTA cloud end calling the ringing server to wake up the TBOX, and after the TBOX is woken up, pulling up the OTA component procedure to communicate with the OTA cloud end.
In a possible implementation manner of the second aspect, the communication manner in step S500 includes CAN and CANFD.
In a possible implementation manner of the second aspect, step S800 specifically includes the following:
the OTA component directly receives an upgrade result returned by the target ECU module, compares the target version number of the upgrade result with the software version number issued by the OTA cloud, judges that the upgrade is successful if the target version number is consistent with the software version number issued by the OTA cloud, and judges that the upgrade is failed if the target version number is not consistent with the software version number issued by the OTA cloud.
In a possible implementation manner of the second aspect, step S800 specifically includes the following:
and if the upgrading task is finished, the OTA component does not receive an upgrading result returned by the target ECU module, actively transmits a diagnosis command to read the software version number of the target ECU module, compares the read target version number with the software version number issued by the OTA cloud, judges that the upgrading is successful, and if the upgrading task is finished, judges that the upgrading is failed.
In a possible implementation manner of the second aspect, the target ECU module responds to the flushing request in step S700 and performs a flushing task on the received message data and feeds back the flushing progress to the OTA component in time through the gateway.
According to the OTA upgrading method for the vehicle-mounted bus multi-communication type, the communication mode for sending the upgrading packet data is informed through the configuration file, and the sending communication mode is identified and selected by the TBOX, so that compared with the existing gateway switching protocol, the OTA upgrading method for the vehicle-mounted bus multi-communication type is shorter in time complexity. The method for distinguishing the refreshing communication mode by adopting the configuration file mode completely avoids the frame loss risk caused by gateway routing, improves the success rate of upgrading, and reduces the cost of changing the parts and the labor cost of lifting the ECU module caused by frame loss.
According to the vehicle, the vehicle comprises an automobile OTA upgrading system, and the automobile OTA upgrading system performs OTA upgrading on the vehicle-mounted bus multi-communication type by executing the upgrading method.
Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a system block diagram for an in-vehicle bus multi-communication type OTA upgrade system according to an embodiment of the present invention;
fig. 2 is a flow chart of a method for an on-board bus multi-communication type OTA upgrade method according to an embodiment of the present invention.
Detailed Description
The following detailed description of embodiments of the present invention is exemplary, with reference to the accompanying drawings, it being understood that the specific embodiments described herein are merely illustrative of the application and not intended to limit the application.
It will be understood that when an element is referred to as being "fixed to" another element, it can be directly on the other element or intervening elements may also be present. When an element is referred to as being "connected" to another element, it can be directly connected to the other element or intervening elements may also be present.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used herein in the description of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The term "and/or" as used herein includes any and all combinations of one or more of the associated listed items.
The terms "first," second, "" third and the like in the description and in the claims and drawings are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprising," "including," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion. For example, a series of steps or elements may be included, or alternatively, steps or elements not listed or, alternatively, other steps or elements inherent to such process, method, article, or apparatus may be included.
Only some, but not all, of the matters relevant to the present application are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart depicts operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently, or at the same time. Furthermore, the order of the operations may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figures. The processes may correspond to methods, functions, procedures, subroutines, and the like.
As used in this specification, the terms "component," "module," "system," "unit," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a unit may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or being distributed between two or more computers. Furthermore, these units may be implemented from a variety of computer-readable media having various data structures stored thereon. The units may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., second unit data from another unit interacting with a local system, distributed system, and/or across a network).
Example 1
Referring to fig. 1, an OTA upgrade system for a vehicle bus of a multi-communication type according to an embodiment of the first aspect of the present invention includes:
the OTA cloud is used for uploading a software compression package of the target ECU containing the configuration file and pushing the software compression package to the OTA component;
the vehicle-mounted remote control terminal is communicated with the OTA cloud through a 4G network, and comprises an OTA component for downloading, checking and decompressing a software upgrading package, and realizing internal transmission of a configuration file and a data package in the software package;
the gateway is compatible with a CAN communication protocol and is used for receiving the message and forwarding the message, and the gateway is in communication connection with the vehicle-mounted remote control terminal;
and the target ECU module is in communication connection with the gateway and is used for receiving the message data forwarded by the gateway and realizing the self-refreshing task.
Specifically, the OTA cloud deployment upgrade task comprises the packaging, encryption, signature, uploading of the software package and the upgrade task of upgrade software.
According to the OTA upgrading system for the vehicle-mounted bus multi-communication type, the communication mode for sending the upgrading packet data is informed through the configuration file, and the sending communication mode is identified and selected by the TBOX, so that compared with the existing gateway switching protocol, the OTA upgrading system for the vehicle-mounted bus multi-communication type is shorter in time complexity. The method for distinguishing the refreshing communication mode by adopting the configuration file mode completely avoids the frame loss risk caused by gateway routing, improves the success rate of upgrading, and reduces the cost of changing the parts and the labor cost of lifting the ECU module caused by frame loss.
Example 2
Referring to fig. 2, the present embodiment provides a method for upgrading a vehicle bus multi-communication type OTA, which includes the following steps:
step S100, a vehicle-mounted bus multi-communication type remote upgrading system is built, and the system specifically comprises a remote cloud end, wherein the remote cloud end is used for deploying upgrading tasks;
the vehicle-mounted remote control terminal is in vehicle cloud communication with the remote cloud through a 4G network, and comprises a remote component used for downloading, checking and decompressing a software upgrading package and realizing internal transmission of the vehicle-mounted remote control terminal through configuration files and data packages in the software package;
the gateway is in communication connection with the vehicle-mounted remote control terminal;
and the target ECU module is in communication connection with the gateway.
Step S200, the vehicle operator uploads the software package of the target electronic control unit module to the remote cloud, the remote cloud completes the deployment of the upgrade task,
specifically, the step S200 further includes updating a configuration file, packaging a data packet and the configuration file, selecting a vehicle to be upgraded and a target ECU module, setting an upgrade mode upgrade time, and the like.
Step S300, after receiving an upgrade task, a remote component downloads a software upgrade package of a remote cloud and performs signature verification and decompression;
step S400, the remote component transmits the configuration file information and the upgrade data packet after the software upgrade packet is decompressed in the vehicle-mounted remote control terminal;
step S500, after receiving the configuration file information and the upgrade data packet, the vehicle-mounted remote control terminal sends message data to the gateway according to a communication mode defined in the configuration file information;
step S600, the gateway receives message data sent by the vehicle-mounted remote control terminal and forwards the message data to the target electronic control unit module;
step S700, the target electronic control unit module responds to the refreshing request, executes the refreshing task on the received message data and feeds back the refreshing progress to the remote component;
step S800, after receiving the instruction after finishing the brushing, the remote component reports the brushing result to the remote cloud;
step S900, the multi-communication type remote upgrade process for the vehicle bus is ended.
Specifically, the step S300 further includes that before the remote component receives the upgrade task, the remote cloud needs to call the ringing server to wake up the vehicle-mounted remote control terminal, and after the vehicle-mounted remote control terminal wakes up, the remote component program is pulled up to communicate with the remote cloud.
Specifically, the communication method in step S500 includes CAN and CANFD.
Specifically, step S800 specifically includes the following:
the remote component directly receives an upgrade result returned by the target ECU module, compares the target version number of the upgrade result with the software version number issued by the remote cloud, and judges that the upgrade is successful if the target version number is consistent with the software version number issued by the remote cloud, otherwise, judges that the upgrade is failed.
Specifically, step S800 specifically includes the following:
and after the upgrading task expires, the remote component does not receive an upgrading result returned by the target ECU module, actively transmits a diagnosis command to read the software version number of the target ECU module, compares the read target version number with the software version number issued by the remote cloud, judges that the upgrading is successful if the read target version number is consistent with the software version number issued by the remote cloud, and judges that the upgrading is failed if the read target version number is not consistent with the software version number issued by the remote cloud.
Specifically, in step S700, the target ECU module responds to the refresh request and executes the refresh task on the received message data, and timely feeds back the refresh progress to the remote component through the gateway.
According to the OTA upgrading method for the vehicle-mounted bus multi-communication type, the communication mode for sending the upgrading packet data is informed through the configuration file, and the vehicle-mounted remote control terminal recognizes and selects the sending communication mode. The method for distinguishing the refreshing communication mode by adopting the configuration file mode completely avoids the frame loss risk caused by gateway routing, improves the success rate of upgrading, and reduces the cost of changing the parts and the labor cost of lifting the ECU module caused by frame loss.
Example 3
The embodiment provides a vehicle, which comprises an automobile OTA upgrading system, wherein the automobile OTA upgrading system performs OTA upgrading on a vehicle-mounted bus multi-communication type by executing the upgrading method.
In the description of the present invention, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", "axial", "radial", "circumferential", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings are merely for convenience in describing the present invention and simplifying the description, and do not indicate or imply that the device or element being referred to must have a specific orientation, be configured and operated in a specific orientation, and therefore should not be construed as limiting the invention.
In the description of the present specification, reference to the terms "one embodiment," "some embodiments," "illustrative embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples.
It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application for the embodiment. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly understand that the embodiments described herein may be combined with other embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
While embodiments of the present invention have been shown and described, it will be understood by those of ordinary skill in the art that: many changes, modifications, substitutions and variations may be made to the embodiments without departing from the spirit and principles of the invention, the scope of which is defined by the claims and their equivalents.
Claims (10)
1. An on-board bus multi-communication type OTA upgrading method is characterized by comprising the following steps:
step S100, constructing an OTA upgrading system for a vehicle-mounted bus with multiple communication types;
step S200, a vehicle operator uploads a software package of a target ECU module to an OTA cloud end, and the OTA cloud end completes deployment of an upgrading task;
step S300, after receiving the upgrade task, the OTA component downloads a software upgrade package of the OTA cloud end, and performs signature verification and decompression;
step S400, the OTA component transmits the configuration file information and the upgrade data packet after the software upgrade packet is decompressed in the TBOX;
step S500, after the TBOX receives the configuration file information and the upgrade data packet, message data is sent to the gateway according to a communication mode defined in the configuration file information;
step S600, the gateway receives the message data sent by the TBOX and forwards the message data to the target ECU module;
step S700, the target ECU module responds to the refreshing request and executes the refreshing task on the received message data and feeds back the refreshing progress to the OTA component;
step S800, after receiving the instruction after finishing the writing, the OTA component reports the writing result to the OTA cloud;
step S900, the multi-communication type OTA upgrading process for the vehicle bus is ended.
2. The method for OTA upgrade of multiple communication types of vehicle buses according to claim 1, wherein said step S200 further comprises updating of configuration files, packaging of data packets and configuration files.
3. The method of claim 1, wherein step S300 further includes the step of the OTA cloud end calling a ringing server to wake up a TBOX before the OTA component receives the upgrade task, and pulling up the OTA component program to communicate with the OTA cloud end after the TBOX is waken up.
4. The method for OTA upgrades of multiple communication types of an on-board bus according to claim 1, wherein the communication means in step S500 comprises CAN, CANFD.
5. The method for OTA upgrading of multiple communication types of on-board buses according to claim 1, wherein step S800 specifically comprises the following steps:
the OTA component directly receives an upgrade result returned by the target ECU module, compares the target version number of the upgrade result with the software version number issued by the OTA cloud, judges that the upgrade is successful if the target version number is consistent with the software version number issued by the OTA cloud, and judges that the upgrade is failed if the target version number is not consistent with the software version number issued by the OTA cloud.
6. The method for OTA upgrading of multiple communication types of on-board buses according to claim 1, wherein step S800 specifically comprises the following steps:
and if the upgrading task is finished, the OTA component does not receive an upgrading result returned by the target ECU module, actively transmits a diagnosis command to read the software version number of the target ECU module, compares the read target version number with the software version number issued by the OTA cloud, judges that the upgrading is successful, and if the upgrading task is finished, judges that the upgrading is failed.
7. The method for OTA upgrades of the multiple communication types of the vehicle bus according to claim 1, wherein the target ECU module in step S700 responds to the flush request and performs a flush task on the received message data and feeds back the flush progress to the OTA component in time through the gateway.
8. An OTA upgrade system for vehicle bus multi-communication type is characterized in that the system is used for realizing
The steps for an on-board bus multi-communication type OTA upgrade method according to any one of claims 1 to 7, comprising:
the OTA cloud end is used for deploying upgrading tasks;
the vehicle-mounted remote control terminal is communicated with the OTA cloud through a 4G network, and comprises an OTA component for downloading, checking and decompressing a software upgrading package, and realizing internal transmission of a configuration file and a data package in the software package;
the gateway is in communication connection with the vehicle-mounted remote control terminal;
and the target ECU module is in communication connection with the gateway.
9. The system of claim 8, wherein the OTA cloud deployment upgrade tasks include packaging, encryption, signing, uploading software packages, and upgrade tasks of upgrade software.
10. A vehicle comprising an automotive OTA upgrade system, wherein the automotive OTA upgrade system performs an OTA upgrade of a vehicle bus multi-communication type by an upgrade method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310696961.XA CN116437337A (en) | 2023-06-13 | 2023-06-13 | Multi-communication type OTA upgrading system and method for vehicle-mounted bus and vehicle |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310696961.XA CN116437337A (en) | 2023-06-13 | 2023-06-13 | Multi-communication type OTA upgrading system and method for vehicle-mounted bus and vehicle |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116437337A true CN116437337A (en) | 2023-07-14 |
Family
ID=87091117
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310696961.XA Pending CN116437337A (en) | 2023-06-13 | 2023-06-13 | Multi-communication type OTA upgrading system and method for vehicle-mounted bus and vehicle |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116437337A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117440363A (en) * | 2023-09-08 | 2024-01-23 | 重庆数智融合创新科技有限公司 | Production line terminal data self-adaptive distribution method and system based on 5G technology |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111682965A (en) * | 2020-05-25 | 2020-09-18 | 青岛海信日立空调系统有限公司 | FOTA controller |
| CN114201192A (en) * | 2021-11-24 | 2022-03-18 | 一汽奔腾轿车有限公司 | Cloud-configurable automobile OTA (over the air) upgrading system and method |
| CN115051975A (en) * | 2021-02-26 | 2022-09-13 | 威马智慧出行科技(上海)股份有限公司 | ECU remote upgrading method based on vehicle-mounted Ethernet |
| CN115257596A (en) * | 2022-07-28 | 2022-11-01 | 一汽奔腾轿车有限公司 | System and method for switching over-the-air (OTA) upgrading power supply modes of automobile |
| CN115391180A (en) * | 2022-08-04 | 2022-11-25 | 安徽蔚来智驾科技有限公司 | Closed loop simulation method, system and medium for intelligent driving function |
-
2023
- 2023-06-13 CN CN202310696961.XA patent/CN116437337A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111682965A (en) * | 2020-05-25 | 2020-09-18 | 青岛海信日立空调系统有限公司 | FOTA controller |
| CN115051975A (en) * | 2021-02-26 | 2022-09-13 | 威马智慧出行科技(上海)股份有限公司 | ECU remote upgrading method based on vehicle-mounted Ethernet |
| CN114201192A (en) * | 2021-11-24 | 2022-03-18 | 一汽奔腾轿车有限公司 | Cloud-configurable automobile OTA (over the air) upgrading system and method |
| CN115257596A (en) * | 2022-07-28 | 2022-11-01 | 一汽奔腾轿车有限公司 | System and method for switching over-the-air (OTA) upgrading power supply modes of automobile |
| CN115391180A (en) * | 2022-08-04 | 2022-11-25 | 安徽蔚来智驾科技有限公司 | Closed loop simulation method, system and medium for intelligent driving function |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117440363A (en) * | 2023-09-08 | 2024-01-23 | 重庆数智融合创新科技有限公司 | Production line terminal data self-adaptive distribution method and system based on 5G technology |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10782955B2 (en) | Pre-shutdown swap verification | |
| CN112470118B (en) | Vehicle electronic control system and program update consent determination method | |
| WO2020022265A1 (en) | Electronic control system for vehicle, method for determining authorization of program update, and program for determining authorization of program update | |
| US10963241B2 (en) | Control apparatus, program update method, and computer program | |
| CN111061499A (en) | ECU updating method and system based on file system | |
| WO2011055447A1 (en) | Vehicle gateway device | |
| CN110928567A (en) | Vehicle system upgrading method, terminal device and computer-readable storage medium | |
| US10970063B2 (en) | Relay apparatus, transfer method, and computer program | |
| CN109673009B (en) | Method and device for upgrading VCU software in air | |
| CN116437337A (en) | Multi-communication type OTA upgrading system and method for vehicle-mounted bus and vehicle | |
| CN213303011U (en) | OTA-based vehicle ECU upgrading system | |
| CN111399885B (en) | Vehicle component upgrading pushing method and device and computer readable storage medium | |
| CN110187904B (en) | Device and method for updating vehicle controller firmware | |
| US20240069906A1 (en) | Server, software update system, distribution method, and non-transitory storage medium | |
| KR20220156057A (en) | Devices and methods for managing electronic control units of a motor vehicle | |
| CN115344281A (en) | Finished automobile OTA (over the air) upgrading method, system, storage medium and equipment | |
| KR20070076201A (en) | Rom program update system and method do electron control unit in vehicles | |
| JP2022168981A (en) | Update control system, update control method, update control program, and on-vehicle control apparatus | |
| US20230259354A1 (en) | Program management device, program management method, and recording medium | |
| CN116382747A (en) | Method for upgrading vehicle ECU through wifi upgrading equipment | |
| US20220391193A1 (en) | Ota master, system, method, non-transitory storage medium, and vehicle | |
| CN116048587A (en) | Remote automatic upgrading method, device, server, equipment and medium for vehicle | |
| CN115904437A (en) | Parallel flash system and method for automobile electronic control unit | |
| WO2022205443A1 (en) | Software upgrade method and apparatus | |
| KR20150043732A (en) | System and method for software update of vehicle controller |
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: 20230714 |
|
| RJ01 | Rejection of invention patent application after publication |