In-vehicle device, management method, and management program

Abstract

The vehicle-mounted device is a vehicle-mounted device in a vehicle network, comprising: a first connection port for connecting an external device with a storage area via a USB interface; a detection unit for detecting the connection of the external device to the first connection port; and a mounting processing unit for mounting the file system of the external device detected by the detection unit to a directory accessible from other devices in the vehicle network.

Description

Technical Field

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

[0002] This application claims priority based on Japanese Application No. 2024-9880, filed on January 26, 2024, the entire disclosure of which is incorporated herein. Background Technology

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

[0004] [Existing Technical Documents]

[0005] [Patent Literature]

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

[0007] The vehicle-mounted device disclosed herein is a vehicle-mounted device in a vehicle network, comprising: a first connection port capable of connecting an external device having a storage area via a USB interface; a detection unit for detecting the connection of the external device to the first connection port; and a mounting processing unit for mounting the file system of the external device detected by the detection unit to a directory accessible from other devices in the vehicle network.

[0008] One aspect of this disclosure can be implemented not only as an in-vehicle device with such a characteristic processing unit, but also as a semiconductor integrated circuit that implements part or all of the in-vehicle device, or as a system that includes the in-vehicle device. Attached Figure Description

[0009] Figure 1 This is a diagram illustrating an example of the configuration of an in-vehicle network management system according to an embodiment of this disclosure.

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

[0011] Figure 3 This is a diagram illustrating an example 1 of the connection between a USB memory and an in-vehicle ECU according to an embodiment of the present disclosure.

[0012] Figure 4 This diagram illustrates the directory structure of the shared directory under the mounting processing unit in the vehicle ECU according to an embodiment of this disclosure.

[0013] Figure 5 This is a diagram illustrating Example 2 of the connection between a USB memory and an in-vehicle ECU according to an embodiment of this disclosure.

[0014] Figure 6 This diagram illustrates the directory structure of the shared directory under the mounting processing unit in the vehicle ECU according to an embodiment of this disclosure.

[0015] Figure 7 This is a flowchart illustrating an example of the operational steps involved in the mounting process of an on-board ECU according to an embodiment of this disclosure.

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

[0017] In recent years, with the popularization of car sharing and the expectation of increased processing power of in-vehicle devices, there has been a demand for customized in-vehicle networks by connecting external devices to the in-vehicle devices.

[0018] [The problem this disclosure aims to solve]

[0019] Beyond the technology described in Patent Document 1, this technology aims to enable simple processing in an in-vehicle network to access the storage area of ​​an external device connected via a USB (Universal Serial Bus) interface.

[0020] This disclosure was made to solve the aforementioned problems, and its purpose is to provide an in-vehicle device, management method, and management program that enables easy access to the storage area of ​​an external device connected via a USB interface in an in-vehicle network.

[0021] [The Effects of This Disclosure]

[0022] According to this disclosure, in an in-vehicle network, the storage area of ​​an external device connected via a USB interface can be accessed through simple processing.

[0023] [Description of embodiments of this disclosure]

[0024] First, the contents of the embodiments of this disclosure will be described.

[0025] (1) The vehicle-mounted device of the present disclosure is a vehicle-mounted device in a vehicle network, comprising: a first connection port, which can connect to an external device having a storage area via a USB interface; a detection unit, which detects the connection of the external device to the first connection port; and a mounting processing unit, which mounts the file system of the external device detected by the detection unit to a directory accessible from other devices in the vehicle network.

[0026] With this structure, when an external device is connected to the first connection port, no user operation is required, and the storage area of ​​the external device can be accessed from other devices in the vehicle network. Therefore, the storage area of ​​an external device connected via the USB interface can be accessed with simple processing.

[0027] (2) In (1) above, the vehicle-mounted device may also have multiple first connection ports, and the mounting processing unit may also set the directory name of the file system of the external device to the directory name corresponding to the first connection port connected to the external device.

[0028] With this structure, no user intervention is required, and the directory name of the file system of the external device can be set, and the file system of the external device can be managed using the set directory name.

[0029] (3) In (1) or (2) above, the detection unit may detect the connection of the external device to the first connection port via the hub, the hub having a plurality of second connection ports that comply with USB, and the mounting processing unit sets the directory name of the file system of the external device to the directory name corresponding to the first connection port connected to the hub and the second connection port connected to the external device in the hub.

[0030] With this structure, no user operation is required, and the directory name of the file system of the external device connected to the first connection port via the hub can be set, and the file system of the external device can be managed using the set directory name.

[0031] (4) The management method involved in the embodiments of this disclosure is a management method in a vehicle device in a vehicle network, the vehicle device having a first connection port that can connect to an external device with a storage area via a USB interface, the management method including: a step of detecting the connection of the external device to the first connection port; and a step of mounting the file system of the detected external device to a directory that can be accessed from other devices in the vehicle network.

[0032] In this way, when an external device is connected to the first connection port, no user operation is required, and the storage area of ​​the external device can be accessed from other devices in the vehicle network. Therefore, the storage area of ​​an external device connected via the USB interface can be accessed with simple processing.

[0033] (5) The management program of the embodiments of this disclosure is a management program used in a vehicle device in a vehicle network, the vehicle device having a first connection port that can connect to an external device with a storage area via a USB interface, the management program enabling a computer to function as a detection unit and a mounting processing unit, the detection unit detecting the connection of the external device to the first connection port, and the mounting processing unit mounting the file system of the external device detected by the detection unit to a directory in the vehicle network that can be accessed from other devices.

[0034] With this structure, when an external device is connected to the first connection port, no user operation is required, and the storage area of ​​the external device can be accessed from other devices in the vehicle network. Therefore, the storage area of ​​an external device connected via the USB interface can be accessed with simple processing.

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

[0036] [Structure and Basic Movements]

[0037] Figure 1 This is a diagram illustrating an example of the structure of an in-vehicle network management system according to an embodiment of the present disclosure. (See reference) Figure 1 The vehicle network management system 301 includes an on-board electronic control unit (ECU) 101 and two on-board ECUs 111. The vehicle network management system 301 is mounted on a vehicle 1. The on-board ECU 101 is an example of an on-board device. The on-board ECUs 101 and 111 constitute the vehicle network 201. Alternatively, the vehicle network management system 301 may also have a structure with one or more on-board ECUs 111.

[0038] Vehicle-mounted ECUs 101 and 111 include, for example, relay devices, TCUs (Telematics Communication Units), autonomous driving ECUs, engine ECUs, sensors, navigation devices, human-machine interfaces, and cameras.

[0039] The vehicle ECU 101 has two communication ports PA and USB (registered trademark) ports P1, P2, and P3. Hereinafter, USB ports P1, P2, and P3 will also be referred to as USB port P. USB port P is an example of the first connection port.

[0040] The communication port PA is, for example, a connector capable of connecting an Ethernet (registered trademark) cable 2. The USB port P can connect to an external device with storage space via a USB interface. That is, the USB port P is a connector capable of connecting a USB connector. In the following text, the port numbers of USB ports P1, P2, and P3 are "01", "02", and "03", respectively. Furthermore, the vehicle ECU 101 can also have a structure with two or more USB ports P. Additionally, the vehicle ECU 101 is not limited to a structure with multiple USB ports P; it can also have a structure with only one USB port P.

[0041] The vehicle ECU 111 is connected to the communication port PA in the vehicle ECU 101 via Ethernet cable 2. The vehicle ECU 111 is not limited to the configuration of being connected to the vehicle ECU 101 via Ethernet cable 2, but can also be configured to be connected via communication lines conforming to other standards such as Controller Area Network (CAN) (registered trademark).

[0042] [Topic]

[0043] A technique is desired that allows access to the storage area from the vehicle ECU 111 via a simple process when an external device with a storage area is connected to the USB port P of the vehicle ECU 101.

[0044] For example, when a personal computer has an external device connected to its USB port, the user can specify the mount destination directory for that external device and the storage destination for the data on that external device. Then, the personal computer, following the user's instructions, mounts the file system of that external device to a directory accessible from other devices connected to the personal computer.

[0045] On the other hand, in the vehicle network 201, from a security perspective, user access to the vehicle network management system 301 is restricted. Therefore, the following technology is desired: for example, when an external device is installed on the USB port P of the vehicle ECU 101 after the vehicle 1 leaves the factory, the storage area of ​​the external device can be accessed automatically from the vehicle ECU 111 without user operation.

[0046] Therefore, the vehicle network management system 301 according to the embodiments of this disclosure solves the above problems through the following configuration.

[0047] (Vehicle ECU)

[0048] Figure 2 This is a diagram illustrating the configuration of an on-board ECU according to an embodiment of the present disclosure. (See reference) Figure 2 The vehicle-mounted 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. Part or all of the connection processing unit 11, the mounting processing unit 12, and the communication unit 13 are implemented, 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 aforementioned processing circuit.

[0049] (Connection Example 1)

[0050] Figure 3 This is a diagram illustrating an example 1 of the connection between a USB memory and an in-vehicle ECU according to an embodiment of the present disclosure. Figure 3 This indicates that USB memories 121A and 121B, which are USB memories 121, are connected to USB ports P1 and P2, respectively. USB memory 121 has a storage area. USB memory 121 is an example of an external device.

[0051] Reference Figure 3 The connection processing unit 11 detects the connection of the USB memory 121A and 121B to the USB ports P1 and P2.

[0052] More specifically, when the USB memory 121A is connected to the USB port P1, it sends USB information containing the ID of the USB memory 121A to the vehicle ECU 101. The connection processing unit 11 receives the USB information from the USB memory 121A via the USB port P1 and identifies that the USB memory 121A is connected to the USB port P1 based on the received USB information. Then, the connection processing unit 11 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 that restricts access by the vehicle ECU 111. In addition, the connection processing unit 11 generates connection information C1 representing 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 generated connection information C1 to the mounting processing unit 12.

[0053] Furthermore, when the USB memory 121B is connected to the USB port P2, it sends USB information containing the ID of the USB memory 121B to the vehicle ECU 101. The connection processing unit 11 receives the USB information from the USB memory 121B via the USB port P2, and based on the received USB information, identifies that the USB memory 121B is connected to the USB port P2. Then, the connection processing unit 11 mounts the file system FsB, which is the file system Fs of the USB memory 121B, in the restricted directory Rd. In addition, the connection processing unit 11 generates connection information C2 representing the ID of the USB memory 121B and the port number of the USB port P2 where the USB memory 121B is connected, and outputs the generated connection information C2 to the mounting processing unit 12.

[0054] The mounting processing unit 12 performs mounting processing on the file systems FsA and FsB of the USB storage devices 121A and 121B that are detected and connected by the connection processing unit 11, and mounts them to the directory in the vehicle network 201 that can be accessed from the vehicle ECU 111. Hereinafter, the directory that can be accessed from the vehicle ECU 111 will also be referred to as the shared directory Sd.

[0055] More specifically, the mount processing unit 12 receives connection information C1 from the connection processing unit 11 and obtains the ID and port number from the received connection information C1. Based on the ID and port number obtained from the connection information C1, the mount processing unit 12 determines the file system FsA to be mounted by the connection processing unit 11 to the restricted directory Rd. The mount processing unit 12 unmounts the specified file system FsA and mounts the file system FsA in the shared directory Sd.

[0056] Additionally, the mount processing unit 12 receives connection information C2 from the connection processing unit 11 and obtains the ID and port number from the received connection information C2. Based on the ID and port number obtained from the connection information C2, the mount processing unit 12 determines the file system FsB to be mounted by the connection processing unit 11 to the restricted directory Rd. The mount processing unit 12 unmounts the specified file system FsB and mounts the file system FsB in the shared directory Sd.

[0057] Figure 4 This is a diagram showing the directory structure under the shared directory after the mounting process is performed by the mounting processing unit in the vehicle ECU according to an embodiment of the present disclosure. Figure 4 This represents the directory structure after the mount process in Example 1. Hereafter, the shared directory Sd will be named "usbshared".

[0058] Reference Figure 4The mounting processing unit 12 sets the directory names of the file systems FsA and FsB of the USB storage devices 121A and 121B to the directory names corresponding to the USB ports P1 and P2 connected to the USB storage devices 121A and 121B.

[0059] More specifically, the mounting processing unit 12 sets the directory name of the file system FsA of the USB memory 121A to "usbshared / 01", which is formed by combining the directory name of the shared directory Sd, namely "usbshared", with the port number "01" shown in the connection information C1 by a forward slash.

[0060] In addition, the mounting processing unit 12 sets the directory name of the file system FsB of the USB memory 121B to "usbshared / 02", which is formed by combining "usbshared" and the port number "02" shown in the connection information C2 with a forward slash.

[0061] (Connection Example 2)

[0062] Figure 5 This is a diagram illustrating Example 2 of the connection between a USB memory and an in-vehicle ECU according to an embodiment of this disclosure. Figure 5 This indicates that, compared to connection example 1, the USB hub 131 is further connected to the USB port P3, and the USB memory 121C, which serves as the USB memory 121, is connected to the USB port H1.

[0063] Hub 131 includes USB ports H1, H2, and H3, which serve as USB ports H. The port numbers of USB ports H1, H2, and H3, which are also the hub port numbers, are "01", "02", and "03", respectively. USB port H allows connection to external devices with storage space via a USB interface. That is, USB port H is a connector capable of connecting to a USB connector. USB port H is an example of a second connection port. Furthermore, hub 131 may also have a structure with two or more USB ports H. Additionally, hub 131 is not limited to a structure with multiple USB ports H; it may also have a structure with only one USB port H.

[0064] Reference Figure 5 The connection processing unit 11 detects the connection of the USB memory 121C to the USB port P3 via the hub 131.

[0065] More specifically, when the USB memory 121C is connected to the USB port P3 via the hub 131, it sends USB information containing the ID of the USB memory 121C to the vehicle ECU 101 via the hub 131. Additionally, the hub 131 sends hub information indicating the hub port number of the USB port H1 to which the USB memory 121C is connected to the vehicle ECU 101.

[0066] The connection processing unit 11 receives hub information and USB information from the hub 131 and the USB memory 121C, respectively. Based on the received hub information and USB information, it identifies that the hub 131 is connected to the USB port P3 and the USB memory 121C is connected to the USB port H1 in the hub 131. Then, the connection processing unit 11 mounts the file system FsC, which is the file system Fs of the USB memory 121C, in the restricted directory Rd. In addition, the connection processing unit 11 generates connection information C3, which represents the ID of the USB memory 121C, the hub port number of the USB port H1 connected to the USB memory 121C, and the port number of the USB port P3 connected to the hub 131, and outputs the generated connection information C3 to the mounting processing unit 12.

[0067] The mounting processing unit 12 performs mounting processing to mount the file system FsC of the USB memory 121C that was detected as connected by the connection processing unit 11 to the shared directory Sd.

[0068] More specifically, the mount processing unit 12 receives connection information C3 from the connection processing unit 11, and obtains the ID, hub port number, and port number from the received connection information C3. Based on the ID, hub port number, and port number obtained from the connection information C3, the mount processing unit 12 determines the file system FsC to be mounted by the connection processing unit 11 to the restricted directory Rd. The mount processing unit 12 unmounts the specified file system FsC and mounts the file system FsC in the shared directory Sd.

[0069] Figure 6 This is a diagram showing the directory structure under the shared directory after the mounting process is performed by the mounting processing unit in the vehicle ECU according to an embodiment of the present disclosure. Figure 6 This represents the directory structure after the mounting process in Example 2.

[0070] Reference Figure 6 The mounting 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 connected to the hub 131 and the USB port H1 in the hub 131 where the USB memory 121C is connected.

[0071] More specifically, the mounting processing unit 12 sets the directory name of the file system FsC of the USB memory 121C to "usbshared / 03.01". This "usbshared / 03.01" is formed by combining "usbshared" with the port number "03" shown in the connection information C3 with a forward slash, and combining "03" with the hub port number "01" shown in the connection information C3 with a period.

[0072] (Publication of the catalog)

[0073] Refer again Figure 3 and Figure 5 For example, the vehicle ECU 101 acts as an NFS (Network File System) server, exposing the directory of the file system Fs mounted in the shared directory Sd to the vehicle network 201.

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

[0075] When the mounting processing unit 12 stores the mounting information in the storage unit 14, the communication unit 13 uses the OfferService message based on SOME / IP (Scalable service-Oriented Middleware over IP) to provide the vehicle ECU 111 with the service of using the file system Fs indicated by the mounting information.

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

[0077] The vehicle ECU 111 receives an OfferService message M1 from the vehicle ECU 101 and obtains the catalog name and service ID from the received OfferService message M1. If the vehicle ECU 111 accepts the offer of the service represented by the obtained service ID, it sends a FindService message M2 containing the service ID to the vehicle ECU 101.

[0078] In addition, the vehicle ECU 111 sends an RpcMountRequest message M3 to the vehicle ECU 101 to request access to the directory using the obtained directory name.

[0079] The communication unit 13 in the vehicle ECU 101 receives the RpcMountRequest message M3 from the vehicle ECU 111 via the communication port PA, and in response to the received RpcMountRequest message M3, sends the RpcMountReply message M4 to the vehicle ECU 111 via the communication port PA.

[0080] When the vehicle ECU 111 receives the RpcMountReply message M4 from the vehicle ECU 101, it accesses the file system Fs of the USB memory 121 via the vehicle ECU 101 to write data to and read data from the USB memory 121.

[0081] For example, the vehicle ECU 111 sends an RpcRequest message M5 to the vehicle ECU 101. The RpcRequest message M5 includes the data Dw to be written to the USB memory 121 and the directory name of the file system Fs of the USB memory 121.

[0082] When the communication unit 13 in the vehicle ECU 101 receives the RpcRequest message M5 via the communication port PA, it obtains the data Dw and the directory name from the received RpcRequest message M5 and outputs the obtained data Dw and the directory name to the connection processing unit 11.

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

[0084] The communication unit 13 receives a completion notification from the connection processing unit 11 and, in response to the RpcRequest message M5, sends an RpcReply message M6, indicating that the writing of data Dw is complete, to the vehicle ECU 111 via the communication port PA.

[0085] In addition, for example, the vehicle ECU 111 sends an RpcRequest message M7 to the vehicle ECU 101, which includes the filename of the data Dr read from the USB memory 121 and the directory name of the file system Fs of the USB memory 121.

[0086] When the communication unit 13 in the vehicle ECU 101 receives the 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.

[0087] The connection processing unit 11 receives the filename and directory name from the communication unit 13, and performs data acquisition processing to retrieve the filename data Dr 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.

[0088] The communication unit 13 receives data Dr from the connection processing unit 11 and, in response to the RpcRequest message M7, sends an RpcReply message M8 containing data Dr to the vehicle ECU 111 via the communication port PA.

[0089] It should be noted that the vehicle ECU 111 can also be configured to not perform either writing data to or reading data from the USB memory 121.

[0090] [Action Flow]

[0091] Figure 7 This is a flowchart illustrating an example of the operational steps involved in the mounting process of an on-board ECU according to an embodiment of this disclosure.

[0092] Reference Figure 7 First, the vehicle ECU 101 waits for the arrival of USB information (no in step S11). When it receives USB information from the USB memory 121 (yes in step S11), it recognizes that the USB memory 121 is connected to the USB port P, and mounts the file system Fs of the USB memory 121 to the restricted directory Rd (step S12).

[0093] Next, the 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 vehicle ECU 101 sets the directory name of the file system Fs according to the above process (step S13).

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

[0095] Next, the vehicle ECU 101 waits for new USB information to arrive (no in step S11).

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

[0097] Reference Figure 8 First, when the USB memory 121 is connected to the USB port P in the vehicle ECU 101, it sends USB information to the vehicle ECU 101 (step S21).

[0098] Next, the vehicle ECU 101 receives USB information from the USB memory 121, identifies that the USB memory 121 is connected to the USB port P, and mounts the file system Fs of the USB memory 121 to the restricted directory Rd (step S22).

[0099] Next, the 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 (step S23).

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

[0101] Next, the vehicle ECU 101 sends an OfferService message M1 to the vehicle ECU 111 (step S25).

[0102] Next, the vehicle ECU 111 sends the FindService message M2 to the vehicle ECU 101 (step S26).

[0103] Next, the vehicle ECU 111 sends an RpcMountRequest message M3 to the vehicle ECU 101 (step S27).

[0104] Next, the vehicle ECU 101 sends an RpcMountReply message M4 to the vehicle ECU 111 via the communication port PA (step S28).

[0105] Next, the vehicle ECU 111 sends an RpcRequest message M5, which includes the data Dw and the directory name of the file system Fs, to the vehicle ECU 101 (step S29).

[0106] Next, the vehicle ECU 101 obtains the data Dw and 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).

[0107] Next, the vehicle ECU 101 sends the RpcReply message M6 to the vehicle ECU 111 via the communication port PA (step S31).

[0108] Next, the vehicle ECU 111 sends an RpcRequest message M7, which includes the filename of the data Dr and the directory name of the file system Fs, to the vehicle ECU 101 (step S32).

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

[0110] Next, the vehicle ECU 101 sends the RpcReply message M8 containing the data Dr to the vehicle ECU 111 via the communication port PA (step S34).

[0111] Furthermore, the order of steps S29, S30, S31 and S32, S33, S34 is not limited to those described above, and their order can be changed. Additionally, in the vehicle network management system 301, any one of steps S29, S30, S31 and S32, S33, S34 may be omitted.

[0112] Furthermore, in the vehicle ECU 101 of the embodiments of this disclosure, the mounting processing unit 12 sets the directory names of the file systems FsA and FsB of the USB storage devices 121A and 121B to the directory names corresponding to the USB ports P1 and P2 connected to the USB storage devices 121A and 121B, but it is not limited to this. The mounting processing unit 12 may also set the directory names of the file systems FsA and FsB of the USB storage devices 121A and 121B to a predetermined directory name regardless of the USB ports P1 and P2.

[0113] Furthermore, in the vehicle ECU 101 of the embodiments of this disclosure, the directory name of the file system FsC of the USB memory 121C is set to a directory name corresponding to the USB port P3 connected to the hub 131 and the USB port H1 in which the USB memory 121C is connected to the hub 131, but it is not limited to this. The mounting processing unit 12 may also be a structure that sets the directory name of the file system FsC of the USB memory 121C to a predetermined directory name regardless of the USB ports P3 and H1.

[0114] Furthermore, while the vehicle ECU 101 of this disclosure has a structure with a USB port P, it is not limited to this. The vehicle ECU 101 may also have a connection port that allows connection to external devices 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 a connection of an external device to the connection port. Then, the mount processing unit 12 mounts the file system of the external device detected by the connection processing unit 11 to the shared directory Sd.

[0115] The above embodiments should be considered illustrative rather than limiting in all respects. The scope of the invention is defined not by the foregoing description but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0116] Each process (function) in the above-described embodiments is implemented by a processing circuit including one or more processors. Besides the one or more processors, the processing circuit may also be composed of an integrated circuit combining one or more memories, various analog circuits, and various digital circuits. The one or more memories store programs (commands) that cause the one or more processors to execute the above processes. The one or more processors may execute the above processes according to the programs read from the one or more memories, or they may execute the above processes according to logic circuits designed to pre-execute the above processes. The processors may be various processors suitable for computer control, such as CPUs (Central Processing Units), GPUs (Graphics Processing Units), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and ASICs (Application Specific Integrated Circuits). Furthermore, physically separate processors may also cooperate to execute the above processes. For example, the processors installed on multiple physically separate computers can also cooperate with each other via networks such as LAN (Local Area Network), WAN (Wide Area Network), and the Internet to execute the aforementioned processes. The programs can be installed into the memory from external server devices via the aforementioned network, or they can be transferred from recording media such as CD-ROM (Compact Disc Read Only Memory), DVD-ROM (Digital Versatile Disk Read Only Memory), and semiconductor memory to the memory.

[0117] The above description includes the following features.

[0118] [Postscript 1]

[0119] An in-vehicle device, which is an in-vehicle device in an in-vehicle network, includes: a first connection port for connecting an external device with a storage area via a USB interface; a detection unit for detecting the connection of the external device to the first connection port; a mounting processing unit for mounting the file system of the external device detected by the detection unit to a directory accessible from other devices in the in-vehicle network; and a communication unit for providing services using the file system mounted by the mounting processing unit to the other devices.

[0120] [Postscript 2]

[0121] An in-vehicle device, which is an in-vehicle device in an in-vehicle network, includes: a processing circuit; and a first connection port, which can connect to an external device having a storage area via a USB interface. The processing circuit detects the connection of the external device to the first connection port and mounts the detected file system of the external device to a directory in the in-vehicle network that can be accessed from other devices.

[0122] [Explanation of reference numerals in the attached figures]

[0123] 1 vehicle

[0124] 2 Ethernet cables

[0125] 11 Connection Processing Unit

[0126] 12 Mounting and Processing Department

[0127] 13 Ministry of Communications

[0128] 14 Storage Department

[0129] 101 Vehicle ECU

[0130] 111 Vehicle ECU

[0131] 121, 121A, 121B, 121C US memory

[0132] 131 Hub

[0133] 201 Vehicle Network

[0134] 301 Vehicle Network Management System

[0135] PA communication port

[0136] P, P1, P2, P3 US ports

[0137] H, H1, H2, H3 US ports

[0138] Sd shared directory

[0139] Fs, FsA, FsB, FsC file systems.

Claims

1. An in-vehicle device that is an in-vehicle device in an in-vehicle network, wherein, have: The first connection port can connect to an external device with storage space via a USB interface; The detection unit detects the connection of the external device to the first connection port; as well as The mounting processing unit mounts the file system of the external device detected by the detection unit to a directory accessible from other devices in the vehicle network.

2. The vehicle-mounted device according to claim 1, wherein, The vehicle-mounted device has multiple of the first connection ports. The mounting processing unit sets the directory name of the file system of the external device to the directory name corresponding to the first connection port to which the external device is connected.

3. The vehicle-mounted device according to claim 1 or 2, wherein, The detection unit detects the connection of the external device to the first connection port via a hub, the hub having multiple second connection ports conforming to USB. The mounting processing unit sets the directory name of the file system of the external device to the directory name corresponding to the first connection port connected to the hub and the second connection port of the external device connected to the hub.

4. A management method, which is a management method for in-vehicle devices in an in-vehicle network, wherein, The vehicle-mounted device has a first connection port that enables connection to an external device with storage space via a USB interface. The management method includes: The steps of detecting the connection of the external device to the first connection port; and The step of mounting the file system of the detected connected external device to a directory that can be accessed from other devices in the vehicle network.

5. A management program used in an on-board unit within an on-board network, wherein, The vehicle-mounted device has a first connection port that enables connection to an external device with storage space via a USB interface. The management program enables the computer to function as both a detection unit and a mounting and processing unit. The detection unit detects the connection of the external device to the first connection port. The mounting processing unit mounts the file system of the external device detected by the detection unit to a directory accessible from other devices in the vehicle network.

Images