PROGRAM UPDATE SYSTEM, PROGRAM UPDATE SERVER, INFORMATION PROCESSING DEVICE, VEHICLE, METHOD, AND PROGRAM
The system enables efficient program updates for vehicles by allowing each in-vehicle device to communicate directly with a server, reducing the need for vehicle-specific master functions and enabling synchronized updates with remote user monitoring.
Patent Information
- Application Number
- JP2023016581
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-02-07
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2038-07-30
AI Technical Summary
Existing program update systems require a master ECU with different settings for each vehicle type and model, necessitating significant man-hours for preparation.
A system where each in-vehicle device communicates directly with a server to update its programs, eliminating the need for a vehicle-specific master function, and a server manages updates for all devices collectively, allowing synchronized updates without omissions.
Reduces the man-hours required for adapting to unique vehicle configurations, ensures synchronized updates, and allows users to instruct and monitor progress remotely through a terminal device like a smartphone.
Smart Images

Figure 0007582354000001 
Figure 0007582354000002 
Figure 0007582354000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a system, a server, an information processing device, a vehicle, a method, and a program for updating a program of a device mounted on a vehicle. [Background technology]
[0002] Vehicles are equipped with multiple on-board devices called ECUs (Electronic Control Units). Each on-board device such as an ECU has one or more control units such as a CPU and a memory unit that stores one or more programs executed by the control units. To improve the functionality of on-board devices, it has been proposed to update such programs. In particular, it has been proposed that the vehicle receive data for program updates from an external server via wireless communication so that programs can be updated without going to a repair shop or the like.
[0003] Patent Document 1 discloses that a specific ECU functions as a master ECU, communicates with a server, and updates the programs of the master ECU itself and other slave ECUs. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2011-148398 A Summary of the Invention [Problem to be solved by the invention]
[0005] In Patent Document 1, a master ECU holds identification information of the master ECU and slave ECUs and version information of the control programs. The master ECU transmits the identification information and version information to a server, and the server transmits the identification information and the update file to the master ECU if an update file is available. If the ECU corresponding to the identification information is the master ECU, the master ECU updates the control program of the master ECU based on the update file, and if the ECU corresponding to the identification information is a slave ECU, the master ECU transmits the update file to the slave ECU, and the slave ECU updates the control program based on the update file.
[0006] In the method of Patent Document 1, the master ECU needs to perform processing that depends on the ECU configuration specific to the vehicle it is installed in. Therefore, in order to accommodate different ECU configurations, it is necessary to prepare a master ECU with different settings for each vehicle model and type, which requires a lot of man-hours.
[0007] An object of the present invention is to provide a program update system and the like that can reduce the number of steps required to prepare a master ECU corresponding to a unique in-vehicle device configuration for each vehicle. [Means for solving the problem]
[0008] In order to solve the above problem, one aspect of the present invention is a program update system comprising a vehicle including a plurality of on-board devices and a server provided outside the vehicle, wherein each on-board device of the vehicle has a memory unit that stores one or more programs, an on-board device side communication unit that communicates with the server, and an update execution unit that updates the program stored in the memory unit based on communication with the server by the on-board device side communication unit, and the server has a server side communication unit that communicates with each on-board device, and an update management unit that identifies on-board devices to be updated and programs to be updated in a set of multiple on-board devices based on information received from each on-board device through communication by the server side communication unit, and executes an update process to cause the server side communication unit to send update data for updating the programs to be updated to the on-board devices to be updated.
[0009] This allows each in-vehicle device to communicate with the server and update its own program, eliminating the need to provide the vehicle with an advanced master function for managing the configuration and program version of the in-vehicle device. In addition, the server identifies the update targets for the entire set of in-vehicle devices in the vehicle, which can prevent, for example, omissions in synchronous updates.
[0010] In addition, the server-side communication unit may further communicate with a terminal device outside the vehicle, and the update management unit may cause the server-side communication unit to transmit information regarding the update process to the terminal device to be displayed on the display screen of the terminal device.
[0011] This allows the user to give instructions for program update processing and check the progress status even when not in the vehicle, using a smartphone, etc. Also, since the server can handle the communication method and display method of the terminal device, it is not necessary to handle each vehicle separately.
[0012] Another aspect of the present invention is a program update server comprising a server capable of communicating with a vehicle including a plurality of on-board devices, the program update server having a communication unit that communicates with each of the plurality of on-board devices, and an update management unit that executes an update process to identify an on-board device to be updated and a program to be updated in a set of the plurality of on-board devices based on information received from each on-board device, and to cause the communication unit to transmit update data for updating the program to be updated to the on-board device to be updated.
[0013] This allows the server to communicate with each on-board device in sequence and identify all update targets for the entire set of on-board devices in the vehicle, making it possible to update programs without providing the vehicle with an advanced master function for managing the configuration of the on-board devices and program versions.
[0014] Another aspect of the present invention is a vehicle including a plurality of on-board devices, each of which has a memory unit that stores one or more programs, a communication unit that communicates with an external server, and an update execution unit that updates the program stored in the memory unit based on communication with the external server by the communication unit.
[0015] This allows each vehicle-mounted device to communicate with the server in sequence to update its own program, making it possible to update programs without the need to provide the vehicle with an advanced master function for managing the configuration and program versions of each vehicle-mounted device. Effect of the Invention
[0016] As described above, according to the present invention, it is possible to provide a program update system and the like that reduces the number of steps required to accommodate the in-vehicle device configuration for each vehicle, such as providing the above-mentioned master function. [Brief description of the drawings]
[0017] [Figure 1] FIG. 1 is a diagram showing functional blocks of a program update system according to an embodiment of the present invention. [Diagram 2] FIG. 1 is a sequence diagram showing an example of a process according to an embodiment of the present invention. [Diagram 3] FIG. 1 is a diagram showing an example of data used in processing according to an embodiment of the present invention; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0018] (overview) In the program update system according to the present invention, each in-vehicle device sequentially communicates with the server to update its own program. This reduces the labor required to provide the vehicle with an advanced master function that manages the configuration and program versions of the in-vehicle devices. The server identifies the update targets for the entire set of in-vehicle devices in the vehicle, which can prevent, for example, omissions in synchronous updates. The server can communicate with smartphones, etc., so that the user can issue instructions for program update processing and check the progress even when outside the vehicle. The server can handle the communication method and display method for smartphones, etc., so no labor is required to handle each vehicle separately.
[0019] (Embodiment) Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
[0020] <Configuration> 1 shows functional blocks of a configuration example of a program update system 100 and a terminal device 3 according to this embodiment. The program update system 100 includes a vehicle 1 and a server 2. As an example, the vehicle 1 includes a DCM (data communication module) 15 that performs wireless communication, and three in-vehicle devices 10A, 10B, and 10C, although the number of in-vehicle devices is not limited to three. The server 2 includes a server-side communication unit 21 and an update management unit 22.
[0021] Each of the in-vehicle devices 10A, 10B, and 10C of the vehicle 1 has a storage unit 11, an in-vehicle device side communication unit 12, and an update execution unit 13. In the in-vehicle devices 10A, 10B, and 10C, the storage unit 11 stores one or more programs executed by a control unit (CPU) not shown. The in-vehicle device side communication unit 12 communicates with the server 2 using a wireless communication function of the DCM 15. The update execution unit 13 updates the program by storing a new program in the storage unit 11 based on update data that the in-vehicle device side communication unit 12 receives from the server 2. The functions of the in-vehicle device side communication unit 12 and the update execution unit 13 can be executed by the control unit. Also, all the in-vehicle devices of the vehicle 1 do not have to be in-vehicle devices capable of such program updates.
[0022] The server-side communication unit 21 of the server 2 communicates with the vehicle 1 and the terminal device 3. The update management unit 22 identifies the in-vehicle devices to be updated among the in-vehicle devices 10A, 10B, and 10C of the vehicle 1 through communication with the vehicle 1 via the server-side communication unit 21, and further identifies the program to be updated as described below. The update management unit 22 also controls the server-side communication unit 21 to transmit update data used to update the program to be updated to the in-vehicle device to be updated.
[0023] The terminal device 3 is an information processing device that has a communication function with the server 2 and is equipped with a display screen that displays information related to the program update process and an input unit. The terminal device 3 is typically a general-purpose information processing device owned by the user of the vehicle 1, such as a smartphone, a tablet device, or a personal computer. The terminal device 3 may be a device that is mounted on the vehicle 1, such as a car navigation device. In this way, the type, number, and location of the terminal devices 3 are not limited.
[0024] <Processing> Fig. 2 is a sequence diagram showing the process performed by the program update system 100. Fig. 3 shows an example of data used in this process. The process content will be described with reference to Fig. 2 and Fig. 3. This process may be executed periodically, for example, or may be executed in response to an instruction from the user to the terminal device 3, as described later.
[0025] (Step S101): The update execution unit 13 of the in-vehicle device 10A of the vehicle 1 transmits information such as an identifier representing the type and version of a program stored in the memory unit 11 of the vehicle 1 from the in-vehicle device side communication unit 12 to the server 2 via the DCM 15 of the vehicle 1.
[0026] (Step S102): The update execution unit 13 of the in-vehicle device 10B of the vehicle 1 similarly transmits information such as an identifier representing the type and version of the program stored in its own memory unit 11 from the in-vehicle device side communication unit 12 to the server 2 via the DCM 15 of the vehicle 1.
[0027] (Step S103): The update execution unit 13 of the in-vehicle device 10C of the vehicle 1 similarly transmits information such as an identifier representing the type and version of the program stored in the storage unit 11 of the vehicle 1 from the in-vehicle device side communication unit 12 to the server 2 via the DCM 15 of the vehicle 1. The order of steps S101 to S103 is not limited.
[0028] 3(a) shows an example of information acquired by the server 2 from each of the in-vehicle devices 10A, 10B, and 10C. The update management unit 22 of the server 2 acquires, via the server-side communication unit 21, information indicating the types and versions of, for example, four, two, and one programs, respectively, from the in-vehicle devices 10A, 10B, and 10C, and a unique management number that identifies a series of processes in this sequence.
[0029] (Step S104): The update management unit 22 of the server 2 identifies the system version of the set of the on-board devices 10A, 10B, 10C of the vehicle 1 based on the identifier of the current program for this set. The identification can be performed, for example, by storing the association between the on-board devices 10A, 10B, 10C and the program version for each system version in the server 2 and comparing this with the current program versions of the on-board devices 10A, 10B, 10C. An example of data indicating the identified current system version is shown in (b) of FIG. 3.
[0030] (Step S105): The update management unit 22 of the server 2 checks the updated system version for the current system version. Information on the updated system version and the update program are provided to the server 2, for example, every time an update occurs from the program provider. An example of data representing the updated system version is shown in (c) of FIG. 3. In the example shown in (c) of FIG. 3, updated programs have been provided for two of the programs of the in-vehicle device 10A and two of the programs of the in-vehicle device 10B.
[0031] (Step S106): The update management unit 22 of the server 2 causes the server side communication unit 21 to transmit to the terminal device 3 the confirmation result of the updated system version.
[0032] (Step S107): The terminal device 3 receives the confirmation result of the updated system version and displays it to the user. If there is no updated system version, a message to that effect is displayed, and this sequence ends.
[0033] (Step S108): The terminal device 3 receives an instruction from the user indicating whether or not to execute a program update.
[0034] (Step S109): The terminal device 3 transmits the instruction received from the user to the server 2.
[0035] (Step S110): If the user's instruction is an instruction not to execute a program update, the update management unit 22 of the server 2 ends the process. If the user's instruction is an instruction to execute a program update, the update management unit 22 of the server 2 causes the server-side communication unit 21 to transmit update data required to update the program to the in-vehicle device having the storage unit 11 that stores the program to be updated, among the in-vehicle devices 10A, 10B, and 10C. In the example shown in FIG. 3(d), update data for two programs is transmitted to the in-vehicle device 10A, and update data for two programs is transmitted to the in-vehicle device 10B, but since there is no program to be updated in the in-vehicle device 10C, no update data is transmitted.
[0036] (Step S111): When the in-vehicle device 10A of the vehicle 1 receives update data via the DCM 15 through the in-vehicle device side communication unit 12, the update execution unit 13 updates the program stored in the memory unit 11 of the vehicle 1 based on the update data, and also updates the information representing the version of the program.
[0037] (Step S112): Similarly, when the in-vehicle device side communication unit 12 of the in-vehicle device 10B of the vehicle 1 receives update data via the DCM 15, the update execution unit 13 updates the program stored in the memory unit 11 of the vehicle 1 based on the update data, and also updates the information representing the version of the program.
[0038] (Step S113): Similarly, when the in-vehicle device side communication unit 12 receives update data via the DCM 15, the update execution unit 13 of the in-vehicle device 10C of the vehicle 1 updates the program stored in the storage unit 11 of the in-vehicle device 10C based on the update data, and also updates the information indicating the version of the program. In the example shown in Fig. 3(d), since there is no update to the program of the in-vehicle device 10C, this process is not executed.
[0039] This ends the sequence. The above process can be modified as appropriate. For example, after steps S111 to S113 are executed, the in-vehicle devices 10A, 10B, and 10C may notify the server 2 of the completion of the program update, and the server 2 may transmit the completion notification to the terminal device 3 to notify the user. Furthermore, the server 2 may notify the user of the progress status by transmitting the progress status of each step to the terminal device 3 in parallel with the progress of the update process. Furthermore, the execution of the above sequence may be started by the terminal device 3 accepting an execution instruction from the user and transmitting it to the server 2, and the server 2 requesting the in-vehicle devices 10A, 10B, and 10C to execute the processes of steps S101 to S103.
[0040] (effect) In this embodiment, the in-vehicle devices 10A, 10B, and 10C sequentially transmit the type and version of their programs to the server 2, and the server 2 can identify the system version for each vehicle. The server 2 can store and manage such system versions collectively for each vehicle model and type, and the vehicle does not need an in-vehicle device having an advanced master function for acquiring and managing the configuration and program type and version of the in-vehicle device for each vehicle, so that the number of steps required can be significantly reduced. Note that the adjustment of the communication timing between the in-vehicle devices 10A, 10B, and 10C and the server 2 can be achieved, for example, by providing the vehicle 1 with a simple communication control function. Any one of the in-vehicle devices 10A, 10B, and 10C may operate as a simple master having such a minimum communication control function.
[0041] In addition, the server 2 manages versions in system version units as a set of the multiple in-vehicle devices 10A, 10B, and 10C as a whole, and checks whether or not there is an update program. This is preferable because, for example, even if the programs of the multiple in-vehicle devices are related to each other and program updates need to be executed synchronously, the updates can be executed without missing any synchronous updates.
[0042] Conventionally, the progress of the program update process was confirmed and an update instruction from the user before the update process was received by a specific terminal device, such as a navigation device fixedly installed in the vehicle, and a master function of the vehicle. In contrast, in this embodiment, the server 2 can communicate not only with the navigation device fixedly installed in the vehicle, but also with a terminal device 3 that is not fixedly installed in the vehicle, such as a smartphone or a personal computer, so that even if the user is not in the vehicle, the user can issue instructions for the program update process and check the progress, improving user convenience.
[0043] Furthermore, the server 2 can handle the communication method, display method, and so on, of each terminal device 3, and there is no need to handle each vehicle separately.
[0044] As described above, in the program update system according to the present invention, the labor required to manufacture a master ECU corresponding to the on-board equipment configuration of each vehicle can be reduced, thereby reducing the cost of the vehicle, and further, it is possible to issue update instructions and check the update status from a variety of terminal devices, thereby improving user convenience.
[0045] Although an embodiment of the present invention has been described above, the present invention can be understood as a program update system, a program update server, a vehicle, or a program update method executed by each part of the server or vehicle, a program update program, and a computer-readable non-transitory recording medium storing the program, etc. [Industrial Applicability]
[0046] The present invention is useful for a program updating system for updating a program for an in-vehicle device or the like. [Explanation of symbols]
[0047] 1 vehicle 2 Server 3 Terminal Equipment 10A, 10B, 10C automotive equipment 11 Storage section 12 In-vehicle equipment side communication section 13 Update Execution Department 15 DCM 21 Server-side communication section 22 Update Management Department 100 Program Update System
Claims
1. An information processing device that is not fixedly installed in a vehicle, A first receiving unit that receives information indicating whether or not an update program is available for a system version of the vehicle, the information being confirmed based on an identifier of a program of an in-vehicle device that is associated with the information processing device; a reception unit that receives, when the first reception unit receives the information, an instruction from a server to transmit the update program to the in-vehicle device that is to be updated; and a second receiving unit that, when the receiving unit receives the instruction, receives a progress status of the transmission process in parallel with the transmission process of the update program from the server to the in-vehicle device to be updated.
2. The information processing apparatus according to claim 1 , further comprising a display unit that performs a display related to the information received by the first receiving unit.
3. The information processing device according to claim 1 , further comprising a notification unit that notifies a user of the vehicle of the progress status of the transmission process received by the second receiving unit.
4. The information processing device according to claim 1 , wherein the reception unit receives an instruction from a user of the vehicle indicating whether or not to execute an update of the program.
5. The information processing device according to claim 1 , wherein the information processing device is a smartphone or a tablet device.
6. A method executed by a computer of an information processing device that is not fixedly installed in a vehicle, comprising: receiving information indicating the presence or absence of an update program for a system version of the vehicle, the information being confirmed based on an identifier of a program of an in-vehicle device mounted on the vehicle associated with the information processing device; receiving, when the information is received, an instruction from a server to transmit the update program to the vehicle-mounted device to be updated; when the instruction is received, receiving a progress status of the transmission process from the server in parallel with the process of transmitting the update program to the in-vehicle device to be updated.
7. A program to be executed by a computer of an information processing device that is not fixedly installed in a vehicle, receiving information indicating the presence or absence of an update program for a system version of the vehicle, the information being confirmed based on an identifier of a program of an in-vehicle device mounted on the vehicle associated with the information processing device; receiving, when the information is received, an instruction from a server to transmit the update program to the vehicle-mounted device to be updated; and when the instruction is received, receiving a progress status of the transmission process from the server in parallel with the process of transmitting the update program to the in-vehicle device to be updated.
Citation Information
Patent Citations
Program update system for vehicle
JP2011148398A
Software managing system, and managing server, for wheeled vehicles, and wheeled vehicle
JP2017167646A
In-vehicle device
JP2017220092A
