JP2020035151A - Driver authentication device and operation management system - Google Patents

Abstract

To perform personal authentication of a driver.SOLUTION: A driver authentication device according to the present embodiment that communicates with a driver's license incorporating an IC chip includes: a reading section that reads data without inputting a password; a storage section for storing a table defining information used for generating identification information, and driver information including the identification information of a plurality of drivers among information included in the data, for each type of the driver's license; a specifying section that refers to the table and specifies a type of the driver's license with which the reading section has performed communication; a generating section that refers to the table, extracts information corresponding to the identified type from the data, and inputs the extracted information to a predetermined function to generate the identification information; and a comparison section that compares the identification information generated by the generating section with the identification information included in the driver information.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a driver authentication device and an operation management system.

  2. Description of the Related Art In recent years, vehicles equipped with a drive recorder or a digital tachograph for recording information related to vehicle operation have been increasing. Also, a technique is known in which a drive recorder and a mobile phone terminal are combined, and the mobile phone terminal transfers the driving status data received from the drive recorder to a server (for example, see Patent Document 1).

  Companies that own commercial vehicles such as taxis, buses, and trucks create operation schedules that show who and when they drove each vehicle, based on dispatch information and reports from drivers, in order to manage operations. The operation schedule and the driving situation data recorded by the drive recorder are stored in association with each other.

  The operation schedule can also be created by performing personal authentication with a vehicle recorder such as a drive recorder when the driver gets on the vehicle. Conventionally, personal identification has been performed by holding an IC employee card over an on-vehicle device or entering a driver number using a numeric keypad. However, making an IC employee ID card was costly. Also, inputting the driver number was troublesome.

  Each driver's license has a built-in IC chip. By reading personal information such as a name from the IC chip, personal authentication can be performed. However, personal information cannot be obtained from the IC chip without inputting a preset password in the IC license. Therefore, when the driver forgets the personal identification number, personal information cannot be read from the IC chip, and personal identification cannot be performed. In addition, inputting the password was troublesome, and there was strong resistance to what a passenger could see.

JP 2010-238214 A

  An object of the present invention is to provide a driver authentication device and an operation management system that can easily perform individual authentication of a driver.

  A driver authentication device according to the present invention communicates with a driver's license having a built-in IC chip and reads data without inputting a personal identification number. A table defining information used for generating identification information, a storage unit storing driver information including identification information of a plurality of drivers, and a storage unit storing the table, and the reading unit performs communication with the reading unit. A specifying unit that specifies the type of the driver's license, and referring to the table, extracts information corresponding to the specified type from the data, and inputs the extracted information to a predetermined function to generate identification information. A generating unit; and a matching unit that matches the identification information generated by the generating unit with the identification information included in the driver information.

  In one aspect of the present invention, an image capturing unit that captures a driver's face in a vehicle equipped with the driver authentication device to generate a face image, a face image of each driver included in the driver information, A face image comparing unit that compares the face image generated by the photographing unit.

  According to one aspect of the present invention, the vehicle further includes a determination unit that determines whether or not the vehicle equipped with the driver authentication device can be driven, wherein the storage unit stores vehicle information including a vehicle rating of the vehicle, and the driver information Includes a driver's license expiration date and a driver's driving qualification, the determination unit refers to the driver information, and the vehicle's driving qualification corresponding to the identification information generated by the generation unit is included in the vehicle information. It is determined whether the driver's license is within the validity period and whether the driver's license is valid or not.

  In one aspect of the present invention, the data read by the reading unit includes an ATQB command received as a response to the REQB command or the WUPB command transmitted by the reading unit at least twice to the driver's license, and application free area information. .

  According to one aspect of the present invention, the information processing apparatus further includes an information acquisition unit that acquires operation history information related to the operation of the vehicle, and a communication unit that transmits the operation history information and identification information of a driver who drives the vehicle.

  An operation management system according to the present invention includes the driver authentication device of the present invention, and a management server that receives the operation history information and the identification information from the driver authentication device and performs operation management of the vehicle. .

  A driver authentication device according to the present invention communicates with a driver's license incorporating an IC chip using the input unit for receiving input of a driver's license password and reads personal information including the driver's license number. A reading unit, a storage unit for storing personal information of a plurality of drivers, and a collation unit for collating the personal information read by the reading unit with the personal information stored in the storage unit. .

  According to the present invention, personal authentication of a driver can be easily performed.

It is a schematic diagram of an operation management system according to an embodiment of the present invention. FIG. 3 is a hardware configuration diagram of a management server. FIG. 4 is a diagram illustrating a data structure of a request response signal. FIG. 9 is a diagram illustrating an example of a data selection table. FIG. 4 is a functional block diagram realized by executing an ID number generation program. 9 is a flowchart illustrating an ID number generation process according to the embodiment. It is a hardware block diagram of a driver authentication device. It is a functional block diagram realized by executing a driver authentication program. 4 is a flowchart illustrating a driver authentication method according to the same embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. The operation management system according to the present embodiment includes a management server 1 and a driver authentication device 2 mounted on a vehicle C. For example, a company that owns a plurality of vehicles C and employs a plurality of drivers is provided. The driver is used when managing the driver who drives each vehicle C and the operation history.

  Each driver has a driver's license with a built-in IC chip. The IC chip stores personal information such as the driver's name, date of birth, address, and license number. In order to read the personal information, it is required to input a password set in advance (at the time of issuing a license).

  Vehicle information and driver information of each vehicle C are registered in the management server 1 in advance. The vehicle information is, for example, vehicle verification description information such as a vehicle classification. The driver information includes the name, date of birth, license number, expiration date of license, type of license, driving qualification, license conditions, face image, and the like for each driver. For example, the person in charge of registration checks the items described in the license of each driver and inputs information using a keyboard or the like. As the face image, image data obtained by photographing the driver with a digital camera may be registered, or the face photo portion of the license may be read by a scanner and registered.

  In this driver information, an ID number (identification information) for personal authentication at the time of driving is assigned to each driver. The management server 1 generates an ID number in advance using information that can be read from the IC chip of the driver's license without inputting a password. The method of generating the ID number will be described later.

  The management server 1 transmits the driver information and the vehicle information of the vehicle C to the driver authentication device 2 of each vehicle C.

  The driver authentication device 2 is installed on, for example, a dashboard or a roof of the vehicle C, and functions as a drive recorder or a digital tachograph for acquiring operation information, a reading unit that reads information from an IC chip, and a photographing operation for photographing a driver's face. Parts. The photographing unit photographs the face of the driver who got into the vehicle C. The driver authentication device 2 compares the feature points between the face image of each driver included in the driver information and the face image photographed by the photographing unit, and detects a matching driver.

  The driver holds the driver's license over the driver authentication device 2 when the vehicle C gets on. The driver authentication device 2 reads information from the IC chip of the driver's license. The information read here is information that can be read without inputting a password.

  The driver authentication device 2 generates an ID number from the information read by the reading unit in the same manner as the management server 1, and checks the ID number with the ID number of the driver whose face image matches. If the ID numbers match, the driver authentication device 2 determines from the driver information of the driver whether the driver's license has not expired, whether the driver's driving qualification corresponds to the class of the vehicle C, and the like. Check and allow operation.

  After the driving is completed, the driver authentication device 2 transmits the operation history information to the server device 1 together with the driver ID number. The server device 1 stores the operation history information.

  Personal information such as name and license number is stored in the IC chip of the driver's license, and personal authentication may be performed using this personal information. However, when reading personal information, it is necessary to input a personal identification number. It is time-consuming because it is necessary. If the driver forgets the password, personal information cannot be read and personal authentication cannot be performed. Also, when a password is entered on the numeric keypad screen of the display, the password may be seen by a fellow passenger.

  On the other hand, in the present embodiment, since the input of the personal identification number is unnecessary, the personal identification of the driver can be easily performed simply by holding the driver's license over the driver authentication device 2 and the operation management can be performed.

  FIG. 2 is a block diagram of the management server 1. The management server 1 includes a CPU (Central Processing Unit) 10, a main memory 11, a communication unit 12, a disk device 13, a reading device 14, and an input device 15. The input device 15 is a mouse, a keyboard, a scanner, or the like.

  The disk device 13 is a storage device such as a hard disk device, and stores a data selection table, an ID number generation program, vehicle information, driver information, operation history information of each vehicle C, and the like.

  The reader 14 acquires data from the driver's license IC chip of each driver by non-contact communication. In the present embodiment, communication between the reading device 14 and the IC chip is based on Type B standardized by ISO / IEC7816 (and ISO / IEC14443).

  When a driver's license, which is a type B PICC (proximity IC card), is passed over the operating magnetic field, the reader 14 transmits a request signal (request command, REQB / WUPB) so that the IC chip responds. Upon receiving the request signal, the IC chip transmits a request response signal (ATQB: Answer To Request, Type B).

  FIG. 3 shows the data structure of the request response signal. The request response signal is 14-byte data with a tag “50” added to the first byte, PUPI in the second to fifth bytes, application data in the sixth to ninth bytes, and application data in the tenth to twelfth bytes. CRC_B is defined in the 13th and 14th bytes of the protocol information.

  PUPI is a pseudo-unique identifier of the PICC, is used to identify the PICC at the time of collision prevention processing, and is a temporarily generated random number or a fixed value.

  The application data is used to tell the reader 14 what application is being written to the PICC. The application data is defined in accordance with the ADC (application data encoding) field of the protocol information described in the next section, and defines whether CRC_B compression encoding or individual encoding is applied. When CRC_B compression encoding is used, the application data includes AFI, CRC_B (AID), and the number of applications.

  AFI is a 1-byte value that defines the field of application. CRC_B (AID) is a 2-byte value indicating the result of CRC_B calculation of the AID in the PICC that matches the AFI described in the REQB / WUPB command. The number of applications is a one-byte value indicating the number of other applications existing in the PICC.

  For example, the first and second bytes of the application data are arbitrary values for each IC maker, and the third byte is an IC maker code defined by ISO / IEC7816-6Amendment1.

  The protocol information defines an allowable bit transmission rate, a maximum frame size, a protocol type, FWI, ADC, and FO. The allowable bit transmission rate is a one-byte value indicating the capability corresponding to the communication speed of the driver's license.

  The maximum frame size is a 4-bit value indicating the maximum frame length that the driver's license can receive. The protocol type is a 4-bit value indicating the protocol type supported by the driver's license.

  FWI (Frame Latency Factor) is a 4-bit value encoded with an integer value to define the frame latency (FWT). The FWT is the maximum time from the end of the frame sent from the reader 14 until the driver's license starts responding.

  ADC (Application Data Encoding) is a 2-bit value indicating the application data encoding supported by the driver's license. FO (frame option) is a 2-bit value indicating a frame option supported by the driver's license.

  CRC_B is a cyclic redundancy check code calculated from all data bits (the number of bits) in the frame.

  In order to determine whether the PUPI included in the request response signal is a random number or a fixed value, the reading device 14 transmits the request signal and receives the request response signal at least twice. If the PUPI included in the plurality of received request response signals has the same value, it can be determined that the value is a fixed value, and if the PUPI is different, it can be determined that the value is a random number.

  Further, the reading device 14 transmits a request signal for acquiring the free area information of the application, and acquires the free area information of the application from the IC chip of the driver's license. The free area information indicates, for example, the date of issuance of the driver's license and the expiration date.

  As described above, the reading device 14 reads the ATQB signal and the free area information of the application, which can be obtained without inputting the password, from the IC chip of the driver's license.

  Some information included in the ATQB signal differs depending on the driver's license depending on the case where there are a plurality of manufacturers that produce the driver's license and the specifications of the IC chip built in the driver's license.

  For example, among the information included in the ATQB signal, PUPI, CRC_B (AID) of application data, FWI, ADC, and FO of protocol information are characteristic information that may differ among driver licenses.

  The driver's license can be classified into several types depending on the manufacturer, the type of the built-in IC chip, and the like, which information is characteristic information. In the present embodiment, the type of the driver's license is specified, and an ID number for identifying the driver using information that is characteristic in the information of the ATQB signal transmitted by the driver's license, free area information of the application, and the like. Generate

  FIG. 4 shows an example of a data selection table stored in the disk device 13. The data selection table shows a combination of information suitable for ID number generation for each type of driver's license. The data selection table is prepared in advance.

  For example, driver's licenses are classified into four types, cards # 1 to # 4, depending on the manufacturer, the type of the built-in IC chip, and the like. In the card # 1, the PUPI and the protocol information of the ATQB signal are characteristic values, and the issuing date and the expiration date of the application free area are suitable for ID number generation.

  In cards # 2 and # 4, the PUPI of the ATQB signal is random, indicating that it is inappropriate for ID number generation.

  The CPU 10 loads the ID number generation program stored in the disk device 13 into the main memory 11 and executes the program, as shown in FIG. 5, so that the response signal acquisition unit 17, the card type identification unit 18, and the ID number The generation unit 19 is realized.

  The response signal acquisition unit 17 acquires information read by the reader 14 from the driver's license. For example, the response signal acquiring unit 17 acquires a request response signal for at least two readings and application free area information.

  The card type specifying unit 18 specifies the card type of the driver's license from which the reading device 14 has read the information, with reference to the data selection table. For example, when the PUPI of the request response signal for two readings is different, the type of the driver's license is card # 2 or # 4. Further, when the protocol information of the request response signal is the data pattern Y, the type of the driver's license is specified as the card # 2.

  The ID number generation unit 19 refers to the data selection table and confirms information used for generating an ID number with the card type specified by the card type specification unit 18. The ID number generation unit 19 extracts information used for ID number generation from the data acquired from the reading device 14 and inputs the information to a hash function to calculate a hash value. This hash value is assigned as the ID number of the driver who owns the driver's license.

  For example, when it is specified that the type of the driver's license is card # 2, a hash function is used for the CRC_B (AID) of the application data of the request response signal, the FWI, ADC, and FO of the protocol information and the application free area information. To generate an ID number.

  FIG. 6 is a flowchart illustrating the ID number generation processing. The reading device 14 of the management server 1 transmits a request signal to the driver's license (Step S101) and receives a request response signal (Step S102). The acquisition of the request response signal is performed one more time (steps S103 and S104).

  Subsequently, the reading device 14 transmits a request signal for application free area information to the driver's license (step S105), and receives the application free area information (step S106).

  The card type specifying unit 18 of the management server 1 specifies the card type of the driver's license using the request response signal and the application free area information (Step S107). The ID number generation unit 19 of the management server 1 refers to the data selection table, extracts information to be used for ID number generation, inputs the information to the hash function, and generates an ID number for identifying the driver (Step S108). .

  The person in charge of registration of the company holds the driver's license submitted by each driver over the reader 14 to generate an ID number, and inputs the information on the driver's license to the management server 1 using a keyboard or the like. In addition, a face image obtained by photographing the driver with a digital camera or a face image obtained by scanning a driver's license with a scanner is input to the management server 1. Then, the driver information in which the ID number, the item on the ticket surface, and the face image are associated with each other is registered. After registering the driver information, the driver's license will be returned to the driver.

  The management server 1 uses the communication unit 12 to communicate with the driver authentication device 2 mounted on each vehicle C, transmits driver information and a data selection table, and receives operation history information. The operation history information is stored in the disk device 13 in association with the ID number of the driver who has driven the vehicle.

  FIG. 7 is a block diagram of the driver authentication device 2. The driver authentication device 2 includes a CPU 20, a storage unit 21, a communication unit 22 having a wireless communication function, a reading unit 23 such as a card reader, a photographing unit 24 such as a digital camera, and an information acquisition unit 25.

  The storage unit 21 stores driver information, vehicle information, and a data selection table received from the management server 1 using the communication unit 22. The operation history information acquired by the information acquisition unit 25 is stored in the storage unit 21.

  The information acquisition unit 25 acquires operation history information on the operation of the vehicle C. For example, the information acquisition unit 25 outputs a signal output by an ECU (Electronic Control Unit) that controls an engine, a signal output by a brake pedal unit, and the like. Information indicating the state of each unit, information detected by the acceleration detection unit and the position detection unit, and images of at least one of the outside and inside of the vehicle C captured by the built-in or externally mounted shooting unit 24 are acquired.

  When the CPU 20 executes the operation management program stored in the storage unit 21, as shown in FIG. 8, the information update unit 200, the face image comparison unit 201, the response signal acquisition unit 202, the card type identification unit 203, An ID number generation unit 204, an ID number collation unit 205, a determination unit 206, and an operation history information transmission unit 207 are realized.

  The information updating unit 200 receives the latest driver information from the management server 1 and updates the driver information in the storage unit 21.

  The face image comparison unit 201 compares a face image of the driver sitting in the driver's seat of the vehicle C by the imaging unit 24 with a face image included in the driver information, and specifies a matching driver.

  The functions of the response signal acquisition unit 202, the card type identification unit 203, and the ID number generation unit 204 are the same as the functions of the response signal acquisition unit 17, card type identification unit 18, and ID number generation unit 19 of the management server 1 described above. Yes, the reading unit 23 generates an ID number using data read from the driver's license held by the driver.

  The ID number collating unit 205 collates the ID number registered in the driver information of the driver whose face image matches with the ID number generated by the ID number generating unit 204.

  The determination unit 206 determines whether the driver can drive the vehicle C using the driver information and the vehicle information. For example, the determination unit 206 determines whether the driver can drive the vehicle by checking whether the vehicle is of a size that can be driven by the driver, whether the driver's license has expired, or the like.

  The operation history information transmission unit 207 uses the communication unit 22 to transmit the operation history information to the management server 1 together with the driver ID number.

  FIG. 9 is a flowchart illustrating an authentication method when the driver gets into the vehicle C. When the driver sits in the driver's seat, the photographing unit 24 photographs the driver and generates a face image (step S1).

  The face image comparison unit 201 compares the face image generated by the imaging unit 24 with the face image included in the driver information stored in the storage unit 21 (Step S2). If the face images match and it is confirmed that the driver is a registered driver (step S3_Yes), the reading unit 23 starts. When the driver holds the driver's license over the reader 23, the reader 23 reads data from the IC chip of the driver's license (step S4) and generates an ID number (step S5). The data reading and the generation of the ID number are the same as steps S101 to S108 in the flowchart shown in FIG.

  The ID number registered in the driver information of the driver whose face image matches in step S3 is compared with the ID number generated in step S5. If the ID numbers match (step S6_Yes), it is determined whether the driver can drive the vehicle. When driving is possible (Step S7_Yes), the driver starts operation (Step S8).

  If the face images and the ID numbers do not match (step S2_No, step S6_No), or if it is determined that the vehicle cannot be driven (step S7_No), an authentication error is notified by voice or screen display (step S9).

  After the operation is completed, when the driver presses the end button, detects that the engine of the vehicle has run out, or confirms that the driver gets off from the image captured by the imaging unit 24, the operation history information and the driver ID number Is transmitted to the management server 1.

  As described above, according to the present embodiment, the driver's ID number can be generated simply by holding the driver's license without entering a personal identification number, personal identification can be easily performed, and operation management can be performed.

  In the above-described embodiment, the driver authentication method in which the input of the password is not required has been described. However, the input of the password may be performed. In this case, when registering the driver information, the driver is requested to input a personal identification number, and the driver information is created and registered using the personal information such as the license number read from the IC chip of the driver's license. For example, the license number is an ID number for identifying the driver. Further, face image data is stored in the IC chip, and this face image data is used for driver information.

  When the driver gets on the vehicle C, the photographing unit 24 photographs the driver and compares the driver with the face image of each driver included in the driver information in order. The driver holds the driver's license over the driver authentication device 2 (or puts the driver's license on a predetermined place) and inputs a password. The driver authentication device 2 reads personal information such as a license number from the IC chip of the driver's license and checks the personal information included in the driver information of the driver whose face image matches.

  Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying constituent elements in an implementation stage without departing from the scope of the invention. Various inventions can be formed by appropriately combining a plurality of components disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiment. Further, components of different embodiments may be appropriately combined.

1 management server 2 driver authentication device

Claims (7)

A reading unit that communicates with a driver's license containing an IC chip and reads data without inputting a password;
For each type of driver's license, of the information included in the data, a table that defines information used for generating identification information, and a storage unit that stores driver information including identification information of a plurality of drivers,
A specifying unit that refers to the table and specifies a type of the driver's license with which the reading unit has performed communication;
A generating unit that refers to the table, extracts information corresponding to the identified type from the data, and inputs the extracted information to a predetermined function to generate identification information;
The identification information generated by the generation unit, a matching unit that matches the identification information included in the driver information,
A driver authentication device comprising: A photographing unit for photographing the face of a driver who has boarded a vehicle equipped with the driver authentication device and generating a face image,
A face image of each driver included in the driver information, and a face image comparison unit that compares the face image generated by the imaging unit;
The driver authentication device according to claim 1, further comprising: The apparatus further includes a determination unit that determines whether or not the vehicle equipped with the driver authentication device can be driven,
The storage unit stores vehicle information including a vehicle rating of the vehicle,
The driver information includes a driver's license expiration date and a driver's driving qualification,
The determination unit refers to the driver information, determines whether the driver's driving qualification corresponding to the identification information generated by the generation unit corresponds to the vehicle classification included in the vehicle information, and The driver authentication device according to claim 1, wherein it is determined whether or not the driver's license has expired.   The data read by the reading unit includes an ATQB command received as a response to the REQB command or the WUPB command transmitted by the reading unit at least twice to the driver's license, and application free area information. The driver authentication device according to any one of claims 1 to 3. An information acquisition unit for acquiring operation history information on the operation of the vehicle,
A communication unit that transmits the operation history information and identification information of a driver who drives the vehicle,
The driver authentication device according to any one of claims 1 to 4, further comprising: A driver authentication device according to claim 5,
A management server that receives the operation history information and the identification information from the driver authentication device and performs operation management of the vehicle;
Operation management system equipped with. An input unit for receiving an input of a driver's license password,
A reading unit that communicates with a driver's license containing a built-in IC chip using the password and reads personal information including the license number;
A storage unit for storing personal information of a plurality of drivers;
Personal information read by the reading unit, a collating unit for collating personal information stored in the storage unit,
A driver authentication device comprising:

Images