JP2009237104A - Driving simulation device, driving simulation method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a driving simulation device, a driving simulation method, and a program by which a dangerous situation high in occurrence probability of accidents is greated in the consideration of actuality. <P>SOLUTION: The driving simulation device 1 includes: a reference information recording section 17 in which load reference information to be the reference for calculating driver load amount to a driver is recorded in advance; a driver load amount calculation section 18 calculating the driver load amount on the basis of the load reference information and the situation of a virtual moving body or the situation of the driver; a target load recording section 19 recording the target load information indicating the target load amount to which the driver is to be subjected; and a load amount control section 20 which instructs a scenario execution section 16 to modify a sub-task scenario or modify the execution state of the sub-task scenario so that the driver load amount is reduced when the driver load amount is larger than the target load amount and the driver load amount is increased when the drive load amount is smaller than the target load amount. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a driving simulation apparatus, a driving simulation method, and a program for realizing a virtual space including a virtual road traffic environment and a virtual moving body that can travel in the virtual road traffic environment according to a driving operation by a driver.

  Conventionally, a driving simulation device (driving simulator) that simulates driving / running of a vehicle in a virtual space is known (see, for example, Patent Documents 1 to 3). In general, the driving simulation apparatus displays a video outside the vehicle viewed from the window of the driver by a three-dimensional display on a screen and outputs sounds generated when the vehicle travels, such as engine sound, road noise, and wind noise, from a speaker. That is, by performing a driving operation on a virtual moving body (for example, an automobile) in a virtual space via an input device such as a steering handle, an accelerator pedal, a brake pedal, and a shift lever that is provided in the same manner as a real vehicle, Control the behavior of moving objects. In addition, the behavior of a virtual obstacle (for example, a tricycle, an automobile, a motorcycle, a bicycle, a pedestrian, etc.) that can become an obstacle to the virtual moving body is usually controlled by a control program that operates on the driving simulation apparatus. In addition, an operation simulation apparatus provided with a fluctuation generating apparatus is also known. According to the driving simulation apparatus provided with the shake generating device, for example, the driver can be caused to experience a vibration associated with acceleration or deceleration while the vehicle is traveling.

  Such a driving simulation device is used, for example, for driving training that increases the risk prediction ability of the driver by causing the driver to experience a simulated accident as part of safe driving education at a driving school or the like. The driving simulation device is also used for research for analyzing the behavior of the driver or evaluating the driving support device under various conditions, for example. Note that the driving support device provides the driver with information based on information detected by various sensors (for example, position information of surrounding vehicles) in order to prevent an accident caused by a driver's recognition error or judgment error. This is a device that provides information, gives warnings, or performs intervention control on vehicles. Furthermore, the driving simulation device is also used for amusement such as car racing games.

  Here, in the driving simulation apparatus for driving training, it is necessary to reproduce a dangerous situation in which an accident occurs in order to make the driver simulate an accident. Also, in the driving simulation device for research, it is necessary to reproduce a dangerous situation in which an accident occurs in order to quantitatively verify the accident prevention effect by the driving support device. In order to reproduce a dangerous situation in which an accident occurs, a method for causing a driver to perform an operation (subtask) other than the driving operation during driving is known (see, for example, Non-Patent Document 1). Here, the subtasks include, for example, a mental calculation task in which the driver performs mental calculation, a memorization task in which the driver memorizes information, an operation task in which the driver performs an operation, and the like. Note that the mental calculation task corresponds to, for example, an act of having a conversation with a passenger in actual driving. The memorization task corresponds to, for example, an act of memorizing a third party's telephone number or an act of memorizing a mark for a destination in actual driving. Furthermore, the operation task corresponds to, for example, an act of operating a radio or an act of operating a car navigation system.

  That is, by allowing the driver to perform a subtask during driving, the driver is prevented from concentrating on driving operation (main task) (so-called driver distraction). Since concentration on driving operation is hindered, it becomes easy for a driver to make a recognition error and a determination error. As a result, it is possible to create a dangerous situation with a high probability of an accident.

However, in order to actively create a dangerous situation with a high probability of an accident, the driver is required to perform a subtask with a load that is impossible in reality, or multiple that are impossible in reality If the driver performs the sub-task, the training may fail to satisfy the driver or the driver assistance apparatus may not be evaluated properly. Further, even when the subtask is performed on the driver, if the accident or the state just before the accident is insufficient, it is difficult for the driver to make a recognition error or a determination error. Furthermore, if the driver performs the same subtask continuously, the driver gets used to the subtask, so that it is difficult for the driver to make a recognition error or a determination error. As a result, a dangerous situation with a high probability of an accident cannot be created. In other words, by causing the driver to experience a simulated accident, the driver deviates from the purpose of driving training to improve the driver's risk prediction ability. Moreover, unless a dangerous situation with a high probability of occurrence of an accident can be created, a proper evaluation of the driving assistance device cannot be performed.
JP-A-6-118866 JP 2002-72224 A JP 2007-264055 A Makoto Ito, Hiroshi Furukawa, Toshiyuki Inagaki, “Detection of high-risk mental state based on evaluation of consistency between traffic conditions and driving behavior”, Proceedings of the Society of Instrument and Control Engineers System and Information Division 2005, 2005, p112- p117

  The present invention has been made in view of the above-described problems, and the purpose thereof is a driving simulation apparatus, a driving simulation method, and a driving simulation apparatus capable of creating a dangerous situation with a high probability of occurrence of an accident while considering reality. And to provide a program.

  In order to achieve the above object, a driving simulation apparatus according to the present invention is a simulation management that realizes a virtual space including a virtual road traffic environment and a virtual moving body that can travel in the virtual road traffic environment according to a driving operation by a driver. In the driving simulation apparatus comprising a unit, when an operation other than the driving operation by the driver is a subtask, an output unit for giving an instruction to the driver, and for causing the driver to perform the subtask A scenario recording unit in which a subtask scenario is recorded in advance and a subtask scenario recorded in the scenario recording unit are read out, and the subtask scenario is executed according to the subtask scenario by executing the read out subtask scenario. Scenario execution unit that outputs to the driver via the Reference information recording unit in which load reference information serving as a reference for calculating a driver load received by the driver is recorded in advance, load reference information recorded in the reference information recording unit, and the virtual moving body Or a driver load amount calculation unit that calculates the driver load amount received by the driver based on the situation of the driver or the driver, and target load information indicating the target load amount that the driver should receive A target load recording unit for recording, and when the driver load amount is larger than the target load amount, the driver load amount is decreased, and when the driver load amount is smaller than the target load amount, A load amount control unit that instructs the scenario execution unit to change the subtask scenario or change the execution status of the subtask scenario in order to increase the driver load amount;

  According to the driving simulation apparatus of the present invention, the driver load amount calculation unit receives the driver based on the load reference information recorded in the reference information recording unit and the situation of the virtual moving body or the situation of the driver. Calculate the driver load. In the target load recording unit, target load information indicating the target load amount that the driver should receive is recorded. Here, when the driver load amount is larger than the target load amount, the load amount control unit causes the scenario execution unit to change the subtask scenario or change the execution status of the subtask scenario in order to reduce the driver load amount. Instruct. As a result, the driver load received by the driver can be reduced. In addition, when the driver load amount is smaller than the target load amount, the load amount control unit changes the subtask scenario or the execution status of the subtask scenario to the scenario execution unit in order to increase the driver load amount. Instruct. As a result, the driver load received by the driver can be increased. As a result, the driving simulation apparatus of the present invention can create a dangerous situation with a high probability of occurrence of an accident while considering reality.

  In order to achieve the above object, a driving simulation apparatus according to the present invention is a simulation management that realizes a virtual space including a virtual road traffic environment and a virtual moving body that can travel in the virtual road traffic environment according to a driving operation by a driver. In the driving simulation apparatus comprising a unit, when an operation other than the driving operation by the driver is a subtask, an output unit for giving an instruction to the driver, and for causing the driver to perform the subtask A scenario recording unit in which a subtask scenario is recorded in advance and a subtask scenario recorded in the scenario recording unit are read out, and the subtask scenario is executed according to the subtask scenario by executing the read out subtask scenario. Scenario execution unit that outputs to the driver via the A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance, the load reference information recorded in the reference information recording unit, and the virtual moving body Or a driver load amount calculation unit that calculates a driver load amount received by the driver based on a situation of the driver or the driver state, and the subtask defined by a change with time of the driver load amount A condition information recording unit in which condition information indicating a scenario execution start condition and a stop condition is recorded in advance, and a change in the driver load amount matches the start condition while the execution of the subtask scenario is stopped In such a case, the scenario execution unit is instructed to start execution of the subtask scenario, and the change in the driver load amount is changed during the execution of the subtask scenario. If that matches the, as to stop the execution of the sub-task scenario, and a scenario control unit for instructing to the scenario execution unit.

  According to the driving simulation apparatus of the present invention, the driver load amount calculation unit receives the driver based on the load reference information recorded in the reference information recording unit and the situation of the virtual moving body or the situation of the driver. Calculate the driver load. In the condition information recording unit, condition information indicating a start condition and a stop condition for executing the subtask scenario, which is determined by a change in the driver load amount with time, is recorded in advance. Here, the scenario control unit instructs the scenario execution unit to start the execution of the subtask scenario when the change in the driver load amount matches the start condition while the execution of the subtask scenario is stopped. Instruct. The scenario control unit instructs the scenario execution unit to stop the execution of the subtask scenario when the change in the driver load amount matches the stop condition during the execution of the subtask scenario. As a result, the driving simulation apparatus of the present invention can create a dangerous situation with a high probability of occurrence of an accident while considering reality.

  In order to achieve the above object, a driving simulation method according to the present invention is a simulation management that realizes a virtual space including a virtual road traffic environment and a virtual moving body that can travel in the virtual road traffic environment according to a driving operation by a driver. And a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask when the operation other than the driving operation by the driver is a subtask, and the driving the driver is receiving A reference information recording unit in which load reference information serving as a reference for calculating a driver load amount is recorded in advance, and a target load recording unit that records target load information indicating a target load amount to be received by the driver A driving simulation method in which a computer executes processing, wherein an output unit included in the computer is provided to the driver An output step for giving an instruction, and a scenario execution unit included in the computer reads out the subtask scenario recorded in the scenario recording unit, and executes the read out subtask scenario, thereby executing a subtask execution instruction according to the subtask scenario. A scenario execution step for outputting to the driver via the output step, a driver load amount calculation unit included in the computer, load reference information recorded in the reference information recording unit, and a situation of the virtual moving body Alternatively, based on the driver's situation, a driver load amount calculation step for calculating a driver load amount received by the driver, and a load amount control unit provided in the computer, the driver load amount is When it is larger than the target load amount, the driver load amount is decreased, and the driver load amount is smaller than the target load amount. If smaller in order to increase the driver's load, and a load control step of instructing a change or changes to the running state of the sub-task scenario of the sub-task scenario to the scenario execution process.

  In order to achieve the above object, a driving simulation method according to the present invention is a simulation management that realizes a virtual space including a virtual road traffic environment and a virtual moving body that can travel in the virtual road traffic environment according to a driving operation by a driver. And a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask when the operation other than the driving operation by the driver is a subtask, and the driving the driver is receiving A reference information recording unit in which load reference information serving as a reference for calculating a driver load amount is recorded in advance, and a start condition and a stop condition for execution of the subtask scenario, which are determined by a change with time of the driver load amount, A driving simulation in which a computer having a condition information recording unit in which condition information indicating the condition is recorded is executed. The output unit provided in the computer provides an output process for giving an instruction to the driver, and the scenario execution unit provided in the computer reads out the subtask scenario recorded in the scenario recording unit. A scenario execution step for causing the driver to output a subtask execution instruction according to the subtask scenario by executing the read subtask scenario, and a driver load amount calculation unit included in the computer, Driver load calculation that calculates the driver load received by the driver based on the load reference information recorded in the reference information recording unit and the status of the virtual moving body or the driver. While the process and the scenario control unit included in the computer are stopped from executing the subtask scenario When the change in the driver load amount matches the start condition, the scenario execution step is instructed to start execution of the subtask scenario, and the driver load amount is executed during the execution of the subtask scenario. A scenario control step for instructing the scenario execution step to stop the execution of the subtask scenario when the change in the condition matches the stop condition.

  In order to achieve the above object, a program according to the present invention includes a simulation management unit that realizes a virtual space including a virtual road traffic environment and a virtual moving body that can travel in the virtual road traffic environment according to a driving operation by a driver; A scenario recording unit in which a subtask scenario for causing the driver to perform the subtask when the operation other than the driving operation by the driver is a subtask, and the driver load received by the driver A computer including a reference information recording unit in which load reference information serving as a reference for calculating the amount is recorded in advance, and a target load recording unit that records target load information indicating a target load amount to be received by the driver A program for executing a process, which is recorded in the scenario recording unit and an output process for giving an instruction to the driver; By reading out the subtask scenario and executing the read out subtask scenario, a subtask execution instruction according to the subtask scenario is output to the driver via the output process, and recorded in the reference information recording unit A driver load amount calculation process for calculating a driver load amount received by the driver based on the load reference information and the status of the virtual moving body or the driver status; and the driver load amount In order to decrease the driver load amount when the driver load amount is smaller than the target load amount, and to increase the driver load amount when the driver load amount is smaller than the target load amount. A load amount control process for instructing the scenario execution process to change or change the execution status of the subtask scenario. To be executed by the over data.

  In order to achieve the above object, a program according to the present invention includes a simulation management unit that realizes a virtual space including a virtual road traffic environment and a virtual moving body that can travel in the virtual road traffic environment according to a driving operation by a driver; A scenario recording unit in which a subtask scenario for causing the driver to perform the subtask when the operation other than the driving operation by the driver is a subtask, and the driver load received by the driver A reference information recording unit in which load reference information serving as a reference for calculating the amount is recorded in advance, and a start condition and a stop condition for execution of the subtask scenario, which are determined by a change with time of the driver load amount A program that causes a computer including a condition information recording unit in which condition information is recorded in advance to execute processing, An output process for giving an instruction to the subtask scenario, and a subtask scenario recorded in the scenario recording unit is read out, and the subtask scenario is executed according to the subtask scenario by executing the read subtask scenario. The driver receives the scenario execution process to be output to the driver via the load reference information recorded in the reference information recording unit and the situation of the virtual moving body or the situation of the driver. If the change in the driver load amount matches the start condition while the execution of the subtask scenario is stopped while the execution of the subtask scenario is stopped, the subtask scenario is executed. The scenario execution process is instructed to start, and the driver load amount is changed during the execution of the subtask scenario. If a is consistent with the stop condition, to stop the execution of the sub-task scenario, to execute and scenario control process for instructing to the scenario execution processing on the computer.

  As described above, the driving simulation apparatus, the driving simulation method, and the program of the present invention have an effect that it is possible to create a dangerous situation with a high probability of occurrence of an accident while considering the reality.

  In an embodiment of the present invention, the driving simulation device further includes a correspondence recording unit in which a correspondence relationship between the subtask scenario and a load of the subtask scenario is recorded in advance, in order to reduce the driver load amount, When the instruction to change the subtask scenario is issued from the load amount control unit, the scenario execution unit refers to the correspondence recording unit, thereby substituting the currently executing subtask scenario more than the subtask scenario. In order to change to a sub-task scenario with a low load and to increase the driver load amount, when the instruction to change the sub-task scenario is given from the load amount control unit, the scenario execution unit, the correspondence recording unit The subtask scenario currently being executed can be referred to Preferably in a manner to change the high load sub task scenario. According to this aspect, when the instruction to change the subtask scenario is issued from the load amount control unit in order to reduce the driver load amount, the scenario execution unit changes to the subtask scenario with a low load. The driver load received by the vehicle can be reduced. In addition, when an instruction to change the subtask scenario is issued from the load amount control unit in order to increase the driver load amount, the scenario execution unit changes to a subtask scenario with a high load. The driver load can be increased.

  In an embodiment of the present invention, the driving simulation device includes a correspondence relationship in which a correspondence relationship between a parameter representing a degree of load to be received by the driver defined in the subtask scenario and a load of the parameter is recorded in advance. A recording unit, and when there is an instruction from the load amount control unit to change the execution status of the subtask scenario in order to reduce the driver load amount, the scenario execution unit includes the correspondence relationship recording unit , The parameter in the currently executed subtask scenario is changed to a parameter having a lower load than the parameter, and an instruction to change the execution status of the subtask scenario is issued in order to increase the driver load. In the case of being from the load amount control unit, the scenario execution unit refers to the correspondence recording unit And by the parameters of the sub-task scenario currently running, preferably in the manner of changing to a higher load than the parameter parameter. According to this aspect, in order to reduce the driver load amount, when there is an instruction from the load amount control unit to change the execution status of the subtask scenario, the scenario execution unit changes to a low load parameter. The amount of driver load received by the driver can be reduced. In addition, when an instruction to change the execution status of the subtask scenario is given from the load amount control unit in order to increase the driver load amount, the scenario execution unit changes to a parameter with a high load. It is possible to increase the driver load amount.

  In an embodiment of the present invention, the driving simulation device is configured such that when the instruction to change the execution status of the subtask scenario is issued from the load amount control unit to reduce the driver load amount, the scenario execution unit If the instruction to change the execution status of the subtask scenario is issued from the load amount control unit in order to stop the currently executing subtask scenario and increase the driver load amount, the scenario execution unit It is preferable that the execution of a new subtask scenario is started. According to this aspect, in order to reduce the driver load amount, when an instruction to change the execution status of the subtask scenario is given from the load amount control unit, the scenario execution unit stops the currently executing subtask scenario. As a result, the driver load received by the driver can be reduced. In addition, when an instruction to change the execution status of the subtask scenario is given from the load amount control unit in order to increase the driver load amount, the scenario execution unit starts executing a new subtask scenario. The amount of driver load received by the vehicle can be increased.

  In an embodiment of the present invention, the driving simulation device is accessible to a dozing detection device that detects a sign of the driver's dozing, and the target load recording unit includes a plurality of different target load amounts. The target load information is recorded in advance, and the driving simulation device detects that the driver's drowsy sign is detected by the drowsiness detection device as compared to the case where the driver's drowsy sign is not detected. It is preferable to further include a target load selection unit that selects one target load information from a plurality of pieces of target load information recorded in the target load recording unit so that the target load amount becomes low. According to this aspect, when a sign of a driver's sleep is detected, one target load information can be selected from a plurality of target load information so that the target load amount is reduced. Thereby, it can avoid that a driver | operator's consciousness recovers and it guide | induces to a safe state. As a result, it is possible to create a dangerous situation with a high probability of an accident.

  In an embodiment of the present invention, the driver load amount calculation unit acquires driving operation information related to a driving operation by the driver from the simulation management unit, and records the acquired driving operation information and the reference information recording unit. It is preferable that the driver load amount received by the driver is calculated based on the load reference information. According to this aspect, the driver load received by the driver can be calculated according to the driving operation by the driver.

  In an embodiment of the present invention, the driver load amount calculation unit acquires road traffic information indicating the virtual road traffic environment from the simulation management unit, and records the acquired road traffic information and the reference information recording unit. It is preferable that the driver load amount received by the driver is calculated based on the load reference information. According to this aspect, the driver load received by the driver can be calculated according to the virtual road traffic environment.

  In an embodiment of the present invention, the driving simulation device is accessible to a biological reaction detection device that detects a biological reaction of the driver, and the driver load amount calculation unit is detected by the biological reaction detection device. It is preferable that the driver load received by the driver is calculated based on the driver's biological reaction and the load reference information recorded in the reference information recording unit. According to this aspect, the driver load received by the driver can be calculated according to the biological reaction of the driver.

  In an embodiment of the present invention, the driving simulation device further includes an execution result detection unit that detects an execution result of the subtask when the driver performs a subtask according to the execution of the subtask scenario by the scenario execution unit, The driver load amount calculation unit is configured so that the driver load received by the driver based on the execution result of the subtask detected by the execution result detection unit and the load reference information recorded in the reference information recording unit. It is preferable that the amount is calculated. According to this aspect, the driver load received by the driver can be calculated according to the execution result of the subtask when the driver performs the subtask.

  In an embodiment of the present invention, a plurality of load reference information that are different from each other are recorded in the reference information recording unit in advance, and the driving simulation device is characterized by the driving operation by the driver, the driver An attribute information recording unit that records driver attribute information indicating characteristics of the biological reaction of the driver, or characteristics of an execution result of the subtask when the driver performs a subtask, and a driver recorded in the attribute information recording unit It is preferable to further include a reference information selection unit that selects one load reference information from among a plurality of load reference information recorded in the reference information recording unit based on attribute information. According to this aspect, since one load reference information is selected from among a plurality of load reference information based on the driver attribute information, the driver load amount calculation unit operates based on the selected load reference information. The person load can be calculated.

  In an embodiment of the present invention, the driving simulation device is configured to use the attribute information based on a driving operation by the driver, a biological reaction of the driver, or an execution result of the subtask when the driver performs a subtask. It is preferable to further include an attribute information update unit that updates driver attribute information recorded in the recording unit. According to this aspect, the driver attribute information recorded in the attribute information recording unit can be updated to the latest state.

  Hereinafter, more specific embodiments of the present invention will be described in detail with reference to the drawings.

[Embodiment 1]
FIG. 1 is a block diagram illustrating a schematic configuration of a driving simulation apparatus 1 according to the present embodiment. The driving simulation apparatus 1 shown in FIG. 1 is connected to an input device 2, a display device 3, and an output device 4. Here, the driving simulation apparatus 1 according to the present embodiment is used, for example, for driving training for making the driver simulate an accident. In addition, the driving simulation apparatus 1 according to the present embodiment provides, for example, a research environment that provides an experimental environment for evaluating a driving support apparatus that provides various information and warnings to a driver in order to prevent an accident. Also used as The input device 2 includes a steering wheel, an accelerator pedal, a brake pedal, a shift lever, a winker, an engine key, and the like that are provided in the same manner as an actual vehicle. The display device 3 includes a projector, a liquid crystal display, an organic EL display, a plasma display, a CRT display, and the like. The output device 4 includes a speaker, headphones, and the like.

  The driving simulation apparatus 1 includes a simulation management unit 11, an operation input unit 12, a video output unit 13, and an audio output unit 14. Here, the functions of the simulation management unit 11, the operation input unit 12, the video output unit 13, and the audio output unit 14 are realized by an arithmetic device such as a CPU provided in the computer executing a predetermined program. . Therefore, a program for realizing the above functions by a computer or a recording medium on which the program is recorded is also an embodiment of the present invention.

  The simulation management unit 11 realizes a virtual space including a virtual road traffic environment and a virtual moving body that can travel in the virtual road traffic environment according to a driving operation by the driver. In the present embodiment, the virtual moving body is an automobile in the virtual space, but is not limited thereto, and may be any moving body such as a tricycle, a motorcycle, a train, a ship, an airplane, and the like. . Here, the virtual road traffic environment includes a virtual road and one or a plurality of virtual obstacles (for example, a tricycle, an automobile, a motorcycle, a bicycle, a pedestrian, etc.) that can become obstacles to the virtual moving body.

  The operation input unit 12 receives a driving operation on a virtual moving body in the virtual space via the input device 2. According to the driving operation received by the operation input unit 12, the simulation management unit 11 determines the behavior of the virtual moving body. The simulation management unit 11 determines the behavior of the virtual obstacle in the virtual space according to a control program recorded in advance in a memory (not shown) of the driving simulation apparatus 1. The simulation management unit 11 instructs the video output unit 13 to display a video of the virtual space including the determined behavior of the virtual moving body and the determined behavior of the virtual obstacle on the display device 3. In addition, the simulation management unit 11 instructs the audio output unit 14 to output the audio generated in the virtual space from the output device 4.

  The video output unit (output unit) 13 causes the display device 3 to display a video of the virtual space including the behavior of the virtual moving body and the behavior of the virtual obstacle according to the instruction from the simulation management unit 11. The sound output unit (output unit) 14 causes the output device 4 to output sound generated in the virtual space in accordance with an instruction from the simulation management unit 11. For example, the sound generated in the virtual space is engine sound, road noise, wind noise, etc. of the virtual moving body.

  The driving simulation apparatus 1 has a function for causing the driver to perform an operation (subtask) other than the driving operation during driving. That is, by allowing the driver to perform subtasks during driving, the driver is prevented from concentrating on driving operations. Since concentration on driving operation is hindered, it becomes easy for a driver to make a recognition error and a determination error. As a result, the probability that an accident will occur increases. Therefore, the driving simulation apparatus 1 includes a scenario recording unit 15, a scenario execution unit 16, a reference information recording unit 17, a driver load amount calculation unit 18, a target load recording unit 19, a load amount control unit 20, and a correspondence relationship recording unit. 21 is further provided.

  Here, each function of the scenario execution unit 16, the driver load amount calculation unit 18, and the load amount control unit 20 is realized by an arithmetic device such as a CPU included in the computer executing a predetermined program. Therefore, a program for realizing the above functions by a computer or a recording medium on which the program is recorded is also an embodiment of the present invention. Further, the scenario recording unit 15, the reference information recording unit 17, the target load recording unit 19, and the correspondence relationship recording unit 21 are realized by a built-in storage device of a computer or a storage device accessible from this computer. The same applies to each member of Embodiments 2 to 8 described below.

  In the scenario recording unit 15, a subtask scenario for causing the driver to perform the subtask is recorded in advance. The subtask means an operation other than the driving operation (main task) by the driver. For example, the subtasks include a mental calculation task in which a driver performs a mental calculation, a memorization task in which a driver memorizes information, an operation task in which a driver performs an operation, and the like. In the present embodiment, the scenario recording unit 15 includes a subtask scenario for causing the driver to perform a mental calculation task, a subtask scenario for causing the driver to perform a memorization task, and an operation task for the driver. Are recorded in advance. Here, the subtask scenario is described in a language such as Voice XML (Voice Extensible Markup Language), XML (Extensible Markup Language), or HTML (Hyper Text Markup Language).

  In the above description, examples of a mental calculation task, a memorization task, and an operation task have been described as subtasks. However, the present invention is not limited to this. For example, in addition to the mental calculation task, the memorization task, and the operation task, the subtask includes a dialogue task in which the driver has a dialogue, a viewing task in which the driver hears a sound, a gaze task in which the driver gazes at an image, etc. is there. That is, the subtask is not particularly limited as long as it is an operation other than the driving operation by the driver. For this reason, the subtask scenario recorded in the scenario recording unit 15 is not particularly limited as long as it is a scenario for causing the driver to perform an operation other than the driving operation.

  The scenario execution unit 16 reads the subtask scenario recorded in the scenario recording unit 15 and outputs the subtask execution instruction according to the subtask scenario to the driver via the voice output unit 14 by executing the read subtask scenario. Let That is, the scenario execution unit 16 outputs a subtask execution instruction according to the subtask scenario to the simulation management unit 11 by executing the subtask scenario. The simulation management unit 11 outputs a subtask execution instruction to the driver from the output device 4 via the voice output unit 14 by voice. Thereby, the driver can perform the subtask according to the subtask execution instruction by the sound output from the output device 4. Here, if the subtask scenario is a subtask scenario of a mental arithmetic task, the driver can perform addition (mental arithmetic) of, for example, one-digit numbers according to the voice subtask execution instruction output from the output device 4. . If the subtask scenario is a subtask scenario of a memorization task, the driver can memorize, for example, seven numbers in order according to the subtask execution instruction by voice output from the output device 4. Furthermore, if the subtask scenario is a subtask scenario of an operation task, the driver can operate the operation button with the instruction in accordance with the subtask execution instruction by voice output from the output device 4.

  In the above description, an example has been described in which the scenario execution unit 16 outputs a subtask execution instruction according to the subtask scenario to the driver via the voice output unit 14 by executing the subtask scenario. Not. For example, the scenario execution unit 16 may output a subtask execution instruction according to the subtask scenario to the driver via the video output unit 13 by executing the subtask scenario. In this case, the simulation management unit 11 outputs a subtask execution instruction to the driver from the display device 3 via the video output unit 13 as a video.

  In the reference information recording unit 17, load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance. FIG. 2 is a diagram illustrating an example of load reference information recorded in the reference information recording unit 17 according to the present embodiment. That is, the reference information recording unit 17 according to the present embodiment records the load reference information as the load reference table 170. As shown in FIG. 2, the range of the number of times of wander N and the driver load amount are recorded in the load reference table 170. Here, the number N of times of wobbling indicates the number of times that the steering operation by the driver has fluctuated. Note that the fluctuation of the steering wheel operation by the driver will be described later. In the example shown in FIG. 2, “level 1” has the lowest driver load, and “level 3” has the highest driver load. That is, in the reference information recording unit 17, the load reference table 170 is recorded so that the stage (level) of the driver load amount increases as the number of times of wobbling N increases.

  In the above description, the example in which the load reference table 170 having a table structure is recorded in the reference information recording unit 17 is described, but the present invention is not limited to this. That is, the data structure of the data recorded in the reference information recording unit 17 is not limited to the table structure and is arbitrary. Further, the content of the load reference table 170 is only an example, and is not limited thereto. For example, in the present embodiment, the driver load amount is represented by a level, but may be represented by a numerical value instead of the level. That is, in this specification, the data structure of data to be recorded in the various recording units is not particularly limited and is arbitrary. Also, the contents of data to be recorded in the various recording units are merely examples, and are not particularly limited.

  The driver load amount calculation unit 18 calculates the driver load amount that the driver is currently receiving. Specifically, the driver load amount calculation unit 18 first acquires the driving operation information related to the driving operation by the driver from the simulation management unit 11. Here, in the present embodiment, the driving operation information is steering operation information related to the steering operation by the driver. The driver load amount calculation unit 18 determines whether or not the steering operation by the driver has fluctuated based on the acquired steering operation information.

  Specifically, the driver load amount calculation unit 18 calculates the angular velocity ω of the steering wheel based on the acquired steering wheel operation information. The angular velocity ω is expressed in radians per second (rad / s). The driver load amount calculation unit 18 determines whether or not the calculated steering wheel angular velocity ω is greater than or equal to a threshold value. The threshold value is recorded in advance in a memory (not shown) of the driving simulation apparatus 1. Here, if the driver load amount calculation unit 18 determines that the calculated angular velocity ω of the steering wheel is equal to or greater than the threshold value, the driver load amount calculation unit 18 determines that the steering operation by the driver has fluctuated. If the driver load amount calculation unit 18 determines that the steering wheel operation by the driver has fluctuated, the driver load amount calculation unit 18 records that the steering wheel operation has fluctuated in the frequency recording unit 18a. As a result, the total number of times of wobbling with the steering operation by the driver is recorded in the number of times recording unit 18a.

  The driver load amount calculation unit 18 refers to the number recording unit 18a, and calculates the number N of times of wobbling that the driver has fluctuated in the steering operation from the current time to a predetermined time in the past. The driver load amount calculation unit 18 determines in which range the calculated number of fluctuations N is included in the range of the number of fluctuations N. The driver load amount calculation unit 16 reads the driver load amount corresponding to the range of the fluctuation number N including the calculated fluctuation number N from the load reference table 170. For example, if the calculated number of times of wobbling N is “8”, the driver load amount calculation unit 18 determines the driver load corresponding to the range “N <10” of the number of times of wobbling N including the calculated number of times of wobbling “8”. The quantity “level 1” is read from the load reference table 170. That is, the driver load amount calculation unit 18 calculates that the driver load amount received by the driver is “level 1”. The driver load amount calculation unit 18 outputs the calculated driver load amount to the load amount control unit 20.

  The target load information indicating the target load amount that the driver should receive is recorded in the target load recording unit 19. In the present embodiment, the target load recording unit 19 records the target load amount at any one of the three levels 1 to 3 as target load information. In other words, the target load recording unit 19 uses the reality as target load information so that the administrator of the driving simulation apparatus 1 does not cause the driver to perform a subtask with a load that is impossible in reality. The target load amount is recorded in consideration of Note that the target load information recorded in the target load recording unit 19 can be arbitrarily updated by the administrator of the driving simulation apparatus 1.

  The load amount control unit 20 first reads the target load information recorded in the target load recording unit 19. The load amount control unit 20 compares the driver load amount output from the driver load amount calculation unit 18 with the target load amount indicated by the read target load information. As a result of the comparison, when the driver load amount is larger than the target load amount, the load amount control unit 20 instructs the scenario execution unit 16 to reduce the driver load amount. In other words, the load amount control unit 20 instructs the scenario execution unit 16 to reduce the driver load amount if the driver load amount is so large that it is impossible in reality. For example, when the target load amount is “level 2” and the driver load amount is “level 3”, the load amount control unit 20 causes the scenario execution unit to decrease the driver load amount “level 3”. 16 is instructed.

  Further, when the driver load amount is smaller than the target load amount, the load amount control unit 20 instructs the scenario execution unit 16 to increase the driver load amount. That is, the load amount control unit 20 instructs the scenario execution unit 16 to increase the driver load amount if the driver load amount is insufficient to induce an accident or a state just before the accident. . For example, when the target load amount is “level 2” and the driver load amount is “level 1”, the load amount control unit 20 causes the scenario execution unit to increase the driver load amount “level 1”. 16 is instructed. When the driver load amount and the target load amount are the same (same level), the load amount control unit 20 does not instruct the scenario execution unit 16.

  In the correspondence recording unit 21, the correspondence between the subtask scenario and the load of the subtask scenario is recorded in advance. FIG. 3 is a diagram illustrating an example of the correspondence recorded in the correspondence recording unit 21 according to the present embodiment. That is, the correspondence relationship is recorded as the correspondence relationship table 210 in the correspondence relationship recording unit 21 according to the present embodiment. As shown in FIG. 3, the correspondence table 210 records a subtask scenario and a load of the subtask scenario. That is, the correspondence table 210 according to the present embodiment indicates that the mental task subtask scenario has the highest load for the driver, and the operation task subtask scenario has the lowest load for the driver.

  When there is an instruction from the load amount control unit 20 so as to reduce the driver load amount, the scenario execution unit 16 refers to the correspondence recording unit 21 to determine the currently executed subtask scenario. Change to a subtask scenario that has a lower load than the subtask scenario. For example, when the subtask scenario currently being executed is a subtask scenario of the memorization task, the scenario execution unit 16 refers to the correspondence table 210 to change from the subtask scenario of the memorization task to the subtask scenario of the operation task. To do. That is, the scenario execution unit 16 reads the changed subtask scenario of the operation task from the scenario recording unit 15 and newly executes the read subtask scenario of the operation task.

  Further, when an instruction is given from the load amount control unit 20 so as to increase the driver load amount, the scenario executing unit 16 refers to the correspondence recording unit 21 to determine the currently executed subtask scenario. , Change to a subtask scenario having a higher load than the subtask scenario. For example, when the subtask scenario currently being executed is a subtask scenario of the operation task, the scenario execution unit 16 refers to the correspondence table 210 to thereby change the subtask scenario or mental calculation of the memorization task from the subtask scenario of the operation task. Change to a task subtask scenario. That is, the scenario execution unit 16 reads the changed subtask scenario of the memorization task or the changed subtask scenario of the mental calculation task from the scenario recording unit 15, and newly executes the read subtask scenario of the memorization task or the read subtask scenario of the mental calculation task. To do.

  The subtask scenario change timing by the scenario execution unit 16 is arbitrary.

  Next, the operation of the driving simulation apparatus 1 according to the above configuration will be described with reference to FIGS. 4 and 5.

  FIG. 4 is a flowchart illustrating an example of the overall operation of the driving simulation apparatus 1 according to the present embodiment. As shown in FIG. 4, the driver load amount calculation unit 18 calculates the driver load amount that the driver is currently receiving (Op1).

  Here, an example of driver load amount calculation processing by the driver load amount calculation unit 18 in Op1 will be described with reference to FIG.

  FIG. 5 is a flowchart illustrating an example of a driver load amount calculation process by the driver load amount calculation unit 18 according to the present embodiment. As illustrated in FIG. 5, the driver load amount calculation unit 18 first acquires driving operation information related to the driving operation by the driver from the simulation management unit 11 (Op11). Here, in the present embodiment, the driving operation information is steering operation information related to the steering operation by the driver. The driver load amount calculation unit 18 calculates the angular velocity ω of the steering wheel based on the steering wheel operation information acquired in Op11 (Op12). The driver load amount calculation unit 18 determines whether or not the steering wheel angular velocity ω calculated in Op12 is equal to or greater than a threshold (Op13).

  If the driver load amount calculation unit 18 determines that the steering wheel angular velocity ω calculated in Op12 is equal to or greater than the threshold value (YES in Op13), the fact that the steering wheel operation has been staggered is recorded in the number recording unit 18a ( Op14). As a result, the total number of times of wobbling with the steering operation by the driver is recorded in the number of times recording unit 18a. On the other hand, if the driver load amount calculation unit 18 determines that the steering wheel angular velocity ω calculated in Op12 is not equal to or greater than the threshold (NO in Op13), the process returns to Op11.

  Then, the driver load amount calculation unit 18 refers to the number recording unit 18a, and calculates the number N of times of wobbling that the driver has fluctuated in the steering wheel during a certain past time from the current time (Op15). The driver load amount calculation unit 18 reads the driver load amount corresponding to the range of the number of times of fluctuation N including the number of times of fluctuation N calculated in Op15 from the reference information recording unit 17 (Op16). Accordingly, the driver load amount calculation unit 18 calculates the driver load amount.

  Returning to FIG. 4, the load amount control unit 20 reads the target load information recorded in the target load recording unit 19 (Op2). The load amount control unit 20 compares the driver load amount calculated in Op1 with the target load amount indicated by the target load information read out in Op2, thereby obtaining the driver load amount and the target load amount. Are determined to be the same (Op3). If load amount control unit 20 determines that the driver load amount and the target load amount are the same (YES in Op3), the process of FIG. 4 ends. On the other hand, when determining that the driver load amount and the target load amount are not the same (NO in Op3), the load amount control unit 20 determines whether the driver load amount is larger than the target load amount ( Op4).

  If load amount control unit 20 determines that the driver load amount is larger than the target load amount (YES at Op4), it instructs the scenario execution unit 16 to decrease the driver load amount (Op5). ). On the other hand, if load amount control unit 20 determines that the driver load amount is smaller than the target load amount (NO at Op4), it instructs the scenario execution unit 16 to increase the driver load amount. (Op6).

  Here, when there is an instruction of Op5, the scenario executing unit 16 refers to the correspondence recording unit 21, and changes the currently executing subtask scenario to a subtask scenario having a lower load than the subtask scenario. (Op7). On the other hand, when there is an instruction of Op6, the scenario executing unit 16 refers to the correspondence recording unit 21 to change the currently executing subtask scenario to a subtask scenario having a higher load than the subtask scenario. (Op8).

  As described above, the driving simulation apparatus 1 repeats the processing from Op1 to Op8 shown in FIG. 4 every predetermined time. In the present embodiment, the driving simulation device 1 repeats the processing from Op1 to Op8 shown in FIG. 4 every second. That is, the driving simulation apparatus 1 according to the present embodiment always controls the driver load received by the driver so that the driver load approaches the target load.

  As described above, according to the driving simulation apparatus 1 according to the present embodiment, the driver load amount calculation unit 18 includes the load reference information recorded in the reference information recording unit 17 and the driving operation information related to the driving operation by the driver. Based on the above, the driver load received by the driver is calculated. In the target load recording unit 19, target load information indicating the target load amount that the driver should receive is recorded in advance. Here, when the driver load amount is larger than the target load amount, the load amount control unit 20 instructs the scenario execution unit 16 to change the subtask scenario in order to decrease the driver load amount. That is, if the driver load amount is so large that it is impossible in reality, the load amount control unit 20 instructs the scenario execution unit 16 to change the subtask scenario in order to reduce the driver load amount. As a result, the driver load received by the driver can be reduced. In addition, when the driver load amount is smaller than the target load amount, the load amount control unit 20 instructs the scenario execution unit 16 to change the subtask scenario in order to increase the driver load amount. In other words, if the driver load amount is insufficient for inducing an accident or a state just before the accident, the load amount control unit 20 changes the subtask scenario to increase the driver load amount. To direct. As a result, the driver load received by the driver can be increased. As a result, the driving simulation apparatus 1 according to the present embodiment can create a dangerous situation with a high probability of occurrence of an accident while considering the reality.

  The above-described embodiment shows a specific example of the embodiment of the present invention, and various modifications can be made. Hereinafter, some main modifications will be described.

[Modification 1]
In the above-described embodiment, an example has been described in which the scenario execution unit 16 changes the currently executed subtask scenario by referring to the correspondence recording unit 21 when an instruction is issued from the load amount control unit 20. On the other hand, in the first modification, when an instruction is issued from the load amount control unit 20, the scenario execution unit 16 is defined in the currently executed subtask scenario by referring to the correspondence recording unit 21. An example of changing the parameters will be described.

  In the first modification, it is assumed that the scenario execution unit 16 executes a subtask scenario of the mental arithmetic task.

  In the correspondence recording unit 21, a correspondence table 211 shown in FIG. 6 is recorded instead of the correspondence table 210 shown in FIG. As shown in FIG. 6, the correspondence table 211 records parameters defined in the subtask scenario of the mental arithmetic task and the load of the parameters. In addition, the parameter prescribed | regulated in the subtask scenario is a parameter showing the degree of the load which a driver | operator should receive. For example, in FIG. 6, as the parameter in the subtask scenario, the number of digits of the number when the driver adds an arbitrary number is defined. However, the present invention is not limited to this, and for example, the memorized amount when the driver memorizes, the number of operations when the driver performs an operation, and the like may be defined as parameters in the subtask scenario. That is, in the correspondence table 211 according to the present embodiment, in the subtask scenario of the mental arithmetic task, the addition of three-digit numbers has the highest load for the driver, and the addition of one-digit numbers has the highest load for the driver. It is low.

  When there is an instruction from the load amount control unit 20 so as to reduce the driver load amount, the scenario execution unit 16 refers to the correspondence recording unit 21 to set parameters in the currently executed subtask scenario. Is changed to a parameter having a lower load than that parameter. For example, if the subtask scenario of the mental calculation task currently being executed is a subtask scenario that causes the driver to add two-digit numbers, the scenario execution unit 16 refers to the correspondence table 211 to obtain two digits. The parameter is changed so that the addition of the numbers of the numbers becomes the addition of the numbers of one digit. That is, the scenario execution unit 16 newly executes a subtask scenario of the mental arithmetic task whose parameters are changed.

  Further, when an instruction is given from the load amount control unit 20 so that the driver load amount increases, the scenario execution unit 16 refers to the correspondence recording unit 21 so that the subtask scenario currently being executed can be detected. Is changed to a parameter having a higher load than that parameter. For example, when the subtask scenario of the mental calculation task that is currently being executed is a subtask scenario that causes the driver to add one digit number, the scenario execution unit 16 refers to the correspondence table 211 to obtain one digit. The parameter is changed so that the addition of two numbers becomes the addition of two-digit numbers. That is, the scenario execution unit 16 newly executes a subtask scenario of the mental arithmetic task whose parameters are changed.

  As described above, according to the first modification, when the load amount control unit 20 instructs to reduce the driver load amount, the scenario execution unit 16 changes the parameter to a low load parameter. The driver load received by the driver can be reduced. Further, when an instruction is given from the load amount control unit 20 so that the driver load amount increases, the scenario execution unit 16 changes to a parameter with a high load, so that the driver load received by the driver is increased. The amount can be increased.

[Modification 2]
In the above-described embodiment, an example has been described in which the scenario execution unit 16 changes the currently executed subtask scenario by referring to the correspondence recording unit 21 when an instruction is issued from the load amount control unit 20. On the other hand, in the second modification, when instructed from the load amount control unit 20, the scenario execution unit 16 stops the currently executing subtask scenario or starts executing a new subtask scenario. Will be described.

  That is, when there is an instruction from the load amount control unit 20 so that the driver load amount is reduced, the scenario execution unit 16 stops the currently executed subtask scenario. That is, when there is one subtask scenario currently being executed, the scenario execution unit 16 stops the one subtask scenario. When there are a plurality of currently executed subtask scenarios, the scenario executing unit 16 stops any one subtask scenario among the plurality of subtask scenarios. Further, when an instruction is given from the load amount control unit 20 so that the driver load amount increases, the scenario execution unit 16 reads a new subtask scenario from the scenario recording unit 15 and executes the read subtask scenario. To do.

  In Modification 2, when an instruction is issued from the load amount control unit 20, the scenario execution unit 16 stops the currently executing subtask scenario or starts executing a new subtask scenario. 1 does not need to be provided.

  As described above, according to the second modification, the scenario executing unit 16 stops the currently executing subtask scenario when instructed by the load amount control unit 20 to reduce the driver load amount. Thus, the driver load received by the driver can be reduced. Further, when the load amount control unit 20 gives an instruction to increase the driver load amount, the scenario execution unit 16 starts executing a new subtask scenario. Person load can be increased.

[Modification 3]
In the above-described embodiment, the driver load amount calculation unit 18 has been described with respect to the example in which the steering operation information related to the steering operation performed by the driver is acquired from the simulation management unit 11. For example, the driver load amount calculation unit 18 may acquire pedal operation information related to the accelerator operation or the brake operation by the driver from the simulation management unit 11. In this case, the driver load amount calculation unit 18 calculates the number of times the driver has switched from the accelerator pedal to the brake pedal based on the acquired pedal operation information. The driver load amount calculation unit 18 reads out the driver load amount corresponding to the calculated number of step changes from the reference information recording unit 17. For this reason, in the reference information recording unit 17, a load reference table is recorded so that the step (level) of the driver load amount increases as the number of times of stepping increases. Accordingly, the driver load amount calculation unit 18 can calculate the driver load amount received by the driver based on the number of times of stepping. The driver load amount calculation unit 18 may calculate the driver load amount based on the operation amount of the accelerator pedal or the operation amount of the brake pedal instead of the number of times of stepping.

  Further, for example, the driver load amount calculation unit 18 may acquire the winker operation information related to the winker operation by the driver from the simulation management unit 11. In this case, the driver load amount calculation unit 18 determines whether or not the driver is currently performing the winker operation based on the acquired winker operation information. If it is determined that the driver is currently operating the winker operation, the driver load amount calculation unit 18 drives the driver so that the driver load amount increases compared to the case where the driver does not perform the winker operation. Calculate the person load. Further, if it is determined that the driver is not currently operating the winker operation, the driver load amount calculation unit 18 may decrease the driver load amount as compared with the case where the driver is performing the winker operation. The driver load amount is calculated. Accordingly, the driver load amount calculation unit 18 can calculate the driver load amount received by the driver based on the winker operation.

[Embodiment 2]
FIG. 7 is a block diagram showing a schematic configuration of the driving simulation apparatus 1a according to the present embodiment. That is, the driving simulation apparatus 1a according to the present embodiment includes a reference information recording unit 22 and a driver load amount calculating unit 23 instead of the reference information recording unit 17 and the driver load amount calculating unit 18 illustrated in FIG. Yes. In FIG. 7, components having the same functions as those in FIG. 1 are given the same reference numerals, and detailed descriptions thereof are omitted.

  Similar to the reference information recording unit 17 shown in FIG. 1, the reference information recording unit 22 records in advance load reference information serving as a reference for calculating the driver load amount received by the driver. FIG. 8 is a diagram showing an example of the load reference information recorded in the reference information recording unit 22 according to the present embodiment. That is, the reference information recording unit 22 according to the present embodiment records a plurality of load reference information as load reference tables 220 and 221, respectively.

  As shown in FIG. 8, the range of the collision allowance time TTC and the driver load amount are recorded in the load reference table 220. Here, the collision allowance time TTC (Time To Collision) indicates an allowance time until the virtual moving body collides with a vehicle (hereinafter, referred to as “previous vehicle”) that runs immediately before the virtual moving body. In other words, the load reference table 220 is recorded in the reference information recording unit 22 such that the stage (level) of the driver load amount increases as the collision margin time TTC becomes shorter. In the present embodiment, the collision margin time TTC is expressed in seconds.

In addition, the range of the intersection arrival time T _C and the driver load amount are recorded in the load reference table 221. Here, the intersection arrival time T _C indicates the time until the virtual moving body reaches the nearest intersection in the traveling direction of the virtual moving body. That is, in the reference information recording unit 22, the load reference table 221 is recorded so that the step (level) of the driver load amount increases as the intersection arrival time T _C becomes shorter. In the present embodiment, the intersection arrival time T _C is expressed in seconds.

  The driver load amount calculation unit 23 calculates the driver load amount currently received by the driver, similarly to the driver load amount calculation unit 18 shown in FIG. Specifically, the driver load amount calculation unit 23 first acquires road traffic information indicating the virtual road traffic environment of the virtual mobile body from the simulation management unit 11.

  Here, the driver load amount calculation unit 23 first determines whether there is a preceding vehicle based on the acquired road traffic information. If the driver load amount calculation unit 23 determines that there is a preceding vehicle, the driver load amount calculation unit 23 calculates a collision margin time TTC for the preceding vehicle. The collision margin time TTC is calculated by a value obtained by dividing the distance (inter-vehicle distance) between the virtual moving body and the preceding vehicle by the relative speed with respect to the preceding vehicle. The driver load amount calculation unit 23 determines which range of the range of the collision margin time TTC the calculated collision margin time TTC is included in. The driver load amount calculation unit 23 reads a driver load amount corresponding to the range of the collision margin time TTC including the calculated collision margin time TTC from the load reference table 220. For example, if the calculated collision margin time TTC is “7” (seconds), the driver load amount calculation unit 23 includes a range “4 <TTC” of the collision margin time TTC including the calculated collision margin time “7”. The driver load amount “level 1” corresponding to is read from the load reference table 220. That is, the driver load amount calculation unit 23 calculates that the driver load amount received by the driver is “level 1”.

On the other hand, if the driver load amount calculation unit 23 determines that there is no preceding vehicle, the driver load amount calculation unit 23 calculates the intersection arrival time T _C. The intersection arrival time T _C is calculated by a value obtained by dividing the distance between the virtual moving body and the intersection by the current speed of the virtual moving body. The driver load amount calculation unit 23 determines in which range the calculated intersection arrival time T _C is included in the range of the intersection arrival time T _C. Driver load amount calculating unit 23, a driver load corresponding to the range of intersection arrival time T _C that contains the intersection arrival time T _C that calculated, read from the load reference table 221. For example, if the calculated intersection arrival time T _C is “25” (seconds), the driver load amount calculation unit 23 determines the range “10 <of the intersection arrival time T _C including the calculated intersection arrival time“ 25 ”. The driver load “level 1” corresponding to “T _C ” is read from the load reference table 221. That is, the driver load amount calculation unit 23 calculates that the driver load amount received by the driver is “level 1”.

  Next, operation | movement of the driver | operator load amount calculation part 23 which concerns on said structure is demonstrated, referring FIG.

  FIG. 9 is a flowchart illustrating an example of a driver load amount calculation process by the driver load amount calculation unit 23 according to the present embodiment. As shown in FIG. 9, the driver load amount calculation unit 23 first acquires road traffic information indicating the virtual road traffic environment of the virtual mobile body from the simulation management unit 11 (Op21). The driver load amount calculation unit 23 determines whether there is a preceding vehicle based on the road traffic information acquired in Op21 (Op22).

  If it is determined that the preceding vehicle is present (YES at Op22), driver load amount calculation unit 23 calculates a collision margin time TTC for the preceding vehicle (Op23). The driver load amount calculation unit 23 reads the driver load amount corresponding to the range of the collision margin time TTC including the collision margin time TTC calculated in Op23 from the load reference table 220 (Op24). Accordingly, the driver load amount is calculated by the driver load amount calculation unit 23.

On the other hand, when determining that there is no preceding vehicle (NO at Op22), the driver load amount calculation unit 23 calculates the intersection arrival time T _C (Op25). The driver load amount calculation unit 23 reads the driver load amount corresponding to the range of the intersection arrival time T _C including the intersection arrival time T _C calculated in Op25 from the load reference table 221 (Op26). Thereby, the driver load amount calculation unit 23 calculates the driver load amount.

  As described above, according to the driving simulation apparatus 1a according to the present embodiment, it is possible to calculate the driver load received by the driver according to the virtual road traffic environment.

In the present embodiment, the driver load amount calculation unit 23 calculates the collision margin time TTC or the intersection arrival time T _C based on the acquired road traffic information, and calculates the calculated collision margin time TTC or the intersection arrival time. Although the example which calculates driver | operator load amount was demonstrated based on _TC , it is not limited to this. For example, the driver load amount calculation unit 23 may detect a congestion state around the virtual moving body based on the acquired road traffic information, and calculate the driver load amount based on the detected congestion state. . Specifically, the driver load amount calculation unit 23 calculates the number of virtual obstacles existing around the virtual moving body (for example, within a radius of 20 m from the virtual moving body) based on the acquired road traffic information. . The driver load amount calculation unit 23 reads out the driver load amount corresponding to the calculated number of virtual obstacles from the reference information recording unit 22. For this reason, a load reference table is recorded in the reference information recording unit 22 such that the stage (level) of the driver load increases as the number of virtual obstacles increases. Accordingly, the driver load amount calculation unit 23 can calculate the driver load amount received by the driver based on the congestion situation around the virtual moving body. Note that the driver load amount calculation unit 23 does not use the congestion state around the virtual moving body, but the traveling state of the virtual moving body, the road width of the virtual road on which the virtual moving body travels, or the road type of the virtual road (one The driver load may be calculated based on whether the vehicle is a lane or a two-lane vehicle.

[Embodiment 3]
FIG. 10 is a block diagram showing a schematic configuration of the driving simulation apparatus 1b according to the present embodiment. That is, the driving simulation device 1 b according to the present embodiment is further connected to the pulse detection device 5. That is, the driving simulation device 1b according to the present embodiment can access the pulse detection device 5. Here, the pulse detection device (biological reaction detection device) 5 is a device that detects the pulse rate of the driver. That is, when a human heart pumps blood, a pulse is generated in the artery, and the pulse detection device 5 detects the number of pulses generated in the artery. In the present embodiment, the pulse detection device 5 detects the pulse rate per minute of the driver. For this reason, the pulse detector 5 is mounted on the driver's arm, for example.

  Further, the driving simulation apparatus 1b according to the present embodiment includes a pulse rate acquisition unit 24 in addition to the driving simulation apparatus 1 shown in FIG. Furthermore, the driving simulation apparatus 1b according to the present embodiment includes a reference information recording unit 25 and a driver load amount calculating unit 26 instead of the reference information recording unit 17 and the driver load amount calculating unit 18 illustrated in FIG. Yes. 10, components having the same functions as those in FIG. 1 are given the same reference numerals, and detailed descriptions thereof are omitted.

  The pulse rate acquisition unit 24 acquires pulse rate information indicating the pulse rate per minute of the driver from the pulse detection device 5. The pulse rate acquisition unit 24 outputs the acquired pulse rate information to the driver load amount calculation unit 26.

  Similar to the reference information recording unit 17 shown in FIG. 1, the reference information recording unit 25 records in advance load reference information serving as a reference for calculating the driver load amount received by the driver. FIG. 11 is a diagram illustrating an example of the load reference information recorded in the reference information recording unit 25 according to the present embodiment. That is, the reference information recording unit 25 according to the present embodiment records the load reference information as the load reference table 250. As shown in FIG. 11, the range of the pulse rate P and the driver load amount are recorded in the load reference table 250. Here, the pulse rate P indicates the pulse rate per minute of the driver. That is, in the reference information recording unit 25, the load reference table 250 is recorded so that the stage (level) of the driver load amount increases as the pulse rate P increases.

  The driver load amount calculation unit 26 calculates the driver load amount currently received by the driver, similarly to the driver load amount calculation unit 18 shown in FIG. Specifically, the driver load amount calculation unit 26 determines in which range of the pulse rate P the pulse rate P indicated by the pulse rate information output from the pulse rate acquisition unit 24 is included. The driver load amount calculation unit 26 reads out the driver load amount corresponding to the range of the pulse rate P including the pulse rate P indicated by the pulse rate information output from the pulse rate acquisition unit 24 from the load reference table 250. For example, if the pulse rate P indicated by the pulse rate information output from the pulse rate acquisition unit 24 is “75”, the driver load amount calculation unit 26 determines the range of the pulse rate P including the pulse rate “75”. The driver load “level 1” corresponding to “P <80” is read from the load reference table 250. That is, the driver load amount calculation unit 26 calculates that the driver load amount received by the driver is “level 1”.

  Next, operations of the pulse rate acquisition unit 24 and the driver load amount calculation unit 26 according to the above configuration will be described with reference to FIG.

  FIG. 12 is a flowchart showing an example of processing by the pulse rate acquisition unit 24 and the driver load amount calculation unit 26 according to the present embodiment. As shown in FIG. 12, the pulse rate acquisition unit 24 acquires pulse rate information indicating the pulse rate per minute of the driver from the pulse detection device 5 (Op31). The driver load amount calculation unit 26 reads out the driver load amount corresponding to the range of the pulse rate P including the pulse rate P indicated by the pulse rate information acquired in Op31 from the load reference table 250 (Op32). Thereby, the driver load amount calculation unit 26 calculates the driver load amount.

  As described above, according to the driving simulation apparatus 1b according to the present embodiment, the driver load received by the driver can be calculated according to the driver's biological reaction (pulse rate).

  In addition, in this embodiment, although the driver load amount calculation part 26 demonstrated the example which calculates a driver load amount based on a driver's pulse rate, it is not limited to this. For example, the driver load amount calculation unit 26 may calculate the driver load amount based on a driver's arbitrary biological reaction such as driver perspiration, respiratory rate, eye movement, blood pressure, brain activity, and the like. Here, when calculating a driver | operator load amount based on a driver | operator's perspiration, a perspiration detection apparatus is provided instead of the pulse detection apparatus 5 shown in FIG. The sweat detection device detects, for example, mental sweat that appears on the palm of the driver by wearing it on the palm of the driver. That is, the driver load amount calculation unit 26 calculates the driver load amount such that the driver load amount increases as the driver sweats more. Moreover, when calculating driver | operator load amount based on a driver | operator's respiration rate, the respiration rate detection apparatus is provided instead of the pulse detection apparatus 5 shown in FIG. The respiration rate detection device detects the respiration rate of the driver by, for example, wearing it on the chest and abdomen of the driver. That is, the driver load amount calculation unit 26 calculates the driver load amount so that the driver load amount increases as the driver's respiration rate increases.

  Moreover, when calculating a driver | operator load amount based on a driver | operator's eyes | visual_axis movement, an image recognition apparatus is provided instead of the pulse detection apparatus 5 shown in FIG. The image recognition device detects the driver's line of sight movement, for example, by performing image recognition of the driver's face. That is, the driver load amount calculation unit 26 calculates the driver load amount so that the driver load amount increases as the driver's line-of-sight movement increases. When calculating the driver load based on the blood pressure of the driver, a blood pressure detection device is provided instead of the pulse detection device 5 shown in FIG. The blood pressure detection device detects the blood pressure of the driver. That is, the driver load amount calculation unit 26 calculates the driver load amount so that the driver load amount increases as the driver's blood pressure increases. Furthermore, when calculating a driver | operator load amount based on a driver | operator's brain activity, an electroencephalogram detection apparatus is provided instead of the pulse detection apparatus 5 shown in FIG. The electroencephalogram detection device detects a driver's electroencephalogram. That is, the driver load amount calculation unit 26 calculates the driver load amount so that the driver load amount increases if the brain wave of the driver indicates a brain wave different from that at the normal time.

[Embodiment 4]
FIG. 13 is a block diagram illustrating a schematic configuration of the driving simulation apparatus 1c according to the present embodiment. That is, the driving simulation apparatus 1c according to the present embodiment includes an execution result detection unit 27 in addition to the driving simulation apparatus 1 shown in FIG. Further, the driving simulation apparatus 1c according to the present embodiment includes a reference information recording unit 28 and a driver load amount calculating unit 29 instead of the reference information recording unit 17 and the driver load amount calculating unit 18 illustrated in FIG. Yes. In FIG. 13, components having the same functions as those in FIG. 1 are given the same reference numerals, and detailed descriptions thereof are omitted.

  The execution result detection unit 27 detects the execution result of the subtask when the driver performs the subtask in accordance with the execution of the subtask scenario by the scenario execution unit 16. Here, in the present embodiment, the execution result detection unit 27 detects the execution result of the mental calculation task when the driver performs the mental calculation task in accordance with the execution of the subtask scenario of the mental calculation task by the scenario execution unit 16. To do. Of course, in addition to the execution result of the mental calculation task, the execution result of other subtasks such as the memorization task and the operation task may be detected.

  Specifically, the execution result detection unit 27 receives an answer to the problem indicated by the subtask execution instruction by voice output from the output device 4 from the driver. In the present embodiment, it is assumed that the given question is addition of arbitrary numbers of one digit. That is, when the driver utters an answer, the execution result detection unit 27 receives the answer. Therefore, the execution result detection unit 27 has a voice recognition function for recognizing the driver's utterance.

The execution result detection unit 27 calculates the reaction time _Tr from the time when the problem indicated by the voice subtask execution instruction output from the output device 4 is given to the time when the answer to the problem is received. In the present embodiment, the reaction time _Tr is expressed in seconds. Further, the execution result detection unit 27 determines whether or not the accepted answer is correct. If the execution result detection unit 27 determines that the received answer is correct, the execution result detection unit 27 sets the calculated reaction time _Tr as the evaluation value E. If the execution result detection unit 27 determines that the received answer is incorrect, the execution result detection unit 27 sets the evaluation value E to a value obtained by adding the penalty α to the calculated reaction time _Tr . The execution result detection unit 27 records the calculated evaluation value E in the evaluation value recording unit 27a. As a result, the accumulated evaluation value of the driver is recorded in the evaluation value recording unit 27a.

Execution result detector 27, by referring to the evaluation value recording section 27a, cumulative evaluation value of the driver from the current time until a past predetermined time (hereinafter, referred to as "evaluation cumulative value") of the E _S calculate. Execution result detector 27, the calculated evaluation cumulative value E _S, and outputs to the driver load amount calculating unit 29.

Similar to the reference information recording unit 17 shown in FIG. 1, the reference information recording unit 28 records in advance load reference information serving as a reference for calculating the driver load amount received by the driver. FIG. 14 is a diagram illustrating an example of load reference information recorded in the reference information recording unit 28 according to the present embodiment. That is, the reference information recording unit 28 according to the present embodiment records the load reference information as the load reference table 280. As shown in FIG. 14, the range of the accumulated evaluation value E _S and the driver load amount are recorded in the load reference table 280. That is, the reference information storage unit 28, as the evaluation cumulative value E _S increases, as the stage of the driver load (level) is increased, the load reference table 280 is recorded.

The driver load amount calculation unit 29 calculates the driver load amount currently received by the driver, similarly to the driver load amount calculation unit 18 shown in FIG. Specifically, the driver load amount calculating unit 29 determines whether the execution result output from the detecting unit 27 evaluation cumulative value E _S is included in which the range of the scope of the assessment cumulative value E _S. The driver load amount calculation unit 29 reads the driver load amount corresponding to the range of the evaluation accumulated value E _S including the evaluation accumulated value E _S output from the execution result detection unit 27 from the load reference table 280. For example, if the accumulated evaluation value E _S output from the execution result detecting unit 27 is “34”, the driver load amount calculating unit 29 determines the range of the accumulated evaluation value E _S including the evaluated accumulated value “34”. The driver load “level 1” corresponding to “E _S <50” is read from the load reference table 280. That is, the driver load amount calculation unit 29 calculates that the driver load amount received by the driver is “level 1”.

  Next, operations of the execution result detection unit 27 and the driver load amount calculation unit 29 according to the above configuration will be described with reference to FIG.

FIG. 15 is a flowchart illustrating an example of processing by the execution result detection unit 27 and the driver load amount calculation unit 29 according to the present embodiment. As illustrated in FIG. 15, the execution result detection unit 27 receives an answer to the problem indicated by the subtask execution instruction by the voice output from the output device 4 from the driver (Op41). Execution result detector 27, the problem indicated by the subtasks execution instruction by voice output from the output device 4 from the time when the question, to calculate the reaction time T _r up to the time of accepting the answer at Op41 (Op42). Then, the execution result detection unit 27 determines whether or not the answer received at Op41 is a correct answer (Op43).

Execution result detector 27, if determined that the answer received in Op41 is correct (YES in Op43), the evaluation value E and the reaction time T _r calculated in Op42 (Op44). On the other hand, the execution result detector 27, if determined that the answer received in Op41 is incorrect (NO in Op43), evaluates the value obtained by adding a penalty α reaction time T _r calculated in Op42 Value E is set (Op45). The execution result detection unit 27 records the evaluation value E calculated in Op44 or Op45 in the evaluation value recording unit 27a (Op46). As a result, the accumulated evaluation value of the driver is recorded in the evaluation value recording unit 27a.

Then, the execution result detector 27, by referring to the evaluation value recording section 27a, calculates the evaluation cumulative value E _S (Op47). Driver load amount calculating unit 29, a driver load amount corresponding to a range of evaluation cumulative value E _S including the evaluation cumulative value E _S calculated in Op47, read from the load reference table 280 (Op48). Accordingly, the driver load amount calculation unit 29 calculates the driver load amount.

  As described above, according to the driving simulation device 1c according to the present embodiment, the driver load amount received by the driver is calculated according to the execution result of the subtask when the driver performs the subtask. Can do.

[Embodiment 5]
FIG. 16 is a block diagram illustrating a schematic configuration of the driving simulation apparatus 1d according to the present embodiment. That is, the driving simulation apparatus 1d according to the present embodiment includes a condition information recording unit 30 and a scenario control unit 31 instead of the target load recording unit 19 and the load amount control unit 20 shown in FIG. In addition, the driving simulation apparatus 1d according to the present embodiment includes a scenario execution unit 32 instead of the scenario execution unit 16 illustrated in FIG. Here, the driving simulation device 1d according to the present embodiment does not include the correspondence recording unit 21 illustrated in FIG. In FIG. 16, components having the same functions as those in FIG. 1 are given the same reference numerals, and detailed descriptions thereof are omitted.

  In the condition information recording unit 30, condition information indicating a start condition and a stop condition for executing the subtask scenario, which are determined by a change in the driver load amount with time, is recorded in advance. FIG. 17 is a diagram illustrating an example of condition information recorded in the condition information recording unit 30 according to the present embodiment. That is, the condition information recording unit 30 according to the present embodiment records the condition information as the start condition table 300 and the stop condition table 301. That is, in the condition information recording unit 30 according to the present embodiment, when the driver load amount increases by two levels, or when the driver load amount of level 1 continues for 10 minutes, the scenario execution unit 32 displays the subtask scenario. A start condition table 300 is recorded so as to start execution. Further, the condition information recording unit 30 according to the present embodiment includes a stop condition table 301 so that the scenario execution unit 32 stops the execution of the subtask scenario when the driver load amount at the same level continues for 15 minutes. It is recorded.

  When the change in the driver load amount matches the start condition while the execution of the subtask scenario is stopped, the scenario control unit 31 instructs the scenario execution unit 32 to start the execution of the subtask scenario. Instruct.

  For example, while the execution of the subtask scenario is stopped, the change in the driver load amount output from the driver load amount calculation unit 18 has increased by two levels, such as level 1 to level 3. Then, the scenario control unit 31 determines that the change in the driver load amount matches the start condition. In this case, the scenario control unit 31 instructs the scenario execution unit 32 to start execution of the subtask scenario. That is, if the driver load increases by two levels, it can be said that a situation in which the driver should concentrate on the driving operation has occurred. That is, when a situation that should be concentrated on the driving operation occurs, the driver is prevented from concentrating on the driving operation by causing the driver to perform a subtask. Since concentration on driving operation is hindered, it becomes easy for a driver to make a recognition error and a determination error. As a result, it is possible to create a dangerous situation with a high probability of an accident.

  Further, for example, while the execution of the subtask scenario is stopped, the change in the driver load amount output from the driver load amount calculation unit 18 indicates that the level 1 state continues for 10 minutes. Then, the scenario control unit 31 determines that the change in the driver load amount matches the start condition. In this case, the scenario control unit 31 instructs the scenario execution unit 32 to start execution of the subtask scenario. That is, if the level 1 state continues for 10 minutes, the driver is less likely to concentrate on the driving operation, and the driver is likely to perform the driving operation casually. In other words, when the concentration is reduced with respect to the driving operation, the driver is further reduced in the concentration with respect to the driving operation by causing the driver to perform a subtask. For this reason, a driver's recognition error and determination error are likely to occur. As a result, it is possible to create a dangerous situation with a high probability of an accident.

  Moreover, the scenario control unit 31 instructs the scenario execution unit 32 to stop the execution of the subtask scenario when the change in the driver load amount matches the stop condition during the execution of the subtask scenario.

  For example, if the change in the driver load amount output from the driver load amount calculation unit 18 during the execution of the subtask scenario indicates that the same level continues for 15 minutes, the scenario control unit 31 It is determined that the change in the driver load amount matches the stop condition. In this case, the scenario control unit 31 instructs the scenario execution unit 32 to stop the execution of the subtask scenario. That is, if the driver load continues at the same level for 15 minutes, it is highly likely that the driver has become accustomed to the subtask currently being performed. When the driver gets used to the subtask, it becomes difficult for the driver to make a recognition error or a determination error. As a result, a dangerous situation with a high probability of an accident cannot be created. For this reason, in such a case, the scenario control unit 31 instructs the scenario execution unit 32 to stop the execution of the subtask scenario.

  When there is an instruction from the scenario control unit 31 to start execution of the subtask scenario, the scenario execution unit 32 starts execution of the subtask scenario. That is, the scenario execution unit 32 reads the subtask scenario instructed from the scenario control unit 31 from the scenario recording unit 15 and executes the read subtask scenario. In addition, when the scenario control unit 31 instructs to stop the execution of the subtask scenario, the scenario execution unit 32 stops the execution of the subtask scenario.

  Next, the operation of the driving simulation apparatus 1d according to the above configuration will be described with reference to FIG.

  FIG. 18 is a flowchart illustrating an example of the overall operation of the driving simulation apparatus 1d according to the present embodiment. As shown in FIG. 18, the driver load amount calculation unit 18 calculates the driver load amount that the driver is currently receiving (Op51). In the present embodiment, as described in the first embodiment, the driver load amount calculation unit 18 calculates the driver load amount based on the driving operation information related to the driving operation by the driver. However, the present invention is not limited to this, and the driver load amount calculation unit 18 is described in the road traffic information described in the second embodiment, the biological information described in the third embodiment, and described in the fourth embodiment. The driver load amount may be calculated based on the execution result of the subtask.

  The scenario control unit 31 reads out the condition information recorded in the condition information recording unit 30 (Op52). Then, the scenario control unit 31 determines whether or not the subtask scenario is being executed by monitoring the scenario execution unit 32 (Op53). If it is determined that the subtask scenario is being executed (YES in Op53), the scenario control unit 31 determines whether the change in the driver load calculated in Op51 matches the stop condition (Op54). ). On the other hand, if it is determined that the subtask scenario is not being executed (NO in Op53), the scenario control unit 31 determines whether or not the change in the driver load calculated in Op51 matches the start condition ( Op55).

  In Op54, if the scenario control unit 31 determines that the change in the driver load calculated in Op51 matches the stop condition (YES in Op54), the scenario execution unit stops the execution of the subtask scenario. 32 is instructed (Op56). Then, the scenario execution unit 32 stops the execution of the subtask scenario (Op57). On the other hand, if the scenario control unit 31 determines that the change in the driver load amount calculated in Op51 does not match the stop condition (NO in Op54), the process of FIG. 18 ends.

  In Op55, if it is determined that the change in the driver load calculated in Op51 matches the start condition (YES in Op55), the scenario control unit 31 starts the execution of the subtask scenario. 32 is instructed (Op58). Then, the scenario execution unit 32 starts executing the subtask scenario (Op59). On the other hand, if the scenario control unit 31 determines that the change in the driver load amount calculated in Op51 does not match the start condition (NO in Op55), the process of FIG. 18 ends.

  As described above, the driving simulation device 1d repeats the processing from Op51 to Op59 shown in FIG. 18 every predetermined time. In the present embodiment, the driving simulation device 1d repeats the processing from Op51 to Op59 shown in FIG. 18 every second. In other words, the driving simulation apparatus 1d according to the present embodiment always determines whether the change in the driver load received by the driver matches the start condition or the stop condition, and starts the operation. If the condition is met, execution of the subtask scenario is started, and if the condition is stopped, execution of the subtask scenario is stopped.

  As described above, according to the driving simulation apparatus 1d according to the present embodiment, the scenario control unit 31 determines that the change in the driver load amount matches the start condition while the execution of the subtask scenario is stopped. The scenario execution unit 32 is instructed to start execution of the subtask scenario. Moreover, the scenario control unit 31 instructs the scenario execution unit 32 to stop the execution of the subtask scenario when the change in the driver load amount matches the stop condition during the execution of the subtask scenario. As a result, the driving simulation apparatus 1d according to the present embodiment can create a dangerous situation with a high probability of occurrence of an accident while considering reality.

[Embodiment 6]
In the first to fourth embodiments, the example in which the driver load received by the driver is calculated based on the driving operation information, the road traffic information, the biological information, or the execution result of the subtask has been described. However, even if the driving operation information, road traffic information, biometric information, or subtask execution results are the same, the load on the driver varies depending on the driver. For example, the collision margin time TTC with the preceding vehicle is normally shorter (for example, the average value of the collision margin time TTC is 2 seconds) and the collision margin time TTC with the preceding vehicle is longer than usual (for example, Consider a case where there is a driver B whose collision margin time TTC has an average value of 4 seconds. In this case, in a situation where the collision margin time TTC is 2 seconds, the load on the driver A is not high, but the load on the driver B is high. For this reason, it is preferable to calculate the driver load amount based on the load reference information corresponding to each driver. Therefore, in the present embodiment, an example in which one load reference information is selected from a plurality of load reference information based on the driver attribute information, and the driver load amount is calculated based on the selected load reference information. explain. In the following, an example applied to the driving simulation apparatus 1b shown in FIG. 10 will be described. However, the driving simulation apparatus 1 shown in FIG. 1, the driving simulation apparatus 1a shown in FIG. 7, the driving simulation apparatus 1c shown in FIG. Of course, the present invention can also be applied to the driving simulation apparatus 1d shown in FIG.

  FIG. 19 is a block diagram showing a schematic configuration of the driving simulation apparatus 1e according to the present embodiment. That is, the driving simulation apparatus 1e according to the present embodiment includes a reference information recording unit 33 instead of the reference information recording unit 25 illustrated in FIG. Further, the driving simulation device 1e according to the present embodiment includes an attribute information recording unit 34 and a reference information selection unit 35 in addition to the driving simulation device 1b shown in FIG. In FIG. 19, configurations having the same functions as those in FIG. 10 are given the same reference numerals, and detailed descriptions thereof are omitted.

  In the reference information recording unit 33, a plurality of load reference information serving as different references are recorded in advance. FIG. 20 is a diagram illustrating an example of the load reference information recorded in the reference information recording unit 33 according to the present embodiment. That is, the reference information recording unit 33 according to the present embodiment records a plurality of load reference information as load reference tables 330, 331, 332,. That is, a plurality of load reference tables 330, 331, 332,... Are recorded in the reference information recording unit 33 so as to be different from each other.

  The attribute information recording unit 34 records driver attribute information indicating characteristics of the driving operation by the driver, characteristics of the driver's biological reaction, or characteristics of the execution result of the subtask when the driver performs the subtask. FIG. 21 is a diagram illustrating an example of driver attribute information recorded in the attribute information recording unit 34 according to the present embodiment. That is, the attribute information recording unit 34 according to the present embodiment records the driver attribute information as the driver attribute table 340. As shown in FIG. 21, in the driver attribute table 340, items of driver attribute information and the driver attribute information are recorded.

  That is, in the driver attribute table 340 according to the present embodiment, the average value of the collision margin time TTC “2 seconds” and the average value of the brake start timing “10 seconds to the stop line” are characteristic of the driving operation by the driver. Is recorded. Further, in the driver attribute table 340 according to the present embodiment, as a feature of the driver's biological reaction, the resting pulse rate “80 times / minute” and the pulse fluctuation magnitude “small” due to the load are recorded. Has been. Further, in the driver attribute table 340 according to the present embodiment, as a feature of the execution result of the subtask when the driver performs the subtask, the subtask scenario “large” of the memorization task and the subtask scenario “medium” of the mental calculation task , And the subtask scenario “small” of the operation task is recorded. That is, the subtask scenario of the memorization task has the highest load for the driver, and the subtask scenario of the operation task represents the lowest load for the driver.

  In the correspondence recording unit 21 according to the present embodiment, the subtask scenario “large” of the memorization task, the subtask scenario “medium” of the mental calculation task, and the subtask scenario “of the operation task” recorded in the driver attribute table 340 The same data as “small” is recorded.

  The driver attribute information is recorded in advance in the attribute information recording unit 34 by the driver or the like. For example, when the driver measures his / her biological reaction or the driver answers a questionnaire regarding his / her driving operation, the driver attribute information is generated, and the generated driver attribute information is sent to the attribute information recording unit. 34.

  The reference information selection unit 35 selects one load reference information from among a plurality of load reference information recorded in the reference information recording unit 33 based on the driver attribute information recorded in the attribute information recording unit 34. In the present embodiment, the reference information selection unit 35 first reads from the driver attribute table 340 the resting pulse rate “80 times / minute” and the pulse fluctuation magnitude “small” due to the load. Then, the reference information selection unit 35 selects a load reference table in which the read pulse rate at rest “80 times / 1 minute” becomes the boundary condition of the level 1 driver load. That is, the reference information selection unit 35 selects the load reference tables 330 and 331 from the load reference tables 330 to 332. Further, the reference information selection unit 35 determines the interval of the boundary condition in the range of the pulse rate P based on the magnitude of the pulse fluctuation due to the load. In this embodiment, since the magnitude of the pulse fluctuation due to the load is small, the reference information selection unit 35 selects the load reference table 330 having the narrowest boundary condition interval from the selected load reference tables 330 and 331. .

  The driver load amount calculation unit 26 is based on the load reference table 330 selected by the reference information selection unit 35 and the pulse rate information output from the pulse rate acquisition unit 24. Calculate the load.

  Next, the operation of the reference information selection unit 35 according to the above configuration will be described with reference to FIG.

  FIG. 22 is a flowchart illustrating an example of load reference information selection processing by the reference information selection unit 35 according to the present embodiment. As illustrated in FIG. 22, the reference information selection unit 35 first determines whether or not the load reference information selection mode is set (Op61). Here, in the present embodiment, the driver can enter the selection mode of the load reference information by giving an instruction via the input device 2. Note that each time the driver attribute information recorded in the attribute information recording unit 34 is updated, the load reference information selection mode may be automatically set. If it is determined that the load reference information selection mode is set (YES in Op61), reference information selection unit 35 reads out driver attribute information recorded in attribute information recording unit 34 (Op62). On the other hand, if reference information selection unit 35 determines that the load reference information selection mode is not set (NO in Op61), the process of FIG. 22 ends.

  Then, the reference information selection unit 35 selects one load reference information from among a plurality of load reference information recorded in the reference information recording unit 33 based on the driver attribute information read in Op62 ( Op63).

  As described above, according to the driving simulation apparatus 1e according to the present embodiment, one load reference information is selected from a plurality of load reference information on the basis of the driver attribute information. The driver load amount 26 can be calculated based on the selected load reference information.

[Embodiment 7]
In the sixth embodiment, an example in which one load reference information is selected from a plurality of load reference information based on driver attribute information, and a driver load amount is calculated based on the selected load reference information will be described. did. However, the driver attribute information may change depending on the passage of time and the situation. For this reason, it is preferable to update the driver attribute information recorded in the attribute information recording unit 34 so as to be always in the latest state according to the passage of time and the situation. Therefore, in this embodiment, the driver attribute recorded in the attribute information recording unit 34 based on the driving operation by the driver, the driver's biological reaction, or the execution result of the subtask when the driver performs the subtask. An example of updating information will be described.

  FIG. 23 is a block diagram illustrating a schematic configuration of the driving simulation apparatus 1f according to the present embodiment. That is, the driving simulation apparatus 1f according to the present embodiment includes an attribute information update unit 36 in addition to the driving simulation apparatus 1e shown in FIG. In FIG. 23, components having the same functions as those in FIG.

  The attribute information update unit 36 acquires driving operation information or road traffic information from the simulation management unit 11, and driver attribute information recorded in the attribute information recording unit 34 based on the acquired driving operation information or road traffic information. Update. For example, the attribute information update unit 36 calculates a plurality of collision margin times TTC in a certain section based on the road traffic information. Then, the attribute information update unit 36 calculates an average value of the plurality of calculated collision margin times TTC. Here, it is assumed that the attribute information update unit 36 calculates the average value “5 seconds” of the collision allowance time TTC. The attribute information update unit 36 updates the average value “2 seconds” (see FIG. 21) of the collision margin time TTC recorded in the attribute information recording unit 34 to the calculated average value “5 seconds” of the collision margin time TTC. .

  The attribute information update unit 36 acquires pulse rate information indicating the pulse rate per minute of the driver from the pulse rate acquisition unit 24 and is recorded in the attribute information recording unit 34 based on the acquired pulse rate information. Update driver attribute information. For example, the attribute information update unit 36 calculates the pulse rate per minute of the driver when the driver is performing a certain subtask during driving based on the pulse rate information. The attribute information update unit 36 determines how much the magnitude of the pulse fluctuation due to the load shows the change based on the calculated pulse rate. Here, it is assumed that the pulse fluctuation due to the load shows a large change. In this case, the attribute information update unit 36 updates the pulse fluctuation magnitude “small” (see FIG. 21) due to the load recorded in the attribute information recording section 34 to the determined pulse fluctuation magnitude “large”. To do.

  Further, the attribute information update unit 36 acquires the driver load amount received by the driver when the driver performs the subtask from the driver load amount calculation unit 26, and based on the acquired driver load amount. Then, the driver attribute information recorded in the attribute information recording unit 34 is updated. For example, the attribute information update unit 36 calculates the driver load amount for each subtask scenario, and calculates the average value of the driver load amount for each subtask scenario. The attribute information update unit 36 arranges the subtask scenarios in descending order of the calculated average value of the driver load. Here, it is assumed that the attribute information update unit 36 is arranged in the order of the subtask scenario of the operation task, the subtask scenario of the memorization task, and the subtask scenario of the mental calculation task. In this case, the attribute information update unit 36 records the subtask scenario “large” of the memorization task, the subtask scenario “medium” of the mental calculation task, and the subtask scenario “small” of the operation task recorded in the attribute information recording unit 34 (FIG. 21). Are updated to the subtask scenario “large” of the operation task, the subtask scenario “medium” of the memorization task, and the subtask scenario “small” of the mental calculation task.

  Next, the operation of the attribute information update unit 36 according to the above configuration will be described with reference to FIG.

  FIG. 24 is a flowchart illustrating an example of driver attribute information update processing by the attribute information update unit 36 according to the present embodiment. As shown in FIG. 24, the attribute information update unit 36 first determines whether or not the driver attribute information update mode is set (Op71). Here, in the present embodiment, the driver attribute information update mode can be set by instructing the driver via the input device 2. Note that the driver attribute information update mode may be periodically entered without the driver giving an instruction via the input device 2. If attribute information update unit 36 determines that the driver attribute information update mode is set (YES in Op71), it acquires driving operation information, road traffic information, pulse rate information, or driver load ( Op72). On the other hand, if attribute information update unit 36 determines that the driver attribute information update mode is not set (NO in Op71), the process of FIG. 24 ends.

  Then, the attribute information update unit 36 acquires the driver attribute information recorded in the attribute information recording unit 34 based on the driving operation information, road traffic information, pulse rate information, or driver load acquired at Op72. Update (Op73). Accordingly, the driver attribute information recorded in the attribute information recording unit 34 is updated to the latest state.

  As described above, according to the driving simulation device 1 f according to the present embodiment, the driver attribute information recorded in the attribute information recording unit 34 can be updated to the latest state.

[Embodiment 8]
In the first embodiment, the example in which the subtask scenario to be executed is determined by comparing the driver load amount and the target load amount has been described. However, in order to reproduce a dangerous situation in which an accident occurs, the load to be applied to the driver is preferably changed according to the driver's condition. For example, when the driver's consciousness is clear, it is possible to induce an accident or a state just before the accident by increasing the load to be given to the driver. On the other hand, if the driver's consciousness is not clear, that is, if the driver is going to fall asleep, increasing the load to the driver will restore the driver's consciousness and conversely There is a high probability of being guided to a safe state. For this reason, it is preferable to dynamically change the target load amount depending on whether or not the driver is going to fall asleep. Therefore, in the present embodiment, an example will be described in which one target load information is selected from a plurality of target load information according to whether or not a sign of a driver's sleep is detected. In the following, an example applied to the driving simulation apparatus 1 shown in FIG. 1 will be described. However, the driving simulation apparatus 1a shown in FIG. 7, the driving simulation apparatus 1b shown in FIG. 10, the driving simulation apparatus 1c shown in FIG. Of course, the present invention can also be applied to the driving simulation apparatus 1e shown in FIG. 19 and the driving simulation apparatus 1f shown in FIG.

  FIG. 25 is a block diagram illustrating a schematic configuration of the driving simulation apparatus 1g according to the present embodiment. That is, the driving simulation apparatus 1g according to the present embodiment is further connected to the dozing detection apparatus 6. That is, the driving simulation device 1g according to the present embodiment can access the dozing detection device 6. Here, the dozing detection device 6 is a device that detects a sign of a driver's dozing. The dozing detection device 6 is, for example, an image recognition device or a pulse detection device. When the dozing detection device 6 is an image recognition device, a sign of the driver's dozing is detected by detecting a change in the number of blinks of the driver. In addition, when the dozing detection device 6 is a pulse detection device, a sign of dozing is detected by detecting fluctuations in the pulse of the driver.

  The driving simulation device 1g according to the present embodiment includes a target load recording unit 37 instead of the target load recording unit 19 shown in FIG. Furthermore, the driving simulation device 1g according to the present embodiment includes a target load selection unit 38 in addition to the driving simulation device 1 shown in FIG. In FIG. 25, components having the same functions as those in FIG. 1 are given the same reference numerals, and detailed descriptions thereof are omitted.

  In the target load recording unit 37, a plurality of pieces of target load information having different target load amounts are recorded in advance. In the present embodiment, the target load recording unit 37 includes target load information indicating the level 1 target load amount, target load information indicating the level 2 target load amount, and target load indicating the level 3 target load amount. Information is recorded.

  The target load selection unit 38 is configured such that when the drowsiness detection device 6 detects the driver's nap sign, the target load amount is lower than when the driver's drowsiness sign is not detected. Then, one target load information is selected from a plurality of target load information recorded in the target load recording unit 37. For example, when a drowsiness sign of the driver is detected by the drowsiness detection device 6, the target load selection unit 38 selects target load information indicating a target load amount of level 1 from a plurality of target load information. . On the other hand, when the driver's drowsiness sign is not detected by the drowsiness detection device 6, the target load selection unit 38 selects target load information indicating a target load amount of level 2 from a plurality of target load information.

  The load amount control unit 20 compares the driver load amount output from the driver load amount calculation unit 18 with the target load amount indicated by the target load information selected by the target load selection unit 38. As a result of the comparison, when the driver load amount is larger than the target load amount, the load amount control unit 20 instructs the scenario execution unit 16 to reduce the driver load amount. Further, when the driver load amount is smaller than the target load amount, the load amount control unit 20 instructs the scenario execution unit 16 to increase the driver load amount.

  Next, the operation of the target load selection unit 38 according to the above configuration will be described with reference to FIG.

  FIG. 26 is a flowchart illustrating an example of target load information selection processing by the target load selection unit 38 according to the present embodiment. As shown in FIG. 26, the target load selection unit 38 determines whether or not a sign of a driver's sleep is detected by the sleep detection device 6 (Op81). If the target load selection unit 38 determines that the driver's drowsiness sign has been detected by the dozing detection device 6 (YES in Op81), the target load recording unit 37 records the target load amount so as to decrease. One target load information is selected from a plurality of target load information (Op82). On the other hand, if target load selection unit 38 determines that a sign of a driver's sleep is not detected by sleep detection device 6 (NO in Op81). One target load information is selected from a plurality of pieces of target load information recorded in the target load recording unit 37 so that the target load amount becomes high (Op83).

  As described above, according to the driving simulation apparatus 1g according to the present embodiment, when a sign of a driver's sleep is detected, the target load amount is reduced from a plurality of target load information so that the target load amount is reduced. Target load information can be selected. Thereby, it can avoid that a driver | operator's consciousness recovers and it guide | induces to a safe state. As a result, it is possible to create a dangerous situation with a high probability of an accident.

  Regarding the above embodiment, the following additional notes are disclosed.

(Appendix 1)
In a driving simulation apparatus comprising a simulation management unit that realizes a virtual space including a virtual road traffic environment and a virtual moving body capable of traveling in the virtual road traffic environment according to a driving operation by a driver,
An output unit for giving instructions to the driver;
When an operation other than the driving operation by the driver is a subtask, a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask is recorded in advance,
A scenario execution unit that reads out the subtask scenario recorded in the scenario recording unit, and outputs the subtask execution instruction according to the subtask scenario to the driver via the output unit by executing the read subtask scenario;
A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance;
Driver load calculation that calculates the driver load received by the driver based on the load reference information recorded in the reference information recording unit and the status of the virtual moving body or the driver. And
A target load recording unit for recording target load information indicating a target load amount to be received by the driver;
When the driver load amount is larger than the target load amount, the driver load amount is decreased. When the driver load amount is smaller than the target load amount, the driver load amount is increased. And a load amount control unit that instructs the scenario execution unit to change the subtask scenario or change the execution status of the subtask scenario.

(Appendix 2)
The driving simulation device further includes a correspondence recording unit in which the correspondence between the subtask scenario and the load of the subtask scenario is recorded in advance.
When the instruction to change the subtask scenario is issued from the load amount control unit in order to reduce the driver load amount, the scenario execution unit is currently executing by referring to the correspondence recording unit The subtask scenario is changed to a subtask scenario having a lower load than the subtask scenario, and the load amount control unit instructs to change the subtask scenario in order to increase the driver load amount, The operation simulation apparatus according to appendix 1, wherein the scenario execution unit changes the currently executed subtask scenario to a subtask scenario having a higher load than the subtask scenario by referring to the correspondence relationship recording unit.

(Appendix 3)
The driving simulation device further includes a correspondence recording unit in which a correspondence between a parameter representing a degree of load to be received by the driver specified in the subtask scenario and a load of the parameter is recorded in advance.
In order to reduce the driver load amount, when there is an instruction from the load amount control unit to change the execution status of the subtask scenario, the scenario execution unit refers to the correspondence recording unit, A parameter in the currently executing subtask scenario is changed to a parameter having a lower load than that parameter, and an instruction to change the execution status of the subtask scenario is received from the load amount control unit in order to increase the driver load amount. If there is, the scenario execution unit changes a parameter in the currently executed subtask scenario to a parameter having a higher load than the parameter by referring to the correspondence recording unit. Driving simulation equipment.

(Appendix 4)
In order to reduce the driver load amount, when there is an instruction from the load amount control unit to change the execution status of the subtask scenario, the scenario execution unit stops the currently executing subtask scenario, and In order to increase the driver load amount, when an instruction to change the execution status of the subtask scenario is given from the load amount control unit, the scenario execution unit starts executing a new subtask scenario. The driving simulation device described in 1.

(Appendix 5)
The driving simulation device is accessible to a dozing detection device that detects a sign of the driver's dozing,
In the target load recording unit, a plurality of target load information that are different target load amounts are recorded in advance,
In the driving simulation device, when a drowsiness sign of the driver is detected by the drowsiness detection device, the target load amount is reduced as compared to the case where the drowsy sign of the driver is not detected. The driving simulation apparatus according to any one of appendices 1 to 4, further comprising a target load selection unit that selects one target load information from among a plurality of target load information recorded in the target load recording unit.

(Appendix 6)
In a driving simulation apparatus comprising a simulation management unit that realizes a virtual space including a virtual road traffic environment and a virtual moving body capable of traveling in the virtual road traffic environment according to a driving operation by a driver,
An output unit for giving instructions to the driver;
When an operation other than the driving operation by the driver is a subtask, a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask is recorded in advance,
A scenario execution unit that reads out the subtask scenario recorded in the scenario recording unit, and outputs the subtask execution instruction according to the subtask scenario to the driver via the output unit by executing the read subtask scenario;
A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance;
Driver load calculation that calculates the driver load received by the driver based on the load reference information recorded in the reference information recording unit and the status of the virtual moving body or the driver. And
A condition information recording unit preliminarily recorded with condition information indicating a start condition and a stop condition of execution of the subtask scenario, which is determined by a change with time in the driver load amount;
When the change of the driver load amount matches the start condition while the execution of the subtask scenario is stopped, the scenario execution unit is instructed to start the execution of the subtask scenario, A scenario control unit that instructs the scenario execution unit to stop the execution of the subtask scenario when a change in the driver load amount matches the stop condition during the execution of the subtask scenario; Driving simulation device.

(Appendix 7)
The driver load amount calculation unit acquires driving operation information related to a driving operation by the driver from the simulation management unit, and acquires the acquired driving operation information and the load reference information recorded in the reference information recording unit. The driving simulation device according to any one of appendices 1 to 6, wherein the driving load received by the driver is calculated based on the driving load.

(Appendix 8)
The driver load amount calculation unit acquires road traffic information indicating the virtual road traffic environment from the simulation management unit, and acquires the acquired road traffic information and the load reference information recorded in the reference information recording unit. The driving simulation device according to any one of appendices 1 to 6, wherein the driving load received by the driver is calculated based on the driving load.

(Appendix 9)
The driving simulation device can access a biological reaction detection device that detects a biological reaction of the driver,
The driver load amount calculation unit is configured to drive the driver on the basis of the driver's biological reaction detected by the biological reaction detector and the load reference information recorded in the reference information recording unit. The driving simulation device according to any one of appendices 1 to 6, which calculates a person load.

(Appendix 10)
The driving simulation device further includes an execution result detection unit that detects an execution result of the subtask when the driver performs a subtask according to the execution of the subtask scenario by the scenario execution unit,
The driver load amount calculation unit is a driver that the driver receives based on the execution result of the subtask detected by the execution result detection unit and the load reference information recorded in the reference information recording unit. The driving simulation device according to any one of appendices 1 to 6, which calculates a load amount.

(Appendix 11)
In the reference information recording unit, a plurality of load reference information serving as different references are recorded in advance.
The driving simulation device includes:
An attribute information recording unit for recording driver attribute information indicating characteristics of the driving operation by the driver, characteristics of the biological reaction of the driver, or characteristics of an execution result of the subtask when the driver performs a subtask; ,
A reference information selection unit that selects one load reference information from among a plurality of load reference information recorded in the reference information recording unit based on the driver attribute information recorded in the attribute information recording unit; The driving simulation device according to any one of appendices 1 to 10.

(Appendix 12)
The driving simulation device is a driving operation recorded in the attribute information recording unit based on a driving operation by the driver, a biological reaction of the driver, or an execution result of the subtask when the driver performs a subtask. The driving simulation apparatus according to appendix 11, further comprising an attribute information update unit that updates the person attribute information.

(Appendix 13)
A simulation management unit for realizing a virtual space including a virtual road traffic environment and a virtual moving body capable of traveling in the virtual road traffic environment according to a driving operation by a driver;
When an operation other than the driving operation by the driver is a subtask, a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask is recorded in advance,
A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance;
A driving simulation method in which a computer including a target load recording unit that records target load information indicating a target load amount to be received by the driver executes processing,
An output unit provided in the computer, an output step for giving an instruction to the driver;
The scenario execution unit included in the computer reads the subtask scenario recorded in the scenario recording unit, and executes the read subtask scenario, thereby operating the subtask execution instruction according to the subtask scenario through the output step. Scenario execution process to be output to the user,
The driver load amount calculation unit included in the computer is received by the driver based on the load reference information recorded in the reference information recording unit and the situation of the virtual moving body or the situation of the driver. A driver load amount calculating step for calculating a driver load amount;
When the load control unit provided in the computer reduces the driver load when the driver load is larger than the target load, and when the driver load is smaller than the target load Includes a load amount control step of instructing the scenario execution step to change the subtask scenario or to change the execution status of the subtask scenario in order to increase the driver load amount.

(Appendix 14)
A simulation management unit for realizing a virtual space including a virtual road traffic environment and a virtual moving body capable of traveling in the virtual road traffic environment according to a driving operation by a driver;
When an operation other than the driving operation by the driver is a subtask, a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask is recorded in advance,
A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance;
A driving simulation in which a computer including a condition information recording unit in which condition information indicating a start condition and a stop condition of execution of the subtask scenario, which is determined by a change with time of the driver load amount, is recorded in advance is executed. A method,
An output unit provided in the computer, an output step for giving an instruction to the driver;
The scenario execution unit included in the computer reads the subtask scenario recorded in the scenario recording unit, and executes the read subtask scenario, thereby operating the subtask execution instruction according to the subtask scenario through the output step. Scenario execution process to be output to the user,
The driver load amount calculation unit included in the computer is received by the driver based on the load reference information recorded in the reference information recording unit and the situation of the virtual moving body or the situation of the driver. A driver load amount calculating step for calculating a driver load amount;
When the change in the driver load amount matches the start condition while the execution of the subtask scenario is stopped, the scenario control unit included in the computer starts the execution of the subtask scenario. Instructing the scenario execution step, and if the change in the driver load amount meets the stop condition during the execution of the subtask scenario, the scenario execution step is stopped so as to stop the execution of the subtask scenario. A driving simulation method including a scenario control step for instructing.

(Appendix 15)
A simulation management unit for realizing a virtual space including a virtual road traffic environment and a virtual moving body capable of traveling in the virtual road traffic environment according to a driving operation by a driver;
When an operation other than the driving operation by the driver is a subtask, a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask is recorded in advance,
A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance;
A program that causes a computer to include a target load recording unit that records target load information indicating a target load amount to be received by the driver,
Output processing for giving instructions to the driver;
A scenario execution process for reading a subtask scenario recorded in the scenario recording unit and executing the read subtask scenario to output a subtask execution instruction according to the subtask scenario to the driver via the output process;
Driver load calculation that calculates the driver load received by the driver based on the load reference information recorded in the reference information recording unit and the status of the virtual moving body or the driver. Processing,
When the driver load amount is larger than the target load amount, the driver load amount is decreased. When the driver load amount is smaller than the target load amount, the driver load amount is increased. A program that causes the computer to execute a load amount control process that instructs the scenario execution process to change the subtask scenario or to change the execution status of the subtask scenario.

(Appendix 16)
A simulation management unit for realizing a virtual space including a virtual road traffic environment and a virtual moving body capable of traveling in the virtual road traffic environment according to a driving operation by a driver;
When an operation other than the driving operation by the driver is a subtask, a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask is recorded in advance,
A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance;
A program for causing a computer to execute a process including a condition information recording unit in which condition information indicating a start condition and a stop condition of execution of the subtask scenario, which is determined by a change with time of the driver load, is recorded. There,
Output processing for giving instructions to the driver;
A scenario execution process for reading a subtask scenario recorded in the scenario recording unit and executing the read subtask scenario to output a subtask execution instruction according to the subtask scenario to the driver via the output process;
Driver load calculation that calculates the driver load received by the driver based on the load reference information recorded in the reference information recording unit and the status of the virtual moving body or the driver. Processing,
When the change of the driver load amount matches the start condition while the execution of the subtask scenario is stopped, the scenario execution process is instructed to start the execution of the subtask scenario, A scenario control process that instructs the scenario execution process to stop the execution of the subtask scenario when the change in the driver load amount matches the stop condition during the execution of the subtask scenario; A program to be executed by a computer.

  As described above, the present invention is useful as a driving simulation apparatus, a driving simulation method, or a program that can create a dangerous situation with a high probability of occurrence of an accident in consideration of reality.

It is a block diagram showing a schematic structure of a driving simulation device concerning a 1st embodiment. It is a figure which shows an example of the load reference | standard information recorded on the reference | standard information recording part in the said driving simulation apparatus. It is a figure which shows an example of the correspondence recorded on the correspondence recording part in the said driving simulation apparatus. It is a flowchart which shows an example of the whole operation | movement of the said driving simulation apparatus. It is a flowchart which shows an example of the calculation process of the driver load amount by the driver load amount calculation part in the said driving simulation apparatus. It is a figure which shows the other example of the load reference information recorded on the said reference | standard information recording part. It is a block diagram which shows schematic structure of the driving | running simulation apparatus which concerns on 2nd Embodiment. It is a figure which shows an example of the load reference | standard information recorded on the reference | standard information recording part in the said driving simulation apparatus. It is a flowchart which shows an example of the calculation process of the driver load amount by the driver load amount calculation part in the said driving simulation apparatus. It is a block diagram which shows schematic structure of the driving | running simulation apparatus which concerns on 3rd Embodiment. It is a figure which shows an example of the load reference | standard information recorded on the reference | standard information recording part in the said driving simulation apparatus. It is a flowchart which shows an example of the process by the pulse rate acquisition part and driver | operator load amount calculation part in the said driving simulation apparatus. It is a block diagram which shows schematic structure of the driving | running simulation apparatus which concerns on 4th Embodiment. It is a figure which shows an example of the load reference | standard information recorded on the reference | standard information recording part in the said driving simulation apparatus. It is a flowchart which shows an example of the process by the execution result detection part and driver | operator load amount calculation part in the said driving simulation apparatus. It is a block diagram which shows schematic structure of the driving | running simulation apparatus which concerns on 5th Embodiment. It is a figure which shows an example of the condition information recorded on the condition information recording part in the said driving simulation apparatus. It is a flowchart which shows an example of the whole operation | movement of the said driving simulation apparatus. It is a block diagram which shows schematic structure of the driving | running simulation apparatus which concerns on 6th Embodiment. It is a figure which shows an example of the load reference | standard information recorded on the reference | standard information recording part in the said driving simulation apparatus. It is a figure which shows an example of the driver attribute information recorded on the attribute information recording part in the said driving simulation apparatus. It is a flowchart which shows an example of the selection process of the load reference | standard information by the reference | standard information selection part in the said driving simulation apparatus. It is a block diagram which shows schematic structure of the driving | running simulation apparatus which concerns on 7th Embodiment. It is a flowchart which shows an example of the update process of the driver attribute information by the attribute information update part in the said driving simulation apparatus. It is a block diagram which shows schematic structure of the driving | running simulation apparatus which concerns on 8th Embodiment. It is a flowchart which shows an example of the selection process of the target load information by the target load selection part in the said driving simulation apparatus.

Explanation of symbols

1, 1a, 1b, 1c, 1d, 1e, 1f, 1g Driving simulation device 5 Pulse detection device (biological reaction detection device)
6 Dozing detection device 11 Simulation management unit 13 Video output unit (output unit)
14 Audio output unit (output unit)
15 Scenario recording unit 16, 32 Scenario execution unit 17, 22, 25, 28, 33 Reference information recording unit 18, 23, 26, 29 Driver load amount calculation unit 19, 37 Target load recording unit 20 Load amount control unit 21 Relation recording unit 27 Execution result detection unit 30 Condition information recording unit 31 Scenario control unit 34 Attribute information recording unit 35 Reference information selection unit 36 Attribute information update unit 38 Target load selection unit

Claims (10)

In a driving simulation apparatus comprising a simulation management unit that realizes a virtual space including a virtual road traffic environment and a virtual moving body capable of traveling in the virtual road traffic environment according to a driving operation by a driver,
An output unit for giving instructions to the driver;
When an operation other than the driving operation by the driver is a subtask, a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask is recorded in advance,
A scenario execution unit that reads out the subtask scenario recorded in the scenario recording unit, and outputs the subtask execution instruction according to the subtask scenario to the driver via the output unit by executing the read subtask scenario;
A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance;
Driver load calculation that calculates the driver load received by the driver based on the load reference information recorded in the reference information recording unit and the status of the virtual moving body or the driver. And
A target load recording unit for recording target load information indicating a target load amount to be received by the driver;
When the driver load amount is larger than the target load amount, the driver load amount is decreased. When the driver load amount is smaller than the target load amount, the driver load amount is increased. And a load amount control unit that instructs the scenario execution unit to change the subtask scenario or change the execution status of the subtask scenario. The driving simulation device further includes a correspondence recording unit in which the correspondence between the subtask scenario and the load of the subtask scenario is recorded in advance.
When the instruction to change the subtask scenario is issued from the load amount control unit in order to reduce the driver load amount, the scenario execution unit is currently executing by referring to the correspondence recording unit The subtask scenario is changed to a subtask scenario having a lower load than the subtask scenario, and the load amount control unit instructs to change the subtask scenario in order to increase the driver load amount, The operation simulation device according to claim 1, wherein the scenario execution unit changes the currently executed subtask scenario to a subtask scenario having a higher load than the subtask scenario by referring to the correspondence relationship recording unit. In a driving simulation apparatus comprising a simulation management unit that realizes a virtual space including a virtual road traffic environment and a virtual moving body capable of traveling in the virtual road traffic environment according to a driving operation by a driver,
An output unit for giving instructions to the driver;
When an operation other than the driving operation by the driver is a subtask, a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask is recorded in advance,
A scenario execution unit that reads out the subtask scenario recorded in the scenario recording unit, and outputs the subtask execution instruction according to the subtask scenario to the driver via the output unit by executing the read subtask scenario;
A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance;
Driver load calculation that calculates the driver load received by the driver based on the load reference information recorded in the reference information recording unit and the status of the virtual moving body or the driver. And
A condition information recording unit preliminarily recorded with condition information indicating a start condition and a stop condition of execution of the subtask scenario, which is determined by a change with time in the driver load amount;
When the change of the driver load amount matches the start condition while the execution of the subtask scenario is stopped, the scenario execution unit is instructed to start the execution of the subtask scenario, A scenario control unit that instructs the scenario execution unit to stop the execution of the subtask scenario when a change in the driver load amount matches the stop condition during the execution of the subtask scenario; Driving simulation device.   The driver load amount calculation unit acquires driving operation information related to the driving operation by the driver from the simulation management unit, and acquires the acquired driving operation information and the load reference information recorded in the reference information recording unit. The driving simulation device according to any one of claims 1 to 3, wherein a driving load received by the driver is calculated based on the driving load.   The driver load amount calculation unit acquires road traffic information indicating the virtual road traffic environment from the simulation management unit, and acquires the acquired road traffic information and the load reference information recorded in the reference information recording unit. The driving simulation device according to any one of claims 1 to 3, wherein a driving load received by the driver is calculated based on the driving load. The driving simulation device can access a biological reaction detection device that detects a biological reaction of the driver,
The driver load amount calculation unit is configured to drive the driver on the basis of the driver's biological reaction detected by the biological reaction detector and the load reference information recorded in the reference information recording unit. The driving simulation device according to any one of claims 1 to 3, wherein a person load is calculated. The driving simulation device further includes an execution result detection unit that detects an execution result of the subtask when the driver performs a subtask according to the execution of the subtask scenario by the scenario execution unit,
The driver load amount calculation unit is a driver that the driver receives based on the execution result of the subtask detected by the execution result detection unit and the load reference information recorded in the reference information recording unit. The driving simulation device according to any one of claims 1 to 3, wherein a load amount is calculated. In the reference information recording unit, a plurality of load reference information serving as different references are recorded in advance.
The driving simulation device includes:
An attribute information recording unit for recording driver attribute information indicating characteristics of the driving operation by the driver, characteristics of the biological reaction of the driver, or characteristics of a subtask execution situation when the driver performs a subtask;
A reference information selection unit that selects one load reference information from among a plurality of load reference information recorded in the reference information recording unit based on the driver attribute information recorded in the attribute information recording unit; The driving | running simulation apparatus as described in any one of Claims 1-7. A simulation management unit for realizing a virtual space including a virtual road traffic environment and a virtual moving body capable of traveling in the virtual road traffic environment according to a driving operation by a driver;
When an operation other than the driving operation by the driver is a subtask, a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask is recorded in advance,
A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance;
A driving simulation method in which a computer including a target load recording unit that records target load information indicating a target load amount to be received by the driver executes processing,
An output unit provided in the computer, an output step for giving an instruction to the driver;
The scenario execution unit included in the computer reads the subtask scenario recorded in the scenario recording unit, and executes the read subtask scenario, thereby operating the subtask execution instruction according to the subtask scenario through the output step. Scenario execution process to be output to the user,
The driver load amount calculation unit included in the computer is received by the driver based on the load reference information recorded in the reference information recording unit and the situation of the virtual moving body or the situation of the driver. A driver load amount calculating step for calculating a driver load amount;
When the load control unit provided in the computer reduces the driver load when the driver load is larger than the target load, and when the driver load is smaller than the target load Includes a load amount control step of instructing the scenario execution step to change the subtask scenario or to change the execution status of the subtask scenario in order to increase the driver load amount. A simulation management unit for realizing a virtual space including a virtual road traffic environment and a virtual moving body capable of traveling in the virtual road traffic environment according to a driving operation by a driver;
When an operation other than the driving operation by the driver is a subtask, a scenario recording unit in which a subtask scenario for causing the driver to perform the subtask is recorded in advance,
A reference information recording unit in which load reference information serving as a reference for calculating the driver load received by the driver is recorded in advance;
A program that causes a computer to include a target load recording unit that records target load information indicating a target load amount to be received by the driver,
Output processing for giving instructions to the driver;
A scenario execution process for reading a subtask scenario recorded in the scenario recording unit and executing the read subtask scenario to output a subtask execution instruction according to the subtask scenario to the driver via the output process;
Driver load calculation that calculates the driver load received by the driver based on the load reference information recorded in the reference information recording unit and the status of the virtual moving body or the driver. Processing,
When the driver load amount is larger than the target load amount, the driver load amount is decreased. When the driver load amount is smaller than the target load amount, the driver load amount is increased. A program that causes the computer to execute a load amount control process that instructs the scenario execution process to change the subtask scenario or to change the execution status of the subtask scenario.

Images