JP7322682B2 - Control method, information processing device, information processing system and program - Google Patents

Description

The present invention relates to a control method, an information processing device, an information processing system, and a program.

2. Description of the Related Art In recent years, image data (hereinafter referred to as “DR data”) captured by a drive recorder has attracted attention as evidence of a traffic accident. In the past, DR data could be falsified, so it was considered difficult to use it as evidence in out-of-court settlements or trials. I got out. The trial suggests that collecting and combining DR data from multiple uninterested vehicles could serve as evidence. Therefore, it is considered effective to collect DR data over a wide range for investigation of the cause of the accident.

WO2018/124297

On the other hand, DR data may also contain information about privacy. Therefore, as a provider of DR data, it is desirable to prevent the outflow of DR data, which is unlikely to contribute to the investigation of the cause of the accident, to the outside.

Accordingly, in one aspect, an object of the present invention is to make it possible to suppress leakage of captured images that are not requested to be provided.

In one aspect, the control method refers to a first blockchain that records shooting position information of each captured image taken by an in-vehicle camera, upon receiving the specification of the position information, to the specified position information. a process of acquiring photographing position information in response, a process of making a request to provide a photographed image specified by the photographing position information acquired, to a recording source of the photographing position information in the first blockchain; When the target photographic image of the provision request is recorded in the second blockchain, the computer executes a process of obtaining the target photographic image by referring to the second blockchain.

As one aspect, it is possible to suppress the outflow of captured images that are not requested to be provided.

It is a figure which shows the structural example of the information processing system in embodiment of this invention. It is a figure which shows the hardware structural example of the insurance server 10 in embodiment of this invention. It is a figure which shows the functional structural example of the insurance server 10 in embodiment of this invention. FIG. 11 is a sequence diagram for explaining an example of a processing procedure of registration processing of metadata to a block chain C1 by the drive recorder 20; FIG. 4 is a diagram for explaining an example of a conversion method of a GPS data group; FIG. 4 is a sequence diagram for explaining an example of a processing procedure that is executed when an accident occurs; FIG. 4 is a diagram for explaining GPS conversion data according to generated position information;

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention will be described below based on the drawings. FIG. 1 is a diagram showing a configuration example of an information processing system according to an embodiment of the present invention. In the information processing system 1 shown in FIG. 1, a plurality of drive recorders 20 are connected to a block chain C1 via a network such as a mobile communication network or the Internet. Also, the insurance server 10 is connected to the blockchain C1 and a plurality of owner terminals 30 via a network such as the Internet.

Each drive recorder 20 is mounted in a vehicle (automobile), and is an example of a vehicle-mounted camera in the present embodiment. The drive recorder 20 records, in a file format, moving image data (captured images) taken at fixed time intervals (30 seconds, 1 minute, 3 minutes, etc.) while the vehicle is running. Therefore, a file (hereinafter referred to as "DR data") is generated at regular time intervals. It should be noted that the shooting may be performed at all times while driving, or when certain conditions are met (when an impact or acceleration above a certain level is detected, or when the driver performs a predetermined operation (such as pressing a button)). , etc.). The drive recorder 20 registers metadata of each DR data in the block chain C1. As a result, the blockchain records metadata for each DR data. Here, the metadata includes a hash value of the DR data, shooting position information of the DR data, and information of the owner of the DR data (for example, the driver of the vehicle equipped with the drive recorder 20 shooting the DR data). It is data that includes information (e-mail address, contact information such as telephone number, etc.) in association with each other. Note that the owner of the DR data is an example of the recording source of the metadata on the blockchain C1.

The owner terminal 30 is a communication terminal used by the owner of the DR data (for example, the driver of the vehicle). For example, a mobile phone, a smart phone, a tablet terminal, a vehicle-mounted device (a communication device mounted on a vehicle), or the like may be used as the owner terminal 30 . Alternatively, the drive recorder 20 may also serve as the owner terminal 30 .

The insurance server 10 is one or more computers used by an automobile insurance company (hereinafter simply referred to as "insurance company") to which the driver of each vehicle subscribes. In addition, when the insurance company of the driver of each vehicle is different, a plurality of insurance servers 10 may be connected to the block chain C1. When a vehicle-related accident occurs, the insurance server 10 searches for metadata including shooting position information corresponding to the accident occurrence position information, and provides the DR data corresponding to the metadata to the owner of the DR data ( request to the record source of the metadata. As will be described later, the DR data is provided from the drive recorder 20 to the insurance server 10 via the block chain C1 in response to the request for the provision. As a result, the insurance server 10 can collect the location where the accident occurred or captured images around the location.

FIG. 2 is a diagram showing a hardware configuration example of the insurance server 10 according to the embodiment of the present invention. The insurance server 10 of FIG. 2 has a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, etc., which are interconnected by a bus B, respectively.

A program for realizing the processing in insurance server 10 is provided by recording medium 101 . When the recording medium 101 recording the program is set in the drive device 100 , the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100 . However, the program does not necessarily need to be installed from the recording medium 101, and may be downloaded from another computer via the network. The auxiliary storage device 102 stores installed programs, as well as necessary files and data.

The memory device 103 reads out and stores the program from the auxiliary storage device 102 when a program activation instruction is received. The CPU 104 executes functions related to the insurance server 10 according to programs stored in the memory device 103 . The interface device 105 is used as an interface for connecting to a network.

An example of the recording medium 101 is a portable recording medium such as a CD-ROM, a DVD disk, or a USB memory. An example of the auxiliary storage device 102 is an HDD (Hard Disk Drive) or a flash memory. Both the recording medium 101 and the auxiliary storage device 102 correspond to computer-readable recording media.

FIG. 3 is a diagram showing a functional configuration example of the insurance server 10 according to the embodiment of the present invention. 3, the insurance server 10 includes an accident information reception unit 11, a metadata search unit 12, a DR data request unit 13, a DR data acquisition unit 14, a DR data verification unit 15, and the like. Each of these units is implemented by processing that one or more programs installed in the insurance server 10 cause the CPU 104 to execute.

When a vehicle-related accident occurs, the accident information reception unit 11 receives input of information related to the accident (hereinafter referred to as "accident information"). The accident information includes information on the date and time of occurrence of the accident and information on the location of the accident (for example, place name, etc.). The accident information is, for example, communicated to the insurance company by telephone or the like by the parties involved in the accident. At the insurance company, an operator inputs the accident information to the insurance server 10 .

The metadata search unit 12 searches the blockchain C1 for metadata including location information corresponding to the occurrence location information and the occurrence date and time information included in the accident information received by the accident information reception unit 11, and retrieves the corresponding metadata. is obtained from the block chain C1.

The DR data requesting unit 13 requests provision of DR data corresponding to the metadata acquired by the metadata searching unit 12 . For example, the DR data requesting unit 13 sends an e-mail indicating the provision request to the owner terminal 30 of the driver who owns the DR data. The driver who has received the DR data provision request instructs the drive recorder 20 to register the DR data in the block chain C1 when permitting the provision of the DR data according to the provision request. As a result, the DR data is recorded in the block chain C1.

When the DR data acquisition unit 14 detects that the DR data to be requested to be provided has been recorded in the block chain C1, it acquires the DR data by referring to the block chain C1 (acquires from the block chain C1). .

The DR data verification unit 15 verifies that the DR data acquired by the DR data acquisition unit 14 has not been tampered with using metadata corresponding to the DR data.

A processing procedure executed in the information processing system 1 will be described below. FIG. 4 is a sequence diagram for explaining an example of a processing procedure of metadata registration processing in the block chain C1 by the drive recorder 20. As shown in FIG. In FIG. 4 , one or more programs installed in the drive recorder 20 cause the drive recorder 20 to execute the processing executed by the drive recorder 20 .

In step S101, the drive recorder 20 stores a file (hereinafter referred to as "target DR data") containing moving image data (captured images) captured (recorded) during the most recent past fixed time period T1. Record on device.

Subsequently, the drive recorder 20 sends a set of one or more GPS (Global Positioning System) data (hereinafter referred to as "target GPS data group") acquired at a time interval T2 equal to or shorter than the certain time T1. Record in memory. For example, if T1 is 1 minute and T2 is 15 seconds, then 4 GPS data are recorded in the storage device. Each GPS data includes latitude and longitude information and reception date/time information (information indicating the date/time when a signal from a GPS satellite was received). In other words, each piece of GPS data is positional information of any point on the movement trajectory of the vehicle during the fixed time T1.

Subsequently, the drive recorder 20 generates a hash value of the target DR data (hereinafter referred to as "target hash value") (S103). The target hash value is generated to enable verification that the target DR data has not been tampered with. For example, a sufficiently strong cryptographic hash function (such as SHA256) may be used to calculate the target hash value.

Subsequently, the drive recorder 20 converts the target GPS data group into data in a format suitable for searching in order to facilitate inquiry of DR data recorded at or around the location of the accident (S104).

FIG. 5 is a diagram for explaining an example of a method of converting a GPS data group. In FIG. 5, the positions indicated by the four GPS data d1 to d4 forming the GPS data group are plotted.

The drive recorder 20 first obtains the center of gravity P1 of the GPS data d1 to d4. The center of gravity point P1 is the geometric center of the GPS data d1-d4. Subsequently, the drive recorder 20 obtains the distances between the center of gravity point P1 and each of the GPS data d1 to d4. Subsequently, the drive recorder 20 specifies the largest value (the distance from the center of gravity point P1 to the farthest position) among the obtained distances, and sets the specified distance as the distance r1. In the example of FIG. 5, the distance between the center of gravity point P1 and the GPS data d4 is specified as r1. The drive recorder 20 converts the set (P1, r1) of the latitude and longitude of the center of gravity point P1 (hereinafter simply referred to as "P1") and the distance r1 to the converted data of the GPS data d1 to d4 (hereinafter referred to as "GPS conversion data”). The GPS-converted data is treated as data indicating the area (area) of a circle c1 with radius r1 centered on P1.

Subsequently, the drive recorder 20 generates metadata for the target DR data (hereinafter referred to as "target metadata") (S105). The target metadata includes a target hash value, GPS conversion data, the start date and time and end date and time of the certain time T1 (that is, date and time information), and owner information. The start date and time and the end date and time (information indicating the period from the start date and time to the end date and time is hereinafter referred to as "shooting period information") are the reception date and time information of the oldest GPS data and the latest reception date and time of the target GPS data group. GPS data reception date and time information. The owner information is information (contact information such as e-mail address or telephone number, etc.) of the owner of the target DR data, and may be stored in the drive recorder 20 in advance, for example.

In order to ensure the association between the target DR data and the target metadata, for example, identification information of the target DR data (hereinafter referred to as "DR data ID") is assigned to both the target DR data and the target metadata. may be given. The DR data ID may be included in each file name of the target DR data and target metadata.

Subsequently, the drive recorder 20 registers the target metadata in the blockchain C1 (S106).

Note that steps S101 to S106 are executed at regular time intervals T1 while the vehicle is running (from ignition ON to ignition OFF). However, steps S103 to S106 may be executed in a cycle longer than the fixed time T1. For example, when the ignition of the vehicle is turned off, steps S103 to S106 may be collectively executed for each DR data and each GPS data group recorded during the period from when the ignition is turned on. By doing so, the communication load between the drive recorder 20 and the blockchain C1 can be reduced. However, in order to ensure the reliability of the metadata, it is desirable that the metadata corresponding to the DR data be registered in the block chain C1 in real time as the DR data is generated.

FIG. 6 is a sequence diagram for explaining an example of a processing procedure executed upon occurrence of an accident.

With the occurrence of an accident, when the insurance company receives accident information (occurrence date and time information, occurrence location information) from the parties involved in the accident, the accident information reception unit 11 of the insurance server 10 receives the accident information (hereinafter referred to as "target accident information") is received from the operator of the insurance company (S201).

Subsequently, the metadata search unit 12 refers to the block chain C1 and acquires metadata corresponding to the target accident information from the block chain C1 (S202). Metadata corresponding to the target accident information includes shooting period information indicating a period including the date and time indicated by the occurrence date and time information of the target accident information, and metadata including GPS conversion data corresponding to the occurrence location information of the target accident information. data. However, the condition that the photographing period information indicating the period including the date and time indicated by the occurrence date and time information of the target accident information is included may not be used.

FIG. 7 is a diagram for explaining GPS-converted data corresponding to the generated position information. FIG. 7 shows a circle c1 whose center is the center of gravity point P1 shown in FIG. 5 and whose radius is the distance r1. Also, in FIG. 7, the point P2 corresponds to the position indicated by the occurrence position information. As shown in FIG. 7, when the circle c1 includes the point P2, the GPS-converted data is determined to be GPS-converted data according to the generated position information. On the other hand, when the point P2 is positioned outside the circle c1, it is determined that the GPS-converted data is not the GPS-converted data corresponding to the generated position information.

However, the GPS-converted data corresponding to the generated location information may be specified by other conditions. For example, the GPS conversion data may be data indicating the trajectory of the GPS data group of the conversion source. In this case, when the shortest distance between the trajectory and the point P2 is equal to or less than a threshold value, the GPS-converted data may be determined to be GPS-converted data according to the generated position information.

In short, in step S202, if the metadata corresponding to the DR data that may have captured the point P2 or the vicinity of the point P2 can be specified, the metadata corresponding to the target accident information can be specified by another method. good too.

Next, the DR data requesting unit 13 refers to the owner information included in each piece of metadata acquired by the metadata searching unit 12, and sends the metadata to the owner terminal 30 of the owner of each piece of metadata. (S203). The supply request specifies the DR data ID of the DR data. Note that there is a possibility that the same owner terminal 30 is requested to provide a plurality of pieces of metadata. In this case, one provision request including multiple DR data IDs may be transmitted to the owner terminal 30 in question.

Also, the DR data provision request may be registered in the block chain C1. In this case, the provision request may be sent to the owner terminal 30 by the smart contract of the blockchain C1.

When a provision request is made by e-mail or by registration in the block chain C1, the owner terminal 30, upon receiving the provision request, outputs a notification of receipt of the provision request. As a result, the owner (driver, etc.) can know the presence of the DR data provision request to itself.

Alternatively, the request for DR data may be made by telephone contact from the insurance company operator to the owner. In this case, the DR data requesting unit 13 may output a list of DR data IDs and owner information (telephone numbers) related to the provision request to the operator's terminal of the insurance company in step S202. In this case, the operator may request the provision of the DR data by calling the telephone number included in the list and notifying the owner of the DR data ID and the like. In this case, the owner can know the existence of the DR data provision request to himself/herself through the telephone.

When the owner learns of the existence of the request for provision of DR data to himself/herself, the owner inputs to the drive recorder 20 an instruction to reproduce the DR data corresponding to the DR data ID specified in the request for provision.

The drive recorder 20 reproduces the DR data for which the reproduction instruction is input (hereinafter referred to as "provided data") in response to the input of the reproduction instruction (S204). The owner views the data to be provided and inputs an instruction to upload the data to be provided to the drive recorder 20 when the owner judges that the data to be provided can be disclosed to the outside. On the other hand, if the owner determines that the data to be provided cannot be disclosed to the outside, the owner does not input the upload instruction.

The request for providing the DR data may specify a condition regarding the content of the image, such as "I want an image of the accident site at the XXX intersection." In this case, even if disclosure of the data to be provided is permissible, the owner need not input an upload instruction if the content of the data to be provided does not meet the conditions.

Note that when there are a plurality of pieces of data to be provided, steps S204 and subsequent steps are executed for each piece of data to be provided. Here, for convenience of explanation, it is assumed that there is one provision target data.

When the owner inputs an instruction to upload the data to be provided (S205), the drive recorder 20 executes steps S206 and subsequent steps. On the other hand, if the upload instruction is not input, step S206 and subsequent steps are not executed.

In step S206, the drive recorder 20 uses, for example, a cryptographic pseudo-random number generation function (SHA1PRNG, etc.) to generate a unique common key for each piece of data to be provided. Subsequently, the drive recorder 20 uses the common key (hereinafter referred to as "target common key") to encrypt the data to be provided (S207). A sufficiently strong common key encryption technology (AES256, etc.) may be used in the encryption. The purpose of encrypting the data to be provided is to prevent unauthorized decryption of the data to be provided in the upload path.
The encrypted data to be provided is hereinafter referred to as "encrypted DR data".

Subsequently, the drive recorder 20 encrypts the target common key using the insurance company's public key so that a third party other than the insurance company cannot obtain the target common key (S208). TLS 1.2 or the like may be used to use the regular public key. The encrypted target common key is hereinafter referred to as "encrypted common key".

Subsequently, the drive recorder 20 associates the encrypted DR data and the encrypted common key with the DR data ID of the encrypted DR data (hereinafter referred to as "target DR data ID") and uploads them to the block chain C1 (S209). As a result, the encrypted DR data and the encrypted common key are recorded in the block chain C1 in association with the target DR data ID.

After that, when the DR data acquisition unit 14 of the insurance server 10 detects the upload, it refers to the block chain C1 and retrieves the encrypted DR data, the encrypted common key, and the target DR data ID from the block chain C1. It acquires and records the acquired data in the auxiliary storage device 102 or the like (S210).

Note that the upload may be notified to the DR data acquisition unit 14 of the insurance server 10 by the smart contract of the blockchain C1. In this case, the DR data acquisition unit 14 may detect the upload based on a notification from the smart contract. Alternatively, the DR data acquisition unit 14 may check whether there is an upload to the blockchain C1 by polling.

Subsequently, the DR data verification unit 15 decrypts the encrypted common key using the private key of the insurance company (S211). As a result, a plaintext target common key is obtained. Subsequently, the DR data verification unit 15 decrypts the encrypted DR data using the target common key (S212). As a result, plaintext data to be provided is obtained. Subsequently, the DR data verification unit 15 calculates a hash value of the provision target data (S213). Next, the DR data verification unit 15 compares the hash value calculated in step S213 with the hash value included in the metadata corresponding to the target DR data ID among the metadata acquired in step S202. Then, it is determined whether or not the data to be provided has been falsified (S214). That is, when both match, the DR data verification unit 15 determines that the provision target data has not been falsified. On the other hand, if the two are different, the DR data verification unit 15 determines that the provision target data has been falsified. If it is determined that the provision target data has been falsified, the DR data verification unit 15 may discard the provision target data. This is because such data to be provided does not qualify as evidence of an accident.

In the above example, the encrypted DR data upload destination is the same block chain C1 as the metadata registration destination. It may be a chain.

As described above, according to the present embodiment, based on the metadata registered in the block chain C1, DR data to be requested to be provided is identified, and a request for provision of the DR data is made. Therefore, the owner of the DR data can prevent the outflow of DR data (photographed images) for which provision has not been requested.

Metadata also includes a hash value generated when DR data is captured. Therefore, the insurance server 10 can verify whether or not the obtained DR data has been tampered with based on the hash value. As a result, the insurance server 10 can collect DR data that has not been tampered with.

In addition, by giving the owner an opportunity to confirm the DR data related to the provision request, it is possible to prevent the DR data in which the owner's personal information and the like are recorded from being disclosed to the outside.

Note that in the present embodiment, the insurance server 10 is an example of an information processing device. The metadata search unit 12 is an example of a first acquisition unit. The DR data requesting section 13 is an example of a requesting section. The DR data acquisition unit 14 is an example of a second acquisition unit. Blockchain C1 is an example of a first blockchain and a second blockchain.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various Transformation and change are possible.

With respect to the above description, the following items are further disclosed.
(Appendix 1)
When receiving the designation of the position information, referring to the first blockchain that records the photographing position information of each photographed image taken by the in-vehicle camera, the processing of acquiring the photographing position information according to the designated position information. and,
a process of requesting a captured image specified by the acquired shooting position information to a recording source of the shooting position information in the first blockchain;
when the target captured image requested for provision is recorded in a second blockchain, referring to the second blockchain to obtain the target captured image;
A control method characterized in that the processing is executed by a computer.
(Appendix 2)
The first blockchain further records shooting date and time information of each captured image taken by the on-vehicle camera,
In the process of acquiring the photographing position information, when the designation of the position information and the date and time information is received, the first block chain is referred to, and the photographing position corresponding to the designated position information and the designated date and time information is obtained. Acquire information and shooting date and time information,
In the processing for requesting provision, a request is made to the recording source to provide the captured image specified by the acquired shooting position information and date and time information.
The control method according to Supplementary Note 1, characterized by:
(Appendix 3)
The first blockchain further records information of a recording source of shooting position information of each captured image captured by the on-vehicle camera,
The process of acquiring the shooting position information further includes acquiring information of a recording source of the shooting position information corresponding to the specified position information by referring to the first blockchain,
In the processing for requesting provision, provision of the captured image specified by the acquired shooting position information is requested based on the acquired information of the recording source.
The control method according to appendix 1 or 2, characterized by:
(Appendix 4)
The first blockchain further records a hash value of each photographed image photographed by the in-vehicle camera in association with photographing position information,
The process of acquiring the shooting position information further includes acquiring a first hash value associated with the shooting position information corresponding to the specified position information by referring to the first blockchain,
A computer executes a process of comparing a second hash value and the first hash value of the target captured image;
The control method according to any one of appendices 1 to 3, characterized in that:
(Appendix 5)
When the designation of the position information is received, the first block chain that records the photographing position information of each photographed image photographed by the in-vehicle camera is referred to, and the photographing position information corresponding to the designated position information is obtained. 1 acquisition unit;
a request unit for requesting a captured image specified by the acquired shooting position information to a recording source of the shooting position information in the first blockchain;
a second acquisition unit that acquires the target captured image by referring to the second blockchain when the target captured image requested for provision is recorded in a second blockchain;
An information processing device comprising:
(Appendix 6)
The first blockchain further records shooting date and time information of each captured image taken by the on-vehicle camera,
When the first acquisition unit receives designation of location information and date and time information, the first acquisition unit refers to the first blockchain, and captures location information and shooting location information according to the designated location information and the designated date and time information. Acquire shooting date and time information,
The request unit requests the recording source to provide the captured image specified by the acquired shooting position information and date and time information.
The information processing apparatus according to Supplementary Note 5, characterized by:
(Appendix 7)
The first blockchain further records information of a recording source of shooting position information of each captured image captured by the on-vehicle camera,
The first acquisition unit further acquires information of a recording source of the shooting position information corresponding to the designated position information by referring to the first blockchain,
The request unit requests provision of the captured image specified by the acquired shooting position information based on the acquired information of the recording source.
The information processing apparatus according to appendix 5 or 6, characterized by:
(Appendix 8)
The first blockchain further records a hash value of each photographed image photographed by the in-vehicle camera in association with photographing position information,
The first acquisition unit further acquires a first hash value associated with shooting position information corresponding to the designated position information by referring to the first blockchain,
A comparison unit that compares a second hash value of the target captured image and the first hash value,
The information processing apparatus according to any one of appendices 5 to 7, characterized by:
(Appendix 9)
An information processing system including an in-vehicle camera and an information processing device,
The information processing device is
When the designation of the position information is received, the first block chain that records the photographing position information of each photographed image photographed by the vehicle-mounted camera is referred to, and the photographing position information corresponding to the designated position information is obtained. a first acquisition unit;
a request unit for requesting a captured image specified by the acquired shooting position information to a recording source of the shooting position information in the first blockchain;
a second acquisition unit that acquires the target captured image by referring to the second blockchain when the target captured image requested for provision is recorded in a second blockchain;
An information processing system characterized by having:
(Appendix 10)
The first blockchain further records shooting date and time information of each captured image taken by the on-vehicle camera,
When the first acquisition unit receives designation of location information and date and time information, the first acquisition unit refers to the first blockchain, and captures location information and shooting location information according to the designated location information and the designated date and time information. Acquire shooting date and time information,
The request unit requests the recording source to provide the captured image specified by the acquired shooting position information and date and time information.
The information processing system according to appendix 9, characterized by:
(Appendix 11)
The first blockchain further records information of a recording source of shooting position information of each captured image captured by the on-vehicle camera,
The first acquisition unit further acquires information of a recording source of the shooting position information corresponding to the designated position information by referring to the first blockchain,
The request unit requests provision of the captured image specified by the acquired shooting position information based on the acquired information of the recording source.
The information processing system according to appendix 9 or 10, characterized by:
(Appendix 12)
The first blockchain further records a hash value of each photographed image photographed by the in-vehicle camera in association with photographing position information,
The first acquisition unit further acquires a first hash value associated with shooting position information corresponding to the designated position information by referring to the first blockchain,
The information processing device is
A comparison unit that compares a second hash value of the target captured image and the first hash value,
12. The information processing system according to any one of appendices 9 to 11, characterized by:
(Appendix 13)
When receiving the designation of the position information, referring to the first blockchain that records the photographing position information of each photographed image taken by the in-vehicle camera, the processing of acquiring the photographing position information according to the designated position information. and,
a process of requesting a captured image specified by the acquired shooting position information to a recording source of the shooting position information in the first blockchain;
when the target captured image requested for provision is recorded in a second blockchain, referring to the second blockchain to obtain the target captured image;
A program characterized by causing a computer to execute processing.
(Appendix 14)
The first blockchain further records shooting date and time information of each captured image taken by the on-vehicle camera,
In the process of acquiring the photographing position information, when the designation of the position information and the date and time information is received, the first block chain is referred to, and the photographing position corresponding to the designated position information and the designated date and time information is obtained. Acquire information and shooting date and time information,
In the processing for requesting provision, a request is made to the recording source to provide the captured image specified by the acquired shooting position information and date and time information.
The program according to appendix 13, characterized by:
(Appendix 15)
The first blockchain further records information of a recording source of shooting position information of each captured image captured by the on-vehicle camera,
The process of acquiring the shooting position information further includes acquiring information of a recording source of the shooting position information corresponding to the specified position information by referring to the first blockchain,
In the processing for requesting provision, provision of the captured image specified by the acquired shooting position information is requested based on the acquired information of the recording source.
15. The program according to appendix 13 or 14, characterized by:
(Appendix 16)
The first blockchain further records a hash value of each photographed image photographed by the in-vehicle camera in association with photographing position information,
The process of acquiring the shooting position information further includes acquiring a first hash value associated with the shooting position information corresponding to the specified position information by referring to the first blockchain,
causing a computer to execute a process of comparing a second hash value and the first hash value of the target captured image;
16. The program according to any one of appendices 13 to 15, characterized by:

1 Information processing system 10 Insurance server 11 Accident information reception unit 12 Metadata search unit 13 DR data request unit 14 DR data acquisition unit 15 DR data verification unit 20 Drive recorder 30 Owner terminal 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 interface device B bus C1 block chain

Claims (7)

When receiving the designation of the position information, referring to the first blockchain that records the photographing position information of each photographed image taken by the in-vehicle camera, the processing of acquiring the photographing position information according to the designated position information. and,
a process of requesting a captured image specified by the acquired shooting position information to a recording source of the shooting position information in the first blockchain;
when the target captured image requested for provision is recorded in a second blockchain, referring to the second blockchain to obtain the target captured image;
A control method characterized in that the processing is executed by a computer. The first blockchain further records shooting date and time information of each captured image taken by the on-vehicle camera,
In the process of acquiring the photographing position information, when the designation of the position information and the date and time information is received, the first block chain is referred to, and the photographing position corresponding to the designated position information and the designated date and time information is obtained. Acquire information and shooting date and time information,
In the processing for requesting provision, a request is made to the recording source to provide the captured image specified by the acquired shooting position information and date and time information.
2. The control method according to claim 1, wherein: The first blockchain further records information of a recording source of shooting position information of each captured image captured by the on-vehicle camera,
The process of acquiring the shooting position information further includes acquiring information of a recording source of the shooting position information corresponding to the specified position information by referring to the first blockchain,
In the processing for requesting provision, provision of the captured image specified by the acquired shooting position information is requested based on the acquired information of the recording source.
3. The control method according to claim 1, wherein: The first blockchain further records a hash value of each photographed image photographed by the in-vehicle camera in association with photographing position information,
The process of acquiring the shooting position information further includes acquiring a first hash value associated with the shooting position information corresponding to the specified position information by referring to the first blockchain,
A computer executes a process of comparing a second hash value and the first hash value of the target captured image;
4. The control method according to any one of claims 1 to 3, characterized in that: When the designation of the position information is received, the first block chain that records the photographing position information of each photographed image photographed by the in-vehicle camera is referred to, and the photographing position information corresponding to the designated position information is obtained. 1 acquisition unit;
a request unit for requesting a captured image specified by the acquired shooting position information to a recording source of the shooting position information in the first blockchain;
a second acquisition unit that acquires the target captured image by referring to the second blockchain when the target captured image requested for provision is recorded in a second blockchain;
An information processing device comprising: An information processing system including an in-vehicle camera and an information processing device,
The information processing device is
When the designation of the position information is received, the first block chain that records the photographing position information of each photographed image photographed by the vehicle-mounted camera is referred to, and the photographing position information corresponding to the designated position information is obtained. a first acquisition unit;
a request unit for requesting a captured image specified by the acquired shooting position information to a recording source of the shooting position information in the first blockchain;
a second acquisition unit that acquires the target captured image by referring to the second blockchain when the target captured image requested for provision is recorded in a second blockchain;
An information processing system characterized by having: When receiving the designation of the position information, referring to the first blockchain that records the photographing position information of each photographed image taken by the in-vehicle camera, the processing of acquiring the photographing position information according to the designated position information. and,
a process of requesting a captured image specified by the acquired shooting position information to a recording source of the shooting position information in the first blockchain;
when the target captured image requested for provision is recorded in a second blockchain, referring to the second blockchain to obtain the target captured image;
A program characterized by causing a computer to execute processing.

Images