In-vehicle system, in-vehicle device, and software switching method

Abstract

To prevent the increase in capacity of a memory installed on an in-vehicle device.SOLUTION: An in-vehicle device installed in a vehicle comprises: a memory in which first software for providing the user with first information, is stored; a determination unit which determines whether or not software to be executed should be switched from the first software to second software for providing the user with second information more detailed than the first information, on the basis of state information about a state of the vehicle; a requesting unit which requests an external device disposed outside the vehicle to download the second software if it is determined by the determination unit that the software to be executed, should be switched from the first software to the second software; and a switching unit which installs the second software downloaded from the external device into the memory and switches the software to be executed from the first software to the second software.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present disclosure relates to an in-vehicle system, an in-vehicle device, and a software switching method. [Background technology]

[0002] Software is installed in an on-board device mounted in a vehicle, and the on-board device realizes a specific function by executing the software (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-062909 A [Patent Document 2] JP 2018-69888 A [Patent Document 3] JP 2014-237427 A [Patent Document 4] JP 2012-111264 A Summary of the Invention [Problem to be solved by the invention]

[0004] As software becomes more functional, it becomes possible to provide users with a wider variety of information, but the size of the software also increases. The capacity of memory (ROM: Read Only, RAM: Random Access Memory) installed in an in-vehicle device is limited, and as the software size increases, the memory capacity is strained. Furthermore, the increase in software size leads to an increase in memory capacity. [Means for solving the problem]

[0005] An in-vehicle system according to one embodiment of the present disclosure includes a first in-vehicle device, a second in-vehicle device capable of communicating with the first in-vehicle device, and an external communication device capable of communicating with an external device arranged outside the vehicle, wherein the first in-vehicle device includes a memory that stores first software for providing first information to a user, a determination unit that determines whether to switch the software to be executed from the first software to second software for providing the user with second information that is more detailed than the first information based on status information regarding the status of the vehicle, a request unit that requests download of the second software to the external device via the external communication device when the determination unit determines that the software to be executed should be switched from the first software to the second software, and a switching unit that installs the second software downloaded from the external device in the memory and switches the software to be executed from the first software to the second software.

[0006] An in-vehicle device according to one embodiment of the present disclosure is an in-vehicle device mounted on a vehicle, and includes: a memory that stores first software for providing first information to a user; a determination unit that determines whether to switch the software to be executed from the first software to second software for providing the user with second information that is more detailed than the first information based on status information regarding the status of the vehicle; a request unit that requests download of the second software to an external device located outside the vehicle when the determination unit determines that the software to be executed should be switched from the first software to the second software; and a switching unit that installs the second software downloaded from the external device in the memory and switches the software to be executed from the first software to the second software.

[0007] A software switching method according to one embodiment of the present disclosure is a software switching method for switching software built into an in-vehicle device mounted on a vehicle, and includes the steps of: determining, based on status information regarding the status of the vehicle, whether to switch the software to be executed from first software for providing first information to a user to second software for providing second information to the user that is more detailed than the first information; when it is determined that the software to be executed should be switched from the first software to the second software, requesting download of the second software to an external device located outside the vehicle; and installing the second software downloaded from the external device into a memory included in the in-vehicle device, and switching the software to be executed from the first software to the second software.

[0008] The present disclosure can be realized not only as an in-vehicle device having the above-described characteristic configuration, a software switching method in which characteristic processing in the in-vehicle device is performed as steps, and an in-vehicle system including the in-vehicle device, but also as a program for causing the in-vehicle device to execute the characteristic processing, or as a semiconductor integrated circuit as part or all of the in-vehicle device. Effect of the Invention

[0009] According to the present disclosure, it is possible to provide a variety of information to a user while suppressing an increase in the memory capacity to be installed in an in-vehicle device. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a schematic diagram for explaining an example of a communication system according to an embodiment. [Diagram 2] 1 is a block diagram showing an example of a configuration of an in-vehicle system according to an embodiment; [Diagram 3] 2 is a block diagram showing an example of a configuration of an integrated ECU according to the embodiment; FIG. [Figure 4]2 is a block diagram showing an example of a configuration of an individual ECU according to the embodiment; FIG. [Diagram 5] FIG. 2 is a functional block diagram illustrating an example of functions of an integrated ECU according to the embodiment. [Figure 6] FIG. 13 illustrates an example of a priority table. [Figure 7] FIG. 13 is a diagram showing an example of a display screen of simple software. [Figure 8] FIG. 13 is a diagram showing an example of a detailed software display screen. [Figure 9] FIG. 13 is a diagram showing another example of the display screen of the simple software. [Figure 10] FIG. 13 is a diagram showing another example of the detailed software display screen. [Figure 11] 5 is a flowchart illustrating an example of a data collection process by an individual ECU according to the embodiment. [Figure 12] 5 is a flowchart illustrating an example of a software switching determination process by an integrated ECU according to the embodiment. [Figure 13] 5 is a flowchart illustrating an example of software switching processing by an integrated ECU according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] <Overview of the embodiment of the present disclosure> Below, an overview of the embodiments of the present disclosure will be listed and described.

[0012] (1) The in-vehicle system according to the present embodiment includes a first in-vehicle device, a second in-vehicle device capable of communicating with the first in-vehicle device, and an external communication device capable of communicating with an external device disposed outside the vehicle. The first in-vehicle device includes a memory that stores first software for providing first information to a user, a determination unit that determines whether to switch software to be executed from the first software to second software for providing a user with second information more detailed than the first information based on status information related to the status of the vehicle, a request unit that requests the external device to download the second software via the external communication device when the determination unit determines that the software to be executed is to be switched from the first software to the second software, and a switching unit that installs the second software downloaded from the external device in the memory and switches the software to be executed from the first software to the second software. When simple information is to be provided to a user, the first software is used. This can prevent the memory capacity of the first in-vehicle device from being overloaded. This can prevent an increase in the memory capacity of the first in-vehicle device. When detailed information is to be provided to the user, the software to be executed is switched from the first software to the second software, so that a variety of information can be provided to the user.

[0013] (2) The second in-vehicle device may include a sensor that detects a state of hardware mounted on the vehicle, and the state information may include information about the state of the hardware detected by the sensor. Using the information acquired by the sensor, it may be possible to determine whether to switch from the first software to the second software. In this way, when it is determined from the state of the hardware detected by the sensor that the hardware needs to be replaced or repaired, for example, the second software may be executed to provide the user with detailed information for replacing or repairing the hardware.

[0014] (3) The state information may include information predicting a future usage state of the hardware installed in the vehicle. Whether or not to switch from the first software to the second software can be determined in consideration of the future usage state of the hardware installed in the vehicle. In this way, when it is determined that the hardware needs to be replaced or repaired based on the predicted future usage state of the hardware, for example, the second software can be executed to provide the user with detailed information for replacing or repairing the hardware.

[0015] (4) The state information may include information about the state of the environment around the vehicle. Whether or not to switch from the first software to the second software can be determined in consideration of the state of the environment around the vehicle. In this way, when it is determined from the state of the environment around the vehicle that, for example, hardware needs to be replaced or repaired, the second software can be executed to provide the user with detailed information for replacing or repairing the hardware.

[0016] (5) The determination unit may determine whether to switch the software to be executed from the first software to the second software based on a priority assigned to a state of an environment around the vehicle. For example, when the priority is higher than a reference level, the software to be executed may be switched from the first software to the second software.

[0017] (6) When an instruction to switch the software to be executed from the first software to the second software is given by a user, the determination unit may determine that the software to be executed is to be switched from the first software to the second software. This makes it possible to switch the software to be executed from the first software to the second software in response to the user's instruction.

[0018] (7) The determination unit may determine whether to switch the software to be executed from the first software to the second software based on a priority assigned to the second software. A priority may be assigned to the second software according to the importance of information provided to a user by the second software. For example, when the priority is higher than a reference level, the first software may be switched to the second software.

[0019] (8) The priority may be associated with a type of the second software and a type of a state of the environment around the vehicle. For example, the priority may be determined according to the importance of information that the second software provides to the user and the severity of the state of the environment around the vehicle.

[0020] (9) The state information may include information about a communication state of the external communication device. For example, when the communication state of the external communication device is good, the second software can be downloaded, and when the communication state of the external communication device is bad, downloading of the second software can be avoided.

[0021] (10) The first information may be text information, and the second information may include image information. By making the first information simple text information, the size of the first software can be reduced. By including image information in the second information, detailed information in the form of images can be provided to the user.

[0022] (11) The first information may be text information, and the second information may include audio information. By making the first information simple text information, the size of the first software can be reduced. By including audio information in the second information, detailed information can be provided to the user by audio.

[0023] (12) The first information may be information indicating an abnormality in hardware mounted on the vehicle, and the second information may include information indicating an abnormality in the hardware mounted on the vehicle and information indicating a countermeasure to the abnormality. When an abnormality occurs in the hardware, the first software can notify a user of the occurrence of the abnormality. Furthermore, the size of the first software can be reduced. The second software can not only notify the user of the occurrence of the abnormality, but also present a countermeasure to the abnormality to the user.

[0024] (13) The in-vehicle device according to the present embodiment is an in-vehicle device mounted on a vehicle, and includes a memory that stores first software for providing first information to a user, a determination unit that determines whether to switch the software to be executed from the first software to second software for providing the user with second information more detailed than the first information based on status information related to the status of the vehicle, a request unit that requests download of the second software to an external device disposed outside the vehicle when the determination unit determines that the software to be executed is to be switched from the first software to the second software, and a switching unit that installs the second software downloaded from the external device in the memory and switches the software to be executed from the first software to the second software. When simple information is to be provided to the user, the first software is used. Therefore, it is possible to suppress pressure on the memory capacity of the first in-vehicle device. Therefore, it is possible to suppress an increase in the memory capacity mounted in the first in-vehicle device. When detailed information is to be provided to the user, the software to be executed is switched from the first software to the second software. Therefore, it is possible to provide a variety of information to the user.

[0025] (14) The software switching method according to the present embodiment is a software switching method for switching software incorporated in an in-vehicle device mounted on a vehicle, and includes the steps of: determining whether to switch the software to be executed from a first software for providing a user with first information to a second software for providing a user with second information more detailed than the first information, based on status information on the status of the vehicle; requesting an external device disposed outside the vehicle to download the second software when it is determined that the software to be executed is to be switched from the first software to the second software; and installing the second software downloaded from the external device into a memory included in the in-vehicle device, and switching the software to be executed from the first software to the second software. When simple information is to be provided to the user, the first software is used. Therefore, it is possible to suppress pressure on the memory capacity of the first in-vehicle device. Therefore, it is possible to suppress an increase in the memory capacity mounted in the first in-vehicle device. When detailed information is to be provided to the user, the software to be executed is switched from the first software to the second software. Therefore, it is possible to provide a variety of information to the user.

[0026] <Details of the embodiment of the present disclosure> Hereinafter, the details of the embodiments of the present invention will be described with reference to the drawings. Note that at least some of the embodiments described below may be combined in any desired manner.

[0027] [1. Communication Systems] FIG. 1 is a schematic diagram for explaining an example of a communication system according to the present embodiment.

[0028] The communication system is a system for providing information about the vehicle to a passenger (user) of the vehicle 10. The communication system includes the vehicle 10, a database 40, and a server 50. The vehicle 10 is equipped with an on-board system as described below.

[0029] The vehicle 10 is capable of communicating with devices external to the vehicle by wireless communication. The vehicle 10 is equipped with a wireless communication terminal that complies with, for example, a fifth generation mobile communication system (5G) or a fourth generation mobile communication system (4G), and is capable of wireless communication with a base station 20. The base station 20 is connected to the Internet 30. The database 40 and the server 50 are also connected to the Internet 30. With this configuration, the vehicle 10 and the database 40 can communicate with each other, and the vehicle 10 and the server 50 can communicate with each other.

[0030] The database 40 stores installation data of detailed software for providing a user with detailed information about the vehicle 10. The database 40 can transmit the installation data of the detailed software to the vehicle 10. The database 40 is an example of an "external device." The detailed software is an example of a "second software."

[0031] The server 50 can transmit to the vehicle 10 information used to determine whether or not to switch the software to be executed from the simple software to the detailed software. The simple software is software for providing the user with simple information about the vehicle 10. The simple software is an example of "first software." The server 50 can transmit to the vehicle 10, for example, weather information indicating current weather conditions, weather forecast information indicating future weather conditions, and road condition information indicating road conditions.

[0032] [2. In-vehicle systems] FIG. 2 is a block diagram showing an example of the configuration of an in-vehicle system according to this embodiment.

[0033] This implementation form The in-vehicle system 100 includes an integrated ECU 200 and individual ECUs 300A, 300B, 300C, and 300D. The integrated ECU 200 and the individual ECUs 300A, 300B, 300C, and 300D are connected to each other by communication cables.

[0034] The integrated ECU 200 controls the entire vehicle 10 and provides the user with information related to the vehicle 10. The integrated ECU 200 is capable of executing simple software or detailed software. The integrated ECU 200 is an example of a second in-vehicle device.

[0035] The individual ECUs 300A, 300B, 300C, and 300D are disposed in various parts of the vehicle 10. The individual ECUs 300A, 300B, 300C, and 300D individually control the hardware of the various parts of the vehicle 10 and monitor the state of the hardware of the various parts of the vehicle 10. For example, the individual ECU 300A is a device for monitoring the state of tires. The individual ECU 300B is a device for controlling a braking device and monitoring the state of the braking device. The individual ECU 300C is a device for controlling a door and monitoring the state of the door. The individual ECU 300D is a device for controlling a battery for driving the vehicle and monitoring the state of the battery. In the following description, the individual ECUs 300A, 300B, 300C, and 300D are collectively referred to as "individual ECUs 300."

[0036] The integrated ECU 200 is connected to each of the individual ECUs 300A, 300B, 300C, and 300D via an in-vehicle bus such as a CAN (Controller Area Network) bus. The integrated ECU 200 can communicate with each of the individual ECUs 300A, 300B, 300C, and 300D. The individual ECU 300 is an example of a first in-vehicle device.

[0037] The integrated ECU 200 is connected to a display device 250. The display device 250 includes, for example, a liquid crystal panel or an OEL (organic electroluminescence) panel. The display device 250 can display information in the form of characters or images. The integrated ECU 200 can control the display device 250 to cause the display device 250 to display information (character information, image information).

[0038] The integrated ECU 200 is connected to an input device 260. The input device 260 includes, for example, a capacitive or pressure-sensitive touch pad overlaid on the display device 250. A user can input information to the integrated ECU 200 by operating the input device 260.

[0039] The integrated ECU 200 is connected to a speaker 270. The speaker 270 is capable of outputting audio. The integrated ECU 200 controls the speaker 270 to cause the speaker 270 to output audio information.

[0040] The integrated ECU 200 is connected to an external communication device 500. The external communication device 500 is, for example, a wireless communication terminal conforming to 5G or 4G. The external communication device 500 can communicate with a database 40 and a server 50. The external communication device 500 relays communication between the integrated ECU 200 and the database 40 and the server 50.

[0041] A sensor 400 is connected to each of the individual ECUs 300A, 300B, 300C, and 300D. The sensor 400 detects the state of the hardware of the vehicle 10. The sensor 400 outputs data indicating a detection value (hereinafter, referred to as "sensor data"). For example, the sensor 400 connected to the individual ECU 300A includes an air pressure sensor that measures the air pressure of the tires and a temperature sensor that measures the temperature of the tires. For example, the sensor 400 connected to the individual ECU 300A may include a wear sensor that detects the wear degree of the tires. For example, the sensor 400 connected to the individual ECU 300B includes a wear sensor that detects the wear degree of the brake pads. For example, the sensor 400 connected to the individual ECU 300C includes a sensor that detects the open / close state of a door. For example, the sensor 400 connected to the individual ECU 300D includes a voltage sensor that measures the voltage of a battery and a temperature sensor that detects the temperature of the battery. The individual ECUs 300A, 300B, 300C, and 300D can transmit the sensor data output from the sensor 400 to the integrated ECU 200.

[0042] The individual ECUs 300A, 300B, 300C, and 300D may be connected to actuators for operating hardware. For example, the individual ECU 300B may be connected to a motor for operating a braking device. For example, the individual ECU 300C may be connected to a motor for opening and closing a door.

[0043] [3. Integrated ECU Configuration] 3 is a block diagram showing an example of the configuration of the integrated ECU according to this embodiment. The integrated ECU 200 includes a processor 201, a non-volatile memory 202, a volatile memory 203, a first communication interface (I / F) 204, a second communication I / F 205, a graphic processing circuit 206, an input / output unit 207, and an audio processing circuit 208.

[0044] The volatile memory 203 is, for example, a semiconductor memory such as a static random access memory (SRAM) or a dynamic random access memory (DRAM). The non-volatile memory 202 is, for example, a flash memory, a hard disk, a read only memory (ROM), etc. The non-volatile memory 202 stores a control program 209 and simple software 210, which are computer programs, and data used to execute these software. The integrated ECU 200 can install the detailed software 211 in the non-volatile memory 202 using installation data of the detailed software 211 downloaded from the database 40. The integrated ECU 200 is configured with a computer, and each function of the integrated ECU 200 is realized by executing the control program 209, simple software 210, and detailed software 211, which are computer programs stored in a storage device of the computer.

[0045] The software (control program 209, simple software 210, detailed software 211) includes, for example, program modules. A program module is a software component for realizing a partial function of the software. Software is configured by combining a plurality of program modules.

[0046] The simple software 210 is already installed in the non-volatile memory 202. That is, the simple software 210 is installed in the non-volatile memory 202 in an initial state. A plurality of types of simple software 210 are installed in the non-volatile memory 202. The plurality of simple software 210 include, for example, software for notifying the user of an abnormality in tire air pressure, and software for notifying that the cold climate function of the vehicle 10 (for example, a window deicer) has been turned on. The simple software 210 is not limited to these, and may include software for notifying the user of information other than those mentioned above.

[0047] The detail software 211 is not installed in the non-volatile memory 202 in the initial state. In other words, the detail software 211 is software that is additionally installed in the non-volatile memory 202. The database 40 stores installation data for multiple types of detail software 211. The integrated ECU 200 can download installation data for a specific type of detail software 211 (the type of detail software 211 requested by the integrated ECU 200) from the database 40 and install the specific type of detail software 211 in the non-volatile memory 202.

[0048] The control program 209 is software for determining whether or not to switch the software to be executed from the simple software 210 to the detailed software 211. When the processor 201 executes the control program 209, the integrated ECU 200 can execute a software switching determination process as described below. The control program 209 manages the installation of the detailed software 211. That is, the control program 209 downloads installation data for the detailed software 211 from the database 40, and installs the detailed software 211 in the non-volatile memory 202 using the installation data. When the detailed software 211 is installed, the control program 209 switches the software to be executed from the simple software 210 to the detailed software 211.

[0049] The processor 201 is, for example, a CPU (Central Processing Unit). However, the processor 201 is not limited to a CPU. The processor 201 may be a GPU (Graphics Processing Unit). The processor 201 is configured to be able to execute a computer program. However, the processor 201 may include, for example, an ASIC (Application Specific Integrated Circuit) in part, or may include a programmable logic device such as a gate array or an FPGA (Field Programmable Gate Array) in part.

[0050] Each of the first communication I / F 204 and the second communication I / F 205 is, for example, a CAN interface. The first communication I / F 204 is connected to each of the individual ECUs 300A, 300B, 300C, and 300D via a communication bus. The integrated ECU 200 can communicate with the individual ECUs 300A, 300B, 300C, and 300D through the first communication I / F 204.

[0051] The second communication I / F 205 is connected to the external communication device 500 via a communication bus. The integrated ECU 200 can communicate with the external communication device 500 via the second communication I / F 205.

[0052] The graphics processing circuit 206 is connected to the display device 250 and controls the display on the display device 250. The graphics processing circuit 206 includes, for example, a GPU and a VRAM (Video RAM). The graphics processing circuit 206 holds data to be displayed on the display device 250 in the VRAM, periodically reads one frame of video data from the VRAM, and generates a video signal. The generated video signal is output to the display device 250, and a video is displayed on the display device 250. The function of the graphics processing circuit 206 may be included in the processor 201. A part of the area of ​​the volatile memory 203 may be used as the VRAM.

[0053] The input / output unit (I / O) 207 is connected to the input device 260. Information given by the user to the input device 260 is given to the processor 201 through the I / O 207. The audio processing circuit 208 is connected to the speaker 270, and controls the audio output from the speaker 270.

[0054] [4. Individual ECU configuration] 4 is a block diagram showing an example of the configuration of an individual ECU according to this embodiment. The individual ECU 300 includes a processor 301, a non-volatile memory 302, a volatile memory 303, a communication I / F 304, and an input / output I / F (I / O) 305.

[0055] The volatile memory 303 is, for example, a semiconductor memory such as an SRAM or a DRAM. The non-volatile memory 302 is, for example, a flash memory, a hard disk, a ROM, etc. The non-volatile memory 302 stores a control program 306, which is a computer program, and data used for executing the control program 306. The individual ECU 300 is configured with a computer, and each function of the individual ECU 300 is realized by executing the control program 306, which is a computer program stored in a storage device of the computer.

[0056] The control program 306 is software for monitoring the state of some of the hardware of the vehicle 10 and transmitting data related to the state of the hardware to the integrated ECU 200. The control program 306 may have a function of controlling some of the hardware of the vehicle 10.

[0057] The processor 301 is, for example, a CPU. However, the processor 301 is not limited to a CPU. The processor 301 may be a GPU. The processor 301 may be, for example, an ASIC, or a programmable logic device such as a gate array or an FPGA. In this case, the ASIC or the programmable logic device is configured to be able to execute the same process as the control program 306.

[0058] The communication I / F 304 is, for example, a CAN interface. The communication I / F 304 is connected to the integrated ECU 200 and the other individual ECUs 300 via a communication bus. The individual ECUs 300 can communicate with the integrated ECU 200 via the communication I / F 304.

[0059] The I / O 305 is connected to the sensor 400. The I / O 305 receives sensor data output from the sensor 400. The I / O 305 may be connected to an actuator provided in the vehicle 10. The I / O 305 can output a control signal to the actuator.

[0060] Even if the hardware differs depending on the vehicle, the individual ECU 300 transmits data of common specifications to the integrated ECU 200. For example, even if the specifications of a temperature sensor that measures the temperature of a tire differ between vehicle A and vehicle B, the individual ECU 300 processes sensor data of the temperature sensor and generates data of the same specifications (hereinafter, referred to as "processed data"). The individual ECU 300 transmits the generated processed data to the integrated ECU 200. As a specific example, a case will be described in which the sampling rate of the temperature sensor of vehicle A differs from the sampling rate of the temperature sensor of vehicle B. The individual ECU 300 mounted on vehicle A performs processing such as calculating a moving average value or a moving median value of the sensor data output from the temperature sensor, and generates the processed data. The individual ECU 300 mounted on vehicle A transmits the processed data to the integrated ECU 200 at a predetermined time interval. The individual ECU 300 mounted on vehicle B also performs processing such as calculating a moving average value or a moving median value of the sensor data output from the temperature sensor, and generates the processed data. The individual ECU 300 mounted on the vehicle B transmits the processing data to the integrated ECU 200 at the same time intervals as the time intervals at which the individual ECU 300 mounted on the vehicle A transmits the processing data.

[0061] Further, even if the actuators differ depending on the vehicles, the individual ECU 300 receives a command of common specifications from the integrated ECU 200 and generates a control signal adapted to the actuator connected to the individual ECU 300 based on the command. The individual ECU 300 outputs the generated control signal to the actuator to control the actuator. As a specific example, a case will be described in which a motor for a power window of a vehicle A is different from a motor for a power window of a vehicle B. The individual ECU 300 mounted on the vehicle A generates a control signal adapted to the specifications of the motor mounted on the vehicle A based on the command received from the integrated ECU 200. The individual ECU 300 mounted on the vehicle A outputs the generated control signal to the motor to control the power window. The same command as that of the individual ECU 300 mounted on the vehicle A is transmitted from the integrated ECU 200 to the individual ECU 300 mounted on the vehicle B. The individual ECU 300 mounted on the vehicle B generates a control signal adapted to the specifications of the motor mounted on the vehicle B based on the received command. The individual ECU 300 mounted on the vehicle B outputs the generated control signal to a motor to control the power window.

[0062] [5. Functions of the integrated ECU] FIG. 5 is a functional block diagram showing an example of functions of the integrated ECU according to the present embodiment.

[0063] When the processor 201 executes the control program 209, the functions of an acquisition unit 221, a determination unit 222, a request unit 223, a reception unit 224, a switching unit 225, and an uninstallation unit 226 are realized.

[0064] The acquisition unit 221 acquires status information regarding the status of the vehicle 10. The status information may include information regarding the status of the hardware detected by the sensor 400.

[0065] The individual ECU 300 receives the sensor data output from the sensor 400 and performs a predetermined process on the sensor data. For example, the individual ECU 300 processes the detection value of the sensor 400 and generates processed data. The processed data is an example of information related to the state of the hardware.

[0066] The type of hardware installed in the vehicle is an example of the state of the vehicle 10. As a specific example, a case will be described in which the sensor 400 is an RFID reader and an RF tag with tire information written thereon is embedded in the tire. Information indicating that the tire is a summer tire is written in the RF tag of a summer tire, and information indicating that the tire is a studless tire is written in the RF tag of a studless tire. The sensor 400 reads information from the RF tag of the tire of the vehicle 10, and the individual ECU 300 transmits the information (or information obtained by processing the information) to the integrated ECU 200. The information indicating studless tires read from the RF tag indicates the state of the vehicle 10, that is, that studless tires are mounted on the vehicle 10.

[0067] The state information may include information predicting a future use state of the hardware. For example, the acquisition unit 221 can predict a future use state from the use history of the hardware of the vehicle 10. As a specific example, prediction of a future use state of a tire will be described. The sensor 400 detects attachment / detachment of a tire to the vehicle 10. When the sensor 400 detects a tire change, the individual ECU 300 transmits state information indicating a state of the vehicle 10 in which the tire has been changed to the integrated ECU 200. The integrated ECU 200 manages the elapsed time since the previous tire change, and estimates the time when the next tire change is required. The acquisition unit 221 acquires the estimated time for the next tire change as information predicting a future use state.

[0068] The state information may include information on the state of the environment around the vehicle 10 (hereinafter referred to as "environmental state information"). The environmental state information may include, for example, position information of the vehicle 10, weather information indicating the weather at the location where the vehicle 10 is located, weather forecast information at the location where the vehicle 10 is located, temperature information indicating the temperature at the location where the vehicle 10 is located, etc. The acquisition unit 221 can receive the environmental state information from the server 50.

[0069] The determining unit 222 determines whether or not to switch the software to be executed from the simple software 210 to the detailed software 211 based on the state information.

[0070] For example, the determining unit 222 can determine whether or not to switch the software to be executed from the simple software 210 to the detailed software 211 using information indicating the state of the hardware.

[0071] (Example 1) This example is an example of software switching judgment for tire replacement. In this example, the state information includes information indicating the air pressure of the tire. For example, the sensor 400 is an air pressure sensor that measures the air pressure of the tire. The individual ECU 300 can process the sensor data output from the sensor 400 and judge whether or not it is time to replace the tire. For example, the time when the tire needs to be replaced is when the air pressure of the tire of company A becomes less than 80%, and when the air pressure of the tire of company B becomes less than 60% and the time decrease rate of the air pressure becomes less than a specific value. In this way, the nominal value of the time when the tire needs to be replaced differs depending on the manufacturer, but the individual ECU 300 handles such hardware differences. That is, the individual ECU 300 applies the air pressure of the sensor data to the nominal value of the tire manufacturer and judges whether or not it is time to replace the tire. The individual ECU 300 transmits the judgment result of whether or not it is time to replace the tire to the integrated ECU 200 as state information. The determination unit 222 uses the result of the determination as to whether it is time to change tires to determine whether or not to switch the software to be executed from the simple software 210 to the detailed software 211. If it is time to change tires, the determination unit 222 determines that the software to be executed should be switched from the simple software 210 to the detailed software 211 in order to provide the user with detailed information regarding changing tires. If it is not time to change tires, the determination unit 222 determines that the software to be executed should not be switched from the simple software 210 to the detailed software 211.

[0072] (Example 2) This example is another example of software switching judgment for tire change. In this example, the status information used for the judgment includes the number of years since the tire was installed (A1), the distance traveled since the tire was installed (A2), and the past vehicle usage status (user's driving history) (A3). A certain user drives the vehicle 10 3 km on weekdays to go to work and home, and drives the vehicle 10 4 km on weekends to go shopping. In this case, the mileage of the vehicle 10 in one month is 3 (km) x 23 (days) + 4 (km) x 6 (days) = 93 (km). This calculation result is used as A3. The judgment unit 222 calculates the following formula (1). A = A1 × a + A2 × b + A3 × c … (1) a, b, and c are weight coefficients. The determination unit 222 compares the calculation result A of the above formula with a threshold value N, and determines whether or not to switch the software to be executed from the simple software 210 to the detailed software 211. If A is greater than N, a tire change is necessary. In this case, the determination unit 222 determines that the software to be executed should be switched from the simple software 210 to the detailed software 211 in order to provide the user with detailed information regarding the tire change. If A is equal to or less than N, the determination unit 222 determines that the software to be executed should not be switched from the simple software 210 to the detailed software 211.

[0073] (Example 3) This example is yet another example of software switching judgment for tire replacement. In this example, the status information used for the judgment includes the number of years since the tire was fitted (A1), the distance traveled since the tire was fitted (A2), and the future vehicle usage status (user's driving plan) (B3). B3 is the long-distance driving distance (e.g., 100 km or more) of the vehicle 10 planned for the next month. The judgment unit 222 judges whether or not to switch the software to be executed from the simple software 210 to the detailed software 211 using the following four conditions. Condition 3-1: A1×B3 is greater than or equal to threshold value N1. Condition 3-2: A2×B3 is greater than or equal to threshold value N2. Condition 3-3: A1 is 80% or more of the catalog value of the tire's usable life. Condition 3-4: A2 is 80% or more of the tire's catalog value for the mileage. When any one or more of the conditions 3-1, 3-2, 3-3, and 3-4 are satisfied, the determination unit 222 determines that the software to be executed should be switched from the simple software 210 to the detailed software 211 in order to provide the user with detailed information regarding tire replacement. When all of the conditions 3-1, 3-2, 3-3, and 3-4 are not satisfied, the determination unit 222 determines that the software to be executed should not be switched from the simple software 210 to the detailed software 211.

[0074] (Example 4) This example is an example of software switching judgment for changing to studless tires. In this example, the status information used includes whether or not there is snow currently (C1), whether or not the vehicle 10 is currently equipped with studless tires (C2), whether or not a certain amount of snow is forecast for the next two weeks (C3), the date (C4), the temperature (C5), and the weather (C6).

[0075] For example, the priority level assigned to each of the following days from the present is used for C4. For example, 1 day later: 99(%), 2 days later: 96(%), 3 days later: 92(%), 4 days later: 90(%), ..., 10 days later: ( 60% ) , after 11 days: ( 57% ) Priorities are given as follows:

[0076] C5 uses a priority assigned to each minimum temperature in the weather forecast. For example, the following priority is given: below -10°C: 99(%), between -10°C and -5°C: 90(%), between -5°C and 0°C: 85(%), between 0°C and 3°C: 80(%), between 3°C and 5°C: 65(%), between 5°C and 8°C: 50(%), and above 8°C: 0(%).

[0077] C6 uses a priority assigned to each type of weather in the weather forecast. For example, the priorities are given as follows: rain: 70(%), sunny: 50(%), light snow: 85(%), snow: 90(%), heavy snow: 100(%).

[0078] The determination unit 222 determines whether or not to switch the software to be executed from the simple software 210 to the detailed software 211, using the following four conditions. Condition 4-1: C1 is YES and C2 is YES. Condition 4-2: C2 is YES and C3 is YES. Condition 4-3: C2 is YES and C4×C5 is equal to or greater than a threshold value N3. Condition 4-4: C2 is YES and C4×C6 is equal to or greater than a threshold value N4. When any one or more of the conditions 4-1, 4-2, 4-3, and 4-4 are satisfied, the determination unit 222 determines that the software to be executed should be switched from the simple software 210 to the detailed software 211 in order to provide the user with detailed information regarding changing to studless tires. ,4-4 If none of the above conditions is met, the determining unit 222 determines not to switch the software to be executed from the simple software 210 to the detailed software 211.

[0079] In this example, the state information may also include snowfall conditions (C7) throughout the year (for example, last year). Priorities assigned to each month are used for C7, for example. For example, in City A, priorities are given as follows: November: 30%, December: 60%, January: 60%, February: 80%, March: 80%, others: 0%. For example, in City B, priorities are given as follows: October: 10%, November: 90%, December: 90%, January: 70%, February: 70%, others: 0%. For example, in Condition 4-3, "C4×C5 is equal to or greater than threshold N3" can be replaced with "C4×C5×C7 is equal to or greater than threshold N3", and in Condition 4-4, "C4×C6 is equal to or greater than threshold N4" can be replaced with "C4×C6×C7 is equal to or greater than threshold N4".

[0080] The determination unit 222 can determine whether or not to switch the software to be executed from the simple software 210 to the detailed software 211 based on the priority assigned to the detailed software 211. The information provided to the user by the detailed software 211 includes information of high importance related to danger to the user, accidents of the vehicle 10, etc., and information that is useful but low in importance. For example, information for notifying the user of abnormal tire pressure and information for notifying the user of the need to change to studless tires are of high importance, and traffic congestion information is of low importance. The detailed software 211 may be assigned a priority according to the information to be notified to the user. For example, the detailed software 211 that notifies the user of abnormal tire pressure and the detailed software 211 that notifies the user of the need to change to studless tires are assigned a priority of "high", and the detailed software 211 that provides the user with traffic information is assigned a priority of "low". The determination unit 222 can determine whether or not to switch the software by combining the state information and the priority of the detailed software 211.

[0081] Priorities may be associated with the types of the detailed software 211 and the types of environmental conditions around the vehicle 10. For example, the determination unit 222 can use a priority table that indicates the correspondence between the types of the detailed software 211 and the types of environmental conditions around the vehicle 10. FIG. 6 is a diagram showing an example of the priority table. The rows of the table indicate the types (A, B, C, D) of the detailed software 211, and the columns of the table indicate the types (1, 2, 3, 4) of environmental conditions. In the priority table 230, a priority is assigned to each combination of the types A, B, C, D of the detailed software 211 and the types 1, 2, 3, 4 of environmental conditions. The determination unit 222 identifies the types of the detailed software 211 and the types of environmental conditions that are the targets of the switching determination, and determines the priority by referring to the priority table 230. The priority table 230 is stored in the non-volatile memory 202.

[0082] When an instruction to switch the software to be executed from the simple software 210 to the detailed software 211 is given by the user, the determination unit 222 may determine that the software to be executed is switched from the simple software 210 to the detailed software 211. For example, in the above example 1, when it is time to change tires, the determination unit 222 may display a screen (e.g., a screen including an instruction button) on the display device 250, in which the user can input an instruction to switch from the simple software 210 to the detailed software 211 in order to provide detailed information for changing tires. When the user inputs an instruction to switch the software to be executed from the simple software 210 to the detailed software 211 through the screen to the input device 260 connected to the integrated ECU 200, the determination unit 222 can determine that the software to be executed is switched from the simple software 210 to the detailed software 211. When the above instruction is not input from the user to the integrated ECU 200, the determination unit 222 can determine that the software to be executed is not switched from the simple software 210 to the detailed software 211.

[0083] Returning to FIG. 5, the state information may include information about the communication state of the external communication device 500. If the communication state of the external communication device 500 is good, the integrated ECU 200 can access the database 40 and the server 50. If the communication state of the external communication device 500 is poor, it is difficult for the integrated ECU 200 to access the database 40 and the server 50. In this way, the communication state of the external communication device 500 represents one state of the vehicle 10. The information about the communication state of the external communication device 500 is, for example, a received signal strength indicator (RSSI). The determination unit 222 can compare, for example, the RSSI with a threshold value and determine whether or not to switch the software to be executed from the simple software 210 to the detailed software 211. For example, if the RSSI is equal to or greater than the threshold value, the determination unit 222 can determine that the software to be executed is to be switched from the simple software 210 to the detailed software 211. For example, when the RSSI is less than a threshold, the determination unit 222 can determine not to switch the software to be executed from the simple software 210 to the detailed software 211. Furthermore, when the RSSI is less than a threshold, the determination unit 222 can suspend downloading of the installation data for the detailed software 211.

[0084] When the determining unit 222 determines that the software to be executed is to be switched from the simple software 210 to the detailed software 211, the requesting unit 223 requests the database 40 to download the installation data for the detailed software 211.

[0085] The database 40 downloads the installation data of the detailed software 211 in response to the request from the request unit 223. The receiving unit 224 receives the installation data of the detailed software 211.

[0086] The switching unit 225 installs the detailed software 211 in the non-volatile memory 202 using the installation data downloaded from the database 40. The switching unit 225 switches the software to be executed from the simple software 210 to the detailed software 211. For example, the switching unit 225 ends the simple software 210 and starts up the detailed software 211.

[0087] The information provided by the simple software 210 to the user is text information. That is, the simple software 210 causes the display device 250 to display the text information. The information provided by the detailed software 211 to the user includes image information. That is, the detailed software 211 causes the display device to display information including image information.

[0088] The information provided by the simple software 210 to the user is information indicating an abnormality in the hardware mounted on the vehicle 10. For example, the information provided by the simple software 210 to the user indicating an abnormality in the hardware mounted on the vehicle 10 is text information. The information provided by the detailed software 211 to the user includes information indicating an abnormality in the hardware mounted on the vehicle 10 and information indicating a countermeasure to the abnormality. For example, the information provided by the detailed software 211 to the user indicating an abnormality in the hardware mounted on the vehicle 10 may be text information, image information, or audio information. The information indicating a countermeasure to the abnormality may also be text information, image information, or audio information.

[0089] Fig. 7 is a diagram showing an example of a display screen of the simple software, and Fig. 8 is a diagram showing an example of a display screen of the detailed software. The examples shown in Figs. 7 and 8 are display screens of the simple software 210 and the detailed software 211 for notifying a user of an abnormality in tire air pressure. When an abnormality in tire air pressure is detected, the simple software 210 causes the display device 250 to display a display screen 600A. The display screen 600A includes text information 601. The text information 601 is information indicating an abnormality in a tire, such as "Tire pressure is low."

[0090] Referring to FIG. 8, when an abnormality in tire pressure is detected, the detail software 211 causes the display device 250 to display a display screen 600B. The display screen 600B includes image information 602 and text information 603. The image information 602 includes a diagram of the vehicle 10 viewed from above and text information on the air pressure and temperature of five tires including the spare tire. The image information 602 is information indicating the tire abnormality by using numerical values. The text information 603 indicates the estimated time for tire replacement. The estimated time for tire replacement is an example of a countermeasure for eliminating the abnormality in tire pressure. As yet another example, the display screen 600B of the detail software 211 may include text information, image information, or a combination thereof that explains how to adjust tire pressure, or may include a map or address indicating the location of a shop where tire pressure adjustment is performed.

[0091] In addition to the above-mentioned display screen 600B, the detail software 211 may output audio information for notifying the user of an abnormality in tire air pressure from the speaker 270. Note that the detail software 211 may cause the display device 250 to display the display screen 600B including image information without outputting audio information to the speaker 270, or may cause the display device 250 to output audio information without displaying the display screen 600B including image information (for example, cause the display device 250 to display a display screen including no image information and including text information regarding an abnormality in tire air pressure).

[0092] Fig. 9 is a diagram showing another example of the display screen of the simple software, and Fig. 10 is a diagram showing another example of the display screen of the detailed software. The examples shown in Figs. 9 and 10 are display screens of the simple software 210 and the detailed software 211 for notifying the user of information necessary for driving the vehicle 10 in cold regions. When it is determined that the vehicle 10 is in a cold region based on temperature, weather information, location information, etc., the simple software 210 causes the display device 250 to display a display screen 610A. The display screen 610A includes text information 611. The text information 611 is "Cold region function has been turned ON."

[0093] 10, when it is determined that the vehicle 10 is in a cold region, the detail software 211 causes the display device 250 to display a display screen 610B. The display screen 610B includes image information 612. The image information 612 is a map showing locations where slip accidents are likely to occur. As still another example, the display screen 610B of the detail software 211 may include information showing whether or not studless tires are installed, information suggesting changing to studless tires, text information explaining how to change tires, image information, or a combination of these, information suggesting the concentration ratio of antifreeze, etc.

[0094] In addition to the above-mentioned display screen 610B, the detail software 211 may output audio information for notifying the user that, for example, changing to studless tires is necessary from the speaker 270. Note that the detail software 211 may cause the display device 250 to display the display screen 610B including image information without outputting audio information to the speaker 270, or may cause the display device 250 to output audio information without displaying the display screen 610B including image information (for example, cause the display device 250 to display a display screen including no image information and including text information indicating that the cold climate function is ON).

[0095] 5, the uninstallation unit 226 uninstalls unnecessary detailed software 211 from the non-volatile memory 202. For example, when the remaining capacity of the non-volatile memory 202 is less than a reference value, a part of the installed detailed software 211 is uninstalled. The target of uninstallation is selected based on the priority of the detailed software 211, for example.

[0096] [6. Operation of individual ECUs] The operation of the in-vehicle system 100 according to this embodiment will be described below. The processor 301 of the individual ECU 300 executes the control program 306 to perform data collection processing as described below. Fig. 11 is a flowchart showing an example of the data collection processing by the individual ECU according to this embodiment.

[0097] The sensor 400 detects a state of hardware and outputs sensor data indicating a detected value. The individual ECU 300 acquires the sensor data output from the sensor 400 (step S101).

[0098] The processor 301 processes the sensor data to generate processed data (step S102). The processing is a process of calculating a moving average value, a moving median value, or the like of the detected values.

[0099] The processor 301 transmits the generated processing data to the integrated ECU 200 (step S103). After that, the processor 301 returns to step S101. As a result, the repetitive processing data is generated and transmitted to the integrated ECU 200.

[0100] [7. Operation of the integrated ECU] The processor 201 of the integrated ECU 200 executes the control program 209 to perform a software switching determination process as described below. Fig. 12 is a flowchart showing an example of the software switching determination process performed by the integrated ECU according to this embodiment.

[0101] As described above, the individual ECU 300 transmits the processing data. Furthermore, the integrated ECU 200 requests the server 50 for environmental state information such as weather information, weather forecast information, and temperature information. The server 50 transmits the environmental state information in response to the request from the integrated ECU 200. The integrated ECU 200 receives the processing data and the environmental state information (step S201).

[0102] Based on the processed data and the environmental condition information, the processor 201 determines the state of the hardware installed in the vehicle 10 (whether the tires are underinflated, the type of tires installed on the vehicle 10, etc.) and the state of the environment surrounding the vehicle 10 (current weather conditions, future weather conditions, current temperature, etc.) (step S202).

[0103] The processor 201 determines whether or not to switch the software to be executed from the simple software 210 to the detailed software 211 based on the determined state of the vehicle 10 (step S203).

[0104] If it is determined that the software should not be switched (NO in step S203), the processor 201 proceeds to step S208.

[0105] If it is determined that the software is to be switched (YES in step S203), the processor 201 inquires about the communication state (RSSI) of the external communication device 500. The processor 201 determines whether or not the installation data of the detailed software 211 can be downloaded based on the RSSI (step S204).

[0106] If it is determined that the download of the installation data of the detailed software 211 is not possible (NO in step S204), the processor 201 suspends the download of the installation data of the detailed software 211 and reserves the download of the installation data (step S205). After reserving the download of the installation data, the processor 201 proceeds to step S208.

[0107] If it is determined that the installation data of the detailed software 211 can be downloaded (YES in step S204), the processor 201 requests the database 40 to download the installation data of the detailed software 211 (step S206).

[0108] After downloading the installation data, the processor 201 executes a software switching process (step S207).

[0109] FIG. 13 is a flowchart showing an example of software switching processing by the integrated ECU according to the present embodiment.

[0110] The processor 201 requests the database 40 for installation data of the detailed software 211 (step S211). In response to the request, the database 40 downloads the installation data of the detailed software 211. The integrated ECU 200 receives the installation data (step S212).

[0111] The processor 201 uses the downloaded installation data to install the detailed software 211 in the non-volatile memory 202 (step S213).

[0112] When the installation of the detailed software 211 is completed, the processor 201 terminates the running simple software 210 (step S214). The processor 201 starts up the installed detailed software 211 (step S215). This completes the software switching process.

[0113] Returning to FIG. 12, when the software switching process ends, the processor 201 proceeds to step S208.

[0114] In step S208, the processor 201 determines whether there is any unnecessary detail software 211 (step S208). For example, when the free space of the non-volatile memory 202 is less than a predetermined reference value, the detail software 211 with the lowest priority is determined to be unnecessary. In another example, when the detail software 211 for notifying of an abnormality in the hardware of the vehicle 10 is being executed, if the abnormality has already been resolved, the detail software 211 is determined to be unnecessary.

[0115] If there is unnecessary detailed software 211 (YES in step S208), the processor 201 uninstalls the unnecessary detailed software 211 from the non-volatile memory 202 (step S209). After uninstalling the detailed software, the processor 201 returns to step S201. If there is no unnecessary detailed software 211 (NO in step S208), the processor 201 also returns to step S201.

[0116] [8. Variation Examples] In the above embodiment, the integrated ECU 200 switches the software to be executed from the simple software to the detailed software based on the status information on the status of the vehicle 10. However, the present invention is not limited to this. For example, in an in-vehicle system including a plurality of in-vehicle devices (ECUs) having a function of controlling the hardware of the vehicle 10 or a function of providing information to a user, the plurality of in-vehicle devices may determine whether to switch the software to be executed from the simple software to the detailed software based on the status information on the status of the vehicle 10.

[0117] In the above embodiment, the integrated ECU 200 and the individual ECUs 300 are connected to each other by a CAN. However, the present invention is not limited to this. For example, the integrated ECU 200 and the individual ECUs 300 may be connected to each other by Ethernet (registered trademark).

[0118] [9. Effects] The in-vehicle system 100 includes an integrated ECU 200 (first in-vehicle device), an individual ECU 300 (second in-vehicle device), and an external communication device 500. The individual ECU 300 can communicate with the integrated ECU 200. The external communication device 500 can communicate with a database 40 (external device) arranged outside the vehicle 10. The integrated ECU 200 includes a non-volatile memory 202 (memory), a determination unit 222, a request unit 223, and a switching unit 225. The non-volatile memory 202 stores simple software 210 (first software). The simple software 210 is software for providing simple information (first information) to a user. The determination unit 222 determines whether or not to switch the software to be executed from the simple software 210 to the detailed software 211 (second software) based on state information related to the state of the vehicle 10. The detailed software 211 is software for providing the user with detailed information (second information) that is more detailed than the simple information. When the determination unit 222 determines that the software to be executed is to be switched from the simple software 210 to the detailed software 211, the request unit 223 requests the database 40 to download the detailed software via the external communication device 500. The switching unit 225 installs the detailed software 211 downloaded from the database 40 in the non-volatile memory 202. The switching unit 225 switches the software to be executed from the simple software 210 to the detailed software 211. When simple information is to be provided to the user, the simple software 210 is used. Therefore, it is possible to suppress pressure on the capacity of the non-volatile memory 202 and the volatile memory 203 of the integrated ECU 200. Therefore, it is possible to suppress an increase in the memory capacity mounted in the integrated ECU 200. When detailed information is to be provided to the user, the software to be executed is switched from the simple software 210 to the detailed software 211. Therefore, it is possible to provide a variety of information to the user.

[0119] The individual ECU 300 includes a sensor 400 for detecting the state of hardware mounted on the vehicle 10. ConnectedThe status information may include information on the status of the hardware detected by the sensor 400. Using the information acquired by the sensor 400, it is possible to determine whether to switch from the simple software 210 to the detailed software 211. In this way, when it is determined from the status of the hardware detected by the sensor 400 that the hardware needs to be replaced or repaired, for example, detailed software can be executed to provide the user with detailed information for replacing or repairing the hardware.

[0120] The state information may include information predicting a future usage state of the hardware mounted on the vehicle 10. Whether or not to switch from the simple software 210 to the detailed software 211 can be determined in consideration of the future usage state of the hardware mounted on the vehicle 10. In this way, when it is determined that the hardware needs to be replaced or repaired, for example, based on the predicted future usage state of the hardware, the detailed software 211 can be executed to provide the user with detailed information for replacing or repairing the hardware.

[0121] The state information may include information regarding the state of the environment around the vehicle 10. Whether or not to switch from the simple software 210 to the detailed software 211 can be determined taking into consideration the state of the environment around the vehicle 10. In this way, when it is determined from the state of the environment around the vehicle 10 that, for example, hardware needs to be replaced or repaired, the detailed software 211 can be executed to provide the user with detailed information for replacing or repairing the hardware.

[0122] The determination unit 222 may determine whether to switch the software to be executed from the simple software 210 to the detailed software 211 based on a priority assigned to the state of the environment around the vehicle 10. For example, when the priority is higher than a reference level, the simple software 210 can be switched to the detailed software 211.

[0123] When an instruction to switch the software to be executed from the simple software 210 to the detailed software 211 is given by the user, the determination unit 222 may determine that the software to be executed is to be switched from the simple software 210 to the detailed software 211. This makes it possible to switch the software to be executed from the simple software 210 to the detailed software 211 in response to the user's instruction.

[0124] The determination unit 222 may determine whether or not to switch the software to be executed from the simple software 210 to the detailed software 211 based on the priority assigned to the detailed software 211. A priority may be assigned to the detailed software 211 according to the importance of information that the detailed software 211 provides to the user. For example, when the priority is higher than a standard, the simple software 210 can be switched to the detailed software 211.

[0125] The priority may be associated with the type of the detail software 211 and the type of the environmental condition around the vehicle 10. For example, the priority can be determined according to the importance of the information that the detail software 211 provides to the user and the severity of the environmental condition around the vehicle 10.

[0126] The status information may include information regarding the communication status of the external communication device 500. For example, when the communication status of the external communication device 500 is good, the detailed software 211 can be downloaded, and when the communication status of the external communication device 500 is bad, the download of the detailed software 211 can be avoided.

[0127] The simple information provided to the user by the simple software 210 may be text information. The detailed information provided to the user by the detailed software 211 may include image information. By making the simple information simple text information, the size of the simple software 210 can be reduced. By including image information in the detailed information, detailed information in the form of images can be provided to the user.

[0128] The simple information provided to the user by the simple software 210 may be text information. The detailed information provided to the user by the detailed software 211 may include audio information. By making the simple information simple text information, the size of the simple software 210 can be reduced. By including audio information in the detailed information, detailed information can be provided to the user by audio.

[0129] The simple information may be information indicating an abnormality in the hardware mounted on the vehicle 10. The detailed information may include information indicating an abnormality in the hardware mounted on the vehicle 10 and information indicating a countermeasure to the abnormality. When an abnormality occurs in the hardware, the simple software 210 can notify the user of the occurrence of the abnormality. Furthermore, the size of the simple software 210 can be reduced. The detailed software 211 can not only notify the user of the occurrence of an abnormality, but also present the user with a countermeasure to the abnormality.

[0130] [10. Notes] An in-vehicle device mounted on a vehicle, A sensor for detecting a state of hardware installed in the vehicle; a transmission unit that transmits information regarding the state of the hardware detected by the sensor to the other in-vehicle device in order to determine whether the other in-vehicle device should switch the software to be executed from first software for providing first information to a user to second software for providing second information to the user that is more detailed than the first information; Equipped with In-vehicle device.

[0131] A computer program for causing a computer including a memory to function as an on-board device mounted in a vehicle, a determination unit that determines whether or not to switch software to be executed from first software for providing first information to a user to second software for providing second information to the user that is more detailed than the first information, based on status information regarding a status of the vehicle; a request unit that requests download of the second software to an external device disposed outside the vehicle when the determination unit determines that the software to be executed is to be switched from the first software to the second software; and a switching unit that installs the second software downloaded from the external device in the memory and switches the software to be executed from the first software to the second software; and causing the computer to function as: Computer program.

[0132] [11. Supplementary Note] The embodiments disclosed herein are illustrative in all respects and are not restrictive. The scope of the present invention is defined by the claims rather than the above-described embodiments, and includes the meaning equivalent to the claims and all modifications within the scope thereof. [Explanation of symbols]

[0133] 10 Vehicles 20 base station 30 Internet 40 Databases 50 Servers 100 In-vehicle systems 200 Integrated ECU 201 Processor 202 Non-volatile memory 203 Volatile Memory 204 First communication interface (first communication I / F) 205 Second communication interface (Second communication I / F) 206 Graphics Processing Circuit 207 Input / output section (I / O) 208 Audio processing circuit 209 Control Program 210 Simple Software 211 Detailed Software 221 Acquisition Department 222 Judgment section 223 Request part 224 Receiving section 225 Switching section 226 Uninstallation section 230 Priority Table 250 Display device 260 Input Device 270 Speaker 300,300A,300B,300C,300D Individual ECU 301 Processor 302 Non-volatile memory 303 Volatile Memory 304 Communication Interface (Communication I / F) 305 Input / Output Interface (I / O) 306 Control Program 400 Sensors 500 External communication device 600A,600B,610A,610B display screen 601,603,611 Text information 602,612 Image information

Claims

1. A first in-vehicle device; a second in-vehicle device capable of communicating with the first in-vehicle device; an external communication device capable of communicating with an external device disposed outside the vehicle; Equipped with The first in-vehicle device is a memory storing first software for providing first information to a user; a determination unit that determines whether to switch software to be executed from the first software to second software for providing a user with second information that is more detailed than the first information, based on status information regarding the status of the vehicle; a request unit that requests the external device to download the second software via the external communication device when the determination unit determines that the software to be executed is to be switched from the first software to the second software; a switching unit that installs the second software downloaded from the external device in the memory and switches the software to be executed from the first software to the second software; Including, In-vehicle systems.

2. the second in-vehicle device includes a sensor that detects a state of hardware mounted in the vehicle; the status information includes information regarding a status of the hardware detected by the sensor; The in-vehicle system according to claim 1 .

3. The state information includes information predicting a future usage state of the hardware installed in the vehicle.

3. The in-vehicle system according to claim 1 or 2.

4. The state information includes information regarding a state of an environment surrounding the vehicle. The in-vehicle system according to any one of claims 1 to 3.

5. the determination unit determines whether to switch the software to be executed from the first software to the second software based on a priority assigned to a state of an environment around the vehicle. The in-vehicle system according to claim 4.

6. the determination unit determines that the software to be executed is to be switched from the first software to the second software when an instruction to switch the software to be executed from the first software to the second software is given by a user. The in-vehicle system according to any one of claims 1 to 5.

7. the determination unit determines whether or not to switch the software to be executed from the first software to the second software based on a priority assigned to the second software. The in-vehicle system according to any one of claims 1 to 6.

8. The priority is associated with a type of the second software and a type of an environmental state around the vehicle. The in-vehicle system according to claim 7.

9. the status information includes information regarding a communication status of the external communication device; The in-vehicle system according to any one of claims 1 to 8.

10. The first information is character information, The second information includes image information. The in-vehicle system according to any one of claims 1 to 8.

11. The first information is character information, The second information includes audio information. The in-vehicle system according to any one of claims 1 to 8.

12. the first information is information indicating an abnormality in hardware mounted in the vehicle, The second information includes information indicating an abnormality in hardware mounted in the vehicle and information indicating a countermeasure for the abnormality. The in-vehicle system according to any one of claims 1 to 11.

13. An in-vehicle device mounted on a vehicle, a memory storing first software for providing first information to a user; a determination unit that determines whether to switch software to be executed from the first software to second software for providing a user with second information that is more detailed than the first information, based on status information regarding the status of the vehicle; a request unit that requests download of the second software to an external device disposed outside the vehicle when the determination unit determines that the software to be executed is to be switched from the first software to the second software; a switching unit that installs the second software downloaded from the external device in the memory and switches the software to be executed from the first software to the second software; Equipped with In-vehicle device.

14. A software switching method for switching software installed in an in-vehicle device mounted in a vehicle, comprising: determining whether to switch software to be executed from first software for providing first information to a user to second software for providing second information to the user that is more detailed than the first information, based on status information regarding the status of the vehicle; when it is determined that the software to be executed is to be switched from the first software to the second software, requesting download of the second software to an external device disposed outside the vehicle; installing the second software downloaded from the external device into a memory included in the in-vehicle device, and switching the software to be executed from the first software to the second software; Including, Software switching method.

Images