JP2024066145A - Setting device - Google Patents

Abstract

[Problem] To appropriately update communication settings of an in-vehicle network in response to the connection of a new in-vehicle device. [Solution] An SDN controller 15 that controls communication settings of multiple SDN switches 12 that are installed in an in-vehicle network 10 and perform frame forwarding has a memory 21 in which multiple pieces of setting information are stored. The SDN controller 15 performs selection processing and update processing when an in-vehicle device 14 that performs frame communication is connected to the in-vehicle network. The selection processing is processing for selecting one of the multiple pieces of setting information based on type information of the newly connected in-vehicle device 14. The update processing is processing for updating the communication settings of each SDN switch 12 based on the setting information selected in the selection processing. [Selected Figure] Figure 1

Description

The present invention relates to a setting device that controls communication settings of a relay device in an in-vehicle network.

Patent Document 1 describes an SDN (Software Defined Networking) system that can change the network configuration and settings without changing the hardware configuration by controlling communication devices with software. The SDN system includes multiple SDN switches that act as frame relay devices, and an SDN controller that updates the communication settings of each SDN switch.

JP 2017-169044 A

It is conceivable that an SDN system like the one described above could be used for an in-vehicle network. Meanwhile, new in-vehicle devices may be added to the in-vehicle network in order to add functions, etc. When the configuration of the in-vehicle network changes due to the connection of new in-vehicle devices, it is necessary to appropriately update the communication settings of the SDN switch.

The setting device that solves the above problem is a device that controls the communication settings of multiple relay devices that are installed in an in-vehicle network and perform frame forwarding, and has a storage unit that stores multiple pieces of setting information. The setting device performs a selection process and an update process when an in-vehicle device that performs frame communication is connected to the in-vehicle network. The selection process is a process of selecting one of the multiple pieces of setting information based on type information of the in-vehicle device. The update process is a process of updating the communication settings of the multiple relay devices based on the setting information selected in the selection process.

When a new in-vehicle device is connected to the in-vehicle network, the setting device selects one of the multiple setting information stored in the memory unit and updates the communication settings of the multiple relay devices based on the selected setting information. In other words, the setting information is information that indicates the communication settings of each relay device to be updated.

On the other hand, the type of communication that an in-vehicle device newly connected to the in-vehicle network will perform is determined to some extent by the type of the in-vehicle device. Therefore, based on the type information of the in-vehicle device newly connected to the in-vehicle network, it is possible to select setting information that corresponds to the state in which the in-vehicle device is connected. Therefore, the setting device has the effect of being able to appropriately update the communication settings of the in-vehicle network in response to the connection of a new in-vehicle device.

FIG. 2 is a diagram illustrating a configuration of a setting device according to the first embodiment. 11 is a sequence diagram showing an example of an update operation of communication settings in the embodiment. FIG. 13 is a sequence diagram showing another example of the communication setting update operation in the embodiment. FIG. FIG. 11 is a diagram illustrating a schematic configuration of an OTA master installed in an in-vehicle network in which a setting device according to a second embodiment is provided. 11 is a sequence diagram showing an example of an update operation of setting information and communication settings in the embodiment. FIG. 13 is a sequence diagram showing another example of the communication setting update operation in the embodiment. FIG.

First Embodiment
Hereinafter, a first embodiment of the setting device will be described in detail with reference to FIGS.
<Configuration of in-vehicle network and setting device>
First, the configuration of an in-vehicle network 10 to which the present embodiment is applied and a setting device of the present embodiment will be described with reference to Fig. 1. As shown in Fig. 1, the in-vehicle network 10 includes a plurality of SDN switches 12. The SDN switches 12 are connected to each other via a network line 13. The SDN switches 12 are connected to in-vehicle devices 14, respectively. The in-vehicle devices 14 are devices that transmit and receive frames to each other via the in-vehicle network 10. The in-vehicle devices 14 include various ECUs (Electronic Control Units), sensors, car navigation systems, etc. that are mounted on the vehicle. Meanwhile, the SDN switch 12 is a relay device that transfers frames transmitted and received by the in-vehicle devices 14.

An SDN controller 15 is connected to one of the SDN switches 12. The SDN controller 15 is a setting device that controls the communication settings of each SDN switch 12. The communication settings define the rules for frame forwarding, such as the communication path of frames between the in-vehicle devices 14, restrictions on the communication path for security purposes, and adjustments to the forwarding order and amount of forwarding for quality of service (QoS). For example, the communication settings include a routing table that specifies the forwarding destination of frames for each destination.

The SDN controller 15 includes a CPU 20 and a memory 21. The CPU 20 executes processing related to updating communication settings. The memory 21 stores in advance programs and data used in the processing of the CPU 20.

<Connecting new in-vehicle devices to the in-vehicle network>
In order to add a function to the vehicle, a new in-vehicle device 14 may be connected to the in-vehicle network 10. The connection of the new in-vehicle device 14 to the in-vehicle network 10 here includes the following cases in addition to the case where the new in-vehicle device 14 is additionally installed in the vehicle.

Currently, it is conceivable that an in-vehicle device 14 for implementing a function that is prohibited by law may be installed in a vehicle in advance in a disabled state in anticipation of future changes to the law. A disabled in-vehicle device 14 is treated by the in-vehicle network 10 as not existing, even if it is physically connected to the in-vehicle network 10. When such an in-vehicle device 14 is enabled, it is treated as being newly connected to the in-vehicle network 10. In this embodiment, a connection by enabling an in-vehicle device 14 installed in a disabled state is also included in the connection of a new in-vehicle device 14 to the in-vehicle network 10.

In the following description, the in-vehicle device 14 newly connected to the in-vehicle network 10 is referred to as new in-vehicle device 14A. The new in-vehicle device 14A is, for example, an ECU or a sensor. In addition, a unit having one or more ECUs, one or more sensors, and an SDN switch to which they are connected may be connected to the in-vehicle network 10. For example, a unit for adding functions required for the vehicle's automatic driving to the vehicle may include a camera or sensor for recognizing objects around the vehicle, an ECU for calculating the vehicle's driving route and driving speed, and an SDN switch to which they are connected. If such a unit is newly connected to the in-vehicle network 10, it may also be new in-vehicle device 14A.

The configuration of the in-vehicle network 10 changes when new in-vehicle device 14A is connected. The connection of new in-vehicle device 14A also changes the state of frame communication within the in-vehicle network 10. In response to this, the SDN controller 15 updates the communication settings of each SDN switch 12 when new in-vehicle device 14A is connected.

The aspect of the communication performed by the new in-vehicle device 14A differs depending on the type. For example, if the new in-vehicle device 14A is a sensor, the sensor basically only transmits frames. Furthermore, the in-vehicle device 14 to which the sensor transmits frames is limited depending on the object detected by the sensor. In addition, the amount of communication and the priority of the communication performed by the new in-vehicle device 14A differ depending on the type of the new in-vehicle device 14A. For example, if the new in-vehicle device 14A is a unit that adds a function necessary for automatic driving as described above, the amount of communication performed by the unit will be large and the communication will have a high priority. In this way, the communication settings required for each SDN switch 12 differ depending on the type of the new in-vehicle device 14A. In addition, even if the new in-vehicle device 14A is the same type, there may be devices with high and low communication volumes. In addition, even if the new in-vehicle device 14A is the same type, it may be connected to different positions in the in-vehicle network 10. As described above, the communication settings of each SDN switch 12 corresponding to the connection of new in-vehicle equipment 14A will differ depending on the type, communication volume, and connection location of the new in-vehicle equipment 14A.

In response to this, multiple pieces of setting information are pre-stored in the memory 21 of the SDN controller 15. The setting information is information indicating the communication settings of each SDN switch 12 that are updated when a new in-vehicle device 14A is connected. The multiple pieces of setting information stored in the memory 21 are classified according to the type, communication volume, and connection location of the new in-vehicle device 14A.

<Update communication settings>
Next, the update of the communication settings of the in-vehicle network 10 accompanying the connection of the new in-vehicle device 14A will be described with reference to FIG.

Figure 2 shows an example of the operation of each device related to updating the communication settings of the in-vehicle network 10. Figure 2 shows the operation that occurs after a new in-vehicle device 14A is physically connected to one of the SDN switches 12 installed in the in-vehicle network 10 and a connection is established between the SDN switch 12 and the new in-vehicle device 14A. Note that Figure 2 shows two of the SDN switches 12 installed in the in-vehicle network 10 and one of the in-vehicle devices 14 already connected to the in-vehicle network 10 as representatives of each.

When the new in-vehicle device 14A is connected to the in-vehicle network 10, it transmits its type information to the SDN controller 15 (S1). The type information is information for identifying the type of the new in-vehicle device 14A. In the in-vehicle network 10, a unique IP address and MAC address are set for each model of the in-vehicle device 14. Therefore, the IP address and MAC address of the new in-vehicle device 14A can be type information for identifying the type of the new in-vehicle device 14A. In addition, the product number and serial number of the new in-vehicle device 14A can also be type information for identifying the type of the new in-vehicle device 14A. In addition, in the in-vehicle device 14, functions may be added or deleted by updating the software. Therefore, even if the in-vehicle device 14 is the same, the content of the communication to be performed may differ depending on the software version. In such a case, when updating the communication settings, it may be appropriate to treat the same in-vehicle device 14 as being of different types depending on the software version. In this embodiment, one or more of the IP address, MAC address, product number, serial number, and software version of the new in-vehicle device 14A are used as type information.

In addition, the in-vehicle device 14 pre-records information on the communication volume, such as the average and maximum values of the communication volume. The new in-vehicle device 14A also acquires the identifier (ID) of the SDN switch 12 to which it is connected. The identifier of the SDN switch 12 is information that indicates the connection position of the new in-vehicle device 14A in the in-vehicle network 10. In S1 of FIG. 2, the new in-vehicle device 14A transmits information on its communication volume and connection position, together with type information, to the SDN controller 15.

In response to this, the SDN controller 15 selects setting information that matches the information received from the new in-vehicle device 14A from among the multiple setting information stored in the memory 21 (S2). Then, the SDN controller 15 instructs each SDN switch 12 to update the communication settings based on the selected setting information (S3). Each SDN switch 12 updates the communication settings based on the instruction (S4). Then, when each SDN switch 12 completes the update of the communication settings, it notifies the SDN controller 15 of the completion (S5). When the SDN controller 15 receives the update completion notification from all SDN switches 12, it notifies each connected in-vehicle device 14 and the new in-vehicle device 14A that the update of the communication settings of the entire in-vehicle network 10 has been completed (S6). In response to the notification, each connected in-vehicle device 14 starts frame communication (S7). Also, the new in-vehicle device 14A is enabled in response to the notification and starts frame communication (S7).

In addition, after the vehicle is shipped, a model of on-board device 14 that can be connected to the on-board network 10 may be added. In such a case, the memory 21 of the SDN controller 15 may not store setting information corresponding to the added on-board device 14. In such a case, the added on-board device 14 is provided with setting information indicating the communication settings of each SDN switch 12 when the on-board device 14 is connected to the on-board network 10, and the communication settings are updated based on the setting information.

Figure 3 shows an example of the operation of each device related to the update of communication settings in such a case. In this case, when the new in-vehicle device 14A is connected to the in-vehicle network 10, it transmits information on its type, communication volume, and connection location to the SDN controller 15 (S10). The SDN controller 15 then tries to select setting information that matches the received information, but in this case, such setting information does not exist. When the SDN controller 15 confirms that matching setting information is not stored (S11), it requests the new in-vehicle device 14A to transmit the setting information stored in the new in-vehicle device 14A (S12). In response to this request, the new in-vehicle device 14A transmits the setting information (S13), and the SDN controller 15 instructs each SDN switch 12 to update the communication settings based on the setting information received from the new in-vehicle device 14A (S14). The subsequent operations are the same as those in Figure 2.

<Effects of the embodiment>
The effects of the setting device of the present embodiment described above will now be described.
The SDN controller 15 has a memory 21 in which a plurality of pieces of setting information are stored. Each piece of setting information includes, in addition to frame transport route settings, frame transport service quality settings and communication route restriction settings for security purposes.

On the other hand, when the new in-vehicle device 14A is connected to the in-vehicle network 10, it transmits information on its type, communication volume, and connection location to the SDN controller 15. The SDN controller 15 selects the setting information that matches the information received from the new in-vehicle device 14A from among the multiple setting information stored in the memory 21. The SDN controller 15 then updates the communication settings of each SDN switch 12 based on the selected setting information. This updates the frame transport path, service quality, and communication path restriction settings of each SDN switch 12. When the SDN controller 15 confirms that the communication setting updates of all SDN switches 12 have been completed, it notifies each in-vehicle device 14 already connected to the in-vehicle network 10 and the new in-vehicle device 14A of the completion of the updates. Upon receiving this notification, each in-vehicle device 14 and the new in-vehicle device 14A start frame notification.

There may be cases where the setting information that matches the information received from the new in-vehicle device 14A is not stored in the memory 21, i.e., the setting information to be selected is not included among the multiple setting information stored in the memory 21. In this case, the SDN controller 15 updates the communication settings of each SDN switch 12 based on the setting information stored in the new in-vehicle device 14A.

As described above, in this embodiment, the SDN switch 12 corresponds to a relay device, the SDN controller 15 corresponds to a setting device, and the memory 21 corresponds to a storage unit. The process of S2 in FIG. 2 corresponds to a selection process that selects one of the multiple setting information based on the type information of the in-vehicle device 14. The process of S3 in FIG. 2 corresponds to an update process that updates the communication settings of the multiple relay devices based on the setting information selected in the selection process.

According to the present embodiment described above, the following effects can be obtained.
(1) The SDN controller 15 has a memory 21 in which multiple pieces of setting information are stored. When a new in-vehicle device 14A is connected to the in-vehicle network 10, the SDN controller 15 performs a selection process (S2) and an update process (S3). The selection process is a process of selecting one of the multiple pieces of setting information based on type information of the new in-vehicle device 14A. The update process is a process (S3) of updating the communication settings of each SDN switch 12 based on the setting information selected in the selection process. Therefore, the communication settings of each SDN switch 12 can be updated to appropriate communication settings according to the type of the in-vehicle device 14 newly connected to the in-vehicle network 10.

(2) In the selection process (S2), the SDN controller 15 selects the setting information based on the communication volume information of the new in-vehicle device 14A. Therefore, the communication settings of each SDN switch 12 can be updated to the appropriate communication settings according to the communication volume of the new in-vehicle device 14A.

(3) In the selection process (S2), the SDN controller 15 selects the setting information based on the information on the connection position of the new in-vehicle device 14A in the in-vehicle network 10. Therefore, the communication settings of each SDN switch 12 can be updated to the appropriate communication settings according to the connection position of the new in-vehicle device 14A.

(4) Information on the type, communication volume, and connection location of the new in-vehicle device 14A can be more easily obtained from the new in-vehicle device 14A than from the SDN controller 15. The SDN controller 15 obtains the type information, communication volume information, and connection location information from the new in-vehicle device 14A. This makes it easier to obtain the information necessary to select setting information.

(5) Each piece of setting information stored in memory 21 includes information on setting the quality of service for frame communication and information on setting communication path restrictions for security. Therefore, in response to a change in the configuration of the in-vehicle network 10 due to the connection of a new in-vehicle device 14A, advanced communication control such as setting the quality of service for frame transport and setting communication path restrictions for security can be implemented.

(6) Due to a difference in the release dates of the vehicle and the new in-vehicle device 14A, the setting information stored in the memory 21 may not include setting information corresponding to the new in-vehicle device 14A. In such a case, the SDN controller 15 acquires the setting information stored in the new in-vehicle device 14A and updates the communication settings of each SDN switch 12 based on the setting information. Therefore, even if the setting information corresponding to the new in-vehicle device 14A is not stored in the memory 21, the communication settings of each SDN switch 12 corresponding to the new in-vehicle device 14A can be updated.

Second Embodiment
Next, a second embodiment of the setting device will be described in detail with reference to Figures 4 to 6. In this embodiment, components common to the above embodiment will be denoted by the same reference numerals and detailed description thereof will be omitted.

<Configuration of Setting Device of Second Embodiment>
The configuration of the SDN controller 15 of this embodiment is the same as that of the first embodiment. The SDN controller 15 of this embodiment also updates the communication settings in the same manner as in the first embodiment. Meanwhile, in the in-vehicle network 10 in which the SDN controller 15 of this embodiment is installed, in addition to the SDN switch 12 and the in-vehicle device 14, an OTA master 30 is installed as a management device that manages software updates of the in-vehicle device 14.

As shown in FIG. 4, the OTA master 30 is connected to one of the multiple SDN switches 12 set in the in-vehicle network 10. The OTA master 30 is configured as an electronic control device including a CPU 31 and a memory 32. The CPU 31 executes processing for updating the software of the in-vehicle device 14. The memory 32 stores programs and data used in the processing of the CPU 31. The OTA master 30 is connected to a wireless communication device 33. The wireless communication device 33 establishes data communication with a data center 35 outside the vehicle via a wireless communication network 34 such as a mobile communication network. The data center 35 distributes update data for the software of the in-vehicle device 14 to the OTA master 30 of each vehicle via the wireless communication network 34. The OTA master 30 then updates the software of the in-vehicle device 14 to be updated based on the update data distributed from the data center 35. The in-vehicle device 14 is temporarily disconnected from the in-vehicle network 10 during the software update. After the software update is completed, the in-vehicle device 14 is reconnected to the in-vehicle network 10. The data center 35 also distributes update data for the setting information stored in the memory 21 of the SDN controller 15. The OTA master 30 also manages updates to the setting information.

The functions of the in-vehicle device 14 may change due to software updates. The changes in functions may also change the manner in which the in-vehicle device 14 communicates. In this embodiment, the SDN controller 15 updates the communication settings of each SDN switch 12 when the in-vehicle device 14 is reconnected after a software update.

<Updating setting information and communication settings>
Next, the update of the setting information and the communication settings in this embodiment will be described with reference to Fig. 5. Fig. 5 shows the operations of the data center 35, the OTA master 30, the SDN controller 15, and the SDN switch 12 related to the update of the setting information and the communication settings. Note that Fig. 5 shows one of the multiple SDN switches 12 installed in the in-vehicle network 10 as a representative thereof.

In the case of FIG. 5, the data center 35 distributes update data for the setting information prior to distribution of update data for the software of the in-vehicle device 14 (S20). When the OTA master 30 receives the update data from the data center 35, it transmits the update data to the SDN controller 15 (S21). The SDN controller 15 updates the setting information stored in the memory 21 based on the update data (S22). The updated setting information includes setting information indicating the communication settings of each SDN controller 15 corresponding to the software update of the in-vehicle device 14. Note that the setting information is updated not only when the software is updated, but also when a new model of the in-vehicle device 14 that can be connected to the in-vehicle network 10 is added, for example.

Then, the data center 35 distributes update data for the software of the in-vehicle device 14 (S23). When the OTA master 30 receives the update data from the data center 35, it updates the software of the in-vehicle device 14 to be updated based on the update data (S24). Then, when the software update is completed, the OTA master 30 notifies the SDN controller 15 of the completion (S25). At this time, the OTA master 30 also transmits information on the type, communication volume, and connection position of the in-vehicle device 14 whose software has been updated to the SDN controller 15 (S25). The type information transmitted at this time includes the version of the updated software.

The SDN controller 15 starts the process of updating the communication settings of each SDN switch 12 when it receives notification of the completion of the software update and information from the OTA master 30. That is, the SDN controller 15 selects the setting information that matches the information received from the OTA master 30 from among the multiple setting information stored in the memory 21 (S26). Then, the SDN controller 15 instructs each SDN switch 12 to update the communication settings based on the selected setting information (S27).

Each SDN switch 12 updates the communication settings based on the instructions (S28). Then, when each SDN switch 12 has completed updating the communication settings, it notifies the SDN controller 15 of the completion (S29). When the SDN controller 15 receives notifications of update completion from all SDN switches 12, it notifies the in-vehicle device 14 that updated its software that the update of the communication settings for the entire in-vehicle network 10 has been completed (S30). In response to this notification, the in-vehicle device 14 is enabled (activated) and starts frame communication (S31).

Note that updating the setting information and updating the software may each require the user's permission. If the user permits a software update before permitting an update of the setting information, the software update will be carried out before the setting information is updated. In such a case, it may happen that the setting information stored in memory 21 does not include setting information that is compatible with the updated software.

FIG. 6 shows the operations of the data center 35, the OTA master 30, the SDN controller 15, and the SDN switch 12 relating to the update of communication settings in such a case.
In this case, the data center 35 distributes update data for the software of the in-vehicle device 14 (S50). The OTA master 30 updates the software of the in-vehicle device 14 to be updated based on the update data (S51). Then, when the software update is completed, the OTA master 30 notifies the SDN controller 15 of the completion (S52). The OTA master 30 also transmits information such as the type of the in-vehicle device 14 whose software has been updated to the SDN controller 15 (S52). However, in this case, the multiple pieces of setting information stored in the memory 21 do not include setting information that matches the type information received from the OTA master 30. At this time, the SDN controller 15 notifies the OTA master 30 that there is no setting information that matches the memory 21 (S53). In response to this notification, the OTA master 30 requests the data center 35 to distribute setting information corresponding to the previously performed software update (S54). In response to this request, the setting information distributed by the data center 35 is sent to the SDN controller 15 via the OTA master 30 (S55). The SDN controller 15 then instructs each SDN switch 12 to update the communication settings based on the received setting information (S56). The subsequent operations are the same as those in FIG. 5.

<Effects of the embodiment>
The effects of the setting device of the present embodiment described above will now be described.
The OTA master 30 updates the software of the in-vehicle device 14 based on the update data distributed from the data center 35. The OTA master 30 also updates the setting information stored in the memory 21 of the SDN controller 15 based on the update data distributed from the data center 35.

When the software update of the in-vehicle device 14 is completed, the OTA master 30 transmits information on the type, communication volume, and connection location of the in-vehicle device 14 to the SDN controller 15. As a result, the SDN controller 15 obtains the type, communication volume, and connection location information used to select setting information from the OTA master 30. Next, the SDN controller 15 selects one of the multiple setting information stored in the memory 21 based on that information. Then, the SDN controller 15 updates the communication settings of each SDN switch 12 based on the selected setting information.

In some cases, the multiple pieces of setting information stored in the memory 21 do not include setting information that matches the information received from the OTA master 30. In this case, the SDN controller 15 obtains setting information used to update the communication settings of the SDN switch 12 from a data center 35 outside the vehicle.

In this embodiment, the OTA master 30 corresponds to a management device that manages software updates of the in-vehicle devices 14 connected to the in-vehicle network 10. In addition, the process of S26 in FIG. 5 corresponds to the selection process, and the process of S27 corresponds to the update process.

According to the present embodiment described above, in addition to the above effects (1) to (6), the following effects can be achieved.
(7) In the in-vehicle network 10 in which the SDN controller 15 of the present embodiment is installed, an OTA master 30 that manages software updates of the in-vehicle devices 14 is installed. The functions of the in-vehicle devices 14 may be changed by software updates, and the communication settings of the in-vehicle network 10 may need to be updated. In response to this, the OTA master 30 notifies the SDN controller 15 when the software update of the in-vehicle devices 14 is completed. Then, in response to receiving the notification, the SDN controller 15 performs a selection process (S26) and an update process (S27) to update the communication settings of each SDN switch 12. That is, the SDN controller 15 updates the communication settings of each SDN switch 12 upon completion of the software update of the in-vehicle devices 14. Therefore, the communication settings of the in-vehicle network 10 can be updated in response to the software update of the in-vehicle devices 14.

(8) The SDN controller 15 acquires type information and the like used to select the setting information in the above selection process (S26) from the OTA master 30. The type and communication volume of the in-vehicle device 14 may change due to a software update. The type and communication volume of the in-vehicle device 14 after the software update are known by the OTA master 30, which manages the software update. In addition, the OTA master 30 also recognizes the connection position to the in-vehicle network 10 of the in-vehicle device 14 whose software has been updated. Therefore, the SDN controller 15 can easily and accurately acquire information used to select the setting information.

(9) If the multiple pieces of setting information stored in the memory 21 do not contain setting information that matches the type and other information acquired from the OTA master 30, the SDN controller 15 acquires setting information from an external data center 35. Therefore, even if appropriate setting information is not stored in the memory 21, the communication settings can be appropriately updated.

(10) The OTA master 30 updates multiple pieces of setting information stored in the memory 21 of the SDN controller 15 based on update data distributed from the data center 35. That is, multiple pieces of setting information are stored in the memory 21 of the SDN controller 15 in a state in which updates by the OTA master 30 are permitted. Therefore, each piece of setting information stored in the memory 21 can be updated appropriately in response to changes in the functions of the in-vehicle device 14 due to software updates, etc.

<Other embodiments>
The above embodiment can be modified as follows. The above embodiment and the following modified examples can be combined with each other to the extent that they are not technically inconsistent. The present disclosure is not limited to these examples, but is intended to include all modifications within the meaning and scope of the claims.

(About updating software and settings information)
In the second embodiment, the software update and the setting information update by the OTA master 30 may be performed together.

The OTA master 30 may be configured to update the software of the in-vehicle device 14 but not update the setting information. In this case, multiple pieces of setting information are stored in the memory 21 of the SDN controller 15 in a state where updates by the OTA master 30 are not permitted.

The SDN controller 15 may obtain information such as the type used to select the setting information in the selection process of S26 in FIG. 5 from the in-vehicle device 14 whose software has been updated.
5, the OTA master 30 notifies the completion of the software update and transmits information such as the type of the in-vehicle device 14 whose software has been updated. The transmission of the information such as the type may be used as the notification of the completion of the software update. In this case, in S25, only the information such as the type is transmitted from the OTA master 30 to the SDN controller 15.

(Regarding selection process)
The selection of setting information in the selection process may be performed without using either or both of the information on the communication volume of the in-vehicle device 14 and the information on the connection position of the in-vehicle device 14 in the in-vehicle network 10 .

- The type information of the in-vehicle device 14 used to select the setting information in the selection process may be information other than that exemplified in the above embodiment, as long as the information is capable of identifying the type of the in-vehicle device 14.

(Regarding the operation of updating communication settings when the setting information to be selected in the selection process is not included in the multiple setting information stored in the memory 21)
If an OTA master 30 is installed in the in-vehicle network 10, the processes of S12 and S13 in FIG. 3 may be replaced with processes of acquiring setting information from a data center 35 outside the vehicle via the OTA master 30.

- The processes of S12 and S13 in FIG. 3 and S54 and S55 in FIG. 6 may be replaced with processes of obtaining setting information from a data center 35 outside the vehicle via a diagnostic tool connected by wire to the in-vehicle network 10.

- The update operation when the setting information to be selected in the selection process is not included among the multiple setting information stored in memory 21, i.e., the update operation shown in Figures 3 and 6, is not required. For example, in the above case, the communication settings may be updated manually.

(others)
The SDN controller 15 of the second embodiment may be configured not to update the communication settings when a new in-vehicle device 14 is connected.

- Some or all of the multiple SDN switches 12 installed in the in-vehicle network 10 may be replaced with other relay devices that forward frames, such as routers, and that can update communication settings using software.

- The in-vehicle network 10 in the above embodiment is configured so that the in-vehicle devices 14 communicate at the data link layer (L2). The in-vehicle network 10 may be configured so that communication between the in-vehicle devices 14 occurs at a layer other than the data link layer. That is, the SDN controller 15 in the above embodiment may be configured as a device that controls the communication settings of each relay device in an in-vehicle network provided with multiple relay devices that forward messages.

The SDN controller 15 may be configured as any configuration having the function of a setting device that updates the communication settings of multiple communication devices installed in the in-vehicle network 10. The OTA master 30 may be configured as any configuration having the function of a management device that manages software updates of the in-vehicle devices 14 connected to the in-vehicle network 10. For example, one or both of the functions of the SDN controller 15 and the OTA master 30 in the above embodiment may be provided by one of the ECUs. That is, the setting device and the update device may be configured as a circuit (circuitry) including one or more processors that execute various processes according to a computer program (software). The setting device may be configured as a circuit including one or more dedicated hardware circuits, such as application specific integrated circuits (ASICs), that execute at least a part of the various processes, or a combination thereof. The processor includes a CPU and memories such as RAM and ROM. The memory stores program code or instructions configured to cause the CPU to execute the processes. The memory, i.e., the computer-readable medium, includes any available medium that can be accessed by a general-purpose or dedicated computer.

<Additional Notes>
[Appendix 1] A setting device that controls communication settings of multiple relay devices that are installed in an in-vehicle network and perform frame forwarding, the setting device having a memory unit in which multiple setting information is stored, and that performs a selection process and an update process when an in-vehicle device that performs frame communication is connected to the in-vehicle network, the selection process being a process of selecting one of the multiple setting information based on type information of the in-vehicle device, and the update process being a process of updating the communication settings of the multiple relay devices based on the setting information selected in the selection process.

[Appendix 2] The setting device described in [Appendix 1], in which the type information includes at least one of the IP address, MAC address, product number, serial number, and software version of the in-vehicle device.

[Appendix 3] The setting device described in [Appendix 1] or [Appendix 2], in which the information used to select the setting information in the selection process includes the type information and information on the connection position of the in-vehicle device in the in-vehicle network.

[Appendix 4] The setting device described in any one of [Appendix 1] to [Appendix 3], in which the information used to select the setting information in the selection process includes the type information and information on the communication volume of the in-vehicle device.

[Supplementary Note 5] The setting device according to any one of [Supplementary Note 1] to [Supplementary Note 4], which acquires the type information from the in-vehicle device when the in-vehicle device is newly connected to the in-vehicle network.
[Appendix 6] A setting device described in any of [Appendix 1] to [Appendix 5], wherein the setting information includes information on setting the service quality of the frame communication and information on setting communication path restrictions for security purposes.

[Appendix 7] The in-vehicle network is provided with a management device that manages software updates for in-vehicle devices connected to the in-vehicle network, and the management device notifies the setting device when the software update is complete, and the setting device performs the selection process and the update process in response to receiving the notification. The setting device described in any one of [Appendix 1] to [Appendix 6].

[Supplementary Note 8] The setting device according to [Supplementary Note 7], which acquires the type information from the management device.
[Supplementary Note 9] The setting device according to [Supplementary Note 7] or [Supplementary Note 8], wherein the plurality of setting information are stored in the memory unit in a state in which updating by the management device is permitted.

[Appendix 10] A setting device according to any one of [Appendix 1] to [Appendix 9], which, if the plurality of pieces of setting information stored in the storage unit does not include the setting information to be selected in the selection process, acquires setting information from a data center outside the vehicle and updates the communication settings of the plurality of relay devices based on the acquired setting information.

[Appendix 11] The setting information is stored in the in-vehicle device, and if the setting information to be selected in the selection process is not included in the multiple setting information stored in the storage unit, the setting device updates the communication settings of the multiple relay devices based on the setting information stored in the in-vehicle device. [Appendix 1] to [Appendix 10].

[Appendix 12] A setting device that controls communication settings of multiple relay devices that are installed in an in-vehicle network and perform message transfer, the setting device having a storage unit that stores multiple pieces of setting information, and performing a selection process and an update process when an in-vehicle device that performs message communication is connected to the in-vehicle network, the selection process being a process of selecting one of the multiple pieces of setting information based on type information of the in-vehicle device, and the update process being a process of updating the communication settings of the multiple relay devices based on the setting information selected in the selection process.

[Appendix 13] The setting device described in [Appendix 12], in which the type information includes at least one of the IP address, MAC address, product number, serial number, and software version of the in-vehicle device.

[Appendix 14] The setting device described in [Appendix 12] or [Appendix 13], in which the information used to select the setting information in the selection process includes the type information and information on the connection position of the in-vehicle device in the in-vehicle network.

[Appendix 15] The setting device described in any one of [Appendix 12] to [Appendix 14], in which the information used to select the setting information in the selection process includes the type information and information on the communication volume of the in-vehicle device.

[Appendix 16] The setting device described in any one of [Appendix 12] to [Appendix 15] obtains the type information from the in-vehicle device when the in-vehicle device is newly connected to the in-vehicle network.

[Appendix 17] The setting device described in any one of [Appendix 12] to [Appendix 16], in which the setting information includes information on setting the quality of service of the message communication and information on setting communication path restrictions for security purposes.

[Appendix 18] The in-vehicle network is provided with a management device that manages software updates for in-vehicle devices connected to the in-vehicle network, and the management device notifies the setting device when the software update is complete, and the setting device performs the selection process and the update process in response to receiving the notification. A setting device as described in any one of [Appendix 12] to [Appendix 17].

[Supplementary Note 19] The setting device according to [Supplementary Note 18], which acquires the type information from the management device.
[Supplementary Note 20] The setting device according to [Supplementary Note 18] or [Supplementary Note 19], wherein the plurality of setting information are stored in the memory unit in a state in which updating by the management device is permitted.

[Appendix 21] A setting device according to any one of [Appendix 12] to [Appendix 20], which, if the plurality of pieces of setting information stored in the storage unit does not include the setting information to be selected in the selection process, acquires setting information from a data center outside the vehicle and updates the communication settings of the plurality of relay devices based on the acquired setting information.

[Appendix 22] The setting information is stored in the in-vehicle device, and if the setting information to be selected in the selection process is not included in the multiple setting information stored in the storage unit, the setting device updates the communication settings of the multiple relay devices based on the setting information stored in the in-vehicle device. [Appendix 12] to [Appendix 21].

10... In-vehicle network 12... SDN switch (relay device)
13: network line 14: in-vehicle device 14A: new in-vehicle device 15: SDN controller (setting device)
20...CPU
21...Memory (storage unit)
30... OTA master 31... CPU
32: Memory 33: Wireless communication device 34: Wireless communication network 35: Data center

Claims (11)

A setting device that controls communication settings of a plurality of relay devices that are installed in an in-vehicle network and perform frame forwarding,
A storage unit is provided in which a plurality of pieces of setting information are stored,
When an in-vehicle device that performs frame communication is connected to the in-vehicle network, the in-vehicle device performs a selection process and an update process;
the selection process is a process of selecting one of the plurality of pieces of setting information based on type information of the in-vehicle device,
The update process updates communication settings of the plurality of relay devices based on the setting information selected in the selection process. The setting device according to claim 1, wherein the type information includes at least one of the IP address, MAC address, product number, serial number, and software version of the in-vehicle device. The setting device according to claim 1, wherein the information used to select the setting information in the selection process includes the type information and information on the connection position of the in-vehicle device in the in-vehicle network. The setting device according to claim 1, wherein the information used to select the setting information in the selection process includes the type information and information on the communication volume of the in-vehicle device. The setting device according to claim 1, which acquires the type information from the in-vehicle device when the in-vehicle device is newly connected to the in-vehicle network. The setting device according to claim 1, wherein the setting information includes information on setting the quality of service of the frame communication and information on setting communication path restrictions for security. a management device that manages software updates of in-vehicle devices connected to the in-vehicle network is installed in the in-vehicle network;
the management device notifies the setting device when the software update is completed;
The setting device according to claim 1 , wherein the setting device performs the selection process and the update process in response to receiving the notification. The setting device according to claim 7, which acquires the type information from the management device. The setting device according to claim 7, wherein the plurality of pieces of setting information are stored in the storage unit in a state in which the setting information is allowed to be updated by the management device. The setting device according to claim 1, which, if the setting information to be selected in the selection process is not included in the multiple setting information stored in the storage unit, acquires setting information from a data center outside the vehicle and updates the communication settings of the multiple relay devices based on the acquired setting information. The setting device according to claim 1, wherein the setting information is stored in the in-vehicle device, and when the setting information to be selected in the selection process is not included in the multiple setting information stored in the storage unit, the setting device updates the communication settings of the multiple relay devices based on the setting information stored in the in-vehicle device.

Images