In-vehicle network system

[0067]FIG. 1 is a diagram illustrating an in-vehicle network system 100 according to a first embodiment. The in-vehicle network system 100 is mounted on a vehicle.

[0068]The in-vehicle network system 100 includes relay devices (hereinafter referred to as gateway electronic control units (ECUs)) 110A, 110B, a plurality of controllers (hereinafter referred to as ECUs) 121, 122, 123, 124, 125, 126, 127, 128, communication lines 131, 132, 133, 134, 135, 136, 137, 138, 139, 141, and a data link connector (DLC) 140. Sensors 151, 152 are connected to the ECUs 121, 122, respectively, and a switch 153 is connected to the ECU 123.

[0069]The in-vehicle network system 100 uses, for example, an Ethernet protocol as a communication protocol. The communication lines 131, 132, 133, 134, 135, 136, 137, 138, 139, 141 do not indicate physical buses, and are virtual communication lines that build virtual local area networks (VLANs) 130A, 130B, 130C according to the Ethernet protocol.

[0070]The VLAN 130A is b

[0175]FIG. 11 is a diagram illustrating a relationship between a path for data to be transferred and an L2 switch, an L3 switch, and an L7 switch in an in-vehicle network system 200 according to a second embodiment.

[0176]The in-vehicle network system 200 according to the second embodiment has a configuration obtained by adding an ECU 129, a communication line 231, and a data communication module (DCM) 600 to the in-vehicle network system 100 according to the first embodiment.

[0177]The ECU 129 is connected to a port 7 of a gateway ECU 110B via the communication line 231. In the second embodiment, the ECU 129 is used as an example of a connector capable of connecting the DCM 600.

[0178]The VLAN 130D is built by the communication line 231, and the gateway ECU 110B and ECU 129 are connected thereto. The communication line 231 is an example of a second communication line. In FIG. 11, anything is not connected to the DLC 140.

[0179]Since a configuration other than the above-described configura