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

Abstract

To make it possible to relay communication between an external device connected to an in-vehicle network via a USB interface and another device in the in-vehicle network using a simple configuration.SOLUTION: An in-vehicle apparatus includes a connection port to which a USB device can be connected via a USB interface, a detection unit that detects connection of the USB device to the connection port, an acquisition unit that acquires software used in relay processing that relays communication between another device in the in-vehicle network and the USB device from an apparatus external to the in-vehicle apparatus, and a processing unit that performs the relay processing using the software. The processing unit performs at least one of termination of communication with the USB device and termination of communication with the other device in the relay processing.SELECTED DRAWING: Figure 2

Description

[Technical Field]

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

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

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

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

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

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

[0007] The in-vehicle device of the present disclosure is an in-vehicle device in an in-vehicle network, and includes a connection port to which a USB device can be connected via a USB interface, a detection unit that detects connection of the USB device to the connection port, an acquisition unit that acquires software used in a relay process that relays communication between the USB device whose connection is detected by the detection unit and other devices in the in-vehicle network from a device external to the in-vehicle device, and a processing unit that performs the relay process using the software acquired by the acquisition unit, and in the relay process, the processing unit terminates at least one of communication with the USB device and communication with the other devices.

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

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

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

[0011] First, the contents of the embodiments of the present disclosure will be listed and described. (1) An in-vehicle device according to an embodiment of the present disclosure is an in-vehicle device in an in-vehicle network, 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, an acquisition unit that acquires software used in a relay process that relays communication between the USB device whose connection is detected by the detection unit and other devices in the in-vehicle network from a device external to the in-vehicle device, and a processing unit that performs the relay process using the software acquired by the acquisition unit, and the processing unit terminates at least one of communication with the USB device and communication with the other devices in the relay process.

[0012] With this configuration, it is possible to acquire software necessary for relaying communication between a USB device connected to the connection port and other devices, and perform relaying using the acquired software, without having to previously store multiple pieces of software corresponding to each of the multiple USB devices that can be connected to the connection port. This allows relaying to be performed efficiently using the limited resources of the in-vehicle device. Therefore, it is possible to relay communication between an external device connected to the in-vehicle network via a USB interface and other devices on the in-vehicle network with a simple configuration.

[0013] (2) In the above (1), the acquisition unit may acquire the software from a device in the in-vehicle network.

[0014] With this configuration, software can be acquired in a shorter time than in a configuration in which software is acquired from a device outside the vehicle, without using a network outside the vehicle.

[0015] (3) In the above (1), the acquisition unit may acquire the software from a device outside the vehicle in which the in-vehicle network is installed.

[0016] With this configuration, compared to a configuration in which software is obtained from a device in an in-vehicle network, there is no need to store multiple pieces of software in advance in the memory area of the device in the vehicle, thereby reducing the resource usage of the device in the vehicle.

[0017] (4) In the above (1), the acquisition unit may acquire the software from the USB device.

[0018] With this configuration, relay processing can be started with simple processing using software obtained from the USB device connected to the connection port, without having to specify the software used to relay communication between the USB device connected to the connection port and other devices.

[0019] (5) In any one of (1) to (4) above, the acquisition unit may store the acquired software in a non-volatile storage area in the in-vehicle device.

[0020] With this configuration, the software used for the relay process can be obtained from the non-volatile storage area when the in-vehicle device is started or the USB device is reconnected, so the relay process can be started with a simpler process than a configuration in which software is obtained from a device outside the in-vehicle device every time the in-vehicle device is started or the USB device is reconnected.

[0021] (6) An in-vehicle system according to an embodiment of the present disclosure is an in-vehicle system in an in-vehicle network, comprising a first in-vehicle device and a second in-vehicle device, wherein the first in-vehicle device has a connection port to which a USB device can be connected via a USB interface, and when the USB device is connected to the connection port, the first in-vehicle device transmits a download request to the second in-vehicle device to download software used in a relay process that relays communication between the USB device and other devices in the in-vehicle network, and the second in-vehicle device provides the software to the first in-vehicle device in accordance with the download request received from the first in-vehicle device, and the first in-vehicle device performs the relay process using the software provided by the second in-vehicle device, and in the relay process, the first in-vehicle device terminates at least one of communication with the USB device and communication with the other devices.

[0022] With this configuration, the first in-vehicle device can acquire software necessary for relaying communication between a USB device connected to the connection port and other devices, and perform relay processing using the acquired software, without having to previously store multiple pieces of software corresponding to multiple USB devices that can be connected to the connection port. This allows relay processing to be performed efficiently using the limited resources of the first in-vehicle device. Therefore, communication between an external device connected to the in-vehicle network via a USB interface and other devices on the in-vehicle network can be relayed with a simple configuration.

[0023] (7) A communication method according to an embodiment of the present disclosure is a communication method in an in-vehicle device in an in-vehicle network, the in-vehicle device having a connection port to which a USB device can be connected via a USB interface, the communication method including the steps of: detecting connection of the USB device to the connection port; acquiring, from a device external to the in-vehicle device, software used for relaying communication between the detected USB device and other devices in the in-vehicle network; and performing the relaying process using the acquired software, wherein the relaying process includes terminating at least one of communication with the USB device and communication with the other devices.

[0024] This method allows the software required for relaying communications between a USB device connected to a connection port and other devices to be acquired and relayed using the acquired software, without having to previously store multiple pieces of software corresponding to each of the multiple USB devices that can be connected to the connection port. This allows relaying to be performed efficiently using the limited resources 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 according to an embodiment of the present disclosure is a communication program used in an in-vehicle device in an in-vehicle network, the in-vehicle device having a connection port to which 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, an acquisition unit that acquires, from a device external to the in-vehicle device, software used in a relay process that relays communication between the USB device whose connection is detected by the detection unit and other devices in the in-vehicle network, and a processing unit that performs the relay process using the software acquired by the acquisition unit, and the processing unit performs at least one of terminating communication with the USB device and terminating communication with the other devices in the relay process.

[0026] With this configuration, it is possible to acquire software necessary for relaying communication between a USB device connected to the connection port and other devices, and perform relaying using the acquired software, without having to previously store multiple pieces of software corresponding to each of the multiple USB devices that can be connected to the connection port. This allows relaying to be performed efficiently using the limited resources of the in-vehicle device. Therefore, it is possible to relay communication between an external device connected to the in-vehicle network via a USB interface and other devices on the in-vehicle network 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 illustrating an example of the configuration of an in-vehicle system according to an embodiment of the present disclosure. Referring to FIG. 1, the in-vehicle system 301 includes in-vehicle ECUs (Electronic Control Units) 101, 102, and 111. The in-vehicle ECU 101 is an example of a first in-vehicle device. The in-vehicle ECU 102 is an example of a second in-vehicle device. The in-vehicle system 301 is mounted on a vehicle 1. The in-vehicle ECUs 101, 102, and 111 configure an in-vehicle network 201. Note that the in-vehicle system 301 may include two or more in-vehicle ECUs 111, or may include two or more in-vehicle ECUs 102.

[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 102 stores a plurality of pieces of software and provides the software to the in-vehicle ECU 101 in response to a request from the in-vehicle ECU 101.

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

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

[0033] The in-vehicle ECUs 111 and 102 are connected to communication ports P1A and P1B of the in-vehicle ECU 101 via an Ethernet cable 2. The in-vehicle ECUs 111 and 102 are not limited to being connected to the in-vehicle ECU 101 via the Ethernet cable 2, and may be connected via communication lines conforming to other standards such as CAN (Controller Area Network) (registered trademark) and FlexRay (registered trademark).

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

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

[0036] 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 USB. Therefore, in the in-vehicle system 301, the in-vehicle ECU 101 performs relay processing between the USB device 121 and the in-vehicle ECU 111 using a relay application.

[0037] Furthermore, since there are a wide variety of USB devices 121 that can be connected to the in-vehicle ECU 101, in order to be able to relay communications between all of the USB devices 121 and the in-vehicle ECU 111, it is necessary to install in the in-vehicle ECU 101 a large number of relay applications that correspond to the types of USB devices 121. However, if a large number of relay applications are installed in the in-vehicle ECU 101, the resources of the in-vehicle ECU 101 will be insufficient.

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

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

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

[0041] 3, USB devices 121 are classified into one or more USB device classes with similar functions according to the standard established by the USB-IF (Implementers Forum). For example, a USB device 121 that is a video camera is classified into a USB device class with the class name "Video." Also, a USB device 121 that is a microphone is 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.

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

[0043] (Connection detection) 2 again, the USB communication unit 11 detects the connection of the USB device 121 to the USB port P2. 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 recognizes that the USB device 121 is connected to the USB port P2.

[0044] The USB communication unit 11 acquires USB information about the USB device 121 whose connection to the USB port P2 has been detected. More specifically, when the USB communication unit 11 recognizes that the USB device 121 has been connected to the USB port P2, it transmits a device information request to the USB device 121 via the USB port P2.

[0045] When the USB device 121 receives a device information request from the in-vehicle ECU 101, the USB device 121 transmits a device information response including USB information to the in-vehicle ECU 101 as a response to the device information request.

[0046] When the USB communication unit 11 receives a device information response from the USB device 121 via the USB port P2, the USB communication unit 11 acquires USB information from the received device information response. The USB communication unit 11 outputs the acquired USB information to the management unit 14.

[0047] (Software Download) The management unit 14 acquires software SW used for relay processing that relays communication between the USB device 121, the connection of which is detected by the USB communication unit 11, and the in-vehicle ECU 111, from a device external to the in-vehicle ECU 101. For example, the management unit 14 acquires the software SW from the in-vehicle ECU 102. Also, for example, the management unit 14 acquires application software, device drivers, and shared libraries as the software SW.

[0048] 4 is a diagram illustrating an example of a correspondence table stored in a storage unit in an on-vehicle ECU according to an embodiment of the present disclosure. Referring to FIG. 4, for example, storage unit 15 stores correspondence table T1 indicating a correspondence relationship between USB information and a soft ID, which is an identifier of software SW.

[0049] The management unit 14 refers to the correspondence table T1 in the storage unit 15 and identifies the software ID corresponding to the USB information received from the USB communication unit 11.

[0050] Referring back to FIG. 2, the management unit 14 transmits a download request including the identified software ID to the in-vehicle ECU 102 via the ECU communication unit 12 and the communication port P1B, the download request being for downloading the software SW.

[0051] The in-vehicle ECU 102 stores software SW used for relay processing that relays communication between the USB device 121 and the in-vehicle ECU 111. For example, the in-vehicle ECU 102 stores the same number of types of software SW as the number of USB device classes of the USB device 121 that can be connected to the USB port P2 of the in-vehicle ECU 101. Furthermore, for example, the in-vehicle ECU 102 stores, as the software SW, application software, device drivers, and shared libraries for realizing relay processing of communication between the USB device 121 and the in-vehicle ECU 111.

[0052] The in-vehicle ECU 102 receives a download request from the in-vehicle ECU 101 and provides the in-vehicle ECU 101 with the software SW in accordance with the received download request. More specifically, the in-vehicle ECU 102 receives the download request from the in-vehicle ECU 101 and acquires a software ID from the received download request. The in-vehicle ECU 101 generates a download response including the software SW corresponding to the acquired software ID and transmits the generated download response to the in-vehicle ECU 101.

[0053] The management unit 14 in the in-vehicle ECU 101 receives the download response from the in-vehicle ECU 102 via the communication port P1B and the ECU communication unit 12, and acquires the software SW from the received download response. For example, the management unit 14 stores the acquired software SW in a non-volatile storage area in the in-vehicle ECU 101. More specifically, the management unit 14 stores the acquired software SW in the storage unit 15.

[0054] After storing the software SW in the storage unit 15, the management unit 14 provides the service using the USB device 121 to the in-vehicle ECU 111 using an OfferService message conforming to SOME / IP (Scalable service-oriented middleware over IP).

[0055] More specifically, the management unit 14 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.

[0056] The in-vehicle ECU 111 receives the OfferService message M1 from the in-vehicle ECU 101 and acquires the 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.

[0057] When the management unit 14 receives the FindService message M2 from the in-vehicle ECU 111 via the communication port P1A and the ECU communication unit 12, it outputs a relay start instruction including the ID of the in-vehicle ECU 111 to the proxy unit 13.

[0058] (Relay processing) The proxy unit 13 performs relay processing using the software SW acquired by the management unit 14. More specifically, when the management unit 14 stores the software SW in the storage unit 15, the proxy unit 13 acquires the software SW from the storage unit 15 and installs the acquired software SW. Furthermore, every time the in-vehicle ECU 101 starts up, the proxy unit 13 acquires the software SW from the storage unit 15 and installs the acquired software SW. By installing the software SW, the proxy unit 13 becomes able to relay communication between the USB device 121 and the in-vehicle ECU 111.

[0059] Furthermore, upon receiving a relay start instruction from the management unit 14, the proxy unit 13 starts a relay process for relaying communication between the USB device 121 connected to the USB port P2 and the in-vehicle ECU 111.

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

[0061] (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 includes the communication data Dt1 and is addressed to the in-vehicle ECU 111, and conforms to the USB standard, and transmits the generated frame F1 to the in-vehicle ECU 101.

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

[0063] The proxy unit 13 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 proxy unit 13 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.

[0064] Then, the proxy unit 13 generates a frame F2 conforming to the Ethernet standard, including the acquired communication data Dt1, and transmits the generated frame F2 to the destination in-vehicle ECU 111 via the ECU communication unit 12 and the corresponding communication port P1.

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

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

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

[0068] The proxy unit 13 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 proxy unit 13 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.

[0069] Then, the proxy unit 13 generates a frame F1 conforming to the USB standard and including the communication data Dt2, and transmits the generated frame F1 to the destination USB device 121 via the USB communication unit 11 and the corresponding USB port P2.

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

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

[0072] Referring to FIG. 5, first, the in-vehicle ECU 101 waits for a connection notification (NO in step S11), and upon receiving the connection notification from the USB device 121 via the USB port P2 (YES in step S11), the in-vehicle ECU 101 recognizes that the USB device 121 has been connected to the USB port P2, and transmits a device information request to the USB device 121 via the USB port P2 (step S12).

[0073] Next, the in-vehicle ECU 101 waits for the arrival of a device information response (NO in step S13), and when it receives the device information response from the USB device 121 via the USB port P2 (YES in step S13), it refers to the correspondence table T1 in the memory unit 15 and identifies the soft ID corresponding to the USB information included in the device information response (step S14).

[0074] Next, the in-vehicle ECU 101 acquires from the in-vehicle ECU 102 software SW used for relay processing that relays communication between the USB device 121 connected to the USB port P2 and the in-vehicle ECU 111 (step S15).

[0075] Next, the in-vehicle ECU 101 installs the acquired software SW (step S16).

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

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

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

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

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

[0081] Next, the USB device 121 transmits a device information response including the USB information to the in-vehicle ECU 101 as a response to the device information request (step S23).

[0082] Next, the in-vehicle ECU 101 acquires the USB information from the device information response, and refers to the correspondence table T1 in the storage unit 15 to identify the soft ID corresponding to the acquired USB information (step S24).

[0083] Next, the in-vehicle ECU 101 transmits a download request including the identified software ID to the in-vehicle ECU 102 (step S25).

[0084] Next, the in-vehicle ECU 102 acquires the software ID from the download request received from the in-vehicle ECU 101, and transmits a download response including the software SW corresponding to the acquired software ID to the in-vehicle ECU 101 (step S26).

[0085] Next, the in-vehicle ECU 101 acquires the software SW from the download response received from the in-vehicle ECU 102, and stores the acquired software SW in the storage unit 15 (step S27).

[0086] Next, the in-vehicle ECU 101 installs the software SW (step S28).

[0087] 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 S29).

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

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

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

[0091] 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 S33).

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

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

[0094] 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 S36).

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

[0096] In the in-vehicle system 301, any one of steps S32, S33, and S34 and steps S35, S36, and S37 may not be performed. More specifically, the in-vehicle system 301 may be configured such that the USB device 121 transmits the communication data Dt1 to the in-vehicle ECU 111 via the in-vehicle ECU 101, while the in-vehicle ECU 111 does not transmit the communication data Dt2. In this case, the proxy unit 13 terminates communication with the USB device 121, but does not terminate communication with the in-vehicle ECU 111.

[0097] 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 proxy unit 13 terminates communication with the in-vehicle ECU 111, but does not terminate communication with the USB device 121.

[0098] Furthermore, in the in-vehicle ECU 101 according to the embodiment of the present disclosure, the management unit 14 is configured to acquire application software, device drivers, and shared libraries as software SW, but this is not limited thereto. The management unit 14 may be configured to acquire application software and shared libraries as software SW, but not acquire device drivers. For example, the storage unit 15 may be configured to store device drivers corresponding to application software used to relay communication between the USB device 121 that may be connected to the USB port P2 and the in-vehicle ECU 111. In this case, when the management unit 14 stores the software SW in the storage unit 15, the proxy unit 13 acquires the software SW and the corresponding device drivers from the storage unit 15 and installs the acquired software SW and device drivers.

[0099] Furthermore, in the in-vehicle ECU 101 according to the embodiment of the present disclosure, the management unit 14 is configured to store the software SW acquired from the in-vehicle ECU 102 in the storage unit 15, but this is not limited to this. The management unit 14 may be configured to store the software SW in a volatile memory in the in-vehicle ECU 101 instead of in the storage unit 15. In this case, the management unit 14 acquires the software SW from the in-vehicle ECU 102 every time the in-vehicle ECU 101 is started.

[0100] (Variation 1) In the in-vehicle ECU 101 according to the embodiment of the present disclosure, the management unit 14 is configured to acquire the software SW from the in-vehicle ECU 102, but this is not limited thereto. The management unit 14 may also be configured to acquire the software SW from the USB device 121 connected to the USB port P2.

[0101] 7 is a diagram illustrating an example of a communication sequence in an in-vehicle system according to Modification 1 of the embodiment of the present disclosure. Referring to FIG. 7, the in-vehicle ECU 101 and the USB device 121 perform the same processes as steps S21 to S23 in FIG. 6 as the processes of steps S41 to S43.

[0102] Next, the management unit 14 in the in-vehicle ECU 101 transmits a download request to the USB device 121 via the USB communication unit 11 and the USB port P2 (step S44).

[0103] Next, the USB device 121 receives the download request from the in-vehicle ECU 101, and transmits a download response including the software SW to the in-vehicle ECU 101 as a response to the received download request (step S45).

[0104] Next, the management unit 14 in the in-vehicle ECU 101 receives a download response from the USB device 121 via the USB port P2 and the USB communication unit 11, acquires the software SW from the received download response, and stores the acquired software SW in the memory unit 15 (step S46).

[0105] Next, the in-vehicle ECUs 101 and 111 and the USB device 121 perform the same processes as steps S28 to S37 in FIG. 6 as the processes from step S47 to step S56.

[0106] The USB device 121 may transmit a download response including a URL (Uniform Resource Locator) indicating the location of the software SW on the cloud server, instead of the software SW, to the in-vehicle ECU 101. In this case, the management unit 14 receives the download response from the USB device 121 via the USB port P2 and the USB communication unit 11, and acquires the software SW from the cloud server by accessing the URL included in the received download response.

[0107] (Variation 2) The management unit 14 may be configured to acquire the software SW from a device external to the vehicle 1. More specifically, the management unit 14 may be configured to acquire the software SW from, for example, a cloud server.

[0108] 8 is a diagram showing an example of a communication sequence in an in-vehicle system according to Modification 2 of the embodiment of the present disclosure. Referring to FIG. 8, the in-vehicle ECU 101 and the USB device 121 perform the same processes as steps S21 to S24 in FIG. 6 as the processes of steps S61 to S64.

[0109] Next, the management unit 14 in the in-vehicle ECU 101 transmits a download request including the software ID to the cloud server via the network (step S65).

[0110] Next, the cloud server receives the download request from the in-vehicle ECU 101, and transmits a download response including the software SW as a response to the received download request to the in-vehicle ECU 101 via the network (step S66).

[0111] Next, the management unit 14 in the in-vehicle ECU 101 receives the download response from the cloud server via the network, acquires the software SW from the received download response, and stores the acquired software SW in the storage unit 15 (step S67).

[0112] Next, the in-vehicle ECUs 101 and 111 and the USB device 121 perform the same processes as steps S28 to S37 in FIG. 6 as the processes of steps S68 to S77.

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

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

[0115] The above description includes the following additional features. [Appendix 1] An in-vehicle device in an in-vehicle network, 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; an acquisition unit that acquires software used in a relay process that relays communication between the USB device, the connection of which is detected by the detection unit, and other devices in the in-vehicle network from a device outside the in-vehicle device; a processing unit that performs the relay process using the software acquired by the acquisition unit, the processing unit performs at least one of a termination of communication with the USB device and a termination of communication with the other device in the relay process; The acquisition unit acquires application software, device drivers, and shared libraries as the software.

[0116] [Appendix 2] An in-vehicle device in an in-vehicle network, a processing circuit and a connection port to which a USB device can be connected via a USB interface; The processing circuitry Detecting the connection of the USB device to the connection port; obtaining software used for relay processing for relaying communication between the USB device whose connection has been detected and other devices in the in-vehicle network from a device external to the in-vehicle device; performing the relay process using the acquired software; In the relay process, the in-vehicle device performs at least one of termination of communication with the USB device and termination of communication with the other device. [Explanation of symbols]

[0117] 1 vehicle 2 Ethernet cables 11 USB communication unit 12 ECU communication section 13 Proxy section 14 Management Department 15 Storage section 101 Automotive ECU 102 Automotive ECU 111 Automotive ECU 121 USB devices 201 In-vehicle network 301 In-Vehicle Systems P1, P1A, P1B communication ports P2, P2A, P2B, P2C USB ports T1 Supported Table

Claims

1. An in-vehicle device in an in-vehicle network, a connection port to which a USB device can be connected via a USB interface; a detection unit that detects the connection of the USB device to the connection port; an acquisition unit that acquires software used in a relay process that relays communication between the USB device, the connection of which is detected by the detection unit, and other devices in the in-vehicle network from a device outside the in-vehicle device; a processing unit that performs the relay process using the software acquired by the acquisition unit, The processing unit performs at least one of a termination of communication with the USB device and a termination of communication with the other device in the relay process.

2. The in-vehicle device according to claim 1 , wherein the acquisition unit acquires the software from a device in the in-vehicle network.

3. The in-vehicle device according to claim 1 , wherein the acquisition unit acquires the software from a device outside the vehicle in which the in-vehicle network is installed.

4. The in-vehicle device according to claim 1 , wherein the acquisition unit acquires the software from the USB device.

5. The in-vehicle device according to claim 1 , wherein the acquisition unit stores the acquired software in a non-volatile storage area of the in-vehicle device.

6. An in-vehicle system in an in-vehicle network, a first in-vehicle device; a second in-vehicle device; the first in-vehicle device includes a connection port to which a USB device can be connected via a USB interface; when the USB device is connected to the connection port, the first in-vehicle device transmits to the second in-vehicle device a download request for downloading software used in a relay process for relaying communication between the USB device and other devices in the in-vehicle network; the second in-vehicle device provides the software to the first in-vehicle device in accordance with the download request received from the first in-vehicle device; the first in-vehicle device performs the relay process using the software provided by the second in-vehicle device; In the relay process, the first vehicle-mounted device performs at least one of termination of communication with the USB device and termination of communication with the other device.

7. A communication method for an in-vehicle device in an in-vehicle network, comprising: the in-vehicle device includes a connection port to which a USB device can be connected via a USB interface; The communication method includes: detecting a connection of the USB device to the connection port; acquiring software used for relay processing for relaying communication between the USB device whose connection has been detected and other devices in the in-vehicle network from a device external to the in-vehicle device; performing the relay process using the acquired software; The communication method, wherein the relay processing step performs at least one of termination of communication with the USB device and termination of communication with the other device.

8. A communication program used in an in-vehicle device in an in-vehicle network, the in-vehicle device includes a connection port to which a USB device can be connected via a USB interface; Computer, a detection unit that detects the connection of the USB device to the connection port; an acquisition unit that acquires software used in a relay process that relays communication between the USB device, the connection of which is detected by the detection unit, and other devices in the in-vehicle network from a device outside the in-vehicle device; a processing unit that performs the relay process using the software acquired by the acquisition unit; It is a program to function as The processing unit performs at least one of termination of communication with the USB device and termination of communication with the other device in the relay process.

Images