Systems, vehicles and methods

Abstract

To provide a system, a vehicle, and a method capable of identifying and determining whether a battery newly installed in a moving vehicle is a dedicated battery or a non-dedicated battery.SOLUTION: An OTA (Over-The-Air) system for updating software of an on-vehicle device ECU 100 installed in a vehicle based on information received from outside the vehicle includes: a detection unit for detecting that a target device to be controlled by the on-vehicle device is changed; a selection and control unit for performing control to select model information of a new battery when the detection unit detects that the battery to be controlled by the on-vehicle device is replaced with a new battery; a reception unit for receiving control data for controlling the new battery from a server external to the vehicle; and an update unit for updating the software of the on-vehicle device so that the new battery is controlled based on the control data.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a system, a vehicle and a method. [Background technology]

[0002] Patent Document 1 discloses a method for identifying whether a battery newly installed in an automobile is a dedicated battery or a non-dedicated battery. [Prior art document] [Patent documents] Patent Document 1: JP 2014-146494 A Summary of the Invention [Problem to be solved by the invention]

[0003] However, when a vehicle battery is replaced with a new one, it is necessary to prevent the new battery from being controlled differently than expected. The present application aims to solve the above problem by improving the marketability of batteries. This will ultimately contribute to the development of a sustainable transportation system by further improving traffic safety and the lifespan of consumables. [Means for solving the problem]

[0004] In a first aspect of the present invention, there is provided a system. The system is an OTA (Over-The-Air) system for updating software of an in-vehicle device provided in the vehicle based on information received from outside the vehicle. The system includes a detection unit that detects that a control target device controlled by the in-vehicle device has been changed. The system includes a selection control unit that, when the detection unit detects that a battery controlled by the in-vehicle device has been replaced with a new battery, performs control to select model information of the new battery. The system includes a receiving unit that receives control data for controlling the new battery from a server external to the vehicle. The system includes an update unit that updates the software of the in-vehicle device so that the new battery is controlled based on the control data.

[0005] The selection control unit may allow a user to select the model information using a user terminal associated with the vehicle.

[0006] The selection control unit may select the model information based on information obtained from the new battery via a power line, or may select the model information based on information generated when a key unit provided on the battery connection terminal matches a key unit provided on the connection terminal of the new battery.

[0007] The update unit may prioritize updating the software of the in-vehicle device over turning on the ignition power after the ignition power of the vehicle is turned off. The system may further include a notification unit that notifies the user that updating the software of the in-vehicle device has priority over turning on the ignition power after the ignition power of the vehicle is turned off.

[0008] The system may further include a change unit that changes, in accordance with the new battery, the time during which information related to the software update can be communicated with the server while the ignition power of the vehicle is turned off.

[0009] The system may further include a notification unit that, if it is determined based on the model information that the new battery is a battery of a model unknown to the vehicle, notifies the vehicle that the battery is an unknown model before performing a software update of the on-board equipment.

[0010] The vehicle may be capable of restarting an engine provided by the vehicle from an idle stop state in which the engine is stopped by using power supplied from the battery. When the update unit determines that the new battery is a type that is not compatible with idle stop, the update unit may perform software update of the in-vehicle device to prohibit idle stop of the vehicle.

[0011] In a second aspect of the present invention, there is provided a vehicle, the vehicle comprising the system described above.

[0012] In a third aspect of the present invention, there is provided a method for performing a software update of an in-vehicle device provided in the vehicle via OTA (Over-The-Air) based on information received from outside the vehicle. The method includes a step of detecting that a control target device controlled by the in-vehicle device has been changed. The method includes a step of performing control to select model information of the new battery when it is detected that a battery controlled by the in-vehicle device has been replaced with a new battery. The method includes a step of receiving control data for controlling the new battery from a server external to the vehicle. The method includes a step of performing a software update of the in-vehicle device so that the new battery is controlled based on the control data. The step of performing control to select model information of the new battery includes having a user select the model information using a user terminal associated with the vehicle.

[0013] The above summary of the invention does not list all of the features of the present invention, and subcombinations of these features may also constitute inventions. [Brief explanation of the drawings]

[0014] [Figure 1] 1 conceptually illustrates a usage scenario of an update system 5 according to an embodiment. [Figure 2] 2 is a block diagram illustrating a schematic functional configuration of an ECU 100. FIG. [Figure 3] 10 is a flowchart showing the flow of processing executed in the update system 5. [Figure 4] An example of a computer 2000 is shown schematically. DETAILED DESCRIPTION OF THE INVENTION

[0015] The present invention will be described below through embodiments of the invention, but the following embodiments do not limit the scope of the invention according to the claims. Furthermore, not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0016] 1 conceptually illustrates a usage scenario of an update system 5 according to an embodiment. The update system 5 includes a vehicle 10, a server 70, and a user terminal 82.

[0017] Vehicle 10 includes system 20. System 20 includes a plurality of ECUs (electronic control units) including ECU 100, ECU 110, ECU 120, and ECU 121, TCU 160, and MID 170. The ECUs included in vehicle 10 include ECUs for controlling devices that directly affect the running of vehicle 10, such as an engine, a transmission, and a steering device. The ECUs included in vehicle 10 include ECUs for controlling devices that do not directly affect the running of vehicle 10, such as an air conditioner and a navigation device. ECU 100, ECU 110, ECU 120, and ECU 121 are examples of in-vehicle devices.

[0018] The TCU 160 is a telematics control unit that is primarily responsible for mobile communications. The MID 170 is a multi-information display.

[0019] The vehicle 10 includes a plurality of ECUs, a TCU 160, and an MID 170, which communicate with each other via a controller area network (CAN) communication network or a communication network 180 conforming to the Ethernet (registered trademark) standard. The vehicle 10 includes the ECUs, the TCU 160, and the MID 170, which are communicably connected with each other via the plurality of communication networks 180. The ECU 100 may function as a gateway that relays communication between the plurality of communication networks 180. The ECU 100 may be an ECU that performs overall control of the entire system 20.

[0020] In this embodiment, the ECU 110 is an ECU that controls, for example, the battery 150. The battery 150 is provided so as to be replaceable. The battery 150 is, for example, a 12V low-voltage battery. The ECU 110 controls, for example, the charging and discharging of the battery 150. The ECU 110 detects various information such as the rated voltage of the battery 150.

[0021] When ECU 100 detects that the battery installed in vehicle 10 has been replaced with a new battery 150, ECU 100 performs control to allow a user 80 of vehicle 10 to select model information of battery 150. User 80 is a user who has been registered in advance as a user of vehicle 10.

[0022] As an example, the ECU 100 notifies the server 70 via the TCU 160 that the battery 150 has been replaced with a new battery 150, thereby requesting the server 70 to have the user 80 select the model of the battery 150. The server 70 communicates with a user terminal 82 that has been registered in advance as the user terminal used by the user 80, and notifies the user 80 to select the model of the battery 150. When the user 80 selects the model information of the battery 150 using the user terminal 82, the server 70 receives the model information of the battery 150 that has been input to the user terminal 82 from the user terminal 82.

[0023] As another method, when the battery mounted on the vehicle 10 is replaced with a new battery 150, the ECU 100 allows the user 80 to select model information of the battery 150 via the MID 170. The ECU 100 transmits the model information selected by the user 80 via the MID 170 to the server 70 via the TCU 160.

[0024] The server 70 selects update software for the ECU 110 based on the model information of the battery 150 received via the user terminal 82 or the TCU 160, and transmits the selected software to the vehicle 10. The update software is control software executed by the ECU 110 so that the ECU 110 performs control suitable for the battery 150. When the TCU 160 receives the update software transmitted from the server 70, the ECU 100 reprograms the ECU 100 by rewriting the software that controls the ECU 110 with the update software. In this manner, the system 20 reprograms the ECU 110 by updating the software of the ECU 110 over the air (OTA). In this embodiment, rewriting the software of the ECU 110 with the update software is referred to as a "software update."

[0025] 2 is a block diagram showing a schematic functional configuration of the ECU 100. The ECU 100 includes a processing unit 200 and a storage unit 280. The ECU 100 is an example of an over-the-air (OTA) system for updating software of the ECU 110 included in the vehicle 10 based on information received from outside the vehicle 10.

[0026] The processing unit 200 may be implemented by a processor such as a CPU that performs arithmetic processing. The storage unit 280 may include a non-volatile storage medium such as a flash memory, or a volatile storage medium such as a random access memory. Each ECU 100 may be configured to include a computer. The ECU 100 performs various types of control by the processing unit 200 operating in accordance with a program stored in the non-volatile storage medium.

[0027] The processing unit 200 includes a selection control unit 210 , a receiving unit 220 , an updating unit 230 , a notifying unit 240 , a changing unit 250 , and a detecting unit 260 .

[0028] The detection unit 260 detects that the control target device controlled by the ECU 110 has been changed. For example, the detection unit 260 detects that the control target device has been changed based on information notified by the ECU 110 when the detection unit 260 detects that the control target device has been changed. The selection control unit 210 performs control to select model information of the new battery 150 when the detection unit 260 detects that the battery controlled by the ECU 110 has been replaced with a new battery 150. The reception unit 220 receives control data for controlling the new battery 150 from a server external to the vehicle 10. The update unit 230 updates the software of the ECU 110 so that the new battery 150 is controlled based on the control data. This makes it possible to select model information of the new battery 150 and transmit the model information to the server 70 that provides the control data.

[0029] The selection control unit 210 may allow the user 80 to select model information using a user terminal 82 associated with the vehicle 10. The selection control unit 210 may allow the user 80 to select model information via the server 70 by notifying the server 70 that the battery has been replaced. This allows the user 80 to select the model of the battery 150 using the user terminal 82, making it possible to perform processing related to the software update while the vehicle 10 is stopped.

[0030] The selection control unit 210 may select the model information based on information acquired from the new battery 150 via the power line, or may select the model information based on information generated when a key unit provided at the battery connection terminal matches a key unit provided at the connection terminal of the new battery 150. For example, the ECU 110 may acquire the model information of the battery 150 by communicating with the battery 150 via the power line, and the selection control unit 210 may acquire the model information transmitted from the ECU 110 to the ECU 100. In another embodiment, a battery connection terminal to which the connection terminal of the battery 150 is connected may be provided with a key unit of a specific shape that engages with a key unit of a specific shape provided at a connection terminal of a specific type of battery. The ECU 110 may detect whether the battery has been replaced with a specific type by acquiring information from a sensor that detects whether the key unit of the battery connection terminal engages with the key unit of the connection terminal of the installed battery, and transmit information indicating the detection result to the ECU 100. The selection control unit 210 may acquire the model information based on information indicating the detection result transmitted from the ECU 110 to the ECU 100. A battery of a specific model may be a genuine battery for the vehicle 10. This allows the ECU 110 and the ECU 100 to automatically determine the model of the replaced battery when the battery of the vehicle 10 is replaced. In particular, when the battery is replaced with a genuine battery, the operation of the user 80 to select the model can be reduced.

[0031] After the ignition power of the vehicle 10 is turned off, the update unit 230 prioritizes updating the software of the ECU 110 over turning on the ignition power. For example, while the update unit 230 is updating the software of the ECU 110, turning on the ignition power of the vehicle 10 may be prohibited. The notification unit 240 notifies the user that after the ignition power of the vehicle 10 is turned off, updating the software of the ECU 110 is prioritized over turning on the ignition power. This allows the software update of the ECU 110 to be prioritized when the battery is replaced so that the vehicle 10 can be started properly the next time using the new battery 150.

[0032] The change unit 250 may change the time during which information related to software update can be received from the server 70 while the ignition power of the vehicle 10 is turned off, in accordance with the new battery 150. The change unit 250 may change the time during which information related to software update can be communicated with the server 70, in accordance with the battery capacity determined from model information of the new battery 150. This makes it possible to change the communication time related to software update in accordance with the model of the battery 150. For example, the smaller the battery capacity of the battery 150, the shorter the communication time related to software update can be.

[0033] When it is determined based on the model information that the new battery 150 is an unknown type of battery for the vehicle 10, the notification unit 240 notifies the user 80 that the battery is an unknown type before updating the software of the ECU 110. This makes it possible to warn the user 80 in advance about using an unknown battery in the vehicle 10 if the new battery 150 is an unknown battery. The unknown battery may be a battery that is not intended to be installed in the vehicle 10. The unknown battery may be a battery that does not meet the standards for the vehicle 10. The unknown battery may be a battery with a battery capacity that does not meet the standards for the vehicle 10.

[0034] Vehicle 10 may be able to restart the engine of vehicle 10 from an idle stop state in which the engine has stopped, using power provided from the battery. If it is determined that new battery 150 is a battery of a type that is not compatible with idle stop, update unit 230 performs software update of ECU 110 to prohibit idle stop of vehicle 10. As a result, in a vehicle that is compatible with idle stop, if the type of new battery 150 is not compatible with idle stop, idle stop can be prohibited.

[0035] 3 is a flowchart showing the flow of processing executed in the update system 5. The flowchart shown in FIG.

[0036] In S302, the ECU 110 detects that the battery has been replaced with a new battery 150. For example, the ECU 110 holds battery identification information (BIN) of the battery mounted on the vehicle 10, and the ECU 110 determines that the battery has been replaced when the BIN acquired from the battery 150 does not match the BIN held by the ECU 110. The ECU 110 may detect a dark current of the battery mounted on the vehicle 10, and determine that the battery has been replaced when the dark current is no longer detected. The ECU 110 notifies the ECU 100 that the battery has been replaced.

[0037] In S304, the selection control unit 210 notifies the server 70 that the battery of the vehicle 10 has been replaced, and thereby notifies the user terminal 82 to prompt the user 80, who has been previously associated with the vehicle 10, to select model information of the battery 150. For example, the server 70 transmits to the user terminal 82 a selection menu for the user 80 to select model information of the battery 150.

[0038] In S306, the user terminal 82 determines whether the battery 150 is genuine based on the information input by the user 80. The user terminal 82 displays a selection menu that allows the user 80 to select whether the battery 150 newly installed in the vehicle 10 by the user 80 is genuine. The user terminal 82 determines that the battery 150 is genuine if the user 80 selects through the selection menu that the battery 150 is genuine, and determines that the battery 150 is not genuine if the user 80 selects that the battery 150 is not genuine. If the battery 150 is genuine, the processing of this flowchart ends. As a result, the ECU 110 controls the battery 150 in accordance with the software that has already been installed. Genuine batteries are designated in advance for each vehicle 10 by the manufacturer of the vehicle 10. The software installed in the ECU 110 is pre-created to perform control appropriate for a genuine battery.

[0039] If non-genuine is selected in S306, then in S308, the user terminal 82 prompts the user 80 to select the model of the battery 150. For example, the user terminal 82 displays a menu listing battery manufacturers to prompt the user 80 to select the manufacturer that produced the battery 150, and once the manufacturer is selected, a menu listing battery models manufactured by the selected manufacturer is displayed to prompt the user 80 to select the model of the battery 150. Once the model is selected, in S310, the user terminal 82 transmits model information indicating the selected model to the server 70.

[0040] In S312, the server 70 selects control data and function information that are compatible with the model of the battery 150, based on the model information received from the user terminal 82. The control data is update software that includes a control program and various control data for the ECU 110 to control the battery 150.

[0041] The function information selected by the server 70 in S312 may include at least one of information indicating functions that the battery can or cannot provide to the vehicle, battery performance information, and information indicating whether the battery is non-standard for the vehicle. The server 70 may previously store correspondence information including information indicating functions that the battery can or cannot provide to the vehicle, battery performance information, and information indicating whether the battery is non-standard for the vehicle, in association with multiple battery models and multiple vehicle models. The functions that the battery can or cannot provide to the vehicle may include, for example, an idle stop function. The battery performance information may include information indicating the battery capacity and the battery's rated voltage. In S312, the server 70 may refer to the correspondence information and select function information associated with the model of the battery 150 and the model of the vehicle 10 indicated by the model information received from the user terminal 82.

[0042] In S314, the server 70 transmits function information indicating the control data and the function selected in S312 to the vehicle 10. In S320, when the ECU 100 receives the control data and the function information via the TCU 160, the notification unit 240 of the ECU 100 notifies the user 80 of the update information via the MID 170, and prompts the user 80 to specify whether or not to perform a software update.

[0043] The update information notified to the user 80 in S320 may include information indicating that a software update of the ECU 110 is possible. The update information notified to the user 80 may be information based on function information received from the server 70. For example, the update information notified to the user 80 may include information indicating functions that the battery 150 can provide or functions that the battery 150 cannot provide. Specifically, the update information notified to the user 80 may include information indicating that performing a software update will impose limitations on the idle stop function of the vehicle 10. The update information notified to the user 80 may include information indicating that performing a software update will increase the possibility that the vehicle 10 will not be able to start due to a dead battery. The update information notified to the user 80 may include information indicating that a software update will be performed with priority over turning on the ignition (IG) power supply for the vehicle 10 for a predetermined period after the IG power supply is turned off. The notification in S320 may be made when the IG power supply is turned off.

[0044] In S322, the update unit 230 of the ECU 100 determines whether to perform a software update of the ECU 110. If the user 80 specifies that a software update should be performed when the notification information is notified in S320, the update unit 230 of the ECU 100 determines to perform the software update. If the user 80 does not specify that a software update should be performed when the notification information is notified in S320, the update unit 230 of the ECU 100 determines not to perform the software update. If it is determined that a software update should not be performed, the process of this flowchart ends. If it is determined that a software update should be performed, in S324, the update unit 230 of the ECU 100 rewrites the control data of the ECU 110 with the control data received from the server 70. Furthermore, the change unit 250 of the ECU 100 changes the time during which information related to the software update can be communicated with the server 70, based on the function information of the new battery 150.

[0045] In S326, ECU 110 starts control based on the control data rewritten in S324. S326 may be executed when the IG power supply of vehicle 10 is turned on, for example.

[0046] In S328, the notification unit 240 of the ECU 100 determines whether or not the vehicle 10 has a functional restriction. The notification unit 240 determines whether or not the vehicle 10 has a functional restriction based on the functional information transmitted from the server 70 in S314. If the vehicle 10 has no functional restriction, the process of this flowchart ends. If the vehicle 10 has a functional restriction, the notification unit 240 notifies the user 80 of the content of the functional restriction via the MID 170 in S330, and then ends the process of this flowchart. The functional restriction may include, for example, a restriction on the vehicle 10's idle stop function. The functional restriction may include, for example, a starting restriction that may occur due to a dead battery in the vehicle 10. For example, if the battery capacity of the newly installed battery 150 is smaller than that of a genuine battery, the vehicle 10 may be unable to use the idle stop function, even if the vehicle 10 would be able to use the idle stop function if it were equipped with a genuine battery. In this case, the notification unit 240 can notify the user 80 that the software update has caused the vehicle 10's idle stop function to become unavailable. Furthermore, if the battery capacity of the newly installed battery 150 is unusually low for the vehicle 10, there is a high possibility that the vehicle 10 will not be able to start due to a dead battery. The notification unit 240 can warn the user 80 that the software update has increased the possibility that the vehicle 10 will not be able to start due to a dead battery.

[0047] 3, the processes of S304, S308, and S310 are executed by the user terminal 82. In another embodiment, the selection control unit 210 may allow the user 80 to select the model information of the battery 150 through the MID 170 and an operation member provided in the vehicle 10.

[0048] Although the above describes a mode in which the user 80 is notified through the MID 170, the notification to the user 80 may be made through various user interface devices such as a display audio and IVI (in-vehicle infotainment).

[0049] According to the update system 5 described above, when a non-genuine battery 150 is installed in the vehicle 10 due to a battery replacement, software of the ECU 110 can be updated via OTA so that the ECU 110 can appropriately control the battery 150. Furthermore, if it becomes necessary to restrict the functions of the vehicle 10 due to the software update, the user 80 can be notified of this before and after the software update. This makes it possible to perform appropriate battery management to prevent excessive use of the non-genuine battery 150 and to prevent early deterioration of the battery 150.

[0050] 4 shows an example of a computer 2000 in which multiple embodiments of the present invention may be embodied in whole or in part. A program installed on the computer 2000 may cause the computer 2000 to function as a system or each part of a system, such as the system 20 according to an embodiment, or an apparatus or each part of the apparatus, such as the ECU 100, to perform operations associated with the system or each part of the system or the apparatus or each part of the apparatus, and / or to perform a process or steps of the process according to an embodiment. Such a program may be executed by the CPU 2012 to cause the computer 2000 to perform specific operations associated with some or all of the processing procedures and blocks of the block diagrams described herein.

[0051] The computer 2000 according to this embodiment includes a CPU 2012 and a RAM 2014, which are interconnected by a host controller 2010. The computer 2000 also includes a ROM 2026, a flash memory 2024, a communication interface 2022, and an input / output chip 2040. The ROM 2026, the flash memory 2024, the communication interface 2022, and the input / output chip 2040 are connected to the host controller 2010 via the input / output controller 2020.

[0052] The CPU 2012 operates according to programs stored in the ROM 2026 and RAM 2014, thereby controlling each unit.

[0053] The communication interface 2022 communicates with other electronic devices via a network. The flash memory 2024 stores programs and data used by the CPU 2012 in the computer 2000. The ROM 2026 stores a boot program and the like executed by the computer 2000 upon activation, and / or programs dependent on the hardware of the computer 2000. The input / output chip 2040 may also connect various input / output units such as a keyboard, mouse, and monitor to the input / output controller 2020 via input / output ports such as a serial port, a parallel port, a keyboard port, a mouse port, a monitor port, a USB port, an HDMI (registered trademark) port, etc.

[0054] The programs are provided via a computer-readable storage medium such as a CD-ROM, a DVD-ROM, or a memory card, or via a network. The RAM 2014, the ROM 2026, or the flash memory 2024 are examples of computer-readable storage media. The programs are installed in the flash memory 2024, the RAM 2014, or the ROM 2026 and executed by the CPU 2012. Information processing described in these programs is read by the computer 2000, and causes cooperation between the programs and the various types of hardware resources described above. An apparatus or a method may be configured by implementing operations or processing of information in accordance with the use of the computer 2000.

[0055] For example, when communication is performed between the computer 2000 and an external device, the CPU 2012 may execute a communication program loaded into the RAM 2014 and instruct the communication interface 2022 to perform communication processing based on the processing described in the communication program. Under the control of the CPU 2012, the communication interface 2022 reads transmission data stored in a transmission buffer processing area provided in a recording medium such as the RAM 2014 or flash memory 2024, transmits the read transmission data to a network, and writes received data received from the network to a reception buffer processing area or the like provided on the recording medium.

[0056] The CPU 2012 may also cause all or a necessary portion of a file or database stored on a recording medium such as the flash memory 2024 to be read into the RAM 2014, and perform various types of processing on the data on the RAM 2014. The CPU 2012 then writes the processed data back to the recording medium.

[0057] Various types of information, such as various types of programs, data, tables, and databases, may be stored on the recording medium and subjected to information processing. The CPU 2012 may perform various types of processing on data read from the RAM 2014, including various types of operations, information processing, conditional judgment, conditional branching, unconditional branching, information search / replacement, etc., as described herein and specified by the instruction sequences of the programs, and write the results back to the RAM 2014. The CPU 2012 may also search for information in a file, database, etc. on the recording medium. For example, if multiple entries each having an attribute value of a first attribute associated with an attribute value of a second attribute are stored on the recording medium, the CPU 2012 may search for an entry that matches a condition specified by the attribute value of the first attribute from among the multiple entries, read the attribute value of the second attribute stored in the entry, and thereby obtain the attribute value of the second attribute associated with the first attribute that satisfies a predetermined condition.

[0058] The above-described programs or software modules may be stored in a computer-readable storage medium on or near the computer 2000. A recording medium such as a hard disk or RAM provided in a server system connected to a dedicated communication network or the Internet can be used as the computer-readable storage medium. The programs stored in the computer-readable storage medium may be provided to the computer 2000 via a network.

[0059] A program installed in computer 2000 and causing computer 2000 to function as ECU 110 may act on CPU 2012 or the like to cause computer 2000 to function as each unit of ECU 110. When the information processing described in these programs is read into computer 2000, it functions as each unit of ECU 110, which is a specific means formed by the software and the various hardware resources described above working together. These specific means then perform calculations or processing of information according to the intended use of computer 2000 in this embodiment, thereby constructing a specific ECU 110 according to the intended use.

[0060] Various embodiments have been described with reference to block diagrams. In the block diagrams, each block may represent (1) a stage of a process where an operation is performed or (2) a portion of an apparatus responsible for performing the operation. Particular stages and portions may be implemented by dedicated circuitry, programmable circuitry provided with computer-readable instructions stored on a computer-readable storage medium, and / or a processor provided with computer-readable instructions stored on a computer-readable storage medium. Dedicated circuitry may include digital and / or analog hardware circuitry, and may include integrated circuits (ICs) and / or discrete circuits. Programmable circuitry may include reconfigurable hardware circuitry including logical AND, logical OR, logical XOR, logical NAND, logical NOR, and other logic operations, flip-flops, registers, memory elements such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), and the like.

[0061] A computer-readable storage medium may include any tangible device capable of storing instructions that are executed by an appropriate device, such that the computer-readable storage medium with instructions stored thereon constitutes at least a portion of an article of manufacture containing instructions that can be executed to provide means for performing the operations specified in a process or block diagram. Examples of computer-readable storage media may include electronic storage media, magnetic storage media, optical storage media, electromagnetic storage media, semiconductor storage media, etc. More specific examples of computer-readable storage media may include floppy disks, diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), electrically erasable programmable read-only memory (EEPROM), static random access memory (SRAM), compact disc read-only memory (CD-ROM), digital versatile disc (DVD), Blu-ray disc, memory stick, integrated circuit card, etc.

[0062] The computer readable instructions may include either assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, or source or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk®, JAVA®, C++, etc., and conventional procedural programming languages ​​such as the “C” programming language or similar programming languages.

[0063] The computer-readable instructions may be provided to a processor or programmable circuitry of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, either locally or over a wide-area network (WAN) such as a local area network (LAN), the Internet, etc., and executed to provide means for performing the operations specified in the process steps or block diagrams described. Examples of processors include computer processors, processing units, microprocessors, digital signal processors, controllers, microcontrollers, etc.

[0064] Although the present invention has been described above using embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be apparent to those skilled in the art that various modifications and improvements can be made to the above embodiments. It is clear from the claims that such modifications and improvements can also be included within the technical scope of the present invention.

[0065] It should be noted that the execution order of each process, such as operations, procedures, steps, and stages, in the devices, systems, programs, and methods shown in the claims, specifications, and drawings is not specifically stated as "before," "prior to," etc., and that the processes can be performed in any order unless the output of a previous process is used in a subsequent process. Even if the operational flow in the claims, specifications, and drawings is described using "first," "next," etc. for convenience, this does not mean that the processes must be performed in this order. [Explanation of symbols]

[0066] 5 Update System 10 vehicles 20 Systems 70 servers 80 users 82 User terminals 100 ECU 110 ECU 120 ECU 121 ECU 150 Battery 160 TCU 170 MID 180 Communication Network 200 Processing section 210 Selection control section 220 Receiving unit 230 Update Department 240 Notification Department 250 Changes 260 Detector 280 Storage section 2000 Computer 2010 Host Controller 2012 CPU 2014 RAM 2020 Input / Output Controller 2022 Communication Interface 2024 flash memory 2026 ROM 2040 Input / Output Chip

Claims

1. An OTA (Over-The-Air) system for updating software of an in-vehicle device provided in a vehicle based on information received from outside the vehicle, a detection unit that detects that a control target device controlled by the in-vehicle device has been changed; a selection control unit that performs control to select model information of the new battery when the detection unit detects that the battery controlled by the in-vehicle device has been replaced with a new battery; a receiving unit that receives control data for controlling the new battery from a server external to the vehicle; an update unit that updates software on the in-vehicle device so that the new battery is controlled based on the control data; A system comprising:

2. The selection control unit allows a user to select the model information using a user terminal associated with the vehicle. The system of claim 1 .

3. The selection control unit selects the model information based on information acquired from the new battery through a power line, or selects the model information based on information generated when a key unit provided at a battery connection terminal matches a key unit provided at a connection terminal of the new battery. The system of claim 1 .

4. the update unit, after an ignition power supply of the vehicle is turned off, performs a software update of the in-vehicle device with priority over turning on the ignition power supply; The system comprises: a notification unit that notifies the user that software update of the in-vehicle device takes priority over turning on the ignition power after the ignition power of the vehicle is turned off; The system of claim 1 , further comprising:

5. a change unit that changes, in accordance with the new battery, a time during which information regarding the software update can be communicated with the server while an ignition power source of the vehicle is turned off; The system of claim 1 , further comprising:

6. a notification unit that notifies the vehicle of the fact that the new battery is an unknown type of battery before performing a software update of the in-vehicle device when the new battery is determined to be an unknown type of battery for the vehicle based on the model information; The system of claim 1 , further comprising:

7. the vehicle is capable of restarting an engine provided in the vehicle from an idle stop state in which the engine is stopped by using electric power provided by the battery; When it is determined that the new battery is a battery of a type that is not compatible with idle stop, the update unit updates the software of the in-vehicle device so as to prohibit idle stop of the vehicle. A system according to any one of claims 1 to 3.

8. A vehicle comprising a system according to any one of claims 1 to 7.

9. A method for updating software of an in-vehicle device provided in a vehicle by OTA (Over-The-Air) based on information received from outside the vehicle, comprising: detecting that a control target device controlled by the in-vehicle device has been changed; When it is detected that the battery controlled by the in-vehicle device has been replaced with a new battery, performing control to select model information of the new battery; receiving control data for controlling the new battery from a server external to the vehicle; updating software of the in-vehicle device so that the new battery is controlled based on the control data; Equipped with The step of controlling to select the new battery model information includes having a user select the model information using a user terminal associated with the vehicle. method.

Images