On-vehicle device
The in-vehicle device addresses frequent user inquiries by automating software updates based on software type, minimizing interruptions through intelligent permission determination.
Patent Information
- Application Number
- JP2023077115
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-09
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2043-05-09
AI Technical Summary
Frequent software updates lead to increased user inquiries, causing annoyance to users.
An in-vehicle device that manages software updates by determining the necessity of user permission based on software type, reducing inquiries through automated updates for certain types and prompting users only when necessary.
Reduces the frequency of user inquiries during software updates by automating updates for non-urgent or non-restrictive software, enhancing user experience.
Smart Images

Figure 2024161998000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an on-board device mounted in a vehicle. [Background technology]
[0002] As an example of such an on-board device, Patent Document 1 describes an on-board device that manages software updates for a vehicle. When updating software, the on-board device inquires of the user about whether or not the update is necessary and when to start the update. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2021-105923 A Summary of the Invention [Problem to be solved by the invention]
[0004] When software updates are performed frequently, the number of inquiries to the user also increases, and as a result, the user may feel annoyed by the frequent inquiries. [Means for solving the problem]
[0005] The vehicle-mounted device that solves the above problem is an on-board device that is mounted in a vehicle and manages software updates for the vehicle, and is equipped with a judgment unit that judges whether user consent is required based on the type of software, and a control unit that, when the judgment unit determines that user consent is required, queries the user as to whether or not to perform processing for updating the software. Effect of the Invention
[0006] The above-mentioned vehicle-mounted device has the effect of reducing the frequency of inquiries to the user regarding software updates. [Brief description of the drawings]
[0007] [Figure 1] FIG. 2 is a diagram illustrating a configuration of an embodiment of an in-vehicle device. [Diagram 2] FIG. 11 is a sequence diagram showing the flow of a software update process. [Diagram 3] 11 is a table showing an example of settings for whether or not user approval is required for each type of software. [Figure 4] FIG. 13 is a diagram showing an example of a consent screen. [Diagram 5] FIG. 13 illustrates an example of a selection screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0008] Hereinafter, one embodiment of the vehicle-mounted device will be described in detail with reference to FIGS. <In-vehicle device configuration> First, the configuration of the vehicle-mounted device of this embodiment will be described with reference to FIG.
[0009] The vehicle 10 is equipped with various ECUs (electronic control units) 15 that control various parts of the vehicle 10. Examples of the ECUs 15 include an engine ECU, a transmission ECU, a brake ECU, an advanced driving assistance ECU, and a multimedia ECU.
[0010] The vehicle 10 is also equipped with an OTA master 11, which is an on-board device that manages software updates in the vehicle 10. The OTA master 11 includes a processing circuit 12 and a storage device 13. A program for managing software updates is stored in advance in the storage device 13. The OTA master 11 is configured to perform processing related to the management of software updates by having the processing circuit 12 read and execute the program stored in the storage device 13. In this embodiment, the OTA master 11 corresponds to an on-board device that manages software updates of the vehicle 10. A wireless communication module 17 for performing outside-vehicle communication through a mobile communication network 18 is connected to the OTA master 11.
[0011] Furthermore, the vehicle 10 is equipped with an HMI (human machine interface) 16. The HMI 16 includes an input device that accepts operations by the occupant, and an output device that presents information to the occupant by image and sound. In this embodiment, the HMI 16 includes a navigation function that provides route guidance, and an entertainment function that plays music and video. The OTA master 11, each ECU 15, and the HMI 16 are configured to be able to communicate with each other via the in-vehicle network line 14.
[0012] Software updates in the vehicle 10 are performed based on update data distributed from an OTA server 20 via a mobile communication network 18 or the like. The OTA server 20 includes a processing circuit 21 and a storage device 22. The OTA server 20 is configured to be able to communicate with the outside via the mobile communication network 18.
[0013] Furthermore, the OTA master 11 and the OTA server 20 are configured to be able to communicate with a mobile terminal 30 of a user of the vehicle 10 via a mobile communication network 18 or the like. An example of the mobile terminal 30 is a smartphone. The mobile terminal 30 includes a processing circuit 31, a storage device 32, and an HMI 33. The processing circuit 31 reads and executes a program stored in the storage device 32. The programs stored in the storage device 13 include a program for vehicle management.
[0014] <Software updates> Next, software update of the vehicle 10 will be described. Specific software updates are performed on the software of the on-board electronic devices such as the OTA master 11, each ECU 15, and the HMI 16. In the following description, the on-board electronic devices that are the targets of software updates are referred to as target devices. Software updates are performed through three phases: download, installation, and activation.
[0015] In the download phase, software update data is downloaded to the vehicle 10. In the download phase, the OTA master 11 obtains the update data from the OTA server 20 and stores it in the storage device 13. The download phase includes a series of processes related to downloading, such as judging whether the download can be performed and verifying the update data. The update data transmitted from the OTA server 20 to the OTA master 11 may include any of update software, compressed data obtained by compressing the update software, and divided data obtained by dividing the update software or the compressed data. The update data may also include an identifier of the update device and an identifier of the software before the update. The update data is downloaded as a distribution package. The distribution package includes update data for one or more in-vehicle electronic devices.
[0016] In the installation phase, the update software is written to the target device. In the installation phase, the OTA master 11 writes the update software to the memory of the target device. The installation phase includes a series of processes related to the installation, such as judging whether the installation can be performed, transferring the update data, and verifying the update software. If the update data includes the update software itself, the OTA master 11 transfers the update data to the target device in the installation phase. If the update data includes compressed data, difference data, or split data of the update software, a process of generating the update software from the update data is performed. The generation process may be performed by the OTA master 11 or the target device. The update software can be generated by decompressing the compressed data and assembling the difference data or split data. Note that the update software is disabled when the installation phase is completed.
[0017] In the activation phase, the update program is activated on the target device. In other words, in the activation phase, the software used to operate the target device is switched from the pre-update software to the updated software. The activation phase includes a series of processes related to activation, such as determining whether activation can be performed, checking the consistency of the update program, and verifying the results of the activation.
[0018] Hereinafter, the process relating to the software update will be described in detail with reference to Fig. 2 to Fig. 4. Fig. 2 shows the flow of the process relating to the software update. As shown in FIG. 2, when updating software, the OTA server 20 first distributes campaign information to the vehicle 10 that is the target of the update. The campaign information includes information such as the vehicle model to be updated, the update contents, the start time of distribution of the update data, the size of the update data, and the expected time for the update. Note that update software is classified into a number of types depending on the in-vehicle electronic device to which it is applied, its functions, its importance, its urgency, and the like. The campaign information also includes information on the type of update software. The OTA master 11 obtains the type of software to be updated from such campaign information.
[0019] Thereafter, when the download of update data becomes executable, the OTA master 11 determines whether or not user permission is required for the execution of the download based on the type of update software. As described above, software update is performed through three phases: download, installation, and activation. In the vehicle-mounted device of this embodiment, whether or not user permission is required for the execution of each phase is set in advance for each type of software. The storage device 13 of the OTA master 11 stores in advance a data table regarding whether or not user permission is required for each phase for each type of software. The OTA master 11 determines whether or not user permission is required by referring to the data table.
[0020] Figure 3 shows an example of the structure of such a data table. In the case of Figure 3, type A software requires user consent for all of downloading, installing, and activating. Type B software requires user consent for downloading, but does not require user consent for installation and activation. Type C software does not require user consent for any of downloading, installing, and activating.
[0021] If the OTA master 11 determines that user permission is not required for the download, it automatically starts downloading the update data. When starting the download, the OTA master 11 requests the OTA server 20 to transmit the update data. In response to this request, the OTA server 20 transmits the update data to the OTA master 11. The OTA master 11 stores the received update data in the storage device 13.
[0022] On the other hand, if it is determined that user consent is required for the download, the OTA master 11 inquires of the user about permission to execute the download. When making the inquiry, the OTA master 11 first instructs the HMI 16 to display a permission screen. The HMI 16 displays the permission screen in response to this instruction. The permission screen is configured so that the user can select whether or not to permit the execution of the download of the update data. In the following description, a user operation that selects to permit the execution of the download is referred to as a permission operation. Also, a user operation that selects not to permit the execution of the download is referred to as a refusal operation. When the user performs the permission operation on the HMI 16 that displays the permission screen, the HMI 16 notifies the OTA master 11 that the user has permitted the download. The OTA master 11 starts downloading the update data in response to this notification.
[0023] Fig. 4 shows an example of the configuration of the permission screen. In the screen configuration examples of Figs. 4 and 5, software updates and update data are referred to as "system updates." The permission screen in Fig. 4 displays a message informing the user that downloading is possible, and the type and version of the software to be updated. The permission screen also displays buttons for selecting whether or not to permit the start of downloading. The permission screen may be configured to allow transition to a screen that displays detailed content of the software to be updated.
[0024] If the user rejects the request on the permission screen, the download of the update data is temporarily suspended. In this case, the OTA master 11 inquires about the user's permission again when the conditions for downloading are met again. When the user rejects the request, the user may be allowed to manually set the date and time for starting the download.
[0025] When installation can be performed after the download is complete, the OTA master 11 determines whether or not user permission is required to perform the installation based on the type of update data. If the OTA master 11 determines that user permission is not required, it automatically starts installing the update software on the target device. On the other hand, if it determines that user permission is required, the OTA master 11 makes an inquiry about user permission in the same way as in the case of downloading. Then, the OTA master 11 waits for user permission to be obtained before starting the installation. Specifically, the OTA master 11 instructs the target device to start the installation. Then, the OTA master 11 confirms that the installation is complete by receiving a completion notification from the target device.
[0026] Thereafter, when activation of the update software becomes possible, the OTA master 11 determines whether or not user permission is required to execute the activation, based on the type of update data. If the OTA master 11 determines that user permission is not required, it automatically starts the activation. On the other hand, if it determines that user permission is required, the OTA master 11 makes an inquiry about user permission in the same way as in the case of downloading or installing. Then, the OTA master 11 waits for user permission to be obtained before starting the activation. Specifically, the OTA master 11 instructs the target device to start the activation. Then, the OTA master 11 confirms that the activation has been completed by receiving a completion notification from the target device.
[0027] <Effects of the embodiment> The operation and effects of this embodiment will be described. An OTA master 11, which is one of the onboard devices mounted on the vehicle 10, manages software updates for the vehicle 10. When updating software, the OTA master 11 determines whether user consent is required based on the type of software to be updated. If the OTA master 11 determines that user consent is required, it queries the user as to whether or not to perform processing for updating the software. In this embodiment, the OTA master 11 corresponds to a determination unit and a control unit.
[0028] In addition, the OTA master 11 performs software updates in the vehicle 10 through three phases: downloading update data, installing the update program in the target device, and activating the update program. The OTA master 11 individually determines whether or not user consent is required in each of the above three phases.
[0029] Depending on the type of software, some software requires user consent for all three phases, while others do not. In the above embodiment, if user consent is not required, the update process proceeds automatically without asking the user. Therefore, the in-vehicle device of the above embodiment has the effect of reducing the frequency of asking the user questions when updating software.
[0030] <Setting whether user consent is required depending on the type of software> As described above, in this embodiment, the necessity of user consent in each phase of a software update is changed depending on the type of software. The type of software for which the necessity of user consent differs may be determined taking into consideration the software function, the urgency of the update, the time required for the update work, etc.
[0031] Some software updates have a deadline for completing the update. For example, in the case of software updates to comply with legal amendments, the updates must be completed before the laws come into force. In addition, for security reasons, there are also cases where software updates are required immediately. It is possible to set whether or not user consent is required, taking into consideration the urgency of such updates. In this case, software is classified into those with high and low urgency of updates. The OTA master 11 judges the urgency of the software update based on the type of software update. Then, when updating software with high urgency, the OTA master 11 automatically executes the update without inquiring about user consent. When updating software with low urgency, the OTA master 11 inquires about user consent and executes the update at the time desired by the user.
[0032] Depending on the software, the functions of the vehicle 10 may be restricted in some or all of the phases of the software update. For example, in the case of software for driving control of the vehicle 10, the vehicle 10 may be prohibited from driving during activation. On the other hand, depending on the type and phase of the software, the update work may be carried out without restricting the functions of the vehicle 10. It is possible to set whether or not user consent is required, taking into consideration the presence or absence of such functional restrictions during the update. In this case, the software is classified into those that have functional restrictions during the update and those that do not. Then, when functional restrictions occur, the update work is performed after obtaining user consent, while when functional restrictions do not occur, the necessity of user consent is set so that the update work is automatically performed. In addition, some functions of the vehicle 10 that are restricted during software update may be easily tolerated by the user. For example, even if the entertainment function of the HMI 16 is temporarily restricted, the user may be able to tolerate it as long as the vehicle 10 can be driven. Therefore, even when functional restrictions occur, the necessity of user consent may be switched depending on the content of the restriction.
[0033] There are software updates that require long and short update times. If the functions of the vehicle 10 are restricted during the update, the longer the update time, the longer the time the functions are restricted. It is possible to set whether or not user permission is required taking such update work time into consideration. In this case, software is classified into software that requires long and short update work. Then, whether or not user permission is required is set so that if the update work takes a long time, the update work is performed after obtaining user permission, whereas if the update work takes a short time, the update work is performed automatically.
[0034] (Other embodiments) <User settings for permission required> In the above embodiment, the OTA master 11 determines whether or not user consent is required based on a data table stored in advance in the storage device 13. The user may manually set whether or not user consent is required for each phase of each type of software.
[0035] Fig. 5 shows an example of the configuration of a setting screen displayed on the HMI 16 for such manual configuration. This example of the configuration of the setting screen is configured so that the user can manually switch whether or not user consent is required for each phase of each type of software.
[0036] Also, the types of software that require user consent and the types of software that do not require user consent may be learned based on the user's selection results, for example, as follows. Immediately after the start of learning, when the OTA master 11 receives campaign information, it displays the following selection screen on the HMI 16. The selection screen displays the contents of the update and buttons for the user to select whether or not user consent is required for each phase. The OTA master 11 determines whether or not user consent is required for each phase of the current software update according to the user's selection result on the selection screen. In addition, the OTA master 11 stores the user's selection result on the selection screen together with the corresponding software type. In this way, the OTA master 11 learns the selection result of whether or not user consent is required for each software type. When the software is updated multiple times and learning is completed, the OTA master 11 omits displaying the selection screen and determines whether or not user consent is required based on the learning result.
[0037] Furthermore, the above embodiment can be modified as follows: This embodiment and the following modified examples can be combined with each other to the extent that there is no technical contradiction. In the above embodiment, the OTA master 11 judges whether user permission is required for each phase of download, installation, and activation individually. The judgment for each phase may be performed collectively. That is, after receiving campaign information, the OTA master 11 judges whether user permission is required for each phase and records the judgment result. Then, in each phase, the OTA master 11 decides whether user permission is required based on the recorded judgment result.
[0038] In the above embodiment, the OTA master 11 determines whether or not user consent is required for each of download, installation, and activation. However, the timing of determining whether or not user consent is required during the software update process and the number of times the determination is performed may be changed.
[0039] The vehicle-mounted device of the above embodiment may be configured so that a permission screen such as that shown in FIG. 4 is displayed on the HMI 33 of the user's mobile terminal 30, and the user performs a permission operation on the HMI 33.
[0040] Either or both of the determination of whether user permission is required and the inquiry about user permission, which were performed by the OTA master 11 in the above embodiment, may be performed by another in-vehicle device. For example, the target device for the software update may perform at least one of the above determination and inquiry. In that case, the in-vehicle device that performs the determination corresponds to the determination unit, and the in-vehicle device that performs the inquiry corresponds to the control unit. The in-vehicle device in the above embodiment may be configured by multiple in-vehicle devices, such as when the determination unit and the control unit correspond to different in-vehicle devices. [Explanation of symbols]
[0041] 10 Vehicles 11 OTA Master 12 Processing circuit 13 Storage device 14 In-vehicle network lines 15 ECU 16 HMI 17 Wireless communication module 18 Mobile communication networks 20 OTA Server 21 Processing circuit 22 Storage device 30 Mobile Devices 31 Processing circuit 32 Storage device 33 Human Machine Interface
Claims
1. An in-vehicle device that is mounted in a vehicle and manages software updates for the vehicle, a determination unit that determines whether or not user consent is required based on the type of the software; a control unit that, when the determination unit determines that the user's consent is necessary, inquires of a user as to whether or not to perform a process for updating the software; An in-vehicle device comprising:
2. The software update is carried out in three phases: downloading the update data, installing the update on the in-vehicle device to be updated, and activating the update. The vehicle-mounted device according to claim 1 , wherein the determination unit determines whether or not the user's permission is required for the execution of each of the three phases individually.
3. 2 . The vehicle-mounted device according to claim 1 , wherein the user is able to select the type of software for which the determination unit determines that the user's consent is required and the type of software for which the determination unit determines that the user's consent is not required.
4. The vehicle-mounted device according to claim 1 , wherein the control unit performs the inquiry through a human-machine interface mounted on the vehicle.
5. The vehicle-mounted device according to claim 1 , wherein the control unit performs the inquiry through a mobile terminal of the user.
Citation Information
Patent Citations
Software managing system, and managing server, for wheeled vehicles, and wheeled vehicle
JP2017167646A
Vehicle electronic control system, screen display control method for progress display, and screen display control program for progress display
JP2021009658A
Software update device, software update system, and software update method
JP2023018282A
Software update apparatus and software update control method
JP2023018286A
Vehicle, software update system and software update method
JP2021105923A
Cited By
Remote parking control device for vehicles
CN123123400A
Enzymatic process for obtaining 17 alpha-monoesters of cortexolone and / or its 9,11-dehydroderivatives
US12337002B2
