Data authentication system and data authentication method

The data authenticity certification system verifies data integrity by calculating eigenvalues at different times to ensure only untampered data is stored, addressing the inability of existing systems to prove data authenticity during registration.

JP7578079B2Active Publication Date: 2024-11-06DENSO CORP
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2021129532
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-08-06
Publication Date
2024-11-06
Estimated Expiration
2041-08-06

AI Technical Summary

Technical Problem

Existing data authenticity systems cannot prove that data stored on a server has not been tampered with during the registration process, despite measures to prevent tampering.

Method used

A data authenticity certification system that calculates unique eigenvalues (hash values) at different times for the data before and after registration, ensuring that only untampered data is stored, using a server and storage device with eigenvalue calculation units and comparison units to verify authenticity.

Benefits of technology

The system effectively proves that registered data is genuine by ensuring that any tampering between reception and registration results in different eigenvalues, preventing the storage of tampered data.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007578079000001
    Figure 0007578079000001
  • Figure 0007578079000002
    Figure 0007578079000002
  • Figure 0007578079000003
    Figure 0007578079000003
Patent Text Reader

Abstract

To provide a data authentication system and a data authentication method for authenticating registered data.SOLUTION: A data authentication system 10 calculates with different timing a hash value A and a hash value B out of evidence data transmitted from a terminal device 12 and when the hash data A and the hash value B are equal, stores the evidence data in a storage device 16, thereby registering the evidence data. If the evidence data is altered or the like in a period from reception of the evidence data from the terminal device 12 to the registration in the storage device 16, the hash data A and the hash value B become different from each other and the evidence data is never registered.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a data authenticity certification system and a data authenticity certification method. [Background technology]

[0002] There have been cases where proof was required that stored data (digital data) had not been tampered with.

[0003] Here, Patent Document 1 describes an evidential data storage system for preventing troubles between a service provider and a service user or between service users when providing a service. A user of this evidential data storage system can display the evidential data stored in the server on the display device of his / her own terminal, and can use this evidential data as a material for resolving troubles when they occur. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2018-151825 A Summary of the Invention [Problem to be solved by the invention]

[0005] Here, even if the data is prevented from being tampered with or fraudulent by technology such as blockchain, it is assumed that the data has not been tampered with at the time of registering it for storage. Although a user of the evidence data storage system described in Patent Document 1 stores captured image data as evidence data in a server, he or she cannot prove that the data has not been tampered with at the time of registering it for storage.

[0006] In view of the above background, an object of the present invention is to provide a data authenticity certification system and a data authenticity certification method that can certify that registered data is authentic data. [Means for solving the problem]

[0007] The present invention employs the following technical means to solve the above problems. The reference characters in the claims and in this section are merely examples showing the corresponding relationship with the specific means described in the embodiments below as one aspect, and do not limit the technical scope of the present invention.

[0008] A data authenticity certification system according to one embodiment of the present invention is a data authenticity certification system (10) that certifies that data received by a server (14) from a terminal device (12) operated by a user has not been tampered with, and includes a first eigenvalue calculation unit (30) that calculates a first eigenvalue, which is a value unique to the data, a second eigenvalue calculation unit (32) that calculates a second eigenvalue, which is a value unique to the data, at a timing different from the calculation of the first eigenvalue by the first eigenvalue calculation unit, a comparison unit (34) that compares the first eigenvalue with the second eigenvalue, and a registration unit (38) that registers the data by storing the data in a storage device (16) when the comparison unit determines that the first eigenvalue and the second eigenvalue are the same.

[0009] According to this configuration, the first unique value and the second unique value are calculated from the data to be registered at different times, and if the first unique value and the second unique value are the same, the data is registered by storing the calculated first unique value and the second unique value in the storage device. Note that the unique value here is, for example, a hash value. If the data is tampered with between receiving the data from the terminal device and registering it in the storage device, the first unique value and the second unique value will be different values, and the data will not be registered. Therefore, according to this configuration, it is possible to prove that the registered data is authentic.

[0010] A data authenticity proof method of one embodiment of the present invention is a data authenticity proof method for proving that data received by a server from a terminal device operated by a user has not been tampered with, and includes the following steps: a first step in which a first eigenvalue calculation unit calculates a first eigenvalue, which is a value unique to the data; a second step in which a second eigenvalue calculation unit calculates a second eigenvalue, which is a value unique to the data, at a timing different from the calculation of the first eigenvalue by the first eigenvalue calculation unit; a third step in which a comparison unit compares the first eigenvalue and the second eigenvalue; and a fourth step in which a registration unit registers the data by storing the data in a storage device when the comparison unit determines that the first eigenvalue and the second eigenvalue are the same. Effect of the Invention

[0011] According to the present invention, it is possible to prove that registered data is authentic. [Brief description of the drawings]

[0012] [Figure 1] 1 is a schematic configuration diagram of a data authenticity certification system according to a first embodiment. [Diagram 2] FIG. 2 is a functional block diagram of a terminal device and a server according to the first embodiment. [Diagram 3] 13 is a flowchart showing the flow of evidence data transmission processing in the first embodiment. [Figure 4] 13 is an example of data generated in the evidence data transmission process of the first embodiment. [Diagram 5] 11 is a flowchart showing the flow of a hash value calculation process according to the first embodiment. [Figure 6] 4 is an example of data generated in a hash value calculation process according to the first embodiment. [Figure 7] 13 is a flowchart showing a flow of evidence data confirmation processing in the first embodiment. [Figure 8] 13 is an example of data generated in the evidence data confirmation process of the first embodiment. [Figure 9] 11 is a flowchart showing the flow of evidence data registration processing in the first embodiment. [Figure 10] 4 is an example of data generated in the evidence data registration process of the first embodiment. [Figure 11] FIG. 11 is a functional block diagram of a terminal device and a server according to a second embodiment. [Figure 12] FIG. 13 is a functional block diagram of a terminal device and a server according to a third embodiment. [Figure 13] FIG. 13 is a schematic diagram showing a method for calculating a modified hash value according to the third embodiment. [Figure 14] FIG. 13 is a schematic diagram showing a method for calculating a hash value according to the fourth embodiment. [Figure 15] 13 is a flowchart showing the flow of evidence data transmission processing in the fifth embodiment. [Figure 16] 23 is a flowchart showing the flow of a QR code issuing process according to the sixth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below shows an example of a case where the present invention is implemented, and the present invention is not limited to the specific configuration described below. In implementing the present invention, a specific configuration according to the embodiment may be appropriately adopted.

[0014] (First embodiment) 1 is a schematic diagram of a data authenticity certification system 10 according to this embodiment. The data authenticity certification system 10 according to this embodiment includes a terminal device 12 used by a user, a server 14 that performs authenticity certification of evidence data, and a storage device 16 that stores the evidence data. The terminal device 12 is preferably a device equipped with a camera, a global positioning system (GPS) or various sensors, a computing device, a storage area, a communication device, etc., and examples of the terminal device 12 include a surveillance camera with a sensor, a smartphone, a tablet terminal, a notebook computer, a desktop computer equipped with a camera, a drone, a robot, smart glasses, etc.

[0015] The data authenticity certification system 10 of the embodiment is a third-party data generation system that generates data requiring authentication under the management of the system in a terminal device 12 operated by a user, and certifies that the data forcibly transmitted from the terminal device 12 to a server 14 has not been tampered with. In other words, until the data generated by the data authenticity certification system 10 is stored in the storage device 16, not only a person who illegally accesses the terminal device 12 but also the user of the terminal device 12 cannot tamper with the evidence data.

[0016] As an example, the data authenticity certification system 10 of this embodiment registers still image data (hereinafter referred to as "photographed data") acquired by a camera 20 (see Figure 2) equipped to the terminal device 12, as well as the shooting time and shooting location of the photographed data, as evidence data by storing them in the storage device 16 via the server 14.

[0017] The server 14 of this embodiment is provided in the cloud or on-premise, and can be accessed from the terminal device 12. The server 14 of this embodiment performs a data authenticity certification process that certifies that the evidence data to be registered has not been tampered with and is authentic by calculating a unique value calculated from the evidence data stored in the storage device 16 multiple times at different timings and determining whether the unique values ​​are identical. In other words, the data authenticity certification system 10 of this embodiment certifies that the evidence data has not been tampered with while performing the registration process of the evidence data transmitted from the terminal device 12.

[0018] In addition, the unique value calculated from the evidence data in this embodiment is a hash value, for example.

[0019] The storage device 16 of this embodiment is provided in the cloud or on-premise, and can be accessed from the terminal device 12. Examples of the storage device 16 of this embodiment include a database, storage, and blockchain, in which evidence data such as shooting data is stored in the storage, evidence information such as GPS information and date and time information of the shooting data and paths of the evidence data stored in the storage are stored in the database, and basic information of the evidence data is stored in the blockchain. Note that, in this embodiment, one storage device 16 includes a database, storage, and blockchain, but this is not limiting, and the database, storage, and blockchain may be stored separately in different storage devices.

[0020] An overview of the data authenticity certification process of this embodiment will be described with reference to FIG. 1. First, the terminal device 12 transmits evidence data to the server 14 as a registration request based on a user operation. The server 14 temporarily stores (hereinafter referred to as "temporarily stored") the received evidence data, and calculates a hash value A based on this evidence data. Thereafter, the server 14 transmits a confirmation request to the terminal device 12 to have the user confirm the evidence data. After the user completes the confirmation, the terminal device 12 calculates a hash value B from the temporarily stored evidence data, and compares the hash value A with the hash value B. If the hash value A and the hash value B are identical, the server 14 registers the evidence data by storing the evidence data in the storage device 16. Note that the evidence data registered in the storage device 16 is stored, as an example, by a block chain.

[0021] FIG. 2 is a functional block diagram showing the functions of the server 14 in this embodiment.

[0022] In addition to the camera 20, the terminal device 12 also includes a forced data transmission control unit 22, a data transmission / reception unit 24, and a storage unit .

[0023] The forced data transmission control unit 22 controls the data transceiver unit 24 to transmit the captured image data to the server 14 immediately after the terminal device 12 generates evidence data, in this embodiment, immediately after the camera 20 acquires the captured image data. Forced transmission here refers to transmitting evidence data to the server 14 without obtaining permission from the user operating the terminal device 12. Note that when the forced data transmission control unit 22 transmits evidence data to the server 14, the evidence data is not stored in the terminal device 12.

[0024] The data transmission / reception unit 24 transmits and receives data to and from other information processing devices such as the server 14, a printing device, and the like.

[0025] The storage unit 26 stores various programs executed by the terminal device 12 and various data.

[0026] The server 14 includes a first hash value calculation unit 30, a second hash value calculation unit 32, a comparison unit 34, a reception time determination unit 36, a registration unit 38, a QR code generation unit 40, a storage unit 42, and a data transmission / reception unit 44.

[0027] The first hash value calculation section 30 calculates a hash value A which is a value unique to the evidence data.

[0028] The second hash value calculation unit 32 calculates a hash value B, which is a value unique to the evidence data, at a timing different from the calculation of the hash value A by the first hash value calculation unit 30.

[0029] The first hash value calculation unit 30 and the second hash value calculation unit 32 may be a single hash value calculation unit.

[0030] The comparison unit 34 compares the hash value A with the hash value B, and determines whether the hash value A and the hash value B are the same.

[0031] The reception time determination unit 36 ​​determines that the received evidence data is not authentic when the difference between the generation time of the evidence data and the reception time of the evidence data is equal to or greater than a predetermined time. Note that this predetermined time is, for example, 5 seconds.

[0032] If the comparison unit 34 determines that the hash value A and the hash value B are the same, the registration unit 38 stores the evidence data in the storage device 16, thereby registering the evidence data.

[0033] The QR code generating unit 40 generates an information code indicating the registration information of the evidence data stored in the storage device 16. In this embodiment, the information code is a QR code (registered trademark) as an example, but is not limited to this, and the information code may be another two-dimensional code such as SQRC (registered trademark) or a barcode which is a one-dimensional code. A user or the like can check the registered evidence data by reading this QR code with the terminal device 12 or the like.

[0034] The storage unit 42 stores various data such as a program for executing the data authenticity certification process, each piece of data received from the terminal device 12, and data generated in the data authenticity certification process.

[0035] The data transmission / reception unit 44 transmits and receives data between the terminal device 12 and other information processing devices such as the storage device 16 .

[0036] Next, various processes included in the data authenticity certification process will be described with reference to a flowchart. Each process included in the data authenticity certification process is executed by a program stored in a storage medium such as the storage unit 26 of the terminal device 12 or the storage unit 42 of the server 14. Execution of this program executes a method corresponding to the program.

[0037] 3 is a flowchart showing the flow of the evidence data transmission process. The evidence data transmission process is a process for transmitting photographed data as evidence data from the terminal device 12 to the server 14, and is executed by the terminal device 12. Note that the evidence data transmission process is performed by starting an application preinstalled in the terminal device 12, or by starting a browser and accessing an application for transmitting the evidence data.

[0038] First, in step S100, a user photographs a subject using the camera function of the terminal device 12 to obtain photographed data to be used as evidence data.

[0039] In the next step S102, shooting state data indicating the state when the shooting data was acquired is acquired. As shown in Fig. 4(A), the shooting state data is data including, for example, Base64 data obtained by converting the shooting data (hereinafter referred to as "shooting Base64 data"), the shooting date and time of the shooting data, and the shooting location. Note that the shooting location is the latitude and longitude acquired by the GPS function of the terminal device 12.

[0040] In the next step S104, a format check is performed on the shooting status data. If the format check is successful, the process proceeds to step S106. If the format check is unsuccessful, the evidence data transmission process is terminated. The format check is, for example, checking whether the items and format of the shooting status data satisfy predetermined conditions. The same applies to the format checks in each process described below.

[0041] In step S106, registration data is generated. The registration data is data in which an ID (token ID) is added to the shooting state data, as shown in Fig. 4(B). Note that the array of evidence data in Fig. 4(B) is the shooting date and time, shooting location, and shooting Base64 data included in the shooting state data.

[0042] In the next step S108, the forced data transmission control unit 22 controls the data transmission / reception unit 24 to transmit the registration data to the server 14, thereby transmitting the registration data to the server 14 and terminating this evidence data transmission process.

[0043] FIG. 5 is a flowchart showing the flow of the hash value calculation process executed by the server 14 that has received the registration data.

[0044] First, when the server 14 receives the registration data from the terminal device 12, in step S200, the reception time determination unit 36 ​​checks the reception time of the registration data.

[0045] In the next step S202, the reception time determination unit 36 ​​determines whether the reception time of the received registration data is appropriate, and if the determination is positive, the process proceeds to step S204, and if the determination is negative, the hash value calculation process ends. If the shooting time read from the registration data and the reception time of the registration data differ by more than a predetermined time, the reception time determination unit 36 ​​determines that the data is not appropriate, that is, that the evidence data indicated by the received registration data is not authentic. If the shooting time and the reception time differ by more than a predetermined time, this indicates the possibility that some kind of tampering has been performed on the shooting data.

[0046] In the next step S204, the format of the registration data is confirmed, and in step S206, it is determined whether or not the format is appropriate. If the determination is positive, the process proceeds to step S208, whereas if the determination is negative, the hash value calculation process is terminated.

[0047] When the determination in step S202 or step S204 is negative and the hash value calculation process is terminated, the server 14 transmits failure information to the terminal device 12.

[0048] In the next step S208, the photographing Base64 data included in the registration data is decoded and stored in the storage unit 42. The path of the photographing data stored in the storage unit 42 is acquired as a temporary storage path.

[0049] In the next step S210, the first hash value calculation section 30 calculates a hash value of the captured image data obtained by decoding (hereinafter referred to as the "captured image data hash value").

[0050] In the next step S212, the first hash value calculation unit 30 calculates a temporary storage hash value. The temporary storage hash value is a value obtained by forming the shooting date and time, GPS latitude, GPS longitude, shooting data hash value, and temporary storage path of the shooting data into a character string and hashing the character string. This temporary storage hash value corresponds to the above-mentioned hash value A. The forming here refers to combining the letters and numbers that constitute the shooting date and time, GPS latitude, GPS longitude, shooting data hash value, and temporary storage path of the shooting data into one piece of data.

[0051] In the next step S214, various data are registered in the temporary storage table and stored in the storage unit 42. As shown in Fig. 6(A), the temporary storage table is data in which the temporary storage hash value, the shooting date and time of the shooting data, the GPS latitude, the GPS longitude, the shooting data hash value, and the temporary storage path are recorded.

[0052] In the next step S216, user confirmation data is generated. The user confirmation data is data consisting of a processing result, a processing code, a message, and a temporarily stored hash value, as shown in Fig. 6(B). The user confirmation data is data for having the user confirm the photographic data to be registered, and is a return value.

[0053] In the next step S218, the user verification data is transmitted to the terminal device 12 via the data transmitter / receiver 44, and the hash value calculation process is terminated.

[0054] 7 is a flowchart showing the flow of evidence data confirmation processing executed by the terminal device 12 when the terminal device 12 receives user confirmation data. As described above, in this embodiment, evidence data is generated by the terminal device 12, and is also forcibly transmitted to the server 14, and the evidence data is not left in the terminal device 12. For this reason, the user will confirm the evidence data (photographed data in this embodiment) through the evidence data confirmation processing.

[0055] First, in step S300, the photographed data is displayed on the display of the terminal device 12. In order to display the photographed data on the display, as an example, a temporary storage table stored in the server 14 is read based on the temporary storage hash value included in the confirmation data, which is the return value. Then, the photographed data indicated by the temporary storage path included in the temporary storage table is read, and the photographed data is displayed on the display.

[0056] The display of the terminal device 12 displays a comment field, a send button, and a retake button together with the photographed data. The user can input any text or numbers into the comment field. The send button is operated (pressed) when the user confirms that the photographed data displayed on the display is appropriate. On the other hand, the retake button is operated (pressed) when the user determines that the photographed data displayed on the display is not appropriate.

[0057] In the next step S301, the user checks the image of the photographed data displayed on the display, and if the user determines that the photographed data is appropriate, the process proceeds to step S302, where the user operates the send button. On the other hand, if the user determines that the photographed data is not appropriate, the process proceeds to step S310, where the user operates the retake button.

[0058] In step S304, which follows step S302, confirmed data is generated. As shown in Fig. 8, the confirmed data is data consisting of a token ID, a temporarily stored hash value, and a comment. The token ID is the same as the token ID of the registration data shown in Fig. 4(B). The temporarily stored hash value is the same as the temporarily stored hash value of the user confirmation data shown in Fig. 6(B). The comment is a character string entered by the user in the comment field, and will be included as part of the evidence data array.

[0059] In the next step S306, a format check is performed on the generated confirmed data, and if the format check is successful, the process proceeds to step S308, and if it is unsuccessful, the evidence data confirmation process is terminated.

[0060] In step S308, the confirmed data is sent to the server 14, and the evidence data confirmation process ends.

[0061] On the other hand, in step S312, which follows step S310, the evidence data transmission process described with reference to Fig. 3 is performed, the photographed data to be the evidence data is acquired again, and the acquired photographed data is transmitted as the evidence data to the server 14. Thereafter, the hash value calculation process shown in Fig. 5 is performed, and the process returns to step S300.

[0062] FIG. 9 is a flowchart showing the flow of evidence data registration processing executed by the server 14 when the server 14 receives confirmed data.

[0063] First, in step S400, a format check is performed on the received confirmed data, and if the format check is successful, the process proceeds to step S402, and if it is unsuccessful, the evidence data registration process is terminated.

[0064] In the next step S402, a temporary storage table that contains the same temporary storage hash value as the temporary storage hash value contained in the confirmed data is searched for and read from the storage unit 42. If the temporary storage table cannot be read from the storage unit 42, it means that either the confirmed data or the temporary storage table stored in the storage unit 42 has been tampered with.

[0065] In the next step S404, the shooting date and time, GPS latitude, GPS longitude, shooting data hash value, and temporary storage path are read from the read temporary storage table, and these are converted into character strings and hashed, thereby calculating a temporary storage hash value by the second hash value calculation unit 32. The temporary storage hash value calculated in this step S404 corresponds to the above-mentioned hash value B.

[0066] In the next step S406, the comparison unit 34 compares the temporarily stored hash value (hash value A) included in the confirmed data with the temporarily stored hash value (hash value B) calculated in step S404, and determines whether these hash values ​​are the same. If they are the same in step S406, that is, if the result is a positive judgment, the process proceeds to step S408, and if they are not the same, that is, if the result is a negative judgment, the evidence data registration process is terminated.

[0067] In the next step S408, various data are obtained from the temporary storage table.

[0068] In the next step S410, the photographed data is read from the storage unit 42 using the temporary storage path acquired from the temporary storage table. Then, the registration unit 38 uploads the photographed data to the storage device 16 as evidence data, and the storage device 16 stores (registers) the photographed data in storage. The path of the storage storing the photographed data is stored in the database of the storage device 16, and this path is acquired as a registered evidence file storage path.

[0069] In the next step S412, the registration unit 38 generates an evidence ID. The evidence ID is, for example, a Merkle root of the registrant's name of the evidence data, the registration date and time, the photography date and time, the GPS latitude, the GPS longitude, a comment, the photography data hash value, the registered evidence file storage path, and the value up to the deletion flag, and is treated as a hash value.

[0070] In the next step S414, the evidence ID, the name of the registrant, the registration date and time, the photography date and time, the GPS latitude, the GPS longitude, the comment, the photography data hash value, the registered evidence file storage path, and the deletion flag are registered in the evidence table shown in Fig. 10(A). This evidence table is stored in the storage device 16.

[0071] In the next step S416, the registration unit 38 generates an information ID (key value). The information ID is the evidence ID, management information ID, registration date and time, and the Merkle root of the date hash, as shown in Fig. 10(B), and is set as a hash value.

[0072] In the next step S418, the registration unit 38 registers the evidence data in the blockchain.

[0073] In the next step S420, the QR code generating unit 40 generates a QR code based on the information ID.

[0074] In the next step S422, the data transmitter / receiver 44 transmits the QR code data shown in Fig. 10(C) to the terminal device 12, and ends this evidence data registration process. Note that the QR code indicated by the QR code data is, for example, data in Base64 format, but is not limited to this and may be data in another format.

[0075] The user of the terminal device 12 that has received the QR code data may, for example, print the QR code and attach it to a product or its packaging. A purchaser of the product may then read the attached QR code with an evidence data reading application to read the evidence data (photographed data).

[0076] In addition, when reading out the photographed data using a QR code, a photographed data hash value of the photographed data may also be calculated, and this hash value may be compared with the photographed data hash value contained in the evidence table to determine whether they are identical.

[0077] Specifically, the photographing data is read from the storage based on the registered evidence file storage path included in the read evidence table, and a photographing data hash value is calculated. Then, this photographing data hash value is compared with the photographing data hash value recorded in the evidence table to determine whether they are the same. If they are the same, the photographing data read from the blockchain is displayed. On the other hand, if they are not the same, the photographing data registered in the blockchain may have been tampered with, so the photographing data is not displayed.

[0078] As described above, the data authenticity certification system 10 of this embodiment transmits evidence data generated by the terminal device 12 to the server 14 without storing it in the terminal device 12. The server 14 calculates hash value A and hash value B from the received evidence data at different times, and if hash value A and hash value B are the same, stores the evidence data in the storage device 16, thereby registering the evidence data. If the evidence data is tampered with between receiving it from the terminal device 12 and registering it in the storage device 16, the hash value A and the hash value B will be different values, and the evidence data will not be registered. Therefore, according to the data authenticity certification system 10 of this embodiment, it is possible to prove that the registered evidence data is authentic data.

[0079] 7 is executed, the evidence data confirmation process may not be executed. Even in this embodiment, the calculation of hash value B is performed at a timing different from the calculation of hash value A, and if hash value A and hash value B are the same, they are stored in storage device 16, thereby registering the evidence data.

[0080] Second embodiment The data authenticity certification system 10 of this embodiment will be described below. Fig. 11 is a schematic diagram of the data authenticity certification system 10 of this embodiment. Note that the same components in Fig. 11 as those in Fig. 2 are given the same reference numerals and their description will be omitted.

[0081] The terminal device 12 of this embodiment includes a hash value calculation unit 21 in addition to the components described in the first embodiment.

[0082] The hash value calculation unit 21 calculates a hash value (hereinafter referred to as "hash value a") that is a value unique to evidence data. When the terminal device 12 of this embodiment generates photographed data to be evidence data, the hash value calculation unit 21 calculates a photographed data hash value (hash value a) from the photographed Base64 data. Then, the terminal device 12 adds the hash value a to the registration data shown in FIG. 4(B) and transmits it to the server 14 via the data transmission / reception unit 24.

[0083] The server 14 of this embodiment has the same configuration as that described in the first embodiment, but the comparison unit 34 compares the received hash value a with the hash value A calculated by the first hash value calculation unit 30.

[0084] Then, when the comparison unit 34 determines that the hash value a and the hash value A are the same, the server 14 generates confirmation data and transmits it to the terminal device 12. Thereafter, the evidence data confirmation process and the evidence data registration process described in the first embodiment are performed, and the evidence data is registered by storing the captured data in the storage device 16.

[0085] Third embodiment The data authenticity certification system 10 of this embodiment will be described below. Fig. 12 is a schematic diagram of the data authenticity certification system 10 of this embodiment. Note that the same components in Fig. 12 as those in Fig. 11 are given the same reference numerals and their description will be omitted.

[0086] The server 14 includes a pattern data selection unit 43, and a plurality of pattern data each showing a different predetermined rule is stored in a storage unit .

[0087] The pattern data selection unit 43 selects one piece of pattern data from among the multiple pieces of pattern data. The pattern data selected by the pattern data selection unit 43 is transmitted to the terminal device 12 via the data transmission / reception unit 44. The hash value A calculated by the terminal device 12 changes based on a rule (hereinafter referred to as a "pattern") indicated by the pattern data. In the following description, a hash value modified based on a pattern is referred to as a modified hash value.

[0088] As an example of the pattern, as shown in the schematic diagram of Fig. 13, the photographed Base64 data is mixed into the photographed data hash value calculated from the photographed Base64 data. The underlined character strings in the transformed hash value shown in Fig. 13 are the photographed Base64 data mixed into the hash value. Note that the pattern is not limited to this, and may be, for example, a rule for mixing a predetermined character string into the hash value, or a rule for rearranging the calculated hash values.

[0089] The hash value calculation unit 21 included in the terminal device 12 changes the calculated photographic data hash value (hash value a) based on the pattern data received from the server 14 to generate a modified hash value. The modified hash value is transmitted to the server 14 via the data transmission / reception unit 44 together with the registration data.

[0090] When the server 14 receives the registration data and the modified hash value from the terminal device 12, it temporarily stores them in the storage unit 42. Then, the modified hash value is restored to the original photographed data hash value (hash value a) based on the pattern data transmitted to the terminal device 12. Then, the first hash value calculation unit 30 calculates the photographed data hash value (hash value A) from the photographed Base64 data included in the registration data, and the comparison unit 34 compares the hash value a with the hash value A.

[0091] Note that server 14 may change the image capture data hash value calculated by first hash value calculation unit 30 to a modified hash value based on the pattern data, without restoring the modified hash value to the original image capture data hash value, and compare this modified hash value with the modified hash value received from terminal device 12. In addition, the server that transmits the pattern data to terminal device 12 may be a server different from server 14.

[0092] Thus, according to the data authenticity certification system 10 of this embodiment, the hash value a calculated from the evidence data is changed in a predetermined pattern and transmitted from the terminal device 12 to the server 14, making it more difficult to tamper with the evidence data in the process of transmitting it from the terminal device 12 to the server 14.

[0093] (Modification of the third embodiment) In a form in which evidence data is changed using pattern data, the evidence data does not necessarily have to be hashed.

[0094] For example, the terminal device 12 changes the photographed Base64 data of the evidence data based on the pattern data, and transmits the changed photographed Base64 data (hereinafter referred to as "changed evidence data") together with the registration data to the server 14. When the server 14 receives the registration data and the transformed evidence data, the server 14 restores the transformed evidence data to the original photographed Base64 data based on the pattern data, compares the returned photographed Base64 data with the photographed Base64 data included in the registration data, and registers the evidence data in the storage device 16 if they are identical.

[0095] (Fourth embodiment) The method of calculating the hash value by the hash value calculation unit 21 included in the terminal device 12 is not limited to the calculation method described in the above embodiment, and other calculation methods may be used.

[0096] The hash value calculation unit 21 may calculate the hash value a from the data divided into a plurality of parts. As a specific example, the hash value calculation unit 21 may divide the photographed Base64 data into a plurality of parts, calculate a Merkle hash from the divided data, and set it as the hash value a. In the example of Fig. 14, the photographed Base64 data is divided into three parts, and hash values ​​are calculated for the first divided data and the second divided data, and the hash value a is calculated from the hash value and the third divided data.

[0097] Also, for example, image data to be evidence data may be divided into a plurality of pieces, and a hash value may be calculated for each of the divided image data or for each of the plurality of divided image data, and this may be set as hash value a.

[0098] Furthermore, when the evidence data is video data, the video data may be divided at regular intervals, a hash value may be calculated for each divided video data, and the hash values ​​may be arranged in chronological order to be the hash value a. In this case, while the video data is being shot, a hash value may be calculated from the video data at predetermined time intervals (e.g., every 3 seconds) and transmitted to the server 14. That is, while the video is being shot, a hash value may be calculated at predetermined time intervals. Furthermore, a Merkle hash may be calculated from a plurality of hash values ​​arranged in chronological order, and this Merkle hash may be used as a comparison target for authenticating the evidence data. Still image data may be obtained at predetermined time intervals from the video data, and a hash value for authenticating the evidence data may be calculated from this still image data.

[0099] The hash value a may also be calculated from other data (hereinafter referred to as "additional data") added to the evidence data. The additional data is, for example, metadata such as EXIF ​​(Exchangeable Image File Format) added to the image data. The hash value may be calculated only from the additional data, or may be calculated from the image data and the additional data.

[0100] In addition, the first hash value calculation unit 30 of the server 14 calculates the hash value A of the evidence data received from the terminal device 12 in a manner similar to the method used to calculate the hash value a by the hash value calculation unit 21 of the terminal device 12, and the comparison unit 34 compares the hash value a with the hash value A.

[0101] On the other hand, when comparing hash value A and hash value B calculated by server 14, the first hash value calculation unit 30 and the second hash value calculation unit 32 calculate the temporarily stored hash value described in the first embodiment. That is, when comparing hash value A and hash value B, hash values ​​are not calculated from data divided into a plurality of pieces or additional data.

[0102] Fifth embodiment The terminal device 12 of this embodiment has a function of dividing the storage area (memory space) of the storage unit 26 into a normal world and a secure world. The normal world is a normal storage area where data can be accessed, and the secure world is a storage area where access to data is restricted. In other words, the secure world is a high-security execution environment separated from the normal world, which is a normal execution environment. When the terminal device 12 of this embodiment cannot access the network, it divides the storage area into the normal world and the secure world by switching the operation mode of the CPU.

[0103] When terminal device 12 having such a function is unable to transmit or receive data to server 14 and is unable to send generated evidence data to server 14, it stores the evidence data in the secure world. This protects the evidence data from tampering from other external devices and the normal world in a state in which terminal device 12 is unable to access the network and is temporarily storing the evidence data in terminal device 12. Note that, if terminal device 12 becomes able to access the network after storing the evidence data in the secure world, the evidence data is sent to server 14.

[0104] Fig. 15 is a flowchart showing the flow of evidence data transmission processing in this embodiment. Note that the same steps in Fig. 15 as those in Fig. 3 are denoted by the same reference numerals as those in Fig. 3, and their explanations will be omitted in part or in whole.

[0105] In the evidence data transmission process of this embodiment, after generating registration data in step S106, the process proceeds to step S107.

[0106] In step 107, it is determined whether or not the terminal device 12 is connected to the network. If the determination is affirmative, the process proceeds to step 108, and if the determination is negative, the process proceeds to step 109.

[0107] In step S108, the registration data is transmitted to the server 14, and the evidence data transmission process ends.

[0108] On the other hand, in step S109, the registration data is stored in the secure world of the storage unit 26, and the process proceeds to step S107, where the registration data is stored in the secure world until the terminal device 12 is connected to the network. When the registration data stored in the secure world is transmitted to the server 14, the registration data is deleted from the secure world.

[0109] Sixth embodiment In the above embodiment, a form was described in which a QR code was issued after evidence data was registered, but in this embodiment, a form is described in which a QR code indicating identification information of the evidence data (evidence ID or management information ID, hereinafter referred to as "ID") is issued in advance, and the evidence data is registered in the storage device 16 in association with the ID indicated by the QR code.

[0110] FIG. 16 is a flowchart showing the flow of the QR code issuing process.

[0111] First, in step S500, a QR code is issued to a user. The ID of the evidence data is recorded in advance in this QR code. The QR code may be issued by printing, imprinting, marking, or the like on paper such as a label by a printing device and distributing it to the user, or may be transmitted as Base64 data to the user's terminal device 12. Note that the issued QR code may also record other information in advance in addition to the ID of the evidence data. The other information may be, for example, information about the subject when the evidence data is photographed data, information about the user who generated the evidence data, and the like.

[0112] In the next step S502, the terminal device 12 transmits the evidence data and the QR code generated by the terminal device 12 to the server 14. If the QR code has been issued by being printed on a label, the user reads the QR code using the terminal device 12 and transmits the read information to the server 14. The information read from the QR code is, as an example, QR code data in Base64 format, but is not limited to this and may be data in another format.

[0113] In the next step S504, the data authenticity verification process described in the above embodiment is executed.

[0114] In the next step S506, the registration unit 38 of the server 14 registers the evidence data, whose authenticity has been verified, in the storage device 16 in association with the ID indicated by the QR code.

[0115] Although the present invention has been described above using the above embodiment, the technical scope of the present invention is not limited to the scope described in the above embodiment. Various modifications or improvements can be made to the above embodiment without departing from the gist of the invention, and the forms with such modifications or improvements are also included in the technical scope of the present invention.

[0116] For example, in the above embodiment, the evidence data is image data of a still image, but the evidence data is not limited to this, and may be data other than image data. For example, various data such as video data, audio data, text data, numerical data, and data detected by a sensor may be applied as evidence data. Furthermore, in the above embodiment, the evidence data is added with location information (latitude and longitude), but other information such as a user's ID may be added to the evidence data in addition to or instead of the location information.

[0117] In the above embodiment, the form in which the evidence data is generated by the terminal device 12 has been described, but the present invention is not limited to this, and the evidence data may be generated by a device different from the terminal device 12. For example, photographed data acquired by a digital camera that does not have a communication function to the Internet may be transmitted to the terminal device 12, and the terminal device 12 may transmit the photographed data to the server 14 as evidence data.

[0118] In addition, in the above embodiment, a form has been described in which a QR code is applied as an information code indicating the registration information of evidence data stored in the storage device 16, but this is not limited to the above, and the information code may be issued in various formats, such as other two-dimensional codes or URLs (Uniform Resource Locators).

[0119] In addition, in the above embodiment, a form was described in which a unique value calculated from evidence data is used as a hash value, but this is not limited to this, and the unique value may be any other value as long as it is an irreversible value calculated from evidence data.

[0120] 3, a form has been described in which evidence data is transmitted to the server 14 without being stored in the terminal device 12, but the form is not limited thereto, and evidence data generated in the terminal device 12 may be transmitted to the server 14 or stored in the storage unit 26 of the terminal device 12. In this form, it is preferable that the evidence data is stored in a storage area (secure world) where access to data is restricted.

[0121] Furthermore, the processing flow described in the above embodiment is merely an example, and unnecessary steps may be deleted, new steps may be added, or the processing order may be rearranged, without departing from the spirit of the present invention. [Explanation of symbols]

[0122] 10: data authenticity certification system, 12: terminal device, 14: server, 16: storage device, 21... hash value calculation unit, 30... first hash value calculation unit, 32... second hash value calculation unit, 34: comparison unit, 36: reception time determination unit, 38: registration unit, 40: QR code generation unit

Claims

1. A data authenticity certification system (10) that certifies that data received by a server (14) from a terminal device (12) operated by a user has not been tampered with, A first eigenvalue calculation unit (30) that calculates a first eigenvalue that is a value unique to the data; a second eigenvalue calculation unit (32) that calculates a second eigenvalue that is a value unique to the data at a timing different from the calculation of the first eigenvalue by the first eigenvalue calculation unit; a comparison unit (34) for comparing the first eigenvalue with the second eigenvalue; a registration unit (38) that registers the data by storing the data in a storage device (16) when the comparison unit determines that the first eigenvalue and the second eigenvalue are the same; Equipped with the terminal device generates the data and transmits the data to the server without storing the data in the terminal device; the server is provided with the first eigenvalue calculation unit, the second eigenvalue calculation unit, the comparison unit, and the registration unit, The first eigenvalue calculation unit calculates the first eigenvalue from the data received from the terminal device; the second eigenvalue calculation unit calculates the second eigenvalue from the data after the first eigenvalue is calculated and the user confirms the data to be registered on the terminal device. Data authenticity verification system.

2. The terminal device includes an eigenvalue calculation unit (21) that calculates an eigenvalue that is a value unique to the data, and transmits the data and the eigenvalue to the server; the comparison unit included in the server compares the eigenvalue with the first eigenvalue, and then compares the first eigenvalue with the second eigenvalue; 2. The data authenticity verification system according to claim 1.

3. 3. The data authenticity certification system according to claim 2, wherein the eigenvalue calculation unit changes the calculated eigenvalue based on a predetermined rule to obtain the eigenvalue.

4. The data authenticity certification system according to claim 2 , wherein the eigenvalue calculation unit and the first eigenvalue calculation unit calculate the eigenvalue and the first eigenvalue from the data divided into a plurality of parts.

5. 3. The data authenticity certification system according to claim 2, wherein the eigenvalue calculation unit and the first eigenvalue calculation unit calculate the eigenvalue and the first eigenvalue from other data added to the data.

6. 6. The data authenticity certification system according to claim 1, further comprising a determination unit (36) that determines that the received data is not authentic if the difference between the reception time of the data and the generation time of the data is greater than or equal to a predetermined time.

7. The data authenticity certification system according to any one of claims 1 to 6, wherein when the terminal device is unable to transmit or receive the data to the server and is therefore unable to transmit the generated data to the server, the terminal device stores the data in a memory area where access to the data is restricted.

8. The server includes an information code generating unit (40) that generates an information code for reading out the data stored in the storage device, The information code is transmitted from the server to the terminal device. The data authenticity certification system according to any one of claims 1 to 7.

9. An information code indicating identification information of the data is issued in advance, the terminal device transmits the information code and the data to the server; 8. The data authenticity certification system according to claim 1, wherein the registration unit registers the data in the storage device in association with identification information indicated by the information code.

10. A data authenticity verification method for verifying that data received by a server from a terminal device operated by a user has not been tampered with, comprising the steps of: A first step of calculating a first eigenvalue that is a value unique to the data by a first eigenvalue calculation unit; a second step of calculating a second eigenvalue, which is a value unique to the data, by a second eigenvalue calculation unit at a timing different from the calculation of the first eigenvalue by the first eigenvalue calculation unit; a third step of comparing the first eigenvalue with the second eigenvalue by a comparison unit; a fourth step in which, when the comparison unit determines that the first eigenvalue and the second eigenvalue are the same, a registration unit registers the data by storing the data in a storage device; having the terminal device generates the data and transmits the data to the server without storing the data in the terminal device; the server is provided with the first eigenvalue calculation unit, the second eigenvalue calculation unit, the comparison unit, and the registration unit, The first eigenvalue calculation unit calculates the first eigenvalue from the data received from the terminal device; the second eigenvalue calculation unit calculates the second eigenvalue from the data after the first eigenvalue is calculated and the user confirms the data to be registered on the terminal device. Data authenticity verification method.

Citation Information

Patent Citations

  • System, device and method for registering electronic filing document and computer program

    JP2010081372A

  • Method, system and program for managing linguistic content, linguistic content transmitter, and linguistic content receiver

    JP2010178289A

  • Authentication system, authentication server, device, and program

    JP2015222552A

  • Evidence data storage system and program

    JP2018151825A

  • Change detection program, change detection method and change detection apparatus

    JP2019082967A