On-vehicle device, management method, and management program

Abstract

Provided is an in-vehicle device in an in-vehicle network comprising: a first connection port capable of connecting an external apparatus having a storage region via a USB interface; a detection unit for detecting connection of the external apparatus to the first connection port; and a mount processing unit for mounting a file system of the external apparatus whose connection is detected by the detection unit to a directory which is accessible from other apparatuses in the in-vehicle network.

Description

In-vehicle device, management method, and management program

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

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

[0003] International Publication No. 2020 / 179123

[0004] The in-vehicle device of the present disclosure is an in-vehicle device in an in-vehicle network, and includes a first connection port to which an external device having a storage area can be connected via a USB interface, a detection unit that detects connection of the external device to the first connection port, and a mount processing unit that mounts the file system of the external device whose connection is detected by the detection unit in a directory that is accessible from other devices in the in-vehicle network.

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

[0006] FIG. 1 is a diagram illustrating an example of the configuration of an in-vehicle 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 a first 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 diagram illustrating a second example of connection of a USB memory to an in-vehicle ECU according to an embodiment of the present disclosure. FIG. 6 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. 7 is a flowchart defining an example of an operational procedure when an in-vehicle ECU according to an embodiment of the present disclosure performs a mount process. FIG. 8 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 device, a management method, 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 device according to an embodiment of the present disclosure is an in-vehicle device in an in-vehicle network, and includes: a first connection port to which an external device having a storage area can be connected via a USB interface; a detection unit that detects connection of the external device to the first connection port; and a mount processing unit that mounts a file system of the external device, the connection of which is detected by the detection unit, in a directory accessible from other devices in the in-vehicle network.

[0012] With this configuration, when an external device is connected to the first connection port, the storage area of ​​the external device can be accessed by other devices on the in-vehicle network without requiring user operation, thereby enabling easy access to the storage area of ​​the external device connected via the USB interface.

[0013] (2) In the above (1), the in-vehicle device may be provided with a plurality of the first connection ports, and the mount processing unit may set a directory name of the file system of the external device to a directory name corresponding to the first connection port to which the external device is connected.

[0014] With this configuration, it is possible to set a directory name for the file system of the external device without requiring any user operation, and to manage the file system of the external device using the set directory name.

[0015] (3) In (1) or (2) above, the detection unit may detect the connection of the external device to the first connection port via a hub having multiple second connection ports conforming to USB, and the mount processing unit may set the directory name of the file system of the external device to a directory name corresponding to the first connection port to which the hub is connected and the second connection port in the hub to which the external device is connected.

[0016] With this configuration, it is possible to set a directory name for the file system of an external device connected to the first connection port via a hub without requiring user operation, and to manage the file system of the external device using the set directory name.

[0017] (4) A management method according to an embodiment of the present disclosure is a management method for an in-vehicle device in an in-vehicle network, the in-vehicle device having a first connection port to which an external device having a storage area can be connected via a USB interface, and the management method includes a step of detecting connection of the external device to the first connection port, and a step of mounting a file system of the external device whose connection has been detected in a directory accessible from other devices in the in-vehicle network.

[0018] With this method, when an external device is connected to the first connection port, it is possible to enable other devices in the in-vehicle network to access the storage area of ​​the external device without requiring user operation, thereby enabling simple processing to access the storage area of ​​the external device connected via the USB interface.

[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 first connection port to which an external device having a storage area can be connected via a USB interface, and the program causes a computer to function as a detection unit that detects connection of the external device to the first connection port and a mount processing unit that mounts the file system of the external device whose connection is detected by the detection unit in a directory accessible from other devices in the in-vehicle network.

[0020] With this configuration, when an external device is connected to the first connection port, the storage area of ​​the external device can be accessed by other devices on the in-vehicle network without requiring user operation, thereby enabling easy access to the storage area of ​​the external device connected via the USB interface.

[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 two in-vehicle ECUs 111. The in-vehicle network management system 301 is mounted on a vehicle 1. The in-vehicle ECU 101 is an example of an 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 two communication ports PA and USB (registered trademark) ports P1, P2, and P3. Hereinafter, each of the USB ports P1, P2, and P3 will also be referred to as a USB port P. The USB port P is an example of a first 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 P can connect an external device having a storage area via a USB interface. That is, the USB port P is a connector to which a USB connector can be connected. Hereinafter, the port numbers of the USB ports P1, P2, and P3 are assumed to be "01," "02," and "03," respectively. Note that the in-vehicle ECU 101 may be configured to include two or four or more USB ports P. Furthermore, the in-vehicle ECU 101 is not limited to a configuration including multiple USB ports P, and may be configured to include only one USB port P.

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

[0027] [Problem] When an external device having a storage area is connected to a USB port P of an 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 P 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 showing the 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. 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] (Connection Example 1) Fig. 3 is a diagram illustrating connection example 1 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 P1 and P2, respectively. The USB memory 121 has a storage area. The USB memory 121 is an example of an external device.

[0033] Referring to FIG. 3, the connection processing unit 11 detects the connection of the USB memories 121A and 121B to the USB ports P1 and P2.

[0034] More specifically, when the USB memory 121A is connected to the USB port P1, 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 P1 and recognizes that the USB memory 121A has been connected to the USB port P1 based on the received USB information. The connection processing unit 11 then mounts the file system FsA, which is the file system Fs of the USB memory 121A, in a predetermined restricted directory Rd, which is a directory to which access by the in-vehicle ECU 111 is restricted. The connection processing unit 11 also creates connection information C1 indicating the ID of the USB memory 121A and the port number of the USB port P1 to which the USB memory 121A is connected, and outputs the created connection information C1 to the mounting processing unit 12.

[0035] Furthermore, when the USB memory 121B is connected to the USB port P2, 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 P2 and recognizes that the USB memory 121B has been connected to the USB port P2 based on the received USB information. The connection processing unit 11 then mounts the file system FsB, which is the file system Fs of the USB memory 121B, in the restricted directory Rd. The connection processing unit 11 also creates connection information C2 indicating the ID of the USB memory 121B and the port number of the USB port P2 to which the USB memory 121B is connected, and outputs the created connection information C2 to the mounting processing unit 12.

[0036] The mount processing unit 12 performs a mount 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.

[0037] More specifically, the mount processing unit 12 receives connection information C1 from the connection processing unit 11 and acquires an ID and a port number from the received connection information C1. Based on the ID and port number acquired from the connection information C1, 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. The mount processing unit 12 unmounts the identified file system FsA and mounts the file system FsA on the shared directory Sd.

[0038] The mount processing unit 12 also receives connection information C2 from the connection processing unit 11 and acquires an ID and a port number from the received connection information C2. Based on the ID and port number acquired from the connection information C2, the mount processing unit 12 identifies the file system FsB mounted on the restricted directory Rd by the connection processing unit 11. The mount processing unit 12 unmounts the identified file system FsB and mounts the file system FsB on the shared directory Sd.

[0039] 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. 4 illustrates the directory structure after a mount process in connection example 1. Hereinafter, the directory name of the shared directory Sd is assumed to be "usbshared."

[0040] Referring to FIG. 4, the mounting processing unit 12 sets the directory names of the file systems FsA and FsB of the USB memories 121A and 121B to the directory names corresponding to the USB ports P1 and P2 to which the USB memories 121A and 121B are connected.

[0041] More specifically, the mount processing unit 12 sets the directory name of the file system FsA of the USB memory 121A to "usbshared / 01", which is the directory name of the shared directory Sd, "usbshared", and the port number "01" indicated by the connection information C1, combined with a slash.

[0042] The mount processing unit 12 also sets the directory name of the file system FsB in the USB memory 121B to "usbshared / 02," which is obtained by combining "usbshared" with "02," the port number indicated by the connection information C2, using a slash.

[0043] 5 is a diagram illustrating a second connection example of a USB memory to an in-vehicle ECU according to an embodiment of the present disclosure. Compared to the first connection example, the second connection example illustrates a state in which a USB-compliant hub 131 is further connected to the USB port P3, and a USB memory 121C, which is the USB memory 121, is connected to the USB port H1.

[0044] The hub 131 includes USB ports H1, H2, and H3. The port numbers of the USB ports H1, H2, and H3 are assumed to be "01," "02," and "03," respectively. The USB port H can connect to an external device having a storage area via a USB interface. That is, the USB port H is a connector to which a USB connector can be connected. The USB port H is an example of a second connection port. The hub 131 may be configured to include two or four or more USB ports H. Furthermore, the hub 131 is not limited to a configuration including multiple USB ports H, and may be configured to include only one USB port H.

[0045] Referring to FIG. 5, the connection processing unit 11 detects the connection of the USB memory 121C to the USB port P3 via the hub 131.

[0046] More specifically, when the USB memory 121C is connected to the USB port P3 via the hub 131, the USB memory 121C transmits USB information including the ID of the USB memory 121C to the in-vehicle ECU 101 via the hub 131. The hub 131 also transmits hub information indicating the hub port number of the USB port H1 to which the USB memory 121C is connected to the in-vehicle ECU 101.

[0047] The connection processing unit 11 receives hub information and USB information from the hub 131 and the USB memory 121C, respectively, and recognizes, based on the received hub information and USB information, that the hub 131 is connected to the USB port P3 and the USB memory 121C is connected to the USB port H1 of the hub 131. The connection processing unit 11 then mounts the file system FsC, which is the file system Fs of the USB memory 121C, in the restricted directory Rd. The connection processing unit 11 also creates connection information C3 that indicates the ID of the USB memory 121C, the hub port number of the USB port H1 to which the USB memory 121C is connected, and the port number of the USB port P3 to which the hub 131 is connected, and outputs the created connection information C3 to the mounting processing unit 12.

[0048] The mount processing unit 12 performs a mount process of mounting the file system FsC of the USB memory 121C, the connection of which is detected by the connection processing unit 11, on the shared directory Sd.

[0049] More specifically, the mount processing unit 12 receives connection information C3 from the connection processing unit 11 and acquires an ID, a hub port number, and a port number from the received connection information C3. Based on the ID, hub port number, and port number acquired from the connection information C3, the mount processing unit 12 identifies the file system FsC mounted on the restricted directory Rd by the connection processing unit 11. The mount processing unit 12 unmounts the identified file system FsC and mounts the file system FsC on the shared directory Sd.

[0050] 6 is a diagram illustrating a directory structure under a shared directory after a mounting process by a mounting processor in an in-vehicle ECU according to an embodiment of the present disclosure. FIG. 6 illustrates the directory structure after a mounting process in connection example 2.

[0051] Referring to Figure 6, the mount processing unit 12 sets the directory name of the file system FsC of the USB memory 121C to the directory name corresponding to the USB port P3 to which the hub 131 is connected and the USB port H1 in the hub 131 to which the USB memory 121C is connected.

[0052] More specifically, the mount processing unit 12 sets the directory name of the file system FsC of the USB memory 121C to "usbshared / 03.01", which is obtained by combining "usbshared" and "03", the port number indicated by the connection information C3, with a slash, and by combining "03" and "01", the hub port number indicated by the connection information C3, with a period.

[0053] (Publication of Directory) Referring again to FIGS. 3 and 5, 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.

[0054] More specifically, the mount processing unit 12 stores mount information indicating the directory name of the file system Fs in the storage unit 14 .

[0055] When the mount processing unit 12 stores the mount information 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 using an OfferService message conforming to SOME / IP (Scalable service-Oriented Middleware over IP).

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

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

[0058] The in-vehicle ECU 111 also transmits to the in-vehicle ECU 101 an RpcMountRequest message M3 for requesting access to the directory with the acquired directory name.

[0059] The communication unit 13 in the in-vehicle ECU 101 receives the RpcMountRequest message M3 from the in-vehicle ECU 111 via the communication port PA, and transmits an RpcMountReply message M4 to the in-vehicle ECU 111 via the communication port PA as a response to the received RpcMountRequest message M3.

[0060] 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 writes data to the USB memory 121 and reads data from the USB memory 121.

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

[0062] When the communication unit 13 in the in-vehicle ECU 101 receives an RpcRequest message M5 via the communication port PA, 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.

[0063] 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 121 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.

[0064] 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 111 via the communication port PA as a response to the RpcRequest message M5.

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

[0066] When the communication unit 13 in the vehicle ECU 101 receives an RpcRequest message M7 via the communication port PA, 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.

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

[0068] 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 111 via the communication port PA as a response to the RpcRequest message M7.

[0069] The in-vehicle ECU 111 may be configured not to write data to the USB memory 121 or not to read data from the USB memory 121 .

[0070] [Operation Flow] FIG. 7 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.

[0071] Referring to Figure 7, 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).

[0072] 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. Here, the in-vehicle ECU 101 sets the directory name of the file system Fs according to the procedure described above (step S13).

[0073] Next, the in-vehicle ECU 101 stores mount information indicating the directory name of the file system Fs in the storage unit 14 (step S14).

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

[0075] FIG. 8 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.

[0076] Referring to FIG. 8, 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).

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

[0078] 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 S23).

[0079] Next, the in-vehicle ECU 101 stores mount information indicating the directory name of the file system Fs in the storage unit 14 (step S24).

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

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

[0082] Next, the in-vehicle ECU 111 transmits an RpcMountRequest message M3 to the in-vehicle ECU 101 (step S27).

[0083] Next, the in-vehicle ECU 101 transmits an RpcMountReply message M4 to the in-vehicle ECU 111 via the communication port PA (step S28).

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

[0085] 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 S30).

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

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

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

[0089] 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 S34).

[0090] The order of steps S29, S30, S31 and steps S32, S33, S34 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 S29, S30, S31 and steps S32, S33, S34.

[0091] In addition, in the in-vehicle ECU 101 according to the embodiment of the present disclosure, the mounting processing unit 12 is configured to set the directory names of the file systems FsA and FsB of the USB memories 121A and 121B to directory names corresponding to the USB ports P1 and P2 to which the USB memories 121A and 121B are connected, but this is not limitative. The mounting processing unit 12 may be configured to set the directory names of the file systems FsA and FsB of the USB memories 121A and 121B to predetermined directory names regardless of the USB ports P1 and P2.

[0092] Furthermore, in the in-vehicle ECU 101 according to the embodiment of the present disclosure, the directory name of the file system FsC in the USB memory 121C is set to a directory name corresponding to the USB port P3 to which the hub 131 is connected and the USB port H1 to which the USB memory 121C is connected in the hub 131. However, this is not limitative. The mounting processing unit 12 may be configured to set the directory name of the file system FsC in the USB memory 121C to a predetermined directory name regardless of the USB port P3 or H1.

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

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

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

[0096] The above description includes the following additional features: [Supplementary Note 1] An in-vehicle device in an in-vehicle network, comprising: a first connection port to which an external device having a storage area can be connected via a USB interface; a detection unit that detects connection of the external device to the first connection port; a mount processing unit that mounts a file system of the external device, the connection of which is detected by the detection unit, in a directory accessible from other devices in the in-vehicle network; and a communication unit that provides services using the file system mounted by the mount processing unit to the other devices.

[0097] [Supplementary Note 2] An in-vehicle device in an in-vehicle network, comprising: a processing circuit; and a first connection port to which an external device having a storage area can be connected via a USB interface, wherein the processing circuit detects connection of the external device to the first connection port; and mounts a file system of the detected external device in a directory accessible from other devices in the in-vehicle network.

[0098] 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 In-vehicle ECU 121, 121A, 121B, 121C USB memory 131 Hub 201 In-vehicle network 301 In-vehicle network management system PA Communication port P, P1, P2, P3 USB port H, H1, H2, H3 USB port Sd Shared directory Fs, FsA, FsB, FsC File system

Claims

1. An in-vehicle device in an in-vehicle network, comprising: a first connection port capable of connecting an external device having a storage area via a USB interface; a detection unit that detects connection of the external device to the first connection port; and a mount processing unit that mounts a file system of the external device detected by the detection unit to a directory accessible from other devices in the in-vehicle network.

2. The in-vehicle device according to claim 1, wherein the in-vehicle device includes a plurality of the first connection ports, and the mount processing unit sets a directory name of the file system of the external device to a directory name corresponding to the first connection port to which the external device is connected.

3. The in-vehicle device according to claim 1 or 2, wherein the detection unit detects connection of the external device to the first connection port via a hub including a plurality of second connection ports conforming to USB, and the mount processing unit sets a directory name of the file system of the external device to a directory name corresponding to the first connection port to which the hub is connected and the second connection port in the hub to which the external device is connected.

4. A management method for an in-vehicle device in an in-vehicle network, wherein the in-vehicle device includes a first connection port capable of connecting an external device having a storage area via a USB interface, and the management method includes: detecting connection of the external device to the first connection port; and mounting a file system of the external device detected as being connected to a directory accessible from other devices in the in-vehicle network.

5. A management program used in an in-vehicle device in an in-vehicle network, wherein the in-vehicle device includes a first connection port capable of connecting an external device having a storage area via a USB interface, and the management program causes a computer to function as: a detection unit that detects connection of the external device to the first connection port; and a mount processing unit that mounts a file system of the external device detected by the detection unit to a directory accessible from other devices in the in-vehicle network.

Images