JP7785599B2 - Systems, vehicles and methods - Google Patents

Description

The present invention relates to a system, a vehicle, and a method.

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 documents]
[Patent Documents]
Patent Document 1: JP 2014-146494 A

However, when a vehicle's battery is replaced with a new one, it is important to ensure that the new battery is not controlled in a way that differs from what was expected. This application aims to solve the above problem by improving the marketability of batteries. This will ultimately contribute to the development of sustainable transportation systems by further improving traffic safety and the lifespan of consumables.

A first aspect of the present invention provides a system. The system is an OTA (Over-The-Air) system for updating the software of on-board equipment 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 on-board equipment has been changed. The system includes a selection control unit that, when the detection unit detects that the battery controlled by the on-board equipment has been replaced with a new battery, performs control to select model information for 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 on-board equipment so that the new battery is controlled based on the control data.

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

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.

The update unit may prioritize updating the software of the in-vehicle device after the ignition power of the vehicle is turned off over turning on the ignition power. 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.

The system may further include a change unit that changes the time during which information regarding the software update can be communicated with the server while the vehicle's ignition power is turned off, depending on the new battery.

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

The vehicle may be capable of restarting the engine of the vehicle from an idle stop state in which the engine is stopped, using power provided by the battery. If the update unit determines that the new battery is a type of battery that is not compatible with idle stop, it may update the software of the on-board equipment to prohibit idle stop of the vehicle.

In a second aspect of the present invention, a vehicle is provided. The vehicle includes the above-described system.

A third aspect of the present invention provides a method. The method is for performing a software update of an on-board 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 on-board 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 the battery controlled by the on-board 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 on-board 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 involves having a user select the model information using a user terminal associated with the vehicle.

The above summary of the invention does not list all of the features of the present invention. Also, subcombinations of these features may also constitute inventions.

1 conceptually illustrates a usage scenario of the update system 5 according to an embodiment. 2 is a block diagram showing a schematic functional configuration of an ECU 100. FIG. 10 is a flowchart showing the flow of processing executed in the update system 5. An example of a computer 2000 is shown schematically.

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

Figure 1 conceptually illustrates a usage scenario of the update system 5 in one embodiment. The update system 5 includes a vehicle 10, a server 70, and a user terminal 82.

Vehicle 10 includes system 20. System 20 includes multiple ECUs (electronic control units) including ECU 100, ECU 110, ECU 120, and ECU 121, as well as 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 the engine, transmission, and 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 the air conditioner and navigation device. ECU 100, ECU 110, ECU 120, and ECU 121 are examples of on-board equipment.

TCU 160 is a telematics control unit. TCU 160 is primarily responsible for mobile communications. MID 170 is a multi-information display.

The multiple ECUs, TCU 160, and MID 170 provided in vehicle 10 communicate with each other via a Controller Area Network (CAN) communication network or a communication network 180 that conforms to the Ethernet (registered trademark) standard. The ECUs, TCU 160, and MID 170 provided in vehicle 10 are communicably connected to each other via the multiple communication networks 180. ECU 100 may function as a gateway that relays communications between the multiple communication networks 180. ECU 100 may be the ECU that controls the entire system 20.

In this embodiment, the ECU 110 is an ECU that controls, for example, the battery 150. The battery 150 is 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.

When the ECU 100 detects that the battery installed in the vehicle 10 has been replaced with a new battery 150, it performs control to allow the user 80 of the vehicle 10 to select model information for the battery 150. The user 80 is a user who has been pre-registered as a user of the vehicle 10.

As an example, the ECU 100 notifies the server 70 via the TCU 160 that the battery 150 has been replaced with a new one, 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 pre-registered 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 was input to the user terminal 82 from the user terminal 82.

As another method, when the battery installed in the vehicle 10 is replaced with a new battery 150, the ECU 100 allows the user 80 to select model information for the battery 150 via the MID 170. The ECU 100 then transmits the model information selected by the user 80 via the MID 170 to the server 70 via the TCU 160.

Based on the model information of the battery 150 received via the user terminal 82 or the TCU 160, the server 70 selects update software for the ECU 110 and transmits it to the vehicle 10. The update software is control software executed by the ECU 110 so that the ECU 110 can perform control appropriate 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 via OTA (Over The Air). In this embodiment, rewriting the software of the ECU 110 with the update software is referred to as a "software update."

Figure 2 is a block diagram that shows a schematic functional configuration of ECU 100. ECU 100 includes a processing unit 200 and a memory unit 280. ECU 100 is an example of an OTA (over-the-air) system that updates the software of ECU 110 included in vehicle 10 based on information received from outside vehicle 10.

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 flash memory, or a volatile storage medium such as random access memory. Each ECU 100 may be configured to include a computer. The ECU 100 performs various controls by the processing unit 200 operating in accordance with programs stored in the non-volatile storage medium.

The processing unit 200 includes a selection control unit 210, a receiving unit 220, an updating unit 230, a notification unit 240, a change unit 250, and a detection unit 260.

The detection unit 260 detects that the control target device controlled by the ECU 110 has changed. For example, the detection unit 260 detects that the control target device has changed based on information notified by the ECU 110 when it detects that the control target device has changed. The selection control unit 210 performs control to select model information for 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 receiving 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 for the new battery 150 and transmit the model information to the server 70 that provides the control data.

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 software update processing while the vehicle 10 is stopped.

The selection control unit 210 may select the model information based on information obtained from the new battery 150 via the power line, or may select the model information based on information generated when the key unit provided at the battery connection terminal matches the key unit provided at the connection terminal of the new battery 150. For example, the ECU 110 may obtain the model information of the battery 150 by communicating with the battery 150 via the power line, and the selection control unit 210 may obtain the model information transmitted from the ECU 110 to the ECU 100. In another embodiment, the 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 the connection terminal of a specific type of battery. The ECU 110 may detect whether the battery has been replaced with a specific type by obtaining information from a sensor that detects whether the key unit of the battery connection terminal and the key unit of the connection terminal of the installed battery are engaged, and transmit information indicating the detection result to the ECU 100. The selection control unit 210 may acquire model information based on information indicating the detection results sent from the ECU 110 to the ECU 100. A specific model battery may be a genuine battery for the vehicle 10. This allows the ECU 110 and 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 required for the user 80 to select the model can be reduced.

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 that after the ignition power of the vehicle 10 is turned off, updating the software of the ECU 110 takes priority over turning on the ignition power. This allows the software update of the ECU 110 to be prioritized so that, when the battery is replaced, the vehicle 10 can be started properly the next time using the new battery 150.

The change unit 250 may change the time during which information related to software updates can be received from the server 70 while the ignition power of the vehicle 10 is turned off, depending on the new battery 150. The change unit 250 may change the time during which information related to software updates can be communicated with the server 70, depending on the battery capacity determined from the model information of the new battery 150. This makes it possible to change the communication time related to software updates depending on 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 updates can be.

If 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 it is an unknown battery before performing a software update on 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. An unknown battery may be a battery that is not intended to be installed in the vehicle 10. An unknown battery may be a battery that does not meet the standards for the vehicle 10. An unknown battery may be a battery with a battery capacity that does not meet the standards for the vehicle 10.

The vehicle 10 may be able to restart the engine of the vehicle 10 from an idle stop state in which the engine has stopped, using power provided by the battery. If the update unit 230 determines that the new battery 150 is a battery model that is not compatible with idle stop, it updates the software of the ECU 110 to prohibit idle stop of the vehicle 10. This makes it possible to prohibit idle stop in a vehicle that is compatible with idle stop if the model of the new battery 150 is not compatible with idle stop.

Figure 3 is a flowchart showing the flow of processing executed in the update system 5. The flowchart shown in Figure 3 is a flowchart for obtaining model information of the battery 150 via the user terminal 82.

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

In S304, the selection control unit 210 notifies the server 70 that the battery of the vehicle 10 has been replaced, thereby notifying the user terminal 82 to prompt the user 80, who has been previously associated with the vehicle 10, to select model information for 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 for the battery 150.

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 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 specified in advance for each vehicle 10 by the manufacturer of the vehicle 10. The software installed in the ECU 110 is pre-created to provide control appropriate for genuine batteries.

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

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.

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 that corresponds to multiple battery models and multiple vehicle models and includes 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 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.

In S314, the server 70 transmits function information indicating the control data and functions selected in S312 to the vehicle 10. In S320, when the ECU 100 receives the control data and 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.

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 limit 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 likelihood 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 prioritized over turning on the ignition (IG) power supply of the vehicle 10 for a predetermined period after the ignition (IG) power supply of the vehicle 10 is turned off. The notification in S320 may be made when the IG power supply is turned off.

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 a 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 a software update. If it is determined that a software update should not be performed, the processing 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.

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

In S328, the notification unit 240 of the ECU 100 determines whether the vehicle 10 has a functional restriction. The notification unit 240 determines whether 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 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 capacity of the newly installed battery 150 is smaller than that of a standard 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 standard 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 may be a high possibility that the vehicle 10 will be unable 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 be unable to start due to a dead battery.

In the flowchart of FIG. 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 model information for the battery 150 via the MID 170 and operation members provided on the vehicle 10.

The above describes a method of notifying the user 80 via the MID 170, but notifications to the user 80 may also be sent via various user interface devices such as display audio and IVI (in-vehicle infotainment).

With the update system 5 described above, if a non-genuine battery 150 is installed in the vehicle 10 due to a battery replacement, the software of the ECU 110 can be updated via OTA so that the ECU 110 can properly control the battery 150. Furthermore, if the software update requires restricting the functions of the vehicle 10, the user 80 can be notified 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 premature deterioration of the battery 150.

Figure 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 system 20 according to an embodiment, or an apparatus or each part of an apparatus, such as 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.

The computer 2000 according to this embodiment includes a CPU 2012 and 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.

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

The communications 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 programs such as a boot program executed by the computer 2000 upon activation and/or programs that depend 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, parallel port, keyboard port, mouse port, monitor port, USB port, HDMI (registered trademark) port, etc.

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

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

The CPU 2012 may also cause all or a necessary portion of a file or database stored on a recording medium such as 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.

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 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 program, and write the results back to RAM 2014. The CPU 2012 may also search for information in files, databases, 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 and specifies an 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.

The programs or software modules described above may be stored on a computer-readable storage medium on or near the computer 2000. Recording media such as a hard disk or RAM provided within a server system connected to a dedicated communications network or the Internet can be used as the computer-readable storage medium. The programs stored on the computer-readable storage medium may be provided to the computer 2000 via the network.

Programs installed on computer 2000 that cause computer 2000 to function as ECU 110 may act on CPU 2012, etc., to cause computer 2000 to function as each part of ECU 110. When the information processing described in these programs is loaded into computer 2000, it functions as each part of ECU 110, which is a concrete means formed by the software and the various hardware resources described above working together. These concrete means then perform calculations or processing of information according to the intended use of computer 2000 in this embodiment, thereby constructing a unique ECU 110 according to the intended use.

Various embodiments have been described with reference to block diagrams and the like. 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 an 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.

A computer-readable storage medium may include any tangible device capable of storing instructions for execution by an appropriate device, such that the computer-readable storage medium having 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.

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.

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 described process steps or block diagrams. Examples of processors include computer processors, processing units, microprocessors, digital signal processors, controllers, microcontrollers, etc.

The present invention has been described above using embodiments, but the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be clear 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.

The order of execution 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," or the like, and it should be noted that 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 it is necessary to perform the processes in that order.

5 Update system 10 Vehicle 20 System 70 Server 80 User 82 User terminal 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 section 230 Update section 240 Notification section 250 Change section 260 Detection section 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 (9)

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 of the in-vehicle device so that the new battery is controlled based on the control data. The system according to claim 1 , wherein the selection control unit allows a user to select the model information using a user terminal associated with the vehicle. The system described in claim 1, wherein the selection control unit selects the model information based on information obtained from the new battery via a power line, or selects the model information based on information generated when a key unit provided on a battery connection terminal matches a key unit provided on a connection terminal of the new battery. 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:
The system according to claim 1 , further comprising a notification unit that notifies the user that a software update of the in-vehicle device takes priority over turning on the ignition power after the ignition power of the vehicle has been turned off. The system described in any one of claims 1 to 4, further comprising a change unit that changes the time during which information regarding the software update can be communicated with the server when the ignition power of the vehicle is turned off, depending on the new battery. 6. The system according to claim 1, further comprising a notification unit that, when 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 owner that the new battery is an unknown battery before performing a software update of the in-vehicle device. 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;
The system according to any one of claims 1 to 3, wherein the update unit updates the software of the on-board equipment so as to prohibit idle stop of the vehicle if it is determined that the new battery is a type of battery that is not compatible with idle stop. A vehicle equipped with the system described in any one of claims 1 to 7. 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;
The step of controlling selection of model information of the new battery includes having a user select the model information using a user terminal associated with the vehicle.