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

Abstract

The vehicle-mounted device includes: a connection port for connecting to an external device; a detection unit for detecting the connection of a USB device to the connection port via a connector; an acquisition unit for acquiring device information related to the USB device and connector information related to the connector; a plurality of relay units; a startup unit for starting the relay units; and a storage unit for storing correspondence information representing the correspondence between each of the plurality of relay units and the device information and the connector information, wherein the startup unit determines which relay unit to start based on the correspondence information, the device information, and the connector information.

Description

Technical Field

[0001] This disclosure relates to vehicle-mounted devices, vehicle-mounted systems, communication methods, and communication procedures.

[0002] This application claims priority based on Japanese Application No. 2024-9886, filed on January 26, 2024, and incorporates all of its disclosures herein. Background Technology

[0003] Patent Document 1 (International Publication No. 2020 / 179123) discloses a management device as follows. That is, the management device comprises: a detection unit that detects the addition of a function unit to a network including one or more vehicle-mounted function units; an acquisition unit that acquires function unit information, including information related to the network configuration of the added function unit (i.e., the new function unit) detected by the detection unit and the layer below the application layer of the vehicle-mounted function unit; and a generation unit that, based on the function unit information acquired by the acquisition unit, generates configuration information of the network, i.e., a new network, further including the new function unit.

[0004] Existing technical documents

[0005] Patent documents

[0006] Patent Document 1: International Publication No. 2020 / 179123 Summary of the Invention

[0007] The vehicle-mounted device disclosed herein is a vehicle-mounted device in a vehicle network, comprising: a connection port capable of connecting to an external device via a USB interface; a detection unit for detecting the connection of a USB device to the connection port via a connector; an acquisition unit for acquiring device information related to the USB device detected as connected by the detection unit and connector information related to the connector; a plurality of relay units for performing relay processing, in which communication between the USB device and other devices in the vehicle network is relayed; a startup unit for starting one of the plurality of relay units that performs the relay processing between the USB device detected as connected by the detection unit and the other devices; and a storage unit for storing correspondence information representing the correspondence between each of the plurality of relay units and the device information and the connector information, wherein the relay unit performs at least one of terminating communication with the USB device and terminating communication with the other devices in the relay processing, and the startup unit determines the relay unit to be started based on the correspondence information and the device information and connector information acquired by the acquisition unit.

[0008] One aspect of this disclosure can be implemented not only as an in-vehicle device with such a characteristic processing unit, but also as a semiconductor integrated circuit that implements part or all of the in-vehicle device. Attached Figure Description

[0009] Figure 1 This is a diagram illustrating an example of the configuration of an in-vehicle system according to an embodiment of the present disclosure.

[0010] Figure 2 This is a diagram illustrating the configuration of an on-board ECU according to an embodiment of the present disclosure.

[0011] Figure 3 This is a diagram showing an overview of USB device categories for embodiments of the present disclosure.

[0012] Figure 4 This is a diagram showing an example of a correspondence table stored in the storage unit of an on-board ECU according to an embodiment of the present disclosure.

[0013] Figure 5 This is a flowchart illustrating an example of the operation process when the vehicle ECU of the present disclosure begins relay processing.

[0014] Figure 6 This is a flowchart illustrating an example of the operation process when the vehicle ECU of the present disclosure starts the termination section.

[0015] Figure 7 This is a diagram illustrating an example of a communication sequence in an in-vehicle system according to an embodiment of the present disclosure. Detailed Implementation

[0016] Previously, with the popularization of car sharing and the expectation of improved processing power of in-vehicle devices, there was a demand to customize in-vehicle networks by connecting external devices to the in-vehicle devices.

[0017] [The problem this disclosure aims to solve]

[0018] Beyond the technology described in Patent Document 1, there is a technology that aims to relay communication between external devices connected to the vehicle network via a USB (Universal Serial Bus) interface and other devices in the vehicle network in a simple structure.

[0019] This disclosure was made to solve the aforementioned problems, and its purpose is to provide an in-vehicle device, in-vehicle system, communication method, and communication program that can relay communication between an external device connected to an in-vehicle network via a USB interface and other devices in the in-vehicle network in a simple structure.

[0020] [The Effects of This Disclosure]

[0021] According to this disclosure, it is possible to relay communication between external devices connected to a vehicle network via a USB interface and other devices in the vehicle network with a simple structure.

[0022] [Description of embodiments of this disclosure]

[0023] First, the contents of the embodiments of this disclosure will be described.

[0024] (1) The vehicle-mounted device according to the embodiments of the present disclosure is a vehicle-mounted device in a vehicle network, comprising: a connection port capable of connecting an external device via a USB interface; a detection unit for detecting the connection of a USB device to the connection port via a connector; an acquisition unit for acquiring device information related to the USB device detected by the detection unit and connector information related to the connector; a plurality of relay units for performing relay processing, in which communication between the USB device and other devices in the vehicle network is relayed; a startup unit for starting one of the plurality of relay units that performs the relay processing between the USB device detected by the detection unit and the other devices; and a storage unit for storing correspondence information representing the correspondence between each of the plurality of relay units and the device information and the connector information, wherein the relay unit performs at least one of terminating communication with the USB device and terminating communication with the other devices in the relay processing, and the startup unit determines the relay unit to be started based on the correspondence information and the device information and connector information acquired by the acquisition unit.

[0025] This structure allows the relay unit to be activated based on pre-stored information in the storage unit, enabling relay processing between USB devices 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 begin without user intervention. Furthermore, if the vehicle device has multiple connection ports and multiple USB devices of the same model are connected to these ports, the relay unit can be activated according to the different connectors used for connection, establishing a corresponding connection with each USB device. Moreover, compared to a structure that associates the activated relay unit with the port number of the connection port, this structure avoids the constraint of the connection port at the destination when connecting a USB device to the vehicle device, and activates the relay unit accordingly. Therefore, a simple structure can be used to relay communication between external devices connected to the vehicle network via USB and other devices in the vehicle network.

[0026] (2) In (1) above, the storage unit may also store a correspondence table containing a composite primary key consisting of items of the device information and items of the connector information as the correspondence information.

[0027] With this structure, the relay unit to be activated can be uniquely determined based on both device information and connector information.

[0028] (3) The vehicle system of the present disclosure is a vehicle system in a vehicle network, wherein it includes a vehicle device and a connector. The vehicle device includes: a connection port that can connect to an external device via a USB interface; and a plurality of relay units that perform relay processing, in which communication between the USB device and other devices in the vehicle network is relayed. The connector stores connector information related to the connector. The vehicle device obtains the connector information from the connector connected to the connection port and obtains device information related to the USB device connected to the connection port via the connector. The vehicle device also includes a storage unit that stores correspondence information representing the correspondence between each of the plurality of relay units and the device information and the connector information. The vehicle device determines which of the plurality of relay units to be activated based on the correspondence information and the obtained device information and connector information.

[0029] This structure allows the relay unit to be activated based on pre-stored information in the storage unit, enabling relay processing between USB devices 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 begin without user intervention. Furthermore, if the vehicle device has multiple connection ports and multiple USB devices of the same model are connected to these ports, the relay unit can be activated according to the different connectors used for connection, establishing a corresponding connection with each USB device. Moreover, compared to a structure that associates the activated relay unit with the port number of the connection port, this structure avoids the constraint of the connection port at the destination when connecting a USB device to the vehicle device, and activates the relay unit accordingly. Therefore, a simple structure can be used to relay communication between external devices connected to the vehicle network via USB and other devices in the vehicle network.

[0030] (4) In (3) above, the vehicle device may also have a first connection port and a second connection port as the connection port. The connector connected to the first connection port, i.e. the first connector, stores the first connector information as the connector information. The connector connected to the second connection port, i.e. the second connector, stores the second connector information as the connector information that is different from the first connector information. The vehicle device obtains the first connector information from the first connector and obtains the second connector information from the second connector.

[0031] With this structure, when multiple USB devices of the same model are connected to the first connection port and the second connection port respectively, a corresponding start-up relay can be established with the USB devices according to the different connectors.

[0032] (5) The communication method of the present disclosure is a communication method in a vehicle-mounted device in a vehicle network, wherein the vehicle-mounted device includes: a connection port capable of connecting to an external device via a USB interface; and a plurality of relay units for relaying communication between a USB device and other devices in the vehicle network, wherein the relay unit performs at least one of terminating communication with the USB device and terminating communication with the other devices in the relaying process, and the communication method includes: a step of detecting a connection of a USB device to the connection port via a connector; a step of obtaining device information related to the detected connected USB device and connector information related to the connector; and a step of activating one of the plurality of relay units that performs the relaying process between the detected connected USB device and the other devices, wherein the vehicle-mounted device further includes a storage unit that stores correspondence information representing the correspondence between each of the plurality of relay units and the device information and the connector information, and in the step of activating the relay unit, the vehicle-mounted device determines the relay unit to be activated based on the correspondence information and the obtained device information and connector information.

[0033] This method enables the relay unit to be activated based on pre-stored information in the storage unit, facilitating relay processing between USB devices 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 begin without user intervention. Furthermore, if the vehicle system has multiple connection ports and multiple USB devices of the same model are connected to these ports, the relay unit can be activated according to the different connectors used for connection, establishing a corresponding connection with each USB device. Moreover, compared to methods that associate activated relay units with port numbers, this method avoids the limitation of the connection port at the destination when connecting a USB device to the vehicle system, allowing the relay unit to be activated according to the USB device. Therefore, a simple structure can be used to relay communication between external devices connected to the vehicle network via USB and other devices within the vehicle network.

[0034] (6) The communication program of the present disclosure is a communication program used in an in-vehicle device in an in-vehicle network, wherein the in-vehicle device has a connection port capable of connecting to an external device via a USB interface, and the communication program causes a computer to function as the following units: a detection unit that detects the connection of a USB device to the connection port via a connector; an acquisition unit that acquires device information related to the USB device detected as connected by the detection unit and connector information related to the connector; multiple relay units that perform relay processing, in which communication between the USB device and other devices in the in-vehicle network is relayed; and a startup unit. The vehicle-mounted device further includes a storage unit that stores correspondence information representing the correspondence between each of the plurality of relay units and the device information and the connector information. The relay unit performs at least one of the following in the relay process: termination of communication with the USB device and termination of communication with the other device. The activation unit determines which relay unit to activate based on the correspondence information and the device information and connector information obtained by the acquisition unit.

[0035] This structure allows the relay unit to be activated based on pre-stored information in the storage unit, enabling relay processing between USB devices 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 begin without user intervention. Furthermore, if the vehicle device has multiple connection ports and multiple USB devices of the same model are connected to these ports, the relay unit can be activated according to the different connectors used for connection, establishing a corresponding connection with each USB device. Moreover, compared to a structure that associates the activated relay unit with the port number of the connection port, this structure avoids the constraint of the connection port at the destination when connecting a USB device to the vehicle device, and activates the relay unit accordingly. Therefore, a simple structure can be used to relay communication between external devices connected to the vehicle network via USB and other devices in the vehicle network.

[0036] The embodiments of this disclosure will now be described using the accompanying drawings. It should be noted that identical or equivalent parts in the drawings are labeled with the same reference numerals, and their descriptions will not be repeated. Furthermore, at least some of the embodiments described below may be combined arbitrarily.

[0037] [Structure and Basic Movements]

[0038] Figure 1 This is a diagram illustrating an example of the structure of an in-vehicle system according to an embodiment of the present disclosure. (Refer to...) Figure 1 The vehicle system 301 includes an on-board ECU (Electronic Control Unit) 101, on-board ECUs 111A and 111B (which are also on-board ECUs 111), and a USB connector 131. The USB connector 131 is an example of a connector. The vehicle system 301 is mounted on a vehicle 1. The on-board ECUs 101 and 111 constitute an on-board network 201. It should be noted that the vehicle system 301 can have a structure with one or more on-board ECUs 111, or it can have a structure with multiple USB connectors 131.

[0039] Vehicle-mounted ECUs (ECUs) include, for example, relay devices, TCUs (Telematics Communication Units), autonomous driving ECUs, engine ECUs, sensors, navigation devices, human-machine interfaces, and cameras.

[0040] The vehicle-mounted ECU 101 has communication ports P1A and P1B and USB (registered trademark) ports P2A, P2B, and P2C. Hereinafter, communication ports P1A and P1B will also be referred to as communication port P1, and USB ports P2A, P2B, and P2C will also be referred to as USB port P2. USB port P2 is an example of a connection port. It should be noted that the vehicle-mounted ECU 101 may also have one or more communication ports P1. Additionally, the vehicle-mounted ECU 101 may also have two or more USB ports P2.

[0041] Communication port P1 is, for example, a connector capable of connecting an Ethernet (registered trademark) cable 2. USB port P2 can connect external devices such as USB connector 131 and USB device 121 via a USB interface. That is, USB port P2 is a connector capable of connecting a USB connector.

[0042] Vehicle ECUs 111A and 111B are connected to communication ports P1A and P1B in vehicle ECU 101 via Ethernet cable 2, respectively. It should be noted that vehicle ECU 111 is not limited to the structure of being connected to vehicle ECU 101 via Ethernet cable 2, but can also be connected via communication lines that conform to other standards such as CAN (Controller Area Network) (registered trademark) and FlexRay (registered trademark).

[0043] [Topic]

[0044] The desired technology is to relay communication between a USB device 121 connected to a vehicle network 201 via a USB interface and other devices in the vehicle network 201 in a simple structure.

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

[0046] On the other hand, in the vehicle system 301, when a USB device 121 is connected to the USB port P2 of the vehicle ECU 101, the exchange of communication data Dt between the USB device 121 and the vehicle ECU 111 via the vehicle ECU 101 is considered. However, the USB device 121 communicates according to the USB standard, while the vehicle ECU 111 communicates according to a different standard. Therefore, in the vehicle system 301, a relay application for relaying between the USB device 121 and the vehicle ECU 111 is mounted on the vehicle ECU 101.

[0047] For example, the vehicle ECU 101 is equipped with multiple relay applications corresponding to various USB devices 121 that can be connected to the vehicle ECU 101. For example, it is desirable that when the USB device 121 is installed on the USB port P2 of the vehicle ECU 101 after the vehicle 1 leaves the factory, the application corresponding to the USB device 121 can be automatically selected and launched from the multiple relay applications without user operation, and communication between the USB device 121 and the vehicle ECU 111 can begin.

[0048] Therefore, the vehicle system 301 of the present disclosure solves the above-mentioned problems through the following structure.

[0049] (Vehicle ECU)

[0050] Figure 2 This is a diagram illustrating the structure of an on-board ECU according to an embodiment of the present disclosure. (Refer to...) Figure 2 The vehicle-mounted ECU 101 includes a USB communication unit 11, an ECU communication unit 12, a proxy unit 13, a start unit 15, and a storage unit 16. The proxy unit 13 includes multiple termination units 14. The USB communication unit 11 is an example of a detection unit and an example of an acquisition unit. The termination units 14 are examples of relay units. Part or all of the USB communication unit 11, ECU communication unit 12, proxy unit 13, and start unit 15 are implemented, for example, by a processing circuit including one or more processors. The storage unit 16 is, for example, a non-volatile memory included in the aforementioned processing circuit.

[0051] exist Figure 2 In the example shown, USB connectors 131A and 131B, which function as USB connectors 131, are connected to USB ports P2A and P2C, respectively. Additionally, USB devices 121A and 121B, which function as 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.

[0052] For example, after vehicle 1 leaves the factory, the USB connector 131 is connected by the user of vehicle 1 to the USB port P2 while the USB device 121 is connected. It should be noted that the USB connector 131 can also be pre-connected to the USB port P2 before vehicle 1 leaves the factory, and the user can connect the USB device 121 to the USB connector 131 after vehicle 1 leaves the factory.

[0053] For example, USB devices 121A and 121B are dynamic image cameras. USB device 121 and vehicle ECU 111 transmit communication data Dt via USB connector 131 and vehicle ECU 101.

[0054] USB connector 131 stores connector information associated with it. For example, USB connector 131 stores a string iProduct (product string index) written to memory by the manufacturer of USB connector 131 as connector information. It should be noted that USB connector 131 may also have the following structure: instead of iProduct, it stores idVender (manufacturer identifier) ​​as connector information, idProduct (product identifier) ​​as a number representing the manufacturer of USB connector 131, iManufacturer (manufacturer string index) as a string written to memory by the manufacturer, or iSerialNumber (serial number string index) as a string written to memory by the manufacturer.

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

[0056] Figure 3 This is a diagram showing an overview of USB device categories for embodiments of the present disclosure. Figure 3 This shows the category name of the USB device class and the correspondence between the USB device 121 corresponding to that USB device class.

[0057] Reference Figure 3USB devices 121 are classified into a specific USB device category according to the standards defined by USB-IF (Implementers Forum). For one or more USB devices 121 with similar functions, each is classified into a specific USB device category. USB devices 121A and 121B, which function as video cameras, are classified into the USB device category named "Video". Furthermore, USB device 121, which functions as a microphone, is classified into the USB device category named "Audio". Additionally, USB device 121, which functions as a keyboard, is classified into the USB device category named "HID (Human Interface Device)". USB devices 121 belonging to the same USB device category communicate with other devices using a common interface specification.

[0058] USB device 121 stores device information associated with it. For example, as device information, USB device 121 stores a category number indicating the USB device category to which it belongs, an idVender number indicating the manufacturer of the USB device 121, and an idProduct number assigned to the USB device 121 by the manufacturer.

[0059] Refer again Figure 2 The terminal unit 14 in the agent unit 13 performs relay processing to relay the communication between the USB device 121 and the vehicle ECU 111.

[0060] As an example, the types of the multiple termination sections 14 in the proxy unit 13 vary according to each USB device category. That is, the proxy unit 13 contains the same number of termination sections 14 of different types as the number of USB device categories to which the USB devices 121 can be connected to the USB port P2. The termination section 14 of a certain type corresponding to a particular USB device category can communicate with the USB devices 121 belonging to that USB device category.

[0061] For example, agent 13 includes multiple terminals 14 of the same type. More specifically, each terminal 14 has the same application ID. Agent 13 includes multiple terminals 14 with the same application ID.

[0062] (Connectivity Detection)

[0063] The USB communication unit 11 detects the 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, it sends a connection notification to the vehicle ECU 101 via the USB connector 131. Upon receiving the 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 is connected to the USB port P2 via the USB connector 131.

[0064] The USB communication unit 11 acquires device information related to the USB device 121 that detects a connection to the USB port P2 and connector information related to the USB connector 131. That is, the USB communication unit 11 acquires device information from the USB device 121 and connector information from the USB connector 131. For example, the USB communication unit 11 acquires multiple types of device information for a single USB device 121.

[0065] More specifically, when the USB communication unit 11 detects that the USB device 121 is connected to the USB port P2 via the USB connector 131, it sends a device information request to the USB device 121 via the USB port P2 and the USB connector 131. Additionally, the USB communication unit 11 sends a connector information request to the USB connector 131 via the USB port P2.

[0066] When the USB device 121 receives a device information request from the vehicle ECU 101, in response to the device information request, it sends a device information response including the category number, idVender, and idProduct of the USB device 121 to the vehicle ECU 101 via the USB connector 131.

[0067] When the USB connector 131 receives a connector information request from the vehicle ECU 101, it sends a connector information response containing the iProduct of the USB connector 131 to the vehicle ECU 101 in response to the connector information request.

[0068] 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 obtains the category number, idVender, and idProduct from the received device information response. Additionally, when the USB communication unit 11 receives a connector information response from the USB connector 131 via the USB port P2, it obtains the idProduct from the received connector information response. The USB communication unit 11 generates connection information Con representing the obtained category number, idVender, idProduct, and idProduct, and outputs the generated connection information Con to the startup unit 15.

[0069] (Startup based on the terminal of the corresponding table)

[0070] The start unit 15 activates one of the multiple termination units 14 that performs relay processing between the USB device 121, which is detected as connected by the USB communication unit 11, and the vehicle ECU 111.

[0071] Figure 4 This is a diagram illustrating an example of a mapping table stored in the storage unit of an onboard ECU according to an embodiment of the present disclosure. (Refer to...) Figure 4 The storage unit 16 stores a correspondence table T1 that represents the correspondence between each of the plurality of termination units 14 and the device information and connector information. The correspondence table T1 is an example of the correspondence information.

[0072] For example, table T1 contains a composite primary key consisting of items for device information and items for connecting device information. More specifically, table T1 is a table showing the correspondence between the composite primary key consisting of items for category number, idVender, idProduct, and iProduct, and the application ID.

[0073] The values ​​of some items in the composite primary key of table T1 are arbitrary. More specifically, table T1 contains multiple records R1 in which all items in the composite primary key are set to specified values, and multiple records R2 in which each item in idVender and idProduct is set to arbitrary values, i.e., NULL.

[0074] For example, the correspondence table T1 also represents the correspondence between each of the multiple terminals 14 of the same type and the additional information that can identify the terminal 14, namely the service ID and the option ID. More specifically, the correspondence table T1 also represents the correspondence between the application ID and the service ID and the option ID. Specifically, the correspondence table T1 contains a record R1 with the application ID "AP001" and the service ID and option ID "X001" and "Y001" respectively, and a record R1 with the application ID "AP001" and the service ID and option ID "X002" and "Y002" respectively.

[0075] The startup unit 15 determines which termination unit 14 to start based on the correspondence table T1 in the storage unit 16 and the device information and connector information obtained from the USB communication unit 11. More specifically, the startup unit 15 receives connection information Con from the USB communication unit 11 and refers to the correspondence table T1 in the storage unit 16.

[0076] The startup unit 15 retrieves a record R1 from multiple records R1 in the correspondence table T1 that contains a composite primary key consistent with the category number, idVender, idProduct, and iProduct represented by the connection information Con received from the USB communication unit 11. If a record R1 is found, the startup unit 15 obtains the application ID contained in that record R1. The startup unit 15 then activates the termination unit 14 with the obtained application ID. Specifically, for example, if the port number, category number, idVender, idProduct, and iProduct represented by the connection information Con are “C002”, “V001”, “P004”, and “EEE” respectively, the startup unit 15 activates the termination unit 14 with the application ID “AP004”.

[0077] For example, if there is no terminal section 14 in the correspondence table T1 that corresponds to all types of device information and connector information, the starting unit 15 determines which terminal section 14 to start based on a subset of device information and connector information.

[0078] More specifically, if the record R1 to be searched does not exist, the startup unit 15 searches for a record R2 from among multiple records R2 in the correspondence table T1 that contains a composite primary key consistent with the category number and iProduct represented by the connection information Con received from the USB communication unit 11. If the record R2 to be searched exists, the startup unit 15 obtains the application ID contained in that record R2. The startup unit 15 then activates the termination unit 14 with the obtained application ID. Specifically, for example, if the category number, idVender, idProduct, and iProduct represented by the connection information Con are “C001”, “V051”, “P051”, and “GGG” respectively, the startup unit 15 activates the termination unit 14 with the application ID “AP011”.

[0079] When the termination unit 14 is started, the startup unit 15 obtains the service ID and option ID corresponding to the application ID of the termination unit 14 from the correspondence table T1. In addition, when the termination unit 14 is started, the startup unit 15 outputs the connection information Con received from the USB communication unit 11 to the started termination unit 14.

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

[0081] (Example of starting the terminal)

[0082] For example, USB devices 121A and 121B have a category number of "C001", an idVender of "V001", and an idProduct of "P001". Additionally, as mentioned above, the iProducts of USB connectors 131A and 131B are "AAA" and "BBB", respectively.

[0083] In this case, the startup unit 15 receives connection information Con from the USB communication unit 11 as the USB device 121A is connected to the USB port P2A via the USB connector 131A. Based on the received connection information Con and the correspondence table T1, the termination unit 14, i.e., the termination unit 14A, which has the application ID "AP001", is started.

[0084] Additionally, the startup unit 15 receives connection information Con from the USB communication unit 11 as the USB device 121B is connected to the USB port P2C via the USB connector 131B. Based on the received connection information Con and the correspondence table T1, the termination unit 14, i.e. the termination unit 14B, which has the application ID "AP001", is started.

[0085] When the terminating unit 14 is activated, the activating unit 15 uses the OfferService message, which conforms to SOME / IP (Scalable service-Oriented Middleware over IP), to provide the on-board ECU 111 with the service using the USB device 121.

[0086] More specifically, when the termination unit 14A is activated, the activation unit 15 obtains "X001", which is the service ID corresponding to the application ID of the termination unit 14A, and "Y001", which is the option ID corresponding to the application ID of the termination unit 14A, from the correspondence table T1. The activation unit 15 generates an OfferService message M1A including the obtained service ID and option ID, and sends the generated OfferService message M1A to the vehicle ECU 111 via the ECU communication unit 12 and the communication port P1.

[0087] The vehicle ECU 111 receives an OfferService message M1A from the vehicle ECU 101 and obtains the service ID from the received OfferService message M1A. For example, in order to accept the provision of the service represented by the obtained service ID, the vehicle ECU 111A sends a FindService message M2A containing the service ID and the ID of the vehicle ECU 111A to the vehicle ECU 101.

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

[0089] Furthermore, when the start unit 15 activates the termination unit 14B, the start unit 15 obtains "X002", which is the service ID corresponding to the application ID of the termination unit 14B, and "Y002", which is the option ID corresponding to the application ID of the termination unit 14A, from the correspondence table T1. The start unit 15 generates an OfferService message M1B including the obtained service ID and option ID, and sends the generated OfferService message M1B to the vehicle ECU 111 via the ECU communication unit 12 and the communication port P1.

[0090] The vehicle ECU 111 receives an OfferService message M1B from the vehicle ECU 101 and obtains a service ID from the received OfferService message M1B. For example, in order to accept the provision of the service represented by the obtained service ID, the vehicle ECU 111B sends a FindService message M2B, which includes the service ID and the ID of the vehicle ECU 111B, to the vehicle ECU 101.

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

[0092] (Relay processing)

[0093] Termination unit 14 performs relay processing to relay communication between the USB device 121 detected as connected by USB communication unit 11 and the vehicle ECU 111 in vehicle network 201. For example, termination unit 14 performs relay processing to relay communication between a USB device 121 corresponding to termination unit 14 and vehicle ECU 111.

[0094] More specifically, the termination unit 14A receives a relay start instruction from the start unit 15 and begins relay processing for the communication between the USB device 121A connected to the USB port P2A and the vehicle ECU 111A.

[0095] In addition, the termination unit 14B receives a relay start instruction from the start unit 15 and begins relay processing for the communication between the USB device 121B connected to the USB port P2B and the vehicle ECU 111B.

[0096] The termination unit 14 terminates communication with the USB device 121 and communication with the vehicle ECU 111 during relay processing. That is, the termination unit 14 performs termination processing of the USB communication protocol and termination processing of the communication protocol in the vehicle network.

[0097] (1) Transmission of communication data Dt from USB device 121 to vehicle ECU 111

[0098] USB device 121 generates communication data Dt, i.e., communication data Dt1, to be sent to vehicle ECU 111. USB device 121 generates a frame F1, which contains the communication data Dt1 and conforms to the USB standard, to be sent to vehicle ECU 111, and sends the generated frame F1 to vehicle ECU 101 via USB connector 131.

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

[0100] In the proxy unit 13, the termination unit 14, corresponding to the USB device 121 that sent 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 a termination process, the termination unit 14 obtains communication data Dt1 from the frame F1 and sends a response frame to the USB device 121 via the USB communication unit 11, the USB port P2, and the USB connector 131.

[0101] Then, the termination unit 14 generates an Ethernet-compliant frame F2 containing the acquired communication data Dt1, and sends the generated frame F2 to the vehicle ECU 111 at the destination via the ECU communication unit 12 and the corresponding communication port P1.

[0102] For example, when the terminating unit 14 sends a response frame to the on-board ECU 111 that received frame F2, it also receives the response frame via communication port P1 and ECU communication unit 12 as a terminating process.

[0103] (2) Transmission of communication data Dt from vehicle ECU 111 to USB device 121

[0104] The vehicle ECU 111 generates communication data Dt, or communication data Dt2, to be sent to the USB device 121. The vehicle ECU 111 generates an Ethernet-compliant frame F2 containing the communication data Dt2 to be sent to the USB device 121, and sends the generated frame F2 to the vehicle ECU 101.

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

[0106] In the agent 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 vehicle network. More specifically, as a termination process, the termination unit 14 obtains communication data Dt2 from the frame F2 and sends a response frame to the vehicle ECU 111 via the ECU communication unit 12 and the communication port P1.

[0107] Then, the termination unit 14 generates a frame F1 conforming to the USB standard, which contains communication data Dt2, and sends the generated frame F1 to the USB device 121 at the sending destination via the USB communication unit 11, the corresponding USB port P2 and the corresponding USB connector 131.

[0108] For example, when the termination unit 14 sends a response frame to the USB device 121 that received frame F1, it also receives the response frame via the USB connector 131, the USB port P2 and the USB communication unit 11 as a termination process.

[0109] [Action Flow]

[0110] Figure 5 This is a flowchart illustrating an example of the operation process when an on-board ECU begins relay processing according to an embodiment of this disclosure.

[0111] Reference Figure 5 First, the vehicle ECU 101 waits for the arrival of the connection notification (no in step S11). When it receives the 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 is connected to the USB port P2 via the USB connector 131. It sends a device information request to the USB device 121 via the USB port P2 and the USB connector 131, and sends a connector information request to the USB connector 131 via the USB port P2 (step S12).

[0112] Next, the vehicle ECU 101 waits for the arrival of device information response and connector information response (no in step S13). When it receives device information response and connector information response from USB device 121 and USB connector 131 respectively (yes in step S13), it generates connection information Con representing category number, idVender, idProduct and iProduct (step S14).

[0113] Next, the vehicle ECU 101 activates the termination section 14 corresponding to the device information and connector information represented by the connection information Con based on the correspondence table T1 in the storage unit 16 (step S15).

[0114] Next, the vehicle ECU 101 begins relay processing of the communication between the USB device 121 connected to the USB port P2 and the vehicle ECU 111 (step S16).

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

[0116] Figure 6 This is a flowchart illustrating an example of the operation process when the vehicle ECU of the present disclosure starts the termination section. Figure 6 It shows Figure 5 Details of step S15 in the process.

[0117] Reference Figure 6 First, the vehicle ECU 101 retrieves a record R1 containing a composite primary key that matches the category number, idVender, idProduct, and iProduct shown in the connection information Con from multiple records R1 in the corresponding table T1 (step S21).

[0118] Next, if the record R1 containing the target of the search exists (yes in step S22), the vehicle ECU 101 obtains the application ID contained in the record R1 and starts the terminal 14 with the obtained application ID (step S23).

[0119] On the other hand, if there is no record R1 for the target of the search (no in step S22), the vehicle ECU 101 searches for a record R2 containing a composite primary key that is consistent with the category number and iProduct shown in the connection information Con from multiple records R2 in the corresponding table T1 (step S24).

[0120] Next, if the record R2 containing the target of the search exists (yes in step S25), the vehicle ECU 101 obtains the application ID contained in the record R2 and starts the terminal 14 with the obtained application ID (step S23).

[0121] On the other hand, if the record R2 of the target to be searched is not found (no in step S29), the vehicle ECU 101 will terminate the process without starting the termination unit 14.

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

[0123] Reference Figure 7 First, when the USB device 121 is connected to the USB port P2 in the vehicle ECU 101 via the USB connector 131, it sends a connection notification to the vehicle ECU 101 via the USB connector 131 (step S31).

[0124] Next, when a connection notification is received from the USB device 121 via the USB connector 131 and the USB port P2, the vehicle ECU 101 recognizes that the USB device 121 is 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).

[0125] Next, the vehicle ECU 101 sends a connector information request to the USB connector 131 via the USB port P2 (step S33).

[0126] Next, in response to the device information request, the USB device 121 sends a device information response including the category number, idVender, and idProduct of the USB device 121 to the vehicle ECU 101 via the USB connector 131 (step S34).

[0127] Next, in response to the connector information request, the USB connector 131 sends the connector information response of the iProduct including the USB connector 131 to the vehicle ECU 101 (step S35).

[0128] Next, the vehicle ECU 101 activates the termination section 14 corresponding to the category 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).

[0129] Next, the vehicle ECU 101 sends an OfferService message M1, which includes a service ID and an option ID corresponding to the application ID of the terminal unit 14, to the vehicle ECU 111 (step S37).

[0130] Next, the vehicle ECU 111 that receives the OfferService message M1 will send the FindService message M2, which includes the service ID corresponding to the application ID of the terminal 14 and the ID of the vehicle ECU 111, to the vehicle ECU 101 (step S38).

[0131] Next, the vehicle ECU 101 receives the FindService message M2 from the vehicle ECU 111 and begins relay processing for the communication between the USB device 121 and the vehicle ECU 111 (step S39).

[0132] Next, the USB device 121 receives, for example, a notification from the vehicle ECU 101 indicating the receipt of the FindService message M2, and sends the frame F1 destined for the vehicle ECU 111 to the vehicle ECU 101 via the USB connector 131 (step S40).

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

[0134] Next, the vehicle ECU 101 sends frame F2 containing the acquired communication data Dt1 to the vehicle ECU 111 (step S42).

[0135] Next, for example, the vehicle ECU 111 sends frame F2 destined for USB device 121 to the vehicle ECU 101 (step S43).

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

[0137] Next, the vehicle ECU 101 sends frame F1 containing the acquired communication data Dt2 to the vehicle ECU 111 via USB connector 131 (step S45).

[0138] It should be noted that the order of steps S32 and S33 is not limited to the above, and the order can be changed. Similarly, the order of steps S34 and S35 is not limited to the above, and the order can be changed.

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

[0140] Alternatively, in the vehicle system 301, the vehicle ECU 111 may send communication data Dt2 to the USB device 121 via the vehicle ECU 101, while the USB device 121 does not send communication data Dt1. In this case, the termination unit 14 terminates communication with the vehicle ECU 111, but does not terminate communication with the USB device 121.

[0141] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the USB connectors 131A and 131B are structures that store different connector information, but are not limited to this. The USB connectors 131A and 131B may also be structures that store the same connector information.

[0142] Furthermore, while the vehicle system 301 of this disclosure includes a USB connector 131, it is not limited to this. The vehicle system 301 may also have a USB hub that stores connector information instead of the USB connector 131. In this case, the USB communication unit 11 in the vehicle ECU 101 detects the connection of the USB device 121 to the USB port P2 via the USB hub, and obtains device information related to the USB device 121 and connector information related to the USB hub.

[0143] Alternatively, in the vehicle-mounted ECU 101 of this embodiment, the correspondence table T1 may also be a structure containing multiple records R3, in addition to records R1 and R2, where all items of the device information are set to arbitrary values, i.e., NULL. In this case, if the records R1 and R2 for which a search is desired do not exist, the start-up unit 15 obtains the application ID corresponding to the connector information shown in the connection information Con, and starts the termination unit 14 corresponding to the obtained application ID. Alternatively, the correspondence table T1 may also be a structure containing multiple records R4, in addition to records R1 and R2, where all items of the connector information are set to arbitrary values, i.e., NULL. In this case, if the records R1 and R2 for which a search is desired do not exist, the start-up unit 15 obtains the application ID corresponding to the device information shown in the connection information Con, and starts the termination unit 14 corresponding to the obtained application ID.

[0144] Furthermore, in the vehicle ECU 101 of the embodiments of this disclosure, the termination unit 14 is a structure that performs relay processing to relay communication between a USB device 121 corresponding to the termination unit 14 and the vehicle ECU 111, but it is not limited to this. The termination unit 14 may also be a structure that performs relay processing to relay communication between multiple USB devices 121 and the vehicle ECU 111.

[0145] Furthermore, in the vehicle ECU 101 of the embodiments of this disclosure, the start unit 15 is configured to determine the terminal unit 14 to be started based on the correspondence table T1 in the storage unit 16 and the device information and connector information obtained from the USB communication unit 11, but is not limited thereto. The start unit 15 may also be configured to receive the selection result of the terminal unit 14 to be started from the user instead of determining the terminal unit 14 to be started. More specifically, the start unit 15 receives connection information Con from the USB communication unit 11 and performs processing to display, for example, the device information, purpose, and installation location in the vehicle 1 of the connected USB device 121 on a GUI (Graphical User Interface). The start unit 15 receives the selection result of the terminal unit 14 to be started from the user via the GUI. Then, the start unit 15 starts the terminal unit 14 selected by the user.

[0146] The above embodiments should be considered illustrative rather than limiting in all respects. The scope of the invention is defined not by the foregoing description but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0147] Each process (function) in the above-described embodiments is implemented by a processing circuit including one or more processors. Besides the one or more processors, the processing circuit may also be composed of an integrated circuit combining one or more memories, various analog circuits, and various digital circuits. The one or more memories store programs (commands) that cause the one or more processors to execute the above processes. The one or more processors may execute the above processes according to the programs read from the one or more memories, or they may execute the above processes according to logic circuits pre-designed to execute the above processes. The processors may be various processors suitable for computer control, such as CPUs (Central Processing Units), GPUs (Graphics Processing Units), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and ASICs (Application Specific Integrated Circuits). It should be noted that physically separate processors may also cooperate to execute the above processes. For example, the processors installed on multiple physically separate computers can also cooperate with each other via networks such as LAN (Local Area Network), WAN (Wide Area Network), and the Internet to execute the aforementioned processes. The programs can be installed into the memory from external server devices via the aforementioned network, or they can be transferred from recording media such as CD-ROM (Compact Disc Read Only Memory), DVD-ROM (Digital Versatile Disk Read Only Memory), and semiconductor memory, and installed into the memory.

[0148] The above description includes the following features.

[0149] [Postscript 1]

[0150] An in-vehicle device, which is an in-vehicle device in an in-vehicle network, wherein it comprises: The connection port allows connection to external devices via a USB interface; The detection unit detects the connection of a USB device to the connection port via the connector; The acquisition unit acquires device information related to the USB device detected as connected by the detection unit and connector information related to the connector; Multiple relay units perform relay processing, in which communication between the USB device and other devices in the vehicle network is relayed; The startup unit activates the relay unit among the plurality of relay units that performs the relay processing between the USB device detected as connected by the detection unit and the other devices; and The storage unit stores correspondence information representing the correspondence between each of the plurality of relay units and the device information and the connector information. The relay unit performs at least one of the following during the relay process: termination of communication with the USB device and termination of communication with the other devices. The activation unit determines which relay unit to activate based on the corresponding information, the device information, and the connector information obtained by the acquisition unit. The types of relays vary for each USB device category.

[0151] [Postscript 2]

[0152] An in-vehicle device, which is an in-vehicle device in an in-vehicle network, wherein it comprises: Processing circuitry; and a connection port, enabling connection to external devices via a USB interface. The processing circuit performs the following processing: Detect the connection of the USB device to the connection port via the connector; Obtain device information related to the detected USB device and connector information related to the connector; Relay processing is performed to relay communication between the USB device and other devices in the vehicle network; The relay unit that initiates the relay process among the multiple relay units performing the relay process between the detected connected USB device and the other device. The vehicle-mounted device also includes a storage unit that stores correspondence information representing the correspondence between each of the plurality of relay units and the device information and connector information. In the relay process, the processing circuit performs at least one of the following: terminating communication with the USB device and terminating communication with the other devices. Based on the corresponding information, the obtained device information, and the connector information, the relay unit to be activated is determined.

[0153] Explanation of reference numerals in the attached figures

[0154] 1 vehicle

[0155] 2 Ethernet cables

[0156] 11 USB Communication Department

[0157] 12 ECU Communication Department

[0158] 13th Agency Department

[0159] 14. Terminal

[0160] 15 Start-up Department

[0161] 16 Storage Units

[0162] 101 vehicle ECU

[0163] 111, 111A, 111B vehicle ECU

[0164] USB devices 121, 121A, and 121B

[0165] 131, 131A, 131B USB connectors

[0166] 201 Vehicle Network

[0167] 301 vehicle system

[0168] P1, P1A, P1B communication ports

[0169] P2, P2A, P2B, P2C USB ports

[0170] T1 Correspondence Table.

Claims

1. An in-vehicle device that is an in-vehicle device in an in-vehicle network, wherein, Possessing: a connection port capable of connecting an external device via a USB interface; a detection section that detects connection of a USB device to the connection port via a connector; an acquisition section that acquires device information related to the USB device for which connection was detected by the detection section and connector information related to the connector; a plurality of relay sections that perform a relay process in which communication of the USB device with another device in the in-vehicle network is relayed; an activation section that activates the relay section of the plurality of relay sections that performs the relay process between the USB device for which connection was detected by the detection section and the another device; and a storage section that stores correspondence information indicating a correspondence relationship between each of the plurality of relay sections and the device information and the connector information, the relay section performs at least either of termination of communication with the USB device or termination of communication with the another device in the relay process, the activation section determines the relay section to be activated based on the correspondence information and the device information and the connector information acquired by the acquisition section.

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

3. An in-vehicle system that is an in-vehicle system in an in-vehicle network, wherein an in-vehicle device and a connector are provided, the in-vehicle device is provided with a connection port capable of connecting an external device via a USB interface and a plurality of relay sections that perform a relay process in which a USB device and another device in the in-vehicle network are relayed, 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 is further provided with a storage section that stores correspondence information indicating a correspondence relationship between each of the plurality of relay sections and device information and connector information, the in-vehicle device determines the relay section of the plurality of relay sections to be activated based on the correspondence information and the acquired device information and connector information.

4. The in-vehicle system according to claim 3, wherein the in-vehicle device is provided with a first connection port and a second connection port as the connection port, the connector connected to the first connection port, that is, a first connector, stores first connector information as the connector information, the connector connected to the second connection port, that is, a second connector, stores second connector information as the connector information that is different from the first connector information, 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 that is a communication method in an in-vehicle device in an in-vehicle network, wherein The in-vehicle device includes a connection port that can connect an external device via a USB interface, and a plurality of relay sections that perform a relay process in which communication of a USB device with other devices in the in-vehicle network is relayed, The relay section performs at least either of termination of communication with the USB device or termination of communication with the other devices in the relay process, The communication method includes: a step of detecting connection of a USB device to the connection port via a connector; a step of acquiring device information related to the USB device for which connection is detected and connector information related to the connector; and a step of activating, among the plurality of relay sections, the relay section that performs the relay process between the USB device for which connection is detected and the other devices, The in-vehicle device further includes a storage section that stores correspondence information indicating a correspondence relationship between each of the plurality of relay sections and the device information and the connector information, In the step of activating the relay section, the in-vehicle device determines the relay section to be activated on the basis of the correspondence information and the acquired device information and connector information.

6. A communication program for use in an in-vehicle device in an in-vehicle network, in which The in-vehicle device includes a connection port that can connect an external device via a USB interface, The communication program causes a computer to function as: a detection section that detects connection of a USB device to the connection port via a connector; an acquisition section that acquires device information related to the USB device for which connection is detected by the detection section and connector information related to the connector; a plurality of relay sections that perform a relay process in which communication of the USB device with other devices in the in-vehicle network is relayed; and an activation section that activates, among the plurality of relay sections, the relay section that performs the relay process between the USB devices for which connection is detected by the detection section and the other devices, The in-vehicle device further includes a storage section that stores correspondence information that indicates a correspondence relationship between each of the plurality of relay sections and the device information and the connector information. The relay section performs at least either of termination of communication with the USB device or termination of communication of the other devices in the relay process, The activation section determines the relay section to be activated on the basis of the correspondence information and the device information and the connector information acquired by the acquisition section.

Images