DEVICE AND METHOD FOR CONTROLLING AN UPDATE FOR A VEHICLE CONTROL SYSTEM AND VEHICLE WITH THE SAME
Patent Information
- Application Number
- DE102019213973
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-12-12
- Filing Date
- 2019-09-13
- Publication Date
- 2026-08-27
- Estimated Expiration
- 2039-09-13
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
TECHNICAL AREA The present disclosure relates to a device and a method for controlling an update for a vehicle control system and a vehicle system. BACKGROUND An update operation of a vehicle control system is generally performed using an electrical load when the ignition of a power engine is switched off. An electrical load is a power source that provides the driving force to ignite the engine of a vehicle. The electrical load must have a certain level of electrical energy to ensure ignition power. If the vehicle control unit update is performed with the engine ignition off, the vehicle's ignition performance cannot be guaranteed due to the electrical load's consumption of energy. If even a small amount of electrical energy remains in the load, the control unit update operation cannot be completed. From German patent applications DE 10 2014 115 943 A1 and DE 10 2017 107 744 A1, an update control device for a vehicle controller is known, comprising a device for collecting condition information, which is configured to collect vehicle condition information when an update event of the vehicle controller occurs; a battery control device, which is configured to determine an update-based final target state of charge (target SOC) based on the collected vehicle condition information and to control charging or discharging of a battery based on the determined final target SOC; and a control device, which is configured to download update data of the vehicle controller from an update server and to update the vehicle controller. US patent 2018 / 0241229A1 discloses a server for a charging / discharging system comprising a control unit. The control unit is configured to communicate with a multitude of registered vehicles, each equipped with a rechargeable and dischargeable battery. The control unit is configured to collect information about the scheduled start time of the next trip for each of the registered vehicles. The control unit is configured to collect information about the electrical power. Based on the scheduled trip start time and the electrical power information, the control unit is configured to determine a target vehicle from among the registered vehicles that are at least parked, and whose battery is to be charged or discharged.The control unit is configured to send either a charging command to the target vehicle, instructing it to charge the target vehicle's battery, or a discharging command, instructing it to discharge the target vehicle's battery. In KR 10 2013 0 014 885 A, a vehicle's software update device is connected via internal communication to a multitude of electronic control units in a vehicle to manage the software versions of a multitude of electronic control units, accesses an update server to download the software to be updated, transmits the downloaded software to a multitude of electronic control units, a wireless internet connection unit to connect to the update server via the wireless internet; a display unit to output a status of the update control unit; and a keypad input unit to approve data for the update request item displayed on the display unit. US Patent 2012 / 0078553A1 describes a device for providing information about a battery charge booster to a vehicle equipped with an externally charged battery. The device includes a current position sensor that detects the vehicle's current location, a charge level sensor that detects the battery's state of charge (SOC), a database that stores information about the battery charge booster, and a control unit. The control unit registers the vehicle's current location in the database as the location of a battery charge booster when the SOC has been boosted under a predefined condition.This increases the amount of information about the locations of usable facilities for increasing the battery charging capacity. Furthermore, DE 10 2016 102 507 A1 shows a vehicle comprising a connector for coupling a battery in the vehicle with a load located outside the vehicle. An energy management system includes a controller programmed to operate the vehicle's battery within a target state-of-charge range defined by upper and lower state-of-charge limits. In response to a request to prepare for power generation at a destination before arrival, the controller increases the lower state-of-charge limit as the distance to the destination decreases. During the journey to the destination, the battery is operated in such a way that the battery's state of charge upon arrival allows it to provide power to the external load for a predetermined period before the internal combustion engine is started. OVERVIEW The present disclosure was made to solve the aforementioned problems that arise in the prior art, while preserving the advantages gained through the prior art. The purpose of this disclosure is to provide a device and a method for controlling an update for a vehicle control unit and a vehicle system, which sets a target state of charge (SOC) of a battery required to perform an update of the vehicle control unit while the vehicle is being driven, in order to control the charging or discharging of the battery. Therefore, the vehicle's ignition performance is ensured even after an update of the vehicle control unit, while fuel efficiency is maintained at the time the update data is downloaded. The problem is solved by an update control device with the features of claim 1, an update control method with the features of claim 9, a vehicle system with the features of claim 15, and an update control device for a vehicle control system with the features of claim 16. Advantageous further developments are found in the dependent claims. The technical problems to be solved by the present inventive concept are not limited to those mentioned above. Any other technical problems not mentioned herein will be clearly understandable to someone with ordinary technical skills, to which the present disclosure belongs, from the following description. According to one aspect of the present disclosure, an update control device for a vehicle controller may include a state information gathering device that collects vehicle state information when a vehicle controller update event occurs. The update control device further includes a battery control device that determines an update-based final target state of charge (SOC) based on the collected vehicle state information and controls the charging or discharging of a battery based on the determined final target SOC. The update control device also includes a control device that downloads vehicle controller update data from an update server and updates the vehicle controller.The battery control device determines an increase in a target SOC based on a smaller value obtained by subtracting the current SOC from a fully charged state and a request SOC at the time of the vehicle control update. The battery control device determines the final target SOC by applying the increase in the target SOC based on whether navigation setting information is set and whether a previous update has been approved. Furthermore, the battery control device determines the final target SOC based on a value obtained by adding the increase in the target SOC to a target SOC based on generation control when navigation setting information is not available and the previous update has been approved for the vehicle control. The vehicle status information can include at least battery SOC information, navigation setting information and / or information about an estimated driving time. The battery control device can determine the required SOC based on at least one load power consumption, battery capacity, amount of update data, reset or rollback data and / or data transmission rate. The control device can determine whether the update event occurs by identifying software version information of the vehicle control unit from the update server. The control device can issue a message requesting whether update data should be downloaded at the time the update event occurs. The battery control device can set the vehicle's target state of charge (SOC) to the specified final target SOC once the download of the update data has been approved. The control device can issue a message requesting permission to update the vehicle control system at a time when the vehicle's ignition is switched off. The control device can update the vehicle control system when an approval for the vehicle control system update is completed, and switch the vehicle from an operating mode to a sleep mode if the approval for the vehicle control system update is rejected. According to one aspect of the present disclosure, an update control procedure for a vehicle controller may include: collecting vehicle state information when a vehicle controller update event occurs, determining an update-based final target state of charge (target SOC) based on the collected vehicle state information and controlling a charging or discharging of a battery based on the determined final target SOC, downloading vehicle controller update data and updating the vehicle controller.Controlling the charging or discharging of the battery involves determining a final target SOC by applying an increase in the target SOC based on whether navigation setting information is set and whether a previous update has been approved, and determining the final target SOC by applying the increase in the target SOC depending on whether navigation setting information is set and whether a previous update has been approved for vehicle control. According to one aspect of the present disclosure, a vehicle system may include an update server that provides update data to a vehicle controller. The vehicle system may further include an update control unit that determines an update-based final target state of charge (target SOC) based on vehicle state information when a vehicle controller update event occurs, controls charging or discharging of a battery based on the determined final target SOC, downloads vehicle controller update data from the update server, and updates the vehicle controller.The update control unit determines the final target SOC by applying an increase amount to a target SOC based on whether navigation setting information is set and whether a previous update is approved, and the update control unit determines the final target SOC based on a value obtained by adding the increase amount to the target SOC to a generation control-based target SOC when navigation setting information is not available and the previous update is approved for vehicle control. According to one aspect of the present disclosure, an update control device for a vehicle control system comprises a processor and non-transitory memory coupled to the processor. The update control device further comprises computer-executable code stored in the non-transitory memory, which is executable by the processor to cause the processor to collect vehicle state information when a vehicle control system update event occurs, determine an update-based final target state of charge (SOC) based on the collected vehicle state information, control the charging or discharging of a battery based on the determined final target SOC, download vehicle control system update data from an update server, and update the vehicle control system.The final target SOC is determined by applying an increase amount to a target SOC based on whether navigation setting information is set and whether the update is approved for vehicle control, and the final target SOC is determined based on a value obtained by adding the increase amount in the target SOC to a generation control-based target SOC when navigation setting information is not present and the update is approved for vehicle control. BRIEF DESCRIPTION OF THE DRAWINGS The above-mentioned and other tasks, features, and advantages of the present disclosure will be more apparent from the following detailed description in conjunction with the accompanying drawings, in which: Fig. 1 illustrates a vehicle system to which an update control device of a vehicle controller according to an embodiment of the present disclosure is applied; Fig. 2 illustrates a configuration of an update control device of a vehicle controller according to an embodiment of the present disclosure; Figs. 3A-3C, 4, and 5A-5D illustrate an embodiment describing the operation of an update control device of a vehicle controller according to an embodiment of the present disclosure; Figs. 6 and 7 illustrate flowcharts of an update control procedure of a vehicle controller according to an embodiment of the present disclosure; and Fig.Figure 8 illustrates a computing system in which a method according to an embodiment of the present disclosure is carried out. DETAILED DESCRIPTION Various embodiments of the present disclosure are described in detail below with reference to the drawings. When adding reference numbers to the components of each drawing, it should be noted that the identical or equivalent component is designated by the same number, even if the same component is shown in other drawings. Furthermore, when describing the embodiment of the present disclosure, a detailed description of generally known features or functions will be excluded or omitted in order not to unnecessarily obscure the main point of the present disclosure. In describing the components of the embodiment according to the present disclosure, expressions such as first / first / first, second / second / second, "A", "B", (a), (b), and the like may be used. These expressions are intended only to distinguish one component from another and do not restrict the nature, sequence, or order of the components. Unless otherwise defined, all expressions used herein, including technical or scientific terms, have the same meanings as those normally understood by someone with ordinary technical skills in the field to which the present disclosure belongs.Such expressions as those defined in a generally used dictionary are to be interpreted as having meanings equal to contextual meanings in the relevant field of technology, and not as having ideal or overly formal meanings, unless they are clearly defined as having such meanings in the present application. Fig. 1 illustrates a vehicle system to which an update control device of a vehicle control system according to an embodiment of the present disclosure is applied. With reference to Fig. 1, a vehicle system may include an update control unit 100 (hereinafter referred to as an “update control unit”) of a vehicle controller and an update server 200. The update server 200 can store and manage update data from vehicle-internal controllers 11, 12 and 13 (hereinafter referred to as controllers 11-13) in a vehicle 1 and provide the update data of the controllers 11-13 according to a request from the update control unit 100. The update control unit 100 can communicate wirelessly with the update server 200 and determine whether an update event occurs for the vehicle's internal controllers 11-13. If an update event occurs for at least one of the vehicle's internal controllers 11-13, the update control unit 100 can determine an update-based final target state of charge (target SOC) based on vehicle state information and ensure the energy required for the update by controlling the charging or discharging of a battery based on the final target SOC. In this case, the update control unit 100 can download the update data for the vehicle's internal controls 11-13 from the update server 200, while simultaneously controlling the charging or discharging of the battery based on the final target state of charge (SOC). When the vehicle's ignition is switched off, the update control unit 100 can update a corresponding control unit using the downloaded update data. According to the update control device 100 of the present disclosure, the charging or discharging is controlled by setting the target state of charge (SOC) of the battery to perform the update of the vehicle's internal controls 11-13 while the vehicle 1 is being driven, thereby ensuring sufficient energy at the time of data download and update. Therefore, the ignition power of the vehicle 1 is maintained even after the update of the controls 11-13, while fuel efficiency is maintained at the time of data download. The update control unit 100 according to the present disclosure can be implemented in the vehicle 1. In this case, the update control unit 100 can be formed integrally with the internal control units of the vehicle 1 and implemented as a separate device, and connected to the control units of the vehicle 1 by separate coupling devices. A detailed configuration of the update control unit 100 is given with reference to an embodiment of Fig. 2. Fig. 2 illustrates a configuration of an update control unit of a vehicle control system according to an embodiment of the present disclosure. With reference to Fig. 2, the update control device 100 can include a control device 110, an interface 120, a communication device 130, a memory 140, a device 150 for collecting status information, and a battery control device 160. In the present disclosure, the control device 110, the device 150 for collecting status information, and the battery control device 160 of the update control device 100 can be implemented as at least one processor according to the embodiment. The interface 120 can include an input device that receives a control command from a user and an output device that outputs the operating status, results, or the like of the update control device 100. The input device can include a keypad and may also include a mouse, control lever, jog shuttle, stylus, and the like. Additionally, the input device may also include a softkey implemented on a display. The output device can include a display and may also include an audio output device, such as a speaker. For example, the output device can display a message requesting a user to approve the vehicle control unit update and / or the download of update data. Additionally, the output device can display an operational status at the time the vehicle control unit update data is being downloaded and / or the vehicle control unit is being updated. In this case, if a touch sensor, such as a touch film, touch plate or touch field or touchpad, is provided in the display, the display can function as a touchscreen and be implemented in a form where the input device and the output device are integrated. The display can include at least a liquid crystal display (LCD), a thin film transistor liquid crystal display (TFT LCD), an organic light-emitting diode (OLED) display, a flexible display, a field emission display (FED), and / or a three-dimensional display (3D display). The communication device 130 may contain a communication module that supports communication interfaces with electronic components and / or controls provided in the vehicle. For example, the communication module can receive version information of the control software from the controllers installed in the vehicle and transmit update data to the controllers. The communication module can also receive battery status information from a battery management system (BMS). Furthermore, the communication module can receive destination setting information, estimated time of arrival information, or similar data from a navigation device. The disclosure may include vehicle network communication supporting the module, such as CAN communication (Controller Area Network communication), LIN communication (Local Interconnect Network communication), and Flex-Ray communication. In addition, the communication device 130 can contain a communication module for wireless internet connection or a communication module for short-range communication. For example, the communication module can be connected to the update server 200 via wireless communication and receive update information from the controllers. The communication module can also download the update data for each controller via wireless communication with the update server 200. In the revelation, wireless internet technology may include wireless LAN (WLAN), wireless broadband (WIBRO), Wi-Fi, World Interoperability for Microwave Access (WIMAX), and the like. Near-field communication technology can include Bluetooth, ZigBee, Ultra Wideband (UWB), Radio Frequency Identification (RFID), Infrared Data Association (IrDA) and the like. Memory 140 can, for example, store data and / or an algorithm that is required for the update control unit 100 to function. For example, memory 140 can store information from the vehicle's internal control systems. Memory 140 can also store vehicle status information received by communication unit 130. Memory 140 can store condition information, instructions, and / or algorithms for determining a final target state of charge (SOC) based on vehicle condition information. Memory 140 can also store instructions and / or algorithms for updating any control unit. In the disclosure, the memory 140 may contain a storage medium, such as random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), or the like. The control device 110 can process signals transmitted between components of the update control unit 100 during the download of the vehicle control update data or the update of the vehicle control. The control device 110 can determine whether an update event is occurring by identifying software version information of the vehicle control unit via the update server 200. If it is determined that an update event is occurring for the control units, the control device 110 can request the device 150 to collect vehicle status information. When the update event for the controllers occurs, the device 150 can collect vehicle status information in response to the request from the control device 110. According to the disclosure, the vehicle status information can include at least battery state of charge (SOC) information, navigation setting information, and / or information about the estimated driving time. The device 150 for collecting condition information can collect vehicle condition information from the controllers connected by the communication device 130 or collect vehicle condition information from sensors. The device 150 for collecting condition information can transmit the collected vehicle condition information to the control device 110. The control device 110 can transmit the vehicle condition information to the battery control device 160 and request the battery control device 160 to control the charging or discharging of the battery according to the vehicle condition. The battery control device 160 can determine an update-based final target SOC based on the vehicle state information in response to the request from the control device 110 and control charging or discharging of the battery based on the determined final target SOC. The battery control device 160 can first determine an increase in the target state of charge (SOC) based on the vehicle's state. In this case, the battery control device 160 can determine an increase in the target SOC based on the smallest value obtained by subtracting the current SOC from a fully charged state (e.g., 100%) and a request SOC at the time of the control update. In the disclosure, the request SOC can mean the SOC that is requested to update the control. For example, the battery control device 160 can calculate the request SOC by applying a load current consumption, a battery capacity and a remaining update time to the following equation 1. In equation 1, the remaining update time is the sum of a remaining update time and a rollback time, and the remaining update time can be derived from equation 2. Once the target SOC increase amount is determined, the battery control device 160 can determine the final target SOC by applying the previously determined target SOC increase amount to a target SOC based on a generation control. In this case, the battery control device 160 can determine the final target SOC differently depending on whether a navigation destination is set or whether a previous update has been approved. As an example, the battery control device 160 can calculate an initial target SOC by adding the previously determined target SOC increase to the target SOC based on a generation control. In this case, if no destination setting information is available and the previous update for the control is approved, the battery control device 160 can determine the initial target SOC as the final target SOC. One embodiment for calculating the initial target SOC can refer to Equation 3. If the final target SOC is set to the initial target SOC, a change in SOC during a single drive cycle can be illustrated as in Fig. 3A. Referring to Fig. 3A, the generation control-based target SOC during a single drive cycle is A%, as shown in the graph referenced by 311, while the final target SOC upon the occurrence of a control update event during the single drive cycle can be B%, since the generation control-based target SOC A% increases by the target SOC increase amount, as indicated by 321. The battery control device 160 can also set the target state of charge (SOC) increase rate according to a trip time and an estimated trip time, and calculate a second target SOC based on a value obtained by adding the set target SOC increase rate to the target SOC based on a generation control. In this case, if destination setting information is available and the previous update for the control is approved, the battery control device 160 can determine the second target SOC as the final target SOC. One embodiment for calculating the second target SOC can refer to Equation 4. If the final target SOC is set to the second target SOC, a change in SOC during a single drive cycle can be illustrated as in Fig. 3B. With respect to Fig. 3B, the generation control-based target SOC during a single drive cycle is A%, as shown in the graph referenced by 311. If a control update event occurs, the final target SOC during the single drive cycle can gradually increase from the generation control-based target SOC A% according to the drive time and estimated drive time, as indicated by 331. In this case, if the amount of data to be updated is small, the maximum SOC can decrease from B% to C%, as indicated by 333.If the estimated travel time is short, the SOC also increases quickly and the time required to reach the maximum SOC B% can be reduced, as indicated by reference number 335. The battery control device 160 can also set the increase rate of the target state of charge (SOC) according to the number of driving cycles and the number of control steps required to restore the SOC, and calculate a third target SOC based on a value obtained by adding the set increase rate of the target SOC to the target SOC based on generation control. In this case, if approval of the previous update for vehicle control is rejected, the battery control device 160 can determine the third target SOC as the final target SOC. In this case, the third target SOC can decrease gradually as the number of driving cycles (DC counter) increases. One embodiment for calculating the third target SOC can refer to Equation 5. If the approval of the previous update is rejected, the battery control device 160 can determine that there is no intention to update and can gradually decrease the SOC, which was previously increasing, to improve fuel efficiency. If the update approval is rejected, the change in SOC can be displayed in the next driving cycle, as shown in Fig. 3C. Referring to Fig. 3C, the final SOC is B% when the target SOC is set from reference 311 to reference 331 for downloading the update data in the previous cycle. Therefore, the SOC will be B% at the time a second driving cycle is initiated. If the approval of the previous update is rejected, the SOC, which has increased to B%, may gradually decrease by D% for each cycle, as indicated by references 341 and 351. The control device 110 can output a message to the display to request permission to download the update data when an update event occurs. In this case, one embodiment for outputting a message to the display can refer to Fig. 5A. A user can select whether to approve or reject a download by means of a message 511 displayed on the screen. Once the download of the update data has been approved, the battery control unit 160 can determine the final target SOC by setting the vehicle's target SOC to the first target SOC, the second target SOC, or the third target SOC, depending on whether a navigation destination has been set and whether the approval of the previous update has been completed. In this case, once the final target SOC has been determined, the battery control device 160 can control the charging or discharging of the battery based on the determined final target SOC. On the other hand, the battery control device 160 can maintain a previously set target SOC if no update event occurs or if the user rejects the download authorization. The control device 110 can download the vehicle control update data from the update server 200 while the battery charging or discharging is controlled by the battery control device 160. In this case, the control device 110 can output a message to the display indicating that the battery is being charged according to the set target state of charge (SOC), as well as the data download status. One embodiment for outputting a message to the display can be found in Fig. 5B. Therefore, the user can identify the download and charging statuses via a message 521 in Fig. 5B. When the vehicle's ignition is switched off, the control unit 110 can determine whether downloaded update data is available. If the downloaded update data is available, the control unit 110 can output a message to the display to request whether a corresponding control unit needs to be updated. In this case, one embodiment for outputting a message to the display can refer to Fig. 5C. A user can select, via a message 531 displayed on the screen, whether to approve (execute) or reject an update of the corresponding control. If the user rejects the update, the control device 110 can also issue a guidance message 541 as shown in Fig. 5D. If the update of the relevant controller is approved, the control device 110 can command the execution of an update while the downloaded update data is transferred to the relevant controller. Therefore, the relevant controller can update its software according to the command from the control device 110. The device 100 according to the present embodiment, which operates in the manner described above, can be implemented in the form of an independent hardware device containing a memory and a processor for handling each operation, and can be implemented in the form contained in other hardware devices, such as a microprocessor or a general-purpose computer system. Fig. 4 illustrates a change in SOC at the time of download and update when a final target SOC is corrected upwards according to a vehicle condition. If the target SOC is set to the SOC based on a generation control system, as specified by reference 411, charged energy can be used with respect to Fig. 4 while update data is being downloaded, and the control system can be updated using the remaining energy even in the state where the vehicle's ignition is off. In this case, the energy charged in an electrical load does not remain as much as the minimum energy required for ignition during the control system update, such as a range P, and the vehicle cannot be started. The update control unit 100 of the vehicle control unit of this disclosure can adjust the target state of charge (SOC) upwards according to the vehicle's condition or the amount of data available at the time the control unit's update data is downloaded. Therefore, the minimum energy required for ignition remains the same even after the update, as specified by reference 421. This ensures the vehicle's ignition performance after the vehicle control unit update, while maintaining the fuel efficiency at the time of the download. A schedule of operations for the facility as described in the present disclosure, configured as above, is detailed below. Figures 6 and 7 illustrate flowcharts of an update control procedure for a vehicle control unit according to an embodiment of the present disclosure. In the disclosure, Figure 6 illustrates a flowchart that demonstrates the operation of downloading the update data of a vehicle control unit. Figure 7 illustrates a flowchart that demonstrates the operation of updating a control unit after the ignition of a vehicle is switched off. With reference to Fig. 6 and Fig. 7, when the vehicle ignition is switched on (S110), the update control unit can identify (S120) information about the version of a software (S / W) of an in-vehicle control from the update server and determine (S130) whether an update event is occurring. If it is determined that no update event occurs at S130, the update control unit can operate the vehicle while maintaining a previous target SOC (S240). When S130 determines that the update event occurs, the update control unit can determine whether a download is approved by a user (S140). If the user rejects the download authorization in step S140, the update control unit can operate the vehicle while maintaining the previous target SOC (S240). Once the user has approved the download in step S140, the update control unit can identify the vehicle's state by gathering vehicle state information (S150) and calculate a target SOC increase based on that state (S160). Specific implementations for calculating the target SOC increase can be found in [Equation 1] and [Equation 2]. The update control unit can then determine whether an authorization is rejected at the time of the previous update for a corresponding control (S170). If step S170 determines that the authorization is rejected at the time of the previous update for the corresponding control, the update control unit can set a target SOC to the third target SOC and suspend a relevant operation. If step S170 determines that the authorization for the corresponding controller will not be rejected at the time of the previous update, the update controller can set the target SOC to either the first target SOC or the second target SOC. In this case, the update controller can set the target SOC to the first target SOC (S180 and S190) if no destination information is available, and to the second target SOC if destination information is available (S180 and S200). Specific embodiments for calculating the first to third target SOC can refer to [Equation 3] to [Equation 5]. If the final target SOC is set in step S190 or S200, the update control unit can begin downloading the update data (S210). Once the download is complete (S220), the update control unit can terminate the update data download operation. On the other hand, the update control unit may terminate the operation with respect to the downloading of the update data if there is a request to forcibly abort the download if the download is not completed (S225). If there is a request to switch to a state in which the vehicle's ignition is off (S310), the update control unit may then disable the vehicle's starting (S320). When the vehicle's ignition is off, the update control unit can determine whether the downloaded update data is available through the steps in Fig. 6 (S330). If the downloaded update data is available as a result of the determination in S330, the update control unit can request whether an update of the relevant control unit with respect to a user needs to be authorized and determine whether authorization has been completed (S340). In this case, the update control unit can update the software (S / W) of the control of a corresponding controller (S350) if the user permits the update, switch a vehicle mode to a sleep mode if the user rejects the permit (S360), and terminate an operation relating to an update. Fig. 8 illustrates a computing system in which a method according to an embodiment of the present disclosure is carried out. With reference to Fig. 8, a computing system 1000 can include at least a processor 1100, a memory 1300, a user interface input device 1400, a user interface output device 1500, a memory 1600 and / or a network interface 1700, which are interconnected via a bus 1200. The processor 1100 can be a central processing unit (CPU) or a semiconductor device that processes instructions stored in memory 1300 and / or memory 1600. Memory 1300 and memory 1600 can contain various types of volatile or non-volatile storage media. For example, memory 1300 can contain ROM (Read Only Memory) 1310 and RAM (Random Access Memory) 1320. Consequently, the operations of the method or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module, in computer-executable code performed by the processor 1100, or in a combination thereof. The software module can reside on a storage medium (i.e., the memory 1300 and / or the memory 1600), such as RAM, flash memory, ROM, EPROM, EEPROM, a register, a hard disk, a removable disk, or a CD-ROM. The storage medium can be coupled to the processor 1100, and the processor 1100 can read information from and write information to the storage medium. Alternatively, the storage medium can be integrated with the processor 1100.The 1100 processor and the storage medium can be contained within an application-specific integrated circuit (ASIC). The ASIC can be located within a user terminal device. Alternatively, the 1100 processor and the storage medium can be separate components within the user terminal device. According to the present disclosure, the charging or discharging of a battery is controlled by setting the target state of charge (SOC) of the battery in order to perform the update of the vehicle control system while driving, thereby maintaining fuel efficiency at the time of data download and ensuring the ignition performance of the vehicle even after the vehicle control system has been updated. Although the present disclosure has been described above with regard to various embodiments and the accompanying drawings, the present disclosure is not limited thereto, but can be modified and altered in various ways by someone with ordinary skills in the technology to which the present disclosure belongs, without deviating from the essence and scope of the present disclosure as claimed in the following claims. Fig. 1 11 CONTROL 1 12 CONTROL 2 13 CONTROL 3 100 UPDATE CONTROL DEVICE 200 UPDATE SERVER Fig. 2 110 CONTROL DEVICE 120 INTERFACE 130 COMMUNICATION DEVICE 140 STORAGE 150 CONDITION INFORMATION COLLECTION DEVICE 160 BATTERY CONTROL DEVICE Fig. 5A 511 SHOULD FREE DOWNLOAD BE PERFORMED? Fig. 5B 521 <herunterladen>Optimal charging is carried out to prevent vehicle unloading (Fig. 5C 531).<DOWNLOAD ABGESCHLOSSEN> SHOULD AN UPDATE BE PERFORMED? Fig. 5D 541 BATTERY PLEASE CHARGE SUFFICIENTLY BEFORE UPDATE APPROVAL Fig. 8 1100 PROCESSOR 1300 MEMORY 1400 USER SURFACE INPUT DEVICE 1500 USER SURFACE OUTPUT DEVICE 1600 MEMORY 1700 NETWORK INTERFACE< / herunterladen>
Claims
Update control device (100) for a vehicle controller, comprising: a device (150) for collecting condition information, configured to collect vehicle condition information when a vehicle controller update event occurs; a battery control device (160) configured to determine an update-based final target state of charge (target SOC) based on the collected vehicle condition information and to control charging or discharging of a battery based on the determined final target SOC; and a control device (110) configured to download vehicle controller update data from an update server (200) and update the vehicle controller, wherein the battery control device (160) increases a target SOC based on a lower value of a value.which is obtained by subtracting a current SOC from a fully charged state, and determines a request SOC at the time of the vehicle control update, wherein the battery control device (160) determines the final target SOC by applying the target SOC increase amount based on whether navigation setting information is set and whether a previous update is approved, and wherein the battery control device (160) determines the final target SOC based on a value obtained by adding the target SOC increase amount to a generation control-based target SOC when navigation setting information is not available and the previous update is approved for the vehicle control. Update control device (100) according to claim 1, wherein the vehicle status information includes at least SOC information of the battery, navigation setting information and / or information about an estimated driving time. Update control device (100) according to claim 1, wherein the battery control device (160) determines the request SOC based on at least one load current consumption, one battery capacity, one quantity of update data, one rollback data and / or one data transmission rate. Update control device (100) according to claim 1, wherein the control device (110) determines whether the update event occurs by identifying software version information of the vehicle control from the update server (200). Update control device (100) according to claim 4, wherein the control device (110) issues a message requesting whether the update data is to be downloaded at the time of the occurrence of the update event. Update control device (100) according to claim 5, wherein the battery control device (160) sets the target SOC of the vehicle to the specified final target SOC when the approval of the download of the update data is completed. Update control device (100) according to claim 1, wherein the control device (110) outputs a message requesting whether an update of the vehicle control is approved at a time when the ignition of the vehicle is switched off. Update control device (100) according to claim 7, wherein the control device (110) updates the vehicle control when an approval of the update of the vehicle control is completed, and switches an operating mode of the vehicle to a sleep mode when the approval of the update of the vehicle control is rejected. Update control procedure for a vehicle controller, comprising: collecting vehicle state information when a vehicle controller update event occurs; determining an update-based final target state of charge (target SOC) based on the collected vehicle state information and controlling a battery charge or discharge based on the determined final target SOC; downloading vehicle controller update data;and updating the vehicle control, wherein controlling the charging or discharging of the battery includes determining a final target SOC by applying an increase amount in a target SOC based on whether navigation setting information is set and whether a previous update is approved; determining the final target SOC by applying the increase amount of the target SOC depending on whether navigation setting information is set and whether a previous update is approved for the vehicle control. Update control method according to claim 9, wherein controlling the charging or discharging of the battery includes: determining the increase amount of a target SOC based on a minimum value of a value obtained by subtracting a current SOC from a fully charged state and a request SOC at the time of an update of the vehicle control. Update control method according to claim 9, further comprising: Determining whether the update event occurs by identifying software version information of the vehicle control unit from an update server (200). Update control method according to claim 9, wherein controlling the charging or discharging of the battery includes requesting whether to approve a download of the update data when the update event occurs, and setting a target SOC of the vehicle to the specified final target SOC when approval of the download of the update data is completed. Update control method according to claim 9, wherein updating the vehicle control includes requesting whether to approve an update of the vehicle control when the vehicle ignition is switched off, and updating the vehicle control when approval of the update of the vehicle control has been completed. Update control method according to claim 13, further comprising: switching an operating mode of the vehicle into a sleep mode when the approval of the update of the vehicle control is rejected. Vehicle system comprising: an update server (200) configured to provide update data to a vehicle controller; and an update control unit (100) configured to determine an update-based final target state of charge (target SOC) based on vehicle state information upon the occurrence of a vehicle controller update event, control charging or discharging of a battery based on the determined final target SOC, download vehicle controller update data from the update server (200), and update the vehicle controller, wherein the update control unit (100) determines the final target SOC by applying an increase in a target SOC based on whether navigation setting information is set and whether a previous update was approved.and wherein the update control unit (100) determines the final target SOC based on a value obtained by adding the increase quantity in the target SOC to a generation control-based target SOC when the navigation setting information is unavailable and the previous update for vehicle control is approved. Update control device (100) for a vehicle control system, wherein the update control device (100) comprises: a processor; a non-transitory memory (140) coupled to the processor; and computer-executable code stored in the non-transitory memory (140) and executable by the processor to cause the processor to: collect vehicle state information when a vehicle control system update event occurs; determine an update-based final target state of charge (target SOC) based on the collected vehicle state information and control the charging or discharging of a battery based on the determined final target SOC;and downloads vehicle control update data from an update server (200) and updates the vehicle control, whereby the final target SOC is determined by applying an increment amount in a target SOC based on whether navigation setting information is set and whether the update is approved for the vehicle control, and wherein the final target SOC is determined based on a value obtained by adding the increment amount in the target SOC to a generation control-based target SOC when the navigation setting information is not present and the update is approved for the vehicle control.;
Citation Information
Patent Citations
System and procedure for preparing a vehicle for a remote reflash event
DE102014115943A1
Vehicle, energy management system and method for preparation for vehicle battery charging for post-travel power generation
DE102016102507A1
METHOD AND SYSTEM FOR DOWNLOADING AND INSTALLING A REMOTE SOFTWARE UPDATE ON A VEHICLE
DE102017107744A1
Apparatus for updating software of vehicle and method thereof
KR1020130014885A
Battery charge amount increase facility information provision device and method
US20120078553A1