Management system, management device, and management program

Abstract

To provide a management system, a management device, an on-vehicle device, and a management program that can prevent a portable recording medium from being easily taken out.SOLUTION: A management system according to the embodiment includes an on-vehicle device and a management device. The on-vehicle device includes a fixing unit that fixes a portable recording medium. The management device includes a storage unit and a control unit. The storage unit stores identification information unique to the on-vehicle device. When receiving an operation of selecting the on-vehicle device that includes the portable recording medium to be released from fixation, the control unit transmits a release command to the on-vehicle device corresponding to identification information unique to the on-vehicle device so as to cause the fixing unit to release the fixation of portable recording medium.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The disclosed embodiments relate to a management system, a management device, an in-vehicle device, and a management program.

Background Art

[0002] Conventionally, there are drive recorders that record images captured by an in-vehicle camera on a portable recording medium such as an SD (registered trademark) card. In a drive recorder, for example, when an image that is inconvenient for a user is recorded, the user may take out the portable recording medium and erase the data.

[0003] For this reason, there are drive recorders configured such that the portable recording medium can be taken out only when an input according to a predetermined operation procedure set in advance is received (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the conventional technology, when the drive recorder is in a state where it can accept inputs according to the predetermined operation procedure, for example, in a state where the power is on, anyone who knows the predetermined operation procedure can take out the portable recording medium.

[0006] One aspect of the embodiments has been made in view of the above, and an object thereof is to provide a management system, a management device, an in-vehicle device, and a management program that can prevent the portable recording medium from being easily taken out.

Means for Solving the Problems

[0007] A management system according to one embodiment includes an in-vehicle unit and a management device. The in-vehicle unit includes a fixing part for fixing a portable recording medium. The management device includes a storage unit and a control unit. The storage unit stores identification information specific to the in-vehicle unit. When the control unit receives a selection operation from the in-vehicle unit to release the fixing of the portable recording medium, it sends a release command to the in-vehicle unit corresponding to the identification information specific to the in-vehicle unit, causing the fixing part to release the fixing of the portable recording medium. [Effects of the Invention]

[0008] A management system, management device, in-vehicle device, and management program according to one embodiment of the system have the effect of preventing the portable recording medium from being easily removed. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 is an explanatory diagram showing a management system according to an embodiment. [Figure 2] Figure 2 is a block diagram showing an example configuration of an in-vehicle device, a management device, and a terminal device according to an embodiment. [Figure 3] Figure 3 is a flowchart showing an example of a process performed by the control unit of the in-vehicle device according to the embodiment. [Figure 4] Figure 4 is a flowchart showing an example of a process performed by the control unit of the management device according to the embodiment. [Figure 5] Figure 5 is a flowchart showing an example of a process performed by the control unit of the in-vehicle device according to this embodiment. [Figure 6] Figure 6 is a flowchart showing an example of a process performed by the control unit of the management device according to the embodiment. [Figure 7] Figure 7 is a flowchart showing an example of a process performed by the control unit of the terminal device according to this embodiment. [Figure 8] Figure 8 is a flowchart showing an example of a process performed by the control unit of the in-vehicle device according to the embodiment. [Modes for carrying out the invention]

[0010] The embodiments of the management system, management device, in-vehicle unit, and management program will be described in detail below with reference to the attached drawings. However, the present invention is not limited to the embodiments described below.

[0011] [1. Management System Configuration] Figure 1 is an explanatory diagram showing a management system 1 according to an embodiment. As shown in Figure 1, it includes a plurality of in-vehicle units 10, a management device 20, and a terminal device 30. Each in-vehicle unit 10 is installed in each of the plurality of vehicles 100. The plurality of vehicles 100 are, for example, vehicles used by unspecified users such as rental cars or company cars. Note that the vehicles 100 may be vehicles owned by individuals.

[0012] The in-vehicle device 10 is, for example, a drive recorder. The in-vehicle device 10 includes a camera 14 and a removable portable recording medium, and captures images of the area around the vehicle 100 and records the image information of the captured images onto the portable recording medium.

[0013] The portable recording medium is, for example, an SD card (registered trademark) 11. The portable recording medium is not limited to an SD card 11, but may also be a miniSD (registered trademark) card, a microSD (registered trademark) card, a microSDHC (registered trademark) card, or a microSDXC (registered trademark) card.

[0014] The management device 20 is, for example, a device used by an administrator 101 who manages multiple in-vehicle units 10. The management device 20 is, for example, a desktop or notebook personal computer, or a server device.

[0015] The terminal device 30 is a device used by the administrator 101 who manages the in-vehicle device 10. The terminal device 30 is, for example, a smartphone on which an application program for managing a plurality of in-vehicle devices 10 is installed. Note that the terminal device 30 may be a tablet terminal or a portable device dedicated to in-vehicle device management.

[0016] The in-vehicle device 10, the management device 20, and the terminal device 30 are configured to be capable of mutually transmitting and receiving various data by wireless communication via a communication network 110 such as the Internet, for example.

[0017] [2. Configurations of In-Vehicle Device, Management Device, and Terminal Device] Figure 2 is a block diagram illustrating a configuration example of the in-vehicle device 10, the management device 20, and the terminal device 30 according to the embodiment.

[0018] As shown in Figure 2, an SD card 11 is inserted inside the in-vehicle device 10. The in-vehicle device 10 includes a fixing unit 12, a control unit 13, and a camera 14. The fixing unit 12 includes an electric lock mechanism and an openable / closable lid that fix the SD card 11 inserted into the in-vehicle device 10 at an appropriate position to make it unremovable. The fixing unit 12 can also release the fixation of the SD card 11 to make it removable. The operation of the fixing unit 12 is controlled by the control unit 13.

[0019] The control unit 13 includes a microcomputer and various circuits having a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and the like. The control unit 13 controls the operations of the fixing unit 12 and the camera 14 by causing the CPU to execute a program stored in the ROM using the RAM as a work area.

[0020] Furthermore, the control unit 13 may be composed of hardware such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array), either in part or in whole.

[0021] Camera 14 is equipped with a solid-state imaging device, such as a CMOS (Complementary Metal Oxide Semiconductor) image sensor. Camera 14 is controlled by the control unit 13, and captures images of the area around the vehicle 100 on which it is mounted, and outputs the image information of the captured images to the SD card 11 for recording.

[0022] The management device 20 includes an operation unit 21, a control unit 22, and a storage unit 23. The operation unit 21 is, for example, an information input device such as a keyboard and a mouse. The operation unit 21 receives information input operations from the administrator 101 and outputs commands corresponding to the input operations to the control unit 22.

[0023] The control unit 22 includes a microcomputer with a CPU, ROM, RAM, and various circuits. The control unit 22 communicates with the in-vehicle unit 10 and the terminal device 30 and manages the in-vehicle unit 10 by having the CPU execute a program stored in ROM, using RAM as a workspace.

[0024] Furthermore, the control unit 22 may be composed of hardware such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array), either in part or in whole.

[0025] The memory unit 23 is, for example, an information storage device such as a data flash, and stores the management program 24 and the in-vehicle device identification information 25. The control unit 22 manages multiple in-vehicle devices 10 by executing the management program 24.

[0026] The in-vehicle device identification information 25 is unique identification information for each in-vehicle device 10, managed by the management device 20. Examples of the in-vehicle device identification information 25 include the Wi-Fi address number used by the in-vehicle device 10 for wireless communication, and the IMEI (International Mobile Equipment Identifier) ​​number used for LTE (Long Term Evolution) communication.

[0027] The management device 20 can store the in-vehicle unit identification information 25 entered by the administrator 101. The management device 20 can also store the in-vehicle unit identification information 25 transmitted from the in-vehicle unit 10 during initial startup. Furthermore, the management device 20 can send a transmission command for the in-vehicle unit identification information 25 to each in-vehicle unit 10 and store the in-vehicle unit identification information 25 returned as a response.

[0028] The terminal device 30 includes a control unit 31 and an operation unit 32. The control unit 31 includes a microcomputer having a CPU, ROM, RAM, and various circuits. The control unit 31 manages the in-vehicle device 10 by communicating with the management device 20, with the CPU executing a program stored in ROM and using RAM as a work area.

[0029] The control unit 31 may be composed of hardware such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array), either partially or entirely. The operation unit 32 is, for example, a touch panel display, which receives information input operations from the administrator 101 and outputs commands to the control unit 31 in accordance with the input operations.

[0030] In typical dashcams, if the SD card 11 is not properly inserted (i.e., partially inserted), image information cannot be recorded to the SD card 11. Furthermore, if the SD card 11 is partially inserted, it may become dislodged from the dashcam due to vibrations of the vehicle 100, leading to malfunction.

[0031] Therefore, the in-vehicle device 10 according to this embodiment is equipped with a fixing part 12 that secures the SD card 11 in an appropriate position and makes it impossible to remove. This prevents the SD card 11 from being partially inserted and from falling out due to vibration or the like.

[0032] Furthermore, when the SD card 11 is secured, the fixing part 12 closes the hinged cover. This allows the in-vehicle unit 10 to protect the SD card 11 from static electricity, thus preventing damage to image information due to static electricity.

[0033] Furthermore, with typical dashcams, for example, if images undesirable to the user are recorded, the user may remove the SD card 11 and illegally erase the data.

[0034] Therefore, in the management system 1 according to this embodiment, the administrator 101 sends a fixing command from the management device 20 to the in-vehicle unit 10. When the in-vehicle unit 10 receives a fixing command from the management device 20, it fixes the SD card 11 with the fixing part 12.

[0035] In the management system 1 according to this embodiment, the administrator 101 sends a release command from the management device 20 to the in-vehicle unit 10. The in-vehicle unit 10 releases the fixing of the SD card 11 by the fixing part 12 only when it receives the release command from the management device 20. This makes it possible for the management system 1 to prevent users other than the administrator from easily removing the SD card 11.

[0036] Furthermore, the management device 20 may be configured to send a lock command or a release command to the in-vehicle unit 10 when it receives a predetermined command from the terminal device 30 through an operation by the administrator 101. This also makes it possible for the management system 1 according to this embodiment to prevent users other than the administrator from easily removing the SD card 11.

[0037] Furthermore, the in-vehicle unit 10 may be configured to fix and release the SD card 11 using the fixing part 12. For example, the in-vehicle unit 10 may be configured to fix the SD card 11 using the fixing part 12 when the power is turned on, and to release the fixing of the SD card 11 by the fixing part 12 when the power is turned off.

[0038] This prevents the user from removing the SD card 11 from the in-vehicle unit 10, at least while the power is on. An example of the processes performed by the in-vehicle unit 10, the management device 20, and the terminal device 30 will be described in detail below.

[0039] [3. Processes performed by in-vehicle devices, management devices, and terminal devices] Figures 3, 5, and 8 are flowcharts illustrating an example of processing performed by the control unit 13 of the in-vehicle device 10 according to the embodiment. Figures 4 and 6 are flowcharts illustrating an example of processing performed by the control unit 22 of the management device 20 according to the embodiment. Figure 7 is a flowchart illustrating an example of processing performed by the control unit 31 of the terminal device 30 according to the embodiment.

[0040] Here, we will first explain the case where the SD card 11 is inserted into the in-vehicle unit 10 and secured by the fixing part 12 when the in-vehicle unit 10 is purchased. In this case, the control unit 13 of the in-vehicle unit 10 executes the process shown in Figure 3.

[0041] Specifically, as shown in Figure 3, when the in-vehicle unit 10 is started up, the control unit 13 first determines whether it is the first startup or not (step S101). If the control unit 13 determines that it is the first startup (step S101, Yes), it sends identification information unique to the SD card 11 to the management device 20 (step S102) and moves the process to step S103.

[0042] Furthermore, if the control unit 13 determines that it is not the first startup (step S101, No), it takes an image with the camera 14 (step S103) and records the image information of the captured image onto the SD card 11 (step S104).

[0043] Subsequently, the control unit 13 determines whether or not it has received a release command from the management device 20 (step S105). If the control unit 13 determines that it has not received a release command (step S105, No), it moves the process to step S107.

[0044] Furthermore, if the control unit 13 determines that it has received a release command (step S105, Yes), it releases the fixing of the SD card 11 by the fixing unit 12 (step S106). After that, the control unit 13 determines whether or not it has received a fixing command from the management device 20 (step S107).

[0045] If the control unit 13 determines that it has not received a fix command (step S107, No), it moves the process to step S109. If the control unit 13 determines that it has received a fix command (step S107, Yes), it fixes the SD card 11 with the fixing unit 12 (step S108).

[0046] Subsequently, the control unit 13 determines whether or not the power has been turned off (step S109). If the control unit 13 determines that the power has not been turned off (step S109, No), it proceeds to step S103. Alternatively, if the control unit 13 determines that the power has been turned off (step S109, Yes), it terminates the process.

[0047] Meanwhile, the control unit 22 of the management device 20 repeatedly executes the process shown in Figure 4 during the period when the power is on. Specifically, as shown in Figure 4, the control unit 22 first determines whether or not there is a selection operation of the in-vehicle device 10 to release the SD card 11 (step S201).

[0048] If the control unit 22 determines that there is no selection operation (step S201, No), it moves the process to step S204. If the control unit 22 determines that there is a selection operation (step S201, Yes), it selects an in-vehicle device 10 to release the SD card 11 based on the in-vehicle device identification information 25 (step S202).

[0049] Next, the control unit 22 sends a release command to the selected in-vehicle unit 10 to release the fixing of the SD card 11 by the fixing unit 12 (step S203). In this way, the management system 1 makes the SD card 11 removable from the in-vehicle unit 10 only when a release command is sent from the management device 20, thus preventing the SD card 11 from being easily removed.

[0050] Subsequently, the control unit 22 determines whether or not there is a selection operation for the in-vehicle device 10 to secure the SD card 11 (step S204). If the control unit 22 determines that there is no selection operation (step S204, No), it terminates the current process.

[0051] Furthermore, if the control unit 22 determines that a selection operation is required (step S204, Yes), it selects the in-vehicle unit 10 to secure the SD card 11 based on the in-vehicle unit identification information 25 (step S205).

[0052] Next, the control unit 22 sends a fixing command to the selected in-vehicle unit 10, causing the fixing unit 12 to fix the SD card 11 (step S206), and the process ends. This prevents users other than the administrator 101 using the management device 20 from removing the SD card 11 from the in-vehicle unit 10.

[0053] Next, we will describe the case in which the SD card 11 is automatically secured by the fixing part 12 after being inserted into the in-vehicle unit 10. In this case, the control unit 13 of the in-vehicle unit 10 executes the process shown in Figure 5.

[0054] Specifically, as shown in Figure 5, when the control unit 13 is started, it first determines whether it is the first startup or not (step S301). If the control unit 13 determines that it is the first startup (step S301, Yes), it sends identification information unique to the SD card 11 to the management device 20 (step S302) and moves the process to step S303.

[0055] Furthermore, if the control unit 13 determines that it is not the first startup (step S301, No), it determines whether or not the SD card 11 is inserted (step S303). If the control unit 13 determines that the SD card 11 is not inserted (step S303, No), it terminates the process.

[0056] If the control unit 13 determines that the SD card 11 is inserted (step S303, Yes), it secures the SD card 11 with the fixing part 12 (step S304). Subsequently, the control unit 13 takes an image with the camera 14 (step S305) and records the image information of the captured image onto the SD card 11 (step S306).

[0057] Subsequently, the control unit 13 determines whether or not it has received a release command from the management device 20 (step S307). If the control unit 13 determines that it has not received a release command (step S307, No), it moves the process to step S309.

[0058] Furthermore, if the control unit 13 determines that it has received a release command (step S307, Yes), it releases the fixing of the SD card 11 by the fixing unit 12 (step S308). After that, the control unit 13 determines whether or not the power has been turned off (step S309). If the control unit 13 determines that the power has not been turned off (step S309, No), it moves the process to step S305. Also, if the control unit 13 determines that the power has been turned off (step S309, Yes), it terminates the process.

[0059] Meanwhile, the control unit 22 of the management device 20 repeatedly executes the process shown in Figure 6 during the period when the power is on. Specifically, as shown in Figure 6, the control unit 22 first determines whether or not there is a selection operation of the in-vehicle device 10 to release the SD card 11 (step S401).

[0060] If the control unit 22 determines that there is no selection operation (step S401, No), it terminates the current process. If the control unit 22 determines that there is a selection operation (step S401, Yes), it selects an in-vehicle device 10 to release the SD card 11 based on the in-vehicle device identification information 25 (step S402).

[0061] Next, the control unit 22 sends a release command to the selected in-vehicle unit 10 to release the fixing of the SD card 11 by the fixing unit 12 (step S403), and the process ends. In this way, the management system 1 makes the SD card 11 removable from the in-vehicle unit 10 only when a release command is sent from the management device 20, thus preventing the SD card 11 from being easily removed.

[0062] Next, we will describe the case where the terminal device 30 used by the administrator 101 controls the fixing part 12 of the in-vehicle unit 10. In this case, the control unit 31 of the terminal device 30 repeatedly executes the process shown in Figure 7.

[0063] Specifically, as shown in Figure 7, the control unit 31 first determines whether or not there is a selection operation of the in-vehicle device 10 to release the SD card 11 (step S501). If the control unit 31 determines that there is no selection operation (step S501, No), it moves the process to step S503.

[0064] Furthermore, if the control unit 31 determines that a selection operation has occurred (step S501, Yes), A release command is sent to the management device 20, which causes the selected in-vehicle device 10 to send a release command to the in-vehicle device 10 corresponding to the in-vehicle device identification information 25 of the selected in-vehicle device 10 (step S502).

[0065] Subsequently, the control unit 31 determines whether or not there is a selection operation for the in-vehicle device 10 to secure the SD card 11 (step S503). If the control unit 31 determines that there is no selection operation (step S503, No), it terminates the current process.

[0066] Furthermore, if the control unit 31 determines that a selection operation has occurred (step S503, Yes), it sends a fix command to the management device 20 to send a fix command to the in-vehicle unit 10 corresponding to the in-vehicle unit identification information 25 of the selected in-vehicle unit 10 (step S504), and terminates the current process.

[0067] Meanwhile, the control unit 22 of the management device 20 repeatedly executes a process in which the contents of steps S201 and S204 shown in Figure 4 have been partially modified. Specifically, instead of the process in step S201, the control unit 22 determines whether or not it has received a release command from the terminal device 30.

[0068] If the control unit 22 determines that it has not received a release command, it moves the process to step S204. If the control unit 22 determines that it has received a release command, it moves the process to step S202.

[0069] Furthermore, instead of performing the processing in step S204, the control unit 22 determines whether or not a fixed instruction has been received. If the control unit 22 determines that no fixed instruction has been received, it terminates the current process. If the control unit 22 determines that a fixed instruction has been received, it moves the process to step S205.

[0070] In this case, the control unit 13 of the in-vehicle unit 10 performs the same process as shown in Figure 5. This allows the administrator 101 to fix and unfix the SD card 11 using the terminal device 30, regardless of their location.

[0071] Next, we will describe the case where the in-vehicle unit 10 itself fixes and releases the SD card 11. In this case, the control unit 13 of the in-vehicle unit 10 performs the process shown in Figure 8. Specifically, when the power is turned on, the control unit 13 first fixes the SD card 11 with the fixing unit 12 (step S601).

[0072] Subsequently, the control unit 13 takes an image using the camera 14 (step S602) and records the image information of the captured image onto the SD card 11 (step S603). Then, the control unit 13 determines whether or not the power has been turned off (step S604).

[0073] If the control unit 13 determines that the power is not turned off (step S604, No), it moves the process to step S602. Also, if the control unit 13 determines that the power is turned off (step S604, Yes), it releases the fixing of the SD card 11 by the fixing part 12 (step S605) and terminates the process. This prevents the in-vehicle device 10 from removing the SD card 11 by the user while the power is on.

[0074] [4. Addendum] As an addendum, the features of the present invention are as follows. (1) Including an in-vehicle device and a management device, The aforementioned in-vehicle device is It is equipped with a fixing part for securing a portable recording medium, The aforementioned control device is A memory unit that stores identification information specific to the in-vehicle device, The system includes a control unit that, upon receiving a selection operation from an in-vehicle unit to release the fixing of the portable recording medium, transmits a release command to the in-vehicle unit corresponding to the in-vehicle unit's unique identification information, thereby releasing the fixing of the portable recording medium by the fixing part. Management system. (2) The aforementioned in-vehicle device is When the portable recording medium is inserted, the fixing part secures the portable recording medium. The management system described in (1) above. (3) The control unit, When an in-vehicle unit selects a unit to fix the portable recording medium, a fixing command is sent to the in-vehicle unit corresponding to the in-vehicle unit's unique identification information, causing the fixing unit to fix the portable recording medium. The management system described in (1) above. (4) The system further includes a terminal device that, when it receives an operation to select an in-vehicle unit to release the portable recording medium, transmits a release command to the management device causing the in-vehicle unit corresponding to the in-vehicle unit's unique identification information to transmit the release command, The control unit, When the aforementioned release command is received, the release command is transmitted to the in-vehicle unit corresponding to the identification information. A management system as described in any one of the above (1) to (3). (5) The system further includes a terminal device that, when accepting an operation to select an in-vehicle unit for fixing the portable recording medium, transmits a fixing command to the management device, causing the in-vehicle unit to send a fixing command to the in-vehicle unit corresponding to the in-vehicle unit's unique identification information, The control unit, Upon receiving the aforementioned fixing command, a fixing command is sent to the in-vehicle unit corresponding to the identification information, causing the fixing unit to fix the portable recording medium. The management system described in (4) above. (6) A storage unit that stores identification information specific to the in-vehicle device, which includes a fixing part for securing a portable recording medium, When an in-vehicle unit selects an operation to release the portable recording medium, the control unit transmits a release command to the in-vehicle unit corresponding to the in-vehicle unit's unique identification information, thereby releasing the portable recording medium from the fixing part. Management device. (7) A fixing part for securing the portable recording medium being inserted, A control unit that, when the power is turned on, fixes the portable recording medium with the fixing part, and when the power is turned off, releases the fixing part from fixing the portable recording medium. An in-vehicle device equipped with the following features. (8) A procedure for storing unique identification information for an in-vehicle device equipped with a fixing part for securing a portable recording medium, When an in-vehicle unit receives an operation to release the fixing of the portable recording medium, a release command is sent to the in-vehicle unit corresponding to the in-vehicle unit's unique identification information to release the fixing of the portable recording medium by the fixing part. A management program that causes a computer to execute a command.

[0075] Further effects and modifications can be readily derived by those skilled in the art. Therefore, broader aspects of the present invention are not limited to the specific details and representative embodiments expressed and described above. Accordingly, various modifications are possible without departing from the spirit or scope of the overall concept of the invention as defined by the appended claims and their equivalents. [Explanation of Symbols]

[0076] 1 Management System 10 Onboard equipment 11 SD card 12 Fixed part 13 Control Unit 14 Cameras 20 Management device 21 Control section 22 Control Unit 23 Memory section 24 Management Programs 25. In-vehicle device identification information 30 Terminal devices 31 Control Unit 32 Operation section 100 vehicles 101 Administrator 110 Communication Network

Claims

1. A plurality of in-vehicle devices, each mounted on a plurality of vehicles, and a management device for managing the plurality of in-vehicle devices, The aforementioned multiple in-vehicle devices are It is equipped with a fixing part for securing a portable recording medium, The aforementioned control device is A storage unit that stores unique identification information for each of the aforementioned multiple in-vehicle devices, The system includes a control unit that, when it receives an operation to select one of the multiple in-vehicle units to release the portable recording medium, sends a release command to the in-vehicle unit corresponding to the unique identification information of that in-vehicle unit, thereby releasing the portable recording medium from the fixing part. Management system.

2. The aforementioned in-vehicle device is When the portable recording medium is inserted, the fixing part secures the portable recording medium. The management system according to claim 1.

3. The control unit, When an in-vehicle unit selects a unit to fix the portable recording medium, a fixing command is sent to the in-vehicle unit corresponding to the unit's unique identification information, causing the fixing unit to fix the portable recording medium. The management system according to claim 1.

4. The system further includes a terminal device that, when it receives an operation to select an in-vehicle unit to release the portable recording medium, transmits a release command to the management device causing the in-vehicle unit corresponding to the unique identification information of the in-vehicle unit to transmit the release command, The control unit, When the aforementioned release command is received, the release command is transmitted to the in-vehicle unit corresponding to the identification information. The management system according to claim 1.

5. The system further includes a terminal device that, when accepting an operation to select an in-vehicle unit for fixing the portable recording medium, transmits a fixing command to the management device, causing the in-vehicle unit to send a fixing command to the in-vehicle unit corresponding to the unique identification information of the in-vehicle unit, The control unit, Upon receiving the aforementioned fixing command, a fixing command is sent to the in-vehicle unit corresponding to the identification information, causing the fixing unit to fix the portable recording medium. The management system according to claim 4.

6. A storage unit that stores unique identification information for each of a plurality of in-vehicle devices, each of which is mounted on a plurality of vehicles and has a fixing part for fixing a portable recording medium, When the system receives an operation to select one of the multiple in-vehicle units to release the portable recording medium, it sends a release command to the in-vehicle unit corresponding to the unique identification information of that unit, causing the fixing part to release the portable recording medium, and the system includes a control unit that manages the multiple in-vehicle units. Management device.

7. A procedure for storing unique identification information for each of a plurality of in-vehicle devices, each mounted on a plurality of vehicles and equipped with a fixing part for fixing a portable recording medium, When an operation is received to select one of the multiple in-vehicle units to release the portable recording medium, a release command is sent to the in-vehicle unit corresponding to the unique identification information of that in-vehicle unit, causing the fixing part to release the portable recording medium, and the procedure for managing the multiple in-vehicle units is as follows: A management program that causes a computer to execute a command.

8. A plurality of in-vehicle devices mounted on a plurality of vehicles, and a management device for managing the plurality of in-vehicle devices, The aforementioned multiple in-vehicle devices are It is equipped with a fixing part for securing a portable recording medium, The aforementioned control device is A storage unit that stores unique identification information for each of the aforementioned multiple in-vehicle devices, The system includes a control unit that, when it receives an operation to select one of the multiple in-vehicle units that will fix the portable recording medium, sends a fixing command to the in-vehicle unit corresponding to the unique identification information of that in-vehicle unit, thereby fixing the portable recording medium with the fixing unit. Management system.

9. Includes a plurality of in-vehicle devices mounted on a plurality of vehicles, a management device for managing the plurality of in-vehicle devices, and a terminal device, The aforementioned multiple in-vehicle devices are It is equipped with a fixing part for securing a portable recording medium, The aforementioned terminal device is When the selection operation for an in-vehicle unit to fix the portable recording medium is received from among the plurality of in-vehicle units, a fix command is sent to the management device to cause the in-vehicle unit corresponding to the unique identification information of that in-vehicle unit to send a fix command. The aforementioned control device is A storage unit that stores unique identification information for each of the aforementioned multiple in-vehicle devices, The system includes a control unit that, upon receiving the aforementioned fixing command, transmits a fixing command to the in-vehicle unit corresponding to the identification information among the plurality of in-vehicle units, thereby fixing the portable recording medium with the fixing unit. Management system.

Images