CN114979297B - Vehicle software version large-span OTA upgrading method - Google Patents
Vehicle software version large-span OTA upgrading method Download PDFInfo
- Publication number
- CN114979297B CN114979297B CN202210582309.0A CN202210582309A CN114979297B CN 114979297 B CN114979297 B CN 114979297B CN 202210582309 A CN202210582309 A CN 202210582309A CN 114979297 B CN114979297 B CN 114979297B
- Authority
- CN
- China
- Prior art keywords
- ota
- software
- version
- upgrade
- controller
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- 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
- 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)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a vehicle software version large-span OTA upgrading method, which comprises the following steps: 1) Acquiring current version information of controller software; 2) Judging whether the current software version of the controller is lower than the software version required by normal upgrading, if yes, executing the step 3), otherwise, executing the step 4); 3) Executing the simple upgrading task to update the OTA application software and the controller software to the transition version; 4) Performing the normal upgrade task updates the OTA application software and the controller software to the latest version. In the invention, when the software version of the controller is too low to directly upgrade the latest version, the transient version software is adopted to temporarily replace the OTA application and the upgrade program of the controller, so that the cross-multi-version forced upgrade is realized, the problem that the user cannot upgrade the latest version OTA upgrade task on line once due to too low software version of the controller and too large software version gap can be effectively solved, and the effects of improving the OTA upgrade reliability and the user experience are obtained.
Description
Technical Field
The invention belongs to the technical field of automobile intellectualization, and particularly relates to a large-span OTA upgrading method for a vehicle software version.
Background
With the rapid development of automobile intellectualization, development of automobile software is more and more emphasized, and OTA (over the air) upgrading requirements of automobile controller software are more and more frequent. When the train enterprise maintenance platform issues an OTA upgrading task to the train, most users choose to ignore the upgrading message in consideration of time; over time, versions of controller software for the same model on the market become irregular, and due to adjustment of requirements or modifications made to some major problems, the latest version of controller software may be greatly different from the old version of controller software; when the upgrade condition is detected, the upgrade flow or the communication protocol part is changed, or the latest version of software cannot be supported due to overlarge difference between the new version and the old version of the controller firmware, the situation of failure of OTA upgrade can occur. In addition, each time an upgrade message is received by a part of users, only part of software controllers may be upgraded, but the associated software controller version is not updated all the time, so that the associated software controller version is too low, other controller states are relied on in the upgrading process, and the OTA upgrade may also fail due to incompatibility of protocols.
For the above situation, the current common solution in the market is to start the vehicle back to the 4S store, upgrade the vehicle by the service personnel of the 4S store through a special online or offline channel, and upgrade the vehicle to the latest version by multiple intermediate versions. Therefore, a method capable of performing OTA upgrading across multiple versions is needed to solve the problem that the latest version of OTA upgrading task cannot be completed on line at one time because the controller software version is too low as the user does not upgrade for a long time.
Disclosure of Invention
Aiming at the defects of the prior art, the technical problem to be solved by the invention is to provide a vehicle software version large-span OTA upgrading method, which solves the problem that the latest version OTA upgrading task cannot be completed on line at one time due to overlarge software version gap, and achieves the effects of improving the OTA upgrading reliability and the user experience.
In order to solve the technical problems, the invention adopts the following technical scheme:
a vehicle software version large-span OTA upgrading method comprises the following steps:
1) The OTA application acquires the current version information of the controller software and uploads the current version information to an OTA server;
2) The OTA server judges whether the current software version of the controller is lower than the software version required by normal upgrading, if yes, the step 3) is executed, and if not, the step 4) is executed;
3) The OTA server executes a simple upgrading task to update OTA application software and controller software to a transition version;
4) The OTA server performs normal upgrade tasks to update the OTA application software and the controller software to the latest version.
Further, step 3) comprises the following sub-steps:
31 The OTA server obtains the transition version software of the OTA application and the controller from the database and transmits the transition version software to the OTA application;
32 OTA application updates the OTA application software and the controller software to the transition version based on the transition version software;
33 The OTA application feeds the upgrading result back to the OTA server, and the OTA server transmits the latest version software to the OTA application.
Further, in step 32), the OTA application software upgrade is prioritized over the controller software upgrade.
Further, the transitional version software of the OTA application can be downward compatible with the functions of the OTA application and support easy upgrade.
Further, the transitional version of the controller supports upgrades of low version controller software and facilitates upgrades.
Further, the easy upgrade refers to temporarily replacing a normal upgrade protocol between the OTA application and the controller to be an easy upgrade protocol to remove more condition detection and cumbersome handshake signals outside the association.
Further, step 31) further includes the OTA server sending a protocol switching signal to the OTA application, and step 32) further includes the OTA application receiving a protocol switching signal to switch the normal upgrade protocol to the easy upgrade protocol.
Further, the simple upgrade protocol comprises the functions of version request, upgrade request, file transmission, file verification, upgrade progress reply and installation result reply.
Further, the OTA application can complete the updating confirmation of the controller and the OTA application and the updating confirmation of the controller and the OTA application by transmitting the updating packet to the controller, the firmware and the program in the controller based on the simple updating protocol.
Compared with the prior art, the invention has the following beneficial effects:
the invention relates to a vehicle software version large-span OTA upgrading method, which comprises the steps of pre-storing transition version software of an OTA application and a controller in an OTA server, replacing a normal upgrading protocol of the OTA application with a simple upgrading protocol when the OTA server knows that the software version of the controller is too low to directly upgrade the latest version, issuing the transition version software to quickly upgrade the OTA application and the controller to the transition version, and then normally upgrading. The invention adopts the transition version software to temporarily replace the OTA application and the upgrading program of the controller, thereby realizing the cross-multi-version forced upgrading, effectively solving the problems that users do not upgrade for a long time, the controller software version is too low, the software version gap is too large, and the latest version OTA upgrading task can not be completed on line at one time, and obtaining the effects of improving the OTA upgrading reliability and the user experience.
Drawings
Fig. 1 is a flowchart of a vehicle software version large-span OTA upgrading method according to an embodiment.
Detailed Description
The following describes the embodiments of the present invention in further detail with reference to the drawings.
Examples:
referring to fig. 1, a vehicle software version large-span OTA upgrading method includes the following steps:
1) The OTA application acquires the current version information of the controller software and uploads the current version information to an OTA server;
2) The OTA server judges whether the current software version of the controller is lower than the software version required by normal upgrading, if yes, the step 3) is executed, and if not, the step 4) is executed;
the software version which is lower than the software version required by normal upgrading refers to the situation that a developer cannot upgrade to the latest version at one time under the condition that certain early versions are known because program logic is not supported.
3) The OTA server executes a simple upgrading task to update OTA application software and controller software to a transition version; the simple upgrade refers to that a normal upgrade protocol between the OTA application and the controller is replaced temporarily to be a simple upgrade protocol, more condition detection and complicated handshake signals outside the association are removed, and the process of transmitting an upgrade packet to the controller, refreshing firmware and programs in the controller and confirming the upgrade of the OTA application by using a simple communication protocol is completed.
Step 3) comprises the following sub-steps:
31 The OTA server obtains the transition version software of the OTA application and the controller from the database and transmits the transition version software to the OTA application, and meanwhile, the OTA server transmits a protocol switching signal to the OTA application;
the transition version software of the OTA application not only can be downward compatible with the functions of the OTA application, but also can support simple upgrading; the transition version software of the controller not only supports low version upgrade of the controller, but also supports simple upgrade of the OTA application, and the transition version software of the controller does not change the functional part of the controller software and only replaces the interaction part of the controller software and the OTA application;
32 The OTA application receives the protocol switching signal to switch the normal upgrading protocol into the simple upgrading protocol, and the OTA application updates the OTA application software and the controller software to the transition version based on the transition version software;
the priority of the OTA application software upgrade is higher than that of the controller software upgrade so as to finish the software replacement of the OTA application in advance, thereby ensuring that the controller software can be smoothly updated to a transition version;
the OTA application can finish the updating of the updating packet transmitted to the controller, the firmware and the program in the controller and the updating confirmation of the controller and the OTA application based on the simple updating protocol;
33 The OTA application feeds the upgrading result back to the OTA server, and the OTA server transmits the latest version software to the OTA application.
4) The OTA server executes a normal upgrading task to update OTA application software and controller software to the latest version; at this time, the OTA server again transmits a protocol switching signal to the OTA application to switch the simple upgrade protocol to the normal upgrade protocol.
The invention pre-stores the transition version software of the OTA application and the controller in the OTA server, when the OTA server knows that the software version of the controller is too low to directly upgrade the latest version, the OTA application normal upgrade protocol is replaced by the simple upgrade protocol, and the transition version software is issued to rapidly upgrade the OTA application and the controller to the transition version, and then the OTA application and the controller are normally upgraded. The invention adopts the transition version software to temporarily replace the OTA application and the upgrading program of the controller, thereby realizing the cross-multi-version forced upgrading, effectively solving the problems that users do not upgrade for a long time, the controller software version is too low, the software version gap is too large, and the latest version OTA upgrading task can not be completed on line at one time, and obtaining the effects of improving the OTA upgrading reliability and the user experience.
Finally, it is noted that the above embodiments are only for illustrating the technical solution of the present invention and not for limiting the same, and although the present invention has been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications and equivalents may be made thereto without departing from the spirit and scope of the technical solution of the present invention, which is intended to be covered by the scope of the claims of the present invention.
Claims (7)
1. A vehicle software version large-span OTA upgrading method is characterized in that: the method comprises the following steps:
1) The OTA application acquires the current version information of the controller software and uploads the current version information to an OTA server;
2) The OTA server judges whether the current software version of the controller is lower than the software version required by normal upgrading, if yes, the step 3) is executed, and if not, the step 4) is executed;
3) The OTA server executes a simple upgrading task to update OTA application software and controller software to a transition version;
4) The OTA server executes a normal upgrading task to update OTA application software and controller software to the latest version;
step 3) comprises the following sub-steps:
31 The OTA server obtains the transition version software of the OTA application and the controller from the database and transmits the transition version software to the OTA application;
32 OTA application updates the OTA application software and the controller software to the transition version based on the transition version software;
33 The OTA application feeds the upgrading result back to the OTA server, and the OTA server transmits the latest version software to the OTA application;
the simple upgrade refers to temporarily replacing a normal upgrade protocol between the OTA application and the controller to be a simple upgrade protocol to remove more condition detection and tedious handshake signals outside the association.
2. The method for large-span OTA upgrade of vehicle software versions according to claim 1, wherein: in step 32), the OTA application software upgrade has a higher priority than the controller software upgrade.
3. The method for large-span OTA upgrade of vehicle software versions according to claim 1, wherein: the transitional version software of the OTA application can be downward compatible with the functions of the OTA application and support simple upgrading.
4. The method for large-span OTA upgrade of vehicle software versions according to claim 1, wherein: the transitional version of the controller supports upgrades of low version controller software and supports easy upgrades.
5. The method for large-span OTA upgrade of vehicle software versions according to claim 1, wherein: step 31) further comprises the OTA server sending a protocol switching signal to the OTA application, and step 32) further comprises the OTA application receiving a protocol switching signal to switch the normal upgrade protocol to the easy upgrade protocol.
6. The method for large-span OTA upgrade of vehicle software versions according to claim 1, wherein: the simple upgrade protocol comprises the functions of version request, upgrade request, file transmission, file verification, upgrade progress reply and installation result reply.
7. The method for large-span OTA upgrade of vehicle software versions according to claim 1, wherein: the OTA application can finish the updating confirmation of the controller and the OTA application and the updating confirmation of the controller by transmitting the updating packet to the controller, the updating of the firmware and the program in the controller based on the simple updating protocol.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210582309.0A CN114979297B (en) | 2022-05-26 | 2022-05-26 | Vehicle software version large-span OTA upgrading method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210582309.0A CN114979297B (en) | 2022-05-26 | 2022-05-26 | Vehicle software version large-span OTA upgrading method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114979297A CN114979297A (en) | 2022-08-30 |
| CN114979297B true CN114979297B (en) | 2023-06-27 |
Family
ID=82955724
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210582309.0A Active CN114979297B (en) | 2022-05-26 | 2022-05-26 | Vehicle software version large-span OTA upgrading method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114979297B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115460079A (en) * | 2022-09-20 | 2022-12-09 | 台铃科技股份有限公司 | OTA (over the air) upgrading system, method and storage medium for electric vehicle |
| CN115617378A (en) * | 2022-12-16 | 2023-01-17 | 石家庄科林电气股份有限公司 | Upgrading method and device of battery management system and readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105279001A (en) * | 2015-11-20 | 2016-01-27 | 杭州云柚科技有限公司 | Software remote upgrading method for network terminal devices |
| CN112486531A (en) * | 2020-11-24 | 2021-03-12 | 航天信息股份有限公司 | Method and system for updating equipment application software |
| CN113094073A (en) * | 2021-04-29 | 2021-07-09 | 芜湖雄狮汽车科技有限公司 | Vehicle remote upgrading method and device and server |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104066077A (en) * | 2014-06-24 | 2014-09-24 | 青岛海信移动通信技术股份有限公司 | OTA downloading and upgrading method and device thereof |
| CN106470114B (en) * | 2015-08-20 | 2019-09-20 | 青岛海信移动通信技术股份有限公司 | A kind of configuration method and device of OTA upgrade package |
| CN110489143B (en) * | 2019-07-18 | 2023-10-13 | 南京依维柯汽车有限公司 | FOTA firmware remote upgrading system and method on new energy automobile |
| CN113225729B (en) * | 2020-01-21 | 2022-07-12 | 荣耀终端有限公司 | OTA (over the air) upgrading method and device and readable storage medium |
| CN112230966B (en) * | 2020-11-06 | 2023-12-01 | 天津经纬恒润科技有限公司 | OTA upgrading method and device |
| CN114327544A (en) * | 2021-12-20 | 2022-04-12 | 经纬恒润(天津)研究开发有限公司 | ECU version management method |
-
2022
- 2022-05-26 CN CN202210582309.0A patent/CN114979297B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105279001A (en) * | 2015-11-20 | 2016-01-27 | 杭州云柚科技有限公司 | Software remote upgrading method for network terminal devices |
| CN112486531A (en) * | 2020-11-24 | 2021-03-12 | 航天信息股份有限公司 | Method and system for updating equipment application software |
| CN113094073A (en) * | 2021-04-29 | 2021-07-09 | 芜湖雄狮汽车科技有限公司 | Vehicle remote upgrading method and device and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114979297A (en) | 2022-08-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114979297B (en) | Vehicle software version large-span OTA upgrading method | |
| CN103841155B (en) | A kind of method for downloading software and software download device | |
| CN106897086B (en) | Method, device and system for upgrading robot operating system | |
| CN102609326B (en) | Data downloading processing method and data downloading processing device | |
| US20020086688A1 (en) | Method for processing messages in a cellular base station system | |
| CN101241364B (en) | Local controller, remote management controller and method for automatically updating the local controller of an air conditioner system | |
| WO2010148739A1 (en) | Terminal device and upgrade method and system thereof | |
| CN107809324A (en) | A kind of OBD equipment and its upgrade method | |
| CN101179425A (en) | Client terminal software updating control method and system | |
| US20160191307A1 (en) | Data Updating Method, Device for Vehicle Diagnosing Apparatus and Vehicle Diagnosing Apparatus | |
| CN111427595B (en) | Client upgrading method, device and system | |
| CN111367542A (en) | Household appliance and household appliance firmware upgrading method | |
| WO2013040906A1 (en) | Method and system for managing software version of base station | |
| CN105100144A (en) | Application updating method and device | |
| CN100481776C (en) | Distributed upgrading method for centralization management mode | |
| WO2023123875A1 (en) | Bluetooth-based multi-device ota upgrade method, electronic device, storage medium and program product | |
| CN113934442A (en) | Software upgrading method and device | |
| CN118283284A (en) | Method, system and medium for upgrading set top box pushed by distributed server | |
| WO2018040923A1 (en) | Pos terminal application package download method and apparatus, and communication method | |
| CN111722856B (en) | Method and device for upgrading firmware in vehicle-mounted microcontroller | |
| CN109901860B (en) | Android mobile phone software version control method | |
| CN115334358B (en) | Fusion gateway automation software remanufacturing method and storage medium | |
| CN109189462A (en) | A kind of touch-control system with automatic upgrade function | |
| CN115495099A (en) | Mobile terminal remote control method suitable for OTA (over the air) upgrading of automobile | |
| CN113076121A (en) | Robot, method and device for updating firmware of robot and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |