Automobile non-inductive upgrading method and device

Abstract

The invention belongs to the technical field of OTA automobile upgrading, and provides an automobile non-inductive upgrading method and device, and the method comprises the steps: obtaining the partition information and software version of a controller; wherein the partition information of the controller comprises a running partition and a backup partition; the software version is a current version of a running partition; an upgrading condition is confirmed, and upgrading data of the target version is downloaded to a backup partition; switching a running partition of the controller into a backup partition to finish upgrading; according to the method, the upgrading data of the target version is downloaded to the backup partition, so that the vehicle can be normally used in the upgrading process, and the problems that in the prior art, the vehicle must be kept in a static state, a vehicle owner cannot use the vehicle, and the upgrading efficiency is high due to the fact that the non-file system controller in the vehicle is upgraded through UDS diagnosis service are solved. And the user experience is influenced.

Description

Technical Field

[0001] The present invention belongs to the technical field of OTA (Over-The-Air) automobile upgrade, and in particular relates to a method and device for non-sensing automobile upgrade. Background Art

[0002] With the continuous improvement of the intelligence and automation level of automobile parts, there will be more and more software installed in cars in the future. Regardless of whether the vehicle encounters software failure or software update, the offline service station recall model is no longer the best choice to meet user experience. Remote upgrade technology can complete the repair of software defects by remotely pushing data packets, greatly avoiding the risk of vehicle recall and the uncontrollable recall costs.

[0003] When the existing OTA solution is used to upgrade a vehicle, the vehicle can only be stationary and the owner cannot use the vehicle. Summary of the invention

[0004] In view of the problem that when the existing OTA solution is used to upgrade a vehicle, the vehicle can only be in a stationary state and the owner cannot use the vehicle, the present invention proposes a method and device for seamlessly upgrading a vehicle.

[0005] In order to achieve the above object, the present invention adopts the following technical solutions:

[0006] In a first aspect, the present disclosure provides a method for seamlessly upgrading a car, which is applied to a non-file system and includes:

[0007] Obtaining the partition information and software version of the controller; wherein the partition information of the controller includes a running partition and a backup partition; the software version is the current version of the running partition;

[0008] Confirm the upgrade conditions and download the upgrade data of the target version to the backup partition;

[0009] The running partition of the controller is switched to the backup partition to complete the upgrade.

[0010] Furthermore, the upgrade confirmation conditions include: the target version is higher than the current version, the battery power is sufficient, and the vehicle is in a safe state.

[0011] Furthermore, before switching the running partition of the controller to the backup partition, the method further includes: confirming that the upgrade data is valid.

[0012] Furthermore, if the upgrade data is invalid, the upgrade is exited.

[0013] Furthermore, before completing the upgrade, the method further includes: checking whether the running partition of the controller is switched to the backup partition and whether the software version of the controller is the target version.

[0014] Furthermore, after checking whether the running partition of the controller is switched to the backup partition and whether the software version of the controller is the target version, the method further includes: based on the result of the checking, feeding back the upgrade result to the user.

[0015] Further, if the controller is not switched to the backup partition and / or the software version of the controller is not the target version, the software version of the rolled-back controller is the current version.

[0016] Furthermore, when downloading the upgrade data of the target version to the backup partition, the whole vehicle application message silencing is not performed.

[0017] Further, by executing 36 service data transmission, and using the controller flow control frame to download the upgrade data of the target version to the backup partition.

[0018] In a second aspect, the present disclosure provides a vehicle non-sensing upgrade device, comprising:

[0019] An acquisition module, used to acquire the partition information and software version of the controller; wherein the partition information of the controller includes a running partition and a backup partition; and the software version is the current version of the running partition;

[0020] Download module, used to confirm the upgrade conditions and download the upgrade data of the target version to the backup partition;

[0021] The upgrade module is used to switch the running partition of the controller to the backup partition to complete the upgrade.

[0022] Beneficial effects of the present invention:

[0023] 1. For a controller with dual partitions (a running partition and a backup partition), the method of the present invention first downloads the upgrade data of the target version to the backup partition so that the vehicle can be used normally during the upgrade process. This solves the problem in the prior art that the non-file system controller in the vehicle is upgraded through the UDS diagnostic service, resulting in the vehicle having to remain stationary and the owner being unable to use the vehicle, which affects the user experience.

[0024] 2. The method of the present invention shares CAN bus resources with messages through a reasonable flow control mechanism, thereby avoiding the problems of excessive bus load rate and abnormal vehicle function, and ensuring the stability and reliability of data transmission.

[0025] Other features and advantages of the present invention will be described in the following description, and partly become obvious from the description, or be understood by implementing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures pointed out in the description and the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0027] Figure 1 The process of the vehicle non-sensing upgrade method of the present invention is shown Figure 1 ;

[0028] Figure 2 The process of the vehicle non-sensing upgrade method of the present invention is shown Figure 2 ;

[0029] Figure 3 The device framework diagram of the present invention is shown;

[0030] Figure 4 A schematic diagram of the device structure of the present invention is shown. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0032] In the prior art, the method usually adopted by car remote upgrade OEMs is to use the vehicle network to upgrade the non-file system controller in the vehicle through the UDS diagnostic service. According to the standard upgrade process, during the upgrade process, all controllers on the bus will be notified to stop sending application messages. The entire vehicle network will be silent and can only receive / send diagnostic messages. The vehicle must remain stationary, which makes the owner unable to use the vehicle, affecting the user experience.

[0033] Refer to the instruction manual Figure 1 and 2 As shown, a method for non-sensing vehicle upgrade is shown, which is for non-file systems and controllers that support dual application partitions (running partition and backup partition). Non-file system means that the internal storage structure of the controller does not organize data in the form of standard file directories, but uses a specific memory layout or data blocks to store software code and configuration information.

[0034] A method for non-sensing upgrade of a car, specifically comprising the following steps:

[0035] S1. When the vehicle is powered on, the OTA master control node obtains the partition information and software version of the controller; the partition information of the controller includes the running partition and the backup partition; the software version is the current version of the running partition;

[0036] The target version refers to the software version to be installed or updated in the car system. The target version contains some improvements, new features, performance optimizations or security patches. The target version is released by the vehicle manufacturer or software supplier and pushed to the vehicle through OTA technology.

[0037] The current version refers to the existing software version of the vehicle controller before the software upgrade, that is, the software version currently used by the vehicle. The current version is pre-installed when the vehicle leaves the factory, or is the version after the last successful upgrade.

[0038] Partitions are logical divisions of the ECU's internal storage space to store different types of software and data.

[0039] The controller partition information includes:

[0040] Partition layout: includes the physical location and size of each partition in the controller.

[0041] Partition type: Different partitions may be used to store different types of software or data. For example, some partitions may be used to store the currently running software version (running partition), while other partitions may be used as backups (backup partitions).

[0042] Partition status: includes information such as the read / write status of the partition, whether it is encrypted, and whether it contains valid software. The partition status is used by the OTA master node to understand which partition is upgradeable and which partition contains the currently running software version.

[0043] S2. The OTA master control node confirms the upgrade conditions and downloads the upgrade data of the target version to the backup partition;

[0044] Specifically, the upgrade conditions include whether the target version is higher than the current version, whether the battery power is sufficient, whether the vehicle is in a safe state (such as not driving), etc.

[0045] During the process of the OTA master node downloading the upgrade data to the backup partition of the controller, the system will not execute the silencing of the vehicle application messages. That is, during the process of downloading the upgrade data to the backup partition of the controller, other application messages of the vehicle (such as communication data related to vehicle operation, safety, etc.) can still be sent and received normally, and will not interfere with the normal operation of the vehicle.

[0046] In some embodiments, during the process of the OTA master node downloading the upgrade data to the backup partition of the controller, the 36 services of the ISO 15765-2 standard are executed for data transmission. Specifically, the receiving controller responds to the sending controller by sending a flow control frame. In the flow control frame, the BS (Block Size) field is set to 0x0A, indicating that the maximum receiving capacity of each data block of the receiving controller is currently 10 bytes. At the same time, the ST (Sequent ia l Timer) field is set to 0x64 (100 milliseconds), indicating that the sending controller needs to wait at least 100 milliseconds before sending the next data block to achieve delay control of data transmission. Even during the OTA upgrade data download process, the vehicle's normal communication and application messages are still being sent, and the OTA data transmission shares the CAN bus resources with these messages through a reasonable flow control mechanism, thereby avoiding the problems of excessive bus load rate and abnormal vehicle functions, and ensuring the stability and reliability of data transmission.

[0047] S3. After the upgrade data is downloaded, the OTA master control node checks the validity of the upgrade data;

[0048] If the upgrade data is invalid, the upgrade will be exited. If the upgrade data is valid, continue to execute the subsequent steps.

[0049] S4. In response to the upgrade request signal, the OTA master control node switches the running partition of the controller to the backup partition to complete the upgrade;

[0050] Before the running partition of the controller is switched to the backup partition, the OTA master control node will send an upgrade notification to the user through the user interface (such as the vehicle display or mobile phone APP). The notification content includes the necessity of the upgrade, the estimated upgrade time, and the possible impact. The user can choose to confirm or cancel the upgrade. If the user chooses to confirm, the OTA master control node will continue to perform the partition switching operation; if the user chooses to cancel, the OTA master control node will terminate the upgrade process. After receiving the upgrade notification, the user can choose to click to confirm the upgrade. Once the user confirms, the OTA master control node will execute the partition switching of the controller, that is, switch from the current running partition to the upgraded backup partition.

[0051] After switching from the current running partition to the upgraded backup partition, the backup partition will serve as the new running partition, and the original running partition will be converted into the backup partition, that is, the roles of the running partition and the backup partition are exchanged.

[0052] S5. Before completing the upgrade, the OTA master control node will also check whether the controller has switched to the backup partition and whether the software version of the controller is the target version;

[0053] The OTA master node checks whether the controller has switched to the backup partition and whether the software version is the target version. If both are yes, the upgrade is successful; if not, the upgrade fails.

[0054] After detecting an upgrade failure, the OTA master control node will record the cause of the failure and start the rollback mechanism to restore the running partition of the controller to the original version (i.e. the current version) to ensure the safety and functionality of the vehicle. The rollback process includes clearing the data of the backup partition and restoring the data of the running partition to the state before the upgrade. The rollback mechanism ensures that the vehicle can still operate normally after the upgrade fails, avoiding functional abnormalities or safety hazards caused by the upgrade failure. The recorded failure reasons will be saved in the log file for subsequent analysis and troubleshooting by technicians.

[0055] S6. Feedback the upgrade result to the user based on the inspection result;

[0056] Specifically, the upgrade result includes upgrade success or upgrade failure. Information about upgrade success or upgrade failure is fed back to the user through the user interface. Exemplary: If the upgrade is successful, the user interface displays the message "upgrade success" and records the upgrade log. If the upgrade fails, the user interface displays the message "upgrade failure" and provides the reason for the failure and a suggested solution.

[0057] Failure feedback: If the upgrade fails, the user interface will display the message "Upgrade failed"

[0058] For controllers with dual partitions (a running partition and a backup partition), the target version's upgrade data is first downloaded to the backup partition so that the vehicle can be used normally during the upgrade process. This solves the problem in the prior art of upgrading the non-file system controller in the vehicle through the UDS diagnostic service, which causes the vehicle to have to remain stationary and the owner to be unable to use the vehicle, affecting the user experience.

[0059] Refer to the instruction manual Figure 3 As shown, based on the same inventive concept, the present disclosure also proposes a car non-sensing upgrade device, comprising:

[0060] The acquisition module 110 is used to acquire the partition information and software version of the controller; wherein the partition information of the controller includes a running partition and a backup partition; and the software version is the current version of the running partition;

[0061] The download module 120 is used to confirm the upgrade conditions and download the upgrade data of the target version to the backup partition;

[0062] The upgrade module 130 is used to switch the running partition of the controller to the backup partition to complete the upgrade.

[0063] Refer to the instruction manual Figure 4 As shown, based on the same inventive concept, the present disclosure also proposes a device, including a memory and a processor, wherein the memory stores computer instructions that can be run on the processor, and is characterized in that the above-mentioned method for seamless vehicle upgrade is executed when the processor runs the computer instructions.

[0064] Based on the same inventive concept, the present disclosure also proposes a computer-readable storage medium on which computer instructions are stored. When the computer instructions are executed, the above-mentioned vehicle seamless upgrade method can be implemented.

[0065] Among them, any reference to memory, storage, database or other media used in the embodiments provided by the present invention may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory.

[0066] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0067] Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent substitutions for some of the technical features therein; and these modifications or substitutions do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for non-sensing upgrade of automobiles, applied to non-file systems, characterized in that: include: Obtaining the partition information and software version of the controller; wherein the partition information of the controller includes a running partition and a backup partition; the software version is the current version of the running partition; Confirm the upgrade conditions and download the upgrade data of the target version to the backup partition; The running partition of the controller is switched to the backup partition to complete the upgrade.

2. The method for non-sensing vehicle upgrade according to claim 1, characterized in that: The upgrade confirmation conditions include: the target version is higher than the current version, the battery is sufficiently charged, and the vehicle is in a safe state.

3. The method for non-sensing vehicle upgrade according to claim 1, characterized in that: Before switching the running partition of the controller to the backup partition, the method further includes: confirming that the upgrade data is valid.

4. The method for non-sensing vehicle upgrade according to claim 3, characterized in that: If the upgrade data is invalid, exit the upgrade.

5. The method for non-sensing vehicle upgrade according to claim 1, characterized in that: Before completing the upgrade, the method further includes: checking whether the running partition of the controller is switched to the backup partition and whether the software version of the controller is the target version.

6. The method for non-sensing vehicle upgrade according to claim 5, characterized in that: After checking whether the running partition of the controller is switched to the backup partition and whether the software version of the controller is the target version, the method further includes: feeding back an upgrade result to a user based on the result of the checking.

7. The method for non-sensing vehicle upgrade according to claim 5, characterized in that: If the controller is not switched to the backup partition and / or the software version of the controller is not the target version, the software version of the rolled-back controller is the current version.

8. The method for non-sensing vehicle upgrade according to claim 1, characterized in that: When downloading the upgrade data of the target version to the backup partition, the whole vehicle application message silencing is not performed.

9. The method for non-sensing vehicle upgrade according to claim 1 or 8, characterized in that: The service data transmission is performed by executing 36, and the upgrade data of the target version is downloaded to the backup partition using the controller flow control frame.

10. A car non-sensing upgrade device, characterized in that: include: An acquisition module, used to acquire the partition information and software version of the controller; wherein the partition information of the controller includes a running partition and a backup partition; and the software version is the current version of the running partition; Download module, used to confirm the upgrade conditions and download the upgrade data of the target version to the backup partition; The upgrade module is used to switch the running partition of the controller to the backup partition to complete the upgrade.

Images