VEHICLE CONTROL SYSTEM AND VEHICLE CONTROL METHOD

Abstract

A vehicle control system includes a plurality of devices, a first device included in the devices including: a storage configured to store consistency information including a permitted combination of versions of software installed on each of one or more devices in association with each of the control functions; a determination unit configured to determine whether the consistency information consistent with versions of software installed on a part of the devices exists when consistency does not exist in the versions of all software installed on each of the devices; and a performance control unit configured to permit performance of a part of control functions associated with the consistency information consistent with the versions of software installed on the part of the devices when the consistency information consistent with the versions of software installed on the part of the devices exists.

Claims

1. A master device of a plurality of devices mounted on a vehicle, the master device comprising: a storage configured to store consistency information including a permitted combination of two or more devices of the plurality of devices and versions of software installed on each of the two or more devices of the plurality of devices; and a processor configured to: acquire versions of software installed on the plurality of devices; determine whether the versions of the software installed on each of the two or more devices of the plurality of devices are compatible by collating the versions of the software acquired from the plurality of devices with the consistency information; and permit performance of control functions obtained by the two or more devices of the plurality of devices in response to determining that the versions of the software installed on the two or more devices of the plurality of devices are compatible.

2. The vehicle control system according to claim 1, wherein the processor is configured to perform determination processing every time when a power supply of the vehicle is turned on.

3. The vehicle control system according to claim 1, wherein the permitted combination of the versions of the software of the two or more devices of the plurality of devices is a combination of versions of the software that is permitted to be performed simultaneously.

4. A vehicle control method of a master device of a plurality of devices mounted on a vehicle, the method comprising: storing, by a computer of the master device, consistency information including a permitted combination of versions of software installed on each of the two or more devices of the plurality of devices; acquiring, by the computer, the versions of the software installed on the plurality of devices; determining, by the computer, whether the versions of the software installed on the two or more devices are compatible by collating the versions of the software acquired from the plurality of devices with the consistency information; and permitting, by the computer, performance of control functions obtained by the two or more devices of the plurality of devices in response to determining that the versions of the software installed on the two or more devices of the plurality of devices are compatible.

5. An over-the-air master device connected to a plurality of electronic control units mounted on a vehicle, the over-the-air master device comprising: a storage configured to store consistency information including a permitted combination of two or more electronic control units of the plurality of electronic control units and versions of software installed on each of the two or more electronic control units of the plurality of electronic control units; and a processor configured to: acquire versions of software installed on the plurality of electronic control units; determine whether the versions of the software installed on each of the two or more electronic control units of the plurality of electronic control units are compatible by collating the versions of the software acquired from the plurality of electronic control units with the consistency information; and permit performance of control functions obtained by the two or more electronic control units of the plurality of electronic control units in response to determining that the versions of the software installed on the two or more electronic control units of the plurality of electronic control units are compatible.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Features, advantages, and technical and industrial significance of exemplary embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like numerals denote like elements, and wherein:

[0016] FIG. 1 is a block diagram showing a schematic configuration of a vehicle control system according to an embodiment;

[0017] FIG. 2 is a functional block diagram of the vehicle control system shown in FIG. 1;

[0018] FIG. 3 is a diagram for explaining a consistency determination method of versions of software in an embodiment; and

[0019] FIG. 4 is a flowchart exemplarily showing control processing performed by a representative in-vehicle device shown in FIG. 1.

DETAILED DESCRIPTION OF EMBODIMENTS

[0020] Even when versions of software of one or some of in-vehicle devices composing a vehicle control system are not consistent with a permitted version, the present disclosure enables to provide control functions that can be executed by one or some of in-vehicle devices holding software that is consistent with the permitted version. Even when not all the control functions of the vehicle control system can be provided, one or some of control functions are allowed to be provided, and thereby, convenience of a user is improved.

EMBODIMENT

[0021] Configuration

[0022] FIG. 1 is a block diagram showing a schematic configuration of a vehicle control system according to an embodiment.

[0023] A vehicle control system 100 is a system which is composed of in-vehicle devices A to D which can communicate with one another and which realizes predetermined vehicle control by combining control functions of the in-vehicle devices A to D. While in the example of FIG. 1, the vehicle control system 100 is composed of the four in-vehicle devices A to D, the number of in-vehicle devices composing the vehicle control system 100 is not limited to four. Examples of the predetermined vehicle control realized by the vehicle control system 100 include automated driving. The in-vehicle devices A to D correspond to ECUs which control vehicle travelling such as acceleration, deceleration and steering, and a ECU which combines those ECUs controlling the vehicle travelling to perform travelling assistance. Notably, in the following description, a specific in-vehicle device A which is one of the plurality of in-vehicle devices A to D composing the vehicle control system is referred to as representative in-vehicle device A.

[0024] FIG. 2 is a functional block diagram of the vehicle control system shown in FIG. 1. FIG. 3 is a diagram for explaining a consistency determination method of versions of software according to an embodiment.

[0025] Representative in-Vehicle Device A

[0026] The representative in-vehicle device A is one of the in-vehicle devices providing the control functions of the vehicle control system 100, and functions as a master device in a consistency examination process for versions of software of the in-vehicle devices A to D. The representative in-vehicle device A examines consistency in the versions of software of all the in-vehicle devices A to D composing the vehicle control system 100 with turn-on of a power supply of a vehicle being as a trigger. The representative in-vehicle device A includes a software storage 10, a first consistency information storage 11, a second consistency information storage 12, a version acquisition unit 13, a first determination unit 21, a second determination unit 22, a performance control unit 23 and a transmission-reception unit 24.

[0027] The software storage 10 stores software for operating the representative in-vehicle device A. The representative in-vehicle device A executes the software stored in the software storage 10, and thereby, realizes a predetermined function for controlling operation of the vehicle.

[0028] The first consistency information storage 11 stores a first consistency table in which a combination of versions of software of all the in-vehicle devices A to D composing the vehicle control system 100 is defined. The combination of versions of software of the in-vehicle devices A to D which combination is defined in the consistency table is a combination with which the vehicle control system 100 is confirmed to normally operate and which includes versions permitted to be simultaneously performed. As shown in FIG. 3, for example, the first consistency table can include a system number for specifying the vehicle control system 100, and versions of software of the in-vehicle devices A to D. For the system number, an identifier for specifying the vehicle control system 100 may be used, or a version of the vehicle control system 100 may be used. Moreover, in the example of the first consistency table in FIG. 3, a single version is defined as the version of each in-vehicle device. Instead, a range of versions of each in-vehicle device which versions can be combined may be defined. Moreover, in the first consistency table, a plurality of sets of combinations of versions (or ranges of versions) may be defined which combination of versions (or ranges of versions) is permitted to be simultaneously performed. When one in-vehicle device holds a plurality of pieces of software, a permitted version for each of the plurality of pieces of software is defined in the first consistency table. The first consistency table is used as first consistency information with which the first determination unit 21 mentioned later determines whether or not consistency exists in versions of software of the in-vehicle devices A to D.

[0029] The second consistency information storage 12 stores a second consistency table for examining consistency of a version of software of an in-vehicle device for each control function of the vehicle control system 100. As shown in FIG. 3, in the second consistency table, a control function composing the vehicle control system 100 is associated with one or more in-vehicle devices used for performing the control function and a combination of versions of software of the one or more in-vehicle devices. When one in-vehicle device holds a plurality of pieces of software, a permitted version of each of the plurality of pieces of software is also defined in the second consistency table. In the example presented in the second consistency table shown in FIG. 3, there are a control function_1, a control function_2 and a control function_3 as control functions which can be partially provided out of the plurality of control functions composing the vehicle control by vehicle control system 100. The second consistency table is provided for each of those control functions. For example, there is defined in the table for the control function_1 that the control function_1 is performed by a combination of the in-vehicle devices A and B, and that versions of software of the in-vehicle devices A and B needed for performing the control function_1 are respectively defined as 12345 and 23456. When the vehicle control provided by all the control functions of the vehicle control system 100 is automated driving, examples of the control function_1, control function_2 and control function_3 include a following travelling control function, a lane keeping support function, a lane deviation alarm function and a brake support function. The second consistency tables are used as second consistency information with which the second determination unit 22 mentioned later determines whether or not there is a control function that can be provided using one or some of the in-vehicle devices A to D.

[0030] The version acquisition unit 13 acquires the version of software of each of the other in-vehicle devices B to D through communication. When there is an in-vehicle device holding a plurality of pieces of software among the in-vehicle devices B to D, the version acquisition unit 13 acquires all the versions of software held in the in-vehicle device.

[0031] The first determination unit 21 determines whether or not consistency exists in the versions of software of all the in-vehicle devices A to D composing the vehicle control system 100. The determination is performed by the first determination unit 21 collating the version of software stored in the software storage 10 of the representative in-vehicle device A and the versions of software acquired from the other in-vehicle devices B to D by the version acquisition unit 13 individually with the first consistency table stored in the first consistency information storage 11.

[0032] Specific examples are described. When the versions for the in-vehicle devices acquired by the version acquisition unit 13 are as in version acquisition example 1 shown in FIG. 3, the first determination unit 21 collates the acquired versions with the first consistency table shown in FIG. 3, and as a result, determines that consistency exists in the versions of software of all the in-vehicle devices A to D. On the contrary, when the versions for the in-vehicle devices acquired by the version acquisition unit 13 are as in version acquisition example 2 shown in FIG. 3, the first determination unit 21 collates the acquired versions with the first consistency table shown in FIG. 3, and as a result, determines that consistency does not exist in the versions of software of all the in-vehicle devices A to D since the version for the in-vehicle device B is not consistent with the first consistency table.

[0033] The second determination unit 22 determines whether or not there is, among the second consistency tables stored in the second consistency information storage 12, one that is consistent with a combination of versions of software of one or some of the in-vehicle devices composing the vehicle control system 100. The determination is performed by the second determination unit 22 collating the version of software stored in the software storage 10 of the representative in-vehicle device A and the versions of software acquired from the other in-vehicle devices B to D by the version acquisition unit 13 with each of the second consistency tables stored in the second consistency information storage 12. Notably, the determination by the second determination unit 22 is processing performed when the first determination unit 21 determines that consistency does not exist in the versions of software of all the in-vehicle devices A to D composing the vehicle control system 100.

[0034] Specific examples are described. When the versions for the in-vehicle devices acquired by the version acquisition unit 13 are as in version acquisition example 2 shown in FIG. 3, as mentioned above, the first determination unit 21 determines that consistency does not exist in the versions of software of all the in-vehicle devices A to D composing the vehicle control system 100. In this case, the second determination unit 22 collates the versions of software of the in-vehicle devices with the combination of the versions of software defined in each of the second consistency tables shown in FIG. 3. In version acquisition example 2 shown in FIG. 3, although the versions of software of the in-vehicle devices A, C and D are consistent with the permitted versions, the version of software of the in-vehicle device B is not consistent with the permitted version. The second determination unit 22 determines that there are the tables for the control function_2 and the control function_3 as second consistency tables that are consistent with the versions of software of one or some of the in-vehicle devices composing the vehicle control system.

[0035] The performance control unit 23 controls performance of the control functions of the vehicle control system 100 based on the determination results of the first determination unit 21 and the second determination unit 22. When the first determination unit 21 determines that consistency exists in the versions of software of all the in-vehicle devices A to D composing the vehicle control system 100, the performance control unit 23 permits performance of the vehicle control of the vehicle control system 100 which vehicle control can be performed using all the in-vehicle devices A to D. When the second determination unit 22 determines that there exists a second consistency table consistent with versions of software of one or some of the in-vehicle devices composing the vehicle control system the performance control unit 23 permits performance of only the control function associated with the second consistency table that is determined to exist. When the second determination unit 22 determines that there does not exists a second consistency table consistent with versions of software of one or some of the in-vehicle devices composing the vehicle control system, the performance control unit 23 prohibits performance of all the control functions of the vehicle control system 100.

[0036] The transmission-reception unit 24 transmits and receives various kinds of information and instructions to/from the in-vehicle devices B to D.

[0037] In-Vehicle Devices B to D

[0038] Each of the in-vehicle devices B to D includes a software storage 30 and a transmission-reception unit 31. The software storage 30 stores software for operating each of the in-vehicle devices B to D. Each of the in-vehicle devices B to D executes the software stored in the software storage 30, and thereby, realizes a predetermined function for controlling operation of the vehicle. The transmission-reception unit 31 transmits and receives various kinds of information and instructions to/from the other in-vehicle devices.

[0039] Control Processing

[0040] Hereafter, with reference to FIG. 2 and FIG. 4, control processing performed by the representative in-vehicle device A is described.

[0041] FIG. 4 is a flowchart exemplarily showing control processing performed by the representative in-vehicle device shown in FIG. 1.

[0042] Step S1: the version acquisition unit 13 acquires the versions of software of the other in-vehicle devices B to D. After that, the process moves to step S2.

[0043] Step S2: the first determination unit 21 collates the version of software of the representative in-vehicle device A and the versions of software acquired from the other in-vehicle devices B to D with the first consistency table stored in the first consistency information storage 11, and determines whether or not consistency exists in the versions of software of the in-vehicle devices A to D. When the determination in step S2 is YES, the process moves to step S3, and in the other case, the process moves to step S4.

[0044] Step S3: the performance control unit 23 permits performance of the vehicle control using the in-vehicle devices A to D combined. After that, the process is ended.

[0045] Step S4: the second determination unit 22 collates the version of software of the representative in-vehicle device A and the versions of software acquired from the other in-vehicle devices B to D with the second consistency tables stored in the second consistency information storage 12, and determines whether or not a second consistency table consistent with a combination of versions of software of one or some of the in-vehicle devices A to D exists. Notably, since with the determination in step S2, an in-vehicle device having software in a version not consistent with the first consistency table can be specified, the determination processing in step S4 may be performed only using the versions of software of the in-vehicle devices which versions are determined to be consistent with the first consistency table in step S2. When the determination in step S4 is YES, the process moves to step S5, and in the other case, the process moves to step S6.

[0046] Step S5: the performance control unit 23 permits performance of control functions associated with the second consistency table determined to exist by the second determination unit in step S4, and prohibits performance of the other control functions of the vehicle control system 100. After that, the process is ended.

[0047] Step S6: the performance control unit 23 prohibits performance of all the control functions of the vehicle control system 100. After that, the process is ended.

[0048] The aforementioned control processing in FIG. 4 may be realized by a dedicated circuit, or may be realized, for example, by causing a computer such as an ECU having a processor, a ROM, a RAM, a hard disk drive and the like to perform processes in the individual steps. When a computer such as an ECU is caused to perform such control processes in FIG. 4, a program described such that these control processes can be performed may be prestored in a storage apparatus such a ROM and a hard disk drive, and a processor included in the computer may be caused to read the program from the storage apparatus and to execute it.

[0049] Effects and Others

[0050] As described above, with the vehicle control system 100 according to the present embodiment, even in the case where versions of software of one or some of the in-vehicle devices A to D composing the vehicle control system 100 are not consistent with permitted versions, when control functions that can be performed by one or some of in-vehicle devices that hold software in permitted versions exist, performance of the control function is permitted. Accordingly, even when one or some of in-vehicle devices are restricted to be used as in cases where repair of an in-vehicle device or update of software of an in-vehicle device is needed, one or some of functions of the vehicle control system 100 can be provided. Hence, convenience of a user can be improved.

[0051] Notably, the determination processing of the first determination unit 21 and the second determination unit 22 may be performed every time a power supply of a vehicle is turned on. By examining that consistency exists in the versions of software of the in-vehicle devices A to D every time the power supply of the vehicle is turned on, there can be reduced a possibility that unexpected vehicle control is performed due to inconsistency in the versions of software of the in-vehicle devices A to D.

[0052] The present disclosure can be used for a vehicle control system which realizes a predetermined vehicle control function with a combination of a plurality of in-vehicle devices.