Driver estimation device, control method, program and storage medium

Abstract

To provide a driver estimation device that can estimate a driver as needed.SOLUTION: A communication part 27 of a navigation device 2 receives heart rate data Dh including time-sequence measurement data of a heart rate of an occupant from a wearable terminal 1 worn by the vehicle occupant. A control part 21 of the navigation device 2 estimates if the occupant is a vehicle driver based on the occupant heart rate data Dh received by the communication part 27.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a technique for estimating a driver. [Background technology]

[0002] Conventionally, there are known techniques for authenticating a driver when starting to drive a vehicle. For example, Patent Document 1 discloses a technique for authenticating a driver when starting to drive a vehicle by accepting input of the driver's name through an input device such as a touch screen or by performing biometric authentication such as a fingerprint. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2011-242190 A Summary of the Invention [Problem to be solved by the invention]

[0004] The driving support device described in Patent Document 1 performs driver authentication only when driving starts. Therefore, with the technology in Patent Document 1, if the driver changes during the route, the current driver cannot be correctly identified.

[0005] The present invention has been made in order to solve the above-mentioned problems, and has as its main object to provide a driver estimation device capable of estimating a driver at any time. [Means for solving the problem]

[0006] The invention described in the claims is a driver estimation device comprising: a receiving unit that receives data relating to a heart rate or pulse from a terminal worn by a vehicle occupant and measures the heart rate or pulse of the occupant; and an estimation unit that estimates whether the occupant is the driver of the vehicle based on the data relating to the heart rate or pulse.

[0007] The invention described in the claims is a wearable driver estimation device comprising: an entry detection unit that detects when a wearer of the driver estimation device has entered a vehicle; a measurement unit that measures the heart rate or pulse of the wearer and generates data relating to the heart rate or pulse when the entry detection unit detects that the wearer has entered the vehicle; and an estimation unit that estimates whether the wearer is the driver of the vehicle based on the data relating to the heart rate or pulse.

[0008] The invention described in the claims is a control method executed by a driver estimation device, characterized in that it includes a receiving process of receiving data relating to a heart rate or pulse from a terminal worn by a vehicle occupant and measuring the heart rate or pulse of the occupant, and an estimation process of estimating whether the occupant is the driver of the vehicle based on the data relating to the heart rate or pulse. The invention described in the claims is a control method executed by a wearable driver estimation device, comprising: a boarding detection step of detecting that a wearer of the driver estimation device has boarded a vehicle; a measurement step of measuring the wearer's heart rate or pulse when it is detected that the wearer has boarded the vehicle, and generating data relating to the heart rate or pulse; and an estimation step of estimating whether the wearer is the driver of the vehicle based on the data relating to the heart rate or pulse.

[0009] The invention described in the claims is a program executed by a computer, which causes the computer to function as a receiving unit that receives data regarding the heart rate or pulse from a terminal worn by a vehicle occupant and measures the heart rate or pulse of the occupant, and an estimation unit that estimates whether the occupant is the driver of the vehicle based on the data regarding the heart rate or pulse. The invention described in the claims is a program executed by a wearable driver estimation device, which causes the driver estimation device to function as an input detection unit that detects when a wearer of the driver estimation device has entered a vehicle, a measurement unit that measures the wearer's heart rate or pulse and generates data related to the heart rate or pulse when the input detection unit detects that the wearer has entered a vehicle, and an estimation unit that estimates whether the wearer is the driver of the vehicle based on the data related to the heart rate or pulse. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a schematic diagram of a driver estimation system. [Diagram 2] 4 is an example of a driver characteristic map. [Diagram 3] 10 is a flowchart showing an example of a procedure for a driver estimation process. [Figure 4] FIG. 1 is a schematic diagram of a driver estimation system when multiple wearable devices are present in a vehicle. [Diagram 5] 10 is a flowchart showing an example of a procedure of a driver estimation process according to a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] In one preferred embodiment of the present invention, the driver estimation device includes a receiving unit that receives data regarding the heart rate or pulse from a terminal worn by a vehicle occupant and measures the heart rate or pulse of the occupant, and an estimation unit that estimates whether the occupant is the driver of the vehicle based on the data regarding the heart rate or pulse.

[0012] The driver estimation device includes a receiving unit and an estimation unit. The receiving unit receives data on the heart rate or pulse of a vehicle occupant from a terminal worn by the vehicle occupant. The estimation unit estimates whether the occupant is a driver of the vehicle based on the data on the heart rate or pulse of the occupant received by the receiving unit. In this aspect, the driver estimation device receives data on the heart rate or pulse from the terminal worn by the occupant and estimates whether the occupant is a driver based on the data. In general, the driver of the vehicle and the occupant who is not driving the vehicle have different tensions and stress states due to safety confirmation, etc., so that a difference occurs in the behavior of the heart rate or pulse. Therefore, the driver estimation device can estimate at any time whether the occupant wearing the terminal is a driver by this aspect.

[0013] In one aspect of the driver estimation device, the data on the heart rate or pulse is time series data of the passenger's heart rate or pulse, and the estimation unit estimates whether the passenger is the driver of the vehicle based on the tendency of change in the passenger's heart rate or pulse identified from the time series data of the heart rate or pulse. In general, the driver of a vehicle and a passenger who is not driving the vehicle are in a different state of tension or stress due to safety confirmation, etc., so there is a difference in the tendency of change in the time series of the heart rate or pulse. Therefore, with this aspect, the driver estimation device can suitably estimate whether the passenger wearing the terminal is the driver.

[0014] In another aspect of the driver estimation device, the receiving unit receives data on the heart rate or pulse from the terminals worn by the passengers, and the estimation unit estimates whether each of the passengers is the driver of the vehicle based on the data on the heart rate or pulse received from each terminal. In this way, even if there are multiple passengers in the vehicle, the driver estimation device can estimate the driver based on the heart rate or pulse data transmitted from each terminal.

[0015] In another aspect of the driver estimation device, the estimation unit estimates whether the passenger is the driver of the vehicle based on the data on the heart rate or pulse rate and at least one of the vehicle's running state or the type of road on which the vehicle is traveling. In general, the behavior of the driver's heart rate or pulse rate differs depending on the vehicle's running state and / or the type of road on which the vehicle is traveling. Therefore, with this aspect, the driver estimation device can more accurately estimate whether the passenger is the driver.

[0016] In another aspect of the driver estimation device, the estimation unit estimates the driver of the vehicle when the vehicle is stopped for a predetermined time. The "predetermined time" is set based on an experiment or the like, for example, on the time required for a driver to be changed. With this aspect, the driver estimation device estimates the driver of the vehicle when there is a possibility that the driver has been changed, and can accurately estimate the new driver even if the driver has been changed.

[0017] In another aspect of the driver estimation device, the driver estimation device further includes a door opening / closing detection unit that detects whether a door of the vehicle is opened or closed, and the estimation unit estimates the driver of the vehicle when the door of the vehicle is closed. In this aspect, the driver estimation device estimates the driver of the vehicle when the door is opened or closed, since there is a possibility that the driver has been changed. As a result, even if the driver has been changed, the driver after the change can be accurately estimated.

[0018] In another aspect of the driver estimation device, when the estimation unit estimates that the passenger is the driver of the vehicle based on the data on the heart rate or pulse, the estimation unit accumulates the data on the heart rate or pulse in a storage unit, and when the receiving unit receives the data on the heart rate or pulse, if the data on the heart rate or pulse is stored in the storage unit, the estimation unit estimates whether the passenger is the driver of the vehicle based on the data on the heart rate or pulse received by the receiving unit and the data on the heart rate or pulse stored in the storage unit. With this aspect, when the same driver repeatedly rides in the vehicle, it is possible to speed up the driver estimation process and improve the estimation accuracy.

[0019] In another embodiment of the present invention, a wearable driver estimation device includes an onboarding detection unit that detects that a wearer of the driver estimation device has boarded a vehicle, a measurement unit that measures a heart rate or pulse of the wearer and generates data related to the heart rate or pulse when the onboarding detection unit detects that the wearer has boarded the vehicle, and an estimation unit that estimates whether the passenger is a driver of the vehicle based on the data related to the heart rate or pulse. With this aspect, the driver estimation device can estimate at any time whether the wearer is a driver by measuring the heart rate or pulse.

[0020] In yet another embodiment of the present invention, a control method executed by a driver estimation device includes a receiving step of receiving data related to a heart rate or a pulse rate from a terminal worn by a vehicle occupant and measuring the heart rate or a pulse rate of the occupant, and an estimation step of estimating whether the occupant is a driver of the vehicle based on the data related to the heart rate or the pulse rate. By executing this control method, the driver estimation device can estimate at any time whether the occupant wearing the terminal is a driver or not.

[0021] In yet another embodiment of the present invention, a program executed by a computer causes the computer to function as a receiving unit that receives data related to a heart rate or pulse from a terminal worn by a vehicle occupant and measures the heart rate or pulse of the occupant, and an estimating unit that estimates whether the occupant is a driver of the vehicle based on the data related to the heart rate or pulse. By executing this program, the computer can estimate at any time whether the occupant wearing the terminal is a driver. Preferably, the program is stored in a storage medium. EXAMPLES

[0022] Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings.

[0023] [Driver Estimation System Configuration] Fig. 1 is a schematic diagram of a driver estimation system according to the present embodiment. As shown in Fig. 1, the driver estimation system includes a wearable device 1 worn by a vehicle occupant such as a driver, and a navigation device 2. The wearable device 1 and the navigation device 2 perform data communication wirelessly or via a wire (wireless in Fig. 1).

[0024] The wearable device 1 is a wearable terminal that transmits data on the wearer's heart rate (also referred to as "heart rate data Dh") to the navigation device 2 based on a request from the navigation device 2. The wearable device 1 may be a terminal manufactured specifically for this driver estimation system, or may be a general-purpose terminal installed with a program for complying with this driver estimation system.

[0025] The navigation device 2 is a stationary in-vehicle device or a portable terminal such as a PND (Portable Navigation Device) or a smartphone, and performs route guidance to a destination specified by a user. In this embodiment, the navigation device 2 performs a process (also called a "driver estimation process") to determine whether or not the wearer of the wearable device 1 is a driver, based on the heart rate data Dh received from the wearable device 1.

[0026] Next, still with reference to FIG. 1, the configurations of the wearable terminal 1 and the navigation device 2 will be described.

[0027] As shown in FIG. 1, the wearable device 1 mainly includes a control unit 11, a communication unit 12, a heart rate sensor 13, and a storage unit 14. The communication unit 12 performs data communication with the navigation device 2 under the control of the control unit 11. The heart rate sensor 13 measures the heart rate of the wearer of the wearable device 1 under the control of the control unit 11, and supplies the measurement result to the control unit 11. The storage unit 14 saves a program for controlling the operation of the wearable device 1 and holds information necessary for the operation of the wearable device 1. The storage unit 14 also stores identification information unique to the wearable device 1 (also called a "terminal ID"), etc.

[0028] The control unit 11 of the wearable device 1 includes a CPU (not shown) and performs various controls on each component in the wearable device 1. In this embodiment, when the control unit 11 receives a transmission request for heart rate data Dh from the navigation device 2 via the communication unit 12, the control unit 11 transmits time series data of the heart rate measured by the heart rate sensor 13 over a predetermined time span (also referred to as "time series measurement data") and the terminal ID stored in the storage unit 14 as heart rate data Dh to the navigation device 2 via the communication unit 12. The above-mentioned "time series measurement data" is data that allows the measurement time of each heart rate measured in time series to be identified, and is, for example, time series data in which the measured heart rate is associated with time information indicating the time when the heart rate was measured.

[0029] Next, a description will be given of the configuration of the navigation device 2. As shown in Fig. 1, the navigation device 2 mainly includes a control unit 21, a positioning unit 22, a display unit 23 such as a display, a sound output unit 24 such as a speaker, an input unit 25, a storage unit 26, and a communication unit 27.

[0030] The positioning unit 22 is an autonomous positioning device such as a gyro sensor or a distance sensor, a GPS receiver, or the like, and performs positioning of the vehicle's current location, traveling direction, and the like. Output data indicating the measurement results of the measurement unit 22 is stored in the memory unit 26. The display unit 23 displays a map for route guidance, etc., based on the control of the control unit 21. The sound output unit 24 outputs voice guidance for route guidance, a predetermined warning, etc., based on the control of the control unit 21. The input unit 25 is a button, a switch, a touch panel, a voice input device, etc., and supplies input information to the control unit 21. The communication unit 27 transmits a request signal for heartbeat data Dh to the wearable device 1, and receives heartbeat data Dh transmitted from the wearable device 1, based on the control of the control unit 21. The communication unit 27 is an example of a "receiving unit" in the present invention.

[0031] The storage unit 26 stores programs for controlling the operation of the navigation device 2 and holds information necessary for the operation of the navigation device 2. For example, the storage unit 26 stores map data including road data in which road types and the like are registered. The storage unit 26 also stores a map (also called a "driver characteristics map Mp") that records the change characteristics of the driver's heart rate for each combination of the vehicle's driving state and the road type on which the vehicle is traveling. The storage unit 26 also stores the output data of the measurement unit 22 in association with the measurement time, and stores the heart rate data Dh received by the communication unit 27, based on the control of the control unit 21.

[0032] The control unit 21 includes a CPU (not shown) and performs various controls on each component in the navigation device 2. In this embodiment, when the control unit 21 receives heartbeat data Dh from the wearable device 1, the control unit 21 determines whether the wearer of the wearable device 1 is the driver based on the time-series measurement data included in the heartbeat data Dh and the driver characteristic map Mp. When the control unit 21 determines that the wearer of the wearable device 1 is the driver, the control unit 21 stores the terminal ID included in the received heartbeat data Dh in the storage unit 26 as the terminal ID of the wearable device 1 worn by the driver. After that, for example, the control unit 21 transmits a control signal to the wearable device 1 corresponding to the terminal ID stored in the storage unit 26 to instruct the wearable device 1 to execute a predetermined operation to assist the driver in driving. The control unit 21 is an example of the "estimation unit" and the "computer" that executes a program in the present invention.

[0033] [Driver estimation process] Next, the details of the driver estimation process executed by the control unit 21 of the navigation device 2 will be described. In summary, when the time-series change in the heart rate of the wearer of the wearable device 1 indicated by the time-series measurement data of the heart rate data Dh matches the characteristics of the heart rate change of the driver recognized by referring to the driver characteristics map Mp, the control unit 21 estimates that the wearer is the driver. In this case, the control unit 21 accurately recognizes the characteristics of the heart rate change of the driver described above by referring to the driver characteristics map Mp from the traveling state of the vehicle at the time of measuring the heart rate and the type of road on which the vehicle is traveling.

[0034] In the following, first, a driver characteristics map Mp used in the driver estimation process will be described. Fig. 2 shows an example of the driver characteristics map Mp.

[0035] The driver characteristics map Mp shown in Fig. 2 shows the characteristics of the change in the driver's heart rate for each combination of the vehicle's driving state when the heart rate is measured and the type of road on which the vehicle is traveling when the heart rate is measured (road type). The combinations of driving state and road type defined in the driver characteristics map Mp are combinations that cause a difference in the change in heart rate between the driver and passengers other than the driver.

[0036] In the example of FIG. 2, four vehicle driving states are defined: "stopped" corresponding to a state where the vehicle is stopped, "accelerated" corresponding to a state where the vehicle is accelerating, "constant speed" corresponding to a state where the vehicle is driving at a substantially constant speed, and "lane change" corresponding to a state where the vehicle has changed lanes. In addition, in the example of FIG. 2, three types of road types on which the vehicle is driving are defined: "general road", "expressway", and "parking lot". Then, for each combination of the vehicle driving state and road type, the expected change characteristic of the heart rate for the driver of the vehicle (either "increased", "decreased", or "unchanged" in FIG. 2) is recorded. For example, in the example of FIG. 2, when the driving state is "stopped", the heart rate decreases regardless of the road type, and when the driving state is "accelerated", the heart rate increases regardless of the road type. On the other hand, when the driving state is “constant speed”, the heart rate remains unchanged or decreases when the road type is “general road” or “expressway”, and the heart rate remains unchanged or increases when the road type is “parking lot”. Furthermore, when the driving state is “lane change”, the heart rate increases when the road type is “general road” or “expressway”.

[0037] Note that the driver characteristic map Mp in FIG. 2 is merely an example for explaining the present invention, and the driver characteristic map Mp to which the present invention can be applied is not limited to this. For example, the road types defined in the driver characteristic map Mp are not limited to the classification of "general roads," "expressways," and "parking lots." For example, general roads may be further classified into national roads and narrow streets. In another example, the road types defined in the driver characteristic map Mp may be appropriately set for each location where a difference in heart rate change occurs between the driver and passengers other than the driver, such as a point just before an intersection, a point just after passing through an intersection, and a right-turn lane at an intersection. Similarly, the driving conditions defined in the driver characteristic map Mp are not limited to the example in FIG. 2, and may include "right turn" indicating a state when turning right and "left turn" indicating a state when turning left. In this way, the combinations of road types and driving conditions defined in the driver characteristic map Mp are set based on experiments, etc. so as to be combinations that cause a difference in heart rate change between the driver and passengers other than the driver, and the characteristics of the driver's heart rate change for each combination are also set based on experiments, etc.

[0038] Next, a driver estimation method using the driver characteristics map Mp will be described.

[0039] The control unit 21 recognizes the vehicle's running state and the type of road when the heart rate is measured based on the time information of the time-series measurement data included in the heart rate data Dh, and grasps the change characteristics of the driver's heart rate when the heart rate is measured by referring to the driver characteristic map Mp. Then, when the change in the heart rate indicated by the time-series measurement data of the heart rate included in the heart rate data Dh received from the wearable device 1 matches the change characteristics of the driver's heart rate grasped from the driver characteristic map Mp, the control unit 21 stores the terminal ID of the wearable device 1 that transmitted the heart rate data Dh in the storage unit 26 as the terminal ID of the terminal worn by the driver. The control unit 21 recognizes the above-mentioned running state of the vehicle based on the output data of the measurement unit 22 such as an acceleration sensor and a GPS receiver stored in the storage unit 26, and recognizes the above-mentioned type of road based on the trajectory of the running position of the vehicle indicated by the output data of the measurement unit 22 such as a GPS receiver stored in the storage unit 26 and the road data stored in the storage unit 26.

[0040] Generally, the driver of a vehicle and a passenger who is not driving the vehicle are in different states of tension and stress due to safety checks, etc., and therefore there is a difference in the time series change in heart rate while the vehicle is traveling. Taking the above into consideration, the navigation device 2 according to this embodiment stores in advance a driver characteristic map Mp that records the characteristics of the change in the driver's heart rate for each combination of driving state and road type that causes a change in the heart rate specific to the driver. This allows the navigation device 2 to accurately determine whether the wearer of the wearable device 1 that transmitted the heart rate data Dh is the driver, based on the heart rate data Dh received from the wearable device 1.

[0041] [Processing flow] FIG. 3 is a flowchart illustrating an example of a procedure for a driver estimation process.

[0042] First, the navigation device 2 determines whether or not it has detected that the engine switch of the vehicle in which the navigation device 2 is mounted has been turned on (step S101). For example, when power is supplied from the vehicle, or when information that the engine switch has been turned on is received from a control unit (ECU: Electronic Control Unit) of the vehicle via a CAN (Controller Area Network) or the like, the navigation device 2 determines that the engine switch of the vehicle has been turned on.

[0043] Then, when detecting that the engine switch has been turned on (step S101; Yes), the navigation device 2 transmits a request signal for the heart rate data Dh to the wearable device 1 (step S102). In this case, the navigation device 2 may transmit the request signal to an unspecified number of wearable devices by broadcast, or may transmit the request signal to a wearable device 1 with which communication has already been established if such a wearable device 1 is present.

[0044] When the wearable device 1 receives the request signal for the heartbeat data Dh from the navigation device 2, the wearable device 1 measures the heartbeat using the heartbeat sensor 13 (step S103). Then, the wearable device 1 transmits the heartbeat data Dh, which includes time-series measurement data that is time-series data of the heartbeat measured by the heartbeat sensor 13 and the device ID of the wearable device 1, to the navigation device 2 (step S104). Then, the navigation device 2 receives the heartbeat data Dh (step S105).

[0045] Next, the navigation device 2 recognizes the change trend of the heart rate based on the time-series measurement data of the heart rate included in the received heart rate data Dh (step S106).The navigation device 2 also recognizes the traveling state of the vehicle and the type of road traveled at the time when the heart rate was measured (step S107).

[0046] Next, the navigation device 2 determines whether or not it is possible to estimate that the person wearing the wearable device 1 is the driver (step S108). In this case, the navigation device 2 recognizes the change characteristics of the driver's heart rate corresponding to the driving state and driving road type recognized in step S107 by referring to the driver characteristics map Mp, and determines whether or not the change characteristics match the change tendency of the heart rate identified in step S106.

[0047] Then, when the navigation device 2 determines that the wearer of the wearable device 1 can be estimated to be the driver (step S108; Yes), it regards the wearer of the wearable device 1, which is the transmission source of the heartbeat data Dh, as the driver, and stores the device ID included in the heartbeat data Dh in the storage unit 26 (step S109). On the other hand, when the navigation device 2 determines that the wearer of the wearable device 1 cannot be estimated to be the driver based on the change tendency of the measured heart rate (step S108; No), it returns the process to step S102 again, receives the heartbeat data Dh, and determines whether the transmission source of the heartbeat data Dh is the terminal worn by the driver. Note that, when the navigation device 2 cannot estimate that the wearer of the wearable device 1 is the driver in step S108 a predetermined number of times or more, it may determine that the wearer of the wearable device 1 is not the driver, and end the process of the flowchart without executing step S109.

[0048] 3, the wearable device 1 transmits the heartbeat data Dh to the navigation device 2 in step S103 every time a transmission request for the heartbeat data Dh is received in step S102. Alternatively, after a transmission request for the heartbeat data Dh is received once in step S102, the wearable device 1 may repeatedly generate and transmit the heartbeat data Dh until the wearable device 1 receives a notification from the navigation device 2 that the heartbeat data Dh is no longer necessary.

[0049] [When multiple wearable devices are present] Next, a supplementary explanation will be given for the case where multiple wearable devices 1 are present in the vehicle (i.e., multiple passengers are wearing the wearable devices 1). Fig. 4 shows a schematic diagram of the driver estimation system when multiple wearable devices 1 (1A, 1B, ...) are present together with the navigation device 2 in the same vehicle.

[0050] 4, when wearable terminal 1A and wearable terminal 1B receive a request signal for heart rate data Dh from navigation device 2, they transmit the heart rate data Dh including a terminal-specific terminal ID to navigation device 2. Then, based on the heart rate data Dh received from wearable terminal 1A, navigation device 2 determines whether or not the wearer of wearable terminal 1A is a driver, and based on the heart rate data Dh received from wearable terminal 1B, determines whether or not the wearer of wearable terminal 1B is a driver. Then, when navigation device 2 determines that the wearer of either wearable terminal 1A or 1B is a driver, it stores in storage unit 26 the terminal ID of the wearable terminal 1 corresponding to the wearer determined to be a driver.

[0051] In this way, even when multiple wearable devices 1 are present in the vehicle, the navigation device 2 determines whether or not the wearer of each wearable device 1 is the driver based on the heart rate data Dh of each wearable device 1. This allows the navigation device 2 to accurately estimate the driver even when multiple wearable devices 1 are present in the vehicle.

[0052] As described above, the control unit 21 of the navigation device 2 according to this embodiment receives the heart rate data Dh including time-series measurement data of the passenger's heart rate from the wearable device 1 worn by the passenger of the vehicle via the communication unit 27. Then, the control unit 21 estimates whether the passenger is the driver of the vehicle based on the heart rate data Dh of the passenger received by the communication unit 27. In general, the driver of the vehicle and a passenger who is not driving the vehicle are in a different state of tension or stress due to safety checks, etc., and therefore there is a difference in the behavior of their heart rate. Therefore, with this aspect, the navigation device 2 can suitably estimate whether the passenger wearing the wearable device 1 is the driver.

[0053] [Variations] Preferred modifications of the above-described embodiment will be described below. The following modifications may be applied to the above-described embodiment in any combination.

[0054] (Variation 1) The present invention is not limited to driver estimation processing using the driver characteristics map Mp, and driver estimation may be performed without relying on the driver characteristics map Mp by using various known statistical methods such as pattern recognition (including modeling).

[0055] For example, the navigation device 2 performs known learning on time-series data of the heart rates of the driver and passengers other than the driver that have been measured in advance, defines a predetermined feature space, and prescribes each feature amount (feature vector).The navigation device 2 then analyzes the time-series measurement data included in the heart rate data Dh received from the wearable device 1 to extract feature amounts, and compares them with the pre-stored feature amounts of the driver and passengers other than the driver to determine whether the person whose heart rate is being measured is the driver.

[0056] In this case, the navigation device 2 may perform the driver estimation process without using the driver characteristics map Mp based on the road type and the driving state before driving starts, and may perform the driver estimation process of this embodiment based on the road type and the driving state if the driver cannot be authenticated even after the vehicle starts driving. In other words, when multiple driver estimation processes are executable, the navigation device 2 may switch the driver estimation process to be executed depending on the driving situation.

[0057] (Variation 2) When performing driver estimation processing using statistical methods or the like based on variant example 1, the navigation device 2 may accumulate time series measurement data of the heart rate contained in the heart rate data Dh used in the driver estimation processing, and use the time series measurement data as a sample.

[0058] In this case, if the number of times that the navigation device 2 has accumulated the time-series measurement data of the driver's heart rate is less than a predetermined number, the navigation device 2 performs a driver estimation process based on the time-series data of the driver's general heart rate stored in advance in the storage unit 26. Then, when the navigation device 2 estimates that the driver is the driver through the driver estimation process, the navigation device 2 stores the time-series measurement data of the heart rate data Dh used for the estimation in the storage unit 26 as a sample of the driver's heart rate. Then, when the navigation device 2 accumulates samples of the driver's heart rate for a predetermined number of times or more, the navigation device 2 uses the accumulated samples to determine whether the person whose heart rate is being measured is the driver. In this case, for example, the navigation device 2 updates a template or the like that represents the characteristics of the driver's heart rate from the accumulated samples of the driver's heart rate, and determines whether the template and the characteristics of the time-series measurement data included in the received heart rate data Dh approximately match.

[0059] In general, changes in heart rate differ depending on the type (category) of the driver, such as a novice driver, an experienced driver, an elderly driver, etc. In addition, the navigation device 2 is generally used repeatedly by the same driver. Therefore, as described above, the navigation device 2 uses time-series measurement data of the heart rate that is actually measured and accumulated in the driver estimation process, thereby making it possible to more accurately estimate the driver and to shorten the time required for the driver estimation process.

[0060] (Variation 3) The navigation device 2 executes the driver estimation process by referring to the driver characteristics map Mp based on the vehicle's driving state and the road type when the heart rate is measured. Alternatively, the navigation device 2 may execute the driver estimation process based on only one of the vehicle's driving state and the road type when the heart rate is measured.

[0061] In this case, for example, the driver characteristics map Mp specifies the characteristics of changes in the driver's heart rate for either the driving state or the road type. In the driver estimation process, the navigation device 2 recognizes the state or type at the time of measuring the heart rate for either the driving state or the road type specified in the driver characteristics map Mp, and recognizes the characteristics of changes in the driver's heart rate by referring to the driver characteristics map Mp. The navigation device 2 then compares the recognized characteristics of changes in the driver's heart rate with the time-series measurement data of the heart rate included in the heart rate data Dh to determine whether the person whose heart rate is to be measured is the driver.

[0062] (Variation 4) The navigation device 2 may execute the driver identification process again when a predetermined condition is satisfied that indicates that the driver may have been changed, even after the driver has been authenticated.

[0063] For example, when the navigation device 2 detects that the door of the vehicle is opened or closed, it determines that there is a possibility that the driver has been changed. In this case, the navigation device 2 detects the opening or closing of the door of the vehicle by receiving a signal related to the opening or closing of the door from the control unit (ECU) of the vehicle by a protocol such as CAN. Then, when the navigation device 2 detects the opening or closing of the door of the vehicle, it receives the heartbeat data Dh by transmitting a request signal for the heartbeat data Dh to the wearable device 1, and authenticates the driver based on steps S106 to S108 in FIG. 3. Then, when the navigation device 2 determines in step S108 that the wearer of the wearable device 1 having a terminal ID different from the terminal ID previously recorded in step S109 is the driver, it rewrites the record of the terminal ID of the wearable device 1 worn by the driver. Note that, when the navigation device 2 cannot estimate in step S108 that the wearer of the wearable device 1 having the terminal ID previously recorded in step S109 is the driver, the navigation device 2 may erase the terminal ID previously recorded in step S109.

[0064] In another example, when the navigation device 2 detects that the vehicle has started moving after stopping in a parking lot (including a service area or a parking area on a highway) registered in the map data, or when the navigation device 2 detects that the vehicle has started moving after stopping for a predetermined period of time in a location other than a parking lot, the navigation device 2 may determine that the driver may have changed and may perform the driver estimation process again.

[0065] In this way, according to this modification, even if the driver is replaced between when the engine switch is turned on and when it is turned off again, the navigation device 2 can recognize the new driver at any time. Note that the control unit 21 is an example of the "door opening / closing detection unit" in the present invention.

[0066] (Variation 5) The navigation device 2 may receive the heartbeat data Dh via a communication unit (not shown) (also referred to as a "vehicle communication unit") under the control of the vehicle's control unit. In this case, the wearable device 1 and the vehicle communication unit, and the navigation device 2 and the vehicle communication unit, respectively, establish communication, and the vehicle communication unit transfers a transmission request for the heartbeat data Dh received from the navigation device 2 to the wearable device 1, and transfers the heartbeat data Dh received from the wearable device 1 to the navigation device 2.

[0067] (Variation 6) 3, the wearable device 1 transmits the heart rate data Dh in step S104 based on a request to transmit the heart rate data Dh from the navigation device 2. Alternatively, the wearable device 1 may generate the heart rate data Dh and transmit the heart rate data Dh to the navigation device 2 when it recognizes that the wearer has entered the vehicle based on communication with a control unit of the vehicle or based on output of a sensor (not shown) or the like.

[0068] (Variation 7) The control unit (ECU) of the vehicle may execute the driver estimation process executed by the navigation device 2 in this embodiment instead of the navigation device 2.

[0069] In this case, the vehicle control unit exchanges heart rate data Dh and the like with the wearable device 1, for example, via the vehicle communication unit described in Modification 5, and stores the driver characteristic map Mp and the like required for the driver estimation process in a storage unit (not shown). Then, the vehicle control unit executes the processes of steps S101 to S102 and steps S105 to S109 in Fig. 3. In this case, the vehicle communication unit is an example of the "receiving unit" in the present invention, and the vehicle control unit is an example of the "estimation unit" and the "computer" that executes a program in the present invention.

[0070] (Variation 8) The wearable device 1 may execute part or all of the processing of the navigation device 2. For example, the wearable device 1 may determine whether or not a person wearing the device is a driver instead of the navigation device 2, and when it is determined that the wearer is a driver, transmit a terminal ID or the like of the wearable device 1 to the navigation device 2. In another example, the driver estimation system may be composed only of the wearable device 1, and the processing of the navigation device 2 may be executed by the wearable device 1.

[0071] FIG. 5 is an example of a flowchart showing a procedure of a driver estimation process in the case where the wearable terminal 1 executes the process of the navigation device 2 of the embodiment.

[0072] First, the wearable device 1 determines whether or not the wearer has entered the vehicle (step S201). For example, the wearable device 1 determines that the wearer has entered the vehicle when it receives predetermined information from the vehicle control unit, such as information that the engine switch has been turned on or that the door has been opened or closed, or when it detects a predetermined user input. Then, when it detects that the wearer has entered the vehicle (step S201; Yes), the wearable device 1 measures the heart rate (step S202). Then, similar to step S106 in FIG. 3, the wearable device 1 recognizes the tendency of change in the heart rate based on the time-series measurement data of the measured heart rate (step S203).

[0073] Furthermore, the wearable device 1 recognizes the vehicle's running state and road type at the time of measuring the heart rate in order to refer to the driver characteristic map Mp (step S204). In this case, the wearable device 1 may have a positioning unit such as an acceleration sensor or a GPS receiver (not shown) and recognize the running state based on the output of the positioning unit, or may recognize the vehicle's running state by receiving information on a vehicle speed pulse from a control unit of the vehicle. Furthermore, the wearable device 1 recognizes the type of road on which the vehicle is running by receiving, for example, information on a map of the surroundings of the current position recognized by the output of the GPS receiver from a server device (not shown).

[0074] 3, the wearable device 1 determines whether the wearer can be estimated as the driver (step S205). If the wearable device 1 can estimate that the wearer is the driver (step S205; Yes), the wearable device 1 transitions to a mode that assumes that the wearer is a driver (step S206). In this case, the wearable device 1 outputs a predetermined warning, for example, based on the measured heart rate.

[0075] In this way, the wearable device 1 can preferably execute the processing of the navigation device 2 of the embodiment. In this modification, the wearable device 1 is an example of the "driver estimation device" of the present invention, the control unit 11 is an example of the "boarding detection unit" and the "estimation unit" of the present invention, and the heart rate sensor 13 is an example of the "measurement unit" of the present invention.

[0076] (Variation 9) The navigation device 2 may be an in-vehicle device for purposes other than route guidance (for example, a drive recorder, etc.).

[0077] (Variation 10) The wearable device 1 may measure a pulse rate instead of a heart rate, and transmit the time-series measurement data of the pulse rate to the navigation device 2. In this case, the navigation device 2 estimates whether the passenger is the driver of the vehicle based on the time-series measurement data of the pulse rate, similar to the case of the heart rate. In this way, the data that the navigation device 2 receives from the wearable device 1 is not limited to data on the heart rate, and may be data on the pulse rate. The driver of the vehicle and a passenger who is not driving the vehicle are in a different state of tension or stress due to safety confirmation, etc., and therefore, like the heart rate, there is a difference in the behavior of the pulse. Therefore, even in this embodiment, the navigation device 2 can suitably estimate whether the passenger wearing the wearable device 1 is the driver. [Explanation of symbols]

[0078] 1. Wearable devices 2. Navigation devices 11, 21 Control section 12, 27 Communications Department 13 Heart Rate Sensor 14, 26 Storage section 23 Display section 24 Sound output section 25 Input section

Claims

1. A receiving unit that is worn by a vehicle occupant and receives data related to the heart rate or pulse rate from a terminal that measures the heart rate or pulse rate of the occupant; an estimation unit that estimates whether the passenger is a driver of the vehicle based on the data regarding the heart rate or pulse rate; A driver estimation device comprising:

2. The data on the heart rate or pulse is time series data on the heart rate or pulse of the passenger, The driver estimation device according to claim 1, characterized in that the estimation unit estimates whether the occupant is the driver of the vehicle based on a tendency of change in the heart rate or pulse of the occupant identified from the time series data of the heart rate or pulse.

3. The receiving unit receives data related to the heart rate or pulse rate from the terminals worn by each of a plurality of passengers, The driver estimation device according to claim 1 or 2, characterized in that the estimation unit estimates whether each of the multiple occupants is a driver of the vehicle based on the data regarding the heart rate or pulse received for each of the terminals.

4. The driver estimation device according to any one of claims 1 to 3, characterized in that the estimation unit estimates whether the passenger is the driver of the vehicle based on data regarding the heart rate or pulse and at least one of the driving state of the vehicle or the type of road on which the vehicle is traveling.

5. 5. The driver estimation device according to claim 1, wherein the estimation unit estimates the driver of the vehicle when the vehicle is stopped for a predetermined period of time.

6. A door opening / closing detection unit that detects opening / closing of a door of the vehicle is further provided, 6. The driver estimation device according to claim 1, wherein the estimation unit estimates the driver of the vehicle when a door of the vehicle is closed.

7. When the estimation unit estimates that the passenger is the driver of the vehicle based on the data regarding the heart rate or pulse, the estimation unit accumulates the data regarding the heart rate or pulse in a storage unit; The driver estimation device according to any one of claims 1 to 6, characterized in that when the receiving unit receives the data regarding the heart rate or pulse, if there is data regarding the heart rate or pulse stored in the memory unit, the estimation unit estimates whether the occupant is the driver of the vehicle based on the data regarding the heart rate or pulse received by the receiving unit and the data regarding the heart rate or pulse stored in the memory unit.

8. A wearable driver estimation device, an entry detection unit that detects when a person wearing the driver estimation device enters a vehicle; a measurement unit that measures a heart rate or a pulse rate of the wearer when the boarding detection unit detects that the wearer has boarded a vehicle, and generates data related to the heart rate or the pulse rate; an estimation unit that estimates whether the wearer is a driver of the vehicle based on the data regarding the heart rate or pulse rate; A driver estimation device comprising:

9. A control method executed by a driver estimation device, comprising: a receiving step of receiving data relating to a heart rate or a pulse rate from a terminal worn by a vehicle occupant and measuring the heart rate or a pulse rate of the occupant; an estimation step of estimating whether the occupant is a driver of the vehicle based on the data related to the heart rate or pulse rate; A control method comprising the steps of:

10. A control method executed by a wearable driver estimation device, comprising: an entry detection step of detecting that a person wearing the driver estimation device has entered a vehicle; a measuring step of measuring a heart rate or a pulse rate of the wearer when it is detected that the wearer has boarded a vehicle, and generating data relating to the heart rate or the pulse rate; an estimation step of estimating whether the wearer is a driver of the vehicle based on the data regarding the heart rate or pulse rate; A control method comprising the steps of:

11. A program executed by a computer, A terminal worn by a vehicle occupant measures the heart rate or pulse of the occupant, and the heart rate or pulse is measured. A receiving unit for receiving data relating to a pulse rate; Based on the heart rate or pulse data, the occupant is the driver of the vehicle. An estimation part that estimates whether A program for causing the computer to function as a

12. A program executed by a wearable driver estimation device, an entry detection unit that detects when a person wearing the driver estimation device enters a vehicle; a measurement unit that measures a heart rate or a pulse rate of the wearer when the boarding detection unit detects that the wearer has boarded a vehicle, and generates data related to the heart rate or the pulse rate; an estimation unit that estimates whether the wearer is a driver of the vehicle based on the data related to the heart rate or pulse rate; A program for causing the driver estimation device to function as a

Images