In-vehicle device, communication method, and communication program

Abstract

The vehicle-mounted device includes: a connection port for connecting a USB device; a detection unit for detecting the connection between the USB device and the connection port; an acquisition unit for acquiring USB information; multiple relay units; an activation unit for activating the relay units that perform relay processing between the USB device and other devices; and a storage unit for storing correspondence information indicating the correspondence between each of the multiple relay units and the USB information. In the relay processing, each relay unit, acting as at least one of a terminal communicating with the USB device and a terminal communicating with the other devices, determines which relay unit to activate based on the correspondence information and the USB information acquired by the acquisition unit.

Description

Technical Field

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

[0002] The application claims priority based on Japanese Patent Application No. 2024-9872, filed on January 26, 2024, the entire contents of which are incorporated herein by reference. Background Technology

[0003] Patent Document 1 (International Publication No. 2020 / 179123) discloses a management device that includes: a detection unit that detects the addition of a function unit to a network comprising one or more vehicle-mounted function units; an acquisition unit that acquires the function unit information detected by the detection unit as a new function unit, and the function unit information containing information related to the network structure of the vehicle-mounted function unit as a layer lower than the application layer; and a generation unit that generates structural information of the network, i.e., a new network, further comprising the new function unit, based on the function unit information acquired by the acquisition unit.

[0004] Prior art literature

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

[0006] The problem that the invention aims to solve

[0007] The vehicle-mounted device disclosed herein is a vehicle-mounted device in a vehicle network. The vehicle-mounted device includes: a connection port capable of connecting a USB device via a USB interface; a detection unit for detecting the connection between the USB device and the connection port; an acquisition unit for acquiring USB information related to the USB device detected as connected by the detection unit; multiple relay units for relaying communication between the USB device and other devices in the vehicle network; a startup unit for starting one of the multiple relay units that performs the relaying process 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 multiple relay units and the USB information. In the relaying process, each relay unit serves as at least one of a terminal communicating with the USB device and a terminal communicating with the other devices. The startup unit determines which relay unit to start based on the correspondence information and the USB 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, or as a system that includes the in-vehicle device. Attached Figure Description

[0009] 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.

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

[0011] Figure 3 This is a diagram showing a list of USB device categories representing USB devices according to embodiments of the present invention.

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

[0013] Figure 5 This is a flowchart illustrating an example of the operational steps of an on-board ECU when it begins relay processing according to an embodiment of this disclosure.

[0014] Figure 6 This is a flowchart illustrating an example of the operating steps of the vehicle-mounted ECU starting the terminal unit according to an embodiment of this disclosure.

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

[0016] In the past, 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] It is anticipated that, beyond the technology described in Patent Document 1, a technology will be able 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 with a simple structure.

[0019] This disclosure was made to address the aforementioned issues, and its purpose is to provide an in-vehicle device, communication method, and communication program 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 in a simple structure.

[0020] The effect 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 listed for explanation.

[0024] (1) The vehicle-mounted device according to the embodiments of the present disclosure is a vehicle-mounted device in a vehicle network. The vehicle-mounted device includes: a connection port that can connect a USB device via a USB interface; a detection unit that detects the connection between the USB device and the connection port; an acquisition unit that acquires USB information related to the USB device that has been detected as connected by the detection unit; a plurality of relay units that perform relay processing to relay communication between the USB device and other devices in the vehicle network; a startup unit that starts 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 a storage unit that stores correspondence information indicating the correspondence between each of the plurality of relay units and the USB information. The relay unit serves as at least one of a terminal communicating with the USB device and a terminal communicating with the other devices in the relay processing. The startup unit determines the relay unit to be started based on the correspondence information and the USB information acquired by the acquisition unit.

[0025] With this structure, the relay unit can be activated based on corresponding information pre-stored in the storage unit to perform relay processing between USB devices and other devices. Therefore, when a USB device is connected to the connection port, communication between the USB device and other devices can be initiated without user intervention. Thus, it is possible to relay communication between external devices connected to the vehicle network via the USB interface and other devices in the vehicle network with a simple structure.

[0026] (2) Based on (1) above, the vehicle-mounted device may also have multiple connection ports, and the acquisition unit may acquire the USB information for identifying the connection port among the multiple connection ports that is connected to the USB device.

[0027] With this structure, when multiple USB devices of the same model are connected to multiple connection ports, the relay unit can be activated according to the different connection ports and corresponding USB devices.

[0028] (3) Based on (1) or (2) above, the acquisition unit may acquire multiple types of USB information for a USB device. If there is no relay unit in the corresponding information that corresponds to all types of USB information, the startup unit may determine the relay unit to be started based on a portion of the types of USB information.

[0029] This structure increases the flexibility in choosing the types of USB devices and connection ports when connecting USB devices to the connection port, and enables the relay unit to perform relay processing between the USB device connected to the connection port and other devices.

[0030] (4) Based on (3) above, the storage unit may store a correspondence table as the correspondence information. The correspondence table contains a composite key consisting of multiple items corresponding to the various USB information, and the values ​​of some of the items in the composite key are arbitrary.

[0031] With this structure, even in the absence of a relay unit that corresponds to all types of USB information, a mapping table can be used to easily select and activate a relay unit capable of relaying USB devices connected to the connection port to other devices.

[0032] (5) Based on any one of (1) to (4) above, the vehicle-mounted device may also have multiple relay units of the same type, and the storage unit stores the corresponding information that further represents the correspondence between each of the multiple relay units of the same type and additional information that can identify the relay unit.

[0033] With this structure, when the same type of relay is activated, additional information can be used to enable other devices communicating with a USB device to easily identify the relay among the same type of relays that performs relay processing with that USB device.

[0034] (6) The communication method of the present disclosure is a communication method of a vehicle-mounted device in a vehicle network. The vehicle-mounted device includes: a connection port that can connect to a USB device via a USB interface; and a plurality of relay units that perform relay processing to relay communication between the USB device and other devices in the vehicle network. The relay units serve as at least one of a terminal communicating with the USB device and a terminal communicating with the other devices in the relay processing. The communication method includes the following steps: detecting the connection between the USB device and the connection port; obtaining USB information related to the detected connected USB device; and activating the relay unit among the plurality of relay units that performs the relay processing between the detected connected USB device and the other devices. 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 USB information. In the step of activating the relay unit, the relay unit to be activated is determined based on the correspondence information and the obtained USB information.

[0035] 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 the connection port, communication between the USB device and other devices can be initiated without user intervention. Consequently, 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.

[0036] (7) The communication program of the present disclosure is used in an in-vehicle device in an in-vehicle network. The in-vehicle device has a connection port that can connect a USB device via a USB interface. The communication program is a program for enabling a computer to function as a detection unit, an acquisition unit, multiple relay units, and a startup unit. The detection unit detects the connection between the USB device and the connection port. The acquisition unit acquires USB information related to the USB device detected as connected by the detection unit. The multiple relay units perform relay processing to relay communication between the USB device and other devices in the in-vehicle network. The activation unit activates the relay unit among the plurality of relay units that performs the relay processing between the USB device and the other devices detected by the detection unit. 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 USB information. In the relay processing, the relay unit serves as at least one of a terminal communicating with the USB device and a terminal communicating with the other devices. The activation unit determines which relay unit to activate based on the correspondence information and the USB information obtained by the acquisition unit.

[0037] With this structure, the relay unit can be activated based on corresponding information pre-stored in the storage unit to perform relay processing between USB devices and other devices. Therefore, when a USB device is connected to the connection port, communication between the USB device and other devices can be initiated without user intervention. Thus, it is possible to relay communication between external devices connected to the vehicle network via the USB interface and other devices in the vehicle network with a simple structure.

[0038] Hereinafter, embodiments of the present disclosure will be described using the accompanying drawings. Furthermore, the same or equivalent parts in the drawings will be labeled with the same reference numerals, and their descriptions will not be repeated. Additionally, at least some of the embodiments described below may be combined arbitrarily.

[0039] Structure and basic movements

[0040] 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 and on-board ECUs 111A and 111B, which are also on-board ECUs 111. The vehicle system 301 is mounted on the vehicle 1. The on-board ECUs 101 and 111 constitute the vehicle network 201. Alternatively, the vehicle system 301 may also have a structure with one or more on-board ECUs 111.

[0041] 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.

[0042] The vehicle ECU 101 has communication ports P1A and P1B and USB (registered trademark) ports P2A, P2B, and P2C. Hereinafter, communication ports P1A and P1B will be referred to as communication port P1, and USB ports P2A, P2B, and P2C will be referred to as USB port P2. USB port P2 is an example of a connection port. The port numbers of USB ports P2A, P2B, and P2C are "N001", "N002", and "N003", respectively. Alternatively, the vehicle ECU 101 may have one or more communication ports P1. Furthermore, the vehicle ECU 101 may also have two or more USB ports P2.

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

[0044] Vehicle ECUs 111A and 111B are connected to communication ports P1A and P1B in vehicle ECU 101 via Ethernet cable 2, respectively. Furthermore, vehicle ECU 111 is not limited to a structure where it is connected to vehicle ECU 101 via Ethernet cable 2; it can also be connected via communication lines conforming to other standards, such as CAN (Controller Area Network) (registered trademark) and FlexRay (registered trademark).

[0045] Research topic

[0046] 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 with a simple structure.

[0047] For example, when a USB device is connected to a personal computer's USB port, an application selected by the user can be launched. This application communicates directly with the USB device, thereby exchanging communication data.

[0048] 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, it is conceivable that the USB device 121 and the vehicle ECU 111 exchange communication data Dt via the vehicle ECU 101. 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.

[0049] 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, after the vehicle 1 is manufactured and the USB device 121 is installed on the USB port P2 of the vehicle ECU 101, the application corresponding to the USB device 121 can be automatically selected and started from among the multiple relay applications without user operation, thus initiating communication between the USB device 121 and the vehicle ECU 111.

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

[0051] (Vehicle ECU)

[0052] Figure 2 This is a diagram illustrating the structure of an on-board ECU according to an embodiment of this 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 terminal units 14. The USB communication unit 11 is an example of a detection unit and an example of an acquisition unit. The terminal 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 (circuit) including one or more processors. The storage unit 16 is, for example, a non-volatile memory included in the aforementioned processing circuit.

[0053] exist Figure 2 In the example shown, USB devices 121A and 121B, which are USB devices 121, are connected to USB ports P2A and P2B, respectively. For example, USB devices 121A and 121B are animation cameras. USB device 121 and vehicle ECU 111 transmit communication data Dt via vehicle ECU 101.

[0054] Figure 3 This is a diagram showing a list of USB device categories representing the USB devices of embodiments of this disclosure. Figure 3 This indicates the correspondence between the category name of a USB device category and the USB device 121 that conforms to that category.

[0055] Reference Figure 3 USB devices 121 are classified into a specific USB device category according to the standards defined by USB-IF (Implementers Forum). For example, USB devices 121A and 121B, which function as video cameras, are classified into the USB device category named "Video". USB devices 121, which function as microphones, are classified into the USB device category named "Audio". USB devices 121, which function as keyboards, are 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.

[0056] USB device 121 stores USB information associated with it. For example, USB device 121 stores a category number indicating the USB device category to which it belongs, a manufacturer ID indicating the manufacturer of the USB device 121, and a product ID assigned by the manufacturer to each product of the USB device 121 as USB information.

[0057] 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.

[0058] As an example, the types of the multiple terminal units 14 in the agent unit 13 vary according to each USB device category. That is, the agent unit 13 contains the same number of terminal units 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 terminal unit 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.

[0059] For example, agent unit 13 contains multiple terminal units 14 of the same type. More specifically, terminal units 14 have the same application ID for each type. Agent unit 13 contains multiple terminal units 14 with the same application ID.

[0060] (Connectivity Detection)

[0061] The USB communication unit 11 detects the connection between the USB device 121 and the USB port P2. More specifically, when the USB device 121 is connected to the USB port P2, it sends a connection notification to the vehicle ECU 101. Upon receiving the connection notification from the USB device 121 via the USB port P2, the USB communication unit 11 recognizes that the USB device 121 is connected to the USB port P2.

[0062] The USB communication unit 11 acquires USB information related to the detection of a USB device 121 connected to the USB port P2. For example, the USB communication unit 11 acquires the port number of the USB port P2 used to identify the USB device 121 connected to the USB device among a plurality of USB ports P2 as USB information. In addition, for example, the USB communication unit 11 acquires various types of USB information for a single USB device 121.

[0063] More specifically, when the USB communication unit 11 recognizes that the USB device 121 is connected to the USB port P2, it sends a device information request to the USB device 121 via the USB port P2.

[0064] When the USB device 121 receives a device information request from the vehicle ECU 101, it sends a device information response containing the category number, manufacturer ID, and product ID of the USB device 121 to the vehicle ECU 101 in response to the device information request.

[0065] When the USB communication unit 11 receives a device information response from the USB device 121 via the USB port P2, it obtains the port number of the USB port P2. The USB communication unit 11 obtains the category number, manufacturer ID, and product ID from the received device information response. The USB communication unit 11 generates connection information Con representing the obtained port number, category number, manufacturer ID, and product ID, and outputs the generated connection information Con to the startup unit 15.

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

[0067] The start unit 15 starts the terminal unit 14 among the multiple terminal units 14 that performs relay processing between the connected USB device 121 detected by the USB communication unit 11 and the vehicle ECU 111.

[0068] Figure 4 This diagram illustrates an example of a mapping table stored in the storage unit of an onboard ECU according to an embodiment of this disclosure. (Refer to...) Figure 4 The storage unit 16 stores a correspondence table T1 that represents the correspondence between each of the multiple terminal units 14 and the USB information. The correspondence table T1 is an example of the correspondence information.

[0069] For example, table T1 contains a composite primary key consisting of multiple items corresponding to the various USB information types mentioned above. More specifically, table T1 is a table showing the correspondence between a composite primary key consisting of items such as category number, port number, manufacturer ID, and product ID, and an application ID.

[0070] The values ​​of some items in the composite primary key of table T1 are arbitrary. More specifically, table T1 includes: multiple records R1 where all items in the composite primary key are set to predetermined values; multiple records R2 where each item of the manufacturer ID and product ID is set to an arbitrary value, i.e., NULL; multiple records R3 where the port number is set to an arbitrary value, i.e., NULL; and multiple records R4 where each item of the port number, manufacturer ID, and product ID is set to an arbitrary value, i.e., NULL.

[0071] For example, the correspondence table T1 also represents the correspondence between each of the multiple terminal units 14 of the same type and the additional information that can identify the terminal unit 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 includes 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.

[0072] The startup unit 15 determines which terminal unit 14 to start based on the correspondence table T1 in the storage unit 16 and the USB 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.

[0073] The startup unit 15 retrieves a record R1 from among multiple records R1 in the correspondence table T1 that contains a composite primary key consistent with the port number, category number, manufacturer ID, and product ID represented by the connection information Con received from the USB communication unit 11. If a record R1 exists as the search target, the startup unit 15 obtains the application ID contained in that record R1. The startup unit 15 then starts the terminal unit 14 with the obtained application ID. Specifically, for example, if the port number, category number, manufacturer ID, and product ID represented by the connection information Con are “C002”, “N002”, “V002”, and “P002” respectively, the startup unit 15 starts the terminal unit 14 with the application ID “AP004”.

[0074] For example, if there is no terminal unit 14 in the correspondence table T1 that corresponds to all types of USB information, the startup unit 15 determines which terminal unit 14 to start based on a subset of USB information.

[0075] More specifically, if no record R1 is found, the startup unit 15 retrieves a record R2 from among multiple records R2 in the correspondence table T1 that contains a composite primary key consistent with the port number and category number shown in the connection information Con received from the USB communication unit 11. If a record R2 is found, the startup unit 15 obtains the application ID contained in that record R2. The startup unit 15 then starts the terminal unit 14 with the obtained application ID. Specifically, for example, if the port number, category number, manufacturer ID, and product ID shown in the connection information Con are “C001”, “N001”, “V051”, and “P051”, respectively, the startup unit 15 starts the terminal unit 14 with the application ID “AP011”.

[0076] Furthermore, if no records R1 or R2 are found as the search target, the startup unit 15 searches for a record R3 containing a composite primary key that matches the category number, manufacturer ID, and product ID shown in the connection information Con received from the USB communication unit 11 from among multiple records R3 in the correspondence table T1. If a record R3 is found as the search target, the startup unit 15 obtains the application ID contained in that record R3. The startup unit 15 then starts the terminal unit 14 with the obtained application ID. Specifically, for example, if the port number, category number, manufacturer ID, and product ID shown in the connection information Con are "C001", "N051", "V011", and "P011" respectively, the startup unit 15 starts the terminal unit 14 with the application ID "AP021".

[0077] Furthermore, if no records R1, R2, or R3 are found as the search target, the startup unit 15 searches for a record R4 containing a composite primary key that matches the category number shown in the connection information Con received from the USB communication unit 11 from among multiple records R4 in the correspondence table T1. If a record R4 is found as the search target, the startup unit 15 obtains the application ID contained in that record R4. The startup unit 15 then starts the terminal unit 14 with the obtained application ID. Specifically, if the port number, category number, manufacturer ID, and product ID shown in the connection information Con are “C001”, “N051”, “V051”, and “P051”, respectively, the startup unit 15 starts the terminal unit 14 with the application ID “AP031”.

[0078] When the startup unit 15 starts the terminal unit 14, it retrieves the service ID and option ID corresponding to the application ID of the terminal unit 14 from the correspondence table T1. Additionally, when the startup unit 15 starts the terminal unit 14, it outputs the connection information Con received from the USB communication unit 11 to the started terminal unit 14.

[0079] Terminal 14 receives connection information Con from startup 15 and holds the received connection information Con.

[0080] (Example of terminal startup)

[0081] For example, the category number of USB devices 121A and 121B is "C001", the manufacturer ID of USB devices 121A and 121B is "V001", and the product ID of USB devices 121A and 121B is "P001". Additionally, as mentioned above, the port numbers of USB ports P2A and P2B are "N001" and "N002", respectively.

[0082] In this case, the startup unit 15 receives connection information Con from the USB communication unit 11 along with the USB device 121A connected to the USB port P2A. Based on the received connection information Con and the correspondence table T1, the terminal unit 14, i.e., the terminal unit 14A, with the application ID "AP001" is started.

[0083] Additionally, the startup unit 15 receives connection information Con from the USB communication unit 11 along with the USB device 121B and the USB port P2B. Based on the received connection information Con and the correspondence table T1, it starts the terminal unit 14, i.e., the terminal unit 14B, which has the application ID "AP001".

[0084] When the terminal unit 14 is started, the startup unit 15 provides the service using the USB device 121 to the vehicle ECU 111 using the OfferService message according to SOME / IP (Scalable service-oriented middleware over IP).

[0085] More specifically, when the terminal unit 14A is started, the start unit 15 obtains the service ID "X001" corresponding to the application ID of the terminal unit 14A and the option ID "Y001" corresponding to the application ID of the terminal unit 14A from the correspondence table T1. The start unit 15 generates an OfferService message M1A containing 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.

[0086] 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 receive the service provided by the obtained service ID, the vehicle ECU 111A sends a FindService message M2A to the vehicle ECU 101, which contains the service ID and the ID of the vehicle ECU 111A.

[0087] 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 terminal unit 14A.

[0088] Furthermore, when the terminal unit 14B is started, the startup unit 15 obtains the service ID "X002" corresponding to the application ID of the terminal unit 14B and the option ID "Y002" corresponding to the application ID of the terminal unit 14A from the correspondence table T1. The startup unit 15 generates an OfferService message M1B containing 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.

[0089] The vehicle ECU 111 receives an OfferService message M1B from the vehicle ECU 101 and obtains the service ID from the received OfferService message M1B. For example, in order to receive the service provided by the obtained service ID, the vehicle ECU 111B sends a FindService message M2B containing the service ID and the ID of the vehicle ECU 111B to the vehicle ECU 101.

[0090] 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 terminal unit 14B.

[0091] (Relay processing)

[0092] Terminal 14 performs relay processing to relay the communication between the USB device 121, which is detected as connected by USB communication unit 11, and the vehicle ECU 111 in vehicle network 201.

[0093] More specifically, the terminal 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.

[0094] In addition, the terminal 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.

[0095] In relay processing, terminal unit 14 serves as a terminal for communicating with USB device 121 and with vehicle ECU 111. That is, terminal unit 14 performs terminal processing for USB communication protocols and terminal processing for communication protocols in the vehicle network.

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

[0097] USB device 121 generates communication data Dt, i.e., communication data Dt1, with the vehicle ECU 111 as the destination. USB device 121 generates a frame F1 that conforms to the USB standard, containing the communication data Dt1 and with the vehicle ECU 111 as the destination, and sends the generated frame F1 to the vehicle ECU 101.

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

[0099] In the proxy unit 13, the terminal unit 14 corresponding to the USB device 121, the source of the frame F1, receives the frame F1 from the USB communication unit 11 and performs terminal processing of the USB communication protocol. More specifically, as terminal processing, the terminal 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 and the USB port P2.

[0100] Furthermore, the terminal 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, which is the destination, via the ECU communication unit 12 and the corresponding communication port P1.

[0101] For example, when the vehicle ECU 111 that received frame F2 sends a response frame, the terminal unit 14, as a terminal, also receives the response frame via the ECU communication unit 12 and the communication port P1.

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

[0103] The vehicle ECU 111 generates communication data Dt, or communication data Dt2, destined for the USB device 121. The vehicle ECU 111 generates an Ethernet frame F2 containing the communication data Dt2, destined for the USB device 121, and sends the generated frame F2 to the vehicle ECU 101.

[0104] 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.

[0105] In the agent unit 13, the terminal unit 14, which corresponds 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 terminal processing of the communication protocol of the vehicle network. More specifically, as terminal processing, the terminal 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.

[0106] Furthermore, the terminal 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, which is the destination, via the USB communication unit 11 and the corresponding USB port P2.

[0107] For example, when the terminal unit 14 receives a response frame from the USB device 121 that received frame F1, it also receives the response frame via the USB communication unit 11 and the USB port P2 as a terminal.

[0108] Action flow

[0109] Figure 5 This is a flowchart illustrating an example of the operational steps taken when an on-board ECU begins relay processing according to an embodiment of this disclosure.

[0110] 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 port P2 (yes in step S11), it recognizes that the USB device 121 and the USB port P2 are connected, and sends a device information request to the USB device 121 via the USB port P2 (step S12).

[0111] Next, the vehicle ECU 101 waits for the arrival of the device information response (no in step S13). When the device information response is received from the USB device 121 via the USB port P2 (yes in step S13), connection information Con representing the port number, category number, manufacturer ID and product ID is generated (step S14).

[0112] Next, the vehicle ECU 101 starts the terminal unit 14 corresponding to the USB information represented by the connection information Con based on the correspondence table T1 in the storage unit 16 (step S15).

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

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

[0115] Figure 6 This is a flowchart illustrating an example of the operational steps of the vehicle-mounted ECU starting the terminal unit according to an embodiment of this disclosure. Figure 6 It shows Figure 5 Details of step S15 in the process.

[0116] Reference Figure 6 First, the vehicle ECU 101 retrieves a record R1 containing a composite primary key that matches the port number, category number, manufacturer ID, and product ID represented by the connection information Con from multiple records R1 in the corresponding table T1 (step S21).

[0117] Next, if there is a record R1 that is the target of retrieval (yes in step S22), the vehicle ECU 101 obtains the application ID contained in the record R1 and starts the terminal unit 14 with the obtained application ID (step S23).

[0118] On the other hand, if there is no record R1 as the retrieval target (no in step S22), the vehicle ECU 101 retrieves a record R2 containing a composite primary key that is consistent with the port number and category number represented by the connection information Con from multiple records R2 in the corresponding table T1 (step S24).

[0119] Next, if there is a record R2 that is the target of retrieval (yes in step S25), the vehicle ECU 101 obtains the application ID contained in the record R2 and starts the terminal unit 14 with the obtained application ID (step S23).

[0120] On the other hand, if there is no record R2 as the retrieval target (no in step S25), the vehicle ECU 101 retrieves a record R3 containing a composite primary key that is consistent with the category number, manufacturer ID and product ID represented by the connection information Con from multiple records R3 in the corresponding table T1 (step S26).

[0121] Next, if there is a record R3 that is the target of retrieval (yes in step S27), the vehicle ECU 101 obtains the application ID contained in the record R3 and starts the terminal unit 14 with the obtained application ID (step S23).

[0122] On the other hand, if there is no record R3 as the retrieval target (no in step S27), the vehicle ECU 101 retrieves a record R4 containing a composite primary key that is consistent with the category number represented by the connection information Con from a plurality of records R4 in the corresponding table T1 (step S28).

[0123] Next, if there is a record R4 that is the target of retrieval (yes in step S29), the vehicle ECU 101 obtains the application ID contained in the record R4 and starts the terminal unit 14 with the obtained application ID (step S23).

[0124] On the other hand, if there is no record R4 to be searched (no in step S29), the vehicle ECU 101 will not start the terminal unit 14 and will end the process.

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

[0126] Reference Figure 7 First, when the USB device 121A is connected to the USB port P2A in the vehicle ECU 101, it sends a connection notification to the vehicle ECU 101 (step S31).

[0127] Next, when the vehicle ECU 101 receives a connection notification from the USB device 121A via the USB port P2A, it recognizes that the USB device 121A is connected to the USB port P2A and sends a device information request to the USB device 121A via the USB port P2A (step S32).

[0128] Next, the USB device 121A sends a device information response to the vehicle ECU 101, including the category number, manufacturer ID, and product ID of the USB device 121A, as a response to the device information request (step S33).

[0129] Next, the vehicle ECU 101 activates the terminal unit 14A, which corresponds to the category number, manufacturer ID, product ID of the USB device 121A, and port number of the USB port P2A, based on the correspondence table T1 in the storage unit 16 (step S34).

[0130] Next, the vehicle ECU 101 sends an OfferService message M1A to the vehicle ECU 111. The OfferService message M1A contains a service ID corresponding to the application ID of the terminal unit 14A, namely “X001”, and an option ID corresponding to the application ID of the terminal unit 14A, namely “Y001” (step S35).

[0131] Next, for example, the vehicle ECU 111A in the vehicle ECU 111A and 111B that received the OfferService message M1A sends a FindService message M2A to the vehicle ECU 101. The FindService message M2A contains the service ID corresponding to the application ID of the terminal unit 14A, namely "X001", and the ID of the vehicle ECU 111A (step S36).

[0132] Next, the vehicle ECU 101 receives the FindService message M2A from the vehicle ECU 111A and begins relay processing for the communication between the USB device 121A and the vehicle ECU 111A (step S37).

[0133] Next, the USB device 121A receives, for example, a predetermined notification of receiving the FindService message M2A from the vehicle ECU 101, and sends a frame F1 to the vehicle ECU 111A as the destination (step S38).

[0134] Next, the vehicle ECU 101 receives frame F1 from the USB device 121A and performs terminal processing of the USB communication protocol. More specifically, as terminal processing, the vehicle ECU 101 obtains communication data Dt1 from frame F1 and sends a response frame to the USB device 121A (step S39).

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

[0136] Next, for example, the vehicle ECU 111A sends frame F2 to the vehicle ECU 101 with the USB device 121A as the destination (step S41).

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

[0138] Next, the vehicle ECU 101 sends a frame F containing the acquired communication data Dt2 to the vehicle ECU 111A (step S43).

[0139] Next, when the USB device 121B is connected to the USB port P2B in the vehicle ECU 101, it sends a connection notification to the vehicle ECU 101 (step S44).

[0140] Next, when the vehicle ECU 101 receives a connection notification from the USB device 121B via the USB port P2B, it recognizes that the USB device 121B is connected to the USB port P2B and sends a device information request to the USB device 121B via the USB port P2B (step S45).

[0141] Next, the USB device 121B sends a device information response to the vehicle ECU 101, which includes the category number, manufacturer ID and product ID of the USB device 121B, as a response to the device information request (step S46).

[0142] Next, the vehicle ECU 101 activates the terminal unit 14B, which corresponds to the category number, manufacturer ID, product ID of the USB device 121B, and port number of the USB port P2B, based on the correspondence table T1 in the storage unit 16 (step S47).

[0143] Next, the vehicle ECU 101 sends an OfferService message M1B to the vehicle ECU 111. The OfferService message M1B contains a service ID corresponding to the application ID of the terminal unit 14B, namely “X002”, and an option ID corresponding to the application ID of the terminal unit 14A, namely “Y002” (step S48).

[0144] Next, for example, vehicle ECU 111B, which received the OfferService message M1B, sends a FindService message M2B to vehicle ECU 101. The FindService message M2B contains the service ID corresponding to the application ID of terminal unit 14B, namely "X002", and the ID of vehicle ECU 111B (step S49).

[0145] Next, the vehicle ECU 101 receives the FindService message M2B from the vehicle ECU 111B and begins relay processing for the communication between the USB device 121B and the vehicle ECU 111B (step S50).

[0146] Next, the USB device 121B receives, for example, a predetermined notification accompanying the receipt of the FindService message M2B from the vehicle ECU 101, and sends a frame F1 to the vehicle ECU 111B as the destination (step S51).

[0147] Next, the vehicle ECU 101 receives frame F1 from the USB device 121B and performs terminal processing of the USB communication protocol. More specifically, as terminal processing, the vehicle ECU 101 obtains communication data Dt1 from frame F1 and sends a response frame to the USB device 121B (step S52).

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

[0149] Next, for example, the vehicle ECU 111B sends frame F2 to the vehicle ECU 101 with the USB device 121B as the destination (step S54).

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

[0151] Next, the vehicle ECU 101 sends a frame F1 containing the acquired communication data Dt2 to the vehicle ECU 111B (step S56).

[0152] Alternatively, in the vehicle system 301, any one of the above steps S38, S39, S40, S51, S52, S53 and S41, S42, S43, S54, S55, S56 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 terminal unit 14 serves as the terminal for communication with the USB device 121, but not as the terminal for communication with the vehicle ECU 111.

[0153] 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 terminal unit 14 serves as the terminal for communication with the vehicle ECU 111, but not as the terminal for communication with the USB device 121.

[0154] Furthermore, the vehicle ECU 101 of the present disclosure has a structure with multiple USB ports P2, but it is not limited to this. The vehicle ECU 101 may also have a structure with only one USB port P2. In this case, the USB communication unit 11 does not obtain the port number of the USB port P2 to which the USB device 121 is connected, but instead generates connection information Con indicating the category number, manufacturer ID, and product ID and outputs it to the start unit 15.

[0155] Furthermore, in the vehicle ECU 101 of the embodiments of this disclosure, the start unit 15 is configured to start the terminal unit 14 corresponding to a portion of the USB information when there is no terminal unit 14 corresponding to all types of USB information in the correspondence table T1, but it is not limited to this. The start unit 15 may also be configured not to start the terminal unit 14 when there is no terminal unit 14 corresponding to all types of USB information in the correspondence table T1.

[0156] Furthermore, in the vehicle ECU 101 of the embodiments of this disclosure, the storage unit 16 is structured to store a correspondence table T1 containing records R2, R3, and R4, but it is not limited to this. The storage unit 16 may also be structured to store a correspondence table T1 that does not contain records R2, R3, and R4. In this case, the startup unit 15 may also start the terminal unit 14 having the application ID contained in the record R1 if there is a record R1 in which a predetermined number or more items in each item of the composite primary key of the correspondence table T1 are consistent.

[0157] Furthermore, in the vehicle ECU 101 of the embodiments of this disclosure, the agent unit 13 is a structure that includes multiple terminal units 14 of the same type, but it is not limited to this. The agent unit 13 may also be a structure that includes one terminal unit 14 for each type. In this case, the storage unit 16 may also be a structure that stores a mapping table T1 that does not include service IDs and option IDs.

[0158] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the USB device 121 is directly connected to the USB port P2 in the vehicle ECU 101, but it is not limited to this. The USB device 121 may also be connected to the USB port P2 in the vehicle ECU 101 via a hub that includes a USB port. In addition, the correspondence table T1 in the storage unit 16 of the vehicle ECU 101 may also be a structure that includes the port number of the USB port of the hub connected to the USB port of the USB device 121.

[0159] The above embodiments should be considered illustrative and not restrictive 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.

[0160] Each process (function) in the above-described embodiments is implemented by a processing circuit (circuit) including one or more processors. In addition to the one or more processors, the processing circuit may also be composed of an integrated circuit that combines 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). Alternatively, multiple physically separate processors may cooperate to execute the above processes. For example, the processors of multiple physically separate computers can cooperate to execute the aforementioned processes via networks such as LANs (Local Area Networks), WANs (Wide Area Networks), and the Internet. The programs can be installed in the memory from external server devices via the aforementioned network, or they can be circulated in storage media such as CD-ROMs (Compact Disc Read Only Memory), DVD-ROMs (Digital Versatile Disc Read Only Memory), and semiconductor memory, and installed from these storage media into the memory.

[0161] The above description includes the following features.

[0162] Postscript 1

[0163] An in-vehicle device, which is an in-vehicle device in an in-vehicle network, the in-vehicle device comprising: The connection port allows USB devices to be connected via a USB interface; The testing department tests the connection between the aforementioned USB device and the aforementioned connection port; The acquisition unit acquires USB information related to the USB device that has been detected as connected by the detection unit. Multiple relay units perform relay processing to relay communication between the aforementioned USB device and other devices in the aforementioned vehicle network; The startup unit activates the relay unit among the plurality of relay units that performs the relay processing between the USB device and the other devices detected by the detection unit as connected; and The storage unit stores correspondence information representing the correspondence between each of the plurality of relay units and the USB information. In the aforementioned relay process, the relay unit serves as at least one of the terminals communicating with the aforementioned USB device and the terminals communicating with the aforementioned other devices. The aforementioned startup unit determines which relay unit to start based on the aforementioned corresponding information and the aforementioned USB information obtained by the aforementioned acquisition unit. The types of relay units mentioned above vary depending on the category of USB device.

[0164] Appendix 2

[0165] A vehicle-mounted device, which is a vehicle-mounted device in a vehicle network. The aforementioned vehicle-mounted device has processing circuitry and a connection port that can connect to USB devices via a USB interface. The aforementioned processing circuit detects the connection between the aforementioned USB device and the aforementioned connection port. Obtain USB information related to the detected USB devices. Relay processing is performed to relay communication between the aforementioned USB device and other devices in the aforementioned vehicle network. The relay unit that performs the relay processing between the connected USB device and the other devices is activated among the multiple relay units that perform the aforementioned relay processing. The aforementioned vehicle-mounted device also includes a storage unit, which stores correspondence information representing the correspondence between each of the plurality of relay units and the aforementioned USB information. In the aforementioned relay process, the aforementioned processing circuit serves as at least one of the terminals communicating with the aforementioned USB device and the terminals communicating with the aforementioned other devices. The processing circuit determines which relay unit to activate based on the corresponding information and the obtained USB information.

[0166] Explanation of reference numerals in the attached figures

[0167] 1 vehicle

[0168] 2 Ethernet cables

[0169] 11 USB Communication Department

[0170] 12 ECU Communication Department

[0171] 13. Agency Department

[0172] 14 Terminal Department

[0173] 15. Start-up section

[0174] 16 Storage Department

[0175] 101 Vehicle ECU

[0176] 111, 111A, 111B Vehicle ECU

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

[0178] 201 Vehicle Network

[0179] 301 Vehicle In-Flight System

[0180] P1, P1A, P1B communication ports

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

[0182] T1 Correspondence Table.

Claims

1. A vehicle-mounted device, which is a vehicle-mounted device in a vehicle network, the vehicle-mounted device comprising: The connection port allows USB devices to be connected via a USB interface; The detection unit detects the connection between the USB device and the connection port; The acquisition unit acquires USB information related to the USB device that has been detected as connected by the detection unit. Multiple relay units perform relay processing to relay communication between the USB device and other devices in the vehicle network; The startup unit activates the relay unit among the plurality of relay units that performs the relay processing between the USB device that has been 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 USB information. The relay unit serves as at least one of the following in the relay process: a terminal communicating with the USB device and a terminal communicating with the other devices. The startup unit determines which relay unit to start based on the corresponding information and the USB information obtained by the acquisition unit.

2. The vehicle-mounted device according to claim 1, wherein, The vehicle-mounted device has multiple connection ports. The acquisition unit acquires the USB information used to identify the connection port among the plurality of connection ports that is connected to the USB device.

3. The vehicle-mounted device according to claim 1 or 2, wherein, The acquisition unit acquires various USB information for a single USB device. If there is no relay unit in the corresponding information that corresponds to all types of USB information, the startup unit determines which relay unit to start based on a subset of the types of USB information.

4. The vehicle-mounted device according to claim 3, wherein, The storage unit stores a correspondence table as the correspondence information. The correspondence table contains a composite primary key consisting of multiple items that correspond to the various USB information respectively, and the values ​​of some of the items in the composite primary key are arbitrary.

5. The vehicle-mounted device according to any one of claims 1 to 4, wherein, The vehicle-mounted device has multiple relay units of the same type. The storage unit stores correspondence information that further represents the correspondence between each of the plurality of relay units of the same type and additional information capable of identifying the relay unit.

6. A communication method, which is a communication method for vehicle-mounted devices in a vehicle network. The vehicle-mounted device includes: a connection port for connecting a USB device via a USB interface; and multiple relay units for relaying communication between the USB device and other devices in the vehicle network. The relay unit serves as at least one of the following in the relay process: a terminal communicating with the USB device and a terminal communicating with the other devices. The communication method includes the following steps: Detect the connection between the USB device and the connection port; Obtain USB information related to the detection of the connected USB device; and The relay unit among the plurality of relay units that performs the relay processing for detecting the connected USB device and the other devices is activated. 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 USB information. In the step of activating the relay unit, the relay unit to be activated is determined based on the corresponding information and the obtained USB information.

7. A communication program used in an in-vehicle device within an in-vehicle network. The vehicle-mounted device has a connection port that can connect to a USB device via a USB interface. The communication program is used to enable the computer to function as a detection unit, acquisition unit, multiple relay units, and startup unit. The detection unit detects the connection between the USB device and the connection port. The acquisition unit acquires USB information related to the USB device that has been detected as connected by the detection unit. The plurality of relay units perform relay processing to relay communication between the USB device and other devices in the vehicle network; The activation 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. 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 USB information. The relay unit serves as at least one of the following in the relay process: a terminal communicating with the USB device and a terminal communicating with the other devices. The startup unit determines which relay unit to start based on the corresponding information and the USB information obtained by the acquisition unit.

Images