JP2011123720A - Driving recorder - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a driving recorder capable of suitably preventing driving condition data from being overwritten. <P>SOLUTION: The driving recorder includes: a data collection part for collecting driving condition data of a vehicle; a storage part for storing the driving condition data in a non-volatile manner; an operation part for receiving user operation; and a control part for comprehensively controlling respective function parts. In the storage part, an upper limit is set in the number of files of driving condition data allowed to be stored in a non-volatile manner, and if a new driving condition data file is further stored in a non-volatile manner after the number of files of operation condition data stored in the non-volatile manner reaches the upper limit, the oldest driving condition data file is overwritten. When the operation part receives a prescribed overwrite prohibition operation, the control part applies an overwrite prohibition attribute to a driving condition data file being stored at present or a driving condition data file stored immediately before. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a drive recorder that records vehicle driving situation data (video data, traveling data, etc.) when a traffic accident occurs or during dangerous driving.

  In recent years, the number of cases in which a drive recorder is mounted on a vehicle is increasing as a means that can contribute to suppression of traffic accidents and post-mortem analysis.

  As an example of the related art related to the above, Patent Document 1 can be cited.

JP 2008-52230 A

  Certainly, if the above-mentioned conventional drive recorder is installed in the vehicle, you will not like to record your own responsible traffic accidents and dangerous driving, and the driver will always try to drive safely. It becomes possible to contribute to. In the unlikely event that a driver who is not liable for negligence is involved in a traffic accident, the driver's legitimacy can be verified by performing a post-analysis of the driving situation data recorded in the drive recorder. It becomes possible.

  However, in the conventional drive recorder, there is an upper limit on the number of files of operation status data that can be stored in a nonvolatile manner according to the capacity of the storage unit, and the number of files of operation status data stored in a nonvolatile manner is When a new operation status data file is stored in a non-volatile manner after reaching the upper limit, the oldest operation status data file will be overwritten. Even if the driving situation data is not correct, there is a problem that any of them will be overwritten with a new file and cannot be used anymore.

  For example, since a minor contact accident occurred while driving a car, the driving situation data was stored in a non-volatile manner by manual operation just in case, but at that point, there seems to be no particular problem for either myself or the other party. However, I did not negotiate after confirming the driving situation data stored in a nonvolatile manner, but later discovered that the vehicle was damaged and wanted to seek compensation from the other party. May be required to compensate. In such a case, if you can check the driving situation data at the time of the accident, it is possible to negotiate properly with the other party, but the driving situation data at the time of the accident overwrites the new file If it was, it could no longer be confirmed.

  In view of the above-described problems, an object of the present invention is to provide a drive recorder that can appropriately prevent overwriting of driving situation data.

  In order to achieve the above object, a drive recorder according to the present invention includes a data collection unit that collects vehicle driving situation data, a storage unit that stores the driving situation data in a nonvolatile manner, and an operation unit that receives a user operation. And a control unit that comprehensively controls each of these functional units, and the storage unit has an upper limit on the number of files of operation status data that can be stored in a nonvolatile manner, When the number of operating status data files stored in a non-volatile manner reaches the upper limit, if new operating status data files are stored in a non-volatile manner, the oldest operating status data file is overwritten. When the predetermined overwriting prohibition operation is accepted by the operation unit, the control unit is a file of driving status data that is currently being stored, or most recently And is configured as (first configuration) which imparts a file to overwrite prohibition attribute of paid has been the driving condition data.

  In the drive recorder having the first configuration, the control unit stores the operation status data in the storage unit when it is determined that a predetermined nonvolatile storage condition is satisfied (second configuration). It is good to make it.

  In the drive recorder having the second configuration, the reception period of the overwrite prohibition operation is limited to a period from when the predetermined nonvolatile storage condition is satisfied to when the predetermined reception end condition is satisfied. (3rd configuration).

  Further, in the drive recorder having the third configuration, the predetermined reception end condition requires that one driving situation data is stored in a nonvolatile manner and then another driving situation data is stored in a nonvolatile manner. That the predetermined time has elapsed since the predetermined nonvolatile storage condition is satisfied, that the power supply to the drive recorder has been cut off, or that the storage processing for one operating status data is stored in the storage unit It is good to set it as the structure (4th structure) which is at least any one of having completed.

  The drive recorder having the third or fourth configuration may have a configuration (fifth configuration) having a notification unit that notifies that the overwrite prohibition operation is being accepted.

  In the drive recorder having the fifth configuration, the notification unit is lit or flashed during a reception period of the overwriting prohibiting operation or during the storage process of the driving status data, or a microphone that performs a predetermined voice announcement. (6th configuration).

  Further, in the drive recorder having any one of the first to sixth configurations, the operation unit includes a manual storage button for allowing a user to store the driving situation data in the storage unit at an arbitrary timing. The control unit determines that the overwrite prohibition operation has been accepted when the operation unit detects that the manual storage button is pressed while the operation status data is being stored. A configuration (seventh configuration) is preferable.

  Further, in the drive recorder having any one of the first to sixth configurations, the operation unit may be a file of driving status data that is currently being stored by the user at an arbitrary timing, or an operation stored most recently. An overwrite prohibiting button for giving an overwrite prohibiting attribute to the status data file is provided, and the control unit accepts the overwrite prohibiting operation when the pressing of the overwrite prohibiting button is detected. It is good to make it the structure (8th structure) determined to have met.

  With the drive recorder according to the present invention, it is possible to appropriately prevent overwriting of operation status data.

The block diagram which shows one Embodiment of the traffic information system using the drive recorder which concerns on this invention Flow chart of operations executed by drive recorder (conditional storage specification) Flow chart of operation executed by drive recorder (constant storage specification) Schematic diagram for explaining information sharing service related to traffic accidents Time chart showing an example of the driving situation Table showing an example of driving status data Flowchart showing operation of prohibiting overwriting of operation status data stored in a nonvolatile manner

  FIG. 1 is a block diagram showing an embodiment of a traffic information system using a drive recorder according to the present invention.

  As shown in FIG. 1, the traffic information system of the present embodiment includes a drive recorder 1, a mobile phone terminal 2, an electronic control unit 3 (hereinafter referred to as ECU [Electric Control Unit] 3), an in-vehicle sensor 4, The mobile phone line 5 and the server 6 are provided.

  The drive recorder 1 is means for recording vehicle driving situation data (video data, traveling data, etc.) when a traffic accident occurs or during dangerous driving. The configuration and operation of the drive recorder 1 will be described in detail later.

  The mobile phone terminal 2 is brought into the vehicle interior by the driver (or passenger) of the vehicle. In addition to the basic function of performing wireless communication and communication through the mobile phone line 5, the drive recorder 1 Additional function to perform wired or wireless mutual communication with the. The cooperative operation between the drive recorder 1 and the mobile phone terminal 2 will be described in detail later.

  The ECU 3 is a means that is mounted on the vehicle and controls the operation of each part of the vehicle. From the ECU 3 to the drive recorder 1, operation state data (lamps (headlamps) of each part of the vehicle is provided as an element constituting the driving status data of the vehicle. Lighting state data, door lock opening / closing state data, side mirror opening / closing state data, wiper driving state data, power window driving state data, airbag driving state data, ABS [Antilock Brake System] drive status data, etc.) are transmitted.

  The in-vehicle sensor 4 is a means that is mounted on the vehicle and detects the situation of each part of the vehicle and the surroundings of the vehicle. A yaw rate sensor that detects the rotation speed of the vehicle, a vehicle speed sensor that detects the traveling speed of the vehicle, a wheel speed sensor that detects the rotational speed of the wheels (tires), a steering angle sensor that detects the steering angle of the steering, and a steering torque of the steering Steering torque sensor to detect, brake pedal sensor to detect the degree of depression of the brake pedal, hydraulic sensor to detect the oil pressure of each part of the vehicle, air pressure sensor to detect the tire air pressure, temperature sensor to detect the outside air temperature and the inside air temperature, ambient brightness An illuminance sensor that detects the road surface, a road surface sensor that detects the road surface condition, and an inter-vehicle distance sensor that detects the inter-vehicle distance before and after the vehicle. Sa, obstacle sensor (corner sensor) for detecting an obstacle around the vehicle, and can include a collision sensor for detecting a collision occurring to the vehicle. Note that the various detection data described above are transmitted from the in-vehicle sensor 4 to the drive recorder 1 as elements constituting the driving situation data of the vehicle.

  The mobile phone line 5 is a public line to which the mobile phone terminal 2 is connected, and is provided by a communication carrier.

  The server 6 is means for communicating with the mobile phone terminal 2 via the mobile phone line 5 and is installed in the police, an insurance company, or the like.

  Next, the configuration and operation of the drive recorder 1 will be described in detail. As shown in FIG. 1, the drive recorder 1 includes a control unit 101, an imaging unit 102, a GPS [Global Positioning System] receiving unit 103, an acceleration sensor 104, an interface unit 105, and a real time clock 106 (hereinafter referred to as “real time clock”). RTC [Real Time Clock] 106), a storage unit 107, a communication unit 108, an operation unit 109, and a warning unit 110.

  The control unit 101 is a means for comprehensively controlling each of the functional units 102 to 110 constituting the drive recorder 1, and besides a CPU [Central Processing Unit], a ROM [Read Only Memory] and a RAM [Random Access]. Memory] or the like (both not shown). The ROM is used as a storage area for programs executed by the CPU. In addition to being used as a work area for the CPU, the RAM is also used as a buffer area for temporarily storing the driving status data of the vehicle for a predetermined time (several seconds to several minutes). The operation of the control unit 101 will be described in detail later.

  The imaging unit 102 is a camera unit that always captures moving images around the vehicle (at least in front of the vehicle), and performs predetermined image processing (analog / digital conversion processing, noise removal processing, color correction processing, image compression processing) on the obtained video data. Etc.) and output to the control unit 101 (none is shown). Note that a CCD [Charge Coupled Devices] or a CMOS [Complementary Metal Oxide Semiconductor] may be used as a photoelectric conversion element constituting the camera unit. Further, it is desirable that the imaging unit 102 be attached to a position (such as the rear surface of the rearview mirror) that can appropriately capture a moving image of the situation in front of the vehicle and does not hinder the driver's field of view. As described above, by including video data obtained by taking a moving image of the periphery of the vehicle as an element constituting the driving situation data of the vehicle, it becomes possible to quickly and appropriately investigate the cause of the traffic accident.

  In the present embodiment, the configuration in which moving image shooting is always performed around the vehicle is taken as an example, but the configuration of the present invention is not limited to this, for example, moving image shooting intermittently at a predetermined interval, or It may be configured to perform still image shooting. With such a configuration, the storage capacity of the RAM and the storage unit 107 mounted on the control unit 101 can be suppressed.

  The GPS receiving unit 103 is a unit that outputs vehicle position data indicating the current position (latitude, longitude, altitude) of the vehicle to the control unit 101 using a satellite signal from a GPS satellite. As described above, by including the vehicle position data as an element constituting the driving situation data of the vehicle, it is possible to perform a post-analysis of the travel route leading to the occurrence of the traffic accident.

  The acceleration sensor 104 detects accelerations in three orthogonal directions (X-axis direction (= vehicle traveling direction), Y-axis direction (= horizontal direction of the vehicle), and Z-axis direction (= vertical direction of the vehicle)). This is means for outputting this as acceleration data to the control unit 101. As a method for detecting acceleration data, a piezoresistive method or a capacitance method can be used. As described above, by including acceleration data indicating the acceleration of the vehicle as an element constituting the driving situation data of the vehicle, it is possible to perform a post-analysis of the impact of the vehicle that has occurred during a traffic accident.

  The interface unit 105 is a unit that outputs operation state data of each part of the vehicle input from the ECU 3 mounted on the vehicle and various detection data input from the in-vehicle sensor 4 to the control unit 101. Thus, not only the information obtained by the main body of the drive recorder 1 but also the existing equipment mounted on the vehicle itself (such as the ECU 3 and the in-vehicle sensor 4) as elements constituting the driving situation data of the vehicle. ), It is possible to collect a large amount of operation status data without increasing the size and cost of the drive recorder 1.

  The RTC 106 is means for generating time data related to date and time and outputting the time data to the control unit 101. As described above, by including the date and time as elements constituting the driving situation data of the vehicle, it becomes possible to perform a post-mortem analysis of the time elapsed until the occurrence of the traffic accident.

  As described above, in the drive recorder 1 of the present embodiment, the imaging unit 102, the GPS receiving unit 103, the acceleration sensor 104, the interface unit 105, and the RTC 106 are all time-sequential vehicle driving situation data. It functions as a data collection unit that collects data. However, the configuration of the present invention is not limited to this. For example, the GPS receiver 103 and the acceleration sensor 104 mounted on the main body of the drive recorder 1 may be externally connected to the drive recorder 1. A part of the in-vehicle sensor 4 provided outside the recorder 1 may be incorporated in the main body of the drive recorder 1.

  The storage unit 107 is a means for storing the operation status data buffered by the control unit 101 in a non-volatile manner when a predetermined trigger condition (described later in detail) is satisfied, and is a flash memory or an EEPROM [Electrically Erasable and A semiconductor memory such as Programmable Read Only Memory] or a mass storage device such as a hard disk drive can be used. The storage unit 107 may be configured to be attachable / detachable to / from the drive recorder 1 with priority given to the portability of the driving situation data, or conversely, may be configured to be non-detachable with priority given to preventing falsification of the driving situation data. . Further, the content of the driving situation data stored in the storage unit 107 is not limited to the above, and may be configured to store all data input to the control unit 101 with priority on enhancement of the post-mortem analysis. On the contrary, a configuration may be adopted in which only part of the data input to the control unit 101 is stored with priority given to the capacity reduction of the storage unit 107. Further, the storage unit 107 may be configured to encrypt and store the above-described driving situation data in order to prevent unauthorized copying of the driving situation data.

  The communication unit 108 is means for performing wired or wireless mutual communication with the mobile phone terminal 2. When the drive recorder 1 and the mobile phone terminal 2 are connected by wire, a USB communication port, a UART (Universal Asynchronous Receiver Transmitter) communication port, or the like may be used. When the drive recorder 1 and the mobile phone terminal 2 are wirelessly connected, an infrared communication port (IrDA [Infrared Data Association] communication port) or a wireless LAN [Local Area Network] communication port (Wi-Fi communication port) is used. ) Or a Bluetooth (registered trademark) communication port. That is, the communication unit 108 is configured to perform mutual communication with the mobile phone terminal 2 via a general-purpose communication port installed in the mobile phone terminal 2. With such a configuration, mutual communication between the drive recorder 1 and the mobile phone terminal 2 can be realized without requesting addition or change of hardware on the mobile phone terminal 2 side.

  The operation unit 109 is a means for accepting user operations, and is configured using buttons, switches, touch panels, and the like.

  The warning unit 110 is a unit that issues a warning based on an instruction from the control unit 101 so as to refrain from dangerous driving. Note that the above warning may be performed by voice or video (or a combination thereof). If it is the structure which issues such a warning, since a driver will always try safe driving | running | working, it becomes possible to contribute to suppression of a traffic accident. The control unit 101 starts the vehicle suddenly, suddenly handles, suddenly brakes, sudden shift changes, no lights at night, lane change without operation of the direction indicator, meandering, sudden approach to surrounding vehicles and structures. Is detected, the warning unit 110 is instructed to issue the above warning. The warning unit 110 is also used as a means for alerting the driver when providing a service for sharing information related to a traffic accident, which will be described later.

  Next, the operation of storing operation status data by the control unit 101 will be described in detail. When the acceleration of the vehicle detected by the acceleration sensor 104 exceeds a predetermined threshold (when an impact exceeding a predetermined threshold is applied to the vehicle) or when a predetermined user operation ( When a request from the mobile phone terminal 2 is received via the communication unit 108, or when a warning by the warning unit 110 is determined to be necessary. It is determined that the trigger condition (non-volatile storage condition) is satisfied, and the storage unit 107 is controlled to store the operation status data. Here, the driving situation data stored in the storage unit 107 is the driving situation data temporarily stored in the RAM of the control unit 101 during a predetermined period (several seconds to several minutes) before and after the above-described trigger condition is satisfied. It is.

  In this way, if the drive recorder 1 is mounted on the vehicle, the driver refrains from recording a self-responsible traffic accident or dangerous driving, and the driver always tries to drive safely. It is possible to contribute. Also, in the unlikely event that a driver who is not liable for negligence is involved in a traffic accident, the driver's legitimacy can be verified by performing a post-analysis of the driving situation data recorded in the drive recorder 1. Is also possible.

  Next, the cooperative operation between the drive recorder 1 and the mobile phone terminal 2 by the control unit 101 will be described in detail.

  As described above, the drive recorder 1 according to the present embodiment includes the communication unit 108 that performs wired or wireless communication with the mobile phone terminal 2, and the control unit 101 includes the communication unit 108. By controlling the operation setting data for setting the operation status of the drive recorder 1 and the operation status data described above with the mobile phone terminal 2 (for example, traffic accidents and dangerous driving are performed based on the current operation status data). It is configured to transmit / receive a trigger condition for determining whether or not it has occurred and firmware executed by the control unit 101.

  By adopting such a configuration, the mobile phone terminal 2 having an overwhelmingly high penetration rate compared to personal computers is used to view the driving status data recorded in the drive recorder 1 and to confirm / change the operation settings. Therefore, it is possible to provide the drive recorder 1 that is highly convenient for the user.

  For example, when the driver encounters a traffic accident, the driver can browse the driving situation data stored in the drive recorder 1 using his / her mobile phone terminal 2 without delay, so that the police or insurance company can It is possible to report the current situation quickly and accurately.

  Even if you are involved in a traffic accident where the other party is present, you can negotiate and negotiate the negligence ratio of both parties while browsing the driving situation data recorded on the drive recorder 1 on the spot. There is no need to be overwhelmed by the unilateral claims. In addition, since it is difficult for the other party with a high negligence ratio to make an unfair claim for compensation, it is possible to improve traffic manners and to contribute to the suppression of camouflaged traffic accidents caused by hits.

  Further, in the drive recorder 1 of the present embodiment, when the control unit 101 determines that the above-described trigger condition is satisfied, the control unit 101 controls the storage unit 107 to store the operation status data and also controls the communication unit 108. Thus, the driving status data is automatically transmitted to the mobile phone terminal 2. By adopting such a configuration, the driving situation data recorded in the drive recorder 1 is automatically sent to the mobile phone terminal 2 without requiring any operation by the driver, so that it can be easily viewed. Is possible.

  Further, the mobile phone terminal 2 of the present embodiment has a transfer function unit (not shown) for transferring the operation status data from the drive recorder 1 to a predetermined server 6 via the mobile phone line 5. It is set as the structure which consists of. By adopting such a configuration, when a traffic accident occurs, the mobile phone terminal 2 will report the situation of the traffic accident to the police or insurance company itself, so that the driver may be unconscious or injured. Even if it is in a state, the report can be completed without delay. It also leads to prevention of falsification of driving status data.

  In addition, the mobile phone terminal 2 of the present embodiment includes a transmission request function unit (not shown) that requests the drive recorder 1 to transmit operating status data when a predetermined user operation is accepted. Has been. With such a configuration, the mobile phone terminal 2 can be used as if it were a remote controller of the drive recorder 1.

  In addition, the mobile phone terminal 2 of the present embodiment is configured to include a transmission request function unit (not shown) that requests the drive recorder 1 to transmit operating status data in response to a request from the server 6. ing.

  For example, the server 6 recognizing that a traffic accident has occurred at a certain point, with respect to an unspecified number of mobile phone terminals 2 existing in the base station area near the accident site, the accident occurrence time and the location information of the accident site. And requesting to transfer the driving situation data recorded by the drive recorder 1 linked to each of them. The mobile phone terminal 2 that has received this transfer request requests the drive recorder 1 to transmit operating status data, and transfers the operating status data received from the drive recorder 1 to the server 6 via the mobile phone line 5.

  If such a traffic information system is constructed, the information collection capability of the server 6 can be increased, and the post-mortem analysis of the traffic accident can be performed more accurately.

  However, prior to the above transfer, the transfer function unit of the mobile phone terminal 2 analyzes the time data and vehicle position data included in the driving situation data, the accident occurrence time and the accident site position information received from the server 6. When it is determined that the driving situation data recorded in the drive recorder 1 is likely to be useful during the post-mortem analysis of the traffic accident, in other words, the possibility of the traffic accident being recorded in the drive recorder 1 is high. Only when it is determined that it is determined that it is transferred to the server 6. With such a configuration, unnecessary communication traffic on the mobile phone line 5 can be reduced, and post-mortem analysis of traffic accidents can be facilitated.

  In addition, the transmission request function unit and the transfer function unit of the mobile phone terminal 2 are special function units that are necessary only for the cooperation with the drive recorder 1 and the construction of the traffic information system. Therefore, as a means for realizing these functional units, an arithmetic processing unit (not shown) that installs a predetermined program in the mobile phone terminal 2 and executes it is not added to the hardware necessary for this. It is desirable to function as a transmission request function unit and a transfer function unit in software. By adopting such a configuration, it is possible to realize the cooperation between the drive recorder 1 and the mobile phone terminal 2 and the construction of the above traffic system without requiring the mobile phone terminal 2 to add or change hardware. It becomes.

  The above-described drive recorder 1 can be said to be a specification in which the operation status data is stored in the storage unit 107 in a nonvolatile manner when the trigger condition is satisfied (hereinafter referred to as “conditional storage specification” for convenience). . The outline of the operation executed in the conditional storage specification drive recorder 1 is as shown in the flowchart of FIG.

  That is, the drive recorder 1 collects the operation status data and temporarily stores it in a buffer (such as the RAM of the control unit 101) (step S11), monitors whether the trigger condition is satisfied (step S12), and The operation (step S13) for monitoring whether or not there is a request for transmission of driving status data from the mobile phone terminal 2 is continuously executed.

  When the trigger condition is satisfied (Y in step S12), the drive recorder 1 stores the driving situation data stored in the buffer in the storage unit 107 in a nonvolatile manner (step S14), and the driving situation. Data is transmitted to the mobile phone terminal 2 (step S15). Further, when there is a request for transmission of driving situation data from the mobile phone terminal 2 (Y in step S13), the drive recorder 1 sends the driving situation data to the mobile phone terminal 2 (step S15). After the transmission, the process returns to step S11.

  According to the drive recorder 1 of the “conditional storage specification” described above, it is possible to store the operation status data in the storage unit 107 efficiently (only when the trigger condition is satisfied). Therefore, it is possible to suppress as much as possible the processing burden for recording the driving situation data and the increase in the storage capacity of the storage unit 107.

  On the other hand, if the specification of the drive recorder 1 is a specification in which the operation status data is continuously stored in the storage unit 107 (that is, in a nonvolatile manner) (hereinafter referred to as “always stored specification” for convenience), It is possible to prevent as much as possible the omission of operating status data due to the cause. Therefore, the post-mortem analysis regarding the cause of the accident and the like is easier than in the case where the drive recorder 1 has the “conditional storage specification”.

  For example, when a person or a bicycle touches the vehicle very lightly, the impact received by the vehicle at that time is too small, and the trigger condition may not be satisfied (the detection value of the acceleration sensor does not exceed a predetermined threshold). In this case, according to the drive recorder 1 of the conditional storage specification, the operation status data at the time when the contact occurs is not stored in the storage unit 107. Therefore, it is usually difficult to confirm the operation status data afterwards.

  However, according to the drive recorder 1 of the always storing specification, since the operation status data at the time when the contact occurs is also stored in the storage unit 107, the operation status data can be confirmed afterwards. As a result, the operation status data can be used for post-mortem analysis such as the cause of an accident. For example, when a failure of various sensors occurs, an abnormality may occur in the determination of the trigger condition (thus, even if the trigger condition is satisfied, it is not determined that the trigger condition is satisfied). I can't deny it. Even in such a situation, according to the drive recorder 1 of the constant storage specification, it is possible to prevent the recording of the operation status data from being missed.

  When the drive recorder 1 is always stored, the operation status data is continuously collected and temporarily stored in a buffer (such as the RAM of the control unit 101) and the trigger condition is satisfied. Regardless of whether or not it has been done, all of the temporarily stored operation status data may be transferred to and stored in the storage unit 107. In addition, when the drive recorder 1 is always stored, the operation status data collected continuously at all times may be directly stored in the storage unit 107 without using a buffer. In any case, during the operation of the drive recorder 1 (for example, when the power switch of the drive recorder 1 is on), the operation status data is continuously collected and stored in the storage unit 107 in a non-volatile manner. Stored in

  In the storage process of the driving situation data in the storage unit 107, for example, when the storage area of the driving situation data in the storage unit 107 is saturated, new data is overwritten in the oldest data storage area. It may be. In this way, a shortage of the storage area for the driving situation data can be avoided, and new data with high importance can be preferentially left.

  Moreover, in the drive recorder 1 of the constant storage specification, the operation of storing the operation status data in the storage unit 107 is basically performed continuously at all times, but means for stopping the operation just in case ( For example, a switch for stopping the operation may be provided. Further, only some types of operation status data may be always stored in the storage unit 107.

  For example, only the video data acquired by the imaging unit 102 among the driving status data is always stored in the storage unit 107, and the other driving status data is set when the trigger condition is satisfied. However, it may be stored in the storage unit 107 only. According to such a configuration, it is possible to prevent an image from being missed when the trigger condition is not satisfied, and to suppress an increase in processing load related to data storage in the storage unit 107 as much as possible. Become.

  Note that the imaging unit 102 may acquire video data inside the vehicle instead of the video data around the vehicle or in addition to the video data around the vehicle. In this way, video data inside the vehicle can be stored in the storage unit 107. As a result, for example, even if a trouble occurs between a driver and a customer in a taxi car, this situation can be confirmed afterwards. In the imaging unit 102, a plurality of camera units (imaging devices) are installed inside and outside the vehicle, and images around and inside the vehicle can be acquired from various positions and angles. Also good.

  The outline of the operation executed in the drive recorder 1 of the always stored specification is as shown in the flowchart of FIG.

  That is, the drive recorder 1 collects operation status data and stores it in the storage unit 107 in a nonvolatile manner (step S21), an operation for monitoring whether the trigger condition is satisfied (step S22), and the mobile phone terminal 2. The operation (step S23) for monitoring whether or not there is a request for transmission of the operation status data is continuously executed.

  Then, when the trigger condition is satisfied (Y in step S22) or when there is a request for transmission of the driving situation data from the mobile phone terminal 2 (Y in step S23), the drive recorder 1 stores the driving situation data. It transmits to the mobile phone terminal 2 (step S24). After the transmission, the process returns to step S21.

  Note that the specification of the drive recorder 1 may be set (switchable) to either the conditional storage specification or the constant storage specification in accordance with a user instruction (operation of the operation unit 109 or the like), for example. Absent. In this way, the convenience of the drive recorder 1 can be further improved. Moreover, as the driving situation data handled in the drive recorder 1, in addition to what has been specifically shown above, the driving situation data (for example, whether or not the vehicle is driven, how it is driven, etc.) It is possible to employ various data indicating the above.

  As described above, the drive recorder 1 of the always-storing specification is connected between the mobile phone terminal 2 and a functional unit (data collection / storage unit) that collects and stores the driving state data of the vehicle in a non-volatile manner. It comprises a functional unit (communication unit) that performs mutual communication by radio and a functional unit (control unit) that comprehensively controls these functional units, and the control unit is connected to the mobile phone terminal 2. The communication unit is controlled so as to transmit and receive the driving status data and the operation setting data, and the data collection storage unit is controlled so that the driving status data is constantly collected and stored.

  Therefore, according to the drive recorder 1, it becomes easy for the mobile phone terminal 2 to browse the driving situation data and to confirm / change the operation setting. The convenience can be improved. In addition, since the driving situation data is continuously collected and stored in a non-volatile manner, it is possible to avoid the omission of the recording of the driving situation data as much as possible.

  Next, the information sharing service related to traffic accidents with the server 6 as the main component will be described in detail with reference to FIG. As shown in FIG. 4, the server 6 that mainly realizes the above function includes a communication unit 61, an information management unit 62, an information analysis unit 63, and an information storage unit 64.

  The communication unit 61 communicates with the mobile phone terminal 2 through the mobile phone line 5 and also has the traffic center server 8, the police server 9, and the insurance company through the other line 7 (dedicated line, the Internet, etc.). Communication with the server 10 is performed.

  The information management unit 62 is configured to analyze the driving situation data transferred from the drive recorder 1 mounted on the vehicle in which the traffic accident has occurred via the mobile phone terminal 2 and the traffic accident generated by analyzing the driving situation data. Manage (acquire) data (locations and times of occurrence of traffic accidents) and cumulative data of traffic accidents (multiple locations and times of traffic accidents) generated by cumulatively analyzing multiple traffic accident data Analysis, storage, and transmission).

  The information analysis unit 63 analyzes the driving situation data transferred from the drive recorder 1 mounted on the vehicle in which the traffic accident has occurred via the mobile phone terminal 2 to generate the traffic accident data. In addition, the information analysis unit 63 cumulatively analyzes a plurality of traffic accident data, and generates the traffic accident cumulative data.

  The information storage unit 64 stores the above driving situation data, traffic accident data, and traffic accident accumulated data in a nonvolatile manner.

  In addition, the server 6 cooperates with the traffic center server 8, the police server 9, and the insurance company server 10, and information regarding traffic accidents (including the above driving situation data, traffic accident data, and cumulative traffic accident data). It is desirable to have a configuration that can be used mutually. By adopting such a configuration, it becomes possible to enhance information on traffic accidents (increase in the number of known traffic accident parameters) and decentralize server capabilities.

  The server 6 configured as described above transmits the latest accumulated traffic accident data in response to a request from the mobile phone terminal 2. The mobile phone terminal 2 transfers the content received from the server 6 to the drive recorder 1. At this time, if communication between the drive recorder 1 and the mobile phone terminal 2 is impossible, the content received from the server 6 is temporarily stored in the nonvolatile storage unit of the mobile phone terminal 2, and communication with the drive recorder 1 is possible. When it becomes possible, the latest accumulated traffic accident data is transferred from the mobile phone terminal 2 to the drive recorder 1 again.

  In the drive recorder 1 that has received the transfer from the mobile phone terminal 2, the control unit 101 updates the old accumulated traffic accident data stored in the storage unit 107, and thereafter operates based on the latest accumulated traffic accident data. The warning unit 110 is controlled so as to alert the person. For example, when the traffic accident accumulated data includes information related to the accident frequent occurrence point, the driver of the vehicle approaching the accident frequent occurrence point is alerted. As this alert, you may be notified by voice that it is an accident-prone area, or you can use a car navigation system monitor that is separately installed in the vehicle and mark the map screen showing the accident-prone area ( Icon display etc.).

  In addition, it is desirable that the cumulative traffic accident data includes incidental information such as the accident frequency time zone and the cause of the accident in addition to the information on the accident frequent occurrence point. For example, if the incidental information of a certain accident occurrence point has been flagged as “there are many encounter collisions”, a warning that the safety of surroundings should be thoroughly confirmed as a reminder in advance If the flag “Center line over due to excessive speed on the curve” is flagged, the above warning should indicate that the vehicle should decelerate sufficiently when entering the curve. Warning can be made in advance. However, in order to include such accompanying information, it is often insufficient to simply analyze the driving situation data from the drive recorder 1 mounted on the vehicle that has caused the traffic accident. As described above, it is desirable to link the traffic center server 8, the police server 9, and the insurance company server 10 so that information regarding traffic accidents can be used mutually.

  As described above, if the traffic information system mainly provides the information sharing service regarding traffic accidents with the server 6 as a main body, the drive recorder 1 can be actively used as a means for preventing traffic accidents in advance. This will be an incentive to purchase a drive recorder, which can greatly contribute to the promotion of traffic safety.

  In the above description, the configuration in which the latest traffic accident accumulated data is transmitted from the server 6 in response to a request from the mobile phone terminal 2 has been described as an example. However, the configuration of the present invention is limited to this. For example, the latest accumulated traffic accident data is transmitted from the server 6 on a regular basis (for example, once a month) to the mobile phone terminal 2 pre-registered as a service sharing service for information on traffic accidents. It is good also as a structure. With such a configuration, the accumulated traffic accident data stored in the drive recorder 1 can always be kept up-to-date.

  Further, in the above description, the configuration for transmitting the traffic accident accumulated data to the mobile phone terminal 2 has been described as an example. However, the configuration of the present invention is not limited to this, for example, a traffic accident is performed. At the time when the driving situation data is transferred from the waked vehicle to the server 6, at least one of the above driving situation data for the unspecified number of mobile phone terminals 2 existing in the base station area near the accident occurrence point. It is good also as a structure which transmits the positional infomation on an accident occurrence point promptly. By adopting such a configuration, the driver of the vehicle approaching the accident occurrence point can know in real time that a traffic accident has occurred on the route of the vehicle, so search for a detour route, etc. Thus, it is possible to avoid traffic jams and secondary traffic accidents.

  Next, a fuel efficiency improvement determination service mainly using the server 6 will be described in detail with reference to FIGS. FIG. 5 is a time chart showing an example of the driving situation, where the horizontal axis represents time and the vertical axis represents the speed of the vehicle. FIG. 6 is a data table showing an example of the driving situation data recorded under the driving situation of FIG. 5. In particular, parameters necessary for the determination service of the fuel efficiency improvement driving (in FIG. 6, the date and time (ti), The position of the vehicle (P (ti), speed V (ti), acceleration A (ti), and engine speed R (ti), where i = 0 to 14) are described.

  Note that the series of parameters shown in FIG. 6 does not depend on whether the drive recorder 1 is in the “conditional storage specification” or “always storage specification” described above, and stops after the engine is started. All measured values collected until the recording is performed (that is, while the drive recorder 1 is driven) are stored in the nonvolatile storage unit 107 without being discarded. On the other hand, as described above, only the data collected for several seconds to several minutes before and after the accident occurrence timing is stored in the nonvolatile storage unit 107 as the driving situation data necessary for the post-mortem analysis of the traffic accident. Old data is discarded in sequence. As described above, among the driving situation data, the parameters necessary for the determination service for the fuel efficiency improvement driving must be retained for a long period of time (for example, 24 hours). These parameters do not include imaging data collected by the imaging unit 102, so there is no concern of unnecessarily pressing the storage capacity of the storage unit 107.

  When the engine is started at time t0, collection and storage of operation status data by the drive recorder 1 is started. The time interval for collecting the driving situation data may be set to an appropriate value (for example, every 0.5 seconds) in consideration of the balance between analysis accuracy and data capacity. Time t0 to time t1 is an idling period. Time t1 to time t2 is an acceleration travel period. Time t2 to time t3 is a constant speed traveling period. Time t3 to time t4 is a deceleration traveling period. Then, when the engine is stopped at time t4, the collection and storage of the driving situation by the drive recorder 1 is ended.

  When the engine is started again at time t5, the collection and storage of the operation status data by the drive recorder 1 is resumed. Time t5 to time t6 is an idling period. Time t6 to t7 is an acceleration travel period. Time t7 to time t8 is a constant speed traveling period. Time t8 to t10 is an acceleration travel period. Time t10 to time t11 is a constant speed traveling period. Time t11 to time t14 is a deceleration travel period. Then, when the engine is stopped at time t14, the collection and storage of the driving situation by the drive recorder 1 is ended.

  Thereafter, when the driver performs an operation of transferring the driving situation data using the mobile phone terminal 2, the driving situation data stored in the storage unit 107 is transferred to the server 6 via the mobile phone terminal 2. The server 6 analyzes the driving situation data received from the mobile phone terminal 2 and performs a determination process on the fuel efficiency improvement of the driving content, and then transmits the determination result to the mobile phone terminal 2. The above determination result may be described in the body of the e-mail, or a URL [Uniform Resource Locator] in which the determination result is described may be notified.

  The determination regarding the fuel efficiency improvement described above will be described more specifically. Examples of driving operations that unnecessarily waste fuel include excessive increases in speed, rapid acceleration, rapid deceleration, and excessive increases in speed (including flying) (Referred to as “inefficient operation”). Therefore, the server 6 accounts for the time during which the above inefficient operation is performed in one traveling time (in FIG. 5 and FIG. 6, the total time of time t0 time t4 and time t5 to time t14). , And based on the calculated value, enlightenment and suggestion of fuel efficiency improvement driving for the driver are performed.

  That is, in the determination regarding the fuel efficiency improvement, the server 6 determines whether the speed V (ti) does not exceed the predetermined upper limit value Vth, the acceleration A (ti) does not exceed the predetermined upper limit value Ath +, or the acceleration A ( ti) is not lower than a predetermined lower limit value Ath- and whether the rotational speed R (ti) is not higher than a predetermined upper limit value Rth. If there is at least one determination item corresponding to the above, It is determined that the inefficient operation was performed at the time ti.

  A specific description will be given in accordance with the driving conditions illustrated in FIGS. 5 and 6. However, in order to simplify the description, in the following description, it is assumed that the rotational speed R (ti) is unquestioned, and the determination regarding the fuel efficiency improvement is performed based on the speed V (ti) and the acceleration A (ti).

  Regarding the determination of overspeed, it is determined that the speed V (t9) to the speed V (t12) exceed a predetermined upper limit value Vth, and the time t9 to the time t12 are counted as an inefficient operation period (overspeed period). The Further, regarding the determination of the rapid acceleration, it is determined that the acceleration A (t6) to the acceleration A (t7) exceeds a predetermined upper limit value Ath +, and the time t6 to the time t7 is set as an inefficient driving period (rapid acceleration period). Be counted. Further, regarding the determination of the rapid deceleration, it is determined that the acceleration A (t11) to the acceleration A (t13) are below a predetermined lower limit value Ath-, and the time t11 to the time t13 are inefficient driving periods (rapid deceleration periods). Is counted as However, since the time t11 to the time t12 are the overspeed period and the rapid deceleration period, duplicate counting is not performed.

  After completion of the determination process, the server 6 creates data of determination results to be notified to the driver. In addition, as the notification content of the determination result, for example, the achievement degree of the fuel efficiency improvement driving may be displayed based on the ratio of the inefficient driving in one run, or the breakdown of the driving content (for example, Fuel efficiency improvement driving period: A%, idling period: B%, inefficient driving period C% (overspeed period: a%, rapid acceleration period: b%, rapid deceleration period: c%)) may be displayed. It is also effective to point out the driving operation (for example, overspeed) that seems to have caused the most deterioration in fuel consumption during this travel and to display advice so as to correct this. As a matter of course, a display unit (liquid crystal display panel or the like) mounted on the mobile phone terminal 2 can be used as a means for notifying the driver of the determination result of the fuel efficiency improvement driving received from the server 6. That's fine.

  As described above, if the traffic information system mainly provides the fuel efficiency improvement driving determination service with the server 6 as the main body, the drive recorder 1 is used as an auxiliary means for the driver to learn, practice and continue the fuel efficiency improvement driving. Since it can be actively used, it becomes an incentive to purchase a drive recorder, and as a result, it can greatly contribute to the promotion of environmental conservation.

  In addition, if the detailed analysis of the operation status data is performed on the server 6 side instead of the drive recorder 1, the information processing capability of the drive recorder 1 does not need to be increased unnecessarily, which increases the size and cost of the device. You don't have to invite me.

  The server 6 may be configured to cumulatively store the determination results of the fuel efficiency improvement driving. By adopting such a configuration, the achievement degree of the fuel efficiency improvement driving is compared with the previous driving time for each run, or the achievement degree of the fuel efficiency improvement driving is averaged over a predetermined counting period, etc. Thus, since more continuous analysis can be performed, it is possible to notify how the skill of the fuel efficiency improvement driving changes and to increase the motivation of the driver.

  5 and FIG. 6, the time t0 to the time t1 and the time t5 to the time t6 are all idling periods, and the velocity V (ti) and the acceleration A (ti) are both zero values. Therefore, in light of the above determination items, these periods are not counted as inefficient operation periods. However, if the idling period is too long, fuel is unnecessarily wasted. Therefore, the determination algorithm related to fuel efficiency improvement may be appropriately changed so that this is determined as inefficient driving.

  Also, in the above, for the sake of simplicity, the rotational speed R (ti) is made unquestioned, and no special reference is made to other determination items, but in order to make more detailed determinations regarding fuel efficiency improvement. For example, it is desirable to add whether or not the fluctuation of the speed V (ti) (repetition of acceleration / deceleration) occurs to the determination item.

  The upper limit value Vth of the speed V (ti), the upper limit value Ath + and the lower limit value Ath− of the acceleration A (ti), and the upper limit value Rth of the rotational speed R (ti) are as follows: It is desirable to adjust appropriately taking into account the driving conditions, such as the difference in driving speed and the driving speed on ordinary roads and highways. When adjusting such a threshold value, it is necessary to include information on the position P (ti) of the vehicle as the driving situation data transferred from the drive recorder 1 to the server 6.

  In the above, among the driving situation data collected by the drive recorder 1, as parameters necessary for the determination service of the fuel efficiency improvement driving, the date and time (ti), the position of the vehicle (P (ti), the speed V (ti), The acceleration A (ti) and the engine speed R (ti) are selected, and these parameters are continuously measured and stored from time t0 to time t4 and from time t5 to time t14. Although the description has been given by taking as an example a configuration in which all contents are transferred from the drive recorder 1 to the server 6, the configuration of the present invention is not limited to this, and the capacity of the storage unit 107 can be reduced or the mobile phone terminal 2 If priority is given to the reduction of communication data (and hence the reduction of communication costs), as indicated by the hatched portion in FIG. 6, only when starting and stopping the engine and during inefficient operation. Is stored in the storage unit 107, and the stored contents are transferred to the server 6. When such a configuration is adopted, the drive recorder 1 side determines the inefficient operation (overspeed determination, Sudden acceleration determination, rapid deceleration determination, rotation speed excess determination, etc.) must be performed. For this purpose, it is sufficient to compare each parameter with a predetermined threshold value, and therefore it is necessary to unnecessarily increase the information processing capability of the drive recorder 1 Absent.

  Next, an operation for prohibiting overwriting operation status data stored in the storage unit 107 in a nonvolatile manner will be described in detail.

  In the drive recorder 1 according to the present embodiment, the upper limit value (for example, the number of storage files of 10 by sensor trigger and the manual operation trigger) can be stored in a nonvolatile manner in accordance with the capacity of the storage unit 107. When the number of operation status data files stored in a non-volatile manner reaches the upper limit and a new operation status data file is stored in a non-volatile manner, The old operating data file is overwritten. This is the same as the conventional drive recorder.

  However, in the drive recorder 1 of the present embodiment, it is possible to assign either “overwrite permission attribute” or “overwrite prohibition attribute” to each file of the operation status data stored in a nonvolatile manner. ing. It should be noted that an “overwrite permission attribute” is given as a default attribute to each file of the driving situation data stored in the storage unit 107 in a nonvolatile manner. Therefore, unless the “overwrite prohibition attribute” is intentionally given, the operation status data cannot be used after being overwritten by a new file. On the other hand, since a file intentionally assigned with the “overwrite prohibition attribute” is excluded from being overwritten by a new file, even if the file is the oldest file stored in the storage unit 107. Since it is not overwritten by a new file, the contents of the driving situation data can be confirmed at any time unless the user intentionally deletes the file.

  For example, since a minor contact accident occurred while driving a car, the driving situation data was stored in a non-volatile manner by manual operation just in case, but at that point, there seems to be no particular problem for either myself or the other party. However, I did not negotiate after confirming the driving situation data stored in a nonvolatile manner, but later discovered that the vehicle was damaged and wanted to seek compensation from the other party. May be required to compensate. In such a case, if the “overwrite prohibition attribute” is assigned to the operation status data file that was stored just in case at the time of the accident, the stored file will not be lost by overwriting. As a result, it becomes possible to check the driving status data at the time of the accident if necessary, and it becomes possible to negotiate appropriately with the other party.

  FIG. 7 is a flowchart showing an operation of prohibiting overwriting of operation status data stored in a nonvolatile manner.

  First, in step S31, it is determined whether or not the predetermined trigger condition described above is satisfied. Here, when it is determined that a predetermined trigger condition is satisfied (for example, when an excessive impact is generated in the vehicle or when the user manually stores the driving situation data), the flow continues. The process proceeds to step S32. On the other hand, when it is not determined that the predetermined trigger condition is satisfied, the flow is returned to step S31, and the above-described trigger condition determination process is continued.

  If it is determined in step S31 that the predetermined trigger condition is satisfied, in step S32, the operation status data collected at that time is stored in the storage unit 107 in a nonvolatile manner. At this time, the “overwrite permission attribute” is given as a default attribute to the storage file of the driving situation data. Note that it is not always necessary to proactively provide such a dedicated flag for the “overwrite permission attribute”, and the “overwrite permission attribute” is assigned because the “overwrite prohibition attribute” is not assigned. Can be considered.

  In a subsequent step S33, a message regarding acceptance of the overwrite prohibition operation is notified. As this notification, for example, even if a microphone that makes a voice announcement such as “Now I have stored the driving status data. If you want to prohibit overwriting of this stored file, please press the overwriting prohibit button on the main unit.” Alternatively, a lamp for notifying that it is the reception timing of the overwrite prohibition operation may be provided, and this may be turned on or blinked. With such a notification configuration, the user can determine whether or not to give the “overwrite prohibition attribute” to the stored file without delay when the driving situation data is stored in a nonvolatile manner. It becomes possible.

  However, the notification of the message in step S33 is not necessarily an essential step. For example, when the drive recorder 1 is provided with a lamp that is lit or flashed during the storage process of the driving status data, the lighting or flashing is performed. The above notification may be used, or the above notification may not be performed at all. With such a configuration, it is not necessary to add any components to the main body of the drive recorder 1.

  In the subsequent step S34, it is determined whether or not the user has performed an overwrite prohibition operation. If it is determined that the user has performed an overwrite prohibition operation, the flow proceeds to step S35. On the other hand, if it is not determined that the user has performed an overwrite prohibition operation, the flow proceeds to step S36.

  As the above-described overwrite prohibition operation, for example, pressing of an overwrite prohibition operation-dedicated button may be detected, or pressing of a manual storage button during operation status data storage processing may be detected.

  With regard to the latter configuration, for example, when an excessive impact is generated on the vehicle or the user presses the manual storage button, it is determined in step S31 that a predetermined trigger condition is satisfied, and in step S32, at that time The collected driving situation data is stored in the storage unit 107. If it is detected in step S34 that the user has pressed the manual storage button while the storage process is being performed, This may be recognized as an overwrite prohibition operation. By adopting such a configuration, it is possible to accept an overwrite prohibition operation by merely rewriting a part of software for operating the control unit 101 without adding any components to the main body of the drive recorder 1. It becomes.

  If it is determined in step S34 that the user has performed an overwrite prohibition operation, in step S35, the “overwrite prohibition attribute” is added to the operation status data file stored in the storage unit 107, and the series of flows ends. Is done. Files with such “overwrite prohibition attributes” are excluded from being overwritten by new files. Therefore, unless the user intentionally deletes the files, the contents of the driving situation data are checked at any time. It becomes possible.

  On the other hand, if it is not determined in step S34 that the user has performed the overwrite prohibition operation, it is determined in step S36 whether or not the condition for ending the overwrite prohibition operation is satisfied. Here, when it is determined that the predetermined acceptance end condition is satisfied, the “overwrite prohibition attribute” is not given to the file of the driving situation data stored in the storage unit 107, which is the default attribute “ A series of flows ends with the “overwrite permission attribute” being given. On the other hand, if it is not determined that the predetermined acceptance end condition is satisfied, the flow is returned to step S34, and the presence / absence determination of the overwrite prohibition operation by the user is continued.

  As the above reception end condition, for example, separately from step S31, it is detected whether a predetermined trigger condition is satisfied, that is, whether it is necessary to store another driving situation data in a nonvolatile manner. do it. In this case, from when one driving status data is stored in a nonvolatile manner until another driving status data needs to be stored in a nonvolatile manner, the “overwriting prohibition attribute” is given to the latest driving status data. Is possible.

  Further, as the above reception end condition, for example, it may be detected whether or not a predetermined time (for example, several minutes to several hours) has elapsed since the trigger condition was satisfied in step S31. In this case, it is possible to give the “overwrite prohibition attribute” to the operation status data until a predetermined time elapses after the one operation status data is stored in a nonvolatile manner.

  Moreover, as said reception completion conditions, you may detect whether the electric power supply to the drive recorder 1 was interrupted | blocked, for example. In this case, until the power supply to the drive recorder 1 is cut off after the one driving state data is stored in a nonvolatile manner, generally until the vehicle is stopped and the ignition key is turned off. It is possible to give “overwrite prohibition attribute” to the situation data.

  Further, as the above reception end condition, for example, it may be detected whether or not the storage process in the storage unit 107 in step S32 is completed. In this case, the timing at which the “overwrite prohibition attribute” can be given to one driving situation data is limited during the storage process in the storage unit 107. When this acceptance end condition is adopted, it is desirable that a lamp that is turned on during the storage process of the driving situation data is provided in the drive recorder 1, and the notification of the message in step S33 is made when the lamp is turned on. .

  The configuration of the present invention can be variously modified in addition to the above-described embodiment without departing from the gist of the invention. That is, the above-described embodiment is an example in all respects and should not be considered as limiting, and the technical scope of the present invention is not the description of the above-described embodiment, but the claims. It should be understood that all modifications that come within the meaning and range of equivalents of the claims are included. For example, the timing for giving the “overwrite prohibition attribute” to the driving situation data may be the time when the recorded image is reproduced.

  The present invention is a technique useful for enhancing the convenience of a drive recorder.

1 Drive recorder 2 Mobile phone terminal 3 Electronic control unit (ECU)
DESCRIPTION OF SYMBOLS 4 In-vehicle sensor 5 Mobile telephone line 6 Server 7 Line 8 Traffic center server 9 Police server 10 Insurance company server 61 Communication part 62 Information management part 63 Information analysis part 64 Information storage part 101 Control part 102 Imaging part 103 GPS receiving part 104 Acceleration sensor 105 Interface section 106 Real-time clock (RTC)
107 storage unit 108 communication unit 109 operation unit 110 warning unit

Claims (8)

A data collection unit that collects driving situation data of the vehicle, a storage unit that stores the driving situation data in a nonvolatile manner, an operation unit that accepts user operations, and a control unit that collectively controls these functional units; A drive recorder comprising:
The storage unit has an upper limit value for the number of operation status data files that can be stored in a nonvolatile manner. When storing the situation data file in a nonvolatile manner, it overwrites the oldest driving situation data file,
When a predetermined overwrite prohibiting operation is accepted by the operation unit, the control unit sets an overwrite prohibition attribute to an operation status data file that is currently being stored, or an operation status data file that has been stored recently. A drive recorder characterized by providing.   2. The drive recorder according to claim 1, wherein when the control unit determines that a predetermined nonvolatile storage condition is satisfied, the operation state data is stored in the storage unit.   3. The drive according to claim 2, wherein a reception period of the overwrite prohibition operation is limited to a period from when the predetermined nonvolatile storage condition is satisfied to when a predetermined reception end condition is satisfied. Recorder.   The predetermined acceptance end condition is that one operation status data is stored in a nonvolatile manner and another operation status data needs to be stored in a nonvolatile manner, and the predetermined nonvolatile storage condition is satisfied after the predetermined nonvolatile storage condition is satisfied. At least one of the following: elapse of time, power supply to the drive recorder has been cut off, or storage processing of the one operation status data in the storage unit has been completed. The drive recorder according to claim 3.   5. The drive recorder according to claim 3, further comprising a notifying unit that notifies that the overwriting prohibiting operation is being accepted.   6. The informing unit according to claim 5, wherein the notification unit is a microphone that performs a predetermined voice announcement, or a lamp that is lit or blinked during a period during which the overwrite prohibition operation is accepted or during the storage process of the driving status data. The described drive recorder. The operation unit has a manual storage button for allowing the user to store the driving status data in the storage unit at an arbitrary timing.
The control unit determines that the overwrite prohibiting operation has been accepted when the operation unit detects that the manual storage button is pressed while the operation status data is being stored. The drive recorder according to any one of claims 1 to 6, characterized in that: The operation unit has an overwrite prohibition button for assigning an overwrite prohibition attribute to an operation status data file that is currently being stored by a user at an arbitrary timing or an operation status data file that has been stored most recently. Have
The drive recorder according to any one of claims 1 to 6, wherein the control unit determines that the overwrite prohibition operation has been received when a press of the overwrite prohibition button is detected.

Images