JP7639597B2 - Software update device, software update method and software update system - Google Patents

Description

The present invention relates to a software update device, a software update method, and a software update system.

A technology is known that obtains version information about the latest version of software and management element information associated with the version from a software distribution server, and updates the stored software if the stored software is not the latest version and the management element information satisfies the automatic update conditions (Patent Document 1)

In Patent Document 1, when a user manually updates software, the user checks the achievement rate of the automatic update conditions displayed on the display unit of the user terminal and updates the software.

JP 2016-38634 A

However, due to a time lag caused by communication delays, etc., the vehicle state displayed on the user terminal may differ from the actual vehicle state. The user instructs the software update to be performed, recognizing that the vehicle state displayed on the user terminal is the current vehicle state. On the other hand, the software update process is performed based on the actual vehicle state. Therefore, when the actual vehicle state differs from the vehicle state displayed on the user terminal, the software update process is not performed according to the user's instructions, which creates a problem in that the user feels uncomfortable.

The problem that this invention aims to solve is to provide a software update device, a software update method, and a software update system that allow a user to instruct a software update to be performed while recognizing that the vehicle state displayed on the user's terminal may differ from the actual vehicle state.

The present invention solves the above problem by acquiring vehicle information including the vehicle state of the vehicle and the vehicle time indicating the time information assigned to the vehicle state, determining whether the time difference between the vehicle time and the current time measured by the user's terminal is equal to or greater than a predetermined time, and notifying the user of the vehicle of the vehicle state included in the vehicle information when the time difference is equal to or greater than the predetermined time, emphasizing that the vehicle state included in the vehicle information is older than the vehicle state at the current time, as compared to when the time difference is less than the predetermined time.

According to the present invention, the user can instruct the software update to be performed while recognizing that the vehicle state displayed on the user's terminal may differ from the actual vehicle state.

FIG. 1 is a diagram illustrating an example of a configuration of a software update system according to the first embodiment. FIG. 2 is an example of a sequence chart showing a control flow in the software update system according to the first embodiment. FIG. 3 is an example of a sequence chart showing a control flow in the software update system according to the second embodiment. FIG. 4 is a diagram illustrating an example of a configuration of a software update system according to the third embodiment. FIG. 5 is an example of a sequence chart showing a control flow in the software update system according to the fourth embodiment. FIG. 6 is an example of a sequence chart showing a control flow in the software update system according to the fourth embodiment. FIG. 7 is an example of a sequence chart showing a control flow in the software update system according to the fourth embodiment. FIG. 8 is an example of a sequence chart showing a control flow in the software update system according to the fourth embodiment.

First Embodiment
An embodiment of the system according to the present invention will be described with reference to the drawings. The configuration of a software update system for updating software of an ECU of a vehicle according to this embodiment will be described with reference to FIG. 1. FIG. 1 is a block diagram showing an example of a software update system 100 including a software update device 1 according to this embodiment, an in-vehicle terminal device 20 mounted on a vehicle 2, a user terminal 3, and a communication network 4. The software update system 100 is a FOTA system capable of updating software of an ECU mounted on a vehicle 2 by OTA. The software update device 1 and the in-vehicle terminal device 20 can transmit and receive data to and from each other via the communication network 4. In addition, the software update device 1 and the user terminal 3 can transmit and receive data to and from each other via the communication network 4.

When update data for rewriting software is input by the software supplier, the software update device 1 stores the update data. For each software update campaign, the software update device 1 manages the VIN of the target vehicle, the target ECU, and the update data. A campaign refers to a unit of information for linking and managing information required for updating, such as the VIN of the target vehicle, to update data. The software update device 1 transmits to the user terminal 3 of the user of the vehicle 2 that the software of the ECU of the vehicle 2 is to be updated. When the software update device 1 receives a command to execute a software update from the user terminal 3, it transmits software update data to the in-vehicle terminal device 20. When the in-vehicle terminal device 20 receives the update data from the software update device 1, it uses the update data to rewrite and update the software of the ECU to be updated.

The user terminal 3 is a terminal operated by the user of the vehicle 2, and may be a mobile phone such as a smartphone carried by the user, a tablet terminal, a portable personal computer, or the like. The communication network 4 includes, for example, a mobile communication network using a 4G line or the like, the Internet, and the like. The software update data is update program data for updating the software of the ECU of the vehicle 2, and is provided by a software supplier. The update data may be all data equivalent to the entire software after the update, or may be difference data equivalent to the difference between the software before the update and the software after the update. The update data may also be compressed using well-known data compression technology.

The software update device 1 is a server that manages software update data provided by software suppliers and transmits the update data to the vehicle to be updated. The software update device 1 has a controller 10, a storage device 11, a communication device 12, and an input device 13, and is configured to be able to communicate data with each other. The controller 10 manages software updates for the vehicle 2. The controller 10 is equipped with a computer having hardware and software, and this computer includes a ROM that stores a program, a CPU that executes the program stored in the ROM, and a RAM that functions as an accessible storage device. The controller 10 is configured to include an update control unit 101, a transmission/reception unit 102, and an acquisition unit 103 as functional blocks, and executes each function by cooperation between the software for realizing each function or executing each process and the hardware. In this embodiment, the functions of the controller 10 are divided into three blocks, and the functions of each functional block are described, but the functions of the controller 10 do not necessarily have to be divided into three blocks, and may be divided into two or less functional blocks, or four or more functional blocks.

The update control unit 101 stores the update data input by the software supplier in the storage device 11. The update control unit 101 then determines, for all vehicles under its management, whether or not the vehicle is a target vehicle that requires a software update based on the input update data. Specifically, the update control unit 101 first compares, for each vehicle, the vehicle identification number of the vehicle with the target VIN managed as a software update target, and determines whether the vehicle identification numbers match. If the vehicle identification numbers match, the update control unit 101 compares the current ECU software version of the vehicle with the matching vehicle identification number with the software version of the latest software. If the vehicle's current ECU software version is not the software version of the latest software applicable to the vehicle, the update control unit 101 determines that a software update is required.

When it is determined that a software update is necessary, the transmission/reception unit 102 transmits information indicating that a software update is necessary for each vehicle 2 for which a software update is determined to be necessary to the user terminal 3 of the user of the vehicle 2. In addition, when the transmission/reception unit 102 receives a request command requesting the vehicle status of the vehicle 2 from the user terminal 3, it transmits the request command for the vehicle status of the vehicle 2 to the in-vehicle terminal device 20.

The acquisition unit 103 acquires vehicle information including the vehicle state of the vehicle 2 and the vehicle time indicating time information assigned to the vehicle state of the vehicle 2 from the in-vehicle terminal device 20. The vehicle time is, for example, time information indicating the time when the vehicle state is detected by the in-vehicle terminal device 20 or the time when the vehicle state is transmitted from the in-vehicle terminal device 20.

When the transmission/reception unit 102 receives vehicle information from the in-vehicle terminal device 20, it transmits the acquired vehicle information to the user terminal 3. The transmission/reception unit 102 also receives a command to execute a software update from the user terminal 3. When a command to execute a software update is acquired from the user terminal 3, the update control unit 101 transmits software update data to the in-vehicle terminal device 20. The transmission/reception unit 102 also receives a reacquisition command from the user terminal 3 instructing the user terminal 3 to reacquire the vehicle status. When the transmission/reception unit 102 receives a reacquisition command, it transmits a request command for the vehicle status to the in-vehicle terminal device 20. When the transmission/reception unit 102 receives vehicle information in response to the reacquisition request, it transmits the vehicle information to the user terminal 3.

In addition, in this embodiment, the transmission/reception unit 102 may transmit a request command for the vehicle state to the in-vehicle terminal device 20 at regular intervals and receive vehicle information including the vehicle state. When vehicle information is acquired from the in-vehicle terminal device 20, the update control unit 101 determines whether the vehicle state has changed. Specifically, the update control unit 101 determines whether the vehicle state is different from the vehicle state acquired last time. When it is determined that the vehicle state is different from the vehicle state acquired last time, the update control unit 101 detects that the vehicle state has changed. When it is not determined that the vehicle state is different from the vehicle state acquired last time, the update control unit 101 detects that the vehicle state has not changed. In addition, when the vehicle state of the vehicle 2 has changed, the acquisition unit 103 may acquire vehicle information including the changed vehicle state from the in-vehicle terminal device 20. For example, when the vehicle state is detected by the in-vehicle terminal device 20 at regular intervals and the detected vehicle state is different from the vehicle state detected last time, the vehicle information including the changed vehicle state is transmitted from the in-vehicle terminal device 20.

When the transmitter/receiver unit 102 detects that the vehicle state has changed, it transmits to the user terminal 3 information indicating that the vehicle state has changed and/or vehicle information including the vehicle state after the change. When the update control unit 101 detects that the vehicle state has changed, it rejects the instruction to execute a software update transmitted from the user terminal 3. The update control unit 101 may also transmit to the user terminal 3 a control signal that disables the input of an instruction to execute a software update by the user.

In addition, in this embodiment, if the change in the vehicle state is a transient change, the transceiver 102 transmits information indicating that the change in the vehicle state has started to the user terminal 3 when the change in the vehicle state starts. A transient change is a gradual change in state when the vehicle state changes from the pre-change vehicle state to the post-change vehicle state. For example, a transient change includes a drop in the battery voltage. Then, when the change in the vehicle state ends, that is, when the vehicle state has changed to the post-change vehicle state, the transceiver 102 transmits vehicle information including the post-change vehicle state to the user terminal 3.

When the transmission/reception unit 102 receives update completion information from the in-vehicle terminal device 20 indicating that the software update has been completed, the transmission/reception unit 102 transmits the update completion information to the user terminal 3. In addition, when the transmission/reception unit 102 receives update impossible information from the in-vehicle terminal device 20 indicating that the software cannot be updated, the transmission/reception unit 102 transmits the update impossible information to the user terminal 3.

The storage device 11 stores various data related to software updates of the ECU of the vehicle 2. Specifically, the storage device 11 stores update data. The communication device 12 is connected to the in-vehicle communication device 22 of the in-vehicle terminal device 20 via the communication network 4, and transmits and receives various data. For example, the communication device 12 transmits a request command for the vehicle status and update data to the in-vehicle communication device 22, and receives vehicle information including the vehicle status and vehicle time from the in-vehicle communication device 22. The communication device 12 is also connected to the communication device 32 of the user terminal 3 via the communication network 4, and transmits and receives various data. For example, the communication device 12 receives a command to execute a software update and a request command for the vehicle status from the user terminal 3, and transmits vehicle information to the user terminal 3.

The input device 13 accepts input of data from a software supplier, such as update data for the software of the vehicle 2. When the input device 13 accepts input of update data, it outputs the update data to the controller 10.

The in-vehicle terminal device 20 controls various ECUs mounted on the vehicle 2, and when update data is received from the software update device 1, it uses the update data to update the software of the ECU to be updated. The in-vehicle terminal device 20 includes a CGW 21, an in-vehicle communication device 22, an ECU 23, a vehicle state detection device 24, and a timing device 25, and is connected so that data communication can be performed between the CGW 21 and the in-vehicle communication device 22, between the CGW 21 and the ECU 23, between the in-vehicle communication device 22 and the vehicle state detection device 24, and between the in-vehicle communication device 22 and the timing device 25.

The CGW 21 is a vehicle gateway device having a data relay function. When the CGW 21 acquires update data from the in-vehicle communication device 22, it determines whether the software can be updated based on the vehicle state detected by the vehicle state detection device 24. For example, if the vehicle speed of the vehicle 2 is zero, i.e., the vehicle 2 is stopped, it is determined that the software can be updated. If the vehicle speed of the vehicle 2 is equal to or greater than a predetermined value, i.e., the vehicle 2 is moving, it is determined that the software cannot be updated. If it is determined that the software can be updated, the CGW 21 distributes the update data to the ECU to be updated, and updates the software of the ECU to be updated using the update data. When the software update is completed, the CGW 21 transmits update completion information to the software update device 1. If it is determined that the software cannot be updated, the CGW 21 does not update the software, and transmits update impossible information to the software update device 1 via the in-vehicle communication device 22.

The CGW 21 also aggregates the software versions of the software of multiple ECUs 23. Specifically, when the ignition power of the vehicle 2 is turned on, the CGW 21 aggregates the software versions of the ECUs at that time. The CGW 21 also aggregates the software versions of the ECUs at that time at a fixed interval. The CGW 21 transmits the aggregated software versions of each ECU to the software update device 1 via the in-vehicle communication device 22. The in-vehicle communication device 22 is an in-vehicle communication device that performs data communication with the software update device 1 via the communication network 4, and upon receiving update data from the software update device 1, transfers the update data to the CGW 21.

The ECU 23 includes, for example, a body system ECU, a driving system ECU, and an information system ECU. The body system ECU is an ECU that controls the body system, such as a door ECU that controls door lock/unlock. The driving system ECU is an ECU that controls the driving system, such as an engine ECU that controls the operation of the engine. The information system ECU is an ECU that controls the information system, such as a navigation ECU that controls a navigation system. The type of ECU 23 is not limited to the configuration illustrated. When the ECU 23 obtains update data from the CGW 21, it updates the software using the update data. The ECU 23 also manages the software version of the software, and transmits the software version in response to a request signal from the CGW 21.

The vehicle state detection device 24 detects the vehicle state of the vehicle 2. The vehicle state is, for example, the software update status of the ECU of the vehicle 2. The vehicle state also includes information for determining whether or not to execute a software update of the vehicle 2, such as information on the vehicle speed and current location of the vehicle 2. For example, the vehicle state is a state in which the vehicle speed of the vehicle 2 is zero, i.e., the vehicle is stopped, or the vehicle 2 is located in a parking lot at home. The vehicle state may also be the open/closed state of the doors of the vehicle 2, the state of the battery voltage, etc. The vehicle state detection device 24 detects the vehicle state when a request command for the vehicle state is received from the software update device 1.

The vehicle state detection device 24 may also detect the vehicle state at regular intervals. When the vehicle state detection device 24 detects that the vehicle state has changed, it transmits the changed vehicle state to the software update device 1 via the in-vehicle communication device 22.

The timing device 25 is a device with a timing function. For example, the timing device 25 is a timer. When the vehicle state is detected by the vehicle state detection device 24, the timing device 25 acquires the vehicle time indicating the time information assigned to the vehicle state. For example, the timing device 25 uses the timing function to record the time when the vehicle state is detected as the vehicle time. The detected vehicle state is transmitted to the software update device 1 together with the vehicle time via the in-vehicle communication device 22.

The user terminal 3 includes a controller 30, an output device 31, a communication device 32, and an input device 33. The controller 30 includes a control unit 301, a clock unit 302, and a determination unit 303, and controls each device. The clock unit 302 clocks the current time. For example, when vehicle information is received, the clock unit 302 clocks the time at that point as the current time. The determination unit 303 determines whether the time difference between the vehicle time and the current time is equal to or greater than a predetermined time. The control unit 301 then controls the output device 31 to change the content of the notification to the user depending on the determination result.

When the control unit 301 determines that the time difference is equal to or greater than the predetermined time, the control unit 301 controls the output device 31 to notify the user of the vehicle state by emphasizing that the vehicle state included in the vehicle information is older than the vehicle state at the current time, as compared to when the time difference is less than the predetermined time. For example, the control unit 301 changes the display color of the vehicle state displayed on the display of the output device 31. Specifically, the control unit 301 changes the display color to red, whereas the display color is normally set to black. The control unit 301 may also display the vehicle state and an icon on the display of the output device 31. The icon is a symbol that emphasizes that the displayed vehicle state is older, for example, a symbol indicating an exclamation mark. The icon may include text information indicating that the displayed vehicle state is older. The control unit 301 may also control the output device 31 to notify the user of the vehicle state and the vehicle time, or may control the output device 31 to notify the user of the vehicle state, the vehicle time, and the current time.

In addition, when the control unit 301 determines that the time difference is less than a predetermined time, it controls the output device 31 to notify the user of the vehicle state without notifying the user of incidental information such as icons and time.In addition, when the control unit 301 determines that the time difference is less than a predetermined time, it may control the output device 31 to notify the user of the vehicle state and the current time.

In addition, if the time difference between the vehicle time and the current time is equal to or greater than a predetermined time, the control unit 301 may control the output device 31 to notify the user of the vehicle status and a disclaimer that "user operations may not be accepted."

The output device 31 outputs various information. The information output by the output device 31 includes information related to the software update and vehicle information including the vehicle state and vehicle time. The information related to the software update includes the contents of the software update, information indicating the software update status, and information indicating that a software update of the vehicle 2 is necessary. The information indicating the software update status includes update completion information and update impossible information. The output device 31 displays various information on a display, for example. The output device 31 may also output various information as audio information through a speaker.

When the output device 31 receives information indicating that a software update is necessary, it outputs information indicating that a software update is necessary. When the output device 31 receives vehicle information, it outputs the vehicle information. When the output device 31 receives vehicle information, it changes the notification content to be notified to the user depending on whether the time difference between the vehicle time and the current time is equal to or greater than a predetermined time. Specifically, when the time difference is equal to or greater than a predetermined time, the output device 31 notifies the user of the vehicle state by emphasizing that the notified vehicle state is older than the vehicle state at the current time. For example, the output device 31 may display the vehicle state by changing the display color, or may display the vehicle state and an icon. When the output device 31 receives vehicle information, it outputs the vehicle information. When the time difference is equal to or greater than a predetermined time, the output device 31 changes the notification content to be notified to the user depending on whether the time difference between the vehicle time and the current time is equal to or greater than a predetermined time. Specifically, when the time difference is equal to or greater than a predetermined time, the output device 31 notifies the user of the vehicle state by emphasizing that the notified vehicle state is older than the vehicle state at the current time. For example, the output device 31 may display the vehicle state by changing the display color, or may display the vehicle state and an icon. The output device 31 may display the vehicle state and the vehicle time.

The output device 31 may notify the vehicle status and text information when the time difference between the vehicle time and the current time is equal to or greater than a predetermined time. Also, the output device 31 notifies the vehicle status and the current time when the time difference between the vehicle time and the current time is less than a predetermined time.

The user checks the contents and update status of the software update output to the output device 31 and determines whether to instruct the software update to be performed. For example, when the user is in the vehicle 2 and the vehicle state is displayed on the in-vehicle display, it is considered that there is almost no discrepancy between the actual vehicle state and the vehicle state displayed on the in-vehicle display. However, when the vehicle state is displayed on the display of a terminal such as a smartphone, a time lag of about several tens of seconds generally occurs, and the actual vehicle state may differ from the vehicle state displayed on the display. In other words, a time lag may occur due to communication delays between the time the vehicle state is detected by the vehicle and the time the detected vehicle state is displayed on the display of the user terminal, and during that time, the actual vehicle state may have changed from the state at the time of detection. The user recognizes that the vehicle state displayed on the display is the current vehicle state and instructs the software update to be performed, but if the actual vehicle state is in a state where the software update is not possible, the software update will be forcibly canceled on the vehicle side. Therefore, the user feels uncomfortable that the software update is not performed as instructed, and causes inconvenience to the user.

In this embodiment, as described above, when notifying the vehicle state at the vehicle time, if there is a time difference between the vehicle time and the current time, the notified vehicle state is notified as being old. This allows the user to know how old the notified vehicle state is. For example, if the vehicle state is displayed as being software updatable and the vehicle time is displayed as being several seconds before the current time, the vehicle state is unlikely to have changed in the meantime if it is only a few seconds, so the user recognizes that it is highly likely that the software update can be performed. On the other hand, for example, if the vehicle state is displayed as being software updatable but the vehicle time is displayed as being several minutes before the current time, the larger the time difference, the higher the possibility that the actual vehicle state has changed from the displayed vehicle state, i.e., the vehicle state at the time of detection. Therefore, the user can issue an execution instruction, etc., after recognizing in advance that even if the user terminal displays that the software update is possible, the actual vehicle state has changed to a state in which the software update is not possible and the software update may not be possible.

The communication device 32 is a device capable of communicating with the software update device 1 and transmits and receives various data. For example, the communication device 32 transmits a request command for the vehicle status of the vehicle 2 and a command to execute a software update to the software update device 1, and receives information related to the software update and vehicle information from the software update device 1. The input device 33 accepts input of various data by the user. For example, the input device 33 accepts input of an instruction to execute and an instruction to cancel a software update by the user. The input device 33 may also accept input of a request command for the vehicle status and an instruction to reacquire the vehicle status by the user. Note that, when the user terminal 3 is directly connected to the in-vehicle terminal device 20 via Bluetooth (registered trademark) or the like, the user terminal 3 may perform data communication with the software update device 1 via the in-vehicle communication device 22 of the vehicle 2. Also, when the in-vehicle terminal device 20 and the user terminal 3 are directly connected, the in-vehicle terminal device 20 may communicate with the software update device 1 from the user terminal 3 via the communication network 4.

Next, the control process of the software update executed by the software update system will be described. FIG. 2 shows a sequence diagram for executing the control process of the software update in the software update system. In this embodiment, when the user operates the user terminal 3 to connect to the software update screen, the control flow starts from step S1.

In step S1, when the user terminal 3 receives an operation input to connect to the software update screen by the user, the user terminal 3 transmits a request command for the vehicle status of the vehicle 2 to the software update device 1. In addition, the request command may be transmitted automatically when the user connects to the software update screen and then requests the vehicle status of the vehicle 2. That is, the user terminal 3 may transmit a request command to the software update device 1 when it receives an input of a request command for the vehicle status by the user. In step S2, the software update device 1 transmits a request command for the vehicle status of the vehicle 2 to the in-vehicle terminal device 20. In step S3, the in-vehicle terminal device 20 detects the vehicle status of the vehicle 2 and acquires the vehicle time indicating the time information assigned to the vehicle status. In step S4, the in-vehicle terminal device 20 transmits vehicle information including the vehicle status and the vehicle time to the software update device 1. In step S5, the software update device 1 transmits vehicle information including the vehicle status and the vehicle time to the user terminal 3.

In step S6, the user terminal 3 acquires the current time using the clock function of the user terminal 3. In step S7, the user terminal 3 compares the vehicle time with the current time, and determines whether the time difference between the vehicle time and the current time is equal to or greater than a predetermined time. If it is determined that the time difference is equal to or greater than the predetermined time, the user terminal 3 proceeds to step S8. If it is determined that the time difference is less than the predetermined time, the user terminal 3 proceeds to step S9. In step S8, the user terminal 3 displays the vehicle state by emphasizing that the vehicle state included in the vehicle information is older than the vehicle state at the current time. For example, the user terminal 3 displays the vehicle state and the vehicle time.

In step S9, the user terminal 3 displays the vehicle state in a normal manner. For example, the user terminal 3 displays the vehicle state and the current time. In step S10, the user terminal 3 receives an instruction to execute a software update. In step S11, the user terminal 3 transmits an instruction to execute a software update to the software update device 1. In step S12, the software update device 1 transmits update data to the in-vehicle terminal device 20. In step S13, the in-vehicle terminal device 20 detects the vehicle state and determines whether the software can be updated based on the vehicle state. If it is determined that the software can be updated, the process proceeds to step S14. If it is not determined that the software can be updated, the process proceeds to step S18. In step S14, the in-vehicle terminal device 20 updates the software using the update data. In step S15, the in-vehicle terminal device 20 transmits update completion information indicating that the software update has been completed to the software update device 1. In step S16, the software update device 1 transmits the update completion information to the user terminal 3. In step S17, the user terminal 3 notifies the user of the update completion information. In step S18, the in-vehicle terminal device 20 transmits update disable information to the software update device 1. In step S19, the software update device 1 transmits the update disable information to the user terminal 3. In step S20, the user terminal 3 notifies the user of the update disable information. Also, in this embodiment, in step S8, the user terminal 3 may transmit a command to reacquire the vehicle state to the software update device 1.

As described above, in this embodiment, the controller includes an acquisition unit that acquires the vehicle state of the vehicle and the vehicle time indicating time information assigned to the vehicle state, and a transmission unit that transmits vehicle information including the vehicle state and the vehicle time to the user terminal in response to a command from the user terminal of the vehicle user, and when the time difference between the vehicle time and the current time clocked by the clock unit of the user terminal is equal to or greater than a predetermined time, the user terminal notifies the user of the vehicle state included in the vehicle information by emphasizing that the vehicle state included in the vehicle information is older than the vehicle state at the current time, rather than when the time difference is less than the predetermined time. This allows the user to instruct to perform a software update while recognizing that the vehicle state displayed on the user's terminal may differ from the actual vehicle state.

In this embodiment, the controller further includes an update control unit, and the update control unit transmits update data for updating the vehicle's software to the vehicle based on a command to execute a software update from the user terminal. This allows the vehicle's software to be updated according to the user's decision to execute a software update.

In addition, in this embodiment, when the vehicle state changes, the controller transmits a message to the user terminal indicating that the vehicle state has changed. This allows the user to give appropriate execution instructions according to the vehicle state.

In addition, in this embodiment, if the controller detects that the vehicle state has changed, it rejects the instruction to execute a software update sent from the user terminal. This makes it possible to prevent the user from issuing an instruction to execute a software update when there is a possibility that the actual vehicle state has changed from the vehicle state displayed on the user's terminal.

In addition, in this embodiment, when the controller detects that the vehicle state has changed, it transmits a control signal to the user terminal to disable the user's input of an instruction to execute a software update. This makes it possible to prevent the user from issuing an instruction to execute a software update when there is a possibility that the actual vehicle state has changed from the vehicle state displayed on the user's terminal.

In addition, in this embodiment, if the vehicle state changes, the controller transmits the changed vehicle state to the user terminal. This prevents the user from instructing a software update when the actual vehicle state may have changed from the vehicle state displayed on the user's terminal.

In addition, in this embodiment, when the controller detects that a change in the vehicle state has started, it transmits that information to the user terminal, and when it detects that the change in the vehicle state has ended, it transmits the changed vehicle state to the user terminal. This allows the user to determine whether or not to give an appropriate execution instruction depending on the actual vehicle state.

In this embodiment, the software update system includes a vehicle, a server that manages software updates for the vehicle, and a user terminal that is operated by a user of the vehicle and can communicate with the server. The server acquires the vehicle state of the vehicle and the vehicle time that indicates time information assigned to the vehicle state, and transmits vehicle information including the vehicle state and the vehicle time to the user terminal. The user terminal measures the current time, compares the vehicle time with the current time, and, if the time difference between the vehicle time and the current time is equal to or greater than a predetermined time, notifies the user of the vehicle state included in the vehicle information by emphasizing that the vehicle state included in the vehicle information is older than the vehicle state at the current time, rather than when the time difference is less than the predetermined time. This allows the user to instruct the software update to be performed while recognizing that the vehicle state displayed on the user's terminal may differ from the actual vehicle state.

Second Embodiment
Next, a second embodiment of the present invention will be described. In the second embodiment, the software update system 100 has a similar configuration to the software update system 100 of the first embodiment shown in Fig. 1 and operates in the same manner as the first embodiment, except for the differences from the first embodiment in the points described below, and the description of the first embodiment will be used as appropriate. In this embodiment, the difference from the first embodiment is that the user terminal 3 sets the input of an instruction to execute a software update by a user to be invalid or valid depending on whether the time difference between the vehicle time and the current time is equal to or greater than a predetermined time.

In this embodiment, the control unit 301 controls the input device 33 to disable the user's input of an instruction to perform a software update when the time difference is equal to or greater than a predetermined time, and controls the input device 33 to enable the user's input of an instruction to perform a software update when the time difference is less than the predetermined time. The control unit 301 may also control the output device 31 to change the notification content to be notified to the user depending on whether the input of the instruction to perform a software update is invalid. For example, when the input of the instruction to perform a software update is invalid, the control unit 301 notifies the user of invalid instruction information indicating that the input of the instruction to perform a software update is not accepted. The control unit 301 may also notify the user to reacquire the vehicle state when the time difference is equal to or greater than a predetermined time. Then, when a reacquisition command to reacquire the vehicle state is input, the control unit 301 causes the software update device 1 to transmit a vehicle state reacquisition command.

The input device 33 invalidates the input of an instruction to execute a software update when the time difference between the vehicle time and the current time is equal to or greater than a predetermined time. The output device 31 notifies the user of invalid instruction information indicating that the input of an instruction to execute a software update will not be accepted when the time difference between the vehicle time and the current time is equal to or greater than a predetermined time.

Next, the control process of the software update in the software update system according to this embodiment will be described with reference to FIG. 3. FIG. 3 is a sequence diagram of the control process of the software update in the software update system. Specifically, FIG. 3 shows an example of the control process in which the user terminal 3 sets the input of an instruction to execute a software update to invalid or valid depending on whether the time difference between the vehicle time and the current time is equal to or greater than a predetermined time. In this embodiment, when the user inputs a connection operation to connect to the software update screen via the user terminal 3, the control flow starts from step S21. In this embodiment, steps S21 to S27 and S34 to S40 are similar to steps S1 to S7, S10 to S12, and S14 to S17 in the first embodiment, and therefore description thereof will be omitted.

If it is determined in step S27 that the time difference between the vehicle time and the current time is equal to or greater than the predetermined time, the process proceeds to step S28. If it is determined that the time difference between the vehicle time and the current time is less than the predetermined time, the process proceeds to step S32. In step S28, the user terminal 3 sets the input of the software update execution instruction by the user to be invalid. In step S29, the user terminal 3 displays the vehicle status and invalid instruction information indicating that the input of the execution instruction has been invalidated. At this time, the user terminal 3 may notify the user of information instructing the user to reacquire the vehicle status. In step S30, the user terminal 3 accepts the input of a vehicle status request instruction by the user. In step S31, the user terminal 3 transmits a vehicle status request command to the software update device 1. When the vehicle status request command is transmitted, the process returns to step S22, and the flow is repeated thereafter. In step S32, the user terminal 3 sets the input of the software update execution instruction by the user to be valid. In step S33, the user terminal 3 displays the vehicle status.

As described above, in this embodiment, the user terminal notifies the user that the instruction to perform a software update by the user will not be accepted if the time difference is equal to or greater than a predetermined time. This makes it possible to prevent the user from instructing a software update in cases where the vehicle state displayed on the user's terminal may differ from the actual vehicle state.

In addition, in this embodiment, the user terminal transmits a reacquisition command to the controller to newly acquire the vehicle state when the time difference is equal to or greater than a predetermined time, and the transmission unit transmits vehicle information including the vehicle state and vehicle time reacquired from the vehicle to the user terminal in response to the reacquisition command. This allows the vehicle state displayed on the user terminal to be updated when there is a possibility that the vehicle state displayed on the user terminal differs from the actual vehicle state.

In addition, in this embodiment, the user terminal disables the user's input of an instruction to perform a software update if the time difference is equal to or greater than a predetermined time. This makes it possible to prevent the user from issuing an instruction to perform a software update when the vehicle state displayed on the user's terminal may differ from the actual vehicle state.

In addition, in this embodiment, the user terminal changes the notification content to be notified to the user depending on whether the input of the instruction to execute the software update is invalid. This allows the user to decide whether to issue an instruction to execute depending on whether the input is invalid.

Third Embodiment
Next, a software update system 100 according to a third embodiment will be described. The software update system 100 according to the third embodiment has the same configuration as the first embodiment and operates in the same manner as the first embodiment, except for differences from the software update system 100 according to the first embodiment in the points described below, and the description of the first embodiment will be used as appropriate. The configuration of this embodiment differs from the configuration of the first embodiment in that the software update device 1 is a terminal device operated by a user and has the functions of the user terminal 3 in the first embodiment.

As shown in FIG. 4, the software update system 100 according to the third embodiment includes a software update device 1, an in-vehicle terminal device 20 mounted on a vehicle 2, a communication network 4, and a software management device 5. The software update device 1 in the third embodiment differs from the first embodiment in that it further includes an output device 14. The output device 14 has the same function as the output device 31 in the first embodiment, and notifies the user of the vehicle 2 of various information including vehicle information. In addition, the controller 10 in the third embodiment further includes a timer unit 104 and a determination unit 105.

The clock unit 104 has a function similar to that of the clock unit 302 in the first embodiment and clocks the current time. The judgment unit 105 has a function similar to that of the judgment unit 303 in the first embodiment and judges whether the time difference between the vehicle time and the current time is a predetermined time or more. When it is judged that the time difference is a predetermined time or more, the update control unit 101 controls the output device 14 to notify the vehicle user of the vehicle state included in the vehicle information by emphasizing that the vehicle state included in the vehicle information is older than the vehicle state at the current time, as compared to when the time difference is less than the predetermined time. The input device 13 in the third embodiment has a function similar to that of the input device 33 in the first embodiment and is a device that accepts input of a software update execution instruction by a user. In this embodiment, when a software update execution instruction is input to the input device 13, the software update device 1 transmits a software update execution command via the communication device 12. The connection between the in-vehicle terminal device 20 of the vehicle 2 and the user terminal 3 may be wireless, such as via Bluetooth (registered trademark) or Wi-Fi (Wireless Fidelity) (registered trademark).

The software management device 5 is a server that manages software update data provided by the software supplier. The software management device 5 includes an input device 50, a communication device 51, and a storage device 52. The input device 50 accepts input of data such as update data from the software supplier. When update data is input, the communication device 51 transmits information indicating that a software update is necessary to the software update device 1 of the user of the vehicle that is the target of the software update. The storage device 52 stores various data related to the software update, including the update data.

As described above, in this embodiment, the software update device includes a controller that instructs a software update of a vehicle, and the controller includes an acquisition unit that acquires vehicle information including the vehicle state of the vehicle and the vehicle time indicating time information assigned to the vehicle state, a clock unit that clocks the current time, a determination unit that determines whether the time difference between the vehicle time and the current time is equal to or greater than a predetermined time, and a notification unit that, when the time difference is equal to or greater than the predetermined time, notifies the user of the vehicle of the vehicle state included in the vehicle information by emphasizing that the vehicle state included in the vehicle information is older than the vehicle state at the current time, compared to when the time difference is less than the predetermined time. This allows the user to instruct the software update to be performed while recognizing that the vehicle state displayed on the user's terminal may differ from the actual vehicle state.

Fourth Embodiment
Next, a software update system 100 according to a fourth embodiment will be described. The software update system 100 according to the fourth embodiment has the same configuration as the first embodiment and operates in the same manner as the first embodiment, except that it differs from the software update system 100 according to the first embodiment in the points described below, and the description of the first embodiment will be used as appropriate. The configuration of this embodiment differs from the configuration of the first embodiment in that there are multiple user terminals 3. For example, the multiple user terminals 3 are a first user terminal 310 and a second user terminal 320 different from the first user terminal 310, and each user terminal has the same configuration and function as the user terminal 3 in the first embodiment.

In this embodiment, the first user terminal 310 is a terminal operated by the first user, and the second user terminal 320 is a terminal operated by the second user. The first user and the second user manage the same vehicle 2 via their respective user terminals and give instructions to execute software updates, etc. However, there is a time difference between the time when the vehicle status is notified via the first user terminal 310 and the time when the vehicle status is notified via the second user terminal 320. In this embodiment, there are two user terminals, but this is not limited to this, and there may be three or more user terminals.

In this embodiment, when the vehicle state displayed on one of the user terminals is updated, the vehicle state displayed on the other user terminal is also updated. Specifically, when the controller 10 receives a request command for the vehicle state from the first user terminal 310, the controller 10 transmits a request command for the vehicle state to the in-vehicle terminal device 20. Then, when the controller 10 acquires vehicle information including the vehicle state and the vehicle time from the in-vehicle terminal device 20, the controller 10 transmits the acquired vehicle information to both the first user terminal 310 and the second user terminal 320. Also, when the controller 10 receives a command to reacquire the vehicle state from the first user terminal 310, the controller 10 acquires vehicle information from the in-vehicle terminal device 20 and transmits the acquired vehicle information to the first user terminal 310 and the second user terminal 320. That is, when a request command for the vehicle state or a reacquisition command is received from one user terminal, the controller 10 transmits the same vehicle information acquired based on the command to one user terminal and the other user terminal. This allows multiple user terminals to update the notification content so that the vehicle state corresponding to the same vehicle time is notified.

In general, when vehicle state request commands are transmitted from multiple user terminals at different times, the controller 10 acquires the vehicle states at different vehicle times. If the vehicle times are different and the vehicle state has changed in the meantime, the vehicle states at each vehicle time will be different. For this reason, in this embodiment, the vehicle state at the same vehicle time is transmitted to each user terminal.

For example, the open/closed state of the door of the vehicle 2 will be described as an example of the vehicle state. Assume that the open/closed state of the door at different times is acquired and transmitted to the first user terminal 310 and the second user terminal 320, respectively. In this case, for example, the first user terminal 310 displays that the door is open, and the second user terminal 320 displays that the door is closed. The first user tries to input an instruction to close the door, but the vehicle state displayed on the first user terminal 310 may be an old state. Also, for example, if the second user terminal 320 displays that the door is closed, even if the first user has already issued an instruction to operate the door lock, the fact that the door has been locked by the first user is not displayed, and the second user cannot recognize that the door has been locked by the first user. In order to solve such a problem, in this embodiment, the vehicle state at the same vehicle time is transmitted to each user terminal, and the execution result based on the command by one of the users is also transmitted to the other user terminal.

When the controller 10 receives execution completion information indicating that the software update based on the instruction from the first user terminal 310 has been completed, the controller 10 transmits the execution completion information of the software update to the first user terminal 310 and the second user terminal 320. As a result, the result of the operation performed based on the instruction from one user terminal is also notified to the other user terminal.

In addition, when the controller 10 receives a command to execute a software update from one user terminal, it prevents the software update based on a command from the other user terminal from being executed until the software update based on the execution command is completed. That is, the controller 10 prevents simultaneous operations from multiple user terminals. For example, when the controller 10 receives a command to execute a software update from the first user terminal 310, it transmits user operation information to the second user terminal 320 and transmits a control signal to the second user terminal 320 to notify the second user of the user operation information. The user operation information is, for example, text information indicating that an operation is being performed by the other user. When a software update is being executed, the user operation information is text information stating that "the software update of the vehicle is being executed based on the command to execute a software update by the first user." Then, when the controller 10 receives execution completion information from the in-vehicle terminal device 20, it transmits a stop signal to the second user terminal 320 to stop the notification of the execution completion information and the user operation information.

When the controller 10 receives a command to execute a software update from one user terminal, the controller 10 suspends the authority of the other user to issue a command to execute a software update from the other user terminal until the software update based on the command is completed. For example, when the controller 10 receives a command to execute a software update from the first user terminal 310, the controller 10 transmits a control signal to the second user terminal 320 to disable the input of the command to execute the software update. When the controller 10 receives execution completion information regarding the software update from the in-vehicle terminal device 20, the controller 10 transmits the execution completion information and a control signal to the second user terminal 320 to cancel the disablement of the input of the execution command.

For example, when the controller 10 receives a command to execute a software update from the first user terminal 310, the controller 10 may set the second user terminal 320 as an execution refusal target for the period from when the execution command is received until the execution of the software update is completed. The controller 10 rejects the execution command for the software update sent from the second user terminal 320 that is set as an execution refusal target while the second user terminal 320 is set as an execution refusal target. When the controller 10 receives execution completion information from the in-vehicle terminal device 20, the controller 10 cancels the setting of the second user terminal 320 as an execution refusal target. When the controller 10 rejects the execution command, the controller 10 transmits rejection information to the second user terminal 320 indicating that the execution command is rejected.

Next, an example of the control process of the software update in the software update system according to this embodiment will be described with reference to FIG. 5. FIG. 5 is a sequence diagram of the control process of the software update in the software update system. Specifically, FIG. 5 shows an example of the control process in which, when a request command for the vehicle state is transmitted from the first user terminal 310, the software update device 1 transmits vehicle information including the vehicle state and the vehicle time acquired based on the command to the first user terminal 310 and the second user terminal 320. In this embodiment, when the first user inputs a connection operation to connect to the software update screen via the first user terminal 310, the control flow starts from step S41. In this embodiment, steps S41, S44 to S46 are the same as steps S1, S3 to S5 in the first embodiment, and therefore the description will be omitted.

In this example, an example is described in which the software update device 1 receives a request command for the vehicle status from the second user terminal 320 before transmitting a request command for the vehicle status based on a command from the first user terminal 310 to the in-vehicle terminal device 20, but this is not limited to the above, and the timing of transmitting the request command from the second user terminal 320 can be any time before the vehicle information is transmitted from the software update device 1 to the second user terminal 320.

In step S42, when the second user terminal 320 accepts an input operation by the second user to connect to the software update screen, the second user terminal 320 transmits a request command for the vehicle state to the software update device 1. In step S43, the software update device 1 transmits a request command for the vehicle state to the in-vehicle terminal device 20 based on the request command transmitted from the first user terminal 310 in step S41. In step S47, the software update device 1 transmits to the second user terminal 320 vehicle information including the vehicle state and vehicle time transmitted from the in-vehicle terminal device 20 in step S25.

Next, an example of the control process of a software update in the software update system according to this embodiment will be described with reference to FIG. 6. FIG. 6 is a sequence diagram of the control process of a software update in the software update system. FIG. 6 shows an example in which, when a command to execute a software update is received from the first user terminal 310, the software update device 1 transmits user operation information to the second user terminal 320 indicating that a software update is being performed based on an instruction from the first user. In this embodiment, when the first user connects to the software update screen via the first user terminal 310, the control flow starts from step S51. In this embodiment, steps S51 to S55 are the same as steps S1 to S5 in FIG. 2, and therefore description thereof will be omitted.

In step S56, the first user terminal 310 displays the vehicle state. When displaying the vehicle state, the first user terminal 310 may display the vehicle state by emphasizing that the displayed vehicle state is older than the vehicle state at the current time, as in the first embodiment, if the time difference between the vehicle time and the current time is equal to or greater than a predetermined time. In step S57, the first user inputs an instruction to execute a software update to the first user terminal 310 by the first user. In step S58, the first user terminal 310 transmits an instruction to execute a software update to the software update device 1. In step S59, the software update device 1 transmits update data to the in-vehicle terminal device 20.

In step S60, the software update device 1 transmits user operation information to the second user terminal 320. In step S61, the second user terminal 320 displays the user operation information. In step S62, the in-vehicle terminal device 20 updates the software using the update data. In step S63, the in-vehicle terminal device 20 transmits update completion information to the software update device 1. In step S64, the software update device 1 transmits the update completion information to the second user terminal 320. In step S65, the second user terminal 320 stops displaying the user operation information.

Next, an example of the control process of the software update in the software update system according to this embodiment will be described with reference to FIG. 7. FIG. 7 is a sequence diagram of the control process of the software update in the software update system. FIG. 7 shows an example in which, when a command to execute a software update is received from the first user terminal 310, the software update device 1 transmits a control signal to the second user terminal 320 to disable the input of an instruction to execute a software update by the user. In this embodiment, when the first user connects to the software update screen via the first user terminal 310, the control flow starts from step S51. In this embodiment, steps S71 to S75 are the same as steps S1 to S5 in FIG. 2, and therefore their description will be omitted. Also, steps S76 to S79 are the same as steps S56 to S59 in FIG. 6, and therefore their description will be omitted.

In step S80, the software update device 1 transmits an invalidation control signal to the second user terminal 320 to invalidate the input of an instruction to execute a software update. In step S81, the second user terminal 320 invalidates the input of an instruction to execute a software update. In step S82, the in-vehicle terminal device 20 updates the software using the update data. In step S83, the in-vehicle terminal device 20 transmits update completion information to the software update device 1. In step S84, the software update device 1 transmits the update completion information to the first user terminal 310. In step S85, the software update device 1 transmits an unlock signal to the second user terminal 320 to unlock the invalidation of the input of the execution instruction. In step S86, the second user terminal 320 unlocks the invalidation of the input of the execution instruction and enables the input operation.

Next, an example of the control process of software update in the software update system according to this embodiment will be described with reference to FIG. 8. FIG. 8 is a sequence diagram of the control process of software update in the software update system. FIG. 8 shows an example in which, when a command to execute software update is received from the first user terminal 310, the software update device 1 sets the second user terminal 320 as an execution refusal target. In this embodiment, when the first user connects to the software update screen via the first user terminal 310, the control flow starts from step S71. In this embodiment, steps S91 to S95 are the same as steps S1 to S5 in FIG. 2, and therefore their description will be omitted. Also, steps S96 to S99 are the same as steps S56 to S59 in FIG. 6, and therefore their description will be omitted.

In step S100, the software update device 1 sets the second user terminal 320 as an execution refusal target. In step S101, the second user terminal 320 transmits a command to execute the software update to the software update device 1. In step S102, the software update device 1 rejects the command from the second user terminal 320 and transmits execution refusal information to the second user terminal 320. In step S103, the second user terminal 320 displays the execution refusal information. In step S104, the in-vehicle terminal device 20 updates the software using the update data. In addition, in step S105, the in-vehicle terminal device 20 transmits update completion information to the software update device 1. In step S106, the software update device 1 transmits the update completion information to the first user terminal 310. In step S107, the software update device 1 cancels the setting of the second user terminal 320 as an execution refusal target.

As described above, in this embodiment, when there are multiple user terminals, when the vehicle state notified via one user terminal is updated, the controller transmits a control signal to the other user terminal to update the vehicle state notified via the other user terminal. This makes it possible to display a vehicle state similar to the vehicle state displayed on one user terminal on the other user terminal, even if the vehicle state displayed on one user terminal is updated.

In addition, in this embodiment, when there are multiple user terminals, while a vehicle software update is being performed based on a software update execution command from one user, the controller transmits a control signal to the user terminal of the other user to disable input of a software update execution command from the other user. This makes it possible to prevent an execution command from being given from one user terminal when the other user terminal has given the execution command.

In addition, in this embodiment, the controller transmits a control signal to the user terminal of one user to notify the other user that a software update of the vehicle is being performed based on an instruction to perform a software update from the other user. This allows the other user to determine that, when one user has given an instruction to perform an update, the other user will not give an instruction to perform an update.

The above-described embodiments are described to facilitate understanding of the present invention, and are not described to limit the present invention. Therefore, each element disclosed in the above embodiments is intended to include all design modifications and equivalents that fall within the technical scope of the present invention.

For example, in the first embodiment of the present invention, the user terminal 3 determines whether the time difference between the vehicle time and the current time is equal to or greater than a predetermined time, but the present invention is not limited to this, and the controller 10 may determine whether the time difference is equal to or greater than a predetermined time. In this case, the controller 10 may obtain the current time measured by the user terminal 3 from the user terminal 3, or may measure the current time by the controller 10. When it is determined that the time difference is equal to or greater than a predetermined time, the controller 10 transmits to the user terminal 3 a control signal that notifies the user of the vehicle state included in the vehicle information, emphasizing that the vehicle state included in the vehicle information is older than the vehicle state at the current time, as compared to when the time difference is less than the predetermined time. Furthermore, when it is determined that the time difference is equal to or greater than a predetermined time, the controller 10 may reject a command to execute a software update transmitted from the user terminal 3.

In addition, in this embodiment, the target of the operation command from the user has been described as a software update of the vehicle 2, but this is not limited thereto, and other parts of the vehicle 2 that can be operated remotely may be the target of the operation command. For example, the target of the operation command may be opening and closing the doors of the vehicle 2, etc.

Reference Signs List 100: software update system 1: software update device 10: controller 2: vehicle 20: vehicle-mounted terminal device 3: user terminal 30: controller 31: output device 4: communication network

Claims (17)

A software update device comprising a controller for managing software updates of a vehicle,
The controller:
an acquisition unit that acquires a vehicle state of the vehicle and a vehicle time indicating time information assigned to the vehicle state;
a transmission unit configured to transmit vehicle information including the vehicle state and the vehicle time to the user terminal in response to a command from the user terminal of the vehicle;
The user terminal,
When the time difference between the vehicle time and the current time measured by a timing unit of the user terminal is equal to or greater than a predetermined time, the software update device notifies the user of the vehicle state included in the vehicle information by emphasizing that the vehicle state included in the vehicle information is older than the vehicle state at the current time, more so than when the time difference is less than the predetermined time. The controller further includes an update control unit.
The software update device according to claim 1 , wherein the update control unit transmits update data for updating the software of the vehicle to the vehicle based on a software update execution command from the user terminal. The software update device according to claim 1, wherein the user terminal notifies the user that the instruction to execute a software update by the user will not be accepted if the time difference is equal to or greater than a predetermined time. the user terminal transmits a re-acquisition command to the controller to newly acquire the vehicle state when the time difference is equal to or greater than a predetermined time;
The software update device according to claim 3 , wherein the transmission unit transmits the vehicle information, including the vehicle state and the vehicle time reacquired from the vehicle, to the user terminal in response to the reacquisition command. The software update device according to claim 3 or 4, wherein the user terminal invalidates the input of an instruction to execute a software update by the user if the time difference is equal to or greater than a predetermined time. The software update device according to claim 5, wherein the user terminal changes the notification content notified to the user depending on whether the input of the instruction to execute the software update is invalid. The software update device according to claim 1, wherein the controller transmits a notification of the change in the vehicle state to the user terminal when the vehicle state changes. The software update device according to claim 7, wherein the controller rejects an instruction to execute a software update sent from the user terminal when it detects that the vehicle state has changed. The software update device according to claim 7, wherein the controller transmits a control signal to the user terminal to disable input of an instruction to execute a software update by the user when the controller detects that the vehicle state has changed. The software update device according to claim 1, wherein the controller transmits the changed vehicle state to the user terminal when the vehicle state changes. The controller:
When detecting that the change in the vehicle state has started, transmitting to the user terminal information that the change in the vehicle state has started;
The software update device according to claim 10 , wherein when it is detected that the change in the vehicle state has ended, the vehicle state after the change is transmitted to the user terminal. The controller:
The software update device of claim 1, wherein when there are multiple user terminals, when the vehicle state notified via one user terminal is updated, a control signal for updating the vehicle state notified via the other user terminal is transmitted to the other user terminal. The controller:
2. The software update device according to claim 1, wherein, when there are a plurality of user terminals, while a software update of the vehicle is being performed based on an instruction to execute a software update by one user, a control signal for disabling input of an instruction to execute a software update by the other user is transmitted to the user terminal of the other user. The software update device according to claim 12, wherein the controller transmits a control signal to the user terminal of the other user to notify the other user that a software update of the vehicle is being performed based on an instruction to perform a software update by the one user. A software update device including a controller that instructs a software update of a vehicle,
The controller:
an acquisition unit that acquires vehicle information including a vehicle state of the vehicle and a vehicle time indicating time information assigned to the vehicle state;
A timekeeping unit that keeps track of the current time;
a determination unit that determines whether a time difference between the vehicle time and the current time is equal to or greater than a predetermined time;
and a notification unit that, when the time difference is equal to or greater than a predetermined time, notifies a user of the vehicle of the vehicle state included in the vehicle information by emphasizing that the vehicle state included in the vehicle information is an older state than the vehicle state at the current time, compared to when the time difference is less than the predetermined time. 1. A software update method for managing software updates for a vehicle, the method comprising:
The controller:
Acquire a vehicle state of the vehicle and a vehicle time indicating time information assigned to the vehicle state;
Transmitting vehicle information including the vehicle state and the vehicle time to the user terminal in response to a command from the user terminal of the vehicle;
The user terminal,
A software update method that, when the time difference between the vehicle time and the current time measured by a timing unit of the user terminal is equal to or greater than a predetermined time, notifies the user of the vehicle state included in the vehicle information by emphasizing that the vehicle state included in the vehicle information is older than the vehicle state at the current time, more so than when the time difference is less than the predetermined time. Vehicles and
A server that manages software updates for the vehicle;
A software update system comprising: a user terminal that is operated by a user of the vehicle and is capable of communicating with the server,
The server,
Acquire a vehicle state of the vehicle and a vehicle time indicating time information assigned to the vehicle state;
Transmitting vehicle information including the vehicle state and the vehicle time to the user terminal;
The user terminal,
Measure the current time,
Comparing the vehicle time with the current time;
A software update system that notifies the user of the vehicle state contained in the vehicle information by emphasizing that the vehicle state contained in the vehicle information is older than the vehicle state at the current time when the time difference between the vehicle time and the current time is a predetermined time or more, compared to when the time difference is less than the predetermined time.