Operation management device, server, and operation management system

Abstract

To provide a driving management device capable of suppressing an increase in a load on a driver in transmission work of travel route information to a server, the server and a driving management system.SOLUTION: The present invention relates to a driving management device comprising a position detection section, a travel route information recording section, a wireless communication section and a driver information acquisition section. The driver information acquisition section acquires driver information relating to a driver driving a vehicle. The travel route information recording section allows information related to the driver information acquired by the driver information acquisition section to be transmitted / received to / from a server. The travel route information recording section allows travel route information related to different driver information from the acquired driver information to be transmitted to the server.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to a driving management device, a server, and a driving management system.

Background Art

[0002] There is a driving management device mounted on a vehicle and configured to record driving route information corresponding to a route on which the vehicle travels (Patent Document 1). The driving management device can transmit (in other words, upload) the recorded driving route information to the server. The driving management device can constitute a driving management system together with the server.

[0003] Some driving management devices are configured to acquire driver information of a vehicle and record the driver information in association with the driving route information. Such a driving management device can suppress information leakage by restricting the use of driving route information for each driver. For example, the driving route information associated with the driver information can be restricted so that it can only be transmitted to the server by the driver corresponding to the driver information.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the above-described driving management device, the data volume of the driving route information that is not transmitted to the server may increase, and there is a possibility that the driving route information cannot be appropriately managed on the server. That is, since the person who can transmit the driving route information to the server is restricted to the driver corresponding to the driver information associated with the driving route information, the driving route information cannot be transmitted to the server while the driver has forgotten the upload operation.

[0006] If this situation continues, the server will be unable to properly manage the driving route information, requiring drivers to be careful not to forget to send the driving route information. This will increase the burden on drivers in sending driving route information to the server.

[0007] Therefore, one aspect of this disclosure is the desire to provide a driving management device, server, and driving management system that can suppress the increased burden on the driver in the task of transmitting driving route information to the server. [Means for solving the problem]

[0008] One aspect of this disclosure is a driving management device configured to be mounted on a vehicle, comprising: a position detection unit; a driving route information recording unit; a wireless communication unit; and a driver information acquisition unit. The position detection unit is configured to detect the vehicle's current position. The driving route information recording unit is configured to record driving route information. The driving route information includes time-series information of the vehicle's current position as detected by the position detection unit during vehicle movement. The wireless communication unit is configured to transmit and receive various types of information to and from the server via wireless communication. The driver information acquisition unit is configured to acquire driver information about the driver operating the vehicle.

[0009] The driving route information recording unit is configured to record driver information acquired by the driver information acquisition unit in association with the driving route information. Furthermore, the route information recording unit is configured to allow the transmission and reception of information associated with driver information acquired by the driver information acquisition unit to the server. The route information recording unit is configured not to allow the transmission and reception of information that is not route information but is associated with driver information other than the acquired driver information to the server. Furthermore, the route information recording unit is configured to allow the transmission of route information associated with driver information other than the acquired driver information to the server.

[0010] This driving management device transmits driving route information to the server even if the driver information associated with the driving route information recorded by the driving route information recording unit does not match the driver information acquired by the driver information acquisition unit, provided that the driving route information of a particular driver has been recorded by the driving route information acquisition unit. In other words, even if a certain driver's driving route information is not transmitted to the server for an extended period, the device can still transmit the untransmitted driving route information to the server if the driver information acquisition unit has acquired driver information for another driver.

[0011] Therefore, the driving management device described in this disclosure can prevent prolonged periods in which driving route information is not transmitted to the server. For administrators managing the server, this reduces the workload of reminding drivers of driving route information.

[0012] The driving management device of this disclosure may include a short-range wireless communication unit. The short-range wireless communication unit may be configured to communicate by short-range wireless communication, which has a maximum communication range shorter than that of wireless communication. The driver information acquisition unit may acquire driver information via the short-range wireless communication unit. As a result, the driving management device can acquire driver information via the short-range wireless communication unit, for example, from a driver's license.

[0013] In the operation management device of this disclosure, the wireless communication unit may transmit and receive various types of information to and from the server via a mobile terminal device connected by wireless communication. By communicating wirelessly with the mobile terminal device, the wireless communication unit can use a wireless communication method with a relatively shorter communication range compared to a configuration in which wireless communication is directly transmitted to the server. Since the wireless communication unit itself does not need to be capable of long-distance wireless communication, information transmission and reception to and from the server can be achieved at low cost. In this case, the mobile terminal device may be, for example, a smartphone.

[0014] In the driving management device of this disclosure, the driver information acquisition unit may be configured to acquire driver information via a wireless communication unit and / or a short-range wireless communication unit. This allows driver information to be acquired by either a first acquisition method, which acquires driver information from a driver's license via the short-range wireless communication unit, or a second acquisition method, which acquires driver information from a mobile terminal device via the wireless communication unit.

[0015] In the driving management device of this disclosure, the wireless communication unit may be configured to transmit and receive various types of information to and from a server via a mobile terminal device connected by wireless communication. The driver information acquisition unit may acquire driver information from the mobile terminal device via the wireless communication unit. This driving management device can achieve both the transmission and reception of information to and from the server and the acquisition of driver information using a mobile terminal device.

[0016] In the driving management device of this disclosure, the portable terminal device may be configured to be connected to an alcohol checker used to perform a driver's alcohol test. The driver information acquisition unit may acquire the alcohol test results from the alcohol checker via the portable terminal device. The driving route information recording unit may record the alcohol test results acquired by the driver information acquisition unit in association with the driving route information. By recording the alcohol test results in association with the driving route information, the driving management device can deter drunk driving.

[0017] In the operation management device of this disclosure, the driver information acquisition unit may be configured to use the driver information acquired at the first stop time as the driver information acquired at the first start time if the difference time is less than or equal to a predetermined allowable threshold. The difference time is the difference between the first stop time and the first start time. The first stop time is the most recent stop time of the operation management device. The first start time is the most recent start time of the operation management device.

[0018] This means that if the operation management device is restarted within a time limit below the permissible threshold after it has stopped, the process of reading driver information can be omitted, thereby reducing the burden on the driver.

[0019] The operation management device of this disclosure may include an unauthenticated notification unit. The unauthenticated notification unit may be configured to notify that the driver information has not been read if the driver information acquisition unit has not acquired driver information during the standby period. The standby period is the period from the start time of the operation management device until a predetermined authentication standby time has elapsed.

[0020] This allows the driving management device to notify the driver that driver information has not yet been read, thereby preventing the vehicle from being operated without driver information being acquired. The unauthenticated notification unit may be configured not to issue a notification if the driver information acquisition unit acquires driver information during the standby period.

[0021] In the operation management device of this disclosure, if the difference time is less than or equal to a predetermined allowable threshold, the travel route information recording unit may record the travel route information recorded up to the first stop time and the travel route information recorded from the first start time as a single continuous travel route information. The difference time is the difference between the first stop time, which is the most recent stop time of the operation management device, and the first start time, which is the time when the operation management device was started.

[0022] As a result, if the operation management device is restarted within a time limit below an acceptable threshold after the operation management device has stopped, it will not record the route information after restarting separately from the route information recorded before stopping, but will record it as a single continuous route information. With this operation management device, it is possible to suppress the increase in the number of route information entries in applications where short-term vehicle stops are repeated, and the workload when managing multiple route information entries can be reduced.

[0023] The driving management device of this disclosure may include a recording medium connection unit configured to connect a recording medium. The driving route information recording unit may be configured to store driving route information for all drivers, regardless of the driver information acquired, on the recording medium connected to the recording medium connection unit.

[0024] As a result, the driving management device can utilize a method of outputting the travel route information to the server via a recording medium in addition to the method of outputting via the wireless communication unit as a method of outputting the travel route information from the driving management device to the server. According to this driving management device, in an environment where output via the wireless communication unit is impossible, the output method via the recording medium can be selected, so that the operation of outputting the travel route information from the driving management device to the server can be executed more frequently.

[0025] Another aspect of the present disclosure is a server configured to store the travel route information recorded by the driving management device, including a server wireless communication unit, a server recording unit, and an untransmitted notification unit. The server wireless communication unit is configured to transmit and receive various information to and from the driving management device by wireless communication. The server recording unit is configured to record the travel route information received via the server wireless communication unit. The untransmitted notification unit is configured to notify that the transmission of the travel route information from the driving management device to the server has not been performed in response to the fulfillment of a predetermined urging condition. The urging condition is satisfied when the elapsed time from the time when the travel route information was last received exceeds a predetermined elapsed time threshold. Or, the urging condition is satisfied every time a predetermined condition period elapses.

[0026] This server can notify that the transmission of the travel route information to the server has not been performed, so that it can prompt the driver to perform the transmission operation of the travel route information. The notification method may be a notification method such as a buzzer, voice, or light emission. When connected to a smartphone, it may be a notification method such as display on the smartphone app or notification by email.

[0027] The server of the present disclosure may include a server recording medium connection unit. The server recording medium connection unit may be configured such that a recording medium on which the travel route information is recorded is connected. The server recording unit may be configured to receive the travel route information via the server wireless communication unit or a recording medium connected to the server recording medium connection unit.

[0028] This allows the server to receive route information from the operation management device via a recording medium in addition to receiving it via a wireless communication unit. With this server, in environments where reception via wireless communication unit is not possible, the server can select the method of receiving information via a recording medium, thus enabling it to perform the task of receiving route information from the operation management device at a higher frequency.

[0029] The server of this disclosure may include a display unit. The travel route information may include the start time of travel, the end time of travel, the distance traveled, and the travel time. The display unit may be configured to display the start time of travel, the end time of travel, the distance traveled, and the travel time based on the travel route information. With this server, various types of information included in the travel route information recorded by the driving management device can be displayed on the display unit, so that the travel route information can be provided to the user at a location different from the vehicle.

[0030] In the server of this disclosure, the server wireless communication unit may be configured to transmit and receive various types of information to and from the driving management device via a mobile terminal device connected by wireless communication. The server may include a login information receiving unit, a driver list recording unit, and a login determination unit. The login information receiving unit may receive login information of applicants to log in to the server from the mobile terminal device. The driver list recording unit may be configured to record driver registration information. The driver registration information may include a list of candidates to drive vehicles equipped with the driving management device. The login determination unit may be configured to allow the applicant to log in if their login information is included in the driver registration information. The login determination unit may be configured not to allow the applicant to log in if their login information is not included in the driver registration information.

[0031] Login information may include an identification number and password entered on a mobile device. Login information may also include the driver's license number and driver's license expiration date transmitted from the mobile device via the driver management device. Driver registration information may include each candidate's identification number and password, and each candidate's driver's license number and driver's license expiration date.

[0032] This allows server users to log in to the server using either an identification number and password via a mobile device, or by using their driver's license number and the expiration date of their driver's license.

[0033] The server in this disclosure may include a notification unit. The notification unit may be configured to notify a mobile terminal device of the approach of a predetermined specific date. The specific date may include the expiration date of the driver's license.

[0034] This server notifies drivers of the approaching expiration date of their driver's license, which is included in their driver registration information. This allows drivers to be notified of the approaching expiration date without requiring them to configure notification settings in advance. Therefore, it can encourage drivers to renew their driver's license without requiring them to go through the trouble of configuring notification settings.

[0035] One aspect of this disclosure is a driving management system comprising one of the driving management devices described above and one of the servers described above. Similar to the driving management devices described above, this driving management system can prevent a prolonged period in which driving route information is not transmitted to the server. Furthermore, similar to the servers described above, this driving management system can notify the driver that driving route information has not been transmitted to the server, thereby prompting the driver to transmit the driving route information. [Brief explanation of the drawing]

[0036] [Figure 1]This diagram shows the general configuration of an operation management system that includes an operation management device, a mobile terminal device, and a server. [Figure 2] This sequence diagram shows the states of the operation management device, the mobile terminal device, and the server during the login authentication process and information transmission process to the server using a mobile terminal device. [Figure 3] This sequence diagram shows the states of the driver authentication process and information transmission process to the driver management system using a driver's license, including the driver management system, the mobile terminal device, and the server. [Figure 4] This is a sequence diagram showing the status of the operation management device, the mobile terminal device, and the server in an information transmission process using a mobile terminal device. [Figure 5] This is a sequence diagram showing the states of the operation management device, the mobile terminal device, and the server during the driver authentication process for the operation management device using a mobile terminal device. [Figure 6] This is a flowchart for the driver authentication continuation process. [Figure 7] This is a flowchart for the process of reporting unauthenticated activity. [Figure 8] This is an explanatory diagram illustrating the screen transitions on a mobile device when operating a connected application. [Figure 9] This is a flowchart for processing unsent notifications. [Figure 10] This is a flowchart for the specific Nippon Express notification process. [Modes for carrying out the invention]

[0037] Exemplary embodiments of the present disclosure are described below with reference to the drawings. Furthermore, this disclosure is not limited in any way to the embodiments described below, and it goes without saying that it can take various forms as long as they fall within the technical scope of this disclosure.

[0038] [1. First Embodiment] [1-1. Overall Structure] The operation management system 1 of the first embodiment is configured to manage the operation of a vehicle (not shown).

[0039] As shown in Figure 1, the operation management system 1 comprises an operation management device 11 and a server 31. The driving management device 11 is installed in the vehicle and is configured to record driving route information Dr. The driving route information Dr includes information representing the route the vehicle has traveled.

[0040] The operation management device 11 is configured to connect to the mobile terminal device 21 via wireless communication. Wireless communication includes, for example, Bluetooth® and Wi-Fi®. The operation management device 11 transmits and receives various types of information to and from the mobile terminal device 21 via wireless communication. The mobile terminal device 21 includes, for example, a smartphone or a tablet terminal device.

[0041] The driving management device 11 is configured to receive driver information Dd from the driver's license 23 (hereinafter also referred to as the driver's license 23) by touch operation of the driver's license 23 containing an IC chip using short-range wireless communication. Short-range wireless communication includes, for example, NFC (Near Field Communication). A contactless IC card storing driver information Dd may be used instead of the driver's license 23.

[0042] The operation management device 11 is configured to allow the attachment and detachment of the recording medium 25. The operation management device 11 is configured to record travel route information Dr on the recording medium 25. The recording medium 25 includes, for example, an SD card (registered trademark), a memory card, and the like.

[0043] Server 31 is configured to store the driving route information Dr recorded by the driving management device 11. Server 31 is configured to be connected to the mobile terminal device 21 by wireless communication (e.g., mobile phone wireless communication, LTE (Long Term Evolution)). Server 31 transmits and receives various types of information to and from the mobile terminal device 21 via wireless communication.

[0044] Server 31 is connected to the operating terminal 41 by wired communication. Server 31 transmits and receives various types of information to and from the operating terminal 41. The operating terminal 41 includes, for example, a personal computer. The operating terminal 41 is configured to allow the attachment and detachment of the recording medium 25. The operating terminal 41 is configured to read the travel route information Dr recorded on the recording medium 25. The operating terminal 41 includes a display unit (not shown) and is configured to display the travel route information Dr on the display unit. The display unit may be, for example, a liquid crystal display, an organic EL display, or the like.

[0045] Server 31 is configured to receive route information Dr from the operation management device 11 via the mobile terminal device 21. Server 31 is also configured to receive route information Dr from the operation management device 11 via the recording medium 25.

[0046] Server 31 is configured to display the received route information Dr on the display unit of the operating terminal 41. [1-2. Operation Management Device] As shown in Figure 1, the driving management device 11 includes a driving route information recording unit 13, a position detection unit 15, a wireless communication unit 17, and a short-range wireless communication unit 19.

[0047] The driving route information recording unit 13 is configured to record driving route information Dr, which includes the vehicle's driving route. Dr includes not only the vehicle's driving route, but also the start time of the drive, the end time of the drive, the distance traveled, and the duration of the drive.

[0048] The driving route information recording unit 13 comprises a control unit 13a and a recording medium connection unit 13b. The control unit 13a includes an arithmetic unit (hereinafter also referred to as a CPU) (not shown) and internal memory (not shown). The CPU is configured to control each part of the operation management device 11 by executing various processes according to a computer program. The CPU is configured to read computer programs from the internal memory. The internal memory stores various information, including computer programs for the CPU to execute. The internal memory may include RAM, ROM, and flash memory. ROM stores computer programs. RAM is used as a work area when executing processes according to the computer program. Flash memory is used to store various data such as setting data and video data.

[0049] The recording medium connection section 13b is configured to allow the attachment and detachment of the recording medium 25. The recording medium connection section 13b is configured to enable writing operations to the attached recording medium 25 and reading operations to the attached recording medium 25.

[0050] The position detection unit 15 is configured to measure the current position of the driving management device 11. The position detection unit 15 is configured to measure the current position based on satellite signals from GPS satellites, for example. The position detection unit 15 transmits the measured current position information (hereinafter also referred to as current position information Dc) to the driving route information recording unit 13. In other words, the position detection unit 15 is configured to detect the current position of the vehicle on which the driving management device 11 is installed.

[0051] The driving route information recording unit 13 receives the current location information Dc detected by the position detection unit 15 when the vehicle is moving, and records the driving route information Dr, which includes the time-series data of the current location information Dc, on the recording medium 25.

[0052] The wireless communication unit 17 is connected to the driving route information recording unit 13 by a wired connection. The wireless communication unit 17 is configured to transmit and receive various types of information to and from the driving route information recording unit 13. The wireless communication unit 17 is also configured to connect to the mobile terminal device 21 wirelessly. Wireless communication includes, for example, Bluetooth® and WiFi®. The wireless communication unit 17 transmits and receives various types of information to and from the mobile terminal device 21 via wireless communication. Furthermore, the wireless communication unit 17 is configured to transmit and receive various types of information to and from the server 31 via the mobile terminal device 21 connected by wireless communication.

[0053] The short-range wireless communication unit 19 is configured to communicate using short-range wireless communication, which has a shorter maximum communication range than the wireless communication of the wireless communication unit 17. The short-range wireless communication unit 19 is configured to receive driver information Dd from the driver's license 23 by touch operation of the IC chip-equipped driver's license 23. The short-range wireless communication unit 19 is connected to the driving route information recording unit 13 by wire. The short-range wireless communication unit 19 is configured to transmit driver information Dd to the driving route information recording unit 13.

[0054] [1-3. Server] Server 31 comprises a server control unit 32, a server recording unit 33, and a server wireless communication unit 35.

[0055] The server control unit 32 includes a server processing unit (hereinafter also referred to as the server CPU), which is not shown in the diagram, and server internal memory, which is not shown in the diagram. The server CPU is configured to control various parts of the server 31 by executing various processes according to a computer program. The server CPU is configured to read computer programs from the server internal memory. The server internal memory stores various information, including computer programs for the CPU to execute. The server internal memory may include RAM, ROM, and flash memory. ROM stores computer programs. RAM is used as a work area when executing processes according to the computer program. Flash memory is used to store various data such as setting data and video data.

[0056] The server recording unit 33 is configured to record various types of information. The server recording unit 33 may include, for example, a hard disk drive (hereinafter also referred to as HDD), a solid state drive (hereinafter also referred to as SSD), etc. The server recording unit 33 can record, for example, driver registration information Dmd and driving route information Dr.

[0057] The driver registration information Dmd includes a list of candidates who will drive vehicles equipped with the driving management device 11. The driver registration information Dmd is pre-registered information regarding drivers who are to be managed by the driving management system 1. The driver registration information Dmd includes information for multiple drivers. For each of the multiple drivers, the driver registration information Dmd includes an identification number (hereinafter also referred to as user ID), password, name, department, etc. The driver registration information Dmd may further include the expiration date of the driver's license, the driver's email address, etc.

[0058] The travel route information Dr is information received from the driving management device 11 and corresponds to the route traveled by the vehicle. The server wireless communication unit 35 is configured to transmit and receive various types of information to and from the mobile terminal device 21 via wireless communication. The server wireless communication unit 35 is configured to connect to the mobile terminal device 21 using, for example, mobile phone wireless communication, LTE (Long Term Evolution), etc. The server wireless communication unit 35 is configured to transmit and receive various types of information to and from the operation management device 11 via wireless communication through the mobile terminal device 21. The server wireless communication unit 35 can receive travel route information Dr from the operation management device 11 via the mobile terminal device 21.

[0059] [1-4. Mobile Devices] The mobile terminal device 21 is configured to communicate wirelessly with other devices using mobile phone wireless communication, LTE, Bluetooth®, WiFi®, etc. The mobile terminal device 21 transmits and receives various information with the operation management device 11 via wireless communication. The mobile terminal device 21 also transmits and receives various information with the server 31 via wireless communication.

[0060] The mobile terminal device 21 is equipped with various application software (hereinafter also referred to as "apps") configured to perform various processes in response to operations by the user or driver. The various application software includes application software for the driving management device (hereinafter also referred to as the driving management app). The driving management app is configured to perform various processes in response to commands from the driver. These processes include processes for authenticating the driver's login (hereinafter also referred to as the login authentication process) and processes for transmitting driving route information Dr from the driving management device 11 to the server 31 (hereinafter also referred to as the information transmission process).

[0061] The mobile terminal device 21 is configured to output input data (specifically, user ID and password) entered by the driver to the server 31 by performing the login authentication process for the driving management application. The server 31 checks whether the user ID and password are registered in the driver registration information Dmd and sends the result to the mobile terminal device 21. If the user ID and password are included in the driver registration information Dmd, authentication is successful; if the user ID and password are not included in the driver registration information Dmd, authentication is failed. If the result is authentication success, commands from the mobile terminal device 21 to the driving management device 11 and the server 31 are recognized as commands from an authenticated driver.

[0062] The mobile terminal device 21 receives the driving route information Dr from the driving management device 11 by executing the information transmission process of the driving management application, and then executes the process of sending the received driving route information Dr to the server 31.

[0063] The mobile terminal device 21 is configured to connect to the alcohol checker 27 via wireless or wired communication. Wireless communication here includes, for example, Bluetooth®.

[0064] The alcohol checker 27 is configured to perform a breathalyzer test on the driver based on the alcohol concentration in the driver's breath. The alcohol checker 27 outputs the breathalyzer test results to the connected portable terminal device 21.

[0065] The portable terminal device 21 transmits the alcohol test results received from the alcohol checker 27 to the driving management device 11 via wireless communication. Furthermore, when the mobile terminal device 21 receives the results of the alcohol test from the alcohol checker 27, it may display a message on its screen requesting the driver to take a photograph of their face. The mobile terminal device 21 may then transmit the driver's photograph along with the alcohol test results to the driving management device 11 via wireless communication.

[0066] The recording format of the alcohol test results in the driving management device 11 will be described later. [1-5. Login authentication and information transmission processing to a server using a mobile terminal device] This section describes the login authentication process and information transmission process to the server 31 executed by the operation management system 1. It also describes a method of login authentication using a mobile terminal device 21. In other words, login authentication is equivalent to driver authentication.

[0067] As shown in Figure 2, first, in S110 (where S represents a step), the driver enters their own user ID and password into the mobile terminal device 21. The mobile terminal device 21 transmits the user ID and password to the server 31 via wireless communication.

[0068] In S120, the server 31 performs a driver authentication determination based on the input data (in other words, the user ID and password). Specifically, if the input data is included in the driver registration information Dmd, the server 31 determines that authentication is successful and allows the driver corresponding to the input data to log in. If the input data is not included in the driver registration information Dmd, the server 31 determines that authentication has failed and does not allow the driver corresponding to the input data to log in. The server 31 transmits the result of the authentication determination to the mobile terminal device 21.

[0069] In S130, the mobile terminal device 21 receives the authentication result from the server 31. If the authentication result received from the server 31 is "authentication successful", the mobile terminal device 21 transmits driver information Dd to the driving management device 11 via wireless communication. Here, driver information Dd is the user ID.

[0070] If the authentication result received from the server 31 is "authentication failed," the mobile terminal device 21 notifies the user of the "authentication failed" status. The notification method includes displaying the information on the screen or providing an audio notification. Once the notification process is complete, the mobile terminal device 21 terminates this process.

[0071] In S140, first, in the driving management device 11, the control unit 13a of the driving route information recording unit 13 executes control processing to acquire driver information Dd in response to the transmission of driver information Dd from the mobile terminal device 21. The control unit 13a records the acquired driver information Dd in an internal memory (not shown) or in a recording medium 25 attached to the recording medium connection unit 13b. The control unit 13a authenticates the acquired driver information Dd as the driver information Dd of the driving management device 11.

[0072] Furthermore, in S140, the control unit 13a records the travel route information Dr, which includes the time-series data of the current location information Dc detected by the position detection unit 15, together with the driver information Dd, onto the recording medium 25 attached to the recording medium connection unit 13b. In other words, the control unit 13a associates the driver information Dd with the travel route information Dr and records it on the recording medium 25. That is, the driving management device 11 is configured to record the travel route information Dr and the driver information Dd on the travel route information recording unit 13.

[0073] Furthermore, the driving route information recording unit 13 stores the driving route information Dr for all drivers in the recording medium 25 connected to the recording medium connection unit 13b, regardless of the acquired driver information Dd (in other words, the driver information Dd being authenticated).

[0074] When the driving route information recording unit 13 acquires driver information Dd, it permits the transmission and reception of information associated with driver information Dd to and from the server 31. The driving route information recording unit 13 does not permit the transmission and reception of information associated with driver information other than the acquired driver information Dd, but which is not driving route information Dr, to and from the server 31. However, the driving route information recording unit 13 permits the transmission of driving route information Dr, which is associated with driver information other than the acquired driver information Dd, to the server 31.

[0075] In S150, the driving management device 11 transmits the driving route information Dr, associated with the driver information Dd, to the mobile terminal device 21 via wireless communication. At this time, the driving management device 11 transmits the driving route information Dr to the mobile terminal device 21 in order to transmit the driving route information Dr to the server 31 via the mobile terminal device 21.

[0076] At this time, the driving management device 11 transmits the unsent driving route information Dr from the driving route information recording unit 13 to the server 31. The driving management device 11 transmits the driving route information Dr related to all driver information Dd, not just the driver information Dd being authenticated, to the server 31 via the mobile terminal device 21.

[0077] In S160, the mobile terminal device 21 receives driver information Dd and route information Dr from the driving management device 11, and then transmits the driver information Dd and route information Dr to the server 31 via wireless communication.

[0078] In S170, the server 31 records the driver information Dd and the driving route information Dr received from the mobile terminal device 21 in the server recording unit 33. In other words, the server 31 records the driving route information Dr associated with the driver information Dd in the server recording unit 33.

[0079] Of these, processes S110 to S130 correspond to the login authentication process. Processes S130 to S170 correspond to the information transmission process. In this way, the driver management system 1 performs driver login authentication on the server 31 by determining whether or not the driver is registered in the driver registration information Dmd based on the input data (specifically, the user ID and password) entered into the mobile terminal device 21.

[0080] Furthermore, in the driving management system 1, the driving management device 11 does not only record the driving route information Dr, but also records the driver information Dd in association with the driving route information Dr. When the driving management device 11 sends unsent driving route information Dr to the server 31, it sends not only the driver information Dd corresponding to the driver currently logged in, but also all unsent driving route information Dr for all driver information Dd.

[0081] [1-6. Driver authentication and information transmission process to the driving management system using a driver's license] This section describes the driver authentication process and information transmission process to the driving management device 11, which are performed by the driving management system 1. It also describes a method of driver authentication using an IC chip-embedded driver's license 23.

[0082] As shown in Figure 3, in S210, the driving management device 11 obtains driver information Dd from the driver's license 23 by touch operation of the driver's license 23 using the short-range wireless communication unit 19.

[0083] In S220, the driving management device 11 records the driving route information Dr and the driver information Dd in the driving route information recording unit 13. The driving route information recording unit 13 records the driver information Dd in association with the driving route information Dr.

[0084] In S230, the driving management device 11 transmits the driving route information Dr associated with the driver information Dd to the server 31 via wireless communication through the mobile terminal device 21. At this time, the driving management device 11 transmits the driving route information Dr that has been recorded in the driving route information recording unit 13 but has not yet been transmitted to the server 31. The driving management device 11 transmits the driving route information Dr related to all driver information Dd, not just the driver information Dd being authenticated, to the server 31 via the mobile terminal device 21.

[0085] In S240, the mobile terminal device 21 receives the driving route information Dr associated with the driver information Dd from the driving management device 11, and then transmits the driving route information Dr associated with the driver information Dd to the server 31 via wireless communication.

[0086] In S250, the server 31 records the driving route information Dr, which is associated with the driver information Dd received from the mobile terminal device 21, in the server recording unit 33. Of these, the process in S210 corresponds to the driver authentication process. Furthermore, the processes from S220 to S250 correspond to the information transmission process.

[0087] Thus, in the driving management system 1, the driving management device 11 obtains driver information Dd from the driver's license 23 by touch operation of the driver's license 23 using short-range wireless communication, and performs driver authentication processing.

[0088] Furthermore, in the driving management system 1, the driving management device 11 does not only record the driving route information Dr, but also records the driver information Dd in association with the driving route information Dr. When the driving management device 11 sends unsent driving route information Dr to the server 31, it sends not only the driver information Dd corresponding to the driver currently being authenticated, but also all unsent driving route information Dr for all driver information Dd.

[0089] [1-7. Information transmission processing using mobile terminal devices] This section describes the information transmission process using a mobile terminal device 21, which is executed by the operation management system 1. The information transmission process involves sending travel route information Dr from the operation management device 11 to the server 31.

[0090] As shown in Figure 4, first, in S310, when the mobile terminal device 21 receives a request to transmit travel route information Dr from a user who is undergoing login authentication, it transmits a travel route information request signal Sdr to the driving management device 11 via wireless communication.

[0091] In S320, the driving management device 11 transmits not only the driver information Dd corresponding to the user currently logged in, but also the driving route information Dr for all driver information Dd, to the server 31 via wireless communication using the mobile terminal device 21. At this time, the driving management device 11 transmits the driving route information Dr recorded in the driving route information recording unit 13 that has not yet been sent to the server 31.

[0092] In S330, the mobile terminal device 21 receives the driving route information Dr related to all driver information Dd from the driving management device 11, and then transmits the driving route information Dr related to all driver information Dd to the server 31 via wireless communication.

[0093] In S340, the server 31 records the route information Dr related to all driver information Dd received from the mobile terminal device 21 in the server recording unit 33. The server 31 notifies the mobile terminal device 21 via wireless communication whether or not the recording of the route information Dr to the server recording unit 33 was successful.

[0094] Thus, the driving management system 1 transmits the driving route information Dr related to all driver information Dd recorded in the driving management device 11 to the server recording unit 33 in response to terminal operations performed by a user (driver) using the mobile terminal device 21. In other words, the driving management system 1 is configured to upload the driving route information Dr for all drivers to the server recording unit 33, regardless of who the authenticated user is.

[0095] [1-8. Driver authentication process for the operation management system using a mobile terminal device] This section describes the driver authentication process for the operation management device 11, which is performed by the operation management system 1. It also describes a method of driver authentication using a portable terminal device 21.

[0096] As shown in Figure 5, first, in S410, the driver enters their own user ID and password into the mobile terminal device 21. Then, the mobile terminal device 21 transmits the user ID and password to the server 31 via wireless communication.

[0097] In S420, the server 31 performs driver authentication based on the input data (in other words, the user ID and password). Specifically, the server 31 determines that authentication is successful if the input data is included in the driver registration information Dmd, and determines that authentication is unsuccessful if the input data is not included in the driver registration information Dmd. The server 31 transmits the result of the authentication determination to the mobile terminal device 21.

[0098] In S430, the mobile terminal device 21 receives the authentication result from the server 31. If the authentication result received from the server 31 is "authentication successful", the mobile terminal device 21 transmits driver information Dd to the driving management device 11 via wireless communication. Here, driver information Dd is the user ID.

[0099] If the authentication result received from the server 31 is "authentication failed," the mobile terminal device 21 notifies the user of the "authentication failed" status. The notification method includes displaying the information on the screen or providing an audio notification. Once the notification process is complete, the mobile terminal device 21 terminates this process.

[0100] In S440, the driving management device 11 records the driving route information Dr and the driver information Dd on the recording medium 25 attached to the recording medium connection part 13b of the driving route information recording unit 13. The driving route information recording unit 13 records the driver information Dd in association with the driving route information Dr.

[0101] The operation management device 11 terminates this process when it completes S440. After performing driver authentication in this manner, the driving management device 11 records the travel route information Dr and driver information Dd onto the recording medium 25 while the driving management device 11 is running. In other words, in this case, the driving management device 11 can upload the travel route information Dr and driver information Dd to the server 31 via the operating terminal 41 using the recording medium 25, rather than transmitting them to the server 31 via the mobile terminal device 21 using wireless communication.

[0102] Furthermore, the series of processes described above using Figure 2 corresponds to the process in which the driving management device 11 transmits the driving route information Dr and driver information Dd to the server 31 via the mobile terminal device 21 using wireless communication after driver authentication is completed.

[0103] [1-9. Driver Authentication Continuation Process] The driver authentication continuation process performed by the operation management device 11 will now be described. The driver authentication continuation process is performed by the control unit 13a after the operation management device 11 is started up and before the driver authentication process is performed.

[0104] As shown in Figure 6, when the driver authentication continuation process is started in the control unit 13a of the operation management device 11, first in S510 it determines whether a predetermined skip condition has been met. If it has been met, it makes an affirmative determination and proceeds to S520, and if it has not been met, it makes a negative determination and terminates this process.

[0105] The skip condition is met if the difference time Tdf between the first stop time Tst and the first start time Twa is less than or equal to a predetermined allowable threshold Tth, and not met if the difference time Tdf is greater than the allowable threshold Tth. The first stop time Tst is the most recent stop time of the operation management device 11 (in other words, the last stop time). The first start time Twa is the most recent start time of the operation management device 11 (in other words, the latest start time). The allowable threshold Tth is predetermined and may be set to, for example, 15 minutes.

[0106] In S520, the operation management device 11 executes a process to carry over the driver information Dd authenticated during the previous operation of the operation management device 11 as the driver information Dd to be authenticated this time. In other words, if the skip condition is met, the operation management device 11 will continue to authenticate the driver information Dd that was authenticated last time.

[0107] In S530, the operation management device 11 starts the process of recording the travel route information Dr as a continuation of the travel route information Dr recorded during the previous operation of the operation management device 11. In other words, the operation management device 11 records the travel route information Dr recorded up to the first stop time Tst and the travel route information Dr that was started recording from the first start time Twa as a single continuous travel route information Dr. The operation management device 11 also records the driver information Dd, which was taken over in S520, in association with the travel route information Dr and in the travel route information recording unit 13.

[0108] The operation management device 11 terminates this process when S530 is completed. The driver authentication continuation process is performed by the driver management device 11. If the driver management device 11 is restarted within a time period less than or equal to the allowable threshold Tth after the driver management device 11 has stopped, the process of reading the driver information Dd can be omitted, thereby reducing the burden on the driver during driver authentication.

[0109] Furthermore, if the operation management device 11 is restarted within a time period less than or equal to the allowable threshold Tth after the operation management device 11 has stopped, the operation management device 11 does not record the route information Dr after restarting separately from the route information Dr recorded before stopping. In other words, the operation management device 11 records the route information Dr recorded before stopping and the route information Dr after restarting as a single continuous route information Dr. With this operation management device 11, it is possible to suppress the increase in the number of route information Dr in applications where short-term vehicle stops are repeated, and the workload when managing multiple route information Dr can be reduced.

[0110] [1-10. Unauthenticated Notification Processing] The unauthenticated notification process performed by the operation management device 11 will now be described. The unauthenticated notification process is repeatedly performed by the control unit 13a from the time the operation management device 11 is started until the operation management device 11 is stopped.

[0111] As shown in Figure 7, when the control unit 13a of the operation management device 11 starts the unauthenticated notification process, it first determines in S610 whether or not the unauthenticated notification has already been performed. If the unauthenticated notification has already been performed, the control unit 13a makes an affirmative determination and proceeds to S650, and if the unauthenticated notification has not been performed, it makes a negative determination and proceeds to S620. The operation management device 11 determines that the unauthenticated notification has been performed if the process in S640, which will be described later, has been completed.

[0112] In S620, the operation management device 11 determines whether a predetermined authentication waiting time Tas has elapsed since the start time of the operation management device 11. If the determination is positive, the process proceeds to S630; if the determination is negative, the process ends. The authentication waiting time Tas may be set to, for example, 5 minutes.

[0113] In S630, the operation management device 11 determines whether or not driver authentication has been completed. If it determines that the result is positive, it terminates this process; if it determines that the result is negative, it proceeds to S640. The operation management device 11 determines that driver authentication has been completed if it has acquired driver information Dd. The driver authentication method may be a driver authentication method using the mobile terminal device 21, or a driver authentication method using the driver's license 23.

[0114] In S640, the operation management device 11 notifies the driver that driver authentication has not been performed. If the operation management device 11 is equipped with a notification unit such as a buzzer or LED, the notification method may be a notification method using that notification unit. If the operation management device 11 is connected to a mobile terminal device 21, the notification method may be a display on the mobile terminal device 21 or notification by email.

[0115] In S650, the operation management device 11 determines whether the vehicle is stationary or not. If the determination is positive, the process proceeds to S660; if the determination is negative, the process ends. Here, "stationary" means that the vehicle's engine is running, but the vehicle is not moving.

[0116] In S660, the operation management device 11, similar to S640, informs the driver that driver authentication has not been performed. The operation management device 11 terminates this process when S640 and S660 are completed.

[0117] In other words, the operation management device 11, which performs the unauthenticated notification process, notifies that the driver information Dd has not been read if it has not acquired the driver information Dd during the waiting period from the start time of the operation management device 11 until the authentication waiting time Tas has elapsed.

[0118] As a result, the operation management device 11 can notify the driver that the driver information Dd has not yet been read, thereby preventing the vehicle from being operated without the acquisition of driver information Dd. The control unit 13a may be configured not to issue a notification if the driver information Dd is acquired during the standby period.

[0119] Furthermore, after the driver information Dd has not been read, the driver management device 11 will not issue a notification if the vehicle is not stopped (NO in S650), but will issue a notification again if the vehicle is stopped (YES in S650). In this way, the driver management device 11 will refrain from interfering with the driver's driving operations by stopping the notification while the vehicle is moving. Also, once the vehicle has stopped, the driver management device 11 will prompt the driver to authenticate by again notifying that driver authentication has not been performed.

[0120] [1-11. Recording of alcohol test results using the driving control device] This section describes a configuration in which the results of a driver's alcohol test using an alcohol checker 27 are recorded by a driving management device 11.

[0121] As described above, the portable terminal device 21 is configured to transmit the alcohol test results received from the alcohol checker 27 to the driving management device 11 via wireless communication. As mentioned above, the mobile terminal device 21 is equipped with various application software. The mobile terminal device 21 is equipped with an application (hereinafter referred to as the connection application) that displays candidates for external devices that can be connected via wireless communication.

[0122] When the mobile terminal device 21 launches the target application in response to the driver's (or user's) operation, it displays a connection list screen 21a1 as shown in Figure 8. The connection list screen 21a1 in Figure 8 displays four candidates for external devices: a driving management device, an alcohol checker, external device A, and external device B.

[0123] When the driver selects "Driving Management System" on the connection list screen 21a1, the mobile terminal device 21 connects to the driving management system 11 via wireless communication and displays the driving management system information screen 21a2. The driving management system information screen 21a2 displays the status of the driving management system 11. For example, if the driving management system 11 recognizes that the driver is in the vehicle, it displays "Inside the vehicle".

[0124] When the driver selects "Alcohol Checker" on the connection list screen 21a1, the mobile terminal device 21 connects to the alcohol checker 27 via wireless communication and displays the alcohol checker information screen 21a3. The alcohol checker information screen 21a3 displays a message to the driver prompting them to take a photo of their face and blow their breath into the alcohol checker 27. The alcohol checker information screen 21a3 includes a video display area that shows the video being recorded.

[0125] Once the mobile terminal device 21 has completed both receiving the alcohol test results from the alcohol checker 27 and taking a photograph of the driver's face, it displays an alcohol test results screen 21a4 that includes the numerical value of the alcohol test result. The mobile terminal device 21 is configured to transmit the alcohol test results and the driver's face photograph received from the alcohol checker 27 to the driving management device 11 via wireless communication.

[0126] The driving management device 11 receives the results of the alcohol test and the driver's facial photograph via the mobile terminal device 21. More specifically, in the driving management device 11, the wireless communication unit 17 receives the results of the alcohol test and the driver's facial photograph via the mobile terminal device 21. The driving route information recording unit 13 records the results of the alcohol test and the driver's facial photograph acquired by the wireless communication unit 17, associating them with the driving route information Dr.

[0127] In other words, the driving management device 11 acquires the results of the alcohol test from the alcohol checker 27 and the driver's facial photograph via the portable terminal device 21, and records the acquired alcohol test results and the driver's facial photograph in association with the driving route information Dr.

[0128] Accordingly, the information recorded by the driving management device 11 in association with the driving route information Dr includes not only driver information Dd, but also the results of the alcohol test and the driver's photograph. When the driving management device 11 outputs the driving route information Dr to the server 31, it outputs the driver information Dd, the results of the alcohol test, and the driver's photograph in association with the driving route information Dr.

[0129] Furthermore, the mobile terminal device 21 may not be configured to take a photograph of the driver's face during the alcohol test. In other words, the mobile terminal device 21 may be configured to transmit only the alcohol test results to the driving management device 11. In this case, the driving management device 11 may record the acquired alcohol test results in association with the driving route information Dr. When the driving management device 11 outputs the driving route information Dr to the server 31, it may output the driver information Dd and the alcohol test results in association with the driving route information Dr.

[0130] [1-12. Processing of unsent notifications] The unsent notification process performed on server 31 is described below. The unsent notification process is repeatedly executed at predetermined execution cycles Cb. The execution cycle Cb may be, for example, 24 hours.

[0131] As shown in Figure 9, when the server control unit 32 of the server 31 starts the unsent notification process, first in S710 it determines whether or not a predetermined reminder condition has been met. If the determination is positive, it proceeds to S720; if the determination is negative, it terminates this process.

[0132] The reminder condition is met when the elapsed time Tpa exceeds the elapsed time threshold Tpt. The elapsed time Tpa corresponds to the time elapsed since the server 31 last received the travel route information Dr. The elapsed time threshold Tpt is a predetermined threshold, which may be, for example, 12 hours, 24 hours, or 2 days.

[0133] In S720, the server control unit 32 executes a process to notify all drivers registered in the driver registration information Dmd that the transmission of the driving route information Dr from the driving management device 11 to the server 31 has not been performed. The server control unit 32 sends a notification message to the email addresses of the drivers registered in the driver registration information Dmd, stating that the transmission of the driving route information Dr has not been performed.

[0134] The server control unit 32 terminates this process once it has completed S720. Furthermore, in this embodiment, if any one driver executes the process of transmitting the driving route information Dr, the driving route information Dr associated with other drivers' information Dd can also be transmitted to the server 31. Therefore, by notifying all drivers registered in the driver registration information Dmd, the server 31 can increase the likelihood that the operation to transmit the driving route information Dr will be performed.

[0135] Alternatively, the reminder condition may be met each time a predetermined condition period Cd has elapsed, regardless of whether the server 31 has received the travel route information Dr. The condition period Cd may be, for example, 24 hours, 2 days, 5 days, etc.

[0136] Server 31 includes a server control unit 32 that performs non-transmission notification processing, allowing it to notify the driver that the driving route information Dr has not been transmitted to Server 31. This prompts the driver to perform the driving route information Dr transmission.

[0137] Furthermore, the notification method is not limited to sending notification messages to email addresses; for example, it may also be a notification method using a buzzer, voice, or light emission from the operation management device 11. When connected to a mobile terminal device 21, the notification method may also be a notification method displayed on the application of the mobile terminal device 21.

[0138] [1-13. Notification Processing on Specific Dates] The specific day notification process executed on server 31 is described below. The specific day notification process is executed daily at a predetermined execution time Tc. The execution time Tc may be, for example, 7 AM, noon, 3 PM, etc.

[0139] As shown in Figure 10, when the server control unit 32 of the server 31 starts the specific date notification process, it first determines in S810 whether the specific date is approaching. If it determines that the date is approaching, it proceeds to S820; if it determines that the date is not approaching, it terminates the process. The server control unit 32 determines that the specific date is approaching and makes a positive determination if the difference between the date at the time the specific date notification process is executed and the specific date is smaller than a predetermined number of days Dn. The number of days Dn may be, for example, 10 days or 1 month.

[0140] The specified date may include, for example, the expiration date of the driver's license. The expiration date of the driver's license may be read from the date registered in the driver registration information Dmd. The specified date may also include the vehicle inspection expiration date of the vehicle on which the driving management device 11 is installed. The vehicle inspection expiration date may be pre-recorded in the server recording unit 33 of the server 31 and read from the server recording unit 33 for use.

[0141] In S820, the server control unit 32 executes a process to notify that a specific date is approaching. When the server control unit 32 notifies that the expiration date of a driver's license is approaching, it sends a notification message to the email address of the driver corresponding to that driver's license. This notification message includes a statement to alert the driver that the expiration date of the driver's license is approaching.

[0142] When the server control unit 32 notifies a vehicle that its vehicle inspection expiration date is approaching, it sends a notification message to the email address of the vehicle's administrator. This notification message includes a statement reminding the administrator that the vehicle's inspection expiration date is approaching. The vehicle administrator's email address may be pre-recorded in the server recording unit 33 of the server 31 and read from the server recording unit 33 for use.

[0143] The server control unit 32 terminates this process once it has completed S820. Server 31 can notify drivers of the approaching expiration date of their driver's license based on the information registered in the driver registration information Dmd, by having the server control unit 32 execute a specific date notification process. Therefore, drivers can be notified that their driver's license is about to expire without requiring them to perform any prior notification setting operations. Thus, server 31 can prompt drivers to renew their driver's license without requiring them to perform any notification setting operations.

[0144] [1-14. Effects] According to the embodiments described in detail above, the following effects can be obtained. (1a) Even if the driving route information Dr of a certain driver is not sent to the server 31 for an extended period, the driving management device 11 can send the unsent driving route information Dr to the server 31, provided that the driver information Dd of another driver is authenticated.

[0145] Therefore, the driving management device 11 can prevent a prolonged period in which the driving route information Dr is not transmitted to the server 31. For the administrator managing the server 31, this reduces the workload of issuing warnings to drivers in the management of the driving route information Dr.

[0146] (1b) The wireless communication unit 17 communicates wirelessly with the mobile terminal device 21, allowing it to use a wireless communication method with a relatively shorter communication range compared to a configuration where it communicates wirelessly directly with the server 31. Since the wireless communication unit 17 itself does not need to be capable of long-distance wireless communication, it is possible to transmit and receive information with the server 31 at a low cost.

[0147] (1c) The driving management device 11 acquires driver information Dd via the wireless communication unit 17 and / or the short-range wireless communication unit 19. Thus, the driving management device 11 can acquire driver information Dd by either a first acquisition method, which acquires driver information Dd from the driver's license 23, or a second acquisition method, which acquires driver information Dd from the mobile terminal device 21.

[0148] (1d) The driving management device 11 can deter drunk driving by recording the results of the alcohol test in association with the driving route information Dr. (1e) If the operation management device 11 is started up within a time period less than or equal to the allowable threshold after the operation management device 11 has stopped, the operation of reading the driver information Dd can be omitted, thereby reducing the burden on the driver.

[0149] (1f) The operation management device 11 can notify the driver that the driver information Dd has not been read, thereby preventing the vehicle from being operated without the acquisition of driver information Dd.

[0150] (1g) If the operation management device 11 is restarted within a time period less than or equal to an allowable threshold after the operation management device 11 has stopped, the operation management device 11 records the travel route information Dr recorded before stopping and the travel route information Dr after restarting as a single continuous travel route information Dr. According to the operation management device 11, in applications where short-term vehicle stops are repeated, it is possible to suppress an increase in the number of travel route information Dr, and to reduce the workload when managing multiple travel route information Dr.

[0151] (1h) The operation management device 11 can output the travel route information Dr to the server 31 via the recording medium 25, in addition to outputting it via the wireless communication unit 17. According to the operation management device 11, in environments where output via the wireless communication unit 17 is not possible, the output method via the recording medium 25 can be selected, so the operation of outputting the travel route information Dr to the server 31 from the operation management device 11 can be performed at a higher frequency.

[0152] (1i) The server 31 can notify the driver that the driving route information Dr has not been sent to the server 31, and can prompt the driver to send the driving route information Dr. (1j) According to the server 31, various types of information contained in the driving route information Dr recorded by the driving management device 11 can be displayed on the display unit of the operating terminal 41, so that the driving route information Dr can be provided to the user at a location different from the vehicle.

[0153] (1k) Server 31 enables users of the server to log in to Server 31 using a mobile terminal device 21 and an identification number and password. [1-15. Correspondence between terms] Here, we will explain the correspondence between the terms.

[0154] The control unit 13a that performs the processing in S140 corresponds to an example of a driver information acquisition unit in this disclosure, and the control unit 13a that performs the processing in S710 and S720 corresponds to an example of an unauthenticated notification unit in this disclosure.

[0155] The operating terminal 41 corresponds to an example of a server recording medium connection unit in this disclosure, and the operating terminal 41 (specifically, the display unit) corresponds to an example of a display unit in this disclosure. The server wireless communication unit 35 corresponds to an example of a login information receiving unit in this disclosure, and the server recording unit 33 corresponds to an example of a driver list recording unit in this disclosure. The server control unit 32 corresponds to an example of a login determination unit in this disclosure, and the server control unit 32 that executes the processing of S820 corresponds to an example of a notification unit in this disclosure.

[0156] [2. Other Embodiments] Although embodiments of this disclosure have been described above, this disclosure is not limited to the embodiments described above, and can be implemented in various forms without departing from the gist of this disclosure.

[0157] (a) In the above embodiment, a configuration was described in which the driving route information recording unit 13 is configured to record information on a recording medium 25 connected to the recording medium connection unit 13b. However, the driving route information recording unit is not limited to this configuration. For example, the driving route information recording unit 13 may include a driving record unit instead of the recording medium connection unit 13b. The driving record unit may be configured with, for example, an HDD, an SSD, etc. If the output of driving route information Dr from the driving management device 11 to the server 31 can be achieved solely by wireless communication, the output method via the recording medium 25 may be omitted. In this case, the driving route information recording unit 13 may record the driving route information Dr in the driving record unit without including the recording medium connection unit 13b and output the driving route information Dr to the server 31 by wireless communication. Alternatively, the driving route information recording unit 13 may include a driving record unit in addition to the recording medium connection unit 13b.

[0158] (b) The conditions for reminder are not limited to those described above and may be other conditions. The conditions for reminder may also be established in response to receiving a reminder command from the operation management device 11. For example, the operation management device 11 may be configured to send a reminder command when the data capacity of the route information Dr recorded in the route information recording unit 13 that has not been transmitted to the server 31 exceeds a predetermined capacity threshold.

[0159] (c) The non-transmission notification process is not limited to notifying all drivers registered in the driver registration information Dmd. For example, the non-transmission notification process may be configured to send notification messages only to drivers whose driving route information Dr has not been transmitted.

[0160] (d) The specific date notification process is not limited to the form described above and may take other forms. For example, the specific date may include the vehicle inspection expiration date of the vehicle on which the driving management device is installed. The notification unit may notify a device other than the mobile terminal device of the approaching specific date. The other device may be used by the server administrator rather than the driver. Alternatively, the notification unit may notify a device other than the mobile terminal device of the approaching specific date. In other words, the notification unit may notify multiple devices of the approaching specific date. The notification unit may configure the timing of notifications to differ depending on the content of the specific date. For example, the driver's license expiration date may be notified one month in advance, and the vehicle inspection expiration date may be notified two months in advance.

[0161] (e) Login authentication to server 31 is not limited to the form described above and may take other forms. For example, login information may include an identification number and password entered on the mobile terminal device, as well as the driver's license number and driver's license expiration date transmitted from the mobile terminal device 21 via the driving management device 11. Driver registration information may include each candidate's identification number and password, and each candidate's driver's license number and driver's license expiration date.

[0162] (f) The functions of one component in the above embodiment may be distributed among multiple components, or the functions of multiple components may be integrated into one component. Also, at least a part of the configuration of the above embodiment may be replaced with a known configuration having a similar function. Also, a part of the configuration of the above embodiment may be omitted. Also, at least a part of the configuration of the above embodiment may be added to or replaced with the configuration of other above embodiments. Any aspect of the technical concept specified solely by the wording in the claims is an embodiment of the present disclosure. [Explanation of Symbols]

[0163] 1... Driving management system, 11... Driving management device, 13... Driving route information recording unit, 13a... Control unit, 13b... Recording medium connection unit, 15... Position detection unit, 17... Wireless communication unit, 19... Short-range wireless communication unit, 21... Portable terminal device, 23... Driver's license with IC chip, 25... Recording medium, 27... Alcohol checker, 31... Server, 32... Server control unit, 33... Server recording unit, 35... Server wireless communication unit, 41... Operation terminal.

Claims

1. A driving control device configured to be installed in a vehicle, A position detection unit configured to detect the current position of the vehicle, A driving route information recording unit is configured to record driving route information including time-series information of the current position of the vehicle detected by the position detection unit when the vehicle is moving. A wireless communication unit configured to transmit and receive various types of information to and from a server via wireless communication, A driver information acquisition unit configured to acquire driver information relating to the driver operating the vehicle, It is equipped with, The aforementioned driving route information recording unit is configured to record the driver information acquired by the driver information acquisition unit in association with the driving route information. Furthermore, the driving route information recording unit permits the transmission and reception of information associated with the driver information acquired by the driver information acquisition unit to the server. Furthermore, the driving route information recording unit is configured such that, when predetermined preconditions are met, it does not permit the transmission or reception of information that is not the driving route information but is associated with driver information other than the acquired driver information to the server, and does permit the transmission of the driving route information associated with driver information other than the acquired driver information to the server. The above precondition is met when the driving route information recording unit has recorded driving route information associated with driver information other than that of the driver currently operating the vehicle, and when the transmission of driving route information associated with driver information other than that of the driver currently operating the vehicle has not yet been performed. Operation management device.

2. An operation management device according to claim 1, It includes a short-range wireless communication unit configured to communicate using short-range wireless communication, which has a shorter maximum communication range than the aforementioned wireless communication. The driver information acquisition unit is configured to acquire the driver information via the short-range wireless communication unit. Operation management device.

3. The operation management device according to claim 2, The wireless communication unit is configured to transmit and receive various types of information to and from the server via a portable terminal device connected by wireless communication. Operation management device.

4. The operation management device according to claim 3, The driver information acquisition unit is configured to acquire the driver information via the wireless communication unit and / or the short-range wireless communication unit. Operation management device.

5. An operation management device according to claim 1, The wireless communication unit is configured to transmit and receive various types of information to and from the server via a portable terminal device connected by wireless communication. The driver information acquisition unit is configured to acquire the driver information from the mobile terminal device via the wireless communication unit. Operation management device.

6. The operation management device according to claim 4, The aforementioned portable terminal device is configured to be connected to an alcohol checker used to perform a breathalyzer test on the driver. The driver information acquisition unit is configured to acquire the results of the alcohol test from the alcohol checker via the portable terminal device. The aforementioned driving route information recording unit is configured to record the results of the alcohol test acquired by the driver information acquisition unit in association with the driving route information. Operation management device.

7. The operation management device according to claim 4, The driver information acquisition unit is configured to use the driver information acquired at the first stop time as the driver information acquired at the first start time if the difference between the first stop time, which is the most recent stop time of the operation management device, and the first start time, which is the most recent start time of the operation management device, is less than or equal to a predetermined allowable threshold. Operation management device.

8. The operation management device according to claim 7, The system includes an unauthenticated notification unit configured to notify that the driver information has not been read if the driver information acquisition unit has not acquired the driver information during the waiting period from the start time of the operation management device until a predetermined authentication waiting time has elapsed. Operation management device.

9. The operation management device according to claim 2, The aforementioned route information recording unit is configured to record the route information recorded up to the first stop time and the route information recorded from the first start time as a single continuous route information if the difference between the first stop time, which is the most recent stop time of the operation management device, and the first start time, which is the time the operation management device was started, is less than or equal to a predetermined allowable threshold. Operation management device.

10. The operation management device according to claim 2, It includes a recording medium connection section configured to connect a recording medium, The aforementioned driving route information recording unit is configured to store the aforementioned driving route information for all drivers, regardless of the driver information acquired, in the recording medium connected to the recording medium connection unit. Operation management device.

11. A server configured to store travel route information recorded by a driving management device, A server wireless communication unit configured to transmit and receive various information to and from the aforementioned operation management device via wireless communication, A server recording unit configured to record the route information received via the server wireless communication unit, A non-transmission notification unit is configured to notify that the transmission of the driving route information from the driving management device to the server has not been performed when predetermined reminder conditions are met, Equipped with, The aforementioned reminder condition is met when the elapsed time since the last receipt of the aforementioned travel route information exceeds a predetermined elapsed time threshold, or when a predetermined conditional cycle has elapsed. server.

12. A server according to claim 11, The server includes a recording medium connection unit configured to connect to a recording medium on which the aforementioned travel route information is recorded, The server recording unit is configured to receive the travel route information via the recording medium connected to the server wireless communication unit or the server recording medium connection unit. server.

13. A server according to claim 12, The aforementioned route information includes the start time of travel, the end time of travel, the distance traveled, and the travel time. The server includes a display unit configured to display the start time of travel, the end time of travel, the distance traveled, and the duration of travel based on the travel route information. server.

14. The server according to claim 13, The server wireless communication unit is configured to transmit and receive various types of information to and from the operation management device via a portable terminal device connected by wireless communication. The aforementioned server, A login information receiving unit configured to receive login information of a user who has applied to log in to the server from the mobile terminal device, A driver list recording unit is configured to record driver registration information, including a list of candidates who will drive a vehicle equipped with the aforementioned driving management device. A login determination unit is configured to allow the login applicant to log in if the login information of the login applicant is included in the driver registration information, and to not allow the login applicant to log in if the login information of the login applicant is not included in the driver registration information. Equipped with, The login information is the identification number and password entered on the mobile terminal device, or the driver's license number and driver's license expiration date transmitted from the mobile terminal device via the operation management device. The driver registration information includes the identification number and password of each candidate, and the driver's license number and expiration date of the driver's license of each candidate. server.

15. The server according to claim 14, It includes a notification unit configured to notify the mobile terminal device of the approach of a predetermined specific date, The aforementioned specified date includes the expiration date of the driver's license. server.

16. An operation management device according to any one of claims 1 to 10, A server according to any one of claims 12 to 15, A driving management system equipped with the following features.

Images