JP2014154920A - On-vehicle relay device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an on-vehicle gate way that makes it possible to easily add or replace an ECU.SOLUTION: When receiving a relay request frame from an external device or ECU, a gate way retrieves a physical address and so on of a relay destination from a routing table based on the physical address of ECU or the like of the relay destination set in the frame (S105). When the retrieval succeeds (S110: Yes), relay is carried out based on the result of the retrieval. On the other hand, if the retrieval fails (S110: No), the gate way performs broadcast transmission of a frame instructing transmission of the physical address, and so on to the relay destination (S115). When receiving the physical address and so on from the relay destination, they are registered in the routing table (S125), and relay to the ECU or the like, which is a relay destination, is carried out.

Description

  The present invention relates to a vehicle-mounted relay device that relays data to a vehicle-mounted device.

  In recent years, many in-vehicle devices are mounted on vehicles, but these in-vehicle devices are classified according to their functions, uses, etc., and a plurality of in-vehicle devices having the same type of functions, uses, etc. are, for example, CAN, An in-vehicle network conforming to a communication protocol such as LIN is formed.

  Each in-vehicle network is connected to a relay device, and in-vehicle devices connected to different in-vehicle networks communicate via the relay device. It is also known that a fault diagnosis of an in-vehicle device is performed by connecting an external device for failure diagnosis to the relay device, and the external device and the in-vehicle device communicate via the relay device.

  Here, the gateway described in Patent Document 1 includes a gateway control unit having information in which events corresponding to relayed messages, execution timings of the events, and the like are registered, separately from the CPU that performs overall control of the device itself. Prepare. When the gateway control unit receives the message, the gateway control unit executes an event corresponding to the message based on the information at the registered execution timing, thereby reducing the processing load on the CPU and relaying the message at high speed. Done.

Special table 2009-527168

  By the way, the relay device has the identification information of each in-vehicle device, the identification information of the in-vehicle network to which the in-vehicle device is connected, etc., and based on these information, between the in-vehicle devices connected to different in-vehicle networks Alternatively, the communication between the external device and the in-vehicle device is relayed.

  Therefore, when an in-vehicle device is replaced or added, it is necessary to set the identification information of the replaced in-vehicle device or the identification information of the in-vehicle network to which the in-vehicle device is connected to the relay device. However, there is a problem that replacement or addition of the in-vehicle device cannot be easily performed.

  This invention is made | formed in view of the said subject, and it aims at providing the vehicle-mounted relay apparatus which can perform addition or replacement | exchange of a vehicle-mounted apparatus easily.

  The in-vehicle relay device according to claim 1 made in view of the above problems communicates with each in-vehicle device constituting a plurality of in-vehicle networks provided in the own vehicle or an external device temporarily connected to the own device. Via the communication means, the storage means storing the correspondence information registered in association with the logical address indicating the in-vehicle device and the identification information related to the in-vehicle device indicated by the logical address, via the communication means, When relay request data including a logical address is received from the in-vehicle device or the external device, a specifying unit that specifies identification information related to the in-vehicle device indicated by the logical address registered in the correspondence information is provided.

  In addition, when the specifying unit fails to specify the identification information, the in-vehicle relay device receives instruction data that instructs the in-vehicle device related to the identification information to transmit response data including the identification information to the own device. , Indicating means for broadcasting to a plurality of in-vehicle devices via the communication means, and receiving response data via the communication means, the identification information included in the response data and the in-vehicle device related to the identification information Registration means for registering the logical address in association with the correspondence information.

  In addition, when the specifying unit succeeds in specifying the identification information, the in-vehicle relay device is connected to the in-vehicle device based on the identification information and relay request data including a logical address indicating the in-vehicle device related to the identification information. When the corresponding relay data is generated and the identification unit fails to identify the identification information, the identification information included in the response data received according to the instruction data transmitted due to the failure, and the in-vehicle device related to the identification information Based on the relay request data including the logical address to indicate, the generating means for generating the relay data corresponding to the in-vehicle device, and the relay data generated by the generating means via the communication means, the in-vehicle corresponding to the relay data Transmitting means for transmitting to the apparatus.

  According to such a configuration, the in-vehicle device or the external device transmits the relay request data in which the logical address of the in-vehicle device or the external device as the transmission destination is set to the in-vehicle relay device, so that the in-vehicle device of the transmission destination Data can be transmitted to the For this reason, even if the in-vehicle device or the like does not know the physical address or communication protocol of the destination in-vehicle device or the like, as long as it knows the logical address, the other in-vehicle device via the vehicle relay device Etc. can communicate.

  Further, when the destination logical address is not registered in the correspondence information of the in-vehicle relay device, the in-vehicle relay device performs address resolution by broadcasting the instruction data, and the in-vehicle corresponding to the logical address Identification information regarding the device or the like is registered in the correspondence information. As a result, the in-vehicle relay device can relay data to the in-vehicle device or the like even if the identification information regarding the destination in-vehicle device or the like is not grasped.

  For this reason, even when the in-vehicle device is newly added or when the in-vehicle device is replaced, if the other in-vehicle device knows the logical address of the newly added in-vehicle device, Data can be transmitted and received via the in-vehicle relay device. Similarly, for external devices, if the logical address of a newly added in-vehicle device is known, data is transmitted to and received from the in-vehicle device via the in-vehicle relay device, and the failure diagnosis of the in-vehicle device is performed. Etc. can be performed.

  Therefore, according to the in-vehicle relay device of the first aspect, it is possible to easily add or replace the in-vehicle device.

It is a block diagram which shows the structure of a gateway. It is a block diagram which shows the structure of a routing table. It is explanatory drawing which shows the hierarchical structure of communication functions, such as a gateway in case an application level relay is performed. It is explanatory drawing which shows the hierarchical structure of communication functions, such as a gateway in case a network level relay is performed. It is explanatory drawing which shows the structure of a relay request | requirement frame. It is a flowchart of a relay process. It is a flowchart of an external communication process. It is explanatory drawing which shows the structure of the address resolution instruction | indication frame based on CAN, and an address resolution response frame in case an application level relay is performed. It is a flowchart about the address resolution at the time of relaying between the external device connected to each vehicle-mounted network based on CAN, and ECU when application level relaying is performed. It is explanatory drawing which shows the structure of the address resolution instruction | indication frame based on CAN, and an address resolution response frame in case a network level relay is performed. It is a flowchart about the address resolution at the time of relaying between the external device connected to each vehicle-mounted network based on CAN, and ECU when network level relaying is performed. It is explanatory drawing which shows the structure of the address resolution instruction | indication frame and address resolution response frame based on LIN when relay of an application level is performed. It is explanatory drawing which shows the structure of the address resolution instruction | indication frame based on FlexRay, and an address resolution response frame in case an application level relay is performed. It is a flowchart about the address resolution at the time of relaying between the external device connected to each vehicle-mounted network based on a different communication protocol, and ECU.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. The embodiment of the present invention is not limited to the following embodiment, and can take various forms as long as they belong to the technical scope of the present invention.

[Description of configuration]
<About the gateway>
The in-vehicle gateway 10 of this embodiment is connected to a plurality of in-vehicle networks 40 compliant with a communication protocol such as CAN, LIN, etc., and is configured to relay communication between the ECUs 30 connected to the in-vehicle network 40 ( (See FIG. 1). The gateway 10 may be connected to a plurality of in-vehicle networks 40 that conform to the same communication protocol.

  The gateway 10 can communicate with, for example, a smartphone equipped with an application for failure diagnosis of the ECU 30 or an external device 20 configured as a failure diagnosis tool. The external device 20 can perform a failure diagnosis of the ECU 30 by communicating with the ECU 30 via the gateway 10.

  The external device 20 may communicate with the gateway 10 by wireless communication conforming to a communication protocol such as a wireless LAN, or may be temporarily connected to the in-vehicle network 40 and connected to the gateway 10 via the in-vehicle network 40. Communication may be performed. The external device 20 may be configured to be accessible to a wireless communication network, and may communicate with the gateway 10 via the wireless communication network.

The gateway 10 includes a CPU 11, a RAM 12, a ROM 13, a communication unit 17, a telematics communication unit 16, and the like, which are connected by an internal bus 14.
The CPU 11 operates according to a program stored in the ROM 13 and controls the gateway 10 as a whole. As one of the programs, a communication processing unit 15 for controlling the communication unit 17 is provided.

The telematics communication unit 16 is a part for accessing the wireless communication network, and communicates with the external device 20 via the wireless communication network.
In addition, the communication unit 17 includes, as an example, portions 17a to 17c that perform wireless communication in conformity with a wireless LAN, WiFi, BT (Bluetooth (registered trademark)), and the like. Communication takes place. Moreover, the communication part 17 has the site | parts 17d-17i which perform communication based on CAN, LIN, MOST, Ethernet (trademark), FlexRay, USB etc. as an example. By these parts, communication is performed with the ECU 30 configuring the in-vehicle network 40 and the external device 20 temporarily connected to the in-vehicle network 40.

And CPU11 communicates with ECU30 connected to the external device 20 and the vehicle-mounted network 40 via the communication part 17 by operate | moving according to the communication process part 15. FIG.
In the present embodiment, a unique logical address is set for each ECU 30 and the external device 20. When the ECU 30 and the external device 20 communicate via the gateway 10, the relay destination is a logical address. Is specified. It should be noted that logical addresses corresponding to a plurality of ECUs 30 may be provided. In such a case, the logical addresses are designated as relay destinations, so that the corresponding ECUs 30 are relayed simultaneously.

  In order to perform such relaying, the gateway 10 has a routing table indicating a correspondence relationship between a logical address and identification information (for example, a physical address) regarding the ECU 30 or the external device 20 in which the logical address is set. . The routing table is stored in the ROM 13 and the RAM 12, and the gateway 10 searches the routing table to identify information related to the in-vehicle network 40 and the ECU 30 that are relay destinations.

  Furthermore, when a logical address that is not registered in the routing table is a relay destination, the gateway 10 performs address resolution and is necessary for relaying to the ECU 30 or the external device 20 corresponding to the logical address. Information is acquired (details will be described later).

<About routing table>
In the routing table 50, an item indicating the “logical address” of each ECU 30 or the external device 20 is provided. Corresponding to the “logical address”, “relay availability information”, “relay buffer size”, “relay type”, “ECU identification information”, “communication protocol”, “in-vehicle network identification information”, “transmission I” Items such as “/ F”, “relay destination buffer size”, and “history information” are provided (see FIG. 2).

  “Relayability information” is an item indicating a logical address of the ECU 30 or the external device 20 that is permitted to communicate with the ECU 30 or the like indicated by the corresponding logical address. By this item, for example, communication from the external device 20 configured as a smartphone possessed by a general user to the ECU 30 such as an airbag is prohibited, and as a result, for example, inappropriate such as stopping the airbag function from the smartphone. Processing is prevented.

The “relay buffer size” indicates the size of the relay buffer used when the gateway 10 relays communication to the ECU 30 or the like indicated by the corresponding logical address.
More specifically, for example, Ethernet has a higher communication speed than CAN, and the data length of one frame is also large. For this reason, when relaying from the ECU 30 connected to the Ethernet to the ECU 30 connected to the CAN, it is necessary to temporarily store the data received from the relay source, and perform accumulation relay that divides the data and sequentially relays the data. . The “relay buffer size” indicates the size of the relay buffer used for such accumulation relay.

The “relay type” is an item indicating a method for relaying to the ECU indicated by the logical address corresponding to the gateway 10.
As a relay method, in addition to the above-described accumulation relay, a method (sequential relay) in which each time a frame is received from the relay source, the frame is modified as necessary and transmitted to the in-vehicle network 40 or the like of the relay destination is considered. It is done. Whether the relay method is the accumulation relay or the sequential relay is determined based on, for example, the communication speed of the in-vehicle network 40 that is the relay destination.

  The “ECU identification information” is an item indicating identification information (for example, a physical address) related to the ECU 30 or the like indicated by the corresponding logical address. When the ECU 30 or the like is connected to the CAN, the item includes, for example, information necessary for communication such as a CAN-ID used at the time of transmission to the ECU 30 or the like or a response from the ECU 30 or the like. Used to allocate.

  The “communication protocol” indicates a communication protocol of the in-vehicle network 40 to which the ECU 30 or the like indicated by the corresponding logical address is connected, or a communication protocol when performing wireless communication with the external device 20 indicated by the logical address.

The “in-vehicle network identification information” indicates identification information of the in-vehicle network 40 to which the ECU 30 or the like indicated by the corresponding logical address is connected.
The “transmission I / F” is a relay when the communication protocol of the in-vehicle network 40 to which the ECU 30 or the like (relay destination ECU 30 or the like) indicated by the corresponding logical address is connected and the relay in-vehicle network 40 is different. A frame conversion method is shown.

  The “relay destination buffer size” indicates a buffer size for communication provided in the ECU 30 or the like corresponding to the logical address. When relaying to the ECU 30, the gateway 10 determines the data length of the frame relayed to the ECU 30 in consideration of the buffer size.

  “History information” indicates a record of relay to the ECU 30 or the like corresponding to the logical address. The “history information” may be stored in the RAM 12 or a rewritable nonvolatile memory (not shown) (flash memory or the like).

  The routing table 50 includes a portion (preset table) stored in the ROM 13 (or a flash memory (not shown)) and a portion (cache table) stored in the RAM 12 (or a flash memory (not shown)). Exists.

  Then, the logical addresses of the ECU 30 and the external device 20 that are scheduled to communicate are registered in the preset table. On the other hand, the logical address of the ECU 30 and the like newly connected to the in-vehicle network 40 is registered in the cache table by address resolution described later.

In addition, for logical addresses indicating a plurality of ECUs 30, information relating to these ECUs 30 is registered in each item corresponding to the logical addresses.
<About communication functions such as gateways>
Next, communication functions in the gateway 10, the ECU 30, and the external device 20 will be described. The communication function is hierarchized into an AP (application) layer, a TP (transport) layer, an NW (network) layer, a DL (data link) layer, and a physical layer (see FIGS. 3 and 4).

  In addition, as described above, the gateway 10 can perform relaying by two types of storage relays and sequential relays. However, when relaying by each method is performed, processing performed in each layer of the communication function Are partly different.

  First, the accumulation relay is performed (see FIG. 3). The accumulation relay is mainly performed when relaying communication of the ECU 30 or the external device 20 connected to the in-vehicle network 40 conforming to a different communication protocol. (Of course, it may be performed when relaying communication between the ECU 30 and the external device 20 connected to the in-vehicle network 40 compliant with the same communication protocol). In addition to this, accumulation relay is also mainly performed when relaying communication between the external device 20 that communicates with the gateway 10 and the ECU 30 via a wireless LAN, a wireless communication network, or the like.

When accumulation relay is performed, relay and address resolution are performed at the center of the AP layer (in other words, accumulation relay is an application level relay).
That is, in the gateway 10, the communication unit 17 functions as a DL layer and a physical layer, and the communication processing unit 15 functions as a TP layer and an NW layer. Further, the gateway 10 is provided with a GW control unit 11a and an address resolution unit 11b as programs for controlling the CPU 11, and these function as an AP layer.

  On the other hand, in the ECU 30, the communication unit 34 that performs communication in accordance with the communication protocol of the in-vehicle network 40 to which the device is connected functions as the DL layer and the physical layer, and the communication processing unit 33 that controls the communication unit 34 includes the TP layer, It functions as an NW layer. Further, the ECU 30 is provided with a server unit 31 and an address resolution unit 32 that are programs for controlling the CPU and function as an AP layer. The server unit 31 communicates with another ECU 30 and the external device 20 via the gateway 10, and the address resolution unit 32 performs the above-described processing for address resolution.

  In the external device 20, the communication unit 23 that performs communication in accordance with a predetermined communication protocol functions as the DL layer and the physical layer, and the communication processing unit 22 that controls the communication unit 23 functions as the TP layer and the NW layer. To do. In addition, a client unit 21 that is a program for controlling the CPU of the external device 20 and functions as an AP layer is provided. The client unit 21 communicates with the ECU 30 via the gateway 10, thereby causing a malfunction of the ECU 30. Make a diagnosis.

  When transmission of relay request frames from the external device 20 or the ECU 30 to the gateway 10 is started, the GW control unit 11a of the gateway 10 receives these relay request frames via the communication unit 17 and the communication processing unit 15. The data is stored in a buffer provided in the RAM 12.

  Thereafter, when the reception of all relay request frames is completed, the GW control unit 11a, based on the logical address set as the relay destination in the relay request frame, from the routing table 50 to the physical address of the relay destination ECU 30 and the in-vehicle network 40 The identification information and the like are searched. Based on the search result, a relay frame corresponding to the relay destination is generated and sent to the in-vehicle network 40 to which the relay destination ECU 30 is connected via the communication processing unit 15 and the communication unit 17.

The address resolution unit 11b performs the above-described processing for address resolution.
On the other hand, the sequential relay is mainly performed when relaying communication between the ECU 30 and the external device 20 connected to the in-vehicle network 40 compliant with the same communication protocol (of course, the in-vehicle network compliant with different communication protocols). 40 may be performed when relaying communication between the ECU 30 connected to 40 and the external device 20). FIG. 4 shows, as an example, a case where communication between the external device 20 connected to a different in-vehicle network 40 compliant with CAN and the ECU 30 is relayed.

When sequential relay is performed, relay and address resolution are performed centering on the NW layer, TP layer, and AP layer (in other words, sequential relay can be said to be relay at the network level).
That is, in the gateway 10, the communication unit 17 functions as a DL layer and a physical layer. In addition, the gateway 10 is provided with a router control unit 15a and an address resolution unit 15b configured by a program for controlling the CPU 11 and a communication processing unit 15, and these function as an AP layer, a TP layer, and an NW layer. .

  On the other hand, in the ECU 30, the communication unit 34 functions as a DL layer and a physical layer, the communication processing unit 33 functions as a TP layer and an NW layer, and the server unit 31 functions as an AP layer. In addition, an address resolution unit 35 including a program for controlling the CPU and a communication processing unit 33 is provided. The address resolution unit 35 functions as an AP layer, a TP layer, and an NW layer, and the address described above. Process for resolution.

The external device 20 has the same configuration as that in the case where accumulation relay is performed.
When transmission of a relay request frame from the external device 20 or the ECU 30 to the gateway 10 is started, the router control unit 15a of the gateway 10 receives the relay request frame via the communication unit 17. Further, the router control unit 15a searches the routing table 50 for identification information of the ECU 30 and the in-vehicle network 40 from the routing table 50 based on the logical address set as the transmission destination in the relay request frame.

  Further, the router control unit 15a modifies the relay request frame as necessary based on the search result, generates a relay frame, and transmits the relay frame to the in-vehicle network 40 to which the ECU 30 as the transmission destination is connected via the communication unit 17. To do. Note that, as a specific example of the modification, if the in-vehicle network 40 is compliant with CAN, conversion of a CAN-ID according to a transmission destination may be considered.

The address resolution unit 15b performs the above-described processing for address resolution.
<Relay request frame>
The relay request frame 60 transmitted from the relay ECU 30 or the like to the gateway 10 when relaying by the gateway 10 is generally composed of a protocol dependent unit 61, a source address 62, a target address 63, a message 64, and the like. (See FIG. 5).

  The protocol dependent unit 61 is data for transmission from the ECU 30 or the like of the relay source (transmission source of the relay request frame 60) to the gateway 10, and is determined according to the communication protocol between these devices.

The source address 62 is data indicating a logical address of the relay source ECU 30 or the external device 20.
The target address 63 is data indicating a logical address of the relay destination ECU 30 or the external device 20.

  The message 64 is data indicating the contents of instructions to the relay destination ECU 30 and the like. Specifically, for example, in the case of instructing a failure diagnosis of the ECU 30 from the external device 20, it is conceivable that a transmission request for data stored in a failure code or a specified address is used as a message. Further, for example, when a response to the failure diagnosis is sent from the ECU 30 to the external device 20, a failure code or data read in response to an instruction from the external device 20 may be used as a message.

[Description of operation]
<About relay processing>
Next, a relay process in which the gateway 10 relays communication between the ECUs 30 or between the ECU 30 and the external device 20 will be described with reference to a flowchart shown in FIG. This process is started when the gateway 10 is activated.

  In S <b> 100, the CPU 11 of the gateway 10 waits for reception of the relay request frame 60 from the ECU 30 or the external device 20. It is assumed that the relay request frame 60 is received from the in-vehicle network 40, received via wireless communication, or received from the wireless communication network via the telematics communication unit 16. Then, when the CPU 11 receives the relay request frame 60, the process proceeds to S105.

  In S105, the CPU 11 specifies the source address 62 of the received relay request frame 60 as a logical address of the relay source ECU 30 and the like, and specifies the target address 63 as a logical address of the relay destination ECU 30 and the like. Then, the CPU 11 searches the routing table 50 for the logical address of the relay destination.

  In subsequent S110, the CPU 11 determines whether or not the search of the logical address of the relay destination has succeeded. If the search is successful (S110: Yes), the process proceeds to S130, and if the search has failed (S110). : No), the process proceeds to S115.

  In S115, the CPU 11 broadcasts an address resolution instruction frame (details will be described later) to all ECUs 30 and external devices 20 connected to the gateway 10 via the in-vehicle network 40 or wireless communication. This address resolution instruction frame contains the logical address of the relay destination, and instructs the ECU 30 or the like indicated by the logical address to transmit identification information of the own device to the gateway 10.

  The identification information may be a physical address of the ECU 30 indicated by the logical address of the relay destination. Further, when the communication protocol of the in-vehicle network 40 to which the ECU 30 is connected is CAN, it may be a CAN-ID used for transmission to the ECU 30 and a response.

  Alternatively, a configuration may be adopted in which the in-vehicle network 40, the ECU 30, and the like that are targets for address resolution are determined in advance, and address resolution instruction frames are broadcasted for these.

  In subsequent S120, the CPU 11 determines whether or not an address resolution response frame including the identification information of the ECU 30 is received from the ECU 30 indicated by the logical address of the relay destination, and when an affirmative determination is obtained (S120). : Yes), the process proceeds to S125.

  On the other hand, if the address resolution response frame cannot be received after the time limit has elapsed after the address resolution instruction frame is transmitted (S120: No), the CPU 11 shifts the process to S100 and stops relaying.

  In S125, the CPU 11 newly registers the logical address of the relay destination in the routing table 50 (cache table), and is included in the received address resolution response frame as “ECU identification information” corresponding to the logical address. Registered identification information.

  Further, the CPU 11 identifies the identification information and communication protocol of the in-vehicle network 40 that has received the address resolution response frame, and registers them as “in-vehicle network identification information” and “communication protocol” corresponding to the logical address of the relay destination.

  In addition, the CPU 11 determines a relay buffer size that can be used when relaying communication to the ECU 30 or the like indicated by the relay destination logical address, and registers it as a “relay buffer size” corresponding to the logical address.

  Further, the CPU 11 determines the relay method and frame conversion method based on the communication speed of the in-vehicle network 40 to which the ECU 30 or the like indicated by the relay destination logical address is connected, and the “relay type”, corresponding to the logical address, Register as “Communication I / F”. Note that the CPU 11 may communicate with the ECU 30 or the like and determine a relay method or a frame conversion method based on information acquired from the ECU 30 or the like.

  Further, the CPU 11 communicates with the ECU 30 or the like indicated by the logical address of the relay destination, acquires a logical address indicating the ECU 30 or the like permitted to communicate with the ECU 30 or the like, and has a communication buffer size provided in the ECU 30 or the like. (Of course, these pieces of information may be included in the address resolution response frame). The acquired logical address and buffer size are registered as “relay availability information” and “relay destination buffer size” corresponding to the logical address.

  In subsequent S130, the CPU 11 generates a new relay frame from the received relay request frame based on the information registered in the routing table 50 corresponding to the logical address of the relay destination, and then transmits the relay frame to the relay destination. (S135). If an address resolution response frame is received, the CPU 11 may generate a relay frame based on the address resolution response frame, the received relay request frame, or the like.

  Specifically, the CPU 11 determines whether the logical address of the relay source ECU 30 or the like is registered in the “relay enable / disable information” of the relay destination logical address, and if it is not registered, the relay is not performed. The process proceeds to S100.

  On the other hand, when the logical address of the relay source is registered, the CPU 11 refers to the “relay type” corresponding to the logical address of the relay destination, and determines the relay method such as whether the relay method is accumulation relay or sequential relay. Determine. When relaying communication between the ECUs 30 and the like connected to the two in-vehicle networks 40 conforming to the same communication protocol, the CPU 11 relays sequentially regardless of the relay method indicated by the “relay type”. You may choose to do.

  Further, the CPU 11 refers to “ECU identification information”, “communication protocol”, “in-vehicle network identification information”, “transmission I / F”, and “relay destination buffer size” corresponding to the logical address of the relay destination. Then, based on the information indicated by these items, the CPU 11 identifies a relay frame generation method corresponding to the communication protocol of the relay destination ECU 30 or the in-vehicle network 40 from the received relay request frame.

  When the relay method is accumulation relay, after the reception of all relay request frames is completed, a new relay frame is generated based on the received relay request frame in accordance with the generation method, and the relay destination ECU 30 or the like The transmission of the relay frame to is started.

  On the other hand, in the case of sequential relay, every time the CPU 11 receives a relay request frame, the CPU 11 generates a new relay frame based on the relay request frame according to the above generation method, and transmits it to the relay destination ECU 30 or the like. At this time, the CPU 11 may transmit the received relay request frame as it is to the relay destination ECU 30.

  When the size of the relay buffer being used reaches the buffer size indicated by “relay buffer size”, the CPU 11 interrupts the relay and shifts the processing to S100.

  During relaying, the CPU 11 measures the data size of the relayed frame and the time required for relaying. When the relaying is completed, these pieces of information are used as “history information” corresponding to the logical address of the relay destination. After that, the process proceeds to S100.

  By such relay processing, the ECU 30 and the external device 20 transmit data to the relay destination by transmitting to the gateway 10 a relay request frame in which the logical addresses of the ECU 30 and the external device 20 serving as the relay destination are set. Can do. For this reason, the ECU 30 or the like communicates with other ECUs 30 or the like via the gateway 10 as long as it knows the logical address even if it does not know the physical address or communication protocol of the relay destination ECU 30 or the like. be able to.

  If no logical address is registered in the routing table 50 of the gateway 10, the address is resolved in the gateway 10, and identification information related to the ECU 30 or the like corresponding to the logical address is registered in the routing table 50. Thereby, the gateway 10 can relay data to the ECU 30 or the like even if the gateway 10 does not grasp the identification information regarding the ECU 30 or the like of the transmission destination.

  For this reason, even when the ECU 30 is newly added or replaced, as long as the other ECU 30 knows the logical address of the newly added ECU 30, the communication is performed via the gateway 10. It can be carried out. Similarly, if the external device 20 knows the logical address of the newly added ECU 30, it can communicate with the ECU 30 via the gateway 10 to perform failure diagnosis of the ECU 30. .

Therefore, by using the gateway 10 of the present embodiment, the ECU 30 can be easily added or replaced.
<External communication processing>
Next, external communication processing in which the external device 20 for failure diagnosis communicates with the ECU 30 via the gateway 10 and performs failure diagnosis of the ECU 30 will be described with reference to a flowchart shown in FIG. This process is started in response to an instruction from the user at the external device 20.

In S200, the external device 20 activates an in-vehicle cooperation app for performing failure diagnosis, various settings, and the like of the ECU 30, etc., and proceeds to S205.
In S205, the external device 20 displays abstract vehicle functions and diagnostic items such as an engine, a brake, and an air conditioner on a display, and accepts selection of these functions and the like via a touch panel or the like. Each function or the like is associated with a logical address of one or a plurality of ECUs 30 related thereto, and a target ECU 30 for failure diagnosis is set by accepting selection of the function or the like. In addition, after accepting selection of a function or the like, the external device 20 accepts an input of a measure (for example, failure diagnosis contents or various setting changes) that the user intends to perform on the function or the like.

  In subsequent S210, the external device 20 generates a relay request frame 60 to be transmitted to the target ECU 30 based on the input content from the user. That is, the external device 20 generates the protocol dependence unit 61 based on the communication protocol with the gateway 10. The external device 20 sets the logical address of the target ECU 30 as the target address 63 and sets the logical address of its own device as the source address 62.

  Furthermore, the external device 20 generates a message 64 (for example, a request for transmitting a data stored in a failure code or a specified address, a request for changing a set value of the ECU 30) corresponding to the input action. . The external device 20 generates a relay request frame 60 based on these, and transmits the relay request frame 60 to the gateway 10.

  In subsequent S <b> 215, the external device 20 waits to receive a relay frame as a response from the target ECU 30 via the gateway 10. When the relay frame is received, the external device 20 displays processing corresponding to the content of the message in the relay frame (for example, processing for displaying a fault code and read data, and a result of changing the set value of the ECU 30). And the process proceeds to S205.

  As described above, the external device 20 can communicate with the ECU 30 via the gateway 10 as long as it knows the logical address, even if it does not know the physical address and communication protocol of the ECU 30. Furthermore, even when the ECU 30 is added or exchanged and the physical address of the ECU 30 or the ID of the frame used for communication changes, the address resolution is performed by the gateway 10, so the external device 20 adds the ECU 30, etc. Communication can be performed in the same manner as before.

  Therefore, the external device 20 for failure diagnosis can communicate with the ECU 30 regardless of the manufacturer, the vehicle type, and the type of the vehicle type, and the external device 20 can be used properly according to the manufacturer or the like. It is possible to perform fault diagnosis on a general basis without using different apps.

  Therefore, the external device 20 for failure diagnosis can provide a failure diagnosis function based on abstract vehicle functions and diagnosis items, as in the above-described external communication processing. For this reason, even if the user does not have advanced in-vehicle network knowledge such as the physical address of the ECU 30 and the ID of the frame used for failure diagnosis, the user can easily perform failure diagnosis of the target using the external device 20. be able to.

Furthermore, by using a smartphone as the external device 20, a general user can easily perform a failure diagnosis.
[Specific examples of address resolution]
<Specific example 1>
First, one example of a process for performing address resolution of the ECU 30 connected to the in-vehicle network 40 compliant with CAN, for example, when accumulation relay is performed (when relay is performed at the application level) will be described.

  In the address resolution instruction frame 300 in such a case, an ID indicating broadcast transmission is set as the CAN-ID 301. The data field is composed of N_PCI (Network Protocol Control Information) 302, SID (Service ID) 303, transmission destination logical address 304, transmission source logical address 305, and option 306 (see FIG. 8).

  N_PCI 302 indicates the type of frame such as SF (Single Frame), FF (First Frame), etc., and SID 303 indicates the content of the instruction by the address resolution instruction frame 300. Further, the transmission destination logical address 304 indicates a logical address of the relay destination ECU 30 or the like, the transmission source logical address 305 indicates a logical address of the relay source ECU 30 or the like, and the option 306 indicates various information related to address resolution. Show.

  In the address resolution response frame 310, an ID indicating that the gateway 10 is the transmission destination is set as the CAN-ID 311. The data field includes N_PCI 312, RSID (Response Service ID) 313, Type 314, request CAN-ID 315, response CAN-ID 316, and option 317.

  RSID 313 indicates the response content and the like by the address resolution response frame 310, and Type 314 indicates the communication protocol of the in-vehicle network 40 as the relay destination. The request CAN-ID 315 indicates a CAN-ID used for transmission to the relay destination ECU 30 or the like, and the response CAN-ID 316 indicates a CAN-ID used for a response from the relay destination ECU 30 or the like.

  For example, if a failure diagnosis of the relay destination ECU 30 is performed, a CAN-ID for failure diagnosis of the ECU 30 is set as the request CAN-ID 315 and the response CAN-ID 316.

  Next, a specific example of address resolution when the gateway 10 relays communication between the external device 20 connected to each in-vehicle network 40 compliant with CAN and the ACECU 30a at the application level (when accumulation relay is performed). Will be described with reference to the flowchart shown in FIG.

  In S400, the external device 20 (logical address is 0xE403 as an example) transmits a relay request frame to the gateway 10 (logical address is 0x1000 as an example) to transmit data to the AECU 30a (logical address is 0x100A as an example). The logical address is binary data or an object having a defined structure, but is described as binary data in this example.

At this time, if the data size is 8 bytes or less, a relay request frame configured as SF is transmitted.
On the other hand, when the data size is larger than 8 bytes, the relay request frame configured as FF, CF (Consecutive Frame) is transmitted a plurality of times. That is, a relay request frame configured as FF is first transmitted from the external device 20 to the gateway 10, and FC (Flow Control) is transmitted from the gateway 10 to the external device 20 as a response thereto. Thereafter, a relay request frame configured as a CF is transmitted from the external device 20 to the gateway 10, and an FC is returned from the gateway 10 to the external device 20. Thereafter, until the transmission is completed, the external device 20 and the gateway 10 Alternately transmit CF (relay request frame) and FC.

  When the gateway 10 receives the relay request frame, the gateway 10 searches the routing table 50 for the logical address of the relay destination AECU 30a by the relay processing described above (S405), and if the search fails, processing for address resolution is performed. I do.

  Specifically, the gateway 10 broadcasts an address resolution instruction frame to all connected in-vehicle networks 40 and waits for reception of an address resolution response frame from the relay destination AECU 30a (S410). Note that the above-described address resolution instruction frame 300 is broadcasted to the in-vehicle network 40 compliant with CAN.

  At this time, even if the ECU 30 other than the AECU 30a receives the address resolution instruction frame, it ignores the address resolution instruction frame because the destination logical address does not indicate its own logical address.

  When the gateway 10 receives the address resolution response frame 310 from the AECU 30a, the gateway 10 registers the logical address, identification information, and the like of the AECU 30a in the routing table 50 (cache table) (S415).

  Note that the gateway 10 may perform processing for address resolution after completion of reception of the relay request frame from the external device 20, or may be performed in parallel with reception of the relay request frame.

  After that, the gateway 10 completes reception of the relay request frame from the external device 20, and when registration of the AECU 30a is completed, the gateway 10 generates a relay frame corresponding to the AECU 30a from the received relay request frame, and sends the relay frame to the AECU 30a. Transmit (S420). When there are a plurality of relay frames, similarly, the relay frames configured as FF and CF are transmitted a plurality of times.

  Thereafter, it is assumed that the AECU 30a transmits a relay request frame as a response using the external device 20 as a relay destination (S425). When the reception of these relay request frames is completed, the gateway 10 generates a relay frame corresponding to the external device 20 from the relay request frame received with reference to the routing table 50, and transmits the relay frame to the external device 20. (S430).

When there are a plurality of relay request frames and relay frames, similarly, relay request frames configured as FF and CF are transmitted a plurality of times.
Also, when relaying communication between the ECUs 30 and the like connected to each in-vehicle network 40 compliant with a communication protocol other than CAN at the application level, the gateway 10 similarly performs address resolution.

<Specific example 2>
Next, when sequential relaying is performed (when relaying is performed at the network level), for example, processing for performing address resolution of the ECU 30 or the like connected to the in-vehicle network 40 compliant with CAN will be described.

  In the address resolution instruction frame 320 in such a case, an ID indicating broadcast transmission is set as the CAN-ID 321. The data field includes N_PCI 322 (4 bits) in which data indicating an address resolution instruction (for example, 1111b) is set, a transmission destination logical address 323, a transmission source logical address 324, and an option 325 (see FIG. 10). .

  In the address resolution response frame 330, an ID that can be received by the gateway 10 is set as the CAN-ID 331. The data field includes N_PCI 332 (4 bits) in which data indicating an address resolution response (for example, 1110b) is set, a request CAN-ID 333, a response CAN-ID 334, and an option 335.

  N_PCI 322 and 332 indicate the type of frame such as SF and FF. When network level relay is performed, an address resolution instruction and an address resolution response are provided as one of the types.

  Note that the transmission destination logical address 323, the transmission source logical address 324, the request CAN-ID 333, the response CAN-ID 334, and the options 325 and 335 are the same components as when relaying is performed at the application level.

  Next, a specific example of address resolution when the gateway 10 relays communication between the external device 20 connected to each in-vehicle network 40 compliant with CAN and the ACECU 30a at the network level is a flowchart shown in FIG. Will be described.

In S500, the external apparatus 20 transmits a relay request frame configured as FF to the gateway 10 in order to transmit data exceeding 8 bytes to the AECU 30a.
When the gateway 10 receives the relay request frame, the gateway 10 searches the routing table 50 for the logical address of the relay destination AECU 30 by the relay processing described above (S505), and if the search fails, performs processing for address resolution. Do.

  Specifically, the gateway 10 broadcasts an address resolution instruction frame to all the in-vehicle networks 40 and waits for reception of an address resolution response frame 330 from the relay destination AECU 30a (S510). Note that the above-described address resolution instruction frame 320 is broadcasted to the in-vehicle network 40 compliant with CAN.

  At this time, even if the ECU 30 other than the AECU 30a receives the address resolution instruction frame, it ignores the address resolution instruction frame because the destination logical address does not indicate its own logical address.

  When the gateway 10 receives the address resolution response frame 330 from the AECU 30a, the gateway 10 registers the logical address, identification information, and the like of the AECU 30a in the routing table 50 (S515).

  In subsequent S520, the gateway 10 generates a relay frame (FF) corresponding to the AECU 30a from the received relay request frame, and transmits the relay frame to the AECU 30a. When the gateway 10 receives the FC from the AECU 30a as a response to the relay frame, the gateway 10 generates an FC (relay frame) corresponding to the external device 20 that is the relay source, and transmits the FC to the external device 20.

  Further, the external device 20 that has received the FC transmits a relay request frame configured as a CF to the gateway 10. When the gateway 10 receives the relay request frame, the gateway 10 generates a relay frame (CF) corresponding to the AECU 30a from the relay request frame, and transmits the relay frame to the AECU 30a.

  Thereafter, the gateway 10 alternately relays the FC from the AECU 30a and the relay request frame (CF) from the external device 20 until the data transmission by the external device 20 is completed.

  Then, it is assumed that the AECU 30a starts transmitting response data exceeding 8 bytes to the external device 20 after the reception of the relay frame is completed (S525). The AECU 30a first transmits a relay request frame configured as FF to the gateway 10 with the AECU 30a as a relay destination.

  When the gateway 10 receives the relay request frame, the gateway 10 generates a relay frame (FF) corresponding to the external device 20 from the relay request frame, and transmits the relay frame to the external device 20. When the gateway 10 receives an FC from the external device 20 as a response to the relay frame, the gateway 10 generates an FC (relay frame) corresponding to the relay source AECU 30a, and transmits the FC to the AECU 30a.

  On the other hand, the AECU 30 a that has received the FC transmits a relay request frame configured as a CF to the gateway 10. When the gateway 10 receives the relay request frame, the gateway 10 generates a relay frame (CF) corresponding to the external device 20 from the relay request frame and transmits the relay frame (CF) to the external device 20.

  Thereafter, the gateway 10 alternately relays the FC from the external device 20 and the relay request frame (CF) from the AECU 30a until the transmission by the AECU 30a is completed.

  When the external device 20 or the AECU 30a transmits data of 8 bytes or less, the external device 20 or the like transmits one relay request frame configured as SF. In the same way, relaying is performed after address resolution is performed as necessary.

  Also, when relaying communication between the ECUs 30 and the like connected to each in-vehicle network 40 compliant with a communication protocol other than CAN at the network level, the gateway 10 similarly performs address resolution.

<Specific example 3>
Next, address resolution when relaying is performed between the ECU 30 and the like connected to the in-vehicle network 40 conforming to different communication protocols will be described. In such a case, it is generally considered to perform application level relay (of course, network level relay may be performed).

  In such a case, when the relay destination in-vehicle network 40 conforms to CAN, the address resolution instruction frame 300 and the address resolution response frame 310 illustrated in FIG. 8 are used.

  Further, when the relay destination in-vehicle network 40 conforms to LIN, the following address resolution instruction frame 340 and address resolution response frame 350 are used (FIG. 12).

  That is, in the address resolution instruction frame 340, an ID (for example, 0x3C) indicating an address resolution instruction is set in the ID field 341. The data field includes a node address 342, a PCI (Protocol Control Information) 343, an SID 344, a transmission destination logical address 345, a transmission source logical address 346, and an option 347.

  The node address 342 is set to broadcast (for example, 0x7E), the PCI 343 indicates the type of frame such as SF, FF, and the like, and the SID 344 indicates the content of the instruction by the address resolution instruction frame 340. Further, the transmission destination logical address 345 indicates the logical address of the relay destination ECU 30 and the like, the transmission source logical address 346 indicates the logical address of the relay source ECU 30 and the like, and the option 347 displays various information related to address resolution. Show.

  In the address resolution response frame 350, 0x3D which is an ID indicating an address resolution response is set in the ID field 351. The data field includes a node address 352, a PCI 353, an RSID 354, a relay destination node address 355, and an option 356.

  The node address 352 is set with an ID (for example, 0x70) indicating the gateway 10, the RSID 354 indicates the response content by the address resolution response frame 350, and the relay destination node address 355 is the node address of the relay destination ECU 30 or the like. Indicates.

  Further, when the relay destination in-vehicle network 40 is compliant with FlexRay, the following address resolution instruction frame 360 and address resolution response frame 370 are used (see FIG. 13).

  That is, in the address resolution instruction frame 360, 0x100 which is an ID indicating an address resolution instruction is set in the frame ID 361. The data field includes a TA (Target Address) 362, an SA (Source Address) 363, a PCI 364, a transmission destination logical address 365, a transmission source logical address 366, and the like.

  The TA 362 is set with an ID indicating broadcast, the SA 363 is set with an ID that the gateway 10 can receive, and the PCI 364 indicates a frame type such as SF (Start Frame) or CF. The transmission destination logical address 365 indicates a logical address of the relay destination ECU 30 and the like, and the transmission source logical address 366 indicates a logical address of the relay source ECU 30 and the like.

  Also, in the address resolution response frame 370, 0x101 which is an ID indicating an address resolution response is set in the frame ID 371, and the data field is composed of TA372, SA373, PCI374 and the like.

  The TA 372 is set with an ID that can be received by the gateway 10, and the SA 373 is set with the physical address of the transmission source of the address resolution response frame 370 (in other words, the physical address of the relay destination ECU 30 or the like).

  Next, a specific example of address resolution when relaying is performed between the external device 20 connected to each in-vehicle network 40 conforming to a different communication protocol and the ACECU 30a will be described with reference to the flowchart shown in FIG. .

  In S600, the external device 20 transmits a relay request frame to the gateway 10 to transmit data to the AECU 30a. At this time, the relay request frame is transmitted once or a plurality of times according to the data size.

  On the other hand, when the gateway 10 receives the relay request frame, the gateway 10 searches the routing table 50 for the logical address of the relay destination AECU 30a by the relay processing described above (S605). I do.

  Specifically, the gateway 10 broadcasts an address resolution instruction frame to all connected in-vehicle networks 40 and waits for reception of an address resolution response frame from the relay destination AECU 30a (S610).

  The above-described address resolution instruction frames 300, 340, and 360 are broadcasted to the in-vehicle network 40 that conforms to CAN, LIN, and FlexRay, respectively.

  At this time, even if the ECU 30 other than the AECU 30a receives the address resolution instruction frame, it ignores the address resolution instruction frame because the destination logical address does not indicate its own logical address.

  When the gateway 10 receives the address resolution response frame from the AECU 30a, the gateway 10 registers the logical address, identification information, and the like of the AECU 30a in the routing table 50 (S615).

  Further, the gateway 10 completes reception of the relay request frame from the external device 20, and when registration of the AECU 30a is completed, the gateway 10 generates a relay frame corresponding to the AECU 30a from the received relay request frame, and sends the relay frame to the AECU 30a. Transmit (S620). At this time, the relay frame is transmitted once or a plurality of times according to the data size to be relayed, the communication protocol of the in-vehicle network 40 as the relay destination, and the like.

  Thereafter, it is assumed that the AECU 30a transmits a relay request frame as a response using the external device 20 as a relay destination (S625). When the reception of these relay request frames is completed, the gateway 10 generates a relay frame corresponding to the external device 20 from the received relay request frame, and transmits the relay frame to the external device 20 (S630).

<Others>
In specific examples 1 to 3, relaying and address resolution in the case where communication between the external device 20 connected to the different in-vehicle network 40 and the ECU 30 is performed according to the flowcharts have been described.

  However, the same applies to the case where communication between the ECUs 30 connected to different in-vehicle networks 40 is performed, or the case where communication is performed between the external device 20 that communicates with the gateway 10 via wireless communication or the like and the ECU. Relay and address resolution.

Further, relaying and address resolution are performed between the external device 20 and the ECU 30 connected to the same in-vehicle network 40 and between the ECUs 30 in the same manner as in the second specific example.
[Other Embodiments]
(1) Although it is assumed that Ethernet is used as the communication protocol of the in-vehicle network 40, in such a case, a frame or procedure compliant with ARP (Address Resolution Protocol) for performing address resolution in a network constituted by a PC or the like. Address resolution may be performed by By doing so, it is possible to divert existing resources, and it is possible to improve reliability while suppressing development costs.

  However, since ARP assumes address resolution of a PC or the like, the frame configuration and procedure used are more complicated than address resolution of this embodiment. For this reason, when an in-vehicle communication protocol such as CAN or LIN is mainly used as the communication protocol of the in-vehicle network 40, address resolution is performed by a simple configuration frame or procedure as in this embodiment. It is considered preferable to do so.

  (2) Conventionally, in a gateway, a relay buffer is secured in advance for each of a plurality of in-vehicle networks connected to the gateway. When relaying, a relay buffer corresponding to the in-vehicle network as a relay destination is used. It has become the composition which uses. For this reason, as the number of in-vehicle networks increases, the size of the relay buffer to be secured in advance increases, and there is a problem that the capacity of the RAM is depleted.

  Therefore, in the gateway 10 of the present embodiment, when a relay area common to each in-vehicle network 40 is provided and relaying is performed, a relay having a size corresponding to the communication protocol of the relay-mounted in-vehicle network 40 is performed from the relay area. A configuration may be adopted in which the buffer for use is dynamically secured. By doing so, the RAM capacity required for relaying can be saved.

  (3) The gateway 10 of the present embodiment is configured to be communicable with the external device 20, but may be configured to relay communication between the ECUs 30 without communicating with the external device 20. Even if it has such a structure, the same effect can be acquired.

[Correspondence with Claims]
The correspondence between the terms used in the description of the above embodiment and the terms used in the description of the claims is shown.

  The gateway 10 corresponds to an in-vehicle relay device, the ECU 30 corresponds to an in-vehicle device, the communication processing unit 15, the telematics communication unit 16, and the communication unit 17 of the gateway 10 correspond to communication means, and the RAM 12 and ROM 13 correspond to storage means.

The routing table 50 corresponds to correspondence information, the relay request frame 60 corresponds to relay request data, and the relay frame corresponds to relay data.
Address resolution instruction frames 300, 320, 340, and 360 correspond to instruction data, and address resolution response frames 310, 330, 350, and 370 correspond to response data.

  Also, S105 of the relay process corresponds to the specifying unit, S115 corresponds to the instruction unit, S125 corresponds to the registration unit, S130 corresponds to the generation unit, and S135 corresponds to the transmission unit.

  DESCRIPTION OF SYMBOLS 10 ... Gateway, 11 ... CPU, 12 ... RAM, 13 ... ROM, 14 ... Internal bus, 15 ... Communication processing part, 16 ... Communication part for telematics, 17 ... Communication part, 20 ... External device, 30 ... ECU, 40 ... In-vehicle network, 50 ... Routing table, 60 ... Relay request frame, 61 ... Protocol dependent unit, 62 ... Source address, 63 ... Target address, 64 ... Message, 300 ... Address resolution instruction frame, 310 ... Address resolution response frame, 320 ... Address resolution instruction frame, 330... Address resolution response frame, 340... Address resolution instruction frame, 350... Address resolution response frame, 360... Address resolution instruction frame, 370.

Claims (3)

Communication means for communicating with each in-vehicle device (30) constituting a plurality of in-vehicle networks (40) provided in the own vehicle or an external device (20) temporarily connected to the own device (15-17) ),
Storage means (12, 13) for storing correspondence information (50) in which a logical address indicating the on-vehicle device and identification information on the on-vehicle device indicated by the logical address are registered in association with each other;
When the relay request data (60) including the logical address is received from the in-vehicle device or the external device via the communication unit, the in-vehicle device related to the in-vehicle device indicated by the logical address registered in the correspondence information A specifying means (S105) for specifying identification information;
When the identification unit fails to identify the identification information, it instructs the in-vehicle device related to the identification information to transmit response data (310, 330, 350, 370) including the identification information to the own device. Instruction means (S115) for broadcasting instruction data (300, 320, 340, 360) to the plurality of in-vehicle devices via the communication means;
When the response data is received via the communication means, the identification information included in the response data and the logical address indicating the in-vehicle device related to the identification information are registered in association with the correspondence information. Registration means to perform (S125);
When the specifying means succeeds in specifying the identification information, the relay data corresponding to the in-vehicle device based on the identification information and the relay request data including the logical address indicating the in-vehicle device related to the identification information And when the identification unit fails to identify the identification information, the identification information included in the response data received according to the instruction data transmitted due to the failure, and the in-vehicle related to the identification information Generating means (S130) for generating the relay data corresponding to the in-vehicle device based on the relay request data including the logical address indicating the device;
Transmitting means (S135) for transmitting the relay data generated by the generating means to the in-vehicle device corresponding to the relay data via the communication means;
A vehicle-mounted relay device (10) comprising: The in-vehicle relay device according to claim 1,
The relay request data is data transmitted from any of the in-vehicle devices to the other in-vehicle device,
An in-vehicle relay device. In the in-vehicle relay device according to claim 1 or 2,
The relay request data is data transmitted from the external device to diagnose a failure of the in-vehicle device,
An in-vehicle relay device.

Images