JP6866982B2 - Vehicle data recording device and vehicle data recording system - Google Patents

Description

The present invention relates to a vehicle data recording device and a vehicle data recording system.

Conventionally, there is known a system (vehicle data recording system) that records vehicle data before and after this event in a non-volatile memory in the vehicle when an event such as a collision or an operation of an automatic brake occurs. The data recorded by this vehicle data recording system is used, for example, to verify the behavior of the vehicle at that time when a trouble occurs during traveling.

As a device for recording such vehicle data, a time length upper limit value holding unit that holds a predetermined recording time length upper limit value for at least one type of first data out of two or more types of recording target data. When the free area on the recording medium is insufficient, the recording time length of the first data recorded on the recording medium is compared with the recording time length upper limit value, and the recording time length upper limit value is compared. When the amount exceeds the above, a drive recorder has been proposed in which unnecessary data is erased from the area in which the first data is recorded to secure a new free area (Patent Document 1).

In addition, processing for taking an image and saving the image data is performed by generating a trigger linked to the operation of the measuring instrument, and the type information indicating the type of measurement is associated with the image data obtained by taking a picture during measurement. A device for recording is proposed (Patent Document 2).

Japanese Unexamined Patent Publication No. 2013-61727 Japanese Unexamined Patent Publication No. 2004-363823

In the vehicle data recording system described above, vehicle data is recorded in a non-volatile memory, and the recordable capacity is finite. Therefore, when vehicle data is recorded up to the upper limit of the storage capacity of the non-volatile memory, the latest vehicle data is sequentially overwritten so as to be recorded in the area where the oldest recorded data is recorded. In this case, if overwriting occurs between the occurrence of the event and the use of the vehicle data, the vehicle data cannot be used. Therefore, assuming the time from the occurrence of the event to the reading to use the data, the number of events that occur within this time is calculated based on the frequency of occurrence of the event, and the vehicle for that number of times. The recording area required to record the data is set. Further, when vehicle data is recorded for a plurality of types of events, a recording area required for each type of event is obtained, and a recording area of a non-volatile memory is allocated for each type of event so as to secure the required recording area.

In this way, the recording area of the non-volatile memory is allocated to each event in advance based on the frequency of occurrence of each event, but the frequency of occurrence of each event differs depending on factors such as the driver of the vehicle, the driving area, and the season. There is a problem that the preset recording area and the actually required recording area deviate from each other, and the storage area setting becomes inappropriate. For example, if the actual occurrence frequency is lower than the expected occurrence frequency, the actually required recording area becomes smaller than the preset recording area, so that a part of the storage area is wasted. Also, if the actual frequency of occurrence is higher than the expected frequency of occurrence, the actually required recording area will be larger than the preset recording area, so overwriting will occur in a shorter period than expected, and the vehicle data will be overwritten. There is a possibility that the required vehicle data does not remain at the time of use.

The present invention has been made to solve such a problem, and an object of the present invention is to provide a technique for appropriately setting the capacity of a recording area corresponding to an event type.

In order to solve the above problems, the present invention employs the following means. That is, the vehicle data recording device of the present invention
The acquisition unit that acquires vehicle data from the vehicle,
A determination unit that determines the occurrence of a plurality of types of events in the vehicle, and
When the determination unit determines that the event has occurred, the recording control unit that records the vehicle data acquired by the acquisition unit in the recording area assigned to each type of the event.
An event transmission unit that sends event information indicating the occurrence of the event to the management server, and
It is provided with a change unit that receives change information for changing the capacity of the storage area allocated for each type of event according to the occurrence frequency of each type of event from the management server and changes the capacity of the storage area. ..

According to the present invention, it is possible to provide a technique for appropriately setting the capacity of the recording area corresponding to the type of event.

FIG. 1 is a diagram showing a vehicle data recording system. FIG. 2 is an explanatory diagram of a process executed by the vehicle data recording device at the time of recording vehicle data. FIG. 3 is a diagram showing an example of allocation of a storage area in the vehicle data recording device. FIG. 4 is an explanatory diagram of information held by the management server for generating change information. FIG. 5 is an explanatory diagram of a process in which the management server adjusts the recordable number of times. FIG. 6 is a diagram showing a specific example of the process of adjusting the recordable number of times. FIG. 7 is an explanatory diagram of a process in which the management server adjusts the recordable number of times in the second embodiment. FIG. 8 is an explanatory diagram of a process in which the management server adjusts the recordable number of times in the third embodiment. FIG. 9 is a diagram showing a configuration of a vehicle data recording device according to a fourth embodiment. FIG. 10 is an explanatory diagram of a process in which the vehicle data recording device adjusts the recordable number of times. FIG. 11 is an explanatory diagram of a process in which the vehicle data recording device adjusts the recordable number of times.

Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings. However, the embodiments described below are examples for carrying out the present invention, and the present invention is not limited to the embodiments described below.

<First Embodiment>
<Overall configuration>
FIG. 1 is a diagram showing a vehicle data recording system 1. The vehicle data recording system 1 includes a vehicle data recording device 3 provided in the vehicle 2 and a management server 4 installed outside the vehicle 2.

The vehicle 2 includes a vehicle data recording device 3, a vehicle data detection unit 20, and a communication unit 21. When a so-called "event" occurs, such as when a collision occurs in the vehicle 2 or when the automatic brake is activated, the vehicle data recording device 3 triggers the occurrence of the event and determines the predetermined values before and after the occurrence of the event. The vehicle data acquired from the detection unit 20 is recorded in the non-volatile memory over a period of time (for example, several seconds to several tens of seconds). Here, the vehicle data recording device 3 determines the type of event and records the vehicle data in the storage area allocated for each type of event. This makes it possible to explain to the driver and verify after the fact about the behavior of the vehicle when an event occurs. In particular, the vehicle data recording device 3 according to the present embodiment obtains the occurrence frequency for each event type, and changes the capacity of the storage area allocated for each event type according to the occurrence frequency.

The detection unit 20 acquires vehicle data of the vehicle 2, and includes, for example, an acceleration sensor 201, a vehicle speed sensor 202, a steering angle sensor 203, a position detection unit 204, an ECU (Electronic Control Unit) 205, and the like. The acceleration sensor detects acceleration in three axial directions, for example, up and down, left and right, and front and back of the vehicle. The vehicle speed sensor detects the vehicle speed of the vehicle. The steering angle sensor 203 detects the operated angle of the steering. The position detection unit 204 detects the position of the own vehicle by GPS (Global Positioning System) or the like. In addition, the position detection unit 204
May provide map information and detect the area where the vehicle exists and the type of road on which the vehicle is traveling (hereinafter, also referred to as road type). The position detection unit 204 may be a so-called car navigation device. The ECU 205 detects the activation of the automatic brake. Further, the detection unit may be a switch that is turned ON / OFF depending on whether or not the seat belt is fastened and whether the headlight is turned on or off. Further, the ECU may be an ECU that collects data such as the engine speed, the water temperature of the coolant, the ESC (Electronic Stability Control), the ABS (Anti-lock Brake System), and the obstacle detection device. Note that these detection units 20 are examples, and may have other detection units such as a gyro sensor, a camera for detecting obstacles, and a millimeter wave radar.

The communication unit 21 is a device that communicates with the management server 4 via a communication line such as a WAN, transmits event information from the vehicle data recording device 3 to the management server 4, and changes information from the management server 4. Is received and sent to the vehicle data recording device 3.

<Vehicle data recording device>
The vehicle data recording device 3 includes a control unit 31, a recording unit 32, and an acquisition unit 33. The control unit 31 is, for example, a microcomputer provided with a CPU and a memory. The memory may include a main storage device and an auxiliary storage device. The main storage device is used as a CPU work area, a program or data storage area, and a communication data buffer area. The main storage device is formed, for example, by Random Access Memory (RAM) or a combination of RAM and Read Only Memory (ROM). Programs such as the operating system and firmware are installed in the memory.

The CPU is also called an MPU (Micro Processor Unit), a microprocessor, a processor, or a processing device. The CPU is not limited to a single processor, and may have a multiprocessor configuration. Further, a single CPU connected by a single socket may have a multi-core configuration. Even if at least a part of the processing of each of the above parts is performed by a processor other than the CPU, for example, a dedicated processor such as a Digital Signal Processor (DSP), a Graphics Processing Unit (GPU), a numerical arithmetic processor, a vector processor, or an image processing processor. good. Further, at least a part of the processing of each of the above parts may be an integrated circuit (IC) or another digital circuit. Further, an analog circuit may be included in at least a part of each of the above parts. Integrated circuits include LSIs, application specific integrated circuits (ASICs), and programmable logic devices (PLDs). PLD includes, for example, a Field-Programmable Gate Array (FPGA). Each of the above parts may be a combination of a processor and an integrated circuit. The combination is called, for example, an MCU (Micro Controller Unit), a SoC (System-on-a-chip), a system LSI, a chipset, or the like.

The CPU loads the program stored in the memory into the main storage device and executes the process described in the program to perform the functions of the determination unit 301, the recording control unit 302, the event transmission unit 303, and the change unit 304. Fulfill.

The determination unit 301 determines the occurrence of a plurality of types of events in the vehicle. For example, the determination unit 301 of this example detects a collision, sudden acceleration, slip, automatic braking operation, ABS operation, ESC operation, and the like as events. The occurrence of these events may be notified from the ECU or the like as the detection unit 20, or based on the vehicle data acquired from the detection unit 20, it is determined that the event has occurred when the vehicle data satisfies a predetermined condition. You may. For example, the determination unit 301 determines that a collision has occurred when the condition that the acceleration acquired from the acceleration sensor 201 exceeds the threshold value is satisfied. Further, the determination unit 301 determines that sudden acceleration has occurred when the conditions that the acceleration acquired from the acceleration sensor 201 is higher than the predetermined value and the depression amount of the accelerator pedal acquired from the ECU is larger than the predetermined value are satisfied. To do.

The recording control unit 302 records the vehicle data acquired by the detection unit 20 in the recording area assigned to each event type in the recording unit 32, triggered by the determination that the event has occurred by the determination unit 301. Let me.

The event transmission unit 303 transmits event information indicating the occurrence of an event to the management server 4 via the communication unit 21.

The change unit 304 receives change information from the management server that changes the capacity of the storage area allocated for each event type according to the occurrence frequency of each event type based on the event information, and the recording unit 32 receives the change information of the event. Change the capacity of the storage area allocated for each type. That is, if the capacity of the storage area allocated for each event type is insufficient, it is increased, and if it is excessive, it is decreased.

Further, the recording unit 32 is a non-volatile memory, and vehicle data is recorded by the recording control unit 302.

The acquisition unit 33 acquires vehicle data from the vehicle, passes it to the control unit 31 and the recording unit 32, and uses it for determining the occurrence of an event and recording the vehicle data.

<Management server>
The management server 4 is, for example, a computer provided with a CPU, a memory, and a communication unit. The CPU and memory in the management server 4 have the same configuration as the CPU and memory of the control unit 31, and the description of the same configuration will be omitted. The CPU of the management server 4 loads the recording management program stored in the memory into the main storage device and executes the process described in the program to execute the event information receiving unit 401, the change information generating unit 402, and the data. It functions as the transmitter 403.

The event information receiving unit 401 receives event information from the vehicle data recording device via the communication unit. The change information generation unit 402 generates change information based on the received event information. The method of generating change information will be described later. The data transmission unit 403 transmits the change information generated via the communication unit to the vehicle data recording device 3.

An operating system and a records management program are installed in the memory of the management server 4.

<Vehicle data recording method>
FIG. 2 is an explanatory diagram of a process executed by the vehicle data recording device 3 at the time of recording vehicle data. The vehicle data recording device 3 executes the process of FIG. 2 when the vehicle start switch (for example, accessory switch (ACC)) is turned on or when the start is instructed.

First, the vehicle data recording device 3 acquires change information from the management server 4 (step S10). For example, the vehicle data recording device 3 transmits a change information acquisition request to the management server 4, and receives the change information transmitted by the management server 4.

Next, in step S20, the vehicle data recording device 3 changes the capacity of the storage area allocated to each event type in the recording unit 32 based on the change information, and proceeds to step S30.

In step S30, the vehicle data recording device 3 acquires vehicle data from the detection unit 20 and proceeds to step S40.

In step S40, the vehicle data recording device 3 determines whether or not an event has occurred based on the acquired vehicle data. In the case of a negative determination in step S40, the vehicle data recording device 3 ends the process of FIG. 2, and in the case of an affirmative determination, records the vehicle data acquired in step S30 according to the type of event that occurred. Recording is performed in the storage area of unit 32 (step S50).

Further, the vehicle data recording device 3 transmits event information indicating that an event has occurred and the type of the event to the management server 4 (step S60).

As described above, the vehicle data recording device 3 transmits event information to the management server 4 when an event related to the vehicle occurs, and the capacity of the storage area according to the change information obtained based on the event information. To change.

FIG. 3 is a diagram showing an example of allocation of a storage area in the vehicle data recording device 3. In FIG. 3, types A to D indicate the type of event, and the recordable number of times indicates the number of times that the event can be recorded in the recording area, that is, the capacity of the recording area. As described above, in this example, the storage area capacity (recordable number of times) is allocated for each event type.

FIG. 4 is an explanatory diagram of information held by the management server 4 for generating change information. As shown in FIG. 4, the management server 4 stores the recordable number of times, the minimum recordable number of times, and the event occurrence number of times as setting information of each vehicle for each event type. In the initial state, as shown in FIG. 4A, the number of occurrences of the event is 0, and when the event information is received, the number of occurrences of the type of the event is counted. In FIG. 4B, the number of occurrences of type A is increased by 1. The minimum number of times of storage determines the minimum number of times (capacity) required when using vehicle data.

Further, the management server 4 defines a period for retaining vehicle data (retention period), for example, the number of days t. The holding period is not limited to the number of days and may be the mileage. Further, the management server 4 stores the value of the adjustment number counter for counting the number of adjustments and the value of the number of days counter for counting the retention period for each vehicle.

FIG. 5 is an explanatory diagram of a process in which the management server 4 adjusts the recordable number of times. The management server 4 executes the process of FIG. 5 at a predetermined timing, once a day in this example, for each vehicle. First, the management server 4 determines whether or not the value of the number of days counter has reached a predetermined value (t days) (
Step S110). When it is determined that the predetermined timing has been reached, the management server 4 executes the processing after step S115, and in this example, it is determined whether or not the retention period (t days) has been reached. .. The criterion for this determination is not limited to the storage period, and other values such as 1/2 of the storage period may be set. Further, the criterion for this determination is not limited to the number of days, but may be the mileage of the vehicle targeted for processing in FIG. 5 (hereinafter also referred to as the target vehicle), the number of occurrences of events, and the like, and a combination thereof. ..

If the determination is affirmative in step S110, the management server 4 calculates the degree of insufficient storage capacity for each event type (step S115). The degree of insufficient storage capacity is determined by, for example, Equation 1 below.

Insufficiency = number of events occurred ÷ (number of recordable times * number of adjustments) ・ ・ ・ (Equation 1)
In Equation 1, the number of adjustments is the number of times the number of days counter value reaches t days and the adjustment process after step S115 is executed. That is, the number of adjustments is a value obtained by dividing the cumulative value of the number of days (the number of days counter value) by the number of days t. For example, the number of events expected to occur during the storage period is 5, the recordable number is set to 5, and when the process of FIG. 5 is performed on the 2 × t day, the adjustment number is 2. .. Then, if the number of events that occurred in these 2 × t days is 10, the degree of deficiency is 10 ÷ (5 × 2) = 1 from Equation 1. That is, the set number of recordable times (5 times) and the number of times the event actually occurred per t day (10/2 = 5 times) match, and the number of record times (capacity) allocated to the storage area. There is no excess or deficiency in the memory. At this time, if the number of occurrences exceeds 10, that is, if the number of occurrences per t day exceeds 5, the degree of shortage exceeds 1, and the number of recordings (capacity) allocated to the storage area is insufficient. It is in a state of being. Further, when the number of occurrences is less than 10, that is, when the number of occurrences per t day is less than 5, the degree of deficiency is less than 1, and the number of recordings (capacity) allocated to the storage area is sufficient. ..

Next, the management server 4 searches for each type of event having the largest degree of deficiency (step S120), and proceeds to step S125 as the processing target α.

In step S125, the management server 4 determines whether or not the degree of shortage of the event set as the processing target α exceeds 1. In this example, the criterion for this determination is 1, but it is not strictly limited to 1, and a value larger than 1 may be set.

In the case of affirmative determination in step S125, the management server 4 searches for the one with the smallest degree of deficiency among each type of event (step S130), and proceeds to step S135 as the processing target β.

In step S135, the management server 4 determines whether or not the degree of shortage of the event set as the processing target β is less than 1. In this example, the criterion for this determination is 1, but it is not strictly limited to 1, and a value smaller than 1 may be set.

In the case of an affirmative determination in step S135, the management server 4 determines whether or not the recordable number of events set as the processing target β satisfies the following equations (2) and (3) (step S140).

Kβ> Mβ ・ ・ ・ Equation (2)
Hβ ÷ ((Kβ-1) × TK) ≦ 1 ・ ・ ・ Equation (3)
Kβ: Number of recordable times of processing target β Mβ: Minimum number of recording times of processing target β Hβ: Number of occurrences of events set as processing target β TK: Number of adjustments Counter value In formula (2), the number of recordable times of processing target β is This is a condition for preventing the change from falling below the minimum number of recordings of the processing target β. Further, the equation (3) is for preventing the shortage of the processing target β from exceeding 1 when the change (-1 in this example) is performed to reduce the recordable number of times of the processing target β. It is a condition. That is, the equations (2) and (3) confirm whether or not the recordable number of times of the processing target β can be reduced.

In the case of an affirmative determination in step S140, the management server 4 makes a change to increase the recordable number of the processing target α by 1 (step S150), and makes a change to decrease the recordable number of the processing target β by 1 (step S155). ), Return to step S115. That is, steps S150 and S155 are processes for changing the number of recordable times.

On the other hand, in the case of a negative determination in step S140, the management server 4 excludes the type of the event from the search target of the processing target β (step S145), returns to step S130, and redoes the search of the processing target β.

If a negative determination is made in step S125, the number of recordable times of the processing target α is sufficient and adjustment is not necessary. Therefore, the management server 4 proceeds to step S160 and initializes the number of days counter. For example, when the recordable number of times is no longer insufficient due to the change in steps S150 and S155, the management server 4 makes a negative determination in step S125.

In step S165, the management server 4 counts up the adjustment count counter. Then, in step S170, the management server 4 generates information indicating the recordable number of times of the target vehicle as change information. The management server 4 may transmit the change information to the target vehicle when the change information is generated, or change to the vehicle when communicating with the vehicle, for example, when there is a request for acquisition of the change information from the vehicle. Information may be sent. Note that the management server 4 may generate change information and transmit it to the target vehicle in step S170 only when the recordable number of times is changed in steps S150 and S155, regardless of whether or not there is a change. The change information in step S170 may be generated or transmitted to the target vehicle.

If a negative determination is made in step S110, the management server 4 proceeds to step S175 and counts up the number of days counter.

FIG. 6 is a diagram showing a specific example of the process of adjusting the recordable number of times. In this example, as shown in FIG. 6A, the recordable times of event types A, B, C, and D are 5, 6, 4, and the number of occurrences is 6, 7, before the adjustment. It is 2,5.

In this case, the management server 4 sets the degree of deficiency of the event types A, B, C, and D to 1.20, 1.17, 0.50, and 0, based on the equation (1) in step S115 of FIG. We ask for 71.

Next, the management server 4 searches for each type of event having the largest degree of deficiency (step S120), and sets the event type A as the processing target α.

In step S125, the management server 4 determines whether or not the shortage degree (1.20) of the event set as the processing target α exceeds 1, and makes an affirmative determination.

In step S130, the management server 4 searches for each type of event having the smallest degree of deficiency, and sets the event type C as the processing target β.

In step S135, the management server 4 determines whether or not the shortage degree (0.50) of the event set as the processing target β is less than 1, and makes an affirmative determination.

In step S140, the management server 4 determines whether or not the recordable number of events set as the processing target β satisfies the equations (2) and (3), and determines affirmatively.

In step S150, the management server 4 makes a change that increases the recordable number (5) of the processing target α by 1 (step S150), and decreases the recordable number (4) of the processing target β by 1 in step S155. Is performed, and the process returns to step S115. At this time, the recordable times of the event types A, B, C, and D are 6, 6, 3, and 7, as shown in FIG. 6 (B).

The management server 4 returning to step S115 determines the degree of deficiency of the event types A, B, C, and D as 1.00, 1.17, 0.67, 0.71 based on the equation (1).

In step S120, the management server 4 searches for each type of event having the largest degree of deficiency, and sets the event type B as the processing target α.

In step S125, the management server 4 determines whether or not the shortage degree (1.17) of the event set as the processing target α exceeds 1, and makes an affirmative determination.

In step S130, the management server 4 searches for each type of event having the smallest degree of deficiency, and sets the event type C as the processing target β.

In step S135, the management server 4 determines whether or not the shortage degree (0.67) of the event set as the processing target β is less than 1, and makes an affirmative determination.

In step S140, the management server 4 determines whether or not the recordable number of events set as the processing target β satisfies the equations (2) and (3), and the recordable number (3) is the minimum recordable number (3). 3) Since it is not larger than 3) and does not satisfy the equation (2), a negative judgment is made. Then, the management server 4 excludes the event type C from the search target of the processing target β (step S145), returns to step S130, and redoes the search of the processing target β.

In step S130, the management server 4 searches for each type of event having the smallest degree of deficiency, and sets the event type D as the processing target β.

In step S135, the management server 4 determines whether or not the shortage degree (0.71) of the event set as the processing target β is less than 1, and makes an affirmative determination.

In step S140, the management server 4 determines whether or not the recordable number of events set as the processing target β satisfies the equations (2) and (3), and determines affirmatively.

In step S150, the management server 4 makes a change that increases the recordable number (6) of the processing target α by 1 (step S150), and decreases the recordable number (7) of the processing target β by 1 in step S155. Is performed, and the process returns to step S115. At this time, event type A
, B, C, and D can be recorded at 6, 7, 3, and 6 as shown in FIG. 6 (C).

The management server 4 returning to step S115 determines the degree of deficiency of the event types A, B, C, and D as 1.00, 1.00, 0.67, 0.83 based on the equation (1).

In step S120, the management server 4 searches for the event having the highest degree of deficiency among the types of events, and since there are a plurality of the highest deficiencies (1.00), the event is based on a predetermined priority. Type A is the processing target α.

In step S125, the management server 4 determines whether or not the shortage degree (1.00) of the event set as the processing target α exceeds 1, and makes a negative determination.

Then, in step S170, as shown in FIG. 6D, the management server 4 generates change information in which the recordable times of the event types A, B, C, and D are 6, 7, 3, and 6. .. The vehicle data recording device acquires this change information from the management server 4 (step S10), and changes the recordable number of times according to the change information (step S20).

<Effect of embodiment>
As described above, in the vehicle data recording device 3 of the present embodiment, when the determination unit 301 determines that an event has occurred, the vehicle data acquired by the detection unit 20 is assigned to each type of the event. From the management server, the recording control unit 302 for recording in the recording area and the change information for changing the capacity of the storage area allocated for each event type according to the occurrence frequency of each event type based on the event information. It is provided with a changing unit 304 that receives and changes the capacity of the storage area.

With this configuration, the vehicle data recording device 3 of the present embodiment can set the capacity of the recording area corresponding to the type of event without excess or deficiency, and can optimize the allocation of the recording area in the recording unit (nonvolatile memory) 32. As a result, it is possible to prevent the required vehicle data from being erased when the vehicle data is used due to insufficient capacity of the recording area.

<Second Embodiment>
In the second embodiment, the storage area allocation is optimized according to external factors. Since the other configurations are the same as those of the above-described first embodiment, the same elements are designated by the same reference numerals, and the description thereof will be omitted again. FIG. 7 is an explanatory diagram of a process in which the management server 4 adjusts the recordable number of times in the present embodiment.

In FIG. 7, the processes of steps S110 and S115 are the same as those in FIG. After step S115, the management server 4 determines whether or not there is a change in the external factor as compared with the time of the previous adjustment (step S117). Here, the external factor is, for example, the occurrence status of an event in a peripheral vehicle existing around the vehicle, the area where the vehicle exists, the road type, the season, the weather, the day of the week, the time zone, or a combination thereof. The management server 4 acquires the position information of the vehicle, identifies the peripheral vehicles existing in the vicinity of the vehicle, and reads out the number of occurrences of the event in the peripheral vehicle from the storage unit. In addition, the management server 4 acquires the position information of the vehicle and identifies the area where the vehicle exists and the road type from the map information. Further, the management server 4 specifies the season, the day of the week, and the time zone from the current date and time. Further, the management server 4 acquires the position information of the vehicle and acquires the weather at the position from the external server.

If the determination is affirmative in step S117, the management server 4 increases / decreases (adjusts) the number of occurrences of the event according to the external factor (step S118), and if the determination is negative, skips step S118 and steps S120. Move to. For example, in a cold region in winter, when there are many slips, the number of occurrences such as ESC operation is multiplied by a predetermined coefficient and increased. Further, when the number of events such as the automatic braking of a peripheral vehicle is large, the number of occurrences of the event is multiplied by a predetermined coefficient to increase the number of events. As a result, the number of recordable times is increased so that the number of occurrences increased in the subsequent steps can be recorded. Further, when the number of recordable times of an event type such as ESC operation is reduced due to a change of season, for example, the number of occurrences of the event type is multiplied by a predetermined coefficient and reduced. As a result, in the subsequent steps, the number of recordable times is reduced so that the reduced number of occurrences can be recorded. The processing after step S120 is the same as that in FIG.

According to the present embodiment, it is possible to more accurately optimize the allocation of the storage area based on external factors such as the occurrence status of events in peripheral vehicles and regional characteristics.

<Third Embodiment>
In the third embodiment, the storage area allocation is optimized according to the priority. Since the other configurations are the same as those in the second embodiment described above, the same elements are designated by the same reference numerals, and the description thereof will be omitted again. FIG. 8 is an explanatory diagram of a process in which the management server 4 adjusts the recordable number of times in the present embodiment.

In FIG. 8, the processing of steps S110 to S120 is the same as that in FIG. After step S120, the management server 4 changes the processing target α according to a predetermined priority (step S122). For example, the types of events such as ABS operation, automatic braking operation, and ESC operation are prioritized in the order in which they are to be preferentially recorded. Then, if the management server 4 has an event type having a higher priority than the one set as the processing target α in step S120 among those for which the shortage degree obtained in step S115 exceeds 1.00, the management server 4 has the priority. Change the processing target α to a higher event type.

As a result, the type of the event having a high priority is adjusted before the others, so that the storage area of the event type is preferentially secured.

<Fourth Embodiment>
In the fourth embodiment, an example in which the vehicle data recording device 3A has a function of adjusting the recordable number of times is shown. It should be noted that the same elements as those in the above-described first embodiment are designated by the same reference numerals, and the description thereof will be omitted again. 9 is a diagram showing the configuration of the vehicle data recording device 3A according to the present embodiment, FIG. 10 is an explanatory diagram of processing executed by the vehicle data recording device 3A at the time of vehicle data recording, and FIG. 11 is a vehicle data recording device. It is explanatory drawing of the process which 3A adjusts the recordable number of times.

As shown in FIG. 9, the vehicle data recording device 3A of the present embodiment has a different configuration in which the change unit 304A is provided instead of the change unit 304 as compared with the vehicle data recording device 3 of FIG.

The changing unit 304A calculates the occurrence frequency for each event type, and changes the capacity of the storage area allocated for each event type according to the occurrence frequency.
FIG. 10 is an explanatory diagram of a process executed by the vehicle data recording device 3A at the time of recording vehicle data. The vehicle data recording device 3A executes the process of FIG. 10 when the vehicle start switch (for example, accessory switch (ACC)) is turned on or when the start is instructed.

In step S230, the vehicle data recording device 3A acquires vehicle data from the detection unit 20 and proceeds to step S240.

In step S240, the vehicle data recording device 3A determines whether or not an event has occurred based on the acquired vehicle data. In the case of a negative determination in step S240, the vehicle data recording device 3A ends the process of FIG. 2, and in the case of an affirmative determination, records the vehicle data acquired in step S230 according to the type of event that occurred. Recording is performed in the storage area of unit 32 (step S250).

Further, the vehicle data recording device 3A executes the process of FIG. 11 at a predetermined timing, once a day in this example, for each vehicle. First, the vehicle data recording device 3A determines whether or not the value of the number of days counter has reached a predetermined value (t days) (step S310). The vehicle data recording device 3A executes the processing after step S315 when it is determined that the predetermined timing has been reached. In this example, it is determined whether or not the storage period (t days) has been reached. And said. The criterion for this determination is not limited to the storage period, and other values such as 1/2 of the storage period may be set. Further, the criterion for this determination is not limited to the number of days, but may be the mileage of the vehicle, the number of times an event has occurred, or a combination thereof.

If the determination is affirmative in step S310, the vehicle data recording device 3A calculates the degree of insufficient storage capacity for each event type (step S315). The degree of insufficient storage capacity is determined by, for example, the above equation 1.

Insufficiency = number of event occurrences ÷ (number of recordable times * number of adjustments) ・ ・ ・ (Equation 1)
Next, the vehicle data recording device 3A searches for the event having the largest degree of deficiency among the types of events (step S320), and proceeds to step S322 as the processing target α.

In step S322, the vehicle data recording device 3A changes the processing target α according to a predetermined priority (step S322). For example, the types of events such as ABS operation, automatic braking operation, and ESC operation are prioritized in the order in which they are to be preferentially recorded. Then, if the vehicle data recording device 3A has a type of event having a higher priority than the one set as the processing target α in step S320 among those for which the degree of deficiency obtained in step S315 exceeds 1.00, the priority is given. Change the processing target α to the type of event with a high degree.

In step S325, the vehicle data recording device 3A determines whether or not the degree of shortage of the event set as the processing target α exceeds 1. In this example, the criterion for this determination is 1, but it is not strictly limited to 1, and a value larger than 1 may be set.

In the case of affirmative determination in step S325, the vehicle data recording device 3A searches for the one with the smallest degree of deficiency among each type of event (step S330), and proceeds to step S335 as the processing target β.

In step S335, the vehicle data recording device 3A determines whether or not the degree of shortage of the event set as the processing target β is less than 1. In this example, the criterion for this determination is 1, but it is not strictly limited to 1, and a value smaller than 1 may be set.

In the case of an affirmative determination in step S335, the vehicle data recording device 3A determines whether or not the number of recordable times of the event set as the processing target β satisfies the following equations (2) and (3) (step S340). ).

Kβ> Mβ ・ ・ ・ Equation (2)
Hβ ÷ ((Kβ-1) × TK) ≦ 1 ・ ・ ・ Equation (3)
Kβ: Number of recordable times of processing target β Mβ: Minimum number of recording times of processing target β Hβ: Number of occurrences of events set as processing target β TK: Number of adjustments Counter value If affirmative judgment is made in step S340, the vehicle data recording device 3A , The change that increases the recordable number of the processing target α by 1 (step S350), the change that decreases the recordable number of the processing target β by 1 (step S355), and returns to step S315. That is, steps S350 and S355 are processes for changing the number of recordable times.

On the other hand, in the case of a negative determination in step S340, the vehicle data recording device 3A excludes the type of the event from the search target of the processing target β (step S345), returns to step S330, and redoes the search of the processing target β. ..

Further, if a negative determination is made in step S325, the number of recordable times of the processing target α is sufficient and adjustment is not necessary. Therefore, the vehicle data recording device 3A shifts to step S360 and initializes the number of days counter. To do. For example, when there is no shortage in the number of recordable times due to the change in steps S350 and S355, the vehicle data recording device 3A makes a negative determination in step S325.

In step S365, the vehicle data recording device 3A counts up the adjustment count counter. Then, in step S370, the vehicle data recording device 3A changes the allocation of the capacity of the storage area based on the recordable number of times adjusted in steps S315 to S355.

As described above, the vehicle data recording device 3A of the present embodiment can set the capacity of the recording area corresponding to the type of event without excess or deficiency, and can optimize the allocation of the recording area in the recording unit (nonvolatile memory) 32. .. As a result, it is possible to prevent the required vehicle data from being erased when the vehicle data is used due to insufficient capacity of the recording area. Further, the vehicle data recording device 3A of the present embodiment can optimize the storage area without requiring an external device such as a management server 4.

1 Vehicle data recording system 2 Vehicle 3 Vehicle data recording device 3, 3A Vehicle data recording device 4 Management server 20 Detection unit 21 Communication unit 31 Control unit 32 Recording unit 33 Acquisition unit

Claims (5)

The acquisition unit that acquires vehicle data from the vehicle,
A judgment unit that determines the occurrence of multiple types of events in a vehicle,
When the determination unit determines that the event has occurred, the recording control unit that records the vehicle data acquired by the acquisition unit in the recording area assigned to each type of the event.
An event transmission unit that sends event information indicating the occurrence of the event to the management server, and
A change unit that receives change information from the management server that changes the capacity of the storage area allocated for each type of event according to the frequency of occurrence of each type of event, and changes the capacity of the storage area.
Vehicle data recording device. The change information changes the capacity of the storage area to the capacity obtained for each type of the event based on the event information of the vehicle existing around the vehicle in addition to the event information of the vehicle. The vehicle data recording device according to claim 1. The vehicle data recording device according to claim 1 or 2, wherein the change information changes the capacity of the storage area to a capacity obtained for each type of the event based on a predetermined priority. The acquisition unit that acquires vehicle data from the vehicle,
A judgment unit that determines the occurrence of multiple types of events in a vehicle,
When the determination unit determines that the event has occurred, the recording control unit and the event type that record the vehicle data acquired by the acquisition unit in the recording area assigned to each event type. A change unit that calculates the frequency of occurrence for each event and changes the capacity of the storage area allocated for each type of event according to the frequency of occurrence.
Vehicle data recording device. A vehicle data recording system including a vehicle data recording device and a management server connected via a communication line.
The vehicle data recording device
The acquisition unit that acquires vehicle data from the vehicle,
A judgment unit that determines the occurrence of multiple types of events in a vehicle,
When the determination unit determines that the event has occurred, the recording control unit that records the vehicle data acquired by the acquisition unit in the recording area assigned to each type of the event and the occurrence of the event. An event transmitter that sends event information indicating
A change unit that receives change information from the management server that changes the capacity of the storage area allocated for each type of event according to the frequency of occurrence of each type of event, and changes the capacity of the storage area.
With
The management server
An event information receiving unit that receives the event information and
A change information generation unit that generates the change information based on the event information,
A data transmission unit that transmits the change information to the vehicle data recording device, and
Vehicle data recording system equipped with.

Images