In-vehicle apparatus, in-vehicle system, communication method, and communication program

Abstract

To make it possible to relay communication between an external device connected to an in-vehicle network via a USB interface and another device in the in-vehicle network using a simple configuration.SOLUTION: An in-vehicle apparatus includes a connection port to which an external device can be connected, a detection unit that detects connection of a USB device to the connection port via a connector, an acquisition unit that acquires device information about the USB device and connector information about the connector, a plurality of relay units, a startup unit that starts the relay units, and a storage unit that stores correspondence information that indicates the correspondence between each of the plurality of relay units and the device information and the connector information. The startup unit determines which of the relay units to start based on the correspondence information, the device information, and the connector information.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to an in-vehicle device, an in-vehicle system, a communication method, and a communication program. [Background technology]

[0002] With the spread of car sharing and the demand for improved processing capabilities of in-vehicle devices installed in vehicles, there has been a demand for customizing in-vehicle networks by connecting external devices to the in-vehicle devices.

[0003] For example, Patent Document 1 (WO 2020 / 179123) discloses the following management device: That is, the management device includes a detection unit that detects the addition of a functional unit to a network that includes one or more in-vehicle functional units, an acquisition unit that acquires functional unit information including information on the new functional unit that is the functional unit whose addition is detected by the detection unit and on the network configuration of the in-vehicle functional unit at a layer lower than the application layer, and a generation unit that generates configuration information of the new network that is the network that further includes the new functional unit, based on the functional unit information acquired by the acquisition unit. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Publication No. 2020 / 179123 Summary of the Invention [Problem to be solved by the invention]

[0005] There is a demand for a technology that goes beyond the technology described in Patent Document 1 and that is capable of relaying communication between an external device connected to an in-vehicle network via a USB (Universal Serial Bus) interface and other devices in the in-vehicle network with a simple configuration.

[0006] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide an in-vehicle device, an in-vehicle system, a communication method, and a communication program that are capable of relaying communication between an external device connected to an in-vehicle network via a USB interface and other devices in the in-vehicle network with a simple configuration. [Means for solving the problem]

[0007] The in-vehicle device of the present disclosure is an in-vehicle device in an in-vehicle network, and includes: a connection port to which an external device can be connected via a USB interface; a detection unit that detects connection of a USB device to the connection port via a connector; an acquisition unit that acquires device information about the USB device whose connection is detected by the detection unit and connector information about the connector; a plurality of relay units that perform relay processing to relay communications between the USB device and other devices in the in-vehicle network; a startup unit that starts one of the plurality of relay units that performs the relay processing between the USB device whose connection is detected by the detection unit and the other devices; and a memory unit that stores correspondence information indicating a correspondence between each of the plurality of relay units, the device information, and the connector information, and the relay unit terminates at least one of communication with the USB device and communication with the other devices during the relay processing, and the startup unit determines which of the relay units to start based on the correspondence information, and the device information and the connector information acquired by the acquisition unit.

[0008] One aspect of the present disclosure can be realized not only as an in-vehicle device including such a characteristic processing unit, but also as a semiconductor integrated circuit that realizes part or all of the in-vehicle device. [Effects of the Invention]

[0009] According to the present disclosure, it is possible to relay communication between an external device connected to an in-vehicle network via a USB interface and other devices in the in-vehicle network with a simple configuration. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of an in-vehicle system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a diagram illustrating a configuration of an in-vehicle ECU according to an embodiment of the present disclosure. [Figure 3] FIG. 3 is a diagram showing a list of USB device classes of USB devices according to an embodiment of the present disclosure. [Figure 4] FIG. 4 is a diagram illustrating an example of a correspondence table stored in a storage unit in an in-vehicle ECU according to an embodiment of the present disclosure. [Figure 5] FIG. 5 is a flowchart illustrating an example of an operation procedure when the vehicle-mounted ECU according to the embodiment of the present disclosure starts relay processing. [Figure 6] FIG. 6 is a flowchart defining an example of an operation procedure when the in-vehicle ECU according to the embodiment of the present disclosure starts up the termination unit. [Figure 7] FIG. 7 is a diagram illustrating an example of a communication sequence in the in-vehicle system according to the embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0011] First, the contents of the embodiments of the present disclosure will be listed and described. (1) An in-vehicle device according to an embodiment of the present disclosure is an in-vehicle device in an in-vehicle network, comprising: a connection port to which an external device can be connected via a USB interface; a detection unit that detects connection of a USB device to the connection port via a connector; an acquisition unit that acquires device information about the USB device whose connection is detected by the detection unit and connector information about the connector; a plurality of relay units that perform relay processing to relay communications between the USB device and other devices in the in-vehicle network; a startup unit that starts one of the plurality of relay units that performs the relay processing between the USB device whose connection is detected by the detection unit and the other devices; and a memory unit that stores correspondence information indicating a correspondence between each of the plurality of relay units, the device information, and the connector information, wherein the relay unit terminates at least one of communication with the USB device and communication with the other devices during the relay processing, and the startup unit determines which of the relay units to start based on the correspondence information, and the device information and the connector information acquired by the acquisition unit.

[0012] With this configuration, the relay unit can be activated based on correspondence information stored in advance in the storage unit to perform relay processing between the USB device and other devices. Therefore, when a USB device is connected to a connection port via a connector, communication between the USB device and other devices can be initiated without requiring user operation. Furthermore, for example, when an in-vehicle device has multiple connection ports and multiple USB devices, for example, of the same model number, are connected to the multiple connection ports, the relay unit can be activated in association with the USB device depending on the connector used for the connection. Furthermore, compared to a configuration that uses correspondence information linking the activated relay unit with the port number of the connection port, the relay unit can be activated in association with the USB device without imposing restrictions on the connection port to which the USB device is connected when connecting the USB device to the in-vehicle device. Therefore, communication between an external device connected to the in-vehicle network via a USB interface and other devices on the in-vehicle network can be relayed with a simple configuration.

[0013] (2) In the above (1), the storage unit may store, as the correspondence information, a correspondence table including a composite primary key made up of items of the device information and items of the connector information.

[0014] With this configuration, it is possible to uniquely determine the relay unit to be activated based on both the device information and the connector information.

[0015] (3) An in-vehicle system according to an embodiment of the present disclosure is an in-vehicle system in an in-vehicle network, comprising an in-vehicle device and a connector, wherein the in-vehicle device comprises a connection port to which an external device can be connected via a USB interface, and a plurality of relay units that perform relay processing to relay communications between the USB device and other devices in the in-vehicle network, the connector stores connector information related to the connector, the in-vehicle device acquires the connector information from the connector connected to the connection port, and acquires device information related to the USB device connected to the connection port via the connector, the in-vehicle device further comprises a memory unit that stores correspondence information indicating a correspondence between each of the plurality of relay units, the device information, and the connector information, and the in-vehicle device determines which of the plurality of relay units to activate based on the correspondence information, the acquired device information, and the connector information.

[0016] With this configuration, the relay unit can be activated based on correspondence information stored in advance in the storage unit to perform relay processing between the USB device and other devices. Therefore, when a USB device is connected to a connection port via a connector, communication between the USB device and other devices can be initiated without requiring user operation. Furthermore, for example, when an in-vehicle device has multiple connection ports and multiple USB devices, for example, of the same model number, are connected to the multiple connection ports, the relay unit can be activated in association with the USB device depending on the connector used for the connection. Furthermore, compared to a configuration that uses correspondence information linking the activated relay unit with the port number of the connection port, the relay unit can be activated in association with the USB device without imposing restrictions on the connection port to which the USB device is connected when connecting the USB device to the in-vehicle device. Therefore, communication between an external device connected to the in-vehicle network via a USB interface and other devices on the in-vehicle network can be relayed with a simple configuration.

[0017] (4) In (3) above, the vehicle-mounted device may have a first connection port and a second connection port, which are the connection ports, and the first connector, which is the connector connected to the first connection port, may store first connector information, which is the connector information, and the second connector, which is the connector connected to the second connection port, may store second connector information, which is the connector information different from the first connector information, and the vehicle-mounted device may acquire the first connector information from the first connector and the second connector information from the second connector.

[0018] With this configuration, when multiple USB devices of the same model number are connected to the first connection port and the second connection port, the relay unit can be activated in association with the USB device depending on the connector.

[0019] (5) A communication method according to an embodiment of the present disclosure is a communication method in an in-vehicle device in an in-vehicle network, the in-vehicle device having a connection port to which an external device can be connected via a USB interface and a plurality of relay units that perform relay processing to relay communications between the USB device and other devices in the in-vehicle network, the relay units performing at least one of terminating communications with the USB device and terminating communications with the other devices in the relay processing, the communication method including the steps of detecting connection of a USB device to the connection port via a connector, acquiring device information about the USB device whose connection has been detected and connector information about the connector, and activating one of the relay units that performs the relay processing between the USB device whose connection has been detected and the other devices, the in-vehicle device further having a memory unit that stores correspondence information indicating a correspondence between each of the plurality of relay units, the device information, and the connector information, and in the step of activating the relay unit, the relay unit to be activated is determined based on the correspondence information, and the acquired device information and connector information.

[0020] This method activates the relay unit based on correspondence information stored in advance in the storage unit and performs relay processing between the USB device and other devices. Therefore, when a USB device is connected to a connection port via a connector, communication between the USB device and other devices can be initiated without requiring user operation. Furthermore, for example, when an in-vehicle device has multiple connection ports and multiple USB devices, for example, of the same model number, are connected to the multiple connection ports, the relay unit can be activated in association with the USB device depending on the connector used for the connection. Furthermore, compared to a method using correspondence information that associates the activated relay unit with the port number of the connection port, the relay unit can be activated in association with the USB device without imposing restrictions on the connection port to which the USB device is connected when connecting the USB device to the in-vehicle device. Therefore, communication between an external device connected to the in-vehicle network via a USB interface and other devices on the in-vehicle network can be relayed with a simple configuration.

[0021] (6) A communication program according to an embodiment of the present disclosure is a communication program used in an in-vehicle device in an in-vehicle network, the in-vehicle device having a connection port to which an external device can be connected via a USB interface, the in-vehicle device including a computer, a detection unit that detects connection of a USB device to the connection port via a connector, an acquisition unit that acquires device information about the USB device whose connection is detected by the detection unit and connector information about the connector, a plurality of relay units that perform relay processing to relay communication between the USB device and other devices in the in-vehicle network, and a relay unit that relays communication between the USB device and other devices in the in-vehicle network and the USB device and the other devices in the in-vehicle network. The in-vehicle device further includes a storage unit that stores correspondence information indicating the correspondence between each of the plurality of relay units, the device information, and the connector information, and the relay unit terminates at least one of communication with the USB device and communication with the other device during the relay processing, and the startup unit determines which relay unit to start based on the correspondence information, the device information, and the connector information acquired by the acquisition unit.

[0022] With this configuration, the relay unit can be activated based on correspondence information stored in advance in the storage unit to perform relay processing between the USB device and other devices. Therefore, when a USB device is connected to a connection port via a connector, communication between the USB device and other devices can be initiated without requiring user operation. Furthermore, for example, when an in-vehicle device has multiple connection ports and multiple USB devices, for example, of the same model number, are connected to the multiple connection ports, the relay unit can be activated in association with the USB device depending on the connector used for the connection. Furthermore, compared to a configuration that uses correspondence information linking the activated relay unit with the port number of the connection port, the relay unit can be activated in association with the USB device without imposing restrictions on the connection port to which the USB device is connected when connecting the USB device to the in-vehicle device. Therefore, communication between an external device connected to the in-vehicle network via a USB interface and other devices on the in-vehicle network can be relayed with a simple configuration.

[0023] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, identical or corresponding parts are designated by the same reference numerals, and their description will not be repeated. Furthermore, at least some of the embodiments described below may be combined in any manner.

[0024] [Configuration and basic operation] Fig. 1 is a diagram illustrating an example of the configuration of an in-vehicle system according to an embodiment of the present disclosure. Referring to Fig. 1, the in-vehicle system 301 includes an in-vehicle ECU (Electronic Control Unit) 101, in-vehicle ECUs 111A and 111B that are in-vehicle ECUs 111, and a USB connector 131. The USB connector 131 is an example of a connector. The in-vehicle system 301 is mounted on a vehicle 1. The in-vehicle ECUs 101 and 111 configure an in-vehicle network 201. Note that the in-vehicle system 301 may be configured to include one or three or more in-vehicle ECUs 111, or may be configured to include multiple USB connectors 131.

[0025] The in-vehicle ECU 111 is, for example, a relay device, a TCU (Telematics Communication Unit), an automatic driving ECU, an engine ECU, a sensor, a navigation device, a human-machine interface, a camera, and the like.

[0026] The in-vehicle ECU 101 includes communication ports P1A and P1B and USB (registered trademark) ports P2A, P2B, and P2C. Hereinafter, each of the communication ports P1A and P1B will also be referred to as a communication port P1, and each of the USB ports P2A, P2B, and P2C will also be referred to as a USB port P2. The USB port P2 is an example of a connection port. The in-vehicle ECU 101 may be configured to include one or three or more communication ports P1. The in-vehicle ECU 101 may also be configured to include two or four or more USB ports P2.

[0027] The communication port P1 is a connector that can connect, for example, an Ethernet (registered trademark) cable 2. The USB port P2 can connect external devices such as a USB connector 131 and a USB device 121 via a USB interface. In other words, the USB port P2 is a connector that can connect a USB connector.

[0028] The in-vehicle ECUs 111A and 111B are connected to communication ports P1A and P1B of the in-vehicle ECU 101, respectively, via an Ethernet cable 2. Note that the in-vehicle ECU 111 is not limited to being connected to the in-vehicle ECU 101 via the Ethernet cable 2, and may be connected via a communication line conforming to other standards such as CAN (Controller Area Network) (registered trademark) and FlexRay (registered trademark).

[0029] [assignment] There is a demand for a technology that can relay communication between a USB device 121 connected to an in-vehicle network 201 via a USB interface and other devices in the in-vehicle network 201 with a simple configuration.

[0030] For example, when a USB device is connected to a USB port of a personal computer, the personal computer starts an application selected by the user, and the application communicates directly with the USB device to exchange communication data.

[0031] On the other hand, in the in-vehicle system 301, when the USB device 121 is connected to the USB port P2 of the in-vehicle ECU 101, it is conceivable that the USB device 121 and the in-vehicle ECU 111 exchange communication data Dt via the in-vehicle ECU 101. However, while the USB device 121 communicates in accordance with the USB standard, the in-vehicle ECU 111 communicates in accordance with a standard different from USB. Therefore, in the in-vehicle system 301, a relay application that performs relay processing between the USB device 121 and the in-vehicle ECU 111 is installed in the in-vehicle ECU 101.

[0032] For example, the in-vehicle ECU 101 is equipped with a plurality of relay applications corresponding to the respective types of USB devices 121 that can be connected to the in-vehicle ECU 101. For example, when the USB device 121 is retrofitted to the USB port P2 of the in-vehicle ECU 101 after the vehicle 1 is shipped, a technique is desired that can automatically select and start an application corresponding to the USB device 121 from the plurality of relay applications and start communication between the USB device 121 and the in-vehicle ECU 111 without requiring user operation.

[0033] Therefore, the in-vehicle system 301 according to the embodiment of the present disclosure solves the above problem by the following configuration.

[0034] (In-vehicle ECU) FIG. 2 is a diagram illustrating a configuration of an in-vehicle ECU according to an embodiment of the present disclosure. Referring to FIG. 2, the in-vehicle ECU 101 includes a USB communication unit 11, an ECU communication unit 12, a proxy unit 13, a startup unit 15, and a storage unit 16. The proxy unit 13 includes a plurality of termination units 14. The USB communication unit 11 is an example of a detection unit and an acquisition unit. The termination unit 14 is an example of a relay unit. Some or all of the USB communication unit 11, the ECU communication unit 12, the proxy unit 13, and the startup unit 15 are realized by, for example, a processing circuit including one or more processors. The storage unit 16 is, for example, a non-volatile memory included in the processing circuit.

[0035] 2, USB connectors 131A and 131B, which are USB connectors 131, are connected to USB ports P2A and P2C, respectively. Furthermore, USB devices 121A and 121B, which are USB devices 121, are connected to USB connectors 131A and 131B, respectively. USB port P2A is an example of a first connection port, and USB port P2C is an example of a second connection port. USB connector 131A is an example of a first connector, and USB connector 131B is an example of a second connector.

[0036] For example, after the vehicle 1 is shipped, the USB connector 131 is connected to the USB port P2 by the user of the vehicle 1 with the USB device 121 connected thereto. Note that the USB connector 131 may be connected to the USB port P2 in advance before the vehicle 1 is shipped, and the USB device 121 may be connected to the USB connector 131 by the user after the vehicle 1 is shipped.

[0037] For example, the USB devices 121A and 121B are video cameras. The USB device 121 and the in-vehicle ECU 111 transmit communication data Dt via the USB connector 131 and the in-vehicle ECU 101.

[0038] The USB connector 131 stores connector information related to the USB connector 131. For example, the USB connector 131 stores, as connector information, iProduct, which is a character string written in memory by the manufacturer of the USB connector 131. Note that the USB connector 131 may be configured to store, instead of iProduct, as connector information, idVender, which is a number indicating the manufacturer of the USB connector 131, idProduct, which is a number assigned to each product of the USB connector 131 by the manufacturer, iManufacturer, which is a character string written in memory by the manufacturer, or iSerialNumber, which is a character string written in memory by the manufacturer.

[0039] The USB connectors 131A and 131B store different connector information. More specifically, for example, the iProducts of the USB connectors 131A and 131B are "AAA" and "BBB," respectively. The iProduct of the USB connector 131A is an example of first connector information. The iProduct of the USB connector 131B is an example of second connector information.

[0040] 3 is a diagram showing a list of USB device classes for USB devices according to an embodiment of the present disclosure, illustrating the correspondence between the class names of the USB device classes and the USB devices 121 that correspond to the USB device classes.

[0041] Referring to FIG. 3, USB devices 121 are classified into one or more USB device classes with similar functions according to the standard established by the USB-IF (Implementers Forum). USB devices 121A and 121B, which are video cameras, are classified into a USB device class with the class name "Video." Another USB device 121, which is a microphone, is classified into a USB device class with the class name "Audio." Furthermore, a USB device 121, which is a keyboard, is classified into a USB device class with the class name "HID (Human Interface Device)." USB devices 121 belonging to the same USB device class communicate with other devices according to a common interface specification, i.e., by using a common interface.

[0042] The USB device 121 stores device information related to the USB device 121. For example, the USB device 121 stores, as device information, a class number that indicates the USB device class to which the USB device 121 belongs, an idVender that indicates the manufacturer of the USB device 121, and an idProduct that is a number assigned to each product of the USB device 121 by the manufacturer.

[0043] Referring back to FIG. 2, the termination unit 14 in the proxy unit 13 performs a relay process for relaying communication between the USB device 121 and the in-vehicle ECU 111 .

[0044] As an example, the types of the multiple termination units 14 in the proxy unit 13 differ for each USB device class. That is, the proxy unit 13 includes the same number of types of termination units 14 as the number of USB device classes of the USB devices 121 that can be connected to the USB port P2. A termination unit 14 of a type corresponding to a certain USB device class can communicate with a USB device 121 that belongs to that USB device class.

[0045] For example, the proxy unit 13 includes multiple termination units 14 of the same type. More specifically, the termination units 14 have the same application ID for each type. The proxy unit 13 includes multiple termination units 14 with the same application ID.

[0046] (Connection detection) The USB communication unit 11 detects connection of the USB device 121 to the USB port P2 via the USB connector 131. More specifically, when the USB device 121 is connected to the USB port P2 via the USB connector 131, the USB communication unit 11 transmits a connection notification to the in-vehicle ECU 101 via the USB connector 131. When the USB communication unit 11 receives a connection notification from the USB device 121 via the USB connector 131 and the USB port P2, the USB communication unit 11 recognizes that the USB device 121 has been connected to the USB port P2 via the USB connector 131.

[0047] The USB communication unit 11 acquires device information about the USB device 121 whose connection to the USB port P2 has been detected, and connector information about the USB connector 131. That is, the USB communication unit 11 acquires the device information from the USB device 121, and the connector information from the USB connector 131. For example, the USB communication unit 11 acquires multiple types of device information about one USB device 121.

[0048] More specifically, when the USB communication unit 11 recognizes that the USB device 121 is connected to the USB port P2 via the USB connector 131, it transmits a device information request to the USB device 121 via the USB port P2 and the USB connector 131. The USB communication unit 11 also transmits a connector information request to the USB connector 131 via the USB port P2.

[0049] When the USB device 121 receives a device information request from the vehicle-mounted ECU 101, the USB device 121 transmits a device information response including the class number, idVender, and idProduct of the USB device 121 to the vehicle-mounted ECU 101 via the USB connector 131 as a response to the device information request.

[0050] When the USB connector 131 receives a connector information request from the in-vehicle ECU 101, the USB connector 131 transmits a connector information response including the iProduct of the USB connector 131 to the in-vehicle ECU 101 as a response to the connector information request.

[0051] When the USB communication unit 11 receives a device information response from the USB device 121 via the USB port P2 and the USB connector 131, it acquires the class number, idVender, and idProduct from the received device information response. Furthermore, when the USB communication unit 11 receives a connector information response from the USB connector 131 via the USB port P2, it acquires and idProduct from the received connector information response. The USB communication unit 11 creates connection information Con indicating the acquired class number, idVender, idProduct, and iProduct, and outputs the created connection information Con to the startup unit 15.

[0052] (Starting the termination based on the correspondence table) The activation unit 15 activates one of the plurality of termination units 14 that performs relay processing between the USB device 121 whose connection is detected by the USB communication unit 11 and the in-vehicle ECU 111 .

[0053] 4 is a diagram illustrating an example of a correspondence table stored in a storage unit in an on-vehicle ECU according to an embodiment of the present disclosure. Referring to FIG. 4, storage unit 16 stores correspondence table T1 indicating a correspondence relationship between each of a plurality of termination units 14 and device information and connector information. Correspondence table T1 is an example of correspondence information.

[0054] For example, correspondence table T1 includes a composite primary key consisting of a device information item and a connected device information item. More specifically, correspondence table T1 is a table showing the correspondence between the composite primary key consisting of the class number, idVender, idProduct, and iProduct items and the application ID.

[0055] In correspondence table T1, some of the fields in the composite primary key have arbitrary values. More specifically, correspondence table T1 includes multiple records R1 in which the values of all the fields in the composite primary key are set to predetermined values, and multiple records R2 in which the idVender and idProduct fields are set to arbitrary values, i.e., NULL.

[0056] For example, the correspondence table T1 further indicates the correspondence between each of a plurality of termination units 14 of the same type and a service ID and an option ID, which are additional information that can identify the termination unit 14. More specifically, the correspondence table T1 is a table that further indicates the correspondence between an application ID and a service ID and an option ID. Specifically, the correspondence table T1 includes a record R1 in which the application ID is "AP001" and the service ID and option ID are "X001" and "Y001", respectively, and a record R1 in which the application ID is "AP001" and the service ID and option ID are "X002" and "Y002", respectively.

[0057] The activation unit 15 determines the termination unit 14 to be activated based on the correspondence table T1 in the storage unit 16 and the device information and connector information acquired by the USB communication unit 11. More specifically, the activation unit 15 receives the connection information Con from the USB communication unit 11 and refers to the correspondence table T1 in the storage unit 16.

[0058] The launching unit 15 searches the multiple records R1 in the correspondence table T1 for a record R1 that includes a composite primary key that matches the class number, idVender, idProduct, and iProduct indicated in the connection information Con received from the USB communication unit 11. If the search target record R1 exists, the launching unit 15 acquires the application ID included in the record R1. The launching unit 15 launches the termination unit 14 that has the acquired application ID. Specifically, for example, if the port number, class number, idVender, idProduct, and iProduct indicated by the connection information Con are "C002," "V001," "P004," and "EEE," respectively, the launching unit 15 launches the termination unit 14 that has the application ID "AP004."

[0059] For example, if there is no termination unit 14 in the correspondence table T1 that corresponds to all types of device information and connector information, the startup unit 15 determines the termination unit 14 to start based on some types of device information and connector information.

[0060] More specifically, if the search target record R1 does not exist, the launching unit 15 searches for a record R2 including a composite primary key that matches the class number and iProduct indicated by the connection information Con received from the USB communication unit 11 from among the multiple records R2 in the correspondence table T1. If the search target record R2 exists, the launching unit 15 obtains the application ID included in the record R2. The launching unit 15 launches the termination unit 14 having the obtained application ID. Specifically, for example, if the class number, idVender, idProduct, and iProduct indicated by the connection information Con are "C001," "V051," "P051," and "GGG," respectively, the launching unit 15 launches the termination unit 14 having the application ID "AP011."

[0061] When starting up the termination unit 14, the starting unit 15 obtains, from the correspondence table T1, a service ID and an option ID corresponding to the application ID of the termination unit 14. Furthermore, when starting up the termination unit 14, the starting unit 15 outputs the connection information Con received from the USB communication unit 11 to the started up termination unit 14.

[0062] The termination unit 14 receives the connection information Con from the activation unit 15 and holds the received connection information Con.

[0063] (Example of starting the terminal) For example, the class number of the USB devices 121A and 121B is "C001," the idVender of the USB devices 121A and 121B is "V001," and the idProduct of the USB devices 121A and 121B is "P001." Also, as described above, the iProduct of the USB connectors 131A and 131B are "AAA" and "BBB," respectively.

[0064] In this case, the startup unit 15 receives connection information Con from the USB communication unit 11 in response to the connection of the USB device 121A to the USB port P2A via the USB connector 131A, and starts up the terminal unit 14A, which is the terminal unit 14 having the application ID "AP001", based on the received connection information Con and the correspondence table T1.

[0065] In addition, when USB device 121B is connected to USB port P2C via USB connector 131B, startup unit 15 receives connection information Con from USB communication unit 11, and starts up termination unit 14B, which is termination unit 14 having the application ID "AP001", based on the received connection information Con and correspondence table T1.

[0066] When the activation unit 15 activates the termination unit 14, the activation unit 15 provides the in-vehicle ECU 111 with a service using the USB device 121 by using an OfferService message conforming to SOME / IP (Scalable service-oriented middleware over IP).

[0067] More specifically, when activating the termination unit 14A, the activation unit 15 acquires, from the correspondence table T1, a service ID "X001" corresponding to the application ID of the termination unit 14A and an option ID "Y001" corresponding to the application ID of the termination unit 14A. The activation unit 15 generates an OfferService message M1A including the acquired service ID and option ID, and transmits the generated OfferService message M1A to the in-vehicle ECU 111 via the ECU communication unit 12 and the communication port P1.

[0068] The in-vehicle ECU 111 receives the OfferService message M1A from the in-vehicle ECU 101 and acquires a service ID from the received OfferService message M1A. For example, in order to receive the service indicated by the acquired service ID, the in-vehicle ECU 111A transmits a FindService message M2A including the service ID and the ID of the in-vehicle ECU 111A to the in-vehicle ECU 101.

[0069] When the start-up unit 15 receives the FindService message M2A from the in-vehicle ECU 111A via the communication port P1A and the ECU communication unit 12, it outputs a relay start instruction including the ID of the in-vehicle ECU 111A to the termination unit 14A.

[0070] Furthermore, when activating the terminal unit 14B, the activation unit 15 acquires, from the correspondence table T1, a service ID "X002" corresponding to the application ID of the terminal unit 14B and an option ID "Y002" corresponding to the application ID of the terminal unit 14A. The activation unit 15 generates an OfferService message M1B including the acquired service ID and option ID, and transmits the generated OfferService message M1B to the in-vehicle ECU 111 via the ECU communication unit 12 and the communication port P1.

[0071] The in-vehicle ECU 111 receives the OfferService message M1B from the in-vehicle ECU 101 and acquires a service ID from the received OfferService message M1B. For example, in order to receive the service indicated by the acquired service ID, the in-vehicle ECU 111B transmits a FindService message M2B including the service ID and the ID of the in-vehicle ECU 111B to the in-vehicle ECU 101.

[0072] When the start-up unit 15 receives the FindService message M2B from the in-vehicle ECU 111B via the communication port P1B and the ECU communication unit 12, it outputs a relay start instruction including the ID of the in-vehicle ECU 111B to the termination unit 14B.

[0073] (Relay processing) The termination unit 14 performs a relay process to relay communication between the USB device 121, the connection of which is detected by the USB communication unit 11, and the in-vehicle ECU 111 in the in-vehicle network 201. For example, the termination unit 14 performs a relay process to relay communication between one USB device 121 corresponding to the termination unit 14 and the in-vehicle ECU 111.

[0074] More specifically, upon receiving a relay start instruction from the activation unit 15, the termination unit 14A starts a relay process for relaying communication between the USB device 121A connected to the USB port P2A and the in-vehicle ECU 111A.

[0075] Furthermore, upon receiving a relay start instruction from the activation unit 15, the termination unit 14B starts a relay process for relaying communication between the USB device 121B connected to the USB port P2B and the in-vehicle ECU 111B.

[0076] In the relay process, the termination unit 14 terminates communication with the USB device 121 and communication with the in-vehicle ECU 111. That is, the termination unit 14 performs termination processing of the USB communication protocol and termination processing of the communication protocol in the in-vehicle network.

[0077] (1) Transmission of communication data Dt from the USB device 121 to the in-vehicle ECU 111 The USB device 121 generates communication data Dt1, which is communication data Dt addressed to the in-vehicle ECU 111. The USB device 121 generates a frame F1 that includes the communication data Dt1 and is addressed to the in-vehicle ECU 111, and conforms to the USB standard, and transmits the generated frame F1 to the in-vehicle ECU 101 via the USB connector 131.

[0078] When the USB communication unit 11 in the in-vehicle ECU 101 receives a frame F1 from the USB device 121 via the corresponding USB connector 131 and the corresponding USB port P2, the USB communication unit 11 outputs the received frame F1 to the proxy unit 13.

[0079] In the proxy unit 13, the termination unit 14 corresponding to the USB device 121 that is the sender of the frame F1 receives the frame F1 from the USB communication unit 11 and performs termination processing of the USB communication protocol. More specifically, as the termination processing, the termination unit 14 acquires communication data Dt1 from the frame F1 and transmits a response frame to the USB device 121 via the USB communication unit 11, USB port P2, and USB connector 131.

[0080] The termination unit 14 then generates a frame F2 conforming to the Ethernet standard, including the acquired communication data Dt1, and transmits the generated frame F2 to the destination in-vehicle ECU 111 via the ECU communication unit 12 and the corresponding communication port P1.

[0081] For example, when the in-vehicle ECU 111 that has received the frame F2 transmits a response frame, the termination unit 14 further receives the response frame via the communication port P1 and the ECU communication unit 12 as a termination process.

[0082] (2) Transmission of communication data Dt from the in-vehicle ECU 111 to the USB device 121 The in-vehicle ECU 111 generates communication data Dt2, which is communication data Dt addressed to the USB device 121. The in-vehicle ECU 111 generates a frame F2 that includes the communication data Dt2 and is addressed to the USB device 121 and conforms to Ethernet, and transmits the generated frame F2 to the in-vehicle ECU 101.

[0083] When the ECU communication unit 12 in the in-vehicle ECU 101 receives the frame F2 from the in-vehicle ECU 111 via the corresponding communication port P1, the ECU communication unit 12 outputs the received frame F2 to the proxy unit 13.

[0084] In the proxy unit 13, the termination unit 14 corresponding to the USB device 121 that is the destination of the frame F2 receives the frame F2 from the ECU communication unit 12 and performs termination processing of the communication protocol in the in-vehicle network. More specifically, as the termination processing, the termination unit 14 acquires the communication data Dt2 from the frame F2 and transmits a response frame to the in-vehicle ECU 111 via the ECU communication unit 12 and the communication port P1.

[0085] Then, the termination unit 14 generates a frame F1 conforming to the USB standard and including the communication data Dt2, and transmits the generated frame F1 to the destination USB device 121 via the USB communication unit 11, the corresponding USB port P2, and the corresponding USB connector 131.

[0086] For example, when the USB device 121 that has received the frame F1 transmits a response frame, the termination unit 14 further receives the response frame via the USB connector 131, the USB port P2, and the USB communication unit 11 as termination processing.

[0087] [Operation flow] FIG. 5 is a flowchart illustrating an example of an operation procedure when the vehicle-mounted ECU according to the embodiment of the present disclosure starts relay processing.

[0088] Referring to FIG. 5, first, the in-vehicle ECU 101 waits for a connection notification to arrive (NO in step S11), and when it receives a connection notification from the USB device 121 via the USB connector 131 and the USB port P2 (YES in step S11), it recognizes that the USB device 121 has been connected to the USB port P2 via the USB connector 131, and sends a device information request to the USB device 121 via the USB port P2 and the USB connector 131, and also sends a connector information request to the USB connector 131 via the USB port P2 (step S12).

[0089] Next, the in-vehicle ECU 101 waits for the arrival of a device information response and a connector information response (NO in step S13), and when it receives the device information response and the connector information response from the USB device 121 and the USB connector 131, respectively (YES in step S13), it creates connection information Con indicating the class number, idVender, idProduct, and iProduct (step S14).

[0090] Next, the in-vehicle ECU 101 starts up the termination unit 14 corresponding to the device information and connector information indicated by the connection information Con, based on the correspondence table T1 in the storage unit 16 (step S15).

[0091] Next, the in-vehicle ECU 101 starts a relay process for relaying communication between the USB device 121 connected to the USB port P2 and the in-vehicle ECU 111 (step S16).

[0092] Next, the in-vehicle ECU 101 waits for a connection notification from the new USB device 121 (NO in step S11).

[0093] 6 is a flowchart illustrating an example of an operation procedure when an in-vehicle ECU according to an embodiment of the present disclosure starts up a termination unit, and shows details of step S15 in FIG.

[0094] Referring to FIG. 6, first, the in-vehicle ECU 101 searches the records R1 in the correspondence table T1 for a record R1 that includes a composite primary key that matches the class number, idVender, idProduct, and iProduct indicated by the connection information Con (step S21).

[0095] Next, if the search target record R1 exists (YES in step S22), the in-vehicle ECU 101 acquires the application ID included in the record R1, and starts the terminal unit 14 having the acquired application ID (step S23).

[0096] On the other hand, if the record R1 to be searched for does not exist (NO in step S22), the in-vehicle ECU 101 searches for a record R2 from among the multiple records R2 in the correspondence table T1 that contains a composite primary key that matches the class number indicated by the connection information Con and iProduct (step S24).

[0097] Next, if the search target record R2 exists (YES in step S25), the in-vehicle ECU 101 acquires the application ID included in the record R2, and starts the terminal unit 14 having the acquired application ID (step S23).

[0098] On the other hand, if the record R2 to be searched does not exist (NO in step S29), the in-vehicle ECU 101 ends the process without activating the termination unit 14.

[0099] FIG. 7 is a diagram illustrating an example of a communication sequence in the in-vehicle system according to the embodiment of the present disclosure.

[0100] 7, first, when the USB device 121 is connected to the USB port P2 in the in-vehicle ECU 101 via the USB connector 131, the USB device 121 transmits a connection notification to the in-vehicle ECU 101 via the USB connector 131 (step S31).

[0101] Next, when the in-vehicle ECU 101 receives a connection notification from the USB device 121 via the USB connector 131 and the USB port P2, it recognizes that the USB device 121 has been connected to the USB port P2 and sends a device information request to the USB device 121 via the USB port P2 and the USB connector 131 (step S32).

[0102] Next, the in-vehicle ECU 101 transmits a connector information request to the USB connector 131 via the USB port P2 (step S33).

[0103] Next, the USB device 121 transmits a device information response including the class number, idVender, and idProduct of the USB device 121 to the in-vehicle ECU 101 via the USB connector 131 as a response to the device information request (step S34).

[0104] Next, the USB connector 131 transmits a connector information response including the iProduct of the USB connector 131 to the in-vehicle ECU 101 as a response to the connector information request (step S35).

[0105] Next, the in-vehicle ECU 101 starts the termination unit 14 corresponding to the class number, idVender, and idProduct of the USB device 121 and the iProduct of the USB connector 131 based on the correspondence table T1 in the storage unit 16 (step S36).

[0106] Next, the in-vehicle ECU 101 transmits an OfferService message M1 including a service ID and an option ID corresponding to the application ID of the terminal unit 14 to the in-vehicle ECU 111 (step S37).

[0107] Next, the in-vehicle ECU 111 that has received the OfferService message M1 transmits a FindService message M2 including a service ID corresponding to the application ID of the terminal unit 14 and the ID of the in-vehicle ECU 111 to the in-vehicle ECU 101 (step S38).

[0108] Next, the in-vehicle ECU 101 receives the FindService message M2 from the in-vehicle ECU 111 and starts a relay process for relaying communication between the USB device 121 and the in-vehicle ECU 111 (step S39).

[0109] Next, the USB device 121 receives a predetermined notification accompanying the reception of the FindService message M2 from the in-vehicle ECU 101, and transmits a frame F1 addressed to the in-vehicle ECU 111 to the in-vehicle ECU 101 via the USB connector 131 (step S40).

[0110] Next, the in-vehicle ECU 101 receives the frame F1 from the USB device 121 and performs a termination process of the USB communication protocol. More specifically, as the termination process, the in-vehicle ECU 101 acquires the communication data Dt1 from the frame F1 and transmits a response frame to the USB device 121 via the USB connector 131 (step S41).

[0111] Next, the in-vehicle ECU 101 transmits the frame F2 including the acquired communication data Dt1 to the in-vehicle ECU 111 (step S42).

[0112] Next, for example, the in-vehicle ECU 111 transmits a frame F2 addressed to the USB device 121 to the in-vehicle ECU 101 (step S43).

[0113] Next, the in-vehicle ECU 101 receives the frame F2 from the in-vehicle ECU 111 and performs a termination process of the communication protocol in the in-vehicle network. More specifically, as the termination process, the in-vehicle ECU 101 acquires the communication data Dt2 from the frame F2 and transmits a response frame to the in-vehicle ECU 111 (step S44).

[0114] Next, the in-vehicle ECU 101 transmits the frame F1 including the acquired communication data Dt2 to the in-vehicle ECU 111 via the USB connector 131 (step S45).

[0115] The order of steps S32 and S33 is not limited to the above, and may be reversed.Furthermore, the order of steps S34 and S35 is not limited to the above, and may be reversed.

[0116] Furthermore, in the in-vehicle system 301, any one of the above steps S40, S41, and S42 and the above steps S43, S44, and S45 may not be performed. More specifically, in the in-vehicle system 301, the USB device 121 may transmit the communication data Dt1 to the in-vehicle ECU 111 via the in-vehicle ECU 101, while the in-vehicle ECU 111 may not transmit the communication data Dt2. In this case, the termination unit 14 terminates communication with the USB device 121, but does not terminate communication with the in-vehicle ECU 111.

[0117] Furthermore, the in-vehicle system 301 may be configured such that the in-vehicle ECU 111 transmits the communication data Dt2 to the USB device 121 via the in-vehicle ECU 101, while the USB device 121 does not transmit the communication data Dt1. In this case, the terminal unit 14 terminates communication with the in-vehicle ECU 111, but does not terminate communication with the USB device 121.

[0118] Furthermore, in the in-vehicle system 301 according to the embodiment of the present disclosure, the USB connectors 131A and 131B are configured to store different connector information from each other, but this is not limiting. The USB connectors 131A and 131B may be configured to store the same connector information.

[0119] Furthermore, although the in-vehicle system 301 according to the embodiment of the present disclosure has been described as having a configuration including the USB connector 131, the present disclosure is not limited to this. The in-vehicle system 301 may be configured to have a USB hub that stores connector information instead of the USB connector 131. In this case, the USB communication unit 11 in the in-vehicle ECU 101 detects the connection of the USB device 121 to the USB port P2 via the USB hub, and acquires device information about the USB device 121 and connector information about the USB hub.

[0120] Furthermore, in the in-vehicle ECU 101 according to the embodiment of the present disclosure, the correspondence table T1 may be configured to further include, in addition to the records R1 and R2, a plurality of records R3 in which all of the fields of the device information are set to arbitrary values, i.e., NULL. In this case, if the search target records R1 and R2 are not present, the launch unit 15 acquires an app ID corresponding to the connector information indicated by the connection information Con, and launches the termination unit 14 corresponding to the acquired app ID. Furthermore, the correspondence table T1 may be configured to further include, in addition to the records R1 and R2, a plurality of records R4 in which all of the fields of the connector information are set to arbitrary values, i.e., NULL. In this case, if the search target records R1 and R2 are not present, the launch unit 15 acquires an app ID corresponding to the device information indicated by the connection information Con, and launches the termination unit 14 corresponding to the acquired app ID.

[0121] Furthermore, in the in-vehicle ECU 101 according to the embodiment of the present disclosure, the termination unit 14 is configured to perform relay processing for relaying communication between the one USB device 121 corresponding to the termination unit 14 and the in-vehicle ECU 111, but this is not limited to this. The termination unit 14 may be configured to perform relay processing for relaying communication between a plurality of USB devices 121 and the in-vehicle ECU 111.

[0122] Furthermore, in the in-vehicle ECU 101 according to the embodiment of the present disclosure, the activation unit 15 is configured to determine the termination unit 14 to be activated based on the correspondence table T1 in the storage unit 16 and the device information and connector information acquired by the USB communication unit 11. However, this is not limited to this. Instead of determining the termination unit 14 to be activated, the activation unit 15 may be configured to receive a selection result of the termination unit 14 to be activated from the user. More specifically, the activation unit 15 receives connection information Con from the USB communication unit 11 and performs processing to display, for example, device information, purpose, and installation location in the vehicle 1 of the connected USB device 121 on a graphical user interface (GUI). The activation unit 15 receives the selection result of the termination unit 14 to be activated from the user via the GUI. Then, the activation unit 15 activates the termination unit 14 selected by the user.

[0123] The above-described embodiments should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims.

[0124] Each process (each function) in the above-described embodiments is realized by a processing circuit including one or more processors. The processing circuit may be configured as an integrated circuit or the like that combines one or more memories, various analog circuits, and various digital circuits in addition to the one or more processors. The one or more memories store programs (instructions) that cause the one or more processors to execute each of the processes. The one or more processors may execute each of the processes according to the program read from the one or more memories, or according to a logic circuit pre-designed to execute each of the processes. The processor may be various processors suitable for computer control, such as a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a field programmable gate array (FPGA), and an application-specific integrated circuit (ASIC). Note that the physically separate processors may cooperate with each other to execute each of the processes. For example, the processors mounted on a plurality of physically separated computers may cooperate with each other to execute the above processes via a network such as a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, etc. The program may be installed into the memory from an external server device or the like via the network, or may be distributed in a state stored on a recording medium such as a CD-ROM (Compact Disc Read Only Memory), a DVD-ROM (Digital Versatile Disc Read Only Memory), or a semiconductor memory, and installed into the memory from the recording medium.

[0125] The above description includes the following additional features. [Appendix 1] An in-vehicle device in an in-vehicle network, a connection port to which an external device can be connected via a USB interface; a detection unit that detects connection of a USB device to the connection port via a connector; an acquisition unit that acquires device information about the USB device whose connection is detected by the detection unit and connector information about the connector; a plurality of relay units that perform relay processing for relaying communications between the USB device and other devices in the in-vehicle network; a starting unit that starts up a relay unit among the plurality of relay units that performs the relay process between the USB device whose connection is detected by the detecting unit and the other device; a storage unit that stores correspondence information indicating a correspondence relationship between each of the plurality of relay units and the device information and the connector information; the relay unit performs at least one of a termination of communication with the USB device and a termination of communication with the other device in the relay process; the activation unit determines the relay unit to be activated based on the correspondence information, and the device information and the connector information acquired by the acquisition unit; The in-vehicle device, wherein the types of the plurality of relay units differ for each USB device class.

[0126] [Appendix 2] An in-vehicle device in an in-vehicle network, a processing circuit and a connection port to which an external device can be connected via a USB interface; The processing circuitry Detecting a connection of a USB device to the connection port via a connector; Acquire device information about the detected USB device and connector information about the connector; performing a relay process for relaying communications between the USB device and other devices in the in-vehicle network; activating a relay unit that performs the relay process between the USB device that has detected the connection and the other device, among a plurality of relay units that perform the relay process; The in-vehicle device further comprises: a storage unit that stores correspondence information indicating a correspondence relationship between each of the plurality of relay units, the device information, and the connector information; The processing circuitry In the relay process, at least one of a termination of communication with the USB device and a termination of communication with the other device is performed; The in-vehicle device determines the relay unit to be activated based on the correspondence information, the acquired device information, and the acquired connector information. [Explanation of symbols]

[0127] 1 vehicle 2 Ethernet cables 11 USB communication unit 12 ECU communication section 13 Proxy section 14 Termination 15 Starting part 16 Memory section 101 Automotive ECU 111,111A,111B Automotive ECU 121,121A,121B USB device 131, 131A, 131B USB connector 201 In-vehicle network 301 In-Vehicle Systems P1, P1A, P1B communication ports P2, P2A, P2B, P2C USB ports T1 Supported Table

Claims

1. An in-vehicle device in an in-vehicle network, a connection port to which an external device can be connected via a USB interface; a detection unit that detects connection of a USB device to the connection port via a connector; an acquisition unit that acquires device information about the USB device whose connection is detected by the detection unit and connector information about the connector; a plurality of relay units that perform relay processing for relaying communications between the USB device and other devices in the in-vehicle network; a start-up unit that starts up one of the plurality of relay units that performs the relay process between the USB device, the connection of which is detected by the detection unit, and the other device; a storage unit that stores correspondence information indicating a correspondence relationship between each of the plurality of relay units and the device information and the connector information; the relay unit performs at least one of a termination of communication with the USB device and a termination of communication with the other device in the relay process; The activation unit determines the relay unit to be activated based on the correspondence information, and the device information and the connector information acquired by the acquisition unit.

2. The in-vehicle device according to claim 1 , wherein the storage unit stores, as the correspondence information, a correspondence table including a composite primary key consisting of the device information item and the connector information item.

3. An in-vehicle system in an in-vehicle network, an in-vehicle device; a connector; the in-vehicle device includes a connection port to which an external device can be connected via a USB interface, and a plurality of relay units that perform relay processing to relay communications between the USB device and other devices in the in-vehicle network; the connector stores connector information relating to the connector; the in-vehicle device acquires the connector information from the connector connected to the connection port, and acquires device information regarding the USB device connected to the connection port via the connector; the in-vehicle device further includes a storage unit configured to store correspondence information indicating a correspondence relationship between each of the plurality of relay units, the device information, and the connector information; The in-vehicle device determines which of the plurality of relay units to activate based on the correspondence information, the acquired device information, and the acquired connector information.

4. the in-vehicle device includes a first connection port and a second connection port, which are the connection ports; a first connector that is the connector connected to the first connection port stores first connector information that is the connector information; a second connector that is the connector connected to the second connection port stores second connector information that is the connector information different from the first connector information; The in-vehicle system according to claim 3 , wherein the in-vehicle device acquires the first connector information from the first connector and acquires the second connector information from the second connector.

5. A communication method for an in-vehicle device in an in-vehicle network, comprising: the in-vehicle device includes a connection port to which an external device can be connected via a USB interface, and a plurality of relay units that perform relay processing to relay communications between the USB device and other devices in the in-vehicle network; the relay unit performs at least one of a termination of communication with the USB device and a termination of communication with the other device in the relay process; The communication method includes: detecting a connection of a USB device to the connection port via a connector; acquiring device information about the USB device whose connection has been detected and connector information about the connector; activating a relay unit among the plurality of relay units that performs the relay process between the USB device that has detected the connection and the other device; The in-vehicle device further a storage unit that stores correspondence information indicating a correspondence relationship between each of the plurality of relay units, the device information, and the connector information; In the step of activating the relay unit, the relay unit to be activated is determined based on the correspondence information, and the acquired device information and connector information.

6. A communication program used in an in-vehicle device in an in-vehicle network, the in-vehicle device includes a connection port to which an external device can be connected via a USB interface; Computer, a detection unit that detects connection of a USB device to the connection port via a connector; an acquisition unit that acquires device information about the USB device whose connection is detected by the detection unit and connector information about the connector; a plurality of relay units that perform relay processing for relaying communications between the USB device and other devices in the in-vehicle network; a start-up unit that starts up one of the plurality of relay units that performs the relay process between the USB device whose connection is detected by the detection unit and the other device; It is a program to function as The in-vehicle device further a storage unit that stores correspondence information indicating a correspondence relationship between each of the plurality of relay units, the device information, and the connector information; the relay unit performs at least one of a termination of communication with the USB device and a termination of communication with the other device in the relay process; The launching unit determines the relay unit to be launched based on the correspondence information, and the device information and the connector information acquired by the acquisition unit.

Images