A process work system and mechanism in OTA upgrade process

By designing a process working system during the OTA upgrade process, using the MCU and memory components in the OTA server and controller to work together, the process communication problem during OTA component deployment is solved, and the efficiency and reliability of OTA upgrade is achieved, ensuring that Efficiency and reliability of the upgrade process.

CN115865659BActive Publication Date: 2024-11-15FAW CAR CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202211307599.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-10-24
Publication Date
2024-11-15
Estimated Expiration
2042-10-24

AI Technical Summary

Technical Problem

When OTA components are deployed as independent processes on controllers with operating systems, timing and communication problems of process work are difficult to deal with, affecting the efficiency and reliability of upgrades.

Method used

A process working system during the OTA upgrade process was designed, including the OTA server, the MCU in the TBOX controller and the OTA components in the memory, as well as the MCU and OTA components in the HU controller, and the MCU and OTA components in the HU controller are used. Through clear processes, https is used. The protocol interacts with the private protocol to ensure the efficiency and reliability of the upgrade process.

Benefits of technology

It realizes the efficiency and reliability of the OTA upgrade process, ensures the compatibility of components in different environments, and improves the overall performance of the upgrade.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

The present invention belongs to the field of automotive electronic technology, and specifically relates to a process working system and mechanism in an OTA upgrade process; the system involves an OTA server, an MCU 1 in a TBOX controller, a memory and an OTA component 1 therein, and an MCU 2 and an OTA component 2 in a HU controller, wherein the interaction between the OTA component 2 and the MCU 2 includes specific pop-up window content, the OTA component 1 includes a core management process, a TLS monitoring process, a condition detection process, and an upgrade management process, and the OTA component 2 includes a HU monitoring process; the processes of the present invention work in coordination with clear division of labor, thereby ensuring the efficiency and reliability of the upgrade; and a private protocol is used between the processes, thereby ensuring the compatibility of components deployed in different environments.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of automobile electronics, and in particular relates to a process working system and mechanism in an OTA upgrade process. Background Art

[0002] In the automotive industry, with the popularization of intelligence and electrification, OTA upgrades have become more and more common, and their high efficiency, low cost, and excellent interactive experience have been favored by more and more OEMs. At the same time, some thorny issues in the OTA upgrade process have also attracted everyone's attention. Among them, the most prominent is that OTA components are deployed on controllers with operating systems as independent processes to complete related tasks. The problems caused by this are the timing and communication issues of process work. How to reasonably handle these process work issues has become a hot topic of discussion. Summary of the invention

[0003] In order to overcome the above problems, the present invention provides a process working system and mechanism in the OTA upgrade process, the system involving an OTA server, an MCU 1 in a TBOX controller, a memory and an OTA component 1 therein, and an MCU 2 and an OTA component 2 in a HU controller. The processes of the present invention work together with clear division of labor, thereby ensuring the efficiency and reliability of the upgrade.

[0004] A process working system in an OTA upgrade process includes an OTA cloud server, an MCU 1 in a TBOX controller, a memory and an OTA component 1 therein, and an MCU 2 and an OTA component 2 in a HU controller, wherein the interaction between the OTA component 2 and the MCU 2 includes specific pop-up window content, the OTA component 1 includes a core management process, a TLS monitoring process, a condition detection process, and an upgrade management process, and the OTA component 2 includes a HU monitoring process; the interaction between the OTA component 1 and the OTA cloud server includes establishing a connection, transmitting an upgrade package, transmitting a task progress, and decrypting and verifying the upgrade package, the interaction between the OTA component 1 and the MCU 1 includes obtaining a version, condition detection, and transmitting an upgrade progress, the interaction between the MCU 1 and the TBOX controller memory includes transmitting an upgrade package, and the interaction between the OTA component 1 and the OTA component 2 includes communication of relevant pop-up window information.

[0005] The interaction between OTA component 1 and OTA server in the TBOX controller is based on https protocol, and the process communication between OTA component 1 and OTA component 2 adopts a private protocol.

[0006] The core management process in the OTA component 1 is the overall scheduler of the entire upgrade process and is used to communicate with the cloud server; the TLS monitoring process monitors whether the TLS connection is successfully established and prints log information; the condition detection process interacts with MCU 1 through interface functions each time to detect vehicle control conditions; the upgrade management process monitors specific upgrade information, starts the upgrade after each condition detection process broadcasts a message that the upgrade has passed, and monitors the upgrade progress; the HU monitoring process handles pop-up related work, and controls the HU controller through interface functions to display specific pop-ups.

[0007] A process working mechanism during OTA upgrade, the process is as follows:

[0008] Step 1. The TLS monitoring process monitors the connection established between the TBOX controller and the OTA cloud server. If the connection fails, the TLS monitoring process and the core management process will print relevant failure logs. The core management process determines that the task upgrade has failed and uploads the result to the OTA cloud server, and then the process ends;

[0009] Step 2. If the connection is established successfully, the core management process prints a successful log message and broadcasts the success message to other processes;

[0010] Step 3. The core management process sends a diagnostic command through the MCU of the TBOX controller to obtain the version number of the controller to be upgraded. The core management process then compares the version number with the target version number of this upgrade. If the two version numbers are consistent, the task is considered to be upgraded successfully and there is no need to download the upgrade package. The core management process uploads the success result to the OTA cloud server and the process ends.

[0011] Step 4. If the current version number is inconsistent with the target version number, the core management process downloads the upgrade package from the OTA cloud server and downloads the upgrade package to the memory of the TBOX controller through MCU 1. The memory path is specified by OTA component 1.

[0012] Step 5. After the download is complete, the core management process notifies the upgrade management process through a private protocol to prepare for the upgrade. The upgrade management process obtains the device ID and then decompresses the upgrade package.

[0013] Step 6. The core management process notifies the HU monitoring process to monitor the changes in the bus power supply mode. The bus power supply mode is captured by the process through the interface function with the HU controller. After the power supply mode changes to Recently OFF, the MCU 2 of the HU controller is notified to pop up the installation prompt pop-up window;

[0014] Step 7. Next, determine whether the user confirms the installation. If the user does not confirm the installation, the core management process continues to monitor the changes in the bus power supply mode to notify MCU 2 of the pop-up window of the installation prompt; if the user confirms the installation, the condition monitoring process starts to check the vehicle condition. If the vehicle condition check fails, the HU monitoring process continues to monitor the changes in the bus power supply mode; if the vehicle condition check passes, MCU 1 goes to the memory to obtain the upgrade package for flashing. This path is provided by the core management process;

[0015] Step 8. The upgrade management process obtains and prints the upgrade progress from MCU 1, and then the core management group process obtains the upgrade result, and then reports the result to the OTA cloud server.

[0016] In step 1, the TLS monitoring process monitors the connection established between the core management process in the TBOX controller and the OTA cloud server.

[0017] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0018] The processes of the present invention work in coordination with clear division of labor, thus ensuring the high efficiency and reliability of the upgrade.

[0019] The present invention adopts a private protocol between processes to ensure the compatibility of components deployed in different environments. DETAILED DESCRIPTION

[0020] The present invention will be further described in detail below in conjunction with the embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention.

[0021] In the description of the present invention, unless otherwise clearly specified and limited, the terms "connected", "connected", and "fixed" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0022] In the present invention, unless otherwise clearly specified and limited, a first feature being "above" or "below" a second feature may include that the first and second features are in direct contact, or may include that the first and second features are not in direct contact but are in contact through another feature between them. Moreover, a first feature being "above", "above" and "above" a second feature includes that the first feature is directly above and obliquely above the second feature, or simply indicates that the first feature is higher in level than the second feature. A first feature being "below", "below" and "below" a second feature includes that the first feature is directly below and obliquely below the second feature, or simply indicates that the first feature is lower in level than the second feature.

[0023] In the description of this embodiment, the terms "upper", "lower", "left", "right" and other directions or positional relationships are only for the convenience of description and simplification of operation, and do not indicate or imply that the device or element referred to must have a specific direction, be constructed and operate in a specific direction, and therefore cannot be understood as limiting the present invention. In addition, the terms "first" and "second" are only used to distinguish in the description and have no special meaning.

[0024] Example 1

[0025] A process working system in an OTA upgrade process includes an OTA cloud server, an MCU 1 in a TBOX controller, a memory and an OTA component 1 therein, and an MCU 2 and an OTA component 2 in a HU controller, wherein the interaction between the OTA component 2 and the MCU 2 includes specific pop-up window content, the OTA component 1 includes a core management process, a TLS monitoring process, a condition detection process, and an upgrade management process, and the OTA component 2 includes a HU monitoring process; the interaction between the OTA component 1 and the OTA cloud server includes establishing a connection, transmitting an upgrade package, transmitting a task progress, and decrypting and verifying the upgrade package, the interaction between the OTA component 1 and the MCU 1 includes obtaining a version, condition detection, and transmitting an upgrade progress, the interaction between the MCU 1 and the TBOX controller memory includes transmitting an upgrade package, and the interaction between the OTA component 1 and the OTA component 2 includes communication of relevant pop-up window information.

[0026] The interaction between OTA component 1 and OTA server in the TBOX controller is based on https protocol, and the process communication between OTA component 1 and OTA component 2 adopts a private protocol.

[0027] The core management process in the OTA component 1 is the overall scheduler of the entire upgrade process and is used to communicate with the cloud server; the TLS monitoring process monitors whether the TLS connection is successfully established and prints log information; the condition detection process interacts with MCU 1 through interface functions each time to detect vehicle control conditions; the upgrade management process monitors specific upgrade information, starts the upgrade after each condition detection process broadcasts a message that the upgrade has passed, and monitors the upgrade progress; the HU monitoring process handles pop-up related work, and controls the HU controller through interface functions to display specific pop-ups.

[0028] A process working mechanism during OTA upgrade, the process is as follows:

[0029] Step 1. The TLS monitoring process monitors the connection established between the TBOX controller and the OTA cloud server. If the connection fails, the TLS monitoring process and the core management process will print relevant failure logs. The core management process determines that the task upgrade has failed and uploads the result to the OTA cloud server, and then the process ends;

[0030] Step 2. If the connection is established successfully, the core management process prints a successful log message and broadcasts the success message to other processes;

[0031] Step 3. The core management process sends a diagnostic command through the MCU of the TBOX controller to obtain the version number of the controller to be upgraded. The core management process then compares the version number with the target version number of this upgrade. If the two version numbers are consistent, the task is considered to be upgraded successfully and there is no need to download the upgrade package. The core management process uploads the success result to the OTA cloud server and the process ends.

[0032] Step 4. If the current version number is inconsistent with the target version number, the core management process downloads the upgrade package from the OTA cloud server and downloads the upgrade package to the memory of the TBOX controller through MCU 1. The memory path is specified by OTA component 1.

[0033] Step 5. After the download is complete, the core management process notifies the upgrade management process through a private protocol to prepare for the upgrade. The upgrade management process obtains the device ID and then decompresses the upgrade package.

[0034] Step 6. The core management process notifies the HU monitoring process to monitor the changes in the bus power supply mode. The bus power supply mode is captured by the process through the interface function with the HU controller. After the power supply mode changes to Recently OFF, the MCU 2 of the HU controller is notified to pop up the installation prompt pop-up window;

[0035] Step 7. Next, determine whether the user confirms the installation. If the user does not confirm the installation, the core management process continues to monitor the changes in the bus power supply mode to notify MCU 2 of the pop-up window of the installation prompt; if the user confirms the installation, the condition monitoring process starts to check the vehicle condition. If the vehicle condition check fails, the HU monitoring process continues to monitor the changes in the bus power supply mode; if the vehicle condition check passes, MCU 1 goes to the memory to obtain the upgrade package for flashing. This path is provided by the core management process;

[0036] Step 8. The upgrade management process obtains and prints the upgrade progress from MCU 1, and then the core management group process obtains the upgrade result, and then reports the result to the OTA cloud server.

[0037] In step 1, the TLS monitoring process monitors the connection established between the core management process in the TBOX controller and the OTA cloud server.

[0038] Example 2

[0039] A process work system in an OTA upgrade process, the system involves an OTA server, an MCU 1 in a TBOX controller, a memory and an OTA component 1 therein, wherein the OTA component 1 includes a core management process, a TLS monitoring process, a condition detection process, an upgrade management process, and an MCU 2 and an OTA component 2 in a HU controller, wherein the OTA component 2 includes a HU monitoring process. The interaction between the OTA component 1 in the TBOX controller and the OTA cloud server includes establishing an https connection, transmitting an upgrade package, transmitting a task progress, and decrypting and verifying the upgrade package. The interaction between the OTA component 1 and the MCU 1 in the TBOX controller includes obtaining a version, condition detection, and transmitting an upgrade progress. The interaction between the MCU 1 and the memory of the TBOX controller includes the transmission of the upgrade package, wherein the memory path is provided by the OTA component 1. The interaction between the TBOX controller and the OTA component 2 of the HU controller includes the communication of pop-up window information. The interaction between the OTA component 2 of the HU controller and the MCU 1 of the HU includes specific pop-up window content.

[0040] The interaction between OTA component 1 and OTA server in TBOX controller is based on https protocol, and the process communication between OTA components adopts private protocol. The main work of the core management process in OTA component 1 is the overall scheduling of the entire upgrade process and communication with the cloud server; the TLS monitoring process is to monitor whether the TLS connection is successfully established and print log information; the condition detection process is to interact with MCU 1 through interface functions each time to detect vehicle control conditions; the upgrade management process monitors the specific information of the upgrade, starts the upgrade after each condition detection process broadcasts the message of the upgrade passing, and monitors the upgrade progress; the HU monitoring process is to handle pop-up related work, and control the HU controller through interface functions to display specific pop-ups.

[0041] The process of the present invention is described as follows:

[0042] 1. The process starts.

[0043] 2. The TLS process monitors the connection established between TBOX and the cloud server. If the connection fails, both the TLS process and the core management process print relevant failure logs. The core management process determines that the task upgrade has failed, uploads the result to the server, and then the process ends.

[0044] 3. If the connection is established successfully, the core management process prints a successful log message and broadcasts the success message to other processes.

[0045] 4. The core management process sends a diagnostic command through the MCU of TBOX to obtain the version number of the controller to be upgraded. The core management process then compares the version number with the target version number of this upgrade. If the two version numbers are consistent, the task is considered to be upgraded successfully and there is no need to download the upgrade package. The core management process uploads the success result to the OTA server and the process ends.

[0046] 5. If the current version number is inconsistent with the target version number, the core management process controls the download of the upgrade package to the memory of TBOX. The memory path is specified by the OTA component.

[0047] 6. After the download is complete, the core management component notifies the upgrade management process through a private protocol to prepare for the upgrade. The upgrade management process obtains the device ID and then decompresses the upgrade package.

[0048] 7. The core management process notifies the HU monitoring process to monitor changes in the bus power supply mode, which is captured by the process through the interface function with the HU. When the power supply mode changes to Recently OFF, the MCU of the HU is notified to pop up an installation prompt window.

[0049] 8. Next, determine whether the user confirms the installation. If not, the core management process continues to monitor the bus power mode changes to notify the pop-up window of the installation prompt. If the user confirms the installation, the condition monitoring process starts to check the vehicle condition. If the vehicle condition check fails, the HU monitoring process continues to monitor the changes in the bus power mode. If the vehicle condition check passes, the TBOX MCU goes to the memory to get the upgrade package for flashing. This path is provided by the core management process.

[0050] 9. The upgrade management process obtains and prints the upgrade progress, and then the core management component obtains the upgrade result and reports the result to the OTA server.

[0051] The preferred embodiments of the present invention are described in detail above. However, the protection scope of the present invention is not limited to the specific details in the above embodiments. Within the technical concept of the present invention, any technician familiar with the technical field can make equivalent replacements or changes according to the technical scheme and inventive concept of the present invention within the technical scope disclosed by the present invention. These simple variations all belong to the protection scope of the present invention.

[0052] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present invention will not further describe various possible combinations.

[0053] In addition, various embodiments of the present invention may be arbitrarily combined, and as long as they do not violate the concept of the present invention, they should also be regarded as the contents disclosed by the present invention.

Claims

1. A process work system in the OTA upgrade process, characterized in that It includes an OTA cloud server, MCU 1 in the TBOX controller, memory and OTA component 1 therein, and MCU 2 and OTA component 2 in the HU controller, wherein the interaction between OTA component 2 and MCU 2 includes specific pop-up window content, the OTA component 1 includes a core management process, a TLS monitoring process, a condition detection process, and an upgrade management process, and OTA component 2 includes a HU monitoring process; the interaction between OTA component 1 and the OTA cloud server includes establishing a connection, transmitting an upgrade package, transmitting a task progress, and decrypting and verifying the upgrade package, the interaction between OTA component 1 and MCU 1 includes obtaining a version, condition detection, and transmission of upgrade progress, the interaction between MCU 1 and the memory in the TBOX controller includes the transmission of the upgrade package, and the interaction between OTA component 1 and OTA component 2 includes communication of relevant pop-up window information; The working mechanism flow of the process working system during the OTA upgrade process is as follows: Step 1. The TLS monitoring process monitors the connection established between the TBOX controller and the OTA cloud server. If the connection fails, the TLS monitoring process and the core management process will print relevant failure logs. The core management process determines that the task upgrade has failed and uploads the result to the OTA cloud server, and then the process ends; Step 2. If the connection is established successfully, the core management process prints a successful log message and broadcasts the success message to other processes; Step 3. The core management process sends a diagnostic command through the MCU of the TBOX controller to obtain the version number of the controller to be upgraded. The core management process then compares the version number with the target version number of this upgrade. If the two version numbers are consistent, the task is considered to be upgraded successfully and there is no need to download the upgrade package. The core management process uploads the success result to the OTA cloud server and the process ends. Step 4. If the current version number is inconsistent with the target version number, the core management process downloads the upgrade package from the OTA cloud server and downloads the upgrade package to the memory of the TBOX controller through MCU 1. The memory path is specified by OTA component 1. Step 5. After the download is complete, the core management process notifies the upgrade management process through a private protocol to prepare for the upgrade. The upgrade management process obtains the device ID and then decompresses the upgrade package. Step 6. The core management process notifies the HU monitoring process to monitor the changes in the bus power supply mode. The bus power supply mode is captured by the process through the interface function with the HU controller. After the power supply mode changes to Recently OFF, the MCU 2 of the HU controller is notified to pop up the installation prompt pop-up window; Step 7. Next, determine whether the user confirms the installation. If the user does not confirm the installation, the core management process continues to monitor the bus power supply mode changes to notify the MCU of the pop-up window of the second installation prompt; If the user confirms the installation, the condition monitoring process starts to check the vehicle condition. If the vehicle condition check fails, the HU monitoring process continues to monitor the changes in the bus power supply mode. If the vehicle condition check passes, the MCU goes to the memory to obtain the upgrade package for flashing. This path is provided by the core management process. Step 8. The upgrade management process obtains and prints the upgrade progress from MCU 1, and then the core management group process obtains the upgrade result, and then reports the result to the OTA cloud server.

2. According to the process work system of the OTA upgrade process of claim 1, it is characterized in that The interaction between OTA component 1 and OTA cloud server in the TBOX controller is based on https protocol, and the process communication between OTA component 1 and OTA component 2 adopts private protocol.

3. The process working system in the OTA upgrade process according to claim 1, characterized in that The core management process in the OTA component 1 is the overall scheduler of the entire upgrade process and is used to communicate with the OTA cloud server; the TLS monitoring process can monitor whether the TLS connection is successfully established and print log information; the condition detection process interacts with MCU 1 through interface functions each time to detect vehicle control conditions; the upgrade management process monitors the specific information of the upgrade, starts the upgrade after each condition detection process broadcasts a message that the upgrade has passed, and monitors the upgrade progress.

4. The process working system in the OTA upgrade process according to claim 1, characterized in that The HU monitoring process can handle pop-up window related tasks and control the HU controller through an interface function to display a specific pop-up window.

5. According to claim 1, the process working mechanism in the OTA upgrade process is characterized in that In step 1, the TLS monitoring process monitors the connection established between the core management process in the TBOX controller and the OTA cloud server.