JP2011188176A - Onboard device, system and method for processing data, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To specify a vehicle which has collected video data recorded in a drive recorder. <P>SOLUTION: When a drive recorder 1 stores video data recorded upon occurrence of an accident or the like in a recording medium, the drive recorder 1 generates the data hash value of video data to be written, an immobilizer ECU 2 generates an authentication hash value from the key ID and the data hash value of an automobile key 3 held in secret, and then the drive recorder 1 writes the video data to be written and the authentication hash value in the recording medium. The drive recorder 1 reads the authentication hash value from the recording medium later on, and transmits the authentication hash value and the data hash value to the immobilizer ECU 2. The immobilizer ECU 2 calculates the hash value from the key ID and the data hash value of the automobile key 3, and presumes that the video data in the recording medium has been recorded in the drive recorder 1 if the calculated hash value matches the authentication hash value. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for managing video data and the like taken by a drive recorder device (hereinafter also simply referred to as a drive recorder).

The conventional vehicle history information storage system uses history information together with request information for requesting an encryption key using identification information (ID (Identification) information stored in advance in the memory of the IC chip) attached to the drive recorder. The history information management device stores the identification information and the decryption key in association with each other, and transmits the encryption key corresponding to the decryption key to the drive recorder.
The drive recorder transmits history information (video data, vehicle data, and vehicle peripheral data) and identification information encrypted using the received encryption key, and the history information management device decrypts based on the received identification information. Falsification is prevented by acquiring a key and decrypting history information (video data, vehicle data, and vehicle peripheral data) received using the decryption key (for example, Patent Document 1).

  In addition, another conventional vehicle history information storage system prevents falsification by obtaining a time stamp for a total hash value calculated by processing an entire hash function including authentication information such as acquired video data and input data. (For example, Patent Document 2).

Another conventional vehicle history information storage system calculates a hash value of a read instruction signal, encrypts it with private key information stored in a memory, creates an electronic signature, and reads the read instruction signal, the electronic signature, and the electronic certificate. Is sent to the UIM card and a read request is made to compare hash values 1 and 2 to determine a match.
Then, after the UIM card that received the electronic certificate is authorized, the UIM card reads the stored contents of the vehicle situation in order to transmit the stored contents information to the accident situation analyzing apparatus and read the stored contents of the locked memory. The stored content is encrypted with the transmitted public key information and transmitted.
Then, the accident situation analysis apparatus prevents falsification by decrypting the stored content with the information of the private key of the electronic certificate and reading it out (for example, Patent Document 3).

As a technology different from the drive recorder of the vehicle history information storage system, there is an immobilizer technology as a technology for preventing car theft.
There are two types of communication between an automobile key and an immobilizer ECU (Electronic Control Unit, electronic control unit): a mechanical key type immobilizer and a smart entry type immobilizer.

In the mechanical key type immobilizer, a coil is embedded in a key cylinder mounting portion, and a transponder IC is embedded in a knob (portion held in a hand) of an automobile key.
The transponder has no power supply.
When the power supply communicates with the immobilizer ECU, a certain amount of energy is put on the radio wave generated from the coil by turning the car key, and the power is generated by electromagnetic coupling with the coil embedded in the transponder IC. Yes.
The key ID in the car key is transmitted to the immobilizer ECU wirelessly. If the collation result with the key ID in the immobilizer ECU is OK, the engine is started. If the collation result is NG, the engine is not started (for example, Patent Document 4). Patent Document 5).

  A smart entry type immobilizer is a system in which a battery is built in an automobile key, and the key ID in the automobile key is transmitted wirelessly to the immobilizer ECU using the battery as a power source. The key ID and the automobile key in the immobilizer ECU are periodically transmitted. The key ID is checked and monitored (for example, Patent Document 6).

JP 2003-87234 A JP 2002-215029 A JP 2004-322785 A JP-A-8-80811 JP-A-8-113114 JP 2006-290246 A

The drive recorder of the conventional vehicle history information storage system calculates the recorded video data by encrypting or authenticating using the encryption key or authentication key unique to the drive recorder, or the encryption key or authentication key unique to the user. The video data etc. recorded in the drive recorder are stored after calculation using.
However, specific information for identifying the vehicle from which video data was acquired can be altered even if it is recorded, and it is possible to identify the vehicle from which the data acquired by the drive recorder was collected. There is a problem that it cannot be done.

  The main object of the present invention is to solve the above-described problems, and it is an object of the present invention to specify a vehicle that has collected video data and the like recorded by a drive recorder.

The in-vehicle device according to the present invention is
This is an in-vehicle device that is connected to a drive recorder device that takes a picture on a mounted vehicle and writes specific video data to be written to a predetermined recording medium. And
A storage unit for storing secret information uniquely set in the mounted vehicle;
When the drive recorder device writes the write target video data to the recording medium, the write target video data or data after a predetermined calculation is performed on the write target video data is input from the drive recorder device as calculation target data. An input section;
When the calculation target data is input from the input unit, the calculation target data and the secret information are used to perform a one-way calculation, and the one-way calculation data calculated by the one-way calculation is used as the write target video. A one-way operation data generation unit for generating instruction information for instructing the drive recorder device to write to the recording medium together with data;
And an output unit for outputting the one-way calculation data and the instruction information to the drive recorder device.

  According to the present invention, the drive recorder device writes the one-way calculation data generated using the secret information uniquely set on the mounted vehicle and the calculation target data to the recording medium together with the write target video data. It is possible to verify whether the video data in the recording medium is taken by the drive recorder device of the on-board vehicle by performing verification using the secret information on the one-way calculation data in the medium. .

FIG. 3 is a diagram illustrating a configuration example of an in-vehicle network according to the first embodiment. FIG. 3 shows a configuration example of a drive recorder device according to the first embodiment. FIG. 3 is a diagram illustrating a configuration example of an immobilizer ECU according to the first embodiment. FIG. 3 is a flowchart showing an example of processing when the engine according to Embodiment 1 is started. The flowchart figure which shows the process example at the time of the accident occurrence etc. which concern on Embodiment 1. FIG. FIG. 3 is a diagram illustrating an example of information in a recording medium according to the first embodiment. The flowchart figure which shows the example of a process at the time of the accident data reference using immobilizer ECU which concerns on Embodiment 1. FIG. The flowchart figure which shows the process example at the time of the accident data reference using the data reference apparatus which concerns on Embodiment 1. FIG. The figure which shows the structural example of immobilizer ECU which concerns on Embodiment 2. FIG. The flowchart figure which shows the example of a process at the time of the accident occurrence etc. which concern on Embodiment 2. FIG. FIG. 6 is a diagram illustrating an example of information in a recording medium according to Embodiment 2. The flowchart figure which shows the example of a process at the time of the accident data reference using immobilizer ECU which concerns on Embodiment 2. FIG. FIG. 5 is a diagram illustrating a configuration example of a drive recorder device according to a third embodiment. FIG. 4 is a diagram illustrating a configuration example of an immobilizer ECU according to a third embodiment. FIG. 9 is a flowchart showing an example of processing when an accident occurs according to the third embodiment. The flowchart figure which shows the process example at the time of the accident data reference using the data reference apparatus which concerns on Embodiment 3. FIG.

Embodiment 1 FIG.
FIG. 1 is an in-vehicle network configuration diagram showing a system configuration according to the present embodiment.
In FIG. 1, only elements necessary for the description of the present embodiment, that is, a drive recorder device 1, an immobilizer ECU 2, an automobile key 3, an engine switch 4, an engine ECU 5, an automobile engine unit 6, and an in-vehicle network 7 are illustrated. .
FIG. 1 does not exclude that other elements not shown are connected to the in-vehicle network 7.
Hereinafter, the vehicle on which the elements shown in FIG. 1 are mounted is also referred to as a mounted vehicle.

In FIG. 1, a drive recorder device 1 is a device that records an image and sound at the time of an accident.
The immobilizer ECU 2 is a vehicle antitheft device equipped with a microprocessor and peripheral circuits. The immobilizer ECU 2 is an example of an in-vehicle device.
The car key 3 holds a key ID that is an identifier of the car key, and transmits the key ID to the immobilizer ECU 2 by radio.
The engine switch 4 is a switch for starting the engine.
The engine ECU 5 is a device equipped with a microcomputer for controlling the engine and its peripheral circuits. The engine ECU 5 is an example of an engine control mechanism.
The automobile engine unit 6 is a car engine.
The in-vehicle network 7 is an in-vehicle LAN (Local Area Network) such as a CAN (Controller Area Network) or a FlexRay.

  FIG. 2 is an internal configuration diagram of the drive recorder device 1 according to the present embodiment.

In FIG. 2, the drive recorder CPU unit 11 is a microprocessor.
The drive recorder digital camera unit 12 is a digital camera that captures images outside the vehicle.
The drive recorder ROM unit 13 is a ROM (Read Only Memory) in which a program is stored. The drive recorder CPU unit 11 executes a program in the drive recorder ROM unit 13.
The drive recorder RAM unit 14 is a RAM (Random Access Memory) of a volatile memory such as an SRAM (Static Random Access Memory) or a DRAM (Dynamic Random Access Memory).
The drive recorder communication control unit 15 is a module that controls communication with the in-vehicle network 7.
The drive recorder non-volatile memory unit 16 performs writing / reading to / from a slot of a rewritable recording medium such as an SD (registered trademark) card for recording the copied video.
The drive recorder acceleration sensor unit 17 is a module that determines a collision or sudden stop such as an accident based on acceleration.
The drive recorder timer unit 18 is a clock that provides time information.
The drive recorder data collation instruction button unit 19 is a button for instructing collation of accident data.
The drive recorder data verification result notification LED 20 is an LED (Light Emitting Diode) that emits two or more colors for presenting the verification result of accident data.
The recording medium 21 is a recording medium for recording the copied video.

  FIG. 3 is an internal configuration diagram of the immobilizer ECU 2 according to the present embodiment.

In FIG. 3, the immobilizer CPU unit 31 is a microprocessor.
The immobilizer CPU unit 31 executes a program stored in an immobilizer ROM unit 36 described later.
Although details will be described later, the immobilizer CPU unit 31 functions as a one-way calculation data generation unit, a verification processing unit, and an ID determination unit by executing a program in the immobilizer ROM unit 36.

The immobilizer EEPROM unit 32 is an EEPROM (Erasable Programmable ROM) that cannot be easily rewritten.
The immobilizer EEPROM unit 32 stores a vehicle number 33, an encryption key 34, and a key ID 35.
The vehicle number 33 is an identifier of a vehicle (mounted vehicle) on which the immobilizer ECU 2 is mounted. The car number 33 is, for example, a manufacturing number.
The encryption key 34 is a key for decrypting the key ID of the encrypted car (mounted vehicle) key.
The key ID 35 is an identifier of the key of the automobile (mounted vehicle).
The key ID 35 is an ID uniquely set for the mounted vehicle and is kept secret.
The key ID 35 is an example of secret information and a vehicle key ID.
The immobilizer EEPROM unit 32 is an example of a storage unit.
The uniqueness of the key ID 35 means that there is no other car key having that ID.

The immobilizer ROM unit 36 is a ROM that stores a program.
The immobilizer RAM unit 37 is a RAM of volatile memory such as SRAM or DRAM.

The immobilizer wired control unit 38 is a module that controls communication with the in-vehicle network 7.
More specifically, the immobilizer wired control unit 38 inputs data from the drive recorder device 1 through the in-vehicle network 7 and outputs data to the drive recorder device 1 through the in-vehicle network 7.
The immobilizer wired control unit 38 is an example of an input unit and an output unit.
In the following description, the expression that the immobilizer wired control unit 38 inputs (or receives) data from the drive recorder device 1 and the expression that the immobilizer wired control unit 38 outputs (or transmits) data to the drive recorder device 1 are also used. Although used, these input (reception) and output (transmission) mean the input (reception) and output (transmission) via the in-vehicle network 7.

The immobilizer wireless control unit 39 is a module that controls wireless communication and receives ID information.
The immobilizer radio control unit 39 is an example of an ID information receiving unit.
The immobilizer amplifier unit 40 is a module that amplifies a wireless signal through wireless communication.
The immobilizer antenna 41 is an antenna for performing wireless communication with the outside of the immobilizer ECU 2.

  Here, the outline | summary of operation | movement of the drive recorder apparatus 1 which concerns on this Embodiment, immobilizer ECU2, etc. is demonstrated.

When the engine is started, the immobilizer wireless control unit 39 receives ID information by wireless communication.
The immobilizer CPU unit 31 determines whether or not the ID information matches the key ID 35 stored in the immobilizer EEPROM unit 32. If the ID information matches, the ID information is transmitted from the correct vehicle key 3. As you can see, allow the engine to start.
In addition, the immobilizer CPU unit 31 holds a verification result that the ID information matches the key ID 35.
Since the automobile key 3 transmits the ID information in an encrypted state, the immobilizer CPU unit 31 decrypts the received ID information with the encryption key 34 and collates it with the key ID 35.

When the engine is activated, the drive recorder digital camera unit 12 of the drive recorder device 1 performs shooting outside the vehicle.
Then, when the drive recorder acceleration sensor unit 17 detects the occurrence of an accident or an acceleration of a predetermined level or more due to a sudden handle for avoiding the accident or the like, a predetermined time before the detection of the acceleration in the captured video data. Is the video data to be written to the recording medium 21.
The drive recorder CPU unit 11 of the drive recorder device 1 performs a hash operation on the video data to be written to generate a hash value.
Hereinafter, this hash value is referred to as a data hash value XXX.

In the immobilizer ECU 2, the immobilizer CPU unit 31 inputs a data hash value XXX (example of calculation target data) from the drive recorder device 1 via the immobilizer wired control unit 38.
The immobilizer CPU unit 31 refers to the query result when the engine is started, and if the collation result indicates that the ID information matches the key ID 35, the hash calculation (example of one-way calculation) is performed on the data hash value XXX and the key ID 35. Go to generate a hash value.
Hereinafter, this hash value is referred to as an authentication hash value YYY (an example of one-way calculation data).
In addition, the immobilizer CPU unit 31 generates instruction information that instructs the drive recorder device 1 to write the authentication hash value YYY and the car number 33 to the recording medium 21.
Then, the immobilizer CPU unit 31 outputs the authentication hash value YYY, the car number 33, and the instruction information to the drive recorder device 1 via the immobilizer wired control unit 38.

In the drive recorder device 1, the drive recorder non-volatile memory unit 16 writes the authentication hash value YYY and the car number 33 to the recording medium 21 together with the video data to be written in accordance with the instruction information from the immobilizer CPU unit 31.
Further, the drive recorder nonvolatile memory unit 16 may write the data hash value XXX into the recording medium 21.

After the accident, if the recording medium 21 is removed from the drive recorder device 1 or if the driver or passenger leaves the mounted vehicle even if the recording medium 21 is stored in the drive recorder device 1, the video recorded on the recording medium 21 It is necessary to verify whether the data is collected by the onboard vehicle (whether the video data or car number has been tampered with).
For example, it is conceivable that such verification work is necessary when video data is used as evidence in a court procedure for an accident, an insurance claim procedure, or the like.
The authentication hash value YYY in the recording medium 21 is a hash value for the data hash value XXX and the key ID 35, and the key ID 35 is in the immobilizer EEPROM unit 32 of the immobilizer ECU 2.
Since the immobilizer EEPROM unit 32 is tamper resistant, the key ID 35 cannot be taken out of the immobilizer EEPROM unit 32.
For this reason, the above-described verification work is performed by the immobilizer ECU 2.
Specifically, first, the drive recorder nonvolatile memory unit 16 reads the authentication hash value YYY from the recording medium 21 (verification target recording medium).
When the data hash value XXX is present in the recording medium 21, the drive recorder nonvolatile memory unit 16 may read the data hash value XXX from the recording medium 21.
When video data (stored video data) is stored in the recording medium 21, the drive recorder CPU 11 performs a hash operation on the video data (stored video data) to generate a data hash value XXX. Also good.
Then, the drive recorder communication control unit 15 outputs the data hash value XXX (example of verification calculation target data) and the authentication hash value YYY (example of verification one-way calculation data) to the immobilizer ECU 2.

In the immobilizer ECU 2, the immobilizer CPU unit 31 inputs the data hash value XXX and the authentication hash value YYY from the drive recorder device 1 via the immobilizer wired control unit 38.
Then, the immobilizer CPU unit 31 performs a hash operation on the data hash value XXX and the key ID 35 in the immobilizer EEPROM unit 32, and collates the calculated value by the hash operation with the input authentication hash value YYY.
If the calculated value matches the authentication hash value YYY, the immobilizer CPU unit 31 determines that the video data recorded on the recording medium 21 is collected by the mounted vehicle.
As described above, the key ID 35 is not leaked from the immobilizer EEPROM unit 32, and the authentication hash value YYY when the accident occurs (or when the accident is avoided) is calculated in the immobilizer ECU 2. Therefore, the possibility that a third party can forge a hash value having the same value as the authentication hash value YYY is extremely low.
For this reason, in the verification process in the immobilizer CPU unit 31, when the hash calculation value and the authentication hash value YYY input from the recording medium 21 match, the video data recorded on the recording medium 21 is collected by the mounted vehicle. You may think.

The above is the outline of the operations of the drive recorder device 1 and the immobilizer ECU 2 according to the present embodiment.
Next, details of operations of the drive recorder device 1, the immobilizer ECU 2, and the like will be described using a flowchart and the like.

  FIG. 4 is a flowchart of processing at the time of engine startup in the present embodiment.

  FIG. 5 is a flowchart of a process when a collision or a sudden stop occurs due to a car accident or the like in the present embodiment.

FIG. 6 is a diagram showing information of the recording medium 21 in the drive recorder nonvolatile memory unit 16.
In FIG. 6, a recording medium 21 is a recording medium such as an SD (registered trademark) card or a USB (Universal Serial Bus) memory.
The video data 52 is a video recorded by the drive recorder device 1.
The time information 53 is information representing the time when the accident occurred.
The data hash value XXX54 is a hash value obtained by calculating the video data 52 with a hash function.
The data hash value XXX54 corresponds to the data hash value XXX described in the above overview.
The authentication hash value valid / invalid flag 55 is flag information indicating whether the authentication hash value is valid / invalid.
The authentication hash value YYY56 is a hash value obtained by calculating the data hash value XXX54 and the data of the key ID 35 using a hash function.
The authentication hash value YYY56 corresponds to the authentication hash value YYY described in the above overview.
The vehicle information 33 is a production number for identifying a vehicle held in the immobilizer ECU 2.

  FIG. 7 is a flowchart of the process at the time of accident data collation by the immobilizer ECU 2.

FIG. 8 is a flowchart of a process at the time of accident data collation using the data collation apparatus.
The data verification device is not shown in FIG.
The data verification device is a device owned by the manufacturer of the vehicle and the dealer sales dealer.
Although details of the data verification device will be described later, this is an example of a verification device.

Next, the operation in the present embodiment will be described in detail.
First, the process at the time of engine startup will be described with reference to FIG.
There are two types of communication between the car key 3 and the immobilizer ECU 2: a mechanical key type immobilizer and a smart entry type immobilizer. An example of a smart entry type immobilizer will be described below.

The automobile key 3 periodically transmits an encryption key ID, which is an encrypted key ID, to the immobilizer ECU 2 (S01).
The immobilizer ECU 2 receives the encryption key ID (ID information) (S02).
The encryption key ID is written to the immobilizer RAM unit 37 via the immobilizer antenna 41 and the immobilizer amplifier unit 40 and the immobilizer radio control unit 39.
The immobilizer CPU unit 31 detects that the encryption key ID has been received from the vehicle key 3 based on the notification from the immobilizer wireless control unit 39.
The immobilizer CPU unit 31 reads the encryption key 34 from the immobilizer EEPROM unit 32, decrypts the encryption key ID using the encryption key 34, and extracts the key ID (S03).
The immobilizer CPU unit 31 collates the key ID 35 held in the immobilizer EEPROM unit 32 with the decrypted key ID, determines a key ID collation result (OK if coincidence / NG if not coincidence), and key ID collation result OK / NG is held in the immobilizer RAM unit 37 (S04).
The user of the automobile switches on the engine switch 4 (S05).
The engine ECU 5 detects that the engine switch 4 is switched on and starts an engine program (S06).
The engine ECU 5 issues an engine start notification to the automobile engine unit 6 (S07).
The car engine unit 6 starts the engine (S08).
The engine ECU 5 transmits a key ID verification result inquiry notification to the immobilizer ECU 2 (S09).
The key ID verification result inquiry notification is notified to the immobilizer CPU unit 31 via the immobilizer wired control unit 38.
The immobilizer CPU unit 31 in the immobilizer ECU 2 reads the key ID verification result (OK / NG) held in the immobilizer RAM unit 37 (S10), and sends the key ID verification result to the engine ECU 5 via the immobilizer wired control unit 38. Notification is made (S11).
The engine ECU 5 continues to start the engine if the key ID verification result returned from the immobilizer ECU 2 is OK (S12), and stops the engine startup if the key ID verification result is NG. Is notified of the key ID verification result notification NG (S13).
If the key ID verification result is NG, the automobile engine unit 6 receives the key ID verification result notification NG and stops the engine start (S14).

  Next, operations of the drive recorder device 1 and the immobilizer ECU 2 at the time of an accident caused by a vehicle will be described with reference to FIG.

The car key 3 transmits the encryption key ID (S21), the immobilizer ECU 2 receives the encryption key ID (S22), the immobilizer ECU 2 decrypts the received encryption key ID using the encryption key 34, and the key ID (S23), the key ID 35 held in the immobilizer EEPROM unit 32 is collated with the received key ID, the key ID collation result OK / NG is determined, and the key ID collation result OK / NG is determined as the immobilizer RAM unit 37. The operation up to (S24) is the same as the operation from S01 to S04 in FIG.
Since the key IDs are collated in the processes of S01 to S04 when the engine is started, the processes of S21 to S24 may be omitted.

The drive recorder device 1 always records video with the drive recorder digital camera unit 12 at normal times when no accident occurs, and records the recorded video data in the drive recorder RAM unit 14.
Since the drive recorder RAM unit 14 has a limited memory capacity, it constantly overwrites the old video data and writes and holds the latest data (S25).

From here, the operation when a collision such as a car accident or a sudden stop occurs will be described.
A large acceleration is generated in the vehicle due to an accident shock or sudden operation for avoiding the accident (S26).
The drive recorder acceleration sensor unit 17 in the drive recorder device 1 determines an accident by the acceleration sensor and notifies the drive recorder CPU unit 11 of the accident.
The drive recorder CPU unit 11 writes the video data recorded in the drive recorder RAM unit 14 as video data 52 to the recording medium 21 of the drive recorder nonvolatile memory unit 16 (S27).
At this time, the drive recorder CPU unit 11 acquires the time information of the year, month, day and time from the drive recorder timer unit 18 and records the video data 52 to the recording medium 21 of the drive recorder nonvolatile memory unit 16 together with the video data of the accident. Write as time information 53.
The drive recorder CPU unit 11 calculates the data hash value XXX of the video data including the written time information (S28).
The data hash value is calculated using SHA1 (Secure Hash Algorithm 1), which is a one-way function, HMAC-SHA1 (Keyed-Hashing for Message Authentication SHA1), which is a hash algorithm with a key, or the like.
The drive recorder CPU unit 11 transmits the data hash value XXX as an authentication hash value generation request to the immobilizer ECU 2 via the drive recorder communication control unit 15 (S29).

The immobilizer CPU unit 31 receives the data hash value XXX as an authentication hash value generation request via the immobilizer wired control unit 38, and the immobilizer CPU unit 31 stores the key ID verification result (OK / NG stored in the immobilizer RAM unit 37. ) Is read (S30).
Only when the key ID collation result is OK, the immobilizer CPU unit 31 reads the key ID 35 from the immobilizer EEPROM unit 32, combines the received data hash value XXX and the key ID 35 on the memory, and calculates the authentication hash value YYY. (S31).
The algorithm for calculating the authentication hash value YYY is calculated using a hash algorithm such as SHA1 that is a one-way function or HMAC-SHA1 that is a hash algorithm with a key.
If the key ID verification result is OK, the vehicle number 33 is read from the immobilizer EEPROM unit 32.
On the other hand, when the key ID collation result is NG, the immobilizer CPU unit 31 generates an error notification.
Then, the immobilizer CPU unit 31 notifies the drive recorder device 1 of an authentication hash value generation response via the immobilizer wired control unit 38 (S32).
If the key ID verification result is OK, an authentication hash value generation response including instruction information for instructing to write the car number 33 and the authentication hash value YYY and the car number 33 and the authentication hash value YYY to the recording medium 21 is transmitted. The
On the other hand, when the key ID verification result is NG, an authentication hash value generation response including an error notification is transmitted.

The drive recorder CPU unit 11 receives the authentication hash value generation response result (OK / NG) via the drive recorder communication control unit 15.
If the result of the authentication hash value generation response is OK, the drive recorder CPU unit 11 sets the authentication hash value valid / invalid flag 55 as valid, and sets the authentication hash value valid / invalid flag 55, the car number 33, and the authentication hash value YYY56. Write to the recording medium 21 of the drive recorder non-volatile memory unit 16 (S33).
If the result of the authentication hash value generation response is NG, the drive recorder CPU unit 11 sets the authentication hash value valid / invalid flag 55 as invalid, and records the authentication hash value valid / invalid flag 55 in the drive recorder nonvolatile memory unit 16. Writing to the medium 21 (S33).

FIG. 6 is a diagram of the recording medium 21 in the drive recorder nonvolatile memory unit 16.
When the result of the accident is that the immobilizer ECU 2 returns OK as the result of the authentication hash value generation response, all data remains as a record of the accident.
The data hash value XXX54 may not be stored in the recording medium 21.
When the immobilizer ECU 2 returns NG as the result of the authentication hash value generation response, the authentication hash value valid / invalid flag 55 is set invalid, and the area of the vehicle number 33 and the authentication hash value YYY56 is invalid.

  Next, regarding the vehicle that has acquired the video data stored in the recording medium 21 of the drive recorder nonvolatile memory unit 16 and the information of the data hash value XXX, is the data acquired by the vehicle to which the drive recorder device 1 is currently attached? A procedure for verifying whether or not will be described with reference to FIG.

  The car key 3 transmits the encryption key ID (S41), and the immobilizer ECU 2 decrypts the received encryption key ID using the encryption key 34, extracts the key ID (S43), and holds it in the immobilizer EEPROM 32. The operation until the key ID 35 and the received key ID are collated, the key ID collation result OK / NG is determined, and the key ID collation result OK / NG is held in the immobilizer RAM unit 37 (S44) is shown in S01 of FIG. It is the same as the operation up to S04.

The user inserts the recording medium 21 into the drive recorder non-volatile memory unit 16.
Here, it is assumed that the video data, the data hash value XXX, the car number 33, and the authentication hash value YYY are recorded on the drive recorder device 1 on the recording medium 21, but the data hash value XXX is recorded on the recording medium as described above. 21 may not be present.
The user instructs collation of accident data by pressing the drive recorder data collation instruction button 19 (S45).

The drive recorder CPU unit 11 detects that the button has been pressed down from the drive recorder data collation instruction button unit 19 and displays the data hash value XXX, the authentication hash value YYY, and the authentication hash value valid / invalid flag in the drive recorder non-volatile memory unit 16. Is read from the recording medium 21 (S46).
When the read authentication hash value validity / invalidity flag is set to invalid, the drive recorder CPU unit 11 lights the drive recorder data collation result notification LED 20 in red (S51).
When the read authentication hash value valid / invalid flag is set to valid, the drive recorder CPU unit 11 sends the data hash value XXX and the authentication hash value to the immobilizer ECU 2 via the drive recorder communication control unit 15 as an authentication hash value collation request. YYY is transmitted (S47).

The immobilizer CPU unit 31 receives the data hash value XXX and the authentication hash value YYY via the immobilizer wired control unit 38, and the immobilizer CPU unit 31 receives the key ID verification result (OK / NG) held in the immobilizer RAM unit 37. Read (S48).
When the key ID collation result is OK, the immobilizer CPU unit 31 performs the hash calculation by the same algorithm as the hash calculation algorithm at the time of the accident from the data hash value XXX and the key ID, and calculates and receives the authentication hash value YYY. The authentication hash value YYY is collated, and the collation result of the hash value is determined as (OK if matched / NG if not matched) (S49).
If the key ID verification result is NG, the hash value verification result is NG (S49).
The immobilizer CPU unit 31 transmits a hash value verification result notification (OK / NG) to the drive recorder device 1 via the immobilizer wired control unit 38 as an authentication hash value verification response (S50).

  The drive recorder CPU unit 11 receives the hash value verification result notification (OK / NG) via the drive recorder communication control unit 15, and if the hash value verification result notification is OK, the drive recorder data verification result notification LED 20 When the hash value verification result notification is NG, the drive recorder data verification result notification LED 20 is lit red (S51).

The user acquires the video data stored in the recording medium 21 of the drive recorder non-volatile memory unit 16 when the drive recorder data verification result notification LED 20 is lit blue / red, and the drive recorder device 1 is currently attached. To determine if it is a car.
When the light is blue, it is determined that the vehicle at the time of data acquisition matches the vehicle to which the drive recorder device 1 is attached.
If the light is red, it is determined that the vehicle at the time of data acquisition does not match the vehicle to which the drive recorder device 1 is attached.

In the above description, the drive recorder CPU unit 11 reads the data hash value XXX from the recording medium 21 and transmits the read data hash value XXX together with the authentication hash value YYY to the immobilizer ECU 2.
Instead, the drive recorder CPU unit 11 reads the video data from the recording medium 21, performs a hash operation on the video data, generates a hash value having the same value as the data hash value XXX, and uses this hash value. You may make it transmit to immobilizer ECU2.

  Next, with reference to FIG. 8, the operation of the data verification device held by the car manufacturer or the dealer sales dealer will be described.

The data collating apparatus sells a car and simultaneously holds a set of a car number and a key ID in advance (S61).
The combination of the car number and the key ID is different for each sold car, and the car number is a number that can be uniquely identified by a different number.

The user takes out the recording medium 21 storing the data hash value XXX, the car number, and the authentication hash value YYY from the drive recorder nonvolatile memory unit 16 of the drive recorder device 1 (S62).
The user reads the data hash value XXX, the car number, and the authentication hash value YYY from the recording medium 21 with a personal computer (hereinafter referred to as a personal computer).
If invalidity is set in the read authentication hash value valid / invalid flag, the personal computer displays the vehicle number and verification result (NG) on the personal computer display (S67).
The personal computer sends the data hash value XXX, the authentication hash value YYY, and the vehicle number (an example of the verification vehicle ID) to the data verification device via the network (S63).

The data verification device reads the key ID that forms a set from the vehicle number (S64).
Next, the data verification device calculates an authentication hash value YYY by hash calculation from the data hash value XXX and the key ID, and compares the received authentication hash value YYY with the calculated authentication hash value YYY, and the hash value verification result (OK) / NG) is determined (S65).
The calculation algorithm of the authentication hash value YYY in the data collating device is the same as the hash calculation algorithm when the immobilizer CPU unit 31 generates the authentication hash value YYY when an accident occurs.
The data verification device returns a hash value verification result notification (OK / NG) to the personal computer via the network (S66).

The personal computer receives the hash value collation result notification (OK / NG) and displays the vehicle number and collation result on the personal computer display (S67).
When the hash value collation result notification is OK by the hash value collation result notification (OK / NG) from the data collation device, the user is connected to the vehicle in which the drive recorder device 1 that collected the video at the time of the accident was attached. Get information.

As described above, the user can obtain an effect of verifying that the video data is recorded and stored in the car having the saved car number.
In the above-described operation example of the data collating apparatus, the example in which the personal computer and the data collating apparatus are connected via the network is described. However, the recording medium storing the data hash value XXX, the car number, and the authentication hash value YYY The user can obtain the same effect by inserting 21 into the data verification device, reading the data hash value XXX, the car number, and the authentication hash value YYY, and displaying the hash value verification result on the display of the data verification device.
Even in the case of using the data collating apparatus of FIG. 8, the user's personal computer reads the video data instead of reading the data hash value XXX from the recording medium 21, performs a hash operation on the video data, and performs the data hash value XXX. It is also possible to generate a hash value having the same value as and send this hash value to the data collating device.

  In the above description, the video data including the time information is stored as data to be saved by the drive recorder device 1 at the time of the accident. However, the audio data, vehicle data, and vehicle peripheral data recorded using the microphone are the same as the video data. As a treatment, the same effect can be obtained even if the data hash value XXX is hash-calculated.

  In the present embodiment, an example of a smart entry type immobilizer has been described. However, a mechanical key type immobilizer can also be realized by the same operation, and the same effect can be obtained.

In the present embodiment, the drive recorder normally records the video data, vehicle data, and vehicle peripheral data in the memory, and when the sudden stop is detected by the acceleration sensor, the video data and the vehicle data are transferred from the memory to the medium. The example in which the vehicle peripheral data is moved and transferred is described.
Instead, normally, video data, vehicle data, and vehicle peripheral data are recorded in a memory, and even if an emergency stop such as an accident does not occur, the video data, vehicle data, and vehicle peripheral data are read from the memory. Overwrite in order from the oldest data above, when a sudden stop is detected by the acceleration sensor, overwriting to the video data on the medium, vehicle data, and vehicle surrounding data is stopped, and the data on the medium is prohibited from being overwritten. The same effect can be obtained by calculating the data hash value.

Further, in the present embodiment, when an accident occurs, a series of processing sequences of FIG. 5 are executed with a sudden stop by the acceleration sensor of the drive recorder acceleration sensor unit 17.
Instead, a video data storage button is provided in the drive recorder device 1, and when the user depresses the video data storage button, the drive recorder CPU unit 11 triggers the video data storage button to be depressed as a series of FIG. Even if the processing sequence is executed, the same effect is obtained.

In this embodiment, the drive recorder device 1 uses the LED lamp display as the display means for displaying the verification result of the authentication hash value to the user. However, the voice recorder or sound notification means is used. Also good.
Or you may notify to a user by notifying other apparatuses, such as a car navigation system, via a network.
When the car navigation system receives the verification result of the authentication hash value, the car navigation system displays the result of the authentication hash value matching response to the user.

In the present embodiment, the drive recorder device 1 performs a hash operation on the video data to be written and outputs the data hash value XXX to the immobilizer ECU 2. The immobilizer ECU 2 hashes the data hash value XXX and the key ID. An authentication hash value YYY is generated by performing an operation.
Instead, the drive recorder device 1 outputs the write target video data itself to the immobilizer ECU 2, and the immobilizer ECU 2 performs a hash operation on the write target video data and the key ID to generate an authentication hash value YYY. Also good.
In the present embodiment, similarly, at the time of collation, the drive recorder device 1 outputs the data hash value XXX to the immobilizer ECU 2, and the immobilizer ECU 2 performs a hash operation on the data hash value XXX and the key ID to perform the authentication hash. A value YYY is generated.
Instead, the drive recorder device 1 outputs the stored video data to be verified itself to the immobilizer ECU 2, and the immobilizer ECU 2 performs a hash operation on the stored video data to be verified and the key ID to generate an authentication hash value YYY. You may make it do.

As described above, in the present embodiment, the vehicle history information storage system including the following means has been described.
(A) Means for calculating data hash values of video data, vehicle data and vehicle peripheral data stored in a medium or memory using a hash algorithm, and writing the hash values to the medium or memory. (B) Data hash value and engine activation Means for calculating an authentication hash value using a hash algorithm from an automobile key ID for use (c) means for writing a car identification number and an authentication hash value different from the car key ID into a medium or a memory (d) a data verification instruction by a user (E) means for reading a data hash value stored in a medium or memory, a number for identifying a vehicle, and an authentication hash value; (f) calculating an authentication hash value from the data hash value and the vehicle key ID; Or, verify the authentication hash value read from the memory with the calculated authentication hash value. , Match / mismatch means for determining (g) display means for displaying to the user a match / mismatch of the authentication hash value or notifying means by voice or sound or means for notifying via the network to another device,.

Moreover, in this Embodiment, the vehicle history information storage system provided with the following means was further demonstrated.
(A) In normal times, video data, vehicle data, and vehicle periphery data are recorded in a memory, and video data is transferred from the memory to the medium when detection of an approaching vehicle distance or the like or a sudden stop is detected by an acceleration sensor to prevent accidents. The vehicle data and the vehicle peripheral data are moved and transferred, or the video data, the vehicle data, and the vehicle peripheral data are normally recorded in the memory, and the video data and the vehicle are transferred from the memory to the medium at any operation of the user. Data and vehicle peripheral data can be moved and transferred, or normally, video data, vehicle data, and vehicle peripheral data can be recorded in memory, and video data and vehicle data can be stored even if an emergency stop does not occur. And vehicle peripheral data are read from the memory, and the oldest data on the medium is overwritten and recorded in order. When an emergency stop is detected by the sensor, overwriting of the video data, vehicle data, and vehicle surrounding data on the medium is stopped, or in normal times, the video data, vehicle data, and vehicle surrounding data are recorded in the memory, and an accident occurs. Even if a sudden stop does not occur, the video data, vehicle data, and vehicle peripheral data are read from the memory, overwritten in order from the old data on the medium, and when the user performs any operation, the video data on the medium Means for stopping overwriting of vehicle data and vehicle surrounding data.

Moreover, in this Embodiment, the vehicle history information storage system provided with the following means was demonstrated.
(A) The drive recorder uses a hash algorithm to calculate the data hash value of the video data, vehicle data, and vehicle peripheral data stored in the medium or memory, and writes the hash value to the medium. (B) The drive recorder Means for transmitting the calculated data hash value to the immobilizer ECU as an authentication hash value generation request (c) The immobilizer ECU that has received the data hash value as the authentication hash value generation request uses the data hash value and the vehicle key ID for starting the engine. Means for calculating an authentication hash value using a hash algorithm (d) In the immobilizer ECU, means for transmitting an authentication hash value and a number for identifying a vehicle different from the vehicle key ID as an authentication hash value generation response (e) In the drive recorder, Authentication hash Means for receiving vehicle identification number and authentication hash value from immobilizer ECU as generation response (f) In drive recorder, means for writing vehicle identification number and authentication hash value to medium (g) In drive recorder, drive recorder Means for detecting a data collation instruction button input by a user's depression of the user (h) In the drive recorder, means for reading out the data hash value stored in the medium, the vehicle identification number and the authentication hash value from the medium (i) the drive recorder Then, means (j) for transmitting the read data hash value and the authentication hash value to the immobilizer ECU as an authentication hash value verification request. (J) In the immobilizer ECU that has received the data hash value and the authentication hash value as the authentication hash value verification request, Value and car Means for calculating an authentication hash value from the ID, comparing the received authentication hash value with the calculated authentication hash value, and determining a match / mismatch (k) In the immobilizer ECU, the authentication hash value match response Means for transmitting mismatch (l) In drive recorder, means for receiving match / mismatch of authentication hash value from immobilizer ECU as authentication hash value verification response (m) In drive recorder, match / mismatch of authentication hash value Display means for displaying to other users, notification means by voice or sound, or means for notifying other devices via a network.

Moreover, in this Embodiment, the vehicle history information storage system provided with the following means was further demonstrated.
(A) Normally, the drive recorder records video data, vehicle data, and vehicle surrounding data in the memory, and from the memory to the medium when detecting an approaching distance or detecting a sudden stop by the acceleration sensor to prevent accidents. Video data, vehicle data, and vehicle periphery data can be moved and transferred, or normally, the drive recorder records the video data, vehicle data, and vehicle periphery data in the memory, and from the memory at any user operation Move video data, vehicle data, and vehicle surrounding data to the medium and transfer them to the medium. Ordinarily, the video data, vehicle data, and vehicle surrounding data are recorded in the memory, so that there is no need for a sudden stop such as an accident. Video data, vehicle data, and vehicle peripheral data are read from the memory, and are overwritten in order from the oldest data on the medium to prevent accidents. Therefore, when detecting an approaching distance between vehicles or a sudden stop by an acceleration sensor, overwriting of the video data, vehicle data, and vehicle surrounding data on the medium is stopped. Record vehicle data and vehicle periphery data in memory, even if an emergency stop such as an accident does not occur, read video data, vehicle data, and vehicle periphery data from memory, and overwrite and record in order from the old data on the medium, Means for stopping overwriting of video data, vehicle data, and vehicle peripheral data on the medium at any operation of the user.

Embodiment 2. FIG.
In the first embodiment described above, the time information of the accident occurrence time is acquired in the drive recorder and stored in the medium. Next, the position information and time information are stored in the immobilizer ECU. 1 shows an embodiment of a drive recorder.

The in-vehicle network configuration according to the present embodiment is the same as in FIG.
The internal configuration of the drive recorder device 1 according to the present embodiment is the same as that shown in FIG.

  FIG. 9 is an internal configuration diagram of the immobilizer ECU 2 according to the present embodiment.

9 is the same as that shown in FIG. 3 except for an immobilizer GPS (Global Positioning System) unit 42.
That is, the immobilizer CPU unit 31 is a microprocessor, and the immobilizer EEPROM unit 32 is an EEPROM that cannot be easily rewritten.
The car number 33 is a manufacturing number for identifying the car, the encryption key 34 is a key for decrypting the encrypted car key, and the key ID 35 is information on the car key.
The immobilizer ROM unit 36 is a ROM in which a program is stored, and the immobilizer RAM unit 37 is a RAM of a volatile memory such as SRAM or DRAM.
The immobilizer wired control unit 38 is a module that controls communication with the in-vehicle network 7.
The immobilizer wireless control unit 39 is a module that controls wireless communication with the automobile key 3, the immobilizer amplifier unit 40 is a module that amplifies a wireless signal through wireless communication, and the immobilizer antenna 41 is wirelessly communicated with the vehicle key 3. It is an antenna for doing.
The immobilizer GPS unit 42 is a module that receives position information and time information from a satellite.
The immobilizer GPS unit 42 is an example of a positioning unit.

  FIG. 10 is a flowchart of the processing when a collision such as a car accident or a sudden stop occurs in the present embodiment.

FIG. 11 is a diagram showing information on a medium in the drive recorder nonvolatile memory unit 16.
In FIG. 11, a recording medium 21 is a recording medium such as an SD (registered trademark) card or a USB memory.
The information in the recording medium 21 in FIG. 11 is the same as that shown in FIG. 6 except for the position information 58 and time information # 2 (59).
That is, the video data 52 is a video recorded by the drive recorder device 1.
The data hash value XXX54 is a hash value obtained by calculating the video data 52 with a hash function.
The authentication hash value valid / invalid flag 55 is flag information indicating whether the authentication hash value is valid / invalid.
The authentication hash value YYY56 is a hash value obtained by calculating the data hash value XXX54 and the data of the key ID 35 using a hash function.
Time information # 1 (57) is time information collected by the drive recorder device 1 when an accident occurs.
The position information 58 is information indicating the position by GPS at the time of occurrence of the accident.
Time information # 2 (59) is time information collected by the immobilizer ECU 2 when the accident occurred.
The car number 33 is a manufacturing number for identifying the car held in the immobilizer ECU 2.

  FIG. 12 is a flowchart of a process when collating accident data with a vehicle in the present embodiment.

  Next, operations of the drive recorder device 1 and the immobilizer ECU 2 at the time of an accident caused by a vehicle will be described with reference to FIG.

The car key 3 transmits the encryption key ID (S81), the immobilizer ECU 2 receives the encryption key ID (S82), the immobilizer ECU 2 decrypts the received encryption key ID using the encryption key 34, and obtains the key ID. Extraction (S83), the key ID 35 held in the immobilizer EEPROM unit 32 is collated with the received key ID, the key ID collation result (OK when matched / NG when not matched) is determined, and the key ID collation result OK / NG is held in the immobilizer RAM unit 37 (S84).
Note that since the key IDs are collated in the processes of S01 to S04 at the time of starting the engine described in the first embodiment, the processes of S81 to S84 may be omitted.

The drive recorder device 1 always records video with the drive recorder digital camera unit 12 at normal times when no accident occurs, and records the recorded video data in the drive recorder RAM unit 14.
Since the drive recorder RAM section 14 has a limited memory capacity, it constantly overwrites the old video data and writes and holds the latest data (S85).

From here, the operation when a collision such as a car accident or a sudden stop occurs will be described.
A large acceleration is generated in the vehicle due to an accident shock or a sudden operation for avoiding the accident (S86).
The drive recorder acceleration sensor unit 17 in the drive recorder device 1 determines an accident by the acceleration sensor and notifies the drive recorder CPU unit 11 of the accident.
The drive recorder CPU unit 11 writes the video data recorded in the drive recorder RAM unit 14 to the recording medium 21 of the drive recorder nonvolatile memory unit 16 (S87).
At this time, the drive recorder CPU unit 11 acquires the time information # 1 of the year / month / day / time from the drive recorder timer unit 18, and the video data to the recording medium 21 of the drive recorder non-volatile memory unit 16 together with the video data of the accident. 52 and time information # 1 (57).
The drive recorder CPU unit 11 calculates the data hash value XXX of the video data including the written time information # 1 (S88).
Note that the data hash value is calculated using SHA1, which is a one-way function, HMAC-SHA1, which is a hash algorithm with a key, and the like.
The drive recorder CPU unit 11 transmits the data hash value XXX as an authentication hash value generation request to the immobilizer ECU 2 via the drive recorder communication control unit 15 (S89).

The immobilizer CPU unit 31 receives the data hash value XXX as an authentication hash value generation request via the immobilizer wired control unit 38, and the immobilizer CPU unit 31 stores the key ID verification result (OK / NG) held in the immobilizer RAM unit 37. Is read (S90).
The immobilizer CPU unit 31 acquires position information and time information # 2 from the immobilizer GPS unit 42 only when the key ID collation result is OK (S91).
Only when the key ID collation result is OK, the immobilizer CPU unit 31 reads the key ID 35 from the immobilizer EEPROM unit 32, and combines the received data hash value XXX, position information, time information # 2, and key ID 35 on the memory, An authentication hash value YYY is calculated (S92).
The algorithm for calculating the authentication hash value YYY is calculated using a hash algorithm such as SHA1 that is a one-way function or HMAC-SHA1 that is a hash algorithm with a key.
If the key ID verification result is OK, the vehicle number 33 is read from the immobilizer EEPROM unit 32.
On the other hand, when the key ID collation result is NG, the immobilizer CPU unit 31 generates an error notification.
Then, the immobilizer CPU unit 31 notifies the drive recorder device 1 of an authentication hash value generation response via the immobilizer wired control unit 38 (S93).
When the key ID collation result is OK, an authentication hash value generation response including the car number 33, the authentication hash value YYY, the position information, the time information # 2, and the instruction information instructing to write these into the recording medium 21 is received. Sent.
On the other hand, when the key ID verification result is NG, an authentication hash value generation response including an error notification is transmitted.

The drive recorder CPU unit 11 receives the authentication hash value generation response result (OK / NG) via the drive recorder communication control unit 15.
If the result of the authentication hash value generation response is OK, the drive recorder CPU unit 11 sets the authentication hash value valid / invalid flag 55 as valid, sets the authentication hash value valid / invalid flag 55, the car number 33, the authentication hash value YYY56, The position information 58 and time information # 2 (59) are written to the recording medium 21 of the drive recorder nonvolatile memory unit 16 (S94).
If the result of the authentication hash value generation response is NG, the drive recorder CPU unit 11 sets the authentication hash value valid / invalid flag 55 as invalid, and records the authentication hash value valid / invalid flag 55 in the drive recorder nonvolatile memory unit 16. Writing to the medium 21 (S94).

  Next, it is verified whether or not the vehicle that has acquired the information of the video data and the data hash value XXX stored in the recording medium 21 of the drive recorder nonvolatile memory unit 16 is the vehicle to which the drive recorder device 1 is currently attached. The procedure for this will be described with reference to FIG.

  The car key 3 transmits the encryption key ID (S101), the immobilizer ECU 2 receives the encryption key ID (S102), the immobilizer ECU 2 decrypts the received encryption key ID using the encryption key 34, and obtains the key ID. Extraction (S103), the key ID 35 held in the immobilizer EEPROM unit 32 is collated with the received key ID, the key ID collation result OK / NG is determined, and the key ID collation result OK / NG is stored in the immobilizer RAM unit 37. The operation up to holding (S104) is the same as the operation from S81 to S84 in FIG.

The user inserts the recording medium 21 in which the video data, the data hash value XXX, the car number 33, the authentication hash value YYY, the position information, and the time information # 2 are recorded into the drive recorder nonvolatile memory unit 16.
The user instructs collation of accident data by pressing the drive recorder data collation instruction button 19 (S105).

The drive recorder CPU unit 11 detects that the button has been pushed down from the drive recorder data collation instruction button unit 19, and stores the stored data hash value XXX, authentication hash value valid / invalid flag, position information, time information # 2, The authentication hash value YYY is read from the recording medium 21 of the drive recorder nonvolatile memory unit 16 (S106).
When the read authentication hash value validity / invalidity flag is set to invalid, the drive recorder CPU unit 11 lights the drive recorder data collation result notification LED 20 in red (S111).
When the read authentication hash value valid / invalid flag is set to valid, the drive recorder CPU unit 11 sends the data hash value XXX, the position information, and the authentication hash value collation request to the immobilizer ECU 2 via the drive recorder communication control unit 15. The time information # 2 and the authentication hash value YYY are transmitted (S107).

The immobilizer CPU unit 31 receives the data hash value XXX, the position information, the time information # 2, and the authentication hash value YYY via the immobilizer wired control unit 38, and the immobilizer CPU unit 31 stores the key ID held in the immobilizer RAM unit 37. The collation result (OK / NG) is read (S108).
When the key ID collation result is OK, the immobilizer CPU unit 31 calculates the authentication hash value YYY by hash calculation from the data hash value XXX, the position information, the time information # 2, and the key ID, and collates with the received authentication hash value YYY. Then, the collation result of the hash value is determined as (OK when matched / NG when not matched) (S109).
If the key ID verification result is NG, the hash value verification result is NG (S109).
The immobilizer CPU unit 31 transmits a hash value verification result notification (OK / NG) to the drive recorder device 1 via the immobilizer wired control unit 38 as an authentication hash value verification response (S110).

The drive recorder CPU unit 11 receives the hash value verification result notification (OK / NG) via the drive recorder communication control unit 15, and if the hash value verification result notification is OK, the drive recorder data verification result notification LED 20 When the hash value verification result notification is NG, the drive recorder data verification result notification LED 20 is lit red (S111).
The user is currently driving the vehicle that has acquired the video data and the data hash value XXX information stored in the recording medium 21 of the drive recorder non-volatile memory unit 16 by the blue / red lighting of the drive recorder data verification result notification LED 20. It is determined whether the vehicle is equipped with the recorder device 1.
When the light is blue, it is determined that the vehicle at the time of data acquisition is coincident with the vehicle to which the drive recorder device 1 is attached. Confirm that it is the information collected in.
If the light is red, it is determined that the vehicle at the time of data acquisition does not match the vehicle to which the drive recorder device 1 is attached.

  As described above, the user can verify that the video data, the position information, and the time information are recorded and stored in the vehicle having the stored vehicle number.

  In the present embodiment, video data including time information is stored as data to be saved by the drive recorder device 1 at the time of an accident. However, audio data, vehicle data, and vehicle peripheral data recorded using a microphone are the same as video data. The same effect can be obtained by performing a hash calculation on the data hash value XXX.

  Further, in the present embodiment, an example of a smart entry type immobilizer has been described, but a mechanical key type immobilizer can be realized by the same operation, and the same effect can be obtained.

In the present embodiment, in the drive recorder, in the drive recorder, the video data, the vehicle data, and the vehicle peripheral data are normally recorded in the memory, and when the sudden stop is detected by the acceleration sensor, the video data is transferred from the memory to the medium. The example in which the vehicle data and the vehicle periphery data are moved and transferred is described.
Instead, normally, video data, vehicle data, and vehicle peripheral data are recorded in a memory, and even if an emergency stop such as an accident does not occur, the video data, vehicle data, and vehicle peripheral data are read from the memory. Overwrite in order from the oldest data above, when a sudden stop is detected by the acceleration sensor, overwriting to the video data on the medium, vehicle data, and vehicle surrounding data is stopped, and the data on the medium is prohibited from being overwritten. The same effect can be obtained by calculating the data hash value.

Further, in the present embodiment, when the drive recorder apparatus 1 has an accident, a series of processing sequences shown in FIG. 10 are executed in response to a sudden stop by the acceleration sensor of the drive recorder acceleration sensor unit 17.
Instead, a video data storage button is provided in the drive recorder device 1, and when the user depresses the video data storage button, the drive recorder CPU unit 11 triggers the video data storage button to be depressed, and the series of FIG. Even if the processing sequence is executed, the same effect is obtained.

Further, in the present embodiment, as the display means for the drive recorder device 1 to display to the user, the means by the LED lamp display is used, but the notification means by voice or sound may be used.
Or you may notify to a user by notifying other apparatuses, such as a car navigation system, via a network.
When the car navigation system receives the verification result of the authentication hash value, the car navigation system displays the result of the authentication hash value matching response to the user.

In the present embodiment, the drive recorder device 1 performs a hash operation on the video data to be written and outputs the data hash value XXX to the immobilizer ECU 2. The immobilizer ECU 2 includes the data hash value XXX, the key ID, and the position information. A hash operation is performed on the time information to generate an authentication hash value YYY.
Instead, the drive recorder device 1 outputs the write target video data itself to the immobilizer ECU 2, and the immobilizer ECU 2 performs a hash operation on the write target video data, the key ID, the position information, and the time information, thereby authenticating the hash value YYY. May be generated.
In the present embodiment, similarly, at the time of collation, the drive recorder device 1 outputs the data hash value XXX to the immobilizer ECU 2, and the immobilizer ECU 2 hashes the data hash value XXX, the key ID, the position information, and the time information. An authentication hash value YYY is generated by performing an operation.
Instead, the drive recorder device 1 outputs the stored video data to be verified itself to the immobilizer ECU 2, and the immobilizer ECU 2 performs a hash operation on the stored video data to be verified, the key ID, the position information, and the time information. An authentication hash value YYY may be generated.

As described above, in the present embodiment, the vehicle history information storage system including the following means has been described.
(A) Means for calculating data hash values of video data, vehicle data and vehicle peripheral data stored in a medium or memory using a hash algorithm, and writing the hash values to the medium or memory (b) GPS (Global Positioning System) Means for calculating an authentication hash value using a hash algorithm from position information obtained from the global positioning system), time information, data hash value, and engine key ID for starting the engine; and (c) identifying a car different from the car key ID. Means for writing number, authentication hash value, position information and time information to medium or memory (d) Means for detecting data collation instruction by user's instruction (e) Identifying data hash value and vehicle stored in medium or memory Number, authentication hash value, location information, and time information (F) An authentication hash value is calculated from position information, time information, a data hash value, and an automobile key ID, and the authentication hash value read from the medium or memory is collated with the calculated authentication hash value. Means for determining (g) Display means for displaying the authentication hash value match / mismatch to the user, a voice or sound notification means, or a means for notifying other devices via the network.

Moreover, in this Embodiment, the vehicle history information storage system provided with the following means was demonstrated.
(A) In the drive recorder, a hash value is used to calculate the data hash value of the video data, vehicle data, and vehicle peripheral data stored on the medium, and the hash value is written to the medium. (B) In the drive recorder, the above calculation is performed. Means for transmitting the obtained data hash value to the immobilizer ECU as an authentication hash value generation request (c) The immobilizer ECU that has received the data hash value as the authentication hash value generation request is obtained from GPS (Global Positioning System, Global Positioning System) Means for calculating an authentication hash value using a hash algorithm from the position information and time information, the received data hash value and the vehicle key ID for starting the engine. (D) The immobilizer ECU uses the vehicle key I as an authentication hash value generation response. (E) In the drive recorder, the number identifying the vehicle from the immobilizer ECU, the authentication hash value, and the position as an authentication hash value generation response in the drive recorder Means for receiving information and time information (f) In the drive recorder, means for writing a car identification number, an authentication hash value, position information, and time information to the medium (g) In the drive recorder, data generated by the user of the drive recorder being pushed down Means for detecting input of collation instruction button (h) In drive recorder, means for reading out data hash value stored in medium, car identification number, authentication hash value, position information and time information from medium (i) drive recorder Then, the read data hash value, authentication hash value, and location information Means for Sending Time Information to Immobilizer ECU as Authentication Hash Value Matching Request (j) The immobilizer ECU that has received the data hash value, the authentication hash value, the position information, and the time information as the authentication hash value matching request, Means for calculating an authentication hash value from the data hash value and the vehicle key ID, comparing the received authentication hash value with the calculated authentication hash value, and determining a match / mismatch (k) In the immobilizer ECU, as an authentication hash value check response Means for transmitting authentication hash value match / mismatch (l) In the drive recorder, means for receiving match / mismatch of authentication hash value from immobilizer ECU as authentication hash value verification response (m) In the drive recorder, authentication hash value Match / mismatch It means for notifying the other devices in the notification means or via the network, by the display means or audio or sound to be displayed on.

Embodiment 3 FIG.
In the second embodiment described above, the drive recorder is a case where the position information and time information are stored by the immobilizer ECU, but in this embodiment, a key ID different from the key ID held by the automobile key is used. It is also stored in the drive recorder, and the key ID of the drive recorder is verified.

  The in-vehicle network configuration according to the present embodiment is the same as in FIG.

  FIG. 13 is an internal configuration diagram of the drive recorder device 1 according to the present embodiment.

13 is the same as that shown in FIG. 2 except for the encryption key # 2 ID22.
That is, the drive recorder CPU unit 11 is a microprocessor.
The drive recorder digital camera unit 12 is a digital camera that captures images outside the vehicle.
The drive recorder ROM unit 13 is a ROM in which programs are stored.
The drive recorder RAM unit 14 is a volatile memory RAM such as SRAM or DRAM.
The drive recorder communication control unit 15 is a module that controls communication with the in-vehicle network 7.
The drive recorder non-volatile memory unit 16 controls the slot of a rewritable medium such as an SD (registered trademark) card for recording the copied video and the writing / reading control to the medium.
The drive recorder acceleration sensor unit 17 is a module that determines a collision such as an accident based on acceleration.
The drive recorder timer unit 18 is a clock that provides time information.
The drive recorder data verification instruction button unit 19 is a button for instructing verification of accident data.
The drive recorder data verification result notification LED 20 is an LED that emits two or more colors for presenting the verification result of accident data.
The recording medium 21 is a medium for recording the copied video.
The encryption key # 2ID22 is an authentication key for the drive recorder.
The encryption key # 2ID22 is an example of a secret code.

  FIG. 14 is an internal configuration diagram of the immobilizer ECU 2 according to the present embodiment.

14 is the same as FIG. 3 except that the information stored in the immobilizer EEPROM unit 32 is different.
That is, the immobilizer CPU unit 31 is a microprocessor.
The immobilizer EEPROM 32 is an EEPROM that cannot be easily rewritten.
The car number 33 is a manufacturing number for identifying the car.
The immobilizer ROM unit 36 is a ROM that stores a program.
The immobilizer RAM unit 37 is a volatile memory RAM such as SRAM or DRAM.
The immobilizer wired control unit 38 is a module that controls communication with the in-vehicle network 7.
The immobilizer wireless control unit 39 is a module that controls wireless communication with the automobile key 3.
The immobilizer amplifier unit 40 is a module that amplifies a wireless signal by wireless communication.
The immobilizer antenna 41 is an antenna for performing wireless communication with the automobile key 3.
The encryption key # 1 (43) is a key for decrypting the encryption key ID held by the automobile key 3.
The encryption key # 2 (44) is a key for decrypting the encryption key ID held by the drive recorder device 1.
Key # 1 ID45 is information on the key ID held by the automobile key 3. Key # 1 ID45 is an example of secret information.
The key # 2 ID 46 is information on a key ID held by the drive recorder device 1. Key # 2ID46 is the same secret code as encryption key # 2ID22 (secret code) held by drive recorder device 1.

  FIG. 15 is a flowchart of a process when a collision such as a car accident or a sudden stop occurs in the present embodiment.

  Information recorded on the storage medium 21 in the drive recorder nonvolatile memory unit 16 is as shown in FIG.

  FIG. 16 is a flowchart of the process at the time of accident data collation using the immobilizer ECU 2 according to the present embodiment.

  Next, operations of the drive recorder device 1 and the immobilizer ECU 2 at the time of an accident caused by a vehicle will be described with reference to FIG.

The car key 3 transmits the encryption key # 1ID (S121), the immobilizer ECU 2 receives the encryption key # 1ID (S122), and the immobilizer ECU 2 receives the encryption key # 1 using the encryption key # 1 (43). 1ID is decrypted and key # 1ID is extracted (S123), the key # 1ID45 held in the immobilizer EEPROM unit 32 is collated with the received key # 1ID, and the collation result of the key # 1ID (when matched, OK / not matched) NG) is determined, and the key # 1 ID collation result OK / NG is held in the immobilizer RAM unit 37 (S124).
Note that since the key IDs are collated in the processes of S01 to S04 at the time of starting the engine described in the first embodiment, the processes of S121 to S124 may be omitted.

The drive recorder device 1 holds the encryption key # 2ID22 in the drive recorder ROM unit 13 (S125).
The drive recorder device 1 always records video with the drive recorder digital camera unit 12 at normal times when no accident occurs, and records the recorded video data in the drive recorder RAM unit 14. Since the drive recorder RAM unit 14 has a limited memory capacity, it constantly overwrites the old video data and writes and holds the latest data (S126).

From here, the operation when a collision such as a car accident or a sudden stop occurs will be described.
A large acceleration is generated in the vehicle due to an accident shock or a sudden operation for avoiding the accident (S127).
The drive recorder acceleration sensor unit 17 in the drive recorder device 1 determines an accident by the acceleration sensor and notifies the drive recorder CPU unit 11 of the accident.
The drive recorder CPU unit 11 writes the video data recorded in the drive recorder RAM unit 14 as video data 52 to the recording medium 21 of the drive recorder nonvolatile memory unit 16 (S128).
At this time, the drive recorder CPU unit 11 acquires the time information of the year, month, day and time from the drive recorder timer unit 18 and records the video data 52 to the recording medium 21 of the drive recorder nonvolatile memory unit 16 together with the video data of the accident. Write as time information 53.
The drive recorder CPU unit 11 calculates the data hash value XXX of the video data including the written time information (S129).
Note that the data hash value is calculated using SHA1, which is a one-way function, HMAC-SHA1, which is a hash algorithm with a key, and the like. The drive recorder CPU unit 11 reads the encryption key # 2ID22 from the drive recorder ROM unit 13. The drive recorder CPU unit 11 transmits the data hash value XXX and the encryption key # 2ID22 as an authentication hash value generation request to the immobilizer ECU 2 via the drive recorder communication control unit 15 (S130).

The immobilizer CPU unit 31 receives the data hash value XXX and the encryption key # 2ID22 as an authentication hash value generation request via the immobilizer wired control unit 38, and the immobilizer CPU unit 31 holds the key # 1ID held in the immobilizer RAM unit 37. The collation result (OK / NG) is read (S131).
If the key # 1 ID collation result is OK, the immobilizer CPU unit 31 uses the encryption key # 2 (44) to decrypt the encryption key # 2ID22 and take out the key # 2ID, and the key # held in the immobilizer EEPROM unit 32 2ID46 is collated and key # 2ID collation result is determined (S132).
The immobilizer CPU unit 31 reads the key # 1 ID45 from the immobilizer EEPROM unit 32 only when both the key # 1 ID verification result and the key # 2 ID verification result are OK, and stores the data hash value XXX, the key # 1 ID, and the key # 2 ID in the memory. The authentication hash value YYY is calculated by combining (S133).
The algorithm for calculating the authentication hash value YYY is calculated using a hash algorithm such as SHA1 that is a one-way function or HMAC-SHA1 that is a hash algorithm with a key.
The immobilizer CPU unit 31 reads the vehicle number 33 from the immobilizer EEPROM unit 32 when both the key # 1 ID verification result and the key # 2 ID verification result are OK.
On the other hand, if both the key # 1 ID verification result and the key # 2 ID verification result are not OK, an error notification is generated.
Then, the immobilizer CPU unit 31 notifies the drive recorder device 1 of an authentication hash value generation response via the immobilizer wired control unit 38 (S134).
When both the key # 1 ID collation result and the key # 2 ID collation result are OK, the vehicle number 33 and the authentication hash value YYY and the instruction information for instructing to write the vehicle number 33 and the authentication hash value YYY into the recording medium 21 are included. An authentication hash value generation response is transmitted.
On the other hand, if neither the key # 1 ID verification result nor the key # 2 ID verification result is OK, an authentication hash value generation response including an error notification is transmitted.

The drive recorder CPU unit 11 receives the authentication hash value generation response result (OK / NG) via the drive recorder communication control unit 15.
If the result of the authentication hash value generation response is OK, the drive recorder CPU unit 11 sets the authentication hash value valid / invalid flag 55 as valid, and sets the authentication hash value valid / invalid flag 55, the car number 33, and the authentication hash value YYY56. Writing to the recording medium 21 of the drive recorder non-volatile memory unit 16 (S135).
If the result of the authentication hash value generation response is NG, the drive recorder CPU unit 11 sets the authentication hash value valid / invalid flag 55 as invalid, and records the authentication hash value valid / invalid flag 55 in the drive recorder nonvolatile memory unit 16. Writing to the medium 21 (S135).

  Next, it is verified whether the user who acquired the video data stored in the recording medium 21 of the drive recorder non-volatile memory unit 16 and the data hash value XXX is a car to which the drive recorder device 1 is currently attached. The procedure for this will be described with reference to FIG.

  The car key 3 transmits the encryption key # 1 ID (S141), the immobilizer ECU 2 receives the encryption key # 1 ID (S142), and the immobilizer ECU 2 receives the encryption key # 1 using the encryption key # 1 (43). 1ID is decrypted and key # 1ID is extracted (S143), the key # 1ID45 held in the immobilizer EEPROM unit 32 is collated with the received key # 1ID, the collation result OK / NG of the key # 1ID is determined, and the key # The operation until the 1 ID collation result OK / NG is held in the immobilizer RAM unit 37 (S44) is the same as the operation from S121 to S124 in FIG.

The user inserts the recording medium 21 in which the video data, the data hash value XXX, the car number 33 and the authentication hash value YYY are recorded in the drive recorder device 1 into the drive recorder nonvolatile memory unit 16.
The user instructs collation of accident data by pressing the drive recorder data collation instruction button 19 (S145).

The drive recorder CPU unit 11 detects that the button has been pressed down from the drive recorder data collation instruction button unit 19, and stores the stored data hash value XXX and authentication hash value YYY in the recording medium of the drive recorder nonvolatile memory unit 16. 21 and the encryption key # 2ID22 is read from the drive recorder ROM unit 13 (S146).
When the read authentication hash value validity / invalidity flag is set to invalid, the drive recorder CPU unit 11 lights the drive recorder data collation result notification LED 20 in red (S152).
When the read authentication hash value valid / invalid flag is set to valid, the drive recorder CPU unit 11 sends the data hash value XXX and the authentication hash value to the immobilizer ECU 2 via the drive recorder communication control unit 15 as an authentication hash value collation request. YYY and encryption key # 2ID22 are transmitted (S147).

The immobilizer CPU unit 31 receives the data hash value XXX, the authentication hash value YYY, and the encryption key # 2ID22 via the immobilizer wired control unit 38. The result (OK / NG) is read (S148).
If the key # 1 ID collation result is OK, the immobilizer CPU unit 31 uses the encryption key # 2 (44) to decrypt the encryption key # 2ID22, retrieves the key # 2ID, and receives the retained key # 2ID46 Key # 2 ID is collated, and key # 2 ID collation result is determined (S149).
If both the key # 1 ID verification result and the key # 2 ID verification result are OK, the immobilizer CPU unit 31 calculates the authentication hash value YYY by hash calculation from the data hash value XXX, the key # 1 ID, and the key # 2 ID, and the received authentication The hash value YYY is collated, and the collation result of the hash value is determined as (OK when matched / NG when not matched) (S150).
If neither the key # 1 ID verification result nor the key # 2 ID verification result is OK, the hash value verification result is set to NG (S150).
The immobilizer CPU unit 31 transmits a hash value verification result notification (OK / NG) to the drive recorder device 1 via the immobilizer wired control unit 38 as an authentication hash value verification response (S151).

The drive recorder CPU unit 11 receives the hash value verification result notification (OK / NG) via the drive recorder communication control unit 15, and if the hash value verification result notification is OK, the drive recorder data verification result notification LED 20 When the hash value verification result notification is NG, the drive recorder data verification result notification LED 20 is lit red (S152).
The user records the video data stored in the recording medium 21 of the drive recorder non-volatile memory unit 16 and the information of the data hash value XXX by the blue / red lighting of the drive recorder data verification result notification LED 20 about the drive recorder and the car. It is determined whether the vehicle is currently equipped with a drive recorder device 1.
If the light is blue, the vehicle at the time of data acquisition matches the vehicle to which the drive recorder device 1 is attached, and it is determined that data has been acquired by the attached drive recorder.
When the drive recorder data collation result notification LED 20 is lit red, the user does not match the car at the time of data acquisition with the car to which the drive recorder device 1 is attached or is the attached drive recorder. Judge that the data was acquired by another drive recorder.

  As described above, the user can record and save the video data in the car having the saved car number, and can obtain an effect of verifying that the video data is recorded and saved by the attached drive recorder.

  In the present embodiment, video data including time information is stored as data to be saved by the drive recorder device 1 at the time of an accident. However, audio data, vehicle data, and vehicle peripheral data recorded using a microphone are the same as video data. The same effect can be obtained by performing a hash calculation on the data hash value XXX.

  In the present embodiment, an example of a smart entry type immobilizer has been described. However, a mechanical key type immobilizer can also be realized by the same operation, and the same effect can be obtained.

In the present embodiment, in the drive recorder, in the drive recorder, the video data, the vehicle data, and the vehicle peripheral data are normally recorded in the memory, and when the sudden stop is detected by the acceleration sensor, the video data is transferred from the memory to the medium. The example in which the vehicle data and the vehicle periphery data are moved and transferred is described.
Instead, normally, video data, vehicle data, and vehicle peripheral data are recorded in a memory, and even if an emergency stop such as an accident does not occur, the video data, vehicle data, and vehicle peripheral data are read from the memory. Overwrite in order from the oldest data above, when a sudden stop is detected by the acceleration sensor, overwriting to the video data on the medium, vehicle data, and vehicle surrounding data is stopped, and the data on the medium is prohibited from being overwritten. The same effect can be obtained by calculating the data hash value.

Further, in the present embodiment, when the drive recorder apparatus 1 has an accident, a series of processing sequences shown in FIG. 15 are executed in response to a sudden stop by the acceleration sensor of the drive recorder acceleration sensor unit 17.
Instead of this, a video data storage button is provided in the drive recorder device 1, and when the user depresses the video data storage button, the drive recorder CPU unit 11 triggers the video data storage button to be depressed as a series of FIG. 15. The same effect can be obtained by executing the processing sequence.

Further, in the present embodiment, as the display means for the drive recorder device 1 to display to the user, the means by the LED lamp display is used, but the notification means by voice or sound may be used.
Or you may notify to a user by notifying other apparatuses, such as a car navigation system, via a network.
When the car navigation system receives the verification result of the authentication hash value, the car navigation system displays the result of the authentication hash value matching response to the user.

In the present embodiment, the drive recorder device 1 performs a hash operation on the video data to be written, and outputs the data hash value XXX and key # 2ID to the immobilizer ECU 2. The immobilizer ECU 2 stores the data hash value XXX and key # 2. A hash operation is performed on 1ID and key # 2ID to generate an authentication hash value YYY.
Instead, the drive recorder device 1 outputs the writing target video data itself and the key # 2ID to the immobilizer ECU 2, and the immobilizer ECU 2 performs authentication on the writing target video data, the key # 1ID, and the key # 2ID by performing a hash operation. A hash value YYY may be generated.
In the present embodiment, similarly, at the time of verification, the drive recorder device 1 outputs the data hash value XXX and the key # 2ID to the immobilizer ECU 2, and the immobilizer ECU 2 uses the data hash value XXX, the key # 1ID, and the key # 2ID. A hash operation is performed on the authentication hash value YYY.
Instead, the drive recorder device 1 outputs the stored video data to be verified and the key # 2ID to the immobilizer ECU 2, and the immobilizer ECU 2 performs a hash operation on the stored video data to be verified, the key # 1ID, and the key # 2ID. To generate an authentication hash value YYY.

As described above, in the present embodiment, the vehicle history information storage system including the following means has been described.
(A) Means for storing an encrypted drive recorder key (b) A hash value is used to calculate a data hash value of video data, vehicle data, and vehicle peripheral data stored in a medium or memory using a hash algorithm, Or, means for writing to memory (c) Only when the encrypted drive recorder key is decrypted and the drive recorder key is taken out, and the result of verification of the drive recorder key matches the drive recorder key held in the immobilizer ECU Means for calculating an authentication hash value using a hash algorithm from the data hash value, the engine activation vehicle key ID and the drive recorder key (d) a vehicle identification number and an authentication hash value which are different from the vehicle key ID Means for writing to memory (e) User data verification finger (F) means for reading out the data hash value stored in the medium or memory, the number for identifying the vehicle, the authentication hash value, and the encrypted drive recorder key (g) the encrypted drive recorder key Decrypt and take out the drive recorder key, and the authentication hash from the data hash value, the car key ID and the drive recorder key only when the result of the drive recorder key verification matches the drive recorder key held in the immobilizer ECU The drive recorder key whose value is calculated, the authentication hash value read from the medium or memory and the calculated authentication hash value are collated, the match / mismatch is determined, and the collation result of the drive recorder key is held by the immobilizer ECU If it does not match, authentication hash value verification result does not match Determining means (h) display means for displaying to the user a match / mismatch of the authentication hash value or notifying means by voice or sound or means for notifying via the network to another device,.

Moreover, in this Embodiment, the vehicle history information storage system provided with the following means was demonstrated.
(A) In the drive recorder, means for holding the encrypted drive recorder key (b) In the drive recorder, the data hash value of the video data, vehicle data, and vehicle peripheral data stored in the medium is calculated using a hash algorithm. (C) means for writing the hash value to the medium; (c) means for transmitting the calculated data hash value and the encrypted drive recorder key to the immobilizer ECU as an authentication hash value generation request; The immobilizer ECU that has received the data hash value and the encrypted drive recorder key as a request decrypts the encrypted drive recorder key, retrieves the drive recorder key, and the drive recorder key verification result is held in the immobilizer ECU. Had Means for calculating an authentication hash value using a hash algorithm from the data hash value, the car key ID for starting the engine and the drive recorder key only when the key matches the eve recorder key. (E) The immobilizer ECU generates an authentication hash value. Means for transmitting vehicle identification number and authentication hash value different from vehicle key ID as response (f) Drive recorder receives vehicle identification number and authentication hash value from immobilizer ECU as authentication hash value generation response Means (g) In the drive recorder, means for writing a car identification number and an authentication hash value to the medium. (H) In the drive recorder, means for detecting data collation instruction button input by the user of the drive recorder being pushed down (i) Drive recorder Now save it to the medium Data hash value, vehicle identification number, authentication hash value, and means for reading encrypted drive recorder key from medium (j) In the drive recorder, the read data hash value, authentication hash value, and encrypted drive recorder Means for transmitting the key to the immobilizer ECU as an authentication hash value verification request (k) In the immobilizer ECU that has received the data hash value, the authentication hash value, and the drive recorder key as the authentication hash value verification request, the immobilizer ECU receives the encrypted drive recorder key. Decrypt and take out the drive recorder key, and the authentication hash from the data hash value, the car key ID and the drive recorder key only when the result of the drive recorder key verification matches the drive recorder key held in the immobilizer ECU The value Calculates, compares the received authentication hash value with the calculated authentication hash value, determines match / mismatch, and authenticates if the drive recorder key match result does not match the drive recorder key held in the immobilizer ECU Means for determining the hash value collation result as inconsistent (1) In the immobilizer ECU, means for transmitting the coincidence / mismatch of the authentication hash value as the authentication hash value collation response (m) In the drive recorder, the immobilizer ECU receives the authentication hash value collation response from the immobilizer ECU (N) In the drive recorder, in the drive recorder, a display means for displaying the authentication hash value match / mismatch to the user of the drive recorder, a voice or sound notification means, or via a network Means for notifying other devices.

  Finally, the operation of the immobilizer CPU unit 31 of the immobilizer ECU 2 shown in the first to third embodiments and the relationship between the immobilizer EEPROM unit 32, the immobilizer ROM unit 36, the immobilizer RAM unit 37, and the like will be described.

As described above, the immobilizer CPU unit 31 of the immobilizer ECU 2 is a processor that executes a program.
The immobilizer CPU unit 31 is connected to the immobilizer EEPROM unit 32, the immobilizer ROM unit 36, the immobilizer RAM unit 37, the immobilizer wired control unit 38, and the immobilizer wireless control unit 39 via the bus, and controls these hardware devices.

The immobilizer ROM unit 36 stores a program executed by the immobilizer CPU unit 31.
The immobilizer CPU unit 31 executes a program of the immobilizer ROM unit 36 and functions as a one-way calculation data generation unit, a verification processing unit, and an ID determination unit.

The immobilizer RAM unit 37 temporarily stores at least a part of a program executed by the immobilizer CPU unit 31 (program of the immobilizer ROM unit 36).
The immobilizer RAM unit 37 stores various data necessary for processing by the immobilizer CPU unit 31.

The immobilizer ROM unit 36 stores a BIOS (Basic Input Output System) program and a boot program.
When the immobilizer ECU 2 is activated, a BIOS program and a boot program are executed.

In the immobilizer RAM unit 37, as a file group, in the description of the first to third embodiments, “determination of”, “calculation of”, “calculation of”, “calculation of”, and “comparison of” are performed. , Information or data indicating the results of the processing described as “matching”, “verifying”, “updating”, “setting”, “registering”, “selecting”, etc. And signal values, variable values, and parameters are stored as items of “˜file” and “˜database”.
The arrows in the flowcharts described in the first to third embodiments mainly indicate input / output of data and signals, and the data and signal values are recorded in the immobilizer RAM unit 37, for example.

Further, in the description of the first to third embodiments, what is described as “to part” and “to means” may be “to circuit”, “to device”, and “to device”. It may be “˜step”, “˜procedure”, “˜processing”.
That is, the “data processing method” according to the present invention can be realized by the steps, procedures, and processes shown in the flowcharts described in the first to third embodiments.
That is, when the operation of the immobilizer CPU unit 31 that functions as a one-way calculation data generation unit, a verification processing unit, and an ID determination unit is regarded as steps (one-way calculation data generation step, verification processing step, ID determination step), the present invention. This is a “data processing method”.
The program executed by the immobilizer CPU unit 31 includes a one-way calculation data process, a verification process, and an ID determination process. By executing these processes, the immobilizer CPU unit 31 performs a one-way calculation data generation unit, a verification process. It functions as a processing unit and an ID determination unit.

  DESCRIPTION OF SYMBOLS 1 Drive recorder apparatus, 2 Immobilizer ECU, 3 Car key, 4 Engine switch, 5 Engine ECU, 6 Car engine part, 7 Car network, 11 Drive recorder CPU part, 12 Drive recorder digital camera part, 13 Drive recorder ROM part, 14 Drive recorder RAM section, 15 Drive recorder communication control section, 16 Drive recorder nonvolatile memory section, 17 Drive recorder acceleration sensor section, 18 Drive recorder timer section, 19 Data collation instruction button section, 20 Data collation result notification LED, 21 Recording medium , 22 Encryption key # 2 ID, 31 Immobilizer CPU part, 32 Immobilizer EEPROM part, 33 Car number, 34 Encryption key, 35 Key ID, 36 Immobilizer OM section, 37 immobilizer RAM section, 38 immobilizer wired control section, 39 immobilizer radio control section, 40 immobilizer amplifier section, 41 immobilizer antenna, 42 immobilizer GPS section, 43 encryption key # 1, 44 encryption key # 2, 45 key # 1ID , 46 Key # 2 ID, 52 Video data, 53 Time information, 54 Data hash value XXX, 55 Authentication hash value valid / invalid flag, 56 Authentication hash value YYY, 57 Time information # 1, 58 Location information, 59 Time information # 2

Claims (14)

This is an in-vehicle device that is connected to a drive recorder device that takes a picture on a mounted vehicle and writes specific video data to be written to a predetermined recording medium. And
A storage unit for storing secret information uniquely set in the mounted vehicle;
When the drive recorder device writes the write target video data to the recording medium, the write target video data or data after a predetermined calculation is performed on the write target video data is input from the drive recorder device as calculation target data. An input section;
When the calculation target data is input from the input unit, the calculation target data and the secret information are used to perform a one-way calculation, and the one-way calculation data calculated by the one-way calculation is used as the write target video. A one-way operation data generation unit for generating instruction information for instructing the drive recorder device to write to the recording medium together with data;
An in-vehicle device, comprising: an output unit that outputs the one-way calculation data and the instruction information to the drive recorder device. The input unit is
When the drive recorder apparatus receives a verification request for the verification target recording medium, the stored video data stored in the verification target recording medium or data after a predetermined calculation is performed on the stored video data is used for verification. Input from the drive recorder device as calculation target data, and further input from the drive recorder device as one-way calculation data for verification stored in the verification target recording medium,
The in-vehicle device further includes
Performing the same one-way calculation as the one-way calculation performed by the one-way calculation data generation unit using the verification calculation target data and the secret information, the calculated value calculated by the one-way calculation and the verification one-way When the calculated data and the one-way calculation data for verification match, the stored video data in the verification target recording medium is video data taken by the drive recorder device of the mounted vehicle. The in-vehicle device according to claim 1, further comprising a verification processing unit that determines that there is one. The in-vehicle device further includes
When the drive recorder device writes the write target video data to the recording medium, the drive recorder device has a positioning unit that measures the location of the in-vehicle device and generates location information of the in-vehicle device,
The one-way calculation data generation unit
When the calculation target data is input from the input unit, the calculation target data, the secret information, and the location information are used to perform a one-way calculation, and the one-way calculation data calculated by the one-way calculation And generating instruction information for instructing the drive recorder device to write the location information to the recording medium,
The output unit is
The in-vehicle device according to claim 1, wherein the one-way calculation data, the location information, and the instruction information are output to the drive recorder device. The input unit is
When the drive recorder apparatus receives a verification request for the verification target recording medium, the stored video data stored in the verification target recording medium or data after a predetermined calculation is performed on the stored video data is used for verification. Input from the drive recorder device as calculation target data, and further input from the drive recorder device as one-way calculation data for verification stored in the verification target recording medium,
The in-vehicle device further includes
Performing the same one-way calculation as the one-way calculation data generation unit using the verification calculation target data, the secret information, and the location information, the calculated value calculated by the one-way calculation and the The one-way calculation data for verification is collated, and when the calculated value and the one-way calculation data for verification match, the stored video data in the verification target recording medium is shot by the drive recorder device of the mounted vehicle. The in-vehicle device according to claim 3, further comprising: a verification processing unit that determines that the video data is received. The storage unit
Storing the same secret code as the secret code possessed by the drive recorder device;
The input unit is
When the drive recorder device writes the write target video data to the recording medium, the calculation target data and a secret code held by the drive recorder device are input from the drive recorder device,
The one-way calculation data generation unit
When the calculation target data and the secret code are input by the input unit, it is determined whether or not the input secret code matches the secret code stored in the storage unit, and the secret code matches In addition, the one-way calculation is performed using the calculation target data, the secret information, and any one of the secret codes, and the one-way calculation data calculated by the one-way calculation is written in the recording medium to the drive recorder device. The in-vehicle device according to claim 1, wherein instruction information to be instructed is generated. The input unit is
When the drive recorder apparatus receives a verification request for the verification target recording medium, the stored video data stored in the verification target recording medium or data after a predetermined calculation is performed on the stored video data is used for verification. The calculation target data is input from the drive recorder device, and the one-way calculation data stored in the verification target recording medium is input from the drive recorder device as verification one-way calculation data. The secret code to be entered from the drive recorder device,
The in-vehicle device further includes
It is determined whether or not the secret code input by the input unit matches the secret code stored in the storage unit, and when the secret code matches, the verification operation target data and the secret information A one-way calculation that is the same as the one-way calculation performed by the one-way calculation data generation unit using the secret code, and compares the calculated value calculated by the one-way calculation with the one-way calculation data for verification. Verification processing for determining that the stored video data in the verification target recording medium is video data captured by the drive recorder device of the mounted vehicle when the calculated value and the one-way calculation data for verification match The in-vehicle device according to claim 5, further comprising: a unit. The input unit is
When the drive recorder device writes the write target video data to the recording medium, the write target video data or the data after a predetermined one-way operation is performed on the write target video data in the drive recorder device Enter as target data,
When the drive recorder device receives a verification request for the verification target recording medium, the stored video data or the data after a predetermined one-way calculation is performed on the stored video data in the drive recorder device The in-vehicle device according to claim 2, wherein the in-vehicle device is input as data. The storage unit
As the secret information, a vehicle key ID (Identification) that is an identifier of a vehicle key used for starting an engine of the mounted vehicle is stored,
The in-vehicle device further includes
An ID information receiving unit for receiving ID information when starting the engine of the mounted vehicle;
An ID determination unit that determines whether or not the ID information received by the ID information reception unit matches the vehicle key ID;
The one-way calculation data generation unit
When the calculation target data is input, the determination result in the ID determination unit is confirmed. When the ID determination unit determines that the ID information matches the vehicle key ID, the one-way calculation data is The in-vehicle device according to claim 1, wherein the on-vehicle device is generated. The in-vehicle device is
Connected to an engine control mechanism for controlling the engine of the mounted vehicle,
The ID determination unit
When it is determined that the ID information received by the ID information receiving unit does not match the vehicle key ID, the engine control mechanism is instructed to perform control not to operate the engine of the mounted vehicle. The in-vehicle device according to claim 8. The storage unit
Storing a vehicle ID which is an identifier of the mounted vehicle;
The one-way calculation data generation unit
Generating instruction information for instructing the drive recorder device to write the one-way calculation data and the vehicle ID together with the write target video data to the recording medium with respect to the drive recorder device;
The output unit is
The in-vehicle device according to claim 1, wherein the one-way calculation data, the vehicle ID, and the instruction information are output to the drive recorder device. The in-vehicle device is
An acceleration sensor is provided, and when the acceleration sensor detects the occurrence of an acceleration of a predetermined level or higher, it is connected to a drive recorder device that writes video data taken after that to the recording medium as video data to be written. The in-vehicle device according to any one of claims 1 to 10. A drive recorder device that shoots on a mounted vehicle and writes specific video data to be written to a predetermined recording medium among the captured video data;
An in-vehicle device that is mounted on the mounted vehicle and stores a pair of secret information uniquely set in the mounted vehicle and a vehicle ID of the mounted vehicle;
A data processing system having a verification device storing a plurality of pairs of secret information and vehicle ID,
The in-vehicle device is
When the drive recorder device writes the video data to be written to the recording medium, the video data to be written or data after a predetermined calculation is performed on the video data to be written is input from the drive recorder device as calculation target data. ,
The one-way calculation is performed using the input calculation target data and the secret information, and the one-way calculation data calculated by the one-way calculation and the vehicle ID are written to the recording medium together with the write target video data. Generate instruction information to instruct the drive recorder device,
Outputting the one-way calculation data, the vehicle ID, and the instruction information to the drive recorder device;
The drive recorder device
The one-way calculation data, the vehicle ID, and the instruction information are input from the in-vehicle device,
According to the instruction information, the one-way calculation data and the vehicle ID are written to the recording medium together with the writing target video data,
The verification device includes:
The stored video data stored in the verification target recording medium or the data after a predetermined calculation is performed on the stored video data is input as verification target data, and the one direction stored in the verification target recording medium Calculation data is input as verification one-way calculation data, and further, a vehicle ID stored in the verification target recording medium is input as a verification vehicle ID,
Extract the secret information that is paired with the entered verification vehicle ID,
Using the extracted secret information and the input operation target data for verification, the same one-way operation as that performed by the in-vehicle device is performed, and the calculated value calculated by the one-way operation and the one-way operation for verification When the calculated value and the one-way calculation data for verification match, the stored video data in the verification target recording medium is video data captured by the drive recorder device of the mounted vehicle. The data processing system characterized by determining with. It is connected to a drive recorder device that takes a picture on the mounted vehicle and writes specific video data to be written to a predetermined recording medium among the captured video data, and is performed by the in-vehicle device mounted on the mounted vehicle. A data processing method,
When the drive recorder device writes the write target video data to the recording medium, the in-vehicle device uses the write target video data or data after a predetermined calculation is performed on the write target video data as the calculation target data. An input step for inputting from the recorder device;
When the calculation target data is input in the input step, the in-vehicle device uses the secret information uniquely set for the mounted vehicle stored in the in-vehicle device and the calculation target data. A unidirectional calculation data generation step for performing direction calculation and generating instruction information for instructing the drive recorder device to write the unidirectional calculation data calculated by the unidirectional calculation together with the write target video data to the recording medium;
The data processing method characterized by the said vehicle-mounted apparatus having the output step which outputs the said one-way calculation data and the said instruction information to the said drive recorder apparatus. An on-vehicle computer that is connected to a drive recorder device that performs shooting on a mounted vehicle and writes specific video data to be written to a predetermined recording medium among the captured video data. To the device,
When the drive recorder device writes the write target video data to the recording medium, the write target video data or data after a predetermined calculation is performed on the write target video data is input from the drive recorder device as calculation target data. Input processing,
When the calculation target data is input by the input process, a one-way calculation is performed using the secret information uniquely set for the mounted vehicle stored in the in-vehicle device and the calculation target data, One-way calculation data generation processing for generating instruction information for instructing the drive recorder device to write the one-way calculation data calculated by the one-way calculation together with the write target video data to the recording medium;
A program for executing an output process for outputting the one-way calculation data and the instruction information to the drive recorder device.

Images