Vehicle emergency notification device, vehicle emergency notification method, and program

Abstract

To enable an erroneous call to be suppressed when an emergency call is unnecessary.SOLUTION: An emergency call device for a vehicle comprises: an invalid condition determination unit that determines whether or not at least one of invalid conditions of not detecting a shock applied to the vehicle within a predetermined time period or being within a predetermined time period after an ignition is turned on is satisfied; and an emergency call button control unit that disables an emergency call button mounted on the vehicle when the invalid condition determination unit determines that the invalid condition is satisfied.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to a vehicle emergency notification device, a vehicle emergency notification method, and a program.

Background Art

[0002] Some drive recorders are equipped with an emergency notification button for making a notification in an emergency. There is a possibility that the emergency notification button may be pressed by mistake when it is not an emergency, resulting in an accidental notification. As a means for preventing such accidental notifications, there is known a means for enabling the pressing of the emergency notification button only when an impact equal to or greater than a certain level is detected (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, with the above-described means, an emergency notification cannot be made when an emergency notification is desired but no impact is detected. For example, when being tailgated by a following vehicle during driving, when stopped due to sudden physical discomfort, or when stopped to assist after witnessing an accident, it is considered that an impact equal to or greater than a certain level is not given to the vehicle body. With the above-described means, in those cases, the emergency notification button cannot be pressed (the pressing is disabled).

[0005] Also, if the emergency notification button is made always pressable in order to avoid this problem, there is a possibility that malfunctions (accidental notifications) will increase when children press it for fun. An increase in accidental notifications leads to a decline in services such as difficulty in connecting to the call center. Similarly, when the emergency call button is made so hard that it cannot be pressed by a child (requiring a certain amount of force or more to press), there is a problem that a user with insufficient force cannot use the emergency call button, leading to poor usability. It has been required that false alarms can be suppressed when emergency calls are not necessary.

[0006] The present invention has been made in view of the above points, and provides a vehicle emergency notification device, a vehicle emergency notification method, and a program that can suppress false alarms when emergency notifications are not necessary.

Means for Solving the Problems

[0007] The present invention has been made to solve the above problems, and one aspect of the present invention is Going back from the current time when it is determined that the vehicle is not in motion Within a predetermined time The It is determined whether at least one of the invalid conditions, that is, no impact applied to the vehicle is detected, or it is within a predetermined time from when the ignition is turned on, is satisfied. An invalid condition determination unit, and when it is determined by the invalid condition determination unit that the invalid condition is satisfied, an emergency call button control unit that invalidates the emergency call button mounted on the vehicle. current time is A vehicle emergency notification device comprising:

[0008] Also, one aspect of the present invention is that in the above vehicle emergency notification device, the invalid condition determination unit 、 By the user during the operation of the menu In the case, it is determined that the invalid condition is satisfied.

[0009] Also, one aspect of the present invention is that in the above vehicle emergency notification device, when the emergency call button is invalid, a valid condition determination unit that determines at least one of the following conditions (a) to (d) as valid conditions: (a) Speech using specific phrases is made; (b) A predetermined physical operation is performed; (c) A predetermined operation is performed on a button realized software-wise; (ii) A specific object or gesture is photographed within the angle of view of the photographing unit; further comprising, wherein the emergency notification button control unit enables the emergency notification button when it is determined by the valid condition determination unit that at least one of the above conditions is satisfied.

[0010] Also, in one aspect of the present invention, in the above vehicle emergency notification device, when it is determined by the invalid condition determination unit that the invalid condition is satisfied and the emergency notification button is pressed, the notification unit is caused to execute a notification to an external device after a predetermined time.

[0011] Also, one aspect of the present invention is Going back from the current time when it is determined that the vehicle is not in motion within a predetermined time The no impact applied to the vehicle is detected, or current time is an invalid condition determination step of determining whether at least one of the invalid conditions that it is within a predetermined time since ignition on is satisfied, and an emergency notification button control step of invalidating the emergency notification button mounted on the vehicle when it is determined by the invalid condition determination step that the invalid condition is satisfied.

[0012] Also, one aspect of the present invention is a program for causing a computer to Going back from the current time when it is determined that the vehicle is not in motion within a predetermined time The no impact applied to the vehicle is detected, or current time is execute an invalid condition determination step of determining whether at least one of the invalid conditions that it is within a predetermined time since ignition on is satisfied, and an emergency notification button control step of invalidating the emergency notification button mounted on the vehicle when it is determined by the invalid condition determination step that the invalid condition is satisfied.

Advantages of the Invention

[0013] According to the present invention, false notifications can be suppressed when emergency notifications are unnecessary.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Modes for Carrying Out the Invention

[0015] (First Embodiment) Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram showing an example of the appearance of the drive recorder 1 according to the present embodiment. The drive recorder 1 is installed, for example, mainly on the dashboard or the windshield of a vehicle 3 (not shown).

[0016] The drive recorder 1 is provided with an emergency notification button 2. The emergency notification button 2 is a button for making a notification in an emergency. When the emergency notification button 2 is pressed, a notification that it is an emergency is sent from the drive recorder 1 to a server 4 (not shown). As will be described later, the drive recorder 1 has a function of preventing false notifications, which is a function for suppressing false notifications when emergency notifications are not necessary and enabling emergency notifications when necessary. Here, the emergency notification button 2 is mounted on the vehicle 3 when the drive recorder 1 is installed on the vehicle 3.

[0017] Here, in FIG. 1, as an example, the case where the shape of the main body portion of the drive recorder 1 is a rectangular parallelepiped is shown, but the shape of the main body portion of the drive recorder 1 is not limited to a rectangular parallelepiped. The emergency notification button 2 is provided, for example, on the front surface of the drive recorder 1. Note that the emergency notification button 2 may be provided on the upper surface, the bottom surface, the side surface, or the rear surface of the drive recorder 1.

[0018] [Configuration of Drive Recorder] FIG. 2 is a diagram showing an example of the hardware configuration of the drive recorder 1 according to the present embodiment. The drive recorder 1 includes an acceleration sensor 10, a GPS receiver 11, a camera 12, a speaker 13, a display 14, an operation button 15, a microphone 16, a timer 17, a CPU 18, a ROM 19, a RAM 110, a communication module 111, and a vehicle signal cable 112. The acceleration sensor 10, the GPS receiver 11, the camera 12, the speaker 13, the display 14, the operation button 15, the microphone 16, the timer 17, the CPU 18, the ROM 19, the RAM 110, the communication module 111, and the vehicle signal cable 112 are connected to each other by signal lines.

[0019] The acceleration sensor 10 measures the acceleration of the vehicle 3. The GPS receiver 11 acquires information indicating the current position of the vehicle 3 using GPS (Global Positioning System). The camera 12 captures and records moving images during the travel of the vehicle 3. The speaker 13 outputs a warning sound by voice.

[0020] The display 14 displays various screens. The display 14 is, for example, a liquid crystal display or an organic electroluminescence (EL) display. The operation button 15 is a button for the user to operate the drive recorder 1. The operation button 15 includes the emergency notification button 2 shown in FIG. 1.

[0021] Note that the display 14 may be a touch panel. In that case, the operation button 15 may be configured integrally with the display 14. Or, a part of the operation button 15 may be configured integrally with the display 14. In the present embodiment, an example in the case where the display 14 is a touch panel and the buttons other than the emergency notification button 2 among the operation buttons 15 are configured integrally with the display 14 will be described.

[0022] The microphone 16 picks up the voice of the user. The timer 17 measures time.

[0023] The CPU 18 reads a program from the ROM 19 and executes various controls according to the read program. The CPU 18 incorporates a plurality of internal storage media such as registers. The CPU 18 temporarily stores data from the ROM 19 in the internal storage media and performs arithmetic processing on this. The CPU 18 outputs the arithmetic result to the register and further outputs it from the register to the RAM 110 or an external storage medium.

[0024] The ROM 19 is a main memory device that stores various programs, data, parameters, etc. for the CPU 18 to perform various operations and controls. The ROM 19 can retain the stored content even when the power supplied to the ROM 19 is zero.

[0025] The RAM 110 is a main memory device used as a working memory for the CPU 18. The RAM 110 is written to and erased by the CPU 18 for programs, data, etc. The RAM 110 is configured using a memory device such as a semiconductor memory device, for example.

[0026] The communication module 111 transmits and receives various information via the wireless network NW. The communication module 111 includes a communication interface (I / F).

[0027] The vehicle signal cable 112 acquires vehicle signals from the vehicle 3. The vehicle signals are signals indicating the state of the vehicle 3. The vehicle signal cable 112 acquires various vehicle signals from the ECU (Electronic Control Unit) of the vehicle 3. The various vehicle signals include, for example, an ignition switch signal, a vehicle speed signal, etc.

[0028] Note that in this embodiment, from the hardware configuration of the drive recorder 1 shown in FIG. 2, the microphone 16 may be omitted.

[0029] FIG. 3 is a diagram showing an example of the functional configuration of the drive recorder 1 according to this embodiment. The drive recorder 1 includes a control unit 20, a speed acquisition unit 21, a vehicle signal acquisition unit 22, a shock detection unit 23, a position acquisition unit 24, a photographing unit 25, a timing unit 26, an operation unit 27, an audio output unit 28, a display unit 29, a communication unit 210, and a storage unit 211.

[0030] The control unit 20 performs various controls on the drive recorder 1. The control unit 20 includes, for example, a CPU and performs various calculations and information exchanges. Each functional unit included in the control unit 20 is realized by the CPU reading a program from the ROM and executing the processing. Each functional unit included in the control unit 20 will be described later. The control unit 20 includes the CPU 18, ROM 19, and RAM 110 shown in FIG. 2.

[0031] The speed acquisition unit 21 acquires the speed of the vehicle 3. The speed acquisition unit 21 generates speed data A1 based on the acquired speed. The speed data A1 indicates the speed of the vehicle 3. As an example, the speed acquisition unit 21 acquires the position of the vehicle 3 from the GPS reception unit 11 at a predetermined cycle, and calculates the speed of the vehicle 3 based on the distance by which the position of the vehicle 3 has changed during the cycle, thereby acquiring the speed of the vehicle 3.

[0032] The vehicle signal acquisition unit 22 acquires the vehicle signals of the vehicle 3. The vehicle signal acquisition unit 22 generates vehicle signal data B1 based on the acquired vehicle signals. The vehicle signal data B1 indicates the on or off state of the ignition. The vehicle signal acquisition unit 22 includes the vehicle signal cable 112 shown in FIG. 2.

[0033] When the vehicle 3 is traveling in a tunnel, the accuracy of the information indicating the current position of the vehicle 3 received by the GPS reception unit 11 may not be sufficiently high. The speed acquisition unit 21 may acquire the speed of the vehicle 3 by acquiring the vehicle speed signal included in the vehicle signals acquired by the vehicle signal acquisition unit 22. Further, the speed acquisition unit 21 may calculate the speed of the vehicle 3 based on the video captured by the camera 12.

[0034] The impact detection unit 23 detects the impact applied to the vehicle 3. The impact detection unit 23 generates impact detection data C1 based on the detection result. The impact detection data C1 indicates at least one of the magnitude or direction of the impact applied to the drive recorder 1. The impact detection unit 23 includes the acceleration sensor 10 shown in FIG. 2.

[0035] The position acquisition unit 24 acquires the position of the vehicle 3. Based on the acquired position, the position acquisition unit 24 generates position data D1. The position data D1 indicates the position of the vehicle 3. Since the drive recorder 1 is mounted on the vehicle 3, the position of the vehicle 3 is the same as the position of the drive recorder 1. The position acquisition unit 24 includes the GPS reception unit 11 shown in FIG. 2.

[0036] The imaging unit 25 captures a moving image. As a result of the imaging, the imaging unit 25 generates image data E1. The image data E1 indicates the video constantly recorded by the camera 12. In addition, the imaging unit 25 captures a moving image for a predetermined length of time before and after the time when an impact is detected, such as during an accident. The imaging unit 25 includes the camera 12 shown in FIG. 2.

[0037] The timing unit 26 performs various timings. The timing unit 26 starts and stops timing in response to a signal from the control unit 20. The timing performed by the timing unit 26 includes the function of a timer. As a result of the timing, the timing unit 26 generates timing data F1. The timing data F1 includes, for example, the time elapsed from when the timing start signal is acquired from the control unit 20 until the timing stop signal is acquired. Alternatively, when the timing unit 26 performs timing as a timer function, the remaining time of the timer is included in the timing data F1. The timing unit 26 may perform a plurality of timings in parallel. When a plurality of timings are performed in parallel, the timing data F1 includes the results of those plurality of timings. In addition, the current time may be included in the timing data F1. The timing unit 26 includes the timer 17 shown in FIG. 2.

[0038] The operation unit 27 is operated by the user of the drive recorder 1 to perform various operations. The operation unit 27 includes the emergency notification button 2 shown in FIG. 1, a release button 271, and a menu operation button 272. The release button 271 is a button for enabling the emergency notification button 2 when the emergency notification button 2 is disabled. The menu operation button 272 is a button for the user to operate the drive recorder 1.

[0039] The emergency notification button 2, the release button 271, and the menu operation button 272 are included in the operation button 15 shown in FIG. 2. As described above, in this embodiment, since the buttons other than the emergency notification button 2 among the operation buttons 15 are configured integrally with the display 14, the release button 271 and the menu operation button 272 are configured integrally with the display 14.

[0040] The voice output unit 28 outputs various voices. The voices output by the voice output unit 28 include, for example, the voice output as a warning sound at the time of impact detection. Note that the voices output by the voice output unit 28 may include a voice for notifying the user that a notification has been made when the emergency notification button 2 is pressed. Further, the voices output by the voice output unit 28 may include a voice for notifying the user that the disabled emergency notification button 2 has become enabled. The voice output unit 28 includes the speaker 13 and the RAM 110 shown in FIG. 2. Voice data is stored in the RAM 110.

[0041] The display unit 29 displays various screens. The screens displayed by the display unit 29 include a menu operation screen for the user to operate the drive recorder 1. The screens displayed by the display unit 29 include, for example, a warning screen displayed as a warning at the time of impact detection. The display unit 29 includes the display 14 and the RAM 110 shown in FIG. 2. The RAM 110 includes image data of the warning screen.

[0042] The communication unit 210 communicates with an external device. The external devices with which the communication unit 210 communicates include a server 4 (not shown). When the emergency notification button 2 is pressed or an event file is transmitted from the drive recorder 1 at the time of impact detection, an emergency notification is sent to the server 4. The communication unit 210 includes the communication module 111 shown in FIG. 2.

[0043] The storage unit 211 stores various types of information. The information stored in the storage unit 211 includes driving record information G1. The driving record information G1 indicates, for example, the history of the position information of the vehicle 3. In this history, the time and the position of the vehicle 3 at that time are associated with each other. Note that the driving record information G1 may be video that is constantly recorded by the camera 12. The driving record information G1 may include both the history of the position information of the vehicle 3 and the video that is constantly recorded by the camera 12.

[0044] The storage unit 211 stores event information H1 generated when an impact is detected. The event information H1 is information in which the time when the impact is detected and the impact detection data C1 are associated with each other. The event information H1 may include video for a predetermined period before and after the time when an impact is detected, such as during an accident. The storage unit 211 includes the RAM 110 shown in FIG. 2.

[0045] Here, each functional unit included in the control unit 20 will be described. The control unit 20 includes an acquisition unit 200, an operation reception unit 207, an impact detection processing unit 2011, an image recording unit 2012, a display control unit 2013, a notification unit 2014, and a false notification prevention processing unit 300.

[0046] The acquisition unit 200 acquires various types of information. The acquisition unit 200 includes a speed data acquisition unit 201, a vehicle signal data acquisition unit 202, an impact detection data acquisition unit 203, a position information acquisition unit 204, a captured image acquisition unit 205, and a timekeeping data acquisition unit 206. The speed data acquisition unit 201 acquires speed data A1 from the speed acquisition unit 21. The vehicle signal data acquisition unit 202 acquires vehicle signal data B1 from the vehicle signal acquisition unit 22. The impact detection data acquisition unit 203 acquires impact detection data C1 from the impact detection unit 23. The position information acquisition unit 204 acquires position data D1 from the position acquisition unit 24. The captured image acquisition unit 205 acquires image data E1 from the imaging unit 25. The timekeeping data acquisition unit 206 acquires timekeeping data F1 from the timekeeping unit 26.

[0047] The operation reception unit 207 receives various operations performed on the operation unit 27. The operation reception unit 207 includes an emergency call reception unit 208, a release reception unit 209, and a menu operation reception unit 2010. The emergency call reception unit 208 receives an emergency call operation. The emergency call reception unit 208 receives the operation by detecting that the emergency call button 2 has been pressed. The release reception unit 209 receives an operation to enable the emergency call button 2 (release the lock of the emergency call button 2) when the emergency call button 2 is disabled (the emergency call button 2 is locked). The release reception unit 209 receives the operation by detecting that the release method has been executed. The execution of the release method is, for example, that the release button 271 has been pressed. The menu operation button 272 receives a menu operation. The menu operation button 272 receives the operation by detecting that the menu operation button 272 has been pressed.

[0048] When the impact detection processing unit 2011 detects an impact of a predetermined magnitude or more by the impact detection unit 23, it performs impact detection time processing, which is predetermined processing. The impact detection time processing includes processing for outputting a warning sound to the voice output unit 28 and processing for displaying a warning screen on the display unit 29. Further, the impact detection time processing includes processing for generating event information H1 and storing the event information H1 in the storage unit 211.

[0049] The image recording unit 2012 stores the image data E1 in the storage unit 211. Note that the image recording unit 2012 continuously stores the image data E1 in the storage unit 211 while the drive recorder 1 is operating. The display control unit 2013 controls the display unit 29 to display various screens on the display unit 29.

[0050] The reporting unit 2014 transmits a report to the server 4 via the communication unit 210. The reporting unit 2014 transmits a report when the emergency reporting button 2 is valid and the emergency reporting reception unit 208 has received an emergency reporting operation. Alternatively, the reporting unit 2014 transmits a report when the emergency reporting button 2 becomes valid after the emergency reporting reception unit 208 has received an emergency reporting operation. The report transmitted by the reporting unit 2014 includes at least one or more pieces of information such as the position of the vehicle 3 indicated by the position data D1, the video recorded by the camera 12 indicated by the image data E1, or the user identification number.

[0051] Here, the user identification number is, for example, at least one or more of an identifier associated with the drive recorder 1, an identifier associated with the user of the drive recorder 1, an identifier associated with the user of the reporting service for which the drive recorder 1 makes a report, and an identifier associated with the vehicle 3. Note that the reporting unit 2014 may be omitted from the configuration of the drive recorder 1 and provided in a device separate from the drive recorder 1. In that case, the control unit 20 causes the reporting unit 2014 provided in the separate device to execute a report via the communication unit 210.

[0052] The false report prevention processing unit 300 executes false report prevention processing. The false report prevention processing is processing for suppressing false reports when emergency reports are unnecessary and enabling emergency reports when necessary. The false report prevention processing unit 300 includes an invalid condition determination unit 301, an emergency reporting button control unit 302, and a valid condition determination unit 303.

[0053] The invalid condition determination unit 301 determines whether an invalid condition is satisfied. The invalid condition is any one or more of the fact that no impact applied to the vehicle is detected within a predetermined time, or the fact that it is within a predetermined time from when the ignition is turned on. In the present embodiment, as an example, the invalid condition is that the vehicle is not in motion, there is no driving record within a predetermined time, no impact applied to the vehicle is detected within a predetermined time, or the menu is not being operated.

[0054] The emergency notification button control unit 302 controls the emergency notification button 2. The state of the emergency notification button 2 includes an effective state and an invalid state. In the effective state, when the emergency notification button 2 is pressed as described above, the notification unit 2014 makes an emergency notification.

[0055] On the other hand, in the invalid state, either control is performed so that an emergency notification is not made by the notification unit 2014 even when the emergency notification button 2 is pressed, or the emergency notification button 2 is in a state where it cannot be physically pressed. The state where the emergency notification button 2 cannot be physically pressed is realized by, for example, a pressing prevention mechanism. Specific examples of the pressing prevention mechanism will be described later.

[0056] When the invalid condition determination unit 301 determines that the invalid condition is satisfied, the emergency notification button control unit 302 invalidates the emergency notification button 2. In the present embodiment, as an example, the state where the emergency notification button 2 is invalid means a state in which control is performed so that an emergency notification is not made by the notification unit 2014 even when the emergency notification button 2 is pressed.

[0057] When the emergency notification button 2 is invalid, the valid condition determination unit 303 determines a valid condition that is at least one of the following conditions (a), (b), (c), and (d). (a) Uttering by a specific phrase; (b) Performing a predetermined physical operation; (c) Performing a predetermined operation on a software-implemented button; (d) A specific object or gesture is photographed within the angle of view of the photographing unit 25;

[0058] In the following description, the method of enabling the emergency notification button 2 when the valid condition is satisfied (unlocking the emergency notification button 2) is also referred to as the unlocking method. In this embodiment, as an example, the valid condition is that the release button 271 is being pressed. That is, in this embodiment, when the emergency notification button 2 is pressed while the release button 271 is being pressed, an emergency notification is executed. In other words, in order to execute an emergency notification, it is necessary to press a plurality of buttons including the emergency notification button 2 and the release button 271. Thus, in this embodiment, the valid condition is that a predetermined physical operation is performed among the above conditions.

[0059] [Emergency Notification Button Control Processing] Next, with reference to FIGS. 4 to 7, the emergency notification button control processing by the drive recorder 1 will be described. FIG. 4 is a diagram showing an example of the emergency notification button control processing according to this embodiment. The emergency notification button control processing shown in FIG. 4 is executed by the control unit 20. The control unit 20 repeatedly executes the emergency notification button control processing shown in FIG. 4, for example, while the power of the drive recorder 1 is on. The invalid condition is determined by the processing of step S10, step S20, step S40, or step S50 shown in FIG. 4. In this embodiment, the invalid condition corresponds to that a menu operation is being performed and the vehicle 3 is parked.

[0060] Step S10: The invalid condition determination unit 301 determines whether a menu operation is in progress. 301 determines that a menu operation is in progress when it acquires a signal indicating that the menu operation button 272 has been pressed from the menu operation reception unit 2010.

[0061] When the invalid condition determination unit 301 determines that a menu operation is in progress (step S10; YES), the false notification prevention processing unit 300 executes the processing of step S60. On the other hand, when the invalid condition determination unit 301 determines that a menu operation is not in progress (step S10; NO), it executes the processing of step S20.

[0062] Step S20: The invalid condition determination unit 301 determines whether the vehicle 3 is in motion. The invalid condition determination unit 301 acquires speed data A1 from the speed data acquisition unit 201. When the speed indicated by the acquired speed data A1 is equal to or higher than a predetermined speed, the invalid condition determination unit 301 determines that the vehicle 3 is in motion.

[0063] When the invalid condition determination unit 301 determines that the vehicle 3 is in motion (Step S20; YES), the false notification prevention processing unit 300 executes the processing of Step S30. On the other hand, when the invalid condition determination unit 301 determines that the vehicle 3 is not in motion (Step S20; NO), the processing of Step S40 is executed.

[0064] Step S30: The emergency notification button control unit 302 enables the emergency notification button 2. Thereafter, the control unit 20 ends the emergency notification button control process.

[0065] Step S40: The invalid condition determination unit 301 determines whether there is a driving record within a predetermined time. The invalid condition determination unit 301 reads driving record information G1 from the storage unit 211. The invalid condition determination unit 301 also acquires timing data F1 from the timing data acquisition unit 206. The invalid condition determination unit 301 determines whether there is a driving record within a predetermined time based on the read driving record information G1 and the current time indicated by the acquired timing data F1. Here, the predetermined time is, for example, 10 seconds.

[0066] When the invalid condition determination unit 301 determines that there is a driving record within a predetermined time (Step S40; YES), the false notification prevention processing unit 300 executes the processing of Step S30. On the other hand, when the invalid condition determination unit 301 determines that there is no driving record within a predetermined time (Step S40; NO), the processing of Step S50 is executed.

[0067] Step S50: The invalid condition determination unit 301 determines whether an impact has been detected within a predetermined time. The invalid condition determination unit 301 reads the event information H1 from the storage unit 211. Also, the invalid condition determination unit 301 acquires the timing data F1 from the timing data acquisition unit 206. The invalid condition determination unit 301 determines whether an impact has been detected within a predetermined time based on the read event information H1 and the current time indicated by the acquired timing data F1. Here, the predetermined time is, for example, 10 seconds.

[0068] When the invalid condition determination unit 301 determines that an impact has been detected within a predetermined time (Step S50; YES), the false alarm prevention processing unit 300 executes the processing of Step S30. On the other hand, when the invalid condition determination unit 301 determines that an impact has not been detected within a predetermined time (Step S50; NO), the false alarm prevention processing unit 300 executes the processing of Step S60.

[0069] Step S60: The emergency call button control unit 302 disables the emergency call button 2. Here, as an example, the emergency call button control unit 302 disables the emergency call button 2 by controlling so that the reporting unit 2014 does not make an emergency call even if the emergency call button 2 is pressed. After that, the false alarm prevention processing unit 300 ends the emergency call button control process. Thus, the control unit 20 ends the emergency call button control process.

[0070] [Processing when the emergency call button is pressed] FIG. 5 is a diagram showing an example of the processing when the emergency call button is pressed according to the present embodiment. The processing when the emergency call button is pressed shown in FIG. 5 is executed by the control unit 20. The control unit 20 repeatedly executes the processing when the emergency call button is pressed shown in FIG. 5, for example, while the power of the drive recorder 1 is on.

[0071] Step S110: The emergency call button control unit 302 determines whether the emergency call button 2 has been pressed. When the emergency call button control unit 302 obtains a signal indicating that the emergency call button 2 has been pressed from the emergency call reception unit 208, it determines that the emergency call button 2 has been pressed.

[0072] When the emergency call button control unit 302 determines that the emergency call button 2 has been pressed (Step S110; YES), it executes the process of Step S120. On the other hand, when the emergency call button control unit 302 determines that the emergency call button 2 has not been pressed (Step S110; NO), it ends the process when the emergency call button is pressed.

[0073] Step S120: The emergency call button control unit 302 determines whether the emergency call button 2 is valid. When the emergency call button control unit 302 determines that the emergency call button 2 is valid (Step S120; YES), it executes the process of Step S130. On the other hand, when the emergency call button control unit 302 determines that the emergency call button 2 is invalid (Step S120; NO), it ends the process when the emergency call button is pressed.

[0074] Step S130: The emergency call button control unit 302 causes the reporting unit 2014 to make an emergency call. The reporting unit 2014 transmits a report to the server 4 via the communication unit 210. With the above, the control unit 20 ends the process when the emergency call button is pressed.

[0075] [Emergency Call Button Switching Process] FIG. 6 is a diagram showing an example of the emergency call button switching process according to the present embodiment. The emergency call button switching process shown in FIG. 6 is executed by the control unit 20. The control unit 20 repeatedly executes the emergency call button switching process shown in FIG. 6, for example, while the power of the drive recorder 1 is on.

[0076] Step S210: The validity condition determination unit 303 determines whether the cancellation method is being executed. For example, when the validity condition determination unit 303 acquires a signal indicating that the cancellation button 271 is being pressed from the cancellation reception unit 209, it determines that the cancellation method is being executed.

[0077] When the validity condition determination unit 303 determines that the cancellation method is being executed (Step S210; YES), the emergency call button control unit 302 executes the process of Step S220. On the other hand, when the validity condition determination unit 303 determines that the cancellation method is not being executed (Step S210; NO), the emergency call button control unit 302 executes the process of Step S230.

[0078] Since the processes of Step S220 and Step S230 shown in FIG. 6 are the same as the processes of Step S30 and Step S60 shown in FIG. 4 respectively, the description is omitted. Thus, the control unit 20 ends the emergency call button switching process.

[0079] In this embodiment, an example where the validity condition is that the cancellation button 271 is being pressed has been described, but it is not limited to this. Other predetermined physical operations may be used as the validity condition. For example, the validity condition may be that the cancellation button 271 is pressed in a state where the emergency call button 2 is invalid. Also, the validity condition may be that a plurality of buttons are pressed in a predetermined order. The plurality of buttons may be, for example, a plurality of cancellation buttons. Also, the plurality of buttons may be composed of the emergency call button 2 and one or more cancellation buttons.

[0080] Also, in the invalid state, when the emergency call button 2 cannot be physically pressed by the depression prevention mechanism, the enabling condition may be to release the depression prevention mechanism. The depression prevention mechanism is electrically controlled by the control unit 20, for example, according to whether the emergency call button 2 is valid or invalid. Note that the depression prevention mechanism may be manually releasable by the user in order to enable the emergency call button 2.

[0081] The depression prevention mechanism is, for example, a locking mechanism that locks the emergency call button 2. The locking mechanism is, for example, a stopper member. The depression prevention mechanism may be a protective member such as a lid or shutter that protects the emergency call button 2. When a protective member is used, the user's touching the emergency call button 2 itself is suppressed. An example of the case where the depression prevention mechanism is used will be described later in the third embodiment.

[0082] Also, the enabling condition may be that a predetermined operation is performed on a software-implemented button. For example, when the display 14 and the operation button 15 are integrated as a touch panel and provided in the drive recorder 1, when a predetermined operation is performed on the button displayed on the touch panel, the emergency call button 2 may be controlled from the invalid state to the valid state.

[0083] For example, the button displayed on the touch panel is displayed as a release button. Or, a plurality of buttons are displayed on the touch panel, and the enabling condition may be that they are pressed simultaneously, or a specific button among the plurality of buttons is pressed. Also, the enabling condition may be that the plurality of buttons displayed on the touch panel are pressed in a predetermined order. Also, a password input form for enabling the emergency call button 2 may be displayed on the touch panel.

[0084] Alternatively, the activation condition may be that a specific object or gesture is captured within the angle of view of the imaging unit 25. The specific object may be, for example, the key of the vehicle 3 on which the drive recorder 1 is mounted, the face of the user, etc. As described above, the function of the imaging unit 25 is realized by the camera 12. The camera 12 is provided on the back surface, which is the surface opposite to the front surface where the display 14 is provided in the drive recorder 1. Therefore, in order to activate the emergency notification button 2, imaging is performed such that a specific object, one's own hand, etc. is located on the back side. Or the user may change the orientation of the drive recorder 1 and direct the camera 12 towards oneself for imaging.

[0085] (Modification example) Note that in the emergency notification button control process shown in FIG. 4, among the invalidation conditions of step S10, step S20, step S40, or step S50, there may be those omitted. That is, the invalidation condition may include at least one or more of the conditions of step S10, step S20, step S40, and step S50. Also, in the emergency notification button control process shown in FIG. 4, as an invalidation condition, in step S40, instead of the condition that there is no driving record within a predetermined time, the condition that it is within a predetermined time from when the ignition is turned on may be determined.

[0086] Note that as an invalidation condition, the position of the vehicle 3 on which the drive recorder 1 is mounted may be included in a predetermined location. In that case, the invalidation condition determination unit 301 acquires the position data D1 from the position information acquisition unit 204. The invalidation condition determination unit 301 determines whether or not the position of the vehicle 3 is included in the predetermined location based on the acquired position data D1. The predetermined location is, for example, a parking lot.

[0087] (Modification example 1) Next, referring to FIG. 7, a modified example of the emergency notification button switching process will be described. FIG. 7 is a diagram showing an example of the emergency notification button switching process according to this modified example. The emergency notification button switching process shown in FIG. 7 is executed by the control unit 20. The control unit 20 repeatedly executes the emergency notification button switching process shown in FIG. 7, for example, while the power of the drive recorder 1 is on.

[0088] Step S310: The valid condition determination unit 303 determines whether the cancellation method is being executed. The valid condition determination unit 303 determines that the cancellation method is being executed, for example, when it acquires a signal indicating that the cancellation button 271 has been pressed from the cancellation reception unit 209. If the valid condition determination unit 303 determines that the cancellation method is being executed (Step S310; YES), it executes the process of Step S320. On the other hand, if the valid condition determination unit 303 determines that the cancellation method is not being executed (Step S310; NO), the false notification prevention unit 300 ends the emergency notification button switching process.

[0089] Step S320: The valid condition determination unit 303 starts timing. The valid condition determination unit 303 outputs a signal for starting timing to the timer unit 26. When the timer unit 26 acquires the signal, it starts timing.

[0090] Step S330: The valid condition determination unit 303 determines whether the emergency notification button 2 has been pressed. The valid condition determination unit 303 determines that the emergency notification button 2 has been pressed when it acquires a signal indicating that the emergency notification button 2 has been pressed from the emergency notification reception unit 208.

[0091] If the valid condition determination unit 303 determines that the emergency notification button 2 has been pressed (Step S330; YES), it executes the process of Step S340. On the other hand, if the valid condition determination unit 303 determines that the emergency notification button 2 has not been pressed (Step S330; NO), it executes the process of Step S330 again.

[0092] Step S340: The valid condition determination unit 303 determines whether it is within a predetermined time since the start of timing. The valid condition determination unit 303 acquires the timing data F1 from the timing data acquisition unit 206. The valid condition determination unit 303 determines whether it is within a predetermined time since the start of timing based on the acquired timing data F1. Here, the predetermined time is, for example, 60 seconds.

[0093] When the valid condition determination unit 303 determines that it is within a predetermined time since the start of timing (Step S340; YES), the emergency call button control unit 302 executes the process of Step S350. On the other hand, when the valid condition determination unit 303 determines that it is not within a predetermined time since the start of timing (Step S340; NO), the valid condition determination unit 303 executes the process of Step S370.

[0094] Step S350: The emergency call button control unit 302 enables the emergency call button 2.

[0095] Step S360: The valid condition determination unit 303 initializes the time measured since the emergency call button 2 was pressed.

[0096] Step S370: The emergency call button control unit 302 disables the emergency call button 2. Then, the false call prevention processing unit 300 executes the process of Step S360. Thus, the false call prevention processing unit 300 ends the emergency call button switching process.

[0097] (Modification Example 2) Note that when the emergency call button control unit 302 is determined by the invalid condition determination unit 301 that the invalid condition is satisfied and the emergency call button 2 is pressed, the notification unit 2014 may be made to execute a notification to an external device after a predetermined time. The external device is, for example, the server 4. On the other hand, when the emergency call button control unit 302 is determined by the invalid condition determination unit 301 that the invalid condition is not satisfied, when the emergency call button 2 is pressed, the notification unit 2014 is immediately made to execute a notification to the external device.

[0098] When the invalidation condition is satisfied, even if the emergency notification button 2 is pressed, the emergency notification can be cancelled within a predetermined time until the emergency notification is executed. For example, even if the emergency notification button 2 is pressed due to an accidental operation or a child's prank, the user can cancel the emergency notification within a predetermined time. A method for cancelling the emergency notification is, for example, to continuously press (long-press) the emergency notification button 2 for a predetermined time or more. Also, a method for cancelling the emergency notification may be to press a cancellation button. In that case, the cancellation button is provided in the operation unit 27.

[0099] Further, even when it is determined by the invalidation condition determination unit 301 that the invalidation condition is satisfied, the emergency notification button control unit 302 may perform control to cause the notification unit 2014 to transmit a notification to the server 4 after a predetermined time when the emergency notification button 2 is pressed according to the traveling speed.

[0100] (Second Embodiment) Hereinafter, a second embodiment of the present invention will be described in detail with reference to FIGS. 8 and 9. In the above-described first embodiment, the case where an emergency notification is executed when the emergency notification button 2 is pressed has been described. In the present embodiment, a case where an emergency notification is executed when a drive recorder has a voice recognition function and a speech using a specific phrase is made will be described. The drive recorder according to the present embodiment is referred to as a drive recorder 1a. Note that the same components as those in the above-described first embodiment may be denoted by the same reference numerals, and the description of the same components and operations may be omitted.

[0101] [Configuration of Drive Recorder] FIG. 8 is a diagram showing an example of the functional configuration of the drive recorder 1a according to the present embodiment. The drive recorder 1a includes a control unit 20a, a speed acquisition unit 21, a vehicle signal acquisition unit 22, an impact detection unit 23, a position acquisition unit 24, a photographing unit 25, a timekeeping unit 26, an operation unit 27, an audio output unit 28, a display unit 29, a communication unit 210, a storage unit 211, and a sound collection unit 212a. Comparing the drive recorder 1a (FIG. 8) according to the present embodiment with the drive recorder 1 (FIG. 3) according to the first embodiment, the drive recorder 1a (FIG. 8) is different from the drive recorder 1 (FIG. 3) in that it includes a control unit 20a and a sound collection unit 212a.

[0102] The sound collection unit 212a collects the user's voice. As a result of the collection, the sound collection unit 212a generates voice data J1. The sound collection unit 212a includes the microphone 16 shown in FIG. 2.

[0103] Here, each functional unit included in the control unit 20a will be described. The control unit 20a includes an acquisition unit 200a, an operation reception unit 207, an impact detection processing unit 2011, an image recording unit 2012, a display control unit 2013, a notification unit 2014, and a false notification prevention processing unit 300a.

[0104] The acquisition unit 200a includes a speed data acquisition unit 201, a vehicle signal data acquisition unit 202, an impact detection data acquisition unit 203, a position information acquisition unit 204, a photographed image acquisition unit 205, a timekeeping data acquisition unit 206, and a voice data acquisition unit 2020a. The voice data acquisition unit 2020a acquires the voice data J1 from the sound collection unit 212a.

[0105] The false notification prevention processing unit 300a executes false notification prevention processing by voice recognition. The false notification prevention processing unit 300a includes an invalid condition determination unit 301, an emergency notification button control unit 302, a valid condition determination unit 303a, and a voice recognition emergency notification control unit 304a.

[0106] When the emergency call button 2 is invalid, the valid condition determination unit 303a determines whether the valid conditions are satisfied by voice recognition. In the present embodiment, the valid condition is that speech using a specific phrase is made. When the valid condition is determined by voice recognition, it is only necessary to identify the phrase, and it is not necessary to identify the subject of the voice.

[0107] The voice recognition emergency call control unit 304a controls the emergency call by voice recognition. The voice recognition emergency call control unit 304a causes the notification unit 2014 to execute an emergency call when the voice data J1 acquired by the voice data acquisition unit 2020a indicates a specific voice.

[0108] [Emergency call button switching process by voice recognition] FIG. 9 is a diagram showing an example of the emergency call button switching process according to the present embodiment. The emergency call button switching process shown in FIG. 9 is executed by the control unit 20a. The control unit 20a repeatedly executes the emergency call button switching process shown in FIG. 9, for example, while the power of the drive recorder 1a is on. At the start of the emergency call button switching process shown in FIG. 9, the emergency call is invalid. When the emergency call is invalid, the emergency call is not executed even if the emergency call keyword is spoken. On the other hand, when the emergency call is valid, the emergency call is executed when the emergency call keyword is spoken.

[0109] Step S410: The valid condition determination unit 303a determines whether a release keyword has been recognized within a predetermined time. The valid condition determination unit 303a acquires the voice data J1 from the voice data acquisition unit 2020a. The valid condition determination unit 303a determines that the release keyword has been recognized when the acquired voice data J1 indicates the release keyword. The release keyword is, for example, "KAISO".

[0110] When the valid condition determination unit 303a determines that the cancellation keyword has been recognized (step S410; YES), the false notification prevention processing unit 300a executes the processing of step S420. On the other hand, when the valid condition determination unit 303a determines that the cancellation keyword has not been recognized (step S410; NO), the false notification prevention processing unit 300a executes the processing of step S430.

[0111] Step S420: The voice recognition emergency notification control unit 304a enables the emergency notification. The voice recognition emergency notification control unit 304a acquires voice data J1 from the voice data acquisition unit 2020a. When the acquired voice data J1 indicates an emergency notification keyword, the voice recognition emergency notification control unit 304a determines that the emergency notification keyword has been recognized. The emergency notification keyword is, for example, "KIN KYUU TSUU HO U".

[0112] Step S430: The voice recognition emergency notification control unit 304a disables the emergency notification. With the above, the control unit 20a ends the emergency notification button switching process.

[0113] Note that before the emergency notification button switching process shown in FIG. 9 is started, processing for starting the voice recognition mode may be performed. In that case, the voice recognition emergency notification control unit 304a determines whether or not the voice recognition keyword has been recognized. The voice recognition emergency notification control unit 304a acquires voice data J1 from the voice data acquisition unit 2020a. When the acquired voice data J1 indicates the voice recognition keyword, the voice recognition emergency notification control unit 304a determines that the voice recognition keyword has been recognized. The voice recognition keyword is, for example, "HAI, DORAIBUREKODA". The voice recognition emergency notification control unit 304a starts the voice recognition mode. In the voice recognition mode, it is possible to enable the emergency notification by voice recognition.

[0114] Note that the emergency call button switching process shown in FIG. 9 may be omitted. That is, when an emergency call keyword is recognized, an emergency call may be immediately executed. Referring to FIG. 10 here, the emergency call process in which an emergency call is immediately executed when an emergency call keyword is recognized will be described. FIG. 10 is a diagram showing an example of an emergency call process by voice recognition according to the present embodiment.

[0115] Step S510: The voice recognition emergency call control unit 304a determines whether an emergency call keyword has been recognized. If the voice recognition emergency call control unit 304a determines that an emergency call keyword has been recognized (step S510; YES), it executes the process of step S520. On the other hand, if the voice recognition emergency call control unit 304a determines that an emergency call keyword has not been recognized (step S510; NO), the false call prevention processing unit 300a ends the emergency call process by voice recognition.

[0116] Step S520: The voice recognition emergency call control unit 304a causes the reporting unit 2014 to execute an emergency call. With the above, the control unit 20b ends the emergency call process by voice recognition.

[0117] Note that when an emergency call can be made using an emergency call keyword, the function of the emergency call by pressing the emergency call button 2 may be enabled or disabled.

[0118] Note that the voice recognition keyword, the cancellation keyword, or the emergency call keyword is preferably a keyword that is not accidentally uttered in daily conversation. From the viewpoint of operability in an emergency, the number of characters of the voice recognition keyword, the cancellation keyword, or the emergency call keyword is preferably about 10 characters at most. Also, the voice recognition keyword, the cancellation keyword, or the emergency call keyword may be preset at the time of manufacturing the drive recorder 1, or may be set or changed by the user after the drive recorder 1 starts to be used.

[0119] In the determination by voice recognition in each of the processes of step S410 shown in FIG. 9, step S420, and S510 shown in FIG. 10, the subject of the voice may be identified. For example, the user of the drive recorder 1 causes their own voice to be picked up by the microphone 16 and registers their voiceprint. The valid condition determination unit 303a and the voice recognition emergency notification control unit 304a determine whether the registered voiceprint matches the voiceprint indicated by the voice data J1 acquired from the voice data acquisition unit 2020a, along with the determination as to whether each keyword has been recognized.

[0120] (Third Embodiment) Hereinafter, a third embodiment of the present invention will be described in detail with reference to FIGS. 11 and 12. In the above-described second embodiment, the case where the drive recorder has a voice recognition function and a specific phrase is used for emergency notification has been described. In this embodiment, the case where the emergency notification button 2 is locked by a locking mechanism will be described. The drive recorder according to this embodiment is referred to as drive recorder 1b. Note that the same components as those in the above-described first embodiment may be denoted by the same reference numerals, and the description of the same components and operations may be omitted.

[0121] [Configuration of Drive Recorder] FIG. 11 is a diagram showing an example of the functional configuration of the drive recorder 1b according to this embodiment. The drive recorder 1b includes a control unit 20b, a speed acquisition unit 21, a vehicle signal acquisition unit 22, a shock detection unit 23, a position acquisition unit 24, a photographing unit 25, a timing unit 26, an operation unit 27b, a voice output unit 28, a display unit 29, a communication unit 210, a storage unit 211, and a sound collection unit 212a. Comparing the drive recorder 1b (FIG. 11) according to this embodiment with the drive recorder 1a (FIG. 8) according to the second embodiment, the drive recorder 1b (FIG. 11) is different from the drive recorder 1a (FIG. 8) in that it includes a control unit 20b and an operation unit 27b.

[0122] The operation unit 27b includes an emergency notification button 2, a lock mechanism 273b, and a menu operation button 272. The lock mechanism 273b locks the emergency notification button 2 when the emergency notification button 2 is invalid. Locking the emergency notification button 2 means suppressing the pressing of the emergency notification button 2. In the lock mechanism 273b, the state of locking the emergency notification button 2 and the state of releasing the lock are switched by electrical control by the control unit 20b. The lock mechanism 273b is, for example, a stopper member. Note that the lock mechanism 273b may be released by direct operation by the user, such as when the stopper member is removed. Also, the lock mechanism 273b may be released by an operation from the menu operation button 272. The menu operation button 272 is realized by, for example, a touch panel.

[0123] Here, each functional unit included in the control unit 20b will be described. The control unit 20b includes an acquisition unit 200a, an operation reception unit 207b, a shock detection processing unit 2011, an image recording unit 2012, a display control unit 2013, a notification unit 2014, and a false notification prevention processing unit 300b.

[0124] The operation reception unit 207b includes an emergency notification reception unit 208 and a menu operation reception unit 2010. Note that, from the configuration of the operation reception unit 207b, the release reception unit 209 provided in the operation reception unit 207 shown in FIG. 3 or FIG. 8 is omitted. This is because, as described above, the lock mechanism 273b is released by the control unit 20b.

[0125] The false notification prevention processing unit 300b includes an invalid condition determination unit 301, an emergency notification button control unit 302b, a valid condition determination unit 303a, and a voice recognition emergency notification control unit 304a. The emergency notification button control unit 302b controls the locking mechanism 273b. The emergency notification button control unit 302b may control the locking mechanism 273b based on voice recognition by the voice recognition emergency notification control unit 304a, or may control the locking mechanism 273b based on an operation from the menu operation button 272.

[0126] [Emergency Notification Button Switching Process by Combination of Voice Recognition and Locking Mechanism] FIG. 12 is a diagram showing an example of the emergency notification button switching process according to the present embodiment. The emergency notification button switching process shown in FIG. 12 is executed by the control unit 20b. The control unit 20b repeatedly executes the emergency notification button switching process, for example, while the power of the drive recorder 1b is on.

[0127] Also, at the start of the emergency notification button switching process by voice recognition shown in FIG. 12, the emergency notification button 2 is locked by the locking mechanism 273b. The locking is executed by the emergency notification button control unit 302b in the process of disabling the emergency notification button 2 in step S60 shown in FIG. 4.

[0128] Step S610: The emergency notification button control unit 302b determines whether the unlocking method is being executed. For example, when the voice data J1 acquired by the voice data acquisition unit 2020a indicates an unlock keyword for unlocking the locking mechanism 273b, the emergency notification button control unit 302b determines that the unlocking method is being executed. Also, when the menu operation reception unit 2010 receives an operation for unlocking the locking mechanism 273b, the emergency notification button control unit 302b determines that the unlocking method is being executed.

[0129] If the emergency notification button control unit 302b determines that the unlocking method is being executed (step S610; YES), it executes the process of step S620. On the other hand, if the emergency notification button control unit 302b determines that the unlocking method is not being executed (step S610; NO), the emergency notification button control unit 302 executes the process of step S630.

[0130] Step S620: The emergency call button control unit 302b releases the locking mechanism 273b. Step S630: The emergency call button control unit 302b locks the emergency call button 2 by the locking mechanism 273b. With the above, the control unit 20b ends the emergency call button switching process.

[0131] In addition, in each of the above-described embodiments, after the emergency call button control unit 302 invalidates the emergency call button 2 when it is determined by the invalid condition determination unit 301 that the invalid condition is satisfied, when it is determined by the valid condition determination unit 303 that the valid condition is satisfied, an example of enabling the emergency call button 2 has been described, but it is not limited thereto. When it is determined by the invalid condition determination unit 301 that the invalid condition is satisfied, the emergency call button control unit 302 may leave the emergency call button 2 invalid. In this case, for example, when the vehicle 3 is parked, the emergency call button 2 becomes invalid.

[0132] In addition, the control unit 20 may be provided as a function of a device mounted on a vehicle 3 of a type other than a drive recorder. The device is, for example, a car navigation device. Alternatively, the control unit 20 may be mounted on the vehicle 3 as a vehicle emergency call device specialized for emergency calls.

[0133] As described above, the vehicle emergency call device according to each of the above-described embodiments (in each of the above-described embodiments, the drive recorders 1, 1a, 1b) includes an invalid condition determination unit 301 and emergency call button control units 302, 302b. The invalid condition determination unit 301 determines whether at least one of the invalid conditions, that is, no impact applied to the vehicle 3 is detected within a predetermined time or it is within a predetermined time from ignition on, is satisfied. When it is determined by the invalid condition determination unit 301 that the invalid condition is satisfied, the emergency call button control units 302, 302b invalidate the emergency call button 2 mounted on the vehicle 3.

[0134] With this configuration, in the vehicle emergency notification device according to each of the above-described embodiments (in each of the above-described embodiments, the drive recorders 1, 1a, 1b), when invalid conditions such as during parking are satisfied, the emergency notification button 2 can be disabled. Therefore, when emergency notification is not required, false notification can be suppressed.

[0135] In the prior art, when some trouble such as reckless driving or poor physical condition occurs, when the user presses the emergency notification button, a notification from the drive recorder is transmitted to an external server. However, in some cases, the notification may be transmitted immediately by a one-touch operation of pressing the emergency notification button. In the prior art, even when it is pressed by a child's prank, the notification is transmitted, resulting in an increase in unnecessary communication volume and an increase in unnecessary server load, which has been a problem. On the other hand, in the vehicle emergency notification device according to each of the above-described embodiments, when invalid conditions such as during parking are satisfied, even if the emergency notification button 2 is pressed, the notification is not transmitted.

[0136] Also, in the vehicle emergency notification device according to each of the above-described embodiments (in each of the above-described embodiments, the drive recorders 1, 1a, 1b), the invalid condition determination unit 301 determines that the invalid condition is satisfied when the device is operated by the user (in each of the above-described embodiments, when the menu operation button 272 is operated).

[0137] With this configuration, in the vehicle emergency notification device according to each of the above-described embodiments (in each of the above-described embodiments, the drive recorders 1, 1a, 1b), during the menu operation, even if the emergency notification button 2 is pressed, the notification is not transmitted. Therefore, it is possible to prevent the vehicle body of the vehicle 3 from shaking during the menu operation and accidentally pressing the emergency notification button 2.

[0138] Also, the vehicle emergency notification device according to each of the above-described embodiments (in each of the above-described embodiments, the drive recorders 1, 1a, 1b) further includes valid condition determination units 303, 303a. The validity condition determination units 303 and 303a are the validity condition determination units 303 and 303a that determine at least one or more validity conditions among the following conditions (a), (b), (c), and (d) when the emergency call button 2 is invalid: (a) Utterance using a specific phrase (in the second embodiment, the release keyword); (b) A predetermined physical operation (in the first embodiment, continuously pressing the release button 271) is performed; (c) A predetermined operation is performed on a software-implemented button; (d) A specific object or gesture is photographed within the angle of view of the photographing unit 25; The emergency call button control units 302 and 302b enable the emergency call button 2 when it is determined by the validity condition determination units 303 and 303a that at least one or more conditions are satisfied.

[0139] With this configuration, in the vehicle emergency call device according to each of the above-described embodiments (in each of the above-described embodiments, the drive recorders 1, 1a, and 1b), even when the emergency call button 2 is invalid, if a validity condition such as pressing the release button 271 is satisfied, the emergency call button 2 can be enabled. Therefore, false calls can be suppressed when an emergency call is not necessary, and an emergency call can be executed when necessary. In other words, the vehicle emergency call device according to each of the above-described embodiments performs an emergency call in a two-step procedure.

[0140] Note that, a part of the drive recorders 1, 1a, and 1b in the above-described embodiments, for example, the false notification prevention processing units 300, 300a, and 300b may be realized by a computer. In that case, a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to be realized. Here, the "computer system" refers to a computer system built in the drive recorders 1, 1a, and 1b, including hardware such as an OS and peripheral devices. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built in a computer system. Furthermore, the "computer-readable recording medium" also includes a medium that holds a program dynamically for a short time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and a volatile memory inside a computer system that becomes a server or a client in that case and holds a program for a certain period of time. Also, the above program may be for realizing a part of the aforementioned functions, and may further be realized in combination with a program already recorded in the computer system for realizing the aforementioned functions. Also, a part or all of the drive recorders 1, 1a, and 1b in the above-described embodiments may be realized as an integrated circuit such as an LSI (Large Scale Integration). Each functional block of the drive recorders 1, 1a, and 1b may be made into a processor individually, or a part or all of them may be integrated and made into a processor. Also, the method of integrating into an integrated circuit is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Further, when a technology for integrating into an integrated circuit that replaces LSI appears due to the progress of semiconductor technology, an integrated circuit using that technology may be used.

[0141] The above has described in detail an embodiment of the present invention with reference to the drawings. However, the specific configuration is not limited to the above, and various design changes and the like can be made without departing from the gist of the present invention.

Explanation of Reference Signs

[0142] 1, 1a, 1b... drive recorder, 2... emergency notification button, 3... vehicle, 301... invalid condition determination unit, 302, 302b... emergency notification button control unit

Claims

An invalid condition determination unit that determines whether at least one of the following invalid conditions is satisfied: no impact applied to the vehicle has been detected within a predetermined time counted backward from the current time when it is determined that the vehicle is not running, or the current time is within a predetermined time from when the ignition is turned on; An emergency call button control unit that invalidates the emergency call button mounted on the vehicle when it is determined by the invalid condition determination unit that the invalid condition is satisfied; A vehicle emergency notification device comprising the above.

2. When the invalid condition determination unit is in the middle of a menu operation by the user, it determines that the invalid condition is satisfied The vehicle emergency notification device according to claim 1.

3. When the emergency call button is invalid, a valid condition determination unit that determines at least one of the following valid conditions: (a) utterance using a specific phrase is made; (b) a predetermined physical operation is performed; (c) a predetermined operation is performed on a software-implemented button; (d) a specific object or gesture is photographed within the angle of view of the photographing unit; Further comprising: When it is determined by the valid condition determination unit that at least one of the above conditions is satisfied, the emergency call button control unit validates the emergency call button The vehicle emergency notification device according to claim 1 or claim 2.

4. When it is determined by the invalid condition determination unit that the invalid condition is satisfied and the emergency call button is pressed, the emergency call button control unit causes the reporting unit to execute a report to an external device after a predetermined time The vehicle emergency notification device according to any one of claims 1 to 3. Invalidation condition determination step of determining whether at least one of the invalidation conditions is satisfied, where no impact applied to the vehicle within a predetermined time backward from the current time determined that the vehicle is not in motion, or the current time is within a predetermined time from ignition on, and Emergency call button control step of invalidating the emergency call button mounted on the vehicle when it is determined by the invalidation condition determination step that the invalidation condition is satisfied, and An emergency call method for a vehicle having the above.

6. On a computer, Invalidation condition determination step of determining whether at least one of the invalidation conditions is satisfied, where no impact applied to the vehicle within a predetermined time backward from the current time determined that the vehicle is not in motion, or the current time is within a predetermined time from ignition on, and Emergency call button control step of invalidating the emergency call button mounted on the vehicle when it is determined by the invalidation condition determination step that the invalidation condition is satisfied, and A program for causing the above to be executed.

Images