Out-vehicle controller, in-vehicle controller, in-vehicle network update system, in-vehicle network update method, and program

Abstract

The invention provides an out-of-vehicle controller, an in-vehicle controller, an in-vehicle network update system, an in-vehicle network update method, and a program. A vehicle exterior controller (11) installed outside a vehicle (20) is provided with a vehicle exterior database (410) that associates configuration information of a plurality of vehicle-mounted networks (21) that configure different configurations with communication setting flags that respectively correspond to the plurality of vehicle-mounted networks (21). The outside-vehicle database (410) is updated as the configuration information is updated. An external controller (11) acquires configuration information of an in-vehicle network (21) in a vehicle (20). The external controller (11) refers to the acquired configuration information and an external database (410) and extracts a communication setting flag applied to the vehicle (20). The out-of-vehicle controller (11) notifies the in-vehicle controller (22) of the extracted communication setting flag.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to an off-vehicle controller, an in-vehicle controller, an in-vehicle network updating system, an in-vehicle network updating method, and a program using an SDN system. BACKGROUND

[0002] In Patent Literature 1, an SDN (Software Defined Networking) system capable of changing a configuration of a network, a communication setting without changing a configuration of hardware by controlling a communication device with software is described. The SDN network system has a plurality of SDN switches and an SDN controller that changes a setting of each of the plurality of SDN switches.

[0003] The SDN controller is a controller that controls a communication setting in the plurality of SDN switches. The SDN switch is a switch that performs data forwarding possessed on a network.

[0004] Patent Literature 1: Japanese Patent Application Publication No. 2017-169044

[0005] It is conceivable to utilize the SDN system described in Patent Literature 1 for an in-vehicle SDN network.

[0006] In a vehicle, a new in-vehicle device is sometimes additionally connected for the purpose of adding a function or the like. In addition, software of the in-vehicle device is sometimes updated due to upgrading. The configuration of the in-vehicle SDN network is sometimes changed due to the addition of the new in-vehicle device, the addition of a function by the update of the software. Even in the case where the configuration of the in-vehicle SDN network is changed, the SDN controller can control the in-vehicle SDN network by appropriately changing the communication setting of the SDN switch.

[0007] The SDN controller needs to have a database in which configuration information of the in-vehicle SDN network such as topology information of the in-vehicle device, version information of the software, and a communication setting of the SDN switch in the vehicle correspond to each other in order to control the in-vehicle SDN network.

[0008] The database stores information indicating a plurality of communication settings corresponding to a plurality of in-vehicle SDN networks having different configurations in order to have versatility for the addition of the in-vehicle device for expanding a function, different types of vehicles.

[0009] Therefore, in order to keep the database in the latest state, even in the case where unused information indicating a communication setting, and an update of unused software are performed in a certain vehicle, the database needs to be updated. Therefore, the number of times of actual update of the database becomes larger compared to the case where only a necessary update is performed in a certain vehicle.

[0010] There is a possibility that driving of the vehicle cannot be performed during upgrading of data in the vehicle. That is, it is necessary to reduce the number of times of upgrading of data in the vehicle. SUMMARY

[0011] In one embodiment of the present disclosure, an off-vehicle controller equipped outside a vehicle is provided.

[0012] The off-vehicle controller has an off-vehicle database in which information on configurations of a plurality of in-vehicle networks different in configuration and information on communication settings corresponding to the plurality of in-vehicle networks are associated with each other.

[0013] The off-vehicle database is updated in association with updating of the information on configurations.

[0014] The off-vehicle controller is configured to perform the following processing:

[0015] acquire the information on configurations of the in-vehicle networks in the vehicle;

[0016] refer to the acquired information on configurations and the off-vehicle database to extract information on the communication settings applied to the vehicle; and

[0017] notify the extracted information on the communication settings to an in-vehicle controller equipped in the vehicle.

[0018] In another embodiment of the present disclosure, an in-vehicle controller equipped in a vehicle is provided.

[0019] The in-vehicle controller is configured to perform the following processing: control communication settings of a plurality of switches each serving as a data forwarding device on an in-vehicle network equipped in the vehicle, based on information on communication settings notified from an off-vehicle controller equipped outside the vehicle.

[0020] In another embodiment of the present disclosure, a vehicle network updating system having the off-vehicle controller and the in-vehicle controller described above is provided.

[0021] In another embodiment of the present disclosure, a vehicle network updating method performed by a vehicle network updating system having an off-vehicle controller equipped outside a vehicle and an in-vehicle controller equipped in the vehicle is provided.

[0022] The vehicle network updating method includes:

[0023] In a first step, the off-vehicle controller having an off-vehicle database in which information on configurations of a plurality of in-vehicle networks different in configuration and information on communication settings corresponding to the plurality of in-vehicle networks are associated with each other acquires the information on configurations in the vehicle;

[0024] Step 2, the above-mentioned off-vehicle controller refers to the above-mentioned acquired configuration information and the above-mentioned off-vehicle database to extract information indicating the above-mentioned communication settings applied to the above-mentioned vehicle;

[0025] Step 3, the above-mentioned off-vehicle controller notifies the above-mentioned in-vehicle controller of the extracted information indicating the above-mentioned communication settings; and

[0026] Step 4, the above-mentioned in-vehicle controller controls the communication settings of each of a plurality of switches as data forwarding devices on the above-mentioned in-vehicle network equipped in the above-mentioned vehicle based on the notified information indicating the above-mentioned communication settings.

[0027] In another other aspect of the present disclosure, a program executed by an off-vehicle controller equipped outside a vehicle is provided.

[0028] The program causes the above-mentioned off-vehicle controller having an off-vehicle database in which configuration information of a plurality of in-vehicle networks having different configurations and information indicating communication settings corresponding to each of the above-mentioned plurality of in-vehicle networks are associated with each other to perform the following processing:

[0029] acquire the above-mentioned configuration information in the above-mentioned vehicle;

[0030] refer to the acquired above-mentioned configuration information and the above-mentioned off-vehicle database to extract information indicating the above-mentioned communication settings applied to the above-mentioned vehicle; and

[0031] notify the in-vehicle controller possessed by the above-mentioned vehicle of the extracted information indicating the above-mentioned communication settings.

[0032] In another other aspect of the present disclosure, a program executed by an in-vehicle controller equipped in a vehicle is provided.

[0033] The program causes the above-mentioned in-vehicle controller to perform the following processing: control the communication settings of each of a plurality of switches as data forwarding devices on an in-vehicle network equipped in the above-mentioned vehicle based on information indicating communication settings notified from an off-vehicle controller equipped outside the above-mentioned vehicle. BRIEF DESCRIPTION OF DRAWINGS

[0034] Figure 1 is a diagram showing an in-vehicle SDN network update system.

[0035] Figure 2 is a diagram showing the configuration of an in-vehicle SDN network provided with an in-vehicle controller and in-vehicle devices.

[0036] Figure 3 is a diagram showing an update action in network settings when the in-vehicle controller holds a database.

[0037] Figure 4 is a diagram showing Figure 3Table of one example of the database shown in FIG. 1.

[0038] Figure 5 Table of one example of the database shown in FIG. 1.

[0039] Figure 6 Table of one example of the database shown in FIG. 1. Figure 3 Table of one example of the updated database which has been updated with respect to the off-vehicle database shown in FIG. 1.

[0040] Figure 7 FIG. 2 is a schematic diagram of one example of the update action in the network setting when the off-vehicle controller has the off-vehicle database and the on-vehicle controller has the on-vehicle database.

[0041] Figure 8 Table of one example of the off-vehicle database possessed by the off-vehicle controller shown in FIG. 1. Figure 7

[0042] Table of one example of the off-vehicle database possessed by the off-vehicle controller shown in FIG. 1. Figure 9 Figure 7 Table of one example of the on-vehicle database possessed by the on-vehicle controller shown in FIG. 1.

[0043] Figure 10 Table of one example of the updated off-vehicle database which has been updated with respect to the off-vehicle database shown in FIG. 1. Figure 7

[0044] FIG. 3 is a schematic diagram of one example of the update action in the on-vehicle SDN network when only the off-vehicle controller has the database. Figure 11 DETAILED DESCRIPTION

[0045] Hereinafter, the off-vehicle SDN network update system 1 will be described with reference to FIG. 1. Figures 1-10 One embodiment of the on-vehicle SDN network update system will be described.

[0046] <Summary of on-vehicle SDN network update system 1>

[0047] Figure 1 A schematic diagram of the on-vehicle SDN network update system 1 is shown. As shown in FIG. 1, the on-vehicle SDN network update system 1 includes an off-vehicle controller 10 and an on-vehicle controller 20. Figure 1 ​​As shown, the vehicle-mounted SDN network update system 1 is a vehicle-mounted network update system comprising a server 10, multiple vehicles 20, and an external communication network 30. The server 10 includes an external controller 11 and a communication device 12. Each vehicle 20 has an vehicle-mounted SDN network 21. An in-vehicle communication device 23 is connected to each vehicle's SDN network 21. The server 10 is connected to the in-vehicle SDN network 21 of each vehicle 20 via the communication device 12, the external communication network 30, and the in-vehicle communication device 23. The external communication network 30 is, for example, a wireless communication network such as a mobile phone network. Therefore, the server 10 and each vehicle 20 can communicate with each other via the external communication network 30.

[0048] The external controller 11 has a CPU and a ROM. The CPU executes the program stored in the ROM.

[0049] <Overview of 21-bit in-vehicle SDN network>

[0050] like Figure 2 As shown, the in-vehicle SDN network 21 in vehicle 20 is an in-vehicle network comprising an in-vehicle controller 22 (acting as an SDN controller), an in-vehicle communication device 23, multiple SDN switches 24, and multiple in-vehicle devices 25. Each in-vehicle device 25 is controlled by software 26 installed on each in-vehicle device 25. The in-vehicle devices 25 include various ECUs (Electronic Control Units), engines, brakes, motors, sensors, and car navigation systems installed in vehicle 20. The in-vehicle devices 25 are connected to the in-vehicle SDN network 21 via PnP (Plug and Play).

[0051] The SDN switch 24 and the vehicle-mounted equipment 25 are communication devices for frame communication. Frame communication here refers to at least one of the following: frame forwarding, frame transmission, and frame reception.

[0052] The vehicle controller 22 controls the communication settings in the vehicle SDN network 21. For example, when the configuration of the vehicle SDN network 21 changes, such as when a new vehicle device 25 is connected, the vehicle controller 22 updates the communication settings. At this time, the vehicle controller 22 sends the communication settings that determine the data communication path to each SDN switch 24 equipped on the vehicle SDN network 21. In this way, the vehicle controller 22 centrally manages the communication settings of the multiple SDN switches 24 equipped on the vehicle SDN network 21. The vehicle controller 22 sends the data that the SDN switches 24 should forward.

[0053] The vehicle-mounted communication device 23 establishes data communication with the external controller 11 via the external communication network 30. Figure 2In this configuration, the vehicle communication device 23 is directly connected to the vehicle controller 22. Alternatively, the vehicle communication device 23 can also be connected to the vehicle controller 22 via an SDN switch 24.

[0054] SDN switch 24 is a data forwarding device that forwards data on the vehicle-mounted SDN network 21. Specifically, SDN switch 24 updates the rules for data forwarding stored in its own process table based on information received from the vehicle controller 22. Then, SDN switch 24 forwards the data received from the vehicle controller 22 to the appropriate vehicle device 25 based on the updated rules. Hereinafter, when referring to each SDN switch 24 separately, they will be referred to as SDN switch 24-1, SDN switch 24-2, SDN switch 24-3, and SDN switch 24-4.

[0055] <Regarding the vehicle controller 22 having database 400>

[0056] like Figure 3 As shown, as a comparative example, consider the case where the vehicle controller 22 has a database 400. In this case, the vehicle SDN network 21 in the vehicle 20 includes the vehicle controller 22, the vehicle communication device 23, and the PnP master 110.

[0057] Database 400 is used to store the configuration information of the multiple vehicle-mounted SDN networks 21 that constitute different vehicles and the communication settings of each SDN switch 24 equipped on each vehicle-mounted SDN network 21.

[0058] Here, the configuration information of the vehicular SDN network 21 refers to the topology information 100 and software information 200 of the vehicular devices 25 in the vehicular SDN network 21. The software information 200, for example, refers to the version information of each software 26 possessed by each vehicular device 25. Information indicating communication settings, for example, refers to the communication settings of each SDN switch 24 in the vehicular SDN network 21 that determines the data communication path on the network.

[0059] The vehicle controller 22 obtains topology information 100 from the PnP master controller 110 on the vehicle SDN network 21. The PnP master controller 110 manages which port on the vehicle SDN network 21 each vehicle device 25 is connected to. That is, the PnP master controller 110 manages the topology information 100. For example, if a new vehicle device 25 is connected to the vehicle SDN network 21, the PnP master controller 110 notifies the vehicle controller 22 that the topology information 100 has changed.

[0060] The vehicle controller 22 obtains software information 200 from a software management system 220 located outside the vehicle via an external communication network 30. The software management system 220 manages the version information of the software 26 of the vehicle devices 25. When a new version of the software 26 is released, the software management system 220 notifies the vehicle controller 22 of the software information 200 via the external communication network 30. The software management system 220 possesses multiple pieces of software information 200 corresponding to multiple pieces of software 26 in multiple vehicle devices 25.

[0061] Since there are multiple software information 200 corresponding to multiple vehicle-mounted devices 25, when distinguishing and recording each software information 200 below, they will be recorded as the first software information 201 and the second software information 202.

[0062] The vehicle controller 22 retrieves the communication settings of each SDN switch 24 by referring to the topology information 100 notified from the PnP master controller 110 and the software information 200 and database 400 notified from the software management system 220. Then, the vehicle controller 22 controls the communication settings of each SDN switch 24 on the vehicle SDN network 21 equipped in the vehicle 20 based on the retrieved communication settings.

[0063] <Specific examples of information stored in database 400>

[0064] like Figure 4 As shown, the database 400 exemplified here stores two types of information, "T_1" and "T_2," for topology information 100. That is, database 400 stores communication settings corresponding to two topologies with different connection methods to the vehicle-mounted device 25. Similarly, database 400 stores three types of information, "S_1_1," "S_1_2," and "S_1_3," for the first software information 201. That is, database 400 stores three different versions of information for the first software information 201. Furthermore, database 400 stores only one type of information, "S_2_1," for the second software information 202. That is, database 400 stores only one version of information as the second software information 202.

[0065] like Figure 4 As shown, the database 400 stores the communication settings of each SDN switch 24 corresponding to each combination of topology information 100, first software information 201, and second software information 202.

[0066] The communication settings for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_1", first software information 201 is "S_1_1", and second software information 202 is "S_2_1", are set to "Conf_1". The communication settings for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_2", first software information 201 is "S_1_1", and second software information 202 is "S_2_1", are set to "Conf_2". The communication settings for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_1", first software information 201 is "S_1_2", and second software information 202 is "S_2_1", are set to "Conf_1". The communication settings for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_2", first software information 201 is "S_1_2", and second software information 202 is "S_2_1", are set to "Conf_2". The communication settings for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_1", first software information 201 is "S_1_3", and second software information 202 is "S_2_1", are set to "Conf_3". The communication settings for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_2", first software information 201 is "S_1_3", and second software information 202 is "S_2_1", are set to "Conf_3".

[0067] like Figure 5 As shown, the vehicle controller 22 operates each SDN switch 24 based on the extracted communication settings of each SDN switch 24, namely "Conf_1", "Conf_2", or "Conf_3". When the communication setting of each SDN switch 24 applied to the vehicle SDN network 21 is "Conf_1", the first SDN switch 24_1 and the second SDN switch 24_2 operate. When the communication setting of each SDN switch 24 applied is "Conf_2", the first SDN switch 24_1, the second SDN switch 24_2, and the fourth SDN switch 24_4 operate. When the communication setting of each SDN switch 24 applied is "Conf_3", the first SDN switch 24_1 and the third SDN switch 24_3 operate.

[0068] like Figure 4 As shown, even if the combinations of topology information 100, first software information 201 and second software information 202 are different, the communication settings of each SDN switch 24 applied to the vehicle SDN network 21 are sometimes the same.

[0069] For example, regardingFigure 4 The two lines shown in the middle, surrounded by dashed lines, are different even though the first software information 201 is "S_1_1" and "S_1_2". The communication settings of each SDN switch 24 that are applied are "Conf_1".

[0070] <Regarding database 400 update>

[0071] If the latest topology information 100 and the latest software information 200 are not present in the database 400 of the vehicle controller 22, the vehicle controller 22 updates the database 400.

[0072] For example, assuming a database update (400) is required, a new version of software 26 is released. The software management system 220 sends the new version of software 26 to the vehicle controller 22. The vehicle controller 22 downloads the new software 26. Then, the vehicle controller 22 installs the new software 26 onto the corresponding vehicle device 25.

[0073] The software management system 220 notifies the vehicle controller 22 of the latest software information 200. The vehicle controller 22 updates the database 400 to include the notified latest software information 200, thus creating an updated database 401.

[0074] The vehicle controller 22 retrieves the communication settings of each SDN switch 24 by referring to the topology information 100 notified from the PnP master controller 110, the software information 200 notified from the software management system 220, and the updated database 401. Then, the vehicle controller 22 controls the communication settings of each SDN switch 24 on the vehicle-mounted SDN network 21 equipped in the vehicle 20 based on the retrieved communication settings.

[0075] <Specific examples of database 400 updates>

[0076] Imagine the scenario where software information 202 is updated. For example... Figure 6 As shown, in the updated database 401, "S_2_2" was appended to the second software information 202. The first to sixth lines of the updated database 401 are... Figure 4 The database shown is the same as 400. Figure 6The range enclosed by dashed lines represents the range appended to the updated database 401. The communication setting for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_1", first software information 201 is "S_1_1", and second software information 202 is "S_2_2", is "Conf_1". The communication setting for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_2", first software information 201 is "S_1_1", and second software information 202 is "S_2_2", is "Conf_2". The communication setting for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_1", first software information 201 is "S_1_2", and second software information 202 is "S_2_2", is "Conf_1". The communication setting for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_2", first software information 201 is "S_1_2", and second software information 202 is "S_2_2", is "Conf_2". The communication setting for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_1", first software information 201 is "S_1_3", and second software information 202 is "S_2_2", is "Conf_3". The communication setting for each SDN switch 24 of the vehicular SDN network 21, where topology information 100 is "T_2", first software information 201 is "S_1_3", and second software information 202 is "S_2_2", is "Conf_3".

[0077] <Issues related to database 400 updates>

[0078] The database 400 of the vehicle controller 22 stores communication settings corresponding to multiple vehicle SDN networks 21 that are different from the topology information 100 and software information 200. Therefore, the database 400 has the versatility to accommodate the additional installation of vehicle equipment 25 for expanded functions and the use of vehicles 20 of different specifications.

[0079] Therefore, in order to keep the database 400 up-to-date, the database 400 needs to be updated even if unused communication settings or unused software 26 in a certain vehicle 20 are updated.

[0080] For example, when new topology information 100 is added to database 400, database 400 is updated to correspond to the added topology information 100.

[0081] For example, when any piece of software information 200 is updated, the database 400 is updated in order to correspond to the new piece of software information 200.

[0082] For example, when the corresponding software 26 is added to the database 400, the database 400 is updated in order to add the software information 200 in the new software 26.

[0083] Therefore, the actual number of updates to the database 400 is increased compared to the case where only necessary updates are performed in a certain vehicle 20.

[0084] The updates to database 400 also include some updates that are not needed by vehicle 20. For example, the software information 200 of onboard equipment 25, which is not installed in vehicle 20, is sometimes updated.

[0085] When updating the database 400, the external controller 11 needs to send activity information related to the database 400 update and distribute data packets to the vehicles 20. That is, when the onboard controllers 22 installed in multiple vehicles 20 have the database 400, the server 10 must send activity information and distribute data packets to the multiple vehicles 20 at a high frequency. This creates the problem of high-frequency data upgrades occurring in each vehicle 20.

[0086] <Vehicle-mounted SDN network update system 1 in this embodiment>

[0087] like Figure 7 As shown, in this embodiment, the vehicle-mounted SDN network update system 1 has an external controller 11 on the server 10 with an external database 410. Furthermore, the vehicle-mounted SDN network update system 1 has an onboard controller 22 on the vehicle-mounted SDN network 21 with an onboard database 420.

[0088] Server 10 has a software management system 220. The software management system 220 stores multiple software information 200 for multiple vehicles 20.

[0089] For example, consider a scenario where a new onboard device 25 is connected to the vehicular SDN network 21 in vehicle 20. In this case, the topology information 100 in vehicle 20 is changed.

[0090] The PnP master controller 110 notifies the external controller 11 of the changed topology information 100. The external controller 11 extracts the communication setting flag by referring to the notified topology information 100, the software information 200 obtained from the software management system 220, and the external database 410. Then, the external controller 11 notifies the on-board controller 22 in the vehicle 20 of the extracted communication setting flag.

[0091] The vehicle controller 22 retrieves the communication settings of each SDN switch 24 corresponding to the communication setting flags by referring to the communication setting flags notified from the external controller 11 and the vehicle database 420. Then, the vehicle controller 22 controls the communication settings of each SDN switch 24 on the vehicle SDN network 21 equipped in the vehicle 20 based on the retrieved communication settings.

[0092] <Specific examples of information stored in the vehicle external database 410>

[0093] like Figure 8 As shown, the external database 410 stores topology information 100, first software information 201, and second software information 202. Furthermore, the external database 410 stores communication setting flags corresponding to the combination of topology information 100, first software information 201, and second software information 202.

[0094] When topology information 100 is "T_1", first software information 201 is "S_1_1", and second software information 202 is "S_2_1", the communication setting flag notified to the vehicle controller 22 is "Flag_1". When topology information 100 is "T_2", first software information 201 is "S_1_1", and second software information 202 is "S_2_1", the communication setting flag notified to the vehicle controller 22 is "Flag_2". When topology information 100 is "T_1", first software information 201 is "S_1_2", and second software information 202 is "S_2_1", the communication setting flag notified to the vehicle controller 22 is "Flag_1". When topology information 100 is "T_2", first software information 201 is "S_1_2", and second software information 202 is "S_2_1", the communication setting flag notified to the vehicle controller 22 is "Flag_1". When topology information 100 is "T_1", first software information 201 is "S_1_3", and second software information 202 is "S_2_1", the communication setting flag notified to the vehicle controller 22 is "Flag_3". When topology information 100 is "T_2", first software information 201 is "S_1_3", and second software information 202 is "S_2_1", the communication setting flag notified to the vehicle controller 22 is "Flag_3".

[0095] For example, such as Figure 8As shown in the diagram enclosed by dashed lines, imagine a scenario where the external controller 11 obtains "T_1" as topology information 100, "S_1_2" as first software information 201, and "S_2_1" as second software information 202. In this case, the external controller 11 refers to the obtained configuration information and the external database 410. As a result, the external controller 11 extracts "Flag_1" as a communication setting flag.

[0096] like Figure 9 As shown by the dashed line, when the external controller 11 notifies the in-vehicle controller 22 of "Flag_1" as a communication setting flag, the in-vehicle controller 22 retrieves "Conf_1" as the communication setting. When the external controller 11 notifies the in-vehicle controller 22 of "Flag_2" as a communication setting flag, the in-vehicle controller 22 retrieves "Conf_2" as the communication setting. When the external controller 11 notifies the in-vehicle controller 22 of "Flag_3" as a communication setting flag, the in-vehicle controller 22 retrieves "Conf_3" as the communication setting.

[0097] like Figure 5 As shown, when the vehicle controller 22 extracts "Conf_1" as a communication setting, the vehicle controller 22 activates the first SDN switch 24_1 and the second SDN switch 24_2. When the vehicle controller 22 extracts "Conf_2" as a communication setting, the vehicle controller 22 activates the first SDN switch 24_1, the second SDN switch 24_2, and the fourth SDN switch 24_4. When the vehicle controller 22 extracts "Conf_3" as a communication setting, the vehicle controller 22 activates the first SDN switch 24_1 and the third SDN switch 24_3.

[0098] <Update regarding vehicle exterior database 410>

[0099] For example, when the existing software 26 is upgraded, the software management system 220 sends the upgraded software 26 to the vehicle controller 22 in the vehicle 20. Furthermore, when the existing software 26 is upgraded, the software management system 220 notifies the external controller 11 of the version information of the software 26. That is, the software management system 220 notifies the external controller 11 of the software information 200.

[0100] For example, suppose the software management system 220 detects an upgrade in the existing software 26. In this case, the software management system 220 retrieves the information from the vehicle 20 that is using the detected upgraded software 26. Then, the software management system 220 sends the new version of software 26 to the vehicle controller 22 in the vehicle 20 that is using the detected upgraded software 26. The vehicle controller 22 installs the new version of software 26 on the corresponding vehicle device 25. In addition, the software management system 220 notifies the external controller 11 of software information 200 containing the new version of software 26.

[0101] Then, the external controller 11 updates the external database 410 based on the notified software information 200. The external controller 11 retrieves the communication setting flag by referring to the notified software information 200 and the external database 410. Afterward, the external controller 11 notifies the on-board controller 22 in the vehicle 20, which has undergone software 26 upgrade, of the communication setting flag.

[0102] The vehicle controller 22 retrieves the communication settings of each SDN switch 24 corresponding to the communication setting flags by referring to the communication setting flags notified from the external controller 11 and the vehicle database 420. Then, the vehicle controller 22 controls the communication settings of each SDN switch 24 on the vehicle SDN network 21 equipped in the vehicle 20 based on the retrieved communication settings.

[0103] like Figure 10 As shown, imagine a scenario where "S_2_2" is appended to the second software information 202 in the updated external vehicle database 411 due to an update of the external vehicle database 410. The first to sixth lines of the updated external vehicle database 411 are... Figure 8 The external database shown is the same as 410.

[0104] like Figure 10As shown in the dashed lines, when topology information 100 is "T_1", first software information 201 is "S_1_1", and second software information 202 is "S_2_2", the communication setting flag notified to the vehicle controller 22 is "Flag_1". When topology information 100 is "T_2", first software information 201 is "S_1_1", and second software information 202 is "S_2_2", the communication setting flag notified to the vehicle controller 22 is "Flag_2". When topology information 100 is "T_1", first software information 201 is "S_1_2", and second software information 202 is "S_2_2", the communication setting flag notified to the vehicle controller 22 is "Flag_1". When topology information 100 is "T_2", first software information 201 is "S_1_2", and second software information 202 is "S_2_2", the communication setting flag notified to the vehicle controller 22 is "Flag_1". When topology information 100 is "T_1", first software information 201 is "S_1_3", and second software information 202 is "S_2_2", the communication setting flag notified to the vehicle controller 22 is "Flag_3". When topology information 100 is "T_2", first software information 201 is "S_1_3", and second software information 202 is "S_2_2", the communication setting flag notified to the vehicle controller 22 is "Flag_3".

[0105] like Figure 9 As shown in the dashed line, when the external controller 11 notifies the in-vehicle controller 22 of "Flag_1" as a communication setting flag, the in-vehicle controller 22 retrieves "Conf_1" as the communication setting. When the external controller 11 notifies the in-vehicle controller 22 of "Flag_2" as a communication setting flag, the in-vehicle controller 22 retrieves "Conf_2" as the communication setting. When the external controller 11 notifies the in-vehicle controller 22 of "Flag_3" as a communication setting flag, the in-vehicle controller 22 retrieves "Conf_3" as the communication setting.

[0106] like Figure 5 As shown, when the vehicle controller 22 extracts "Conf_1" as a communication setting, the vehicle controller 22 activates the first SDN switch 24_1 and the second SDN switch 24_2. When the vehicle controller 22 extracts "Conf_2" as a communication setting, the vehicle controller 22 activates the first SDN switch 24_1, the second SDN switch 24_2, and the fourth SDN switch 24_4. When the vehicle controller 22 extracts "Conf_3" as a communication setting, the vehicle controller 22 activates the first SDN switch 24_1 and the third SDN switch 24_3.

[0107] <The function of this implementation method>

[0108] The vehicle-mounted SDN network update system 1 of this embodiment includes an external controller 11 located outside the vehicle 20. The external controller 11 includes an external database 410. The external database 410 is capable of handling the addition of optional equipment for expanded functionality and is compatible with different vehicle 20 specifications. The external database 410 is updated frequently, for example, to accommodate the addition of new vehicle-mounted equipment 25 and software version upgrades 26.

[0109] The vehicle-mounted SDN network update system 1 of this embodiment includes an onboard controller 22 in the vehicle 20. The onboard controller 22 includes an onboard database 420. In this embodiment, the onboard database 420 stores communication setting flags and the communication settings of each SDN switch 24 in the onboard SDN network 21 in a corresponding manner. That is, the onboard database 420 only needs to be updated when the communication setting flags or the communication settings of each SDN switch 24 are increased. Therefore, as referred to... Figure 4 and Figure 5 As explained, compared to the case where the vehicle controller 22 has a database 400, the frequency of data updates in the vehicle 20 is reduced when the vehicle controller 22 has a vehicle database 420.

[0110] <Effects of this implementation method>

[0111] (1) The vehicle-mounted SDN network update system 1 can reduce the frequency of data upgrades in the vehicle 20.

[0112] (2) When the external controller 11 stores configuration information and communication settings information for each vehicle 20 individually, the external controller 11 needs to store configuration information and communication settings information corresponding to the number of vehicles 20. In addition, when the configuration information is updated due to the release of new software 26, the external controller 11 needs to update the configuration information stored for each vehicle 20 individually according to the number of vehicles 20.

[0113] The external database 410 establishes a correspondence between the configuration information of the multiple in-vehicle SDN networks 21 that constitute different vehicles and the information representing the communication settings corresponding to each of the multiple in-vehicle SDN networks 21. That is, the external database 410 stores the information in an organized state according to each type of in-vehicle SDN network 21. In this way, the external controller 11 stores the external database 410 corresponding to multiple vehicles 20. Therefore, compared to the case where the external controller 11 stores the configuration information and the information representing the communication settings for each vehicle 20 separately, the amount of data stored by the external controller 11 is reduced.

[0114] When the configuration information is updated due to the release of new software 26, the external controller 11 updates the external database 410. Thus, compared to the case where the external controller 11 updates the configuration information stored individually for each vehicle 20, the update can be completed with less communication.

[0115] (3) The vehicle-mounted SDN network update method executed by the vehicle-mounted SDN network update system 1 is a vehicle-mounted network update method. The vehicle-mounted SDN network update method includes a first step in which the external controller 11 obtains configuration information in the vehicle 20. The vehicle-mounted SDN network update method includes a second step in which the external controller 11 extracts a communication setting flag, which represents information applied to the communication settings of the vehicle 20, by referring to the obtained configuration information and the external database 410. The vehicle-mounted SDN network update method includes a third step in which the external controller 11 notifies the vehicle-mounted controller 22 of the extracted communication setting flag. The vehicle-mounted SDN network update method includes a fourth step in which the vehicle-mounted controller 22 controls the communication settings of each SDN switch 24 equipped on the vehicle-mounted SDN network in the vehicle 20 based on the notified communication setting flag. The fourth step of the vehicle-mounted SDN network update method consists of the following fifth and sixth steps. The vehicle-mounted SDN network update method includes a fifth step in which the vehicle controller 22 extracts the communication settings of the vehicle-mounted SDN network 21 corresponding to the communication setting flag by referring to the notified communication setting flag and the vehicle database 420. The vehicle-mounted SDN network update method also includes a sixth step in which the vehicle controller 22 controls the communication settings of the SDN switch 24 on the vehicle-mounted SDN network 21 equipped in the vehicle 20 based on the extracted communication settings.

[0116] By implementing this in-vehicle SDN network update method, the in-vehicle SDN network update system 1 can reduce the frequency of data upgrades in the vehicle 20.

[0117] (4) The external controller 11 has an external database 410 that establishes configuration information for multiple different vehicle-mounted SDN networks 21 and communication setting flags corresponding to each of the multiple vehicle-mounted SDN networks 21. The external database 410 is updated as the configuration information is updated. The external controller 11 obtains the configuration information in the vehicle 20. Then, the external controller 11 extracts the communication setting flags applied to the vehicle 20 by referring to the obtained configuration information and the external database 410. Furthermore, the external controller 11 notifies the vehicle-mounted controller 22 equipped in the vehicle 20 of the extracted communication setting flags.

[0118] The external database 410 needs to be able to cope with the addition of optional equipment for expanded functions and the versatility of different vehicle specifications 20. For example, in order to cope with the addition of new optional equipment and the upgrade of software 26, the external database 410 stored in the external controller 11 is updated frequently.

[0119] According to the aforementioned external controller 11, the database 400, which is updated frequently, does not need to be installed in the vehicle 20. Therefore, the aforementioned external controller 11 can reduce the frequency of data upgrades in the vehicle 20.

[0120] (5) The vehicle controller 22 has an on-board database 420 that establishes corresponding on-board databases for communication setting flags and communication settings of each SDN switch 24 equipped on each on-board SDN network 21. The vehicle controller 22 extracts the communication settings of each SDN switch 24 corresponding to the communication setting flags by referring to the communication setting flags notified from the external controller 11 and the on-board database 420. The vehicle controller 22 controls the communication settings of each SDN switch 24 on the on-board SDN network 21 equipped in the vehicle 20 based on the extracted communication settings.

[0121] The vehicle controller 22 controls the communication settings of each SDN switch 24 equipped on the network in the vehicle 20 based on the communication setting flags notified from the external controller 11.

[0122] For reference Figures 3-6 As illustrated in the comparative example, when the vehicle controller 22 has a database 400 that is updated frequently, the data in the vehicle 20 is upgraded frequently in order to update the database 400. In contrast, the vehicle controller 22 of this embodiment controls the SDN switch 24 based on a communication setting flag notified from the external controller 11.

[0123] That is, according to this embodiment, the vehicle controller 22 can control communication settings even without a database 400 that is updated frequently. Therefore, the vehicle controller 22 can reduce the frequency of data updates in the vehicle 20.

[0124] (6) In this embodiment, the program executed by the external controller 11 enables the external controller 11 to obtain configuration information in the vehicle 20. The program enables the external controller 11 to extract communication setting flags applied to the vehicle 20 by referring to the obtained configuration information and the external database 410. The program enables the external controller 11 to notify the on-board controller 22 of the extracted communication setting flags.

[0125] According to the program executed by the external controller 11, the database 400, which is updated frequently, does not need to be installed in the vehicle 20. Therefore, the program executed by the external controller 11 can reduce the frequency of data updates in the vehicle 20.

[0126] (7) In this embodiment, the program executed by the vehicle controller 22 causes the vehicle controller 22 to control the communication settings of the SDN switch 24 equipped on the network in the vehicle 20 based on the communication setting flags notified from the external controller 11.

[0127] According to this program, even without a database 400 that is updated frequently, the vehicle controller 22 can control the communication settings of the SDN switch 24. Therefore, the program executed by the vehicle controller 22 can reduce the frequency of data upgrades in the vehicle 20.

[0128] <Example of Change>

[0129] This embodiment can be implemented by modification as follows. This embodiment and the following modifications can be combined with each other within a technically compatible scope.

[0130] <Regarding the situation where the external controller 11 notifies the vehicle controller 22 of the communication settings of the SDN switch 24>

[0131] In the above embodiment, the external controller 11 notifies the on-board controller 22 of communication setting flags as information indicating communication settings. Conversely, the external controller 11 may also notify the on-board controller 22 of information other than communication setting flags as information indicating communication settings. For example, the external controller 11 may notify the on-board controller 22 of the communication settings of each SDN switch 24 equipped on the on-board SDN network 21 as information indicating communication settings applied to the vehicle 20. That is, the external controller 11 may notify the on-board controller 22 of information summarizing the communication settings of each SDN switch 24 equipped on the on-board SDN network 21.

[0132] like Figure 11 As shown, in this modified example, the vehicle-mounted SDN network update system 1 has a database 400 on the external controller 11 of the server 10. The server 10 has a software management system 220. The software management system 220 stores multiple software information 200 from multiple vehicles 20.

[0133] For example, consider a scenario where a new in-vehicle device 25 is connected to the in-vehicle SDN network 21 in vehicle 20. In this case, the topology information 100 in vehicle 20 is changed. The PnP master controller 110 notifies the external controller 11 of the changed topology information 100.

[0134] The external controller 11 retrieves the communication settings of each SDN switch 24 by referring to the notified topology information 100 and the software information 200 and database 400 obtained from the software management system 220. Then, the external controller 11 notifies the on-board controller 22 in the vehicle 20 of the communication settings of each SDN switch 24.

[0135] The vehicle controller 22 controls the communication settings of each SDN switch 24 based on the notified communication settings.

[0136] like Figure 4 As shown, the database 400 stores the communication settings of each SDN switch 24 corresponding to each combination of topology information 100, first software information 201 and second software information 202.

[0137] When topology information 100 is "T_1", first software information 201 is "S_1_1", and second software information 202 is "S_2_1", the communication setting notified to each SDN switch 24 of the vehicle controller 22 is "Conf_1". When topology information 100 is "T_2", first software information 201 is "S_1_1", and second software information 202 is "S_2_1", the communication setting notified to each SDN switch 24 of the vehicle controller 22 is "Conf_2". When topology information 100 is "T_1", first software information 201 is "S_1_2", and second software information 202 is "S_2_1", the communication setting notified to each SDN switch 24 of the vehicle controller 22 is "Conf_1". When topology information 100 is "T_2", first software information 201 is "S_1_2", and second software information 202 is "S_2_1", the communication setting notified to each SDN switch 24 of the vehicle controller 22 is "Conf_2". When topology information 100 is "T_1", first software information 201 is "S_1_3", and second software information 202 is "S_2_1", the communication setting notified to each SDN switch 24 of the vehicle controller 22 is "Conf_3". When topology information 100 is "T_2", first software information 201 is "S_1_3", and second software information 202 is "S_2_1", the communication setting notified to each SDN switch 24 of the vehicle controller 22 is "Conf_3".

[0138] like Figure 5As shown, the vehicle controller 22 operates each SDN switch 24 based on the communication settings of the notified SDN switches 24, namely "Conf_1", "Conf_2", or "Conf_3". When the communication settings of the SDN switches 24 notified from the external controller are "Conf_1", the first SDN switch 24_1 and the second SDN switch 24_2 operate. When the communication settings of the notified SDN switches 24 are "Conf_2", the first SDN switch 24_1, the second SDN switch 24_2, and the fourth SDN switch 24_4 operate. When the communication settings of the notified SDN switches 24 are "Conf_3", the first SDN switch 24_1 and the third SDN switch 24_3 operate.

[0139] In this variation, the vehicle-mounted SDN network update method includes a first step whereby the external controller 11 obtains configuration information of the vehicle-mounted SDN network 21 in the vehicle 20. In this variation, the vehicle-mounted SDN network update method includes a second step whereby the external controller 11 extracts communication settings applied to each SDN switch 24 in the vehicle 20 by referring to the obtained configuration information and database 400. In this variation, the vehicle-mounted SDN network update method includes a third step whereby the external controller 11 notifies the vehicle-mounted controller 22 of the extracted communication settings of each SDN switch 24. In this variation, the vehicle-mounted SDN network update method includes a fourth step whereby the vehicle-mounted controller 22 controls the communication settings of each SDN switch 24 equipped in the vehicle-mounted SDN network 21 in the vehicle 20 based on the notified communication settings.

[0140] In this variation, the program executed by the external controller 11 causes it to obtain the configuration information of the on-board SDN network 21 in the vehicle 20. In this variation, the program executed by the external controller 11 causes it to extract information representing communication settings applied to the vehicle 20 by referring to the obtained configuration information and the database 400. In this variation, the program executed by the external controller 11 causes it to notify the on-board controller 22 equipped in the vehicle 20 of the extracted communication settings of each SDN switch 24.

[0141] In this variant, the program executed by the vehicle controller 22 causes the vehicle controller 22 to control the communication settings of each SDN switch 24 equipped on the vehicle SDN network 21 based on the communication settings notified from the external controller 11.

[0142] <Regarding the method of updating the vehicle-mounted SDN network system 1>

[0143] The vehicle-mounted SDN network update system 1 can also be applied to networks other than the vehicle-mounted SDN network 21 described in the above embodiments. For example, the vehicle-mounted SDN network update system 1 can be applied to a vehicle-mounted SDN network 21 with more than 5 SDN switches 24.

[0144] The vehicle-mounted SDN network update system 1 can also be equipped with a software management system 220 on a server 10 that is different from the server 10 equipped with the external controller 11. That is, the vehicle-mounted SDN network update system 1 can have multiple servers 10. In this case, the external controller 11 obtains software information 200 from the software management system 220 via an external communication line network 30 or wired communication.

[0145] <Method for obtaining topology information 100 by the external controller 11>

[0146] The external controller 11 can also obtain the topology information 100 of the vehicle 20 from outside the vehicle 20. For example, the external controller 11 can obtain the topology information 100 from the topology information management system equipped on the server 10.

[0147] The topology information management system is a system that stores multiple topology information 100 for multiple vehicles 20. The topology information management system notifies the external controller 11 of any vehicle 20 that is subject to changes to the topology information 100. In addition, the topology information management system notifies the external controller 11 of the topology information 100.

[0148] The external controller 11 extracts communication setting flags by referring to the topology information 100 obtained from the topology information management system, the software information 200 obtained from the software management system 220, and the external database 410. Then, the external controller 11 notifies the on-board controller 22 in the vehicle 20, which is the object of the change to the topology information 100, of the extracted communication setting flags.

[0149] The vehicle-mounted SDN network update system 1 can also be equipped with a topology information management system on a server 10 that is different from the server 10 equipped with the external controller 11. In this case, the external controller 11 obtains topology information 100 from the topology information management system via an external communication line network 30 or wired communication.

[0150] <Method for obtaining software information 200 by the vehicle external controller 11>

[0151] The external controller 11 can also obtain the software information 200 in the vehicle 20 from outside the software management system 220 equipped on the server 10. For example, the external controller 11 can obtain the software information 200 from the software management device provided with the vehicle 20.

[0152] The software management device manages the software information 200 of the on-board equipment 25 in the vehicle 20. The on-board controller 22 obtains the software information 200 from the software management device via the on-board SDN network 21. The on-board controller 22 notifies the external controller 11 of the obtained software information 200 via the on-board communication device 23 and the external communication line network 30.

[0153] The external controller 11 extracts communication setting flags by referring to the topology information 100 obtained from the PnP master controller 110, the software information 200 obtained from the software management device, and the external database 410. Then, the external controller 11 notifies the on-board controller 22 in the vehicle 20 equipped with the software management device of the extracted communication setting flags.

[0154] <Other>

[0155] The external controller 11 can be configured as a circuit containing one or more processors that perform various processes according to a computer program (software). The external controller 11 can also be configured as a circuit containing one or more application-specific integrated circuits (ASICs) or combinations thereof that perform at least some of the various processes. The processor includes a CPU and memories such as RAM and ROM. The memories store program code or instructions configured to cause the CPU to perform processes. Memory, or computer-readable medium, includes all available media that can be accessed by a general-purpose or special-purpose computer. The same applies to the onboard controller 22. Claims (as amended under Article 19 of the Treaty) 1. (Modified) An external vehicle controller, wherein the external vehicle controller is mounted outside the vehicle. The external controller is equipped with an external database that includes configuration information of multiple different in-vehicle networks and information representing communication settings corresponding to each of the multiple in-vehicle networks. The external vehicle database is updated along with the updates to the constituent information. The external controller is configured to perform the following processes: Obtain the configuration information of the in-vehicle network in the vehicle; Referring to the obtained configuration information and the external vehicle database, information representing the communication settings applied to the vehicle is extracted from the external vehicle database; and The information representing the communication settings extracted from the external database is notified to the onboard controller equipped in the vehicle. 2. The vehicle external controller according to claim 1, wherein, The external controller is equipped with an external database that establishes a corresponding configuration information and communication setting flags of the in-vehicle network. The external controller is configured to perform the following processes: The communication setting flag is extracted as the communication setting applied to the vehicle by referring to the configuration information applied to the vehicle and the external database; and The extracted communication setting flags are then sent to the vehicle controller. 3. (Modified) An on-board controller, wherein the on-board controller is installed in a vehicle. The vehicle controller is configured to perform the following process: control the communication settings of multiple switches that serve as data forwarding devices on the vehicle network based on information representing communication settings extracted from an external database. The external database is set in the external controller and establishes a correspondence between configuration information of multiple different vehicle networks and information representing communication settings corresponding to the multiple vehicle networks respectively. 4. The vehicle controller according to claim 3, wherein, The vehicle controller includes a vehicle database that establishes a corresponding communication setting flag, which represents the communication settings, and the communication settings of each switch equipped on the vehicle network. The vehicle controller is configured to perform the following processes: The communication settings of each switch corresponding to the communication setting flag are retrieved by referring to the communication setting flag notified from the external controller and the vehicle database; and The communication settings of each switch on the vehicle network equipped in the vehicle are controlled based on the extracted communication settings. 5. An in-vehicle network update system, wherein, It comprises the external controller as described in claim 1 and the on-board controller as described in claim 3. 6. The vehicle network update system according to claim 5, wherein, The external controller is configured to perform the following process: notify the onboard controller of a communication setting flag as information indicating the communication settings applied to the vehicle. The vehicle controller is equipped with a vehicle database that establishes corresponding communication setting flags and communication settings of each switch equipped on the vehicle network. The vehicle controller is configured to perform the following processes: The communication settings of each switch corresponding to the communication setting flag are retrieved by referring to the communication setting flag notified from the external controller and the vehicle database; and The communication settings of each switch on the vehicle network equipped in the vehicle are controlled based on the extracted communication settings. 7. (Modified) A method for updating an in-vehicle network, wherein the method is executed by an in-vehicle network update system, the in-vehicle network update system comprising an external controller mounted on the exterior of the vehicle and an in-vehicle controller mounted on the vehicle. The in-vehicle network update method includes: Step 1: The external controller, which is equipped with an external database that establishes a corresponding external database containing configuration information of multiple different in-vehicle networks and information representing communication settings corresponding to the multiple in-vehicle networks respectively, obtains the configuration information in the vehicle. In the second step, the external controller refers to the obtained configuration information and the external database to extract information representing the communication settings applied to the vehicle from the external database; In step 3, the external controller notifies the onboard controller of the communication settings information extracted from the external database; and In step 4, the vehicle controller controls the communication settings of the multiple switches that act as data forwarding devices on the vehicle network equipped in the vehicle based on the notified information indicating the communication settings. 8. The vehicle network update method according to claim 7, wherein, The third step is the step in which the external controller notifies the onboard controller of the communication setting flag as information indicating the communication settings applied to the vehicle. The fourth step consists of the following fifth and sixth steps. In the fifth step, the vehicle controller, which establishes a corresponding vehicle database for the communication setting flag and the communication settings of each switch equipped on the vehicle network, refers to the communication setting flag notified from the external controller and the vehicle database to extract the communication settings of each switch corresponding to the communication setting flag. In the sixth step, the vehicle controller controls the communication settings of each switch on the vehicle network equipped in the vehicle based on the extracted information representing the communication settings. 9. (Amended) A program, wherein the program is executed by an external controller mounted outside the vehicle. The external controller is equipped with an external database that includes configuration information of multiple different in-vehicle networks and information representing communication settings corresponding to each of the multiple in-vehicle networks. The program causes the external controller to perform the following processes: Obtain the configuration information of the vehicle; Referring to the obtained configuration information and the external vehicle database, information representing the communication settings applied to the vehicle is extracted from the external vehicle database; and The information representing the communication settings extracted from the external database is notified to the onboard controller equipped in the vehicle. 10. The procedure according to claim 9, wherein, The external controller is equipped with an external database that establishes a corresponding configuration information and communication setting flags of the in-vehicle network. The program causes the external controller to perform the following processes: The communication setting flag is extracted as information representing the communication setting by referring to the configuration information of the in-vehicle network applied to the vehicle and the external database; and The extracted communication setting flags are then sent to the vehicle controller. 11. (Modified) A program, wherein the program is executed by an onboard controller equipped in a vehicle, The program causes the vehicle controller to perform the following processing: control the communication settings of multiple switches that act as data forwarding devices on the vehicle network equipped in the vehicle based on information representing communication settings extracted from an external database. The external database is set in the external controller and establishes a correspondence between the configuration information of the multiple vehicle networks that constitute different networks and the information representing the communication settings corresponding to the multiple vehicle networks respectively. 12. The procedure according to claim 11, wherein, The vehicle controller is equipped with a vehicle database that establishes corresponding communication setting flags and communication settings of each switch equipped on the vehicle network. The program causes the vehicle controller to perform the following processes: The communication settings of each switch corresponding to the communication setting flag are retrieved by referring to the communication setting flag notified from the external controller and the vehicle database; and The communication settings of each switch on the vehicle network equipped in the vehicle are controlled based on the extracted communication settings.

Claims

1. An external vehicle controller, wherein, The external controller is installed outside the vehicle. The external controller is equipped with an external database that includes configuration information of multiple different in-vehicle networks and information representing communication settings corresponding to each of the multiple in-vehicle networks. The external vehicle database is updated along with the updates to the constituent information. The external controller is configured to perform the following processes: Obtain the configuration information of the in-vehicle network in the vehicle; Information representing the communication settings applied to the vehicle is extracted by referring to the obtained configuration information and the external vehicle database; as well as The extracted information representing the communication settings is then sent to the vehicle's onboard controller.

2. The vehicle external controller according to claim 1, wherein, The external controller is equipped with an external database that establishes a corresponding configuration information and communication setting flags of the in-vehicle network. The external controller is configured to perform the following processes: The communication setting flag is extracted as the communication setting applied to the vehicle by referring to the configuration information applied to the vehicle and the external database; and The extracted communication setting flags are then sent to the vehicle controller.

3. An on-board controller, wherein, The vehicle controller is installed in the vehicle. The vehicle controller is configured to perform the following process: control the communication settings of multiple switches that are data forwarding devices on the vehicle network equipped in the vehicle based on information indicating communication settings that is notified from an external controller equipped outside the vehicle.

4. The vehicle controller according to claim 3, wherein, The vehicle controller includes a vehicle database that establishes a corresponding communication setting flag, which represents the communication settings, and the communication settings of each switch equipped on the vehicle network. The vehicle controller is configured to perform the following processes: The communication settings of each switch corresponding to the communication setting flag are extracted by referring to the communication setting flag notified from the external controller and the vehicle database. and The communication settings of each switch on the vehicle network equipped in the vehicle are controlled based on the extracted communication settings.

5. An in-vehicle network update system, in, It comprises the external controller as described in claim 1 and the on-board controller as described in claim 3.

6. The vehicle network update system according to claim 5, wherein, The external controller is configured to perform the following process: notify the onboard controller of a communication setting flag as information indicating the communication settings applied to the vehicle. The vehicle controller is equipped with a vehicle database that establishes corresponding communication setting flags and communication settings of each switch equipped on the vehicle network. The vehicle controller is configured to perform the following processes: The communication settings of each switch corresponding to the communication setting flag are extracted by referring to the communication setting flag notified from the external controller and the vehicle database. and The communication settings of each switch on the vehicle network equipped in the vehicle are controlled based on the extracted communication settings.

7. A method for updating an in-vehicle network, wherein, The in-vehicle network update method is executed by an in-vehicle network update system, which includes an external controller installed outside the vehicle and an in-vehicle controller installed inside the vehicle. The in-vehicle network update method includes: Step 1: The external controller, which is equipped with an external database that establishes a corresponding external database containing configuration information of multiple different in-vehicle networks and information representing communication settings corresponding to the multiple in-vehicle networks respectively, obtains the configuration information in the vehicle. In the second step, the external controller refers to the obtained configuration information and the external database to extract information representing the communication settings applied to the vehicle; In step 3, the external controller notifies the onboard controller of the extracted information representing the communication settings. as well as In step 4, the vehicle controller controls the communication settings of the multiple switches that act as data forwarding devices on the vehicle network equipped in the vehicle based on the notified information indicating the communication settings.

8. The vehicle network update method according to claim 7, wherein, The third step is the step in which the external controller notifies the onboard controller of the communication setting flag as information indicating the communication settings applied to the vehicle. The fourth step consists of the following fifth and sixth steps. In the fifth step, the vehicle controller, which establishes a corresponding vehicle database for the communication setting flag and the communication settings of each switch equipped on the vehicle network, refers to the communication setting flag notified from the external controller and the vehicle database to extract the communication settings of each switch corresponding to the communication setting flag. In the sixth step, the vehicle controller controls the communication settings of each switch on the vehicle network equipped in the vehicle based on the extracted information representing the communication settings.

9. A program, wherein, The program is executed by an external controller located outside the vehicle. The external controller is equipped with an external database that includes configuration information of multiple different in-vehicle networks and information representing communication settings corresponding to each of the multiple in-vehicle networks. The program causes the external controller to perform the following processes: Obtain the configuration information of the vehicle; Information representing the communication settings applied to the vehicle is extracted by referring to the obtained configuration information and the external vehicle database; as well as The extracted information representing the communication settings is then sent to the vehicle's onboard controller.

10. The procedure according to claim 9, wherein, The external controller is equipped with an external database that establishes a corresponding configuration information and communication setting flags of the in-vehicle network. The program causes the external controller to perform the following processes: The communication setting flag is extracted as information representing the communication setting by referring to the configuration information of the in-vehicle network applied to the vehicle and the external database; and The extracted communication setting flags are then sent to the vehicle controller.

11. A program in which, The program is executed by an onboard controller installed in the vehicle. The program causes the vehicle controller to perform the following processing: controlling the communication settings of multiple switches that act as data forwarding devices on the vehicle network equipped in the vehicle, based on information indicating communication settings that is notified from an external controller equipped outside the vehicle.

12. The procedure according to claim 11, wherein, The vehicle controller is equipped with a vehicle database that establishes corresponding communication setting flags and communication settings of each switch equipped on the vehicle network. The program causes the vehicle controller to perform the following processes: The communication settings of each switch corresponding to the communication setting flag are extracted by referring to the communication setting flag notified from the external controller and the vehicle database. and The communication settings of each switch on the vehicle network equipped in the vehicle are controlled based on the extracted communication settings.

Images