Apparatus for updating vehicle and method thereof

Abstract

The present invention relates to a vehicle update control device and a method for controlling an OTA update of a vehicle. According to the present invention, the device is provided in a vehicle that performs an OTA (Over-The-Air) update, acquires information regarding the vehicle's battery state (SoC, State of Charge), transmits information regarding the OTA update to a target device for the update, and, based on the battery state, can adjust the transmission time interval (STMin, Separation Time Min) between data of the information regarding the OTA update transmitted to the target device for the update. Through the present invention, the effect of preventing a situation where the engine cannot be started due to a lack of battery power after performing an OTA update can be provided.

Description

Technology Field

[0001] The present invention relates to a vehicle update control device and a method thereof, and more specifically, to a vehicle update control device and a method thereof for controlling OTA updates of a vehicle. Background Technology

[0002] OTA (Over The Air) updates are a method that facilitates convenient software updates for electronic devices installed in a vehicle. Update information is received from the OTA update server via an external vehicle communication module and transmitted to the target controller via an internal vehicle communication control module. Additionally, in the event of an update failure, the system reverts to the original software.

[0003] When updating a vehicle's electronic systems using the OTA method, the process is performed with the key turned off. Since performing an OTA update in the key-off state utilizes power from the vehicle's battery, there must be sufficient remaining battery charge to start the engine after the update is complete. In particular, if the battery is aged or its performance deteriorates during winter, the vehicle may become unable to start after the update; therefore, the development of technology to resolve this issue is necessary. The problem to be solved

[0004] An embodiment of the present invention aims to provide a vehicle update control device and a method for controlling an OTA update of a vehicle.

[0005] Another embodiment of the present invention aims to provide a vehicle update control device and a method for preventing a situation in which the engine cannot be started due to a lack of battery after performing an OTA update.

[0006] Another embodiment of the present invention aims to provide a vehicle update control device and a method for managing the remaining battery capacity during an update in situations where battery performance is degraded due to battery aging or winter conditions.

[0007] Another embodiment of the present invention aims to provide a vehicle update control device and a method that solves the problem in which the efficiency of an OTA update may decrease because the OTA entry conditions are not satisfied when the battery level value is increased during an OTA update.

[0008] Another embodiment of the present invention aims to provide a vehicle update control device and a method that can solve the problem of the engine not starting after an OTA update is completed by modifying only the software, without changing the hardware.

[0009] The technical problems of the present invention are not limited to those mentioned above, and other unmentioned technical problems will be clearly understood by those skilled in the art from the description below. means of solving the problem

[0010] A vehicle update control device according to one embodiment of the present invention may include a sensor unit that is provided in a vehicle performing an OTA (Over-The-Air) update and acquires information regarding the battery state (SoC, State of Charge) of the vehicle, and a control unit that transmits information regarding the OTA update to an update target device and, based on the battery state, adjusts the transmission time interval (STMin, Separation Time Min) between data of the information regarding the OTA update transmitted to the update target device.

[0011] In one embodiment, the control unit may reduce the transmission time interval as the battery state is lower.

[0012] In one embodiment, the control unit can adjust the transmission time interval based on the battery status identified in real time while the OTA update is being performed with the vehicle in a Key Off state.

[0013] In one embodiment, the control unit can adjust the transmission time interval while the OTA update is performed with the vehicle in a key-off state, based on the battery status of the vehicle expected at the time of completion of the OTA update.

[0014] In one embodiment, the control unit can calculate the expected battery state of the vehicle at the time of completion of the OTA update based on the current battery state of the vehicle, the current consumed for the OTA update, and the expected time required for the OTA update.

[0015] In one embodiment, the control unit determines whether starting is possible at the time of completion of the OTA update through the battery status before the OTA update is performed, and determines whether the OTA update can be performed based on whether starting is possible after the OTA update is completed.

[0016] In one embodiment, the control unit may determine whether to stop the OTA update based on the battery status identified in real time while the OTA update is being performed with the vehicle in a key-off state, or the battery status of the vehicle expected at the time of completion of the OTA update.

[0017] In one embodiment, the control unit transmits information about the OTA update, including ROM data, to the update target device via background transmission before the OTA update is performed, and if the vehicle becomes key-off during the transmission of information about the OTA update, the transmission time interval can be adjusted based on the battery status identified in real time.

[0018] In one embodiment, the control unit checks whether the battery state of the vehicle expected at the time of completion of the OTA update is above a preset threshold after the transmission of information regarding the OTA update through the background transmission is completed, and if the battery state of the vehicle is above the preset threshold, the operating memory of the vehicle can be set to the memory of the update target device where the ROM data is stored.

[0019] In one embodiment, the control unit can determine whether to stop the OTA update based on the battery status when the OTA update is performed using differential data stored in the update target device.

[0020] In one embodiment, the control unit may stop the OTA update if the battery status is below a preset threshold when the OTA update is performed using differential data stored in the update target device.

[0021] A vehicle update control method according to another embodiment of the present invention may include the steps of: a sensor unit equipped in a vehicle performing an OTA update acquiring information regarding the battery status of the vehicle; and a control unit transmitting information regarding the OTA update to an update target device and adjusting the transmission time interval between data of the information regarding the OTA update transmitted to the update target device based on the battery status.

[0022] In one embodiment, the step of adjusting the transmission time interval between data of information regarding the OTA update transmitted by the control unit to the update target device may include the step of the control unit adjusting the transmission time interval to be shorter as the battery status is lower.

[0023] In one embodiment, the step of adjusting the transmission time interval between data of information regarding the OTA update transmitted by the control unit to the update target device may include the step of the control unit adjusting the transmission time interval based on the battery status identified in real time while the OTA update is being performed with the vehicle in a key-off state or the battery status of the vehicle expected at the time of completion of the OTA update.

[0024] In one embodiment, the control unit may further include the step of calculating the expected battery state of the vehicle at the time of completion of the OTA update based on the current battery state of the vehicle, the current consumed for the OTA update, and the expected time required for the OTA update.

[0025] In one embodiment, the control unit may further include a step of determining whether starting is possible at the time of completion of the OTA update through the battery status before the OTA update is performed, and a step of determining whether the OTA update can be performed based on whether starting is possible after the OTA update is completed.

[0026] In one embodiment, the control unit may further include a step of determining whether to stop the OTA update based on the battery status identified in real time while the OTA update is being performed with the vehicle in a key-off state, or the battery status of the vehicle expected at the time of completion of the OTA update.

[0027] In one embodiment, the step of adjusting the transmission time interval between data of information regarding the OTA update transmitted by the control unit to the update target device may include the step of the control unit transmitting information regarding the OTA update, including ROM data, to the update target device via background transmission before the OTA update is performed, and adjusting the transmission time interval based on the battery status identified in real time when the vehicle becomes key-off during the transmission of information regarding the OTA update.

[0028] In one embodiment, the control unit may further include the step of checking whether the battery state of the vehicle expected at the time of completion of the OTA update is above a preset threshold after the transmission of information regarding the OTA update through the background transmission is completed, and the step of the control unit setting the operating memory of the vehicle to the memory of the update target device where the ROM data is stored if the battery state of the vehicle is above the preset threshold.

[0029] In one embodiment, the control unit may further include a step of determining whether to stop the OTA update based on the battery status when the OTA update is performed using differential data stored in the update target device. Effects of the invention

[0030] The effects of the vehicle update control device and method according to the present invention are described as follows.

[0031] According to at least one embodiment of the present invention, a vehicle update control device and a method for controlling an OTA update of a vehicle can be provided.

[0032] In addition, according to at least one embodiment of the present invention, a vehicle update control device and a method thereof can be provided to prevent a situation in which the engine cannot be started due to a lack of battery after performing an OTA update.

[0033] In addition, according to at least one embodiment of the present invention, a vehicle update control device and a method for managing the remaining battery capacity during an update in a situation where battery performance is degraded due to battery aging or winter conditions may be provided.

[0034] In addition, according to at least one embodiment of the present invention, a vehicle update control device and a method thereof can be provided to solve the problem that the efficiency of an OTA update may be reduced because the OTA entry conditions are not satisfied when the battery level value is increased during an OTA update.

[0035] In addition, according to at least one embodiment of the present invention, a vehicle update control device and a method thereof can be provided to solve the problem of the engine not starting after an OTA update is completed by modifying the software alone, without changing the hardware.

[0036] In addition, various effects that can be identified directly or indirectly through this document may be provided. Brief explanation of the drawing

[0037] FIG. 1 is a block diagram showing a vehicle update control device according to one embodiment of the present invention. FIG. 2 is a drawing showing the specific configuration of a vehicle update control device according to one embodiment of the present invention. FIG. 3 is a flowchart showing whether a vehicle update control device according to one embodiment of the present invention determines whether to perform an OTA update. FIG. 4 is a flowchart showing the process of a vehicle update control device according to one embodiment of the present invention operating for a basic method OTA update. FIG. 5 is a flowchart showing the process of a vehicle update control device according to an embodiment of the present invention operating for an OTA update using a memory redundancy method. FIG. 6 is a flowchart illustrating the process of a vehicle update control device according to an embodiment of the present invention operating on a differential OTA update. FIG. 7 is a flowchart illustrating a vehicle update control method according to one embodiment of the present invention. Specific details for implementing the invention

[0038] Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that in assigning reference numerals to the components of each drawing, the same components are given the same reference numeral whenever possible, even if they are shown in different drawings. Furthermore, in describing the embodiments of the present invention, if it is determined that a detailed description of related known components or functions would hinder understanding of the embodiments of the present invention, such detailed description is omitted.

[0039] In describing the components of the embodiments of the present invention, terms such as first, second, A, B, (a), (b), etc., may be used. These terms are intended merely to distinguish the components from other components, and the essence, order, or sequence of the components is not limited by the terms. Furthermore, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the present invention pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this application.

[0040] Hereinafter, embodiments of the present invention will be described in detail with reference to FIGS. 1 to 7.

[0041] FIG. 1 is a block diagram showing a vehicle update control device according to one embodiment of the present invention.

[0042] Referring to FIG. 1, the vehicle update control device (100) may include a sensor unit (110) and a control unit (120).

[0043] The sensor unit (110) is equipped in a vehicle that performs an OTA (Over-The-Air) update and can obtain information about the vehicle's battery state (SoC, State of Charge).

[0044] For example, the sensor unit (110) is provided in the vehicle's battery and can measure the charge state of the battery.

[0045] For example, the sensor unit (110) can acquire information indicating the battery's charge status as a percentage and transmit it to the control unit (120).

[0046] For example, the sensor unit (110) is connected to the control unit (120) via wireless or wired communication and can transmit information about the battery status to the control unit (120) directly or indirectly.

[0047] The control unit (120) can perform overall control so that each component can perform its function normally. This control unit (120) may be implemented in the form of hardware, software, or a combination of hardware and software. Preferably, the control unit (120) may be implemented as a microprocessor, but is not limited thereto. In addition, the control unit (120) may perform various data processing and calculations, etc., as described below.

[0048] The control unit (120) transmits information about the OTA update to the update target device and, based on the battery status, can adjust the transmission time interval (STMin, Separation Time Min) between the data of the information about the OTA update transmitted to the update target device.

[0049] For example, the control unit (120) can comprehensively control the internal communication of the vehicle.

[0050] For example, the control unit (120) can control CAN (Controller Area Network) communication, CAND-FD (CAN with Flexible Data rate) communication, Ethernet communication, etc. connected inside the vehicle to transmit information about the update to the OTA update target device.

[0051] For example, the information about the OTA update transmitted by the control unit (120) to the update target device may include information transmitted to the update target device in the process of updating the update target device through ROM data that is downloaded in advance from the OTA update server and stored in a memory connected to the control unit (120), when the OTA update uses a basic method.

[0052] For example, the information about the OTA update transmitted by the control unit (120) to the update target device may include ROM data downloaded from the OTA update server and transmitted to the update target device when the OTA update uses a memory redundancy method.

[0053] For example, the control unit (120) can reduce the transmission time interval as the battery condition decreases.

[0054] For example, the control unit (120) can determine which section the battery status obtained from the sensor unit (110) corresponds to based on the transmission time interval for each battery status section set in advance, and can adjust the transmission time interval between data of information for the OTA update to the transmission time interval corresponding to the corresponding battery status section.

[0055] Here, the pre-configured transmission time interval for each battery status range can be set to a shorter interval as the battery status range decreases.

[0056] For example, the control unit (120) can shorten the time for the update to be performed by reducing the transmission time interval, and can reduce the amount of battery used for the update.

[0057] For example, the control unit (120) can adjust the transmission time interval based on the battery status identified in real time while the vehicle is in a Key Off state and an OTA update is being performed.

[0058] For example, the control unit (120) can obtain information about whether the vehicle is turned off through internal vehicle communication.

[0059] For example, the control unit (120) can adjust the transmission time interval based on whether the battery status identified in real time during the OTA update exceeds a preset threshold.

[0060] As another example, the control unit (120) can adjust the transmission time interval according to the transmission time interval corresponding to the section where the battery status identified in real time during an update is performed in a preset battery status section.

[0061] For example, the control unit (120) can adjust the transmission time interval while the OTA update is being performed with the vehicle in a key-off state, based on the expected battery condition of the vehicle at the time of completion of the OTA update.

[0062] For example, when the control unit (120) uses a basic method of updating the target device through ROM data stored in a memory connected to the control unit (120) for the OTA update, it can adjust the transmission time interval of information transmitted to the target device during the update process based on the expected battery condition of the vehicle at the time of completion of the OTA update.

[0063] For example, the control unit (120) can calculate the expected battery condition of the vehicle at the time of completion of the OTA update based on the current battery condition of the vehicle, the current consumed for the OTA update, and the expected time required for the OTA update.

[0064] For example, the control unit (120) can calculate the expected battery state of the vehicle at the time of completion of the OTA update by subtracting the amount of battery consumed when outputting the current consumed for the OTA update during the expected time required for the OTA update from the current battery state of the vehicle.

[0065] For example, the control unit (120) can determine whether the engine can be started at the time of completion of the OTA update through the battery status before the OTA update is performed, and determine whether the OTA update can be performed based on whether the engine can be started after the OTA update is completed.

[0066] For example, the control unit (120) may determine that starting is possible at the time of completion of the OTA update if the battery condition at the time of completion of the OTA update calculated before the OTA update is performed exceeds a reference value, and may determine that starting is not possible at the time of completion of the OTA update if the battery condition at the time of completion of the OTA update calculated before the OTA update is performed does not exceed a reference value.

[0067] For example, the control unit (120) may determine that the OTA update can be performed if it is determined that the engine can be started at the time the OTA update is completed, and may determine that the OTA update cannot be performed if it is determined that the engine cannot be started at the time the OTA update is completed.

[0068] For example, the control unit (120) can determine whether to stop the OTA update based on the battery status identified in real time while the OTA update is being performed with the vehicle in a key-off state or the battery status of the vehicle expected at the time of completion of the OTA update.

[0069] For example, the control unit (120) may determine to stop the OTA update if the battery status identified in real time while the OTA update is being performed is below a threshold value, or if the battery status of the vehicle expected at the time of completion of the OTA update is below a threshold value, and may stop the OTA update.

[0070] For example, the control unit (120) transmits information about an OTA update containing ROM data to the update target device via background transmission before the OTA update is performed, and if the vehicle is turned off during the transmission of information about the OTA update, the transmission time interval can be adjusted based on the battery status identified in real time.

[0071] For example, if the OTA update uses a memory redundancy method, the control unit (120) can transmit information about the OTA update, including OTA update ROM data received from the OTA server, to the update target device via background communication when the vehicle is in the Ignition On state.

[0072] At this time, if the vehicle is turned off while the control unit (120) is transmitting information about an OTA update containing ROM data to the update target device via background communication, the transmission of information about an OTA update containing ROM data can be maintained.

[0073] When the control unit (120) maintains the transmission of information regarding an OTA update containing ROM data while the vehicle is in a key-off state, it can reduce battery consumption by adjusting the transmission time interval based on the battery status identified in real time so that the vehicle can be started even after the background transmission is completed.

[0074] For example, the control unit (120) can reduce the transmission time interval of information for an OTA update containing ROM data to an update target device transmitted via background transmission as the battery status identified in real time becomes lower.

[0075] For example, after the transmission of information for an OTA update via background transmission is completed, the control unit (120) checks whether the battery condition of the vehicle expected at the time of completion of the OTA update is above a preset threshold, and if the battery condition of the vehicle is above the preset threshold, the operating memory of the vehicle can be set to the memory of the update target device where the ROM data is stored.

[0076] For example, when the OTA update uses a memory redundancy method, the control unit (120) can transmit information about the OTA update containing ROM data to the update target device, and if the vehicle's battery condition is above a preset threshold, determine that the vehicle can be started even after the OTA update is completed, and set the memory of the update target device where the ROM data is stored as the operating memory, thereby enabling the OTA update of the update target device to be performed in the vehicle's key-off state.

[0077] For example, the control unit (120) can determine whether to stop the OTA update based on the battery status when the OTA update is performed using differential data stored in the device to be updated.

[0078] When the OTA update uses a differential method, the update target device can perform the OTA update itself using differential data stored in the update target device, and the control unit (120) can determine whether to stop the OTA update based on the battery status to prevent the phenomenon where the update target device does not start after performing the OTA update itself using differential data.

[0079] For example, the control unit (120) can stop the OTA update when the battery status is below a preset threshold when the OTA update is performed using differential data stored in the update target device.

[0080] For example, if the OTA update uses a differential method, the control unit (120) can send an OTA update stop command to the update target device if the battery status is below a preset threshold.

[0081] For example, if the OTA update uses a differential method, the control unit (120) may determine whether the battery status is below a preset threshold, or the control unit (120) may transmit information about the battery status to the update target device and then determine whether the update target device's battery status is below a preset threshold.

[0082] FIG. 2 is a drawing showing the specific configuration of a vehicle update control device according to one embodiment of the present invention.

[0083] Referring to FIG. 2, the control unit (220) may include a CCU (221, Communication Control Unit) and an ICU (222, Integrated Central Control Unit).

[0084] The CCU (221) can receive ROM data for an OTA update from the server (201).

[0085] For example, the CCU (221) can receive data from the server (201) through the vehicle's external communication module.

[0086] For example, the CCU (221) can be connected to the ICU (222) via in-vehicle communication to transmit and receive various information.

[0087] For example, the CCU (221) can transmit information about the update to the update target device (202) via in-vehicle communication.

[0088] For example, the ICU (222) can receive information about the battery status from the sensor unit (210) via in-vehicle communication.

[0089] For example, the vehicle's OTA update may include an update through a basic method in which the CCU (221) downloads ROM package data for the OTA update and current ROM data for restoring the software to its original state before the update in case of update failure from the server (201), stores them in the memory of the CCU (221), and performs the OTA update when the vehicle's key is turned off.

[0090] As another example, the vehicle's OTA update may include an update through a memory redundancy method in which the CCU (221) downloads ROM package data for the OTA update from the server (201), transmits it to the update target device (202) without storing it in the memory of the CCU (221), and when the vehicle's key is turned off, the update target device (202) performs the OTA update itself using the ROM data stored in the memory of the update target device (202).

[0091] As another example, the OTA update of a vehicle may include an update through a memory redundancy differential method in which the CCU (221) downloads ROM package data for the OTA update from the server (201), transmits it to the update target device (202), and the update target device (202) performs the OTA update itself using differential data stored in the memory of the update target device (202).

[0092] The present invention will sequentially explain methods for improving the performance of OTA updates regarding the basic method, the memory redundancy method, and the memory redundancy differential method.

[0093] First, we will explain the case where the vehicle's OTA update uses the default method.

[0094] When the vehicle's OTA update uses the default method, the CCU (221) can download ROM package data for the OTA update and current ROM data for restoring the software to its original state before the update in case of update failure from the server (201).

[0095] The CCU (221) can transmit information about the time required for the update to the ICU (222).

[0096] The ICU (222) can determine whether an OTA update can be performed based on the time required for the update, the current consumed for the update, and the current battery status, and can transmit information about whether an OTA update can be performed and the battery status to the CCU (221).

[0097] The CCU (221) can update the update target device (202) by communicating with the update target device (202) through the ROM data stored in the memory of the CCU (221).

[0098] At this time, the CCU (221) can adjust the transmission time interval between data of information about the update to be transmitted to the update target device (202) based on the battery status.

[0099] If the battery state of the CCU (221) is below a threshold or the expected battery state at the time of update completion is below a threshold, the battery state can be adjusted by reducing the transmission time interval between data, thereby increasing efficiency in terms of the time consumed until the update is completed compared to the method of stopping the update and restoring to the previous software.

[0100] For example, when the battery status is 65% or higher, the CCU (221) can set the transmission time interval between data of information about the update to be transmitted to the update target device (202) to 2.0ms.

[0101] For example, the CCU (221) can set the transmission time interval between data of information about the update to be transmitted to the update target device (202) to 1.5ms when the battery status is 60% or more and less than 65%.

[0102] For example, when the battery status is less than 60%, the CCU (221) can set the transmission time interval between data of information about the update to be transmitted to the update target device (202) to 1.0ms.

[0103] Here, the battery state may include the current battery state or a predicted value of the battery state at the time the update is completed.

[0104] The battery status ranges set to 65% or higher, 60% or higher and less than 65%, and less than 60% are set arbitrarily for example purposes and may actually be set to different ranges.

[0105] In addition, the transmission time intervals between data corresponding to each section are set to 2.0ms, 1.5ms, and 1.0ms for illustrative purposes, and in reality, they may be set to different time intervals.

[0106] Next, we will explain the case where the vehicle's OTA update uses a memory redundancy method.

[0107] If the vehicle's OTA update uses a memory redundancy method, the CCU (221) can download ROM package data for the OTA update and current ROM data for restoring the software to its original state before the update in case of update failure from the server (201) while the vehicle's ignition is on.

[0108] At this time, unlike the basic method, the CCU (221) may not store ROM data in the memory of the CCU (221).

[0109] The CCU (221) can transmit information to the ICU (222) about the time required for the process of transmitting ROM data in the background to the update target device (202).

[0110] The ICU (222) can transmit information about the battery status to the CCU (221).

[0111] The CCU (221) can transmit ROM data downloaded from the server (201) to the update target device (202) via background transmission.

[0112] At this time, the CCU (221) can adjust the transmission time interval between the ROM data transmitted to the update target device (202) based on the battery status when the vehicle is turned off during background transmission.

[0113] If the battery state of the CCU (221) is below a threshold value or the expected battery state at the time of update completion is below a threshold value, the battery state can be adjusted by reducing the transmission time interval between data, thereby preventing the vehicle from being in a key-off state during background transmission and the engine from starting after the background transmission is completed.

[0114] For example, when the battery status of the CCU (221) is 65% or higher, the transmission time interval between data of the ROM data transmitted in the background to the update target device (202) can be set to 2.0ms.

[0115] For example, when the battery status is 60% or higher and less than 65%, the CCU (221) can set the transmission time interval between data of ROM data transmitted in the background to the update target device (202) to 1.5ms.

[0116] For example, when the battery status is less than 60%, the CCU (221) can set the transmission time interval between data of ROM data transmitted in the background to the update target device (202) to 1.0ms.

[0117] Here, the battery state may include the current state of the battery.

[0118] The battery status ranges set to 65% or higher, 60% or higher and less than 65%, and less than 60% are set arbitrarily for example purposes and may actually be set to different ranges.

[0119] In addition, the transmission time intervals between data corresponding to each section are set to 2.0ms, 1.5ms, and 1.0ms for illustrative purposes, and in reality, they may be set to different time intervals.

[0120] After background transmission is completed, if the predicted value of the battery status at the time of OTA update completion is greater than or equal to a preset threshold, the CCU (221) can change the operating memory of the vehicle to the memory of the update target device (202) where the ROM data is stored through swapping.

[0121] Finally, we will explain the case where the vehicle's OTA update uses the memory redundancy differential method.

[0122] When the vehicle's OTA update uses a memory redundancy method, the CCU (221) can download ROM data for the OTA update from the server (201) while the vehicle's ignition is on, and transmit the ROM data to the update target device (202).

[0123] For example, the CCU (221) checks whether the battery status is below a threshold based on information about the battery status received from the ICU (222), and if the battery status falls below the threshold while the update target device (202) is performing an update using differential data stored in the memory of the update target device (202), the CCU (221) can send an update stop command to the update target device (202).

[0124] As another example, the CCU (221) can transmit information about the battery status received from the ICU (222) to the update target device (202), and if the battery status falls below a threshold while the update target device (202) is performing an update using differential data stored in the memory of the update target device (202), the update can stop itself.

[0125] FIG. 3 is a flowchart showing whether a vehicle update control device according to one embodiment of the present invention determines whether to perform an OTA update.

[0126] Referring to FIG. 3, the vehicle update control device (100) can determine the time required for updating the update target devices (S301).

[0127] For example, the CCU (221) can check the devices to be updated when the vehicle's key is turned off, calculate the total time required to update the devices to be updated, and transmit information about the total time required to update calculated to the ICU (222).

[0128] The vehicle update control device (100) determines the time required for the update for the update target devices (S301), and then, using the current battery SOC value, current consumption value, and update time required, checks whether the battery SOC value at the time of update completion exceeds a reference value and determines whether the OTA update can be performed (S302).

[0129] For example, the ICU (222) can calculate the battery SOC value at the end of the update based on the current battery SOC value, the current consumption value, and the update time required. If the calculated battery SOC value at the end of the update exceeds a threshold value, it can determine that the OTA update can be performed, and if the calculated battery SOC value at the end of the update does not exceed a threshold value, it can determine that the OTA update cannot be performed.

[0130] Additionally, the ICU (222) can transmit information to the CCU (221) regarding whether the determined OTA update can be performed.

[0131] The vehicle update control device (100) uses the current battery SOC value, the current consumption value, and the update time to determine whether the battery SOC value at the time of update completion exceeds a reference value, and then determines whether an OTA update can be performed (S302), and then performs or does not perform the OTA based on the information on whether an OTA update can be performed (S303).

[0132] For example, the CCU (221) can perform an OTA update if it is determined that it is possible to perform the OTA based on whether it is possible to perform the OTA received from the ICU (222).

[0133] In the following, it is assumed that the vehicle update control device (100) of FIG. 1 performs the process of FIG. 4 to FIG. 6. Also, in the description of FIG. 4 to FIG. 6, the operation described as being performed by the vehicle update device (100) can be understood as being controlled by the control unit (120) of the vehicle control device (100).

[0134] FIG. 4 is a flowchart showing the process of a vehicle update control device according to one embodiment of the present invention operating for a basic method OTA update.

[0135] Referring to FIG. 4, the vehicle update control device (100) can check whether the vehicle is in a key-off state (S401).

[0136] For example, a vehicle update control device (100) can obtain information about whether the vehicle is in a key-off state through in-vehicle communication.

[0137] The vehicle update control device (100) checks whether the vehicle is in a key-off state (S401), and if it is confirmed to be in a key-off state, it can check whether the user has approved the update (S402).

[0138] For example, a vehicle update control device (100) can obtain information regarding whether a user has entered an update approval through communication within the vehicle via a UI (User Interface) included in a device such as an AVN (Audio, Video, Navigation) of the vehicle.

[0139] The vehicle update control device (100) checks whether the user has approved the update (S402), and if it is confirmed that the user has approved the update, it can check whether the battery SoC value is 65% or higher (S403).

[0140] For example, a vehicle update control unit (100) can check whether the battery status value transmitted from the ICU to the CCU is 65% or higher.

[0141] Here, the percentage of 65% is arbitrarily chosen for the sake of example and may actually be set to a different percentage value.

[0142] In addition, the same applies not only to the word “greater than” but also to cases where it “exceeds” according to embodiments of the present invention.

[0143] The vehicle update control device (100) checks whether the battery SoC value is 65% or higher (S403), and if it is confirmed that the battery SoC value is 65% or higher, it can perform an update by setting the STMin value transmitted to the update target device to 2ms (S404).

[0144] For example, a vehicle update control device (100) can perform an update by setting the STMin value for the information transmitted between the CCU and the update target device to 2ms.

[0145] Here, the time interval of 2ms is arbitrarily chosen for the purpose of example, and in reality, it can be set to a different time interval.

[0146] The vehicle update control unit (100) checks whether the battery SoC value is 65% or higher (S403), and if it is confirmed that the battery SoC value is not 65% or higher, it can check whether the battery SoC value is 60% or higher and less than 65% (S405).

[0147] For example, a vehicle update control unit (100) can check whether the battery status value transmitted from the ICU to the CCU is 60% or more and less than 65%.

[0148] Here, the percentage of 60% is arbitrarily chosen for the sake of example and may actually be set to a different percentage value.

[0149] In addition, the same content may apply to cases of “less than” in accordance with embodiments of the present invention, not limited to the word “less than”.

[0150] The vehicle update control device (100) checks whether the battery SoC value is 60% or more and less than 65% (S405), and if it is confirmed that the battery SoC value is 60% or more and less than 65%, it can perform an update by sending an STMin value of 1.5ms to the update target device (S406).

[0151] For example, a vehicle update control device (100) can perform an update by setting the STMin value for the information transmitted between the CCU and the update target device to 1.5ms.

[0152] Here, the time interval of 1.5ms is arbitrarily chosen for the purpose of example, and in reality, it can be set to a different time interval.

[0153] The vehicle update control device (100) checks whether the battery SoC value is 60% or more and less than 65% (S405), and if it is confirmed that the battery SoC value is 60% or more and not less than 65%, it can perform an update with an STMin value of 1ms transmitted to the update target device (S407).

[0154] For example, a vehicle update control device (100) can perform an update by setting the STMin value for the information transmitted between the CCU and the update target device to 1ms.

[0155] Here, the time interval of 1ms is arbitrarily chosen for the purpose of example, and in reality, it can be set to a different time interval.

[0156] FIG. 5 is a flowchart showing the process of a vehicle update control device according to an embodiment of the present invention operating for an OTA update using a memory redundancy method.

[0157] Referring to FIG. 5, the vehicle update control device (100) can check whether the vehicle is in a key-off state (S501).

[0158] The process of S501 is identical to the process of S401 in Fig. 4, so the explanation will be omitted here.

[0159] The vehicle update control device (100) checks whether the vehicle is in a key-off state (S501), and if it is confirmed to be in a key-off state, it can check whether information about the update is being transmitted in the background to the update target device (S502).

[0160] For example, a vehicle update control device (100) can obtain information about whether information about an update is being transmitted in the background to an update target device through in-vehicle communication.

[0161] The vehicle update control device (100) checks whether information about the update is being transmitted in the background to the update target device (S502), and if it is confirmed that information about the update is being transmitted in the background to the update target device, it can check whether the battery SoC value is 65% or higher (S503).

[0162] The process of S503 is identical to the process of S403 in Fig. 4, so the explanation will be omitted here.

[0163] The vehicle update control device (100) checks whether the battery SoC value is 65% or higher (S503), and if it is confirmed that the battery SoC value is 65% or higher, it can perform background transmission with an STMin value of 2ms to be transmitted to the update target device (S504).

[0164] For example, a vehicle update control device (100) can perform an update by setting the STMin value of the information transmitted via background communication between the CCU and the update target device to 2ms.

[0165] Here, the time interval of 2ms is arbitrarily chosen for the purpose of example, and in reality, it can be set to a different time interval.

[0166] The vehicle update control unit (100) checks whether the battery SoC value is 65% or higher (S503), and if it is confirmed that the battery SoC value is not 65% or higher, it can check whether the battery SoC value is 60% or higher and less than 65% (S505).

[0167] The process of S505 is identical to the process of S405 in Fig. 4, so the explanation will be omitted here.

[0168] The vehicle update control device (100) checks whether the battery SoC value is 60% or more and less than 65% (S505), and if it is confirmed that the battery SoC value is 60% or more and less than 65%, it can perform background transmission with an STMin value of 1.5ms to be transmitted to the update target device (S506).

[0169] For example, a vehicle update control device (100) can perform an update by setting the STMin value of the information transmitted via background communication between the CCU and the update target device to 1.5ms.

[0170] Here, the time interval of 1.5ms is arbitrarily chosen for the purpose of example, and in reality, it can be set to a different time interval.

[0171] The vehicle update control device (100) checks whether the battery SoC value is 60% or more and less than 65% (S505), and if it is confirmed that the battery SoC value is 60% or more and not less than 65%, it can perform background transmission with an STMin value of 1ms to be transmitted to the update target device (S507).

[0172] For example, a vehicle update control device (100) can perform an update by setting the STmin value of the information transmitted via background communication between the CCU and the update target device to 1ms.

[0173] Here, the time interval of 1ms is arbitrarily chosen for the purpose of example, and in reality, it can be set to a different time interval.

[0174] FIG. 6 is a flowchart illustrating the process of a vehicle update control device according to an embodiment of the present invention operating on a differential OTA update.

[0175] Referring to FIG. 6, the vehicle update control device (100) can check whether the vehicle is in a key-off state (S601).

[0176] The process of S501 is identical to the process of S401 in Fig. 4, so the explanation will be omitted here.

[0177] The vehicle update control device (100) checks whether the vehicle is in a key-off state (S601), and if it is confirmed to be in a key-off state, the user approves the update and can check whether the update target device is performing its own update (S602).

[0178] For example, a vehicle update control device (100) can obtain information regarding whether a user has entered an update approval through in-vehicle communication via a UI included in a device such as a vehicle’s AVN.

[0179] For example, a vehicle update control device (100) can obtain information about whether the update target device is performing its own update through in-vehicle communication.

[0180] The vehicle update control device (100) can check whether the user approves the update and whether the update target device is performing its own update (S602), and whether the battery SoC value is above a threshold value (S603).

[0181] For example, a vehicle update control unit (100) can check whether the battery status value transmitted from the ICU to the CCU is above a reference value.

[0182] In addition, the same applies not only to the word “greater than” but also to cases where it “exceeds” according to embodiments of the present invention.

[0183] The vehicle update control device (100) checks whether the battery SoC value is above a threshold value (S603), and if it is confirmed that the battery SoC value is above the threshold value, it can send an update continuation command to the update target device (S604).

[0184] For example, if the battery SoC value is confirmed to be above a threshold, the CCU can send a command to continue the update to the device to be updated.

[0185] The vehicle update control device (100) checks whether the battery SoC value is above a threshold value (S603), and if it is confirmed that the battery SoC value is not above the threshold value, it can send an update stop command to the update target device (S605).

[0186] For example, if it is confirmed that the battery SoC value is not above a threshold, the CCU can send a command to stop the update to the device to be updated.

[0187] FIG. 7 is a flowchart illustrating a vehicle update control method according to one embodiment of the present invention.

[0188] Referring to FIG. 7, the vehicle update control method may include the step of obtaining information about the battery status of the vehicle (S710) and the step of transmitting information about the OTA update to the update target device, and the step of adjusting the transmission time interval between data of the information about the OTA update transmitted to the update target device based on the battery status (S720).

[0189] The step (S710) of obtaining information about the vehicle's battery status can be performed through the sensor unit (110, 210).

[0190] The step (S720) of transmitting information about an OTA update to a device to be updated and adjusting the transmission time interval between data of information about an OTA update transmitted to the device to be updated based on the battery status can be performed through the control unit (120, 220).

[0191] For example, the step (S720) of adjusting the transmission time interval between data of information about an OTA update transmitted to an update target device may include the step of the control unit (120, 220) adjusting the transmission time interval to be shorter as the battery status is lower.

[0192] For example, the step (S720) of adjusting the transmission time interval between data of information about an OTA update transmitted to an update target device may include the step of the control unit (120, 220) adjusting the transmission time interval based on the battery status identified in real time while the OTA update is being performed with the vehicle in a key-off state or the battery status of the vehicle expected at the time of completion of the OTA update.

[0193] For example, the step (S720) of adjusting the transmission time interval between data of information about an OTA update transmitted to an update target device may include the control unit (120, 220) transmitting information about an OTA update containing ROM data to an update target device via background transmission before the OTA update is performed, and, if the vehicle becomes key-off during the transmission of information about the OTA update, adjusting the transmission time interval based on the battery status identified in real time.

[0194] For example, the vehicle update control method may further include a step in which the control unit (120, 220) calculates the expected battery state of the vehicle at the time of completion of the OTA update based on the current battery state of the vehicle, the current consumed for the OTA update, and the expected time required for the OTA update.

[0195] For example, the vehicle update control method may further include a step in which the control unit (120, 220) determines whether the vehicle can be started at the time of completion of the OTA update through the battery status before the OTA update is performed, and a step in which the control unit (120, 220) determines whether the OTA update can be performed based on whether the vehicle can be started after the OTA update is completed.

[0196] For example, a vehicle update control method may further include a step in which a control unit (120, 220) determines whether to stop the OTA update based on the battery status identified in real time while the OTA update is being performed with the vehicle in a key-off state or the battery status of the vehicle expected at the time of completion of the OTA update.

[0197] For example, a vehicle update control method may further include the step of the control unit (120, 220) checking whether the expected battery state of the vehicle at the time of completion of the OTA update is above a preset threshold after the transmission of information for the OTA update through background transmission is completed, and the step of the control unit (120, 220) setting the operating memory of the vehicle to the memory of the update target device where ROM data is stored if the battery state of the vehicle is above the preset threshold.

[0198] For example, a vehicle update control method may further include a step in which a control unit (120, 220) determines whether to stop the OTA update based on the battery status when the OTA update is performed using differential data stored in the update target device.

[0199] The steps of the method or algorithm described in connection with the embodiments disclosed herein may be directly implemented by hardware, software modules, or a combination of both, executed by a processor. The software modules may reside in storage media (i.e., memory and / or storage) such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, and CD-ROMs.

[0200] An exemplary storage medium is coupled to a processor, and the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium may be integrated with the processor. The processor and the storage medium may reside within an Application-Specific Integrated Circuit (ASIC). The ASIC may reside within a user terminal. Alternatively, the processor and the storage medium may reside as separate components within the user terminal.

[0201] The above description is merely an illustrative explanation of the technical concept of the present invention, and those skilled in the art to which the present invention pertains will be able to make various modifications and variations within the scope of the essential characteristics of the present invention.

[0202] Accordingly, the embodiments disclosed in this invention are intended to illustrate, not limit, the technical concept of the invention, and the scope of the technical concept of the invention is not limited by these embodiments. The scope of protection of this invention shall be interpreted by the claims below, and all technical concepts within an equivalent scope shall be interpreted as being included within the scope of rights of this invention.

Claims

Claim 1 A vehicle update control device comprising: a sensor unit equipped in a vehicle performing an OTA (Over-The-Air) update and acquiring information regarding the battery state (SoC, State of Charge) of the vehicle; and a control unit that transmits information regarding the OTA update to an update target device and, based on the battery state, adjusts the transmission time interval (STMin, Separation Time Min) between data of the information regarding the OTA update transmitted to the update target device. Claim 2 In claim 1, the control unit is a vehicle update control device that reduces the transmission time interval as the battery state is lower. Claim 3 In claim 1, the control unit is a vehicle update control device that adjusts the transmission time interval based on the battery status identified in real time while an OTA update is being performed with the vehicle in a Key Off state. Claim 4 In claim 1, the control unit is a vehicle update control device that adjusts the transmission time interval while the OTA update is performed with the vehicle in a key-off state, based on the battery status of the vehicle expected at the time of completion of the OTA update. Claim 5 In claim 4, the control unit is a vehicle update control device that calculates the expected battery state of the vehicle at the time of completion of the OTA update based on the current battery state of the vehicle, the current consumed for the OTA update, and the expected time required for the OTA update. Claim 6 A vehicle update control device according to claim 1, wherein the control unit determines whether starting is possible at the time of completion of the OTA update through the battery status before the OTA update is performed, and determines whether the OTA update can be performed based on whether starting is possible after the OTA update is completed. Claim 7 In claim 1, the control unit is a vehicle update control device that determines whether to stop the OTA update based on the battery status identified in real time while the OTA update is being performed with the vehicle in a key-off state or the battery status of the vehicle expected at the time of completion of the OTA update. Claim 8 A vehicle update control device according to claim 1, wherein the control unit transmits information regarding the OTA update, including ROM data, to the update target device via background transmission before the OTA update is performed, and adjusts the transmission time interval based on the battery status identified in real time when the vehicle becomes key-off during the transmission of information regarding the OTA update. Claim 9 In claim 8, the control unit checks whether the battery state of the vehicle expected at the time of completion of the OTA update is above a preset threshold after the transmission of information regarding the OTA update through the background transmission is completed, and if the battery state of the vehicle is above the preset threshold, the operating memory of the vehicle is set to the memory of the update target device where the ROM data is stored. Claim 10 In claim 1, the control unit is a vehicle update control device that determines whether to stop the OTA update based on the battery status when the OTA update is performed using differential data stored in the update target device. Claim 11 In claim 10, the control unit is a vehicle update control device that stops the OTA update if the battery state is below a preset threshold when the OTA update is performed using differential data stored in the update target device. Claim 12 A vehicle update control method comprising: a sensor unit equipped in a vehicle performing an OTA update, the step of acquiring information regarding the battery status of the vehicle; and a control unit, the step of transmitting information regarding the OTA update to an update target device and adjusting the transmission time interval between data of the information regarding the OTA update transmitted to the update target device based on the battery status. Claim 13 In claim 12, the step of the control unit adjusting the transmission time interval between data of information regarding the OTA update transmitted to the update target device comprises the step of the control unit adjusting the transmission time interval to be shorter as the battery status is lower. Claim 14 In claim 12, the step of adjusting the transmission time interval between data of information regarding the OTA update transmitted by the control unit to the update target device comprises the step of the control unit adjusting the transmission time interval based on the battery status identified in real time while the OTA update is being performed with the vehicle in a key-off state or the battery status of the vehicle expected at the time of completion of the OTA update. Claim 15 A vehicle update control method according to claim 14, wherein the control unit further comprises the step of calculating the expected battery state of the vehicle at the time of completion of the OTA update based on the current battery state of the vehicle, the current consumed for the OTA update, and the expected time required for the OTA update. Claim 16 A vehicle update control method according to claim 12, further comprising: a step in which the control unit determines whether starting is possible at the time of completion of the OTA update through the battery status before the OTA update is performed; and a step in which the control unit determines whether the OTA update can be performed based on whether starting is possible after the OTA update is completed. Claim 17 A vehicle update control method according to claim 12, further comprising the step of the control unit determining whether to stop the OTA update based on the battery status identified in real time while the OTA update is being performed with the vehicle in a key-off state or the battery status of the vehicle expected at the time of completion of the OTA update. Claim 18 In claim 12, the step of adjusting the transmission time interval between data of information regarding the OTA update transmitted by the control unit to the update target device comprises the step of the control unit transmitting information regarding the OTA update, including ROM data, to the update target device via background transmission before the OTA update is performed, and adjusting the transmission time interval based on the battery status identified in real time when the vehicle becomes key-off during the transmission of information regarding the OTA update. Claim 19 A vehicle update control method according to claim 18, further comprising: a step in which the control unit checks whether the battery state of the vehicle expected at the time of completion of the OTA update is above a preset threshold after the transmission of information regarding the OTA update through the background transmission is completed; and a step in which the control unit sets the operating memory of the vehicle to the memory of the update target device where the ROM data is stored if the battery state of the vehicle is above the preset threshold. Claim 20 A vehicle update control method according to claim 12, further comprising the step of the control unit determining whether to stop the OTA update based on the battery status when the OTA update is performed using differential data stored in the update target device.

Images