Method for prompting a vehicle driver to avoid microsleep

Abstract

The present invention proposes a method for prompting a vehicle driver (1) to park the vehicle (100) and take a power nap within a predetermined timespan, in case A) a Telematics service unit (20) determines that a microsleep of the driver (1) is possible in the near future, wherein the determination is made by processing information from the tacho reader (40) of the vehicle (100) so as to receive a remaining allowed driving time of the driver (1), and by processing ADAS system (10) information of the vehicle (100) regarding driver's drowsiness, and / or information regarding traffic and / or weather and / or information regarding time of the day. Alternatively, the present invention proposes a method for prompting a vehicle driver (1) to park the vehicle (100) and take a power nap within a predetermined timespan in case B) a Telematics service unit (20) of the vehicle (100) determines that a forthcoming man- datory break cannot be executed when keep travelling the actual route, wherein the determination is made by processing information from the tacho reader (40) so as to receive a remaining allowed driving time of the driver (1), and by processing infor- mation regarding traffic and / or weather and / or information regarding time of the day.

Description

[0001] Method for prompting a vehicle driver to avoid microsleep

[0002] In current vehicles, systems are already present to support a vehicle driver. Such systems are summarized as vehicle’s advanced driver’s assistance system, shortly ADAS. Part of ADAS are e.g. an Autonomous Emergency Braking (AEB) system, a Forward Collision Warning (FCW) system, an Adaptive Cruise Control (ACC), a Lane Departure Warning System (LDW), a Lane Keeping Assistant (LKA), a Blind Spot Detection (BSD) system, a Driver Drowsiness Attention Warning (DDAW) etc. Such systems recognize the environment, determine driving situation and autonomously operate actuators in the vehicle in order to execute e.g. braking, keeping a predetermined distance etc. Such systems take over from the driver in case it is determined that the current driving situation needs to be controlled, as suggested e.g. in patent application US 2021 0 300 430 A1.

[0003] Since the assistance systems can still be improved, the invention aims to provide a method for prompting the driver to take a power nap in different situations to avoid micro sleeping and / or where driver’s drowsiness might emerge.

[0004] To solve this object, the present invention proposes a method for prompting a vehicle driver to park the vehicle and take a power nap within a predetermined timespan, in case A) a Telematics service unit determines that a microsleep of the driver is possible in the near future, wherein the determination is made by processing information from the tacho reader of the vehicle so as to receive a remaining allowed driving time of the driver, and by processing ADAS system information of the vehicle regarding driver’s drowsiness, and / or information regarding traffic and / or weather and / or information regarding time of the day. Alternatively, the present invention proposes a method for prompting a vehicle driver to park the vehicle and take a power nap within a predetermined timespan in case B) a Telematics service unit of the vehicle determines that a forthcoming mandatory break cannot be executed when keep travelling the actual route, wherein the determination is made by processing information from the tacho reader so as to receive a remaining allowed driving time of the driver, and by processing information regarding traffic and / or weather and / or information regarding time of the day.

[0005] In one embodiment, in case the driver does not park the vehicle within a predefined timespan, the fleet management is informed.

[0006] In one embodiment, processing information from the tacho reader includes at least elapsed driving time of the driver in order to calculate a remaining time to a next mandatory break.

[0007] In one embodiment, wherein in case A) information regarding traffic includes at least traffic density and / or velocity on the actual route.

[0008] In one embodiment, in case A) information from the ADAS includes information whether drowsiness or inattention of the driver is detected, and if this is the case and at least the remaining driving time exceeds a threshold value, microsleep is detected as being possible and the vehicle prompts the driver to park the vehicle and take a power nap within a predetermined timespan.

[0009] In one embodiment, in case B) further information regarding traffic, including at least traffic density and / or velocity on the actual route, and / or weather information and / or information regarding time of the day are used for determining whether the driver is going to violate a forthcoming mandatory break time.

[0010] In one embodiment, the Telematics service unit suggests one or more nearby possible locations for the driver to park the vehicle.

[0011] Further, a commercial vehicle is proposed, comprising a human machine interface adapted to prompt a message to a driver of the vehicle, and a Telematics service unit, which is adapted to receive information from inside and / or outside the vehicle, and which is configured to process the information according to the described method. Also, a computer program product is proposed, comprising instructions, which, when the program is executed by a processing unit, cause the processing unit to carry out the steps of the described method.

[0012] Also, a Telematics service unit adapted to execute the computer program is proposed.

[0013] For a more complete understanding of the invention, the invention will now be described in detail with reference to the accompanying drawings. The detailed description will illustrate and describe what is considered as preferred embodiments of the invention. It should of course be understood that various modifications and changes in form or detail could readily be made without departing from the spirit of the invention. It is therefore intended that the invention may not be limited to the exact form and detail shown and described herein, nor to anything less than the whole of the invention disclosed herein and as claimed herein after. Further, the features described in the description, the drawings and the claims disclosing the invention may be essential for the invention considered alone or in combination. In particular, any reference signs in the claims shall not be construed as limiting the scope of the invention.

[0014] In the accompanying drawings,

[0015] Figure 1 shows a diagram of the detailed working principle of the method according to one aspect of the invention;

[0016] Figure 2 shows a diagram of the detailed working principle of the method according to another aspect of the invention; and

[0017] Figure 3 shows a commercial vehicle according to an aspect of the invention.

[0018] While the present disclosure is subject to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and will herein be described in detail. The invention should be understood to not be limited to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure. The invention focuses on improving vehicle 100 and driver 1 safety by prompting a driver 1 of a vehicle 100 to take a power nap in different situations where driver’s 1 drowsiness might emerge.

[0019] Driver 1 drowsiness detection is a safety feature, which is available in many vehicles 100, especially in commercial vehicles 100, as shown in Figure 3. Though the system is available in all vehicles100, still drowsy driving is prevalent. State-of-the-art ADAS already has a feature that warns drivers 1 when it detects them to be drowsy or sleepy. Such system is reactive, meaning it warns the driver 1 after the driver 1 has acted due to his drowsiness. Also, systems react in case a driver does not, e.g. because of drowsiness. Such systems are e.g. AEB, LDW, LKA, FCW, as already mentioned earlier.

[0020] At the moment, driver 1 drowsiness and attention warning systems work independently without the knowledge of actual drive time of the driver 1 , which is received from time card / tacho reader in order to monitor the driving patterns of the driver 1 and verify that regulations regarding allowed driver 1 driving hours and breaks in between drives are not violated, i.e. that the driver 1 executes mandatory breaks. Hence, it is an aim of the present invention to connect at least those two systems (attention warning systems and drive time information) in order to assist the driver 1 to avoid microsleep by requesting the driver 1 to park the vehicle 100 and take a short power nap when determining that microsleep is possible in the near future. Microsleep is dangerous and close to undetectable without sophisticated systems.

[0021] In one aspect of the invention, possible microsleep is modelled with the help of driving pattern data from warning and safety control features of ADAS 10 ECU. Detecting microsleep is difficult without corresponding systems that are designed to do so.

[0022] According to the invention, existing warning and safety systems are used to devise a method to detect microsleep patterns and prompt the driver 1 at right instance to avoid the same. The invention uses those system outputs and builds upon their solutions in order to increase the overall safety for the driver 1 and the vehicle 100, thereby contributing to safer operations for fleets. The method as shown in Figure 1 is conducted as follows. Vehicle’s 100 ADAS 10 monitors driver 1 drowsiness (arrow DD). Also, ADAS 10 CAN interface (Controller Area Network) is connected to Telematics service units 30 CAN interface and broadcasts (arrow BC) driver 1 inattention status e.g. from AEB, DDAW, LDW to Telematics service unit 30. Telematics service unit 30 extracts the status from the CAN bus. This information is used for the method as described in the following.

[0023] Further, in a first step S1 , Telematics service unit 30 (its ECU) collects driver 1 driving information from the tacho reader 40 of the vehicle 100. Based on this information, Telematics service unit 30 checks if the driver 1 needs to take a break within the near future by e.g. checking if the driving time is within a predefined timespan or whether driver 1 needs to take a break within a predetermined timespan. This is the case if the remaining allowed driving time, which may e.g. be acquired based on an elapsed driving time, is shortly before an end, e.g. 2 or 3 hours before the end.

[0024] In an optional second step S2, Telematics service unit 30 obtains route information from third party systems 20 such as a fleet management (system), and route data and traffic information from third party systems 20 such as a map provider. The map may be provided by the fleet management system as well. Optionally, Telematics service unit 30 considers weather information and / or time of day, which might also be received from third party systems 20. For example, if the time of day is e.g. two hours before sunset time and e.g. weather it is also cloudy or rainy or snowy, driver 1 drowsiness might emerge faster than with good weather conditions and in the middle of the day. Also, Telematics service unit 30 obtains the route data and traffic information from third party systems 20 such as e.g. a map provider.

[0025] In a third step S3, based on all received information, Telematics service unit 30 calculates a driver 1 inattention score by multiplying parameter weights to each parameter listed above and summing them together. The weighing factor of each parameter is preferably preset by e.g. the fleet management based on experience or based on preferences regarding the parameters. Hence, Telematics service unit 30 calculates a normalized inattention score of the driver 1 . Also, in the third step S3, Telematics service unit 30 checks if the score regarding ADAS 10 information on driver 1 drowsiness crosses a threshold score, e.g. set by fleet management.

[0026] In a fourth step S4, if the inattention score is beyond a certain threshold as set e.g. by the fleet management, the Telematics service unit 30 requests (“A” in Figure 3) the driver 1 to park the vehicle 100 at a nearest spot and take a break from driving, since a too high possibility of microsleep in the near future has been detected. It may also suggest to take a power nap by e.g. setting a timer for e.g. 15 minutes.

[0027] Optionally in a fifth step S5, Telematics service unit 30 notifies the fleet management in case the driver 1 has not stopped the vehicle 100 within a timespan set e.g. by the fleet management after the prompt has been output by the vehicle 100.

[0028] In another aspect of the invention, microsleep shall be prevented by prompting the driver to take a power nap in case it is determined that he is going to violate the maximum allowed driving time if he keeps driving the same route. One of the reasons for such a violation could be that driver 1 is going to be caught in traffic and hence not be able to take a mandatory break in between drives at a stipulated time (end of allowed driving time).

[0029] In this aspect of the invention, the driver’s 1 driving time is monitored by the Telematics service unit 30, which also calculates whether the driver 1 would be able to meet a forthcoming, regulated break if he keeps travelling on the same route. If the system calculates a low probability of being able to meet the necessary break time, the system prompts the driver 1 to park the vehicle 100 and take a power nap by e.g. setting a timer for e.g. 15 minutes. Hence, the driver 1 receives information beforehand that his breaktime will be affected due to traffic in his driving route and that thus the possibility of microsleep is rising.

[0030] The method is shown in Figure 2 and is conducted as follows. In a first step S1 , the Telematics service unit 30 (its ECU) collects driver 1 driving information from the tacho reader 40 of the vehicle 100. Such information includes at least elapsed driving time, which is needed to calculate a remaining allowed driving time. Telematics service unit 30 then calculates the next mandatory break for the driver 1 based on the tacho reader 40 information.

[0031] In a second step S2, Telematics service unit 30 also collects the vehicle 100 route from the fleet management server. Telematics service unit 30 obtains the route data and traffic information from e.g. a map provider in order to pre-calculate and predict the driving time to the next planned location for taking a break based on the actual traffic conditions. Additionally, Telematics service unit 30 considers the time of day and / or traffic (real-time) and / or weather information. For example, if the time of day is e.g. two hours before sunset time and e.g. whether it is also cloudy or rainy or snowy, driver 1 drowsiness might emerge faster than with good weather conditions and in the middle of the day in case a mandatory break cannot be met.

[0032] Based on all received information, in a third step S3, Telematics service unit 30 calculates a probability score of not being able to meet the next mandatory break by multiplying parameter weights to each parameter listed above and summing them together. The weighing factor of each parameter is preferably preset by e.g. the fleet management based on experience or based on preferences regarding the parameters. Based on the result (crossing a threshold score or not), Telematics service unit 30 determines whether the driver 1 is going to miss a mandatory break, i.e. violate driving time.

[0033] If the Telematics service unit 30 determines that the driver 1 needs to maintain a break from his driving in the near future, but the route he is travelling experiences too much traffic which would render the break impossible on time, Telematics service unit 30 notifies the driver 1 in a fourth step S4 to take a break and also try to get a power nap in the near future. The determination is done by checking whether the calculated probability score is crossing a threshold.

[0034] In an embodiment, Telematics service unit 30 system suggests the driver 1 to take a power nap by setting a timer for e.g. 15 minutes and providing an alarm after elapse of that time period. In an embodiment, Telematics service unit 30 also suggests one or more nearby possible rest stops, cafes or parking lots for the driver 1 to safely park the vehicle 100.

[0035] Additionally, the Telematics service unit 30 notifies the fleet management (step S5) in case the driver 1 has not stopped the vehicle 100 within a predetermined timespan after the prompt has been output by the vehicle 100.

[0036] In all aspects of the present invention, prompting the driver 1 can be done via a human machine interface HMI, e.g. by displaying a message on a display within the vehicle 100 and / or by a speech message. The display may be part of the infotainment system of the vehicle. In another embodiment the display may be part of the Telematics service unit 30.

[0037] The invention is specifically directed to the operation of commercial vehicles 100 and operators of commercial vehicles 100, which have several vehicles 100 (fleet of vehicles) and drivers 1 and can thus use the information acquired from their vehicles 100 in order to improve safety of their drivers 1 and lifetime of their vehicles 100.

[0038] In all embodiments, the Telematics service unit 30 is a computer-based system within the vehicle 100, which is connected to all vehicles of a fleet, receives information from those vehicles as well as from (external) third party systems 20 such as described above in order to at least analyze the information and provide it to the fleet operator for further processing.

[0039] Reference numerals

[0040] 1 driver

[0041] 10 ADAS

[0042] 20 third party systems

[0043] 30 Telematics service unit

[0044] 40 tacho reader

[0045] HMI human machine interface

[0046] 100 vehicle

Claims

io claims1 . A method for prompting a vehicle (100) driver (1 ) to park the vehicle (100) and take a power nap within a predetermined timespan,A) in case a Telematics service unit (30) determines that a microsleep of the driver (1 ) is possible in the near future, wherein the determination is made by processing information from the tacho reader (40) of the vehicle (100) so as to receive a remaining allowed driving time of the driver (1 ), and by processing ADAS (10) system information of the vehicle (100) regarding driver’s (1 ) drowsiness, and / or information regarding traffic and / or weather and / or information regarding time of the day, or- in case B) a Telematics service unit (30) of the vehicle (100) determines that a forthcoming mandatory break cannot be executed when keep travelling the actual route, wherein the determination is made by processing information from the tacho reader (40) so as to receive a remaining allowed driving time of the driver (1 ), and by processing information regarding traffic and / or weather and / or information regarding time of the day.

2. A method according to claim 1 , wherein in case the driver (1) does not park the vehicle (100) within a predefined timespan, a third party system (20), in particular a fleet management system, is informed.

3. A method according to claim 1 or 2, wherein processing information from the tacho reader (40) includes at least elapsed driving time of the driver (1 ) in order to calculate a remaining time to a next mandatory break.

4. A method according to any one of the preceding claims, wherein in case A) information regarding traffic includes at least traffic density and / or velocity on the actual route.

5. A method according to any one of the preceding claims, wherein in case A) information from the ADAS (10) includes information whether drowsiness or inattention of the driver (1 ) is detected, and if this is the case and at least the remaining driving time exceeds a threshold value, microsleep is detected as being possible and thevehicle prompts the driver (1 ) to park the vehicle (100) and take a power nap within a predetermined timespan.

6. A method according to any one of the preceding claims, wherein in case B) further information regarding traffic, including at least traffic density and / or velocity on the actual route, and / or weather information and / or information regarding time of the day are used for determining whether the driver (1 ) is going to violate a forthcoming mandatory break time.

7. A method according to any one of the preceding claims, wherein the Telematics service unit (30) suggests one or more nearby possible locations for the driver (1 ) to park the vehicle (100).

8. Commercial vehicle (100), comprising- a human machine interface (HMI) adapted to prompt a message to a driver (1 ) of the vehicle (100), and- a Telematics service unit (30), which is adapted to receive information from inside and / or outside the vehicle (100), and which is configured to process the information according to the method according to any one of the preceding claims.

9. A computer program product comprising instructions, which, when the program is executed by a Telematics service unit (30), cause the processing unit to carry out the steps of the method of claims 1 to 7.

10. Telematics service unit (30) adapted to execute the computer program according to claim 9.

Images