Update management apparatus of car and operating method of the same, car

Abstract

An update management device for a vehicle according to one embodiment disclosed in this document may include a memory comprising a first memory bank and a second memory bank provided to perform different operations related to the software of the vehicle, and a controller capable of determining whether to perform an update of the software and setting the operations performed by the first memory bank and the second memory bank based on the determination result.

Description

Technology Field

[0001] The embodiments disclosed in this document relate to an update management device for a vehicle, a method of operation thereof, and a vehicle. Background Technology

[0002] Driven by the rapid advancement of automotive technologies, recently released vehicles are equipped with dozens of controllers to manage various electronic functions, such as ABS, EPS, and ADAS. As the ability to continuously manage the installed software is crucial for the maintenance and management of each controller, software update technologies via OTA (Over The Air) are being developed to respond quickly and continuously to bugs, defects, and changing laws and regulations.

[0003] For software updates via OTA, free space is required in the controller's memory. However, since OTA software updates for controllers occur infrequently—approximately twice a year—over-specification of the controller's memory for these updates should be avoided. In other words, the controller's memory for OTA software updates must be used efficiently. The problem to be solved

[0004] One objective of the embodiments disclosed in this document is to provide an update management device for a vehicle for efficient memory usage when updating software installed in a controller.

[0005] The technical problems of the embodiments disclosed in this document 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

[0006] An update management device for a vehicle according to one embodiment disclosed in this document may include a memory comprising a first memory bank and a second memory bank provided to perform different operations related to the software of the vehicle, and a controller capable of determining whether to perform an update of the software and setting the operations performed by the first memory bank and the second memory bank based on the determination result.

[0007] In one embodiment, the first memory bank may store the first software, and the second memory bank may store the second software.

[0008] In one embodiment, when the controller performs the update, it may set the first memory bank to perform an update operation of the first software and set the second memory bank to perform an execution operation of the second software.

[0009] In one embodiment, the controller may transmit an update readiness signal to the server when the operation of the first memory bank and the second memory bank is set.

[0010] In one embodiment, the controller may configure the first memory bank to perform an update operation of the first software based on information regarding the update of the software obtained from the server.

[0011] In one embodiment, the controller may set the first memory bank to perform the execution operation of the first software when the update is completed.

[0012] In one embodiment, the controller may set the first memory bank to perform the execution operation of the first software when the update is not performed.

[0013] In one embodiment, the controller can increase the size of the first memory bank based on the number of updates of the software.

[0014] In one embodiment, the controller can manage the size of the second memory bank as a fixed size.

[0015] A method of operation of an update device for a vehicle according to one embodiment disclosed in this document may include a step of determining whether to perform a software update and a step of setting an operation performed by a first memory bank and a second memory bank based on whether to perform a software update.

[0016] In one embodiment, the first memory bank may store the first software, and the second memory bank may store the second software.

[0017] In one embodiment, the step of setting the operation performed by the first memory bank and the second memory bank based on whether the software update is performed may include the step of setting the second memory bank to perform the execution operation of the second software and the step of setting the first memory bank to perform the update operation of the first software.

[0018] In one embodiment, when the update is completed, the method may further include the step of setting the first memory bank to perform the first software execution operation.

[0019] In one embodiment, the step of setting the first memory bank to perform an update operation of the first software may further include the step of transmitting an update readiness signal to a server when the operation of the first memory bank and the second memory bank is set, the step of obtaining information regarding the update of the software from the server, and the step of setting the first memory bank to perform an update operation of the first software based on the information regarding the update of the software.

[0020] A vehicle according to one embodiment disclosed in this document may include a modem capable of obtaining information regarding an update of software installed on at least one controller from an OTA (Over The Air) server, and at least one controller capable of communicating with said modem, determining whether to perform an update of said software, and setting operations performed by a first memory bank and a second memory bank based on the determination result.

[0021] In one embodiment, the at least one controller may store a first software in the first memory bank and a second software in the second memory bank.

[0022] In one embodiment, when the at least one controller performs the update, the first memory bank may be configured to perform an update operation of the first software, and the second memory bank may be configured to perform an execution operation of the second software.

[0023] In one embodiment, the at least one controller may configure the first memory bank to perform an update operation of the first software based on information regarding the update of the software obtained from the modem.

[0024] In one embodiment, the at least one controller may set the first memory bank to perform an execution operation of the first software when the update is completed.

[0025] In one embodiment, the at least one controller may set the first memory bank to perform the execution operation of the first software when the update is not performed. Effects of the invention

[0026] An update management device for a vehicle according to one embodiment disclosed in this document can efficiently use the memory of the controller when performing an update of software installed in the vehicle controller. Brief explanation of the drawing

[0027] FIG. 1 is a block diagram showing an update management device for a vehicle according to one embodiment disclosed in this document. FIG. 2 is a conceptual diagram of a first memory bank and a second memory bank of an update management device of a vehicle according to one embodiment disclosed in this document. FIGS. 3 and 4 are flowcharts showing the operation method of an update management device for a vehicle according to one embodiment disclosed in this document. FIG. 5 is a flowchart specifically showing the step of setting a first memory bank to perform an update operation of the first software in a method of operation of an update management device of a vehicle according to one embodiment disclosed in this document. FIG. 6 is a drawing showing a vehicle according to one embodiment disclosed in this document. Specific details for implementing the invention

[0028] The embodiments disclosed in this document are described in detail below 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 disclosed in this document, detailed descriptions of related known configurations or functions are omitted if it is determined that such detailed descriptions would hinder understanding of the embodiments disclosed in this document.

[0029] In describing the components of the embodiments disclosed in this document, terms such as first, second, A, B, (a), (b), etc., may be used. These terms are intended only to distinguish the components from other components and do not limit the essence, order, or sequence of the components. 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 embodiments disclosed in this document belong. 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.

[0030] FIG. 1 is a block diagram showing an update management device for a vehicle according to one embodiment disclosed in this document.

[0031] Referring to FIG. 1, an update management device (100) of a vehicle according to one embodiment disclosed in this document may include a memory (110) and a controller (120).

[0032] The memory (110) may include a first memory bank (111) and a second memory bank (112). The first memory bank (111) and the second memory bank (112) may be provided to perform different operations related to the software of the vehicle. For example, the first software may be stored in the first memory bank (111), and the second software may be stored in the second memory bank (112). Meanwhile, the first software and the second software may perform substantially the same function.

[0033] The controller (120) can determine whether to perform a software update. For example, the controller (120) can communicate with any one of a server, a modem, or a gateway, and can obtain whether to perform a software update from any one of the server, a modem, or a gateway. Alternatively, the controller (120) may directly determine whether to perform a software update. Meanwhile, the communication between the controller (120) and the modem or gateway in the vehicle may include either CAN (Controller Area Network) communication or Ethernet communication.

[0034] The controller (120) can set the actions performed by the first memory bank (111) and the second memory bank (112) based on the result of determining whether to perform an update. For example, when the controller (120) performs an update of the software, it can set the first memory bank (111) to perform the update action of the first software and set the second memory bank (112) to perform the execution action of the second software.

[0035] Meanwhile, if the controller (120) does not perform a software update, it may set the first memory bank (111) to perform the execution operation of the first software and set the second memory bank (112) to perform a standby operation.

[0036] The controller (120) can transmit an update readiness signal to the server when the operation of the first memory bank (111) and the second memory bank (112) is configured. For example, the controller (120) can transmit an update readiness signal to the server when the first memory bank (111) is configured to perform an update operation of the first software and the second memory bank (112) is configured to perform an execution operation of the second software. Here, the server may include an OTA (Over The Air) update server. Additionally, the controller (120) can transmit the update readiness signal to the server directly or indirectly through a modem or gateway within the vehicle.

[0037] The controller (120) can configure the first memory bank (111) to perform an update operation of the first software based on information regarding the update of the software obtained from the server. For example, the controller (120) can configure the first memory bank (111) to perform an update operation of the first software based on information regarding the update of the software by downloading information regarding the update of the software to the first memory bank (111), decompressing it, and updating the first software.

[0038] Meanwhile, the controller (120) can obtain information regarding software updates directly from the server or indirectly through the vehicle's gateway or modem.

[0039] The controller (120) may set the first memory bank (111) to perform the execution operation of the first software when the update is completed. For example, when the update of the first software in the first memory bank (111) is completed, the controller (120) may set the first memory bank (111) to perform the execution operation of the first software for which the update is completed. At this time, the controller (120) may set the second memory bank (112) to perform a standby operation.

[0040] That is, the controller (120) can set the second memory bank (112) to perform the execution operation of the second software when an update is performed, and can set the second memory bank (112) to perform a standby operation when an update is not performed or when the update is completed. Additionally, the controller (120) can set the first memory bank (111) to perform the update operation of the first software when an update is performed, and can set the first memory bank (111) to perform the execution operation of the first software when an update is not performed or when the update is completed. In conclusion, the vehicle update management device (100) can execute the second software only when a software update is performed, and can execute the first software when a software update is not performed or when a software update is completed.

[0041] Meanwhile, the controller (120) can increase the size of the first memory bank (111) based on the number of software updates. For example, the controller (120) can cumulatively increase the size of the first memory bank (111) as the number of software updates accumulates. That is, the controller (120) can increase the size of the first memory bank (111) so that the first software updates can be continuously updated.

[0042] The controller (120) can manage the size of the second memory bank (112) as a fixed size. For example, the controller (120) can set the size of the second memory bank (112) to correspond to the size of the second software that was initially set, and since the second software is not updated, the size of the second software does not change, so the size of the second memory bank (112) can be fixed.

[0043] The vehicle update management device (100) can perform software updates through the operation of the first memory bank (111), the second memory bank (112) included in the memory (110), and the controller (120). For example, when the controller (120) determines that an update is to be performed, it can set the first memory bank (111) to perform the update operation of the first software and set the second memory bank (112) to perform the execution operation of the second software, send an update readiness signal to the server, obtain information regarding the software update from the server, and set the first memory bank (111) to perform the update operation of the first software based on the obtained information regarding the software update. Additionally, the controller (120) can set the first memory bank (111) to perform the execution operation of the first software when the update is completed or when the update is not performed. Accordingly, the vehicle update management device (100) can efficiently use the memory (110) space because the size of the second memory bank (112) can be fixed to the size of the second software, and only the size of the first memory bank (111) increases based on the number of updates. That is, the vehicle update management device (100) can efficiently use the space of the memory (110) so that the space where software is not stored can be set to perform other functions.

[0044] Below, with reference to FIG. 2, we will examine the operation of the first memory bank (111) and the second memory bank (112) during a software update.

[0045] FIG. 2 is a conceptual diagram of a first memory bank and a second memory bank of an update management device of a vehicle according to one embodiment disclosed in this document.

[0046] Referring to FIG. 2, when the software update is not performed, the first memory bank (111) may be set to perform the execution operation of the first software, and the second memory bank (112) may be set to perform the standby operation.

[0047] During the performance of software updates, the first memory bank (111) may be configured to perform the update operation of the first software, and the second memory bank (112) may be configured to perform the execution operation of the second software.

[0048] After the software update is completed, the first memory bank (111) can be set to perform the execution operation of the first software again, and the second memory bank (112) can be set to perform a standby operation. In conclusion, the first memory bank (111) can perform the operation of executing the first software after the update of the first software is performed, and the second memory bank (112) can perform the operation of executing the second software only while the software update is performed.

[0049] That is, after the software update is completed, the size of the first software installed in the first memory bank (111) can be increased, and the size of the second software installed in the second memory bank (112) can be maintained.

[0050] The operation method of the vehicle update management device (100) will be specifically described below with reference to FIGS. 3 and FIGS. 4.

[0051] FIGS. 3 and 4 are flowcharts showing the operation method of an update management device for a vehicle according to one embodiment disclosed in this document.

[0052] Referring to FIG. 3, the method of operation of the update management device (100) of a vehicle may include a step (S100) of determining whether to perform a software update and a step (S200) of setting the operation performed by the first memory bank and the second memory bank based on whether to perform a software update.

[0053] The following is a detailed explanation with reference to Fig. 1.

[0054] In the step (S100) of determining whether to perform a software update, the controller (120) can determine whether to perform an update of the first software stored in the first memory bank (111). For example, in step S100, the controller (120) may directly determine whether to perform a software update, or may obtain information regarding whether to perform an update from a server outside the vehicle, a modem inside the vehicle, or a gateway.

[0055] Meanwhile, the first memory bank (111) may store the first software, and the second memory bank (112) may store the second software.

[0056] In the step (S200) of setting the actions performed by the first memory bank and the second memory bank based on whether an update of the software is performed, the controller (120) can set the actions performed by the first memory bank (111) and the second memory bank (112). For example, in the step S200, if an update is not performed, the controller (120) can set the first memory bank (111) to perform the execution action of the first software and set the second memory bank (112) to perform a standby action.

[0057] In step S200, the controller (120) can set the first memory bank (111) to perform an update operation of the first software when an update is performed, and can set the second memory bank (112) to perform an execution operation of the second software. Additionally, when the update is completed, the controller (120) can set the first memory bank (111) to perform an execution operation of the first software.

[0058] Step S200 will be explained in detail below with reference to FIG. 4.

[0059] Referring to FIG. 4, the operation method of the vehicle update management device (100) may include a step of determining whether to perform a software update (S110), a step of setting a second memory bank to perform an execution operation of the second software (S210), a step of setting a first memory bank to perform an update operation of the first software (S220), and a step of setting the first memory bank to perform an execution operation of the first software when the update is completed (S230).

[0060] In the step (S110) of determining whether to perform a software update, the controller (120) can determine whether to perform an update of the first software of the first memory bank (111), and if it is determined that the update is not performed, the process can be terminated. At this time, the step S110 may be substantially the same as the step S100 in FIG. 2.

[0061] In the step (S210) of setting the second memory bank to perform the execution operation of the second software, the controller (120) may set the second memory bank (112) to perform the execution operation of the second software when performing a software update. For example, the update management device (100) may execute the second software while the update is being performed.

[0062] In the step (S220) of setting the first memory bank to perform an update operation of the first software, the controller (120) can set the first memory bank (111) to perform an update operation of the first software.

[0063] In the step (S230) of setting the first memory bank to perform the execution operation of the first software when the update is completed, the controller (120) may set the first memory bank (111) to perform the execution operation of the first software when the update is completed, and may set the second memory bank (112) to perform a standby operation.

[0064] Meanwhile, in FIG. 3, step S200 may include steps S210 to S230.

[0065] Step S220 will be explained in detail below with reference to FIG. 5.

[0066] FIG. 5 is a flowchart specifically showing the step of setting a first memory bank to perform an update operation of the first software in a method of operation of an update management device of a vehicle according to one embodiment disclosed in this document.

[0067] Referring to FIG. 5, the step of setting the first memory bank to perform an update operation of the first software (S220) may include the step of transmitting an update readiness signal to the server when the operation of the first memory bank and the second memory bank is set (S221), the step of obtaining information regarding the update of the software from the server (S222), and the step of setting the first memory bank to perform an update operation of the first software based on the information regarding the update of the software (S223).

[0068] In the step (S221) of transmitting an update readiness signal to the server when the operation of the first memory bank and the second memory bank is set, the controller (120) may transmit an update readiness signal to the server when the operation of the first memory bank (111) and the second memory bank (112) is set. For example, the controller (120) may transmit an update readiness signal to the server when the first memory bank (111) is set to perform an update operation of the first software and the second memory bank (112) is set to perform an execution operation of the second software. Meanwhile, the controller (120) may transmit the update readiness signal to the server directly or indirectly through a modem or gateway.

[0069] In the step (S222) of obtaining information regarding software updates from a server, the controller (120) may obtain information regarding software updates from the server to perform the update. For example, the information regarding software updates may include at least one of the contents of the firmware, the software version, and the update sequence. Meanwhile, the controller (120) may obtain information regarding software updates directly from the server or indirectly through a modem or gateway.

[0070] In the step (S223) of setting the first memory bank to perform an update operation of the first software based on information regarding the update of the software, the controller (120) may set the first memory bank (111) to perform an update operation of the first software based on the acquired information regarding the update of the software. For example, the controller (120) may perform an update of the first software by downloading information regarding the update to the first memory bank (111) and decompressing it. That is, the first software may be updated based on information regarding the update of the software.

[0071] By performing the operation method of the vehicle update management device (100), the vehicle update management device (100) sets the first memory bank (111) to perform the update operation of the first software, sets the second memory bank (112) to perform the execution operation of the second software while the update is being performed, and sets the first memory bank (111) to perform the execution operation of the first software when the update is not being performed, thereby increasing the size of the first memory bank (111) while fixing the size of the second memory bank (112) to correspond to the size of the second software. That is, the vehicle update management device (100) can perform software updates by efficiently using the memory (110).

[0072] Hereinafter, a vehicle according to one embodiment disclosed in this document will be described with reference to FIG. 5.

[0073] FIG. 6 is a drawing showing a vehicle according to one embodiment disclosed in this document.

[0074] Referring to FIG. 6, a vehicle (1000) according to one embodiment disclosed in this document may include a modem (1100) and at least one controller (1200).

[0075] The modem (1100) can communicate with an OTA (Over The Air) server and obtain information regarding updates to software installed on at least one controller (1200) from the OTA server. For example, information regarding updates to software installed on at least one controller (1200) may include at least one of a CAN (Controller Area Network) ID, firmware content, software version, and update sequence.

[0076] At least one controller (1200) may include a first controller (1210). Although FIG. 6 is illustrated as including only the first controller (1210), it is not limited thereto. At least one controller (1200) may be configured to include n controllers (where n is a natural number greater than or equal to 2).

[0077] At least one controller (1200) can communicate with the modem (1100). For example, at least one controller (1200) can communicate with the modem (1100) via CAN communication or Ethernet communication. Meanwhile, at least one controller (1200) may be substantially the same as the vehicle update management device (100) described above in FIG. 1. That is, at least one controller (1200) may include a memory (110) including a first memory bank (111) and a second memory bank (112), and a controller (120).

[0078] At least one controller (1200) can determine whether to perform a software update and, based on the result of the determination, set the operation to be performed by the first memory bank (111) and the second memory bank (112). For example, the first software may be stored in the first memory bank (111), and the second software may be stored in the second memory bank (112).

[0079] At least one controller (1200) can set the first memory bank (111) to perform the execution operation of the first software and set the second memory bank (112) to perform the standby operation when the software update is not performed.

[0080] At least one controller (1200) can set the operations performed by the first memory bank (111) and the second memory bank (112) when a software update is performed. For example, at least one controller (1200) can set the first memory bank (111) to perform the first software update operation and the second memory bank (112) to perform the second software execution operation when a software update is performed.

[0081] Additionally, at least one controller (1200) can transmit an update readiness signal to a modem (1100) or server when the operation performed by the first memory bank (111) and the second memory bank (112) is set, and can obtain information regarding the software update from the modem (1100) or server.

[0082] At least one controller (1200) can set the first memory bank (111) to perform an execution operation of the first software that has been updated when the update is completed, and set the second memory bank (112) to perform a standby operation.

[0083] At least one controller (1200) inside the vehicle (1000) can perform an update of the first software stored in the first memory bank (111) by setting the operation performed by the first memory bank (111) and the second memory bank (112) when performing a software update, and can execute the second software stored in the second memory bank (112) only while performing the update, and thus, since the second software is not updated, the memory (110) space can be used efficiently to enable the software update.

[0084] In another embodiment disclosed in this document, at least one controller (1200) inside a vehicle (1000) may utilize the memory (110) space that is not used for software updates as a new function or design space for at least one controller (1200) by performing a software update method that efficiently uses the memory (110) space.

[0085] The above description is merely an illustrative explanation of the technical concept disclosed in this document, and a person skilled in the art to which the embodiments disclosed in this document belong may make various modifications and variations within the scope of the essential characteristics of the embodiments disclosed in this document.

[0086] Accordingly, the embodiments disclosed in this document are intended to illustrate, not limit, the technical concept disclosed in this document, and the scope of the technical concept disclosed in this document is not limited by these embodiments. The scope of protection of the technical concept disclosed in this document 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 document. Explanation of the symbols

[0087] 100: Vehicle update management device 110: Memory 111: 1st Memory Bank 112: Second Memory Bank 120: Controller 1000: Vehicle 1100: Modem 1200: At least one controller 1210: 1st controller

Claims

Claim 1 A vehicle update management device comprising: a memory including a first memory bank and a second memory bank provided to perform different operations related to software of a vehicle; and a controller that determines whether to perform an update of said software and sets the operations performed by said first memory bank and said second memory bank based on the determination result, wherein the controller increases the size of said first memory bank based on the number of updates of said software and manages the size of said second memory bank as a fixed size. Claim 2 An update management device for a vehicle according to claim 1, characterized in that a first software is stored in the first memory bank and a second software is stored in the second memory bank. Claim 3 An update management device for a vehicle according to claim 2, wherein, when performing the update, the controller sets the first memory bank to perform an update operation of the first software and sets the second memory bank to perform an execution operation of the second software. Claim 4 An update management device for a vehicle according to claim 3, wherein the controller transmits an update readiness signal to a server when the operation of the first memory bank and the second memory bank is set. Claim 5 An update management device for a vehicle according to claim 3, wherein the controller sets the first memory bank to perform an update operation of the first software based on information regarding the update of the software obtained from a server. Claim 6 An update management device for a vehicle according to claim 5, wherein the controller sets the first memory bank to perform the execution operation of the first software when the update is completed. Claim 7 An update management device for a vehicle according to claim 2, characterized in that the controller sets the first memory bank to perform the execution operation of the first software when the update is not performed. Claim 8 delete Claim 9 delete Claim 10 A method of operation of an update management device for a vehicle, comprising: a step of determining whether to perform a software update; and a step of setting operations performed by a first memory bank and a second memory bank based on whether to perform a software update; wherein the method further comprises the step of increasing the size of the first memory bank based on the number of software updates and managing the size of the second memory bank as a fixed size. Claim 11 A method of operation of an update management device for a vehicle according to claim 10, characterized in that the first software is stored in the first memory bank and the second software is stored in the second memory bank. Claim 12 A method of operation of an update management device for a vehicle, characterized in that, in claim 11, the step of setting the operation performed by the first memory bank and the second memory bank based on whether the software update is performed comprises: the step of setting the second memory bank to perform the execution operation of the second software; and the step of setting the first memory bank to perform the update operation of the first software. Claim 13 A method of operation of an update management device of a vehicle, further comprising the step of, in claim 12, setting the first memory bank to perform the first software execution operation when the update is completed. Claim 14 A method of operation of an update management device for a vehicle according to claim 12, wherein the step of setting the first memory bank to perform an update operation of the first software further comprises: a step of transmitting an update readiness signal to a server when the operation of the first memory bank and the second memory bank is set; a step of obtaining information regarding the update of the software from the server; and a step of setting the first memory bank to perform an update operation of the first software based on the information regarding the update of the software. Claim 15 A vehicle comprising: a modem that obtains information regarding an update of software installed on at least one controller from an OTA (Over The Air) server; and at least one controller that communicates with the modem, determines whether to perform an update of the software, and sets operations performed by a first memory bank and a second memory bank based on the determination result, wherein the controller increases the size of the first memory bank based on the number of software updates and manages the size of the second memory bank as a fixed size. Claim 16 A vehicle according to claim 15, wherein the at least one controller stores a first software in the first memory bank and stores a second software in the second memory bank. Claim 17 A vehicle according to claim 16, wherein, when performing the update, the at least one controller is configured to set the first memory bank to perform an update operation of the first software and to set the second memory bank to perform an execution operation of the second software. Claim 18 A vehicle according to claim 17, wherein the at least one controller sets the first memory bank to perform an update operation of the first software based on information regarding the update of the software obtained from the modem. Claim 19 A vehicle according to claim 18, wherein the at least one controller sets the first memory bank to perform an execution operation of the first software when the update is completed. Claim 20 A vehicle according to claim 16, wherein the at least one controller is configured to set the first memory bank to perform the execution operation of the first software when the update is not performed.

Images