Server, Program, and Software Update Method

Abstract

To improve user convenience in updating software for vehicle control devices.SOLUTION: An OTA center 1 transmits data for updating the software of individual ECUs 22 via wireless communication. The OTA center 1 includes a memory 112 in which a program is stored and a processor 111 that executes the program. The processor 111 sets first data to be displayed on an in-vehicle display 27 to obtain a user's permission for updating the software and second data to be displayed on a user terminal 3 to obtain the user's permission for updating the software. The information granularity of the first data is higher than that of the second data.SELECTED DRAWING: Figure 8

Description

Technical Field

[0001] The present disclosure relates to a server, a program, and a software update method.

Background Art

[0002] Research and development of OTA (Over The Air) technology for updating software (vehicle control program) stored in a vehicle control device (ECU: Electronic Control Unit) by wireless communication has been underway. For example, Japanese Unexamined Patent Application Publication No. 2017-149323 (Patent Document 1) discloses a vehicle control system capable of safely updating software without impairing user convenience. When it is determined that the location of the electronic key of the vehicle is inside the vehicle, the portable device transmits a signal requesting download of the update software to the server. The ECU downloads the update software transmitted from the server via the portable device and updates the software.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] When updating software of electrical devices such as personal computers and smartphones, it is common to condition on the user's permission. Similarly, it is conceivable to obtain the user's permission in advance for updating the software of the ECU.

[0005] The software update of electrical equipment is mainly carried out at the user's home. In contrast, the software update of the ECU may be carried out at the user's home or at the user's destination. Regardless of the situation of the user during the software update, it is desirable to appropriately provide the user with data for obtaining the user's permission without impairing the convenience for the user.

[0006] This disclosure is made to solve the above problems, and one of the objects of this disclosure is to improve the convenience of the user in the software update of the ECU.

Means for Solving the Problems

[0007] (1) The server according to one aspect of the present disclosure transmits data for updating the software of the vehicle control device by wireless communication. The server includes a memory storing a program and a processor executing the program. The processor sets first data to be displayed on the in-vehicle display to obtain the user's permission regarding the software update and second data to be displayed on the user terminal to obtain the user's permission regarding the software update. The information granularity of the first data is higher than that of the second data.

[0008] (2) The amount of character information included in the first data is larger than the amount of character information included in the second data.

[0009] (3) The first data includes video information. The second data does not include video information. (4) When the user further views the second data using the user terminal after viewing the first data halfway using the in-vehicle display, the processor sets the second data displayed on the user terminal to be a continuation of the first data viewed halfway using the in-vehicle display.

[0010] (5) When the user further views the first data using the in-vehicle display after viewing the second data partway through using the user terminal, the processor sets the first data displayed on the in-vehicle display to be the continuation of the second data that the user has viewed partway through using the user terminal.

[0011] (6) When the user further views the first data using the in-vehicle display after viewing the second data partway through using the user terminal, for the part of the second data that the user has already viewed using the user terminal, the processor also sets it to be the first data displayed on the in-vehicle display.

[0012] (7) A program according to another aspect of the present disclosure causes a computer to execute for updating the software of the vehicle control device by wireless communication. When the program is executed by the computer, the computer is caused to perform steps of setting first data to be displayed on the in-vehicle display and second data to be displayed on the user terminal in order to obtain the user's permission regarding software update, and displaying the corresponding data of the first data and the second data on at least one of the in-vehicle display and the user terminal. The information granularity of the first data is higher than that of the second data.

[0013] (8) A software update method according to still another aspect of the present disclosure updates the software of the vehicle control device by wireless communication. The software update method includes steps of setting first data to be displayed on the in-vehicle display and second data to be displayed on the user terminal in order to obtain the user's permission regarding software update, and displaying the corresponding data of the first data and the second data on at least one of the in-vehicle display and the user terminal. The information granularity of the first data is higher than that of the second data.

Advantages of the Invention

[0014] According to the present disclosure, the convenience of the user can be improved in the software update of the ECU.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Embodiments for Carrying Out the Invention

[0016] [Embodiment] <System Configuration> FIG. 1 is a diagram showing a schematic configuration of an information processing system according to an embodiment of the present disclosure. The information processing system 100 includes an OTA center 1, a vehicle 2, and a user terminal 3. The OTA center 1 is communicably connected to the vehicle 2 and the user terminal 3 via a wired or wireless network NW.

[0017] The OTA center 1 is a server that provides software for the ECU (refer to FIG. 3) installed in the vehicle 2. The OTA center 1 is managed, for example, by a vehicle manufacturer that manufactures the vehicle body (VP: Vehicle Platform). The configuration of the OTA center 1 will be described with reference to FIG. 2.

[0018] The vehicle 2 is managed by the user. The user is typically an individual, but may be a legal entity (such as a transportation business operator) that conducts business using the vehicle 2, for example. In this embodiment, the vehicle 2 is an autonomous vehicle. In this case, the OTA center 1 may be managed by the manufacturer of the autonomous driving system (ADS: Autonomous Driving System) (refer to FIG. 3) installed in the VP, instead of or in addition to the vehicle manufacturer. However, the vehicle 2 may be a vehicle that does not support autonomous driving and is only capable of manual driving. The configuration of the vehicle 2 will be described with reference to FIG. 3.

[0019] The user terminal 3 is a terminal operated by the user of the vehicle 2. The user terminal 3 may be a mobile terminal or a fixed terminal. Mobile terminals include, for example, smartphones, tablets, notebook PCs (Personal Computers), and wearable devices (such as smartwatches). Fixed terminals include, for example, desktop PCs. The configuration of the user terminal 3 will be described with reference to FIG. 4.

[0020] Note that, for reasons of space, only one vehicle 2 is shown in FIG. 1, but the number of vehicles 2 is arbitrary. Usually, the information processing system 100 includes a number of vehicles 2. The same applies to the user terminal 3.

[0021] FIG. 2 is a block diagram showing a typical configuration example of the OTA center 1. The OTA center 1 includes a server 11, an input device 12, a display 13, and a communication device 14. The server 11 includes a processor 111, a memory 112, a storage 113, and a network interface 114. The components of the OTA center 1 are connected to each other by a communication bus.

[0022] The storage 113 is a rewritable non-volatile memory such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory. The storage 113 stores a system program 51 including an OS (Operating System), a control program 52 including computer-readable code necessary for control operations, an update program 53 for updating the control program of the vehicle 2, and usage permission information 54 (described later) for obtaining the user's permission regarding the download, installation, etc. of the update program 53. The processor 111 is, for example, a CPU (Central Processing Unit) or an MPU (Micro-Processing Unit). The processor 111 realizes various processes by reading out the system program 51 and the control program 52 and expanding and executing them in the memory 112. The network interface 114 controls data communication between the server 11 and other devices (such as the vehicle 2 and the user terminal 3) via the communication device 14.

[0023] The input device 12 is a keyboard, a mouse, etc., and receives the input of the operator of the server 11. The display 13 displays various information to the operator of the server 11.

[0024] Note that FIG. 2 shows an example in which the server 11 includes one processor 111, but the server 11 may include a plurality of processors. That is, the server 11 includes one or more processors. The same applies to the memory 112 and the storage 113.

[0025] As used herein, the term "processor" is not limited to a processor in the narrow sense that executes processing in a stored-program manner, and may include hard-wired circuits such as an ASIC (Application Specific Integrated Circuit) and an FPGA (Field-Programmable Gate Array). Therefore, the term "processor" can also be read as a processing circuitry whose processing is defined in advance by computer-readable code and / or a hard-wired circuit.

[0026] FIG. 3 is a block diagram showing a typical configuration example of the vehicle 2. The vehicle 2 includes a central ECU 21, a plurality of discrete ECUs 22, an advanced driver-assistance system (ADAS) 23, an ADS 24, a sensor group 25, an input device 26, an in-vehicle display 27, and a DCM (Data Communication Module) 28. The discrete ECU 22 is an ECU divided by function, such as a brake ECU, a steering ECU, a motor generator ECU, and a body ECU. The discrete ECU 22 may be a controller in which software for realizing the functions of the ADAS 23 and / or the ADS 24 is stored. The components of the vehicle 2 are connected to each other by a wired in-vehicle network such as a CAN (Controller Area Network) and in-vehicle Ethernet (registered trademark).

[0027] The basic configurations of the central ECU 21 and the individual ECUs 22 are the same as that of the server 11. In the storage 223 of the individual ECU 22, software (system program 71 and control program 72) executed by the processor 221 of the individual ECU 22 is stored. The individual ECU 22 controls the system corresponding to the individual ECU 22 so that the vehicle 2 reaches a desired state according to signals from the sensor group 25 and the like. Although not shown here, the systems may include a braking system, a steering system, a power train system, a body system, and the like.

[0028] The processor 211 of the central ECU 21 controls the update process of the software stored in the storage 223 of the individual ECU 22. The central ECU 21 receives (downloads) software from the OTA center 1 via the DCM 28, and stores (installs) the downloaded software in the storage 223 of the individual ECU 22 at an appropriate timing. Then, the central ECU 21 activates (activates) the installed software at an appropriate timing.

[0029] The ADAS 23 includes, for example, adaptive cruise control (ACC), auto speed limiter (ASL), lane keeping assist (LKA), pre-crash safety (PCS), and lane departure alert (LDA). The ADS 24 is configured to be able to execute the autonomous driving of the vehicle 2.

[0030] The sensor group 25 includes sensors configured to detect the external situation of the vehicle 2. The sensor group 25 further includes sensors (none of which are shown in the figures) configured to detect information according to the driving state of the vehicle 2 and steering operations, accelerator operations, and brake operations. Specifically, the sensor group 25 may include, for example, a camera, a radar, a lidar (Laser Imaging Detection and Ranging), a vehicle speed sensor, an acceleration sensor, a yaw rate sensor, a steering sensor (none of which are shown in the figures).

[0031] The input device 26 is, for example, a touch panel provided on a multi-information display (MID). The input device 26 may be a physical switch or button. The in-vehicle display 27 is, for example, an MID. The in-vehicle display 27 may be an instrument panel to which display technologies such as liquid crystal and organic EL (Electro Luminescence) are applied. The DCM 28 is an in-vehicle communication module. The DCM 28 is configured to enable two-way data communication between the central ECU 21 and the server 11.

[0032] FIG. 4 is a block diagram showing a typical configuration example of the user terminal 3. The user terminal 3 includes an arithmetic processing unit 31, an input device 32, a display 33, and a communication device 34. The input device 32 and the display 33 are integrally configured as, for example, a touch panel display. However, the input device 32 may be an input-only device (such as a keyboard or a mouse), and the display 33 may be a stationary monitor. Other configurations of the user terminal 3 are the same as those of the server 11 (see FIG. 2).

[0033] <User's permission> The software update of the individual ECU 22 may be performed at the user's home or at the user's destination. In this embodiment, prior to the software update of the individual ECU 22, information for obtaining the user's permission is presented to the user. Hereinafter, this information is referred to as "usage permission information". The usage permission information includes, but is not limited to, information regarding the software usage permission contract. The usage permission information may include information for explaining the update content of the software, or may include information (so-called manual) for explaining how to use the vehicle 2 after the software update. The usage permission information corresponds to the "data" (first data and second data) according to the present disclosure.

[0034] It is desirable to appropriately provide the usage permission information to the user without impairing the convenience for the user. As the display destination of the usage permission information, the in-vehicle display 27 and the user terminal 3 are conceivable. Generally, the in-vehicle display 27 such as the MID and the instrument panel has a larger screen than the user terminal 3 such as a smartphone and a wearable device. Further, the in-vehicle display 27 is angle-adjusted so that the user can view it while sitting in the vehicle interior. In particular, the visibility of the in-vehicle display 27 from the driver's seat is very high. In other words, in the case of the in-vehicle display 27, there is no need to move to a place where a notebook PC, a desktop PC, etc. are installed, and it is also hands-free unlike a smartphone, a tablet, etc. Therefore, the in-vehicle display 27 is considered to be suitable as the display destination of the usage permission information.

[0035] The inventor focused on the fact that when the usage permission information is displayed in the same manner on the in-vehicle display 27 and the user terminal 3, the uniformity may lead to a decrease in user convenience. Therefore, in the present embodiment, a configuration is adopted in which the information granularity of the usage permission information is changed between the in-vehicle display 27 and the user terminal 3. More specifically, the OTA center 1 makes the information granularity of the usage permission information displayed on the in-vehicle display 27 higher than that of the usage permission information displayed on the user terminal 3. A high information granularity means a state in which various information elements are included in one information unit.

[0036] FIG. 5 is a diagram showing an example of the data structure of the usage permission information 54 in the present embodiment. FIG. 6 is a diagram showing another example of the data structure of the usage permission information 54 in the present embodiment. The usage permission information 54 (see FIG. 2) stored in the storage 113 of the server 11 includes a header (metadata) 81 and a body (data main body) 82. The header 81 may include the creator of the data, the creation date, the title, the tag, the data type, the data length, and the like. The body 82 includes the usage permission information.

[0037] In the example shown in FIG. 5, the usage permission information 54 includes character information for obtaining the user's permission regarding software update. The amount of character information (description amount) displayed on the in-vehicle display 27 is larger than the amount of character information displayed on the user terminal 3. As a specific example, the entire character information (for example, items and detailed descriptions of each item) is displayed on the in-vehicle display 27, while only particularly important parts (for example, only items, or items and simple descriptions of each item) are extracted from the character information and displayed on the user terminal 3. This is an example of a high information granularity of the usage permission information 54 displayed on the in-vehicle display 27.

[0038] In the example shown in FIG. 6, the license information 54 displayed on the in-vehicle display 27 includes video information in addition to character information. The video information includes animations that visually explain the software update content, animations that explain the procedures (preparations, precautions, etc.) required for software updates, video manuals on how to use the vehicle 2 after software updates, and the like. On the other hand, the license information 54 displayed on the user terminal 3 includes character information but does not include video information. This is another example where the information granularity of the license information 54 displayed on the in-vehicle display 27 is high.

[0039] As described above, in this embodiment, the license information 54 displayed on the in-vehicle display 27 has a higher information granularity than the user terminal 3. In other words, the amount and / or type of the license information 54 displayed on the in-vehicle display 27 is greater than the amount and / or type of the license information 54 displayed on the user terminal 3. Therefore, the user can confirm the details of the license information 54 on the in-vehicle display 27 suitable for displaying the license information 54 and then permit the software update. Thus, the convenience of the user can be improved.

[0040] <Processing Flow> FIG. 7 is a flowchart showing a first example of a processing procedure for obtaining the user's permission regarding software updates. The processing shown in this flowchart is executed when a predetermined condition is satisfied (for example, when newly updated software is registered in the OTA center 1). In the figure, the processing executed by the vehicle 2 is shown on the left side, the processing executed by the OTA center 1 is shown in the center, and the processing executed by the user terminal 3 is shown on the right side. Hereinafter, steps are abbreviated as S.

[0041] First, the OTA center 1 transmits the license information for display on the in-vehicle display 27 to the vehicle 2, and also transmits the license information for display on the display 33 of the user terminal 3 to the user terminal 3 (S111). The OTA center 1 may transmit the license information to the vehicle 2 and the user terminal 3 at different timings, or may transmit the license information at substantially the same timing. The OTA center 1 may transmit the license information to the vehicle 2 in response to a request from the vehicle 2, and transmit the license information to the user terminal 3 in response to a request from the user terminal 3. As described with reference to FIGS. 5 and 6, the information granularity of the license information displayed on the display 33 of the in-vehicle display 27 is higher than the information granularity of the license information displayed on the user terminal 3.

[0042] In this example, the user performs an operation to view the license information on the input device 26 of the vehicle 2. Then, the ECU of the vehicle 2 (which may be the central ECU 21 or the individual ECU 22) causes the license information to be displayed on the in-vehicle display 27 (S211).

[0043] Before the user performs an operation to grant permission for software update, the viewing of the license information may be interrupted for some reason such as an urgent matter occurring to the user. In that case, the vehicle 2 transmits the interruption location of the license information (information indicating up to where the license information has been viewed) to the OTA center 1 (S212). When the OTA center 1 receives the interruption location of the license information, it records it in the storage 113 (S112).

[0044] The user resumes viewing the license information at a timing convenient for the user, for example. In this example, a situation where the user resumes viewing the license information using the in-vehicle display 273 is assumed. When the vehicle 2 receives a user operation to resume viewing, it transmits a request to resume viewing to the OTA center 1 (S213). In response to the request from the vehicle 2, the OTA center 1 transmits the interruption location recorded in S112 to the vehicle 2 (S113). Then, the vehicle 2 causes the license information to be displayed on the in-vehicle display 273 from the interruption location (S214).

[0045] After receiving a user operation that permits software update, the vehicle 2 transmits the user's permission to the OTA center 1 (S215). Along with this, although not shown, a series of processes for updating the software (the aforementioned download, installation, and activation) are executed in the vehicle 2.

[0046] Thus, when the user interrupts the viewing of the usage permission information and then resumes the viewing, it is preferable to resume from the interrupted point of the usage permission information. This enables the user to avoid viewing again the usage permission information that has already been viewed before the interruption of the viewing, thereby further improving the convenience for the user.

[0047] FIG. 8 is a flowchart showing a second example of a processing procedure for obtaining the user's permission regarding software update. In this example, it is assumed that after the interruption of the viewing of the usage permission information on the vehicle 2 (in-vehicle display 27), the user resumes the viewing of the usage permission information using the user terminal 3. The processing up to S122 is equivalent to the corresponding processing in FIG. 7.

[0048] When the user terminal 3 receives a user operation for resuming the viewing, it notifies the OTA center 1 of a request to resume the viewing (S321). In response to the request from the user terminal 3, the OTA center 1 transmits the interrupted point recorded at S122 to the user terminal 3 (S123). The user terminal 3 displays the usage permission information on the display 33 starting from the interrupted point (S322). After receiving a user operation that permits software update, the user terminal 3 transmits the user's permission to the OTA center 1 (S323).

[0049] FIG. 9 is a flowchart showing a third example of a processing procedure for obtaining the user's permission regarding software update. Without repeating the detailed description, as shown in FIG. 9, contrary to FIG. 8, the viewing of the usage permission information may first be performed on the user terminal 3 and then the viewing of the usage permission information may be taken over by the vehicle 2.

[0050] In this way, when the user interrupts the viewing of the license information and then resumes the viewing, even if the terminal used for viewing the license information is changed before and after the interruption (in other words, regardless of whether the viewing of the license information is performed on the vehicle 2 or the user terminal 3), it is preferable to resume from the interrupted point of the license information. As a result, similar to FIG. 7, the user does not need to view again the license information that has already been viewed before the interruption, so that the convenience of the user can be further improved.

[0051] FIG. 10 is a flowchart showing a fourth example of a processing procedure for obtaining a user's permission regarding software update. Also in FIG. 10, similar to FIG. 9, when the viewing of the license information is interrupted at the user terminal 3, the interrupted point is recorded at the OTA center 1 (S142). Then, the user resumes the viewing of the license information using the vehicle 2 (in-vehicle display 27). When the vehicle 2 receives a user operation for resuming the viewing, the vehicle 2 transmits a request for resuming the viewing to the OTA center 1 (S241). The OTA center 1 receives the request from the vehicle 2.

[0052] In this example, although the interrupted point is recorded in S142, the OTA center 1 transmits a command to the vehicle 2 to view the license information from the beginning (S143). The vehicle 2 causes the in-vehicle display 27 to display the license information from the beginning according to the command (S242). Then, when receiving a user operation for permitting the software update, the vehicle 2 transmits the user's permission to the OTA center 1 (S243).

[0053] In this way, when the user interrupts the viewing of the license information using the user terminal 3 and then resumes the viewing using the vehicle 2, the OTA center 1 may cause the in-vehicle display 27 to display all the license information from the beginning. As a result, the user can view the entire license information using the in-vehicle display 27 that has excellent visibility in the vehicle interior (more specifically, has a large screen, an easy-to-see angle, and is hands-free). Therefore, the user can view the license information carefully and efficiently.

[0054] As described above, in the present embodiment, in view of the installation location and / or visibility for each terminal, the information granularity of the usage permission information is set so that the usage permission information is displayed in a display mode suitable for the terminal. Specifically, the information granularity of the usage permission information displayed on the in-vehicle display 27 is set higher than the information granularity of the usage permission information displayed on the user terminal 3. Thereby, when the user uses the in-vehicle display 27, the user can permit the software update after carefully checking the usage permission information. On the other hand, when the user uses the user terminal 3, the user can permit the software update after briefly checking the usage permission information. Therefore, according to the present embodiment, the convenience of the user can be improved.

[0055] The embodiments disclosed this time should be considered to be illustrative in all respects and not restrictive. The scope of the present disclosure is indicated by the scope of claims rather than the description of the above-described embodiments, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

Explanation of Reference Numerals

[0056] 1 OTA Center, 11 Server, 111 Processor, 112 Memory, 113 Storage, 114 Network Interface, 12 Input Device, 13 Display, 14 Communication Device, 2 Vehicle, 21 Central ECU, 22 Individual ECU, 211, 221 Processor, 212, 222 Memory, 213, 223 Storage, 214, 224 Network Interface, 23 ADAS, 24 ADS, 25 Sensor Group, 26 Input Device, 27 In-vehicle Display, 3 User Terminal, 31 Arithmetic Processing Unit, 311 Processor, 312 Memory, 313 Storage, 314 Network Interface, 32 Input Device, 33 Display, 34 Communication Device, 51, 61, 71 System Program, 52, 62, 72 Control Program, 53 Update Program, 54 Usage Permission Information, 81 Header, 82 Body, 100 Information Processing System.

Claims

1. A server that transmits data for updating software of a vehicle control device by wireless communication, comprising a memory storing a program, and a processor that executes the program, wherein the processor sets first data to be displayed on an in-vehicle display to obtain a user's permission regarding the software update, and second data to be displayed on a user terminal to obtain the user's permission regarding the software update, wherein the information granularity of the first data is higher than that of the second data, wherein the first data is the entire software usage permission information, and wherein the second data is a part of the first data, the server.

2. The server according to claim 1, wherein the amount of character information included in the first data is larger than the amount of character information included in the second data.

3. The server according to claim 1, wherein the first data includes video information, and wherein the second data does not include the video information.

4. The server according to any one of claims 1 to 3, wherein when the user further views the second data using the user terminal after viewing the first data partway using the in-vehicle display, the processor sets the second data displayed on the user terminal to be a continuation of the first data that was viewed partway using the in-vehicle display.

5. The server according to any one of claims 1 to 3, wherein when the user further views the first data using the in-vehicle display after viewing the second data partway using the user terminal, the processor sets the first data displayed on the in-vehicle display to be a continuation of the second data that was viewed partway using the user terminal.

6. The server according to any one of claims 1 to 3, wherein when the user further views the first data using the in-vehicle display after viewing the second data partway using the user terminal, the processor also sets, in the first data displayed on the in-vehicle display, the part of the second data that the user has already viewed using the user terminal.

7. A program for causing a computer to execute to update software of a vehicle control device by wireless communication, wherein when executed by the computer, the computer, A step of setting first data displayed on an in-vehicle display to obtain a user's permission regarding the software update and second data displayed on a user terminal to obtain the user's permission regarding the software update; Executing a step of displaying corresponding data of the first data and the second data on at least one of the in-vehicle display and the user terminal; The information granularity of the first data is higher than that of the second data; The first data is the entirety of the software usage permission information; The second data is a part of the first data, a program.

8. A software update method for updating software of a vehicle control device by wireless communication, A step of setting first data displayed on an in-vehicle display to obtain a user's permission regarding the software update and second data displayed on a user terminal to obtain the user's permission regarding the software update; Including a step of displaying corresponding data of the first data and the second data on at least one of the in-vehicle display and the user terminal; The information granularity of the first data is higher than that of the second data; The first data is the entirety of the software usage permission information; The second data is a part of the first data, a software update method.

9. A server that transmits data for updating software of a vehicle control device by wireless communication, A memory storing a program; A processor that executes the program, and The processor sets first data displayed on an in-vehicle display to obtain a user's permission regarding the software update and second data displayed on a user terminal to obtain the user's permission regarding the software update, The information granularity of the first data is higher than that of the second data, When the user further views the second data using the user terminal after viewing the first data partway using the in-vehicle display, the server sets the second data displayed on the user terminal to be the continuation of the first data viewed partway using the in-vehicle display. A server that transmits data for updating software of a vehicle control device by wireless communication, a memory storing a program, a processor that executes the program, and the processor sets first data to be displayed on an in-vehicle display to obtain the user's permission regarding the software update, and second data to be displayed on a user terminal to obtain the user's permission regarding the software update, the information granularity of the first data is higher than that of the second data, the processor, when the user further views the first data using the in-vehicle display after viewing the second data partway through using the user terminal, sets the first data displayed on the in-vehicle display to be a continuation of the second data that the user has viewed partway through using the user terminal. A server. A server that transmits data for updating software of a vehicle control device by wireless communication, a memory storing a program, a processor that executes the program, and the processor sets first data to be displayed on an in-vehicle display to obtain the user's permission regarding the software update, and second data to be displayed on a user terminal to obtain the user's permission regarding the software update, the information granularity of the first data is higher than that of the second data, the processor, when the user further views the first data using the in-vehicle display after viewing the second data partway through using the user terminal, also sets, for the part of the second data that the user has already viewed using the user terminal, the part to be the first data displayed on the in-vehicle display. A server.

Images