Information notification device, information notification program, factor analysis method, and on-vehicle system

Abstract

To provide a technique for analyzing a factor of discomfort of a user (factor of troublesomeness which the user feels) while suppressing a load on the user in operation or the like.SOLUTION: An information notification device performs: confirming presence / absence of discomfort of a user after notification of information; identifying a scene where the notification is executed when the discomfort exists; identifying cause candidates of the discomfort in response to the identified scene and a state of the user when the information is notified; identifying whether or not the cause of the discomfort is the notification based on a rule base from the identified cause candidates; identifying which one of notification mode elements in the notification is a factor of the discomfort when the cause of the discomfort is the notification; and correcting a notification method in response to the identified factor of the discomfort.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to an information notification device, an information notification program, a factor analysis method, and an in-vehicle system. [Background technology]

[0002] With the advancement of various sensing technologies in modern vehicles, the frequency and volume of various notifications (advice, warnings, etc.) from vehicles to drivers has increased for the purpose of safety and security, and there have been serious complaints that these notifications are bothersome. For this reason, measures have been taken such as setting notification-free areas (conditions), adjusting notification methods based on subject questionnaire surveys, and feedback control based on user reactions to notifications (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2018-179704 Summary of the Invention [Problem to be solved by the invention]

[0004] However, due to individual differences and the influence of the surrounding environment, it has been difficult to provide appropriate notifications.

[0005] In view of the above circumstances, the present invention aims to provide a technology that can analyze the causes of a user's discomfort (the causes of annoyance felt by the user) while minimizing the burden of operations, etc., placed on the user. [Means for solving the problem]

[0006] An exemplary information notification device of the present invention checks whether or not a user feels discomfort after receiving notification of information, and if the user feels discomfort, identifies the scene in which the notification was executed, identifies potential causes of the discomfort based on the identified scene and the user's situation at the time the information was notified, identifies from the identified potential causes based on a rule base whether or not the notification is the cause of the discomfort, and if the discomfort is caused by the notification, identifies which notification style element in the notification is the cause of the discomfort, and modifies the notification method based on the identified cause of the discomfort. [Effects of the Invention]

[0007] According to the exemplary present invention, the causes of the user's discomfort (the causes of the annoyance felt by the user) are identified without necessarily querying the user, so that the causes of the user's discomfort can be analyzed while minimizing the burden on the user of operations, etc. Then, by reflecting the results of this analysis in the notification method, it is possible to realize appropriate notifications according to individual differences, surrounding environmental conditions, etc., while minimizing the burden on the user of operations, etc. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of an in-vehicle system according to an exemplary embodiment of the present invention. [Figure 2] FIG. 1 is a diagram showing an example of the configuration of an information notification device; [Figure 3] FIG. 10 is a diagram showing an example of a notification target scene table. [Figure 4] FIG. 10 is a diagram showing an example of each coefficient data table; [Figure 5] A diagram showing an example of a notification history database. [Figure 6] FIG. 10 is a diagram showing an example of a notification method history database. [Figure 7] Flowchart showing information notification processing of the information notification device [Figure 8] Data structure diagram showing the results of extracting data records for the same scene as the current scene from the notification method history database. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the drawings.

[0010] <In-vehicle system configuration> 1 is a diagram showing an example of the configuration of an in-vehicle system SYS1 according to an exemplary embodiment of the present invention. The in-vehicle system SYS1 is mounted on a vehicle and includes an outside sensor 1, an inside sensor 2, a vehicle behavior sensor 3, a position sensor 4, a timing device 5, an information notification device 6, a display device 7, a speaker 8, and a vibration device 9.

[0011] The external sensor 1 is a sensor for detecting the surrounding conditions of a vehicle (host vehicle) on which the in-vehicle system SYS1 is installed. The external sensor 1 is, for example, a millimeter wave radar, an ultrasonic sensor, a LiDAR, a camera for capturing images of the surroundings of the host vehicle, etc. The external sensor 1 may be composed of one type of sensor or multiple types of sensors.

[0012] The interior sensor 2 is a sensor for detecting the state of the driver (user) of the vehicle. The state of the driver of the vehicle to be detected includes, for example, the emotions of the driver of the vehicle, the presence or absence of passengers in the vehicle (people around the user), and the state of the passengers in the vehicle. The interior sensor 2 is, for example, a camera that captures images of the interior of the vehicle, a microphone that captures sounds generated in the interior of the vehicle, a biosensor that measures biosignals of the driver of the vehicle, etc. The interior sensor 2 may be composed of one type of sensor or multiple types of sensors.

[0013] The vehicle behavior sensor 3 is a sensor for detecting the behavior of the host vehicle. The vehicle behavior sensor 3 is, for example, an accelerator sensor that detects the amount of operation of an accelerator pedal, a brake sensor that detects the amount of operation of a brake pedal, a steering angle sensor that detects the amount of operation of a steering wheel, etc.

[0014] The position sensor 4 is a sensor for detecting the position of the vehicle, and is configured by, for example, a GPS receiver that receives signals from multiple GPS (Global Positioning System) satellites and generates and outputs vehicle position information based on the received signals. The vehicle position information generated by the position sensor 4 represents the current position of the vehicle by longitude and latitude.

[0015] The timing device 5 generates and outputs a signal corresponding to the current date and time. The timing device 5 is configured with, for example, a quartz oscillator timing device, and has a built-in battery, so it operates without an external power supply and keeps accurate date and time. If the position sensor 4 is a GPS receiver, it can also be used as the timing device 5 because it has a timing function based on signals from GPS satellites.

[0016] The information notification device 6 is a device that notifies the driver of driving assistance information using images, sounds, and vibrations, and is configured by a computer.

[0017] The display device 7 is configured with a display device such as a liquid crystal display, and is installed in a position inside the vehicle that is visible to the driver of the vehicle.

[0018] The speaker 8 is installed in the passenger compartment of the vehicle and outputs a sound based on an instruction from the information notification device 6.

[0019] The vibration device 9 is configured by a vibration device such as an exciter, and is installed inside the steering wheel, the seat where the driver of the vehicle sits, etc., and vibrates based on an instruction from the information notification device 6.

[0020] <Configuration of information notification device> Fig. 2 is a diagram showing an example of the configuration of the information notification device 6. Note that Fig. 2 shows components necessary for explaining the features of this embodiment, and omits descriptions of general components.

[0021] The information notification device 6 of the exemplary configuration shown in FIG.

[0022] The communication unit 61 is an interface for communicating data with each of the outside sensor 1, inside sensor 2, vehicle behavior sensor 3, position sensor 4, timing device 5, information notification device 6, display device 7, speaker 8, and vibration device 9 shown in Figure 1 via the in-vehicle network.

[0023] The storage unit 62 is a storage device that stores various types of data and includes volatile memory and nonvolatile memory. The volatile memory may include, for example, RAM (Random Access Memory). The nonvolatile memory may include, for example, ROM (Read Only Memory), flash memory, or a hard disk drive. The nonvolatile memory stores computer-readable programs and data.

[0024] The storage unit 62 stores an information notification program 621, map data 622, a rule base 623, a notification target scene table 624, coefficient data tables 625A to 625G, a notification history database 626, and a notification method history database 627. In this embodiment, the information notification program 621 includes a navigation program for providing guidance on the route to the destination and points of interest.

[0025] The information notification program 621 is a program to be executed by the controller 63 .

[0026] The map data 622 is map-related data used for route guidance and the like, and includes road information, facility information, and point of interest information. The map data is divided into predetermined areas called meshes (for example, 100m square), and each mesh is stored as a separate file. The map data for the area to be used for processing and the like is selected from the map data 622 and used.

[0027] The rule base 623 is logic data for identifying the cause of discomfort felt by the driver (user) of the vehicle.

[0028] The notification target scene table 624 is a table that defines the types of scenes that are the target of notification, and stores detection conditions for the notification target scene type (conditions for the detection values ​​of each sensor) linked to each notification target scene type, as shown in Fig. 3. For example, the notification target scene table 624 shown in Fig. 3 stores data such as "SC2 (e.g., speed of 5 km / h or less continues for 5 minutes or more, and there is a vehicle within 5 m ahead)" as the detection condition for the notification target scene type "traffic jam."

[0029] The coefficient data tables 625A to 625G are data tables storing coefficients used in the calculation to estimate the cause of the user's discomfort, and each table is configured for each parameter type, with a coefficient set and stored for each specific parameter value (specific content). Note that the more likely a parameter value is to be the cause of the user's discomfort, the larger the corresponding coefficient value is set.

[0030] 4, the coefficient data table 625A is a data table in which the notification of a parameter type (presence or absence of notification) is associated with a coefficient A. In the example shown in Fig. 4, the value of the associated coefficient A is set to 1 when the parameter value is "notification present," and the value of the associated coefficient A is set to 0 when the parameter value is "not notification present."

[0031] 4, the coefficient data table 625B is a data table in which parameter types of scenes (scene types) are associated with coefficients B. In the example shown in FIG. 4, the value of coefficient B associated with the parameter value "high risk scene" is set to 3, and the value of coefficient B associated with the parameter value "high risk scene" is set to 1.

[0032] 4, the coefficient data table 625C is a data table in which the parameter types of vehicle behavior (types of host vehicle behavior) are linked to the coefficients C. In the example shown in FIG. 4, the value of the coefficient C linked to the parameter value "sudden braking or long-term low-speed driving" is set to 3, the value of the coefficient C linked to the parameter value "light braking or short-term low-speed driving" is set to 1, and the value of the coefficient C linked to the parameter value "normal vehicle behavior" is set to 0.

[0033] The coefficient data table 625D is a data table in which the driver's state of each parameter type is associated with a coefficient D, as shown in Fig. 4, for example. In the example shown in Fig. 4, the value of the coefficient D associated with the parameter value "state that has a strong impact on discomfort" is set to 2, the value of the coefficient D associated with the parameter value "state that has an impact on discomfort" is set to 1, and the value of the coefficient D associated with the parameter value "state without abnormality" is set to 0.

[0034] 4, the coefficient data table 625E is a data table in which the driver's recognition of a parameter type notification is linked to a coefficient E. In the example shown in FIG. 4, the value of the coefficient E linked to the parameter value "when the notification is recognized" is set to 3, the value of the coefficient E linked to the parameter value "when the notification is recognized and the driver responds" is set to 2, the value of the coefficient E linked to the parameter value "when recognition of the notification is delayed" is set to 1, and the value of the coefficient E linked to the parameter value "when the notification cannot be recognized" is set to 0.

[0035] Coefficient data table 625F is a data table in which the state of a passenger of a parameter type is linked to a coefficient F, as shown in Fig. 4, for example. In the example shown in Fig. 4, the value of coefficient F linked to the parameter value "when the passenger and the driver are talking" is set to 2, the value of coefficient F linked to "when the passenger is making a statement to alert the driver" is set to 1, the value of coefficient F linked to the parameter value "when the passenger is neither talking to the driver nor making a statement to alert the driver" is set to 0, and the value of coefficient F linked to the parameter value "when there is no passenger" is set to 0.

[0036] 4, the coefficient data table 625G is a data table in which the state of the surrounding environment for each parameter type is associated with a coefficient G. In the example shown in Fig. 4, the value of the coefficient G associated with the parameter value "in the case of afternoon sun, morning sun, heavy rain, or fog" is set to 1, and the value of the coefficient C associated with the parameter value "normal environment" is set to 0.

[0037] The notification history database 626 is a database that stores data related to past notifications, and is a database that links together, for example, as shown in FIG. 5, a date and time (when step S40 in FIG. 7, which will be described later, is executed), a notification (whether or not a notification was made) and a coefficient A, a scene (a type of scene) at the date and time and a coefficient B, a vehicle behavior (a type of behavior of the vehicle) for a certain period before and after the date and time and a coefficient C, a driver's state for a certain period immediately after the date and time and a coefficient D, a driver's awareness of the notification for a certain period immediately after the date and time and a coefficient E, a passenger's state for a certain period immediately after the date and time and a coefficient F, and a surrounding environment state for the date and time and a coefficient G. In the notification history database 626, current (latest) data is sequentially registered as the latest history over time. Note that past data is sequentially accumulated in the notification history database 626, but due to storage capacity limitations, older data is sequentially deleted when the storage capacity exceeds a predetermined capacity.

[0038] The notification method history database 627 is a database that stores data related to notification methods used in past notifications. For example, as shown in FIG. 6, the database associates the date and time of notification (when step S110 in FIG. 7, which will be described later, is executed) with the scene (type), notification means, notification content, notification time, notification intensity, and the driver's (user's) awareness of the notification. A default (initial setting) notification method is stored for each scene, and if the notification method is changed, new data is added and stored. In this embodiment, for ease of explanation, it is assumed that the "notification means" is sound, display, and vibration, the "notification content" is standard, simple, and detailed, the "notification time" is standard, long, and short, and the "notification intensity" is standard, strong, and weak.

[0039] The controller 63 includes a processor that performs arithmetic processing and the like. The processor may be configured to include, for example, a CPU (Central Processing Unit). The controller 63 may be configured with one processor or multiple processors. When configured with multiple processors, the processors may be connected to each other so that they can communicate with each other.

[0040] The controller 63 includes, as its functions, an acquisition unit 631, a notification target scene detection unit 632, an emotion determination unit 633, and a notification method determination unit 634. In this embodiment, the functions of the controller 63 are realized by the processor executing arithmetic processing in accordance with an information notification program 621 stored in the storage unit 62.

[0041] The acquisition unit 631 acquires the output signal of the vehicle exterior sensor 1, the output signal of the vehicle interior sensor 2, the output signal of the vehicle behavior sensor 3, the output signal of the position sensor 4, and the output signal of the timing device 5 via the communication unit 61.

[0042] The notification target scene detection unit 632 detects notification target scenes registered in the notification target scene table 624 based on output signals from various sensors such as the outside vehicle sensor 1. Specifically, the output signals from the various sensors are compared with the detection conditions for each notification target scene type in the notification target scene table 624 to detect the corresponding notification target scene.

[0043] The emotion determination unit 633 determines whether the driver is feeling uncomfortable based on the output signal of the interior sensor 2. For example, when the emotion determination unit 633 determines (estimates) that the driver is feeling uncomfortable, the emotion determination unit 633 determines (estimates) that the driver is feeling uncomfortable. The emotion determination unit 633 may determine whether the driver is feeling uncomfortable based on a user operation at the time of notification. For example, when the driver operates the volume operation unit to lower the volume at the time of notification, the emotion determination unit 633 determines (estimates) that the driver is feeling uncomfortable. Specifically, discomfort conditions for determining that the driver is feeling uncomfortable are stored, and when the outputs of various sensors, the driver's emotions, or the driver's operations on various devices, etc., satisfy the discomfort conditions, the emotion determination unit 633 determines that the driver is feeling uncomfortable.

[0044] The notification method determination unit 634 identifies the cause of discomfort if the driver feels discomfort after notification of driving assistance information based on the detection result of the notification target scene detection unit 632 and the determination result of the emotion determination unit 633 (determination result as to whether the driver feels discomfort), and modifies the notification method according to the identified cause of discomfort.

[0045] <Information notification process of the information notification support device> FIG. 7 is a flowchart showing the information notification process executed by the controller 63 of the information notification device 6 of FIG. 2. This flowchart shows the technical content of a computer program that causes a computer device to realize information processing. The computer program is stored in various readable non-volatile recording media and provided (sold, distributed, etc.). The computer program may consist of only one program, or may consist of multiple programs that work together. The information notification process executed by the controller 63 of the information notification device 6 of FIG. 2 includes a factor analysis process that identifies the cause of the driver's discomfort.

[0046] The information processing shown in FIG. 7 is initiated when the host vehicle starts and becomes capable of traveling, and is then repeatedly executed at appropriate time intervals (which may be set based on experiments, for example) that will ensure appropriate operation throughout the time period when driving assistance is required.

[0047] In step S10, the controller 63 (feeling determination unit 633) checks whether or not the driver (user) of the vehicle feels discomfort based on the output signals of the vehicle interior sensors 2 and the like acquired by the acquisition unit 131. When the processing of step S10 ends, the process proceeds to step S20.

[0048] In step S20, the controller 13 (notification target scene detection unit 632) determines whether or not a notification target scene has been detected based on the output signal of the vehicle exterior sensor 1 acquired by the acquisition unit 131 and the data of the notification target scene table 624 stored in the storage unit 62. If a notification target scene has not been detected (NO in step S20), the process returns to step S10. On the other hand, if a notification target scene has been detected (YES in step S20), the process proceeds to step S30.

[0049] In step S30, the controller 13 (notification method determination unit 634) determines a notification method according to the scene detected by the notification target scene detection unit 632. The controller 13 (notification method determination unit 634) uses the latest history in the notification method history database 627 stored in the storage unit 62 as the notification method for each scene detected by the notification target scene detection unit 632. The notification method may be, for example, a notification means (whether to use display, sound, or vibration), notification content (whether or not to include a message, etc.), notification time, notification strength (display size, sound volume, vibration volume), etc. Note that the determination by the notification method determination unit 634 also includes a determination not to provide notification based on the results of past modification of the notification method. After the processing of step S30 ends, the processing proceeds to step S40.

[0050] In step S40, the controller 13 (notification method determination unit 634) performs notification using the display device 7, speaker 8, and vibration device 9 in accordance with the notification method determined in step S30. Note that the processing of step S40 also includes cases where no notification is performed. When the processing of step S40 ends, the processing proceeds to step S50.

[0051] In step S50, the controller 63 (feeling determination unit 633) checks whether the driver (user) of the vehicle is feeling uncomfortable based on the output signals of sensors such as the interior sensor 2 acquired by the acquisition unit 131. If the driver (user) of the vehicle is not feeling uncomfortable (NO in step S50), the process proceeds to step S55. On the other hand, if the driver (user) of the vehicle is feeling uncomfortable (YES in step S50), the process proceeds to step S60.

[0052] In step S55, the controller 63 stores a data set of the output signal of the interior sensor 2 used in step S50 and the scene detected in step S20 (metadata indicating the scene) in the storage unit 62. This data set is used as reference data when estimating the emotion of the driver (user) of the vehicle, for example. When the processing of step S55 ends, the process returns to the processing of step S10.

[0053] In step S60, the controller 63 (emotion determination unit 633) uses the confirmation result in step S10 to confirm whether or not the driver (user) of the vehicle has been feeling uncomfortable before the notification. If the driver (user) of the vehicle has been feeling uncomfortable before the notification (YES in step S60), the notification is likely not the cause of the discomfort of the driver (user) of the vehicle, so the process returns to step S10. On the other hand, if the driver (user) of the vehicle has not been feeling uncomfortable before the notification (NO in step S60), the notification is likely the cause of the discomfort of the driver (user) of the vehicle, so the process proceeds to step S70 to identify the cause.

[0054] In step S70, the controller 63 (notification method determination unit 634) identifies the scene in which notification was executed based on the detection result in step S20. When the process of step S70 ends, the process proceeds to step S80.

[0055] In step S80, the controller 63 (notification method determination unit 634) registers data (including corresponding coefficient values) corresponding to the scene identified in step S70 and the state of the driver (user) of the vehicle at the time of execution of step S40 (a predetermined time period (an appropriate time length is set through experiments, etc.) before and after execution of step S40) as the latest history in the notification history database 626. In this embodiment, the controller 63 (notification method determination unit 634) registers data in the notification history database 626 that includes not only the state of the driver (user) of the vehicle but also the driver's (user's) awareness of the notification and the state of any passengers, thereby improving the accuracy of identifying potential causes of the discomfort of the driver (user) of the vehicle. Then, the controller 63 (notification method determination unit 634) identifies, as target data for subsequent cause narrowing down processing, items associated with coefficients having a value other than 0 in the latest history in the notification history database 626 as potential causes of the discomfort of the driver (user) of the vehicle. When the processing of step S80 is completed, the process proceeds to step S90.

[0056] In step S90, the controller 63 (notification method determination unit 634) identifies the cause of discomfort felt by the driver (user) of the vehicle from the candidate causes identified in step S80 based on the rule base 623. When the processing of step S90 ends, the process proceeds to step S100.

[0057] Specifically, the rule base 623 is a rule that, when one candidate cause is identified in step S80, the candidate cause identified in step S80 is the cause of discomfort felt by the driver (user) of the vehicle. Also, when multiple candidate cause causes are identified in step S80, the rule base 623 is a rule that groups the multiple candidate cause causes taking into account correlations between the candidate cause causes and narrows down the candidate cause causes by group.

[0058] The grouping may be performed based on, for example, experiments, etc., so as to appropriately narrow down the candidate causes. Such rules are created by, for example, collecting a large amount of data on the notification method and user discomfort at the time of notification, as well as data on the data types in the notification history database 626 through experiments, and analyzing this big data. The rule base created in this way is preferably updated as appropriate, stored in the server, and distributed from the server in response to a request from each information notification device 6 (controller 63).

[0059] Specifically, in this embodiment, the candidate causes linked to each of coefficients A, B, and E (values ​​(data) of whether or not a notification is made, scene type, and the driver's awareness of the notification) are grouped together in the first group, the candidate causes linked to each of coefficients C and D (values ​​(data) of vehicle behavior and driver state) are grouped together in the second group, the candidate causes linked to each of coefficients F and D (values ​​(data) of passenger state and driver state) are grouped together in the third group, and the candidate causes linked to each of coefficients G and D (values ​​(data) of the surrounding environment and driver state) are grouped together in the fourth group. The sum of the coefficients is calculated for each group, and the candidate causes are narrowed down to only the group with the largest sum of the coefficients.

[0060] The first group consists of data items closely related to the necessity of information notification, such as the presence or absence of information notification, the cause of notification (scene), and the state of awareness of the notification information. The second group consists of data items closely related to the driver's reaction (driver's state), such as vehicle behavior (movement based on the driver's driving operation) and the driver's state. The third group consists of data items closely related to the in-vehicle environment (such as the atmosphere), such as the state of passengers and the state of the driver. The fourth group consists of data items closely related to the driving environment, such as the state of the surrounding environment and the driver's state (largely influenced by the surrounding (driving) environment). Therefore, by summing the coefficients for each group and comparing these total values, it is possible to infer which types of causes have a significant impact on discomfort, that is, the target events or objects that cause discomfort.

[0061] If there is one corresponding (detailed) candidate cause in the group (target event causing discomfort) with the largest total coefficient value, that candidate cause is determined to be the cause of discomfort for the driver (user) of the vehicle.

[0062] If there are multiple candidate causes in the group with the largest total coefficient value, the cause of the discomfort is identified by taking into account the causal relationships of the narrowed-down candidate causes. For example, if the group with the largest total coefficient value is the third group, and there is a candidate cause linked to coefficient D (the value (data) of the driver's state) and a candidate cause linked to coefficient F (the value (data) of the passenger's state), it is considered that the candidate cause linked to coefficient D (the value (data) of the driver's state) is caused by the candidate cause linked to coefficient F (the value (data) of the passenger's state). Therefore, the candidate cause linked to coefficient F (the value (data) of the passenger's state) is determined to be the cause of the discomfort felt by the driver (user) of the vehicle. Specifically, this can be achieved by creating (based on experiments, etc.) a data table of combinations of candidate causes in each group and the narrowed-down results (results of cause estimation (determination)), and then narrowing down the causes based on the data table. The two-stage process of narrowing down candidate causes by grouping and identifying the cause of discomfort by taking into account the causal relationships makes it easy to identify the cause of discomfort.

[0063] In step S100, the controller 63 (notification method determination unit 634) determines (identifies) whether or not the cause of the discomfort of the driver (user) of the vehicle identified in step S90 is a notification. Specifically, if the group with the largest total value of the coefficients is the first group, it is determined that the cause of the discomfort is a notification. Note that, if the cause of the discomfort of the driver (user) cannot be identified in step S90, the controller 63 (notification method determination unit 634) considers that the cause of the discomfort of the driver (user) of the vehicle is a notification.

[0064] If the cause of discomfort of the driver (user) of the vehicle is not notification (NO in step S100), there is no need to modify the notification method, so the process returns to step S10. On the other hand, if the cause of discomfort of the driver (user) of the vehicle is notification (YES in step S100), the process proceeds to step S110.

[0065] In step S110, the controller 63 (notification method determination unit 634) identifies which element of the notification is causing discomfort to the driver (user) based on the data in the notification method history database 627 stored in the storage unit 62. When the processing of step S110 ends, the process proceeds to step S120.

[0066] Specifically, the controller 63 (notification method determination unit 634) identifies which element of the current notification is causing discomfort to the driver (user) of the vehicle, based on the difference between the notification method of the current notification and the notification method of a past notification in the same type of scene as the current notification. Then, the controller 63 (notification method determination unit 634) modifies the notification method according to the identified cause of discomfort to the driver (user) of the vehicle, and updates the notification method history database 627.

[0067] Here, a detailed specific example (specific example of step S110) of the method for changing the notification method (method for analyzing the cause of discomfort) will be described.

[0068] The controller 63 extracts data records of scenes (past scenes of a similar type) that are the same as the current scene (type) from the notification method history database 627. FIG. 8 is a data structure diagram showing the extraction results. The controller 63 performs information notification using the notification method of the latest data record, and if the notification causes discomfort to the driver (user), acquires the driver's information recognition at the time of the information notification and stores the acquired recognition as the recognition in the latest data record. The controller 63 also determines a new notification method according to a separately defined notification method determination rule, and generates and stores a new data record for the scene. The notification method determination rule is a rule that determines a new notification method based on, for example, the recognition in the latest notification method and the change history of the notification means. Specifically, the notification method determination rule can be defined by a data table in which the recognition and the change history pattern are two parameters (the length and width values ​​of the table), and the notification method is a resultant value determined by these parameter values ​​(the value of the frame defined by the length and width values ​​in the table). In other words, the controller 63 analyzes the cause of discomfort based on the notification method history (notification method and its result (driver's discomfort state)) (as the notification method converges, the cause is eventually analyzed).

[0069] The transition of the notification method will be explained based on Figure 8. Assume that at time ta1, information notification is performed in the default state, and as a result, the driver (user) feels discomfort, and the awareness at that time is low (discomfort is presumed to be due to a lack of information (anxiety, etc.)). In this case, because the driver's awareness was low using the notification method of data record DR0, low is stored as the awareness in data record DR0. In addition, because the driver feels discomfort, a new notification method for the next notification (notification strength: strong) is determined based on the notification method determination rule, and is stored in a newly created data record DR1.

[0070] In this example, when the driver's awareness is low when the driver feels discomfort, the rule is to change the control in the direction of increasing the awareness in the order of notification intensity, notification time, notification content, and notification means. Also, when the driver's awareness is high when the driver feels discomfort, the rule is to change the control in the direction of decreasing the awareness in the order of notification intensity, notification time, notification content, and notification means.

[0071] At time ta2, information notification is performed using the notification method of data record DR1, and as a result, the driver feels discomfort, and the awareness at that time is low (discomfort is presumed to be due to a lack of information (anxiety, etc.)). In this case, because the driver's awareness was low using the notification method of data record DR1, low is stored as the awareness in data record DR1. In addition, because the driver feels discomfort, a new notification method (notification time: long) for the next notification is determined based on the notification method determination rule, and is stored in a newly created data record DR2.

[0072] At time ta3, information notification is performed using the notification method of data record DR2, and as a result, the driver feels discomfort, and the awareness at that time is considered low (discomfort is presumed to be due to a lack of information (anxiety, etc.)). In this case, because the driver's awareness was low using the notification method of data record DR2, low is stored as the awareness in data record DR2. In addition, because the driver feels discomfort, a new notification method (notification content: details) for the next notification is determined based on the notification method determination rule, and is stored in a newly created data record DR3.

[0073] At time ta4, information notification is performed using the notification method of data record DR3, and as a result, the driver feels discomfort, and the awareness at that time is low (discomfort is presumed to be due to a lack of information (anxiety, etc.)). In this case, since the driver's awareness was low using the notification method of data record DR3, low is stored as the awareness in data record DR3. In addition, since the driver feels discomfort, a new notification method (notification means: sound / display) for the next notification is determined based on the notification method determination rule, and is stored in a newly created data record DR4.

[0074] At time ta5, information notification is performed using the notification method of data record DR4, and as a result, the driver feels discomfort, and the awareness at that time is high (discomfort is presumed to be information overload (annoyance, etc.)). In this case, because the driver's awareness was high using the notification method of data record DR4, high is stored as the awareness in data record DR4. In addition, because the driver feels discomfort, a new notification method for the next notification (notification intensity: standard) is determined based on the notification method determination rule, and is stored in a newly created data record DR5 (awareness is undetermined).

[0075] Returning to the description of Fig. 7, in step S120, the controller 63 (notification method determination unit 634) makes an inquiry to the driver (user) of the vehicle using the speaker 8 as necessary. When the processing of step S120 ends, the process proceeds to step S130.

[0076] Specifically, if it is not possible to identify which element of the notification is causing the driver (user) discomfort in step S110, an inquiry is made in step S110 that will help identify which element of the notification is causing the driver (user) discomfort. The response from the driver (user) of the vehicle is detected by the interior sensor 2, and the controller 63 (notification method determination unit 634) identifies which element of the notification is causing the driver (user) discomfort based on the response from the driver (user) of the vehicle. Then, the controller 63 (notification method determination unit 634) modifies the notification method according to the identified factor of discomfort of the driver (user) of the vehicle and updates the notification method history database 627. The processing of step S120 makes it possible to more reliably analyze the factor of discomfort of the driver (user), and more reliably realize appropriate notification according to individual differences, surrounding environmental conditions, etc.

[0077] Note that a method may be adopted in which no inquiry is made to the driver (user) even when it is not possible to identify whether the cause of discomfort is present (the process of step S120 is omitted), that is, a method may be adopted in which the cause analysis is left to the controller 63. Also, a method may be adopted in which an inquiry is made to the driver (user) when a situation in which it is not possible to identify whether the cause of discomfort is present continues for a predetermined threshold number of times or more, or a method in which an inquiry is made based on an operation by the driver (user) to report the cause of discomfort.

[0078] In step S130, the controller 63 (notification method determination unit 634) modifies, if necessary, the rule base 623. When the process of step S130 ends, the process returns to the process of step S10.

[0079] Specifically, if the cause of the driver's (user's) discomfort cannot be identified in step S90, the controller 63 (notification method determination unit 634) communicates with the server using the communication unit 61, acquires an additional coefficient data table, a modified coefficient data table, and modification details of the rule base 623 from the server, and modifies the rule base 623. The processing of step S130 makes it possible to more reliably analyze the cause of the driver's (user's) discomfort, and more reliably realize appropriate notification according to individual differences, surrounding environmental conditions, and the like.

[0080] Note that a method may be adopted in which the rule base 623 is not automatically modified even when it is not possible to identify whether it is a cause of discomfort, etc. Alternatively, a method may be adopted in which the rule base 623 is modified when a situation in which it is not possible to identify whether it is a cause of discomfort continues for a predetermined threshold number of times or more, or a method in which the rule base 623 is modified based on an instruction operation to modify the rule base 623 by the driver (user).

[0081] The processing of steps S10 to S110 identifies the cause of the discomfort of the driver (user) (the cause of the annoyance felt by the driver (user)) without necessarily querying the driver (user), so it is possible to analyze the cause of the discomfort of the driver (user) while minimizing the burden of operations, etc. on the driver (user). Then, by reflecting the results of this analysis in the notification method, it is possible to realize appropriate notification according to individual differences, surrounding environmental conditions, etc., while minimizing the burden of operations, etc. on the driver (user).

[0082] <Notes, etc.> Various technical features disclosed in the description of the present invention may be modified in various ways without departing from the spirit of the technical creation. Furthermore, multiple embodiments and modifications disclosed in the description of the present invention may be combined to the extent possible.

[0083] In the above-described embodiment, the controller 63 of the information notification device 6 includes an acquisition unit 631, a notification target scene detection unit 632, an emotion determination unit 633, and a notification method determination unit 634. However, a server capable of communicating with the information notification device 6 may include at least a portion of the notification target scene detection unit 632, the emotion determination unit 633, and the notification method determination unit 634 in place of the controller 63 of the information notification device 6. [Explanation of symbols]

[0084] 1. Outside vehicle sensor 2. Vehicle interior sensors 3 Vehicle behavior sensor 4 Position Sensor 5 Timing device 6 Information notification device 7 Display device 8 speakers 9 Vibration device SYS1 In-vehicle system

Claims

1. Check whether the user feels any discomfort after receiving the information, Identifying a scene in which the notification was executed when the discomfort was felt; identifying a possible cause of the discomfort according to the identified scene and the user's situation at the time of notification of the information; Identifying whether the notification is the cause of the discomfort based on a rule base from the identified cause candidates; If the cause of the discomfort is the notification, identify which notification aspect element in the notification is a factor in the discomfort; The information notification device modifies a notification method depending on the identified cause of discomfort.

2. the cause candidate belongs to one of a plurality of cause groups that are set in consideration of correlations between the cause candidate candidates; Identifying a cause group based on a specific situation of each of the discomfort cause candidates belonging to each of the discomfort cause groups; Identifying a cause corresponding to the identified cause group as a cause of the discomfort; The information notification device according to claim 1 .

3. adding a coefficient to each of the cause candidates according to the identified scene and the user's situation at the time of notification of the information; aggregating the coefficients of each of the cause candidates for each of the cause groups; Identifying the cause corresponding to the cause group with the largest aggregated value as the cause of the discomfort. The information notification device according to claim 2 .

4. Identifying the cause of the discomfort based on the notification mode of the information and the notification history in similar scenes in the past. The information notification device according to claim 1 .

5. The information notification device according to claim 1 , further comprising: an inquiry to the user regarding the cause of the discomfort depending on a specific state of the cause of the discomfort.

6. The information notification device according to claim 1 , wherein the rule base is modified in accordance with a specific clause of the cause of the discomfort.

7. The information notification device according to claim 1 , wherein the user's status includes the user's awareness of the notification.

8. The information notification device according to claim 1 , wherein the user's situation includes a presence state of people around the user.

9. Checking whether the user feels any discomfort after receiving the information; Identifying a scene in which the notification was executed when the discomfort was felt; Identifying a possible cause of the discomfort according to the identified scene and the user's situation at the time of notification of the information; Identifying whether the notification is the cause of the discomfort based on a rule base from the identified cause candidates; Identifying which notification aspect element in the notification is a factor in the discomfort when the discomfort is caused by the notification; Modifying a notification method in response to the identified cause of discomfort; An information notification program that causes a computer to execute the above.

10. Check whether the user feels any discomfort after receiving the information, Identifying a scene in which the notification was executed when the discomfort was felt; identifying a possible cause of the discomfort according to the identified scene and the user's situation at the time of notification of the information; Identifying whether the notification is the cause of the discomfort based on a rule base from the identified cause candidates; A factor analysis method for identifying, when the cause of the discomfort is the notification, which notification aspect element in the notification is a factor in the discomfort.

11. An in-vehicle system including a detection device that detects discomfort of a user and an information notification device that notifies the user of driving assistance information using images, sounds, and vibrations, The information notification device confirming whether or not the driver feels discomfort after receiving the driving assistance information based on a detection result of the detection device; Identifying a scene in which the notification was executed when the discomfort was felt; Identifying a possible cause of the discomfort according to the identified scene and the user's situation at the time of notification of the driving assistance information; Identifying whether the notification is the cause of the discomfort based on a rule base from the identified cause candidates; If the cause of the discomfort is the notification, identify which notification aspect element in the notification is a factor in the discomfort; The in-vehicle system modifies a notification method depending on the identified cause of the discomfort.

Images