GB2542560A - Vehicle interface apparatus and method - Google Patents

Vehicle interface apparatus and method Download PDF

Info

Publication number
GB2542560A
GB2542560A GB1516684.6A GB201516684A GB2542560A GB 2542560 A GB2542560 A GB 2542560A GB 201516684 A GB201516684 A GB 201516684A GB 2542560 A GB2542560 A GB 2542560A
Authority
GB
United Kingdom
Prior art keywords
driver
output
information
output device
machine interface
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
GB1516684.6A
Other versions
GB2542560B (en
GB201516684D0 (en
Inventor
Singh Harpreet
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jaguar Land Rover Ltd
Original Assignee
Jaguar Land Rover Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jaguar Land Rover Ltd filed Critical Jaguar Land Rover Ltd
Priority to GB1516684.6A priority Critical patent/GB2542560B/en
Publication of GB201516684D0 publication Critical patent/GB201516684D0/en
Priority to US15/748,510 priority patent/US11052923B2/en
Priority to PCT/EP2016/071249 priority patent/WO2017050590A1/en
Priority to EP16763042.5A priority patent/EP3353032B1/en
Publication of GB2542560A publication Critical patent/GB2542560A/en
Application granted granted Critical
Publication of GB2542560B publication Critical patent/GB2542560B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/08Interaction between the driver and the control system
    • B60W50/087Interaction between the driver and the control system where the control system corrects or modifies a request from the driver
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60KARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00Arrangement of adaptations of instruments
    • B60K35/10
    • B60K35/22
    • B60K35/60
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/0097Predicting future conditions
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/08Interaction between the driver and the control system
    • B60W50/10Interpretation of driver requests or demands
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/08Interaction between the driver and the control system
    • B60W50/12Limiting control by the driver depending on vehicle state, e.g. interlocking means for the control input for preventing unsafe operation
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/08Interaction between the driver and the control system
    • B60W50/14Means for informing the driver, warning the driver or prompting a driver intervention
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/08Interaction between the driver and the control system
    • B60W50/14Means for informing the driver, warning the driver or prompting a driver intervention
    • B60W50/16Tactile feedback to the driver, e.g. vibration or force feedback to the driver on the steering wheel or the accelerator pedal
    • B60K2360/1438
    • B60K2360/1442
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W2050/0062Adapting control system settings
    • B60W2050/0075Automatic parameter input, automatic initialising or calibrating means
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/08Interaction between the driver and the control system
    • B60W50/14Means for informing the driver, warning the driver or prompting a driver intervention
    • B60W2050/146Display means
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2540/00Input parameters relating to occupants
    • B60W2540/22Psychological state; Stress level or workload
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2540/00Input parameters relating to occupants
    • B60W2540/221Physiology, e.g. weight, heartbeat, health or special needs
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2540/00Input parameters relating to occupants
    • B60W2540/30Driving style
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60WCONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2556/00Input parameters relating to data
    • B60W2556/10Historical data

Abstract

A human machine interface 1 for a vehicle 2 is provided. The human machine interface 1 includes a first output device 10 for outputting information relating to a vehicle system VS. The human machine interface 1 includes a controller 3 having at least one processor 4 having an input for receiving a driver status signal DSTAT. A memory device 5 is coupled to the at least one processor 4 and has instructions stored therein. The at least one processor 4 is configured to determine an operating state of said vehicle system VS and to control the first output device 10 to output information relating to the determined operating state. The at least one processor 4 is configured to compose the information to be output in dependence on the received driver status signal DSTAT. The present disclosure also relates to a method of controlling the output of information relating to an operating state of a vehicle system VS.

Description

VEHICLE INTERFACE APPARATUS AND METHOD TECHNICAL FIELD
The present disclosure relates to a vehicle interface apparatus and method. More particularly, but not exclusively, the present disclosure relates to a human machine interface and method for composing information to be output to a driver of a vehicle. Aspects of the invention relate to a human machine interface, to a method, and to a vehicle.
BACKGROUND
Traditional human machine interaction in a vehicle is started by the user, typically a driver of the vehicle. Information may be output to the user in a variety of forms, for example audio, visual and haptic output. The nature and dialogue presented by known human machine interfaces is static and does not take account of external factors, such as the driver's mood, personality, workload etc. This limitation in the human machine interface may restrict how the driver perceives and accepts the information.
It is against this background that the present invention has been conceived. At least in certain embodiments, the present invention seeks to overcome or ameliorate at least some of the shortcomings of prior art interfaces.
SUMMARY OF THE INVENTION
Aspects and embodiments of the present invention provide a human machine interface, a method and a vehicle as claimed in the appended claims.
According to an aspect of the present invention there is provided a human machine interface for a vehicle, the human machine interface comprising: a first output device for outputting information relating to a vehicle system; a controller comprising at least one processor having an input for receiving a driver status signal; and a memory device coupled to the at least one processor and having instructions stored therein; the at least one processor being configured to determine at least one of a plurality of operating states of said vehicle system and to control said first output device to output information relating to the determined operating state; wherein the at least one processor is configured to compose the information to be output in dependence on the received driver status signal. The at least one processor may implement a dialogue manager to control the output of information at any given time. The driver status signal provides a measure of the driver status. By monitoring the driver status, the human machine interface may provide a dynamic dialogue manager which responds to driver behaviour. The at least one processor may vary the content and/or structure and/or amount (quantity) of said information in dependence on said driver status signal. The driver status signal may be determined in dependence on one or more of the following: driving conditions, driver personality, historic data to understand driver personality and/or preferences, current driver tasks, predicted driver workload or tasks (for example based on detection of approaching traffic; and/or identification of road junctions or roundabouts) and surrounding conditions. The human machine interface thereby presents information in a manner which is readily comprehensible to the driver of the vehicle.
The human machine interface typically initiates communication with a driver of the vehicle upon detection of an important event relating to a vehicle system. For example, if the at least one processor determines that the vehicle system is not operating correctly, for example a fault or error has developed, information relating to the determined operating state of the vehicle system can be output to the driver. It is envisaged that the human machine interface could be implemented in a system which allows the driver to initiate a dialogue to obtain more information about an event or to discuss a topic of interest in more detail. The at least one processor may learn from historic driver behaviour and responses to different amounts of information in order to understand driver preferences, driver personality and to update the information structure to give information in the most efficient manner. The human machine interface may determine and implement the strategy which results in the least user effort in understanding the information. The at least one processor may assess user effort by monitoring vehicle operating parameters and/or driver behaviour after outputting information. The human machine interface may have a set amount of information to convey to the driver, but may adopt different strategies to output that information depending on the driver status signal. For example, the at least one processor may present the information in a large number of small blocks; or may present the information in a small number of large blocks. Equally, the human machine interface may apply different questioning strategies, for example a direct question or a detailed question with reasoning.
The at least one processor may predict driver workload by considering navigation and/or surrounding conditions to vary the content displayed (e.g. to reduce or limit the output of information when a high driver workload is predicted). The at least one processor may also learn the driver mood in certain driving conditions, for example by monitoring a driver response to an output from the human machine interface. The driver monitoring could, for example, be performed using biosensors. The current external driving conditions may be monitored to understand what type of dialogue structure is preferred for a given driver mood. Consequently, the human machine interface may change the future dialogue content and/or structure based upon the driver mood.
The at least one processor may also learn from the driver response how fast they can read the information. The at least one processor may manage the content and/or amount of information output to the driver. This change in information content based upon driver personality may help the human machine interface to reduce or minimise driver workload.
The at least one processor may be configured to control said first output device to modify the information output by said first output device relating to said first operating state of the vehicle system in dependence on said driver status signal.
The information relating to each operating state of the vehicle system may be defined by a plurality of data packets; and the at least one processor may be configured to compose the information to be output by selecting one or more of said data packets in dependence on said driver status signal. Each data packet may relate to a particular aspect of the operating state of the vehicle system. Thus, the data packets may each consist of a sub-set of the available data defining the operating state of the vehicle system. The at least one processor may be configured to compose the information to be output by selecting one or more of said data packets for output. The at least one processor may also compose the information to be output by selecting the sequence in which two or more of said data packets are output. The at least one processor may control when one or more of said data packets is output.
The first output device may be a display screen, such as a liquid crystal display (LCD). The display screen may be disposed in a centre console of a vehicle, or in an instrument cluster. Alternatively, the display screen may project an image to form a Head Up Display (HUD). A first data packet may comprise a graphical element representing the vehicle system; and/or a second data packet may comprise a numerical value relating to the vehicle system; and/or a third data packet may comprise a statement or message relating to the vehicle system.
The first output device may be an audio output device, such as one or more loud speakers. A first data packet may comprise an audible notification, such as an audible tone; and/or a second data packet may comprise a first audio message relating to the vehicle system; and/or a third data packet may comprise a second audio message relating to the vehicle system. The at least one processor may compose the information by selecting one or more of said data packets for output.
The information relating to each operating state of the vehicle system may be defined in a plurality of different formats for output by said first output device.
The information to be output may be composed by selecting the format of the information to be output by said first output device. The format of the information can, for example, comprise a graphical symbol representing the vehicle system; or a text statement or sentence identifying the vehicle system and the operating state.
The at least one processor may be configured to monitor the driver status signal after the information is output by said first output device; and may re-compose the information in dependence on a detected change in the driver status signal. The at least one processor may modify the information to be output by the first output device in dependence on a detected change in the driver status signal. The human machine interface may store data relating to a driver response in order to establish a database of driver behaviour. The data may, for example, be stored in said memory device. The at least one processor may be configured to control said first output device to output the re-composed information following the detected change in the driver status.
The at least one processor may be configured to store a set of driver preferences in dependence on the detected change in the driver status signal.
The driver status signal may provide an indication of one or more of the following: driver drowsiness; driver distraction; driver alertness; driver annoyance; driver response time; driver workload; driver cognition; driver puzzlement; driver understanding; driver reaction time; and driver physical condition. The driver physical condition may be measured through heart rate, breathing rate, etc. The driver attention may be monitored to assess the driver cognition.
The first output device may be a visual output device; an audio output device; or a haptic output device.
The human machine interface may compose the information to be output in dependence on driver condition and/or historic data and/or surrounding conditions. The at least one processor may be configured to receive the driver status signal from a driver monitoring system. The driver monitoring system may be incorporated into a workload manager and/or a personality model.
The driver monitoring system may comprise a driver-facing camera. The driver behaviour may be determined by an image processor configured to analyse image data generated by said driver-facing camera. The driver monitoring system may determine the driver status in dependence on one or more vehicle operating parameters, for example dynamic operation of the vehicle. Alternatively, or in addition, the driver monitoring system may be coupled to one or more biometric sensors, such as a heart rate sensor and/or a temperature sensor (such as an infra-red camera).
The human machine interface may comprise a second vehicle output device, wherein the at least one processor is configured to control said second output device to output information relating to the determined operating state; the at least one processor being configured to compose the information to be output by said second output device in dependence on the received driver status signal. The at least one processor may be configured to control said first and second vehicle output devices to output different information, for example by changing the content of the information.
According to a further aspect of the present invention there is provided a vehicle comprising a human machine interface as described herein.
According to a further aspect of the present invention there is provided a method of controlling the output of information relating to a vehicle system, the method comprising: determining a driver status; determining at least one of a plurality of operating states of the vehicle system; and outputting information relating to the determined operating state of the vehicle system from a first output device; wherein the information is composed in dependence on the determined driver status.
The method may comprise composing the information to be output by selecting one or more data packets in dependence on the determined driver status.
The method may comprise composing the information to be output by selecting one or more different formats of the information to be output by said first output device. The method may comprise composing the information to be output by selecting the format of the information to be output by said first output device.
The method may comprise monitoring the driver status after the information is output by said first output device; and re-composing the information in dependence on a detected change in the driver status. The method may comprise modifying the information to be output by the first output device in dependence on a detected change in the driver status. The method may comprise outputting the re-composed information following the detected change in the driver status.
The method may comprise storing a set of driver preferences in dependence on the detected change in the driver status.
The driver status may comprise one or more of the following: driver drowsiness; driver distraction; driver alertness; driver annoyance; driver response time; driver workload; driver cognition; driver puzzlement; driver understanding; driver reaction time; and driver physical condition.
The first output device may be a visual output device; an audio output device; or a haptic output device.
The method may comprise using a driver monitoring system to determine the driver status. The driver monitoring system may be incorporated into a workload manager or a personality model.
The method may comprise controlling the output of said information relating to the determined operating state to a second output device. The method may comprise composing the information to be output by said second output device in dependence on the determined driver status.
Within the scope of this application it is expressly intended that the various aspects, embodiments, examples and alternatives set out in the preceding paragraphs, in the claims and/or in the following description and drawings, and in particular the individual features thereof, may be taken independently or in any combination. That is, all embodiments and/or features of any embodiment can be combined in any way and/or combination, unless such features are incompatible. The applicant reserves the right to change any originally filed claim or file any new claim accordingly, including the right to amend any originally filed claim to depend from and/or incorporate any feature of any other claim although not originally claimed in that manner.
BRIEF DESCRIPTION OF THE DRAWINGS
One or more embodiments of the present invention will now be described, by way of example only, with reference to the accompanying figures, in which:
Figure 1 shows a schematic representation of a vehicle comprising a human machine interface in accordance with an embodiment of the present invention; and
Figure 2 is a flowchart representing operation of the human machine interface shown in Figure 1.
DETAILED DESCRIPTION A human machine interface 1 in accordance with an embodiment of the present invention will now be described with reference to the accompanying figures. The human machine interface 1 is disposed in a vehicle 2. In the present embodiment, the vehicle 2 is an automobile, but the invention is not limited in this respect.
The human machine interface 1 comprises a controller 3 having an electronic processor 4 and a memory device 5. A set of computational instructions is stored on the memory device 5. When executed, the computational instructions cause the electronic processor 4 to implement the method(s) described herein.
The electronic processor 4 is coupled to a vehicle communication bus 6, such as a CAN communication bus. The vehicle communication bus 6 is connected to a plurality of vehicle systems (denoted generally by the reference numeral VS in Figure 1) disposed on the vehicle 2. The vehicle systems VS include: an engine management system VS1, a brake management system VS2, a fuel monitoring system VS3, a tyre pressure monitoring system VS4, a vehicle navigation system VS5, a traffic monitoring system VS6. It will be understood that this is a non-exhaustive list of vehicle systems VS suitable for use in conjunction with the human machine interface 1 described herein. The vehicle systems VS publish data signals S to the vehicle communication bus 6. The data signals S each comprise one or more data packets relating to the operating state of the corresponding vehicle systems VS. At least some of the information published to the vehicle communication bus 6 is selectively output to a driver of the vehicle 2. By way of example, the tyre pressure monitoring system VS4 may detect a drop in tyre pressure which may indicate that the tyre has developed a puncture. The tyre pressure monitoring system VS4 publishes a signal S4 to the vehicle communication bus 6 which prompts the human machine interface 1 to output corresponding tyre pressure information. The signal S4 would typically indicate the affected tyre and may also comprise a measured tyre pressure. The human machine interface 1 controls the output of information derived from the signal S4.
As described herein, the controller 3 implements a dialogue manager configured to compose information to be output to the driver. In particular, the human machine interface 1 composes the information to be output in dependence on the status of the driver at that time. The human machine interface 1 selects one or more data packets included in the data signals S to compose the information. The dialogue manager may also control the output of information, for example to control the timing at which a message or notification is output. The controller 3 is configured to receive a driver status signal DStat from a driver monitoring system 7. The driver monitoring system 7 comprises a driver-facing camera 8 and an image processor 9. The driver-facing camera 8 in the present embodiment is an optical digital camera operative to generate digital image data DIMG. The digital image data DIMG is analysed by the image processor 9 to identify and categorize driver behaviour. The image processor 9 may, for example, determine a gaze direction and/or a gaze duration of the driver. The image processor 9 may also identify one or more gestures performed by the driver to assess driver behaviour. The image processor 9 may categorize one or more of the following driver characteristics: driver drowsiness; driver distraction; driver alertness; driver annoyance; driver response time; and driver workload. It will be understood that this list is non-exhaustive and other driver characteristics may be monitored and categorized. The driver monitoring system 7 may also comprise one or more biometric sensors (not shown) and/or an audio input device (not shown), such as a microphone, to monitor and characterise driver behaviour. The audio input device may be implemented in an audio interface system, for example performing speech recognition functions. By monitoring driver inputs and/or responses to the audio input device, the driver monitoring system 7 may categorise driver behaviour.
The image processor 9 categorises the driver behaviour and generates the driver status signal DStat in dependence on said categorisation. The driver status signal DStat is published to the vehicle communication bus 6. Alternatively, or in addition, the driver status signal DSTAT may be generated in dependence on data received from other vehicle systems, for example utilising the vehicle speed and/or steering angle and/or navigation data to determine a driver workload.
The human machine interface 1 comprises a first output device 10 and a second output device 11. In the present embodiment the first output device 10 is in the form of a display screen, for example disposed in an instrument cluster or a centre console (not shown) of the vehicle 2; and the second output device 11 is in the form of an audio output device, such as a loudspeaker, disposed in the cabin of the vehicle 2. The controller 3 is configured to control the output of information from said first and second output devices 10, 11 in dependence on the driver status signal DStat- The information relating to each operating state of the vehicle system is defined by the data packets published to the communication bus 6 by the vehicle systems VS. The electronic processor 4 is configured to compose the information to be output by selecting one or more of said data packets in dependence on said driver status signal DStat- In the above example, the tyre pressure monitoring system VS4 publishes a signal S4 to the vehicle communication bus 6. The signal S4 comprises a first data packet which indicates which tyre is subject to a pressure drop; and a second data packet comprises the measured tyre pressure. By way of example, the tyre pressure monitoring system VS4 may detect a drop in tyre pressure which may indicate that the tyre has developed a puncture. The tyre pressure monitoring system VS4 publishes a signal S4 to the vehicle communication bus 6 which prompts the human machine interface 1 to output corresponding tyre pressure information. The signal S4 may comprise a first data packet indicating the affected tyre and a second data packet specifying a measured tyre pressure. The human machine interface 1 composes the information to be output to the driver of the vehicle 2 by selecting said first data packet and/or said second data packet. The human machine interface 1 outputs said first data packet and/or said second data packet to said first output device 10 and/or said second output device 11.
The operation of the human machine interface 1 will now be described with reference to a block diagram 100 shown in Figure 2. The human machine interface 1 is started with default settings (STEP 105). The human machine interface 1 determines driver preferences, for example a preferred interface and/or form of interaction (for example, language). The driver preferences can be learned from driver responses to create a personality model (STEP 110). A check is then performed to determine if the primary interface selected by the driver to respond/interact with the human machine interface 1 differs from the initial system settings (STEP 115).
If the driver selects a primary interface which is the same as the initial system settings, a sub-routine is optionally implemented to determine if the user efficiency can be increased using other interfaces. The optimal interface settings and information content settings are saved (STEP 120). The information presented through a secondary interface is then increased (STEP 125). A check is then performed to determine if the additional information adversely influences driving parameters (STEP 130). The driving parameters can, for example, include driver distraction, driver annoyance (measured through emotional response and biometric sensors) and response time. If the driving parameters are adversely affected, the human machine interface 1 reverts to the previous settings and saves the optimal interface settings (STEP 135). If the driving parameters are not adversely affected, the revised settings are saved as the optimal interface settings and information content settings (STEP 140). A first loop L1 can be implemented to check if additional information can be presented (STEP 125).
If the driver selects a different primary interface which is not the same as the initial system settings, the amount of information presented by the driver’s preferred interface is increased and made a default primary interface (STEP 145). Alternatively, or in addition, the response language is updated, for example to change style from formal to informal language to reflect driver response. A check is then performed to determine if the additional information adversely influences driving parameters (STEP 150). The driving parameters can, for example, include driver distraction, driver annoyance (measured through emotional response and biometric sensors) and response time. If the driving parameters are adversely affected, the human machine interface 1 reduces the amount of information presented from the selected preferred interface and/or reduces the level of language change (STEP 155). A second loop L2 is implemented to check if the reduction in the amount of information adversely influences driving parameters. When the human machine interface 1 determines that the interface and information content settings are at an optimum level, the settings are saved for future reference (STEP 160).
It will be appreciated that various changes and modifications can be made to the human machine interface 1 described herein without departing from the scope of the present application.
The human machine interface 1 may optionally be configured to predict the status of the driver and compose the information to be output in dependence on the predicted status. The human machine interface 1 may, for example, communicate with a navigation system to identify approaching road junctions and/or roundabouts that would increase driver workload. Alternatively, or in addition, the human machine interface 1 may monitor traffic levels to estimate driver workload.

Claims (24)

CLAIMS:
1. A human machine interface for a vehicle, the human machine interface comprising: a first output device for outputting information relating to a vehicle system; a controller comprising at least one processor having an input for receiving a driver status signal; and a memory device coupled to the at least one processor and having instructions stored therein; the at least one processor being configured to determine at least one of a plurality of operating states of said vehicle system and to control said first output device to output information relating to the determined operating state; wherein the at least one processor is configured to compose the information to be output in dependence on the received driver status signal.
2. A human machine interface as claimed in claim 1, wherein the information relating to each operating state of the vehicle system is defined by a plurality of data packets; and the at least one processor is configured to compose the information to be output by selecting one or more of said data packets in dependence on said driver status signal.
3. A human machine interface as claimed in claim 1 or claim 2, wherein the information relating to each operating state of the vehicle system is defined in a plurality of different formats for output by said first output device.
4. A human machine interface as claimed in any one of the preceding claims, wherein the at least one processor is configured to monitor the driver status signal after the information is output by said first output device; and to re-compose the information in dependence on a detected change in the driver status signal.
5. A human machine interface as claimed in claim 4, wherein the at least one processor is configured to control said first output device to output the re-composed information following the detected change in the driver status.
6. A human machine interface as claimed in claim 5, wherein the at least one processor is configured to store a set of driver preferences in dependence on the detected change in the driver status signal.
7. A human machine interface as claimed in any one of the preceding claims, wherein the driver status signal provides an indication of one or more of the following: driver drowsiness; driver distraction; driver alertness; driver annoyance; driver response time; driver workload; driver cognition; driver puzzlement; driver understanding; driver reaction time; and driver physical condition.
8. A human machine interface as claimed in any one of the preceding claims, wherein the first output device is a visual output device; or an audio output device; or a haptic output device.
9. A human machine interface as claimed in any one of the preceding claims, wherein the at least one processor is configured to receive the driver status signal from a driver monitoring system.
10. A human machine interface as claimed in any one of the preceding claims comprising a second vehicle output device, wherein the at least one processor is configured to control said second output device to output information relating to the determined operating state; the at least one processor being configured to compose the information to be output by said second output device in dependence on the received driver status signal.
11. A vehicle comprising a human machine interface as claimed in any one of the preceding claims.
12. A method of controlling the output of information relating to a vehicle system, the method comprising: determining a driver status; determining at least one of a plurality of operating states of the vehicle system; and outputting information relating to the determined operating state of the vehicle system from a first output device; wherein the information is composed in dependence on the determined driver status.
13. A method as claimed in claim 12, wherein composing the information to be output comprises selecting one or more data packets in dependence on the determined driver status.
14. A method as claimed in claim 12 or claim 13, wherein composing the information to be output comprises selecting one or more different formats of the information to be output by said first output device .
15. A method as claimed in any one of claims 12, 13 or 14 comprising monitoring the driver status after the information is output by said first output device; and re-composing the information in dependence on a detected change in the driver status.
16. A method as claimed in claim 15 comprising outputting the re-composed information following the detected change in the driver status.
17. A method as claimed in claim 16 comprising storing a set of driver preferences in dependence on the detected change in the driver status.
18. A method as claimed in any one of claims 12 to 17, wherein the driver status comprises one or more of the following: driver drowsiness; driver distraction; driver alertness; driver annoyance; driver response time; driver workload; driver cognition; driver puzzlement; driver understanding; driver reaction time; and driver physical condition.
19. A method as claimed in any one of claims 12 to 18, wherein the first output device is a visual output device; or an audio output device; or a haptic output device.
20. A method as claimed in any one of claims 12 to 19 comprising using a driver monitoring system to determine the driver status.
21. A method as claimed in any one of claims 12 to 20 comprising controlling the output of said information relating to the determined operating state to a second output device; wherein the method comprises composing the information to be output by said second output device in dependence on the determined driver status.
22. A human machine interface substantially as herein described with reference to the accompanying figures.
23. A vehicle substantially as herein described with reference to the accompanying figures.
24. A method of controlling the output of information substantially as herein described with reference to the accompanying figures.
GB1516684.6A 2015-09-21 2015-09-21 Vehicle interface apparatus and method Active GB2542560B (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
GB1516684.6A GB2542560B (en) 2015-09-21 2015-09-21 Vehicle interface apparatus and method
US15/748,510 US11052923B2 (en) 2015-09-21 2016-09-09 Vehicle interface apparatus and method
PCT/EP2016/071249 WO2017050590A1 (en) 2015-09-21 2016-09-09 Vehicle interface apparatus and method
EP16763042.5A EP3353032B1 (en) 2015-09-21 2016-09-09 Vehicle interface apparatus and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB1516684.6A GB2542560B (en) 2015-09-21 2015-09-21 Vehicle interface apparatus and method

Publications (3)

Publication Number Publication Date
GB201516684D0 GB201516684D0 (en) 2015-11-04
GB2542560A true GB2542560A (en) 2017-03-29
GB2542560B GB2542560B (en) 2019-02-20

Family

ID=54544552

Family Applications (1)

Application Number Title Priority Date Filing Date
GB1516684.6A Active GB2542560B (en) 2015-09-21 2015-09-21 Vehicle interface apparatus and method

Country Status (4)

Country Link
US (1) US11052923B2 (en)
EP (1) EP3353032B1 (en)
GB (1) GB2542560B (en)
WO (1) WO2017050590A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20180130672A (en) * 2017-05-30 2018-12-10 현대자동차주식회사 Apparatus, system, vehicle and method for initiating conversation based on situation
DE102017210151A1 (en) * 2017-06-19 2018-12-20 Zf Friedrichshafen Ag Device and method for controlling a vehicle module in response to a state signal
GB2588969B (en) * 2019-11-18 2022-04-20 Jaguar Land Rover Ltd Apparatus and method for determining a cognitive state of a user of a vehicle

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120174111A1 (en) * 2010-12-30 2012-07-05 Denso International America, Inc. Method to determine driver workload function and usage of driver workload function for human-machine interface performance assessment
US20140300479A1 (en) * 2013-04-09 2014-10-09 Ford Global Technologies, Llc Method and system for controlling a vehicle during an autonomous control mode
US20150066282A1 (en) * 2013-09-05 2015-03-05 Ford Global Technologeis, Llc Autonomous driving in areas for non-drivers
WO2015165811A1 (en) * 2014-05-01 2015-11-05 Jaguar Land Rover Limited Communication system and related method

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10322458A1 (en) 2003-05-16 2004-12-02 Daimlerchrysler Ag Method and device for influencing the stress of a driver in a motor vehicle
DE102006057278A1 (en) 2006-12-05 2008-06-12 Robert Bosch Gmbh Method for the possibility of adapting the driving situation of a vehicle run by a driver
DE102011111213A1 (en) 2011-08-20 2013-02-21 GM Global Technology Operations LLC (n. d. Gesetzen des Staates Delaware) Apparatus and method for outputting information
JP6477123B2 (en) * 2015-03-25 2019-03-06 株式会社デンソー Operation system
JP6396850B2 (en) * 2015-05-29 2018-09-26 株式会社デンソー Driving support device and driving support method
US10618521B2 (en) * 2015-09-21 2020-04-14 Ford Global Technologies, Llc Wearable in-vehicle eye gaze detection

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120174111A1 (en) * 2010-12-30 2012-07-05 Denso International America, Inc. Method to determine driver workload function and usage of driver workload function for human-machine interface performance assessment
US20140300479A1 (en) * 2013-04-09 2014-10-09 Ford Global Technologies, Llc Method and system for controlling a vehicle during an autonomous control mode
US20150066282A1 (en) * 2013-09-05 2015-03-05 Ford Global Technologeis, Llc Autonomous driving in areas for non-drivers
WO2015165811A1 (en) * 2014-05-01 2015-11-05 Jaguar Land Rover Limited Communication system and related method

Also Published As

Publication number Publication date
GB2542560B (en) 2019-02-20
US20180222493A1 (en) 2018-08-09
US11052923B2 (en) 2021-07-06
EP3353032A1 (en) 2018-08-01
WO2017050590A1 (en) 2017-03-30
GB201516684D0 (en) 2015-11-04
EP3353032B1 (en) 2023-08-16

Similar Documents

Publication Publication Date Title
US10053113B2 (en) Dynamic output notification management for vehicle occupant
EP3353032B1 (en) Vehicle interface apparatus and method
US10940871B2 (en) Contextual autonomous vehicle support through pictorial interaction
Rudin-Brown ‘Intelligent’in-vehicle intelligent transport systems: Limiting behavioural adaptation through adaptive design
JP2008540223A (en) Method for operating a powered vehicle with multiple functional systems
US20170243518A1 (en) Information Presentation Apparatus and Method, and Computer Program Product
KR101500092B1 (en) Apparatus for preventing passive task-related fatigue of driver and method thereof
Mueller et al. Addressing driver disengagement and proper system use: human factors recommendations for level 2 driving automation design
Mehler et al. Defining workload in the context of driver state detection and HMI evaluation
Monsaingeon et al. Impact of interface design on drivers’ behavior in partially automated cars: An on-road study
JP6409726B2 (en) Risk index conversion device
Atwood et al. Evaluate driver response to active warning system in level-2 automated vehicles
CN110949404B (en) Warning method and device, central control equipment, storage medium and system
JP2010282368A (en) Driving support device and program
JP5366017B2 (en) Vehicle notification system
EP3718848A1 (en) System and method for executing an automated driving maneuver in a takeover process of a vehicle from automated driving to manually driving
JP2009001096A (en) Operation support device, operation controller, and program
JP2008126920A (en) Vehicular input device
CN114815676A (en) Generation and presentation of interpretations relating to behavior of an automation control system
Barisic et al. Driver model for Take-Over-Request in autonomous vehicles
Heimgärtner et al. Towards cultural adaptability to broaden universal access in future interfaces of driver information systems
EP4230491A1 (en) A computer-implemented method for providing a function recommendation in a vehicle, a vehicle and a system for implementing the method
Pei Research on Designing and Evaluating Alarm Signals for Varying Criticality Scenarios
US10940757B2 (en) User interfaces, computer program product, signal sequence, transportation vehicle and method for displaying information on a display device
JP2010018072A (en) Driver support apparatus, driver support method, and driver support processing program