Driver verification system, driver verification method, and program
The driver verification system addresses authentication errors by using driving characteristics to identify vehicle drivers, ensuring secure and accurate verification even when face recognition fails, thereby preventing unauthorized use.
Patent Information
- Application Number
- JP2023508245
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-03-24
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2041-03-24
AI Technical Summary
Existing driver verification technologies face challenges in accurately identifying the driver of a vehicle due to authentication errors in face recognition and GPS data unavailability, leading to potential misidentification or unauthorized use of vehicles.
A driver verification system that acquires and compares driving characteristics, including facial information and driving habits, to extract candidate drivers by matching them with past driving data, ensuring accurate identification even if face authentication fails.
The system effectively identifies vehicle driver candidates by utilizing driving characteristics, enhancing security and preventing unauthorized use by accurately verifying the driver's identity.
Smart Images

Figure 0007578184000001 
Figure 0007578184000002 
Figure 0007578184000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a driver verification system that verifies a driver of a vehicle. [Background technology]
[0002] In car sharing, rental cars, and other vehicle rental services, checking whether the person who made the reservation is using the rented vehicle will help prevent the vehicle from being used for other purposes, theft, or criminal use. Also, for vehicles managed by the operator, such as company cars, checking whether the designated driver is using the vehicle will help ensure proper use of these vehicles.
[0003] Patent documents 1 and 2 disclose technologies for identifying a vehicle driver through facial recognition using a facial image obtained by photographing the driver inside the vehicle. Patent document 4 discloses a technology for authenticating an individual by matching the results of biometric authentication with authentication information other than biometric authentication. Patent document 3 discloses a technology for authenticating a driver based on GPS data. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2020-149708 A [Patent Document 2] JP 2020-095694 A [Patent Document 3] JP 2019-006368 A [Patent Document 4] JP 2005-202730 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, face recognition can cause errors. In the technologies disclosed in Patent Documents 1, 2, and 4, if face recognition or the like fails, or in Patent Document 3, if GPS data cannot be obtained, the driver using the vehicle cannot be identified.
[0006] An object of the present disclosure is to provide a technology capable of appropriately extracting candidate drivers of a vehicle. [Means for solving the problem]
[0007] One aspect of the driver verification system disclosed herein is a driver verification system that includes a driver characteristic acquisition unit that acquires driving characteristics related to the driving of a driver of a vehicle, and an extraction processing unit that compares the acquired driving characteristics with the driving characteristics of past drivers to extract driver candidates from the past drivers.
[0008] One aspect of the information management method disclosed herein acquires driving characteristics related to a driver's driving of a vehicle, and compares the acquired driving characteristics with the driving characteristics of past drivers to extract driver candidates from the past drivers.
[0009] One aspect of the program stored in the storage medium of the present disclosure causes a computer to acquire driving characteristics related to a driver's driving in a vehicle, and compare the acquired driving characteristics with the driving characteristics of past drivers to extract driver candidates from the past drivers.
[0010] The program may be stored in a computer-readable and writeable non-transitory storage medium. Effect of the Invention
[0011] According to the present disclosure, vehicle driver candidates can be appropriately extracted. It is possible. [Brief description of the drawings]
[0012] [Figure 1] 1 is a diagram showing an overview of a management system according to a first embodiment. [Diagram 2] 1 is a block diagram showing an example of a configuration of a vehicle system according to a first embodiment. [Diagram 3] FIG. 2 is a diagram showing examples of driver characteristics including face information and driving characteristics. [Figure 4] FIG. 4 is a diagram illustrating an example of information stored in a driver characteristic DB. [Diagram 5] FIG. 4 is a diagram showing an example of driver characteristics stored in a driver characteristics DB. [Figure 6] 1 is a block diagram showing a configuration of a driver verification system according to a first embodiment. [Figure 7] 4 is an example of information stored in a collation DB. [Figure 8] 5 is a flowchart showing an example of an operation of the vehicle system according to the first embodiment. [Figure 9] 5 is a flowchart showing an example of the operation of the driver verification system according to the first embodiment. [Figure 10] FIG. 13 is a diagram showing an example of a notification that is a comparison result between a driver of the vehicle and a person who has reserved the vehicle. [Figure 11] FIG. 13 is a diagram showing an example of a display screen for driver candidates. [Figure 12] 6 is a flowchart showing a modified example of the operation of the driver verification system according to the first embodiment. [Figure 13] 13 is a diagram showing an example of a notification that is a comparison result between the driver and driver candidates of the vehicle and the person reserving the vehicle. FIG. [Figure 14] FIG. 11 is a diagram illustrating an overview of an example of a management system according to a second embodiment. [Figure 15] FIG. 11 is a block diagram showing an example of the configuration of a vehicle system according to a second embodiment. [Figure 16] 10 is a flowchart showing an example of an operation of a vehicle system according to a second embodiment. [Figure 17] FIG. 11 is a block diagram showing an example of the configuration of a driver characteristic system according to a second embodiment. [Figure 18] 10 is a flowchart showing an example of the operation of a driver characteristic system according to the second embodiment. [Figure 19]FIG. 11 is a block diagram showing a configuration of a driver verification system according to a third embodiment. [Figure 20] 13 is a flowchart showing an example of the operation of the driver verification system according to the third embodiment. [Figure 21] FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] A driver verification system according to an embodiment of the present disclosure will be described using an example in which the system is applied to vehicle reservation management. Specifically, the driver verification system uses face information of the driver of the vehicle and the driving characteristics of the vehicle by the driver to verify whether the driver of the vehicle is the person who has reserved the vehicle. The following description of the embodiment is merely an example and is not limited thereto.
[0014] [First embodiment] The management system according to the first embodiment will be described with reference to the drawings. Fig. 1 is a diagram showing an overview of the management system according to the first embodiment. The management system shown in Fig. 1 includes a vehicle system 10, a driver characteristic DB 20, a driver verification system 30, and a verification DB 40.
[0015] The driver verification system 30 is communicatively connected to the vehicle system 10, the driver characteristics DB 20, and the verification DB 40 via a network 50. The vehicle system 10, the driver characteristics DB 20, the driver verification system 30, and the verification DB 40 are described below.
[0016] (Vehicle System 10) The vehicle system 10 is installed in a vehicle such as an automobile, and generates face information and driving characteristics of a driver based on sensor data from various sensors installed in the vehicle. The generated face information and driving characteristics are used in the driver verification system 30 to confirm whether the driver of the vehicle is the person who has reserved the vehicle. Note that the vehicle may include, in addition to automobiles (four-wheeled motor vehicles), motorcycles (including three-wheeled motor vehicles), bicycles, etc.
[0017] The facial information is, for example, a facial image or facial features of a driver of a vehicle. The driving features are features related to the driving of the driver. The facial image is an image including a part or all of a face. The facial features are any data indicating facial features. The driving features may be features before driving (before driving) of the vehicle, features during driving (driving) of the vehicle, or features after driving (driving) of the vehicle.
[0018] The driving features include, for example, person features indicating the features of the driver in the driver's seat of the vehicle, setting features indicating the features of the vehicle settings made by the driver, or driving features indicating the features of the vehicle driving made by the driver. The person features may be the habits or habit of the driver's behavior in the vehicle. For example, the position of the driver's hands holding the steering wheel. Note that the driving features are not limited to person features, setting features, or driving features, as long as they can identify the driver in the vehicle.
[0019] The configuration of the vehicle system will be described with reference to the drawings. Fig. 2 is a block diagram showing an example of the configuration of the vehicle system 10. The vehicle system 10 shown in Fig. 2 includes a vehicle sensor 110, a driver feature generation unit 120, and a communication unit (not shown).
[0020] The vehicle sensor 110 generates sensor data related to the driving of a driver of the vehicle. The vehicle sensor 110 is, for example, a human sensor 111, a setting sensor 112, or a travel sensor 113. Note that the vehicle sensor 110 is not limited to the above three types of sensors. The human sensor 111 is a sensor related to the driver of the vehicle. The human sensor is, for example, a camera that captures the driver's appearance, a microphone that collects the driver's voice, a pressure sensor that measures the weight of the driver, a weight sensor, etc. Note that the human sensor is not limited to a camera, a microphone, etc.
[0021] The setting sensor 112 is a sensor that detects various settings in the vehicle. For example, the setting sensor detects the position settings of the rearview mirror and door mirror, the seat position setting, the temperature setting of the air conditioner, the window opening and closing position setting, and the volume setting of the car audio. However, the objects detected by the setting sensor are not limited to these.
[0022] The driving sensor 113 includes, but is not limited to, an acceleration sensor, a steering angle sensor that measures the steering angle, a torque sensor that detects the steering force, an accelerator position sensor that detects the accelerator opening, etc. The vehicle sensor 110 sends sensor data from each sensor to the driver feature generation unit 120.
[0023] The driver feature generation unit 120 generates face information of the driver and features related to the driver's driving in the vehicle (hereinafter referred to as driving features) based on the sensor data of the vehicle sensor 110. The face information and driving features are also called driver features.
[0024] Next, the driver characteristic generation unit 120 includes a person characteristic generation unit 121, a setting characteristic generation unit 122, and a driving characteristic generation unit 123. The person characteristic generation unit 121 generates face information of the driver in the vehicle and the person characteristics of the driver in the vehicle based on the sensor data of the human sensor 111.
[0025] For example, in the case of face information, the person feature generation unit 121 generates a face image by performing image processing on the photographed data of the driver of the vehicle. The person feature generation unit 121 may generate face features by extracting face features from the generated face image.
[0026] For example, in the case of human features, the human feature generation unit 121 acquires the position of the driver's face or the driving posture in a captured image captured by a fixed camera installed in the vehicle. The human features may be the voice features or weight of the driver in the vehicle obtained from a sensor. The voice features may be, for example, the frequency and sound pressure of the voice.
[0027] The set feature generating unit 122 generates set features of the vehicle based on the sensor data of the set sensor 112. The set features are features related to the settings of the vehicle by the driver. For example, the set feature generating unit 122 generates information on the position of the rearview mirror or door mirrors and the seat position set by the driver. The position information is generated as, for example, the amount of movement from an arbitrary reference position. Note that the set features are not limited to this.
[0028] The driving feature generation unit 123 generates driving features based on the sensor data of the vehicle sensor 110. The driving features are features related to the vehicle driving by the driver. For example, the driving feature generation unit 123 generates driving features related to the accelerator pedal pressure based on the sensor data of an accelerator position sensor. The driving features are not limited to this. For example, the driving feature generation unit 123 may generate operation features such as a turning manner based on sensor data of a steering sensor as the driving feature. The driving feature generation unit 123 may also generate a driving route based on an acceleration sensor, map information, and position information, and a driving time zone based on a clock as the driving feature. Note that the driving route may be a driving route set in a navigation system.
[0029] FIG. 3 is a diagram showing an example of driver characteristics including face information and driving characteristics. In the figure, a vehicle ID is an identifier of a vehicle. The face information or driving characteristics generated by the driver characteristic generating unit 120 is associated with the vehicle ID and a date and time, and stored in a storage unit (not shown). The date and time indicate, for example, the date and time when the vehicle ID is associated with the face features and driving characteristics.
[0030] The driver feature generation unit 120 sends the driver features in which the facial information or driving features are associated with the vehicle ID to the driver feature DB 20 via a communication unit (not shown). For example, at least one of the person features, setting features, and running features among the driving features may be associated with the vehicle ID facial information. Alternatively, there may be an example in which no driving features are included. Examples of the association between facial information and driving features are not limited to this.
[0031] (Driver Features DB20) FIG. 4 is a diagram showing an example of information stored in the driver characteristic DB 20. The driver characteristic DB 20 stores the driver characteristics 201 transmitted from the vehicle system 10 of each vehicle. The driver characteristic DB 20 stores the driver characteristics 201 including face information and driving characteristics transmitted by each vehicle in the past. The driver characteristic DB 20 is, for example, a storage device having a communication function. The driver characteristic DB 20 may be configured by a computer. The driver characteristic DB 20 may be integrated with the matching DB 40.
[0032] FIG. 5 is a diagram showing an example of driver characteristics stored in the driver characteristics DB. In the driver characteristics 201 shown in FIG. 5, a vehicle ID, a date and time, face information of a driver who drives a vehicle, and the driving characteristics of the driver are associated with each other. The driver characteristics DB may include information that can identify an individual. For example, information of the driver's driver's license, personal number card, and IC card transmitted in association with face information and driving characteristics may be included. The items of the driver characteristics 201 shown in FIG. 5 are examples and are not limited to these.
[0033] (Driver Verification System 30) The driver verification system 30 will be described below with reference to the drawings. FIG. 6 is a block diagram showing an example of the configuration of the driver verification system 30 according to the first embodiment. The driver verification system 30 shown in FIG. 6 includes an identification processing unit 301, an extraction processing unit 302, an output processing unit 303, and a communication unit (not shown). The driver verification system 30 is, for example, a computer that executes various functions by software. The driver verification system 30 may be realized by cloud computing.
[0034] (Identification processing unit 301) The identification processing unit 301 compares the facial information of the driver of the vehicle transmitted from the vehicle system 10 with the facial information stored in the comparison DB 40. FIG. 7 is an example of information stored in the comparison DB 40. The comparison DB 40 stores facial information 401 and reservation information 402. The facial information 401 is facial information of the driver registered in advance. The facial information is a facial image or facial features. The reservation information 402 is information about a reserving person who is scheduled to drive the vehicle. In the case of a rental car or the like, the reserving person is a user of the vehicle who is registered when making a reservation. In addition, in the case of a vehicle managed by a business operator, such as a company car, the reserving person is a driver predetermined by the business operator. In this case, the reservation information may be created based on, for example, schedule information set by the business operator (it does not have to involve an explicit reservation operation). The reservation information 402 includes, for example, the name of the reserving person, the vehicle ID of the reserved vehicle, the rental date and time of the vehicle, and the like. The reservation information 402 may include information on a person who may ride in the vehicle with the person who made the reservation and drive on behalf of the person who made the reservation, as a target for driver verification. The person who may drive may be, for example, a family member, friend, or colleague of the person who made the reservation.
[0035] The identification processing unit 301 sends the matching result of the facial information to the vehicle system 10 via a communication unit (not shown), or to the output processing unit 303. The matching result sent to the vehicle system 10 may be, for example, a personal ID linked to the facial information of the driver if facial recognition is successful. Alternatively, if facial recognition is unsuccessful, the matching result sent may be "failed facial recognition." "Failed" indicates that the driver was not identified by facial recognition.
[0036] The driver verification system 30 may receive face information of the driver of the vehicle via the driver feature DB 20, in addition to the vehicle system 10.
[0037] (Extraction processing unit 302) The driver verification system 30 receives driving characteristics related to the driver's driving of the vehicle from the vehicle system 10. The extraction processing unit 302 acquires the driver's driving characteristics and compares the acquired driving characteristics of the driver with past driving characteristics included in the driver characteristics 201 of the driver characteristic DB 20. The past driving characteristics include at least one of person characteristics, setting characteristics, and driving characteristics. The extraction processing unit 302 extracts driver candidates who are the same or similar to the acquired driving characteristics from the past driving characteristics of the drivers.
[0038] The extracted information on the driver candidates is, for example, facial information of the driver linked to the driving characteristics. Alternatively, if a personal ID that can identify an individual is linked to the past driving characteristics in the driver characteristics DB20, the personal ID may be extracted as information on the driver candidate. The personal ID is, for example, a driver's license number, a personal number, a membership number, etc. The extraction processing unit 302 sends the information on the extracted driver candidates to the output processing unit 303 as the extraction result. If the extraction processing unit 302 cannot extract a driver candidate, the extraction result will be "no driver candidate."
[0039] The driver verification system 30 may receive the driving characteristics of the driver of the vehicle via the driver characteristics DB 20, in addition to the vehicle system 10.
[0040] (Output processing unit 303) If the identification processing unit 301 fails to authenticate the driver's face, the output processing unit 303 issues an alert notifying the failure of face authentication. The output processing unit 303 notifies, for example, the vehicle manager (the rental car company, the person in charge of operating the company car, etc.). Note that the notification destination is not limited to these, and the driver of the vehicle himself or the person who made the reservation may also be notified. On the other hand, if the identification processing unit 301 succeeds in authenticating the driver's face, the output processing unit 303 compares the information of the driver identified by face authentication with the reservation information stored in the verification DB 40.
[0041] Specifically, the system compares whether the driver identified by the facial recognition is a reserving person included in the reservation information. The reserving person may include a friend, family member, colleague, or the like who may drive the vehicle requested by the reserving person when registering the reservation information.
[0042] If the comparison shows that the driver identified by face recognition is different from the person who made the reservation included in the reservation information, the output processing unit 303 issues an alert to that effect. If the driver is the same as the person who made the reservation, the output processing unit 303 does not issue a notification.
[0043] In the above, an example has been described in which the extraction processing unit 302 extracts driver candidates based on driving characteristics after the identification processing unit 301 fails to perform face recognition, but the present invention is not limited to this. For example, driver candidates may be extracted using driving characteristics regardless of the success or failure of face recognition, and the output processing unit 303 may compare the driver identified by face recognition and the driver candidates based on the driving characteristics with the reservation party in the reservation information. In the vehicle, the authentication medium may be read to obtain the identification information of the driver. The authentication medium may be an IC card or a mobile terminal. The identification processing unit 301 may identify the driver based on the identification information obtained from the authentication medium instead of or in combination with the face recognition.
[0044] Next, the operation of the vehicle system 10 according to the first embodiment will be described with reference to the drawings. Fig. 8 is a flowchart showing an example of the operation of the vehicle system 10 according to the first embodiment. Hereinafter, an example will be described in which the vehicle system 10 generates face information and driving characteristics of a driver who drives a vehicle, and transmits the generated face characteristics and driving characteristics to the driver verification system 30.
[0045] When the driver gets in the vehicle, the vehicle sensor 110 starts collecting sensor data. For example, when it is detected that the driver has sat in the seat, the vehicle sensor 110 may start collecting sensor data. The vehicle sensor 110 includes a human sensor 111, a setting sensor 112, and a driving sensor 113. The vehicle sensor 110 acquires various sensor data (step S101) and sends the acquired sensor data to the driver characteristic generation unit 120. The various sensor data may be acquired before the vehicle starts traveling or while the vehicle is traveling. For example, a camera installed in the vehicle captures an image of the driver and sends the captured data to the driver characteristic generation unit 120.
[0046] The driver characteristic generation unit 120 generates face information and driving characteristics based on the sensor data. For example, the human characteristic generation unit 121 of the driver characteristic generation unit 120 generates face information of the driver based on the sensor data of the human sensor 111 (step S102). Specifically, the human characteristic generation unit 121 generates a face image of the driver based on the photographed data of the camera.
[0047] Further, the driver feature generation unit 120 generates driving features related to the driver's driving based on the sensor data of the vehicle sensor 110 (step S103). For example, the person feature generation unit 121 of the driver feature generation unit 120 generates person features. The person feature is, for example, the driving posture of the driver. The set feature generation unit 122 generates set features, and the driving feature generation unit 123 generates driving features. The set feature is, for example, the mirror position of the vehicle set by the driver. The driving feature is the driver's driving operation feature, for example, the manner in which the driver presses the accelerator pedal.
[0048] Next, the vehicle system 10 transmits the driver's facial information to the driver verification system 30 for facial authentication using the driver's facial information (step S104). Specifically, the driver feature generation unit 120 associates the driver's facial information with the vehicle ID and transmits it to a communication unit (not shown). The communication unit transmits the driver's facial information associated with the vehicle ID to the driver verification system 30.
[0049] Next, the vehicle system 10 receives the authentication result of the face authentication of the driver from the driver verification system 30 (step S105). If the authentication result is face authentication OK (Yes in step S106), the vehicle system 10 ends the process of acquiring sensor data by the vehicle sensor 110.
[0050] On the other hand, if the authentication result is not face authentication OK (face authentication NG) (Yes in step S106), the vehicle system 10 transmits the driving characteristics of the driver to the driver verification system 30 to identify the driver using the driving characteristics (step S107). Specifically, the driver characteristic generation unit 120 associates at least one of the driving characteristics of the driver, the person characteristics, the setting characteristics, and the driving characteristics with the vehicle ID "#101" and sends them to a communication unit (not shown). The communication unit transmits the driving characteristics of the driver associated with the vehicle ID to the driver verification system 30.
[0051] <Operation of the driver verification system> The operation of the driver verification system 30 according to the first embodiment will be described with reference to the drawings. Fig. 9 is a flowchart showing an example of the operation of the driver verification system 30 according to the first embodiment. The following operation of the driver verification system 30 is an example of using the driving characteristics of the driver after face authentication of the driver in the vehicle has failed.
[0052] The driver verification system 30 receives the facial information of the driver transmitted by the vehicle system 10. The identification processing unit 301 of the driver verification system 30 acquires facial information of the driver of the vehicle (step S201). The identification processing unit 301 compares the acquired facial information of the driver with preregistered facial information 401 stored in the verification DB 40 (step S202) to identify the driver of the vehicle.
[0053] If the face authentication of the driver is successful (Yes in step S203), the identification processing unit 301 collates the information of the driver identified by the face authentication with the reservation information stored in the collation DB 40 (step S207).
[0054] FIG. 10 is a diagram showing an example of a notification that is a comparison result between the driver of the vehicle and the person who reserved the vehicle. The face recognition item shown in FIG. 10 indicates the driver identified by face recognition. In the figure, the driver identified by face recognition is "A." "Failed" in the face recognition item indicates that the driver was not identified by face recognition.
[0055] The driving characteristics item indicates the driver candidates extracted by matching the driving characteristics of the driver. If there are no driver candidates, "None" is displayed. In the figure, the driver candidates extracted by matching the driving characteristics are "A", or "A" and "C". The reserver item indicates the reserver who reserved the vehicle included in the reservation information. In the figure, the reserver is "A" or "B".
[0056] 10, if the face authentication result shows that the driver is "A" and the person reserving the vehicle is "A", the driver and the person reserving the vehicle match, so the output processing unit 303 does not output a notification. On the other hand, if the person reserving the vehicle is "B", the driver and the person reserving the vehicle do not match, so the output processing unit 303 issues a fraud alert to the effect that "the driver is different from the person reserving the vehicle".
[0057] Returning to FIG. 9, if face authentication of the driver fails (No in step S203), the extraction processing unit 302 acquires driving characteristics related to the driving of the driver (step S204).
[0058] The extraction processing unit 302 compares the acquired driving characteristics of the driver with the past driving characteristics in the comparison DB 40 (step S205), and extracts driver candidates who are candidates for the driver of the vehicle (step S206). The extraction processing unit 302 sends the extraction result to the output processing unit 303.
[0059] As shown in Fig. 10, if the driver candidate based on the driving characteristic matching result is "A" and the reservation person is "A", the output processing unit 303 notifies a face authentication failure alert and notifies the driver candidate "A". On the other hand, if the driver candidates based on the driving characteristic matching result are "A" and "C" and the reservation person is "B", the output processing unit 303 notifies a face authentication failure alert and the driver candidates "A" and "C", and also outputs a "fraud" notification because the driver of the vehicle and the reservation person do not match. Note that if there is no driver candidate, the output processing unit 303 notifies a face authentication failure alert.
[0060] 11 is a diagram showing an example of a display screen of driver candidates. The display screen is output by the output processing unit 303. Display 3021 displays driver candidates based on driving characteristics. In the figure, display 3022 displays three driver candidates. Display button 3023 is a button for displaying driver candidates other than display 3022. When there is another driver candidate, display button 3023 is activated.
[0061] In the operation of the driver verification system 30 shown in Fig. 9, after facial authentication of the vehicle driver fails, a driver candidate is extracted based on the driving characteristics of the vehicle driver. Even if facial authentication fails, the driver verification system 30 can compare the information of the driver candidate with the reservation information, and can confirm whether the driver who drives the vehicle is the person who reserved the vehicle or is different from the person who reserved the vehicle.
[0062] (Modification of the first embodiment) Fig. 12 is a flowchart showing a modified operation of the driver identification system 30 according to the first embodiment. The modified operation of the driver identification system 30 uses driving characteristics regardless of whether the face authentication of the driver is successful, and differs from the operation of the driver identification system 30 shown in Fig. 9 in that the driving characteristics are not used when the face authentication of the driver is successful. The modified operation of the driver identification system 30 performs face authentication of the driver of the vehicle and extraction of driver candidates based on the driving characteristics. If the face authentication result and the extraction result indicate different drivers, the face authentication result is given priority.
[0063] First, the operation of the vehicle system 10 of the modified example will be described. When the driver gets in the vehicle system 10, the vehicle sensor 110 starts collecting sensor data and acquires various sensor data. The driver feature generation unit 120 generates face information and driving features based on the sensor data. The vehicle system 10 transmits the generated face recognition and driving features to the driver verification system 30. Unlike the vehicle system 10 of the first embodiment, the vehicle system 10 of the modified example transmits the driving features to the driver verification system 30 without waiting for the verification result of the face information from the driver verification system 30. Next, the operation of the vehicle system 10 of the modified example will be described. The driver verification system 30 receives the facial information of the driver of the vehicle transmitted from the vehicle system 10. The identification processing unit 301 of the driver verification system 30 acquires the facial information of the driver of the vehicle (step S301), and performs facial authentication using the acquired facial information of the driver (step S302). Specifically, the identification processing unit 301 collates the acquired facial information of the driver with pre-registered facial information 401 stored in the verification DB 40, and identifies the driver of the vehicle. The identification processing unit 301 sends the authentication result to the output processing unit 303.
[0064] Next, the driver verification system 30 receives the driving characteristics of the driver of the vehicle transmitted from the vehicle system 10. The extraction processing unit 302 of the driver verification system 30 acquires the driving characteristics of the driver (step S303), and collates the acquired driving characteristics of the driver with the driving characteristics of past drivers in the verification DB 40 (step S304). The extraction processing unit 302 extracts driver candidates who are candidates for the driver of the vehicle (step S305). The extraction processing unit 302 sends the extraction result to the output processing unit 303.
[0065] The output processing unit 303 receives the face authentication result from the identification processing unit 301 and the extraction result from the extraction processing unit 302. The output processing unit 303 uses the collation result of the face authentication result and the driving characteristics to compare with the reservation information 404 in the collation DB 40 (step S306), and outputs the comparison result between the driver of the vehicle and the person reserving the vehicle (step S307).
[0066] Fig. 13 is a diagram showing an example of a notification that is a comparison result between the driver and driver candidates of the vehicle and the person reserving the vehicle. In the example of the notification shown in Fig. 13, the items of face recognition, driving characteristics, and the person reserving the vehicle are the same as those in the example of the notification shown in Fig. 10, and detailed explanations are omitted.
[0067] 13, as a result of face recognition and matching of driving characteristics, the driver and the driver candidate are "A," and if the reserving party in the reservation information is "A," the output processing unit 303 does not issue a notification. On the other hand, if the reserving party in the reservation information is "B," the output processing unit 303 issues a fraud alert to the effect that the driver of the vehicle is "different from the reserving party."
[0068] Furthermore, if the results of facial recognition and driving characteristic matching indicate that the driver is "A" and the candidate driver is "B," and the person who made the reservation in the reservation information is "A," the output processing unit 303 issues an alert stating that "facial recognition and driving characteristics differ." At this time, the facial recognition result takes precedence in the comparison with the reservation information, and the output processing unit 303 does not issue a fraud alert. On the other hand, if the person who made the reservation in the reservation information is "B," the output processing unit 303 issues an alert stating that "facial recognition and driving characteristics differ" and a fraud alert stating that "different from the person who made the reservation."
[0069] In addition, in FIG. 13, when face authentication fails and when the driving characteristic is “none”, the notification pattern output from the output processing unit 303 is the same as the example in FIG.
[0070] As described above, in the modified operation of the driver matching system, the matching results of the driving characteristics are used regardless of the success or failure of face authentication, thereby increasing the number of notification patterns from the output processing unit 303 and enabling more detailed notifications.
[0071] (Effects of the First Embodiment) According to the driver verification system 30 of the first embodiment, it is possible to appropriately extract candidates for the driver of the vehicle. This is because the extraction processing unit 302 acquires driving characteristics of the driver who drives the vehicle from the vehicle system 10, and extracts driver candidates by collating the acquired driving characteristics with past driving characteristics.
[0072] [Second embodiment] A management system according to a second embodiment will be described with reference to the drawings. Fig. 14 is a diagram showing an overview of the management system according to the second embodiment. In the description of the second embodiment, the same components as those in the first embodiment are given the same reference numerals and detailed description thereof will be omitted.
[0073] The management system of the second embodiment differs from the management system of the first embodiment in that the vehicle system 10 and the driver characteristic DB 20 in the management system of the first embodiment are replaced by a vehicle system 11 and a driver characteristic system 21, respectively.
[0074] In the management system of the second embodiment, a vehicle system 11 has a vehicle sensor 110 installed in the vehicle acquire various sensor data and transmits the data to a driver characteristic system 21. The driver characteristic system 21 generates face information and driving characteristics of the driver based on the sensor data transmitted from the vehicle system 11. The configurations of the vehicle system 11 and the driver characteristic system 21 according to the second embodiment will be described below.
[0075] (Vehicle Systems 11) Fig. 15 is a block diagram showing an example of the configuration of a vehicle system 11 according to the second embodiment. The vehicle system 11 in Fig. 15 includes a vehicle sensor 110, a sensor data management unit 130, and a communication unit (not shown). The configuration of the vehicle sensor 110 of the vehicle system 11 is similar to that of the vehicle sensor 110 of the vehicle system 10 according to the first embodiment. Various sensor data collected by the vehicle sensor 110 is sent to the sensor data management unit 130.
[0076] The sensor data management unit 130 associates the sensor data from the vehicle sensor 110 with the vehicle ID and transmits the sensor data to the driver characteristic system 21. For example, the sensor data management unit 130 may transmit the acquired sensor data for each of the human sensor 111, the setting sensor 112, and the driving sensor 113 to the driver characteristic system 21.
[0077] 16 is a flowchart showing an example of the operation of the vehicle system according to the second embodiment. The vehicle sensor 110 of the vehicle acquires various sensor data (step S111). The vehicle sensor 110 is a human sensor 111, a setting sensor 112, or a travel sensor 113. The vehicle sensor 110 transmits the acquired various sensor data to the sensor data management unit 130. The sensor data management unit 130 transmits the acquired sensor data in association with the vehicle ID to the driver characteristic system 21 (step S112).
[0078] (Driver Feature System 21) FIG. 17 is a block diagram showing an example of the configuration of the driver characteristic system 21 according to the second embodiment. The driver characteristic system 21 is, for example, a computer that executes various functions by software. The driver characteristic system 21 may be realized by cloud computing. The driver characteristic system 21 in FIG. 17 includes a driver characteristic generation unit 120 and a driver characteristic DB 20. The driver characteristic generation unit 120 of the driver characteristic system 21 has a configuration similar to that of the driver characteristic generation unit 120 of the vehicle system 10 of the first embodiment, and therefore a detailed description thereof will be omitted. The face information of the driver and the motion characteristics of the driver for each vehicle generated by the driver characteristic generation unit 120 are sent to and stored in the driver characteristic DB 20. The driver characteristic system 21 transmits the face characteristics and driving characteristics generated by the driver characteristic generation unit 120 to the driver verification system 30.
[0079] The configuration of the driver characteristic DB 20 is the same as that of the first embodiment, and therefore detailed description thereof will be omitted. The driver characteristic DB 20 may be installed outside the driver characteristic system 21. For example, the driver characteristic DB 20 may be communicably connected to the driver characteristic system 21 via the network 50 as in the first embodiment.
[0080] <Operation of driver characteristic system 21> The operation of the driver characteristic system 21 according to the second embodiment will be described with reference to the drawings. Fig. 18 is a flowchart showing an example of the operation of the driver characteristic system 21 according to the second embodiment. Hereinafter, an example will be described in which the driver characteristic system 21 generates face information and driving characteristics of a driver who drives a vehicle, and transmits the generated face characteristics and driving characteristics to the driver verification system 30.
[0081] The driver feature system 21 receives sensor data from the vehicle system 11. The sensor data is, for example, photographed data of the driver of the vehicle, the seat installation position, the acceleration of the vehicle, and the like. The driver feature generation unit 120 acquires the sensor data (step S121). The driver feature generation unit 120 generates face information and driving features based on the acquired sensor data. For example, the human feature generation unit 121 of the driver feature generation unit 120 generates face information of the driver based on the sensor data of the human sensor 111 (step S122). Alternatively, the driver feature generation unit 120 generates driving features related to the driver's driving based on the sensor data of the vehicle sensor 110 (step S123). The driving features are, for example, a human feature indicating the driver's driving posture, a setting feature which is the mirror position of the vehicle set by the driver, and a driving feature of the driver's depression of the accelerator pedal.
[0082] Next, the vehicle system 11 transmits the driver's facial information to the driver verification system 30 for facial authentication using the driver's facial information (step S124). Furthermore, the vehicle system 10 transmits the driver's driving characteristics to the driver verification system 30 for driver verification using the driving characteristics (step S125). The facial information and driving characteristics transmitted to the driver verification system 30 are associated with the vehicle ID.
[0083] (Effects of the second embodiment) According to the vehicle system 11 of the second embodiment, since the configuration of the driver feature generation unit 120 is not included, the system configuration of the vehicle system 11 in the vehicle can be simplified, or the load on the system can be reduced.
[0084] Moreover, according to the driver characteristic system 21 of the second embodiment, the driver characteristic generation unit 120 generates face information and driving characteristics for each vehicle, thereby making the generation process more efficient. Specifically, the human characteristic generation unit 121 can generate face information that is a face image or a face feature by collectively processing the captured data from a plurality of vehicles. The driving characteristics can also be generated efficiently by dividing the generation process into the human characteristics of the driver, the setting characteristics of the driver's vehicle settings, and the driving characteristics of the driver, and processing them collectively for a plurality of vehicles.
[0085] [Third embodiment] A driver verification system according to the third embodiment will be described with reference to the drawings. The driver verification system according to the third embodiment is communicatively connected to the vehicle system 10 or the driver characteristic DB 20 via the network 50, similar to the driver verification system 30 according to the first embodiment. The driver verification system 31 may be communicatively connected to the verification DB 40.
[0086] FIG. 19 is a block diagram showing an example of the configuration of a driver verification system 31 according to the third embodiment. The driver verification system 31 corresponds to the extraction processing unit 302 of the driver verification system 30 according to the first embodiment. The driver verification system 31 shown in FIG. 19 includes a driver characteristic acquisition unit 311, an extraction processing unit 312, and a communication unit (not shown). The driver verification system 31 is, for example, a computer that executes various functions by software. Note that the driver verification system 31 may be realized by cloud computing.
[0087] The driver verification system 31 receives driving characteristics related to the driving of the driver in the vehicle from the vehicle system 10. The driver characteristic acquisition unit 311 acquires the driving characteristics of the driver. The driving characteristics of the driver include, for example, at least one of person characteristics, setting characteristics, and driving characteristics.
[0088] The extraction processing unit 312 compares the acquired driving characteristics of the driver with past driving characteristics. The past driving characteristics are included in the driver characteristics 201 of the driver characteristics DB 20, for example. The past driving characteristics of the driver characteristics 201 include at least one of person characteristics, setting characteristics, and driving characteristics. The extraction processing unit 312 extracts driver candidates who are drivers who are the same as or similar to the acquired driving characteristics from among the past driving characteristics of the drivers.
[0089] The extracted information on the driver candidates is, for example, facial information of the driver linked to the driving characteristics. Alternatively, if information that can identify an individual is linked to the past driving characteristics in the driver characteristics DB20, that information may be extracted as the driver candidate information. The information that can identify an individual is, for example, a driver's license number, a personal number, a membership number, etc. If the extraction processing unit 302 cannot extract a driver candidate, the extraction result will be "no driver candidate."
[0090] The driver verification system 31 may receive the driving characteristics of the driver of the vehicle via the driver characteristics DB 20, in addition to the vehicle system 10.
[0091] The operation of the driver verification system 31 according to the third embodiment will be described with reference to the drawings. Fig. 20 is a flowchart showing an example of the operation of the driver verification system 31 according to the third embodiment.
[0092] The driver verification system 31 receives the driving characteristics of the driver of the vehicle transmitted from the vehicle system 10, and the extraction processing unit 312 acquires the driving characteristics of the driver (step S401). The extraction processing unit 312 collates the acquired driving characteristics of the driver with the driving characteristics of past drivers stored in the driver characteristics DB 20 (step S402). The extraction processing unit 312 extracts driver candidates who are candidates for the driver of the vehicle from the past drivers (step S403).
[0093] (Effects of the third embodiment) According to the driver verification system 31 of the third embodiment, it is possible to appropriately extract candidate drivers of a vehicle. This is because the driver characteristic acquisition unit 311 acquires driving characteristics of a driver who drives a vehicle from the vehicle system 10, and the extraction processing unit 312 compares the acquired driving characteristics with driving characteristics of past drivers to extract candidate drivers from past drivers.
[0094] (Hardware configuration) FIG. 21 is a diagram showing an example of a hardware configuration of a computer. The driver verification systems 30 and 31 are realized by executing a program (software program, computer program) in a CPU 91 of a computer 90 shown in FIG. 21. The same applies to the vehicle systems 10 and 11 and the driver characteristic system 21. The function of the driver verification system 30 is realized by executing a program. Any of the functions of the driver verification systems 30 and 31 may be configured in an external device (not shown) and provided to the driver verification system 30 from the external device via a network. The configuration of the driver verification systems 30 and 31 may be realized by a CPU (Central Processing Unit) 91 reading a program 94 from a ROM (Read Only Memory) 92 or a storage device 95 and executing the read program 94 using the CPU 91 and a RAM (Random Access Memory) 93. The present disclosure described using the above-mentioned embodiment as an example can be considered to be configured by a code representing a computer program or a computer-readable storage medium in which the code representing the computer program is stored. The computer-readable storage medium is, for example, the storage device 95, a removable magnetic disk medium (not shown), an optical disk medium, or a memory card. Note that the configuration of each embodiment may be a dedicated hardware using an integrated circuit. The driver verification systems 30 and 31 may be realized by cloud computing.
[0095] The present disclosure is not limited to the above-described embodiments, and various modifications are possible. The technical scope of the present disclosure also includes embodiments obtained by appropriately combining the configurations, operations, and processes disclosed in different embodiments.
[0096] The present disclosure is not limited to the above-described embodiment. That is, the present disclosure can be applied in various aspects that can be understood by a person skilled in the art within the scope of the present disclosure.
[0097] (Additional Note) [Appendix 1] A driver characteristic acquisition means for acquiring driving characteristics related to the driving of a driver of a vehicle; and an extraction processing means for extracting driver candidates from the past drivers by comparing the acquired driving characteristics with the driving characteristics of past drivers. Driver matching system. [Appendix 2] The vehicle further includes an identification processing unit for identifying the driver by face authentication using face information of the driver of the vehicle. 2. A driver verification system as described in claim 1. [Appendix 3] and an output processing means for comparing the identified driver or the extracted driver candidate with a reserving person included in the reservation information of the vehicle and notifying the comparison result. 4. A driver verification system as described in claim 2. [Appendix 4] The output processing means compares the extracted driver candidate with the reserved person when the face authentication fails. 4. A driver verification system as described in appended claim 3. [Appendix 5] The output processing means prioritizes the specified driver when comparing the specified driver and the extracted driver candidates with the reserving driver. 4. A driver verification system as described in appended claim 3. [Appendix 6] The driving characteristics are person characteristics that indicate the characteristics of the driver in the driver's seat of the vehicle. 6. A driver verification system according to any one of claims 1 to 5. [Appendix 7] The person feature is a face position of the driver in the vehicle or a driving posture. 7. A driver verification system as described in appended claim 6. [Appendix 8] The person characteristics are the habits and behaviors of the driver in the vehicle. 7. A driver verification system as described in appended claim 6. [Appendix 9] The driving characteristics are setting characteristics indicating characteristics of the setting of the vehicle by the driver. 6. A driver verification system according to any one of claims 1 to 5. [Appendix 10] The set feature is the position of the rearview mirror or door mirror set by the driver, or the position of the seat. 10. A driver verification system as described in claim 9. [Appendix 11] The driving characteristics are driving characteristics that indicate characteristics of vehicle driving by the driver. 6. A driver verification system according to any one of claims 1 to 5. [Appendix 12] The driving characteristics are operation characteristics indicating at least one of acceleration, braking, and steering characteristics by the driver. 12. A driver verification system as described in claim 11. [Appendix 13] The identification processing means identifies the driver based on identification information acquired from an authentication medium in the vehicle. 4. A driver verification system as described in claim 2. [Appendix 14] Acquire driving characteristics related to the driving of a driver of a vehicle; A driver verification method comprising: verifying the acquired driving characteristics with the driving characteristics of past drivers; and extracting driver candidates from the past drivers. [Appendix 15] Acquire driving characteristics related to the driving of a driver of a vehicle; The acquired driving characteristics are compared with the driving characteristics of past drivers to extract driver candidates from the past drivers. A storage medium that stores a program that causes a computer to execute the following: [Appendix 16] A vehicle sensor that generates sensor data related to a driver's driving in the vehicle; and a driver characteristic generating means for generating driving characteristics of the driver based on the generated sensor data. Vehicle systems. [Appendix 17] A vehicle sensor that generates sensor data related to a driver's driving in the vehicle; A sensor data management means for transmitting the generated sensor data to a driver characteristic system that generates driving characteristics related to the driving of the driver. Vehicle systems. [Appendix 18] A driver characteristic generating means for generating driving characteristics related to the driving of a driver based on sensor data related to the driving of the driver in a vehicle; A driver characteristic database for storing the generated driving characteristics is provided. Driver Feature System. [Explanation of symbols]
[0098] 10, 11 Vehicle Systems 20 Driver characteristics DB 21 Driver Feature System 30, 31 Driver Verification System 40 Matching DB 110 Vehicle Sensor 111 people sensor 112 Setting sensor 113 Travel sensor 120 Driver feature generation unit 121 Human Feature Generation Unit 122 Setting feature generation unit 123 Driving feature generation unit 130 Sensor Data Management Unit 301 Identification processing unit 302 Extraction processing unit 303 Output Processing Unit 401 Face Information 402 Reservation Information 404 Reservation Information
Claims
1. An identification processing means for identifying a driver of a vehicle by face authentication using face information of the driver; a driver characteristic acquisition means for acquiring driving characteristics related to the driving of the driver in the vehicle when the driver is not identified by face authentication; An extraction processing means for extracting driver candidates from the past drivers by comparing the acquired driving characteristics with the driving characteristics of past drivers; an output processing means for notifying an alert that the driver of the vehicle is different from the reserving person included in the reservation information of the vehicle when the driver is identified by face recognition and the identified driver is different from both the reserving person and the person who may drive on behalf of the reserving person; A driver verification system comprising:
2. A driver matching system as described in Claim 1, wherein the output processing means compares the identified driver or extracted driver candidate with a reservation holder included in the vehicle reservation information and notifies the comparison result.
3. A driver matching system as described in Claim 1, wherein the output processing means compares the identified driver or extracted driver candidate with the reservation person and the person riding in the vehicle contained in the vehicle reservation information, and notifies the comparison result.
4. The driver verification system according to claim 2 , wherein the output processing means compares the extracted driver candidate with the reserved driver when the driver is not identified in the face authentication.
5. The driver verification system according to claim 2 , wherein the output processing means prioritizes the identified driver when comparing the identified driver and the extracted driver candidates with the reserving driver.
6. Identifying a driver of a vehicle by face recognition using facial information of the driver; If the driver is not identified by face recognition, acquiring driving characteristics related to the driving of the driver in the vehicle; The acquired driving characteristics are compared with the driving characteristics of past drivers to extract driver candidates from the past drivers; A driver verification method that, when a driver is identified by facial recognition and the identified driver is different from either the person who made the reservation included in the reservation information for the vehicle or a person who may drive on behalf of the person who made the reservation, issues an alert to the effect that the driver of the vehicle is different from the person who made the reservation.
7. Identifying a driver of a vehicle by face recognition using facial information of the driver; If the driver is not identified by face recognition, acquiring driving characteristics related to the driving of the driver in the vehicle; The acquired driving characteristics are compared with the driving characteristics of past drivers to extract driver candidates from the past drivers; When a driver is identified by facial recognition and the identified driver is different from either the person who made the reservation included in the reservation information for the vehicle or the person who may drive on behalf of the person who made the reservation, a program that causes a computer to execute the following to notify an alert that the driver of the vehicle is different from the person who made the reservation.
Citation Information
Patent Citations
Personal authentication apparatus, personal authentication method and passage control apparatus using biometric matching
JP2005202730A
Apparatus and method for supporting right-turn action
JP2006178684A
Device and method for identifying vehicle driver
JP2013095291A
Driver specifying system
JP2015071319A
Driving support device
JP2018136921A
