JP7728069B2 - In-vehicle device - Google Patents

Description

The disclosed embodiments relate to an in-vehicle device.

Dashboards are a type of in-vehicle information recording device known as drive recorders. Drive recorders are required to reliably record video data of the vehicle and its surroundings, particularly video data in the event of an accident or incident.

However, in the event of an accident or other damage to the vehicle, the internal storage area of the drive recorder or removable external storage areas such as SD memory cards may be physically damaged, making it impossible to retrieve the recorded video data.

To prepare for such cases, a drive recorder has been proposed that can continuously transmit video data to a data center via a communications network (see, for example, Patent Document 1).

Japanese Patent Application Laid-Open No. 2019-032725

However, the above-mentioned conventional technologies leave room for further improvement in terms of backing up data reliably and at low cost, especially when the risk of data loss is high.

First, using the conventional technology described above could result in enormous costs for communication expenses and the maintenance and management of data center storage areas. Furthermore, it is desirable to back up drive recorder data with a high degree of reliability, especially when there is a high risk of not being able to retrieve the data from the drive recorder, i.e., when there is a high risk of data loss.

One aspect of the embodiment has been made in light of the above, and aims to provide an information recording device, information recording system, and information recording method that can back up data with high reliability and at low cost, especially when the risk of data loss is high.

According to one aspect of the embodiment, an in-vehicle device is mounted on a vehicle and includes a storage unit and a control unit. The storage unit stores video information from a camera mounted on the vehicle and sensor information from a sensor installed on the vehicle as recorded data. When a situation indicated by the video information and the sensor information matches a predetermined determination criterion, the control unit provides the recorded data to another in-vehicle device mounted on the vehicle .

According to one aspect of the embodiment, data can be backed up with high reliability and at low cost, especially when the risk of data loss is high.

FIG. 1 is a diagram illustrating an outline of an information recording method according to an embodiment. FIG. 2 is a block diagram showing an example of the configuration of an information recording system according to the embodiment. FIG. 3 is an explanatory diagram of the ECU information. FIG. 4 is a diagram showing an example of a determination condition when the risk of loss is high. FIG. 5 is an explanatory diagram of the first selection example. FIG. 6 is an explanatory diagram of the second selection example. FIG. 7 is an explanatory diagram of the third selection example. FIG. 8 is a flowchart showing a processing procedure executed by the drive recorder according to the embodiment.

Embodiments of the information recording device, information recording system, and information recording method disclosed herein will be described in detail below with reference to the accompanying drawings. Note that the present invention is not limited to the embodiments described below.

First, an overview of the information recording method according to the embodiment will be explained using Figure 1. Figure 1 is an explanatory diagram illustrating the overview of the information recording method according to the embodiment.

As shown in FIG. 1, the information recording system 1 according to the embodiment includes a drive recorder 10, one or more ECUs (Electronic Control Units) 50, and a center server 100.

The drive recorder 10 and ECU 50 are communicatively connected via an in-vehicle network VN such as a CAN (Controller Area Network). The drive recorder 10 and at least one ECU 50 are communicatively connected via a dedicated line LL. The dedicated line LL is a serial line or a USB (Universal Serial Bus) line. The drive recorder 10 and center server 100 are also communicatively connected via wireless communication via a mobile phone network or the like.

The drive recorder 10 also has a sensor unit 5 that includes various sensors, including a camera 5a. The drive recorder 10 records video information captured by the camera 5a and vehicle information indicated by sensor data from sensors other than the camera 5a included in the sensor unit 5, in the memory unit 14. The memory unit 14 includes an internal storage area within the drive recorder 10 itself, and a removable external storage area such as an SD memory card.

As shown in FIG. 1, the drive recorder 10 has a normal mode and a redundant mode. The drive recorder 10 is configured to be able to calculate a loss risk, which indicates the risk of losing data recorded by the drive recorder 10 due to damage to the drive recorder 10, based on the surrounding conditions indicated by various sensor data from the sensor unit 5.

If the risk of such loss is determined to be low, the drive recorder 10 operates in normal mode. In normal mode, the drive recorder 10 records video information and vehicle information only in the memory unit 14 of the drive recorder 10.

On the other hand, if the drive recorder 10 determines that there is a high risk of loss, it transitions to redundancy mode. In redundancy mode, the drive recorder 10 records video information and vehicle information in its storage unit 14, and also backs up the same data to the ECU 50 via the dedicated line LL or the in-vehicle network VN (see arrows a1 and a2 in the figure).

At this time, the drive recorder 10 saves the data to the memory unit 54 of the ECU 50. The memory unit 54 has a dedicated area for the ECU 50 and a shared area that can be shared with the drive recorder 10 in redundancy mode, and the drive recorder 10 saves the data to this shared area. Note that if there is no free space in the shared area, the oldest data is overwritten.

In addition, the drive recorder 10 also saves the same data to the center server 100 via a mobile phone network or the like (see arrow a3 in the figure).

Examples of cases where the risk of loss is high include when a strong G-value is detected by the acceleration sensor included in the sensor unit 5, or when location information indicates that the vehicle has passed through a high-accident zone. These are situations where an accident due to a collision, rollover, etc. is expected. Other examples of conditions for determining when the risk of loss is high will be described later using Figure 4.

In this way, when the risk of loss is high, the drive recorder 10 automatically switches to redundancy mode, where it backs up data to a nearby ECU 50, thereby preventing the loss of recorded data in the event of damage to the drive recorder 10. Furthermore, by uploading recorded data to the center server 100 via the communication network only when the drive recorder switches to redundancy mode, the amount of communication data does not need to be increased more than necessary, which helps reduce communication costs.

In addition, the information recording process corresponding to the information recording method according to the embodiment is performed by the control unit 15 (see Figure 2) of the drive recorder 10. Details of the information recording process performed by the control unit 15 will be described later using Figure 2 and subsequent figures.

As described above, in the information recording method according to the embodiment, the control unit 15 of the drive recorder 10 calculates the risk of data loss to be recorded in the memory unit 14 based on the surrounding conditions indicated by the sensor data from the sensor unit 5, and if the risk of loss satisfies a determination condition indicating a high risk of loss, the drive recorder operates in a redundant mode in which the data is evacuated to another device.

Therefore, the information recording method according to the embodiment makes it possible to back up data with high reliability and at low cost, especially when the risk of data loss is high. Below, we will explain in more detail an example configuration of an information recording system 1 that applies the information recording method according to the embodiment described above.

Figure 2 is a block diagram showing an example configuration of an information recording system 1 according to an embodiment. Note that Figure 2 shows only the components necessary to explain the features of this embodiment, and omits a description of general components.

In other words, the components shown in Figure 2 are conceptual functional components and do not necessarily need to be physically configured as shown. For example, the specific form of distribution and integration of each block is not limited to that shown, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

Furthermore, in the explanation using Figure 2, the explanation of components that have already been explained may be simplified or omitted.

As already mentioned, as shown in FIG. 2, the information recording system 1 according to the embodiment includes a drive recorder 10, one or more ECUs 50, and a center server 100. The drive recorder 10 has a sensor unit 5, a dedicated communication unit 11, an in-vehicle communication unit 12, an out-vehicle communication unit 13, a memory unit 14, and a control unit 15.

The sensor unit 5 includes a camera 5a, an acceleration sensor 5b, and a GPS (Global Positioning System) sensor 5c. The sensor unit 5 may be integrated with the drive recorder 10.

The dedicated communication unit 11 is a connection interface for the aforementioned dedicated line LL. The dedicated communication unit 11 is connected to at least one ECU 50 via the dedicated line LL, and transmits and receives information to and from the connected ECU 50.

The in-vehicle communication unit 12 is realized by a network adapter or the like. The in-vehicle communication unit 12 is connected to the aforementioned in-vehicle network VN via a wired connection and transmits and receives information to and from each ECU 50. Note that the in-vehicle communication unit 12 may also transmit and receive information to and from each ECU 50 via wireless communication using Wi-Fi (registered trademark), Bluetooth (registered trademark), UWB (Ultra Wide Band), etc.

The external vehicle communication unit 13 is implemented by a network adapter or the like. The external vehicle communication unit 13 is wirelessly connected to the network N, such as the aforementioned mobile phone network, and transmits and receives information to and from the center server 100.

The storage unit 14 is realized by an internal storage device such as RAM (Random Access Memory), flash memory, or a disk drive, or an external storage device such as an SD memory card. In the example of Figure 2, the storage unit 14 stores ECU information 14a and recording information 14b.

ECU information 14a is information about surrounding ECUs 50 that are candidates for data backup destinations in redundancy mode. Figure 3 is an explanatory diagram of ECU information 14a. As shown in Figure 3, ECU information 14a includes a record for each surrounding ECU 50 that is a candidate for data backup destination.

Each record defines the overwrite priority, ECU name, domain, address, etc. of each ECU 50. The overwrite priority indicates the priority of overwrites as a data backup destination from the perspective of the drive recorder 10. In the example of Figure 3, the smaller the overwrite priority number, the higher the overwrite priority.

The ECU name is identification information for each ECU 50. Here, for ease of explanation, it is referred to as the name. The belonging domain refers to the belonging domain in the in-vehicle network VN. As shown in the figure, domain A is assumed to be the same domain as the drive recorder 10.

Therefore, in the example of Figure 3, the multimedia ECU has a closer network relationship with the drive recorder 10 than the backup ECU. The address is the address information of each ECU 50 in the in-vehicle network VN. The domain to which it belongs may also be included in the address.

Returning to the explanation of Figure 2, recorded information 14b is information that includes a group of recorded data in which vehicle information indicated by sensor data from various sensors other than camera 5a is recorded in synchronization with the video information captured by camera 5a.

The control unit 15 is a controller, and is implemented by a CPU (Central Processing Unit) or MPU (Micro Processing Unit) executing various programs (not shown) stored in the memory unit 14 using RAM as a working area. The control unit 15 can also be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array).

The control unit 15 has an acquisition unit 15a, a calculation unit 15b, a determination unit 15c, an operation mode switching unit 15d, a recording unit 15e, and a transmission unit 15f, and realizes or executes the information processing functions and actions described below.

The acquisition unit 15a acquires various sensor data from the sensor unit 5, including video information and vehicle information. The acquisition unit 15a also acquires information transmitted from the ECU 50 via the dedicated communication unit 11 or the in-vehicle communication unit 12. The acquisition unit 15a also acquires information transmitted from the center server 100 via the out-vehicle communication unit 13.

The calculation unit 15b calculates the aforementioned risk of loss based on the sensor data from the sensor unit 5 acquired by the acquisition unit 15a. The determination unit 15c determines whether the risk of loss calculated by the calculation unit 15b is high.

Here, Figure 4 shows example judgment conditions when the risk of loss is high. The judgment unit 15c judges that the risk of loss is high when the various judgment conditions shown as examples in Figure 4 are met.

Since the example of the judgment condition No. 1 in Figure 4 has already been explained, we will start with No. 2 here. The example of the judgment condition No. 2 is when ABS (Anti-lock Braking System) activation information, airbag deployment information, pre-crash safety, or other driving safety support system activation information is received. This is a situation in which an accident due to a collision, rollover, etc. is expected.

An example of a judgment condition in No. 3 is when image recognition is used to detect a traffic light, stop sign, or one-way sign from the acquired video information, resulting in a judgment that a traffic violation has occurred. This is an anticipated situation in which image recognition is used to detect a traffic light, stop sign, or one-way sign from the acquired video information, resulting in a judgment that a traffic violation has occurred.

An example of a condition for No. 4 is when the write limit for the internal storage area or external storage area is exceeded. This is a situation in which memory corruption is likely to occur.

An example of a judgment condition for No. 5 is when vehicle horn activation information is received. This is a situation where an accident is expected due to sudden braking or sudden steering caused by a vehicle or person suddenly jumping out into the road.

An example of a judgment condition for No. 6 is when a car security alert is received. This is a situation in which the vehicle or items inside the vehicle are likely to be stolen, or vandalized by a suspicious person.

An example of a judgment condition for No. 7 is when a wearable device or other device indicates that the driver is in a dangerous condition. This is a situation in which the driver is likely to be dozing off, looking away, or experiencing abnormalities in their vital signs.

An example of a judgment condition for No. 8 is when the driver detects the pressing of an emergency call switch when he or she is harmed by a passenger or other person. From the outside, this is observed, for example, as the flashing of the company name display light (a so-called "lantern" in the case of a taxi). This is a situation that can be imagined when a taxi or bus is hijacked. Note that Figure 4 is merely an example and does not limit the judgment conditions for determining that there is a high risk of loss.

In addition, to summarize each example in Figure 4, it can be said that the calculation unit 15b calculates the risk of loss based on at least one of the following information contained in the sensor data: vehicle information related to the vehicle's behavior, video information capturing images of the inside and outside of the vehicle, and personal information related to the vehicle's occupants.

Furthermore, it can be said that the calculation unit 15b calculates the risk of loss related to an accident (see No. 1, 2, 3, and 5 in the figure).

Furthermore, it can be said that the calculation unit 15b calculates the risk of loss related to damage to the memory unit 14 (see No. 4 in the figure).

Furthermore, it can be said that the calculation unit 15b calculates the risk of loss related to human causes, including destruction or theft (see Nos. 6 and 8 in the figure).

Furthermore, it can be said that the calculation unit 15b calculates the risk of loss related to abnormalities in the occupant's vital signs (see No. 7 in the figure).

Returning to the explanation of Figure 2, the operation mode switching unit 15d switches the operation mode of the drive recorder 10 to the redundancy mode when the determination unit 15c determines that the risk of loss is high. Furthermore, the operation mode switching unit 15d switches the operation mode of the drive recorder 10 to the normal mode when the determination unit 15c determines that the risk of loss is low.

The determination unit 15c determines the risk of loss each time new video information and vehicle information is acquired by the acquisition unit 15a, and the operation mode switching unit 15d switches the operation mode as needed depending on the determination result of the determination unit 15c.

The recording unit 15e generates recording data that synchronizes vehicle information with the video information captured by the camera 5a, and records the data in the recording information 14b. When the drive recorder 10 switches to redundancy mode, the transmission unit 15f transmits the recording data generated by the recording unit 15e to the ECU 50, which serves as the backup destination, based on the ECU information 14a. The transmission unit 15f also transmits the same recording data to the center server 100.

Next, examples of selecting the ECU 50 to which data is to be saved and the save area for that ECU when the drive recorder 10 transitions to redundancy mode will be described using Figures 5 to 7. Figure 5 is an explanatory diagram of a first selection example. Figure 6 is an explanatory diagram of a second selection example. Figure 7 is an explanatory diagram of a third selection example.

As a premise for the explanation using Figures 5 to 7, in accordance with the example of ECU information 14a shown in Figure 3, the ECUs 50 that are candidates for the evacuation destination are the multimedia ECU 50-1 and the airbag ECU 50-2.

The multimedia ECU 50-1 is connected to the in-vehicle network VN-A, which belongs to the same domain as the drive recorder 10. The multimedia ECU 50-1 is also connected to the drive recorder 10 via a dedicated line LL.

The airbag ECU 50-2 is connected to an in-vehicle network VN-B, which belongs to a different domain from the drive recorder 10. Furthermore, as shown in Figure 3, the overwrite priority of the multimedia ECU 50-1 is higher than that of the airbag ECU 50-2. Note that, hereinafter, when there is no need to distinguish between the in-vehicle networks VN-A and VN-B, they will be collectively referred to as the in-vehicle network VN.

Based on the above, in the first selection example, as shown in Figure 5, when the control unit 15 of the drive recorder 10 transitions to redundancy mode (step S11), it notifies the multimedia ECU 50-1 and airbag ECU 50-2 of the mode transition via the in-vehicle network VN (step S12).

Then, the control unit 15 overwrites and saves the saved data in the ECU 50 with the highest overwrite priority (here, the multimedia ECU 50-1) without waiting for a response from each ECU 50 (step S13).

In other words, as shown in Figure 5, even if there is no free space in the shared area of the multimedia ECU 50-1 but there is free space in the airbag ECU 50-2, the control unit 15 forcibly overwrites and saves the data in the shared area of the multimedia ECU 50-1 (see part M1 in the figure). This first selection example is effective in emergencies, etc., when speed is the top priority.

At this time, the control unit 15 also overwrites and saves the data to be saved in the shared area of the multimedia ECU 50-1 via the dedicated line LL. This prevents data collisions in emergencies and improves robustness.

Also, as shown in FIG. 6, in the second selection example, when the control unit 15 of the drive recorder 10 transitions to the redundancy mode (step S21), it notifies the multimedia ECU 50-1 and the airbag ECU 50-2 of the mode transition via the in-vehicle network VN (step S22).

In response to this notification, the multimedia ECU 50-1 and airbag ECU 50-2 respond to the drive recorder 10 via the in-vehicle network VN with the free space in the shared area of their respective storage units 54 (step S23).

The control unit 15 then saves the data to the ECU 50 (here, the airbag ECU 50-2) with the largest free space (see part M2 in the figure) (step S24). This second selection example is effective when you want to efficiently use the entire logical shared space across each ECU 50 as seen from the drive recorder 10.

In the example shown in Figure 6, if there is no more free space in the shared area of the airbag ECU 50-2, data can be overwritten and saved starting from the shared area of the ECU 50 with the highest overwrite priority. A similar example is the third selection example.

As shown in FIG. 7, in the third selection example, when the control unit 15 of the drive recorder 10 transitions to redundancy mode (step S31), it notifies the multimedia ECU 50-1 and airbag ECU 50-2 of the mode transition via the in-vehicle network VN (step S32).

In response to this notification, the multimedia ECU 50-1 and airbag ECU 50-2 respond to the drive recorder 10 via the in-vehicle network VN with the free space in the shared area of their respective storage units 54 (step S33).

If there is no free space in any of the ECUs 50 (see M3 in the figure), the control unit 15 overwrites and saves the data to be saved in the ECU 50 with the highest overwrite priority (here, the multimedia ECU 50-1) (step S34). This third selection example is effective when you want to reliably save data even if there is no free space in the entire logical shared area across each ECU 50 as seen from the drive recorder 10.

Next, the processing steps executed by the drive recorder 10 will be explained using Figure 8. Figure 8 is a flowchart showing the processing steps executed by the drive recorder 10 according to the embodiment.

As shown in FIG. 8, the acquisition unit 15a of the control unit 15 acquires video information and vehicle information from the sensor unit 5 (step S101). Then, the calculation unit 15b of the control unit 15 calculates the loss risk based on the video information and vehicle information acquired by the acquisition unit 15a (step S102).

Then, the determination unit 15c of the control unit 15 determines whether the loss risk calculated by the calculation unit 15b is high (step S103). If the loss risk is high (step S103, Yes), the operation mode switching unit 15d of the control unit 15 operates the drive recorder 10 in redundancy mode (step S104).

On the other hand, if the risk of loss is low (step S103, No), the operation mode switching unit 15d operates the drive recorder 10 in normal mode (step S105).

The control unit 15 then determines whether or not an end event has occurred (step S106). An end event occurs when the power to the drive recorder 10 is turned off. Such power-off events include when the vehicle's power is turned off as normal, as well as when the power supply from all power sources, including backup power sources, is completely cut off due to an accident or other reason. Conversely, if the power supply is not completely cut off, there is no end event.

If there is no end event (step S106, No), the control unit 15 repeats the process from step S101. If there is an end event (step S106, Yes), the control unit 15 ends the process.

As described above, the drive recorder 10 according to this embodiment is an information recording device mounted on a vehicle and includes a sensor unit 5, a memory unit 14, and a control unit 15. The control unit 15 calculates the risk of data loss recorded in the memory unit 14 based on the surrounding conditions indicated by the sensor data from the sensor unit 5, and operates in a redundant mode in which the data is saved to another device if the risk of loss satisfies a determination condition indicating a high risk of loss.

Therefore, the drive recorder 10 according to the embodiment can back up data with high reliability and at low cost, especially when the risk of data loss is high.

The control unit 15 also calculates the risk of loss based on at least one of the following information contained in the sensor data: vehicle information related to the vehicle's behavior, video information capturing images of the interior and exterior of the vehicle, and personal information related to the vehicle's occupants.

Therefore, the drive recorder 10 according to this embodiment can calculate the risk of loss based on at least one of vehicle information, video information, and personnel information, and perform backups according to this risk of loss.

The control unit 15 also calculates the above-mentioned loss risk related to an accident.

Therefore, the drive recorder 10 according to the embodiment can perform backups to address the above-mentioned risk of loss in situations that may arise from a vehicle accident.

The control unit 15 also calculates the above-mentioned risk of loss due to damage to the memory unit 14.

Therefore, the drive recorder 10 according to the embodiment can perform backups to address the above-mentioned risk of loss in situations that may arise from damage to the memory unit 14.

The control unit 15 also calculates the above-mentioned risk of loss due to human causes, including vandalism or theft.

Therefore, the drive recorder 10 according to the embodiment can perform backups to address the above-mentioned risk of loss in situations that may arise from human causes, including destruction or theft.

The control unit 15 also calculates the risk of loss related to abnormalities in the occupant's vital signs.

Therefore, the drive recorder 10 according to this embodiment can provide backup to address the above-mentioned risk of loss in situations that may arise from abnormalities in the vital signs of an occupant.

The other devices are an ECU 50 (an example of an "other in-vehicle device") other than the drive recorder 10 that is capable of communicating with the drive recorder 10, and a center server 100 (an example of a "server device") that is capable of wireless communication with the drive recorder 10.

Therefore, according to the drive recorder 10 of this embodiment, when switching to redundancy mode, backup can be performed using the ECU 50 and center server 100 as the backup destination.

The control unit 15 also selects the ECU 50 to which the data will be saved based on the predetermined overwrite priority in the redundancy mode.

Therefore, the drive recorder 10 according to the embodiment can select the optimal ECU 50 based on the overwrite priority according to the domain to which it belongs, etc.

Furthermore, at least one of the ECUs 50 is configured to be able to communicate with the drive recorder 10 via a dedicated line LL.

Therefore, the drive recorder 10 according to the embodiment makes it possible to avoid data collisions in emergencies and perform backups with increased robustness.

In addition, when the control unit 15 transitions to the redundancy mode, it forces the ECU 50 with the highest overwrite priority to back up the data via the dedicated line LL.

Therefore, the drive recorder 10 according to the embodiment can provide effective backup when speed is the top priority, such as in an emergency.

The information recording system 1 according to the embodiment includes a drive recorder 10 mounted on a vehicle, an ECU 50 (an example of an "other vehicle-mounted device") other than the drive recorder 10, and a center server 100 (an example of a "server device"). The ECU 50 is capable of communicating with the drive recorder 10. The center server 100 is capable of wireless communication with the drive recorder 10. The drive recorder 10 includes a sensor unit 5, a memory unit 14, and a control unit 15. The control unit 15 calculates the risk of loss of data recorded in the memory unit 14 based on the surrounding conditions indicated by sensor data from the sensor unit 5, and operates in a redundant mode in which the data is saved to the ECU 50 and the center server 100 if the risk of loss satisfies a determination condition indicating a high risk of loss.

Therefore, the information recording system 1 according to the embodiment makes it possible to back up data with high reliability and at low cost, especially when there is a high risk of data loss.

In addition, the information recording method according to the embodiment is an information recording method executed by a drive recorder 10 mounted on a vehicle and having a sensor unit 5 and a memory unit 14, and includes calculating the risk of loss of data recorded in the memory unit 14 based on the surrounding conditions indicated by sensor data from the sensor unit 5, and operating in a redundant mode in which the data is evacuated to another device if the risk of loss satisfies a determination condition indicating a high risk of loss.

Therefore, the information recording method according to the embodiment makes it possible to back up data with high reliability and at low cost, especially when there is a high risk of data loss.

Further advantages and modifications may readily occur to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details and representative embodiments shown and described above. Accordingly, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and their equivalents.

REFERENCE SIGNS LIST 1 Information recording system 5 Sensor unit 5a Camera 5b Acceleration sensor 10 Drive recorder 11 Dedicated communication unit 12 In-vehicle communication unit 13 Out-vehicle communication unit 14 Storage unit 14a ECU information 14b Recorded information 15 Control unit 15a Acquisition unit 15b Calculation unit 15c Determination unit 15d Operation mode switching unit 15e Recording unit 15f Transmission unit 50 ECU
50-1 Multimedia ECU
50-2 Airbag ECU
54 Memory unit 100 Center server LL Dedicated line

Claims (5)

An in-vehicle device that is mounted on a vehicle and has a storage unit and a control unit,
the storage unit stores image information from a camera mounted on the vehicle and sensor information from a sensor provided on the vehicle as recorded data;
the control unit provides the recorded data to another in-vehicle device mounted on the vehicle when the situation indicated by the video information and the sensor information matches a predetermined determination criterion.
In-vehicle device. The control unit
If an accident occurs, or a human act including damage, destruction, or theft of the storage unit is detected, or an abnormality in the vital signs of an occupant of the vehicle is detected from the video information and the sensor information, the recorded data is provided to the other in-vehicle device.
The in-vehicle device according to claim 1 . The control unit
providing the recorded data to an in-vehicle device having a high predetermined priority from among the plurality of other in-vehicle devices mounted on the vehicle ;
The in-vehicle device according to claim 1 or 2. The control unit
selecting an in-vehicle device having the largest free space in a storage unit from among the plurality of other in-vehicle devices mounted on the vehicle ;
providing the recorded data to the selected in-vehicle device;
The in-vehicle device according to claim 1 or 2. The control unit
If the free space in the storage unit of the other in-vehicle device is less than the capacity of the recorded data, the recorded data is overwritten and saved in an in-vehicle device having a preset high priority among the plurality of other in-vehicle devices mounted on the vehicle .
The in-vehicle device according to claim 1 or 2.