JP4457966B2 - Data relay device, terminal device, and data communication system - Google Patents

Description

  The present invention relates to a data relay device that can determine a transfer destination network based on a data identifier that can identify the type of a data body included in a data frame, a terminal device thereof, and a data communication system. It can be suitably applied.

  An in-vehicle LAN (a local area network mounted on a vehicle) may be divided into, for example, a main system main network and a sub-network connected thereto. In such a case, for example, a CAN (Controller Area Network) is adopted for the main network, and a protocol suitable for each application is used for the sub-network, for example, LIN (Local Interconnect Network), J1850 and BEAN (BEAN (for the vehicle body system). Body Electronics Area Network), TTCAN and FlexRay for control systems, Safe-by-Wire and BST for safety systems, MOST (Media Oriented System Transport) and D2B (Digital Domestic Bus) for information systems, etc. Yes. The names of these protocols including CAN are registered trademarks.

  In order to connect networks having different protocols to each other as described above, a data relay device generally called “gateway” is used. However, whenever a change occurs in the connection configuration of a terminal device (also referred to as a “node”) that performs data communication via these networks, so-called network configuration, the network information of the data relay device or the terminal device is changed to change the network. There was a problem that had to be rebuilt.

  Thus, as a technique that can eliminate the complexity of terminal device setting changes accompanying network configuration changes (addition or deletion of nodes), for example, “Data Relay Device and Multiplex Communication System” disclosed in Patent Document 1 below is disclosed. Proposed. In this disclosed technique, for a data frame (with a header added to the data body) transmitted from each node (terminal device) to the data relay device, the relay destination is referred to by the relay destination table from the data type of the data body. In this configuration, a header corresponding to the relay destination protocol is added to the data body, and then transmitted to the relay destination network (Patent Document 1; paragraph numbers 0022 to 0032).

As a result, even if there is a change in the network configuration due to a change in the function of the node, etc., by changing the contents of the relay destination table etc., it becomes substantially equivalent to the setting change of the transmission source node. It can be handled by simply resetting (Patent Document 1; paragraphs 0009 and 0036).
JP 2002-26924 A

  However, according to the technology disclosed in Patent Document 1, the setting change of each terminal device associated with the network reconstruction is no longer necessary, but the setting operation of the data relay device is still necessary. Therefore, when the network configuration is diverse, it is planned to change the data relay table and the like by rewriting or exchanging the ROM storing the relay destination table and header table of the data relay device (Patent Literature). 1; paragraph number 0036).

  In particular, assuming the construction of an in-vehicle LAN that can handle a wide variety of vehicles, if such data relay device setting operations are performed for each vehicle type, the ROM writing and replacement operations are frequently performed. In addition, the management of ROM data and replacement ROM becomes complicated. In addition, even when it is necessary to replace the data relay device due to a failure of the data relay device, such ROM writing or replacement work can occur. Therefore, the management of the ROM data and the replacement ROM is complicated. It is difficult to eliminate.

  In addition, it is possible to prepare multiple types of data relay devices with different settings for each network configuration in advance, but it is assumed depending on whether there are optional settings corresponding to the user specifications of the vehicle in addition to various types of vehicles. The number of types of network configurations to be made becomes enormous. For this reason, preparing data relay devices corresponding to various network configurations for each type is troublesome in managing the data relay device type information, and may cause erroneous assembly of the data relay devices. Invite a new problem.

  Furthermore, when the vehicle option setting is changed by the user, the network configuration at the time of shipment is different. Therefore, the data relay device ROM must be rewritten or replaced by reconfiguring the network. In such a case, the same problem as described above may occur.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a data relay device, a terminal device, and a data communication system that can reduce the burden of setting the data relay device related to the network configuration. Is to provide.

In order to achieve the above object, in the data relay apparatus according to claim 1, the data frame transmitted from one network [NW-n] is connected to another network [NW-1]. In the data relay device [20] that can be transferred to the terminal device [50a, 50b, 50c], the other destination of the transfer is determined based on the data identifier [received data ID] that can identify the type of the data body included in the data frame. A data relay apparatus including a relay destination determination unit [23b1] capable of determining the network [NW-1], which is received by the terminal apparatus [50a, etc.] with information transmitted from the terminal apparatus [50a, etc.]. Receiving type information receiving means [23a2] for receiving type information [received data ID] relating to the type of data body included in the data frame to be received, and the receiving type information receiving means Relay destination determining means generating means [23a5] capable of generating the relay destination determining means [23b1] based on the reception type information [received data ID] received by [23a2], and the reception type information [received data ID] ], The reception type information requesting means [23a3, 23a5] capable of requesting the terminal device [50a etc.] to transmit, the reception type information requesting means [23a3, 23a5] Sending a request for the reception type information [received data ID] for all of the plurality of terminal devices [50a, etc.] to the plurality of terminal devices [50a, etc.] that receive the transmission request of [data ID]. Technical features.
The numbers in [] can correspond to the symbols described in the [Best Mode for Carrying Out the Invention] column (the same applies hereinafter).

  Here, the “reception type information” relating to the type of the data body included in the data frame to be received by the terminal device is sufficient if it is information that can identify the type of the data body. In the embodiment described in the column of “Best Mode”, a data identifier [reception data ID] is used as an example of the “reception type information” for ease of information processing. Therefore, for convenience, it is described as reception type information [reception data ID] (the same applies hereinafter).

In the data relay device according to claim 2, terminal devices [50 a, 50 b, data terminals transmitted from one network [NW-n] are connected to another network [NW-1]. 50c], the other data transfer destination network [NW-1] is determined based on the data identifier [received data ID] that can identify the type of the data body included in the data frame. This is a data relay device provided with a determinable relay destination determining means [23b1], and is information transmitted from the terminal device [50a etc.] and included in the data frame to be received by the terminal device [50a etc.]. The reception type information [reception data ID] relating to the type of data body is received by the receivable reception type information receiving means [23a2] and the reception type information receiving means [23a2]. Relay destination determining means generating means [23a5] capable of generating the relay destination determining means [23b1] based on the reception type information [received data ID], and transmission of the reception type information [received data ID] to the terminal device Reception type information requesting means [23a3, 23a5] that can request [50a etc.], and the reception type information requesting means [23a3, 23a5] sends a transmission request for the reception type information [reception data ID]. For all the terminal devices [50a etc.]
A technical feature is that a request for the reception type information [reception data ID] is transmitted when the data relay device [20] is activated .

  In the data relay device according to claim 3, in the data relay device according to claim 2, the reception type information requesting unit [23 a 3, 23 a 5] transmits the reception type information [reception data ID]. A technical feature is that a broadcast request for the reception type information [received data ID] for all of the plurality of terminal devices [50a, etc.] is transmitted to the plurality of terminal devices [50a, etc.] that receive the request. And

  In the data relay device according to claim 4, the information relay device according to any one of claims 1 to 3, wherein the information is transmitted from the terminal device [50a etc.], and the terminal The device [50a etc.] comprises transmission type information receiving means [23a2] capable of receiving transmission type information [transmission data ID] relating to the type of data body included in the data frame to be transmitted, and the relay destination determining means generating means [23a5] is the relay destination determination unit [23b1] based on the reception type information [reception data ID] and the transmission type information [transmission data ID] received by the transmission type information reception unit [23a2]. Is a technical feature.

  In the data relay device according to claim 5, the data relay device according to claim 4, wherein the data relay device transmits the transmission type information [transmission data ID] to the terminal device [50a, etc.]. ] Is provided with a transmission type information requesting means [23a3, 23a5] that can be requested.

  In the data relay device according to claim 6, the transmission type information requesting means [23a3, 23a5] transmits the transmission type information [transmission data ID] in the data relay device according to claim 5. Technical feature of transmitting a broadcast request for the transmission type information [transmission data ID] for all of the plurality of terminal devices [50a, etc.] to the plurality of terminal devices [50a, etc.] receiving the request And

  In the data relay device according to claim 7, the relay destination determination unit generation means [23a5] includes the reception type information in the data relay device according to any one of claims 1 to 6. If the reception type information [reception data ID] is acquired before the reception type information [reception data ID] is received by the reception means [23a2], the acquired reception type information [reception data ID]. It is a technical feature that the relay destination determination means [23b1] can be generated based on the above.

  In the data relay device according to claim 8, the relay destination determination unit generation unit [23 a 5] is configured to transmit the transmission type information in the data relay device according to any one of claims 4 to 6. If the transmission type information [transmission data ID] is acquired before the transmission type information [transmission data ID] is received by the receiving means [23a2], the acquired transmission type information [transmission data ID]. It is a technical feature that the relay destination determination means [23b1] can be generated based on the above.

  In the data relay device according to claim 9 in the claims, in the data relay device according to any one of claims 1 to 8, the relay destination determination means generation means [23a5] has a first predetermined value. The technical feature is that the relay destination determination unit [23b1] is generated when the condition is satisfied, and the relay destination determination unit [23b1] is not generated when the first predetermined condition is not satisfied.

  In the data relay device according to claim 10 according to the claims, in the data relay device according to any one of claims 1 to 8, the relay destination determination means generating means [23a5] is a second predetermined The technical feature is that the relay destination determination unit [23b1] is generated again when the condition is satisfied, and the relay destination determination unit [23b1] is not generated again when the second predetermined condition is not satisfied.

  The terminal device according to claim 11, wherein the terminal can receive a data frame including a data body and a data identifier [received data ID] capable of identifying the type of the data body from the network. A reception type information generation unit [53a6] capable of generating reception type information [reception data ID] related to the type of the data body of the data frame to be received by the device; and the reception type information generation unit [53a6] The receiving type information [receiving data ID] generated by the receiving type information transmitting means [53a3] capable of transmitting to the network is a technical feature.

  In the terminal device according to claim 12, the reception type information transmitting unit [53a3] according to the terminal device according to claim 11, in response to a request from the data relay device connected to the network, The reception type information [reception data ID] is transmitted to the network as a technical feature.

  In the terminal device according to claim 13 according to the claims, in the terminal device according to claim 11 or 12, transmission type information [transmission data ID] relating to the type of the data body of the data frame to be transmitted by itself is set. Transmission type information generation means [53a7] that can be generated and transmission type information transmission means [53a3] that can transmit the transmission type information [transmission data ID] generated by the transmission type information generation means [53a7] to the network. And a technical feature thereof.

  In the terminal device according to claim 14, according to claim 14, in the terminal device according to claim 13, the transmission type information transmitting unit [53 a 3] responds to a request from the data relay device connected to the network, A technical feature is that the transmission type information [transmission data ID] is transmitted to the network.

In the data communication system according to claim 15, the terminal connected to one network [NW-n], another network [NW-1], and the other network [NW-1] Device [50a etc.] and data that can be transferred to the terminal device [50a etc.] of the other network [NW-1] connected to these networks and transmitted from the one network [NW-n] Relay destination determining means [23b1] capable of determining the other network [NW-1] as the transfer destination based on the data identifier [received data ID] that can identify the type of the data body included in the data frame in the relay device The terminal device [50a etc.] relates to the type of the data body of the data frame to be received by the terminal device [50a etc.] Reception type information generation means [53a6] capable of generating reception type information [reception data ID] and the reception type information [reception data ID] generated by the reception type information generation means [53a6] to the data relay device Receiving type information transmission means [53a3] capable of transmitting, wherein the data relay device receives the receiving type information [receiving data ID] transmitted from the terminal device [50a etc.]. Means [23a2] and relay destination determining means generating means [23b1] capable of generating the relay destination determining means [23b1] based on the reception type information [received data ID] received by the reception type information receiving means [23a2]. and 23a5], Bei a request a receiving type information request unit [23A3,23a5] transmission to the terminal device [50a, etc.] of the received type information [received data ID] The reception type information request means [23a3, 23a5] sends all of the plurality of terminal devices [50a, etc.] to the plurality of terminal devices [50a, etc.] that receive the transmission request for the reception type information [reception data ID]. A technical feature is that a request for the reception type information [reception data ID] is sent to the subject.

In the first aspect of the invention, based on the reception type information [received data ID] received by the reception type information receiving unit [23a2], the relay destination determining unit [23a5] generates the relay destination determining unit [23b1]. To do. As a result, by receiving information received from the terminal device [50a etc.] and receiving type information [received data ID] related to the type of data body included in the data frame to be received by the terminal device [50a etc.]. Thus, it is possible to appropriately generate the relay destination determining means [23b1]. That is, the reception type information [reception data ID] necessary for generating the relay destination determination unit [23b1] is received by the reception type information reception unit [23a2] without relying on human hands, and learning (relay destination) Since the determination means [23b1] is generated), the network can be easily constructed. Therefore, the writing of the ROM storing the relay destination table and the header table and the exchange work are prevented from occurring as the work related to the relay destination determining means [23b1], so that the burden of setting the data relay device related to the network configuration can be reduced. Can do.
Further, in the first aspect of the invention, the data relay device [20] allows the reception type information [reception data ID] to be requested to the terminal device [50a, etc.] reception type information request means [23a3, 23a5]. For example, when the relay destination determination unit [23b1] is not generated or when the relay destination determination unit [23b1] needs to be updated, the reception type information request unit [23a3, 23a5] receives the reception type information [ The reception type information [reception data ID] can be obtained from the terminal device [50a etc.] by the transmission request of the reception data ID]. As a result, the network configuration information can be learned by itself (relay destination determination means [23b1] is generated) based on the reception type information [reception data ID] as necessary. Therefore, it is possible to further reduce the burden of setting the data relay device regarding the network configuration.
In the first aspect of the invention, the reception type information requesting means [23a3, 23a5] sends the plurality of terminal devices to the plurality of terminal devices [50a etc.] that receive the transmission request for the reception type information [reception data ID]. [50a etc.] A request for reception type information [reception data ID] for all is transmitted. That is, since a transmission request for reception type information [received data ID] is broadcast (or multicast) to a plurality of terminal devices [50a, etc.] connected to the same network, such a transmission request is transmitted to a plurality of terminal devices [ 50a, etc.], it is possible to receive the reception type information [reception data ID] in a shorter time compared to the case of individual transmission (unicast). Therefore, since the network construction process can be performed at high speed, it is possible to shorten the setting work time of the data relay apparatus related to the network configuration.

In the invention of claim 2, the data relay device [20] includes reception type information requesting means [23a3, 23a5] capable of requesting the terminal device [50a etc.] to transmit the reception type information [reception data ID]. Therefore, for example, when the relay destination determination unit [23b1] is not generated or when the relay destination determination unit [23b1] needs to be updated, the reception type information [reception data by the reception type information request unit [23a3, 23a5] The reception type information [reception data ID] can be obtained from the terminal device [50a etc.] by the transmission request of [ID]. As a result, the network configuration information can be learned by itself (relay destination determination means [23b1] is generated) based on the reception type information [reception data ID] as necessary. Therefore, it is possible to further reduce the burden of setting the data relay device regarding the network configuration.
Further, in the invention of claim 2, the reception type information requesting means [23a3, 23a5] sends the data relay device [20 to all the terminal devices [50a etc.] that receive the transmission request of the reception type information [reception data ID]. ], A request for reception type information [received data ID] is transmitted, so that even if a plurality of terminal devices [50a, etc.] have different start-up power supply voltages, all terminal devices [50a, etc.] Thus, it is possible to reliably acquire the reception type information [reception data ID]. Therefore, it is possible to generate the relay destination determination means [23b1] that is free from the reception type information [received data ID].

  In the invention of claim 3, the reception type information requesting means [23a3, 23a5] sends a plurality of terminal devices [50a] to the plurality of terminal devices [50a etc.] that receive the transmission request of the reception type information [reception data ID]. Etc.] A broadcast request of reception type information [received data ID] for all is transmitted. That is, since a transmission request for reception type information [received data ID] is broadcast (or multicast) to a plurality of terminal devices [50a, etc.] connected to the same network, such a transmission request is transmitted to a plurality of terminal devices [ 50a, etc.], it is possible to receive the reception type information [reception data ID] in a shorter time compared to the case of individual transmission (unicast). Therefore, since the network construction process can be performed at high speed, it is possible to shorten the setting work time of the data relay apparatus related to the network configuration.

  In the invention of claim 4, the transmission type information receiving means [23a2] is provided, and the relay destination is determined based on the received transmission type information [transmission data ID] in addition to the reception type information [reception data ID]. A means [23b1] is generated. This makes it possible to recognize data frames transmitted and received between terminal devices [50a, etc.] connected to the other network, that is, between terminal devices connected to the same network. The relay device [20] can generate the relay destination determination means [23b1] that performs relaying except for data frames that do not need to be relayed. As a result, the configuration of the relay destination determination unit [23b1] can be simplified. For example, the relay destination determination processing speed by the relay destination determination unit [23b1] can be increased. Therefore, since the network construction process can be performed at high speed, it is possible to shorten the setting work time of the data relay apparatus related to the network configuration.

  In the invention of claim 5, the data relay device [20] includes transmission type information requesting means [23a3, 23a5] capable of requesting the terminal device [50a etc.] to transmit the transmission type information [transmission data ID]. Therefore, for example, when the relay destination determining unit [23b1] is not generated or when the relay destination determining unit [23b1] needs to be updated, the terminal device [50a etc.] adds to the reception type information [received data ID]. The transmission type information [transmission data ID] can also be obtained. As a result, network configuration information can be learned by itself based on the reception type information [reception data ID] and the transmission type information [transmission data ID] as needed (generate relay destination determination means [23b1]). A high-speed network construction process can be performed as appropriate. Therefore, it is possible to further reduce the burden of setting the data relay device regarding the network configuration.

  In the invention of claim 6, the transmission type information requesting means [23a3, 23a5] sends the plurality of terminal devices [50a] to the plurality of terminal devices [50a etc.] that receive the transmission request for the transmission type information [transmission data ID]. Etc.] A broadcast request of transmission type information [transmission data ID] for all is transmitted. That is, since a transmission request for transmission type information [transmission data ID] is broadcast (or multicast) to a plurality of terminal devices [50a, etc.] connected to the same network, such a transmission request is transmitted to a plurality of terminal devices [ 50a etc.], it is possible to receive the transmission type information [transmission data ID] in a shorter time compared to the case of individual transmission (unicast). Therefore, since the network construction process can be performed at high speed, it is possible to shorten the setting work time of the data relay apparatus related to the network configuration.

  In the invention of claim 7, the relay destination determination means generation means [23a5] obtains the reception type information [reception data ID] before the reception type information [reception data ID] is received by the reception type information reception means [23a2]. If it is, the relay destination determination means [23b1] can be generated based on the acquired reception type information [received data ID]. As a result, for example, for the basic configuration of the network that has been known in advance, the reception type information [reception data ID] is given without using the reception type information reception unit [23a2], so that the relay destination determination unit is based on it. [23b1] can be generated. Therefore, in the subsequent generation of the relay destination determining means [23b1] based on the reception type information [received data ID] received by the received reception type information receiving means [23a2], the already received reception type information [received data ID] And the reception type information [received data ID] received thereafter, the relay destination determining means [23b1] is generated for the difference information between the received type information [received data ID] and the relay destination determining means based on the received reception type information [received data ID] [ 23b1] can be processed at high speed. Also, reception type information [reception data ID] that cannot be received by the reception type information receiving means [23a2] is given in advance, and the received reception type information [reception data ID] and the received reception type information [reception data received thereafter]. The relay destination determination means [23b1] is generated for the difference information from the ID], so that the relay destination determination means can also be received for the reception type information [received data ID] that cannot be received by the reception type information reception means [23a2]. [23b1] can be generated. Therefore, it is possible to further reduce the burden of setting the data relay device regarding the network configuration.

  In the invention of claim 8, the relay destination determining means generating means [23a5] acquires the transmission type information [transmission data ID] before receiving the transmission type information [transmission data ID] by the transmission type information receiving means [23a2]. If it is, the relay destination determination means [23b1] can be generated based on the acquired transmission type information [transmission data ID]. Thereby, for example, the basic configuration of the network that has been known in advance is not based on the transmission type information receiving unit [23a2], but is given the transmission type information [transmission data ID], so that the relay destination determining unit is based on it. [23b1] can be generated. For this reason, in the subsequent generation of the relay destination determining means [23b1] based on the transmission type information [transmission data ID] received by the transmission type information receiving means [23a2], the already acquired transmission type information [transmission data ID] Then, the relay destination determination means [23b1] is generated for the difference information between the received transmission type information [transmission data ID] and the relay destination determination means [23b1] based on the received transmission type information [transmission data ID]. 23b1] can be processed at high speed. Further, transmission type information [transmission data ID] that cannot be received by the transmission type information receiving means [23a2] is given in advance, and the acquired transmission type information [transmission data ID] and the transmission type information received thereafter [transmission data] The relay destination determining means [23b1] is generated for the difference information from the ID], so that the relay destination determining means can also be used for transmission type information [transmission data ID] that cannot be received by the transmission type information receiving means [23a2]. [23b1] can be generated. Therefore, it is possible to further reduce the burden of setting the data relay device regarding the network configuration.

  In the invention of claim 9, the relay destination determining means generating means [23a5] generates the relay destination determining means [23b1] when the first predetermined condition is satisfied, and when the first predetermined condition is not satisfied. The relay destination determining means [23b1] is not generated. As the “first predetermined condition”, for example, (1-1) the relay destination determination means [23b1] is not generated, or (1-2) a network or an input device (for example, a diagnostic device or an inspection device) Etc.) There is an input of a specific instruction code (specific command) that can be input to the data relay device [20] from the outside, and the conditions of (1-3) (1-1), (1-2) Are satisfied together. As a result, the relay destination determining unit [23b1] is generated only when the first predetermined condition is satisfied. Therefore, even though the relay destination determining unit [23b1] has already been generated, it is unnecessary or erroneous. The relay destination determining means [23b1] is generated (corresponding to (1-1)), or the relay destination determining means [23b1] is generated in an incomplete network configuration (corresponding to (1-2)) Further, when data having the same meaning and content as the specific instruction code (specific command) is accidentally input due to a transmission error on a transmission medium such as a network, the relay destination determining means [23b1] It is possible to prevent erroneous generation of the relay destination determining means [23b1] such as generated (corresponding to (1-3)).

  In the invention of claim 10, the relay destination determining means generating means [23a5] generates the relay destination determining means [23b1] again when the second predetermined condition is satisfied, and when the second predetermined condition is not satisfied. Does not generate the relay destination determination means [23b1] again. Here, as the “second predetermined condition”, for example, (2-1) a specific that can be input to the data relay device [20] from the outside such as a network or an input device (for example, a diagnostic device or an inspection device) Input of command code (specific command), (2-2) Input of predetermined voltage or current that can be set in the data relay device [20] (power supply (battery etc.) to be constantly supplied is connected The input of voltage and current at the time of being performed). Thereby, only when the second predetermined condition is satisfied, the relay destination determining means [23b1] is generated again, so that it is unnecessary even though the relay destination determining means [23b1] has already been generated. It is possible to prevent the relay destination determination unit [23b1] from being generated again or the relay destination determination unit [23b1] from being generated again by mistake. Further, even when the option setting of the vehicle is changed by the user (addition or deletion of a device from the middle), the relay destination determination unit [23b1] can be regenerated as necessary.

  In the invention of claim 11, the reception type information [reception data ID] relating to the type of the data body of the data frame to be received by the reception type information generation means [53a6] is generated, and the reception type information transmission means [53a3] is generated. ] Is sent to the network. Thereby, for example, the data relay device [20] according to claims 1 to 9 connected to the network can receive the reception type information [received data ID] of the terminal device. Therefore, in the data relay device [20], as described above, the reception type information [reception data ID] necessary for generating the relay destination determination means [23b1] is not manually relied on. Since the information is received by the information receiving means [23a2] and learned by itself (relay destination determining means [23b1] is generated), the network can be easily constructed. Therefore, the writing of the ROM storing the relay destination table and the header table and the exchange work are prevented from occurring as the work related to the relay destination determining means [23b1], so that the burden of setting the data relay device related to the network configuration can be reduced. Can do.

  In the invention of claim 12, the reception type information transmitting means [53a3] transmits the reception type information [reception data ID] to the network in response to a request from the data relay apparatus connected to the network. Accordingly, for example, the data relay device [20] according to claim 2 or claim 3 can respond to a transmission request for the reception type information [received data ID] by the data relay device [20]. As described above, the network configuration information can be learned by itself based on the reception type information [reception data ID] as necessary (the relay destination determination unit [23b1] is generated). Therefore, it is possible to further reduce the burden of setting the data relay device regarding the network configuration.

  In the invention of claim 13, the transmission type information [transmission data ID] relating to the type of the data body of the data frame to be transmitted by itself is generated by the transmission type information generation means [53a7], and the transmission type information transmission means [53a3] ] Is sent to the network. Thereby, for example, the data relay device [20] according to claims 4 to 6 connected to the network can receive the transmission type information [transmission data ID] of the terminal device. Therefore, in the data relay device [20], as described above, data is transmitted and received between the terminal devices [50a etc.] connected to the other network, that is, between the terminal devices connected to the same network. Since the data frame can be recognized, such a data relay device [20] can generate the relay destination determination means [23b1] that relays data frames that do not need to be relayed. As a result, the configuration of the relay destination determination unit [23b1] can be simplified. For example, the relay destination determination processing speed by the relay destination determination unit [23b1] can be increased. Therefore, since the network construction process can be performed at high speed, it is possible to shorten the setting work time of the data relay apparatus related to the network configuration.

  In the invention of claim 14, the transmission type information transmitting means [53a3] transmits the transmission type information [transmission data ID] to the network in response to a request from the data relay apparatus connected to the network. As a result, for example, the data relay apparatus [20] according to claim 5 or claim 6 can respond to a transmission request for transmission type information [transmission data ID]. As described above, the network configuration information can be learned by itself based on the reception type information [reception data ID] and the transmission type information [transmission data ID] as necessary (the relay destination determination means [23b1] is generated). High-speed network construction processing can be performed as appropriate. Therefore, it is possible to further reduce the burden of setting the data relay device regarding the network configuration.

In the invention of claim 15, the terminal device [50a etc.] generates reception type information [reception data ID] related to the type of data body of the data frame to be received by the reception type information generation means [53a6]. Is transmitted to the network by the reception type information transmitting means [53a3]. On the other hand, the data relay device [20] receives the reception type information [received data ID] transmitted from the terminal device [50a, etc.] by the reception type information receiving unit [23a2], and based on this, generates the relay destination determining unit. The relay destination determining means [23b1] is generated by the means [23a5]. As a result, by receiving information received from the terminal device [50a etc.] and receiving type information [received data ID] related to the type of data body included in the data frame to be received by the terminal device [50a etc.]. Thus, it is possible to appropriately generate the relay destination determining means [23b1]. That is, the reception type information [reception data ID] necessary for generating the relay destination determination unit [23b1] is received by the reception type information reception unit [23a2] without relying on human hands, and learning (relay destination) Since the determination means [23b1] is generated), the network can be easily constructed. Therefore, the writing of the ROM storing the relay destination table and the header table as the work relating to the relay destination determining means [23b1] and the exchange work are prevented, so that the burden of the data relay device setting work relating to the network configuration can be reduced. Can do.
Further, in the invention of claim 15, the data relay device [20] allows the reception type information [reception data ID] to be requested to the terminal device [50a, etc.] reception type information request means [23a3, 23a5]. For example, when the relay destination determination unit [23b1] is not generated or when the relay destination determination unit [23b1] needs to be updated, the reception type information request unit [23a3, 23a5] receives the reception type information [ The reception type information [reception data ID] can be obtained from the terminal device [50a etc.] by the transmission request of the reception data ID]. As a result, the network configuration information can be learned by itself (relay destination determination means [23b1] is generated) based on the reception type information [reception data ID] as necessary. Therefore, it is possible to further reduce the burden of setting the data relay device regarding the network configuration.
In the fifteenth aspect of the invention, the reception type information requesting means [23a3, 23a5] sends the plurality of terminal devices to the plurality of terminal devices [50a etc.] that receive the transmission request for the reception type information [reception data ID]. [50a etc.] A request for reception type information [reception data ID] for all is transmitted. That is, since a transmission request for reception type information [received data ID] is broadcast (or multicast) to a plurality of terminal devices [50a, etc.] connected to the same network, such a transmission request is transmitted to a plurality of terminal devices [ 50a, etc.], it is possible to receive the reception type information [reception data ID] in a shorter time compared to the case of individual transmission (unicast). Therefore, since the network construction process can be performed at high speed, it is possible to shorten the setting work time of the data relay apparatus related to the network configuration.

  Hereinafter, embodiments in which a data relay device, a terminal device, and a data communication system of the present invention are applied to an in-vehicle LAN system will be described with reference to the drawings. First, a configuration example of a data communication system according to the present embodiment will be described with reference to FIG. In the following, in relation to the description in the claims, the network NW-1 will be described as being associated with “another network”, and the network NW-n will be described as being associated with a “one network”. For example, the network NW-1, NW-2, NW-3 is “one network”, the network NW-n is “other network”, the network NW-1, NW-2, Any combination of NW-3 as “other network” and network NW-n as “one network” can be assumed, and other correspondence relationships may be used.

  The gateway device 20 can correspond to the “data relay device” described in the claims, and the nodes 50a, 50b, 50c, 50d, 50e, 50f, 50g, 50h, 50i, 50x, 50y, 50z (hereinafter collectively referred to as “node 50a etc.”) can correspond to the “terminal device” described in the claims.

  As shown in FIG. 1, the data communication system according to the present embodiment includes a network NW-1, NW-2, NW-3,..., NW-n (n is a positive integer) (hereinafter referred to as “a positive integer”). These are collectively referred to as “network NW-1 etc.”) and a gateway device 20 connected to these networks NW-1 etc. Each network NW-1 and the like is configured by a bus serving as a data communication transmission medium and a plurality of nodes connected to the bus.

  For example, in the case of the first network NW-1, three nodes 50a, 50b, and 50c are connected to the bus bus-1 so that data communication is possible. Similarly, nodes 50d, 50e, and 50f are included in the bus bus-2 of the second network NW-2, and nodes 50g, 50h, and 50i are included in the bus bus-3 of the third network NW-3. For example, nodes 50x, 50y, and 50z are connected to the bus n of the last nth network.

  In each network NW-1 and the like configured as described above, communication between nodes is performed according to a communication protocol suitable for each application. For example, the network NW-1 uses CAN as a communication protocol suitable for the control system, and the network NW-2 uses J1850 or BEAN as a low-speed communication protocol for vehicle body control or the like. Further, the network NW-3 communication protocol uses multimedia IE-BUS, and the network NW-n communication protocol uses diagnostic control ISO 9141.

  Therefore, in the network NW-1 by CAN, the ECU for engine control as the node 50a, the ECU for brake control as the node 50b, and the ECU for transmission control as the node 50c are connected to the bus bus-1, respectively, and according to J1850 In the network NW-2, an ECU for air conditioner control as a node 50d, an ECU for seat control as a node 50e, and an ECU for wiper control as a node 50f are connected to the bus bus-2. Further, in the network NW-3 based on IE-BUS, an ECU for car navigation control as a node 50g, an ECU for car audio control as a node 50h, and an ECU for video system control as a node 50i are connected to the bus bus-3, respectively. ing. In the network NW-n based on ISO 9141, diagnosis ECUs for vehicle control functions are connected to the bus bus-n as nodes 50x, 50y, and 50z, respectively.

  As described above, the nodes 50a and the like connected to the networks NW-1 and the like perform transmission and reception of data frames between the nodes in accordance with a communication protocol determined for each network. Therefore, even if communication between nodes is possible in the same network, the communication protocol differs between nodes connected to other networks beyond the network. I can't communicate. That is, the node 50a of the network NW-1 illustrated in FIG. 1 cannot communicate with the node 50d of the network NW-2 or the node 50x of the network NW-n, even though the node 50a can communicate with the node 50b and the node 50c.

  Therefore, by connecting each of these networks NW-1 and the like to the gateway device 20, it is interposed between networks having different communication protocols and enables communication between the nodes of these networks. The gateway device 20 can determine the data transfer destination network based on the received data ID that can identify the type of the data body included in the data frame transmitted from each node 50a or the like. Thus, the transfer destination network is not determined based on the node ID that can identify each node 50a and the like. Here, a configuration example of the gateway device 20 will be described with reference to FIG. 2A shows the hardware configuration of the gateway device 20, and FIG. 2B shows the configuration of the outline of processing by the gateway device 20. In FIG. 2, the interface is abbreviated as “I / F”, and the table is abbreviated as “TBL”.

  As shown in FIG. 2A, the gateway device 20 is mainly composed of a CPU 21, a memory 23, and an interface unit 27, and they are electrically connected to each other via an internal bus. The CPU 21 is a central processing unit and is a microprocessing unit also called “MPU”.

  The memory 23 is a semiconductor memory device including a volatile memory device such as a DRAM and a non-volatile memory device such as a ROM or an EEPROM. Usually, a program area 23a and a relay destination table area 23b are secured in a non-volatile memory, and a predetermined control program and data that enable arithmetic processing by each processing unit described later are stored. On the other hand, in the volatile memory, a work area or the like by a program is secured, and a stack, various intermediate data, and the like are temporarily stored. The relay destination table 23b1 is secured in the relay destination table area 23b.

  Thus, by securing the relay destination table area 23b in a non-volatile memory such as PROM or EEPROM, the reception data ID and transmission data stored in the relay destination table 23b1 even when the power supplied to the gateway device 20 is cut off. Since each information such as an ID is not lost, it is possible to prevent loss of network information set at the time of gateway device 20 shipment from the factory. Further, by securing the relay destination table area 23b in the electrically erasable EEPROM and registering the relay destination table 23b1 in this area, the relay destination table 23b1 can be easily rewritten. As a result, there is no need to replace the ROM itself as in the PROM, so there is no need to manage the replacement ROM.

  The interface unit 27 includes interface units corresponding to a plurality of buses bus-1, bus-2, bus-3,..., Bus-n (hereinafter collectively referred to as “bus bus-1 etc.”). For example, an interface unit 27a corresponding to the bus 1 is provided as an interface unit connectable to the bus bus-1. Similarly, as an interface unit connectable to the bus bus-2, an interface unit 27b corresponding to the bus 2, an interface unit connectable to the bus 3 as an interface unit connectable to the bus bus-3, and an interface unit connectable to the bus bus-n. Each interface unit 27n is provided with a bus n. Note that the interface unit 27a corresponding to the bus 1, the interface unit 27b corresponding to the bus 2, the interface unit 27c corresponding to the bus 3 and the interface unit 27n corresponding to the bus n are “reception type information receiving means” and “transmission type information” recited in the claims. It can correspond to “receiving means”, “reception type information requesting means” and “transmission type information requesting means”.

  By configuring the hardware of the gateway device 20 in this way, each process configured as shown in FIG. That is, each process executed by the CPU 21 includes a basic system unit 23a1, a relay frame receiving unit 23a2, a relay frame transmitting unit 23a3, a data ID reference unit 23a4, a relay destination table generating unit 23a5, and a relay destination table 23b1. .

  The basic system unit 23a1 is an operating system that performs basic control between the CPU 21 and hardware resources such as the memory 23 and the interface unit 27, and includes a group of programs that are indispensable as a computer system.

  The relay frame reception unit 23a2 appropriately extracts a data frame that is input to the interface unit 27 and buffered in the reception buffer, an error check process that checks whether there is a transmission error according to a predetermined algorithm, and data in which a transmission error has occurred. The error correction process etc. which correct | amend can be performed, and after these processes, a data frame is passed to data ID reference part 23a4. Since this relay frame receiving unit 23a2 has a function of receiving data frames, it can correspond to “reception type information receiving means” or “transmission type information receiving means” described in the claims. .

  When receiving the data frame whose transfer destination has been determined by the data ID reference unit 23a4, the relay frame transmission unit 23a3 adds data for error detection or error correction to the data frame and outputs it to the transmission buffer of the interface unit 27 as appropriate. Can be performed. Since this relay frame transmission unit 23a3 has a function of transmitting a data frame, it can correspond to a “reception type information request unit” or “transmission type information request unit” described in the claims. .

  The data ID reference unit 23a4 refers to the process of extracting the received data ID from the data frame passed by the relay frame receiving unit 23a2, and the data ID to be received by each node 50a and the like stored in the relay destination table 23b1 Thus, it is possible to perform processing for determining whether or not the referred data ID and the received data ID match (hereinafter, the data ID referred to by the data ID reference unit 23a4 is referred to as “reference data ID”). Then, the data ID reference unit 23a4 passes the data frame to the relay frame transmission unit 23a3 when the two data IDs match, and discards the data frame when they do not match. That is, the gateway device 20 determines a network to which the data frame is to be transferred based on the received data ID that can identify the type of the data body included in the data frame transmitted from each node 50a or the like. The reception data ID can correspond to a “data identifier” and a “reception information type” described in the claims.

  The flow in which the data frame extracted from the reception buffer of the interface unit 27 by the relay frame receiving unit 23a2 as described above is passed to the relay frame transmitting unit 23a3 via the data ID reference unit 23a4 is outlined in FIG. 2B. It is represented by an arrow. The reference of the reference data ID stored in the relay destination table 23b1 by the data ID reference unit 23a4 is represented by a double arrow in FIG. 2 (B).

  The relay destination table generation unit 23a5 generates a relay destination table 23b1 based on the received data ID included in the data frame transmitted from the node 50a in response to the inquiry from the gateway device 20, and the relay destination table 23b1 When the node 50a or the like has not been generated, the node 50a or the like can be inquired about the received data ID of the data frame to be received by the node 50a or the like, or the transmission data ID of the data frame to be transmitted by the node 50a or the like. The relay destination table generating unit 23a5 can correspond to “relay destination determining means generating means”, “reception type information requesting means” and “transmission type information requesting means” described in the claims. The generation process of the relay destination table 23b1 will be described later with reference to FIG.

  The inquiry about the reception data ID and transmission data ID by the relay destination table generation unit 23a5 is made from the gateway device 20 to the corresponding node 50a or the like if the target node 50a or the like can recognize its own node ID. Although the inquiry about the reception data ID and the transmission data ID may be made individually, in the present embodiment, a specific data frame can be broadcast to the target node 50a and the like.

  Specifically, for example, by setting a specific code (for example, all bits “1”) predetermined as a wild card to the data ID of the data frame transmitted from the gateway device 20, the network NW-1 or the like It is notified that the data frame is useful for all the nodes 50a connected to the. As a result, the number of transmissions from the gateway device 20 to the node 50a etc. is reduced to 1 / n (n is the number of nodes) compared to the case where such an inquiry is individually sent to the terminal device 50a etc. (unicast). Therefore, the received data ID can be received in a short time. Accordingly, since the network construction process can be performed at high speed, it is possible to reduce the setting work time of the data relay device 20 relating to the network configuration (substantially corresponding to claims 2 and 3).

  The inquiry about the reception data ID and the transmission data ID is not limited to one time. For example, the inquiry is performed twice or more unconditionally, and the received data ID and the transmission data ID for which each inquiry is answered are collated. Thus, it may be configured to be able to confirm that there is no error in the received data ID or the like. As a result, it is possible to prevent the relay destination table 23b1 from being erroneously generated due to a transmission error. Moreover, when there is no response of the node 50a or the like, or when the reception data ID or the transmission data ID is not transmitted, the inquiry may be retried a predetermined number of times. Thereby, it is possible to effectively cope with the case where the inquiry can be lost due to a reception error of the node 50a or the like.

  The relay destination table 23b1 is a non-volatile storage area configured in the relay destination table area 23b of the memory 23 corresponding to each bus bus-1, etc., and received data that can identify the type of data body included in the data frame. It is possible to determine another network of the transfer destination based on the ID. For example, reception data IDs to be received by the nodes 50a, 50b, and 50c connected to the bus bus-1 are registered in the bus memory 1, and receptions to be received by the nodes 50d, 50e, and 50f connected to the bus bus-2. The data ID is registered in the bus memory 2, and the received data ID to be received by the nodes 50g, 50h, and 50i connected to the bus bus-3 is registered in the bus memory 3 and the nodes 50x and 50x connected to the bus bus-n. Received data IDs to be received by 50y and 50z are registered in the bus memory n. The relay destination table 23b1 can correspond to “relay destination determining means” described in the claims, and details will be described later with reference to FIG.

  Note that the transmission of the process of generating the relay destination table 23b1 based on the received data ID included in the data frame acquired by the relay frame receiving unit 23a2 is represented by a hatched arrow in FIG. Yes. Further, the inquiry transmission of the reception data ID and the transmission data ID by the relay destination table generation unit 23a5 when the relay destination table 23b1 is not generated is represented by a dotted arrow in FIG.

  Next, a configuration example of the node 50a and the like will be described with reference to FIG. Since the basic configuration of each node 50a and the like is substantially the same, here, a configuration example of the node 50a will be described as a representative. 3A shows the hardware configuration of the node 50a, and FIG. 3B shows the configuration of the outline of processing by the node 50a. In FIG. 3, the interface is abbreviated as “I / F”, and the application is abbreviated as “AP”.

  As shown in FIG. 3A, the node 50a is mainly composed of a CPU 51, a memory 53, and an interface unit 57, which are electrically connected to each other via an internal bus. The CPU 51 is a central processing unit and is a microprocessing unit like the CPU 21.

  Similarly to the memory 23 described above, the memory 53 is a semiconductor storage device including a volatile memory device such as a DRAM and a nonvolatile memory device such as a ROM or an EEPROM, and a program area 53a or a transmission / reception ID table area 53b in the nonvolatile memory. Is secured. The program area 53a stores predetermined programs and data that enable arithmetic processing by each processing unit, and a work area or the like by the programs is secured in the volatile memory. Note that a reception ID table 53b1 and a transmission ID table 53b2 are secured in the transmission / reception ID table area 53b.

  The interface unit 57 includes a bus 1 compatible interface unit 57a corresponding to the bus bus-1 and an application compatible interface unit 57b corresponding to a predetermined application. The application-compatible interface unit 57b is provided with an interface that differs depending on the use of the node 50a, for example, an A / D converter or a D / A converter if it processes analog signals.

  By configuring the hardware of the node 50a in this way, each process configured as shown in FIG. 3B is executed by the CPU 51. That is, each process executed by the CPU 51 includes a basic system unit 53a1, a data frame reception unit 53a2, a data frame transmission unit 53a3, a data ID reference unit 53a4, a predetermined processing unit 53a5, a reception ID generation unit 53a6, and a transmission ID generation unit 53a7. The reception ID table 53b1 and the transmission ID table 53b2.

  The basic system unit 53a1 is an operating system that performs basic control between the CPU 51, hardware resources such as the memory 53, the interface unit 57, and the like, and includes an indispensable program group as a computer system.

  The data frame reception unit 53a2 appropriately extracts a data frame input to the interface unit 57 and buffered in the reception buffer, an error check process for checking whether there is a transmission error according to a predetermined algorithm, and data in which a transmission error has occurred. Error correction processing or the like can be performed, and after this processing, the data frame is passed to the data ID reference unit 53a4.

  When the data frame transmission unit 53a3 receives the data frame subjected to the predetermined information processing by the predetermined processing unit 53a5, the reception ID generation unit 53a6, or the transmission ID generation unit 53a7, the data frame transmission unit 53a3 receives data for error detection or error correction. In addition, processing to output to the transmission buffer of the interface unit 57 can be appropriately performed. Since the data frame transmission unit 53a3 has a function of transmitting a data frame, the data frame transmission unit 53a3 can correspond to “reception type information transmission unit” or “transmission type information transmission unit” recited in the claims. .

  The data ID reference unit 53a4 refers to the process of extracting the received data ID from the data frame passed by the data frame receiving unit 53a2, or the data ID to be received by the node 50a stored in the reception ID table 53b1, A process for determining whether or not the reference data ID matches the extracted received data ID can be performed. If the two data IDs match, the data frame is passed to the predetermined processing unit 53a5. If the data IDs do not match, the data frame is discarded. That is, is the node 50a useful for the data frame based on the received data ID that can identify the type of the data body included in the data frame transmitted from the other node 50b or the gateway device 20 or the like? Judging whether or not. The usefulness of the data frame is not determined based on the node ID.

  The predetermined processing unit 53a5 refers to the predetermined process according to the function that the node 50a should have, or the transmission ID table 53b2 after the predetermined process, and the data body of the processed data frame is transferred to another node 50b or the like. If the data frame needs to be transmitted, the data frame can be transferred to the data frame transmission unit 53a3. For example, when the node 50a is an engine control ECU, control related to a fuel injection amount to be output to an injector (fuel injection valve) based on throttle opening information obtained from a data body of a predetermined data frame. After performing the process of calculating the information, the process of passing the data frame to be transmitted to the ECU for controlling the injector capable of controlling the injector with reference to the transmission ID table 53b2 is performed to the data frame transmitting unit 53a3.

  In this way, the data frame taken out from the reception buffer of the interface unit 57 by the data frame receiving unit 53a2 is passed to the predetermined processing unit 53a5 through the data ID reference unit 53a4, and after the predetermined processing by the predetermined processing unit 53a5, the data The flow passed to the frame transmission unit 53a3 is represented by a white arrow in FIG. Further, referring to the reception data ID stored in the reception ID table 53b1 by the data ID reference unit 53a4 and the reference to the transmission data ID stored in the transmission ID table 53b2 by the predetermined processing unit 53a5 are shown in FIG. Is represented by a double arrow.

  In response to the inquiry from the gateway device 20, the reception ID generation unit 53a6 refers to the reception ID table 53b1 for the reception data ID of the data frame to be received by the node 50a, and generates a data frame including the reception data ID. The generated data frame is transferred to the data frame transmission unit 53a3. In addition, when there are a plurality of reception data IDs to be transmitted to the gateway device 20, a plurality of the reception data IDs may be set in the data body so that these can be transmitted at once, and a data frame may be configured. In addition, a configuration may be adopted in which one received data ID is sent in one transmission, and the data frame is transmitted in multiple times. The reception ID generation unit 53a6 may correspond to “reception type information generation means” described in the claims. The reception ID generation processing by the reception ID generation unit 53a6 will be described later with reference to FIG.

  The transmission ID generation unit 53a7 also generates a data frame including the transmission data ID by referring to the transmission ID table 53b2 for the transmission data ID of the data frame to be transmitted by the node 50a in response to the inquiry from the gateway device 20. The generated data frame is transferred to the data frame transmission unit 53a3. In addition, when there are a plurality of transmission data IDs to be transmitted to the gateway device 20, as in the case of the reception ID generation unit 53a6, it can be configured to transmit at one time, or a data frame is transmitted in multiple times. May be. The transmission ID generation unit 53a7 can correspond to “transmission type information generation means” described in the claims. The transmission ID generation process by the transmission ID generation unit 53a7 will be described later with reference to FIG.

  The reception ID table 53b1 is a storage area configured in the transmission / reception ID table area 53b of the memory 53, and stores a reception data ID of a data frame to be received by the node 50a. This table can be referred to by the data ID reference unit 53a4 and the reception ID generation unit 53a6.

  Similarly to the reception ID table 53b1, the transmission ID table 53b2 is a storage area configured in the transmission / reception ID table area 53b of the memory 53, and stores the transmission data ID of the data frame to be transmitted by the node 50a. This table can be referred to by the predetermined processing unit 53a5 and the transmission ID generation unit 53a7.

  The inquiry transmission of the received data ID and the transmitted data ID sent from the relay destination table generating unit 23a5 of the gateway device 20 is represented by a dotted arrow in FIG. The reference of the reception ID table 53b1 by the reception ID generation unit 53a6 and the reference of the transmission ID table 53b2 by the transmission ID generation unit 53a7 are represented by double arrows in FIG. Furthermore, the flow of data frames generated by the reception ID generation unit 53a6 and the transmission ID generation unit 53a7 is represented by hatched arrows in FIG.

  Here, the frame format of each of these communication protocols will be described with reference to FIG. 4A is the CAN protocol, FIG. 4B is the J1850 protocol, FIG. 4C is the BEAN protocol, FIG. 4D is the IE-BUS protocol, and FIG. Each frame format according to ISO 9141 protocol is shown.

  As shown in FIG. 4 (A), in the frame format according to the CAN protocol, the range from the SOF (Start Of Flame) area indicating the start of the frame to the CNT (Control) area is a “header”, and the ID area thereof includes The type of data body stored in the data area is included. That is, in the CAN protocol, this ID area corresponds to a reception data ID or a transmission data ID (data identifier).

  As shown in FIG. 4B, in the frame format according to the J1850 protocol, the type of the data body stored in the data area is included in the header area located after the SOF area indicating the start of the frame. That is, in the J1850 protocol, this header area corresponds to a reception data ID or a transmission data ID (data identifier).

  As shown in FIG. 4C, in the frame format according to the BEAN protocol, the range from the SOF area indicating the start of the frame to the message ID area is a “header”, and the message ID area is stored in the data area. Type of data body to be included. That is, in the BEAN protocol, this message ID area corresponds to a reception data ID or a transmission data ID (data identifier).

  As shown in FIG. 4D, in the frame format according to the IE-BUS protocol, the range from the source physical address area to the OPC (OperationCode) area is a “header”, and stored in the data area in the OPC area. The type of data body to be included. That is, in the IE-BUS protocol, this OPC area corresponds to a reception data ID or a transmission data ID (data identifier).

  As shown in FIG. 4 (E), in the frame format according to the ISO 9141 protocol, the range from the FB (Format Byte) area to the PID area is a “header” and is stored in the data area in the destination address area and the PID area. Type of data body to be included. That is, in the ISO 9141 protocol, the destination address area and the PID area correspond to a reception data ID and a transmission data ID (data identifier).

  The frame format of these protocols can correspond to the “data frame” described in the claims, and the data area can correspond to the “data body” described in the claims. is there.

  Next, reception data ID and transmission data ID included in such a data frame will be described with reference to FIGS. FIG. 5 shows the network NW-1 and NW-n extracted from the network configuration shown in FIG. 1, and the networks NW-2 and NW-3 are omitted.

  As shown in FIG. 5 and FIG. 6A, first, “MsgA_GW”, “MsgA_B”, and “MsgA_C” are assumed as transmission data IDs of data frames transmitted from the node 50a. On the other hand, “MsgGW_A” is assumed as the reception data ID of the frame received by the node 50a. The notation “Msg ○ _ □” indicates that the data ID is the data ID of the data frame transmitted from the ○ mark to the □ mark. Note that this is not an illustration of what is needed, but merely an example of a data ID.

  Similarly, as shown in FIG. 6B, “MsgB_A”, “MsgB_GW”, and “MsgB_C” are assumed as the transmission data IDs of the data frames transmitted from the node 50b. On the other hand, “MsgGW_B” is assumed as the reception data ID of the frame received by the node 50b. Similarly for the node 50c, as shown in FIG. 6C, “MsgC_A”, “MsgC_B”, and “MsgC_GW” are assumed as the transmission data IDs of the data frames transmitted from the node 50c. On the other hand, “MsgGW_C” is assumed as the reception data ID of the frame received by the node 50c.

  Then, the reception data ID related to the bus bus-1 to which the nodes 50a, 50b, and 50c are connected becomes the reception data ID to be received by all the nodes 50a, 50b, and 50c connected to the bus bus-1. That is, in the assumption examples shown in FIGS. 5 and 6, the received data ID of the data frame to be received for all the node nodes 50a, 50b, and 50c connected to the bus bus-1 is extracted from each table of FIG. As a result, a table as shown in FIG.

  That is, by selecting the receiving node that is the node 50a from FIG. 6 (A) to FIG. 6 (C), the “data ID to be received by the node 50a” column in FIG. A table can be shown. Similarly, from FIG. 6, by selecting a node whose receiving node is the node 50b, a table shown in the column of “Data ID to be received by the node 50b” in FIG. Similarly, from FIG. 6, by selecting a node whose receiving node is the node 50c, a table shown in the column of “data ID to be received by the node 50c” in FIG.

  As a result, in the case of the assumption example shown in FIGS. 5 and 6, “MsgGW_A” is used as the data ID to be received by the node 50 a in the bus memory 1 corresponding to the bus bus-1 as the relay destination table 23 b 1 of the gateway device 20. ”,“ MsgB_A ”, and“ MsgC_A ”are registered, and three types of received data IDs“ MsgA_B ”,“ MsgGW_B ”, and“ MsgC_B ”are received as data IDs to be received by the node 50b. Three types of received data IDs “MsgA_C”, “MsgB_C”, and “MsgGW_C” are registered as data IDs that are registered and should be received by the node 50c.

  However, as described above, the gateway device 20 is interposed between networks having different communication protocols, and enables communication between nodes of these networks. For this reason, as shown in FIG. 7A, for example, three types of reception of “MsgGW_A”, “MsgB_A”, and “MsgC_A” are received as data IDs to be received by the node 50a in the relay destination table 23b1 of the gateway device 20. Even if the data ID is registered, the gateway device 20 does not need to be involved in “MsgB_A” and “MsgC_A” that are actually exchanged between nodes in the same network. Originally, the received data ID required by the gateway device 20 is the data ID of a data frame transmitted to another network beyond one network. In this case, “MsgGW_A”, “MsgB_A”, “MsgC_A” Among the received data IDs, only “MsgGW_A”.

  That is, as shown in FIG. 8, the reception data ID necessary for the gateway device 20 is obtained by subtracting the data ID to be transmitted from the data ID to be received. In the case of the assumption example shown in FIGS. 5 and 6, as shown in FIG. 7B, the node 50a, 50b, 50c obtains the data ID to be transmitted, thereby obtaining the originally required reception data ID. be able to.

  For example, for the node 50a, as shown in FIG. 7A, the data IDs to be received are “MsgGW_A”, “MsgB_A”, and “MsgC_A”, whereas the node 50b transmits these data IDs. The data ID “MsgB_A” to be transmitted and the data ID “MsgC_A” to be transmitted by the node 50c are included. For this reason, the communication related to the two data IDs is closed in the same network NW-1, and therefore the gateway device 20 does not need to be involved. Therefore, even if these two data IDs “MsgB_A” and “MsgC_A” are excluded, the relay determination of the gateway device 20 is not affected. Therefore, the data ID to be received by the node 50a is only “MsgGW_A”. I understand that Similarly, the originally required reception data ID can be obtained for the node 50b and the node 50c, and the result is shown in FIG. 7C (the unnecessary reception data ID is erased with a double line).

  As described above, the gateway device 20 obtains the transmission data ID generated and transmitted by the transmission ID generation unit 53a7 such as the node 50a in addition to the reception data ID, thereby connecting to the same network. Since data frames transmitted and received between each other can be recognized, the data relay device 20 can generate the relay destination determination unit 23b1 that relays data frames that do not need to be relayed. As a result, the configuration of the relay destination determination unit 23b1 can be simplified.

  Note that such an inquiry about the transmission data ID is similar to the above-described inquiry about the reception data ID, for example, all the nodes 50a etc. in which the data frame transmitted from the gateway device 20 is connected to the network NW-1, etc. You may perform by the broadcast which notifies that it is useful as object. As a result, the number of transmissions from the gateway device 20 to the node 50a etc. is reduced to 1 / n (n is the number of nodes) compared to the case where such an inquiry is individually sent to the terminal device 50a etc. (unicast). Therefore, the transmission data ID can be received in a short time. Accordingly, since the network construction process can be performed at high speed, it is possible to reduce the setting work time of the data relay device 20 relating to the network configuration (substantially corresponding to claims 5 and 6).

  Next, the flow of processing by the relay destination table generation unit 23a5 executed by the CPU 21 of the gateway device 20 will be described with reference to FIGS. 1, 9, and 10. FIG. The processing of the relay destination table generation unit 23a5 (relay destination table generation processing) is realized by the CPU 21 executing a predetermined control program stored in the memory 23 of the gateway device 20.

  As shown in FIG. 9, in the process by the relay destination table generation unit 23a5, first, in step S101, a process of selecting a bus to be inquired about the received data ID, that is, an inquiry bus is performed. For example, referring to the relay destination table 23b1 in the relay destination table area 23b, the bus memory 1 to n for which the reception data ID corresponding to the bus is not generated is selected as the inquiry bus. A plurality of inquiry buses may be selected. Here, it is assumed that the bus bus-1 (network NW-1) shown in FIG. 1 is selected as the inquiry bus.

  In the subsequent step S103, processing for inquiring received data IDs from all nodes connected to the inquiry bus is performed. For example, in the previous example, all nodes 50a, 50b, and 50c connected to the network NW-1 selected as the inquiry bus are made to respond to the received data ID that the node should receive. Here, as shown in FIG. 7A, three types of received data IDs “MsgGW_A”, “MsgB_A”, and “MsgC_A” are transmitted to the gateway device 20 as data IDs to be received by the node 50a.

  In the next step S105, a process for obtaining the received data ID is performed. Thus, when the data frame transmitted from the node 50a or the like is received in step S101, the received data ID is extracted from the data frame. Here, the data frame transmitted by the node 50a includes three types of received data IDs “MsgGW_A”, “MsgB_A”, and “MsgC_A”, which are acquired in step S105.

  In the subsequent step S107, processing for generating the relay destination table 23b1 is performed. In this process, for example, the relay destination table 23b1 is generated by storing the received data ID acquired in step S105 in the bus memory of the relay destination table 23b1. Here, since three types of received data IDs “MsgGW_A”, “MsgB_A”, and “MsgC_A” have been acquired in step S105, the received data IDs are stored (registered) in the bus memory 1 of the relay destination table 23b1.

  In step S109, processing for determining whether or not the timeout time has elapsed is performed. If it is determined that the predetermined time-out period has not elapsed (S109: No), the process proceeds to step S105, and another node 50b connected to the same bus bus-1 (network NW-1) or the like. An attempt is made to acquire a received data ID that can be transmitted from the terminal, and the processing in step S107 and the like is performed in the same manner as described above.

  On the other hand, if the predetermined time-out period has elapsed (S109: Yes), the process proceeds to the subsequent step S111, and whether or not the acquisition of the reception data ID for all the buses bus-1 to bus-n has been completed. The determination process is performed. If the acquisition of the received data ID has not been completed (S111: No), the process proceeds to step S101, the process of selecting the inquiry bus is performed, and the process of step S103 and the like is performed as described above. Do.

  If it is determined in step S111 that acquisition of the received data ID has been completed (S111: Yes), generation of the relay destination table 23b1 has been completed. Terminate the process.

  In this way, in the processing (relay destination table generation processing) by the relay destination table generation unit 23a5, the relay destination table 23b1 is generated based on the received data ID received by the relay frame reception unit 23a2, so that it is transmitted from the node 50a or the like. By receiving the received data ID related to the type of the data body included in the data frame to be received by the node 50a or the like, the relay destination table 23b1 can be appropriately generated. As a result, the reception data ID necessary for generating the relay destination table 23b1 is received by the relay frame receiving unit 23a2 and learned by itself (generates the relay destination table 23b1) without relying on humans. Easy to build. Therefore, since the writing work and the exchange work of the memory 23 storing the relay destination table 23b1 are prevented, the burden of the setting work of the gateway device 20 relating to the network configuration can be reduced (corresponding substantially to claim 1). ).

  Note that the processing after step S101 and before step S109, that is, steps S103, S105, and S107, is changed to steps S103 ′, S105 ′, S106 ′, and S107 ′ as shown in FIG. The transmission data ID may be acquired in addition to the data ID, and the relay destination table generation unit 23a5 may be generated based on these IDs.

  That is, as shown in FIG. 10, after the process of inquiring the reception data ID and the transmission data ID for all nodes connected to the inquiry bus is performed in step S103 ′, the reception data ID is acquired in step S105 ′. Then, the transmission data ID is acquired, and the process of selecting the reception data ID is further performed in step S106 ′.

  As described with reference to FIG. 7 and FIG. 8, the selection of the reception data ID in step S106 ′ excludes the data ID (transmission data ID) to be transmitted from the data ID (reception data ID) to be received. Thus, the reception data ID necessary for the gateway device 20 is obtained.

  In the subsequent step S107 ', processing for generating the relay destination table 23b1 is performed. Here, for example, the relay destination table 23b1 is generated by storing the received data ID selected in step S106 'in the bus memory of the relay destination table 23b1. This process is the same as step S107 shown in FIG. 9 except that the storage target is “selected received data ID”.

  As described above, according to the relay destination table generation process shown in FIG. 10, the relay destination table 23b1 is generated based on the transmission data ID in addition to the reception data ID. As a result, it is possible to recognize data frames transmitted and received between the nodes 50a and the like connected to the network NW-1, that is, between the nodes 50a and the like connected to the same network. At 20, it is possible to generate a relay destination table 23b1 that relays data frames that do not need to be relayed. As a result, the configuration of the relay destination table 23b1 can be simplified. For example, the relay destination determination processing speed by the relay destination table 23b1 can be increased. Therefore, since the network construction process can be performed at high speed, the setting work time of the gateway device 20 related to the network configuration can be shortened (corresponding substantially to claim 4).

  Subsequently, the process of the reception ID generation unit 53a6 (reception ID generation process) executed by the CPU 51 such as the node 50a, or the process of the transmission ID generation unit 53a7 executed by the CPU 51 such as the node 50a (transmission ID generation process) ) Will be described with reference to FIGS. The reception ID generation process and the transmission ID generation process are realized by the CPU 51 executing a predetermined control program stored in the memory 53 such as the node 50a, and are similarly executed in any node 50a. Therefore, here, the processing by the node 50a will be described as a representative.

  As shown in FIG. 11, the reception ID generation unit 53a6 of the node 50a first determines whether or not there is a reception data ID inquiry (dotted arrow shown in FIG. 3B) by the gateway device 20 in step S301. Done. If there is an inquiry about the received data ID (S301: Yes), a received data ID acquisition process is performed in the subsequent step S303. On the other hand, when there is no inquiry about the received data ID (S301: No), it is not necessary to transmit the received data ID to the gateway device 20, and the series of processing by the received ID generating unit 53a6 is terminated.

  In step S303, reception data ID acquisition processing is performed. Since the reception ID table 53b1 stores the reception data ID of the data frame to be received by the node 50a, the reception data ID corresponding to the inquiry of the gateway device 20 can be obtained by referring to the reception ID table 53b1. get.

  In the subsequent step S305, a process of assembling the reception data ID acquired in step S303 into a predetermined data frame and transmitting it to the gateway device 20 by the data frame transmission unit 53a3 is performed. When there are a plurality of reception data IDs to be transmitted to the gateway device 20, as described above, they are transmitted all at once or transmitted separately. Thereby, since transmission to the gateway device 20 is completed, a series of processes by the reception ID generation unit 53a6 described above is terminated.

  As described above, in the process (reception ID generation process) by the reception ID generation unit 53a6, the reception data ID related to the type of the data body of the data frame to be received by the node 50a or the like (self) is generated, and is generated as the data frame transmission unit 53a3. Is transmitted to the network NW-1 or the like. This transmission is performed in response to a request from the gateway device 20 connected to the network NW-1 or the like. As a result, the gateway device 20 connected to the network NW-1 or the like can receive the reception data ID of the node 50a or the like as necessary. Therefore, as described above, the gateway device 20 relays the relay destination. The reception data ID necessary for generating the table 23b1 is received by the relay frame reception unit 23a2 without relying on humans, and learning is performed (generation of the relay destination table 23b1). Can be easily done. Accordingly, since the writing work and the exchange work of the memory 23 storing the relay destination table 23b1 are prevented, the burden of the setting work of the gateway device 20 relating to the network configuration can be reduced (substantially in claims 11 and 12). Corresponding).

  On the other hand, in the processing (transmission ID generation processing) by the transmission ID generation unit 53a7, processing is performed in which the reception data ID in each step (S301, S303, S305) shown in FIG. 11 is replaced with the transmission data ID. That is, in step S301, it is determined whether or not there is an inquiry about the transmission data ID from the gateway device 20. In step S303, the transmission data ID is acquired, and the acquired transmission data ID is transmitted to the gateway device 20 in step S305. Send. In acquiring the transmission data ID (S303), by referring to the transmission ID table 53b2 in which the transmission data ID of the data frame to be transmitted by the node 50a is stored, as in the reception ID table 53b1, The transmission data ID corresponding to the inquiry of the gateway device 20 is acquired.

  Thus, in the process (transmission ID generation process) by the transmission ID generation unit 53a7, the transmission data ID related to the type of the data body of the data frame to be transmitted by the node 50a or the like (self) is generated, and is generated as the data frame transmission unit 53a3. Is transmitted to the network NW-1 or the like. This transmission is performed in response to a request from the gateway device 20 connected to the network NW-1 or the like. Thereby, the gateway apparatus 20 connected to the network NW-1 or the like can receive the transmission data ID of the node 50a or the like as necessary.

  As shown in FIG. 12, it is determined in step S301 ′ whether there is an inquiry about the transmission data ID in addition to the reception data ID from the gateway device 20, and the reception data ID is acquired in step S303. As in the case where the reception data ID is transmitted to the gateway apparatus 20 by the above, the transmission data ID may be acquired by step S304 ′ and transmitted to the gateway apparatus 20 by step S306 ′.

  That is, in step S304 ′, as in the reception ID table 53b1, the transmission ID table 53b2 stores the transmission data ID of the data frame to be transmitted by the node 50a. Refer to this transmission ID table 53b2. Thus, the transmission data ID corresponding to the inquiry of the gateway device 20 is acquired. In step S306 ', the transmission data ID acquired in step S304' is assembled into a predetermined data frame and transmitted to the gateway apparatus 20 by the data frame transmission unit 53a3 in substantially the same manner as in step S305. In addition, even when there are a plurality of transmission data IDs to be transmitted to the gateway device 20, the transmission data IDs are transmitted all at once or transmitted separately.

  As a result, even if there is an inquiry about the transmission data ID in addition to the reception data ID from the gateway device 20, it can respond to the inquiry, so that the gateway device 20 connected to the network NW-1 or the like can receive the reception data ID and the transmission data. An ID can also be received. Therefore, in the gateway device 20, as described above, data frames transmitted / received between the nodes 50a connected to the network NW-1 etc.], that is, between the nodes 50a connected to the same network, etc. Therefore, the gateway apparatus 20 can generate a relay destination table 23b1 that relays data frames that do not need to be relayed. As a result, the configuration of the relay destination table 23b1 can be simplified. For example, the relay destination determination processing speed by the relay destination table 23b1 can be increased. Therefore, since the network construction process can be performed at high speed, the setting work time of the data relay device relating to the network configuration can be shortened (substantially corresponding to claims 13 and 14).

  Next, the flow of data frame relay processing by the gateway device 20 will be described with reference to FIG. This data frame relay process is stored in the memory 23 of the gateway device 20 with a predetermined control program corresponding to the relay frame receiving unit 23a2, the relay frame transmitting unit 23a3, and the data ID reference unit 23a4 described with reference to FIG. This is realized by executing what is executed by the CPU 21.

  First, in the data frame relay process, a data frame reception process is performed in step S501. This process is performed by the relay frame receiving unit 23a2, and is performed by appropriately extracting a data frame from the reception buffer of the interface unit 57. The reception buffer corresponds to a bus 1 interface unit 27a, a bus 2 interface unit 27b, a bus 3 interface unit 27c,..., Bus n corresponding to a plurality of buses bus-1 connected to the gateway device 20. Since it is provided for each interface unit 27n, the relay frame receiving unit 23a2 recognizes from which bus (referred to as “source bus number”) the extracted data frame is received.

  In step S503, processing for referring to the reception data ID stored in the bus memory of the relay destination table 23b1 is performed. This process is performed by the data ID reference unit 23a4, and the received data ID extracted from the received data frame is received in the bus memory (any one of the bus memory numbers 1 to n) of the relay destination table 23b1. Compare with the data ID to check whether they match. If there is a matching received data ID, the match flag is set and stored.

  In the subsequent step S505, a process is performed to determine whether or not the reference destination bus memory number in the relay destination table 23b1 compared in step S503 and the data frame transmission source bus number do not match. If both bus numbers do not match (S505: Yes), the process proceeds to step S507. If both bus numbers match (S505: No), the process proceeds to step S513. To do.

  For example, when the reference bus memory number (corresponding to the bus bus-3) of the relay destination table 23b1 compared in step S503 is “3”, the bus of the same number, that is, the bus bus-3 is assigned. Even if the data frame is transmitted, the data frame is returned to the transmission source network NW-3. Therefore, the data frame is not transferred to a network NW-1 other than the network NW-3. Therefore, in this step S505, when the bus number of the transmission source of the data frame and the reference destination bus memory number of the relay destination table 23b1 match (S505: No), the reference destination bus of the relay destination table 23b1 A process of excluding the memory number from the data frame transfer destination is performed. Accordingly, when a data frame is received from the bus number k (k = 1 to n), the bus numbers 2 to n when the bus number k = 1, and the bus numbers 1 to (when the bus number k = n. n-1) When the bus number k is other than this, the data are transferred to the bus numbers 1 to (k-1) and the bus numbers (k + 1) to n (S505: Yes).

  In step S507, processing for determining whether or not the received data ID exists in the bus memory is performed. That is, if there is a received data ID that matches the received data ID stored in the bus memory (any of the bus memory numbers 1 to n) of the relay destination table 23b1 by the processing in step S503, the match is found. Since the flag is set, it is possible to make a determination based on the processing by checking this flag.

  If the received data ID exists in the bus memory, that is, if the coincidence flag is set (S507: Yes), a process of passing the data frame to the relay frame transmitting unit 23a3 is performed in step S509. In S511, the data frame is transmitted to the bus.

  On the other hand, if the received data ID does not exist in the bus memory, that is, if the match flag is not set (S507: No), there is no data frame to be transmitted on the bus, so the process proceeds to step S513. Processing for determining whether or not the reference of the data ID in all the bus memories is completed is performed.

  In step S511, a process of transmitting the data frame passed from the data ID reference unit 23a4 to the bus by the relay frame transmission unit 23a3 is performed. This processing is performed by the relay frame transmission unit 23a3 as described above.

  If it is determined in step S513 that the reference of the data IDs in all the bus memories has been completed (S513: Yes), the bus for transferring the data frame does not remain, so the series of data frame relay processes described above are performed. finish.

  On the other hand, if it is not determined in step S513 that the reference of the data IDs in all the bus memories has been completed (S513: No), the previously referenced bus memory number is incremented (or decremented), and then step S503 is performed. Then, the same processing as described above is performed for the bus memory after increment (or decrement).

  As described above, the gateway device 20 can determine the transfer destination network by the data ID reference unit 23a4 and the relay destination table 23b1 based on the received data ID that can identify the type of the data body included in the data frame. The data frame transmitted from the node 50n connected to the NW-n can be transferred to the node 50a connected to the other network NW-1.

  As described above, according to the data communication system according to the present embodiment, the node 50a and the like generate the reception data ID related to the data body type of the data frame to be received by the reception ID generation unit 53a6. The data frame transmission unit 53a3 transmits the data to the network NW-1 or the like. On the other hand, the gateway device 20 receives the reception data ID transmitted from the node 50a or the like by the relay frame reception unit 23a2, and based on the reception data ID, the relay destination table generation unit 23a5 generates the relay destination table 23b1.

  Accordingly, the relay destination table 23b1 can be appropriately generated by receiving the received data ID related to the type of the data body included in the data frame to be received by the node 50a or the like with the information transmitted from the node 50a or the like. It becomes possible. In other words, the reception data ID necessary for generating the relay destination table 23b1 is received by the relay frame receiving unit 23a2 and learned by itself (generates the relay destination table 23b1) without relying on humans. Can be easily done. Therefore, since the writing work and the exchange work of the memory 23 storing the relay destination table 23b1 are prevented, the burden of the setting work of the gateway device 20 related to the network configuration can be reduced. ).

  <B> If the relay destination table generation unit 23a5 has acquired the reception data ID before the reception of the reception data ID by the relay frame reception unit 23a2, the relay destination table generation unit 23a5 performs relaying based on the acquired reception data ID. The destination table 23b1 may be generated. For example, the inspection device is connected to the interface unit 27 of the gateway device 20 at the manufacturing factory, and the received data ID is input to the gateway device 20 from the inspection device, or the diagnosis tool is connected to the network NW- of the gateway device 20 at the repair factory. 1 is connected, and the received data ID is transmitted to the gateway device 20 only by the diagnostic tool to learn (generate relay destination table 23b1) (substantially corresponds to claim 7).

  <B> When the relay destination table generation unit 23a5 has acquired the transmission data ID before receiving the transmission data ID by the relay frame reception unit 23a2, the relay destination table generation unit 23a5 performs relaying based on the acquired transmission data ID. The destination table 23b1 may be generated. For example, an inspection apparatus is connected to the interface unit 27 of the gateway apparatus 20 in a manufacturing factory, and both reception data ID and transmission data ID are command-inputted from the inspection apparatus to the gateway apparatus 20, or a diagnostic tool is connected to a gateway in a repair factory. Connected to the network NW-1 or the like of the device 20 and transmits both the received data ID and the transmitted data ID to the gateway device 20 only by the diagnostic tool to learn (generate the relay destination table 23b1) (substantially in claim 8) ).

  As a result, for example, the basic structure of the network NW-1 or the like that has been identified in advance is not based on the relay frame receiving unit 23a2, and a reception data ID (and transmission data ID) is given to the relay destination based on that. A table 23b1 can be generated. For this reason, in the generation of the relay destination table 23b1 based on the reception data ID (and transmission data ID) received by the subsequent relay frame reception unit 23a2, the reception data ID (and transmission data ID) already acquired and then received By generating the relay destination table 23b1 for the difference information from the received data ID (and transmission data ID), the generation of the relay destination table 23b1 based on the received reception data ID (and transmission data ID) is processed at high speed. can do. In addition, a reception data ID (and transmission data ID) that cannot be received by the relay frame reception unit 23a2 is given in advance by the inspection device or diagnostic tool, and the received reception data ID (and transmission data ID) and the received data are received thereafter. By performing the generation process of the relay destination table 23b1 for the difference information from the reception data ID (and transmission data ID), such a reception data ID (and transmission data ID) that cannot be received by the relay frame reception unit 23a2 is also relayed. A table 23b1 can be generated. Therefore, it is possible to further reduce the burden of setting work of the gateway device 20 related to the network configuration (corresponding substantially to claims 7 and 8).

  When learning with such a diagnosis tool (when generating the relay destination table 23b1), the reception data ID and the transmission data ID are also learned (generating the relay destination table 23b1) with respect to the diagnosis tool. Thus, the gateway device 20 can relay the diagnostic frame to the bus bus-1 or the like to which the diagnostic tool is connected. As a result, the diagnostic information can be reliably acquired regardless of which bus bus-1 or the like the diagnostic tool is connected to.

  <C> Furthermore, the relay destination table generation unit 23a5 generates the relay destination table 23b1 when the first predetermined condition is satisfied, and does not generate the relay destination table 23b1 when the first predetermined condition is not satisfied. You may comprise. As the “first predetermined condition”, for example, (1-1) that the relay destination table 23b1 is not generated, or (1-2) the network NW-1 or the like or an input device (for example, inspection in a manufacturing factory) (1-3) (1-1), (1-2) that there is an input of a specific command code (specific command) that can be input to the gateway device 20 from the outside such as a device or a diagnostic tool in a repair shop) ) And the like together. Thus, since the relay destination table 23b1 is generated only when the first predetermined condition is satisfied, the relay destination table 23b1 is unnecessary or mistakenly generated even though the relay destination table 23b1 is already generated. Generated (corresponding to (1-1)), the relay destination table 23b1 is generated in an incomplete network configuration (corresponding to (1-2)), transmission errors on a transmission medium such as a network, etc. Accidentally, the relay destination table 23b1 is erroneously generated (corresponding to (1-3)) even when data having the same meaning and content as the specific instruction code (specific command) is input. An erroneous generation of the relay destination table 23b1 can be prevented (substantially corresponding to claim 9).

  <D> Furthermore, the relay destination table generating unit 23a5 generates the relay destination table 23b1 again when the second predetermined condition is satisfied, and regenerates the relay destination table 23b1 when the second predetermined condition is not satisfied. You may comprise so that it may not produce | generate. Here, as the “second predetermined condition”, for example, (2-1) the network NW-1 or the like or an input device (for example, an inspection device in a manufacturing factory, a diagnostic tool in a repair factory) or the like from the outside of the gateway device 20 There is an input of a specific command code (specific command) that can be input to (2), or (2-2) input of a predetermined voltage or current that can be set in the gateway device 20 (power supply (battery or the like to be constantly supplied) ) Is input when voltage or current is connected. As a result, the relay destination table 23b1 is generated again only when the second predetermined condition is satisfied. Therefore, the relay destination table 23b1 is unnecessarily regenerated even though the relay destination table 23b1 is already generated. It is possible to prevent the relay destination table 23b1 from being generated or being accidentally generated again. Further, even when the option setting of the vehicle is changed by the user (addition or deletion of a device from the middle), the relay destination table 23b1 can be regenerated as necessary (substantially in claim 10). Correspondence).

  <E> Also, the timing of the inquiry of the reception data ID and transmission data ID to each node 50a, etc. is, for example, immediately after the gateway device 20 is turned on, immediately after the vehicle ignition switch is turned on (IG-ON), or an accessory switch. The gateway device 20 may be configured to make an inquiry to the node 50a or the like connected to the network NW-1 or the like at any timing such as immediately after being turned on (ACC-ON). As a result, even if nodes 50a connected to the network NW-1 or the like have different start-up power supply voltages (for example, the node 50a is activated by ACC-ON and the node 50x is activated by IG-ON). Since each node 50a and the like are inquired about the reception data ID at each timing, the reception data ID and transmission data ID can be reliably acquired from all the nodes 50a and the like. Therefore, it is possible to generate the relay destination table 23b1 that is not missing with respect to the reception data ID and the transmission data ID.

  <F> Further, when a data frame that should be transmitted from the gateway device 20 is not transmitted, the node 50a or the like is configured to be capable of determining communication interruption, and when it is determined that communication interruption has occurred, A configuration capable of notifying the gateway device 20 of which data frame having the received data ID has not been received is adopted in the node 50a and the like. When the gateway device 20 receives the notification, the content of the notification is used. A configuration is adopted in which the received data ID of a data frame that has not reached the node 50a or the like can be added to the relay destination table 23b1. Thereby, even if learning omission occurs, it can be corrected immediately.

  In the gateway device 20 described above, CAN, J1850, BEAN, IE-BUS, and ISO 9141 are exemplified as communication protocols of the network that can be connected to the gateway device 20, but the data that can identify the type of the data body constituting the data frame The present invention can be applied to, for example, TTCAN, FlexRay, Safe-by-Wire, BST, MOST, D2B, IEEE 1394, etc., as long as it adopts a frame format including the identifier in the data frame. The operations and effects described above can be obtained.

It is explanatory drawing which shows the structure of the data communication system which concerns on one Embodiment of this invention. FIG. 2A is a block diagram illustrating a configuration of a gateway device according to the present embodiment, FIG. 2A illustrates a hardware configuration, and FIG. 2B illustrates a configuration of a processing outline. FIG. 3A is a block diagram showing a configuration of a node according to the present embodiment, FIG. 3A shows a hardware configuration, and FIG. 3B shows a configuration of a processing outline. FIG. 4A is a CAN protocol protocol, FIG. 4B is a J1850 protocol, and FIG. 4C is a BEAN protocol. 4D is based on the IE-BUS protocol, and FIG. 4E is based on the ISO 9141 protocol. It is explanatory drawing supplemented about reception data ID and transmission data ID which are contained in the data frame exchanged in this data communication system. FIG. 6A is a diagram showing the reception data ID and transmission data ID of the data frame of each node 50a, 50b, 50c in the example of the data communication system shown in FIG. 5, FIG. 6A is for the node 50a, and FIG. For node 50b, FIG. 6C is for node 50c. 7A and 7B are diagrams illustrating examples of registration contents of the relay destination table of the gateway device in the example of the data communication system illustrated in FIG. 5. FIG. 7A is based on the reception data ID, and FIG. 7B is based on the transmission data ID. FIG. 7 (C) shows a configuration based on the reception data ID excluding the configuration based on the transmission data ID. FIG. 8 is an explanatory diagram that serves as a reference for deriving the reception data ID shown in FIG. It is a flowchart which shows the flow of the relay destination table production | generation process by the gateway apparatus which comprises the data communication system which concerns on this embodiment, and shows the basic form. It is a flowchart which shows the flow of the relay destination table production | generation process by the gateway apparatus of this embodiment, and shows the modification. It is a flowchart which shows the flow of the reception ID production | generation process by each node which comprises the data communication system which concerns on this embodiment. It is a flowchart which shows the flow of the transmission ID production | generation process by each node of this embodiment. It is a flowchart which shows the flow of the data frame relay process by the gateway apparatus of this embodiment.

Explanation of symbols

20 ... Gateway device (data relay device)
23a2 ... Relay frame receiving unit (reception type information receiving means, transmission type information receiving means)
23a3 ... Relay frame transmission unit (reception type information requesting means, transmission type information requesting means)
23a4: Data ID reference unit 23a5: Relay destination table generation unit (relay destination determination unit generation unit, reception type information request unit, transmission type information request unit)
23b: Relay destination table area 23b1: Relay destination table (relay destination determining means)
27a ... Interface unit corresponding to bus 1 (reception type information receiving means, transmission type information receiving means, reception type information requesting means, transmission type information requesting means)
27b ... Interface unit corresponding to bus 2 (reception type information receiving means, transmission type information receiving means, reception type information requesting means, transmission type information requesting means)
27c ... Interface unit corresponding to bus 3 (reception type information receiving means, transmission type information receiving means, reception type information requesting means, transmission type information requesting means)
27n... Bus n compatible interface section (reception type information receiving means, transmission type information receiving means, reception type information requesting means, transmission type information requesting means)
50a, 50b, 50c, 50d, 50e, 50x, 50y, 50z ... Node (terminal device)
53a2 ... Data frame reception unit 53a3 ... Data frame transmission unit (reception type information transmission unit, transmission type information transmission unit)
53a4 ... Data ID reference unit 53a5 ... Predetermined processing unit 53a6 ... Reception ID generation unit (reception type information generation means)
53a7 ... Transmission ID generation unit (transmission type information generation means)
53b1... Reception ID table 53b2... Transmission ID table 57a.
bus-1, bus-2, bus-3, bus-n ... bus
NW-1, NW-2, NW-3, ..., NW-n ... Network (one network, other network)

Claims (15)

In a data relay device capable of transferring a data frame transmitted from one network to a terminal device connected to another network, based on a data identifier capable of identifying the type of data body included in the data frame, A data relay apparatus comprising a relay destination determination means capable of determining another network,
In the information transmitted from the terminal device, reception type information receiving means for receiving the reception type information related to the type of the data body included in the data frame to be received by the terminal device; and
A relay destination determining means generating means capable of generating the relay destination determining means based on the reception type information received by the reception type information receiving means;
Reception type information requesting means capable of requesting the terminal device to transmit the reception type information;
With
The reception type information requesting unit transmits the request for the reception type information for all of the plurality of terminal devices to the plurality of terminal devices receiving the transmission request for the reception type information. Relay device. In a data relay device capable of transferring a data frame transmitted from one network to a terminal device connected to another network, based on a data identifier capable of identifying the type of data body included in the data frame, A data relay apparatus comprising a relay destination determination means capable of determining another network,
In the information transmitted from the terminal device, reception type information receiving means for receiving the reception type information related to the type of the data body included in the data frame to be received by the terminal device; and
A relay destination determining means generating means capable of generating the relay destination determining means based on the reception type information received by the reception type information receiving means;
Reception type information requesting means capable of requesting the terminal device to transmit the reception type information;
With
The reception type information requesting unit transmits a request for the reception type information to all the terminal devices that receive a transmission request for the reception type information when the data relay device is activated .   The reception type information requesting unit transmits a broadcast request for the reception type information for all of the plurality of terminal devices to the plurality of terminal devices receiving the transmission request for the reception type information. The data relay device according to claim 2. Transmission type information receiving means capable of receiving transmission type information relating to the type of data body included in the data frame to be transmitted by the terminal device as information transmitted from the terminal device,
The relay destination determining means generating means can generate the relay destination determining means based on the reception type information and the transmission type information received by the transmission type information receiving means. The data relay device according to any one of 1 to 3.   5. The data relay device according to claim 4, further comprising a transmission type information requesting unit capable of requesting the terminal device to transmit the transmission type information.   The transmission type information requesting means transmits a transmission request for the transmission type information for all of the plurality of terminal devices to the plurality of terminal devices receiving the transmission type information transmission request. The data relay device according to claim 5.   If the reception type information is acquired before the reception type information reception unit receives the reception type information, the relay destination determination unit generation unit is configured to perform the relay based on the acquired reception type information. The data relay device according to any one of claims 1 to 6, wherein a predetermination unit can be generated.   If the transmission destination information is acquired before the transmission type information receiving unit receives the transmission type information, the relay destination determination unit generation unit may generate the relay based on the acquired transmission type information. The data relay device according to any one of claims 4 to 6, wherein a predetermination unit can be generated.   The relay destination determination unit generation unit generates the relay destination determination unit when a first predetermined condition is satisfied, and does not generate the relay destination determination unit when the first predetermined condition is not satisfied. The data relay device according to any one of claims 1 to 8.   The relay destination determination unit generation unit generates the relay destination determination unit again when the second predetermined condition is satisfied, and does not generate the relay destination determination unit again when the second predetermined condition is not satisfied. The data relay device according to any one of claims 1 to 8. A terminal device capable of receiving a data frame including a data body and a data identifier capable of identifying the type of the data body from a network,
Reception type information generating means capable of generating reception type information related to the type of the data body of the data frame to be received by itself;
A terminal device comprising: a reception type information transmission unit capable of transmitting the reception type information generated by the reception type information generation unit to the network.   12. The terminal apparatus according to claim 11, wherein the reception type information transmitting unit transmits the reception type information to the network in response to a request from a data relay apparatus connected to the network. Transmission type information generating means capable of generating transmission type information related to the type of the data body of the data frame to be transmitted by itself;
The terminal apparatus according to claim 11, further comprising: a transmission type information transmitting unit capable of transmitting the transmission type information generated by the transmission type information generating unit to the network.   14. The terminal apparatus according to claim 13, wherein the transmission type information transmitting unit transmits the transmission type information to the network in response to a request from a data relay apparatus connected to the network. One network, another network, a terminal device connected to the other network, and a data frame connected to these networks and transmitted from the one network can be transferred to the terminal device of the other network A data relay device comprising relay destination determination means capable of determining the other network of the transfer destination based on a data identifier capable of identifying the type of data body included in the data frame in the data relay device. A data communication system,
The terminal device
Reception type information generating means capable of generating reception type information related to the type of the data body of the data frame to be received by itself;
A reception type information transmission unit capable of transmitting the reception type information generated by the reception type information generation unit to the data relay device;
The data relay device
Reception type information receiving means capable of receiving the reception type information transmitted from the terminal device;
A relay destination determining means generating means capable of generating the relay destination determining means based on the reception type information received by the reception type information receiving means;
Reception type information requesting means capable of requesting the terminal device to transmit the reception type information;
With
The reception type information requesting unit transmits the request for the reception type information for all of the plurality of terminal devices to the plurality of terminal devices receiving the transmission request for the reception type information. Communications system.

Images