In-vehicle device, communication method, and communication program

The in-vehicle device with class-specific relay units addresses the challenge of complex USB device communication by detecting and converting data formats, ensuring efficient relay with reduced resource usage.

WO2025158900A1PCT designated stage Publication Date: 2025-07-31SUMITOMO ELECTRIC INDUSTRIES LTD +3
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2025/000301
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-01-26
Filing Date
2025-01-08
Publication Date
2025-07-31

AI Technical Summary

Technical Problem

Existing technologies lack a simple configuration for relaying communication between external USB devices connected to an in-vehicle network and other devices within the network, requiring numerous relay applications for various USB device types.

Method used

An in-vehicle device with a USB interface and relay units tailored for different USB device classes, capable of detecting connections, relaying communication, and converting data formats and protocols as needed, reducing the number of required relay unit types.

Benefits of technology

Enables efficient communication relay between USB devices and in-vehicle systems with a simplified configuration by using class-specific relay units, minimizing resource usage and processing load.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2025000301_31072025_PF_FP_ABST
    Figure JP2025000301_31072025_PF_FP_ABST
Patent Text Reader

Abstract

This in-vehicle device is provided with: a connection port to which a USB device can be connected; a detection unit that detects a connection of the USB device; and a plurality of relay units that perform relay processing that relays communication between the USB device and other devices in an in-vehicle network. The types of the plurality of relay units are different for each USB device class. The relay unit can perform the relay processing that relays the communication between the USB device belonging to the corresponding USB device class and the other devices. The relay unit, in the relay processing, performs at least one of a termination of communication with the USB device and a termination of communication with the other devices.
Need to check novelty before this filing date? Find Prior Art

Description

In-vehicle device, communication method, and communication program

[0001] This application claims priority from Japanese Patent Application No. 2024-9870, filed Jan. 26, 2024, the disclosure of which is incorporated herein by reference in its entirety.

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

[0003] International Publication No. 2020 / 179123

[0004] The in-vehicle device of the present disclosure is an in-vehicle device in an in-vehicle network, and includes a connection port to which a USB device can be connected via a USB interface, a detection unit that detects connection of the USB device to the connection port, and a plurality of relay units that perform relay processing to relay communications between the USB device whose connection is detected by the detection unit and other devices in the in-vehicle network, where the types of the plurality of relay units differ for each USB device class, and the relay units are capable of performing the relay processing to relay communications between the USB device belonging to the corresponding USB device class and the other devices, and the relay units perform at least one of terminating communications with the USB device and terminating communications with the other devices in the relay processing.

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

[0006] Fig. 1 is a diagram illustrating an example of the configuration of an in-vehicle system according to an embodiment of the present disclosure. Fig. 2 is a diagram illustrating the configuration of an in-vehicle ECU according to an embodiment of the present disclosure. Fig. 3 is a diagram illustrating a list of USB device classes of USB devices according to an embodiment of the present disclosure. Fig. 4 is a flowchart defining an example of an operation procedure when an in-vehicle ECU according to an embodiment of the present disclosure starts relay processing. Fig. 5 is a diagram illustrating an example of a communication sequence in an in-vehicle system according to an embodiment of the present disclosure.

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

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

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

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

[0011] [Description of Embodiments of the Present Disclosure] First, the contents of the embodiments of the present disclosure will be listed and described. (1) An in-vehicle device according to an embodiment of the present disclosure is an in-vehicle device in an in-vehicle network, and includes: a connection port to which a USB device can be connected via a USB interface; a detection unit that detects connection of the USB device to the connection port; and a plurality of relay units that perform relay processing to relay communication between the USB device whose connection is detected by the detection unit and another device in the in-vehicle network, wherein types of the plurality of relay units differ for each USB device class, and the relay unit is capable of performing the relay processing to relay communication between the USB device belonging to the corresponding USB device class and the other device, and the relay unit performs at least one of terminating communication with the USB device and terminating communication with the other device in the relay processing.

[0012] This configuration allows relaying of communications between devices on the in-vehicle network and USB devices that communicate according to different communication protocols. Furthermore, since the type of multiple relay units differs for each USB device class, the number of types of relay units required for relay processing can be reduced compared to a configuration in which a different type of relay unit is provided for each USB device, thereby reducing the resource usage of the in-vehicle device. Therefore, communications between an external device connected to the in-vehicle network via a USB interface and other devices on the in-vehicle network can be relayed with a simple configuration.

[0013] (2) In the above (1), the relay unit may further perform a conversion process in the relay process to convert the format of communication data transmitted between the USB device and the other device and the communication protocol of the communication data.

[0014] With this configuration, for example, communication data generated by a USB device can be converted into communication data in a format compatible with a device on the in-vehicle network and transmitted according to a communication protocol compatible with the device, allowing the device to use the received communication data without undergoing any conversion process.

[0015] (3) In the above (2), the in-vehicle device may further include a setting unit that sets conversion parameters for the conversion process based on information about the USB device connected to the connection port.

[0016] With this configuration, conversion parameters can be flexibly set according to the type of USB device connected to the connection port.

[0017] (4) In the above (3), the setting unit may set the conversion parameters based on information received from the USB device.

[0018] With this configuration, the conversion parameters can be set according to the specifications of the communication data generated by the USB device.

[0019] (5) In the above (3), the setting unit may set the conversion parameters in accordance with a request from the other device.

[0020] With this configuration, it is possible to set the conversion parameters according to the specifications of the communication data required by the devices in the in-vehicle network.

[0021] (6) In the above (2), the relay unit may perform the conversion process using conversion parameters that are set in advance based on the specifications of the other device.

[0022] This configuration allows communication data generated by a USB device to be converted into communication data in a format compatible with devices on the in-vehicle network with a simple configuration, so that the received communication data can be used by the device without undergoing any conversion process.

[0023] (7) A communication method disclosed herein is a communication method for an in-vehicle device in an in-vehicle network, the in-vehicle device having a connection port to which a USB device can be connected via a USB interface and a plurality of relay units, the types of the plurality of relay units being different for each USB device class, the relay units being capable of performing relay processing to relay communication between the USB device belonging to the corresponding USB device class and another device in the in-vehicle network, the communication method including the steps of: detecting connection of the USB device to the connection port; and performing relay processing using the relay unit to relay communication between the USB device whose connection has been detected and the other device, and the step of performing relay processing includes terminating at least one of communication with the USB device and communication with the other device.

[0024] This method makes it possible to relay communications between devices on an in-vehicle network and USB devices that communicate according to different communication protocols. Furthermore, since the types of relay units differ for each USB device class, the number of types of relay units required for relay processing can be reduced compared to a method in which different types of relay units are used for each USB device to terminate communications, thereby reducing the resource usage of the in-vehicle device. Therefore, communications between an external device connected to the in-vehicle network via a USB interface and other devices on the in-vehicle network can be relayed with a simple configuration.

[0025] (8) A communication program disclosed herein is a communication program used in an in-vehicle device in an in-vehicle network, the in-vehicle device having a connection port to which a USB device can be connected via a USB interface, and causing a computer to function as a detection unit that detects connection of the USB device to the connection port, and a plurality of relay units that perform relay processing to relay communication between the USB device whose connection is detected by the detection unit and other devices in the in-vehicle network, the types of the plurality of relay units being different for each USB device class, the relay units being capable of performing the relay processing to relay communication between the USB device belonging to the corresponding USB device class and the other devices, and the relay units performing at least one of terminating communication with the USB device and terminating communication with the other devices in the relay processing.

[0026] This configuration allows relaying of communications between devices on the in-vehicle network and USB devices that communicate according to different communication protocols. Furthermore, since the type of multiple relay units differs for each USB device class, the number of types of relay units required for relay processing can be reduced compared to a configuration in which a different type of relay unit is provided for each USB device, thereby reducing the resource usage of the in-vehicle device. Therefore, communications between an external device connected to the in-vehicle network via a USB interface and other devices on the in-vehicle network can be relayed with a simple configuration.

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

[0028] [Configuration and Basic Operation] Fig. 1 is a diagram showing an example of the configuration of an in-vehicle system according to an embodiment of the present disclosure. Referring to Fig. 1, the in-vehicle system 301 includes an in-vehicle ECU (Electronic Control Unit) 101 and an in-vehicle ECU 111. The in-vehicle system 301 is mounted on a vehicle 1. The in-vehicle ECUs 101 and 111 configure an in-vehicle network 201. Note that the in-vehicle system 301 may include one or three or more in-vehicle ECUs 111.

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

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

[0031] The communication port P1 is a connector that can be connected to, for example, an Ethernet (registered trademark) cable 2. The USB port P2 can be connected to a USB device 121 via a USB interface. In other words, the USB port P2 is a connector that can be connected to a USB connector.

[0032] The in-vehicle ECU 111 is connected to the communication port P1 of the in-vehicle ECU 101 via an Ethernet cable 2. The in-vehicle ECU 111 is not limited to being connected to the in-vehicle ECU 101 via the Ethernet cable 2, and may be connected via a communication line conforming to other standards such as CAN (Controller Area Network) (registered trademark) and FlexRay (registered trademark).

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

[0034] For example, when a USB device is connected to a USB port of a personal computer, the personal computer exchanges communication data by directly communicating with the USB device.

[0035] On the other hand, in the in-vehicle system 301, when the USB device 121 is connected to the USB port P2 of the in-vehicle ECU 101, the USB device 121 and the in-vehicle ECU 111 may exchange communication data Dt via the in-vehicle ECU 101. However, while the USB device 121 communicates in accordance with the USB standard, the in-vehicle ECU 111 communicates in accordance with a standard different from the USB standard.

[0036] Furthermore, since there are a wide variety of USB devices 121 that can be connected to the in-vehicle ECU 101, if it is necessary to be able to relay communication between all USB devices 121 and the in-vehicle ECU 111, it is necessary to develop a large number of relay applications that correspond to the types of USB devices 121 and install them on the in-vehicle ECU 101.

[0037] Therefore, for example, when a USB device 121 is retrofitted to the USB port PB of the vehicle ECU 101 after the vehicle 1 has been shipped, a technology is desired that can relay communication between the USB device 121 and the vehicle ECU 111 with a simple configuration.

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

[0039] (On-Vehicle ECU) FIG. 2 is a diagram illustrating a configuration of an on-vehicle ECU according to an embodiment of the present disclosure. Referring to FIG. 2, the on-vehicle ECU 101 includes a USB communication unit 11, an ECU communication unit 12, a proxy unit 13, a setting unit 15, and a storage unit 16. The proxy unit 13 includes a plurality of termination units 14A and a plurality of termination units 14B. Hereinafter, each of the termination units 14A and 14B will also be referred to as a termination unit 14. The USB communication unit 11 is an example of a detection unit. The termination unit 14 is an example of a relay unit. Some or all of the USB communication unit 11, the ECU communication unit 12, the proxy unit 13, and the setting unit 15 are realized by, for example, a processing circuit including one or more processors. The storage unit 16 is, for example, a non-volatile memory included in the processing circuit.

[0040] 2, USB devices 121A, 121B, and 121C, which are part of the USB device 121, are connected to USB ports P2A, P2B, and P2C, respectively. The USB device 121A is a video camera, the USB device 121B is a microphone, and the USB device 121C is a speaker. The USB devices 121 and the in-vehicle ECU 111 transmit communication data Dt via the in-vehicle ECU 101.

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

[0042] 3, USB devices 121 are classified into one or more USB device classes with similar functions according to the standard defined by the USB-IF (Implementers Forum). For example, a USB device 121A that is a video camera is classified into a USB device class with the class name "Video." Furthermore, a USB device 121B that is a microphone and a USB device 121C that is a speaker are classified into a USB device class with the class name "Audio." USB devices 121 that belong to the same USB device class communicate with other devices according to a common interface specification, i.e., by using a common interface.

[0043] The USB device 121 stores identification information A1 of the USB device 121 and class information A2 indicating the USB device class to which the USB device 121 belongs.

[0044] (Connection Detection) Referring back to FIG. 2, the USB communication unit 11 detects the connection of the USB device 121 to the USB port P2.

[0045] More specifically, when the USB device 121 is connected to the USB port P2, it transmits a connection notification to the in-vehicle ECU 101. When the USB communication unit 11 receives the connection notification from the USB device 121 via the USB port P2, it transmits a USB device information request to the USB device 121 via the USB port P2.

[0046] When the USB device 121 receives the USB device information request from the in-vehicle ECU 101, the USB device 121 transmits a USB device information response including the identification information A1 and class information A2 of the USB device 121 to the in-vehicle ECU 101 as a response to the USB device information request.

[0047] When the USB communication unit 11 receives a USB device information response from the USB device 121 via the USB port P2, it acquires the identification information A1 and the class information A2 from the received USB device information response. The USB communication unit 11 recognizes that the USB device 121 indicated by the acquired identification information A1 is connected to the USB port P2. The USB communication unit 11 then creates connection information Con that includes the identification information A1 and the class information A2 of the USB device 121 and the port number A3 of the USB port P2, and outputs the created connection information Con to the setting unit 15.

[0048] The setting unit 15 receives the connection information Con from the USB communication unit 11 and activates the termination unit 14 in the proxy unit 13 based on the received connection information Con.

[0049] More specifically, the types of the multiple termination units 14 in the proxy unit 13 differ for each USB device class. That is, the proxy unit 13 includes the same number of types of termination units 14 as the number of USB device classes of the USB devices 121 that can be connected to the USB port P2. As an example, the termination unit 14A corresponds to the "Video" USB device class and is capable of communicating with the USB devices 121 that belong to the "Video" USB device class. The termination unit 14B corresponds to the "Audio" USB device class and is a different type from the termination unit 14A and is capable of communicating with the USB devices 121 that belong to the "Audio" USB device class. The termination unit 14 is capable of performing a relay process to relay communication between the USB devices 121 that belong to the corresponding USB device class and the in-vehicle ECU 111. The proxy unit 13 is not limited to these USB device classes, and may include a termination unit 14 of a type different from the termination units 14A and 14B.

[0050] The storage unit 16 also stores a correspondence table T1 that indicates the correspondence between USB device classes and the termination units 14 that correspond to the USB device classes.

[0051] The setting unit 15 acquires the identification information A1, the class information A2, and the port number A3 from the connection information Con received from the USB communication unit 11. The setting unit 15 refers to the correspondence table T1 in the storage unit 16 to identify the termination unit 14 corresponding to the USB device class indicated by the acquired class information A2. The setting unit 15 starts the identified termination unit 14 and outputs relay setting information R including the acquired identification information A1 and the port number A3 to the termination unit 14. For example, every time a USB device 121 is connected to the USB port P2 and the setting unit 15 receives the connection information Con from the USB communication unit 11, the setting unit 15 starts the termination unit 14 corresponding to the USB device 121.

[0052] Specifically, when setting unit 15 receives connection information Con from USB communication unit 11 as USB device 121A is connected to USB port P2A, setting unit 15 activates termination unit 14A, which is termination unit 14 corresponding to the USB device class of "Video," based on the received connection information Con. Then, setting unit 15 outputs relay setting information RA, which is relay setting information R including identification information A1 indicating USB device 121A and port number A3 indicating USB port P2A, to activated termination unit 14A.

[0053] Furthermore, when the setting unit 15 receives connection information Con from the USB communication unit 11 in response to the connection of the USB device 121B to the USB port P2B, the setting unit 15 activates the termination unit 14B_1, which is the termination unit 14 corresponding to the USB device class of "Audio," based on the received connection information Con. The termination unit 14B_1 is an example of the termination unit 14B. The setting unit 15 then outputs relay setting information RB, which is the relay setting information R including the identification information A1 indicating the USB device 121B and the port number A3 indicating the USB port P2B, to the activated termination unit 14B_1.

[0054] Furthermore, when the setting unit 15 receives connection information Con from the USB communication unit 11 in response to the connection of the USB device 121C to the USB port P2C, the setting unit 15 activates the termination unit 14B_2, which is the termination unit 14 corresponding to the USB device class of "Audio," based on the received connection information Con. The termination unit 14B_2 is an example of the termination unit 14B. The setting unit 15 then outputs relay setting information RC, which is the relay setting information R including the identification information A1 indicating the USB device 121C and the port number A3 indicating the USB port P2C, to the activated termination unit 14B_2.

[0055] The termination unit 14 receives the relay setting information R from the setting unit 15 and holds the received relay setting information R.

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

[0057] More specifically, the setting unit 15 generates an OfferService message M1 including the service ID of the service that the USB device 121 can provide, and transmits the generated OfferService message M1 to the in-vehicle ECU 111 via the ECU communication unit 12 and the communication port P1.

[0058] The in-vehicle ECU 111 receives the OfferService message M1 from the in-vehicle ECU 101 and acquires a service ID from the received OfferService message M1. When the in-vehicle ECU 111 receives the service indicated by the acquired service ID, the in-vehicle ECU 111 transmits a FindService message M2 including the service ID to the in-vehicle ECU 101.

[0059] The in-vehicle ECU 111 also transmits to the in-vehicle ECU 101 a setting request message M3 including an ECU ID, which is the ID of the in-vehicle ECU 111, and a setting request indicating the format of the requested communication data Dt and the communication protocol of the communication data Dt. For example, the configuration request may be sent for the Real Time Streaming Protocol (RTSP), Real-time Transport Protocol (RTP), Hypertext Transfer Protocol (HLS), Hypertext Transfer Protocol (Hypertext Transfer Protocol Live Streaming), Audio Video Bridging Transport Protocol (AVTP), Secure Copy (SCP), Network File System (NFS), and Web-based Distributed Authoring and Video Transport (WebDAV). The protocol Cg1 includes a higher layer protocol related to data transmission, such as a protocol for encoding, decoding, video codec, resolution, and frame rate, and a data format Cg2 including encryption, decoding, video codec, resolution, and frame rate.

[0060] The setting unit 15 sets the conversion parameters CP of the communication data Dt based on information about the USB device 121 connected to the USB port P2. For example, the setting unit 15 sets the conversion parameters CP of the communication data Dt in accordance with a request from the in-vehicle ECU 111, i.e., in accordance with the content of the request from the in-vehicle ECU 111.

[0061] More specifically, when the setting unit 15 receives a setting request message M3 from the in-vehicle ECU 111 via the communication port P1 and the ECU communication unit 12, the setting unit 15 acquires an ECU ID and a setting request from the received setting request message M3. Based on the setting request, the setting unit 15 sets conversion parameters CP1, which are conversion tables for converting the format and communication protocol of the communication data Dt generated by the USB device 121 into a format and communication protocol of the communication data Dt requested by the in-vehicle ECU 111. The setting unit 15 also sets conversion parameters CP2, which are conversion tables for converting the format and communication protocol of the communication data Dt generated by the in-vehicle ECU 111 into a format and communication protocol of the communication data Dt that can be received by the USB device 121. The setting unit 15 stores parameter information indicating a correspondence between the acquired ECU ID and the set conversion parameters CP1 and CP2 in the storage unit 16. The conversion parameters CP1 and CP2 are examples of conversion parameters CP.

[0062] After storing the parameter information in the storage unit 16, the setting unit 15 outputs a relay start instruction to the activated termination unit 14.

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

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

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

[0066] Furthermore, upon receiving a relay start instruction from the setting unit 15, the termination unit 14B_2 starts a relay process of relaying communication between the USB device 121C connected to the USB port P2A and the in-vehicle ECU 111.

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

[0068] For example, in the relay process, the termination unit 14 further performs a conversion process to convert the format of the communication data Dt transmitted between the USB device 121 and the in-vehicle ECU 111 and the communication protocol of the communication data Dt.

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

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

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

[0072] The terminal 14 also refers to the parameter information in the storage unit 16 and acquires conversion parameters CP1 corresponding to the in-vehicle ECU 111 that is the destination of the frame F1. The terminal 14 uses the acquired conversion parameters CP1 to perform a conversion process of converting the format and communication protocol of the acquired communication data Dt1.

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

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

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

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

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

[0078] The terminal 14 also refers to the parameter information in the storage unit 16 and acquires conversion parameters CP2 corresponding to the in-vehicle ECU 111 that is the sender of the frame F2. The terminal 14 uses the acquired conversion parameters CP2 to perform a conversion process for converting the format and communication protocol of the acquired communication data Dt2.

[0079] The termination unit 14 then generates a frame F1 conforming to the USB standard, including the converted communication data Dt2, and transmits the generated frame F1 to the destination USB device 121 via the USB communication unit 11 and the corresponding USB port P2.

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

[0081] [Operation Flow] FIG. 4 is a flowchart defining an example of an operation procedure when the in-vehicle ECU according to the embodiment of the present disclosure starts a relay process.

[0082] Referring to FIG. 4, first, the in-vehicle ECU 101 waits for a connection notification (NO in step S11), and when it receives the connection notification from the USB device 121 via the USB port P2 (YES in step S11), it sends a USB device information request to the USB device 121 via the USB port P2 (step S12).

[0083] Next, the on-board ECU 101 waits for the arrival of a USB device information response including the identification information A1 and the class information A2 (NO in step S13), and when it receives the USB device information response from the USB device 121 via the USB port P2 (YES in step S13), it recognizes that the USB device 121 indicated by the identification information A1 is connected to the USB port P2, and activates the termination unit 14 corresponding to the USB device class indicated by the class information A2 (step S14).

[0084] Next, the in-vehicle ECU 101 acquires the setting request from the in-vehicle ECU 111, and stores parameter information indicating the correspondence between the ECU ID and the conversion parameter CP1 in the storage unit 16 (step S15).

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

[0086] Next, the in-vehicle ECU 101 waits for a new connection notification to arrive (NO in step S11).

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

[0088] Referring to FIG. 5, first, when the USB device 121 is connected to the USB port P2 of the in-vehicle ECU 101, the USB device 121 transmits a connection notification to the in-vehicle ECU 101 (step S21).

[0089] Next, when the in-vehicle ECU 101 receives a connection notification from the USB device 121 via the USB port P2, the in-vehicle ECU 101 transmits a USB device information request to the USB device 121 via the USB port P2 (step S22).

[0090] Next, the USB device 121 transmits a USB device information response including the identification information A1 and the class information A2 to the in-vehicle ECU 101 as a response to the USB device information request (step S23).

[0091] Next, the in-vehicle ECU 101 recognizes that the USB device 121 indicated by the identification information A1 is connected to the USB port P2, and activates the termination unit 14 corresponding to the USB device class indicated by the class information A2 (step S24).

[0092] Next, the in-vehicle ECU 101 transmits an OfferService message M1 including the service ID of the service that the USB device 121 can provide to the in-vehicle ECU 111 (step S25).

[0093] Next, the in-vehicle ECU 111 transmits a FindService message M2 to the in-vehicle ECU 101 (step S26).

[0094] Next, the in-vehicle ECU 111 transmits a setting request message M3 including the ECU ID and a setting request to the in-vehicle ECU 101 (step S27).

[0095] Next, the in-vehicle ECU 101 stores parameter information indicating the correspondence between the ECU ID and the conversion parameter CP1 in the storage unit 16 (step S28).

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

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

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

[0099] Next, the in-vehicle ECU 101 performs a conversion process to convert the format and communication protocol of the communication data Dt1 based on the parameter information in the storage unit 16 (step S32).

[0100] Next, the in-vehicle ECU 101 transmits the frame F2 including the converted communication data Dt1 to the in-vehicle ECU 111 (step S33).

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

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

[0103] Next, the in-vehicle ECU 101 performs a conversion process to convert the format and communication protocol of the communication data Dt2 based on the parameter information in the storage unit 16 (step S36).

[0104] Next, the in-vehicle ECU 101 transmits the frame F1 including the converted communication data Dt2 to the in-vehicle ECU 111 (step S37).

[0105] In addition, in the in-vehicle system 301, any one of the above steps S30, S31, S32, and S33 and the above steps S34, S35, S36, and S37 may not be performed. More specifically, in the in-vehicle system 301, the USB device 121 may transmit the communication data Dt1 to the in-vehicle ECU 111 via the in-vehicle ECU 101, while the in-vehicle ECU 111 may not transmit the communication data Dt2. In this case, the termination unit 14 terminates communication with the USB device 121, but does not terminate communication with the in-vehicle ECU 111.

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

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

[0108] Furthermore, in the in-vehicle ECU 101 according to the embodiment of the present disclosure, the termination unit 14 is configured to perform the conversion process, but this is not limited thereto. Instead of the termination unit 14, an in-vehicle device (not shown) in the in-vehicle system 301 may perform the conversion process. In this case, instead of storing the parameter information in the storage unit 16, the setting unit 15 transmits a setting reflection instruction including the parameter information to the in-vehicle device via the ECU communication unit 12 and the communication port P1. Furthermore, the termination unit 14 transmits a frame F2 including communication data Dt1 to the in-vehicle device via the ECU communication unit 12 and the communication port P1. The in-vehicle device receives the frame F2 from the in-vehicle ECU 101, acquires the communication data Dt1 from the received frame F2, and performs a conversion process on the communication data Dt1 based on the parameter information received from the in-vehicle ECU 101. The in-vehicle device then includes the converted communication data Dt1 in the frame F2 and transmits it to the destination in-vehicle ECU 111. This reduces the processing load on the termination unit 14.

[0109] Alternatively, the USB device 121 may perform the conversion process instead of the termination unit 14. In this case, instead of storing the parameter information in the storage unit 16, the setting unit 15 transmits a setting reflection instruction including the parameter information to the USB device 121 via the USB communication unit 11 and the USB port P2. The USB device 121 performs conversion processing on the communication data Dt1 addressed to the in-vehicle ECU 111 based on the parameter information received from the in-vehicle ECU 101, and transmits a frame F1 including the converted communication data Dt1 to the in-vehicle ECU 101. This reduces the processing load on the termination unit 14.

[0110] Furthermore, in the in-vehicle system 301 according to the embodiment of the present disclosure, the format and communication protocol of the communication data Dt required by the in-vehicle ECU 111 and the format and communication protocol of the communication data Dt that can be received by the USB device 121 may be preset to a format and communication protocol that do not require conversion processing. In this case, the termination unit 14 does not need to perform conversion processing, and therefore the processing load on the termination unit 14 can be reduced.

[0111] Furthermore, in the in-vehicle ECU 101 according to the embodiment of the present disclosure, the terminal unit 14 is configured to convert the format and the communication protocol of the communication data Dt during the conversion process, but this is not limited to this. The terminal unit 14 may be configured to convert the format of the communication data Dt but not convert the communication protocol of the communication data Dt during the conversion process. Furthermore, the terminal unit 14 may be configured to convert the communication protocol of the communication data Dt but not convert the format of the communication data Dt during the conversion process.

[0112] Although the in-vehicle ECU 101 according to the embodiment of the present disclosure is configured to include the setting unit 15, this is not limiting. The in-vehicle ECU 101 may be configured without the setting unit 15. In this case, the termination unit 14 performs the conversion process using conversion parameters CP1 and CP2 that are preset based on the specifications of the in-vehicle ECU 111. More specifically, the storage unit 16 stores a conversion parameter CP1 that is preset based on the format and communication protocol of the communication data Dt required by the in-vehicle ECU 111. The termination unit 14 performs the conversion process using the conversion parameter CP1 stored in the storage unit 16. The storage unit 16 also stores a conversion parameter CP2 that is preset based on the format and communication protocol of the communication data Dt that the USB device 121 can receive. The termination unit 14 performs the conversion process using the conversion parameter CP2 stored in the storage unit 16.

[0113] Furthermore, in the in-vehicle ECU 101 according to the embodiment of the present disclosure, the setting unit 15 is configured to set the conversion parameters CP1 in accordance with a request from the in-vehicle ECU 111, but this is not limiting. The setting unit 15 may be configured to set the conversion parameters CP1 based on information received from the USB device 121 instead of a request from the in-vehicle ECU 111. More specifically, for example, the setting unit 15 receives format information from the USB device 121 via the USB port P2 and the USB communication unit 11, the format information indicating an upper layer protocol Cg3 related to data transmission and a data format Cg4, such as encryption, decryption, video codec, resolution, and frame rate, for the communication data Dt1 generated by the USB device 121. The setting unit 15 sets the conversion parameters CP1 for converting the communication data Dt1 received from the USB device 121 into a predetermined format based on the received format information.

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

[0115] Each process (each function) in the above-described embodiments is realized by a processing circuit (circuitry) including one or more processors. The processing circuit may be configured as an integrated circuit or the like that combines one or more memories, various analog circuits, and various digital circuits in addition to the one or more processors. The one or more memories store programs (instructions) that cause the one or more processors to execute each of the processes. The one or more processors may execute each of the processes according to the program read from the one or more memories, or may execute each of the processes according to a logic circuit designed in advance to execute each of the processes. The processor may be any of various processors suitable for computer control, such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and an ASIC (Application Specific Integrated Circuit). Note that the physically separated processors may cooperate with each other to execute the processes. For example, the processors installed in the physically separated computers may cooperate with each other via a network such as a LAN (Local Area Network), a WAN (Wide Area Network), or the Internet to execute the processes. The program may be installed into the memory from an external server device or the like via the network, or may be distributed in a state stored on a recording medium such as a CD-ROM (Compact Disc Read Only Memory), a DVD-ROM (Digital Versatile Disc Read Only Memory), or a semiconductor memory, and then installed into the memory from the recording medium.

[0116] The above description includes the following additional features: [Supplementary Note 1] An in-vehicle device in an in-vehicle network, comprising: a connection port to which a USB device can be connected via a USB interface; a detection unit that detects connection of the USB device to the connection port; and a plurality of relay units that perform relay processing to relay communications between the USB device whose connection is detected by the detection unit and other devices in the in-vehicle network, wherein the relay unit terminates at least one of communications with the USB device and communications with the other devices in the relay processing, wherein different types of relay units are provided for different USB device classes, and the types of the plurality of relay units are different for each USB device class, and the relay units are capable of performing the relay processing to relay communications between the USB device belonging to the corresponding USB device class and the other devices, and each of the relay units relays communications between one of the USB devices and the other devices.

[0117] [Supplementary Note 2] An in-vehicle device in an in-vehicle network, comprising: a processing circuit; a connection port to which a USB device can be connected via a USB interface; and a plurality of relay units, the types of which vary depending on the USB device class; the relay units are capable of performing relay processing to relay communication between the USB device belonging to the corresponding USB device class and other devices in the in-vehicle network; the processing circuit detects connection of the USB device to the connection port; and uses the relay unit to perform relay processing to relay communication between the detected USB device and the other devices, and in the relay processing, the in-vehicle device performs at least one of termination of communication with the USB device and termination of communication with the other devices.

[0118] REFERENCE SIGNS LIST 1 vehicle 2 Ethernet cable 11 USB communication unit 12 ECU communication unit 13 proxy unit 14, 14A, 14B termination unit 15 setting unit 16 storage unit 101 on-vehicle ECU 111 on-vehicle ECU 121, 121A, 121B, 121C USB device 201 on-vehicle network 301 on-vehicle system P1 communication port P2, P2A, P2B, P2C USB port

Claims

1. An in-vehicle device in an in-vehicle network, comprising: a connection port capable of connecting a USB device via a USB interface; a detection unit that detects the connection of the USB device to the connection port; a plurality of relay units that perform a relay process of relaying communication between the USB device detected by the detection unit and other devices in the in-vehicle network, wherein the types of the plurality of relay units are different for each USB device class, and the relay unit is capable of performing the relay process of relaying communication between the USB device belonging to the corresponding USB device class and the other devices, and the relay unit performs at least one of terminating communication with the USB device and terminating communication with the other devices in the relay process. An in-vehicle device.

2. The in-vehicle device according to claim 1, wherein the relay unit further performs a conversion process of converting a format of communication data transmitted between the USB device and the other devices and a communication protocol of the communication data in the relay process.

3. The in-vehicle device according to claim 2, further comprising: a setting unit that sets conversion parameters in the conversion process based on information about the USB device connected to the connection port.

4. The in-vehicle device according to claim 3, wherein the setting unit sets the conversion parameters based on information received from the USB device.

5. The in-vehicle device according to claim 3, wherein the setting unit sets the conversion parameters according to a request from the other device.

6. The in-vehicle device according to claim 2, wherein the relay unit performs the conversion process using conversion parameters preset based on specifications of the other devices.

7. A communication method in an in-vehicle device in an in-vehicle network, wherein the in-vehicle device includes a connection port capable of connecting a USB device via a USB interface and a plurality of relay units, the types of the plurality of relay units are different for each USB device class, the relay unit is capable of performing a relay process for relaying communication between the USB device belonging to the corresponding USB device class and other devices in the in-vehicle network, the communication method includes a step of detecting connection of the USB device to the connection port, and a step of performing a relay process for relaying communication between the detected USB device and the other devices using the relay unit, and in the step of performing the relay process, at least one of termination of communication with the USB device and termination of communication with the other devices is performed.

8. A communication program used in an in-vehicle device in an in-vehicle network, wherein the in-vehicle device includes a connection port capable of connecting a USB device via a USB interface, and the program causes a computer to function as a detection unit for detecting connection of the USB device to the connection port, and a plurality of relay units for performing a relay process for relaying communication between the USB device detected by the detection unit and other devices in the in-vehicle network, the types of the plurality of relay units are different for each USB device class, the relay unit is capable of performing the relay process for relaying communication between the USB device belonging to the corresponding USB device class and the other devices, and in the relay process, the relay unit performs at least one of termination of communication with the USB device and termination of communication with the other devices.

Citation Information

Patent Citations

  • Communication device and program

    JP2008067346A

  • Device control apparatus and broadcast receiver equipped with the apparatus

    JP2009129170A

  • On-vehicle device and program

    JP2015195491A

  • Expansion unit, onboard device unit, and vehicle system

    WO2023276815A1