Patent Description:
<CIT> describes a device for detecting dangerous driving performed by a user and presenting driving characteristics to the user.

Patent documents No. <CIT> and <CIT> describe devices for acquiring driver data and determining a vehicle operation command based on the driver data.

However, in the invention disclosed in <CIT>, a system determines whether driving is dangerous driving. A user himself/herself determines whether to admit the determination result. Therefore, driving support based on the determination result may not be effective.

The present invention has been made in view of the above problem, and an object of the present invention is to provide a driving support device and a driving support method capable of providing driving support suitable for a user's feeling.

A driving support device and method according to the invention are defined in the appended independent claims. Specific embodiments are defined in the dependent claims. The device determines whether a vehicle is in an abnormal state based on data acquired by a sensor, upon determining that the vehicle is in the abnormal state, outputs a message indicating that the vehicle is in the abnormal state to a user on the vehicle, acquires an answer from the user to the message via an input device, and proposes use of a support function for supporting the user based on the answer from the user.

According to the present invention, it is possible to provide driving support suitable for a user's feeling.

In the description of the drawings, the same parts are denoted by the same reference numerals and the explanation thereof will be omitted.

An example of a configuration of a driving support device <NUM> will be described with reference to <FIG>. As shown in <FIG>, the driving support device <NUM> includes a sensor <NUM>, a microphone <NUM>, a camera <NUM>, a GPS receiver <NUM>, a switch <NUM>, a controller <NUM>, a robot head <NUM>, a speaker <NUM>, a display <NUM>, a steering actuator <NUM>, an accelerator pedal actuator <NUM>, and a brake actuator <NUM>.

The driving support device <NUM> is mounted on a vehicle having automatic driving functions. The driving support device <NUM> may be mounted on a vehicle that can switch between automatic driving and manual driving. As an example, the automatic driving functions perform automatic control such as steering control, braking force control, and driving force control and support driving of a user. In the present embodiment, a "user" means a user who is sitting in a driver's seat of a vehicle.

The sensor <NUM> is used to acquire various pieces of data and information. Examples of the sensor <NUM> include a sensor for acquiring data of a vehicle and a sensor for acquiring vehicle external information. An example of the data of a vehicle is the speed, acceleration, steering angle, brake hydraulic pressure, and accelerator opening. Examples of sensors that acquire these pieces of data include speed sensors, acceleration sensors, steering angle sensors, gyro sensors, brake hydraulic pressure sensors, and accelerator opening sensors.

Examples of the vehicle external information include an object (a pedestrian, bicycle, motorcycle, another vehicle, and the like) present in a periphery of a vehicle (host-vehicle), a traffic light, road division line, sign, pedestrian crosswalk, intersection, and the like. Examples of the sensor for acquiring these pieces of information include a laser range finder, radar, lidar, the camera <NUM>, a sonar, and the like. In the present embodiment, the sensor <NUM> is distinguished form the camera <NUM> for convenience of explanation, but the camera <NUM> is a type of the sensor <NUM>. The data and information acquired by the sensor <NUM> are output to the controller <NUM>.

The microphone <NUM> acquires voice data of the user. The voice data acquired by the microphone <NUM> is output to the controller <NUM>.

The camera <NUM> has an imaging element such as a charge-coupled device (CCD) or a complementary metal oxide semiconductor (CMOS). The installation position of the camera <NUM> is not particularly limited, but as an example, the camera <NUM> is installed in the front, sides, or rear of a vehicle. The camera <NUM> captures an image of a space around the vehicle. The image data captured by using the camera <NUM> is output to the controller <NUM>. Further, in the present embodiment, the camera <NUM> is also installed inside a vehicle. For example, the camera <NUM> is installed near a driver's seat to capture an image the user's face. The face image data captured by using the camera <NUM> is output to the controller <NUM>.

The GPS receiver <NUM> detects position information of a vehicle on the ground by receiving radio waves from an artificial satellite. The position information of the vehicle detected by the GPS receiver <NUM> includes latitude information and longitude information. The GPS receiver <NUM> outputs the detected position information of the vehicle to the controller <NUM>. An entity performing the method for detecting the position information of the vehicle is not limited to the GPS receiver <NUM>. For example, the position of the vehicle may be estimated using a method called an odometry. The odometry is a method for estimating a position of a vehicle by obtaining the amount of movement and a movement direction of the vehicle in accordance with a rotation angle and a rotation angular speed of the vehicle. A GNSS receiver may be used instead of the GPS receiver <NUM>.

The switch <NUM> is used when the user uses support functions. When the user presses the switch <NUM>, the support functions are activated. The "support functions" in the present embodiment include an around-view monitor (hereinafter referred to as an AVM), automatic parking, a side-down-view monitor, steering support, emergency stop brake, emergency avoidance steering, lane deviation prevention, blind spot warning, a combination of an AVM and an ultrasonic sensor, and the like. Since the support functions are well known, a detailed description thereof will be omitted. The switch <NUM> may be a physical switch or a virtual switch. The virtual switch is, for example, a switch displayed on the display <NUM>. Some of the support functions described above are also the automatic driving functions. That is, the support functions of the present embodiment include the automatic driving functions. The automatic driving functions include adaptive cruise control (ACC), constant speed control, and the like.

The controller <NUM> is a general-purpose microcomputer that includes a central processing unit (CPU), a memory, and an input/output unit. A computer program for causing the microcomputer to function as the driving support device <NUM> is installed in the microcomputer. By executing the computer program, the microcomputer functions as a plurality of information processing circuits in the driving support device <NUM>. Here, an example of realizing the plurality of information processing circuits in the driving support device <NUM> by software is shown. However, it is also possible to configure each information processing circuit by preparing dedicated hardware for performing each information processing described below. Further, the plurality of information processing circuits may be configured by individual pieces of hardware. As an example of the plurality of information processing circuits, the controller <NUM> includes a dangerous situation determining unit <NUM>, a responsibility determining unit <NUM>, a message creating unit <NUM>, a speech acquisition unit <NUM>, a speech analyzing unit <NUM>, a parameter changing unit <NUM>, a user determination unit <NUM>, a position detecting unit <NUM>, a support function selecting unit <NUM>, a proposal unit <NUM>, and a support function implementing unit <NUM>.

The robot head <NUM> is a figurine imitating a head of a robot. The robot head <NUM> is installed to enhance the affinity between a user and a vehicle. The robot head <NUM> has a speaker function and an information processing function.

Next, with reference to <FIG>, the details of the dangerous situation determining unit <NUM>, the responsibility determining unit <NUM>, the message creating unit <NUM>, the speech acquisition unit <NUM>, the speech analyzing unit <NUM>, the parameter changing unit <NUM>, the user determination unit <NUM>, the position detecting unit <NUM>, the support function selecting unit <NUM>, the proposal unit <NUM>, and the support function implementing unit <NUM> will be described.

<FIG> shows a scene in which a user <NUM> is having conversations with the robot head <NUM>. The conversations are indicated by reference numerals <NUM> to <NUM>. Reference numerals <NUM> and <NUM> indicate the speech made by the robot head <NUM>. Reference numerals <NUM> and <NUM> indicate the speech made by the user <NUM>. The flow of the conversations is in the order of reference numerals <NUM>, <NUM>, <NUM>, and <NUM>. Reference numeral <NUM> indicates a preceding vehicle. Although a description will be given by assuming that all of reference numerals <NUM> to <NUM> indicate voice, the present invention is not limited thereto. For example, contents indicated by reference numerals <NUM> and <NUM> may be displayed on the display <NUM> as characters. Further, reference numerals <NUM> and <NUM> may indicate information selected by the user <NUM> from a plurality of options. In this case, the plurality of options are displayed on the display <NUM>. First, conditions for outputting voice "Something happened?" indicated by reference numeral <NUM> will be described. The installation of the robot head <NUM> is not essential. A virtual robot head may be displayed on the display <NUM>.

The dangerous situation determining unit <NUM> determines whether the user <NUM> drove dangerously using data acquired from the sensor <NUM>. An example of the determination method will be described with reference to <FIG>. The scene shown in <FIG> is classified into parking, a narrow road, approach to a preceding vehicle, lane deviation, merging or lane change, a right turn, and a left turn. In the scene of "parking", if a distance from an obstacle is <NUM> or shorter, or the number of times a steering wheel is quickly turned to move the vehicle back and forth is five times or more, the dangerous situation determining unit <NUM> determines that the user <NUM> drove dangerously. A distance from an obstacle is detected by a lidar. The number of times a steering wheel is quickly turned is detected by a steering angle sensor. In the scene of "narrow road", if a distance from an obstacle on the left side is <NUM> or shorter, the dangerous situation determining unit <NUM> determines that the user <NUM> drove dangerously. Here, the determination is made based on the Japanese traffic rules (left-hand traffic). The term "left" or "right"" can be appropriately replaced according to the traffic rules of each country.

In the scene of "approach to a preceding vehicle", if the speed of the host-vehicle is <NUM>/h or higher, and a distance from a preceding vehicle is <NUM> or shorter, the dangerous situation determining unit <NUM> determines that the user <NUM> drove dangerously. The speed of the host-vehicle is detected by the speed sensor. The distance from the preceding vehicle is detected by the lidar. In the scene of "lane deviation", if a distance from either one of left and right road division lines is <NUM> or shorter, the dangerous situation determining unit <NUM> determines that the user <NUM> drove dangerously. A distance from a road division line is detected by the camera <NUM>. In the scene of "merging or lane change", if the distance from rear lateral side vehicles is <NUM> or shorter, and the host-vehicle is steered in the directions, the dangerous situation determining unit <NUM> determines that the user <NUM> drove dangerously. The distance from the rear lateral side vehicles is detected by the lidar. The steering direction is detected by the steering angle sensor. In the scene of "right turn", if time to collision (TTC) with an oncoming vehicle that travels straight ahead is equal to or less than a prescribed value, the dangerous situation determining unit <NUM> determines that the user <NUM> drove dangerously. The TTC with the oncoming vehicle that travels straight ahead is calculated using the speed of the oncoming vehicle that travels straight ahead and the distance to the oncoming vehicle that travels straight ahead. In the scene of "left turn", if a distance from an obstacle on the left side is <NUM> or shorter, the dangerous situation determining unit <NUM> determines that the user <NUM> drove dangerously.

If the dangerous situation determining unit <NUM> determines that the user <NUM> drove dangerously, a signal indicating the determination result is transmitted to the responsibility determining unit <NUM>. The responsibility determining unit <NUM>, that has received the signal, determines who is responsible for dangerous driving. In the scene of <FIG>, the responsibility determining unit <NUM> determines that the user <NUM> is responsible for dangerous driving. In this case, a signal indicating the determination result is transmitted to the message creating unit <NUM>. The message creating unit <NUM>, which has received the signal, creates a message which is indicated by reference numeral <NUM>. The message creating unit <NUM> outputs the created message to the robot head <NUM>. Accordingly, as shown in <FIG>, the message indicated by reference numeral <NUM> is output with voice. As shown in <FIG>, in response to the question "Something happened?", the user <NUM> answers "Yes, a slightly dangerous situation arose!" (reference numeral <NUM>). This answer is a positive answer. The "positive answer" here means an answer in which the user <NUM> admits that his/her driving was dangerous.

The voice answer made by the user <NUM> is output to the speech acquisition unit <NUM> by using the microphone <NUM>. The speech acquisition unit <NUM> outputs the voice data of the user <NUM> to the speech analyzing unit <NUM>. The speech analyzing unit <NUM> analyzes the voice data of the user <NUM>. A well-known technique is used for the voice analysis method. The speech analyzing unit <NUM> determines whether the answer made by the user <NUM> is positive, based on the analysis result. A signal indicating the determination result is output to the message creating unit <NUM>. The message creating unit <NUM>, which has received the signal, creates a message (Then, do you need support from next time?) indicated by reference numeral <NUM>. The message indicated by reference numeral <NUM> is created because the answer made by the user <NUM> is positive. As shown in <FIG>, in response to the question "Then, do you need support from next time?", the user <NUM> answers "Yes, please support me!" (reference numeral <NUM>). This answer is a positive answer. The "positive answer" here means an answer in which the user accepts a support function. The answer indicated by reference numeral <NUM> is also analyzed by the speech analyzing unit <NUM> in the same manner as the answer indicated by reference numeral <NUM>. Then, the speech analyzing unit <NUM> determines whether the answer made by the user <NUM> is positive. A signal indicating the determination result is output to a user database <NUM>. The user database <NUM> is stored in a storage device <NUM>. The storage device <NUM> is constituted by hard disk drive (HDD), solid state drive (SSD), and the like.

If it is determined that the user <NUM> drove dangerously, the position detecting unit <NUM> detects a position (location) of the vehicle at that time using data acquired from the GPS receiver <NUM>. The detected position information is stored in the user database <NUM>.

The "support function" in the present embodiment is implemented the next time when the user <NUM> drives a vehicle after the messages indicated by reference numerals <NUM> to <NUM> have been exchanged. When the user <NUM> gets on a vehicle, the camera <NUM> captures an image of the face of the user <NUM>. The face image data captured by using the camera <NUM> is output to the user determination unit <NUM>. The user determination unit <NUM> compares the face image data acquired from the camera <NUM> with face image data stored in advance in the user database <NUM> and specifies the user who has gotten on the vehicle. In the present embodiment, the user who has gotten on the vehicle is specified as the user <NUM>. The reason why it is necessary to specify a user is to provide support suitable for the user. There is a case where one vehicle is shared by multiple users. In this case, it is necessary to specify the user who has gotten on the vehicle in order to provide support suitable for the user. If support is provided without specifying the user, the user may feel uncomfortable.

The support function selecting unit <NUM> selects support suitable for a scene from among the plurality of support functions. As shown in <FIG>, when a scene is "parking", the support function selecting unit <NUM> selects an AVM or automatic parking from among the plurality of support functions. Note that, the support function selecting unit <NUM> may select the AVM and automatic parking. When a scene is a "narrow road", the support function selecting unit <NUM> selects a side-down-view monitor or steering support from among the plurality of support functions. When a scene is "approach to a preceding vehicle", the support function selecting unit <NUM> selects an emergency stop brake or emergency avoidance steering from among the plurality of support functions. When a scene is a "lane deviation", the support function selecting unit <NUM> selects lane deviation prevention from among the plurality of support functions. When a scene is a "merging or lane change", the support function selecting unit <NUM> selects a blind spot warning or steering support from among the plurality of support functions. When a scene is a "right turn", the support function selecting unit <NUM> selects an emergency stop brake from among the plurality of support functions. When a scene is a "left turn", the support function selecting unit <NUM> selects a combination of an AVM and an ultrasonic sensor from among the plurality of support functions.

Here, support when a scene is "parking" will be described. A location when the unit determined last time that the user <NUM> drove dangerously will be referred to as a parking space A. Is is assumed that the user <NUM> goes to the parking space A again. The proposal unit <NUM> determines that the vehicle is in the parking space A, based on position information acquired from the position detecting unit <NUM>. In the exchange of the messages (exchange of the messages indicated by reference numerals <NUM> to <NUM>) made last time, the user <NUM> has accepted a support function. The acceptance result is recorded in the user database <NUM>. The support function selecting unit <NUM> selects a support function to be proposed to the user <NUM> by referring to the user database <NUM>. Here, it is assumed that automatic parking is selected. The support function selecting unit <NUM> outputs the selection result to the proposal unit <NUM>. The proposal unit <NUM> confirms to the user <NUM> whether to implement the support function. The reason why the unit confirms to the user whether to implement the support function again is to enhance the trust relationship between the user <NUM> and the vehicle. This confirmation may be made with voice using the speaker <NUM> or made by displaying characters on the display <NUM>. The user <NUM> answers to the confirmation by using the switch <NUM>. If the user <NUM> presses the switch <NUM>, it means that the user has accepted the support function. After receiving a signal indicating that the switch <NUM> is in an on state, the proposal unit <NUM> outputs an instruction for implementing the support function to the support function implementing unit <NUM>. The support function implementing unit <NUM>, which has received the instruction, controls the steering actuator <NUM>, the accelerator pedal actuator <NUM>, and the brake actuator <NUM>. This performs automatic parking.

When the support function is implemented, the data at that time is recorded in the user database <NUM>. As shown in <FIG>, the recorded data is the user names, date and time, locations, scenes, and implemented support functions.

Although a description has be given by assuming that the message creating unit <NUM> creates the messages <NUM> and <NUM> and outputs the messages to the robot head <NUM>, the present invention is not limited thereto. These kinds of messages may be created in advance. It is sufficient if the messages created in advance are stored in the storage device <NUM>. By referring to the storage device <NUM>, the message creating unit <NUM> can output appropriate messages to the robot head <NUM>. <FIG> shows examples of messages created in advance. If the user <NUM> is responsible for dangerous driving, examples of messages selected by the message creating unit <NUM> include a message "Something happened?", a message "What happened?", a message "What is the matter?", a message "Did you do something?", and a message "What did you do?". The message examples <NUM> is intended to indirectly cause the user <NUM> to admit the responsibility. Meanwhile, the message example <NUM> of <FIG> is intended to specifically prompt the user <NUM> to answer. Examples of the message example <NUM> include a message "Whose fault is it?" and a message "Who is responsible for this?" as shown in <FIG>.

In the above example, it is determined that the user <NUM> drove dangerously. Here, an entity driving the vehicle is not only the user <NUM>. Since the vehicle has automatic driving functions, driving without the intervention of the user <NUM> (automatic driving) is also performed. Normally, automatic driving is designed to prevent dangerous driving. However, due to unexpected factors, some sort of abnormality may occur in automatic driving. Here, the "abnormality" means a state which is not normal. The "abnormality" is a concept that includes not only a malfunction that prevents automatic driving from exhibiting original functions thereof, but also a failure that is not as severe as a malfunction and a warning sign of a malfunction. If an abnormality occurs in automatic driving, there is a possibility that the dangerous situations shown in the determination example in <FIG> may arise. A conversation example when an abnormality occurs in automatic driving will be described with reference to <FIG> shows a scene in which the user <NUM> is having conversations with the robot head <NUM>. The conversations are indicated by reference numerals <NUM> to <NUM>. Reference numerals <NUM> and <NUM> indicate the speech made by the robot head <NUM>. Reference numerals <NUM> and <NUM> indicate the speech made by the user <NUM>. The flow of the conversations is in the order of reference numerals <NUM>, <NUM>, <NUM>, and <NUM>. The conditions for outputting a message "Were you scared?" indicated by reference numeral <NUM> will be described below.

If the dangerous situation determining unit <NUM> determines that an abnormality has occurred in automatic driving, a signal indicating the determination result is transmitted to the responsibility determining unit <NUM>. The responsibility determining unit <NUM>, which has received the signal, determines who is responsible for dangerous driving. Here, the responsibility determining unit <NUM> determines that automatic driving (vehicle) is responsible for dangerous driving. A signal indicating the determination result is transmitted to the message creating unit <NUM>. The message creating unit <NUM>, which has received the signal, creates the message indicated by reference numeral <NUM>. The message creating unit <NUM> outputs the created message to the robot head <NUM>. As a result, the message indicated by reference numeral <NUM> is output with voice as shown in <FIG>. As shown in <FIG>, in response to the question "Were you scared?", the user <NUM> answers "Yes, a distance from another vehicle is too short!" (reference numeral <NUM>). This answer is a positive answer. Here, the "positive answer" means an answer in which the user <NUM> admits that automatic driving has been dangerous driving. The answer made by the user <NUM> is analyzed based on the same method described above. Based on the analysis result, the message creating unit <NUM> creates a message (Then, do you want to increase the distance from next time?) indicated by reference numeral <NUM>. The message indicated by reference numeral <NUM> is created, because the answer made by the user <NUM> has been positive. As shown in <FIG>, in response to the question "Then, do you want to increase the distance from next time?", the user <NUM> answers "Yes, please increase the distance!" (reference numeral <NUM>). This answer is a positive answer. Here, the "positive answer" is an answer for changing a parameter of a support function (automatic driving function). The answer indicated by reference numeral <NUM> is analyzed by the speech analyzing unit <NUM>. Then, it is determined whether the answer made by the user <NUM> is positive. A signal indicating the determination result is output to the parameter changing unit <NUM>. Next time, when automatic driving is performed, the parameter changing unit <NUM> changes a distance from another vehicle such that the distance becomes longer compared with that in previous automatic driving. The changed parameter is output to the support function implementing unit <NUM>. The support function implementing unit <NUM> controls the distance from another vehicle based on the changed parameter. As a result, it is possible to perform driving support suitable for a user's feeling.

The messages indicated by reference numerals <NUM> and <NUM> may also be created in advance in the same manner as the messages indicated by reference numerals <NUM> and <NUM>. When automatic driving (the vehicle) is responsible for dangerous driving, examples of messages selected by the message creating unit <NUM> include a message "Did you feel unsafe?", a message "Was the driving dangerous?", and a message "Were you scared?" as shown in <FIG>. Examples of other messages include a message "Was a brake applied too late?", a message "Was a distance from another vehicle too short?", a message "Was a preceding vehicle too close?", a message "Was an accelerator pressed too much?", a message "Too fast?", a message "Too slow?", a message "Was a steering wheel turned too late/too fast?", a message "Was the vehicle positioned too close to the right/left?", a message "Did vehicle sway?", and a message "Was vehicle in a jerky motion?".

A cause of occurrence of a dangerous situation is not limited to driving by the user <NUM> or automatic driving. For example, a cause may be driving by a user in another vehicle, automatic driving of another vehicle, a pedestrian, or the like. <FIG> shows a scene in which a dangerous situation arose due to a pedestrian <NUM> dashing out. Reference numeral <NUM> indicates a speech made by the robot head <NUM>. Reference numeral <NUM> indicates a speech made by the user <NUM>. The flow of conversations is in the order of reference numerals <NUM> and <NUM>. When a dangerous situation arises due to dashing out of the pedestrian <NUM>, the message creating unit <NUM> creates a message (Were you OK?) indicated by reference numeral <NUM> and outputs the message to the robot head <NUM>.

Next, an operation example of the driving support device <NUM> will be described with reference to the flowchart of <FIG> and <FIG>.

When an ignition is in an on state (YES in step S101), processing proceeds to step S103. The information that "the ignition is in an on state" means that a power supply of the vehicle is turned on. In steps S103 and S105, the dangerous situation determining unit <NUM> determines whether a dangerous situation has occurred using data acquired from the sensor <NUM>. If a dangerous situation has occurred (YES in step S105), the processing proceeds to step S107. In step S107, the responsibility determining unit <NUM> estimates a cause of occurrence of the dangerous situation, based on the data acquired from the sensor <NUM>. For example, if the dangerous situations shown in <FIG> occur due to driving by the user <NUM>, it is estimated that the user <NUM> is responsible for dangerous driving (YES in step S113). If the dangerous situations shown in <FIG> occur due to automatic driving functions of the host-vehicle, it is estimated that automatic driving (vehicle) is responsible for dangerous driving (NO in step S113). If a dangerous situation occurs due to driving by a user in another vehicle, automatic driving functions of another vehicle, or a pedestrian and the like, it is estimated that a user of another vehicle, another vehicle, or a pedestrian and the like is responsible for dangerous driving (NO in step S109). The "pedestrian and the like" includes a pedestrian, a bicycle, and a motorcycle.

In step S111, the message indicated by reference numeral <NUM> is output (see <FIG>). In step S115, the message indicated by reference numeral <NUM> is output (see <FIG>). The processing proceeds to step S117, and the speech acquisition unit <NUM> acquires an answer made by the user <NUM> using the microphone <NUM>. If an answer made by the user <NUM> is determined to be positive (YES in step S119), the message indicated by reference numeral <NUM> for proposing a support function is output (see <FIG>). If an answer by made the user <NUM> is determined to be negative (NO in step S119), a message indicating that the user <NUM> is responsible for dangerous driving is output.

In step S127, the message indicated by reference numeral <NUM> is output (see <FIG>). The processing proceeds to step S129, and the speech acquisition unit <NUM> acquires an answer made by the user <NUM> using the microphone <NUM>. If an answer made by the user <NUM> is determined to be positive (YES in step S131), the parameter changing unit <NUM> reflects a request made by the user <NUM> in control contents when automatic driving is performed next time (step S133). Specifically, the parameter changing unit <NUM> changes a parameter related to an automatic driving function. As an example of parameter change, a distance with another vehicle is changed to a longer distance. If an answer made by the user <NUM> is determined to be negative (NO in step S131), a parameter is not changed. The processing in steps S103 to S135 is repeated until the ignition is in an off state.

Next, an operation example of the driving support device <NUM> will be described with reference to the flowchart of <FIG>.

When the ignition is in an on state (YES in step S201), the processing proceeds to step S203. In step S203, the proposal unit <NUM> acquires position information from the position detecting unit <NUM>. In step S205, the proposal unit <NUM> determines, based on the position information, whether a current position of the vehicle is a position where a support function was proposed last time. The "position where a support function was proposed last time" will be referred to as a "position A". When the current position of the vehicle is the position A (YES in step S205), the support function selecting unit <NUM> refers to the user database <NUM> and proposes a support function to the user <NUM> (step S207). If the user <NUM> accepts the support function (YES in step S209), the support function implementing unit <NUM> implements the support function (step S211). If the user <NUM> does not accept the support function (NO in step S209), the support function implementing unit <NUM> does not implement the support function (step S213). Data when the vehicle passes the position A (YES in step S215) is recorded in the user database <NUM> (step S217). The processing in steps S203 to S217 is repeated until the ignition is in an off state.

As described above, the following actions and effects can be acquired in accordance with the driving support device <NUM> according to the present embodiment.

The driving support device <NUM> includes the sensor <NUM> for acquiring data of a space inside the vehicle and data of a space outside the vehicle, and the controller <NUM>. The controller <NUM> determines whether the vehicle is in an abnormal state, based on the data acquired by the sensor <NUM>. If the controller <NUM> determines that the vehicle is in an abnormal state, the controller <NUM> outputs a message indicating that the vehicle is in an abnormal state to the user <NUM> who is on the vehicle. The controller <NUM> acquires an answer made by the user <NUM> in response to the message using an input device. An example of an input device is the microphone <NUM>. By providing support according to an answer made by the user <NUM>, it is possible to provide driving support suitable for a feeling of the user <NUM>.

The information that "the vehicle is in an abnormal state" means a situation where there is a possibility of collision or accident of the vehicle. It is sufficient if the "possibility of collision or accident of the vehicle" is determined based only on the data acquired by the sensor <NUM>. It does not matter whether an entity performing driving is the user <NUM> or an automatic driving function. However, an entity performing driving may be considered as described later.

An answer made by the user <NUM> relates to a feeling indicating anxiety or danger about the condition of the vehicle.

If the controller <NUM> determines that an answer made by the user <NUM> in response to the message indicates the feeling of anxiety or danger, the controller <NUM> proposes the user to use a support function for supporting the user <NUM>. An example of an answer indicating the feeling of anxiety or danger is the message indicated by reference numeral <NUM> shown in <FIG>. As a result, it is possible to provide driving support suitable for a feeling of the user <NUM>.

The controller <NUM> estimates a cause of occurrence of the abnormal state, based on the data acquired by the sensor <NUM>. If the controller <NUM> estimates that a cause arises from driving by the user <NUM>, the controller <NUM> outputs a message for confirming responsibility to the user <NUM>. An example of the message for confirming responsibility is a message "Who is responsible for this?" shown in <FIG>. If the controller <NUM> determines that an answer made by the user <NUM> in response to the message is for admitting the responsibility, the controller <NUM> proposes the user to use a support function for supporting the user <NUM>. As a result, it is possible to provide driving support that is suitable for a feeling of the user <NUM>. In addition, by causing the user <NUM> himself/herself to admit the responsibility, it is possible to make the relationship between the user <NUM> and the vehicle friendly.

The messages include a message for confirming responsibility to the user <NUM>, a message concerning the condition of the vehicle, a message for confirming a feeling of the user <NUM>, or a message for confirming safety of the user <NUM>. An example of the "message for confirming responsibility to the user <NUM>" is a message "Who is responsible for this?" shown in <FIG>. An example of the "message concerning the condition of the vehicle" is a message "Did you apply a brake too late?" shown in <FIG>. An example of the "message for confirming a feeling of the user <NUM>" is a message "Were you scared?" shown in <FIG>. An example of the "message for confirming safety of the user <NUM>" is a message "Did you feel unsafe?" shown in <FIG>.

An example of the message for confirming responsibility to the user <NUM> is a message for confirming to the user <NUM> whether something has happened in the vehicle or in a periphery of the vehicle (see <FIG>).

If the controller <NUM> determines that an answer made by the user <NUM> in response to the message for confirming responsibility indicates that the user does not admit the responsibility, the controller <NUM> outputs a message indicating that the user <NUM> is responsible for the situation. This can provide, to the user <NUM>, an opportunity to change his/her attitude.

The controller <NUM> estimates a cause of occurrence of the abnormal state, based on the data acquired by the sensor <NUM>. If the controller <NUM> estimates that a cause arises from the automatic driving function, the controller <NUM> outputs a message for confirming whether the user <NUM> had a feeling of anxiety. An example of the "message for confirming whether the user <NUM> had a feeling of anxiety" is a message "Were you scared?" shown in <FIG>. Accordingly, it is possible to confirm whether the user <NUM> has a feeling of anxiety to automatic driving.

If the controller <NUM> determines that an answer made by the user <NUM> in response to the message for confirming anxiety indicates that the user had a feeling of anxiety, the controller <NUM> changes setting of a parameter of the automatic driving function. Specifically, the controller <NUM> changes the parameter of the automatic driving function to the safe side. An example of the parameter change is to increase a distance from another vehicle. As a result, it becomes possible to provide driving support suitable for a feeling of the user <NUM>. In addition, the reliability to automatic driving is enhanced.

Claim 1:
A driving support device (<NUM>) comprising:
a sensor (<NUM>) configured to acquire data of a space inside a vehicle and data of a space outside the vehicle; and
a controller (<NUM>),
wherein the controller (<NUM>) is configured to:
determine whether the vehicle is in an abnormal state based on the data acquired by the sensor (<NUM>);
upon determining that the vehicle is in the abnormal state, output a message indicating that the vehicle is in the abnormal state to a user on the vehicle;
acquire an answer from the user to the message via an input device (<NUM>); and
propose use of a support function for supporting the user based on the answer from the user to the message.