Information processing system, information processing method, and program

Abstract

To provide a technology for evaluating the effect of software update in a vehicle in the case of updating software actually used in the vehicle.SOLUTION: A software update system 1 configured to update software on the basis of update data of software used in a vehicle 10, the data being transmitted to the vehicle 10 from an external device connected to communicate with the vehicle 10 includes: a software update unit 194 which updates software on the basis of update data; a vehicle data acquisition unit 196 which acquires second vehicle data on states of the vehicle 10 before and after updating the software by the software update unit 194; and an effect evaluation unit 304 which evaluates effect of the software update on the basis of the second vehicle data for before and after the software update.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present disclosure relates to an information processing system and the like. [Background technology]

[0002] For example, a technique is known in which software used in a vehicle (for example, data such as a program and parameters used in the program) is transmitted from an external device to the vehicle to update the software (see Patent Document 1).

[0003] In Patent Document 1, an evaluation simulator is used to evaluate the vehicle's operation before and after a software update, and the software update is performed after confirming that the software update corrects the vehicle's functions in the desired direction. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2003-34200 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, the above technology only performs a pre-check before the software update, and it is not certain whether the desired effect will be obtained in the vehicle when the software actually used in the vehicle is updated. Therefore, from the viewpoint of, for example, future vehicle maintenance and inspection serviceability and feedback to future vehicle development, it is desirable to evaluate the effect in the vehicle when the software actually used in the vehicle is updated.

[0006] In view of the above problem, an object of the present invention is to provide a technique capable of evaluating the effect on a vehicle when an update of software actually used in the vehicle is performed. [Means for solving the problem]

[0007] In order to achieve the above object, in one embodiment of the present disclosure, An information processing system for updating software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, an acquisition unit that acquires predetermined data relating to the state of the vehicle before and after the software update; a determination unit that determines whether the predetermined data before the software update has been acquired by the acquisition unit; an update unit that updates the software based on the update data when the determination unit determines that the predetermined data before the software update has been acquired; a guidance unit that, after the software is updated by the update unit, guides a driver of the vehicle along a driving route for acquiring the predetermined data after the software is updated; and an evaluation unit that evaluates an effect of the software update based on the predetermined data before and after the software update. An information processing system is provided. In another embodiment of the present disclosure, An information processing system for updating software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, the information processing system comprising: an update unit that updates the software based on the update data; an acquisition unit that acquires predetermined data relating to the state of the vehicle before and after the software is updated by the update unit; Using a virtual model corresponding to the vehicle, Based on the predetermined data before and after the software update, By conducting virtual simulations and comparing the results, an evaluation unit for evaluating the effect of updating the software; 、 The evaluation unit determines whether or not to perform the virtual simulation when evaluating the effect of the software update depending on the content of the software update. R, An information processing system is provided. In still another embodiment of the present disclosure, An information processing system for updating software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, an update unit that updates the software based on the update data; an acquisition unit that acquires predetermined data relating to the state of the vehicle before and after the software is updated by the update unit; an evaluation unit that performs a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle and compares the results to evaluate an effect of the software update; The evaluation unit changes a driving condition of the vehicle during the virtual simulation according to the content of the software update. An information processing system is provided. In still another embodiment of the present disclosure, An information processing system for updating software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, an update unit that updates the software based on the update data; an acquisition unit that acquires predetermined data relating to the state of the vehicle before and after the software is updated by the update unit; an evaluation unit that performs a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle and compares the results to evaluate an effect of the software update; the evaluation unit evaluates the effect by comparing a change in characteristics of the vehicle obtained by comparing the specified data before and after the software update with a change in characteristics of the vehicle obtained by comparing results of the virtual simulation based on each of the specified data before and after the software update. An information processing system is provided. In still another embodiment of the present disclosure, An information processing system for updating software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, an update unit that updates the software based on the update data; an acquisition unit that acquires predetermined data relating to the state of the vehicle before and after the software is updated by the update unit; A generation unit that generates a virtual model corresponding to the vehicle; an evaluation unit that performs a virtual simulation using the virtual model based on the predetermined data before and after the software update, and compares the results to evaluate an effect of the software update; the virtual model is a dedicated model corresponding to the vehicle; The generation unit updates the virtual model in accordance with at least one of a change over time of the vehicle, a use condition of the vehicle, and a change in a component of the vehicle. An information processing system is provided.

[0009] In still another embodiment of the present disclosure, 1. An information processing method executed by an information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, the information processing method comprising: an acquisition step of acquiring predetermined data regarding the state of the vehicle before and after the software update; a determination step of determining whether or not the predetermined data before the software update has been acquired in the acquisition step; an update step of updating the software based on the update data when it is determined in the determination step that the predetermined data before the update of the software has been acquired; a guidance step of guiding a driver of the vehicle to a driving route for acquiring the predetermined data after the software is updated in the update step; and evaluating an effect of the software update based on the predetermined data before and after the software update. A method for processing information is provided. In still another embodiment of the present disclosure, Based on update data for software used in the vehicle, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, By conducting virtual simulations and comparing the results, An information processing method executed by an information processing device that updates the software, comprising: an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; Using a virtual model corresponding to the vehicle, and an evaluation step of evaluating an effect of the software update based on the predetermined data before and after the software update. fruit , In the evaluation step, it is determined whether or not the virtual simulation is performed when evaluating the effect of the software update, depending on the content of the software update. A method for processing information is provided. In still another embodiment of the present disclosure, 1. An information processing method executed by an information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, the information processing method comprising: an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; and an evaluation step of performing a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and comparing the results of the virtual simulation to evaluate an effect of the software update, In the evaluation step, a driving condition of the vehicle during the virtual simulation is changed according to the content of the software update. A method for processing information is provided. In still another embodiment of the present disclosure, 1. An information processing method executed by an information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, the information processing method comprising: an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; and an evaluation step of performing a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and comparing the results of the virtual simulation to evaluate an effect of the software update, In the evaluation step, the effect is evaluated by comparing a change in characteristics of the vehicle obtained by comparing the predetermined data before and after the software update with a change in characteristics of the vehicle obtained by comparing results of the virtual simulation based on each of the predetermined data before and after the software update. A method for processing information is provided. In still another embodiment of the present disclosure, 1. An information processing method executed by an information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, the information processing method comprising: an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; A generating step of generating a virtual model corresponding to the vehicle; and an evaluation step of performing a virtual simulation using the virtual model based on the predetermined data before and after the software update, and comparing the results to evaluate an effect of the software update, the virtual model is a dedicated model corresponding to the vehicle; In the generating step, the virtual model is updated in accordance with at least one of a change over time of the vehicle, a use condition of the vehicle, and a change in a component of the vehicle. A method for processing information is provided.

[0010] In still another embodiment of the present disclosure, An information processing device that updates software based on update data for software used in the vehicle, the update data being transmitted to the vehicle from an external device that is communicatively connected to the vehicle, an acquisition step of acquiring predetermined data regarding the state of the vehicle before and after the software update; a determination step of determining whether or not the predetermined data before the software update has been acquired in the acquisition step; an update step of updating the software based on the update data when it is determined in the determination step that the predetermined data before the update of the software has been acquired; a guidance step of guiding a driver of the vehicle to a driving route for acquiring the predetermined data after the software is updated in the update step; and an evaluation step of evaluating an effect of the software update based on the predetermined data before and after the software update. The program is provided. In still another embodiment of the present disclosure, An information processing device that updates software used in the vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device that is communicatively connected to the vehicle, an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; Using a virtual model corresponding to the vehicle, Based on the predetermined data before and after the software update, By conducting virtual simulations and comparing the results, an evaluation step of evaluating the effect of updating the software; 、 In the evaluation step, it is determined whether or not the virtual simulation is performed when evaluating the effect of the software update, depending on the content of the software update. R, The program is provided. In still another embodiment of the present disclosure, An information processing device that updates software used in the vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device that is communicatively connected to the vehicle, an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; an evaluation step of performing a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and evaluating an effect of the software update by comparing the results; In the evaluation step, a driving condition of the vehicle during the virtual simulation is changed according to the content of the software update. The program is provided. In still another embodiment of the present disclosure, An information processing device that updates software used in the vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device that is communicatively connected to the vehicle, an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; an evaluation step of performing a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and evaluating an effect of the software update by comparing the results; In the evaluation step, the effect is evaluated by comparing a change in characteristics of the vehicle obtained by comparing the predetermined data before and after the software update with a change in characteristics of the vehicle obtained by comparing results of the virtual simulation based on each of the predetermined data before and after the software update. The program is provided. In still another embodiment of the present disclosure, An information processing device that updates software used in the vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device that is communicatively connected to the vehicle, an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; A generating step of generating a virtual model corresponding to the vehicle; an evaluation step of performing a virtual simulation using the virtual model based on the predetermined data before and after the software update, and comparing the results to evaluate an effect of the software update; the virtual model is a dedicated model corresponding to the vehicle; In the generating step, the virtual model is updated in accordance with at least one of a change over time of the vehicle, a use condition of the vehicle, and a change in a component of the vehicle. The program is provided. Effect of the Invention

[0012] According to the above-described embodiment, it is possible to evaluate the effect on a vehicle when software actually used in the vehicle is updated. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a schematic diagram illustrating an example of a software update system. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a vehicle. [Diagram 3] FIG. 2 illustrates an example of a hardware configuration of a distribution server. [Figure 4] FIG. 2 is a functional block diagram showing an example of a functional configuration of the software update system. [Diagram 5] FIG. 4 is a diagram showing an example of updating a shift map of a vehicle transmission; [Figure 6] FIG. 11 is a diagram showing an example of updating a switching map for a prime mover of a vehicle; [Figure 7] 1 is a diagram showing an example of changes over time in an actual vehicle state during a shift change of a transmission, before and after updating of a control logic related to the shift change (upshift) of the transmission of the vehicle; FIG. [Figure 8] 13A and 13B are diagrams showing other examples of changes over time in the actual state of a vehicle during a shift change of a transmission, before and after updating of the control logic related to the shift change (upshift) of the transmission of the vehicle. [Figure 9] FIG. 13 is a diagram showing an example of the results of a virtual simulation of changes over time in the state of a vehicle during a shift change of the transmission, before and after updating of a control logic related to a shift change (upshift) of the transmission of the vehicle. [Figure 10] 4 is a flowchart illustrating an example of a software update process performed by a central ECU. [Figure 11] 4 is a flowchart illustrating an example of a software update process performed by a central ECU. [Figure 12] 10 is a flowchart illustrating another example of a software update process by the central ECU. [Figure 13] 10 is a flowchart illustrating another example of a software update process by the central ECU. [Figure 14] 13 is a flowchart illustrating an example of an effect evaluation process performed by the analysis server. [Figure 15] 13 is a flowchart illustrating an outline of another example of the effect evaluation process by the analysis server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an embodiment will be described with reference to the drawings.

[0015] [Software update system overview] An overview of a software update system 1 according to this embodiment will be described with reference to FIG.

[0016] FIG. 1 is a schematic diagram showing an example of a software update system 1. As shown in FIG.

[0017] As shown in FIG. 1, a software update system 1 (an example of an information processing system) includes a vehicle 10, a distribution server 20, an analysis server 30, and a user terminal 40.

[0018] The software update system 1 distributes update data for software used in the vehicle 10 to the vehicle 10, and updates the software in the vehicle 10.

[0019] The software of the vehicle 10 includes, for example, programs executed by computers (on-board computers) mounted on the vehicle 10, such as a gateway ECU (Electronic Control Unit) 12, ECU 13, and central ECU 19, which will be described later. The software of the vehicle 10 also includes, for example, various data, such as parameters used in processing by the programs executed by the on-board computers.

[0020] In addition, the software update system 1 evaluates (confirms) the effect of the software update. As a result, the software update system 1 can feed back the evaluation result of the effect of the software update to the development department of the current vehicle model corresponding to the vehicle 10 or the development department of the successor vehicle model, or the service and inspection department of the current vehicle model.

[0021] The effect of updating the software includes, for example, an effect related to an improvement (enhancement) of performance, which corresponds to the purpose of updating the software.

[0022] The effect of the software update includes, for example, an effect related to whether or not the state of the vehicle 10 is realized according to the contents of the software update (update data). For example, when the shifting conditions (shifting lines) of the transmission of the vehicle 10 are updated (see FIG. 5 described later), the realization of the state of the vehicle 10 according to the contents of the software update means that the gear shift of the transmission is actually performed according to the updated gear shifting conditions. For example, when the switching map of the prime mover (engine and electric motor) of the vehicle 10 is updated (see FIG. 6 described later), the realization of the state of the vehicle 10 according to the contents of the software update means that the switching of the prime mover is actually performed according to the updated switching conditions. For example, when the control logic related to the shift change of the transmission of the vehicle 10 is updated (see FIG. 7 to FIG. 9 described later), the realization of the state of the vehicle 10 according to the contents of the software update means that the gear shift of the transmission is actually performed according to the updated control logic.

[0023] The software is updated for the vehicle 10. The vehicle 10 runs on power transmitted from a predetermined prime mover such as an engine or an electric motor to drive wheels via a drive system including a transmission, a differential, and a drive shaft.

[0024] As described below, the vehicle 10 is equipped with a communication device 11 and is communicably connected to external devices such as the distribution server 20 and the analysis server 30 through a predetermined communication line. This allows the vehicle 10 to transmit information signals to the distribution server 20 and the analysis server 30, and to receive control signals and information signals (e.g., software update data) from the distribution server 20 and the analysis server 30.

[0025] The predetermined communication line includes, for example, a wide area network (WAN) such as a mobile communication network terminated in a base station, a satellite communication network using a communication satellite, and the Internet. The predetermined communication line may also include, for example, a local area network (LAN) of a facility where the distribution server 20 and the analysis server 30 are installed. The predetermined communication line may also include, for example, a short-distance communication line based on a wireless communication standard such as WiFi or Bluetooth (registered trademark). The same may be true for the communication line used for communication between the distribution server 20 and the analysis server 30 and the communication line used for communication between the distribution server 20 and the user terminal 40.

[0026] The software update system 1 may include one or more vehicles 10. In the latter case, the multiple vehicles 10 included in the software update system 1 may be, for example, all of the same model, or may include two or more models of vehicles 10.

[0027] The distribution server 20 (an example of an external device) distributes, to the vehicle 10, various types of data used in the vehicle 10. Specifically, the distribution server 20 distributes, to the vehicle 10, software update data.

[0028] The distribution server 20 is, for example, an on-premise server or a cloud server installed in a monitoring center or the like that centrally monitors the states of a plurality of vehicles 10. The distribution server 20 may also be, for example, an edge server installed in an area where the vehicles 10 mainly travel (for example, an area where the vehicles 10 are legally registered). In this case, a plurality of distribution servers 20 may be provided for all the vehicles 10 included in the software update system 1. The same may be true for the analysis server 30 below.

[0029] As described above, the distribution server 20 is communicatively connected to the vehicle 10 through a predetermined communication line. This allows the distribution server 20 to receive various information signals from the vehicle 10 and transmit various information signals (e.g., software update data) and control signals (e.g., software update commands) to the vehicle 10.

[0030] The analysis server 30, for example, acquires various data (hereinafter, "vehicle data") indicating the state of the vehicle 10 from the vehicle 10, and performs an analysis related to the vehicle 10. Specifically, the analysis server 30 performs an analysis related to the effect obtained by updating the software of the vehicle 10.

[0031] As described above, the analysis server 30 is communicatively connected to the vehicle 10 through a predetermined communication line. This allows the analysis server 30 to receive various information signals (e.g., vehicle data) from the vehicle 10 and transmit various information signals and control signals to the vehicle 10.

[0032] The analysis server 30 is also communicably connected to the distribution server 20 and the user terminal 40 through a predetermined communication line. This allows the analysis server 30 to transmit various information signals and control signals to the distribution server 20 and the user terminal 40, and to receive various information signals and control signals from the distribution server 20 and the user terminal 40.

[0033] The functions of the distribution server 20 and the analysis server 30 may be integrated into the distribution server 20 (an example of an information processing device) or the analysis server 30 (an example of an information processing device). The functions of the distribution server 20 and the analysis server 30 may be distributed and realized by three or more servers.

[0034] The user terminal 40 is a terminal device used (possessed) by a user of the vehicle 10. The user of the vehicle 10 is, for example, the owner of the vehicle 10 or a family member of the owner of the vehicle 10. The user terminal 40 is, for example, a portable terminal device such as a smartphone, a tablet terminal, or a laptop PC (Personal Computer). The user terminal 40 may also be, for example, a stationary terminal device such as a desktop PC.

[0035] As described above, the user terminal 40 is communicably connected to the distribution server 20 through a predetermined communication line. This allows the user terminal 40 to receive control signals and information signals transmitted from the distribution server 20, and to allow the user of the vehicle 10 to understand the information contained in the signals through a display, a speaker, or the like. In addition, in response to an input from the user, the user terminal 40 can transmit a control signal or information signal corresponding to the input content to the distribution server, and convey a user request corresponding to the input content from the user to the distribution server 20.

[0036] [Hardware configuration of software update system] Next, the hardware configuration of the software update system 1 will be described with reference to FIG. 2 and FIG. 3 in addition to FIG.

[0037] <Vehicle hardware configuration> FIG. 2 is a diagram illustrating an example of a hardware configuration of the vehicle 10. As shown in FIG.

[0038] As shown in FIG. 2, the vehicle 10 includes a communication device 11, a gateway ECU 12, an ECU 13, a sensor 15, a navigation device 16, an input device 17, a display device 18, and a central ECU 19.

[0039] The communication device 11 communicates with the outside of the vehicle 10 through a predetermined communication line. The communication device 11 is, for example, a mobile communication module that is connected to a mobile communication network with a base station as a terminal and can communicate with the outside, and may be, specifically, a DCM (Data Communication Module). The communication device 11 is communicatively connected to the gateway ECU 12, the ECU 13, the central ECU 19, and the like through a communication line inside the vehicle 10. The communication line inside the vehicle 10 is, for example, a one-to-one communication line or an in-vehicle network. The in-vehicle network is, for example, a controller area network (CAN), a local interconnect network (LIN), FlexRay, an in-vehicle Ethernet, and the like. The communication device 11 may transmit a predetermined signal to the outside in response to, for example, a command (request) from the gateway ECU 12. Furthermore, a signal received from the outside by the communication device 11 is taken into the gateway ECU 12.

[0040] The gateway ECU 12 functions as a gateway between a communication line outside the vehicle 10 and a communication line inside the vehicle 10 (for example, an in-vehicle network).

[0041] The gateway ECU 12 may realize its functions by any hardware or any combination of hardware and software. For example, the gateway ECU 12 may have a hardware configuration similar to that of the central ECU 19 described later, and may realize various functions by loading a program installed in an auxiliary storage device into a memory device and executing it on a CPU (Central Processing Unit). The same may be true for the ECU 13 described below.

[0042] For example, the gateway ECU 12 uses a known method to authenticate that a signal received from the outside by the communication device 11 is a signal transmitted from a legitimate source and has not been tampered with. A legitimate source refers to a source that is registered in advance as a source (e.g., the distribution server 20, the analysis server 30, etc.) or a source that has been authenticated in advance through mutual communication. The gateway ECU 12 transmits only data of signals that have been successfully authenticated, among the signals received by the communication device 11, to a predetermined in-vehicle device (e.g., the ECU 13, the central ECU 19, etc.) through a communication line inside the vehicle 10.

[0043] In addition, for example, the gateway ECU 12 generates a signal including predetermined information, commands (requests), etc. in response to requests from various devices of the vehicle 10, and transmits the signal to a predetermined destination (for example, the distribution server 20 or the analysis server 30) via the communication device 11.

[0044] One or more ECUs 13 are mounted on the vehicle 10. The ECU 13 controls various functions of the vehicle 10. For example, the multiple ECUs 13 include an ECU 13 that controls an engine serving as a power source of the vehicle 10, an ECU 13 that controls an electric motor (MG: Motor Generator) serving as a power source of the vehicle 10, an ECU 13 that controls a shift position of a transmission of the vehicle 10, and the like.

[0045] One or more sensors 15 are mounted on the vehicle 10. The sensor 15 outputs measurement data related to the state of the vehicle 10. The output (measurement data) of the sensor 15 is taken into the central ECU 19 through a communication line inside the vehicle 10. For example, the multiple sensors 15 include a sensor 15 (wheel speed sensor) that measures the wheel speed of each wheel of the vehicle 10. For example, the multiple sensors 15 include a sensor 15 (acceleration sensor) that measures the acceleration in the front-rear direction, the left-right direction, and the up-down direction of the vehicle 10. For example, the multiple sensors 15 include a sensor 15 (temperature sensor) that measures the temperature of a predetermined part of the vehicle 10. The temperature sensor includes, for example, a temperature sensor that measures the temperature of a driving battery or a battery for auxiliary equipment mounted on the vehicle 10, a water temperature sensor that measures the temperature of cooling water for various devices, an oil temperature sensor that measures the oil temperature of lubricating oil for various devices, and the like. For example, the multiple sensors 15 include a sensor 15 (GNSS (Global Navigation Satellite System) sensor) that measures the position of the vehicle 10.

[0046] The navigation device 16 guides the user (driver) of the vehicle 10 along the route along which the vehicle 10 will pass, via the display device 18. For example, under the control of one of the multiple ECUs 13, the navigation device 16 guides the user of the vehicle 10 along the route along which the vehicle 10 will pass.

[0047] The input device 17 is provided in the interior of the vehicle 10 and accepts various inputs from the passenger. The input device 17 includes an operation input device, such as a button, a toggle, a lever, a touch panel, a touch pad, etc., that accepts an operation input from the passenger. The input device 17 also includes a voice input device, such as a microphone, that accepts a voice input from the passenger of the vehicle 10. The input device 17 also includes a gesture input device, such as a camera that can capture an image of the passenger in the interior of the vehicle 10, that accepts a gesture input from the passenger of the vehicle 10. An input signal representing the content of the input accepted by the input device 17 is taken into the central ECU 19 through a communication line inside the vehicle 10.

[0048] The display device 18 is provided in a location that is easily visible from the driver's seat inside the vehicle 10, and displays various information screens. The display device 18 is, for example, a liquid crystal display or an organic EL (Electroluminescence) display. The display device 18 is communicatively connected to the central ECU 19 through a communication line inside the vehicle 10, and the central ECU 19 outputs a control signal to the display device 18, and causes the display device 18 to display a predetermined information screen.

[0049] The central ECU 19, for example, serves as a higher-level control device for various ECUs including the gateway ECU 12 and ECU 13 mounted on the vehicle 10, and controls the operation of the various ECUs and functions as a registration destination for various data used by the various ECUs.

[0050] The functions of the central ECU 19 are realized by any hardware or any combination of hardware and software, etc. For example, as shown in Fig. 2, the central ECU 19 includes an auxiliary storage device 19A, a memory device 19B, a CPU 19C, and an interface device 19D, which are connected by a bus B1.

[0051] The auxiliary storage device 19A is a non-volatile storage means, and stores the programs to be installed as well as necessary files, data, etc. The auxiliary storage device 19A is, for example, a flash memory.

[0052] For example, when an instruction to start a program is received, the memory device 19B loads the program from the auxiliary storage device 19A so that the program can be read by the CPU 19C. The memory device 19B is, for example, a static random access memory (SRAM).

[0053] The CPU 19C executes, for example, a program loaded into the memory device 19B, and realizes various functions of the central ECU 19 according to instructions of the program.

[0054] The interface device 19D is used, for example, as an interface for connecting to a communication line inside the vehicle 10. The interface device 19D may include a plurality of different types of interface devices in accordance with the types of communication lines to be connected.

[0055] The programs for realizing various functions of the central ECU 19 are provided by, for example, a portable recording medium 19E. In this case, the interface device 19D functions as an interface for reading data from the recording medium 19E and writing data to the recording medium 19E. The recording medium 19E is a dedicated tool connected to an external connection connector such as a DLC (Data Link Coupler) by a detachable cable. The recording medium 19E may also be, for example, an SD memory card or a USB (Universal Serial Bus) memory. The programs may also be downloaded from another computer (for example, the distribution server 20) outside the vehicle 10 through a predetermined communication line and installed in the auxiliary storage device 19A.

[0056] <Distribution server hardware configuration> FIG. 3 is a diagram showing an example of a hardware configuration of the distribution server 20. As shown in FIG.

[0057] The functions of the distribution server 20 are realized by any hardware or any combination of hardware and software, etc. For example, as shown in Fig. 3, the distribution server 20 includes an external interface 21, an auxiliary storage device 22, a memory device 23, a CPU 24, a communication interface 26, an input device 27, and a display device 28, which are connected by a bus B2.

[0058] The analysis server 30 and the user terminal 40 may have the same hardware configuration as the distribution server 20. Hereinafter, illustrations and descriptions of the hardware configurations of the analysis server 30 and the user terminal 40 will be omitted.

[0059] The external interface 21 functions as an interface for reading data from the recording medium 21A and writing data to the recording medium 21A. The recording medium 21A includes, for example, a flexible disk, a CD (Compact Disc), a DVD (Digital Versatile Disc), a BD (Blu-ray (registered trademark) Disc), an SD memory card, a USB (Universal Serial Bus) memory, etc. This allows the distribution server 20 to read various data used in processing through the recording medium 21A, store the data in the auxiliary storage device 22, and install programs that realize various functions.

[0060] The distribution server 20 may obtain various data and programs from external devices through the communication interface 26.

[0061] The auxiliary storage device 22 stores various installed programs, as well as files and data necessary for various processes. The auxiliary storage device 22 includes, for example, a hard disc drive (HDD), a solid state drive (SSD), a flash memory, and the like.

[0062] When an instruction to start a program is received, the memory device 23 reads and stores the program from the auxiliary storage device 22. The memory device 23 includes, for example, a dynamic random access memory (DRAM) or a static random access memory (SRAM).

[0063] The CPU 24 executes various programs loaded from the auxiliary storage device 22 to the memory device 23, and realizes various functions related to the distribution server 20 in accordance with the programs.

[0064] The high-speed arithmetic unit 25 performs arithmetic processing at a relatively high speed in cooperation with the CPU 24. The high-speed arithmetic unit 25 includes, for example, a graphics processing unit (GPU), an application specific integrated circuit (ASIC), or a field-programmable gate array (FPGA).

[0065] The high speed calculation device 25 may be omitted depending on the required calculation processing speed.

[0066] The communication interface 26 is used as an interface for connecting to an external device so as to be able to communicate with the external device. This allows the distribution server 20 to communicate with the external device, such as the vehicle 10, the analysis server 30, and the user terminal 40, through the communication interface 26. The communication interface 26 may have multiple types of communication interfaces depending on the communication method between the connected device, etc.

[0067] The input device 27 accepts various inputs from the user.

[0068] The input device 27 includes, for example, an operation input device that accepts mechanical operation input from a user. The operation input device includes, for example, a button, a toggle, a lever, etc. The operation input device also includes, for example, a touch panel mounted on the display device 28, a touch pad provided separately from the display device 28, etc.

[0069] The input device 27 also includes, for example, a voice input device capable of receiving voice input from the user. The voice input device includes, for example, a microphone capable of collecting the user's voice.

[0070] The input device 27 includes, for example, a gesture input device capable of receiving a gesture input from a user. The gesture input device includes, for example, a camera capable of capturing an image of a gesture made by the user.

[0071] The input device 27 includes, for example, a biometric input device capable of receiving biometric input from a user. The biometric input device includes, for example, a camera capable of acquiring image data including information related to a user's fingerprint or iris.

[0072] The display device 28 displays an information screen and an operation screen for the user. The display device 28 includes, for example, a liquid crystal display, an organic EL (Electroluminescence) display, and the like.

[0073] [Software update system functional configuration] Next, the functional configuration of the software update system 1 will be described with reference to FIG. 4 in addition to FIGS.

[0074] FIG. 4 is a functional block diagram showing an example of the functional configuration of the software update system 1. As shown in FIG.

[0075] <Vehicle Functional Configuration> 4, the gateway ECU 12 includes, as functional units, a communication unit 121 and a storage unit 122. The function of the communication unit 121 may be realized, for example, by loading a program installed in an auxiliary storage device of the gateway ECU 12 into a memory device and executing the program on a CPU. The function of the storage unit 122 may be realized, for example, by a storage area defined in the auxiliary storage device of the gateway ECU 12.

[0076] The communication unit 121 controls the communication device 11 to input signals received from outside the vehicle 10 into the gateway ECU 12 and to transmit signals to the outside of the vehicle 10 .

[0077] The storage unit 122 stores various data used by the gateway ECU 12. For example, data of various programs installed in the gateway ECU 12 (auxiliary storage device) is registered (stored) in the storage unit 122. In addition, for example, data of parameters referenced in processing by the various programs of the gateway ECU 12 is registered (stored) in the storage unit 122.

[0078] The ECU 13 includes, as a functional unit, a storage unit 131. The function of the storage unit 131 is realized by, for example, a storage area defined in an auxiliary storage device of the ECU 13.

[0079] The storage unit 131 stores various data used by the ECU 13. For example, data of various programs installed in the ECU 13 (auxiliary storage device) is registered (stored) in the storage unit 131. In addition, for example, data of parameters referenced in processing by the various programs of the ECU 13 is registered (stored) in the storage unit 131.

[0080] The central ECU 19 includes, as functional units, a vehicle data transmission unit 191, a download processing unit 192, a storage unit 193, a software update unit 194, and a storage unit 195. The central ECU 19 also includes a vehicle data acquisition unit 196, a route guidance unit 197, a storage unit 198, and a vehicle data transmission unit 199. The functions of the vehicle data transmission unit 191, the download processing unit 192, the software update unit 194, the vehicle data acquisition unit 196, the route guidance unit 197, and the vehicle data transmission unit 199 may be realized, for example, by loading a program installed in the auxiliary storage device 19A into the memory device 19B and executing the program on the CPU 19C. The functions of the storage units 193, 195, and 198 may be realized, for example, by a storage area defined in the auxiliary storage device 19A.

[0081] The vehicle data transmission unit 191 acquires vehicle data representing the state of the vehicle 10 at predetermined intervals and transmits (uploads) the vehicle data to the analysis server 30 through the gateway ECU 12 (communication device 11). The vehicle data includes, for example, measurement data output from the sensor 15. The vehicle data also includes, for example, command values ​​output from various ECUs such as the gateway ECU 12, the ECU 13, and the central ECU 19, and control data such as values ​​of calculation results during control processing. Hereinafter, the vehicle data to be transmitted by the vehicle data transmission unit 191 is distinguished from the vehicle data to be acquired by the vehicle data acquisition unit 196 (the vehicle data to be transmitted by the vehicle data transmission unit 199), and may be referred to as "first vehicle data" for convenience. For example, the vehicle data transmission unit 191 may upload the acquired first vehicle data to the analysis server 30 in real time. Furthermore, the vehicle data transmission unit 191 may, for example, store the acquired first vehicle data in the memory device 19B or the auxiliary storage device 19A, and transmit the stored vehicle data to the analysis server 30 collectively at a predetermined timing.

[0082] The download processing unit 192 performs processing related to downloading update data for software from the distribution server 20 .

[0083] The storage unit 193 stores update data for software downloaded from the distribution server 20.

[0084] The software update unit 194 (an example of an update unit) uses update data for the software already downloaded to the storage unit 193 to update the software used in the gateway ECU 12, the ECU 13, the central ECU 19, and the like.

[0085] As described later, when the function of the vehicle data acquisition unit 196 is transferred to the analysis server 30, the software update unit 194 may update the software in response to a command from the distribution server 20 (for example, the notification unit 201).

[0086] The storage unit 195 stores various data used by the central ECU 19. For example, data of various programs installed in the central ECU 19 (auxiliary storage device) is registered (stored) in the storage unit 195. In addition, for example, data of parameters referenced in processing by the various programs of the central ECU 19 is registered (stored) in the storage unit 195.

[0087] When the software of the vehicle 10 is updated by the software update unit 194, the vehicle data acquisition unit 196 (an example of an acquisition unit) acquires predetermined vehicle data before and after the update. Hereinafter, the predetermined vehicle data to be acquired by the vehicle data acquisition unit 196 may be referred to as "second vehicle data" for convenience, in order to distinguish it from the vehicle data (first vehicle data) to be transmitted (to be acquired) by the vehicle data transmission unit 191 described above. The second vehicle data is a type of vehicle data necessary for the analysis server 30 to verify the effect obtained by the software update, and corresponds to some or all of the types of vehicle data of the multiple types of vehicle data corresponding to the first vehicle data. In addition, the second vehicle data may change depending on the type of software and the contents of the update. For example, information on the type of second vehicle data to be acquired may be specified in advance in a form linked to the contents of the software update, i.e., the update data, and may be distributed to the vehicle 10 from the distribution server 20, the analysis server 30, or the like. This allows the vehicle data acquisition unit 196 to acquire appropriate second vehicle data in accordance with the contents of the software update (update data).

[0088] For example, the vehicle data acquisition unit 196 records the type of vehicle data to be acquired as second vehicle data, which is specified according to the type of software and the contents of the update, in a ring buffer specified in the memory device 19B at each predetermined period in chronological order. Then, when a predetermined condition (hereinafter, "acquisition condition") specified according to the type of software and the contents of the update is satisfied, the vehicle data acquisition unit 196 acquires vehicle data for a predetermined period at the time when the acquisition condition is satisfied from the ring buffer as second vehicle data, and stores the data in the storage unit 198. The acquisition condition includes, for example, the driving conditions and environmental conditions of the vehicle 10 that are the premise for evaluating the effect of the software update. Alternatively, the acquisition condition may be one or more.

[0089] The function of the vehicle data acquisition unit 196 may be transferred to the analysis server 30. In this case, the functional unit (an example of an acquisition unit) of the analysis server 30 acquires (extracts) second vehicle data that matches an acquisition condition from the first vehicle data uploaded from the vehicle 10, for example. Then, the notification unit 201 (an example of an update unit) of the distribution server 20 may transmit a software update command to the vehicle 10 while grasping the acquisition status of the second vehicle data before the software update of the vehicle 10 in the analysis server 30. Thereby, even if the function of the vehicle data acquisition unit 196 is transferred to the analysis server 30, it is possible to perform the software update of the vehicle 10 after waiting for the acquisition of the second vehicle data before the software update.

[0090] The route guidance unit 197 controls the navigation device 16, and guides (leads) the user (driver) of the vehicle 10 to pass through a route suitable for acquiring the second vehicle data while grasping the position of the vehicle 10 based on the output of the GNSS sensor (sensor 15). For example, the central ECU 19 (route guidance unit 197) may directly output a control command to the navigation device 16 to control the navigation device 16. Also, for example, the central ECU 19 (route guidance unit 197) may control the navigation device 16 through the ECU 13 that controls the navigation device 16 by outputting a control command to the ECU 13.

[0091] The route suitable for acquiring the second vehicle data is a route on which changes in the state of the vehicle 10 due to software updates occur relatively frequently. The conditions of the route (road) suitable for acquiring the second vehicle data may be specified in advance by parameters such as the speed limit, the average speed of passing vehicles, the gradient, the radius of curvature of the curve, etc., and may be distributed to the vehicle 10 from the distribution server 20, the analysis server 30, etc. This allows the route guidance unit 197 to appropriately guide the user (driver) of the vehicle 10 to pass through a route suitable for acquiring the second vehicle data that matches the contents of the software update.

[0092] When the function of the vehicle data acquisition unit 196 is transferred to the analysis server 30, the function of the route guidance unit 197 may also be transferred to the analysis server 30. In this case, the functional unit of the analysis server 30 may control the navigation device 16 from outside the vehicle 10 while using a navigation server (not shown) to provide route guidance for the vehicle 10.

[0093] The storage unit 198 stores the second vehicle data acquired by the vehicle data acquisition unit 196.

[0094] The vehicle data transmission unit 199 transmits the second vehicle data stored in the storage unit 198 to the analysis server 30 through the gateway ECU 12 (communication device 11).

[0095] <Functional configuration of distribution server> 4, the distribution server 20 includes, as functional units, a notification unit 201 and a distribution unit 202. The functions of the notification unit 201 and the distribution unit 202 are realized, for example, by loading a program installed in the auxiliary storage device 22 into the memory device 23 and executing the program on the CPU 24.

[0096] When there is update data for software used in the vehicle 10, the notification unit 201 notifies the user of the vehicle 10 of the existence of the software update data. When the software update system 1 includes multiple vehicles 10, the software update system 1 notifies only the user of the vehicle 10 that is the target of the software update by the update data among the multiple vehicles 10 of the existence of the software update data. For example, when the multiple vehicles 10 include two or more vehicle models 10, the presence or absence of software update and the contents of the update may differ for each vehicle model. In addition, for example, even if the multiple vehicles 10 are all the same vehicle model, the presence or absence of software update and the contents of the update may differ depending on the grade. In addition, for example, depending on the contract content for the vehicle 10, the service that the user can receive, that is, the service for the price (fee) specified in the contract content, may differ, and the presence or absence of software update and the contents of the update may differ.

[0097] Specifically, the notification unit 201 transmits a signal notifying the vehicle 10 of the existence of software update data. This allows the central ECU 19 (download processing unit 192) of the vehicle 10 to notify the existence of software update data through the display device 18. Furthermore, the notification unit 201 may transmit a signal notifying the user terminal 40 of the user of the vehicle 10 of the existence of software update data instead of or in addition to the vehicle 10. This allows the user terminal 40 (notification unit 401) to notify the user of the vehicle 10 of the existence of software update data through the display device. Furthermore, when the user needs to pay a fee (charge) for the software update, the notification unit 201 may transmit a signal notifying the vehicle 10 or the user terminal 40 of the existence of software update data, including the contents of the predicted result of the effect of the software update and the amount of the fee. This allows the central ECU 19 (download processing unit 192) of the vehicle 10 to notify the user of the vehicle 10 of the existence of software update data together with the amount of the fee required for the software update through the display device 18. Furthermore, the user terminal 40 (notification unit 401) can notify the user of the vehicle 10 of the existence of software update data together with the amount of the fee required for the software update via the display device.

[0098] Furthermore, when a signal permitting software update (hereinafter, "update permission signal") is received from the vehicle 10 or the user terminal 40 of the user of the vehicle 10, the notification unit 201 transmits a signal notifying that effect to the analysis server 30. The update permission signal is a signal indicating that the user of the vehicle 10 has made a predetermined input for permitting software update through the input device 17 of the vehicle 10 or the input device of the user terminal 40. At this time, the signal includes information for identifying the target vehicle 10 (for example, identification information such as ID (Identifier) ​​and VIN (Vehicle Identification Number) specified for each vehicle 10), information on the contents of the software update, etc. This allows the analysis server 30 (effect evaluation unit 304 described later) to grasp the vehicle 10 for which the effect of the software update is to be evaluated, and the contents of the software update, etc.

[0099] The distribution unit 202 distributes software update data to the vehicle 10. For example, when an update permission signal is received from the vehicle 10 or the user terminal 40, the notification unit 201 transmits an update data distribution command to the distribution unit 202, and the distribution unit 202 transmits the update data to the target vehicle 10 in response to the update command.

[0100] <Analysis server functional configuration> 4, the analysis server 30 includes, as functional units, a virtual vehicle model acquisition unit 301, a virtual vehicle model storage unit 302, a simulator unit 303, and an effect evaluation unit 304. The functions of the virtual vehicle model acquisition unit 301, the simulator unit 303, and the effect evaluation unit 304 are realized, for example, by loading a program installed in an auxiliary storage device of the analysis server 30 into a memory device and executing the program on a CPU. The function of the virtual vehicle model storage unit 302 is realized, for example, by a storage area defined in the auxiliary storage device of the analysis server 30.

[0101] The virtual vehicle model acquisition unit 301 (an example of a generation unit) acquires a virtual model (hereinafter, "virtual vehicle model") corresponding to the vehicle 10. The virtual vehicle model is a digital model in which various characteristics of the vehicle 10 are reproduced in a virtual space. The virtual vehicle model may be, for example, a full vehicle model in which various overall characteristics of the vehicle 10 are reproduced, or a partial vehicle model in which only some characteristics of the vehicle 10 that are the subject of effect prediction described below are reproduced. The virtual vehicle model may also be a three-dimensional model in which the shape of part or all of the vehicle 10 is reproduced.

[0102] For example, the virtual vehicle model acquisition unit 301 acquires a general-purpose virtual model (an example of a general-purpose model) of the same vehicle type or the same vehicle type and grade as the vehicle 10 as the virtual vehicle model. The general-purpose virtual vehicle model may be, for example, a full vehicle model or a partial vehicle model of the final specifications of the vehicle type or grade corresponding to the vehicle 10, which is created in the development stage of a vehicle type corresponding to the vehicle 10.

[0103] Also, for example, the virtual vehicle model acquisition unit 301 may acquire the virtual vehicle model by generating a dedicated virtual model (one example of a dedicated model) for each vehicle 10. Specifically, the virtual vehicle model acquisition unit 301 may generate a virtual vehicle model dedicated to the vehicle 10 by appropriately updating the virtual vehicle model based on a general-purpose virtual vehicle model and based on the first vehicle data uploaded from the vehicle 10. In this way, the virtual vehicle model acquisition unit 301 can generate (update) the virtual vehicle model in accordance with at least one of the changes over time of the vehicle 10, the use conditions of the vehicle 10, and the changes in the components of the vehicle 10. Therefore, the changes over time of the vehicle 10, the use conditions of the vehicle 10, and the changes in the components of the vehicle 10 can be reflected in the virtual vehicle model dedicated to the vehicle 10. The use conditions of the vehicle 10 may include, for example, conditions related to the environment in which the vehicle 10 is used, driving conditions when the vehicle 10 is used, and conditions related to the frequency with which the vehicle 10 is used. The changes in the components of the vehicle 10 may include, for example, changes in hardware such as parts of the vehicle 10, changes in the software of the vehicle 10, changes in the type of coolant or lubricant used in the vehicle 10, etc. In addition, the virtual vehicle model acquisition unit 301 may generate a digital twin as a dedicated model corresponding to the vehicle 10 by updating the virtual vehicle model in real time based on vehicle data successively uploaded from the vehicle 10.

[0104] The virtual vehicle model storage unit 302 stores the virtual vehicle model acquired (generated) by the virtual vehicle model acquisition unit 301. When the software update system 1 includes a plurality of vehicles 10, a virtual vehicle model is stored for each of the plurality of vehicles 10. However, as described above, when a generic model is acquired as the virtual vehicle model, a generic virtual vehicle model common to some or all of the plurality of vehicles 10 may be stored in the virtual vehicle model storage unit 302 as the virtual vehicle model.

[0105] The simulator unit 303 performs a virtual simulation for the vehicle 10, using the virtual vehicle model of the vehicle 10 registered (stored) in the virtual vehicle model storage unit 302. The virtual simulation for the vehicle 10 includes a running simulation of the vehicle 10 under predetermined running conditions.

[0106] The effect evaluation unit 304 (an example of an evaluation unit) evaluates the effect obtained by updating the software used in the vehicle 10 based on second vehicle data uploaded from the vehicle 10, both before and after the software update of the vehicle 10.

[0107] For example, the effect evaluation unit 304 evaluates the effect of updating the software used in the vehicle 10 by comparing the second vehicle data before and after the software update of the vehicle 10. Specifically, the effect evaluation unit 304 may compare vehicle data related to the effect of the software update that is included in the second vehicle data before and after the software update of the vehicle 10 or that is derived (calculated) from the second vehicle data. In this way, the effect evaluation unit 304 can relatively easily evaluate the effect of updating the software of the vehicle 10 by comparing the second vehicle data that has already been acquired by the vehicle 10 (vehicle data acquisition unit 196).

[0108] Also, for example, the effect evaluation unit 304 causes the simulator unit 303 to perform virtual simulations corresponding to the vehicle 10 before and after the software update, respectively, using second vehicle data before and after the software update of the vehicle 10. Specifically, the simulator unit 303 may perform a virtual simulation of the vehicle 10 under the same driving conditions and environmental conditions, using virtual vehicle models corresponding to the vehicle 10 before and after the software update, respectively, which reflect the second vehicle data before and after the software update of the vehicle 10. The driving conditions during the virtual simulation are variable, for example, depending on the type of software and the contents of the update. This is because the driving conditions under which the characteristics of the vehicle 10 change with the software update may differ depending on the type of software and the contents of the update. Then, the effect evaluation unit 304 may evaluate the effect of the software update of the vehicle 10 by comparing the results of the virtual simulations corresponding to the vehicle 10 before and after the software update. In this way, the effect evaluation unit 304 can evaluate the effect of the software update of the vehicle 10 with higher accuracy by comparing the results of the virtual simulations under the same conditions.

[0109] Furthermore, the effect evaluation unit 304 may evaluate the effect of the software update using a comparison result of the second vehicle data before and after the software update and a comparison result of a virtual simulation corresponding to each of the software update before and after the software update. For example, the effect evaluation unit 304 compares a change in the characteristics of the vehicle 10 obtained by comparing the second data before and after the software update with a change in the characteristics of the vehicle 10 obtained by comparing the results of the virtual simulation corresponding to each of the software update before and after the software update. Specifically, the effect evaluation unit 304 may evaluate the effect of the software update by averaging the change in the characteristics of the vehicle 10 obtained by comparing the second vehicle data of the actual vehicle 10 with the change in the characteristics of the vehicle 10 obtained by comparing the results of the virtual simulation.

[0110] Furthermore, when evaluating the effectiveness of whether a state of vehicle 10 in accordance with the contents of an update to the software of vehicle 10 has been achieved, the effect evaluation unit 304 may use only the second data after the update out of the second data before and after the update.

[0111] For example, when evaluating the effect of improving performance, which corresponds to the purpose of the software update, the effect evaluation unit 304 may evaluate the presence or absence of the effect based on whether or not an index value of the performance improved by the software update exceeds a predetermined standard. The effect evaluation unit 304 may also evaluate the degree of the effect based on the index value of the performance improved by the software update.

[0112] Furthermore, the effect evaluation unit 304 may select an effect evaluation method according to, for example, the type of software and the contents of the update. Specifically, the effect evaluation unit 304 may determine whether to compare the second vehicle data before and after the software update of the vehicle 10, or to perform virtual simulations corresponding to the software update of the vehicle 10 before and after the update, according to the type of software and the contents of the update. Which evaluation method to perform may be specified in advance for each update data, for example, and may be automatically determined according to the specified contents. Furthermore, whether to perform a virtual simulation may be determined using table information, for example, based on the type of software, the contents of the update, and characteristic items of the vehicle 10 that change due to the software update.

[0113] The function of the effect evaluation unit 304 may be transferred to the vehicle 10 (for example, the central ECU 19). In this case, the functional unit (an example of an evaluation unit) of the vehicle 10 (central ECU 19) evaluates the effect of the software update by, for example, checking the second vehicle data after the software update already acquired by the vehicle data acquisition unit 196 and comparing the second vehicle data before and after the software update.

[0114] <Functional configuration of user terminal> 4, the user terminal 40 includes, as a functional unit, a notification unit 401. The function of the notification unit 401 is realized, for example, by loading a program installed in an auxiliary storage device of the user terminal 40 into a memory device and executing it on a CPU.

[0115] The notification unit 401 notifies the user of the existence of update data for the software of the vehicle 10 through the display device based on the above-mentioned signal received from the distribution server 20. This allows the user of the vehicle 10 to know the existence of update data for the software of the vehicle 10 even when the vehicle 10 is not in use. Therefore, for example, the user can input permission for the software update through the input device of the user terminal 40, and complete the distribution of the update data to the vehicle 10 when the vehicle 10 is not in use.

[0116] [Specific example of how to evaluate the effectiveness of vehicle software updates] 5 to 9, a specific example of a method for evaluating the effect of updating the software of the vehicle 10 by the effect evaluation unit 304 will be described. Specifically, a method for evaluating the effect regarding improvement in performance, which corresponds to the purpose of updating the software of the vehicle 10, will be exemplarily described.

[0117] <First concrete example> Fig. 5 is a diagram showing an example of an update of the shift map of the transmission of the vehicle 10. Specifically, Fig. 5 shows the switching conditions between 1st and 2nd gears, between 2nd and 3rd gears, and between 3rd and 4th gears of the transmission of the vehicle 10 on a coordinate system in which the horizontal axis represents the speed of the vehicle 10 and the vertical axis represents the required driving force of the vehicle 10.

[0118] The required driving force of the vehicle 10 is determined, for example, according to the accelerator opening degree of the driver of the vehicle 10. In addition, in Fig. 5, the solid lines represent the switching conditions (shift lines) when shifting up, and the dotted lines represent the switching conditions (shift lines) when shifting down.

[0119] As shown in FIG. 5, in this example, the condition for switching between third and fourth gears is changed from a shift line 501 to a shift line 502 due to an update of software in the ECU 13 that controls the shift position of the transmission.

[0120] For example, the effect evaluation unit 304 uses the second vehicle data after the software update in the operating region 503 in which the switching condition between third and fourth gears has been changed to evaluate whether the gear shift of the transmission has been appropriately achieved in accordance with the contents of the software update. The effect evaluation unit 304 may also compare the second vehicle data in the operating region 503 before and after the software update to evaluate whether the gear shift of the transmission has been appropriately achieved in accordance with the contents of the software update.

[0121] Furthermore, for example, the effect evaluation unit 304 compares the second vehicle data related to the dynamic performance in the operating region 503 before and after the software update, and evaluates the effect of improving the dynamic performance (e.g., acceleration performance) of the vehicle 10. Furthermore, the effect evaluation unit 304 may compare the results of a virtual simulation based on a virtual vehicle model that reflects the second vehicle data in each of the operating regions 503 before and after the software update, and evaluate the effect of improving the dynamic performance of the vehicle 10.

[0122] Furthermore, for example, the effect evaluation unit 304 compares the second vehicle data related to energy-saving performance such as power consumption performance and fuel efficiency performance in the operating region 503 before and after the software update, and evaluates the energy-saving performance of the vehicle 10. Furthermore, the effect evaluation unit 304 may compare the results of a virtual simulation based on a virtual vehicle model reflecting the second vehicle data before and after the software update in the operating region 503, and evaluate the effect of improving the energy-saving performance of the vehicle 10.

[0123] In this way, in this example, the effect evaluation unit 304 can evaluate the effect of updating the software (gear shift map) of the vehicle 10 based on the second vehicle data uploaded from the vehicle 10.

[0124] <Second concrete example> Fig. 6 is a diagram showing an example of updating the prime mover switching map of the vehicle 10. In this example, the vehicle 10 is a so-called hybrid vehicle that can run by switching between two prime movers, an engine and an electric motor. Specifically, Fig. 6 shows, in a coordinate system in which the horizontal axis represents the vehicle speed of the vehicle 10 and the vertical axis represents the required driving force of the vehicle 10, switching conditions between a state in which the engine is stopped and the vehicle 10 is run only by the electric motor (MG) and a state in which the engine is started and the vehicle 10 is run by the engine.

[0125] Note that the state in which the vehicle 10 is run by the engine can include both a state in which the vehicle 10 is run by the engine alone and a state in which the vehicle 10 is run by both the engine and the electric motor.

[0126] As shown in FIG. 6, in this example, due to an update of the software of ECU 13, which controls the operating states of the two prime movers in an integrated manner, the switching condition for switching between a state in which vehicle 10 is run by the electric motor alone and a state in which vehicle 10 is run by the engine is updated from switching line 601 (thin solid line) to switching line 602 (thick solid line).

[0127] For example, the effect evaluation unit 304 evaluates whether switching between the two prime movers has been appropriately achieved in accordance with the contents of the software update by using the second vehicle data after the software update in the operating region 603 in which the prime mover switching conditions have been changed. The effect evaluation unit 304 may also compare the second vehicle data in the operating region 603 before and after the software update to evaluate whether switching between the two prime movers has been appropriately achieved in accordance with the contents of the software update.

[0128] Furthermore, for example, the effect evaluation unit 304 compares the second vehicle data related to fuel economy performance in the operating region 603 before and after the software update, and evaluates the effect of improving the fuel economy performance of the vehicle 10. Furthermore, the effect evaluation unit 304 may compare the results of a virtual simulation based on a virtual vehicle model that reflects the second vehicle data in each of the operating regions 603 before and after the software update, and evaluate the effect of improving the power performance of the vehicle 10.

[0129] In this way, in this example, the effect evaluation unit 304 can evaluate the effect of updating the software (the prime mover switching map) based on the second vehicle data uploaded from the vehicle 10.

[0130] <Third Specific Example> FIG. 7 is a diagram showing an example (time chart 700) of the change over time of the actual state of the vehicle 10 at the time of a shift change of the transmission, before and after updating the control logic related to the shift change (upshift) of the transmission of the vehicle 10. Specifically, FIG. 7 is a diagram showing second vehicle data of one vehicle 10 included in the software update system 1. The time chart 700 includes time charts 701 to 704 showing the change over time of the release pressure command value, the engagement pressure command value, the rotation speed of the prime mover (engine), and the longitudinal acceleration of the vehicle 10 at the time of a shift change of the transmission. FIG. 8 is a diagram showing another example (time chart 800) of the change over time of the state of the vehicle 10 at the time of a shift change of the transmission, before and after updating the control logic related to the shift change (upshift) of the transmission of the vehicle 10. Specifically, FIG. 8 is a diagram showing second vehicle data of another vehicle 10 equipped with a transmission of the same specifications as the one vehicle 10 described above, included in the software update system 1. The time chart 800 includes time charts 801 to 804 which show the time-dependent changes in the release pressure command value, the engagement pressure command value, the rotation speed of the output shaft of the transmission, and the longitudinal acceleration of the vehicle 10 at the time of a shift change of the transmission. FIG. 9 shows an example (time chart 900) of the result of a virtual simulation of the time-dependent changes in the state of the vehicle 10 at the time of a shift change of the transmission, before and after updating the control logic related to the shift change (upshift) of the transmission of the vehicle 10. Specifically, FIG. 9 shows the result of a virtual simulation based on a virtual vehicle model dedicated to the above-mentioned one vehicle 10, which is included in the software update system 1. The time chart 900 includes time charts 901 to 904 which show the time-dependent changes in the release pressure command value, the engagement pressure command value, the rotation speed of the output shaft of the transmission, and the longitudinal acceleration of the vehicle 10 at the time of a shift change of the transmission.

[0131] The release pressure command value represents a command value of hydraulic pressure for operating components of the transmission that transition from an engaged state to a released state by a shift change (e.g., brakes, clutches, etc.). The engagement pressure command value represents a command value of hydraulic pressure for operating components of the transmission that transition from a released state to an engaged state by a shift change. In addition, in Figs. 7 to 9, the control logic related to the shift changes of the transmission before and after the update is the same. Therefore, time charts 701, 702, time charts 801, 802, and time charts 901, 902, which correspond to the control logic, are the same.

[0132] As shown in Figures 7 to 9, in this example, the control logic for the shift change of the transmission is updated so as to shorten the time (shift time) from the start of the shift change (upshift) (the start of the decrease in the release pressure command value) to the end (the end of the increase in the engagement pressure command value).

[0133] For example, the effect evaluation unit 304 may use the time charts 701 and 702 after the software update to evaluate whether or not a control logic according to the contents of the software update is properly realized in one vehicle 10. Similarly, the effect evaluation unit 304 may use the time charts 801 and 802 after the software update to evaluate whether or not a control logic according to the contents of the software update is properly realized in another vehicle 10. Furthermore, the effect evaluation unit 304 may compare the time charts 701 and 702 before and after the software update to evaluate whether or not a control logic according to the contents of the software update is properly realized in one vehicle 10. Similarly, the effect evaluation unit 304 may compare the time charts 701 and 702 before and after the software update to evaluate whether or not a control logic according to the contents of the software update is properly realized in another vehicle 10.

[0134] Also, for example, the effect evaluation unit 304 compares the time charts 703, 704 before and after the software update, and evaluates the effect of improving the speed of shifting of the transmission (shifting speed). Similarly, the effect evaluation unit 304 may compare the time charts 803, 804 before and after the software update, and evaluate the effect of improving the speed of shifting of the transmission (shifting speed).

[0135] In time chart 703, the rate of change (rate of change over time) of the rotation speed of the prime mover (engine) accompanying a gear shift in the transmission becomes relatively large due to the update of the control logic. Also, in time chart 704, the fluctuation in the longitudinal acceleration of vehicle 10 accompanying a gear shift in the transmission also becomes relatively large. Therefore, the user of one vehicle 10 can clearly feel the improvement in the gear shift speed of the transmission. Therefore, in the case of one vehicle 10, the effect evaluation unit 304 can evaluate that there is an effect of improving the gear shift speed by the software update, or that the degree of the effect is relatively large.

[0136] On the other hand, in time chart 803, the rate of change (rate of change over time) of the rotational speed of the prime mover (engine) accompanying a shift change of the transmission remains almost unchanged before and after the update of the control logic. Also, in time chart 804, there is almost no change in the magnitude of fluctuation in the longitudinal acceleration of vehicle 10 accompanying a shift change of the transmission before and after the update of the control logic. Therefore, it becomes difficult for users of other vehicles 10 to realize the improvement in the shift speed of the transmission. Therefore, in the case of other vehicles 10, the effect evaluation unit 304 can predict that there is no effect of improving the shift speed by updating the software, or that the degree of the effect is relatively small.

[0137] Incidentally, as a cause of the difference in the effect of updating the control logic between vehicles 10 equipped with the same specifications of transmissions, for example, the influence of the viscosity of the lubricating oil used in the transmission is considered. For example, if a commercially available lubricating oil with a higher viscosity than the lubricating oil filled in the transmission at the time of shipment from the factory is used, the user may find it difficult to realize the improvement in the shifting speed. In addition, as a cause of the difference in the effect of updating the control logic between vehicles 10 equipped with the same specifications of transmissions, for example, the influence of manufacturing variations in the clearance of the clutch pack of the transmission is considered. For example, when the clearance of the clutch pack of the transmission is near the lower limit of the manufacturing tolerance range, the user may find it difficult to realize the improvement in the shifting speed compared to when it is near the upper limit. In addition, as a cause of the difference in the effect of updating the control logic between vehicles 10 equipped with the same specifications of transmissions, for example, the influence of the cumulative number of shifts of the transmission is considered. For example, when the cumulative number of shifts after the vehicle 10 is shipped from the factory or after the transmission is replaced with a new one is relatively small, the clearance of the clutch pack of the transmission is relatively small compared to when the cumulative number of shifts is large, and the user may find it difficult to realize the improvement in the shift speed. In addition, a cause of the difference in the effect of updating the control logic between vehicles 10 equipped with transmissions of the same specifications is, for example, the influence of air leakage from a solenoid valve that engages and releases the clutch and brake of the transmission. For example, when the air leakage from the solenoid valve of the transmission is relatively small, the shift speed is relatively higher than when the air leakage is relatively large, so that even if the control logic is updated, the user may find it difficult to realize the improvement in the shift speed. In addition, a cause of the difference in the effect of updating the control logic between vehicles 10 equipped with transmissions of the same specifications is, for example, the influence of the temperature environment in which the vehicle 10 is used. For example, when the vehicle 10 is used in a so-called cold climate where the temperature is very low, the viscosity of the lubricating oil becomes higher than when the vehicle is used in a relatively warm temperature condition, so that even if the control logic is updated, the user may find it difficult to feel an improvement in the gear shifting speed.

[0138] Also, for example, the effect evaluation unit 304 may use time charts 903, 904 resulting from a virtual simulation instead of or in addition to the time charts 703, 704 to evaluate the effect of improving the speed of shifting (shifting speed) of the transmission of one vehicle 10. Specifically, the effect evaluation unit 304 may compare the time charts 903, 904 before and after the software update to evaluate the effect of improving the speed of shifting (shifting speed) of the transmission of one vehicle 10. This allows the effect evaluation unit 304 to compare the time charts of the rotation speed of the output shaft of the transmission and the longitudinal acceleration of the vehicle 10 under the same conditions, such as the driving conditions and environmental conditions, before and after the software update. Therefore, the effect evaluation unit 304 can evaluate the effect of improving the shifting speed of the transmission of one vehicle 10 with higher accuracy.

[0139] In time chart 903, as in the case of time chart 703, the rate of change (rate of change over time) of the rotation speed of the prime mover (engine) accompanying a shift change of the transmission becomes relatively large due to the update of the control logic. Also, in time chart 904, as in the case of time chart 704, the fluctuation in the longitudinal acceleration of the first vehicle 10 accompanying a shift change of the transmission also becomes relatively large. Therefore, the user of the first vehicle 10 can clearly feel the improvement in the shift speed of the transmission. Therefore, in the case of the first vehicle 10, the effect evaluation unit 304 can evaluate that there is an effect of improving the shift speed by the software update, or that the degree of the effect is relatively large.

[0140] In addition, as in the case of one vehicle 10, the effect evaluation unit 304 may evaluate the effect of improving the shift change speed (gear change speed) of the transmission of another vehicle 10 using a time chart resulting from a virtual simulation instead of or in addition to the time charts 803, 804.

[0141] In this way, in this example, the effect evaluation unit 304 can evaluate the effect of updating the software (the program related to the control logic for shifting the transmission) based on the second vehicle data uploaded from the vehicle 10.

[0142] [An example of software update processing] Next, an example of a process related to updating software of the vehicle 10 by the central ECU 19 (hereinafter, "software update process") will be described with reference to Figs. 10 and 11.

[0143] 10 and 11 are flowcharts showing an example of software update processing by the central ECU 19. This flowchart is repeatedly executed, for example, from the end of the initial processing at the start of the vehicle 10 to the start of the termination processing at the stop of the vehicle. The start of the vehicle 10 is, for example, when the ignition switch of the vehicle 10 is turned on, and the stop of the vehicle 10 is, for example, when the ignition switch of the vehicle 10 is turned off.

[0144] In this example, the description will be given on the assumption that the gateway ECU 12 and the central ECU 19 are operable even when the vehicle 10 is stopped.

[0145] 10, in step S102, the vehicle data acquisition unit 196 determines whether or not the acquisition of second vehicle data before the software update, which is started in step S114 described below, is in progress. If the vehicle data acquisition unit 196 is in the middle of acquiring second vehicle data before the software update, the process proceeds to step S114, and otherwise the process proceeds to step S104.

[0146] In step S104, the vehicle data acquisition unit 196 determines whether or not the acquisition of second vehicle data after the software update, which is started in step S130 described below, is in progress. If the vehicle data acquisition unit 196 is in the middle of acquiring the second vehicle data after the software update, the process proceeds to step S130, and otherwise the process proceeds to step S106.

[0147] In step S106, download processing unit 192 determines whether or not a signal notifying the presence of software update data has been received from distribution server 20. If a signal notifying the presence of update data has been received from distribution server 20, download processing unit 192 proceeds to step S108; otherwise, download processing unit 192 ends the processing of this flowchart.

[0148] In step S108, download processing unit 192 causes display device 18 to display a notification screen notifying the user of the presence of software update data.

[0149] When the process of step S108 is completed and an input regarding permission or non-permission of the software update is received via the input device 17, the central ECU 19 proceeds to step S110.

[0150] In step S110, download processing unit 192 determines whether or not an input for permitting the software update has been received. If an input for permitting the software update has been received, download processing unit 192 proceeds to step S112, and if an input for rejecting the software update has been received, download processing unit 192 ends this flow chart.

[0151] In step S112, the download processing unit 192 starts downloading the update data.

[0152] When the central ECU 19 completes the process of step S112, the process proceeds to step S114.

[0153] Note that before the user is asked whether or not to permit the software update, the update data may be downloaded to the vehicle 10. In this case, the process of step S112 is omitted.

[0154] In step S114, vehicle data acquisition unit 196 starts acquiring the second vehicle data.

[0155] When the process of step S114 is completed, the central ECU 19 proceeds to step S116.

[0156] In step S116, vehicle data acquisition unit 196 (an example of a determination unit) determines whether acquisition of the second vehicle data has been completed. For example, when there are multiple acquisition conditions, vehicle data acquisition unit 196 determines whether acquisition of the second vehicle data for each of the multiple acquisition conditions has been completed. If acquisition of the second vehicle data has not been completed, vehicle data acquisition unit 196 proceeds to step S118, and if completed, proceeds to step S126.

[0157] In step S118, the vehicle data acquisition unit 196 determines whether the vehicle 10 has been stopped (for example, whether the ignition switch has been turned off). If the vehicle 10 has not been stopped, the vehicle data acquisition unit 196 proceeds to step S120. On the other hand, if the vehicle 10 has been stopped, the vehicle data acquisition unit 196 turns ON a flag indicating that the vehicle 10 is in the middle of acquiring the second vehicle data before the software update, and ends the processing of this flowchart. This allows the vehicle data acquisition unit 196 to determine in step S102 that the vehicle 10 is in the middle of acquiring the second vehicle data before the software update the next time the vehicle 10 is started.

[0158] In step S120, the vehicle data acquisition unit 196 determines whether or not a predetermined time has elapsed since the start of acquisition of the second vehicle data. The predetermined time may be fixed regardless of the type of software or the contents of the update, or may be variable depending on the type of software and the contents of the update. If the predetermined time has elapsed since the start of acquisition of the second vehicle data, the vehicle data acquisition unit 196 proceeds to step S122, and if the predetermined time has not elapsed, the vehicle data acquisition unit 196 returns to step S116.

[0159] In step S122, the route guidance unit 197 determines whether or not route guidance suitable for obtaining second vehicle data in step S124 described below has been performed. If route guidance has not been performed, the route guidance unit 197 proceeds to step S124, and if route guidance has been performed, the route guidance unit 197 returns to step S116.

[0160] In step S124, the route guidance unit 197 controls the navigation device 16 to search for a route suitable for acquiring the second vehicle data, and guides (leads) the user (driver) of the vehicle 10 along the route.

[0161] When the process of step S124 is completed, the central ECU 19 returns to step S116.

[0162] In addition, the route guidance unit 197 may search for a route suitable for acquiring the second vehicle data in accordance with the start of acquisition of the second vehicle data by the vehicle data acquisition unit 196, and may start guiding the user (driver) of the vehicle 10 to pass through the route. In this case, the process of step S124 is performed immediately before step S114. In addition, the processes of steps S120 and S122 are also omitted, and if it is determined in step S118 that the vehicle 10 is not stopped, the process returns to step S116. In addition, the process of step S124 may be omitted. In this case, the processes of steps S120 and S122 are also omitted, and if it is determined in step S118 that the vehicle 10 is not stopped, the process returns to step S116.

[0163] In step S126, the software update unit 194 determines whether or not the software can be updated. For example, the software update unit 194 determines that the software can be updated when the download of the update data by the download processing unit 192 is completed and the state of the vehicle 10 is suitable for updating the software.

[0164] The state of the vehicle 10 suitable for software update varies depending on the type of software and the contents of the update. For example, in the case of software update related to the running of the vehicle 10 (for example, software update in Figs. 5 to 9), the state of the vehicle 10 suitable for the software update is the stopped state of the vehicle 10 (for example, the ignition switch is in the off state). On the other hand, for example, in the case of software update not related to the running of the vehicle 10, the state of the vehicle 10 suitable for the software update may include the state from starting to stopping the vehicle 10. Information regarding the state of the vehicle 10 suitable for the software update may be specified in advance for each update data, and may be downloaded from the distribution server 20 to the central ECU 19 together with the update data.

[0165] If the software update is possible, the software update section 194 proceeds to step S128, and if the software update is not possible, the software update section 194 waits while repeating the process of step S126 until the software update is possible.

[0166] In step S128, software update unit 194 uses the update data already downloaded to storage unit 193 to update the software.

[0167] When the process of step S128 is completed, the central ECU 19 proceeds to step S130.

[0168] As shown in FIG. 11, in step S130, the vehicle data acquisition unit 196 starts acquiring the second vehicle data.

[0169] When the process of step S130 is completed, the central ECU 19 proceeds to step S132.

[0170] In step S132, the vehicle data acquisition unit 196 determines whether acquisition of the second vehicle data has been completed. If acquisition of the second vehicle data has not been completed, the vehicle data acquisition unit 196 proceeds to step S134, and if acquisition of the second vehicle data has been completed, the vehicle data acquisition unit 196 proceeds to step S142.

[0171] In step S134, the vehicle data acquisition unit 196 determines whether the vehicle 10 has been stopped (for example, whether the ignition switch has been turned off). If the vehicle 10 has not been stopped, the vehicle data acquisition unit 196 proceeds to step S136. On the other hand, if the vehicle 10 has been stopped, the vehicle data acquisition unit 196 turns ON a flag indicating that the vehicle 10 is in the middle of acquiring second vehicle data after a software update, for example, and ends the processing of this flowchart. This allows the vehicle data acquisition unit 196 to determine in step S104 that the vehicle 10 is in the middle of acquiring second vehicle data after a software update the next time the vehicle 10 is started.

[0172] In step S136, the vehicle data acquisition unit 196 determines whether or not a predetermined time has elapsed since the start of acquisition of the second vehicle data. The predetermined time may be fixed regardless of the type of software, the contents of the update, etc., or may be variable depending on the type of software, the contents of the update, etc. If the predetermined time has elapsed since the start of acquisition of the second vehicle data, the vehicle data acquisition unit 196 proceeds to step S138, and if the predetermined time has not elapsed, the vehicle data acquisition unit 196 returns to step S132.

[0173] In step S138, the vehicle data acquisition unit 196 determines whether or not route guidance suitable for acquiring second vehicle data in step S140 described below has been performed. If route guidance has not been performed, the vehicle data acquisition unit 196 proceeds to step S140, and if route guidance has been performed, the vehicle data acquisition unit 196 returns to step S132.

[0174] In step S140, similarly to step S124, the route guidance unit 197 controls the navigation device 16 to search for a route suitable for acquiring the second vehicle data, and guides (leads) the user (driver) of the vehicle 10 to pass through the route. At this time, the route guidance unit 197 may guide the user to pass through the same route as when the second vehicle data before the software update was acquired, as the route suitable for acquiring the second vehicle data.

[0175] When the process of step S140 is completed, the central ECU 19 returns to step S132.

[0176] In addition, the route guidance unit 197 may search for a route suitable for acquiring the second vehicle data in accordance with the start of acquisition of the second vehicle data by the vehicle data acquisition unit 196, and may start guiding the user (driver) of the vehicle 10 to pass through the route. In this case, the process of step S140 is performed immediately before step S130. In addition, the processes of steps S136 and S138 are also omitted, and if it is determined in step S134 that the vehicle 10 is not stopped, the process returns to step S132. In addition, the process of step S140 may be omitted. In this case, the processes of steps S136 and S138 are also omitted, and if it is determined in step S134 that the vehicle 10 is not stopped, the process returns to step S132.

[0177] In step S142, the vehicle data transmission unit 199 transmits the second vehicle data before and after the software update stored in the storage unit 198 to the analysis server 30 via the gateway ECU 12 (communication device 11). This enables the analysis server 30 (effect evaluation unit 304) to acquire (receive) the second vehicle data before and after the software update and evaluate the effect of the software update.

[0178] When the process of step S142 is completed, the central ECU 19 ends the process of this flowchart.

[0179] In this manner, in this example, the central ECU 19 performs software update after completing acquisition of the second vehicle data.

[0180] This allows the central ECU 19 to reliably acquire the second vehicle data before the software update. As a result, the software update system 1 can reliably evaluate the effect of the software update by using the second vehicle data before and after the software update.

[0181] [Another example of software update processing] Next, another example of the software update process by the central ECU 19 will be described with reference to FIGS.

[0182] The processing in steps S202 to S212 is the same as the processing in steps S102 to S112 in FIG. 10, and therefore a description thereof will be omitted.

[0183] When the process of step S212 is completed, the central ECU 19 proceeds to step S214.

[0184] In step S214, the vehicle data acquisition unit 196 determines the number of times N1 (an integer equal to or greater than 2) the second vehicle data is acquired before the software update. For example, as described above, when the second vehicle data is acquired as time-series data for a predetermined period when the acquisition condition is satisfied, the number of times N1 corresponds to the number of pieces of second vehicle data acquired as time-series data for the predetermined period. Also, for example, when there are multiple acquisition conditions, the number of times N1 corresponds to the number of times the second vehicle data is acquired for each of the multiple acquisition conditions. The number of times N1 may be fixed or may be variable.

[0185] The number of acquisitions N1 is variable depending on, for example, the type of software and the contents of the update. For example, depending on the type of software and the contents of the update, the range of acquisition conditions (driving conditions, environmental conditions, etc.) for the second vehicle data may be very narrow, increasing the probability of acquiring inappropriate second vehicle data. Therefore, in such a case, by acquiring more second vehicle data under the same acquisition conditions, the probability of acquiring appropriate second vehicle data can be increased. Also, for example, depending on the type of software and the contents of the update, the variation in the type of second vehicle data to be acquired may be relatively large. Therefore, in such a case, by acquiring more second vehicle data under the same acquisition conditions, the analysis server 30 can statistically process the multiple second vehicle data and more accurately evaluate the effect of the software update.

[0186] The number of acquisitions N1 is variable depending on, for example, the scale of the software update. The scale of the software update is determined, for example, by the number of characteristic items of the vehicle 10 that are updated by the software update. The scale of the software update may also be determined, for example, by the amount of data of the software update data.

[0187] For example, the more the number of characteristic items that change due to software update, the higher the interest of the manufacturer and developer of the vehicle 10 in the effect of the software update. Also, for example, the more the characteristic items of the vehicle 10 that change due to software update, the higher the number of lines of source code of the program and the scale of reference data become, and as a result, the data amount of the update data becomes relatively large. Also, for example, when a specific characteristic item of the vehicle 10 is significantly improved by software update, the number of lines of source code of the program and the scale of reference data become, and as a result, the data amount of the update data becomes relatively large due to a major modification of the algorithm, and as a result, the data amount of the update data becomes relatively large. And, the more the characteristic items of the vehicle 10 that change due to software update, or the higher the improvement amount of a specific characteristic item of the vehicle 10 becomes, the higher the possibility that the manufacturer and developer of the vehicle 10 will be, and the higher the possibility that the manufacturer and developer of the vehicle 10 will be, and the higher the possibility that the manufacturer and developer of the vehicle 10 will require a more accurate evaluation result of the effect of the software update. Therefore, the larger the scale of the software update, the higher the possibility that the manufacturer and developer of the vehicle 10 will require a more accurate evaluation result of the effect of the software update. Therefore, the number of acquisitions N1 may be varied so as to become larger (more) as the scale of the software update increases.

[0188] When the process of step S214 is completed, the central ECU 19 proceeds to step S216.

[0189] Step S216 is the same as the process in step S114 in FIG. 10, and therefore a description thereof will be omitted.

[0190] When the process of step S216 is completed, the central ECU 19 proceeds to step S218.

[0191] In step S218, the vehicle data acquisition unit 196 determines whether or not acquisition of the second vehicle data for the acquisition number N1 has been completed. If the vehicle data acquisition unit 196 has not completed acquisition of the second vehicle data for the acquisition number N1, the process proceeds to step S220, and if the vehicle data acquisition unit 196 has completed acquisition of the second vehicle data for the acquisition number N1, the process proceeds to step S228.

[0192] Steps S220 to S230 are the same as the processes in steps S118 to S128 in FIG. 1, and therefore a description thereof will be omitted.

[0193] When the process of step S230 is completed, the central ECU 19 proceeds to step S232.

[0194] In step S232, the vehicle data acquisition unit 196 determines the number of acquisitions N2 of the second vehicle data after the software update. For example, as described above, when the second vehicle data is acquired as time-series data for a predetermined period when the acquisition condition is satisfied, the number of acquisitions N2 corresponds to the number of second vehicle data acquired as time-series data for a predetermined period, similar to the number of acquisitions N1. Also, for example, when there are a plurality of acquisition conditions, the number of acquisitions N2 corresponds to the number of acquisitions of the second vehicle data for each of the plurality of acquisition conditions, similar to the number of acquisitions N1. The number of acquisitions N2 may be fixed or variable, similar to the number of acquisitions N1. Also, the number of acquisitions N2 may be the same as the number of acquisitions N1, or may be different.

[0195] The number of acquisitions N2 varies depending on the type of software and the details of the updates, for example, in the same way as the number of acquisitions N1.

[0196] Also, like the acquisition number N1, the acquisition number N2 is variable according to the scale of the software update. Specifically, the acquisition number N2 may be variable so that it becomes larger (more) as the scale of the software update becomes larger. Also, the acquisition number N2 may be the same as the acquisition number N1, or may be different.

[0197] When the process of step S232 is completed, the central ECU 19 proceeds to step S234.

[0198] As shown in FIG. 13, step S234 is the same as step S130 in FIG. 11, and therefore a description thereof will be omitted.

[0199] When the process of step S234 is completed, the central ECU 19 proceeds to step S236.

[0200] In step S236, the vehicle data acquisition unit 196 determines whether or not acquisition of the second vehicle data for the acquisition number N2 has been completed. If the vehicle data acquisition unit 196 has not completed acquisition of the second vehicle data for the acquisition number N2, the process proceeds to step S238, and if the vehicle data acquisition unit 196 has completed acquisition of the second vehicle data for the acquisition number N2, the process proceeds to step S246.

[0201] Steps S238 to S246 are the same as the processes in steps S134 to S142 in FIG. 11, and therefore a description thereof will be omitted.

[0202] When the process of step S246 is completed, the central ECU 19 ends the process of this flowchart.

[0203] In this manner, in this example, the central ECU 19 performs a software update after completing acquisition of the second vehicle data the acquisition number N1, which is 2 or more. In addition, after the software update, the central ECU 19 acquires the second vehicle data the acquisition number N2, which is 2 or more.

[0204] This allows the central ECU 19 to acquire multiple pieces of second vehicle data before and after the software update. Therefore, the software update system 1 (analysis server 30) can, for example, remove inappropriate data from the acquired multiple pieces of second vehicle data or statistically process the acquired multiple pieces of second vehicle data to evaluate the effect of the software update. Therefore, the software update system 1 can more reliably and more accurately evaluate the effect of the software update.

[0205] [An example of a process for evaluating the effectiveness of software updates] Next, an example of a process of evaluating the effect of updating software of the vehicle 10 by the analysis server 30 will be described with reference to FIG.

[0206] Fig. 14 is a flowchart outlining an example of a process for evaluating the effect of updating software of the vehicle 10, performed by the analysis server 30. This flowchart is executed, for example, when second vehicle data before and after the software update is received from the vehicle 10. The same may be applied to the flowchart in Fig. 15 described below.

[0207] As shown in FIG. 14, in step S302, the effect evaluation unit 304 compares the second vehicle data before and after the software update uploaded from the vehicle 10, and evaluates the effect of the software update on the target vehicle 10.

[0208] For example, when there is one second vehicle data before and after the software update, the effect evaluation unit 304 evaluates the effect of the software update of the vehicle 10 by directly comparing the second vehicle data with each other. The effect evaluation unit 304 may also evaluate the effect of the software update of the vehicle 10 by correcting at least one of the second vehicle data before and after the software update and comparing the corrected second vehicle data with each other. For example, at least one of the second vehicle data before and after the software update is corrected by a predetermined method so as to eliminate relative differences in driving conditions, environmental conditions, etc. at the time of acquisition of each, or absolute differences with respect to a predetermined standard such as driving conditions and environmental conditions at the time of acquisition. When there are multiple second vehicle data before and after the software update (see FIG. 12 and FIG. 13), the effect evaluation unit 304 may perform statistical processing on the multiple second vehicle data to generate one processed second vehicle data, and compare the processed second vehicle data with each other to evaluate the effect of the software update. At this time, the effect evaluation unit 304 may remove inappropriate second vehicle data from the plurality of second vehicle data. The inappropriate second vehicle data is, for example, vehicle data that corresponds to an abnormal value that exceeds an expected range among the plurality of second vehicle data, second vehicle data in a state where the acquisition condition is not satisfied, etc.

[0209] When step S302 is completed, the analysis server 30 proceeds to step S304.

[0210] In step S304, the effect evaluation unit 304 determines whether or not the software update has been evaluated as having an effect in step S302.

[0211] For example, when the evaluation target is the effect related to the improvement (enhancement) of performance corresponding to the purpose of the software update, the effect evaluation unit 304 evaluates the presence or absence of the effect based on whether or not the index value as the evaluation result exceeds a predetermined standard. Also, for example, when the evaluation target is the effect related to whether or not the state of the vehicle 10 in accordance with the contents of the software update is realized, the effect evaluation unit 304 evaluates that there is an effect when the state of the vehicle 10 in accordance with the contents of the software update is realized.

[0212] If the software update is effective, the effect evaluation unit 304 proceeds to step S306, and if the software update is not effective, the effect evaluation unit 304 proceeds to step S308.

[0213] In step S306, the effect evaluation unit 304 sets a flag indicating that the software update is effective to "ON."

[0214] When the process of step S306 is completed, the analysis server 30 proceeds to step S310.

[0215] On the other hand, in step S308, the effect evaluation unit 304 sets the flag indicating that the software update is effective to "OFF."

[0216] When the process of step S308 is completed, the analysis server 30 proceeds to step S310.

[0217] In step S310, the effect evaluation unit 304 registers data on the evaluation result of the effect of updating the software of the target vehicle 10, including the flag data set in step S306 or step S308, in a predetermined storage unit defined in an auxiliary storage device or the like. At this time, the effect evaluation unit 304 registers the data on the evaluation result in the predetermined storage unit in a form associated with the identification information of the target vehicle 10. This allows, for example, the developer of the vehicle 10 or a service person in charge to check the evaluation result of the effect of updating the software for each vehicle 10.

[0218] When the process of step S310 is completed, the analysis server 30 ends this flow chart.

[0219] Thus, in this example, the analysis server 30 evaluates the effect of updating the software of the target vehicle 10 by comparing the second vehicle data uploaded from the vehicle 10 before and after the software update.

[0220] This enables the analysis server 30 to evaluate the effect of updating the software of the vehicle 10 more easily (more efficiently).

[0221] [Another example of evaluation process for the effectiveness of software updates] Next, another example of the process of evaluating the effect of updating software of the vehicle 10 by the analysis server 30 will be described with reference to FIG.

[0222] FIG. 15 is a flowchart illustrating another example of the process of evaluating the effect of updating software of the vehicle 10 by the analysis server 30. In the example shown in FIG.

[0223] As shown in FIG. 15, in step S402, the effect evaluation unit 304 determines whether the effect of the current software update of the target vehicle 10 is to be evaluated by a virtual simulation based on a virtual vehicle model of the vehicle 10.

[0224] For example, whether or not the effect of the current software update of the target vehicle 10 is a subject for evaluation of the effect by a virtual simulation based on a virtual vehicle model of the vehicle 10 is specified in advance for each update data as described above, and is automatically determined according to the specified content. Also, whether or not the effect of the current software update of the target vehicle 10 is a subject for evaluation of the effect by a virtual simulation based on a virtual vehicle model of the vehicle 10 may be determined using table information or the like, based on the type of software, the content of the update, and characteristic items of the vehicle 10 that change due to the software update.

[0225] If the effect of the current software update of the target vehicle 10 is to be evaluated by a virtual simulation based on a virtual vehicle model of the vehicle 10, the effect evaluation unit 304 proceeds to step S404; otherwise, the effect evaluation unit 304 proceeds to step S404.

[0226] In step S404, the effect evaluation unit 304 causes the simulator unit 303 to perform a virtual simulation under the same conditions based on a virtual vehicle model that reflects the second vehicle data before and after the software update of the target vehicle 10.

[0227] When the process of step S404 is completed and the virtual simulation by the simulator unit 303 is completed, the analysis server 30 proceeds to step S406.

[0228] In step S406, the effect evaluation unit 304 compares the results of virtual simulations based on virtual vehicle models corresponding to the vehicle 10 before and after the software update, and evaluates the effect of the software update of the vehicle 10.

[0229] When the process of step S406 is completed, the analysis server 30 proceeds to step S410.

[0230] On the other hand, step S408 is the same as the process in step S302 in FIG. 14, and therefore a description thereof will be omitted.

[0231] When the process of step S408 is completed, the analysis server 30 proceeds to step S410.

[0232] Steps S410 to S416 are the same as the processes in steps S304 to S310 in FIG. 14, and therefore a description thereof will be omitted.

[0233] Thus, in this example, the analysis server 30 uses the virtual vehicle model to perform a virtual simulation under the same conditions based on the second vehicle data before and after the software update of the vehicle 10. Then, the analysis server 30 evaluates the effect of the software update of the vehicle 10 by comparing the results of the virtual simulations before and after the software update of the vehicle 10.

[0234] This allows the analysis server 30 to compare the results of virtual simulations performed under the same conditions, thereby enabling the effect of updating the software of the vehicle 10 to be evaluated with higher accuracy.

[0235] In addition, in this example, the analysis server 30 determines whether or not to evaluate the effect by virtual simulation depending on the type of software, the contents of the update, the types of characteristic items of the vehicle 10 that change due to the software update, etc.

[0236] This allows the analysis server 30 to strike a balance between the efficiency of the evaluation and the accuracy of the evaluation in accordance with the effect of the evaluation target.

[0237] [Effect] Next, the operation of the software update system 1 according to this embodiment will be described.

[0238] In this embodiment, the software update system 1 updates the software based on update data for the software used in the vehicle 10, which is transmitted to the vehicle 10 from a distribution server 20 communicatively connected to the vehicle 10. Specifically, the software update system 1 includes an update unit, an acquisition unit, and an evaluation unit. More specifically, the update unit (e.g., software update unit 194) updates the software of the vehicle 10 based on the update data. In addition, the acquisition unit (e.g., vehicle data acquisition unit 196) acquires predetermined data (e.g., second vehicle data) relating to the state of the vehicle 10 before and after the software of the vehicle 10 is updated by the update unit. Then, the evaluation unit (e.g., effect evaluation unit 304) evaluates the effect of the software update based on the predetermined data before and after the software update.

[0239] This allows the software update system 1 to evaluate the effect on the vehicle 10 when an update of software actually used in the vehicle 10 is performed.

[0240] In addition, in this embodiment, the software update system 1 includes a determination unit. Specifically, the determination unit (for example, the vehicle data acquisition unit 196) may determine whether or not the acquisition unit has acquired predetermined data before the software update. Then, the update unit may update the software when the determination unit determines that the predetermined data before the software update has been acquired.

[0241] This allows the software update system 1 to reliably acquire predetermined data regarding the state of the vehicle 10 before the software update. Therefore, the software update system 1 can reliably evaluate the effect of the software update.

[0242] In the present embodiment, the determination unit may determine whether a first predetermined number (eg, acquisition number N1) of predetermined data before the software update, which is two or more, has been acquired.

[0243] This allows the software update system 1 to use a plurality of predetermined data related to the state of the vehicle 10 before the software update. Therefore, the software update system 1 can evaluate the effect of the software update with higher accuracy.

[0244] In addition, in this embodiment, the above-mentioned first predetermined number may be variable depending on at least one of the content and the scale of the software update of the vehicle 10.

[0245] This allows the software update system 1 to reduce the number of pieces of predetermined data acquired to improve the efficiency of data acquisition, or to increase the number of pieces of predetermined data acquired to improve the accuracy of evaluation of the effect of the software update, depending on the content and scale of the software update. Therefore, the software update system 1 can achieve a balance between the efficiency of data acquisition and the improvement of the accuracy of evaluation of the effect of the software update, depending on the content and scale of the software update.

[0246] In the present embodiment, the software update system 1 may include a guidance unit. Specifically, after the software is updated by the update unit, the guidance unit (e.g., the route guidance unit 197) may guide the driver of the vehicle 10 on a driving route for acquiring predetermined data after the software is updated.

[0247] This allows the software update system 1 to, for example, guide the vehicle 10 to a route that is suitable for the driving conditions and environmental conditions for acquiring the predetermined data required to evaluate the effect of the software update. Also, the software update system 1 can, for example, guide the vehicle 10 to the same route as when acquiring the predetermined data before the software update. Therefore, the software update system 1 can more appropriately acquire the predetermined data related to the state of the vehicle 10 after the software update, and as a result, can evaluate the effect of the software update with higher accuracy.

[0248] In the present embodiment, the acquisition unit may acquire a second predetermined number of pieces of predetermined data after software updates (eg, acquisition count N2), which is two or more.

[0249] This allows the software update system 1 to use a plurality of predetermined data related to the state of the vehicle 10 after the software update. Therefore, the software update system 1 can evaluate the effect of the software update with higher accuracy.

[0250] In addition, in this embodiment, the above-mentioned second predetermined number may be variable depending on at least one of the content and the scale of the software update of the vehicle 10.

[0251] This allows the software update system 1 to reduce the number of pieces of predetermined data acquired to improve the efficiency of data acquisition, or to increase the number of pieces of predetermined data acquired to improve the accuracy of evaluation of the effect of the software update, depending on the content and scale of the software update. Therefore, the software update system 1 can achieve a balance between the efficiency of data acquisition and the improvement of the accuracy of evaluation of the effect of the software update, depending on the content and scale of the software update.

[0252] In addition, in this embodiment, the evaluation unit may evaluate the effect of the software update by comparing predetermined data before and after the software update of the vehicle 10.

[0253] This allows the software update system 1 to evaluate the effect of the software update.

[0254] In addition, in this embodiment, the evaluation unit may use a virtual model corresponding to the vehicle 10 to perform a virtual simulation based on specified data before and after the software update, and evaluate the effect by comparing the results.

[0255] This allows the software update system 1 to evaluate the effect of a software update with higher accuracy.

[0256] In addition, in this embodiment, the evaluation unit may determine whether or not to perform a virtual simulation when evaluating the effect of updating the software of the vehicle 10, depending on the content of the software update.

[0257] This allows the software update system 1 to improve the efficiency of evaluation without performing a virtual simulation, or to perform a virtual simulation and achieve a more accurate evaluation, depending on the content of the software update. Therefore, the software update system 1 can achieve a balance between the efficiency of evaluation and the high accuracy of evaluation, depending on the content of the software update.

[0258] In addition, in this embodiment, the evaluation unit may change the driving conditions of the vehicle 10 during the virtual simulation in accordance with the contents of the software update.

[0259] This allows the software update system 1 to perform a virtual simulation in accordance with the driving conditions that are affected by the software update, and therefore the software update system 1 can evaluate the effect of the software update with higher accuracy.

[0260] In addition, in this embodiment, the evaluation unit may evaluate the effect of the software update by comparing the change in the characteristics of the vehicle 10 obtained by comparing specified data before and after the software update with the change in the characteristics of the vehicle 10 obtained by comparing the results of a virtual simulation based on each of the specified data before and after the software update.

[0261] This allows the software update system 1 to evaluate the effect of the software update using both the comparison result between the predetermined data in the actual vehicle 10 and the comparison result between the results of the virtual simulation. Therefore, the software update system 1 can evaluate the effect of the software update with higher accuracy.

[0262] In addition, in this embodiment, the virtual vehicle model may be a generic model corresponding to the vehicle 10.

[0263] This allows the software update system 1 to predict the effect of a software update, for example, by using a virtual vehicle model (general-purpose model) common to multiple vehicles 10 of the same model. Therefore, the software update system 1 can reduce the effort and time required to prepare a virtual vehicle model for evaluating the effect of a software update, for example, and more efficiently evaluate the effect of a software update.

[0264] In addition, in this embodiment, the virtual vehicle model may be a dedicated model corresponding to the vehicle 10.

[0265] This allows the software update system 1 to evaluate the effect of a software update using a dedicated virtual vehicle model for each vehicle 10. Therefore, the software update system 1 can reflect the unique circumstances of each vehicle 10, and as a result, can evaluate the effect of a software update with higher accuracy.

[0266] In addition, in this embodiment, the software update system 1 may include a generation unit that generates a virtual vehicle model. Specifically, the generation unit (e.g., the virtual vehicle model acquisition unit 301) may update the virtual vehicle model in accordance with at least one of changes over time of the vehicle 10, the use conditions of the vehicle 10, and changes in the components of the vehicle 10.

[0267] This enables the software update system 1 to specifically reflect the unique circumstances of the vehicle 10, such as changes in the vehicle 10 over time, the conditions of use of the vehicle 10, and changes in the components of the vehicle 10, in a virtual vehicle model dedicated to the vehicle 10.

[0268] In addition, in this embodiment, the generation unit may obtain data (e.g., first vehicle data) representing the actual state of the vehicle 10, and generate and update a digital twin of the vehicle 10 as a virtual vehicle model.

[0269] This allows the software update system 1 to evaluate the effect of a software update using a virtual vehicle model (digital twin) that always reflects the latest state of the vehicle 10. Therefore, the software update system 1 can evaluate the effect obtained by a software update with higher accuracy.

[0270] Although the embodiments have been described in detail above, the present disclosure is not limited to such specific embodiments, and various modifications and improvements are possible within the scope of the gist described in the claims. [Explanation of symbols]

[0271] 1 Software update system (information processing system) 10 Vehicles 11. Communications equipment 12 Gateway ECU 13 ECU 15 Sensors 16 Navigation devices 17 Input Devices 18 Display device 19 Central ECU (information processing unit) 19A Auxiliary storage device 19B Memory Device 19C CPU 19D Interface Device 19E Recording media 20 Distribution server (information processing device) 21 External Interface 21A Recording Media 22 Auxiliary storage 23 Memory Device 24 CPU 25 High-speed computing device 26 Communication Interface 27 Input Devices 28 Display device 30 Analysis server (information processing device) 40 User terminal 121 Communications Department 122 Storage section 131 Storage section 191 Vehicle data transmission unit 192 Download processing section 193 Memory section 194 Software Update Department (Update Department) 195 Memory section 196 Vehicle data acquisition unit (acquisition unit, judgment unit) 197 Route Guidance Department (Guidance Department) 198 Memory section 199 Vehicle data transmission unit 201 Notification Department (Update Department) 202 Distribution Department 301 Virtual vehicle model acquisition unit (generation unit) 302 Virtual vehicle model storage unit 303 Simulator Section 304 Effectiveness Evaluation Department (Evaluation Department) 401 Notification Department

Claims

1. An information processing system for updating software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, comprising: an acquisition unit that acquires predetermined data relating to the state of the vehicle before and after the software update; a determination unit that determines whether the predetermined data before the software update has been acquired by the acquisition unit; an update unit that updates the software based on the update data when the determination unit determines that the predetermined data before the software update has been acquired; a guidance unit that, after the software is updated by the update unit, guides a driver of the vehicle along a driving route for acquiring the predetermined data after the software is updated; and an evaluation unit that evaluates an effect of the software update based on the predetermined data before and after the software update. Information processing system.

2. An information processing system for updating software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, comprising: an update unit that updates the software based on the update data; an acquisition unit that acquires predetermined data relating to the state of the vehicle before and after the software is updated by the update unit; an evaluation unit that performs a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and evaluates an effect of the software update by comparing the results of the virtual simulation, the evaluation unit determines whether or not to perform the virtual simulation when evaluating the effect depending on the content of the software update. Information processing system.

3. An information processing system for updating software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, comprising: an update unit that updates the software based on the update data; an acquisition unit that acquires predetermined data relating to the state of the vehicle before and after the software is updated by the update unit; an evaluation unit that performs a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and evaluates an effect of the software update by comparing the results of the virtual simulation, The evaluation unit changes a driving condition of the vehicle during the virtual simulation according to the content of the software update. Information processing system.

4. An information processing system for updating software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, comprising: an update unit that updates the software based on the update data; an acquisition unit that acquires predetermined data relating to the state of the vehicle before and after the software is updated by the update unit; an evaluation unit that performs a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and evaluates an effect of the software update by comparing the results of the virtual simulation, the evaluation unit evaluates the effect by comparing a change in characteristics of the vehicle obtained by comparing the specified data before and after the software update with a change in characteristics of the vehicle obtained by comparing results of the virtual simulation based on each of the specified data before and after the software update. Information processing system.

5. An information processing system for updating software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, comprising: an update unit that updates the software based on the update data; an acquisition unit that acquires predetermined data relating to the state of the vehicle before and after the software is updated by the update unit; A generation unit that generates a virtual model corresponding to the vehicle; an evaluation unit that performs a virtual simulation using the virtual model based on the predetermined data before and after the software update, and compares the results to evaluate an effect of the software update; the virtual model is a dedicated model corresponding to the vehicle; The generation unit updates the virtual model in accordance with at least one of a change over time of the vehicle, a use condition of the vehicle, and a change in a component of the vehicle. Information processing system.

6. An information processing method executed by an information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, comprising: an acquisition step of acquiring predetermined data regarding the state of the vehicle before and after the software update; a determination step of determining whether or not the predetermined data before the software update has been acquired in the acquisition step; an update step of updating the software based on the update data when it is determined in the determination step that the predetermined data before the update of the software has been acquired; a guidance step of guiding a driver of the vehicle to a driving route for acquiring the predetermined data after the software is updated in the update step; and evaluating an effect of the software update based on the predetermined data before and after the software update. Information processing methods.

7. 1. An information processing method executed by an information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, the information processing method comprising: an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; and an evaluation step of performing a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and comparing the results of the virtual simulation to evaluate an effect of the software update, In the evaluation step, it is determined whether or not the virtual simulation is performed when evaluating the effect of the software update, depending on the content of the software update. Information processing methods.

8. An information processing method executed by an information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, comprising: an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; and an evaluation step of performing a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and comparing the results of the virtual simulation to evaluate an effect of the software update, In the evaluation step, a driving condition of the vehicle during the virtual simulation is changed according to the content of the software update. Information processing methods.

9. An information processing method executed by an information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, comprising: an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; and an evaluation step of performing a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and comparing the results of the virtual simulation to evaluate an effect of the software update, In the evaluation step, the effect is evaluated by comparing a change in characteristics of the vehicle obtained by comparing the predetermined data before and after the software update with a change in characteristics of the vehicle obtained by comparing results of the virtual simulation based on each of the predetermined data before and after the software update. Information processing methods.

10. An information processing method executed by an information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device communicatively connected to the vehicle, comprising: an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; A generating step of generating a virtual model corresponding to the vehicle; and an evaluation step of performing a virtual simulation using the virtual model based on the predetermined data before and after the software update, and comparing the results to evaluate an effect of the software update, the virtual model is a dedicated model corresponding to the vehicle; In the generating step, the virtual model is updated in accordance with at least one of a change over time of the vehicle, a use condition of the vehicle, and a change in a component of the vehicle. Information processing methods.

11. An information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device that is communicatively connected to the vehicle, an acquisition step of acquiring predetermined data regarding the state of the vehicle before and after the software update; a determination step of determining whether or not the predetermined data before the software update has been acquired in the acquisition step; an update step of updating the software based on the update data when it is determined in the determination step that the predetermined data before the update of the software has been acquired; a guidance step of guiding a driver of the vehicle to a driving route for acquiring the predetermined data after the software is updated in the update step; and an evaluation step of evaluating an effect of the software update based on the predetermined data before and after the software update. program.

12. An information processing device that updates software used in the vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device that is communicatively connected to the vehicle, an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; an evaluation step of performing a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and evaluating an effect of the software update by comparing the results; In the evaluation step, it is determined whether or not the virtual simulation is performed when evaluating the effect of the software update, depending on the content of the software update. program.

13. An information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device that is communicatively connected to the vehicle, an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; an evaluation step of performing a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and evaluating an effect of the software update by comparing the results; In the evaluation step, a driving condition of the vehicle during the virtual simulation is changed according to the content of the software update. program.

14. An information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device that is communicatively connected to the vehicle, an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; an evaluation step of performing a virtual simulation based on the predetermined data before and after the software update using a virtual model corresponding to the vehicle, and evaluating an effect of the software update by comparing the results; In the evaluation step, the effect is evaluated by comparing a change in characteristics of the vehicle obtained by comparing the predetermined data before and after the software update with a change in characteristics of the vehicle obtained by comparing results of the virtual simulation based on each of the predetermined data before and after the software update. program.

15. An information processing device that updates software used in a vehicle based on update data for the software, the update data being transmitted to the vehicle from an external device that is communicatively connected to the vehicle, an updating step of updating the software based on the update data; an acquisition step of acquiring predetermined data relating to the state of the vehicle before and after the software is updated in the update step; A generating step of generating a virtual model corresponding to the vehicle; an evaluation step of performing a virtual simulation using the virtual model based on the predetermined data before and after the software update, and comparing the results to evaluate an effect of the software update; the virtual model is a dedicated model corresponding to the vehicle; In the generating step, the virtual model is updated in accordance with at least one of a change over time of the vehicle, a use condition of the vehicle, and a change in a component of the vehicle. program.

Images