In-vehicle information processing device, information processing system, and information processing method

Abstract

To provide an in-vehicle information processing device, an information processing system, and an information processing method that can be expected to suppress the occurrence of problems and the like caused by adding a new in-vehicle communication device to a vehicle network.SOLUTION: An in-vehicle information processing device according to this embodiment includes a detection unit that detects connection of an in-vehicle communication device to a network within a vehicle, a creation unit that creates a routing map for determining a relay destination of data transmitted and received over the network when connection of the in-vehicle communication device is detected, a verification unit that verifies communication of the network according to the created routing map by simulation, and an update unit that updates the routing map when a positive verification result is obtained.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present disclosure relates to an in-vehicle information processing apparatus, an information processing system, and an information processing method for performing processing related to communication within a vehicle.

Background Art

[0002] In Patent Document 1, an in-vehicle device acquires a service ID related to an added function and transmits it to a server. The server acquires service information of the function corresponding to the service ID, determines a change location of a routing table based on the service information of a plurality of functions including the acquired service information, and executes a change of the routing table. An information management system has been proposed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] For example, for the purpose of adding functions to a vehicle, a new in-vehicle communication device may be additionally connected to a network related to vehicle communication. An in-vehicle relay device that relays data transmission and reception between in-vehicle communication devices in this network needs to update a routing map (routing table) in order to determine a relay destination of data related to the new in-vehicle communication device. After updating the routing map and starting the relay of data related to the new in-vehicle communication device by the in-vehicle communication device, there may be an increase in communication volume or communication delay in the vehicle network. In recent years, since the types of added functions or added in-vehicle communication devices are diverse, it is difficult to verify in advance whether an increase in communication volume or communication delay will occur due to these additions.

[0005] The present disclosure has been made in view of such circumstances, and an object thereof is to provide an in-vehicle information processing apparatus, an information processing system, and an information processing method capable of suppressing the occurrence of problems such as by adding a new in-vehicle communication device to a vehicle network.

Means for Solving the Problems

[0006] The in-vehicle information processing apparatus according to this aspect includes a detection unit that detects the connection of an in-vehicle communication device to a network in a vehicle, a creation unit that creates a routing map for determining a relay destination of data transmitted and received in the network when the connection of the in-vehicle communication device is detected, a verification unit that verifies the communication of the network by simulation using the created routing map, and an update unit that updates the routing map when a positive verification result is obtained.

[0007] The present application can be realized not only as an apparatus including such a characteristic processing unit, but also as a method including such a characteristic processing as steps, or as a computer program for causing a computer to execute such steps. It can be realized as a semiconductor integrated circuit that realizes part or all of these apparatuses, or as other apparatuses or systems including these apparatuses.

Effects of the Invention

[0008] According to the above, it can be expected to suppress the occurrence of problems such as by adding a new in-vehicle communication device to a vehicle network.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Embodiments for Carrying Out the Invention

[0010] [Description of Embodiments of the Present Disclosure] First, the embodiments of the present disclosure will be listed and described. At least a part of the embodiments described below may be arbitrarily combined.

[0011] (1) The in-vehicle information processing apparatus according to this aspect includes a detection unit that detects the connection of an in-vehicle communication device to a network in a vehicle, a creation unit that creates a routing map for determining a relay destination of data transmitted and received in the network when the connection of the in-vehicle communication device is detected, a verification unit that verifies the communication of the network by simulation using the created routing map, and an update unit that updates the routing map when a positive verification result is obtained.

[0012] In this aspect, an in-vehicle information processing device updates a routing map for determining a data relay destination in a network within a vehicle. When the in-vehicle information processing device detects a connection of a new in-vehicle communication device to the network, it creates a new routing map including information for relaying data from this in-vehicle communication device or data to this in-vehicle communication device. The in-vehicle information processing device verifies the communication of the network when the created routing map is applied by simulation. When a positive verification result is obtained by the simulation, the in-vehicle information processing device updates the old routing map to the newly created routing map. By performing verification in the simulation before updating the routing map, it can be expected to suppress the occurrence of problems such as malfunctions after the update of the routing map.

[0013] (2) Preferably, the verification unit verifies, by the simulation, whether a load factor or communication delay in the network when the in-vehicle communication device is added satisfies a predetermined condition.

[0014] In this aspect, the in-vehicle information processing device verifies by simulation whether a load factor or communication delay of the network when a new in-vehicle information processing device is added satisfies a predetermined condition. The predetermined condition can be, for example, not exceeding a load factor or communication delay at which there is a risk of malfunctions in the functions of the vehicle, etc. The predetermined condition can be determined in advance, for example, by the designer or administrator of the information processing system according to this embodiment. Thereby, it can be expected that the in-vehicle information processing device suppresses the occurrence of problems such as an increase in the load factor or communication delay after the update of the routing map.

[0015] (3) An acquisition unit that acquires information regarding the in-vehicle communication device connected to the network, a transmission unit that transmits the acquired information to an off-vehicle device, and a reception unit that receives update information for updating the routing map transmitted by the off-vehicle device in response to the transmission of the information. Further provided, it is preferable that the creation unit creates the routing map based on the received update information.

[0016] In this aspect, the in-vehicle information processing device acquires information (such as device identification information, etc.) regarding the in-vehicle communication device connected to the network and transmits the acquired information to the off-vehicle device. The off-vehicle device stores various information regarding devices or functions that can be added to the vehicle in a database. The off-vehicle device acquires, from the database, update information for updating the routing map regarding the newly connected in-vehicle communication device based on the information received from the in-vehicle information processing device and transmits it to the in-vehicle information processing device. The update information includes, for example, information to be added to the routing map in order to correctly relay data from or to the in-vehicle communication device. The in-vehicle information processing device that has received the update information creates a new routing map based on this update information. Thereby, even when various in-vehicle communication devices can be connected to the vehicle's network, the in-vehicle information processing device can be expected to create an appropriate routing map.

[0017] (4) When a negative verification result is obtained, it is preferable that the update unit updates the routing map and performs thinning of relaying according to the priority of the data.

[0018] In this aspect, when a negative verification result is obtained through simulation, the in-vehicle information processing device updates the old routing map with the newly created routing map and performs relay thinning according to the priority of the data. For example, when the priority of the data to be relayed is lower than a predetermined threshold, the in-vehicle information processing device can perform thinning by discarding the data without relaying it with a predetermined probability. Thereby, when there is a possibility that a problem or the like may occur by updating the routing map, the in-vehicle information processing device can be expected to suppress the occurrence of problems or the like by thinning the relay and reducing the communication volume.

[0019] (5) A model generation unit that generates a model of the network, a scenario generation unit that generates a scenario for the simulation, and a scenario execution unit that performs input / output of data to the model according to the scenario, and it is preferable that the verification unit performs verification based on the data input / output to the model and the internal state of the model.

[0020] In this aspect, the information processing device generates a model of the network to be the subject of the simulation and a scenario of the simulation, and performs the simulation by performing input / output of data to the model according to the scenario. The information processing device performs verification based on the input / output data to the model and the internal state of the model. Thereby, it can be expected that the information processing device widely verifies the behavior of the network with a newly added in-vehicle communication device through simulations using various scenarios.

[0021] (6) It is preferable to include a configuration database that stores the configuration information of the in-vehicle communication device and the communication line mounted on the vehicle, and the model generation unit generates the model based on the configuration information stored in the configuration database and the configuration information of the in-vehicle communication device connected to the network.

[0022] In this aspect, the information processing device includes a configuration database that stores the configuration of an in-vehicle communication device mounted on a vehicle and components such as a communication line. Based on the information stored in this configuration database and the configuration information of an in-vehicle communication device newly connected to the vehicle's network, for example, by adding the model of the added in-vehicle communication device to a model of an existing network configuration, it is expected that a model used for verification simulation can be generated.

[0023] (7) It is preferable to include an operation database that stores the correspondence between the operations of the vehicle and the events occurring in each operation, and for the scenario generation unit to generate the scenario that defines the events occurring in chronological order based on the information stored in the operation database and the configuration information of the in-vehicle communication device connected to the network.

[0024] In this aspect, the information processing device includes an operation database that stores the correspondence between the operations of the vehicle and the events occurring in each operation. The information processing device generates a scenario that defines the events occurring in chronological order based on the information stored in the operation database and the configuration information of an in-vehicle communication device newly connected to the vehicle's network. As a result, it is expected that the information processing device can perform simulations corresponding to various operations of the vehicle.

[0025] (8) The scenario defines the events occurring in chronological order in the network. The scenario execution unit generates the data to be input to the model based on the chronological events defined in the scenario, inputs the generated data to the model, acquires the data output by the model in response to the input of the data and the internal state of the model when the data is output, and preferably stores the acquired data and the internal state.

[0026] In this aspect, the information processing apparatus generates data to be input to the model based on the time-series events defined in the scenario, inputs the generated data to the model, acquires the data output by the model and the internal state of the model, and stores these acquired pieces of information. Thereby, it can be expected that the information processing apparatus performs a simulation of the vehicle network using the model and the scenario.

[0027] (9) Based on the data and the internal state stored by the scenario execution unit, the verification unit calculates the load rate or communication delay related to the communication of the network, and determines whether the simulation result is positive according to whether the calculated load rate or communication delay satisfies a predetermined criterion. This is preferable.

[0028] In this aspect, the information processing apparatus calculates the load rate or communication delay related to the communication of the network based on the output data of the model and the information on the internal state stored as a result of the simulation. The information processing apparatus can determine whether the simulation result is positive according to whether the calculated load rate or communication delay satisfies a predetermined criterion.

[0029] (10) The information processing system according to this aspect includes an in-vehicle relay device having a relay unit that relays the transmission and reception of data between a plurality of communication lines constituting the in-vehicle network, a detection unit that detects the connection of the in-vehicle communication device to the network in the vehicle, a creation unit that creates a routing map for determining the data relay destination by the in-vehicle relay device that relays the transmission and reception of data in the network when the connection of the in-vehicle communication device is detected, a verification unit that verifies the communication of the network by the created routing map through simulation, and an update unit that updates the routing map of the in-vehicle relay device with the created routing map when a positive verification result is obtained.

[0030] In this aspect, similar to aspect (1), it can be expected to suppress the occurrence of problems or the like after the update of the routing map.

[0031] (11) The information processing method according to this aspect is such that an in-vehicle information processing device detects the connection of an in-vehicle communication device to a network within a vehicle, and when the connection of the in-vehicle communication device is detected, creates a routing map for determining a relay destination of data transmitted and received on the network, verifies the communication of the network according to the created routing map by simulation, and updates the routing map when a positive verification result is obtained.

[0032] In this aspect, as in aspect (1), it can be expected to suppress the occurrence of problems or the like after the update of the routing map.

[0033] [Details of Embodiments of the Present Disclosure] A specific example of an information processing system according to an embodiment of the present disclosure will be described below with reference to the drawings. The present disclosure is not limited to these examples, but is indicated by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0034] [System Configuration] FIG. 1 is a schematic diagram for explaining a configuration example of an information processing system according to the present embodiment. The information processing system according to the present embodiment includes a plurality of devices such as an integrated ECU (Electronic Control Unit) 10, a meter ECU 51, a brake ECU 52, an expansion IF (Interface) 53, and an out-vehicle communication device 54 mounted on a vehicle 1. These plurality of devices are connected via a plurality of communication lines 71 to 74 arranged within the vehicle 1, and constitute an in-vehicle network capable of transmitting and receiving data to and from each other. In the illustrated example, four communication lines 71 to 74 are connected to the integrated ECU 10, the meter ECU 51 is connected to the communication line 71, the brake ECU 52 is connected to the communication line 72, the expansion IF 53 is connected to the communication line 73, and the out-vehicle communication device 54 is connected to the communication line 74. In the illustrated example, two devices are respectively connected to one communication line 71 to 74, but three or more devices may be connected to one communication line 71 to 74.

[0035] The integrated ECU 10 according to this embodiment integrates the functions of three devices, namely, a gateway 11 that relays data transmission and reception, an ADAS (Advanced Driver Assistance Systems)-ECU 12 that performs processing related to driving assistance, and a verification device 13 that verifies communication, into one device. In other words, the integrated ECU 10 includes a virtual gateway 11, an ADAS-ECU 12, and a verification device 13. The gateway 11 and the ADAS-ECU 12 are connected via a virtual communication line 75, and the gateway 11 and the verification device 13 are connected via a virtual communication line 76. In this figure, virtual functional blocks and communication lines are indicated by broken lines. Note that the gateway 11, the ADAS-ECU 12, and the verification device 13 may be mounted on the vehicle 1 as individual devices.

[0036] The integrated ECU 10 can transmit and receive data to and from the meter ECU 51, the brake ECU 52, the extension IF 53, and the vehicle exterior communication device 54 via these communication lines 71 to 74. The meter ECU 51, the brake ECU 52, the extension IF 53, and the vehicle exterior communication device 54 can each transmit and receive data to and from the integrated ECU 10. Further, the integrated ECU 10 relays data transmission and reception between the four communication lines 71 to 74. Thereby, the meter ECU 51, the brake ECU 52, the extension IF 53, and the vehicle exterior communication device 54 can transmit and receive data to and from each other via the integrated ECU 10.

[0037] The meter ECU 51 controls various meters provided near the driver's seat of the vehicle 1. The meter ECU 51 controls the meters based on various information inside the vehicle 1 obtained via the in-vehicle network. For example, the meter ECU 51 performs display control of the speed meter based on information on the traveling speed of the vehicle 1 obtained via the in-vehicle network. Also, for example, the meter ECU 51 performs display control of the tachometer based on information on the engine speed or rotational speed of the vehicle 1 obtained via the in-vehicle network.

[0038] The brake ECU 52 controls the brakes of the vehicle 1. For example, the brake ECU 52 activates the brakes in response to the driver's operation on the foot brake or side brake provided in the driver's seat of the vehicle 1. Information regarding the presence or absence of an operation on the foot brake or side brake and the amount of the operation, etc. may be directly input to the brake ECU 52, or may be provided to the brake ECU 52 via the in-vehicle network. Also, for example, the brake ECU 52 activates the brakes in response to an instruction given from the ADAS-ECU 12 via the in-vehicle network.

[0039] The expansion IF 53 is for connecting an expansion ECU 61 that undertakes this function when adding a function to the vehicle 1, for example. The expansion IF 53 is connected to the communication line 73 in this example, and has connection terminals or slots, etc. for connecting the expansion ECU 61. When the expansion IF 53 detects that the expansion ECU 61 is connected, it notifies the integrated ECU 10 of the connection detection via the communication line 73.

[0040] The expansion ECU 61 is configured to be detachable with respect to the expansion IF 53, and by being attached to the expansion IF 53, it is connected to the communication line 73 of the vehicle 1 and can perform communication via the communication line 73. The expansion ECU 61 may undertake any expansion function of the vehicle 1. In this example, the expansion ECU 61 has a sensor 62 that detects obstacles, etc. existing outside the vehicle 1, and performs processing of periodically acquiring the detection result of the sensor 62 and transmitting it to other devices within the vehicle 1. Thereby, functions such as monitoring the surroundings of the vehicle 1 using the sensor 62 or avoiding obstacles can be added to the vehicle 1.

[0041] The vehicle external communication device 54 is a device that communicates with various devices installed outside the vehicle 1 by performing wireless communication such as mobile phone communication network or wireless LAN (Local Area Network). In the present embodiment, the vehicle external communication device 54 communicates with the server device 3 installed outside the vehicle 1. The vehicle external communication device 54 is connected to the integrated ECU 10 via the communication line 74, transmits data from the integrated ECU 10 to the server device 3, and provides data from the server device 3 to the integrated ECU 10.

[0042] The server device 3 according to the present embodiment stores information about various devices mounted on the vehicle 1 in a database, and distributes programs or data required by various devices mounted on the vehicle 1. For example, when a new extended ECU 61 is connected to the network of the vehicle 1, information about the extended ECU 61 is transmitted from the vehicle 1 to the server device 3. The server device 3 that has received this transmits a program or data for using the extended ECU 61 to the vehicle 1.

[0043] The gateway 11 virtually provided in the integrated ECU 10 relays data between a plurality of communication lines of the communication lines 71 to 74 and the communication lines 75 and 76. In the information processing system according to the present embodiment, the data transmitted and received is assigned an ID, and the gateway 11 has a routing map in which the correspondence between the ID assigned to the data and the communication line through which the data should be relayed is set. When the gateway 11 receives data from any one of the communication lines, it refers to the routing map based on the ID assigned to this data, and transmits the data from the communication line set as the relay destination in the routing map, thereby relaying data between a plurality of communication lines.

[0044] The ADAS-ECU 12 is a device that realizes driving assistance or autonomous driving, etc. by performing driving control of the vehicle 1 based on information obtained from various sensors and the like mounted on the vehicle 1. The ADAS-ECU 12 measures the distance to the vehicle ahead by a sensor mounted on the vehicle 1, for example, and controls the accelerator and brakes of the vehicle 1 to keep the inter-vehicle distance constant and drive the vehicle 1. Note that the control performed by the ADAS-ECU 12 is not limited to the control of maintaining the inter-vehicle distance, and may be control related to various driving assistance or autonomous driving, etc.

[0045] The verification device 13 is a device that verifies whether the extended ECU 61 can be connected when the extended ECU 61 is mounted on the expansion IF 53 and the extended ECU 61 is connected to the communication line 73. In the information processing system according to the present embodiment, when the extended ECU 61 is connected to the communication line 73, it is necessary to update the routing map used when the gateway 11 determines the data relay destination. This is, for example, because the data transmitted by the extended ECU 61 needs to be relayed to other devices, and the data transmitted from other devices needs to be relayed to the extended ECU 61, etc. The verification device 13 creates a new routing map when the extended ECU 61 is connected, and verifies the communication within the vehicle 1 using the new routing map by simulation. When a positive verification result (for example, a verification result that no abnormality occurs, etc.) is obtained by the simulation, the verification device 13 updates the routing map possessed by the gateway 11 to the new routing map.

[0046] FIG. 2 is a block diagram showing a configuration example of the integrated ECU 10 according to the present embodiment. The integrated ECU 10 according to the present embodiment includes a processing unit (processor) 21, a storage unit (storage) 22, a communication unit (transceiver) 23, and the like. The processing unit 21 is configured by using an arithmetic processing device such as a CPU (Central Processing Unit) or an MPU (Micro-Processing Unit), for example. The processing unit 21 can perform various processes by reading and executing a program 22a stored in the storage unit 22. In the present embodiment, the processing unit 21 performs processes related to three devices: the gateway 11, the ADAS-ECU 12, and the verification device 13.

[0047] The storage unit 22 is configured by using a non-volatile memory element such as a flash memory or an EEPROM (Electrically Erasable Programmable Read Only Memory), for example. The storage unit 22 stores various programs executed by the processing unit 21 and various data necessary for the processing of the processing unit 21. In the present embodiment, the storage unit 22 stores a program 22a executed by the processing unit 21, a routing map 22b for the gateway 11 to determine a data relay destination, and verification information 22c necessary for the verification device 13 to perform verification.

[0048] The program (program product) 22a may be written in the storage unit 22, for example, at the manufacturing stage of the integrated ECU 10. The integrated ECU 10 may acquire, through communication, a program distributed by a remote server device or the like. The integrated ECU 10 may read a program recorded on a recording medium 99 such as a memory card or an optical disk and store it in the storage unit 22. Alternatively, a writing device may read a program recorded on the recording medium 99 and write it in the storage unit 22 of the integrated ECU 10. The program 22a may be provided in a distribution mode via a network or in a mode recorded on the recording medium 99.

[0049] The routing map 22b is information used when the integrated ECU 10 performs relay processing as the gateway 11. In the information processing system according to the present embodiment, data transmitted and received in the network of the vehicle 1 is attached with an ID for identifying the type of the data and the like. The routing map 22b is information indicating, for example, the correspondence between the ID attached to the data and the communication lines 71 to 76 to which the data of this ID should be transmitted. When the gateway 11 receives data via any of the communication lines 71 to 76, it can acquire the ID attached to the received data and acquire from the routing map 22b which of the relay destination communication lines 71 to 76 corresponds to this ID.

[0050] The verification information 22c is information used when the integrated ECU 10 performs verification processing as the verification device 13. The verification information 22c may include information such as the network configuration of the vehicle 1, the IDs, periods, and sizes of the data transmitted by each device, and the IDs of the data required by each device. The verification information 22c contains information necessary and sufficient for the verification device 13 to simulate the communication of the network of the vehicle 1. When a new extended ECU 61 is connected, information regarding this extended ECU 61 is acquired from the server device 3 and stored in addition to the verification information 22c. The verification device 13 reads out the verification information 22c, reproduces the network of the vehicle 1 in the simulation environment, and verifies whether there are any problems in the communication when the newly created routing map is applied.

[0051] In the present embodiment, the integrated ECU 10 has four communication units 23. Each communication unit 23 is connected to one communication line 71 to 74 respectively, and communicates with other devices via these communication lines 71 to 74. The communication unit 23 transmits and receives data according to a communication protocol such as CAN (Controller Area Network) or Ethernet (registered trademark). Each communication unit 23 can be configured by using an IC (Integrated Circuit) such as a CAN controller or an Ethernet switch respectively. The communication unit 23 transmits the data by converting the digital data given from the processing unit 21 into an electrical signal and outputting it to the communication lines 71 to 74. The communication unit 23 samples and acquires the potential of the communication lines 71 to 74, converts the electrical signal on the communication line into digital data, and gives the converted data to the processing unit 21 as received data. In this example, the integrated ECU 10 has four communication units 23, but it is not limited to this, and the integrated ECU 10 may have three or less or five or more communication units 23.

[0052] In the present embodiment, the integrated ECU 10 realizes the gateway processing unit 21a, the ADAS processing unit 21b, the verification processing unit 21c, etc. as software functional units in the processing unit 21 by the processing unit 21 reading and executing the program 22a stored in the storage unit 22. The gateway processing unit 21a of the processing unit 21 performs processing corresponding to the above-described virtual gateway 11, the ADAS processing unit 21b performs processing corresponding to the ADAS-ECU 12, and the verification processing unit 21c performs processing corresponding to the verification device 13.

[0053] The gateway processing unit 21a receives data transmitted by other devices via the communication lines 71 to 76, and relays the transmission and reception of data between the communication lines 71 to 76 by transmitting the received data from an appropriate communication line 71 to 76. The gateway processing unit 21a determines the relay destination of this data by referring to the routing map 22b stored in the storage unit 22 based on the ID included in the received data. Further, when the communication protocols are different between the data relay source and the relay destination, the gateway processing unit 21a may perform processing to convert the data to be relayed into a format suitable for each communication protocol.

[0054] The ADAS processing unit 21b performs processing related to driving support or autonomous driving of the vehicle 1. For example, the ADAS processing unit 21b controls the accelerator and brakes of the vehicle 1 to keep the inter-vehicle distance constant. Also, for example, when the vehicle in front photographed by the camera suddenly brakes, the ADAS processing unit 21b gives a warning to the driver. Also, for example, when a collision with the vehicle or obstacle in front cannot be avoided by the warning to the driver, the ADAS processing unit 21b performs control to operate the brakes to stop the vehicle 1. These controls of the ADAS processing unit 21b are just examples and are not limited thereto. The ADAS processing unit 21b may perform any control related to driving support or autonomous driving.

[0055] When the extended ECU 61 is mounted on the extension IF 53 and the extended ECU 61 is connected to the network of the vehicle 1, the verification processing unit 21c performs processing to generate a new routing map 22b and verification processing of communication using the generated routing map 22b. The verification processing unit 21c, for example, acquires information such as the device ID from the newly connected extended ECU 61 and transmits it to the server device 3 outside the vehicle 1, and requests transmission of information necessary for verification of the extended ECU 61. In response to this request, the server device 3 acquires information necessary for verification of the extended ECU 61 from the database and transmits it to the integrated ECU 10. The verification processing unit 21c acquires the information from the server device 3, adds it to the verification information 22c in the storage unit 22, and stores it.

[0056] Next, the verification processing unit 21c creates a new routing map corresponding to the new extended ECU 61 based on the routing map 22b stored in the storage unit 22 and the verification information 22c acquired from the server device 3. In the verification information 22c, for example, the ID of the data transmitted by the extended ECU 61 and the ID of the device that should receive this data are stored in association with each other. Also, in the verification information 22c, for example, the ID of the data required by the extended ECU 61 is stored. Based on this verification information 22c, the verification processing unit 21c can determine which communication lines 71 to 76 the data transmitted by the extended ECU 61 should be relayed to. Also, among the data transmitted by devices such as the meter ECU 51 and the brake ECU 52 already mounted on the vehicle 1, the verification processing unit 21c determines which data should be relayed to the communication line 73 to which the extended ECU 61 is connected. The verification processing unit 21c creates a new routing map based on the determined relay destination.

[0057] Note that in this embodiment, it is assumed that the verification processing unit 21c (verification device 13) creates the routing map, but it is not limited to this. The gateway processing unit 21a (gateway 11) or another processing unit (another device) may create the routing map.

[0058] Next, the verification processing unit 21c verifies the feasibility of the created new routing map through simulation. The verification information 22c includes information such as the network configuration of vehicle 1, the IDs, periods, and sizes of the data transmitted by each device, and the IDs of the data required by each device. Based on this verification information 22c, the verification processing unit 21c constructs a virtual network of vehicle 1 to be simulated on the simulation environment. In the virtual network, the verification processing unit 21c performs a simulation in which each device transmits and receives data at the periods and sizes set in the verification information 22c. The verification processing unit 21c calculates values such as the communication load on each communication line 71 to 76 or the maximum delay time for each data by measuring the amount and frequency of the data transmitted and received on the network of vehicle 1 in the simulation. The verification processing unit 21c determines the feasibility of the new routing map by determining whether these calculated values satisfy a predetermined condition. When a positive verification result (a verification result that satisfies the predetermined condition) is obtained, the verification processing unit 21c updates the routing map 22b by overwriting and storing the new routing map in the routing map 22b stored in the storage unit 22.

[0059] On the other hand, when a negative verification result (a verification result that does not satisfy the predetermined conditions) is obtained, the verification processing unit 21c performs verification by simulation for the case where thinning is performed on the data relay by the gateway processing unit 21a (gateway 11), for example, and determines whether the predetermined conditions are satisfied. In the information processing system according to the present embodiment, the ID attached to each piece of data transmitted and received represents the type of this data and the like, and also represents the priority. The ID of the data is, for example, a numerical value of a predetermined number of digits, and the lower the value, the higher the priority. The verification processing unit 21c performs verification for the case where data is thinned out in ascending order of priority, and determines the data that needs to be thinned out in order to satisfy the predetermined conditions. As a method of thinning out the data relay, for example, a method of discarding data without relaying it at a frequency of once every predetermined number of times, or discarding data without relaying it with a predetermined probability, can be adopted. The verification processing unit 21c notifies the gateway processing unit 21a (gateway 11) of the ID of the data determined to need to be thinned out, and the gateway processing unit 21a thins out the data of this ID and performs relaying thereafter.

[0060] Note that in the present embodiment, when a negative verification result is obtained by simulation, the verification processing unit 21c thins out the data relay by the gateway 11, but it is not limited to this. For example, the verification processing unit 21c may cause a decrease in the data transmission frequency or the like for one or more devices connected to the network of the vehicle 1. Also, for example, the verification processing unit 21c may display a message for rejecting the connection of the newly connected extended ECU 61 or the like on the display of the vehicle 1, and may not update the routing map 22b.

[0061] After the verification of the simulation and the update of the routing map 22b are completed, the verification processing unit 21c notifies the server device 3 to that effect and transmits information such as the updated network configuration and routing map of the vehicle 1 to the server device 3. The server device 3 that has received these information stores the received information in the database in association with the identification information of the vehicle 1 and the like. Further, the server device 3 determines whether the programs of the respective devices mounted on the vehicle 1 need to be updated due to the addition of the extended ECU 61, and if it is determined that an update is necessary, the server device 3 transmits the update program to the vehicle 1. The integrated ECU 10 appropriately transmits the update program from the server device 3 to each device that requires it, and causes each device to update the program.

[0062] <Function expansion process> FIG. 3 is a schematic diagram for explaining the procedure of the function expansion process performed by the information processing system according to the present embodiment. In the information processing system according to the present embodiment, when a user or the like connects the extended ECU 61 to the extension IF 53 that constitutes the network of the vehicle 1, the function of the vehicle 1 is expanded. When the extension IF 53 detects that the extended ECU 61 is connected, it notifies the verification device 13 of the integrated ECU 10 to that effect. At this time, the extension IF 53 acquires information such as the ID from the extended ECU 61 and transmits this information to the verification device 13 together with the connection detection notification. The data of the notification transmitted by the extension IF 53 is received by the verification device 13 via the communication line 73, the gateway 11 of the integrated ECU 10, and the communication line 76.

[0063] The verification device 13 that has received the notification from the extension IF 53 acquires the ID of the extended ECU 61 included in this notification. The verification device 13 notifies by transmitting the acquired ID to the server device 3. At this time, the data including the ID transmitted by the verification device 13 is received by the server device 3 provided outside the vehicle 1 via the communication line 76, the gateway 11, the communication line 74, and the off-vehicle communication device 54.

[0064] In the information processing system according to this embodiment, the server device 3 stores in a database information about various devices that can be additionally connected to the vehicle 1. The information stored in the database may include, for example, information such as the ID, size, and transmission period of the data transmitted by the device, as well as information such as the ID of the data required by this device. When receiving a notification of the ID of the extended ECU 61 additionally connected from the vehicle 1, the server device 3 reads out the information stored in the database corresponding to this ID, and transmits the read information to the vehicle 1 that is the transmission source of the ID. The information transmitted by the server device 3 is received by the verification device 13 via the vehicle exterior communication device 54 of the vehicle 1, the communication line 74, the gateway 11 of the integrated ECU 10, and the communication line 76.

[0065] The verification device 13 that has received the information from the server device 3 creates a new routing map based on the received information. FIG. 4 is a schematic diagram showing an example of the routing map. The routing map shown in the upper part of FIG. 4 stores, for example, information such as "type", "ID", "relay source", "relay destination", and "thinning" in association with each other. The "type" is the type of information included in the data transmitted and received in the network of the vehicle 1, and types such as "travel distance", "vehicle speed", "speed warning", or "abnormal water temperature" can be set. However, the routing map may not include the "type" information.

[0066] The "ID" of the routing map is the identification information attached to the data transmitted and received. Also, the "ID" is used as information indicating the priority of the data, and the smaller the value, the higher the priority. For example, when the CAN communication protocol is used in the network of the vehicle 1, the CAN-ID can be used as the "ID". In this example, a hexadecimal numerical value is set as the "ID".

[0067] In the "relay source" and "relay destination" of the routing map, information for identifying a plurality of communication lines connected to the gateway 11 is set. In this example, using the reference numerals shown in FIG. 1, "communication lines 71 to 76" are described as the identification information of the communication lines. The "relay source" is the communication lines 71 to 76 through which the gateway 11 receives the data, and the "relay destination" is the communication lines 71 to 76 through which the gateway 11 transmits the data. For example, data regarding "travel distance" with an "ID" of "0B2" is transmitted from a device connected to the "communication line 72" of the "relay source" to the gateway 11, and the gateway 11 that has received this data may transmit this data from the "communication line 71" which is the "relay destination".

[0068] In the "decimation" of the routing map, whether or not to perform decimation processing on the corresponding data is set to either "yes" or "no". The gateway 11 performs decimation processing such as reducing the relay frequency on the data for which "yes" is set in the "decimation" of the routing map.

[0069] For the routing map shown in the upper part of FIG. 4, an example of a new routing map created by the verification device 13 due to the addition of the extended ECU 61 is shown in the lower part of FIG. 4. In this example, due to the addition of the extended ECU 61, three types, namely "sonar data", "automatic brake request", and "obstacle warning request", are added to the types of data transmitted and received in the in-vehicle network. The server device 3 notified of the addition of the extended ECU 61 transmits, for example, information indicating that the extended ECU 61 transmits "sonar data" with an "ID" of "501" and this data is used by the ADAS-ECU 12 to the verification device 13. Based on the information from the server device 3 and the configuration of the network of the vehicle 1 (the extended ECU 61 is connected to the communication line 73 and the ADAS-ECU 12 is connected to the communication line 75), the verification device 13 can add the information of "sonar data" shown in the lower part of FIG. 4 to the routing map shown in the upper part of FIG. 4.

[0070] In this example, with the addition of the extended ECU 61, functions such as automatic braking and obstacle warning are added to the vehicle 1. In relation to this function addition, the server device 3 transmits information indicating that, for example, the ADAS-ECU 12 transmits data of "automatic braking request" with "ID" being "0B2" and this data is used by the brake ECU 52, to the verification device 13. Further, the server device 3 transmits information indicating that, for example, the ADAS-ECU 12 transmits data of "obstacle warning request" with "ID" being "202" and this data is used by the meter ECU 51, to the verification device 13. Based on these pieces of information from the server device 3 and the configuration of the network of the vehicle 1, the verification device 13 can add the information of "automatic braking request" and "obstacle warning request" shown in the lower part of FIG. 4 to the routing map shown in the upper part of FIG. 4.

[0071] Note that in this example, the verification device 13 creates a new routing map by adding information to the existing routing map, but it is not limited to this. The verification device 13 may create a new routing map by changing part or all of the information included in the existing routing map, or may create a new routing map by deleting part of the information included in the existing routing map. The verification device 13 may appropriately combine the addition, change, and deletion of information with respect to the existing routing map to create a new routing map, or may create a new routing map from the beginning without using the existing routing map.

[0072] Based on the information received from the server device 3 with the addition of the extended ECU 61, the verification device 13 that created a new routing map verifies, by simulation, the communication of the in-vehicle network when the created new routing map is applied. As shown in FIG. 3, at this time, the verification device 13 performs a simulation of the communication of the in-vehicle network by simulation using the verification information 22c stored in the storage unit 22. The verification information 22c may include, for example, which devices are connected to each communication line 71 to 76 constituting the network of the vehicle 1, the speed of communication performed on each communication line 71 to 76, and information such as the ID, period, and size of the data transmitted by each device. In addition, the information transmitted from the server device 3 described above includes similar information necessary for performing simulation verification regarding the data transmitted and received by the extended ECU 61 and the data added to the in-vehicle network due to the addition of functions based on the extended ECU 61. The verification device 13 stores these information received from the server device 3 by adding them to the verification information 22c in the storage unit 22.

[0073] Based on the information regarding the configuration of the network of the vehicle 1 included in the verification information 22c, the verification device 13 reproduces, for example, the network of the vehicle 1 in the simulation environment. The verification device 13 simulates, for example, the flow of each data when data is transmitted from each device of the reproduced network at the period and size determined in the verification information 22c. The verification device 13 calculates, for example, the ratio of the time during which data is transmitted and received on each communication line 71 to 76 over the entire time of the simulation as the communication load rate, and calculates the average value of the communication load rates of the plurality of communication lines 71 to 76 as the average load rate. The verification device 13 determines whether the calculated average load rate satisfies a predetermined condition (for example, 70% or less).

[0074] Also, the verification device 13 calculates, for each piece of data transmitted and received in the network of the vehicle 1 for example, the delay time from the timing when the data is transmitted from the transmitting device until the data is received by the receiving device. The verification device 13 calculates this delay time for all the data transmitted and received in the simulation, and acquires the one with the largest delay time as the maximum delay time. The verification device 13 determines whether or not this maximum delay time satisfies a predetermined condition (for example, 3 milliseconds or less). Note that the characteristic values of the network calculated by the verification device 13 by simulation are not limited to the above average load factor or maximum delay time. The verification device 13 may calculate various characteristic values such as the amount of data transmitted and received on each communication line 71 to 76, or the occurrence frequency of arbitration processing (arbitration) that occurs when a plurality of devices transmit data simultaneously on each communication line 71 to 76. The verification device 13 may perform any condition determination on the calculated characteristic values.

[0075] When a positive verification result is obtained by simulation using the newly created routing map, the verification device 13 transmits the new routing map to the gateway 11. The gateway 11 that has received the new routing map from the verification device 13 updates the routing map 22b by overwriting the previous routing map 22b with the new routing map. Note that in the information processing system according to the present embodiment, both the verification device 13 and the gateway 11 are present in the integrated ECU 10. Therefore, if the verification device 13 can rewrite the routing map 22b stored in the storage unit 22, the verification device 13 may update the routing map 22b.

[0076] The gateway 11 that has updated the routing map 22b transmits information such as the updated routing map 22b and the configuration of the network of the vehicle 1 to the server device 3 in order to notify that the routing map 22b has been updated. The information transmitted by the gateway 11 is received by the server device 3 via the communication line 74 and the off-vehicle communication device 54. The server device 3 that has received this information stores the received information in a database in association with information such as an ID for identifying the vehicle 1. The database of the server device 3 stores information such as the network configuration of the vehicle 1, the types of devices mounted on the vehicle 1, and the versions of the programs installed in each device. The server device 3 determines whether it is necessary to update (or install, etc.) the program for one or more devices mounted on the vehicle 1 based on the information received from the gateway 11. If it is determined that an update is necessary, the server device 3 reads out the update program from the database or the like and transmits it to the vehicle 1. The update program transmitted by the server device 3 is received by the gateway 11 via the off-vehicle communication device 54 and the communication line 74 of the vehicle 1. The gateway 11 transmits the update program received from the server device 3 to the devices that require it and causes the program to be updated.

[0077] Although not shown in FIG. 3, when a negative verification result is obtained by simulation using the newly created routing map, the verification device 13 determines data for thinning out relays by performing, for example, further simulation. The verification device 13 sets the "thinning out" of the routing map to "yes" for the data determined to perform thinning out, and transmits this routing map to the gateway 11. Further, when a negative verification result is obtained, the verification device 13 may, for example, not update the routing map, cause the meter ECU 51 to display a warning message or the like, and prompt the user to remove the extended ECU 61 or the like.

[0078] In the routing map illustrated in the lower part of FIG. 4, negative verification results were obtained through simulation, and it was determined that thinning processing would be performed on two pieces of data, "abnormal water temperature" and "sonar data", with large (low priority) "ID" values, and "thinning" was set to "yes".

[0079] FIG. 5 is a flowchart showing an example of the procedure of the process performed by the verification device 13 according to the present embodiment. The verification device 13 according to the present embodiment determines whether or not the connection of the extended ECU 61 to the extended IF 53 has been detected based on the presence or absence of a notification from the extended IF 53 (step S1). If the connection of the extended ECU 61 has not been detected (S1: NO), the verification device 13 waits until the extended ECU 61 is connected. If the connection of the extended ECU 61 has been detected (S1: YES), the verification device 13 acquires information such as the ID of the connected extended ECU 61 from the information transmitted from the extended IF 53 (step S2). The verification device 13 requests the server device 3 to acquire information regarding the extended ECU 61 by transmitting the information such as the ID acquired in step S2 to the server device 3 via the vehicle external communication device 54 (step S3).

[0080] The verification device 13 receives the information transmitted from the server device 3 in response to the request in step S3 via the vehicle external communication device 54 (step S4). The verification device 13 adds and stores part or all of the information received in step S4 in the verification information 22c of the storage unit 22 (step S5). The verification device 13 creates a new routing map based on the current routing map 22b stored in the storage unit 22 and the information acquired in step S4 (step S6). The verification device 13 reads out the verification information 22c stored in the storage unit 22 in order to verify the routing map created in step S6 (step S7). The verification device 13 constructs the network of the vehicle 1 on the simulation environment based on the verification information 22c read out in step S7, and verifies the validity of the newly created routing map by performing a simulation of communication according to the routing map created in step S6 (step S8).

[0081] The verification device 13 determines whether a positive verification result has been obtained through the verification in the simulation in step S8 (step S9). If a positive verification result is obtained (S9: YES), the verification device 13 updates the routing map used by the gateway 11 by transmitting the routing map created in step S6 to the gateway 11 (step S11), and ends the process. On the other hand, if a positive verification result is not obtained (S9: NO), that is, if a negative verification result is obtained, the verification device 13 determines, for example, data for thinning out the relay by the gateway 11 by repeating the simulation, and sets the gateway 11 to thin out the data relay (step S10). After that, the verification device 13 updates the routing map (step S11) and ends the process.

[0082] <Summary> In the information processing system according to the present embodiment having the above configuration, when the verification device 13 of the integrated ECU 10 detects the connection of the extended ECU 61 to the network in the vehicle 1, the gateway 11 creates a routing map for determining the data relay destination. The verification device 13 verifies the network communication according to the created routing map by simulation, and updates the routing map 22b when a positive verification result is obtained. Thus, it can be expected that the information processing system suppresses the occurrence of communication problems or the like due to the addition of the extended ECU 61 to the network of the vehicle 1.

[0083] Also, in the information processing system according to the present embodiment, the verification device 13 calculates communication characteristics such as the average load rate or the maximum delay time of the data transmitted and received on each communication line 71 to 76 of the network when the extended ECU 61 is added. The verification device 13 verifies whether the calculated values satisfy a predetermined condition. Thus, it can be expected that the information processing system suppresses the occurrence of communication problems or the like due to an increase in the average load rate or the maximum delay time or the like due to the addition of the extended ECU 61.

[0084] In the information processing system according to the present embodiment, the verification device 13 acquires information such as the ID of the extended ECU 61 newly connected to the network of the vehicle 1 and transmits it to the server device 3 provided outside the vehicle 1. In response to this, the verification device 13 receives information for updating the routing map transmitted from the server device 3, and creates a routing map based on the received information. As a result, the information processing system does not need to hold information on various devices that can be added to the network of the vehicle 1 within the vehicle 1.

[0085] In the information processing system according to the present embodiment, when a negative verification result is obtained by simulation, the routing map is updated, and thinning is performed according to the data priority for data relay by the gateway 11. As a result, when an increase in the communication volume of the network within the vehicle 1 may occur due to the addition of the extended ECU 61, the information processing system can be expected to suppress the increase in the communication volume by performing thinning of the relay by the gateway 11.

[0086] In the present embodiment, the gateway 11 and the verification device 13 are mounted on the vehicle 1 as one device (integrated ECU 10), but the present invention is not limited to this, and the gateway 11 and the verification device 13 may be mounted on the vehicle 1 as individual devices. Further, the server device 3 provided outside the vehicle 1 is configured to hold information necessary for creating a routing map and verification by simulation, but the present invention is not limited to this. These information may be held by any device within the vehicle 1, for example, the verification device 13 or the gateway 11. Further, these information may be acquired by the verification device 13 via a recording medium such as a memory card or an optical disk.

[0087] <Verification Process> FIG. 6 is a schematic diagram for explaining the outline of the simulation performed in the information processing system according to the present embodiment. In the information processing system according to the present embodiment, a verification device 13 (verification processing unit 21c) provided in the integrated ECU 10 mounted on the vehicle 1 performs verification by simulation.

[0088] The verification device 13 includes a model generation unit 131, a scenario generation unit 132, a scenario execution unit 133, and the like. The verification device 13 also includes a vehicle DB (database) 141 and a use case DB 142 that store information necessary for performing the simulation. In the present embodiment, the verification device 13 is a device virtually provided in the integrated ECU 10, and the model generation unit 131, the scenario generation unit 132, and the scenario execution unit 133 are functional blocks provided in the verification processing unit 21c of the processing unit 21 of the integrated ECU 10 shown in FIG. 2. The information stored in the vehicle DB 141 and the use case DB 142 corresponds to the verification information 22c of the storage unit 22 of the integrated ECU 10 shown in FIG. 2.

[0089] The model generation unit 131 performs a process of generating a network model 145 for use in the simulation based on the information stored in the vehicle DB 141 and the information obtained from the server device 3. Here, the model generation unit 131 generates a network model 145 having a configuration in which an additional device is connected to the network of the existing vehicle 1 based on the configuration of the existing in-vehicle devices and communication lines stored in the vehicle DB 141 and the information about the additional device obtained from the server device 3. The vehicle DB 141 is a database that stores the configuration of the communication device and communication lines mounted on the vehicle 1. The vehicle DB 141 stores, for example, the configuration of the integrated ECU 10, the meter ECU 51, the brake ECU 52, the expansion IF 53, the vehicle exterior communication device 54, and the communication lines 71 to 74, etc. as the configuration of the vehicle 1 shown in FIG. 1. The information obtained from the server device 3 is, for example, in the case of the vehicle 1 shown in FIG. 1, the information about the configuration of the expansion ECU 3 connected to the expansion IF 53 and the information of the updated routing map accompanying the addition of this expansion ECU 3.

[0090] The scenario generation unit 132 performs a process of generating a simulation scenario 146 based on the information stored in the vehicle DB 141, the information stored in the use case DB 142, and the information obtained from the server device 3. The use case DB 142 is an operation database that stores the correspondence between various operations performed in the vehicle 1 and the events that occur in these operations.

[0091] The scenario execution unit 133 performs a simulation by executing the scenario 146 based on the network model 145 generated by the model generation unit 131 and the scenario 146 generated by the scenario generation unit 132. For example, the scenario execution unit 133 inputs input data according to the scenario 146 to the network model 145 and acquires the output data output by the network model 145 according to this input data. The scenario execution unit 133 manages the time in the simulation and repeats the input and output of data to the network model 145 according to the passage of time to execute the scenario 146. In addition, the scenario execution unit 133 acquires information such as the internal state of the network model 145 that changes with the execution of the scenario. The scenario execution unit 133 outputs these information obtained by the execution of the scenario 146 as an operation log 147.

[0092] Based on the operation log 147 output by the scenario execution unit 133, the verification device 13 calculates the load rate, delay time, etc. of the network model 145, and determines whether the calculated values satisfy a predetermined criterion. The verification device 13 determines that a positive verification result is obtained when the calculated values satisfy the criterion, and determines that a negative verification result is obtained when the criterion is not satisfied.

[0093] FIG. 7 is a schematic diagram for explaining an example of the network model 145 generated by the model generation unit 131. The illustrated network model 145 shows a part of the model of the configuration of the vehicle 1 shown in FIG. 1. The illustrated network model 145 includes, for example, a virtual gateway that virtually reproduces the gateway 11 of the vehicle 1, and virtual ECUs that virtually reproduce the meter ECU 51, the brake ECU 52, and the like. The network model 145 includes information on these virtual communication devices such as virtual gateways and virtual ECUs, and virtual communication lines connecting them.

[0094] Information such as the number of communication ports, the type of communication ports, the amount of mounted memory, and the CPU processing capacity is set for the virtual communication devices of the network model 145. Also, the internal state of the virtual communication devices, such as state information such as power state, presence or absence of failure state, elapsed time, and CPU state, is managed.

[0095] Also, the operations to be performed in the simulation are set for each virtual communication device. In the network model 145 of FIG. 7, the operation of the virtual gateway is illustrated by functional blocks. In the virtual gateway of this example, for example, the receiving unit receives the data transmitted from the virtual ECU and stores it in the receiving buffer. The relay unit acquires the data from the receiving buffer, determines the relay destination according to the routing map, stores the data in the relay buffer, and when the timing to transmit arrives, acquires the data from the relay buffer and stores it in the transmission buffer. The transmission unit sequentially transmits the data stored in the transmission buffer. The stored contents of the receiving buffer, the relay buffer, and the transmission buffer of the illustrated virtual gateway are treated as internal state information of the virtual gateway in the simulation.

[0096] FIG. 8 is a schematic diagram showing a configuration example of the use case DB 142. The use case DB 142 according to the present embodiment is a database that stores information of, for example, "use case", "precondition", and "occurring event" in association with each other. The "use case" is an operation that can be performed in the vehicle 1, and is classified into types such as, for example, "when adding a function", "when connecting a battery", "unlocking from outside the vehicle in a parked state", "when starting the engine", "when starting driving", and "when the engine stops ~ getting out of the vehicle, locking".

[0097] The "precondition" is information indicating the state of the vehicle 1 when the operation of the "use case" is performed, and the conditions that are the premise when simulating this "use case" are stored. For example, the "preconditions" for "when adding a function" are two: "all existing devices: power on, initialization completed" and "added device: power off, initialization not completed". Also, for example, the "precondition" for "when connecting a battery" is "all existing devices: power off, initialization not completed".

[0098] The "occurring event" is information in which a plurality of events included in the operation of the "use case" are arranged in chronological order. The "occurring events" for "when adding a function" may include events such as, for example, "added device: power on", "added device: initialization start", "added device: initialization completed", "all existing devices: regular transmission start", and "added device: device registration sequence start". Also, the "occurring events" for "when connecting a battery" may include events such as, for example, "all existing devices: power on", "all existing devices: initialization start", "all existing devices: initialization completed", and "all existing devices: regular transmission start".

[0099] The scenario generation unit 132 of the verification device 13 according to this embodiment generates scenarios for performing simulations for all the "use cases" registered in the use case DB 142. For example, for one "use case", the scenario generation unit 132 can generate a command for setting the internal state of the network model 145 so as to satisfy the "preconditions", and time-series input data for the network model 145 for generating each event stored in time series in the "generated events" as a scenario. Further, the scenario generation unit 132 can generate input data for events based on the network and the structure of each device stored in the vehicle DB 141.

[0100] FIG. 9 is a schematic diagram showing an example of the scenario 146. The scenario 146 generated by the scenario generation unit 132 according to this embodiment has, for example, information such as "time", "event type", "source", "destination", "ID", and "data length" associated with each other as one step, and information of a plurality of steps arranged in time series.

[0101] The "time" of the scenario 146 is the simulation time managed by the scenario execution unit 133, and the event of this step is performed at the corresponding time of the simulation. The "event type" is the type of event performed in this step, and various event types such as "CAN transmission" or "user interruption" can be set. The "source" can be set with the ID of the device that transmits data on the communication line in communication. The "destination" can be set with the ID of the device that receives data in communication. The "ID" is the ID attached to the data to be transmitted and received, and in the case of CAN communication, the CAN-ID can be used. The "data length" is the length of the data to be transmitted and received, and a numerical value in units such as bytes can be set.

[0102] The scenario execution unit 133 of the verification device 13 manages the time in the simulation and the states of each device included in the network, etc., and performs the simulation by executing the events set in the scenario 146 generated by the scenario generation unit 132 one step at a time. Based on the information of one step of the scenario 146, the scenario execution unit 133 generates input data for the network model 145 generated by the model generation unit 131. The scenario execution unit 133 inputs the generated data to the network model 145, and acquires the data output by the network model 145 accordingly. Also, the scenario execution unit 133 acquires the internal state of the network model 145 at this time. The scenario execution unit 133 stores the acquired information such as the output data and the internal state as an operation log 147.

[0103] FIG. 10 and FIG. 11 are schematic diagrams showing an example of the operation log 147. Note that FIG. 10 shows the operation log 147 related to the communication bus included in the network model 145, and FIG. 11 shows the operation log 147 related to the communication device included in the network model 145. In the present embodiment, the operation log 147 related to the communication bus and the operation log 147 related to the communication device are generated separately, but the present invention is not limited to this, and the operation logs 147 of the communication bus and the communication device may be combined into one.

[0104] In the operation log related to the communication bus, for example, information such as "time", "communication bus", "operation", and "ID" is stored in association. "Time" is the time in the simulation and corresponds to the "time" of the scenario 146. "Communication bus" can be set with the ID of the communication bus included in the network model 145, etc. "Operation" can store information such as "start" or "end" as the operation state of the communication bus. "ID" is the ID attached to the data transmitted and received on the communication line.

[0105] In the operation log related to the communication device, information such as "time", "communication device", "operation", and "ID" is stored in association. "Time" is the time in the simulation and corresponds to the "time" of scenario 146. For "communication device", the ID of the communication device included in the network model 145 can be set. For "operation", information such as "transmission" or "reception" can be stored as the operation state of the communication device. "ID" is the ID attached to the data transmitted and received by the communication device.

[0106] In the scenario 146 generated by the scenario generation unit 132 in this embodiment, for example, information for simulating all the use cases stored in the use case DB 142 is included. The scenario execution unit 133 executes all the events included in the scenario 146 and performs the simulation of all the use cases for the network model 145. In the operation log 147 output by the scenario execution unit 133, information such as the output data of the network model 145 or the internal state of the devices included in the network model 145 may be included for all the steps included in the scenario 146.

[0107] The verification device 13 calculates the network load rate or communication delay based on the operation log 147 obtained as a result of the simulation. For example, for each communication bus included in the network model 145, the verification device 13 calculates the ratio of the time during which data is transmitted and received on the communication bus with respect to the total simulation time, and can use the highest ratio among all the communication buses or the average value of a plurality of ratios as the network load rate. Also, for example, for all the data transmitted and received in the simulation, the verification device 13 calculates the time (delay time) from when it is transmitted at the transmission source until it is received at the reception destination, and can use the maximum value or average value of the plurality of delay times calculated for all the data as the network communication delay.

[0108] The verification device 13 determines whether the result of the verification by simulation is positive or negative by determining whether the calculated load factor or communication delay meets a predetermined standard. For example, when the load factor is 70% or less, the verification device 13 determines that the result is positive, and when the load factor exceeds 70%, it determines that the result is negative. Also, for example, when the communication delay is 3 milliseconds or less, the verification device 13 determines that the result is positive, and when the communication delay exceeds 3 milliseconds, it determines that the result is negative. Note that the value calculated by the verification device 13 based on the operation log 147 may be other than the load factor or communication delay. Also, the above-mentioned threshold values of the load factor of 70% and the communication delay of 3 milliseconds are merely examples and are not limited thereto, and the designer or administrator of the information processing system according to the present embodiment can appropriately determine appropriate values in advance.

[0109] FIG. 12 is a flowchart showing an example of the procedure of the simulation verification process performed by the verification device 13 according to the present embodiment. The model generation unit 131 of the verification device 13 according to the present embodiment acquires information regarding the additional devices obtained from the server device 3 (step S31). Also, the model generation unit 131 acquires information regarding the vehicle 1 stored in the vehicle DB 141, for example, information regarding the devices and communication lines constituting the network of the vehicle 1 (step S32). Based on the information acquired in steps S31 and S32, the model generation unit 131 generates a network model 145 for performing simulation verification (step S33).

[0110] Also, the scenario generation unit 132 of the verification device 13 acquires the use case stored in the use case DB 142 (step S34). Based on the information acquired in steps S31 and S32 and the use case acquired in step S34, the scenario generation unit 132 generates a simulation verification scenario 146 (step S35).

[0111] The scenario execution unit 133 of the verification device 13 acquires information for one step from the scenario 146 generated in step S35 (step S36). The scenario execution unit 133 inputs the input data generated based on the information acquired in step S36 into the network model 145 generated in step S33 (step S37). The scenario execution unit 133 acquires information such as the data output by the network model 145 according to the data input in step S37 and the internal state of the network model 145 at this time (step S38). The scenario execution unit 133 records the information acquired in step S38 as the operation log 147 (step S39).

[0112] The scenario execution unit 133 determines whether processing has been completed for all steps included in the scenario 146 (step S40). If processing has not been completed for all steps (S40: NO), the scenario execution unit 133 returns the processing to step S36, acquires information regarding the next step from the scenario 146, and repeats the same processing.

[0113] When processing has been completed for all steps of the scenario 146 (S40: YES), the verification device 13 calculates the network load rate and communication delay based on the operation log 147 recorded in step S39 (step S41). The verification device 13 compares the values of the load rate and communication delay calculated in step S41 with a predetermined standard (step S42). The verification device 13 outputs a positive or negative verification result based on the comparison result in step S42 (step S43) and ends the processing.

[0114] As described above, in the information processing system according to the present embodiment, the verification device 13 of the integrated ECU 10 verifies the communication of the network of the vehicle 1 by simulation, and updates the routing map when a positive verification result is obtained. As a result, it is expected that the information processing system can verify in detail the communication when the extended ECU 61 is added to the network of the vehicle 1 by simulation, and suppress the occurrence of problems related to communication and the like.

[0115] In the present embodiment, the vehicle DB 141 stores information regarding the configuration of the network of vehicle 1. However, the present invention is not limited to this, and the generated network model 145 may be stored in the vehicle DB 141. The verification device 13 can update the network model 145 by adding a model for newly added devices to the network model 145 stored in the vehicle DB 141, and perform verification by simulation using the updated network model 145.

[0116] The in-vehicle information processing device includes a computer configured to include a microprocessor, a ROM, a RAM, and the like. An arithmetic processing unit such as a microprocessor may read and execute a computer program including some or all of the steps of a sequence diagram or a flowchart as shown in FIGS. 3 and 5 from a storage unit such as a ROM or a RAM. The computer programs of these multiple devices can be installed from an external server device or the like respectively. Also, these computer programs are distributed in a state stored in a recording medium such as a CD-ROM, a DVD-ROM, or a semiconductor memory.

[0117] The embodiments disclosed this time should be considered as illustrative in all respects and not restrictive. The scope of the present disclosure is shown not by the above description but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0118] <Supplementary Note> (Supplementary Note 1) On a computer mounted on a vehicle, detect the connection of an in-vehicle communication device to a network within the vehicle, when the connection of the in-vehicle communication device is detected, create a routing map for determining a relay destination of data transmitted and received on the network, verify the communication of the network by simulation using the created routing map, Update the routing map when a positive verification result is obtained A computer program that causes processing to be executed.

Explanation of Signs

[0119] 1 Vehicle (Information Processing System) 3 Server Device 10 Integrated ECU (In-Vehicle Information Processing Device, Computer) 11 Gateway (In-Vehicle Relay Device) 12 ADAS-ECU 13 Verification Device (In-Vehicle Information Processing Device, Computer) 21 Processing Unit 21a Gateway Processing Unit 21b ADAS Processing Unit 21c Verification Processing Unit (Detection Unit, Creation Unit, Verification Unit, Update Unit, Acquisition Unit, Transmission Unit, Reception Unit) 22 Storage Unit 22a Program (Computer Program) 22b Routing Map 22c Verification Information 23 Communication Unit 51 Meter ECU 52 Brake ECU 53 Expansion IF 54 Vehicle External Communication Device 61 Expansion ECU (In-Vehicle Communication Device) 62 Sensor 71~76 Communication Lines 99 Recording Medium 131 Model Generation Unit 132 Scenario Generation Unit 133 Scenario Execution Unit 141 Vehicle DB (Configuration Database) 142 Use Case DB (Operation Database) 145 Network Model 146 Scenario 147 Operation Log

Claims

1. A detection unit that detects the connection of an in-vehicle communication device to the network within the vehicle, A creation unit that, upon detecting the connection of the in-vehicle communication device, creates a routing map to determine the relay destination of data transmitted and received on the network, A verification unit that verifies the communication of the network using the created routing map through simulation, If a positive verification result is obtained, the update unit updates the routing map. An in-vehicle information processing device equipped with the following features.

2. The verification unit verifies, through the simulation, whether the load factor or communication delay in the network when the in-vehicle communication device is added satisfies predetermined conditions. The in-vehicle information processing device according to claim 1.

3. An acquisition unit that acquires information about the in-vehicle communication device connected to the aforementioned network, A transmitting unit that transmits the acquired information to an external device, A receiving unit that receives the routing map update information transmitted by the external device in response to the transmission of the aforementioned information. Furthermore, The creation unit creates the routing map based on the received update information. The in-vehicle information processing device according to claim 1.

4. If a negative verification result is obtained, the update unit updates the routing map and performs data thinning according to the priority of the data. The in-vehicle information processing device according to claim 1.

5. A model generation unit that generates a model of the aforementioned network, A scenario generation unit that generates the simulation scenario, A scenario execution unit that performs data input and output to the model according to the aforementioned scenario. Equipped with, The verification unit performs verification based on the data input to and output to the model, and the internal state of the model. The in-vehicle information processing device according to claim 1.

6. The vehicle is equipped with a configuration database that stores configuration information of the on-board communication device and communication lines installed in the vehicle, The model generation unit generates the model based on the configuration information stored in the configuration database and the configuration information of the in-vehicle communication device connected to the network. The in-vehicle information processing device according to claim 5.

7. The vehicle is equipped with an operation database that stores the correspondence between the vehicle's operation and the events that occur during each operation. The scenario generation unit generates the scenario, which defines events that occur in a time series, based on the information stored in the operation database and the configuration information of the in-vehicle communication device connected to the network. The in-vehicle information processing device according to claim 5.

8. The aforementioned scenario defines events that occur in the network in a time series, The aforementioned scenario execution unit, Based on the time-series events defined in the aforementioned scenario, data to be input to the model is generated. The generated data is input into the aforementioned model. The data output by the model in response to the input of the aforementioned data, and the internal state of the model at the time the data was output are acquired. The acquired data and the internal state are stored. The in-vehicle information processing device according to claim 5.

9. The verification unit, Based on the data and internal state stored by the scenario execution unit, the load factor or communication delay related to network communication is calculated. Depending on whether the calculated load factor or communication delay meets a predetermined standard, the simulation result is determined to be positive or negative. The in-vehicle information processing device according to claim 8.

10. An in-vehicle relay device having a relay unit that relays the transmission and reception of data between multiple communication lines constituting an in-vehicle network, An in-vehicle information processing device having: a detection unit for detecting the connection of an in-vehicle communication device to a network within a vehicle; a creation unit for creating a routing map for the in-vehicle relay device, which relays data transmission and reception on the network, to determine the data relay destination when the connection of the in-vehicle communication device is detected; a verification unit for verifying the communication of the network using the created routing map through simulation; and an update unit for updating the routing map of the in-vehicle relay device with the created routing map when a positive verification result is obtained. An information processing system equipped with the following features.

11. The in-vehicle information processing system The system detects the connection of the in-vehicle communication device to the network within the vehicle. When the connection of the in-vehicle communication device is detected, a routing map is created to determine the relay destination of the data transmitted and received over the network. The communication of the network using the created routing map is verified by simulation. If a positive verification result is obtained, update the routing map. Information processing methods.

Images