TWI717909B - Data verification method - Google Patents

Abstract

A data verification method, which is applied to a server, comprises the following steps: generating a first verification value according to a plurality of first record data included in the plurality of record data groups and received during a period of time, and recording a historical data, wherein each of the record data groups has the first record data having different properties, and the historical data has the properties of the first record data; generating an unverified first verification value according to a plurality of unverified first record data included in the plurality of unverified record data groups and the historical data corresponding to the period of time; and comparing the first verification value with the unverified first verification value. If the first verification value is different from the unverified first verification value, it is determined that the record data groups are different from the unverified record data groups.

Description

Data verification method

The invention relates to a data verification method, in particular to a data verification method applied to a server.

Uploading various record data (such as the operation of electronic equipment, file access, external network access, etc.) to the server is a common method for enterprises and companies, and there is usually a set of mechanisms or methods to verify these The purpose of recording data is to read these records when problems occur in the future to investigate the cause of the problem or to clarify the attribution of responsibility.

In order to make these recorded data have legal effect when used as evidence, the data verification method used in the existing technology does not allow any modification of these recorded data, so it is not flexible in management.

The present invention provides a data verification method, which is applied to a server, which not only has legal effect when maintaining record data as evidence, but also provides flexibility in managing record data.

The data verification method provided by the present invention includes the following steps: Step S101: Generate a first verification value based on a plurality of first record data included in a plurality of record data groups received by a server within a period of time, and record historical data, where each A record data group includes first record data with different attributes, and the historical data includes the attributes of the first record data; Step S103: According to the stored multiple record data groups to be verified corresponding to a period of time, multiple first record data groups to be verified include Record data and historical data to generate a first verification value to be verified; and step S105: compare the first verification value with the first verification value to be verified, and if the first verification value is different from the first verification value to be verified, determine the record data The group is different from the record data group to be verified.

In an embodiment of the present invention, in the above step S103, the number of attributes of the record data group to be verified in the period of time is more than the number of attributes recorded in the period of time in the historical data. The first record data to be verified of the attribute recorded by time generates the first verification value to be verified.

In an embodiment of the present invention, the above step S101 includes performing a hash algorithm on the first record data of each record data group, and the historical data further includes the first record data when the hash algorithm is performed on the first record data. The order of the corresponding attributes.

In an embodiment of the present invention, the above step S101 includes: step S1011: performing a first algorithm on the first record data of each record data group to generate a plurality of second verification values; and step S1013: verifying the second The second algorithm is used to generate the first verification value; and step S103 includes: Step S1031: According to historical data, perform the first algorithm on the first record data to be verified in each record data group to be verified to generate a plurality of waiting records. Verify the second verification value; and step S1033: Perform a second algorithm on the second verification value to be verified to generate the first verification value to be verified.

In an embodiment of the present invention, the above-mentioned first algorithm and second algorithm include a hash algorithm.

In an embodiment of the present invention, the above step S1011 includes: when the server receives each record data, assigning a sequence code to each record data, wherein the sequence code of each record data is different from each other; Step S1013 includes: sorting the record data according to the sequence code. After the second verification value, the hash algorithm of the second algorithm is performed on the sorted second verification value to generate the first verification value; and step S1033 includes: after sorting the second verification value to be verified according to the sequence code, sorting The second verification value to be verified performs the hash algorithm of the second algorithm to generate the first verification value to be verified.

In an embodiment of the present invention, the above-mentioned data verification method further includes: Step S107: Compare the second verification value with the second verification value to be verified, if one of the second verification values corresponds to the second verification to be verified If the value is different, it is determined that the corresponding record data group is different from the corresponding record data group to be verified.

In an embodiment of the present invention, the above step S1011 includes: sealing the second verification value through the storage unit.

In an embodiment of the present invention, the above step S1011 includes: publishing the second verification value through a blockchain, a public trust unit, an email or an electronic bulletin board, where the blockchain includes a public chain and/or a private chain.

In an embodiment of the present invention, the above step S101 includes: storing the first verification value and/or historical data through the storage unit.

In an embodiment of the present invention, the above-mentioned step S101 includes: publishing the first verification value through a blockchain, a public trust unit, an email or an electronic bulletin board, where the blockchain includes a public chain and/or a private chain.

In an embodiment of the present invention, the record data set further includes at least one second record data, and the second record data is not used when generating the first verification value in step S101.

Because the present invention uses historical data to record the attributes of the first record data, the corresponding first record data to be verified can be found based on the attributes of the historical data record, and then the first verification value to be verified is generated based on the corresponding first record data to be verified. Therefore, when the attributes of the record data group to be verified are increased due to management needs, it can still be judged whether the record data group is different from the record data group to be verified, thereby providing flexibility in managing record data.

In order to make the above and other objects, features and advantages of the present invention more comprehensible, the following specific examples are given in conjunction with the accompanying drawings to describe in detail as follows.

FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present invention. In this embodiment, the server 100 is, for example, electrically connected to the terminal device 200 via a local area network or a wide area network and receives multiple record data sets R from the terminal device 200. The server 100 can also generate and store the record data set by itself. R, where the terminal device 200 is an electronic device such as a computer, and the number of the terminal device 200 is not limited to FIG. 1. The record data group R is, for example, related to the operation content of the server 100 or the terminal device 200. The server 100 may be installed with database software for managing the received record data group R, such as MySQL, SQL Server, Oracle database, etc. The server 100 includes a storage unit 101 for storing a record data group R. The storage unit 101 is, for example, a traditional hard disk drive (HDD) or a solid-state drive (SSD).

FIG. 2 is a schematic diagram of the record data group R received in a period of time according to an embodiment of the present invention. In this embodiment, the server 100 receives multiple record data sets R from the terminal device 200. The record data sets R received during this period include record data sets R_0 to R_3. The database software of the server 100 is in the form of Mode management record data group R, each record data group R includes the first record data D1 and the second record data D2 with different attributes, wherein each record data group R corresponds to a row of the table, and one attribute corresponds to the table In a column, the first record data D1 and the second record data D2 of each record data group R are individually filled in the columns corresponding to their attributes in the same row. For example, the period of time is, for example, one day or one hour. In the record data group R_0 received during this period, the attributes C_0 to C_3 of the first record data D1_00 to D1_03 are, for example, the time and sequence of storage in the database, respectively Code, user, copy file name, and attribute C_4 of the second record data D2_04 are remarks, for example. The present invention does not limit the quantity and attributes of the first record data D1 and the second record data D2.

FIG. 3 is a schematic diagram of a data verification method according to an embodiment of the invention. The data verification method of this embodiment includes steps S101 to S107, and each step will be further described below.

In an embodiment of the present invention, step S101: generate a first verification value V1 based on a plurality of first record data D1 included in a plurality of record data sets R received by the server 100 within a period of time, and record historical data H, where Each record data group R includes first record data D1 with different attributes, and the historical data H includes attributes of the first record data D1.

FIG. 4 is a schematic diagram of step S101 of a data verification method according to an embodiment of the present invention. In this embodiment, step S101 includes step S1011 and step S1013.

Wherein, step S1011: When the server 100 receives each record data group R, it assigns each record data group R a sequence code (step S1011a). Taking record data group R_0 as an example, the sequence code of record data group R_0 is the first In the record data D1_01, the sequence codes of the record data groups R are different from each other. In another embodiment, the sequence code may also be recorded as the second record data D2. Next, perform the first algorithm on the first record data D1 of each record data group R received during the period of time to generate a second verification value V2 (step S1011b), wherein one record data group R corresponds to a second verification Value V2, the first algorithm is, for example, a hash algorithm. Taking the record data set R0 as an example, a hash algorithm is performed on the first record data (D1_00, D1_01, D1_02, D1_03) to generate the second verification value V2_0. Then, the second verification value V2 is sealed through the storage unit 101, and/or the second verification value V2 is disclosed through the blockchain (including public chain and/or private chain), public trust unit, email or electronic bulletin board (step S1011c) , So that the second verification value V2 can not be tampered with. In another embodiment, step S1011c may not be included.

And, step S1013: after the second verification values are sorted according to the sequence code (step S1013a), after this period of time, a second algorithm is performed on the sorted second verification value V2 to generate the first verification value V1 (step S1013b) , The second algorithm is, for example, a hash algorithm. Taking the table in FIG. 2 as an example, the second verification value (V2_0, V2_1, V2_2, V2_3) sorted according to the sequence codes D1_01, D1_11, D1_21, D1_31 is subjected to the second algorithm to generate the first verification value V1. Then the first verification value V1 and/or historical data H is sealed through the storage unit 101, and/or the first verification value is disclosed through the blockchain (including public chain and/or private chain), public trust unit, email or electronic bulletin board V1 (step S1013c), so that the first verification value V1 has a non-tamperable characteristic. The historical data H is, for example, a text record file readable and writable by database software, which may include the attributes of the first record data D1 and the sequence of the attributes corresponding to the first record data D1 when the first algorithm is performed. In this embodiment, the historical data H is for example records: C_0, C_1, C_2, C_3. In another embodiment, the historical data H may further include the first verification value V1 and/or the second verification value V2 and the historical data H may be disclosed.

The hash algorithms of the first algorithm and the second algorithm are, for example, Secure Hash Algorithm (SHA) or Hash Message Authentication Code (HMAC), etc. The first algorithm and the second algorithm The same or different algorithms can be used. For those with ordinary knowledge in the technical field to which the present invention belongs, they should be able to implement the above algorithm in detail, so the details are not repeated here. As long as the data input to the hash algorithm is different, the generated hash verification value will be very different. Therefore, it is necessary to ensure that the input hash algorithm data is exactly the same as the original data to generate the same hash verification value.

In an embodiment of the present invention, step S103: generate the first record data to be verified D1' and the historical data H included in the plurality of record data groups R'to be verified corresponding to a period of time stored A verification value V1.

FIG. 5 is a schematic diagram of step S103 of a data verification method according to an embodiment of the present invention. In this embodiment, step S103 includes step S1031 and step S1033.

Wherein, step S1031: According to the multiple first record data to be verified D1' included in the multiple record data groups R'to be verified and the aforementioned historical data H stored corresponding to the period of time, select and correspond to the records in the historical data H The attributes are sorted in the order of the first record data to be verified D1' (step S1031a), and then the first algorithm is performed on the selected and sorted first record data D1' to be verified to generate the second verification value V2' to be verified (step S1031b) , And then determine whether the calculation for each record data group R'to be verified is completed (step S1031c), if the determination is no, then return to step S1031a.

Among them, the record data group R'to be verified is, for example, the record data group R received in this period of time in a state to be verified whether it has been modified after another period of time. Please refer to FIG. 6, which is a schematic diagram of the record data group R'to be verified in the embodiment shown in FIG. The difference between Figure 6 and Figure 2 is that Figure 6 adds the attribute C_5 (computer) to the table. For example, the newly received record data group R also includes the first record data D1 of the attribute C_5 (computer), which means , The number of attributes of the record data group R'to be verified is more than the number of attributes recorded in the historical data H during the period.

Specifically, taking the record data group R_0' to be verified in this embodiment as an example, according to the attributes of the period of time in the historical data H and the order of the attributes (C_0, C_1, C_2, C_3), select and correspond to the order of the attributes Sort the first record data to be verified (D1_00', D1_01', D1_02', D1_03'), which does not include the first record data to be verified D1_05'～D1_35', and then select and sort the first record data to be verified (D1_00', D1_01', D1_02', D1_03') Perform the first algorithm to generate the second verification value V2_0' to be verified, and then repeat the above steps for the verification record data set R_1'～R_3', and so on until the generation is completed The second verification value V2_0'～V2_3' to be verified.

Next, step S1033: After sorting the second verification value V2' to be verified according to the sequence code (step S1033a), perform the hash algorithm of the second algorithm on the sorted second verification value V2' to generate the first verification value V2' to be verified The verification value V1' (step S1033b). Since the sequence codes of each record data group R are different from each other, even if the record data group R is stored in the database at the same time, it can be sorted by the sequence code. Take the table in Figure 6 as an example, perform the second algorithm on the second verification values to be verified (V2_0', V2_1', V2_2', V2_3') sorted according to the sequence codes D1_01', D1_11', D1_21', D1_31' A first verification value V1' to be verified is generated.

In an embodiment of the present invention, step S105: compare the first verification value V1 with the first verification value V1' to be verified, and if the first verification value V1 is different from the first verification value V1' to be verified, determine the record data group R is different from the record data group R'to be verified.

In an embodiment of the present invention, step S107: compare the second verification value V2 with the second verification value V2' to be verified, and if one of the second verification values V2 is different from the corresponding second verification value V2' to be verified, It is determined that the corresponding record data group R is different from the corresponding record data group R'to be verified. For example, when the second verification value V2_3 is different from the second verification value V2_3' to be verified, it is determined that the record data set R_3 is different from the corresponding record data set R_3' to be verified, that is, the first record data in the record data set R_3 At least one of D1_30, D1_31, D1_32, and D1_33 has been modified. Step S107 can be used to further determine which of the multiple record data sets R has been modified. In another embodiment, the data verification method of the present invention may not include step S107, for example, when it is only necessary to determine whether any record data group R has been modified during this period, or when it is determined in step S105 that the record data When the group R is the same as the record data group R'to be verified, step S107 is not performed.

In an embodiment of the present invention, the second record data D2 is not used when the first verification value V1 is generated in step S101, such as the second record data D2_04 to D2_34 in FIG. 2; and the first verification value to be verified is generated in step S103 V1' does not use the second record data D2', such as the second record data D2_04'~D2_34' in Figure 6, where the second record data D2' is, for example, the second record data D2 after another period of time. Even if the value of the second record data D2 is changed, the second record data D2' after another period of time does not affect the first verification record data D1' in the verification record data group R'and the first verification value V1' to be verified. As shown in FIG. 2, the attribute C_4 of the second record data D2_04 to D2_34 is, for example, a note, which can be used to facilitate the management of the record data group R. Through the setting of the second record data D2, you can add fields that do not perform calculations according to your needs, allowing you to modify or write new data after data storage, which is convenient for personnel to manage.

In another embodiment, the record data set R received during the period may not include the second record data D2, but for example, the record data set R newly received after another period of time adds the second record data D2.

In another embodiment, when multiple tables are used to store the record data group R, the historical data H can be recorded separately for different tables, for example, including the name of each table and the attribute corresponding to each table.

The present invention uses historical data to record the attributes of the first record data, can find the corresponding first record data to be verified according to the attributes of the historical data record, and then generate the first verification value to be verified based on the corresponding first record data to be verified. When the attributes of the record data group to be verified are increased due to management needs (for example, the newly received record data group includes attributes that did not exist before), it can still ensure that the data input algorithm is correct, and then determine the record data group Whether it is different from the record data group to be verified, which provides flexibility in managing record data.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention. Those with ordinary knowledge in the technical field to which the present invention pertains can make some changes and modifications without departing from the spirit and scope of the present invention. Therefore, the protection scope of the present invention shall be subject to those defined by the attached patent application scope.

100: server 101: storage unit 200: terminal device R, R_0～R_3: record data group C_0～C_5: attributes D1, D1_00～D1_33: the first record data D2, D2’, D2_04～D2_34, D2_04’～D2_34’: the second record data V2, V2_0～V2_3: second verification value V1: first verification value H: Historical data R’, R_0’～R_3’: data group of records to be verified D1’, D1_00’～D1_35’: First record data to be verified V2’, V2_0’～V2_3’: the second verification value to be verified V1’: The first verification value to be verified S101, S103, S105, S107, S1011, S1013, S1031, S1033, S1011a, S1011b, S1011c, S1013a, S1013b, S1013c, S1031a, S1031b, S1031c, S1033a, S1033b: steps

FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present invention. FIG. 2 is a schematic diagram of a record data group received during a period of time according to an embodiment of the present invention. FIG. 3 is a schematic diagram of a data verification method according to an embodiment of the invention. FIG. 4 is a schematic diagram of step S101 of a data verification method according to an embodiment of the present invention. FIG. 5 is a schematic diagram of step S103 of a data verification method according to an embodiment of the present invention. FIG. 6 is a schematic diagram of a record data group to be verified according to an embodiment of the present invention.

S101, S1011, S1013, S1011a, S1011b, S1011c, S1013a, S1013b, S1013c: steps

V2: Second verification value

V1: first verification value

H: Historical data

Claims (12)

A data verification method applied to a server. The data verification method includes the following steps: Step S101: Generate a first verification value based on a plurality of first record data included in a plurality of record data groups received by the server within a period of time, and record a historical data, wherein each of the record data groups includes different attributes The first record data of, the historical data includes the attributes of the first record data; Step S103: Generate a first verification value to be verified according to the plurality of first record data to be verified included in the plurality of record data groups to be verified corresponding to the period of time and the historical data; and Step S105: Compare the first verification value with the first verification value to be verified, and if the first verification value is different from the first verification value to be verified, determine the record data groups and the record data groups to be verified different. The data verification method according to claim 1, wherein in step S103, the number of attributes of the record data groups to be verified in the period of time is greater than the number of attributes recorded in the historical data during the period of time Quantity, the first verification value to be verified is generated based on the first record data to be verified corresponding to the attributes recorded in the period of time in the historical data. The data verification method according to claim 1, wherein the step S101 includes performing a hash algorithm on the first record data of each of the record data groups, and the historical data further includes the first records When the data is used for the hash algorithm, the sequence of the attributes corresponding to the first record data. The data verification method described in claim 1, wherein: This step S101 includes: Step S1011: Perform a first algorithm on the first record data of each of the record data groups to generate a plurality of second verification values; and Step S1013: Perform a second algorithm on the second verification values to generate the first verification value; and This step S103 includes: Step S1031: According to the historical data, perform the first algorithm on the first record data to be verified in each of the record data groups to be verified to generate a plurality of second verification values to be verified; and Step S1033: Perform the second algorithm on the second verification values to be verified to generate the first verification values to be verified. The data verification method according to claim 4, wherein the first algorithm and the second algorithm include a hash algorithm. The data verification method described in claim 5, wherein: The step S1011 includes: when the server receives each record data, assigning each record data a sequence code, wherein the sequence code of each record data is different from each other; The step S1013 includes: after sorting the second verification values according to the sequence code, performing the hash algorithm of the second algorithm on the sorted second verification values to generate the first verification value; and The step S1033 includes: after sorting the second verification values to be verified according to the sequence code, performing the hash algorithm of the second algorithm on the sorted second verification values to generate the first to be verified Verification value. The data verification method described in claim 4 further includes: Step S107: Compare the second verification values with the second verification values to be verified, and if one of the second verification values is different from the corresponding second verification value to be verified, determine the corresponding record data The group is different from the corresponding record data group to be verified. The data verification method according to claim 4, wherein step S1011 includes: sealing the second verification value through a storage unit. The data verification method according to claim 4, wherein step S1011 includes: disclosing the second verification value through a blockchain, a public trust unit, an email or an electronic bulletin board, wherein the blockchain includes a public chain And/or a private chain. The data verification method according to claim 1, wherein the step S101 includes: sealing the first verification value and/or the historical data through a storage unit. The data verification method according to claim 1, wherein the step S101 includes: disclosing the first verification value through a blockchain, a public trust unit, an email, or an electronic bulletin board, wherein the blockchain includes a public Chain and/or a private chain. According to the data verification method of claim 1, wherein the record data groups further include at least one second record data, and the at least one second record data is not used when generating the first verification value in step S101.

Images