CN110712623B

CN110712623B - Vehicle-mounted device, operation management system, and driver confirmation method

Info

Publication number: CN110712623B
Application number: CN201910311995.6A
Authority: CN
Inventors: 佐藤尚良; 竹中美加
Original assignee: Omron Corp
Current assignee: Omron Corp
Priority date: 2018-07-11
Filing date: 2019-04-18
Publication date: 2022-03-25
Anticipated expiration: 2039-04-18
Also published as: JP2020009302A; CN110712623A; JP7087747B2

Abstract

A vehicle-mounted device, an operation management system and a driver confirmation method, wherein the vehicle-mounted device can confirm whether each driver driving a vehicle is a correct driver after face authentication without performing complicated face authentication processing by using face image data; the operation management device comprises an operation management table storage part, wherein an operation management table which registers the identification information of each driver and the operation information of the vehicle driven by each driver is stored, the vehicle-mounted machine comprises a 1 st identification information acquisition part and an identification information transmission part, and the 1 st identification information acquisition part acquires the identification information of the driver authenticated by the face authentication part of the portable terminal from the portable terminal carried by the driver on the vehicle; the identification information transmitting unit transmits the acquired identification information of the driver and the identification information of the in-vehicle device to the operation management apparatus so as to determine whether or not the driver riding in the vehicle is the correct driver registered in the operation management table.

Description

Vehicle-mounted device, operation management system, and driver confirmation method

Technical Field

The invention relates to a vehicle-mounted device, an operation management system, and a driver confirmation method.

Background

Patent document 1 describes an in-vehicle monitoring device configured to store face image data of a driver in a storage means in advance, compare the face image data of an entering person captured by a camera module with a face image stored in a storage means when it is detected that a person enters a vehicle during parking, and permit an engine of the vehicle to be operated when the comparison result matches, that is, when it is determined that the entering person is a registered person.

The in-vehicle monitoring device described in patent document 1 is configured to store face image data of a driver in a storage means in advance. When such an in-vehicle monitoring device is mounted on a vehicle owned by an individual, since the authorized driver is limited, it is possible to deal with a case where the face image data is stored in the storage means in advance even with a small capacity.

However, when such an in-vehicle monitoring device is mounted on, for example, an all-vehicle such as a company, in other words, a vehicle assumed to be driven by a plurality of different drivers, in order to determine whether or not each driver riding the vehicle is a registered person, face image data of all drivers who are likely to drive the vehicle needs to be stored in advance in a storage means of the monitoring device in the vehicle. In this case, a problem arises in that the in-vehicle monitoring device must use a large-capacity storage means.

Patent document 1: japanese patent No. 3797237

Disclosure of Invention

The present invention has been made in view of the above-described problems, and it is an object of the present invention to provide an in-vehicle device that can confirm whether each driver driving a vehicle is a correct driver who has undergone face authentication without storing face image data of all drivers who are likely to drive the vehicle in advance in the in-vehicle device, and without performing a complicated face confirmation process using the face image data in the in-vehicle device, an operation management apparatus that manages operation of a vehicle on which the in-vehicle device is mounted, an operation management system including the same, and a driver confirmation method.

In order to achieve the above object, a vehicle-mounted device (1) according to the present invention is configured so that the vehicle-mounted device (1) and an operation management device are communicable, wherein the operation management device includes an operation management table storage unit configured to store an operation management table in which identification information of each driver and operation information of a vehicle driven by each driver are registered in association with each other;

the vehicle-mounted device includes:

a 1 st identification information acquisition unit configured to acquire, from a portable terminal carried by a driver who gets on the vehicle, identification information of the driver authenticated by a face authentication unit of the portable terminal;

an identification information transmitting unit configured to transmit the identification information of the driver and the identification information of the in-vehicle device acquired by the 1 st identification information acquiring unit to the operation management device so as to determine whether or not the driver riding the vehicle is a correct driver registered in the operation management table.

According to the in-vehicle device (1), the 1 st identification information acquisition unit acquires, from a portable terminal carried by a driver riding in the vehicle, identification information of the driver authenticated by a face authentication unit of the portable terminal. In this way, it is not necessary to store face image data of all drivers who may be driving the vehicle in the in-vehicle device in advance, in other words, it is not necessary to provide a large-capacity storage unit for storing face image data of all drivers in advance. In addition, the in-vehicle device can acquire the driver's identification information subjected to face authentication without performing a complicated face authentication process.

The identification information transmitting unit transmits the identification information of the driver and the identification information of the in-vehicle device to the operation management device. Thus, the operation management device can determine whether or not each driver driving the vehicle is a correct driver registered in the operation management table, that is, a correct driver subjected to face authentication, without performing a complicated face authentication process using face image data on the vehicle-mounted device.

The in-vehicle device (2) according to the present invention is characterized in that the in-vehicle device (1) includes a 1 st authentication disable information acquisition unit and a 1 st authentication disable information transmission unit, wherein the 1 st authentication disable information acquisition unit is configured to acquire, from a portable terminal carried by the driver riding on the vehicle, authentication disable information indicating that the face authentication unit of the portable terminal fails to authenticate; the 1 st authentication disabled information transmitting unit is configured to transmit the driver's authentication disabled information acquired by the 1 st authentication disabled information acquiring unit and the identification information of the in-vehicle device to the operation management device, and to record, in the operation management table, information that the driver who gets on the vehicle is a driver whose face authentication is disabled.

According to the in-vehicle device (2), the authentication-disabled information that the face authentication unit of the portable terminal fails to authenticate is acquired from the portable terminal carried by the driver riding in the vehicle. This makes it possible to acquire authentication disabling information indicating that face authentication has been disabled, without storing face image data of all drivers who may be driving the vehicle in the in-vehicle device in advance, in other words, without performing a complicated face authentication process in the in-vehicle device.

Further, since the authentication disable information and the identification information of the in-vehicle device acquired by the portable terminal carried by the driver are transmitted to the operation management apparatus, it is possible to record the information that the driver riding on the vehicle is a driver whose face authentication is disabled in the operation management table.

The in-vehicle device (3) according to the present invention is characterized in that the in-vehicle device (1) or (2) includes a determination information acquisition unit configured to acquire, from the operation management apparatus, determination information indicating whether or not the driver riding the vehicle is an accurate driver registered in the operation management table.

According to the in-vehicle device (3), the determination information acquisition unit can acquire, from the operation management device, determination information indicating whether or not the driver riding the vehicle is an accurate driver registered in the operation management table. Therefore, the in-vehicle device can confirm whether or not each driver driving the vehicle is a correct driver subjected to face authentication based on the determination information without performing a complicated face authentication process using the face image data, and the load of the confirmation process on the in-vehicle device can be reduced.

The in-vehicle device (4) according to the present invention is characterized in that the in-vehicle device (3) includes a processing unit configured to perform a predetermined warning process or a predetermined antitheft process when determination information indicating that the driver riding the vehicle is not an accurate driver registered in the operation management table is acquired from the determination information acquisition unit.

According to the in-vehicle device (4), when the determination information acquisition unit acquires the determination information indicating that the driver riding on the vehicle is not the correct driver registered in the operation management table, the processing unit performs a designated warning process or a designated theft prevention process. This makes it possible to warn the driver and prevent the vehicle from being stolen.

Further, an operation management device (1) according to the present invention is an operation management device that manages operations of vehicles each having any one of the in-vehicle devices (1) to (4) mounted thereon, and the operation management device (1) includes an operation management table storage unit, a 2 nd identification information acquisition unit, and a driver determination unit; wherein

The operation management table storage unit is configured to store an operation management table in which identification information of drivers who drive the respective vehicles and operation information of vehicles driven by the respective drivers are registered correspondingly;

a 2 nd identification information acquisition unit configured to acquire identification information of the driver and identification information of the in-vehicle device transmitted from the in-vehicle device;

the driver determination unit compares the driver identification information acquired by the 2 nd identification information acquisition unit and the identification information of the in-vehicle device with the operation management table, and determines whether or not the driver riding the vehicle is a correct driver registered in the operation management table

According to the operation management device (1), the driver identification information and the vehicle-mounted device identification information are acquired from the vehicle-mounted device, the acquired driver identification information and the vehicle-mounted device identification information are compared with the operation management table, and whether or not the driver riding the vehicle is a correct driver registered in the operation management table is determined.

Therefore, by executing the determination in the operation management device as to whether or not the driver riding on the vehicle is the driver registered in the operation management table, the processing load on the in-vehicle device can be reduced.

Further, the operation management device (2) according to the present invention is characterized in that the operation management device (1) further includes a determination information recording unit that records determination information on whether or not the driver determined by the driver determination unit is an accurate driver in the operation management table.

According to the operation management device (2), the determination information recording unit records the determination information as to whether or not the driver determined by the driver determining unit is the correct driver in the operation management table. It is possible to centrally manage the determination information whether or not the driver riding the vehicle is the correct driver registered in the operation management table.

Further, the operation management device (3) according to the present invention is characterized in that the operation management device (1) or (2) includes a determination information transmitting unit configured to transmit determination information indicating whether or not the driver determination unit determines that the driver is the correct driver to the in-vehicle device or an end device of a manager who manages the vehicles.

According to the operation management device (3), the determination information determined by the driver determination unit is transmitted to the in-vehicle device or the terminal device of the administrator by the determination information transmission unit.

For example, when the driver determination unit determines that the driver riding the vehicle (in other words, the driver authenticated by the face authentication unit of the portable terminal) is not the correct driver registered in the operation management table, the determination information indicating that the driver is not the correct driver is transmitted to the in-vehicle device or the terminal device of the administrator.

Further, when the driver determination unit determines that the driver riding the vehicle is the correct driver registered in the operation management table, the determination information indicating that the driver is the correct driver is transmitted to the in-vehicle device or the terminal device of the administrator.

Therefore, the determination information can be acquired without performing a complicated determination process on the in-vehicle device or the terminal device of the administrator. In addition, a predetermined process can be executed in accordance with the content of the acquired determination information.

The operation management device (4) according to the present invention is characterized in that any one of the operation management devices (1) to (3) includes a 2 nd authentication disable information acquiring unit that acquires authentication disable information that the face authentication unit of the portable terminal fails to authenticate and identification information of the in-vehicle device transmitted from the in-vehicle device,

and an authentication disable information recording unit that records, in the operation management table, information that the driver who gets on the vehicle is a driver whose face cannot be authenticated, based on the authentication disable information acquired by the 2 nd authentication disable information acquiring unit and the identification information of the in-vehicle device.

According to the operation management device (4), the authentication disabling information that the face authentication unit at the portable terminal fails to authenticate and the identification information of the in-vehicle device are acquired from the in-vehicle device, and the information that the driver riding the vehicle is a driver whose face authentication is disabled is recorded in the operation management table based on the acquired authentication disabling information and the identification information of the in-vehicle device.

It is possible to centrally manage information that the driver riding the vehicle is a driver whose face authentication is impossible through the operation management table.

The operation management device (5) according to the present invention is characterized in that the operation management device (4) includes a 2 nd authentication disable information transmitting unit configured to transmit information indicating that the driver on whom the vehicle is riding is a face-authenticatable driver to the in-vehicle device or a terminal device of a manager managing the vehicle, when the authentication disable information recording unit records information indicating that the driver is a face-authenticatable driver in the operation management table.

According to the above-described operation management device (5), in a case where information that the driver riding the vehicle is a driver whose face authentication is not possible is recorded in the operation management table, information showing that the driver is a driver whose face authentication is not possible is transmitted to the in-vehicle device or a terminal device of an administrator managing the vehicle. Therefore, the terminal device of the in-vehicle device or the administrator can notify the driver or the administrator of the driver or the like who cannot perform the face authentication.

The operation management system according to the present invention is characterized by comprising any one of the in-vehicle devices (1) to (4) and any one of the operation management devices (1) to (5).

According to the operation management system, it is possible to realize a system for confirming whether or not each driver driving the vehicle is a correct driver who has undergone face authentication without storing face image data of all drivers who are likely to drive the vehicle in the in-vehicle device in advance, and without performing a complicated face authentication process using the face image data in the in-vehicle device.

A driver confirmation method according to the present invention is a driver confirmation method performed between an operation management device and a vehicle-mounted device configured to be communicable with the operation management device, wherein the operation management device includes an operation management table storage unit configured to store an operation management table in which identification information of each driver and operation information of a vehicle driven by each driver are registered in association with each other;

the in-vehicle device includes a 1 st identification information acquisition step of acquiring, from a portable terminal carried by a driver riding in the vehicle, identification information of the driver authenticated by a face authentication unit of the portable terminal, and an identification information transmission step of transmitting the identification information of the driver acquired in the 1 st identification information acquisition step and the identification information of the in-vehicle device to the operation management apparatus;

the operation management device includes a 2 nd identification information acquisition step of acquiring identification information of the driver and identification information of the in-vehicle device transmitted from the in-vehicle device; and a driver determination step of comparing the driver identification information and the in-vehicle device identification information acquired in the 2 nd identification information acquisition step with the operation management table, and determining whether or not the driver riding the vehicle is a correct driver registered in the operation management table.

According to the driver confirmation method, the identification information of the driver having undergone face authentication can be acquired without storing face image data of all drivers who are likely to drive the vehicle in the in-vehicle device in advance, and without performing a complicated face authentication process using the face image data in the in-vehicle device.

In addition, each driver driving the vehicle can determine whether the driver is a correct driver registered in the operation management table, that is, whether the driver is a correct driver subjected to face authentication, in the operation management device, and can confirm whether each driver driving the vehicle is a correct driver subjected to face authentication without performing a complicated face authentication process using face image data in the in-vehicle device.

Drawings

Fig. 1 is a schematic diagram showing a configuration example of an operation management system according to an embodiment.

Fig. 2 is a block diagram showing an example of a hardware configuration of an in-vehicle device used in the operation management system according to the embodiment.

Fig. 3 is a block diagram showing an example of a hardware configuration of a server device used in the operation management system according to the embodiment.

Fig. 4 is a diagram showing an example of the configuration of the operation management table stored in the operation management table storage unit.

Fig. 5 is a block diagram showing an example of a functional configuration of an in-vehicle device used in the operation management system according to the embodiment.

Fig. 6 is a block diagram showing an example of a functional configuration of a server device used in the operation management system according to the embodiment.

Fig. 7 is a flowchart showing processing operations performed by a smartphone used in the operation management system according to the embodiment.

Fig. 8 is a flowchart showing a processing operation performed by the in-vehicle device used in the operation management system according to the embodiment.

Fig. 9 is a flowchart showing a processing operation performed by the server device used in the operation management system according to the embodiment.

Fig. 10 is a flowchart of a processing operation performed by the in-vehicle device used in the operation management system according to the embodiment.

Description of the symbols

1 operation management system

2 vehicle

3 driver

4 communication network

10 vehicle-mounted machine

11 platform part

12 acceleration sensor

13 angular velocity sensor

14 GPS receiving part

15 communication part

16 notification unit

17 storage part

18 external interface (external I/F)

19 control part

19a CPU

19b RAM

19c ROM

191 the 1 st identification information acquisition unit

192 identification information transmitting unit

193 decision information acquiring unit

194 processing section

195 st authentication disabled information acquiring unit

196 authentication disabled information transmitting part 1

20 driver monitoring part

21 driver camera

22 image analysis unit

23 interface (I/F)

30 running recording part

31 vehicle exterior camera

32 in-vehicle camera

40 Server device (operation management device)

41 communication unit

50 server computer

51 central processing unit

511 nd 2 nd identification information acquisition unit

512 driver determination unit

513 judging information recording part

514 decision information transmitting unit

515 nd authentication disabled information acquiring unit

516 authentication non-information recording part

517 No. 2 authentication disabled information transmitting part

52 Main reservoir

53 control program

70 holding unit

71 operation management table storage unit

71a operation management table

80 end of the cause

90 Intelligent mobile phone (Portable terminal)

91 Camera part

92 face authentication unit

93 a communication unit.

Detailed Description

Embodiments of an in-vehicle device, an operation management system including the same, and a driver confirmation method according to the present invention will be described below with reference to the drawings.

The in-vehicle device and the operation management device according to the present invention can perform operation management such as the operation status of the vehicle and the traffic status of the driver managed by the service provider, and can be widely applied to a system for supporting appropriate operation management of the vehicle and the driver managed by the service provider, and the like.

[ example of System construction ]

The operation management system 1 is a system for managing operations of the vehicle 2, the traffic situation of the driver 3 riding in the vehicle 2, and the like, and includes at least one in-vehicle device 10 mounted on the vehicle 2, and at least one server device 40 that acquires data from each in-vehicle device 10 and performs a designation process. The server device 40 is an example of the "operation management device" of the present invention.

The vehicle 2 mounted on the in-vehicle device 10 is not particularly limited. In the present embodiment, any vehicle managed by an operator who operates various businesses can be used. For example, a truck managed by a transport carrier, a bus managed by a bus carrier, a taxi managed by a taxi operator, a shared vehicle managed by a shared vehicle operator, a taxi managed by a taxi operator, a car used by a company owned by a company, or a car used by a company leased from a car leasing operator may be used as an object.

The in-vehicle device 10 and the server device 40 are configured to be communicable with each other via the communication network 4. The communication Network 4 may include a wireless communication Network such as a mobile telephone Network (3G/4G) including a base station and a wireless Local Area Network (Local Area Network), and may also include a wired communication Network such as a public telephone Network, and a telecommunication loop such as the internet or a private Network. The server apparatus 40 includes a communication unit 41, a server computer 50, and a storage unit 70.

The end device 80 of the operator who manages the vehicle 2 (hereinafter referred to as operator end) is configured to be communicable with the server device 40 via the communication network 4. The business person terminal 80 may be a personal computer having a communication function, or may be a portable terminal such as a mobile phone, a smartphone, or a tablet terminal. The operator terminal 80 may be configured to be communicable with the in-vehicle device 10 via the communication network 4.

In addition, the driver 3 carries, for example, a smartphone 90 as a portable terminal. The smartphone 90 carried by the driver 3 is equipped with a communication module for short-range wireless communication such as Wi-Fi or Bluetooth (registered trademark) or a communication module for wired communication in addition to a communication module capable of communicating voice and data via a mobile phone network or the like, and is configured to communicate with the in-vehicle device 10 wirelessly or by wire. The smartphone 90 is equipped with a camera, and also with face authentication application software (hereinafter also referred to as a face authentication application) for performing face authentication processing using a face image captured by the camera.

The storage unit 70 of the server device 40 stores systematically-managed identification information (hereinafter, referred to as a driver ID) of each driver 3 and an operation management table registered in association with operation information of the vehicle 2 driven by each driver 3.

An outline of a driver confirmation method performed by the operation management system 1 will be described.

When the driver 3 gets on the vehicle 2, the face authentication application of the smartphone 90 is started first. When the face authentication application is started, the face of the driver 3 is photographed by the smartphone 90, and face authentication processing is performed.

The face authentication process is, for example, to compare the captured face image data of the driver 3 with face image data registered in advance, and to determine whether the face authentication is successful or not by whether or not the degree of similarity of the face image data is a predetermined threshold value. If the face authentication process of the smartphone 90 is successful, the smartphone 90 transmits the driver ID of the driver 3 associated with the face image data registered in advance to the in-vehicle device 10 by wireless communication.

The in-vehicle device 10 acquires the driver ID of the driver 3 who has been face-authenticated by the smartphone 90 (i.e., face authentication has succeeded) from the smartphone 90 carried by the driver 3 who gets on the vehicle 2, and transmits the acquired driver ID and identification information of the in-vehicle device 10 (hereinafter referred to as an in-vehicle device ID) to the server device 40.

On the other hand, the server device 40 acquires the driver ID and the in-vehicle device ID transmitted from the in-vehicle device 10, compares the acquired driver ID and the in-vehicle device ID with the operation management table, and determines whether or not the driver 3 on the vehicle 2 is the correct driver registered in the operation management table. Then, the server device 40 transmits the determination information indicating whether or not the driver is the correct driver to at least one of the in-vehicle device 10 and the dealer terminal 80.

When the in-vehicle device 10 or the dealer terminal 80 acquires the determination information from the server device 40, a predetermined process such as a process of notifying the determination information is executed based on the determination information.

According to the driver confirmation method implemented by the operation management system 1, by using the face authentication application of the smartphone 90 carried by the driver 3, it is not necessary to store the face image data of all drivers who may drive the vehicle 2 in the in-vehicle device 10 in advance, and a large-capacity storage unit is not required in the in-vehicle device 10. Further, the in-vehicle device 10 can confirm whether or not each driver 3 driving the vehicle 2 is a correct driver subjected to face authentication without performing a complicated face authentication process using face image data.

[ hardware constitution ]

Fig. 2 is a block diagram showing an example of a hardware configuration of the in-vehicle device 10 used in the operation management system 1 according to the embodiment.

The in-vehicle device 10 includes a platform unit 11 and a driver monitor unit 20. The in-vehicle device 10 is connected to a travel recording unit 30.

The platform unit 11 is equipped with an acceleration sensor 12 for measuring the acceleration of the vehicle 2, an angular velocity sensor 13 for detecting the angular velocity of the vehicle 2, and a GPS (Global Positioning System) receiving unit 14 for detecting the position of the vehicle 2. The platform unit 11 is provided with a communication unit 15 for performing communication processing with an external device via the communication network 4, a notification unit 16 for outputting a warning sound such as a beep sound or a sound such as warning information, a storage unit 17, and an external interface (external I/F) 18. Further, the platform section 11 is provided with a control section 19 for controlling the processing operation of each section.

The acceleration sensor 12 is a 3-axis acceleration sensor that measures acceleration in three directions of XYZ axes. The 3-axis acceleration sensor may be a capacitance type acceleration sensor, or a semiconductor type acceleration sensor such as a varistor type acceleration sensor. The acceleration sensor 12 may be a 2-axis or 1-axis acceleration sensor. The acceleration data measured by the acceleration sensor 12 may be stored in the RAM19b of the control unit 19 in association with the detection time (i.e., in time series).

The angular velocity sensor 13 is a sensor capable of detecting angular velocity corresponding to at least rotation about a vertical axis (yaw direction), that is, angular velocity data corresponding to rotation in the left-right direction (turning) of the vehicle 2, and is configured by, for example, a gyro sensor (also referred to as a yaw rate sensor). The angular velocity sensor 13 may be a 1-axis gyro sensor that rotates about a vertical axis, a 2-axis gyro sensor that can detect an angular velocity of rotation about a horizontal axis in the left-right direction (pitch direction), or a 3-axis gyro sensor that can detect an angular velocity about a horizontal axis in the front-back direction (roll direction).

The direction of detection of the angular velocity around the vertical axis of the angular velocity sensor 13 may be set such that the clockwise direction is a positive direction and the counterclockwise direction is a negative direction. In this case, the vehicle 2 detects positive angular velocity data if turning in the right direction, and negative angular velocity data if turning in the left direction. The angular velocity sensor 13 detects the angular velocity at a predetermined cycle (for example, a cycle of several tens of ms), and the detected angular velocity data may be stored in the RAM19b of the control unit 19 in association with the detection time, for example. In addition, the acceleration sensor 12 and the angular velocity sensor 13 may also use inertial sensors that enclose these in one package.

The GPS receiving unit 14 receives a GPS signal from an artificial satellite at a predetermined cycle (for example, every second) via an antenna 14a, and detects position data (latitude and longitude) of the current location. The position data detected by the GPS receiving unit 14 is stored in the RAM19b of the control unit 19 in association with the detection time, for example.

The communication unit 15 includes a communication module for performing data output processing and the like to the server device 40 via the communication network 4, and a communication module for performing wireless or wired communication with the smartphone 90.

The storage unit 17 is configured by, for example, a storage device such as a memory card that can be attached and detached, or one or more storage devices such as a Hard Disk Drive (HDD) and a Solid State Drive (SSD). The storage unit 17 may be configured to store various kinds of detection data acquired from the acceleration sensor 12, the angular velocity sensor 13, the GPS receiving unit 14, the driver monitoring unit 20, or the travel recording unit 30 in time series.

The external I/F18 includes, in addition to the travel recording unit 30, an interface circuit, a connection interface, and the like for receiving data and signals from and to an on-vehicle device such as an engine starter, not shown.

The control Unit 19 is constituted by a microcomputer including a CPU (Central Processing Unit)19a, a RAM (Random Access Memory)19b, and a ROM (Read Only Memory)19c, and the control Unit 19 is constituted by reading various data stored in the RAM19b or the storage Unit 17 as necessary in addition to the program stored in the ROM19c, and executing a predetermined program.

For example, the control unit 19 performs a process of acquiring the designated information from the smartphone 90, a process of transmitting the designated information to the server device 40, a process of acquiring the designated information from the server device 40, and the like. The details of the processing operations performed between the control unit 19 and the smartphone 90 and the server device 40 will be described later.

The control unit 19 may also perform processing for storing various types of detection data acquired from the acceleration sensor 12, the angular velocity sensor 13, the GPS receiving unit 14, the driver monitoring unit 20, or the travel recording unit 30 in the RAM19b or the storage unit 17.

The driver monitor unit 20 includes a driver camera 21, an image analysis unit 22, and an interface (I/F) 23.

The driver camera 21 includes, for example, a lens unit, an imaging element unit, a light irradiation unit, and a camera control unit for controlling these components, which are not shown.

The image analysis unit 22 is configured to include an image processor or the like, and performs processing for detecting the behavior of the face of the driver 3 (for example, the face orientation, the line-of-sight direction, the degree of eye openness, and the like) from the image captured by the driver camera 21. The data showing the facial movement of the driver 3 detected by the image analysis unit 22, the image data, the shooting date and time data, and the like are transmitted to the platform unit 11 via the interface (I/F)23 and stored in the RAM19b or the storage unit 17 of the platform unit 11.

The external I/F18 of the platform unit 11 may be connected to an in-vehicle device such as an engine starter, not shown, in addition to the travel recording unit 30. The travel recording unit 30 includes an exterior camera 31 and an interior camera 32.

The vehicle exterior camera 31 is a camera that captures an image of the front of the vehicle 2, and the vehicle interior camera 32 is a camera that captures an image of the interior of the vehicle 2. The vehicle exterior camera 31 and the vehicle interior camera 32 may be configured by, for example, a visible light camera, or may be configured by a near infrared camera.

The vehicle-exterior camera 31 and the vehicle-interior camera 32 capture images with a predetermined frame lag (for example, several tens of frames per second), and the images captured by the vehicle-exterior camera 31 and the vehicle-interior camera 32 and data such as the date and time of capture are transmitted to the platform unit 11 and stored in the RAM19b or the storage unit 17 of the platform unit 11. The travel recording unit 30 may be configured to include only the vehicle exterior camera 31.

The in-vehicle device 10 may have a small-sized configuration in which the platform unit 11 and the driver monitor unit 20 are housed in one housing. In this case, the installation position of the in-vehicle device 10 in the vehicle is not particularly limited as long as the driver camera 21 can capture at least the view of the driver including the face. For example, the in-vehicle device 10 may be provided at a position near the center of the dashboard of the vehicle 2, or may be provided at a steering wheel column portion, near the dashboard, near the rear view mirror, or at an a-pillar portion. The driver monitor unit 20 may be configured integrally with the platform unit 11, or may be configured separately from the platform unit 11.

Fig. 3 is a block diagram showing an example of a hardware configuration of the server device 40 used in the operation management system 1 according to the embodiment.

The server apparatus 40 includes a communication unit 41, a server computer 50, and a storage unit 70, which are connected by a communication path 42.

The communication unit 41 is configured to include a communication device for transmitting and receiving various data and signals between the in-vehicle device 10, the operator terminal 80, and the like via the communication network 4.

The server computer 50 includes a central processing unit 51 including one or more CPUs, and a main memory 52 storing a control program 53. The central processing unit 51 executes various processes in accordance with a control program 53 in the main memory 52.

The storage unit 70 is configured by one or more large-capacity storage devices such as a hard disk drive and a solid-state hard disk drive, and includes an operation management table storage unit 71.

The operation management table storage unit 71 stores an operation management table.

Fig. 4 is a diagram showing an example of the configuration of the operation management table 71a stored in the operation management table storage unit 71.

The operation management table 71a is associated with driver IDs of the drivers 3 managed by the operation management system 1 and operation schedule information of the vehicles 2 driven by the drivers 3. The operation schedule information includes information such as the in-vehicle device ID of the in-vehicle device 10 mounted on each vehicle 2, the operation date, and the scheduled ride time (start time — end time). Further, the operation management table 71a records, as driver confirmation data, information indicating that the comparison with the operation management table 71a is matched or not matched, and authentication disabling information indicating that the smartphone 90 has not obtained face authentication.

The driver ID is not particularly limited as long as it is information added to identify the driver 3, and the data format and the like are not particularly limited. The driver ID may be identification information or the like read by a two-dimensional code or the like. The in-vehicle device ID is not particularly limited as long as it is information added to identify the in-vehicle device 10 (in other words, the vehicle 2).

The storage unit 70 may include a detection data accumulation unit and a driving evaluation data storage unit, which are not shown.

The detection data accumulation unit accumulates, for example, various kinds of detection data acquired from the in-vehicle devices 10 of the respective vehicles 2 in a time series in association with the in-vehicle device IDs of the respective in-vehicle devices 10.

The various detection data may also include data such as a driver ID corresponding to the in-vehicle ID of the in-vehicle device 10, an intersection point passing time t0, the face orientation of the driver (pitch, yaw, and roll), the direction of the line of sight (pitch and yaw), the degree of eye opening (right eye and left eye), the acceleration of the vehicle (front-back, left-right, and up-down), the angular velocity (yaw), the driver image (shooting date and time, frame number, and image data), the vehicle exterior image (shooting date and time, frame number, and image data), the positional information of the vehicle (latitude and longitude), the traveling input, and the like.

The driving evaluation data storage unit stores, for each in-vehicle device 10 or each driver 3, the evaluation result of the safety confirmation operation of the driver 3 of each vehicle 2 executed by the server computer 50, that is, information on at least the evaluation result of the safety confirmation operation of the driver 3 at the intersection.

[ example of functional constitution ]

Fig. 5 is a block diagram showing an example of a functional configuration of the in-vehicle device 10 used in the operation management system 1 according to the embodiment.

The smartphone 90 includes a camera unit 91, a face authentication unit 92, and a communication unit 93.

The camera unit 91 includes, for example, a lens unit, an imaging element unit, a light irradiation unit, and a control unit for controlling these components, which are not shown.

The face authentication unit 92 runs a face authentication application and performs face authentication processing. For example, the face image data of the driver 3 captured by the camera unit 91 is compared with face image data registered in advance, and the determination process of whether the face authentication is successful is performed depending on whether the degree of similarity of the face image data is a predetermined threshold value. The face image data may include position data of each feature point of the face, distance data between these feature points, and the like. The face authentication process may be a two-dimensional face authentication process for recognizing a face in a planar manner, or may be a three-dimensional face authentication process for confirming a face in a stereoscopic manner.

The face authentication application is provided with a registration menu for face authentication, and face image data and a driver ID for face authentication can be stored in association with face image data and a driver ID for face authentication, which are registered in advance, by the registration menu for face authentication.

When the face authentication of the driver 3 is successful, the face authentication unit 92 performs processing to transmit the driver ID stored in association with the face image data for face authentication to the in-vehicle device 10 via the communication unit 93. When the face authentication of the driver 3 fails, the face authentication unit 92 transmits authentication disable information indicating that the face authentication has not been passed to the in-vehicle device 10 via the communication unit 93.

The communication unit 93 includes a communication module that can communicate with the in-vehicle device 10 wirelessly or by wire, such as a communication module of WI-FI, Bluetooth (registered trademark), or the like.

The control unit 19 of the in-vehicle device 10 includes a 1 st identification information acquiring unit 191, an identification information transmitting unit 192, a determination information acquiring unit 193, a processing unit 194, a 1 st authentication disabled information acquiring unit 195, and a 1 st authentication disabled information transmitting unit 196.

The control unit 19 of the in-vehicle device 10 reads a program stored in the ROM19c shown in fig. 2 and executes the program, thereby realizing operations of the respective components of the 1 st identification information acquiring unit 191, the identification information transmitting unit 192, the determination information acquiring unit 193, the processing unit 194, the 1 st authentication disable information acquiring unit 195, and the 1 st authentication disable information transmitting unit 196.

The 1 st identification information acquiring unit 191 acquires the driver ID of the driver 3 authenticated by the face authentication unit 92 of the smartphone 90 from the smartphone 90 carried by the driver 3 riding in the vehicle 2, and stores the driver ID in the RAM19 b.

The identification information transmitting unit 192 reads the driver ID of the driver 3 and the in-vehicle device ID of the in-vehicle device 10 acquired by the 1 st identification information acquiring unit 191 from the RAM19b, transmits the driver ID and the in-vehicle device ID to the server device 40, and makes the server device 40 determine whether or not the driver 3 riding in the vehicle 2 is the correct driver registered in the operation management table 71 a.

The determination information acquiring unit 193 acquires, from the server device 40, determination information (for example, information indicating whether the comparison match or the comparison mismatch) indicating whether or not the driver 3 riding in the vehicle 2 is the correct driver registered in the operation management table 71a, and stores the information in the RAM19 b.

When the determination information acquiring unit 193 acquires the determination information indicating that the driver 3 riding the vehicle 2 is not the correct driver registered in the operation management table 71a (i.e., the comparison does not match), the processing unit 194 operates the notification unit 16 to perform the predetermined warning process or the predetermined antitheft process. The processing unit 194 may transmit a signal for prohibiting starting to an engine starting device, not shown, via the external I/F18.

The 1 st authentication disapproved information acquiring unit 195 acquires the authentication disapproved information indicating that the face authentication unit 92 of the smartphone 90 has not authenticated from the smartphone 90 carried by the driver 3 riding in the vehicle 2, and stores the authentication disapproved information in the RAM19 b. In addition, when the 1 st authentication impossible information acquiring unit 195 acquires the authentication impossible information, the notifying unit 16 may be operated to perform a predetermined warning process or a predetermined theft prevention process, as described above.

The 1 st authentication disabled information transmitting unit 196 reads the authentication disabled information of the driver 3 and the in-vehicle device ID of the in-vehicle device 10 acquired by the 1 st authentication disabled information acquiring unit 195 from the RAM19b, and performs processing of transmitting the information to the server device 40 so as to register the information that the driver 3 riding on the vehicle 2 is a driver whose face authentication is disabled in the operation management table 71 a.

Fig. 6 is a block diagram showing an example of a functional configuration of the server device 40 used in the operation management system 1 according to the embodiment.

The server computer 50 constituting the server device 40 includes a 2 nd identification information acquisition unit 511, a driver determination unit 512, a determination information recording unit 513, a determination information transmission unit 514, a 2 nd authentication disabled information acquisition unit 515, an authentication disabled information recording unit 516, and a 2 nd authentication disabled information transmission unit 517.

The server computer 50 reads out the control program 53 stored in the main memory 52 shown in fig. 3, and executes the control program 53, thereby realizing operations of the respective components of the 2 nd identification information acquiring unit 511, the driver determining unit 512, the determination information recording unit 513, the determination information transmitting unit 514, the 2 nd authentication disabled information acquiring unit 515, the authentication disabled information recording unit 516, and the 2 nd authentication disabled information transmitting unit 517.

The 2 nd identification information acquiring unit 511 acquires the driver ID of the driver 3 and the in-vehicle device ID of the in-vehicle device 10 transmitted from the in-vehicle device 10, and stores the driver ID and the in-vehicle device ID in the main memory 52.

The driver determination unit 512 performs a process of comparing the driver ID of the driver 3 and the in-vehicle device ID of the in-vehicle device 10 acquired by the 2 nd identification information acquisition unit 511 with the operation management table 71a read by the operation management table storage unit 71, and determining whether or not the driver 3 riding the vehicle 2 is a correct driver registered in the operation management table 71a (for example, matching or non-matching).

The determination information recording unit 513 performs a process of recording the determination information (for example, information indicating the matching or the non-matching) as to whether or not the driver determined by the driver determining unit 512 is the correct driver in the operation management table 71 a.

The determination information transmitting unit 514 performs a process of transmitting the determination information indicating whether or not the driver determined by the driver determining unit 512 is the correct driver to at least one of the in-vehicle device 10 and the dealer terminal 80.

The 2 nd authentication disable information acquiring unit 515 acquires the authentication disable information indicating that the face authentication unit 92 of the smartphone 90 has not authenticated and the in-vehicle device ID of the in-vehicle device 10 transmitted from the in-vehicle device 10, and stores the authentication disable information and the in-vehicle device ID in the main storage 52.

The authentication disable information recording unit 516 performs processing for recording, in the operation management table 71a, information that the driver 3 riding on the vehicle 2 is a driver whose face authentication is disabled, based on the authentication disable information acquired by the 2 nd authentication disable information acquiring unit 515 and the in-vehicle device ID of the in-vehicle device 10.

When the authentication disabled information recording unit 516 records the information that the driver 3 riding the vehicle 2 is a driver whose face authentication is disabled in the operation management table 71a, the 2 nd authentication disabled information transmitting unit 517 performs a process of transmitting the information (authentication disabled information) indicating the driver whose face authentication is disabled to either the in-vehicle device 10 or the dealer end 80.

[ example of processing operation ]

Fig. 7 is a flowchart showing processing operations performed by the smartphone 90 used in the operation management system 1 according to the embodiment. The present processing operation is started when the driver 3 riding in the vehicle 2 performs an operation to start the face authentication application of the smartphone 90.

First, in step S1, the smartphone 90 detects an operation of the driver 3 to start the face authentication application, performs processing to start the face authentication application, and then performs processing in step S2.

In step S2, the smartphone 90 carries out the face authentication process, and then performs the process of step S3.

In step S3, the smartphone determines whether the face authentication of the driver 3 is successful, and if it is determined that the face authentication is successful, the process of step S4 is performed.

In step S4, the smartphone 90 reads out the driver ID associated with the face image data for face authentication registered in advance, which is used in the face authentication process in step S2, and then performs the process in step S5.

In step S5, the smartphone 90 performs processing of transmitting the driver ID associated with the face image data to the in-vehicle device 10 by wireless communication, and then ends the processing.

On the other hand, in step S3, if the smartphone 90 determines that the face authentication of the driver 3 is unsuccessful (i.e., fails to authenticate), the process of step S6 is performed.

In step S6, the smartphone 90 sets an authentication impossible flag (authentication impossible information) that displays the failure to authenticate, performs processing of transmitting the authentication impossible flag to the in-vehicle device 10, and then ends the processing.

Fig. 8 is a flowchart showing processing operations performed by the in-vehicle device 10 used in the operation management system 1 according to the embodiment. The present processing operation may be started, for example, when the communication setting process for causing the smartphone 90 carried by the driver 3 riding in the vehicle 2 to perform wireless communication with the in-vehicle device 10 is completed. The communication setting process may be, for example, a configuration in which the setting process is automatically performed when the smartphone 90 is brought within a certain range of the in-vehicle device 10, or a configuration in which the communication setting process is performed when the driver 3 performs a communication setting operation on the in-vehicle device 10 or the smartphone 90.

First, in step S11, the control unit 19 operates as the 1 st identification information acquisition unit 191 to determine whether or not the driver ID is acquired from the smartphone 90, and if it is determined that the driver ID is acquired, the process of step S12 is performed.

In step S12, the control unit 19 operates as the identification information transmitting unit 192 to perform a process of transmitting the driver ID acquired from the smartphone 90 and the in-vehicle device ID of the in-vehicle device 10 to the server device 40, and then ends the process.

On the other hand, in step S11, if the control unit 19 determines that the driver ID is not acquired from the smartphone 90, the process of step S13 is performed.

In step S13, the control unit 19 operates as the 1 st authentication disable information acquisition unit 195 to determine whether or not an authentication disable flag (authentication disable information) indicating that the face is not authenticated is acquired from the smartphone 90, and if it is determined that the authentication disable flag is acquired, the process of step S14 is performed.

In step S14, the control unit 19 operates as the 1 st authentication disabled information transmitting unit 196, performs a process of transmitting the authentication disabled flag acquired from the smartphone 90 and the in-vehicle device ID of the in-vehicle device 10 to the server device 40, and then performs the process of step S15.

In step S15, the control unit 19 operates the notification unit 16 to perform a process of notifying the driver 3 of information that the face authentication of the driver 3 has not been successful (i.e., that the authentication is not possible), and then ends the process.

Alternatively, in step S15, the control unit 19 may operate the notification unit 16 to notify the driver 3 that the face authentication of the driver 3 has not been successful, and transmit an impermissible signal that does not permit the engine start to an engine starting device, not shown, via the external I/F18. By this processing, it is possible to prevent theft of the vehicle and the like by making it impossible for a driver who cannot be authenticated to drive the vehicle.

Fig. 9 is a flowchart showing processing operations performed by the server device 40 used in the operation management system 1 according to the embodiment. This processing action may be repeatedly performed in a specified cycle.

First, in step S21, the server computer 50 operates as the 2 nd identification information acquisition unit 511 to determine whether or not the driver ID and the in-vehicle device ID transmitted from the in-vehicle device 10 are acquired, and if it is determined that the driver ID and the in-vehicle device ID are acquired, the process of step S22 is performed.

In step S22, the server computer 50 reads the operation management table 71a from the operation management table storage unit 71, and performs the processing of step S23.

In step S23, the server computer 50 operates as the driver determination unit 512, performs a process of comparing the driver ID and the in-vehicle device ID acquired in step S21 with the operation schedule (particularly, the driver ID and the in-vehicle device ID) of each driver stored in the operation management table 71a read in step S22, and then performs a process of step S24.

In step S24, the server computer 50 operates as the driver determination unit 512 to determine whether or not there is data matching the driver ID and the in-vehicle device ID acquired in step S21 in the operation schedule of each driver stored in the operation management table 71a, and if it is determined that there is matching data, the process of step S25 is performed.

In step S25, the server computer 50 operates as the determination information recording unit 513 to record a matching flag indicating the matching success with the operation management table 71a (in other words, the success of the confirmation of the driver 3 himself/herself) in the driver confirmation data field of the driver ID matching the operation management table 71a, and then performs the process of step S26.

In step S26, the server computer 50 operates as the determination information transmitting unit 514, performs a process of transmitting the matching identification and the in-vehicle ID of the in-vehicle device 10 to either the in-vehicle device 10 or the dealer end 80, and then ends the process.

When the matching flag and the in-vehicle device ID are acquired from the server device 40, the dealer end 80 performs processing for notifying the administrator of information on the driver 3 registered in the operation schedule multiplied by the vehicle 2 mounted on the in-vehicle device 10 to which the in-vehicle device ID is applied, through display output and voice output.

On the other hand, in step S24, if the server computer 50 determines that there is no data in the operation management table 71a that matches the driver ID and the in-vehicle device ID acquired in step S21, the process of step S27 is performed.

In step S27, the server computer 50 operates as the determination information recording unit 513 to perform a process of recording a check/mismatch (driver mismatch) flag in the driver confirmation data field of the operation management table 71a registered with the in-vehicle device ID corresponding to the in-vehicle device ID acquired in step S21, and then perform the process of step S28.

Further, in step S27, in the driver confirmation data field in the operation management table 71a in which the driver ID corresponding to the driver ID acquired in step S21 is registered, the processing of recording the collation inconsistency (vehicle inconsistency) flag is performed, and then step S28 may be performed.

In step S28, the server computer 50 operates as the determination information transmitting unit 514, transmits the matching flag and the in-vehicle device ID of the in-vehicle device 10 to at least one of the in-vehicle device 10 and the dealer end 80, and ends the processing.

When the mismatch flag and the in-vehicle device ID are compared with each other from the server device 40, the operator terminal 80 performs processing by display output and voice output to give a warning to the administrator that the driver 3 different from the operation schedule gets on the vehicle 2 mounted with the in-vehicle device 10 to which the in-vehicle device ID is applied.

On the other hand, in step S21, if the server computer 50 determines that the driver ID and the in-vehicle device ID transmitted from the in-vehicle device 10 are not acquired, the process of step S29 is performed.

In step S29, the server computer 50 operates as the 2 nd authentication disable information acquiring unit 515 to determine whether or not to acquire the authentication disable flag and the in-vehicle device ID transmitted from the in-vehicle device 10.

In step S29, if the server computer 50 determines that the authentication unidentifiable and the in-vehicle device ID are not obtained, the subsequent processing is ended; on the other hand, if it is determined that the authentication impossible flag and the in-vehicle device ID are acquired, the process of step S30 is performed.

In step S30, the server computer 50 reads the operation management table 71a from the operation management table storage unit 71, and performs the processing of step S31.

In step S31, the server computer 50 operates as the authentication disabled information recording unit 516, and performs a process of recording an authentication disabled flag in the driver confirmation data field in the operation management table 71a registered with the in-vehicle device ID corresponding to the in-vehicle device ID acquired in step S29, and then performs a process of step S32.

In step S32, the server computer 50 operates as the 2 nd authentication disabled information transmitting unit 517, transmits the authentication disabled flag and the in-vehicle device ID to the terminal 80 of the dealer, and then ends the processing.

When the authentication disabled flag and the in-vehicle device ID are acquired from the server device 40, the dealer end 80 performs processing by display output or voice output to send a warning to the manager that the driver who cannot be authenticated gets on the vehicle 2 on which the in-vehicle device 10 to which the in-vehicle device ID is applied is mounted.

Fig. 10 is a flowchart showing processing operations performed by the in-vehicle device 10 used in the operation management system 1 according to the embodiment. This processing operation is repeatedly executed in a predetermined cycle, for example, after the end of the processing in step S12 shown in fig. 8.

First, in step S41, the control unit 19 operates as the determination information acquisition unit 193 to determine whether or not a matching flag is acquired from the server device 40, and if it is determined that a matching flag is acquired, the process of step S42 is performed.

In step S42, the control unit 19 operates the processing unit 194, operates the notification unit 16, performs processing for notifying the driver 3 of the result of matching, and then ends the processing.

On the other hand, in step S41, if the control unit 19 determines that the matching flag is not obtained from the server device 40, the process of step S43 is performed.

In step S43, the control unit 19 operates as the determination information acquisition unit 193 to determine whether or not the matching flag is acquired from the server device 40, and if it is determined that the matching flag is acquired, the process of step S44 is performed.

In step S44, the control unit 19 operates the processing unit 194, operates the notification unit 16, performs processing for notifying the driver 3 of the result of the mismatch in the comparison, and then ends the processing.

[ action and Effect ]

According to the operation management system 1 of the above embodiment, even when the identity authentication of the driver 3 is performed by the face authentication, it is not necessary to store the face image data of all the drivers 3 that can drive the vehicle 2 in the in-vehicle device 10 in advance, and the in-vehicle device 10 can confirm whether or not each driver driving the vehicle 2 is a correct driver who has undergone the face authentication, in other words, whether or not the driver is a correct driver registered in the operation management table 71a, without performing a complicated face authentication process using the face image data.

According to the in-vehicle device 10 of the embodiment, the 1 st identification information acquisition unit 191 acquires the driver ID of the driver 3 authenticated by the face authentication unit 92 of the smartphone 90 from the smartphone 90 carried by the driver 3 riding in the vehicle 2. Thus, it is not necessary to store the face image data of all the drivers who can drive the vehicle 2 in the in-vehicle device 10 in advance, in other words, it is not necessary to provide a large-capacity storage unit for storing the face image data of all the drivers in advance in the in-vehicle device 10. Further, the driver ID of the driver 3 subjected to the face authentication can be acquired without performing a complicated face authentication process in the in-vehicle device 10.

The identification information transmitting unit 192 also transmits the driver ID of the driver 3 and the in-vehicle device ID of the in-vehicle device 10 to the server device 40. Thus, the in-vehicle device 10 can determine whether each driver driving the vehicle 2 is the correct driver registered in the operation management table 71a, that is, the correct driver subjected to the face authentication, in the server device 40 without performing the complicated face authentication process using the face image.

Further, according to the in-vehicle device 10, the 1 st authentication disapproved information acquiring unit 195 acquires the authentication disapproved information indicating that the face authentication unit 92 of the smartphone 90 has failed to authenticate, from the smartphone 90 carried by the driver 3 riding in the vehicle 2. Thus, it is not necessary to store face image data of all drivers who may drive the vehicle 2 in the in-vehicle device 10 in advance, in other words, it is possible to acquire authentication disapproved information indicating that the face is disapproved without performing a complicated face authentication process in the in-vehicle device 10, and it is possible to reduce the load of the authentication process.

The 1 st authentication disabled information transmitting unit 196 acquires authentication disabled information and the in-vehicle device ID of the in-vehicle device 10 from the smartphone 90 carried by the driver 3, and transmits the authentication disabled information and the in-vehicle device ID to the server device 40. It is thereby possible to record information that the driver 3 riding the vehicle 2 is a driver whose face authentication is not possible in the operation management table 71 a.

Further, according to the in-vehicle device 10, the determination information acquiring unit 193 can acquire, from the server apparatus 40, determination information (for example, a match flag or a mismatch flag) indicating whether or not the driver 3 riding on the vehicle 2 is the correct driver registered in the operation management table 71 a. Therefore, without performing the complicated face authentication processing using the face image data, the in-vehicle device 10 can confirm whether or not each driver driving the vehicle 2 is a correct driver for face authentication based on the determination information, and the load of the confirmation processing of the in-vehicle device 10 can be reduced.

Further, according to the in-vehicle device 10, when the determination information obtaining unit 193 obtains, from the server device 40, the determination information (for example, the mismatch flag) as to whether or not the driver 3 riding in the vehicle 2 is the correct driver registered in the operation management table 71a, the processing unit 194 executes the warning process for the driver 3 or the antitheft process for the vehicle 2. This makes it possible to warn the driver 3 and prevent the vehicle 2 from being stolen.

In the server device 40 according to the embodiment, the 2 nd identification information acquiring unit 511 acquires the driver ID of the driver 3 and the in-vehicle device ID of the in-vehicle device 10 from the in-vehicle device 10, and the driver determining unit 512 compares the driver ID and the in-vehicle device ID with the operation management table 71a to determine whether or not the driver 3 riding the vehicle 2 is a correct driver registered in the operation management table 71 a. Therefore, by determining whether or not the driver 3 riding in the vehicle 2 is the correct driver registered in the operation management table 71a in the server device 40, the burden of the identity confirmation process in the in-vehicle device 10 can be reduced.

In the server device 40, the determination information recording unit 513 records the determination information as to whether or not the driver determined by the driver determining unit 512 is the correct driver in the operation management table 71 a. Therefore, the server device 40 can centrally manage the determination information as to whether or not the driver 3 riding in the vehicle 2 is the correct driver registered in the operation management table 71 a.

In the server device 40, the determination information transmitting unit 514 transmits the determination information (for example, the matching flag or the non-matching flag) determined by the driver determining unit 512 to at least one of the in-vehicle device 10 and the customer terminal 80. Therefore, at least either the in-vehicle device 10 or the operator terminal 80 can acquire the determination information without performing a complicated determination process, and can execute a predetermined process in accordance with the content of the acquired determination information.

Further, according to the server device 40, the 2 nd authentication disable information acquiring unit 515 acquires the authentication disable information and the in-vehicle device ID which cannot be authenticated by the face authentication unit 92 of the smartphone 90 from the in-vehicle device 10, and records the information that the driver 3 riding on the vehicle 2 is a driver whose face authentication is disabled in the operation management table 71a based on the acquired authentication disable information and the in-vehicle device ID. Therefore, the information that the driver 3 riding the vehicle 2 is a driver whose face authentication is impossible can be centrally managed by the operation management table 71 a.

Further, according to the server device 40, when the 2 nd authentication disabled information transmitting unit 517 registers the information that the driver 3 riding the vehicle 2 is a driver whose face authentication is disabled in the operation management table 71a, the authentication disabled flag of the driver displayed as being not authenticated is transmitted to at least one of the in-vehicle device 10 and the dealer terminal 80. Therefore, the information of the driver whose face authentication is not possible can be notified to the driver 3 or the administrator of the dealer end 80 by the in-vehicle device 10 or the dealer end 80.

[ modified examples ]

The embodiments of the present invention have been described in detail, but the foregoing description is only an example of the present invention in all aspects. Various improvements and modifications can be made without departing from the scope of the present invention.

In the operation management system according to another embodiment, the control unit 19 of the in-vehicle device 10 may further include a 1 st identification information acquiring unit 191 and an identification information transmitting unit 192. The server computer 50 of the server device 40 may further include a 2 nd identification information acquiring unit 511 and a driver determining unit 512.

In the operation management system according to the other embodiment, the control unit 19 of the in-vehicle device 10 may further include the 1 st identification information acquiring unit 191, the identification information transmitting unit 192, the determination information acquiring unit 193, and the processing unit 194. The server computer 50 of the server device 40 may further include a 2 nd identification information acquisition unit 511, a driver determination unit 512, a determination information recording unit 513, and a determination information transmission unit 514.

In the operation management system according to another embodiment, the control unit 19 of the in-vehicle device 10 may further include a 1 st identification information acquiring unit 191, an identification information transmitting unit 192, a 2 nd authentication disabled information acquiring unit 195, and a 2 nd authentication disabled information transmitting unit 196. The server computer 50 of the server device 40 may further include a 2 nd identification information acquisition unit 511, a driver determination unit 512, a 2 nd authentication disabled information acquisition unit 515, and an authentication disabled information recording unit 516.

[ notes ]

The embodiments of the present invention can be described as follows, but are not limited to these.

Supplementary notes 1

An in-vehicle device 10, wherein the in-vehicle device 10 and an operation management device 40 are configured to be communicable, wherein the operation management device 40 includes an operation management table storage section 71 for storing an operation management table 71a, and identification information of each driver 3 and operation information of a vehicle 2 driven by each driver 3 are registered in the operation management table 71a in association with each other;

the in-vehicle device 10 includes:

a 1 st identification information acquiring unit 191 for acquiring, from a portable terminal 90 carried by a driver 3 riding in the vehicle 2, identification information of the driver 3 authenticated by a face authentication unit 92 of the portable terminal 90, and

an identification information transmitting unit 192 for transmitting the identification information of the driver acquired from the 1 st identification information acquiring unit 191 and the identification information of the in-vehicle device 10 to the operation management device 40 so that the operation management device 40 determines whether the driver 3 riding on the vehicle 2 is the correct driver registered in the operation management table 71 a.

Supplementary notes 2

An operation management device 40 that manages operations of each vehicle 2 on which an in-vehicle device 10 is mounted, the operation management device 40 comprising:

an operation management table storage section 71 for storing an operation management table 71a in which identification information of the drivers 3 who drive the respective vehicles 2 and operation information of the vehicles 2 which are driven by the respective drivers 3 are registered in correspondence, and

a 2 nd identification information acquisition unit 511 for acquiring the identification information of the driver 3 and the identification information of the in-vehicle device 10 transmitted from the in-vehicle device 10, and

the driver determination unit 512 is configured to compare the identification information of the driver 3 and the identification information of the in-vehicle device 10 acquired by the 2 nd identification information acquisition unit 511 with the operation management table 71a, and determine whether the driver 3 who has ridden on the vehicle 2 is a correct driver registered in the operation management table 71 a.

Appendix 3

An operation management system 1 is characterized in that the operation management system 1 includes a vehicle-mounted device 10 and an operation management apparatus 40.

Appendix 4

A driver confirmation method performed between an operation management device 40 and an in-vehicle device 10 configured to be communicable with the operation management device 40, wherein the operation management device 40 includes an operation management table storage 71 for storing an operation management table 71a, and identification information of each driver 3 and operation information of a vehicle 2 driven by each driver 3 are registered in the operation management table 71a in association with each other;

the in-vehicle device 10 includes a 1 st identification information acquisition step S11 of acquiring, from a portable terminal 90 carried by a driver 3 who gets on the vehicle 2, identification information of the driver 3 authenticated by a face authentication unit 92 of the portable terminal 90;

and an identification information transmission step S12 of transmitting the identification information of the driver 3 and the identification information of the in-vehicle device 10 acquired in the 1 st identification information acquisition step S11 to the operation management device 40;

the operation management device 40 includes a 2 nd identification information acquisition step S21 of acquiring the identification information of the driver 3 and the identification information of the in-vehicle device 10 transmitted from the in-vehicle device 10,

and driver determination steps S23 and S24 for comparing the identification information of the driver 3 and the identification information of the onboard device 10 acquired in the 2 nd identification information acquisition step S21 with the operation management table 71a and determining whether or not the driver 3 who rides on the vehicle 2 is the correct driver registered in the operation management table 71 a.

Claims

1. An in-vehicle device configured to be communicable with an operation management apparatus, wherein the operation management apparatus includes an operation management table storage unit configured to store an operation management table in which identification information of each driver and operation information of a vehicle driven by the driver are registered in association with each other;

the vehicle-mounted device includes:

an identification information transmitting unit configured to transmit the identification information of the driver and the identification information of the in-vehicle device acquired by the 1 st identification information acquiring unit to the operation management device so as to determine whether or not the driver riding the vehicle is a correct driver registered in the operation management table;

the identification information of the driver is a driver ID associated with the face image data of the driver registered in the face authentication portion in advance.

2. The in-vehicle device according to claim 1, wherein the in-vehicle device includes:

a 1 st authentication disapproval information acquisition unit configured to acquire authentication disapproval information indicating that a face authentication unit of a portable terminal fails to authenticate, from the portable terminal carried by the driver riding in the vehicle;

and a 1 st authentication disabled information transmitting unit configured to transmit the driver's authentication disabled information acquired by the 1 st authentication disabled information acquiring unit and the identification information of the in-vehicle device to the operation management device, so as to record, in the operation management table, information that the driver who has ridden on the vehicle is a driver whose face authentication is disabled.

3. The in-vehicle device according to claim 1, wherein the in-vehicle device includes a determination information acquisition unit configured to acquire, from the operation management apparatus, determination information indicating whether or not the driver riding the vehicle is a correct driver registered in the operation management table.

4. The in-vehicle device according to claim 3, wherein the in-vehicle device includes a processing unit configured to perform a predetermined warning process or a predetermined antitheft process when the determination information acquisition unit acquires determination information indicating that the driver riding the vehicle is not an accurate driver registered in the operation management table.

5. An operation management device that manages operation of each vehicle on which the in-vehicle device according to any one of claims 1 to 4 is mounted, the operation management device comprising:

an operation management table storage unit configured to store an operation management table in which identification information of drivers who drive the respective vehicles and operation information of vehicles driven by the drivers are registered in correspondence with each other;

a driver determination unit that compares the driver identification information acquired by the 2 nd identification information acquisition unit and the identification information of the in-vehicle device with the operation management table and determines whether or not the driver who rides the vehicle is a correct driver registered in the operation management table;

the driver identification information is a driver ID associated with the face image data of the driver registered in the face authentication portion in advance.

6. The operation management device according to claim 5, wherein the operation management device includes a determination information recording unit configured to record, in the operation management table, determination information as to whether or not the driver determined by the driver determination unit is the correct driver.

7. The operation management device according to claim 5, wherein the operation management device includes a determination information transmitting unit configured to transmit determination information indicating whether or not the correct driver is determined by the driver determining unit to the in-vehicle device or a terminal device of a manager who manages the vehicles.

8. The operation management device according to claim 5, wherein the operation management device comprises:

a 2 nd authentication disable information acquiring unit configured to acquire authentication disable information which is transmitted from the in-vehicle device and which the face authentication unit of the portable terminal fails to authenticate, and identification information of the in-vehicle device;

and an authentication disable information recording unit configured to record, in the operation management table, information that the driver riding the vehicle is a driver whose face cannot be authenticated, based on the authentication disable information acquired by the 2 nd authentication disable information acquiring unit and the identification information of the in-vehicle device.

9. The operation management device according to claim 8, wherein the operation management device includes a 2 nd authentication infeasible information transmitting portion configured to transmit information showing that the driver who cannot be face-authenticated is a driver to the in-vehicle device or a terminal device of an administrator managing the vehicle, in a case where the authentication infeasible information recording portion records information that the driver who rides on the vehicle is a driver whose face cannot be authenticated in the operation management table.

10. An operation management system comprising the in-vehicle device according to any one of claims 1 to 4 and the operation management apparatus according to any one of claims 5 to 9.

11. A driver confirmation method performed between an operation management device and a vehicle-mounted device configured to be communicable with the operation management device, wherein the operation management device includes an operation management table storage unit configured to store an operation management table in which identification information of each driver and operation information of a vehicle driven by the driver are registered in association with each other;

the in-vehicle machine includes:

a 1 st identification information acquisition step of acquiring identification information of a driver authenticated by a face authentication unit of a portable terminal from the portable terminal carried by the driver riding in the vehicle,

and an identification information transmission step of transmitting the identification information of the driver and the identification information of the in-vehicle device acquired in the 1 st identification information acquisition step to the operation management device;

the operation management device includes:

a 2 nd identification information acquisition step of acquiring identification information of the driver and identification information of the in-vehicle device transmitted from the in-vehicle device;

and a driver determination step of comparing the driver identification information and the in-vehicle device identification information acquired in the 2 nd identification information acquisition step with the operation management table, and determining whether or not the driver riding the vehicle is a correct driver registered in the operation management table;