On-vehicle system, on-vehicle device, and management program

Abstract

This on-vehicle system comprises: a USB device that stores setting information on a directory; and a first on-vehicle device including a connection port to which the USB device can be connected via a USB interface. When the USB device has been connected to the connection port, the first on-vehicle device acquires the setting information from the USB device, and the first on-vehicle device mounts the file system of the USB device in a directory accessible from another device in an on-vehicle network and sets the directory name of the file system of the USB device on the basis of the setting information.

Description

In-vehicle system, in-vehicle device and management program

[0001] This application claims priority from Japanese Patent Application No. 2024-9884, 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 system of the present disclosure includes a USB device that stores setting information related to a directory, and a first in-vehicle device in an in-vehicle network, the first in-vehicle device having a connection port to which the 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 acquires the setting information from the USB device, mounts the file system of the USB device in a directory accessible from other devices in the in-vehicle network, and sets a directory name of the file system of the USB device based on the setting information.

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

[0006] FIG. 1 is a diagram illustrating an example of the configuration of an in-vehicle network management 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 an example of connection of a USB memory to an in-vehicle ECU according to an embodiment of the present disclosure. FIG. 4 is a diagram illustrating a directory structure under a shared directory after a mount process by a mount processing unit in an in-vehicle ECU according to an embodiment of the present disclosure. FIG. 5 is a flowchart defining an example of an operation procedure when an in-vehicle ECU according to an embodiment of the present disclosure performs a mount process. FIG. 6 is a diagram illustrating an example of a communication sequence in an in-vehicle network management 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 enables access to the storage area of ​​an external device connected via a USB (Universal Serial Bus) interface in an in-vehicle network through simple processing.

[0009] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide an in-vehicle system, an in-vehicle device, and a management program that enable simple processing to access the storage area of ​​an external device connected via a USB interface in an in-vehicle network.

[0010] Effect of the Present Disclosure According to the present disclosure, in an in-vehicle network, it is possible to access the storage area of ​​an external device connected via a USB interface through a simple process.

[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 system according to an embodiment of the present disclosure includes a USB device that stores setting information related to a directory, and a first in-vehicle device in an in-vehicle network, the first in-vehicle device having a connection port to which the USB device can be connected via a USB interface, wherein when the USB device is connected to the connection port, the first in-vehicle device acquires the setting information from the USB device, mounts a file system of the USB device in a directory accessible from other devices in the in-vehicle network, and sets a directory name of the file system of the USB device based on the setting information.

[0012] With this configuration, when a USB device is connected to the connection port of the first in-vehicle device, the directory name of the file system of the USB device can be set using the setting information stored in the USB device without requiring user operation, and the file system of the USB device can be accessed from other devices on the in-vehicle network. Therefore, the storage area of ​​the external device connected via the USB interface can be accessed with simple processing.

[0013] (2) In the above (1), the USB device may further store access information indicating devices that can access the file system of the USB device, and the first in-vehicle device may acquire the access information from the USB device connected to the connection port and, based on the access information, restrict access by the other devices to the file system of the USB device.

[0014] With this configuration, for example, it is possible to restrict access to the file system of a USB device by devices that are not permitted to access the file system, thereby improving security in the in-vehicle network.

[0015] (3) In the above (1) or (2), the in-vehicle system may further include a second in-vehicle device in the in-vehicle network, the second in-vehicle device storing directory information regarding a directory name of a file system of the USB device, and the second in-vehicle device may access the file system of the USB device mounted by the first in-vehicle device based on the directory information.

[0016] With this configuration, the file system of the USB device can be easily accessed from the second in-vehicle device using a directory name that is pre-registered in the second in-vehicle device and is set when the file system of the USB device is mounted, without requiring any user operation.

[0017] (4) 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 that stores setting information related to a directory 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 the setting information from the USB device whose connection is detected by the detection unit; and a mount processing unit that mounts a file system of the USB device whose connection is detected by the detection unit in a directory accessible from other devices in the in-vehicle network, and the mount processing unit sets a directory name of the file system of the USB device based on the setting information acquired by the acquisition unit.

[0018] With this configuration, when a USB device is connected to the connection port, the directory name of the file system of the USB device can be set using the setting information stored in the USB device without requiring any user operation, and the file system of the USB device can be accessed from other devices on the in-vehicle network. Therefore, the storage area of ​​an external device connected via the USB interface can be accessed with simple processing.

[0019] (5) A management program according to an embodiment of the present disclosure is a management 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 that stores setting information related to a directory can be connected via a USB interface, and the management program is a program for 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 the setting information from the USB device whose connection is detected by the detection unit; and a mount processing unit that mounts the file system of the USB device whose connection is detected by the detection unit in a directory accessible from other devices in the in-vehicle network, and the mount processing unit sets a directory name of the file system of the USB device based on the setting information acquired by the acquisition unit.

[0020] With this configuration, when a USB device is connected to the connection port, the directory name of the file system of the USB device can be set using the setting information stored in the USB device without requiring any user operation, and the file system of the USB device can be accessed from other devices on the in-vehicle network. Therefore, the storage area of ​​an external device connected via the USB interface can be accessed with simple processing.

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

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

[0023] The in-vehicle ECUs 101 and 111 are, 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.

[0024] The in-vehicle ECU 101 includes communication ports PA1 and PA2 and USB (registered trademark) ports PB1, PB2, and PB3. Hereinafter, each of the communication ports PA1 and PA2 will also be referred to as a communication port PA, and each of the USB ports PB1, PB2, and PB3 will also be referred to as a USB port PB. The USB port PB is an example of a connection port.

[0025] The communication port PA is a connector to which, for example, an Ethernet (registered trademark) cable 2 can be connected. The USB port PB is capable of connecting a USB memory 121 (described later) via a USB interface. That is, the USB port PB is a connector to which a USB connector can be connected. Note that the in-vehicle ECU 101 may be configured to include two or four or more USB ports PB. Furthermore, the in-vehicle ECU 101 is not limited to a configuration including multiple USB ports PB, and may be configured to include only one USB port PB.

[0026] The on-board ECUs 111A and 111B are connected to communication ports PA1 and PA2 of the on-board ECU 101, respectively, via an Ethernet cable 2. Hereinafter, the IP addresses of the on-board ECUs 111A and 111B are assumed to be "IPA" and "IPB," respectively. Note that the on-board ECU 111 is not limited to being connected to the on-board ECU 101 via the Ethernet cable 2, and may be connected via a communication line conforming to another standard, such as CAN (Controller Area Network) (registered trademark).

[0027] [Problem] When an external device such as a USB memory having a storage area is connected to the USB port PB of the in-vehicle ECU 101, a technique is desired that enables the in-vehicle ECU 111 to access the storage area through simple processing.

[0028] For example, when an external device is connected to a USB port of a personal computer, the personal computer receives an operation from the user to specify the directory to which the external device is to be mounted, the destination of data on the external device, etc. Then, in accordance with the user's operation, the personal computer mounts the file system of the external device in a directory that can be accessed from other devices connected to the personal computer.

[0029] On the other hand, in the in-vehicle network 201, from the viewpoint of security, etc., user access to the in-vehicle network management system 301 is restricted. Therefore, for example, when an external device is retrofitted to the USB port PB of the in-vehicle ECU 101 after the vehicle 1 is shipped, a technique is desired that enables the in-vehicle ECU 111 to automatically access the storage area of ​​the external device without requiring user operation.

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

[0031] (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 connection processing unit 11, a mounting processing unit 12, a communication unit 13, and a storage unit 14. The connection processing unit 11 is an example of a detection unit and an acquisition unit. Some or all of the connection processing unit 11, the mounting processing unit 12, and the communication unit 13 are realized, for example, by a processing circuit including one or more processors. The storage unit 14 is, for example, a non-volatile memory included in the processing circuit.

[0032] 3 is a diagram illustrating an example of connection of a USB memory to an in-vehicle ECU according to an embodiment of the present disclosure. Fig. 3 illustrates a state in which USB memories 121A and 121B, which are USB memories 121, are connected to USB ports PB1 and PB2, respectively. The USB memory 121 has a storage area. The USB memory 121 is an example of a USB device.

[0033] 3, the USB memory 121A stores setting information D1A, which is setting information D1 related to directories, and access information D2A, which is access information D2. The USB memory 121B stores setting information D1B, which is setting information D1 related to directories, and access information D2B, which is access information D2. For example, the setting information D1 is configuration data that includes, as text data, at least a portion of the directory name of the file system Fs of the USB memory 121. For example, the access information D2 is configuration data that indicates the IP addresses of devices that can access the file system Fs of the USB memory 121.

[0034] For example, USB memory 121A stores setting information D1A including text data indicating "usb01" and access information D2A indicating an IP address of "IPA." USB memory 121B stores setting information D1B including text data indicating "usb02" and access information D2B indicating an IP address of "IPB."

[0035] For example, the setting information D1 and the access information D2 are stored in the USB memory 121 by a maintenance company that performs maintenance on the vehicle 1 before the USB memory 121 is connected to the in-vehicle ECU 101 .

[0036] The in-vehicle ECU 111A stores directory information D3A, which is directory information D3 relating to the directory names of the file system FsA in the USB memory 121A. The in-vehicle ECU 111B stores directory information D3B, which is directory information D3 relating to the directory names of the file system FsB in the USB memory 121B. For example, the directory information D3 is configuration data that includes at least a portion of the directory names of the file system Fs in the USB memory 121 as text data.

[0037] As an example, the in-vehicle ECU 111A stores directory information D3A including text data indicating "usb01," and the in-vehicle ECU 111B stores directory information D3B including text data indicating "usb02."

[0038] For example, after the vehicle 1 is shipped, the directory information D3 is stored in a storage area of ​​the on-board ECU 111 by a maintenance company that performs maintenance on the vehicle 1. The directory information D3 may be stored in a storage area of ​​the on-board ECU 111 before the vehicle 1 is shipped, or may be automatically downloaded and stored in a storage area of ​​the on-board ECU 111 when the firmware of the on-board ECU 111 is updated.

[0039] (Connection Detection) The connection processing unit 11 detects the connection of the USB memories 121A and 121B to the USB ports PB1 and PB2.

[0040] More specifically, when the USB memory 121A is connected to the USB port PB1, it transmits USB information including the ID of the USB memory 121A to the in-vehicle ECU 101. The connection processing unit 11 receives the USB information from the USB memory 121A via the USB port PB1 and recognizes, based on the received USB information, that the USB memory 121A has been connected to the USB port PB1. The connection processing unit 11 then mounts the file system FsA, which is the file system Fs of the USB memory 121A, on a predetermined restricted directory Rd, which is a directory to which access by the in-vehicle ECU 111 is restricted.

[0041] Furthermore, when the USB memory 121B is connected to the USB port PB2, it transmits USB information including the ID of the USB memory 121B to the in-vehicle ECU 101. The connection processing unit 11 receives the USB information from the USB memory 121B via the USB port PB2 and recognizes, based on the received USB information, that the USB memory 121B has been connected to the USB port PB2. The connection processing unit 11 then mounts the file system FsB, which is the file system Fs of the USB memory 121B, on the restricted directory Rd.

[0042] When the USB memory 121 is connected to the USB port PB, the connection processing unit 11 acquires the setting information D1 and the access information D2 from the USB memory 121. That is, the connection processing unit 11 acquires the setting information D1 and the access information D2 from the USB memory 121 that has been detected as being connected to the USB port PB.

[0043] More specifically, when the connection processing unit 11 mounts the file system FsA of the USB memory 121A on the restricted directory Rd, it acquires the setting information D1A and the access information D2A from the USB memory 121A. Then, the connection processing unit 11 creates connection information C1 including the ID of the USB memory 121A, the port number of the USB port PB1 to which the USB memory 121A is connected, the setting information D1A, and the access information D2A, and outputs the created connection information C1 to the mounting processing unit 12.

[0044] The mount processing unit 12 receives the connection information C1 from the connection processing unit 11 and stores the received connection information C1 in the storage unit 14 .

[0045] Furthermore, when the connection processing unit 11 mounts the file system FsB of the USB memory 121B on the restricted directory Rd, it acquires the setting information D1B and the access information D2B from the USB memory 121B. Then, the connection processing unit 11 creates connection information C2 including the ID of the USB memory 121B, the port number of the USB port PB2 to which the USB memory 121B is connected, the setting information D1B, and the access information D2B, and outputs the created connection information C2 to the mounting processing unit 12.

[0046] The mount processing unit 12 receives the connection information C2 from the connection processing unit 11 and stores the received connection information C2 in the storage unit 14. Hereinafter, each of the connection information C1 and C2 will also be referred to as connection information C.

[0047] (Mounting Process) The mounting processing unit 12 performs mounting process of mounting the file systems FsA and FsB of the USB memories 121A and 121B, the connection of which has been detected by the connection processing unit 11, in a directory accessible from the in-vehicle ECU 111 in the in-vehicle network 201. Hereinafter, the directory accessible from the in-vehicle ECU 111 is also referred to as a shared directory Sd.

[0048] More specifically, the mount processing unit 12 identifies the file system FsA that has been mounted on the restricted directory Rd by the connection processing unit 11, based on the ID and port number included in the connection information C1 in the storage unit 14. The mount processing unit 12 unmounts the identified file system FsA and mounts the file system FsA on the shared directory Sd.

[0049] Furthermore, the mount processing unit 12 identifies the file system FsB mounted on the restricted directory Rd by the connection processing unit 11, based on the ID and port number included in the connection information C2 in the storage unit 14. The mount processing unit 12 unmounts the identified file system FsB and mounts the file system FsB on the shared directory Sd.

[0050] 4 is a diagram showing the directory structure under the shared directory after the mounting process by the mounting processor in the in-vehicle ECU according to the embodiment of the present disclosure. Fig. 4 shows the directory structure after the mounting process in the connection example shown in Fig. 3. Hereinafter, the directory name of the shared directory Sd is assumed to be "usbshared."

[0051] Referring to FIG. 4, the mounting processing unit 12 sets the directory name of the file system Fs of the USB memory 121 based on the setting information D1 acquired by the connection processing unit 11 .

[0052] More specifically, the mounting processing unit 12 acquires the setting information D1A from the connection information C1 in the storage unit 14. Then, the mounting processing unit 12 sets the directory name of the file system FsA of the USB memory 121A to "usbshared / usb01," which is obtained by combining, with a slash, "usbshared," which is the directory name of the shared directory Sd, and "usb01," which is indicated by the text data included in the setting information D1A.

[0053] Furthermore, the mounting processing unit 12 acquires the setting information D1B from the connection information C2 in the storage unit 14. Then, the mounting processing unit 12 sets the directory name of the file system FsB of the USB memory 121B to "usbshared / usb02," which is obtained by combining "usbshared" and "usb02" indicated by the text data included in the setting information D1B with a slash.

[0054] (Publication of Directory) Referring back to FIG. 3, for example, the in-vehicle ECU 101 serves as an NFS (Network File System) server and publishes the directory of the file system Fs mounted on the shared directory Sd to the in-vehicle network 201 .

[0055] More specifically, when the mount processing unit 12 sets the directory name of the file system FsA in the USB memory 121A, it acquires access information D2A from the connection information C1 in the storage unit 14. The mount processing unit 12 stores mount information MtA in the storage unit 14, the mount information MtA including the directory name of the file system FsA and the acquired access information D2A.

[0056] Furthermore, after setting the directory name of file system FsB in USB memory 121B, mount processing unit 12 acquires access information D2B from connection information C2 in storage unit 14. Mount processing unit 12 saves mount information MtB, which includes the directory name of file system FsB and the acquired access information D2B, in storage unit 14. Hereinafter, each of mount information MtA and MtB will also be referred to as mount information Mt.

[0057] When the mount processing unit 12 stores the mount information Mt in the memory unit 14, the communication unit 13 provides the in-vehicle ECU 111 with a service using the file system Fs indicated by the mount information Mt using an OfferService message conforming to SOME / IP (Scalable service-Oriented Middleware over IP).

[0058] More specifically, the communication unit 13 generates an OfferService message M1 including the service ID of a service that can be provided using the file system Fs indicated by the mount information Mt, and transmits the generated OfferService message M1 to the vehicle ECU 111 via the communication port PA.

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

[0060] Furthermore, based on the directory information D3, the in-vehicle ECU 111 accesses the file system Fs of the USB memory 121 mounted by the in-vehicle ECU 101. For example, based on the directory name of the shared directory Sd notified in advance by the in-vehicle ECU 101 and the directory information D3, the in-vehicle ECU 111 identifies the directory name of the file system Fs of the USB memory 121, and transmits an RpcMountRequest message M3 to the in-vehicle ECU 101 to request access to the directory with the identified directory name.

[0061] More specifically, based on the directory name of the shared directory Sd and the directory information D3A, the in-vehicle ECU 111A identifies the directory name "usbshared / usb01" of the file system FsA of the USB memory 121A, and sends an RpcMountRequest message M3 including the identified directory name and the IP address of the in-vehicle ECU 111A to the in-vehicle ECU 101.

[0062] In addition, based on the directory name of the shared directory Sd and the directory information D3B, the in-vehicle ECU 111B identifies the directory name "usbshared / usb02" of the file system FsB of the USB memory 121B, and sends an RpcMountRequest message M3 including the identified directory name and the IP address of the in-vehicle ECU 111B to the in-vehicle ECU 101.

[0063] The in-vehicle ECU 101 restricts access by the in-vehicle ECU 111 to the file system Fs of the USB memory 121 based on the access information D2.

[0064] More specifically, when the communication unit 13 in the in-vehicle ECU 101 receives an RpcMountRequest message M3 from the in-vehicle ECU 111 via the communication port PA, the communication unit 13 acquires a directory name and an IP address from the received RpcMountRequest message M3. The communication unit 13 then acquires mount information Mt including the acquired directory name from the storage unit 14. The communication unit 13 then compares the IP address included in the mount information Mt acquired from the storage unit 14 with the IP address acquired from the RpcMountRequest message M3.

[0065] If the IP address included in the mount information Mt acquired from the storage unit 14 matches the IP address acquired from the RpcMountRequest message M3, the communication unit 13 permits the in-vehicle ECU 111 that sent the RpcMountRequest message M3 to access the file system Fs. In this case, the communication unit 13 transmits an RpcMountReply message M4 to the in-vehicle ECU 111 that sent the RpcMountRequest message M3 via the communication port PA.

[0066] On the other hand, if the IP address included in the mount information Mt acquired from the storage unit 14 does not match the IP address acquired from the RpcMountRequest message M3, the communication unit 13 does not permit the in-vehicle ECU 111 that sent the RpcMountRequest message M3 to access the file system Fs. In this case, the communication unit 13 discards the RpcMountRequest message M3 and does not send the RpcMountReply message M4.

[0067] When the in-vehicle ECU 111 receives the RpcMountReply message M4 from the in-vehicle ECU 101 , the in-vehicle ECU 111 accesses the file system Fs of the USB memory 121 via the in-vehicle ECU 101 and performs writing to and reading from the USB memory 121 .

[0068] For example, the in-vehicle ECU 111A writes data to the USB memory 121A. More specifically, the in-vehicle ECU 111A transmits to the in-vehicle ECU 101 an RpcRequest message M5 including data Dw to be written to the USB memory 121A and a directory name of the file system FsA of the USB memory 121A.

[0069] When the communication unit 13 in the in-vehicle ECU 101 receives an RpcRequest message M5 via the communication port PA1, it acquires the data Dw and the directory name from the received RpcRequest message M5 and outputs the acquired data Dw and directory name to the connection processing unit 11.

[0070] The connection processing unit 11 receives the data Dw and the directory name from the communication unit 13 and performs a save process to save the data Dw in the USB memory 121A corresponding to the directory name. When the save process is completed, the connection processing unit 11 outputs a completion notification to the communication unit 13.

[0071] Upon receiving the completion notification from the connection processing unit 11, the communication unit 13 transmits an RpcReply message M6 indicating that writing of the data Dw has been completed to the in-vehicle ECU 111A via the communication port PA1 as a response to the RpcRequest message M5.

[0072] Furthermore, for example, the in-vehicle ECU 111B reads data from the USB memory 121B. More specifically, the in-vehicle ECU 111B transmits to the in-vehicle ECU 101 an RpcRequest message M7 including the file name of the data Dr to be read from the USB memory 121B and the directory name of the file system FsB of the USB memory 121B.

[0073] When the communication unit 13 in the vehicle ECU 101 receives an RpcRequest message M7 via communication port PA2, it obtains the file name and directory name of the data Dr from the received RpcRequest message M7 and outputs the obtained file name and directory name to the connection processing unit 11.

[0074] The connection processing unit 11 receives a file name and a directory name from the communication unit 13, and performs an acquisition process to acquire data Dr having the file name from the USB memory 121 corresponding to the directory name. The connection processing unit 11 outputs the acquired data Dr to the communication unit 13.

[0075] The communication unit 13 receives the data Dr from the connection processing unit 11 and transmits an RpcReply message M8 including the data Dr to the in-vehicle ECU 111B via the communication port PA2 as a response to the RpcRequest message M7.

[0076] The in-vehicle ECU 111A may be configured to read data from the USB memory 121B in addition to or instead of writing data to the USB memory 121A. The in-vehicle ECU 111B may be configured to write data to the USB memory 121B in addition to or instead of reading data from the USB memory 121B.

[0077] [Operation Flow] FIG. 5 is a flowchart defining an example of an operation procedure when the in-vehicle ECU according to the embodiment of the present disclosure performs a mounting process.

[0078] Referring to Figure 5, first, the in-vehicle ECU 101 waits for the arrival of USB information (NO in step S11), and when it receives the USB information from the USB memory 121 (YES in step S11), it recognizes that the USB memory 121 has been connected to the USB port P and mounts the file system Fs of the USB memory 121 in the restricted directory Rd (step S12).

[0079] Next, the vehicle ECU 101 acquires setting information D1 and access information D2 from the USB memory 121 connected to the USB port P, and stores connection information C including the ID of the USB memory 121, the port number of the USB port P, the setting information D1, and the access information D2 in the memory unit 14 (step S13).

[0080] Next, the in-vehicle ECU 101 unmounts the file system Fs mounted in the restricted directory Rd and mounts the file system Fs in the shared directory Sd. The in-vehicle ECU 101 then sets the directory name of the file system Fs based on the setting information D1 in accordance with the procedure described above (step S14).

[0081] Next, the in-vehicle ECU 101 stores the mount information Mt including the directory name of the file system Fs and the access information D2 in the storage unit 14 (step S15).

[0082] Next, the in-vehicle ECU 101 waits for the arrival of new USB information (NO in step S11).

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

[0084] Referring to FIG. 6, first, when the USB memory 121 is connected to the USB port P of the in-vehicle ECU 101, the USB memory 121 transmits USB information to the in-vehicle ECU 101 (step S21).

[0085] Next, the in-vehicle ECU 101 receives USB information from the USB memory 121, recognizes that the USB memory 121 has been connected to the USB port P, and mounts the file system Fs of the USB memory 121 in the restricted directory Rd (step S22).

[0086] Next, the in-vehicle ECU 101 acquires the setting information D1 and the access information D2 from the USB memory 121 (step S23).

[0087] Next, the in-vehicle ECU 101 unmounts the file system Fs mounted on the restricted directory Rd, and mounts the file system Fs on the shared directory Sd (step S24).

[0088] Next, the in-vehicle ECU 101 stores the mount information Mt including the directory name of the file system Fs and the access information D2 in the storage unit 14 (step S25).

[0089] Next, the in-vehicle ECU 101 transmits the OfferService message M1 to the in-vehicle ECU 111 (step S26).

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

[0091] Next, the in-vehicle ECU 111 identifies the directory name of the file system Fs in the USB memory 121 based on the directory name of the shared directory Sd notified in advance by the in-vehicle ECU 101 and the directory information D3 (step S28).

[0092] Next, the in-vehicle ECU 111 transmits an RpcMountRequest message M3 including the specified directory name and the IP address of the in-vehicle ECU 111 to the in-vehicle ECU 101 (step S29).

[0093] Next, the in-vehicle ECU 101 acquires the directory name and IP address from the received RpcMountRequest message M3, and compares the acquired IP address with the IP address included in the mount information Mt that includes the acquired directory name (step S30).

[0094] Next, if the IP address included in the mount information Mt matches the IP address acquired from the RpcMountRequest message M3, the in-vehicle ECU 101 transmits an RpcMountReply message M4 to the in-vehicle ECU 111 via the communication port PA (step S31).

[0095] Next, the in-vehicle ECU 111 transmits an RpcRequest message M5 including the data Dw and the directory name of the file system Fs to the in-vehicle ECU 101 (step S32).

[0096] Next, the in-vehicle ECU 101 acquires the data Dw and the directory name from the received RpcRequest message M5, and stores the data Dw in the USB memory 121 corresponding to the directory name (step S33).

[0097] Next, the in-vehicle ECU 101 transmits an RpcReply message M6 to the in-vehicle ECU 111 via the communication port PA (step S34).

[0098] Next, the in-vehicle ECU 111 transmits an RpcRequest message M7 including the file name of the data Dr and the directory name of the file system Fs to the in-vehicle ECU 101 (step S35).

[0099] Next, the in-vehicle ECU 101 acquires the file name and directory name from the received RpcRequest message M7, and acquires the data Dr of the file name from the USB memory 121 that corresponds to the directory name (step S36).

[0100] Next, the in-vehicle ECU 101 transmits an RpcReply message M8 including the data Dr to the in-vehicle ECU 111 via the communication port PA (step S37).

[0101] The order of steps S32, S33, and S34 and steps S35, S36, and S37 is not limited to the above, and may be reversed. Also, in the in-vehicle network management system 301, it is not necessary to perform either one of steps S32, S33, and S34 or steps S35, S36, and S37.

[0102] Furthermore, in the in-vehicle network management system 301 according to the embodiment of the present disclosure, the USB memory 121 is configured to store the access information D2, but this is not limited to this. The USB memory 121 may be configured not to store the access information D2. In the in-vehicle network management system 301, if the USB memory 121 does not store the access information D2, the in-vehicle ECU 101 does not restrict access to the file system Fs of the USB memory 121 based on the access information D2.

[0103] Furthermore, in the in-vehicle network management system 301 according to the embodiment of the present disclosure, the in-vehicle ECU 111 is configured to store the directory information D3, but this is not limited thereto. The in-vehicle ECU 111 may be configured not to store the directory information D3. In this case, for example, the communication unit 13 in the in-vehicle ECU 101 transmits an OfferService message M1 including a directory name of the file system Fs indicated by the mount information Mt to the in-vehicle ECU 111 via the communication port PA. The in-vehicle ECU 111 acquires the directory name from the received OfferService message M1 and transmits an RpcMountRequest message M3 including the acquired directory name and the IP address of the in-vehicle ECU 111 to the in-vehicle ECU 101.

[0104] Furthermore, although the in-vehicle ECU 101 according to the embodiment of the present disclosure has been described as having a USB port P, this is not limiting. The in-vehicle ECU 101 may be configured to have a connection port to which an external device can be connected via an interface conforming to a standard other than USB, instead of the USB port P. In this case, the connection processing unit 11 detects connection of the external device to the connection port. Then, the mounting processing unit 12 mounts the file system of the external device whose connection is detected by the connection processing unit 11 on the shared directory Sd.

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

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

[0107] The above description includes the following additional features: [Supplementary Note 1] A management method for an in-vehicle system including a USB device that stores setting information related to directories, and a first in-vehicle device in an in-vehicle network, the first in-vehicle device having a connection port to which the USB device can be connected via a USB interface, the management method including the steps of: when the USB device is connected to the connection port, the first in-vehicle device acquiring the setting information from the USB device; and, when the USB device is connected to the connection port, the first in-vehicle device mounting a file system of the USB device in a directory accessible from other devices in the in-vehicle network, and setting a directory name of the file system of the USB device based on the setting information.

[0108] [Supplementary Note 2] A management method for an in-vehicle device in an in-vehicle network, the in-vehicle device having a connection port to which a USB device storing setting information related to a directory can be connected via a USB interface, the management method comprising the steps of: detecting connection of the USB device to the connection port; acquiring the setting information from the USB device whose connection has been detected; and mounting a file system of the USB device whose connection has been detected in a directory accessible from other devices in the in-vehicle network, wherein in the step of mounting the file system of the USB device, a directory name of the file system of the USB device is set based on the acquired setting information.

[0109] [Supplementary Note 3] An in-vehicle device in an in-vehicle network, comprising: a processing circuit; and a connection port to which a USB device that stores setting information related to a directory can be connected via a USB interface, wherein the processing circuit: detects connection of the USB device to the connection port; acquires the setting information from the USB device whose connection has been detected; mounts a file system of the USB device whose connection has been detected in a directory accessible from other devices in the in-vehicle network; and sets a directory name of the file system of the USB device based on the acquired setting information.

[0110] REFERENCE SIGNS LIST 1 Vehicle 2 Ethernet cable 11 Connection processing unit 12 Mount processing unit 13 Communication unit 14 Storage unit 101 In-vehicle ECU 111, 111A, 111B In-vehicle ECU 121, 121A, 121B USB memory 201 In-vehicle network 301 In-vehicle network management system PA, PA1, PA2 Communication port PB, PB1, PB2, PB3 USB port D1, D1A, D1B Setting information D2, D2A, D2B Access information D3, D3A, D3B Directory information Sd Shared directory Fs, FsA, FsB File system

Claims

1. An in-vehicle system comprising: a USB device that stores setting information regarding a directory; and a first in-vehicle device in an in-vehicle network, the first in-vehicle device including a connection port through which the USB device can be connected via a USB interface. When the USB device is connected to the connection port, the first in-vehicle device acquires the setting information from the USB device, mounts the file system of the USB device to a directory accessible from other devices in the in-vehicle network, and sets a directory name of the file system of the USB device based on the setting information.

2. The USB device further stores access information indicating a device that can access the file system of the USB device. The first in-vehicle device acquires the access information from the USB device connected to the connection port and restricts access to the file system of the USB device by the other devices based on the access information. The in-vehicle system according to claim 1.

3. The in-vehicle system further comprises: a second in-vehicle device in the in-vehicle network, the second in-vehicle device storing directory information regarding a directory name of the file system of the USB device. The second in-vehicle device accesses the file system of the USB device mounted by the first in-vehicle device based on the directory information. The in-vehicle system according to claim 1 or claim 2.

4. An in-vehicle device in an in-vehicle network, comprising: a connection port through which a USB device that stores setting information regarding a directory 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 the setting information from the USB device whose connection is detected by the detection unit; and a mount processing unit that mounts the file system of the USB device whose connection is detected by the detection unit to a directory accessible from other devices in the in-vehicle network. The mount processing unit sets a directory name of the file system of the USB device based on the setting information acquired by the acquisition unit.

5. A management 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 that stores setting information regarding a directory via a USB interface, a computer, a detection unit that detects connection of the USB device to the connection port, an acquisition unit that acquires the setting information from the USB device detected by the detection unit, and a mount processing unit that mounts a file system of the USB device detected by the detection unit to a directory accessible from other devices in the in-vehicle network. The mount processing unit sets a directory name of the file system of the USB device based on the setting information acquired by the acquisition unit.

Images