KR20210011260A - Apparatus for integrated management of vehicle controller update using OTA and method thereof - Google Patents

Abstract

The present invention relates to an apparatus for integratively managing an update of a vehicle controller by using Over-The-Air (hereinafter referred to as ′OTA′) and, more specifically, to an apparatus capable of providing different software update processes depending on the types and purposes of vehicle controllers, and a method thereof. According to the present invention, the vehicle controller update integrated management apparatus using OTA includes: a means receiving a software update module from an OTA server creating and transmitting a software update module required for a vehicle controller; a means determining whether the type of the vehicle controller, to which the software update module is going to be applied, is a safety function controller or non-safety function controller; and a means updating the vehicle controller by writing the software update module received from the OTA server in a memory of the vehicle controller, while updating the vehicle controller by using a safety function controller update process for a case in which the determined type of the vehicle controller is a safety function controller, whereas using a non-safety function controller update process for a case in which the determined type of the vehicle controller is a non-safety function controller.

Description

TECHNICAL FIELD [Apparatus for integrated management of vehicle controller update using OTA and method thereof]

The present invention relates to an apparatus and a method for integratedly managing an update of a vehicle controller using OTA (Over-The-Air), and more particularly, to an apparatus and method for providing a different software update process for each vehicle controller type or purpose.

In the past, there was only one engine electronic control unit (Electronic Control Unit, hereinafter referred to as'ECU'), but now various electronic functions such as ABS, EPS, and ADAS are added, and currently, about 80 to 100 units of high-end vehicles ECU is installed. As the vehicle electrification progresses, continuous software and firmware management capabilities are becoming very important, and electronic products that perform various functions and software that control them are installed in the vehicle. Therefore, in order to respond quickly and continuously to bugs, defects and changing laws and systems, the need for updates through OTA is emerging.

However, currently, it is mainly operated as embedded software that controls each electronic product individually due to limited external connectivity and interoperability between electronic parts. In addition, an update method through OTA is used in a very limited manner, and even at this time, software or firmware is updated in a uniform manner regardless of the type and purpose of the vehicle controller.

In other words, it is not possible to respond to different OTA requirements for each type and use of the vehicle controller, and there is a disadvantage that it is impossible to maintain the integrated update management function when the OTA solution is changed.

An object of the present invention is to provide a software update process suitable for each characteristic by dividing the vehicle controller by type or purpose in order to overcome the disadvantages of the prior art described above, and to manage the vehicle controller in an integrated manner.

However, the technical problem to be achieved by the present embodiment is not limited to the technical problem as described above, and other technical problems may exist.

In order to solve the above problems, the present invention categorizes the vehicle controller into a safety function controller and a non-safety function controller, and the safety function controller performs an update by dualizing the memory, so that it is possible to update even while driving. Provides a problem-free device and method.

Specifically, a vehicle controller update integrated management apparatus through OTA according to a first aspect of the present invention includes: means for receiving a software update module from an OTA server that generates and transmits a software update module required for the vehicle controller; Means for determining whether the type of the target vehicle controller to which the software update module is to be applied is a safety function controller or a non-safety function controller; And writing the software update module received from the OTA server into the memory of the vehicle controller to update the vehicle controller, and if the determined vehicle controller type is a safety function controller, a safety function controller update process is used, and the determined vehicle controller And means for updating the vehicle controller using a non-safety function controller update process when the type of is a non-safety function controller.

A method for integrated management of vehicle controller updates through OTA according to a second aspect of the present invention includes: receiving a software update module from an OTA server that generates and transmits a software update module required for the vehicle controller; Determining whether the type of the target vehicle controller to which the software update module is to be applied is a safety function controller or a non-safety function controller; And applying the software update module received from the OTA server to update the vehicle controller, but when the determined type of vehicle controller is a safety function controller, a safety function controller update process is used, and the determined vehicle controller type is non-safe. In the case of a function controller, updating the vehicle controller using a non-safety function controller update process.

In the case of using the apparatus and method for integrated management of vehicle controller updates through OTA proposed in the present invention, there are advantages as follows.

Vehicle controllers are classified by type or purpose (for example, safety function controllers and non-safety function controllers, large-capacity controllers and general controllers, etc.) and update through OTA, so it is safe during operation of vehicles such as steering, engine, and braking. When a security vulnerability is found in the vehicle controller (safety function controller) that performs a function related to the vehicle, it is possible to immediately apply a wireless update for the security patch even when the vehicle is in operation, so that hacking can be quickly prevented.

In addition, since the update process is provided by classifying vehicle controllers by type or use, vehicle controllers (non-safety function controllers) that are not directly related to safety during operation of vehicles such as body, multi-convenience controllers, Updates can be managed by the integrated manager without having a control device. Therefore, it is possible to reduce cost and maximize efficiency by providing an update process suitable for the characteristics of each vehicle controller.

1 shows that the vehicle controller is divided into a safety function controller and a non-safety function controller.
2 is a schematic diagram of a vehicle controller update integrated management apparatus through OTA according to an embodiment for implementing the present invention.
3 shows a safety function controller update process according to an embodiment of the present invention.
4 shows memory duplication in the safety function controller update according to an embodiment of the present invention.
5 shows a process of updating a non-safety function controller according to an embodiment of the present invention.
6 shows a memory in the non-safety function controller update according to an embodiment of the present invention.
7 is a flowchart of a method for integrated management of vehicle controller updates through OTA according to an embodiment for implementing the present invention.

Advantages and features of the present invention, and a method of achieving them will become apparent with reference to the embodiments described in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but will be implemented in various forms different from each other, only this embodiment makes the disclosure of the present invention complete, and those skilled in the art to which the present invention pertains. It is provided to fully inform the scope of the invention to the person, and the invention is defined by the description of the claims.

On the other hand, terms used in the present specification are for explaining examples and are not intended to limit the present invention. In this specification, the singular form also includes the plural form unless specifically stated in the phrase. As used herein, "comprises" or "comprising" refers to the presence of one or more other components, steps, actions and/or elements other than the recited elements, steps, actions and/or elements, or Does not exclude addition.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs.

Meanwhile, when a certain embodiment can be implemented differently, functions or operations specified in a specific block may be performed differently from the order specified in the flowchart. For example, two consecutive blocks may actually be executed at the same time, or the blocks may be executed in reverse depending on a related function or operation.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In adding reference numerals to elements of each drawing, even though they are indicated on different drawings, the same elements are assigned the same reference numerals as much as possible, and in describing the present invention, a detailed description of related known configurations or functions If the gist of the present invention may be obscured, a detailed description thereof will be omitted.

1 shows a vehicle controller according to an embodiment of the present invention divided into a safety function controller 10 and a non-safety function controller 20.

Like the steering engine*?*?* controller, vehicle controllers that are associated with actual safety in vehicle operation are classified as the safety function controller 10, and are not directly related to safety such as body multi*?* controllers. The vehicle controller is classified as a non-safety function controller (20).

The safety function controller 10 and the non-safety function controller 20 classified according to the type in this way update the software through an update process suitable for each characteristic according to the present invention, as will be described later.

In addition, by classifying them into large-capacity controllers such as AVN, HUD, and CLU, and general controllers such as body and braking, it is possible to perform integrated management of updates through OTA according to the present invention by dividing them into various types and uses.

2 shows a schematic configuration of an integrated vehicle controller update management apparatus through OTA according to an embodiment for the implementation of the present invention.

The vehicle controller update integrated management apparatus through OTA according to the present embodiment checks the OTA server 30 for storing and managing the original software and the difference software and the software update information received from the OTA server 30, and It consists of an integrated manager 40 that performs reception determination *?* of the update process of (10, 20) and a display 50 that displays update conditions and completion results.

The OTA server 30 serves to generate an original software module or a differential software module required for each vehicle controller and transmit it to the integrated manager 40.

The integrated manager 40 is a receiver 42. It consists of a determination unit 44 and an execution unit 46. The receiving unit 42 receives the difference update module and the original update module received from the OTA server 30, and performs a function of protecting each stored update module by applying an encryption module.

The determination unit 44 is to provide an update process according to the characteristics of each type or use of the vehicle controller (in this embodiment, the safety function controller 10 update process and the non-safety function controller 20 update process), the software It serves to determine whether the type of the vehicle controller to which the update module is to be applied is the safety function controller 10 or the non-safety function controller 20.

The execution unit 46, based on the result of determining the vehicle controller by type, such as the safety function controller 10 and the non-safety function controller 20 by the determination unit 44, a software update process suitable for each characteristic Provides. In addition, the software update module received from the OTA server 30 serves to update the software of the vehicle controller (writes the received software update module to the memory of the vehicle controller). In addition, after the update is completed, the update result record is transmitted to the OTA server 30, and when the update of the non-safety function controller 20 fails, safety measures such as vehicle operation restriction are performed.

The display 50 serves to display an update possible condition to the driver so that the driver can select whether to proceed with the update, and when the update is completed, the update result is displayed to the driver.

3 shows the safety function controller 10 update process 100 according to an embodiment of the present invention.

After receiving the software update module for the target safety function controller 10 to be updated from the OTA server 30 (110), the update possibility condition of the target safety function controller 10 is checked (120). Also, the update process according to the target vehicle controller to be updated is called.

The checked update condition is displayed to the driver (130), and the driver selects whether to proceed with the update (140).

The update possible condition check 120 is to determine the update possible condition by checking the information of the software update module stored in the OTA server 30 and the current software status of the safety function controller 10 to be updated. it means.

If the driver selects to proceed with the update, the update proceeds (150). While the update is in progress, it checks whether the update has failed (160), and if the update fails without being completed, the target safety function controller 10 performs a rollback with its own chuck (165). When the update is completed, the update result is finally displayed to the driver (170).

The safety function controller update process 100 is possible even when the vehicle is running, and even if the update fails, it does not affect the operation. This is because the memory of the safety function controller 10 is duplicated so that the update is possible while driving and does not affect the operation even if a problem occurs during the update process. This will be described in detail in FIG. 4.

4 shows the memory duplication (180, 190) in the safety function controller 10.

(a) shows the state of the memory before the software update proceeds, and shows that the memory is divided into a portion 182 in which old software is stored and a portion 192 in which current software is stored.

(b) represents a situation in which the software update is in progress, and new software 184 is stored in the previous software portion 182 of (a). At this time, it can be seen that the current software 194 is not affected.

(c) denotes a situation in which the software update has been completed, the new software 184 becomes the software 186 that is currently in progress, and the software 194 that functions before the update becomes the old software 196.

Therefore, since the update is performed by dualizing the memory in this way, even if a problem occurs in the process of downloading the software update module or a problem such as failure occurs during the update process, as seen in (b), the current software 194 Since it does not have any effect, it is possible to update the software of the safety function controller 10 even while the vehicle is running.

5 shows a non-safety function controller update process 200 according to an embodiment of the present invention.

After receiving the software update module for the target non-safety function controller 20 to be updated from the OTA server 30 (210), the update possibility condition of the target non-safety function controller 20 is checked (220). The checked update condition is displayed to the driver (230), so that the driver selects whether to proceed with the update (240).

The update available condition check 220 is to determine the update available condition by checking the information of the software update module stored in the OTA server 30 and the current software status of the non-safety function controller 20 to be updated. Means that.

If the driver selects to proceed with the update, after the vehicle safety mode in which the vehicle cannot be started and operated is set (250), the update proceeds (260). While the update is in progress, it is checked whether the update has failed (270), and if the update is not completed and fails, the integrated manager 40 performs a rollback (275). When the update is completed, the update result is finally displayed to the driver (280), and the vehicle safety mode is canceled to enable the vehicle to be started and operated (290).

Unlike the safety function controller update process 100, the non-safety function controller update process 200 is possible when the vehicle is stopped, and the vehicle controller that is not related to safety while the vehicle is running does not urgently update the software. Since there is no need, the rollback 275 process is not performed by itself, and is processed by the integrated manager 40. Therefore, it is advantageous in terms of economy because it is not necessary to install a control device or a memory capable of being redundant in all vehicle controllers.

6 shows a memory of the non-safety function controller 20.

Even if a problem occurs during the software update process, the non-safety function controller 20, which does not affect the vehicle operation, does not require memory duplication. Therefore, when the vehicle is stopped, the update is in progress, and new software is downloaded to the portion where the currently running software is stored.

7 is a flowchart of a method for integrated management of vehicle controller updates through OTA according to an embodiment for implementing the present invention.

Receiving a software update module from the OTA server 30 that generates and transmits the software update module required for the vehicle controller (310), and whether the type of the vehicle controller to which the software update module is applied is the safety function controller (10) It is determined whether it is a non-safe function controller 20 (320).

Then, the vehicle controller is updated by applying the software update module received from the OTA server 30 (330). At this time, when the determined type of vehicle controller is the safety function controller 10, the safety function controller update process 100 is used, and the determined type of vehicle controller is the non-safety function controller 20. In this case, the vehicle controller is updated using the non-safety function controller update process 200. When the update is completed, the update result is displayed to the driver (340).

Although the apparatus and method of the present invention have been described in connection with specific embodiments, some or all of their components or operations may be implemented using a computer system having a general hardware architecture.

The above description of the present invention is for illustrative purposes only, and those of ordinary skill in the art to which the present invention pertains will be able to understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not limiting. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as being distributed may also be implemented in a combined form.

The scope of the present invention is indicated by the claims to be described later rather than the detailed description, and all changes or modified forms derived from the meaning and scope of the claims and their equivalent concepts should be interpreted as being included in the scope of the present invention. do.

Claims (15)

Means for receiving a software update module from an OTA server for generating and transmitting a software update module required for the vehicle controller;
Means for determining whether the type of the target vehicle controller to which the software update module is to be applied is a safety function controller or a non-safety function controller; And
The vehicle controller is updated by writing the software update module received from the OTA server into the memory of the vehicle controller, but when the determined vehicle controller type is a safety function controller, a safety function controller update process is used, and the determined vehicle controller is And means for updating the vehicle controller by using a non-safety function controller update process when the type is a non-safety function controller.
In claim 1, the safety function controller update process
A means for determining an update possible condition by checking information on the software update module stored in the OTA server and the current software status of the target safety function controller to be updated,
Means for displaying the checked update condition to the driver so that the driver selects whether to proceed with the update, and
A vehicle controller update integrated management device through an OTA including means for performing the update by writing the software update module to a memory of the safety function controller when the driver selects to proceed with the update.
The method of claim 2, further comprising a means for allowing the target safety function controller to self-roll back if the update is not completed and fails by checking whether the update has failed while the update is in progress. Vehicle controller update integrated management device through OTA.
The apparatus of claim 2, further comprising: means for displaying an update result to a driver when the update by the update means is completed.
In claim 2, the memory of the safety function controller
A vehicle controller update integrated management device through OTA, characterized in that a portion in which previous software is stored and a portion in which the software update module is newly written is duplicated.
In claim 1, wherein the non-safety function controller update process
A means for determining an update possible condition by checking information on the software update module stored in the OTA server and the current software status of the target safety function controller to be updated,
Means for displaying the checked update condition to the driver so that the driver selects whether to proceed with the update, and
A vehicle controller update integrated management device through an OTA including means for performing the update after setting a vehicle safety mode in which the vehicle cannot be started and operated when the driver selects to proceed with the update.
[7] The apparatus of claim 6, further comprising: means for performing rollback when the update is not completed and fails by checking whether the update has failed while the update proceeding means is in progress.
In claim 6, when the update is completed, the vehicle controller update integrated management device through OTA, which further includes a means for finally displaying the update result to the driver and releasing the vehicle safety mode to enable the vehicle to be started and operated. .
Receiving a software update module from an OTA server that generates and transmits a software update module required for the vehicle controller;
Determining whether the type of the target vehicle controller to which the software update module is to be applied is a safety function controller or a non-safety function controller; And
The vehicle controller is updated by applying the software update module received from the OTA server, but if the determined type of vehicle controller is a safety function controller, a safety function controller update process is used, and the determined type of vehicle controller is a non-safe function. In the case of a controller, including the step of updating the vehicle controller using a non-safety function controller update process.
In claim 9, the safety function controller update process
Determining an update possibility condition by checking information on the software update module stored in the OTA server and the current software status of the target safety function controller to be updated,
Displaying the checked update condition to the driver so that the driver selects whether to proceed with the update, and
When the driver selects to proceed with the update, the method for integrated management of vehicle controller update through OTA comprising the step of writing the software update module to a memory of the safety function controller to perform the update.
The vehicle controller update through OTA of claim 10, further comprising, in the update progress step, checking whether the update has failed, and if the update fails without being completed, allowing the target safety function controller to self-roll back. Integrated management method.
The method of claim 10, further comprising displaying an update result to a driver when the update is completed in the update step.
In claim 9, the non-safety function controller update process
Determining an update possibility condition by checking information on the software update module stored in the OTA server and the current software status of the target safety function controller to be updated,
Displaying the checked update condition to the driver so that the driver selects whether to proceed with the update, and
When the driver selects to proceed with the update, the vehicle controller update integrated management method through OTA comprising the step of performing the update after setting a vehicle safety mode in which the vehicle cannot be started and operated.
14. The method of claim 13, further comprising: checking whether the update has failed in the update proceeding step, and if the update is not completed and fails, performing a rollback.
In claim 13, when the update is completed, the vehicle controller update integrated management method through OTA, which further comprises the step of finally displaying the update result to the driver and releasing the vehicle safety mode to enable the vehicle to be started and operated. .

Images