JP7435100B2 - Program update system and vehicle management server - Google Patents

Description

The present disclosure relates to a system for updating a program of an electronic device installed in a vehicle or the like, and a vehicle management server included in the system.

A vehicle is equipped with multiple electronic devices called ECUs (Electronic Control Units). In-vehicle devices such as ECUs each include one or more control units such as a CPU and a storage unit storing one or more programs executed by the control units, and execute respective functions. In order to improve the functionality of electronic devices, it has been proposed to update programs stored in storage units by rewriting them to newer versions. In particular, it has been proposed that a vehicle receive program update data from an external server via wireless communication so that the program can be updated without going to a maintenance shop or the like.

Patent Document 1 discloses a program update system for updating a program installed in an ECU installed in a vehicle. In this system, the management device manages version information and update files for each vehicle ID, so based on the vehicle ID sent from the ECU, if the program installed in the ECU is not the latest version, As far as possible, distribution efficiency is improved by sending update files to the ECU.

Japanese Patent Application Publication No. 2011-148398

Regardless of the contents updated by the update program, update status (completion notifications and permission requests) should be displayed to vehicle users, passengers, etc. (hereinafter referred to as "vehicle users") as the update process progresses. If it is put away, the vehicle user may feel troubled. On the other hand, if no update status is displayed to the vehicle user regardless of the progress of the update process, the vehicle user may feel uneasy.

The present disclosure has been made in view of the above problems, and aims to provide a program update system and a vehicle management server that can reduce the annoyance and anxiety felt by vehicle users.

In order to solve the above problems, one aspect of the disclosed technology is a vehicle management server that transmits to the vehicle an update program for updating an existing program of an electronic device installed in a vehicle, and that communicates with the vehicle. The vehicle includes a communication unit and a control unit that controls update processing, and the control unit determines whether or not to present a display regarding update processing of existing programs by the update program to the vehicle user, depending on the type of the update program. Then, information for causing a predetermined information terminal to display a display related to the update process that has been decided to be presented to the vehicle user is transmitted to the vehicle via the communication unit.

Further, another aspect of the disclosed technology includes a vehicle, a vehicle management server that communicates with the vehicle, and transmits to the vehicle an update program for updating an existing program of electronic equipment installed in the vehicle; A program update system including a communicable information terminal, wherein the vehicle management server determines whether or not to present a display regarding update processing of existing programs by the update program to the vehicle user, depending on the type of the update program. Information for displaying on the information terminal a display related to the update process that has been determined and decided to be presented to the vehicle user is transmitted to the vehicle.

According to the program update system and vehicle management server of the disclosed technology, it is possible to reduce the annoyance and anxiety felt by vehicle users.

A diagram showing a configuration example of a program update system according to an embodiment Diagram showing an example of an update scenario stored in the storage unit of the vehicle management server Flowchart of the process of selecting an update scenario to be linked to an update program performed by the control unit of the vehicle management server

The program update system according to the disclosed technology provides a server with a plurality of update scenarios that define update events (completion notifications and permission requests) that cause an information terminal to display an update status display based on the type of update program, etc. keep it. When updating a program, the server sends information to the vehicle to cause the information terminal to display a display corresponding to an update event defined in an update scenario linked to the update program. This reduces the annoyance and anxiety felt by vehicle users regarding the display of update status during program update processing.

<Embodiment>
Hereinafter, one embodiment of the disclosed technology will be described in detail with reference to the drawings.

[composition]
FIG. 1 is a diagram illustrating a configuration example of a program update system according to an embodiment. The program update system 10 illustrated in FIG. 1 includes a vehicle 100, a vehicle management server 200, and a mobile device 300. Vehicle 100 includes a communication device 110, a plurality of electronic devices 120, and a display device 130. Note that the number of electronic devices 120 is not limited.

The communication device 110, the plurality of electronic devices 120, and the display device 130 are communicably connected via an in-vehicle network such as a CAN (Controller Area Network). Furthermore, the communication device 110 is a data communication module (DCM) or the like, and is communicably connected to devices outside the vehicle such as the vehicle management server 200 and mobile device 300 via a wireless network such as 4G or Wi-Fi. There is.

The vehicle management server 200 is a server that manages update programs necessary for updating existing programs of the electronic device 120 mounted on the vehicle 100. This vehicle management server 200 includes a communication section 210, a storage section 220, and a control section 230. The communication unit 210 performs wireless communication with the communication device 110 of the vehicle 100 to accept update inquiries from the vehicle 100, download update programs to the vehicle 100, and the like. The storage unit 220 stores update programs and update scenarios necessary for updating existing programs of the electronic device 120. The update scenario is information that defines notifications and requests (described later) that are update events displayed regarding the update process, such as update status indicating the progress of the program update process, and depending on the type of update program. Associated with updates. The control unit 230 controls the vehicle management server 200 including update processing. The control unit 230 can determine, for each of a plurality of update statuses, whether or not to present a display regarding each update status to the vehicle user, depending on the type of update program, for example. In this embodiment, the control unit 230 determines the display related to the update status to be presented to the vehicle user by selecting an update scenario from the storage unit 220 according to the type of update program.

FIG. 2 is a diagram showing an example of an update scenario stored in the storage unit 220 of the vehicle management server 200. In the example of FIG. 2, the content updated by the update program (update content), which is the type of update program, the urgency determined in advance based on the content and importance of the update program (update urgency), and vehicle usage. Nine update scenarios are defined in which update events are determined based on whether or not automatic update is set by the user (automatic update setting).

An update event is information for displaying a display corresponding to the event on the screen of an information terminal having a display screen. The information terminals in this embodiment are the display device 130 and the mobile device 300. Examples of this update event include (1) an update start notification that notifies the start of the update process for the update program, and (2) permission to the vehicle user to download the update program from the vehicle management server 200 to the electronic device 120. (3) A data DL completion notification that notifies that the download of the update program has been completed from the vehicle management server 200 to the electronic device 120; (4) Starting an update process for an existing program using the update program. (5) a start-up permission request that requests permission from the vehicle user to start the update process of the existing program using the update program (that is, to change the control content); and (6) an example of an update completion notification that notifies that update processing of an existing program using an update program has been completed. Note that the update event may appropriately specify notifications and permission requests other than those described above. For example, there may be a notification that indicates the existence of a program to be updated, which is shown before an update start notification, or a request for permission to start an update using an update program, which indicates the progress of the update process.

The update contents, which are one of the types of update programs, include, for example, contents that change the control specifications of the actuators included in the vehicle 100 (update scenarios 1 to 8), and contents that do not change the control specifications of the actuators included in the vehicle 100 (update scenarios 1 to 8). Update scenario 9).

The contents (update scenarios 1 to 8) of changing the control specifications of the actuators provided in the vehicle 100 include, for example, the operation of equipment related to the behavior of the vehicle (the distance between the own vehicle and the preceding vehicle in driving support, the operation of automatic brakes, etc.). Vehicle users may The content allows you to recognize the changes before and after updating the program. The content of changing the control specifications of the actuator included in this vehicle 100 is to add a new function that was not previously installed in the vehicle 100, and in principle, permission from the vehicle user of the vehicle 100 is required for updating. (Update Scenarios 1 to 4) and improve the functions already installed in the vehicle 100 or add measures and countermeasures for the existing functions. It can be classified into content for which permission is not required (update scenarios 5 to 8).

On the other hand, the contents (update scenario 9) in which the control specifications of the actuators provided in the vehicle 100 are not changed include, for example, the act of a function that automatically collects vehicle driving data and transmits it to a predetermined data center (data to be collected). The content is such that the vehicle user cannot recognize the changes before and after updating the program, such as those that change the program type, upload timing of collected data, etc.). Regarding the program that does not change the control specifications of the actuator included in this vehicle 100 (update scenario 9), the program does not affect the vehicle user or the running of the vehicle, so the automatic update setting status and update urgency will be changed. Regardless, the update is defined so that the update can be performed without displaying any notification or permission request as an update event to the vehicle user.

The update urgency, which is one of the types of update programs, includes, for example, those with relatively low update urgency (update scenarios 1 and 5) and those with relatively high update urgency (update scenarios). 2, 3, 6, 7). Updates with a relatively low degree of urgency are defined so that updates can be performed while displaying all notifications to the vehicle user during the program update process. On the other hand, updates with a relatively high degree of urgency are further classified into two types depending on, for example, for which process during the update process update event information is to be displayed to the vehicle user.

The first category, in which the update has a relatively high degree of urgency, displays information about an update event that requests permission and/or provides notification for downloading an update program (update scenarios 2 and 6). The update event of the first category is, for example, an update program that wants to confirm with the vehicle user in advance whether data can be written to the vehicle 100 or notifies the vehicle user that the download of the update program has been completed. can be applied to. For example, an example is an update program that requires a huge amount of data and requires communication costs and communication time.

The second category, in which update urgency is relatively high, displays information about an update event that requests permission and/or provides notification for the activation process of a downloaded update program (update scenarios 3 and 7). This second category update event is, for example, an update program that wants to inform the vehicle user that the vehicle control will be changed from now on, or that wants to confirm in advance with the vehicle user whether or not the vehicle control can be changed. can be applied to. For example, an update program related to changes in vehicle behavior or ride comfort can be exemplified.

The automatic update settings are items that are provided in the vehicle 100 in advance and can be set arbitrarily by the vehicle user. If automatic updates are set to OFF, during the program update process from the update start notification to the update completion notification, updates will be performed based on the update scenario defined according to the update urgency described above. will be implemented (update scenarios 1-3, 5-7). On the other hand, if automatic updates are set to ON, during the program update process from the update start notification to the update completion notification, update events for vehicle users will be responded to regardless of the update urgency. It is defined so that updates can be performed without being displayed (update scenarios 4 and 8).

The electronic device 120 is, for example, a device called an ECU (Electronic Control Unit) that performs various controls of the vehicle 100. This electronic device 120 stores one or more programs executed by a control unit (not shown) such as a CPU in a storage unit (not shown) such as a RAM. The electronic device 120 communicates with the vehicle management server 200 using the wireless communication function of the communication device 110. Electronic device 120 updates the stored current program based on the update program received from vehicle management server 200. Note that not all electronic devices 120 of vehicle 100 need to be such program-updatable devices.

The display device 130 is an information terminal equipped with a display screen that displays update event information related to program update processing in the electronic device 120. The display device 130 receives an instruction to display a display corresponding to an update event transmitted from the electronic device 120 via the in-vehicle network, or an instruction to display a display corresponding to an update event transmitted from the vehicle management server 200 via the wireless network. Based on this, a predetermined notification or permission request screen is displayed. Examples of the display device 130 include a multi-information display mounted on the vehicle 100 and a car navigation device.

The mobile device 300 is an information terminal equipped with a display screen that receives and displays information on update events related to program update processing in the electronic device 120 via the communication device 110. The mobile device 300 receives an instruction to display a display corresponding to an update event transmitted from the electronic device 120 via the wireless network, or an instruction to display a display corresponding to an update event transmitted from the vehicle management server 200 via the wireless network. Based on this, a predetermined notification or permission request screen is displayed. As the mobile device 300, a general-purpose device such as a smartphone, a tablet device, or a personal computer owned by the vehicle user of the vehicle 100 can be exemplified.

Note that in the program update system 10 of FIG. 1, the display device 130 and the mobile device 300 are included in the configuration as information terminals that display update event information related to program update processing in the electronic device 120, but only one of the configurations is included. It may be. Additionally, components other than the display device 130 and the mobile device 300 may be included as an information terminal, as long as the information on the update event can be displayed and presented to the vehicle user. Further, the display device 130 and the mobile device 300 may be instructed to display update event information by the electronic device 120 that is performing the update, or the update status may be appropriately received from the electronic device 120 that is performing the update. The vehicle management server 200 may also do this.

[control]
With further reference to FIG. 3, the process executed by the vehicle management server 200 in the program update system 10 described above will be described. FIG. 3 is a flowchart showing a procedure for selecting an update scenario to be associated with an update program, which is performed by the control unit 230 of the vehicle management server 200 according to the present embodiment.

The process shown in FIG. 3 is started, for example, when the vehicle 100 makes an inquiry to the vehicle management server 200 regarding the update program stored in the storage unit 220 by the vehicle management server 200 as to whether or not the program is to be updated.

Step S301: The control unit 230 of the vehicle management server 200 determines whether the inquired update program for the vehicle 100 changes the control specifications of the actuators included in the vehicle 100. If the update program is to change the control specifications of the actuator (step S301, Yes), the process proceeds to step S302; if the update program is not to change the control specifications of the actuator (step S301, No), the process advances to step S307.

Step S302: The control unit 230 of the vehicle management server 200 determines whether automatic updating by the vehicle user is set in the vehicle 100. The information as to whether automatic updates are set may be included in the vehicle 100's inquiry as to whether or not to update the program and sent to the vehicle management server 200, or the vehicle management server 200 may send the information to the vehicle management server 200 after receiving the inquiry. 100 and may be acquired. If automatic update is set (step S302, YES), the process advances to step S306, and if automatic update is not set (step S302, no), the process advances to step S303.

Step S303: The control unit 230 of the vehicle management server 200 determines whether the update content of the update program adds a new function to the vehicle. If the update content is a function addition (step S303, YES), the process proceeds to step S304, and if the update content is not a function addition (step S303, no), the process proceeds to step S305.

Step S304: The control unit 230 of the vehicle management server 200 selects an update scenario depending on the urgency of updating the update program. In this embodiment, one of the update scenarios 1, 2, and 3 in FIG. 2 in which the update event is "notification and permission request" is selected. This selection determines the content of at least one of the data DL permission request and the activation permission request to be presented to the vehicle user as the update status. When the update scenario is selected, the update scenario selected in step S304 is linked to the update program, and the process ends.

Step S305: The control unit 230 of the vehicle management server 200 selects an update scenario depending on the urgency of updating the update program. In this embodiment, one of the update scenarios 5, 6, and 7 in FIG. 2 in which the update event is "notification and no permission request" is selected. This selection determines the content in which neither the data DL permission request nor the activation permission request is presented to the vehicle user as the update status. When the update scenario is selected, the update scenario selected in step S305 is linked to the update program, and the process ends.

Step S306: The control unit 230 of the vehicle management server 200 selects update scenario 4 or 8 in FIG. 2 in which the update event is only "update start notification and update completion notification". This selection determines the content of only the update start notification and update completion notification to be presented to the vehicle user as the update status. When the update scenario is selected, the update scenario selected in step S306 is linked to the update program, and the process ends.

Step S307: The control unit 230 of the vehicle management server 200 selects the update scenario 9 of FIG. 2 in which the update event is "no notification and no permission request." This selection determines the update status in which no notification or permission request is presented to the vehicle user. When the update scenario is selected, the update scenario selected in step S307 is linked to the update program, and the process ends.

In the update process of an update program that is associated with an update scenario, the vehicle management server 200 displays information regarding the update status that presents to the vehicle user a display that corresponds to an update event defined in the update scenario that is associated with the update program. Information to be displayed on display device 130 and/or communication device 110 as a display is transmitted to vehicle 100. For example, the vehicle management server 200 transmits an update scenario together with an update program to the vehicle 100, and the electronic device 120 that has received the update scenario sends a predetermined notification and/or notification according to the update scenario in accordance with the progress of the update process of the update program. Alternatively, the permission request can be displayed on the display device 130 and/or on the mobile device 300 via the communication device 110 or the vehicle management server 200. Alternatively, the vehicle management server 200 receives notification from the electronic device 120 of the progress of update processing of the update program, and sends a predetermined notification and/or permission request according to the update scenario to the communication device 110 according to the progress. The information may be displayed on the display device 130 and/or the mobile device 300 via the display device 130 and/or the mobile device 300.

In this embodiment, an update scenario is defined in which an update program is downloaded from the vehicle management server 200 to the vehicle 100 via wireless communication and an update process for an existing program is performed. However, an update scenario may be further defined in which an update process for an existing program is performed using an update program that needs to be updated at a repair shop such as a dealer. In such a case, a worker at a maintenance shop or the like performs the update process, so the vehicle user generally does not need to keep track of the progress of the update process each time. Therefore, as an update scenario, for example, only an update start notification or only an update completion notification can be defined as an update event.

Furthermore, in the present embodiment, the control unit 230 selects an update scenario for an update program based not only on the characteristics of the update program but also on the individual circumstances of the vehicle, such as the mileage of the vehicle acquired from the vehicle and the manufacturing period of parts. You may also do so based on

Furthermore, in the present embodiment, the control unit 230 may further control various displays based on the characteristics of the update program in relation to the above-described update scenario or separately from the update scenario. For example, if the update program is a program having the following characteristics (1) to (3), the control unit 230 acquires information representing this from the vehicle management server 200, and , mobile device 300). In this case, for example, it is preferable that the information terminal (display device 130, mobile device 300) display information in a manner that gives priority notification to the user prior to the update process to ensure that the user is aware of the information.
(1) Programs that are legally obligated to notify users that the program will be updated.
(2) Programs that reset individual vehicle settings, such as user-customized settings, and have a relatively large impact on convenience.
(3) An update program that is relatively large in size, requires a certain amount of time or more to complete the update process, requires a long stop at a garage or the like for the update process, and has a relatively large impact on convenience.

Further, in this embodiment, for example in update scenarios 4, 8, etc., the update start notification may include a notification indicating that the update will be forcibly executed without the consent of the user. Furthermore, in this case, it is preferable that the information terminal (display device 130, mobile device 300) display the information in a manner of preferentially notifying the user to ensure that the user is aware of the information. Furthermore, the display for notifying the forced execution of the update process may be performed independently of the display for notifying the start of the update.

[Action/Effect]
As described above, according to the program update system 10 according to an embodiment of the presently disclosed technology, the update event (completion notification or permission request) that is displayed based on the content of the update by the update program, the urgency of the update, and the vehicle A plurality of update scenarios defining the presence or absence of automatic update settings by the user are stored in advance in the vehicle management server 200. When updating the existing program of the electronic device 120, a display regarding the update status to be presented to the vehicle user determined according to the type of the update program, that is, an update event specified in the update scenario linked to the update program. The vehicle management server 200 transmits information for displaying a corresponding display on the information terminal (display device 130, mobile device 300) to the vehicle 100.

Through this processing, it is possible to suitably set the update status to be displayed on the information terminal such as the display device 130 or the mobile device 300 according to the type of the update program. Therefore, it is possible to reduce the annoyance and anxiety that the vehicle user feels regarding the display of the update status in the program update process.

An embodiment of the disclosed technology has been described above, and the disclosed technology includes not only a program update system and a vehicle management server, but also an update program transmission method, a control program for the method, and a computer readable computer that stores the control program. It is possible to think of it as a non-temporary storage medium, a vehicle equipped with a program update system, etc.

The disclosed technology is useful for a program update system for electronic equipment installed in a vehicle or the like, and a vehicle management server included in the system.

10 Program update system 100 Vehicle 110 Communication device 120 Electronic device 130 Display device 200 Vehicle management server 210 Communication unit 220 Storage unit 230 Control unit 300 Mobile device

Claims (6)

A vehicle management server that sends to the vehicle an update program for updating an existing program of an electronic device installed in the vehicle,
a communication unit that communicates with the vehicle;
A control unit that controls update processing;
The control unit includes:
determining whether to present a display regarding update processing of the existing program by the update program to the vehicle user, depending on the type of the update program;
determining to present a display regarding the update process to the vehicle user, and receiving information from the vehicle via the communication unit indicating that permission for automatic update by the vehicle user is set; In this case, among the displays related to the update process, only a notification of the start of the update process of the existing program by the update program and a completion notification of the update process of the existing program by the update program are presented to the vehicle user. and transmitting only a notification of the start of the update process and a notification of the completion of the update process to the vehicle via the communication unit,
has decided to present a display regarding the update process to the vehicle user, and has received information from the vehicle via the communication unit indicating that permission for automatic update by the vehicle user is not set. transmitting information for displaying a display related to the update process on a predetermined information terminal to the vehicle via the communication unit;
Vehicle management server. The control unit determines to present a display regarding the update process to the vehicle user when the update program is of a type that changes control specifications of an actuator included in the vehicle.
The vehicle management server according to claim 1. The control unit determines not to present a display related to the update process to the vehicle user when the update program is of a type that does not change control specifications of an actuator included in the vehicle.
The vehicle management server according to claim 1. The display related to the update process includes a notification of the start of update process of the existing program by the update program, a request for permission to download the update program from the vehicle management server to the electronic device, and a request for permission to download the update program from the vehicle management server to the electronic device. notification of completion of downloading of the update program; notification of completion of preparations for starting update processing of the existing program by the update program; request for permission to start update processing of the existing program by the update program; including a notification of completion of update processing and a notification of forced execution of update processing of the existing program by the update program;
The vehicle management server according to any one of claims 1 to 3. When the control unit receives information from the vehicle indicating that permission for automatic update by the vehicle user is not set via the communication unit, further:
If the update program adds a predetermined function to the vehicle and changes the control specifications of an actuator included in the vehicle, at least one of the permission requests must be sent to the vehicle user. decided to present it to
If the update program does not add a predetermined function to the vehicle and is of a type that changes the control specifications of actuators included in the vehicle, the permission request is presented to the vehicle user. decide not to
The vehicle management server according to claim 4. vehicle and
a vehicle management server that communicates with the vehicle and sends to the vehicle an update program for updating an existing program of an electronic device installed in the vehicle;
A program update system including an information terminal capable of communicating with the vehicle management server,
The vehicle management server is
determining whether to present a display regarding update processing of the existing program by the update program to the vehicle user, depending on the type of the update program;
If it is determined to present a display regarding the update process to the vehicle user, and information indicating that permission for automatic update by the vehicle user is set is received from the vehicle, the vehicle use out of the displays related to the update process, only a notification of the start of the process of updating the existing program by the update program and a notification of the completion of the process of updating the existing program by the update program are presented to the user, and Sending only a process start notification and a completion notification of the update process to the vehicle;
If it is determined to present a display regarding the update process to the vehicle user, and information indicating that permission for automatic update by the vehicle user is not set is received from the vehicle, the update process transmitting information to the vehicle for causing the information terminal to display a display related to the vehicle;
Program update system.