WO2016194118A1

WO2016194118A1 - Fleet management system

Info

Publication number: WO2016194118A1
Application number: PCT/JP2015/065815
Authority: WO
Inventors: 貞一武藤; クリスチャンヨハンソン
Original assignee: ボルボトラックコーポレーション; 貞一武藤; クリスチャンヨハンソン
Priority date: 2015-06-01
Filing date: 2015-06-01
Publication date: 2016-12-08

Abstract

Provided is a fleet management system in which a driver uses a portable communication terminal (40) belonging to himself to login to a server (10) so as to be establish communication between a vehicle-mounted device (20) and the server (10) and be able to transmit and receive fleet management information. The vehicle-mounted device (20) displays, via an output interface (25), a barcode in which is encoded vehicle identification information which is read out from a storage unit (23). The portable communication terminal (40) transmits to the server (10) the vehicle identification information which is decoded from an image, captured by an image capture unit (43), of the barcode displayed on the output interface (25), together with personal identification information which is read out from a storage unit (42). The server (10) reads out from a storage unit (12) a driver registration table in which an assigned driver is registered by date and time, and determines whether to authenticate the driver on the basis of the received vehicle identification information and personal identification information.

Description

Vehicle operation management system

The present invention relates to a vehicle operation management system that manages the operation status of a vehicle.

Conventionally, in a vehicle operation management system that manages the operation status of a vehicle, an in-vehicle device mounted on the vehicle establishes wireless communication with the vehicle operation management center and transfers information related to vehicle operation management. The server receives the personal identification information of the vehicle-mounted device that is manually input or selected from the past input history and transmitted to the server of the vehicle operation management center together with the vehicle identification information stored in the vehicle-mounted device. The driver is authenticated based on the personal identification information and the vehicle identification information (see, for example, Patent Document 1).

JP 2012-053546 A

However, if the driver erroneously inputs personal identification information, the driver is forced to input personal identification information again. In addition, if a third party deliberately inputs another person's personal identification information and impersonates another person, the vehicle may be illegally operated.

Therefore, in view of the conventional problems as described above, the present invention provides a vehicle operation management system that improves the certainty that the personal identification information of the driver who actually drives the vehicle is transmitted to the server of the vehicle operation management center. The purpose is to do.

For this reason, the vehicle operation management system according to the present invention includes a server that authenticates a driver who drives the vehicle, a first memory that stores vehicle identification information that identifies the vehicle, and a vehicle that is stored in the first memory. An in-vehicle device that includes an encoder that encodes identification information into a barcode, and a display that displays the barcode encoded by the encoder, and that transmits and receives information related to vehicle operation management with the server through server authentication, and a display An image sensor that captures the barcode displayed on the mobile phone, a decoder that decodes the barcode captured by the image sensor into vehicle identification information, and a second communication memory that stores personal identification information that identifies an individual The mobile communication terminal decodes the personal identification information stored in the second memory with a decoder. With the vehicle identification information, characterized in that it is configured to request transmission to authenticate the driver to the server.

According to the vehicle operation management system of the present invention, since the personal identification information stored in the mobile communication terminal belonging to the driver is transmitted to the server of the vehicle operation management center, the personal identification of the driver who actually drives the vehicle The certainty of transmitting information to the server can be improved.

It is explanatory drawing which shows the outline | summary of a vehicle operation management system. It is a functional block diagram which shows the function relevant when a driver | operator logs in to a server among vehicle operation management systems. It is a flowchart which shows the login information display process performed with a vehicle-mounted apparatus. It is explanatory drawing which shows an example of the screen which displayed login information in the vehicle equipment. It is explanatory drawing which shows an example of the screen which displayed the completion of login in the vehicle equipment. It is a flowchart which shows 1st Embodiment of the identification information transmission process for login performed with a portable communication terminal. It is explanatory drawing which shows the screen which displayed the guidance information of identification information transmission in a portable communication terminal. It is a flowchart which shows the authentication process performed with a server. It is a functional block diagram which shows 2nd Embodiment of a portable communication terminal. It is a flowchart which shows 2nd Embodiment of the identification information transmission process for the login performed with a portable communication terminal. It is a functional block diagram which shows 3rd Embodiment of a mobile communication terminal. It is a flowchart which shows 3rd Embodiment of the identification information transmission process for the login performed with a portable communication terminal. It is a functional block diagram which shows 4th Embodiment of a portable communication terminal. It is a flowchart which shows 4th Embodiment of the identification information transmission process for the login performed with a portable communication terminal. It is a functional block diagram which shows 5th Embodiment of a portable communication terminal. It is a flowchart which shows 5th Embodiment of the identification information transmission process for login performed with a portable communication terminal.

Hereinafter, a first embodiment for carrying out the present invention will be described in detail with reference to the accompanying drawings.
FIG. 1 shows an outline of a vehicle operation management system.

In the vehicle operation management system 1, a server 10 installed in a vehicle operation management center (for example, an establishment of a vehicle manufacturer) 2 and an in-vehicle device 20 installed in the vehicle 3 are connected to be communicable via wireless communication. In addition, a management information terminal (for example, a personal computer) 30 and a server 10 of the vehicle operation management center 2 installed at the office 4 of an operation manager (for example, a transportation company) that manages the operation of the vehicle 3 are provided. It is communicably connected via a communication network 5 such as the Internet, and is configured such that operation management information related to operation management of the vehicle 3 is transmitted and received between the management information terminal 30 and the in-vehicle device 10 via the server 10. Has been.

The in-vehicle device 20 receives a GPS signal from a GPS (Global Positioning System) satellite 6, measures the position information and time information of the vehicle 3 based on the received GPS signal, and uses the position information and time information as operation management information. To the server 10 periodically.

Further, the in-vehicle device 20 is set / released by manual input of the driver 7, a working state (for example, loading, unloading, waiting, rest, etc.), traveling road classification (for example, general road, highway, etc.) and Load management information (for example, empty vehicle, actual vehicle, etc.), various measurement times (for example, total driving time, etc.) that are automatically measured, various measurement distances (for example, total driving distance, etc.), etc. as server management information 10 to send periodically.

Further, the in-vehicle device 20 performs management of fuel-saving driving, management of continuous operation time, management of idling time, management of luggage compartment temperature, management of vehicle state, etc. for the vehicle 3, and each managed by these managements. When the parameter exceeds a management threshold value (changeable from the management information terminal 30 via the server 10), the driver 7 is notified and transmitted to the server 10 as operation management information.
And the server 10 memorize | stores the above-mentioned operation management information received from the vehicle-mounted apparatus 20 sequentially.

Therefore, the operation manager can grasp the operation management information transmitted from the in-vehicle device 20 to the server 10 in real time by accessing the server 10 from the management information terminal 30.

In addition, the server 10 automatically creates a daily operation report based on the accumulated operation management information and transmits it to the management information terminal 30 when the vehicle 3 is closed. Promoting.

On the other hand, the management information terminal 30 transmits various operation management information to the in-vehicle device 20 through the server 10 such as, for example, a management threshold value used as a reference in each management described above and a business message for the driver 7.

In such a vehicle operation management system 1, in order to establish communication between the in-vehicle device 20 of the vehicle 3 and the server 10 of the vehicle operation management center 2 and to enable transmission / reception of operation management information, the driver 10 Although authentication is required, in the present embodiment, the driver 7 logs in to the server 10 via wireless communication using the mobile communication terminal 40 belonging to him / her instead of the in-vehicle device 20. Yes.

FIG. 2 is a functional block diagram showing functions related to when the driver 7 logs into the server 10 in the vehicle operation management system 1.
The server 10 includes a communication interface 11, a storage unit 12, and a control unit 13.

The communication interface (I / F) 11 connects the server 10 to the in-vehicle device 20 and the portable communication terminal 40 via the communication network 8 such as a packet communication network so that data communication is possible, and can exchange data. It is configured. The communication network 8 may include not only a wireless communication network but also a wired communication network.

The storage unit 12 is a database that stores in advance a driver registration table VPT in which a driver is registered according to the date and time for a vehicle that is managed by the operation manager. Specifically, in the driver registration table VPT, the vehicle identification information VI for specifying the vehicle and the personal identification information PI for specifying the driver are associated with each other according to the date and time, and the driving responsible for driving the vehicle. Is configured to search for a person.

The control unit 13 includes a CPU (Central Processing Unit), and reads and executes a program stored in advance in a ROM (Read Only Memory) or the like. Specifically, the control unit 13 refers to the driver registration table VPT read from the storage unit 12 and based on the vehicle identification information VI and the personal identification information PI received from the mobile communication terminal 40 via the communication interface 11. Thus, the driver 7 is authenticated, and the result of the authentication is notified to the in-vehicle device 20 or the portable communication terminal 40 via the communication interface 11.

The in-vehicle device 20 includes a communication interface (I / F) 21, an in-vehicle communication unit 22, a storage unit 23, an encoder 24, an output interface (I / F) 25, and a control unit 26. Regardless of whether the ignition switch of the vehicle 3 is turned on or off, the in-vehicle device 20 is always supplied with power from an in-vehicle battery (not shown).

The communication interface 21 connects the in-vehicle device 20 and the server 10 so that data communication is possible.
The in-vehicle communication unit 22 is connected to the in-vehicle communication network of the vehicle 3 such as CAN (Controller Area Network) communication, and an IGN signal indicating that the ignition switch (IGN) is on or off, for example, an engine control Received from a controller outside the in-vehicle device 20 such as a unit.

The storage unit 23 is a non-volatile memory (first memory) such as a ROM (Read Only Memory) that stores the vehicle identification information VI of the vehicle 3. The vehicle identification information VI is character information unique to the vehicle 3 on which the in-vehicle device 20 is mounted. Thus, the vehicle 3 can be specified. The vehicle identification information VI is set including, for example, a chassis number or an automobile registration number that is unique information of the vehicle 3.

The encoder 24 has a function of encoding the vehicle identification information VI of the vehicle 3 into a one-dimensional or two-dimensional barcode. One-dimensional barcodes include UPC (Universal Product Code) code, JPN (Japanese Article Number) code, EAN (European Article Number) code, etc. Two-dimensional barcodes include, for example, QR code (registered trademark). It is well known. The encoder 24 may be configured as a part of the control unit 26.

The output interface 25 is a display unit that is controlled by a display driver (not shown) under an instruction signal from the control unit 26 and displays various types of information. A display screen is displayed in the cabin of the vehicle 3 so that the driver 7 can visually recognize the information. Is formed. The display screen of the output interface 25 is formed, for example, as a part of the in-vehicle device 20 installed in the vehicle interior, or as a display separate from the main body in which the control unit 26 or the like is built. It is provided on dashboards such as the instrument panel. The display screen of the output interface 25 may be a touch panel type liquid crystal display. When the vehicle 3 includes a car navigation system, a display that displays map information, road information, and the like may be shared as a display screen of the output interface 25 of the in-vehicle device 20.

The control unit 26 includes a CPU, and reads and executes a program stored in advance in a ROM or the like built in the in-vehicle device 20. Specifically, the control unit 26 reads the vehicle identification information VI of the vehicle 3 from the storage unit 23 and instructs the encoder 24 to encode the read vehicle identification information VI into a one-dimensional or two-dimensional barcode. The control unit 26 receives the IGN signal transmitted from the in-vehicle communication unit 22, the vehicle identification information VI read from the storage unit 23, the barcode data encoded by the encoder 24, and the server 10 via the communication interface 21. Based on the notification or the like, an instruction signal for displaying information related to login is sent to the output interface 25 (display driver).

Therefore, the in-vehicle device 20 performs a login information display process for displaying information related to login without performing an identification information transmission process for transmitting identification information for login to the server 10.

The mobile communication terminal 40 includes a communication interface 41, a storage unit 42, an imaging unit 43, an input interface (I / F) 44, a decoder 45, an output interface (I / F) 46, and a control unit 47. As the mobile communication terminal 40, for example, a camera-equipped mobile phone or a camera-equipped smartphone is assumed.

Similar to the communication interface 21, the communication interface 41 connects the mobile communication terminal 40 and the server 10 so that data communication is possible.
The storage unit 42 is a non-volatile memory (second memory) such as a ROM that always stores the personal identification information PI. The personal identification information PI is character information unique to the driver 7 who owns the mobile communication terminal 40, and can thereby identify the driver 7. In addition, when the mobile communication terminal 40 is a mobile phone, unique information (phone number, mail address, individual identification number) of the mobile phone may be used as the personal identification information PI.

The imaging unit 43 includes an imaging device such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor, and is an imaging unit that sends an image captured by the imaging device to the control unit 47 as digital data. Is used to photograph a one-dimensional or two-dimensional barcode displayed on the display screen (dotted line arrow in FIG. 3).

The input interface 44 is an input unit for inputting instructions from the driver 7 to the control unit 47, and includes input keys (buttons) including character keys and direction keys arranged on the surface of the mobile communication terminal 40, or It is a touch panel by various systems, such as a resistive film system or a capacitive system. When the mobile communication terminal 40 has a voice recognition function, a microphone that converts voice into an electrical signal may be used as the input interface 44.

The output interface 46 is a display device that displays various types of information under the instruction signal from the control unit 47 and is controlled by a display driver (not shown). The display screen is formed so as to partially define the mobile communication terminal 40. The
The decoder 45 has a function of decoding the one-dimensional or two-dimensional barcode imaged by the imaging unit 43 into the vehicle identification information VI.

The control unit 47 includes a CPU, and the driver 7 reads and executes a program stored in advance in a ROM or the like built in the mobile communication terminal 40 based on an input signal obtained by operating the input interface 44. Specifically, the control unit 47 instructs the decoder 45 to decode the barcode photographed by the imaging unit 43 into the vehicle identification information VI, and the decoded vehicle identification information VI is stored in a RAM (Random Access Memory) (not shown). ) Temporarily stored in a volatile memory. The control unit 47 instructs the output interface 46 (display driver) to display operation information for logging in, and based on the input signal generated by the driver 7 operating the input interface 44 in accordance with the operation information. Then, the vehicle identification information VI decoded by the decoder 45 and the personal identification information PI read from the storage unit 42 are transmitted to the server 10 at once via the communication interface 41.

Therefore, the mobile communication terminal 40 performs identification information transmission processing for login, in which the personal identification information PI and the vehicle identification information VI are transmitted to the server 10.

FIG. 3 shows the contents of the login information display process repeatedly executed in the control unit 25 of the in-vehicle device 20.

In step 101 (abbreviated as “S101” in the figure, the same applies hereinafter), it is determined whether or not the ignition switch is on based on the IGN signal from the in-vehicle communication unit 22.
If it is determined that the ignition switch is on, the intention to operate the vehicle 3 is confirmed, and it can be determined that there is a possibility of logging in to the server 10 in order to exchange the operation management information. In order to continue the information display process, the process proceeds to step 102 (Yes). On the other hand, if it is determined that the ignition switch is off, it is presumed that there is no intention to operate the vehicle 3, so it is determined that there is no possibility of logging in to the server 10, and this step is performed. repeat.

In step 102, it is determined whether or not it is a new login, in other words, whether or not it is already logged in to the server 10.
If it is determined that the login is a new login, the process proceeds to step 103 (Yes). On the other hand, if it is determined that the login is not a new login, the login information display process is terminated.

In step 103, login information display for displaying information for login on the output interface 25 is performed. The login information includes at least the vehicle identification information VI and a one-dimensional or two-dimensional code that encodes the vehicle identification information VI. Further, the login information may include a message for requesting the driver 7 to start a login application for performing identification information transmission processing for login in the mobile communication terminal 40, as will be described later.

As the login information display, for example, as shown in FIG. 4, guidance for performing login guidance on the output interface 25 such as “Do you want to log in?” And “Please read the QR code (registered trademark) on your smartphone”. Information 25a, vehicle identification information VI such as affiliation of vehicle 3, chassis number, vehicle registration number, and QR code (registered trademark) 25b encoded with vehicle identification information VI are displayed. In addition, in the login information display and the login success display described later, information 25c such as time and travel distance may be displayed.

In Step 104, it is determined whether or not an authentication notification for authenticating the driver 7 is received from the server 10 via the communication interface 11 as a result of the authentication process of the driver 7 in the server 10 described later.
If it is determined that the authentication notification has been received, the login has been successful, and the process proceeds to step 105 (Yes). On the other hand, if it is determined that the authentication notification has not been received, the login has not yet been successful. Therefore, it progresses to step 106 (No).

In step 105, the login information display on the output interface 25 is switched to a login success display for displaying that the login is successful. The login success display may be automatically deleted after the estimated time that the driver 7 has confirmed the display content has elapsed.

As the login success display, for example, as shown in FIG. 5, login result information 25 d for indicating the login success and driver authentication information 25 e for confirming the name of the authenticated driver 7 are displayed. Note that a message 25f that urges the driver 7 to drive safely may be displayed as the login success display.

Due to the successful login, communication is established between the in-vehicle device 20 and the server 10, and not only operation management information can be exchanged in the in-vehicle device 20, but also in the management information terminal 30 via the server 10. The operation management information can be exchanged with 20.

In step 106, it is determined whether or not to generate a timeout for ending the login information display process based on the time during which the state in which the authentication notification from the server 10 cannot be received in step 104 continues. That is, in step 104, if the authentication notification cannot be received within a certain time, it is determined that the login has failed, and it is determined that a timeout occurs. This prevents step 104 from being executed indefinitely.
If it is determined that a timeout will occur, the login information display is deleted and the login information display process is terminated (Yes). On the other hand, if it is determined that a timeout will not occur, the process returns to step 104 to continue waiting for an authentication notification from the server 10.

FIG. 6 shows the contents of the identification information transmission process for login, which is started in response to an input signal from the input interface 44 operated by the driver 7 in the control unit 47 of the mobile communication terminal 40.

In step 201, it is determined whether or not the vehicle identification information VI has been acquired. Acquisition of the vehicle identification information VI means that the vehicle identification information VI can be transmitted. Specifically, in this step, for example, the vehicle identification information VI obtained by decoding the one-dimensional or two-dimensional barcode captured by the imaging unit 43 from the output interface 25 by the driver 45 by the decoder 45 is temporarily stored in the RAM or the like. It is determined whether or not it has been done. Note that an image instructing to capture a one-dimensional or two-dimensional barcode may appear on the display screen of the output interface 46 after the execution of the identification information transmission process for login.
If it is determined that the vehicle identification information VI has been acquired, the process proceeds to step 203 (Yes). On the other hand, if it is determined that the vehicle identification information VI has not been acquired, the process proceeds to step 202 (No).

In step 202, it is determined whether or not to generate a timeout for ending the identification information transmission process, based on the time during which the state where the vehicle identification information VI cannot be acquired in step 201 continues. Thereby, for example, this step is not executed indefinitely at the start of the identification information transmission process due to an erroneous operation of the driver 7.
If it is determined that a timeout occurs, the identification information transmission process for login is terminated (Yes). On the other hand, if it is determined that a timeout will not occur, the process returns to step 201 and continues to wait for acquisition of the vehicle identification information VI.

In step 203, the personal identification information PI is read from the storage unit 42 into a volatile memory such as a RAM.
In step 204, whether or not to transmit the vehicle identification information VI and the personal identification information PI temporarily stored in a volatile memory such as a RAM to the server 10 based on an input signal generated by the operation of the input interface 44 of the driver 7 is determined. Determine whether.

Specifically, in step 204, the vehicle identification information VI is displayed on the output interface 46, and the driver 7 is requested to select whether or not to log in to the server 10.
The driver 7 compares both the vehicle identification information VI displayed on the output interface 46 in this step with the vehicle identification information VI displayed on the output interface 25 of the in-vehicle device 20 in step 103. Whether or not the vehicle identification information VI matches can be confirmed, and whether or not to log in can be selected by operating the input interface 44 based on the confirmed result.

As shown in FIG. 7, for example, when the output interface 46 has a touch panel display of a smartphone, the display includes acquisition completion information 46a, vehicle identification information VI, In addition, a “Yes” button icon 46 b and a “No” button icon 46 c are displayed by GUI (Graphical User Interface) so that the user can select whether or not to log in.

When the driver 7 chooses to log in by operating the input interface 44, the vehicle identification information VI and the personal identification information PI temporarily stored in the RAM or the like are collectively or mutually associated with the server 10 (Yes). On the other hand, when the driver 7 selects not to log in by operating the input interface 44, the identification information transmission process for login is terminated.

In step 205, it is determined whether or not a non-authentication notification indicating that the driver 7 is not authenticated is received from the server 10 via the communication interface 41 as a result of the authentication process of the driver 7 in the server 10 described later.
If it is determined that a non-authentication notification has been received, the login has failed and the identification information transmission process for login is terminated (Yes). On the other hand, if it is determined that the non-authentication notification has not been received, since the success or failure of the login is still unknown, the process proceeds to step 206 (No).

In step 206, it is determined whether or not to generate a timeout for ending the identification information transmission process for login, based on the time during which the state where the unauthenticated notification cannot be received in step 205 continues.
If it is determined that a timeout occurs, the identification information transmission process for login is terminated (Yes). On the other hand, if it is determined that a timeout will not occur, the process returns to step 205 and continues to wait for a non-authentication notification from the server 10.

FIG. 8 shows the contents of the authentication process of the driver 7 repeatedly executed by the control unit 13 of the server 10.

In step 301, it is determined whether or not there is an authentication request, that is, whether or not the vehicle identification information VI and the personal identification information PI are received from the mobile communication terminal 40 via the communication interface 11.
If it is determined that there is an authentication request, the process proceeds to step 302 to perform the authentication process (Yes). On the other hand, if it is determined that there is no authentication request, this step is performed again (No).

In step 302, a driver registration table VPT in which a driver in charge of driving is registered from a storage unit 12 to a volatile memory such as a RAM for a vehicle for which the operation manager performs operation management.

In step 303, referring to the driver registration table VPT, whether or not the person in charge of driving the vehicle 3 is the driver 7 at the current date and time, in other words, the combination of the vehicle 3 and the driver 7 is appropriate. It is determined whether or not.

Specifically, by referring to the driver registration table VPT, the driver in charge of driving the vehicle that matches the vehicle identification information VI received from the mobile communication terminal 40 at the current date and time is searched and extracted by the search. It is determined whether or not the driver's personal identification information PI matches the personal identification information PI received from the mobile communication terminal 40.
If it is determined that the combination of the vehicle 3 and the driver 7 is appropriate, the process proceeds to step 304 (Yes), while if the combination of the vehicle 3 and the driver 7 is determined to be inappropriate. Advances to step 305 (No).

In step 304, an authentication notification for authenticating the driver 7 is transmitted to the in-vehicle device 20 via the communication interface 11.
In step 305, a non-authentication notification indicating that the driver 7 is not authenticated is transmitted to the mobile communication terminal 40 via the communication interface 11.

According to such a vehicle operation management system 1, in order for the driver 7 to log in to the server 10, the one-dimensional or two-dimensional barcode displayed on the output interface 25 of the in-vehicle device 20 is captured by the imaging unit of the mobile communication terminal 40. The vehicle identification information VI acquired by photographing at 43 and the personal identification information PI read from the storage unit 42 of the mobile communication terminal 40 are transmitted from the mobile communication terminal 40 to the server 10.

Therefore, since there is no possibility that the driver 7 erroneously inputs the personal identification information PI, the driver 7 is not forced to re-enter the personal identification information PI due to erroneous input. Moreover, if the third party does not have the mobile communication terminal 40 belonging to another person, it cannot impersonate another person, and there is no possibility that the vehicle 3 is operated illegally.

In short, according to the vehicle operation management system 1, the vehicle 7 is actually compared with the case where the driver 7 manually inputs his / her personal identification information to the in-vehicle device 20 or selects from the past input history and transmits it to the server 10. The certainty of transmitting the personal identification information PI of the driver 7 who is driving to the server 10 of the vehicle operation management center 2 can be improved.

Next, a second embodiment for carrying out the present invention will be described. In addition, about the same structure as 1st Embodiment, the description is abbreviate | omitted or simplified by attaching | subjecting the same code | symbol.
FIG. 9 shows a mobile communication terminal 40a according to the second embodiment.

The mobile communication terminal 40 according to the first embodiment has a configuration in which the personal identification information PI transmitted to the server 10 for login is always stored in the storage unit 42 that is a nonvolatile memory. In addition, in the mobile communication terminal 40a according to the second embodiment, for example, identification information stored in an IC (Integrated Circuit) embedded in an identification card such as a driver's license is stored in the IC card reader 48. And the identification information is also transmitted to the server 10. The IC card reader 48 uses, for example, NFC (Near Field Communication), a short-distance wireless communication, in particular, a non-contact communication capable of near-field wireless communication (about 10 cm or less) to obtain identification information from the identification card. It is a reading unit that can read.

In the driver registration table VPT stored in the storage unit 12 of the server 10, the identification information is registered in association with the vehicle identification information VI in addition to the personal identification information PI. Therefore, in step 303 in the authentication process of the driver 7 executed by the control unit 13 of the server 10, the vehicle identification information VI received from the mobile communication terminal 40 at the current date and time by referring to the driver registration table VPT. The driver's personal identification information PI and identification information extracted by the search match the personal identification information PI and identification information received from the mobile communication terminal 40. It is determined whether or not to do.

FIG. 10 shows the content of the identification information transmission process for login according to the second embodiment in which some steps are replaced / added to the first embodiment.
The identification information transmission process for login in the second embodiment is different from the first embodiment in that step 203 is replaced with step 203a1, step 204 is replaced with step 204a, and step 203a2 is further added. .

In step 203a1, it is determined whether or not the reading of the personal identification information PI by the IC card reader 48 is completed.
In step 203a2, it is determined whether or not to generate a timeout for ending the identification information transmission process, based on the duration of the state in which the reading of the personal identification information PI is not completed in step 203a1.

If it is determined that a timeout occurs, the identification information transmission process for login is terminated (Yes). On the other hand, if it is determined that a timeout will not occur, the process returns to step 203a1 to continue waiting for acquisition of the personal identification information PI.
In step 204a, the vehicle identification information VI, personal identification information PI and identification information temporarily stored in a volatile memory such as a RAM are stored in the server 10 based on an input signal generated by the operation of the input interface 44 of the driver 7. It is determined whether or not to transmit.

According to the vehicle management system 1 according to the second embodiment as described above, the personal identification information PI of the driver 7 who actually drives the vehicle 3 is sent to the server 10 of the vehicle operation management center 2 as in the first embodiment. In addition to improving the certainty of transmission, since the identification information stored in the identification card is also transmitted to the server 10 in addition to the personal identification information PI, the authentication accuracy of the driver 7 at the server 10 is also improved. It has the advantage that.

Next, a third embodiment for carrying out the present invention will be described. In addition, about the same structure as 1st Embodiment, the description is abbreviate | omitted or simplified by attaching | subjecting the same code | symbol.
FIG. 11 shows a mobile communication terminal 40b according to the third embodiment.

The mobile communication terminal 40 according to the first embodiment has a configuration in which the personal identification information PI transmitted to the server 10 for login is always stored in the storage unit 42 which is a nonvolatile memory. In addition, in the mobile communication terminal 40b according to the third embodiment, the biological information such as the physical characteristics and behavioral characteristics of the driver 7 is read by the biological information reader 49, and the biological information is also transmitted to the server 10. It is configured to be transmitted. The biometric information reader 49 is, for example, a reading unit such as a sensor that acquires the physical characteristics (such as fingerprints) and behavioral characteristics (handwriting or the like) of the driver 7.

In the driver registration table VPT stored in the storage unit 12 of the server 10, biometric information is registered in advance in association with the vehicle identification information VI in addition to the personal identification information PI. Therefore, in step 303 in the authentication process of the driver 7 executed by the control unit 13 of the server 10, the vehicle identification information VI received from the mobile communication terminal 40 at the current date and time by referring to the driver registration table VPT. Whether the driver's personal identification information PI and biometric information extracted by the search matches the personal identification information PI and biometric information received from the mobile communication terminal 40. Determine whether or not.

FIG. 12 shows the content of the identification information transmission process for login according to the third embodiment in which some steps are replaced and added to the first embodiment.
The identification information transmission process for login in the third embodiment is different from the first embodiment in that step 203 is replaced with step 203b1, step 204 is replaced with step 204b, and step 203b2 is further added. .

In step 203b1, as in step 203a1, it is determined whether or not the biometric information reader 49 has completed reading biometric information.
In step 203b2, as in step 203a2, it is determined whether or not to generate a timeout for ending the identification information transmission process.

If it is determined that a timeout will occur, the identification information transmission process for login is terminated (Yes). If it is determined that a timeout will not occur, the process returns to step 203b1, and biometric information acquisition is continued. wait.
In step 204a, it is determined whether or not the vehicle identification information VI, personal identification information PI, and biological information temporarily stored in the RAM or the like are transmitted to the server 10.

According to the vehicle management system 1 according to the third embodiment, the personal identification information PI of the driver 7 who actually drives the vehicle 3 is sent to the server 10 of the vehicle operation management center 2 as in the first embodiment. In addition to improving the certainty of transmission, the biometric information of the driver 7 is also transmitted to the server 10 in addition to the personal identification information PI, so that the authentication accuracy of the driver 7 at the server 10 is improved. ing.

Next, a fourth embodiment for carrying out the present invention will be described. In addition, about the same structure as 2nd Embodiment, the description is abbreviate | omitted or simplified by attaching | subjecting the same code | symbol.

FIG. 13 shows a mobile communication terminal 40c according to the third embodiment.
Compared to the storage unit 42 of the second embodiment, the storage unit 42c of the third embodiment has an identification stored in the identification card of the driver to which the mobile communication terminal 40c belongs in addition to the personal identification information PI. Proof information PIc is further stored.

FIG. 14 shows contents obtained by replacing / adding some steps in the identification information transmission process for login according to the fourth embodiment with respect to the second embodiment.
The identification information transmission process for login in the fourth embodiment is different from the second embodiment in that step 204a is replaced with step 204c and step 203c is added between step 203a1 and step 204a.

In step 203c, it is determined whether or not the identification information PIc read from the identification card by the IC card reader 48 matches the identification information PIc stored in advance in the storage unit 42c.
If it is determined that the identification information PIc read from the identification card by the IC card reader 48 matches the identification information PIc stored in advance in the storage unit 42c, the process proceeds to step 204c (Yes). On the other hand, if it is determined that they do not match, the mobile communication terminal 40 does not belong to the driver 7, and thus the identification information transmission process for login is terminated in order to prevent unauthorized login.

In step 204c, as in step 204 of the first embodiment, it is determined whether or not the vehicle identification information VI and the personal identification information PI are to be transmitted to the server 10.

According to the vehicle operation management system 1 according to the fourth embodiment, the identification information PIc read from the identification card by the IC card reader 48 is assumed to be transmitted to the server 10 on the assumption that the personal identification information PI is transmitted to the server 10. It is necessary to match the identification information PIc stored in advance in the 40 storage units 42c. Therefore, the certainty of transmitting the personal identification information PI of the driver 7 who actually drives the vehicle 3 to the server 10 of the vehicle operation management center 2 can be improved more than in the first embodiment.

Next, a fifth embodiment for carrying out the present invention will be described. In addition, about the same structure as 3rd Embodiment, the description is abbreviate | omitted or simplified by attaching | subjecting the same code | symbol.

FIG. 15 shows a mobile communication terminal 40d according to the fifth embodiment.
Compared with the storage unit 42 of the third embodiment, the storage unit 42d of the fifth embodiment further stores biometric information PId of the driver to which the mobile communication terminal 40d belongs in addition to the personal identification information PI. Yes.

FIG. 16 shows the content of the identification information transmission process for login according to the fifth embodiment in which some steps are replaced and added to the third embodiment.
The identification information transmission process for login in the fifth embodiment is different from the third embodiment in that step 204b is replaced with step 204d and step 203d is added between step 203b1 and step 204b.

In step 203d, it is determined whether or not the biological information PId read by the biological information reader 49 from a fingerprint or the like matches the biological information PId stored in advance in the storage unit 42d.
If it is determined that the biological information PId read by the biological information reader 49 matches the biological information PId stored in advance in the storage unit 42d, the process proceeds to step 204d (Yes). On the other hand, if it is determined that they do not match, the mobile communication terminal 40d does not belong to the driver 7, so the identification information transmission process for login is terminated in order to prevent unauthorized login.

In step 204d, as in step 204 of the first embodiment, it is determined whether or not the vehicle identification information VI and the personal identification information PI are transmitted to the server 10.

According to the vehicle operation management system 1 according to the fifth embodiment, the biometric information PId read by the biometric information reader 49 from a fingerprint or the like is stored in the storage unit 42d on the premise that the personal identification information PI is transmitted to the server 10. It is necessary to match the biometric information PId stored in advance. Therefore, the certainty of transmitting the personal identification information PI of the driver 7 who actually drives the vehicle 3 to the server 10 of the vehicle operation management center 2 is improved more than the first embodiment as in the fourth embodiment. Can do.

The embodiments selected as described above are merely selected to illustrate and explain the present invention, and without departing from the scope of the present invention as defined in the appended claims. It will be apparent to those skilled in the art from the present disclosure that various changes and modifications can be made.

Also, the foregoing descriptions of embodiments according to the present invention are provided for illustration only and are not intended to limit the present invention (the invention as claimed in the appended claims or equivalents thereof). Absent.

DESCRIPTION OF SYMBOLS 1 ... Vehicle operation management system, 2 ... Vehicle operation management center, 3 ... Vehicle, 7 ... Driver, 8 ... Communication network, 10 ... Server, 20 ... In-vehicle device, 23 ... Memory | storage part, 24 ... Encoder, 25 ... Output interface (I / F), 26 ... control unit, 40, 40a, 40b, 40c, 40d ... mobile communication terminal, 42, 42c, 42d ... storage unit, 43 ... imaging unit, 45 ... decoder, 47 ... control unit, 48 ... IC card reader, 49 ... biometric information reader, PI ... personal identification information, VI ... vehicle identification information, PIc ... identification information, PId ... biometric information

Claims

A server that authenticates the driver who drives the vehicle;
A first memory for storing vehicle identification information for identifying the vehicle; an encoder for encoding the vehicle identification information stored in the first memory into a barcode; and a display for displaying the barcode encoded by the encoder An in-vehicle device that transmits and receives information related to vehicle operation management with the server by authentication of the server;
An image sensor that captures the barcode displayed on the display, a decoder that decodes the barcode captured by the image sensor into the vehicle identification information, and a second memory that stores personal identification information that identifies an individual A mobile communication terminal equipped with
Comprising
The mobile communication terminal is configured to request the driver's authentication by transmitting the personal identification information stored in the second memory to the server together with the vehicle identification information decoded by the decoder. Vehicle operation management system.
The portable communication terminal further includes an IC card reader that reads the identification information stored in the IC embedded in the identification card, and the identification card read by the IC card reader together with the personal identification information and the vehicle identification information. The vehicle operation management system according to claim 1, wherein information is also transmitted to the server.
The mobile communication terminal further includes a biometric information reader that reads biometric information, and is configured to transmit the biometric information read by the biometric information reader to the server together with the personal identification information and the vehicle identification information. Item 4. The vehicle operation management system according to Item 1.
The portable communication terminal further includes an IC card reader for reading the identification information stored in the IC embedded in the identification card, further storing the identification information in the second memory, and the IC card reader The vehicle identification information obtained by decoding the personal identification information stored in the second memory by the decoder when the read identification information matches the identification information stored in the second memory. The vehicle operation management system according to claim 1, configured to transmit to the server together.
The portable communication terminal further includes a biological information reader for reading biological information, further storing the biological information in the second memory, and the biological information read by the biological information reader is stored in the second memory. The personal identification information stored in the second memory is transmitted to the server together with the vehicle identification information decoded by the decoder when the biometric information stored in the second memory matches. The vehicle operation management system according to 1.