JP2023150500A - System, vehicle, and method - Google Patents

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 The present invention relates to systems, vehicles and methods.

Patent Document 1 discloses that it is determined whether a battery newly installed in a vehicle is a dedicated battery or a non-dedicated battery.
[Prior art documents]
[Patent document]
Patent Document 1 Japanese Patent Application Publication No. 2014-146494

By the way, when a battery installed in a vehicle is replaced with a new battery, it is a problem to prevent the new battery from being controlled differently than expected. The present application aims to improve the marketability of batteries in order to solve the above-mentioned problems. In turn, this will further improve traffic safety and the lifespan of consumables, contributing to the development of a sustainable transportation system.

In a first aspect of the invention, a system is provided. The system is an OTA (Over-The-Air) system for updating software of in-vehicle equipment included in the vehicle based on information received from outside the vehicle. The system includes a detection unit that detects that a controlled device controlled by the in-vehicle device has been changed. The system includes 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. Equipped with 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 software of the in-vehicle device so that the new battery is controlled based on the control data.

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

The selection control section selects the model information based on information acquired from the new battery through a power line, or selects the model information based on information obtained from the new battery through a power line, or selects a key section provided at the battery connection terminal and a key provided at the connection terminal of the new battery. The type information may be selected based on information generated when the parts match.

After the ignition power of the vehicle is turned off, the update unit may update the software of the in-vehicle equipment with priority over turning on the ignition power. The system may further include a notification unit that notifies that after the ignition power of the vehicle is turned off, software updating of the in-vehicle equipment is prioritized over turning on the ignition power.

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

If the system determines that the new battery is of an unknown model for the vehicle based on the model information, the system updates the software of the in-vehicle device to indicate that the new battery is an unknown battery. It may further include a notification unit that notifies the user before performing the process.

The vehicle may be capable of restarting the engine from an idle stop state in which the engine of the vehicle is stopped using electric power provided from the battery. If it is determined that the new battery is a type of battery that does not support idle stop, the update unit may update the software of the in-vehicle device to prohibit idle stop of the vehicle.

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

In a third aspect of the invention, a method is provided. The method is a method for updating software of in-vehicle equipment included in the vehicle by OTA (Over-The-Air) based on information received from outside the vehicle. The method includes detecting that a controlled device controlled by the in-vehicle device has been changed. The method includes the step of performing control to select model information of the new battery when it is detected that the battery controlled by the in-vehicle device has been replaced with a new battery. The method includes receiving control data for controlling the new battery from a server external to the vehicle. The method includes the step of updating software of the in-vehicle device so that the new battery is controlled based on the control data. In the step of controlling for selecting the new battery type information, the user selects the type information using a user terminal associated with the vehicle.

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

1 conceptually shows a usage scene of the update system 5 in one embodiment. 1 is a block diagram schematically showing the functional configuration of an ECU 100. FIG. 5 is a flowchart showing the flow of processing executed in the update system 5. FIG. An example of a computer 2000 is schematically shown.

Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the invention according to the claims. Furthermore, not all combinations of features described in the embodiments are essential to the solution of the invention.

FIG. 1 conceptually shows a usage scene of an 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 . The system 20 includes a plurality of ECUs (electronic control units) including ECU 100, ECU 110, ECU 120, and ECU 121, a TCU 160, and an MID 170. The ECU included in the vehicle 10 includes an ECU for controlling devices that directly affect the running of the vehicle 10, such as an engine, a transmission, a steering device, and the like. The ECU included in the vehicle 10 includes an ECU for controlling devices that do not directly affect the running of the vehicle 10, such as an air conditioner and a navigation device. ECU100, ECU110, ECU120, and ECU121 are examples of in-vehicle equipment.

TCU 160 is a telematics control unit. TCU 160 is mainly responsible for mobile communication. MID170 is a multi-information display.

A plurality of ECUs, TCUs 160, and MIDs 170 included in the vehicle 10 communicate with each other via a controller area network (CAN) communication network or a communication network 180 compliant with the Ethernet (registered trademark) standard. The ECU, TCU 160, and MID 170 included in the vehicle 10 are communicably connected to each other via a plurality of communication networks 180. ECU 100 may function as a gateway that relays communications between multiple communication networks 180. The ECU 100 may be an ECU that centrally controls the entire system 20.

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

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

As an example, the ECU 100 requests the server 70 to allow the user 80 to select the type of the battery 150 by notifying the server 70 through the TCU 160 that the battery 150 has been replaced with a new one. The server 70 communicates with a user terminal 82 registered in advance as a user terminal used by the user 80 and notifies the user 80 to select the type of 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 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 the model information of the battery 150 through the MID 170. ECU 100 transmits model information selected by user 80 through MID 170 to server 70 through TCU 160.

Server 70 selects update software for ECU 110 based on the model information of battery 150 received through user terminal 82 or TCU 160, and transmits it to vehicle 10. The update software is control software executed by the ECU 110 in order for the ECU 110 to perform appropriate control of the battery 150. When the TCU 160 receives the updated software transmitted from the server 70, the ECU 100 reprograms the ECU 100 by rewriting the software that controls the ECU 110 with the updated software. In this way, 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 updated software is referred to as "software update."

FIG. 2 is a block diagram schematically showing the functional configuration of the ECU 100. ECU 100 includes a processing section 200 and a storage section 280. ECU 100 is an example of an OTA (OVER-THE-AIR) system for updating software of ECU 110 included in vehicle 10 based on information received from outside of 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 nonvolatile storage medium such as a flash memory, and a volatile storage medium such as a random access memory. Each ECU 100 may be configured to include a computer. ECU 100 executes various controls by causing processing unit 200 to operate according to programs stored in a nonvolatile storage medium.

The processing section 200 includes a selection control section 210, a reception section 220, an update section 230, a notification section 240, a change section 250, and a detection section 260.

Detection unit 260 detects that the controlled device controlled by ECU 110 has been changed. For example, the detection unit 260 detects that the controlled device has been changed based on information notified from the ECU 110 when detecting that the controlled 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. Receiving unit 220 receives control data for controlling new battery 150 from a server external to vehicle 10 . The update unit 230 updates the software of the ECU 110 so that a new battery 150 is controlled based on the control data. Thereby, it is possible to select new model information of the battery 150 and transmit the model information to the server 70 that provides control data.

The selection control unit 210 may allow the user 80 to select model information using the user terminal 82 associated with the vehicle 10. The selection control unit 210 may cause the user 80 to select model information via the server 70 by notifying the server 70 that the battery has been replaced. As a result, the type of battery 150 can be selected using the user terminal 82, so that software update-related processing can be performed even when the vehicle 10 is stopped.

The selection control unit 210 may select the model information based on information acquired from the new battery 150 through the power line, or may select the model information based on the information obtained from the new battery 150 through the power line, or select the model information between the key provided at the battery connection terminal and the connection terminal of the new battery 150. Type information may be selected based on information generated when the key part matches. For example, ECU 110 may acquire model information of battery 150 by communicating with battery 150 through a power line, and selection control unit 210 may obtain model information transmitted from ECU 110 to ECU 100. In another embodiment, the battery connection terminal to which the connection terminal of the battery 150 is connected is provided with a key having a specific shape that engages with a key having a specific shape provided on the connection terminal of a specific type of battery. good. The ECU 110 can determine whether the battery has been replaced with a specific model by acquiring information from a sensor that detects whether the key of the battery connection terminal and the key of the connection terminal of the battery to be installed are engaged. It may be detected and information indicating the detection result may be transmitted to the ECU 100. The selection control unit 210 may acquire model information based on information indicating the detection result transmitted from the ECU 110 to the ECU 100. The particular type of battery may be the genuine battery for the vehicle 10. Thereby, when the battery of vehicle 10 is replaced, ECU 110 and ECU 100 can automatically determine which type of battery has been replaced. In particular, when the battery is replaced with a genuine battery, the user 80 can reduce the number of operations required to select the model.

After the ignition power of the vehicle 10 is turned off, the update unit 230 updates the software of the ECU 110 with priority over turning on the ignition power. For example, when 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. Thereby, when the battery is replaced, priority can be given to updating the software of the ECU 110 so that the next time the vehicle 10 can be started appropriately using the new battery 150.

The changing unit 250 may change the time during which information regarding 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 changing unit 250 may change the time during which information regarding software updates can be communicated with the server 70, depending on the battery capacity determined from the model information of the new battery 150. Thereby, the communicable time regarding software update can be changed depending on the type of battery 150. For example, the smaller the battery capacity of the battery 150, the shorter the communication available time regarding software updates.

When it is determined that the new battery 150 is of a type unknown to the vehicle 10 based on the model information, the notification unit 240 notifies the vehicle 10 of the unknown battery before updating the software of the ECU 110. Notice. Thereby, when the new battery 150 is an unknown battery, it is possible to warn the user 80 in advance about using the unknown battery in the vehicle 10. The unknown battery may be a battery that is not expected to be installed in the vehicle 10. The unknown battery may be a non-standard battery for the vehicle 10. The unknown battery may be a battery whose battery capacity is outside the standard for the vehicle 10.

The vehicle 10 may be able to restart the engine from an idle stop state in which the engine of the vehicle 10 is stopped using electric power provided from the battery. If it is determined that the new battery 150 is a type of battery that does not support idle stop, the update unit 230 updates the software of the ECU 110 to prohibit the idle stop of the vehicle 10. Thereby, in a vehicle compatible with idle stop, if the new battery 150 type cannot support idle stop, idle stop can be prohibited.

FIG. 3 is a flowchart showing the flow of processing executed in the update system 5. As shown in FIG. The flowchart shown in FIG. 3 is a flowchart for acquiring model information of the battery 150 through the user terminal 82.

In S302, 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 installed in the vehicle 10, and if the BIN acquired from the battery 150 does not match the BIN held by the ECU 110, the ECU 110 It is determined that the battery has been replaced. The ECU 110 may detect the 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. ECU 110 notifies 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 instructing the user terminal 82 to cause the user 80 associated with the vehicle 10 in advance to select model information of the battery 150. Notice. For example, the server 70 transmits a selection menu for the user 80 to select model information of the battery 150 to the user terminal 82.

In S306, the user terminal 82 determines whether the battery 150 is a genuine product based on the information input by the user 80. The user terminal 82 displays a selection menu for allowing the user 80 to select whether or not the battery 150 newly installed in the vehicle 10 by the user 80 is a genuine product. The user terminal 82 determines that the battery 150 is a genuine product when the user 80 selects that the battery 150 is a genuine product through the selection menu, and determines that the battery 150 is a genuine product when the user 80 selects that the battery 150 is not a genuine product. It is determined that the battery 150 is not a genuine product. If the battery 150 is a genuine product, the process of this flowchart ends. Thereby, ECU 110 controls battery 150 according to the already installed software. Genuine batteries are specified in advance for each vehicle 10 by the vehicle 10 manufacturer. It is assumed that the software installed in the ECU 110 is created in advance to perform control suitable for a genuine battery.

If it is selected in S306 that the battery is not genuine, the user terminal 82 allows the model of the battery 150 to be selected in S308. For example, the user terminal 82 displays a menu listing battery manufacturers and allows the user 80 to select the manufacturer that manufactured the battery 150. When a manufacturer is selected, the user terminal 82 displays a menu listing battery manufacturers manufactured by the selected manufacturer. is displayed to allow the user 80 to select the type of 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 match the type of battery 150 based on the type information received from the user terminal 82. The control data is update software that includes a control program for ECU 110 to control battery 150 and various control data.

The function information selected by the server 70 in S312 is at least one of information indicating a function that the battery can or cannot provide to the vehicle, performance information of the battery, and information indicating whether the battery is non-standard for the vehicle. may include. The server 70 stores information indicating functions that the battery can or cannot provide to the vehicle, performance information of the battery, and whether or not the battery is non-standard for the vehicle, in association with multiple battery types and multiple vehicle types. Correspondence information including information indicating the information may be stored in advance. 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 rated voltage of the battery. In S312, the server 70 may refer to the correspondence information and select the functional 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 the control data and function information indicating the function selected in S312 to the vehicle 10. In S320, when the ECU 100 receives the control data and function information through the TCU 160, the notification unit 240 of the ECU 100 notifies the user 80 of the update information through the MID 170, and allows the user 80 to specify whether or not to execute the software update.

The update information notified to the user 80 in S320 may include that it is possible to update the software of the ECU 110. The update information notified to the user 80 may be information based on the functional information received from the server 70. For example, the update information notified to the user 80 may include information indicating a function that the battery 150 can provide or a function that the battery 150 cannot provide. Specifically, the update information notified to the user 80 may include information indicating that the idle stop function of the vehicle 10 is restricted by updating the software. The update information notified to the user 80 may include information indicating that updating the software increases the possibility that the vehicle 10 will not be able to start due to the battery of the vehicle 10 running out. The update information notified to the user 80 includes information indicating that the software update will be performed with priority over turning on the IG power during a predetermined period after the ignition (IG) power of the vehicle 10 is turned off. good. The notification in S320 may be performed when the IG power is turned off.

In S322, the update unit 230 of the ECU 100 determines whether to update the software of the ECU 110. The update unit 230 of the ECU 100 determines to execute the software update when the user 80 specifies that the software update is to be performed when the notification information is notified in S320, and the update unit 230 determines that the software update is to be executed when the user 80 specifies that the software update is to be executed when the notification information is notified in S320. If the execution of software update is not specified from 80, it is determined that the software update is not to be executed. If it is determined not to update the software, the process of this flowchart ends. If it is determined that the software should be updated, 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 in S324. Furthermore, the changing unit 250 of the ECU 100 changes the time during which information regarding software updates can be communicated with the server 70 based on the new functional information of the battery 150.

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

In S328, the notification unit 240 of the ECU 100 determines whether the vehicle 10 has any functional limitations. Notification unit 240 determines whether or not there is a functional restriction of vehicle 10 based on the functional information transmitted from server 70 in S314. If there are no functional restrictions on the vehicle 10, the process of this flowchart ends. If there is a functional restriction on the vehicle 10, the notification unit 240 notifies the user 80 of the functional restriction through the MID 170 in S330, and ends the process of this flowchart. The functional limitations may include, for example, limitations on the idle stop function of the vehicle 10. Functional limitations may include, for example, starting limitations that may occur due to a dead battery of the vehicle 10. For example, if the battery capacity of the newly installed battery 150 is smaller than the battery capacity of the regular battery, if the vehicle 10 is equipped with the regular battery, the vehicle 10 may be idle even if the idle stop function is available. You may not be able to use the stop function. In this case, the notification unit 240 can notify the user 80 that the idle stop function of the vehicle 10 is no longer available due to the software update. Furthermore, if the battery capacity of the newly installed battery 150 is lower than the standard for the vehicle 10, there is a high possibility that the vehicle 10 will not be able to be started due to the battery being exhausted. The notification unit 240 can warn the user 80 that there is a higher possibility that the vehicle 10 will not be able to be started due to a dead battery due to the software update.

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 the type information of the battery 150 through the MID 170 and the operation member included in the vehicle 10.

In the above, a mode in which the user 80 is notified through the MID 170 has been described, but the user 80 may also be notified through various user interface devices such as display audio and IVI (in-vehicle infotainment).

According to the update system 5 described above, when a non-regular battery 150 is installed in the vehicle 10 due to battery replacement, the software of the ECU 110 can be updated so that the ECU 110 can appropriately control the battery 150 by OTA. can. Furthermore, if it becomes necessary to limit the functions of the vehicle 10 due to a software update, the user 80 can be notified before and after the software update. This makes it possible to perform appropriate battery management to prevent early deterioration of the battery 150 without excessively using the non-standard battery 150.

FIG. 4 illustrates an example computer 2000 in which embodiments of the present invention may be implemented, in whole or in part. The program installed in the computer 2000 causes the computer 2000 to function as a system such as the system 20 according to the embodiment, or each part of the system, or a device such as the ECU 100, or each part of the device. or may cause each part of the device to perform an operation associated with it and/or cause a process according to an embodiment or a step of the process to be executed. Such programs may be executed by CPU 2012 to cause computer 2000 to perform certain operations associated with some or all of the processing procedures and block diagram blocks described herein.

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

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

Communication interface 2022 communicates with other electronic devices via a network. Flash memory 2024 stores programs and data used by CPU 2012 within computer 2000. ROM 2026 stores programs such as a boot program executed by computer 2000 upon activation and/or programs dependent on the computer 2000 hardware. The input/output chip 2040 also connects various input/output units such as keyboards, mice, and monitors to input/output units such as serial ports, parallel ports, keyboard ports, mouse ports, monitor ports, USB ports, HDMI ports, etc. It may be connected to input/output controller 2020 via an output port.

The program is 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 program is 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 the computer 2000 and provides coordination between the programs and the various types of hardware resources mentioned above. An apparatus or method may be configured to implement the operation or processing of information according to the use of computer 2000.

For example, when communication is executed between the computer 2000 and an external device, the CPU 2012 executes a communication program loaded into the RAM 2014 and sends communication processing to the communication interface 2022 based on the processing written in the communication program. You may give orders. The communication interface 2022 reads transmission data stored in a transmission buffer processing area provided in a recording medium such as a RAM 2014 and a flash memory 2024 under the control of the CPU 2012, transmits the read transmission data to the network, and transmits the transmission data from the network. The received data is written to a reception buffer processing area provided on the recording medium.

The CPU 2012 also causes the RAM 2014 to read all or a necessary part of a file or database stored in a storage medium such as a flash memory 2024, and executes various types of processing on the data on the RAM 2014. good. 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 a recording medium and subjected to information processing. The CPU 2012 performs various types of operations, information processing, conditional judgment, conditional branching, unconditional branching, information retrieval/information processing on the data read from the RAM 2014 as described herein and specified by the instruction sequence of the program. Various types of processing may be performed, including substitutions, etc., and the results are written back to RAM 2014. Further, the CPU 2012 may search for information in a file in a recording medium, a database, or the like. For example, if a plurality of entries are stored in a recording medium, each having an attribute value of a first attribute associated with an attribute value of a second attribute, the CPU 2012 search for an entry that matches the condition from among the multiple entries, read the attribute value of the second attribute stored in the entry, and thereby set the first attribute that satisfies the predetermined condition. An attribute value of the associated second attribute may be obtained.

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

A program that is installed on the computer 2000 and causes the computer 2000 to function as the ECU 110 may act on the CPU 2012 and the like to cause the computer 2000 to function as each part of the ECU 110. When the information processing described in these programs is read into the computer 2000, it functions as each part of the ECU 110, which is a concrete means in which software and the various hardware resources described above cooperate. Then, by realizing calculation or processing of information according to the purpose of use of the computer 2000 in this embodiment using these specific means, a unique ECU 110 according to the purpose of use is constructed.

Various embodiments have been described with reference to block diagrams and the like. In the block diagram, each block may represent (1) a stage in a process in which an operation is performed, or (2) a portion of a device responsible for performing the operation. Certain steps and portions may be provided by dedicated circuitry, programmable circuitry provided with computer readable instructions stored on a computer readable storage medium, and/or provided by a processor provided with computer readable instructions stored on a computer readable storage medium. May be implemented. Dedicated circuitry may include digital and/or analog hardware circuitry, and may include integrated circuits (ICs) and/or discrete circuits. Programmable circuits include logic AND, logic OR, logic may include reconfigurable hardware circuitry, including, for example, reconfigurable hardware circuitry;

A computer-readable storage medium may include any tangible device capable of storing instructions for execution by a suitable device such that a computer-readable storage medium with instructions stored therein may be a process step or block diagram. constitutes at least a portion of a product that includes instructions that can be executed to provide a means for performing the operations specified in the article. Examples of computer-readable storage media may include electronic storage media, magnetic storage media, optical storage media, electromagnetic storage media, semiconductor storage media, and the like. More specific examples of computer readable storage media 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 Disk Read Only Memory (CD-ROM), Digital Versatile Disk (DVD), Blu-ray Disc, Memory Stick , integrated circuit cards, and the like.

Computer-readable instructions may include assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state configuration data, or instructions such as Smalltalk®, JAVA®, C++, etc. any source code or object code written in any combination of one or more programming languages, including object-oriented programming languages such as may include.

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

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

The order of execution of each process, such as the operation, procedure, step, and stage in the apparatus, system, program, and method shown in the claims, specification, and drawings, is specifically defined as "before" or "before". It should be noted that they can be implemented in any order unless the output of the previous process is used in the subsequent process. Even if the claims, specifications, and operational flows in the drawings are explained using "first," "next," etc. for convenience, this does not mean that it is essential to carry out the operations in this order. It's not a thing.

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 Updating section 240 Notification section 250 Changing section 260 Detecting 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 in-vehicle equipment included in the vehicle based on information received from outside the vehicle, the system comprising:
a detection unit that detects that a controlled 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;
A system comprising: 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 selection control section selects the model information based on information acquired from the new battery through a power line, or selects the model information based on information obtained from the new battery through a power line, or selects a key section provided at the battery connection terminal and a key provided at the connection terminal of the new battery. The system according to claim 1 or 2, wherein the type information is selected based on information generated when the parts match. The update unit updates the software of the in-vehicle equipment with priority over turning on the ignition power after the ignition power of the vehicle is turned off,
The system includes:
The system according to any one of claims 1 to 3, further comprising a notification unit that notifies that software updating of the in-vehicle equipment is prioritized over turning on the ignition power after the ignition power of the vehicle is turned off. 5. The vehicle according to claim 1, further comprising a changing unit that changes a time during which information regarding the software update can be communicated with the server while the ignition power of the vehicle is turned off, depending on the new battery. A system according to any one of the clauses. When it is determined that the new battery is a battery of an unknown type for the vehicle based on the model information, a notification that the new battery is an unknown battery is notified before updating the software of the in-vehicle device. The system according to any one of claims 1 to 5, further comprising a notification unit that provides notification. The vehicle is capable of restarting the engine from an idle stop state in which the engine of the vehicle is stopped using electric power provided from the battery;
From claim 1, wherein the update unit updates the software of the in-vehicle device to prohibit idle stop of the vehicle when it is determined that the new battery is a type of battery that does not support idle stop. 3. The system according to any one of 3. A vehicle comprising a system according to any one of claims 1 to 7. A method for updating software of in-vehicle equipment included in a vehicle by OTA (Over-The-Air) based on information received from outside the vehicle, the method comprising:
detecting that a controlled device controlled by the in-vehicle device has been changed;
performing control to select model information of the new battery when it is detected that the battery controlled by the in-vehicle device has been replaced with a new battery;
receiving control data for controlling the new battery from a server external to the vehicle;
updating the software of the in-vehicle device so that the new battery is controlled based on the control data,
The step of performing control for selecting the new battery type information is a method in which the user selects the type information using a user terminal associated with the vehicle.

Images