SYSTEMS AND METHODS FOR SCHEDULING DRIVER INTERFACE TASKS BASED ON DRIVER WORKLOAD

• US 20130110349A1
• Filed: 07/29/2010
• Published: 05/02/2013
• Est. Priority Date: 07/29/2010
• Status: Active Grant

• Current Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Original Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Inventors: Tseng, Finn, Filev, Dimitar Petrov, Lu, Jianbo, Prakah-Asante, Kwaku O.
• Granted Patent: US 9,141,584 B2
• Time in Patent Office: Days
• US Class Current: 701/36
• CPC Class Codes: B60W 2520/10 Longitudinal speed
• CPC Class Codes: B60W 2520/105 Longitudinal acceleration
• CPC Class Codes: B60W 2520/125 Lateral acceleration
• CPC Class Codes: B60W 2520/14 Yaw
• CPC Class Codes: B60W 2540/18 Steering angle
• CPC Class Codes: B60W 2555/20 Ambient conditions, e.g. wind or rain
• CPC Class Codes: B60W 50/087 where the control system corrects or modifies a request from the driver
• CPC Class Codes: G01C 21/3641 Personalized guidance, e.g. limited guidance on previously travelled routes
• CPC Class Codes: G06F 17/00 Digital computing or data processing equipment or methods, specially adapted for specific functions information retrieval, database structures or file system structures therefor G06F16/00

Abstract

A vehicle'"'"'s dynamic handling state, driver inputs to the vehicle, etc. may be examined to determine one or more measures of driver workload. Driver interface tasks may then be delayed and/or prevented from executing based on the driver workload so as to not increase the driver workload. Alternatively, driver interface tasks may be scheduled for execution based on the driver workload and caused to execute according to the schedule, for example, to minimize the impact the executing driver interface tasks have on driver workload.

Claims

1. A vehicle comprising:

at least one processor configured to (i) determine a current handling condition and limit handling condition of the vehicle based on a plurality of vehicle handling parameters, (ii) determine a margin between the current and limit handling conditions, (iii) receive a plurality of driver interface tasks to be executed, and (iv) selectively delay or prevent at least some of the tasks from being executed based on the margin.

2. The vehicle of claim 1 wherein the plurality of vehicle handling parameters includes at least one of vehicle speed, vehicle yaw rate, vehicle lateral acceleration, vehicle longitudinal acceleration and steering wheel angle.

3. The vehicle of claim 1 wherein each of the plurality of driver interface tasks includes a priority type and wherein the at least one processor is configured to selectively delay or prevent at least some of the tasks from being executed further based on the priority type.

4. The vehicle of claim 1 wherein each of the vehicle handling parameters has upper and lower deadband thresholds defining a deadband interval within which the parameter may fall without initiating electronic stability control, anti-lock braking or traction control, and wherein the at least one processor is further configured to, for each of the parameters, determine a normalized difference between the parameter and at least one of the parameter'"'"'s upper and lower deadband thresholds to determine the margin between the current and limit handling conditions.

5. The vehicle of 4 wherein the at least one processor is further configured to identify a minimum of the normalized differences to determine the margin between the current and limit handling conditions.

6. The vehicle of claim 5 wherein the at least one processor is further configured to low-pass filter the minimum of the normalized differences to determine the margin between the current and limit handling conditions.

7. A vehicle comprising:

at least one processor configured to (i) determine a driver workload based on a margin between the vehicle'"'"'s current handling condition and limit handling condition, (ii) receive a plurality of driver interface tasks to be executed, (iii) schedule at least some of the plurality of driver interface tasks for execution based on the driver workload, and (iv) cause the scheduled driver interface tasks to be executed.

8. The vehicle of claim 7 wherein the at least one processor is further configured to determine the vehicle'"'"'s current and limit handling conditions based on a plurality of vehicle handling parameters, wherein each of the parameters has upper and lower deadband thresholds defining a deadband interval within which the parameter may fall without initiating electronic stability control, anti-lock braking or traction control, and wherein the at least one processor is further configured to, for each of the parameters, determine a normalized difference between the parameter and at least one of the parameter'"'"'s upper and lower deadband thresholds to determine the margin between the vehicle'"'"'s current and limit handling conditions.

9. The vehicle of claim 8 wherein the plurality of vehicle handling parameters includes at least one of vehicle speed, vehicle yaw rate, vehicle lateral acceleration, vehicle longitudinal acceleration and steering wheel angle.

10. The vehicle of claim 7 wherein each of the plurality of driver interface tasks includes a priority type and wherein the at least one processor is configured to schedule at least some of the plurality of driver interface tasks for execution further based on the priority type.

11. A method for managing driver interface tasks comprising:

determining, by at least one processing device, a driver workload based on a margin between a vehicle'"'"'s current handling condition and limit handling condition;

receiving a plurality of driver interface tasks to be executed; and

selectively delaying or preventing at least some of the plurality of driver interface tasks from being executed based on the driver workload.

12. The method of claim 11 further comprising determining the vehicle'"'"'s current and limit handling conditions based on a plurality of vehicle handling parameters.

13. The method of claim 11 further comprising determining the margin between the vehicle'"'"'s current and limit handling conditions.

14. The method of claim 13 wherein each of the vehicle handling parameters has upper and lower deadband thresholds defining a deadband interval within which the parameter may fall without initiating electronic stability control, anti-lock braking or traction control, and wherein determining the margin between the vehicle'"'"'s current and limit handling conditions includes determining, for each of the parameters, a normalized difference between the parameter and at least one of the parameter'"'"'s upper and lower deadband thresholds.

15. The method of claim 12 wherein the plurality of vehicle handling parameters includes at least one of vehicle speed, vehicle yaw rate, vehicle lateral acceleration, vehicle longitudinal acceleration and steering wheel angle.

16. The method of claim 11 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output and generating a tactile output.

17. The method of claim 11 wherein the plurality of driver interface tasks includes generating a notification regarding an in-coming call and wherein selectively delaying or preventing at least some of the plurality of driver interface tasks from being executed based on the driver workload includes forwarding the in-coming call to a voice mail system.

18. The method of claim 11 wherein each of the plurality of driver interface tasks includes a priority type and wherein at least some of the plurality of driver interface tasks are selectively delayed or prevented from being executed further based on the priority type.

19. A vehicle comprising:

at least one processor configured to (i) monitor over time a driver control action input, (ii) determine a variability of the driver control action input relative to a mean value of the driver control action input for a particular driver, (iii) receive a plurality of driver interface tasks to be executed, (iii) schedule the plurality of driver interface tasks for execution based on the variability, and (iv) cause the scheduled driver interface tasks to be executed.

20. The vehicle of claim 19 wherein the driver control action input includes accelerator pedal position, brake pedal position or steering wheel angle.

21. The vehicle of claim 19 wherein each of the plurality of driver interface tasks includes a priority type and wherein the at least one processor is configured to schedule the plurality of driver interface tasks for execution further based on the priority type.

22. The vehicle of claim 19 wherein the at least one processor is further configured to recursively calculate a determinant of the covariance of the driver control action input to determine the variability of the driver control action input.

23. The vehicle of claim 22 wherein the at least one processor is further configured to scale the determinant to determine an index representing a driver workload.

24. The vehicle of claim 19 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

25. A driver interface system for a vehicle comprising:

at least one processor configured to (i) monitor over time a driver control action input, (ii) determine a variability of the driver control action input relative to a mean value of the driver control action input for a particular driver, (iii) determine a driver workload based on the variability, (iv) receive a plurality of driver interface tasks to be executed, and (v) selectively delay or prevent at least some of the plurality of driver interface tasks from being executed based on the driver workload.

26. The system of claim 25 wherein the at least one processor is further configured to recursively calculate a determinant of the covariance of the driver control action input to determine the variability of the driver control action input.

27. The system of claim 25 wherein the driver control action input includes accelerator pedal position, brake pedal position or steering wheel angle.

28. The system of claim 25 wherein each of the plurality of driver interface tasks includes a priority type and wherein the at least one processor is configured to selectively delay or prevent at least some of the plurality of driver interface tasks from being executed further based on the priority type.

29. The system of claim 25 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

30. A method for managing driver interface tasks comprising:

monitoring over time a driver control action input;

determining a variability of the driver control action input relative to a mean value of the driver control action input for a particular driver;

receiving a plurality of driver interface tasks to be executed; and

selectively delaying or preventing at least some of the plurality of driver interface tasks from being executed based on the variability.

31. The method of claim 30 wherein determining the variability of the driver control action input includes recursively calculating a determinant of the covariance of the driver control action input.

32. The method of claim 30 wherein the driver control action input includes accelerator pedal position, brake pedal position or steering wheel angle.

33. The method of claim 30 wherein each of the plurality of driver interface tasks includes a priority type and wherein at least some of the plurality of driver interface tasks are selectively delayed or prevented from being executed further based on the priority type.

34. The method of claim 30 wherein the plurality of driver interface tasks includes generating a notification regarding an in-coming call and wherein selectively delaying or preventing at least some of the plurality of driver interface tasks from being executed based on the variability includes forwarding the in-coming call to a voice mail system.

35. The method of claim 30 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

36. A vehicle comprising:

at least one processor configured to (i) monitor an activation state of each of a plurality of driver-vehicle interfaces, (ii) for each of the plurality of driver-vehicle interfaces, generate a parameter representing a level of interaction between a driver and the driver-vehicle interface based on the activation state and a previous value of the parameter, (iii) receive a plurality of driver interface tasks to be executed, and (iv) selectively delay or prevent at least some of the plurality of driver interface tasks from being executed based on a maximum value of the generated parameters.

37. The vehicle of claim 36 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

38. The vehicle of claim 36 wherein each of the plurality of driver interface tasks includes a priority type and wherein the at least one processor is configured to selectively delay or prevent at least some of the plurality of driver interface tasks from being executed further based on the priority type.

39. The vehicle of claim 36 wherein the plurality of driver interface tasks includes generating a notification regarding an in-coming call and wherein selectively delaying or preventing at least some of the plurality of driver interface tasks from being executed based on a maximum value of the generated parameters includes forwarding the in-coming call to a voice mail system.

40. The vehicle of claim 36 wherein the plurality of driver-vehicle interfaces includes a wiper control, a climate control, a radio volume control, a turn indicator control, a center stack console, a door lock, a power seat control, or a voice command interface.

41. A vehicle comprising:

at least one processor configured to (i) determine a level of interaction between a driver and each of a plurality of driver-vehicle interfaces, (ii) determine a driver workload based on a maximum of the determined levels of interaction, (iii) receive a plurality of driver interface tasks to be executed, and (iv) selectively delay or prevent at least some of the plurality of driver interface tasks from being executed if the driver workload falls within a predetermined range of values.

42. The vehicle of claim 41 wherein the at least one processor is configured to determine the level of interaction between the driver and each of the plurality of driver-vehicle interfaces based on a frequency of activation of the driver-vehicle interface by the driver.

43. The vehicle of claim 41 wherein each of the plurality of driver interface tasks includes a priority type and wherein the predetermined range of values depends on the priority type.

44. The vehicle of claim 41 wherein the plurality of driver interface tasks includes generating a notification regarding an in-coming call and wherein selectively delaying or preventing at least some of the plurality of driver interface tasks from being executed if the driver workload falls within a predetermined range of values includes forwarding the in-coming call to a voice mail system.

45. The vehicle of claim 41 wherein the plurality of driver-vehicle interfaces includes a wiper control, a climate control, a radio volume control, a turn indicator control, a center stack console, a door lock, a power seat control, or a voice command interface.

46. The vehicle of claim 41 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

47. A method for managing driver interface tasks comprising:

monitoring an activation state of each of a plurality of driver-vehicle interfaces;

for each of the plurality of driver-vehicle interfaces, generating a parameter representing a level of interaction between a driver and the driver-vehicle interface based on the activation state and a previous value of the parameter;

receiving a plurality of driver interface tasks to be executed;

scheduling at least some of the plurality of driver interface tasks for execution based on a maximum or aggregation of the generated parameters; and

causing the plurality of driver interface tasks to be executed.

48. The method of claim 47 wherein each of the plurality of driver interface tasks includes a priority type and wherein at least some of the plurality of driver interface tasks are scheduled for execution further based on the priority type.

49. The method of claim 47 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

50. The method of claim 47 wherein the plurality of driver-vehicle interfaces includes a wiper control, a climate control, a radio volume control, a turn indicator control, a center stack console, a door lock, a power seat control, or a voice command interface.

51. The method of claim 47 wherein the plurality of driver interface tasks includes generating a notification regarding an in-coming call and wherein scheduling at least some of the plurality of driver interface tasks for execution based on a maximum or aggregation of the generated parameters includes forwarding the in-coming call to a voice mail system.

52. A vehicle comprising:

at least one processor configured to (i) determine a headway between the vehicle and another vehicle based on a history of the vehicle'"'"'s speed and distance to the another vehicle, (ii) determine a driver type, (iii) receive a plurality of driver interface tasks to be executed, and (iv) selectively delay or prevent at least some of the plurality of driver interface tasks from being executed based on the headway and driver type.

53. The vehicle of claim 52 wherein each of the plurality of driver interface tasks includes a priority type and wherein the at least one processor is configured to selectively delay or prevent at least some of the plurality of driver interface tasks from being executed further based on the priority type.

54. The vehicle of claim 52 wherein the plurality of driver interface tasks includes generating a notification regarding an in-coming call and wherein selectively delaying or preventing at least some of the plurality of driver interface tasks from being executed based on the headway and driver type includes forwarding the in-coming call to a voice mail system.

55. The vehicle of claim 52 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

56. A vehicle comprising:

at least one processor configured to receive a plurality of driver interface tasks to be executed and to selectively delay or prevent at least some of the plurality of driver interface tasks from being executed based on a driver type and a distance between the vehicle and another object.

57. The vehicle of claim 56 wherein the at least one processor is configured to selectively delay or prevent at least some of the plurality of driver interface tasks from being executed further based on a speed of the vehicle.

58. The vehicle of claim 56 wherein the at least one processor is further configured to determine the driver type.

59. The vehicle of claim 56 wherein each of the plurality of driver interface tasks includes a priority type and wherein the at least one processor is configured to selectively delay or prevent at least some of the plurality of driver interface tasks from being executed further based on the priority type.

60. The vehicle of claim 56 wherein the plurality of driver interface tasks includes generating a notification regarding an in-coming call and wherein selectively delaying or preventing at least some of the plurality of driver interface tasks from being executed based on the driver type and distance includes forwarding the in-coming call to a voice mail system.

61. The vehicle of claim 56 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

62. The vehicle of claim 56 wherein the object is another vehicle in front of the vehicle, another vehicle in a lane adjacent the vehicle, or a roadway intersection.

63. A method for managing driver interface tasks for a vehicle comprising:

determining a headway between the vehicle and another vehicle based on the vehicle'"'"'s speed and distance to the another vehicle;

determining at least one environmental condition;

receiving a plurality of driver interface tasks to be executed; and

selectively delaying or preventing at least some of the plurality of driver interface tasks from being executed based on the headway and the at least one environmental condition.

64. The method of claim 63 wherein each of the plurality of driver interface tasks includes a priority type and wherein at least some of the plurality of driver interface tasks are selectively delayed or prevented from being executed further based on the priority type.

65. The method of claim 63 wherein the plurality of driver interface tasks includes generating a notification regarding an in-coming call and wherein selectively delaying or preventing at least some of the plurality of driver interface tasks from being executed based on the headway and the at least one environmental condition includes forwarding the in-coming call to a voice mail system.

66. The method of claim 63 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

67. The method of claim 63 wherein the headway is recursively determined.

68. A method for managing a plurality of driver interface tasks comprising:

categorizing a driver workload into a plurality of workload classes representing differing levels of driver workload;

for a specified time period, determining a relative frequency with which the driver workload falls within each of the classes;

scheduling the tasks for execution based on the relative frequencies; and

executing the tasks according to the schedule.

69. The method of claim 68 wherein scheduling the tasks for execution based on the relative frequencies includes determining a maximum of the relative frequencies.

70. The method of claim 69 wherein the tasks are scheduled according to the maximum of the relative frequencies.

71. The method of claim 68 wherein determining a relative frequency with which the driver workload falls within each of the classes includes determining, for each of the classes, a long term driver workload based on the driver workload from a current time period and the driver workload from a past time period, and a scale factor that determines the specified time period.

72. The method of claim 68 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

73. A vehicle comprising:

at least one processor configured to (i) categorize a driver workload into a plurality of workload classes representing differing levels of driver workload, (ii) for a specified time period, determine a relative frequency with which the driver workload falls within each of the classes, (iii) receive a plurality of driver interface tasks to be executed, (iv) schedule the tasks for execution based on the relative frequencies, and (v) execute the tasks according to the schedule.

74. The vehicle of claim 73 wherein the at least one processor is further configured to determine a maximum of the relative frequencies.

75. The vehicle of claim 74 wherein the tasks are scheduled according to the maximum of the relative frequencies.

76. The vehicle of claim 73 wherein the at least one processor is further configured to determine, for each of the plurality of workload classes, a long term driver workload based on the driver workload from a current time period and a driver workload from a past time period, and a scale factor that determines the specified time period.

77. The vehicle of claim 73 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a recommendation for the driver.

78. A vehicle comprising:

at least one processor configured to (i) determine a plurality of scaled parameters each representing a driver workload and each based on one of (a) a level of interaction between a driver and one or more driver-vehicle interfaces, (b) a margin between the vehicle'"'"'s current handling condition and limit handling condition, (c) a variability of at least one driver control action input, or (d) a headway between the vehicle and another object, (ii) receive a plurality of driver interface tasks to be executed, and (iii) selectively delay or prevent at least some of the plurality of driver interface tasks from being executed based on a maximum or aggregation of the plurality of scaled parameters.

79. The vehicle of claim 78 wherein the at least one processor is further configured to determine the aggregation of the plurality of parameters based on a weighted average of the plurality of parameters.

80. The vehicle of claim 78 wherein the at least one processor is further configured to determine a parameter representing a workload of the driver based on whether a predefined set of conditions have been satisfied and to selectively delay or prevent at least some of the plurality of driver interface tasks from being executed further based on the determined parameter.

81. The vehicle of claim 78 wherein the plurality of driver interface tasks includes at least one of generating an audio output, generating a visual output, and generating a tactile output.

82. The vehicle of claim 78 wherein the plurality of driver interface tasks includes generating a recommendation for the driver.

83. The vehicle of claim 78 wherein each of the plurality of driver interface tasks includes a priority type and wherein the at least one processor is configured to selectively delay or prevent at least some of the plurality of driver interface tasks from being executed further based on the priority type.