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

Abstract

To provide an external vehicle controller that can reduce the frequency of updating data in a vehicle.SOLUTION: An external controller 11 provided outside a vehicle 20 includes an external database 410 that associates configuration information of a plurality of in-vehicle networks 21 having different configurations with communication setting flags respectively corresponding to the in-vehicle networks 21. The external database 410 is updated as the configuration information is updated. The external controller 11 acquires configuration information of the in-vehicle networks 21 in the vehicle 20. The external controller 11 refers to the acquired configuration information and the external database 410 to extract a communication setting flag to be applied to the vehicle 20. The external controller 11 notifies an in-vehicle controller 22 of the extracted communication setting flag.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to an external vehicle controller, an in-vehicle controller, an in-vehicle network update system, an in-vehicle network update method, and a program using an SDN system. [Background technology]

[0002] Patent Document 1 describes an SDN (Software Defined Networking) system that can change the network configuration and communication settings without changing the hardware configuration by controlling communication devices with software. The SDN network system includes multiple SDN switches and an SDN controller that changes the settings of each SDN switch.

[0003] The SDN controller is a controller that controls communication settings in multiple SDN switches. The SDN switch is a switch that is installed on the network and performs data transfer. [Prior art documents] [Patent documents]

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

[0005] It is conceivable that the SDN system described in Patent Document 1 may be used in an in-vehicle SDN network. In a vehicle, new in-vehicle devices may be added and connected to the vehicle to add functions, etc. Also, the software of the in-vehicle devices may be updated through updates. The configuration of the in-vehicle SDN network may be changed due to the addition of new in-vehicle devices or the addition of functions through software updates. Even if 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 settings of the SDN switch.

[0006] In order for the SDN controller to control the in-vehicle SDN network, it is necessary to have a database that matches configuration information of the in-vehicle SDN network, such as topology information of in-vehicle devices and software version information, with the communication settings of the SDN switch in the vehicle.

[0007] This database stores information indicating multiple communication settings corresponding to different configurations of in-vehicle SDN networks, making it versatile enough to accommodate the addition of additional in-vehicle equipment for functional expansion or to accommodate vehicles with different specifications.

[0008] Therefore, in order to keep the database up to date, it is necessary to update the database even when information indicating communication settings that are not used in a certain vehicle or updates to software that is not used are performed, which results in more frequent updates to the database than if only necessary updates were performed in a certain vehicle.

[0009] While data is being updated in a vehicle, the vehicle may not be able to be driven, which means that there is a need to reduce the number of updates to data in the vehicle. [Means for solving the problem]

[0010] The means for solving the above problems and their effects will be described below. The external controller for solving the above problem is an external controller provided outside the vehicle. The external controller includes an external database that associates configuration information of a plurality of in-vehicle networks having different configurations with information indicating communication settings corresponding to each of the in-vehicle networks. The external database is updated as the configuration information is updated. The external controller acquires the configuration information of the in-vehicle network in the vehicle. Then, the external controller refers to the acquired configuration information and the external database to extract information indicating the communication settings to be applied to the vehicle. Furthermore, the external controller notifies each in-vehicle controller provided in the vehicle of the extracted information indicating the communication settings.

[0011] The in-vehicle controller for solving the above problem is an in-vehicle controller provided in a vehicle, which controls communication settings of each switch, which is a data transfer device provided on an in-vehicle network in the vehicle, based on information indicating communication settings notified from an external controller provided outside the vehicle.

[0012] The in-vehicle network update system for solving the above problem includes the external controller provided outside the vehicle and the in-vehicle controller provided in the vehicle. The external controller includes an external database that associates configuration information of a plurality of in-vehicle networks having different configurations with information indicating communication settings corresponding to each of the in-vehicle networks. The external database is updated as the configuration information is updated. In this in-vehicle network update system, the external controller acquires the configuration information of the vehicle, and refers to the acquired configuration information and the external database to extract information indicating the communication settings to be applied to the vehicle. Then, the external controller notifies the in-vehicle controller of the extracted information indicating the communication settings. In this in-vehicle network update system, the in-vehicle controller controls communication settings of each switch, which is a data transfer device provided on the in-vehicle network in the vehicle, based on the information indicating the communication settings notified from the external controller.

[0013] The in-vehicle network update method for solving the above problem is an in-vehicle network update method executed by an in-vehicle network update system including an external controller provided outside a vehicle and an in-vehicle controller provided in the vehicle. The in-vehicle network update method includes a first step in which the external controller, which includes an external database in which configuration information of a plurality of in-vehicle networks having different configurations is associated with information indicating communication settings corresponding to each of the in-vehicle networks, acquires the configuration information in the vehicle. The in-vehicle network update method includes a second step in which the external controller refers to the acquired configuration information and the external database to extract information indicating the communication settings to be applied to the vehicle. The in-vehicle network update method includes a third step in which the external controller notifies the in-vehicle controller of the extracted information indicating the communication settings. The in-vehicle network update method includes a fourth step in which the in-vehicle controller controls communication settings of each switch, which is a data transfer device provided on the in-vehicle network in the vehicle, based on the notified information indicating the communication settings.

[0014] A program for solving the above problem is a program executed by an external controller provided outside a vehicle. The program causes the external controller, which has an external database that associates configuration information of a plurality of in-vehicle networks with different configurations with information indicating communication settings corresponding to each of the in-vehicle networks, to acquire the configuration information in the vehicle. The program causes the external controller to refer to the acquired configuration information and the external database, and to extract information indicating the communication settings to be applied to the vehicle. The program causes the external controller to notify the extracted information indicating the communication settings to an in-vehicle controller provided in the vehicle.

[0015] A program for solving the above problem is a program executed by an in-vehicle controller provided in a vehicle, which causes the in-vehicle controller to control communication settings of each switch, which is a data transfer device provided on an in-vehicle network in the vehicle, based on information indicating communication settings notified from an external controller provided outside the vehicle. Effect of the Invention

[0016] The external vehicle controller, the in-vehicle controller, the in-vehicle network update system, the in-vehicle network update method, and the program are capable of reducing the frequency of updating data in a vehicle. [Brief description of the drawings]

[0017] [Figure 1] FIG. 1 is a schematic diagram illustrating an in-vehicle SDN network update system. [Diagram 2] FIG. 2 is a schematic diagram showing the configuration of an in-vehicle SDN network in which an in-vehicle controller and in-vehicle devices are provided. [Diagram 3] FIG. 3 is a schematic diagram showing an update operation in network settings in the case where the database is held by the vehicle-mounted controller. [Figure 4] FIG. 4 is a table showing an example of the database shown in FIG. [Diagram 5] Figure 5 is a table showing the operating status of each SDN switch for each communication setting. [Figure 6] FIG. 6 is a table showing an example of an updated database obtained by updating the database shown in FIG. [Figure 7] FIG. 7 is a schematic diagram showing an example of an update operation in network setting in a case where the external controller has an external database and the in-vehicle controller has an in-vehicle database. [Figure 8] FIG. 8 is a table showing an example of the outside-vehicle database included in the outside-vehicle controller shown in FIG. [Figure 9]FIG. 9 is a table showing an example of an in-vehicle database included in the in-vehicle controller shown in FIG. [Figure 10] FIG. 10 is a table showing an example of an updated exterior database obtained by updating the exterior database shown in FIG. [Figure 11] FIG. 11 is a schematic diagram showing an example of an update operation in an in-vehicle SDN network when only the external controller has a database. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] Hereinafter, an embodiment of an in-vehicle SDN network updating system will be described with reference to FIGS. <Overview of In-Vehicle SDN Network Update System 1> FIG. 1 shows a schematic diagram of an in-vehicle SDN network update system 1. As shown in FIG. 1, the in-vehicle SDN network update system 1 is an in-vehicle network update system including a server 10, a plurality of vehicles 20, and an external communication line network 30. The server 10 includes an external controller 11 and a communication device 12. Each vehicle 20 has an in-vehicle SDN network 21. An in-vehicle communication device 23 is connected to each in-vehicle 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 line network 30, and the in-vehicle communication device 23. The external communication line network 30 is, for example, a wireless communication line network such as a mobile phone line network. Therefore, the server 10 and each vehicle 20 can communicate information with each other via the external communication line network 30.

[0019] The external controller 11 includes a CPU and a ROM. The CPU of the external controller 11 executes a program stored in the ROM. <Overview of In-Vehicle SDN Network 21> 2, an in-vehicle SDN network 21 in a vehicle 20 is an in-vehicle network including an in-vehicle controller 22, which is an SDN controller, an in-vehicle communication device 23, a plurality of SDN switches 24, and a plurality of in-vehicle devices 25. Each of the in-vehicle devices 25 is controlled by software 26 installed in the in-vehicle devices 25. The in-vehicle devices 25 include various ECUs (Electronic Control Units), engines, brakes, motors, sensors, car navigation systems, and the like mounted on the vehicle 20. The in-vehicle devices 25 are connected to the in-vehicle SDN network 21 by a PnP (Plug and Play) method.

[0020] The SDN switch 24 and the in-vehicle device 25 are communication devices that perform frame communication. Here, frame communication refers to performing at least one of forwarding, transmitting, and receiving a frame.

[0021] The in-vehicle controller 22 controls communication settings in the in-vehicle SDN network 21. The in-vehicle controller 22 updates the communication settings when the configuration of the in-vehicle SDN network 21 is changed, for example, when a new in-vehicle device 25 is connected. At this time, the in-vehicle controller 22 transmits communication settings that determine a data communication path to each SDN switch 24 provided on the in-vehicle SDN network 21. In this way, the in-vehicle controller 22 centrally manages communication settings of the multiple SDN switches 24 provided on the in-vehicle SDN network 21. The in-vehicle controller 22 transmits data to be transferred by the SDN switch 24.

[0022] The in-vehicle communication device 23 establishes data communication with the external controller 11 via the external communication line network 30. In Fig. 2, the in-vehicle communication device 23 is directly connected to the in-vehicle controller 22. Note that the in-vehicle communication device 23 may be connected to the in-vehicle controller 22 via an SDN switch 24.

[0023] The SDN switch 24 is a data transfer device that transfers data on the in-vehicle SDN network 21. Specifically, the SDN switch 24 updates rules for data transfer stored in its own flow table based on information received from the in-vehicle controller 22. Then, based on the updated rules, the SDN switch 24 transfers the data received from the in-vehicle controller 22 to an appropriate in-vehicle device 25. Hereinafter, when each SDN switch 24 is to be distinguished from the others, they will be referred to as a first SDN switch 24_1, a second SDN switch 24_2, a third SDN switch 24_3, and a fourth SDN switch 24_4.

[0024] <When the in-vehicle controller 22 includes the database 400> 3, as a comparative example, a case will be considered in which the in-vehicle controller 22 includes a database 400. In this case, the in-vehicle SDN network 21 in the vehicle 20 includes the in-vehicle controller 22, an in-vehicle communication device 23, and a PnP master 110.

[0025] The database 400 stores configuration information of multiple in-vehicle SDN networks 21 with different configurations in association with the communication settings of each SDN switch 24 provided on each in-vehicle SDN network 21.

[0026] Here, the configuration information of the in-vehicle SDN network 21 is topology information 100 of the in-vehicle devices 25 in the in-vehicle SDN network 21 and software information 200 of the in-vehicle devices 25. The software information 200 is, for example, version information of each piece of software 26 included in each in-vehicle device 25. The information indicating the communication settings is, for example, the communication settings of each SDN switch 24 that determines a data communication path on the network in the in-vehicle SDN network 21.

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

[0028] The in-vehicle controller 22 acquires the software information 200 from a software management system 220 provided outside the vehicle via the external communication network 30. The software management system 220 manages version information of the software 26 of the in-vehicle device 25. When a new version of the software 26 is released, the software management system 220 notifies the in-vehicle controller 22 of the software information 200 via the external communication network 30. The software management system 220 includes a plurality of pieces of software information 200 corresponding to a plurality of pieces of software 26 in a plurality of in-vehicle devices 25.

[0029] Since there are multiple pieces of software information 200 corresponding to multiple in-vehicle devices 25, in the following description, when describing each piece of software information 200 in a differentiated manner, they will be described as first software information 201, second software information 202, and so on.

[0030] The in-vehicle controller 22 refers to the topology information 100 notified from the PnP master 110, the software information 200 notified from the software management system 220, and the database 400 to extract communication settings of each SDN switch 24. After that, the in-vehicle controller 22 controls the communication settings of each SDN switch 24 provided on the in-vehicle SDN network 21 in the vehicle 20 based on the extracted communication settings.

[0031] <Specific examples of information stored in database 400> As shown in FIG. 4, the database 400 exemplified here stores two types of information, "T_1" and "T_2", for the topology information 100. That is, the database 400 stores communication settings corresponding to two types of topologies having different connection methods for the in-vehicle device 25. Similarly, the 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, the database 400 stores three different types of version information for the first software information 201. Furthermore, the database 400 stores one type of information, "S_2_1", for the second software information 202. That is, the database 400 stores only one type of version information as the second software information 202.

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

[0033] The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_1", the first software information 201 is "S_1_1", and the second software information 202 is "S_2_1" is "Conf_1". The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_2", the first software information 201 is "S_1_1", and the second software information 202 is "S_2_1" is "Conf_2". The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_1", the first software information 201 is "S_1_2", and the second software information 202 is "S_2_1" is "Conf_1". The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_2", the first software information 201 is "S_1_2", and the second software information 202 is "S_2_1" is "Conf_2". The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_1", the first software information 201 is "S_1_3", and the second software information 202 is "S_2_1" is "Conf_3". The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_2", the first software information 201 is "S_1_3", and the second software information 202 is "S_2_1" is "Conf_3".

[0034] As shown in FIG. 5, the in-vehicle controller 22 operates each SDN switch 24 based on the extracted communication setting of each SDN switch 24, "Conf_1", "Conf_2", or "Conf_3". When the communication setting of each SDN switch 24 applied to the in-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.

[0035] As shown in FIG. 4, even if the combinations of the topology information 100, the first software information 201, and the second software information 202 are different, the communication settings of each SDN switch 24 applied to the in-vehicle SDN network 21 may be the same.

[0036] For example, for the two rows surrounded by dashed lines in FIG. 4, even if the first software information 201 is different between "S_1_1" and "S_1_2", the communication settings applied to each SDN switch 24 will both be "Conf_1".

[0037] <About Database 400 Update> If the latest topology information 100 or the latest software information 200 does not exist in the database 400 of the vehicle controller 22 , the vehicle controller 22 updates the database 400 .

[0038] For example, it is assumed that the database 400 needs to be updated when a new version of the software 26 is released. The software management system 220 transmits the new version of the software 26 to the in-vehicle controller 22. The in-vehicle controller 22 downloads the new software 26. After that, the in-vehicle controller 22 installs the new software 26 in the corresponding in-vehicle device 25.

[0039] The software management system 220 notifies the vehicle controller 22 of the latest software information 200. The vehicle controller 22 updates the database 400 so that the database 400 includes the notified latest software information 200, and creates an updated database 401.

[0040] The in-vehicle controller 22 refers to the topology information 100 notified from the PnP master 110, the software information 200 notified from the software management system 220, and the updated database 401, and extracts communication settings of each SDN switch 24. After that, the in-vehicle controller 22 controls the communication settings of each SDN switch 24 provided on the in-vehicle SDN network 21 in the vehicle 20 based on the extracted communication settings.

[0041] <Specific examples of updating Database 400> Assume that the second software information 202 is updated. As shown in FIG. 6, in the updated database 401, "S_2_2" is added to the second software information 202. The first to sixth lines of the updated database 401 are the same as those of the database 400 shown in FIG. 4. The range enclosed by the dashed line in FIG. 6 is the range added in the updated database 401. The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_1", the first software information 201 is "S_1_1", and the second software information 202 is "S_2_2" is "Conf_1". The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_2", the first software information 201 is "S_1_1", and the second software information 202 is "S_2_2" is "Conf_2". The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_1", the first software information 201 is "S_1_2", and the second software information 202 is "S_2_2" is "Conf_1". The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_2", the first software information 201 is "S_1_2", and the second software information 202 is "S_2_2" is "Conf_2". The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_1", the first software information 201 is "S_1_3", and the second software information 202 is "S_2_2" is "Conf_3". The communication setting of each SDN switch 24 applied to the in-vehicle SDN network 21 in which the topology information 100 is "T_2", the first software information 201 is "S_1_3", and the second software information 202 is "S_2_2" is "Conf_3".

[0042] <Problems with updating Database 400> The database 400 included in the in-vehicle controller 22 stores communication settings corresponding to each of the different in-vehicle SDN networks 21 including the topology information 100 and the software information 200. Thus, the database 400 has versatility that allows the additional installation of in-vehicle devices 25 for function expansion and allows the database 400 to accommodate vehicles 20 with different specifications.

[0043] Therefore, in order to keep the database 400 up to date, it is necessary to update the database 400 even if communication settings that are not used or software 26 that is not used in a certain vehicle 20 are updated.

[0044] For example, when new topology information 100 that corresponds to the database 400 is added, the database 400 is updated to correspond to the added topology information 100. For example, when any of the software information 200 is updated, the database 400 is updated to correspond to the new software information 200 .

[0045] For example, when a software 26 corresponding to the database 400 is added, the database 400 is updated to add the software information 200 for the new software 26 .

[0046] Therefore, the actual database 400 will be updated more frequently than if only necessary updates were made to a given vehicle 20 . The updates to the database 400 include updates that are not required for some of the vehicles 20. For example, this may be the case when the software information 200 of an in-vehicle device 25 that is not installed in the vehicle 20 is updated.

[0047] When updating the database 400, the external controller 11 needs to transmit campaign information and a distribution package related to updating the database 400 to the vehicle 20. In other words, when the on-vehicle controllers 22 mounted on multiple vehicles 20 each include the database 400, the server 10 needs to transmit campaign information and a distribution package to the multiple vehicles 20 at high frequency. This causes a problem that data updates occur frequently in each vehicle 20.

[0048] <In-vehicle SDN network update system 1 according to this embodiment> 7, the in-vehicle SDN network update system 1 in this embodiment includes an off-vehicle database 410 in the off-vehicle controller 11 on the server 10. The in-vehicle SDN network update system 1 includes an on-vehicle database 420 in the on-vehicle controller 22 on the in-vehicle SDN network 21.

[0049] The server 10 includes a software management system 220. The software management system 220 stores a plurality of pieces of software information 200 for a plurality of vehicles 20. For example, assume that a new in-vehicle device 25 is connected to the in-vehicle SDN network 21 in the vehicle 20. In this case, the topology information 100 in the vehicle 20 is changed.

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

[0051] The in-vehicle controller 22 refers to the communication setting flag notified from the external controller 11 and the in-vehicle database 420, and extracts the communication setting of each SDN switch 24 corresponding to the communication setting flag. After that, the in-vehicle controller 22 controls the communication setting of each SDN switch 24 provided on the in-vehicle SDN network 21 in the vehicle 20 based on the extracted communication setting.

[0052] <Specific examples of information stored in the external database 410> 8, the external database 410 stores the topology information 100, the first software information 201, and the second software information 202. Furthermore, the external database 410 stores a communication setting flag corresponding to a combination of the topology information 100, the first software information 201, and the second software information 202.

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

[0054] For example, as shown by the dashed line in Fig. 8, assume that the external controller 11 acquires "T_1" as the topology information 100, "S_1_2" as the first software information 201, and "S_2_1" as the second software information 202. In this case, the external controller 11 refers to the acquired configuration information and the external database 410. As a result, the external controller 11 extracts "Flag_1" as the communication setting flag.

[0055] 9, when the in-vehicle controller 22 is notified of "Flag_1" as the communication setting flag from the external controller 11, the in-vehicle controller 22 extracts "Conf_1" as the communication setting. When the in-vehicle controller 22 is notified of "Flag_2" as the communication setting flag from the external controller 11, the in-vehicle controller 22 extracts "Conf_2" as the communication setting. When the in-vehicle controller 22 is notified of "Flag_3" as the communication setting flag from the external controller 11, the in-vehicle controller 22 extracts "Conf_3" as the communication setting.

[0056] 5, when the in-vehicle controller 22 extracts "Conf_1" as the communication setting, the in-vehicle controller 22 operates the first SDN switch 24_1 and the second SDN switch 24_2. When the in-vehicle controller 22 extracts "Conf_2" as the communication setting, the in-vehicle controller 22 operates the first SDN switch 24_1, the second SDN switch 24_2, and the fourth SDN switch 24_4. When the in-vehicle controller 22 extracts "Conf_3" as the communication setting, the in-vehicle controller 22 operates the first SDN switch 24_1 and the third SDN switch 24_3.

[0057] <About updating the external database 410> For example, when the existing software 26 is updated, the software management system 220 transmits the updated software 26 to the on-board controller 22 in the vehicle 20. When the existing software 26 is updated, the software management system 220 notifies the external controller 11 of version information of the software 26. In other words, the software management system 220 notifies the external controller 11 of the software information 200.

[0058] For example, assume that the software management system 220 detects an update to the existing software 26. In this case, the software management system 220 extracts the vehicles 20 that use the software 26 for which the update has been detected. The software management system 220 then transmits the new version of the software 26 to the in-vehicle controller 22 in the vehicle 20 that uses the software 26 for which the update has been detected. The in-vehicle controller 22 installs the new version of the software 26 in the corresponding in-vehicle device 25. In addition, the software management system 220 notifies the external controller 11 of the software information 200 including the new version of the software 26.

[0059] Then, the external controller 11 updates the external database 410 based on the notified software information 200. The external controller 11 extracts a communication setting flag by referring to the notified software information 200 and the external database 410. After that, the external controller 11 notifies the on-board controller 22 of the vehicle 20 in which the software 26 has been updated of the communication setting flag.

[0060] The in-vehicle controller 22 refers to the communication setting flag notified from the external controller 11 and the in-vehicle database 420, and extracts the communication setting of each SDN switch 24 corresponding to the communication setting flag. After that, the in-vehicle controller 22 controls the communication setting of each SDN switch 24 provided on the in-vehicle SDN network 21 in the vehicle 20 based on the extracted communication setting.

[0061] 10, it is assumed that, due to an update of the outside-vehicle database 410, "S_2_2" is added to the second software information 202 in the updated outside-vehicle database 411. Lines 1 to 6 of the updated outside-vehicle database 411 are the same as those of the outside-vehicle database 410 shown in FIG.

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

[0063] 9, when the in-vehicle controller 22 is notified of "Flag_1" as the communication setting flag from the external controller 11, the in-vehicle controller 22 extracts "Conf_1" as the communication setting. When the in-vehicle controller 22 is notified of "Flag_2" as the communication setting flag from the external controller 11, the in-vehicle controller 22 extracts "Conf_2" as the communication setting. When the in-vehicle controller 22 is notified of "Flag_3" as the communication setting flag from the external controller 11, the in-vehicle controller 22 extracts "Conf_3" as the communication setting.

[0064] 5, when the in-vehicle controller 22 extracts "Conf_1" as the communication setting, the in-vehicle controller 22 operates the first SDN switch 24_1 and the second SDN switch 24_2. When the in-vehicle controller 22 extracts "Conf_2" as the communication setting, the in-vehicle controller 22 operates the first SDN switch 24_1, the second SDN switch 24_2, and the fourth SDN switch 24_4. When the in-vehicle controller 22 extracts "Conf_3" as the communication setting, the in-vehicle controller 22 operates the first SDN switch 24_1 and the third SDN switch 24_3.

[0065] <Action of this embodiment> The in-vehicle SDN network update system 1 of this embodiment includes an external controller 11 outside the vehicle 20. The external controller 11 includes an external database 410. The external database 410 included in the external controller 11 has versatility that allows optional devices to be added for function expansion and can be adapted to vehicles 20 with different specifications. The external database 410 is frequently updated to accommodate, for example, the addition of new in-vehicle devices 25 and upgrades to the software 26.

[0066] The in-vehicle SDN network update system 1 of this embodiment includes an in-vehicle controller 22 in the vehicle 20. The in-vehicle controller 22 includes an in-vehicle database 420. In this embodiment, the in-vehicle database 420 stores a communication setting flag and a communication setting of each SDN switch 24 in the in-vehicle SDN network 21 in association with each other. That is, the in-vehicle database 420 only needs to be updated when the communication setting flag or the communication setting of each SDN switch 24 is increased. Therefore, as described with reference to FIG. 4 and FIG. 5, the frequency of data updates in the vehicle 20 is reduced when the in-vehicle controller 22 includes the in-vehicle database 420 compared to when the in-vehicle controller 22 includes the database 400.

[0067] <Effects of this embodiment> (1) The in-vehicle SDN network update system 1 can reduce the frequency of data updates in the vehicle 20.

[0068] (2) When the external controller 11 stores information indicating configuration information and communication settings for each individual vehicle 20, the external controller 11 needs to store information indicating configuration information and communication settings 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 individual vehicle 20 in accordance with the number of vehicles 20.

[0069] The exterior database 410 associates configuration information of a plurality of in-vehicle SDN networks 21 having different configurations with information indicating communication settings corresponding to each of the in-vehicle SDN networks 21. In other words, the exterior database 410 is a database in which information is organized by type of in-vehicle SDN network 21. In this manner, the exterior controller 11 stores exterior databases 410 corresponding to a plurality of vehicles 20. For this reason, the amount of data stored in the exterior controller 11 is smaller than when the exterior controller 11 stores configuration information and information indicating communication settings for each individual vehicle 20.

[0070] When the configuration information is updated due to the release of new software 26, the external controller 11 updates the external database 410. This allows the external controller 11 to complete the update with less communication traffic than when updating the configuration information stored for each individual vehicle 20.

[0071] (3) The in-vehicle SDN network updating method executed by the in-vehicle SDN network updating system 1 is an in-vehicle network updating method. The in-vehicle SDN network updating method includes a first step in which the off-vehicle controller 11 acquires configuration information in the vehicle 20. The in-vehicle SDN network updating method includes a second step in which the off-vehicle controller 11 refers to the acquired configuration information and the off-vehicle database 410 to extract a communication setting flag, which is information indicating a communication setting to be applied to the vehicle 20. The in-vehicle SDN network updating method includes a third step in which the off-vehicle controller 11 notifies the on-vehicle controller 22 of the extracted communication setting flag. The in-vehicle SDN network updating method includes a fourth step in which the on-vehicle controller 22 controls the communication setting of each SDN switch 24 provided on the in-vehicle SDN network in the vehicle 20 based on the notified communication setting flag. The fourth step of the in-vehicle SDN network updating method includes the following fifth and sixth steps. The in-vehicle SDN network updating method includes a fifth step in which the in-vehicle controller 22 refers to the notified communication setting flag and the in-vehicle database 420, and extracts communication settings of the in-vehicle SDN network 21 corresponding to the communication setting flag. The in-vehicle SDN network updating method includes a sixth step in which the in-vehicle controller 22 controls communication settings of the SDN switch 24 provided on the in-vehicle SDN network 21 in the vehicle 20, based on the extracted communication settings.

[0072] By performing such an in-vehicle SDN network update method, the in-vehicle SDN network update system 1 can reduce the frequency of data updates in the vehicle 20.

[0073] (4) The exterior controller 11 includes an exterior database 410 that associates configuration information of a plurality of in-vehicle SDN networks 21 having different configurations with a communication setting flag corresponding to each of the in-vehicle SDN networks 21. The exterior database 410 is updated along with updates to the configuration information. The exterior controller 11 acquires configuration information of the vehicle 20. Thereafter, the exterior controller 11 refers to the acquired configuration information and the exterior database 410 to extract a communication setting flag to be applied to the vehicle 20. Furthermore, the exterior controller 11 notifies the in-vehicle controller 22 provided in the vehicle 20 of the extracted communication setting flag.

[0074] The external database 410 needs to be versatile enough to accommodate the addition of optional devices for function expansion and to accommodate vehicles 20 with different specifications. The external database 410 stored in the external controller 11 is frequently updated to accommodate, for example, the addition of new optional devices and upgrades to the software 26.

[0075] According to the above-described external controller 11, it becomes unnecessary to mount the database 400, which is updated frequently, on the vehicle 20. Therefore, the above-described external controller 11 can reduce the frequency of updating data in the vehicle 20.

[0076] (5) The in-vehicle controller 22 includes an in-vehicle database 420 that associates communication setting flags with communication settings of each SDN switch 24 provided on each in-vehicle SDN network 21. The in-vehicle controller 22 references the communication setting flag notified from the external controller 11 and the in-vehicle database 420 to extract the communication setting of each SDN switch 24 that corresponds to the communication setting flag. The in-vehicle controller 22 controls the communication setting of each SDN switch 24 provided on the in-vehicle SDN network 21 in the vehicle 20 based on the extracted communication setting.

[0077] The in-vehicle controller 22 controls the communication settings of each SDN switch 24 provided on the network in the vehicle 20 based on the communication setting flag notified from the external controller 11.

[0078] 3 to 6, when the in-vehicle controller 22 includes the database 400 that is updated frequently, data is updated frequently in the vehicle 20 in order to update the database 400. In contrast, the in-vehicle controller 22 of this embodiment controls the SDN switch 24 based on the communication setting flag notified from the external controller 11.

[0079] That is, according to the in-vehicle controller 22 of the present embodiment, it is possible to control communication settings even without the frequently updated database 400. Therefore, the in-vehicle controller 22 can reduce the frequency of updating data in the vehicle 20.

[0080] (6) In this embodiment, the program executed by the external controller 11 causes the external controller 11 to acquire configuration information of the vehicle 20. This program causes the external controller 11 to refer to the acquired configuration information and the external database 410, and to extract a communication setting flag to be applied to the vehicle 20. This program causes the external controller 11 to notify the in-vehicle controller 22 of the extracted communication setting flag.

[0081] According to the program executed by the external controller 11, it becomes unnecessary to mount the database 400, which is updated frequently, on the vehicle 20. Therefore, the program executed by the external controller 11 can reduce the frequency of updating data in the vehicle 20.

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

[0083] According to this program, even if the vehicle controller 22 does not have the 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 updating data in the vehicle 20.

[0084] <Example of change> This embodiment can be modified as follows: This embodiment and the following modifications can be combined with each other to the extent that there is no technical contradiction.

[0085] <When the external controller 11 notifies the in-vehicle controller 22 of the communication setting of the SDN switch 24> In the above embodiment, the external controller 11 notifies the in-vehicle controller 22 of a communication setting flag as information indicating the communication setting. In response to this, the external controller 11 may notify the in-vehicle controller 22 of information other than the communication setting flag as information indicating the communication setting. For example, the external controller 11 may notify the in-vehicle controller 22 of the communication setting of each SDN switch 24 provided on the in-vehicle SDN network 21 as information indicating the communication setting to be applied to the vehicle 20. In other words, the external controller 11 may notify the in-vehicle controller 22 of information summarizing the contents of the communication setting of each SDN switch 24 provided on the in-vehicle SDN network 21.

[0086] 11, the in-vehicle SDN network update system 1 in this modified example includes a database 400 in an external controller 11 on a server 10. The server 10 includes a software management system 220. The software management system 220 stores a plurality of pieces of software information 200 for a plurality of vehicles 20.

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

[0088] The external controller 11 refers to the notified topology information 100, the software information 200 acquired from the software management system 220, and the database 400 to extract communication settings of each SDN switch 24. After that, the external controller 11 notifies the on-board controller 22 in the vehicle 20 of the communication settings of each SDN switch 24.

[0089] The in-vehicle controller 22 controls the communication settings of each SDN switch 24 based on the notified communication settings. As shown in FIG. 4, the database 400 stores communication settings of each SDN switch 24 corresponding to each combination of the topology information 100, the first software information 201, and the second software information 202.

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

[0091] As shown in FIG. 5, the in-vehicle controller 22 operates each SDN switch 24 based on the notified communication setting of each SDN switch 24, "Conf_1," "Conf_2," or "Conf_3." When the communication setting of each SDN switch 24 notified from the external controller 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 notified from the external controller 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 notified is "Conf_3," the first SDN switch 24_1 and the third SDN switch 24_3 operate.

[0092] In this modification, the in-vehicle SDN network updating method includes a first step in which the external controller 11 acquires configuration information of the in-vehicle SDN network 21 in the vehicle 20. In this modification, the in-vehicle SDN network updating method includes a second step in which the external controller 11 extracts communication settings of each SDN switch 24 to be applied to the vehicle 20 by referring to the acquired configuration information and the database 400. In this modification, the in-vehicle SDN network updating method includes a third step in which the external controller 11 notifies the in-vehicle controller 22 of the extracted communication settings of each SDN switch 24. In this modification, the in-vehicle SDN network updating method includes a fourth step in which the in-vehicle controller 22 controls the communication settings of each SDN switch 24 provided in the in-vehicle SDN network 21 in the vehicle 20 based on the notified communication settings.

[0093] In this modification, the program executed by the external controller 11 causes the external controller 11 to acquire configuration information of the in-vehicle SDN network 21 in the vehicle 20. In this modification, the program executed by the external controller 11 causes the external controller 11 to refer to the acquired configuration information and the database 400, and extract information indicating communication settings to be applied to the vehicle 20. In this modification, the program executed by the external controller 11 causes the external controller 11 to notify the in-vehicle controller 22 provided in the vehicle 20 of the extracted communication settings of each SDN switch 24.

[0094] In this modified example, the program executed by the in-vehicle controller 22 causes the in-vehicle controller 22 to control the communication settings of each SDN switch 24 provided on the in-vehicle SDN network 21 based on the communication settings notified from the external controller 11.

[0095] <About the configuration of the in-vehicle SDN network update system 1> The in-vehicle SDN network update system 1 may be applied to an in-vehicle SDN network 21 other than the in-vehicle SDN network 21 in the above embodiment. For example, the in-vehicle SDN network update system 1 may be applied to an in-vehicle SDN network 21 including five or more SDN switches 24.

[0096] The in-vehicle SDN network update system 1 may include the software management system 220 in a server 10 different from the server 10 in which the external controller 11 is provided. That is, the in-vehicle SDN network update system 1 may include a plurality of servers 10. In this case, the external controller 11 acquires the software information 200 from the software management system 220 via the external communication line network 30 or wired communication.

[0097] <Method for the external controller 11 to acquire the topology information 100> The external controller 11 may obtain the topology information 100 in the vehicle 20 from a source other than the vehicle 20. For example, the external controller 11 may obtain the topology information 100 from a topology information management system provided in the server 10.

[0098] The topology information management system is a system that stores a plurality of pieces of topology information 100 for a plurality of vehicles 20. The topology information management system notifies the external controller 11 of the vehicle 20 for which the topology information 100 is to be changed. In addition, the topology information management system notifies the external controller 11 of the topology information 100.

[0099] The external controller 11 extracts a communication setting flag by referring to the topology information 100 acquired from the topology information management system, the software information 200 acquired from the software management system 220, and the external database 410. After that, the external controller 11 notifies the extracted communication setting flag to the on-board controller 22 in the vehicle 20 for which the topology information 100 is to be changed.

[0100] The in-vehicle SDN network update system 1 may include the topology information management system in a server 10 different from the server 10 in which the external controller 11 is included. In this case, the external controller 11 acquires the topology information 100 from the topology information management system via the external communication line network 30 or wired communication.

[0101] <Method for the external controller 11 to acquire the software information 200> The external controller 11 may obtain the software information 200 in the vehicle 20 from a source other than the software management system 220 provided in the server 10. For example, the external controller 11 may obtain the software information 200 from a software management device provided in the vehicle 20.

[0102] The software management device manages software information 200 of the in-vehicle device 25 in the vehicle 20. The in-vehicle controller 22 acquires the software information 200 from the software management device via the in-vehicle SDN network 21. The in-vehicle controller 22 notifies the acquired software information 200 to the external controller 11 via the in-vehicle communication device 23 and the external communication line network 30.

[0103] The external controller 11 extracts a communication setting flag by referring to the topology information 100 acquired from the PnP master 110, the software information 200 acquired from the software management device, and the external database 410. After that, the external controller 11 notifies the extracted communication setting flag to the on-board controller 22 in the vehicle 20 equipped with the software management device.

[0104] <Other> The external controller 11 may be configured as a circuit including one or more processors that execute various processes according to a computer program (software). The external controller 11 may be configured as a circuit including one or more dedicated hardware circuits, such as an application specific integrated circuit (ASIC), that execute at least some of the various processes, or a combination thereof. The processor includes a CPU and memories such as RAM and ROM. The memory stores program codes or instructions configured to cause the CPU to execute the processes. The memory, i.e., computer-readable medium, includes any available medium that can be accessed by a general-purpose or dedicated computer. The same applies to the on-board controller 22. [Explanation of symbols]

[0105] 1. In-vehicle SDN network update system 10. Server 11…External controller 12...Communication equipment 20…Vehicle 21…In-vehicle SDN network 22…In-vehicle controller 23...In-vehicle communication device 24…SDN switch 24_1…First SDN switch 24_2…Second SDN switch 24_3…Third SDN switch 24_4…4th SDN switch 25…In-vehicle equipment 26…Software 30…External communication network 100...Topology information 110...PnP Master 200…Software information 201...First software information 202...Second software information 220...Software Management System 400...Database 401…Updated database 410…External database 411…Updated external database 420…In-vehicle database

Claims

1. An external controller provided outside the vehicle, The vehicle has an external database that associates configuration information of a plurality of in-vehicle networks having different configurations with information indicating communication settings corresponding to each of the in-vehicle networks; The outside-vehicle database is updated in accordance with an update of the configuration information, acquiring the configuration information of the in-vehicle network in the vehicle; extracting information indicating the communication settings to be applied to the vehicle by referring to the acquired configuration information and the external database; notifying each in-vehicle controller provided in the vehicle of the extracted information indicating the communication setting. Outside vehicle controller.

2. the vehicle exterior database includes a correspondence between the configuration information of the in-vehicle network and a communication setting flag; extracting the communication setting flag as the communication setting to be applied to the vehicle by referring to the configuration information to be applied to the vehicle and the external database; notifying the vehicle controller of the extracted communication setting flag. The external controller according to claim 1 .

3. An in-vehicle controller provided in a vehicle, Based on information indicating communication settings notified from an external controller provided outside the vehicle, communication settings of each switch, which is a data transfer device provided on an in-vehicle network in the vehicle, are controlled. In-vehicle controller.

4. a vehicle-mounted database that associates a communication setting flag as information indicating the communication setting with the communication setting of each of the switches provided on each vehicle-mounted network, extracting the communication setting of each of the switches corresponding to the communication setting flag by referring to the communication setting flag notified from the external controller and the in-vehicle database; and controlling the communication settings of each of the switches provided on the in-vehicle network in the vehicle based on the extracted communication settings. The vehicle controller according to claim 3 .

5. An in-vehicle network updating system comprising: an external controller according to claim 1; and an in-vehicle controller according to claim 3.

6. The external controller notifies the in-vehicle controller of a communication setting flag as information indicating the communication setting to be applied to the vehicle; the in-vehicle controller includes an in-vehicle database that associates the communication setting flag with the communication setting of each of the switches provided on each of the in-vehicle networks; the in-vehicle controller refers to the communication setting flag notified from the external controller and the in-vehicle database, and extracts the communication setting of each of the switches corresponding to the communication setting flag; and controlling the communication settings of each of the switches provided on the in-vehicle network in the vehicle based on the extracted communication settings.

6. An in-vehicle network updating system according to claim 5.

7. An in-vehicle network updating method executed by an in-vehicle network updating system including an external controller provided outside a vehicle and an in-vehicle controller provided in the vehicle, A first step of the external controller acquiring the configuration information of the vehicle, the external controller including an external database in which configuration information of a plurality of in-vehicle networks having different configurations is associated with information indicating communication settings corresponding to each of the in-vehicle networks; a second step of the external controller extracting information indicating the communication settings to be applied to the vehicle by referring to the acquired configuration information and the external database; a third step of the external controller notifying the in-vehicle controller of information indicating the extracted communication setting; and a fourth step of controlling communication settings of each switch, which is a data transfer device provided on the in-vehicle network in the vehicle, by the in-vehicle controller based on the notified information indicating the communication settings. How to update an in-vehicle network.

8. the third step being a step of the external controller notifying the in-vehicle controller of a communication setting flag as information indicating the communication setting to be applied to the vehicle; The fourth step is a fifth step in which the in-vehicle controller includes an in-vehicle database in which the communication setting flag and the communication setting of each of the switches provided on each of the in-vehicle networks are associated with each other, and the in-vehicle controller refers to the communication setting flag notified from the external controller and the in-vehicle database to extract the communication setting of each of the switches corresponding to the communication setting flag; and a sixth step of controlling the communication settings of each of the switches provided on the in-vehicle network in the vehicle by the in-vehicle controller based on the extracted information indicating the communication settings. The in-vehicle network updating method according to claim 7.

9. A program executed by an external controller provided outside the vehicle, The external controller includes an external database that associates configuration information of a plurality of in-vehicle networks having different configurations with information indicating communication settings corresponding to each of the in-vehicle networks, acquiring the configuration information of the vehicle; extracting information indicating the communication settings to be applied to the vehicle by referring to the acquired configuration information and the external database; notifying an in-vehicle controller provided in the vehicle of the extracted information indicating the communication setting. program.

10. The external controller includes the external database in which the configuration information of the in-vehicle network is associated with a communication setting flag. extracting the communication setting flag as information indicating the communication setting by referring to the configuration information of the in-vehicle network applied to the vehicle and the external database; notifying the vehicle controller of the extracted communication setting flag. The program according to claim 9.

11. A program executed by an in-vehicle controller provided in a vehicle, The vehicle controller includes: Based on information indicating communication settings notified from an external controller provided outside the vehicle, the communication settings of each switch, which is a data transfer device provided on an in-vehicle network in the vehicle, are controlled. program.

12. The in-vehicle controller includes an in-vehicle database that associates a communication setting flag with the communication setting of each switch provided on each in-vehicle network, With reference to the communication setting flag notified from the external controller and the in-vehicle database, extracting the communication setting of each of the switches corresponding to the communication setting flag, and controlling the communication setting of each of the switches provided on the in-vehicle network in the vehicle based on the extracted communication setting. The program according to claim 11.

Images