A data binding compliance code method and system

Abstract

This invention discloses a method and system for data-bound compliance codes, belonging to the field of data security and information hiding. It comprises two parts: watermark embedding and watermark extraction. The watermark embedding includes: dataset preparation, plaintext encryption preparation, encryption of the compliance code using the AES algorithm, and embedding the watermark into the database. The watermark extraction stage is largely the same as the embedding operation, consisting of dataset preparation, ciphertext decryption preparation, and decryption of the data using the AES algorithm to obtain the watermark data. This solution solves the problem of binding data with compliance codes in data transactions using database watermarking technology.

Description

Technical Field

[0001] The present invention relates to the field of data security and information hiding, and in particular to a data binding compliance code method and system. Background Art

[0002] With the rapid development of computer networks and big data technology, databases have become an important carrier for governments, enterprises and individuals to obtain and transmit information. However, in the process of creation, transmission and sharing, databases have also brought about problems such as data theft, illegal copying and copyright infringement. In order to solve the above problems, database watermarking technology came into being.

[0003] Database watermarking technology is mainly used to solve the problems of data theft and illegal copying caused by the increasing number of database applications in the network environment. With the development of computer technology and network technology, databases are used more and more widely on the Internet. The value and monetization ability of data have led to the rampant black and gray industries of data. Therefore, people have begun to pay attention to the copyright protection of information databases to prevent illegal database thieves from taking advantage of the opportunity and causing significant losses to the copyright owners of the databases.

[0004] In 2002, Agrawal et al. first proposed database watermarking technology. Due to the large amount of database data but small redundancy, and the need to perform certain normal operations on the data, traditional multimedia digital watermarking technology cannot be directly applied to the database. Therefore, it is necessary to study the characteristics of database and digital watermarking technology and develop a watermarking technology that meets the database copyright protection to solve the database copyright protection problem.

[0005] In recent years, database watermarking technology has been rapidly developed and applied driven by security needs. For example, robust database watermarking is mainly used for digital copyright protection and tracing, while fragile database watermarking is mainly used for data integrity protection and authentication. In addition, there are different types of database watermarking technologies, such as distortion-free database watermarking, distortion-free database watermarking, and reversible database watermarking.

[0006] The compliance code in data transactions mainly refers to a series of rules and standards formulated during the data transaction process to ensure the legality, security and effectiveness of data transactions.

[0007] As the value of data gradually becomes more prominent, the country vigorously advocates and supports the development of the digital economy. Data has become an important basic and strategic resource for the country in today's era. In 2020, my country officially listed data as a new production factor and attached great importance to the cultivation of the data market. Data trading is a key link in promoting data flow and stimulating data vitality, and is the key content of accelerating the construction of the data factor market.

[0008] In combination with big data application scenarios, the present invention chooses to use database watermark technology to implement data binding operations. Summary of the invention

[0009] The technical problem solved by the present invention is to provide a data binding compliance code method and system for verifying illegal caching, illegal sale and illegal acquisition of data, data credibility assessment and data traceability.

[0010] The basic solution provided by the present invention: a data binding compliance code method, comprising the following steps: comprising the following steps:

[0011] S100: Reconstruct the structure of the database to establish an attribute splitting table, a user level table, and a key table;

[0012] S200: After obtaining the compliance code label data, determine whether the plaintext bytes are multiples of 16 bytes. If not, pad the plaintext bytes and encrypt them using an encryption algorithm to obtain ciphertext.

[0013] S300: Select an encryption algorithm to perform encryption operation on the data and embed it into the corresponding data table that needs data binding;

[0014] S400: After obtaining the compliance code data of the encryption operation, the primary and foreign keys are reconstructed;

[0015] S500: Search for the corresponding data table and the associated data table of the target database, decrypt the data according to the compliance code encryption and decryption operation, obtain the compliance code plaintext, find the data table associated with this table according to the primary and foreign key relationship constructed according to the implicit rules when the attribute splitting table was established, and thus obtain the data itself bound to this compliance code, and complete the data watermark extraction and traceability operation.

[0016] Further, the S100 includes the following steps:

[0017] S110: Three new tables are created, including an attribute splitting table, a user level table, and a key table;

[0018] S120: The attribute splitting table is used to aggregate and split the attributes of each data table that needs to be bound in the database, so that these tables adapt to multiple rules;

[0019] S130: The user hierarchy table is used to systematically describe the hierarchical relationship of data distribution in this database through a K-Tree structure;

[0020] S140: The key table is used to describe the name, code, and corresponding key and 0-1 attribute table of the user storing the data;

[0021] S150: without changing the data relationships among several tables in the database, the primary and foreign keys of the tables are changed, thereby obtaining corresponding primary and foreign keys generated by themselves, and corresponding implicit rules are applied thereon as embedded watermark information.

[0022] Further, S300 includes the following steps:

[0023] S310: Perform an encryption operation on the data using the AES symmetric encryption algorithm;

[0024] S320: After encrypting the corresponding compliance code to be embedded using AES, it is embedded into the corresponding data table that needs data binding; when using the AES encryption algorithm, 10 rounds of cyclic encryption operations are required. After the round key addition operation is performed on the plaintext at the beginning, the first round of operations is entered, that is, byte replacement, row shift, column confusion, and finally the round key addition. After completing one round, the processed ciphertext is obtained after 10 rounds of cycles are completed in sequence;

[0025] S330: The decryption operation is the inverse operation of the encryption operation, and the key used for encryption and decryption is the same.

[0026] Further, S400 includes the following steps:

[0027] S410: After obtaining the compliant code data after the encryption operation, store these data separately in a data table in order, and then use the attribute splitting table constructed by itself according to the implicit rules and related algorithms in the first step to reconstruct the primary and foreign keys of the data table that needs to be bound in the original database in the form of the attribute splitting table.

[0028] The principles of this solution are:

[0029] 1. Prepare the dataset

[0030] (1) The structure of the database needs to be restructured first: three new tables need to be created in the current database, namely the attribute splitting table, the user level table, and the key table. The attribute splitting table summarizes and splits the attributes of each data table in the database that needs to be bound, so that these tables can adapt to multiple rules. The main function is to consider that a table may have many fields, and for different user levels, only part of the field values ​​will be allowed to be viewed, so only part of the values ​​may be leaked, so we can trace back from part of the values. In the attached table description, 0 means that the corresponding attribute field permissions are not obtained, 1 means that the relevant permissions are obtained, and wm represents the watermark content, that is, the watermark is embedded in the location where wm is located.

[0031] The user hierarchy table can systematically describe the hierarchical relationship of data distribution in this database through a K-Tree tree structure. The node data in the tree stores the code of each data user, such as U1, U2, etc., while the root node represents the owner of the distributed original data, and the parent node of each child node represents the data distributor of the previous level.

[0032] The key table describes the name, code, key and 0-1 attribute table of the user of the stored data. The last column in the key table indicates which object in the attribute split table the access attribute of the user object corresponds to, thereby inheriting his access rights. (2) The compliance code label data and watermark pre-architecture need to be prepared. Connect to the database and read the compliance code source data that needs to be bound, that is, the watermark source.

[0033] Without changing the data relationships in several tables of the database, the primary and foreign keys of the data tables are changed to obtain the corresponding primary and foreign keys generated by themselves, and the corresponding implicit rules are applied on them as embedded watermark information. In this way, once the data is leaked, the source of the data leak can be traced through the extracted watermark.

[0034] 2. Plaintext encryption preparation

[0035] After obtaining the compliance code label data, considering that the data size is not necessarily a multiple of 16 bytes, the encryption algorithm selected in this solution is the AES128 encryption algorithm. If the number of plaintext bytes does not meet the multiple of 16 bytes, a padding operation is required. After the plaintext is processed, the encryption operation can be performed to obtain the corresponding ciphertext.

[0036] 3. Compliance code encryption and decryption process

[0037] Select a suitable encryption algorithm. Here I use the AES symmetric encryption algorithm to perform an encryption operation on the data. After using AES to encrypt the corresponding compliance code that needs to be embedded, embed it into the corresponding data table that needs data binding. When using the AES encryption algorithm, 10 rounds of cyclic encryption operations are required. After the round key addition operation is performed on the plaintext at the beginning, the first round of operations is entered, that is, byte replacement, row shift, column confusion, and finally the round key addition. After completing one round, the processed ciphertext is obtained after completing ten rounds in sequence. Because of the symmetry of AES, the decryption operation is the inverse operation of the encryption operation, and the key used for encryption and decryption is the same.

[0038] 4. After encryption is completed, watermark embedding begins.

[0039] After obtaining the compliance code data after the encryption operation, store these data in a data table in order, and then use the attribute split table obtained according to the implicit rules in the first step to reconstruct the primary and foreign keys of the data table that needs to be bound in the original database in the form of the attribute split table. In this way, a certain compliance code data that you want to embed can be extracted from the separately stored data table and placed in the corresponding position in the attribute split table, thus realizing the binding embedding of a compliance code. This embedding will not affect the data relationship of the original data table, but can use the primary and foreign key relationship between the tables to associate the attribute split table with the original table, thereby realizing the watermark function. If you need to bind a large number of items one by one, you can use a loop statement to meet the needs.

[0040] 5. Extract watermark and data traceability operations

[0041] When watermark information extraction is required, the corresponding data table of the target database and its associated attribute split table are found, and the information carried is taken out. Then, according to the encryption and decryption operation based on the compliance code, the data is decrypted to obtain the compliance code plaintext. According to the primary and foreign key relationship constructed by the implicit rules when the attribute split table is established, the data table associated with this table is found, so as to obtain the data itself bound to this compliance code, and complete the data watermark extraction and traceability operation.

[0042] The present invention uses a database watermark method and a symmetric encryption algorithm to design a data-bound compliance code system. The system uses structured data as a database support, and in each link of the transaction that needs to be bound, the compliance code label data is bound to the data in the form of a database watermark to protect the transaction process.

[0043] The present invention uses a database watermark method and a symmetric encryption algorithm to design a data-bound compliance code system. The system uses structured data as a database support, and in each link of the transaction that needs to be bound, the compliance code label data is bound to the data in the form of a database watermark to protect the transaction process.

[0044] The present invention also provides a data-bound compliance code system, including a database reconstruction module, which is used to reconstruct the structure of the database and establish an attribute splitting table, a user hierarchy table, and a key table;

[0045] The requirement determination module is used to determine whether the plaintext bytes are multiples of 16 bytes after obtaining the compliance code label data. If it is not a multiple of 16 bytes, the plaintext bytes are padded and encrypted through the encryption algorithm to obtain the ciphertext;

[0046] The embedding operation module is used to select an encryption algorithm to perform encryption operations on the data and embed it into the corresponding data table that needs data binding;

[0047] The primary and foreign key reconstruction module is used to reconstruct the primary and foreign keys after obtaining the compliance code data of the encryption operation;

[0048] The data extraction and tracing module is used to find the corresponding data tables and related data tables of the target database, decrypt the data according to the compliance code encryption and decryption operations, obtain the compliance code plaintext, and find the data table associated with this table based on the primary and foreign key relationships constructed according to the implicit rules when the attribute splitting table was established, thereby obtaining the data itself bound to this compliance code and completing the extraction and tracing operations of the data watermark. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 A user-level representation of an embodiment of a data binding compliance code method of the present invention;

[0050] Figure 2 A diagram introducing the principle of the AES encryption algorithm of an embodiment of a data binding compliance code method of the present invention;

[0051] Figure 3 A diagram introducing the compliance code encryption process of an embodiment of a data binding compliance code method of the present invention;

[0052] Figure 4 A flowchart of a data binding method according to an embodiment of a data binding compliance code method of the present invention. DETAILED DESCRIPTION

[0053] The following is further described in detail through specific implementation methods:

[0054] The embodiment is basically as shown in the attached Figure 1 As shown: A data binding compliance code method includes the following steps:

[0055] (1) Pre-architecture of database structure.

[0056] Three new data tables are constructed in the database, namely: attribute splitting table, user level table and key table. The three tables are as follows:

[0057] Table 1 Attribute example table

[0058]

[0059] Table 2 Example of attribute splitting table

[0060]

[0061] Table 3 Key table

[0062]

[0063] The attribute split table summarizes and splits the attributes of each data table in the database that needs to be bound, so that these tables can adapt to multiple rules. The main function is to consider that a table may have many fields, and for different user levels, only part of the field values ​​can be viewed, so only part of the values ​​may be leaked, so we can trace back from part of the values. In the attached table description, 0 means that the corresponding attribute field permission is not obtained, 1 means obtaining the relevant permission, and wm represents the watermark content, that is, the location of wm is used to embed the processing watermark.

[0064] The user hierarchy table can systematically describe the hierarchical relationship of data distribution in this database through a K-Tree tree structure. The node data in the tree stores the code of each data user, such as U1, U2, etc., while the root node represents the owner of the distributed original data, and the parent node of each child node represents the data distributor of the previous level.

[0065] The key table describes the name, code, key and 0-1 attribute table of the user of the stored data. The last column in the key table indicates which object in the attribute splitting table the access attribute of the user object corresponds to, thereby inheriting his access rights.

[0066] (2) Prepare compliance code label data and watermark pre-architecture.

[0067] By using the built-in function library of Java, the target data in the database, namely the compliance code, can be extracted. This method can be used to obtain the compliance code source data that needs to be bound, namely the watermark source.

[0068] Without changing the relationship between the data in several tables of the database, the primary and foreign keys of the table are changed to obtain the corresponding primary and foreign keys generated by themselves, and the corresponding implicit rules are applied on them as embedded watermark information. In this way, once the data is leaked, the source of the data leakage can be traced through the extracted watermark. In the corresponding database, the implicit rules between the data of each module need to be found using a certain algorithm. Assuming that the data involved in the compliance code this time is shopping basket data, the Apriori association rule learning algorithm can be used to find the implicit rules. After finding it, it can be applied to the database design to represent this relationship in the form of foreign keys. Based on the above steps, the table structure of the database can be simply constructed. Finally, this method needs to regularly verify and check the designed rules to avoid whether the rules can continue to be applied to the watermark after the data is updated.

[0069] Prepare to encrypt data.

[0070] The compliance code is extracted from the database, and a group of compliance code data is selected as watermark plaintext for encryption operation.

[0071] Step 2: Prepare for compliance code encryption

[0072] The present invention adopts an encryption algorithm to help encrypt the compliance code. The algorithm selects the AES algorithm, and not using a unified password is to prevent attacks.

[0073] AES is the Advanced Encryption Standard. AES supports three key lengths: 128 bits, 192 bits, and 256 bits. This method uses AES128.

[0074] The present invention adopts AES128 for the following reasons: fast operation speed, low memory requirement, flexible design, high security, and easy parallel computing.

[0075] a) Padding

[0076] AES has the characteristic of block encryption, that is, when encrypting plaintext, it does not encrypt all plaintext together into a whole ciphertext, but splits the plaintext into independent plaintext blocks, each of which is 128 bits long. After the plaintext blocks are processed by the AES encryptor, corresponding ciphertext blocks are generated, and the final encryption result is obtained after the ciphertext blocks are spliced.

[0077] However, if the plaintext length is not a multiple of 128, the split plaintext block may not meet the 128-bit requirement, and the plaintext block needs to be padded. There are three types of padding modes, which will not be introduced in detail here. The present invention uses the default PKCS5Padding method to pad the plaintext, i.e., the compliance code.

[0078] The third step is the compliance code encryption and decryption process.

[0079] This encryption algorithm involves four operations: byte substitution (SubBytes), row shift (ShiftRows), column confusion (MixColumns) and round key addition (AddRoundKey), and each step of the decryption algorithm corresponds to the inverse operation of each step of the encryption algorithm. The key for each round of encryption and decryption is obtained by the seed key set at the beginning through the key expansion algorithm. The 16-byte plaintext, ciphertext and round key involved in the algorithm are all represented by a 4x4 matrix.

[0080] AddRoundKey: Each byte of the data in the matrix is ​​XORed with the round key of that time; each subkey is generated by the key generation scheme. We select a set of compliant codes and transform them into a plaintext matrix P and a pre-set round key matrix K, then the round key addition operation can be expressed as:

[0081]

[0082] Among them, C is the ciphertext matrix of the compliant code obtained after encryption, Represents a bitwise exclusive-or operation.

[0083] SubBytes (byte replacement): Use a nonlinear replacement function (S-box) to replace each byte with the corresponding byte using a lookup table. At this time, the ciphertext matrix obtained in the previous step, that is, the state matrix S in this step, is replaced with bytes using a lookup table. The replacement operation can be expressed as:

[0084]

[0085] in, is the state matrix after byte substitution, Is a byte substitution function.

[0086] ShiftRows (row shift): Circularly shift each horizontal column in the matrix to the left. Shift the state matrix S after the previous step, then the row shift operation can be expressed as:

[0087]

[0088] Among them, S' is the state matrix after row shift, is the row shift function.

[0089] If we denote the element in the i-th row and j-th column of the state matrix S as S[i][j], then the row shift operation can be expressed as follows:

[0090]

[0091] MixColumns (column confusion): In order to fully mix the operations of each column in the matrix. Perform column confusion operation:

[0092]

[0093] in, is the state matrix after column confusion, is the column confusion function.

[0094] exist Figure 3 The process of encrypting data by looping these four steps is shown in the figure, so as to obtain the data encrypted with the corresponding compliance code.

[0095] The fourth step is to embed the ciphertext into the specified position to complete the watermark

[0096] After obtaining the compliance code data after the encryption operation, these data are stored separately in a data table in order. This table is only used as an intermediate storage, so there is no other format requirement. Then, the attribute split table constructed by the first step according to the implicit rules and related algorithms is used to reconstruct the primary and foreign keys of the data table that needs to be bound in the original database in the form of the attribute split table. In this way, a certain compliance code data that you want to embed can be extracted from the separately stored data table and placed in the corresponding position in the attribute split table, that is, the scope position in the example table in Table 2. The scope tuple is a newly created tuple in the attribute split table, and the other tuples are other tuples of the data table associated with the attribute split table using the implicit rules. In this way, the binding embedding of a compliance code is realized. This embedding will not affect the data relationship of the original data table, but the primary and foreign key relationship between the tables can be used to associate the attribute split table with the original table, thereby realizing the watermark function. If a large number of bindings need to be performed one by one, a loop statement can be used to achieve it.

[0097] When performing large-scale binding, you need to use ? in the SQL statement in advance as a placeholder, which can facilitate later maintenance and prevent injection attacks.

[0098] Step 5: Extract watermark and data traceability

[0099] When watermark information extraction is required, the corresponding data table of the target database and its associated attribute split table are found, and then the carried information is taken out from the scope tuple in the attribute split table. Then, according to the encryption and decryption operation based on the compliance code in the third step, because the encryption method used in the present invention is the AES encryption method, its decryption step is the reverse operation of the encryption step, such as Figure 3 As shown on the right. After decrypting the data, you can get the compliance code in plain text. Then, according to the primary and foreign key relationship constructed by the implicit rules when the attribute split table is established, find the data table associated with this table, so as to obtain the data bound to this compliance code, and complete the data watermark extraction and traceability operation. The process is as follows Figure 4 shown.

[0100] In the invention document, because the embedding and extraction methods are roughly the same, the step descriptions of encryption and decryption are not introduced as one point, but are explained in the last figure.

[0101] This solution also provides a data-bound compliance code system, including:

[0102] The database reconstruction module is used to reconstruct the structure of the database and establish the attribute split table, user level table and key table;

[0103] The requirement determination module is used to determine whether the plaintext bytes meet the requirements after obtaining the compliance code label data. If they do not meet the requirements, they are filled and encrypted through the encryption algorithm to obtain the ciphertext;

[0104] The embedding operation module is used to select an encryption algorithm to perform encryption operations on the data and embed it into the corresponding data table that needs data binding;

[0105] The primary and foreign key reconstruction module is used to reconstruct the primary and foreign keys after obtaining the compliance code data of the encryption operation;

[0106] The data extraction and tracing module is used to find the corresponding data tables and related data tables of the target database, decrypt the data according to the compliance code encryption and decryption operations, obtain the compliance code plaintext, and find the data table associated with this table based on the primary and foreign key relationships constructed according to the implicit rules when the attribute splitting table was established, thereby obtaining the data itself bound to this compliance code and completing the extraction and tracing operations of the data watermark.

[0107] The above are only embodiments of the present invention. Common knowledge such as the known specific structures and characteristics in the scheme is not described in detail here. Ordinary technicians in the relevant field know all the common technical knowledge in the technical field to which the invention belongs before the application date or priority date, can obtain all the existing technologies in the field, and have the ability to apply conventional experimental means before that date. Ordinary technicians in the relevant field can improve and implement this scheme in combination with their own abilities under the enlightenment given by this application. Some typical known structures or known methods should not become obstacles for ordinary technicians in the relevant field to implement this application. It should be pointed out that for those skilled in the art, without departing from the structure of the present invention, several deformations and improvements can be made, which should also be regarded as the scope of protection of the present invention, and these will not affect the effect of the implementation of the present invention and the practicality of the patent. The scope of protection required by this application shall be based on the content of its claims, and the specific implementation methods and other records in the specification can be used to interpret the content of the claims.

Claims

1. A data binding compliance code method, characterized by: The following steps are involved: S100: Reconstruct the structure of the database to establish an attribute splitting table, a user level table, and a key table; S200: After obtaining the compliance code label data, determine whether the plaintext bytes are multiples of 16 bytes. If not, pad the plaintext bytes and encrypt them using an encryption algorithm to obtain ciphertext. S300: Select an encryption algorithm to perform encryption operation on the data and embed it into the corresponding data table that needs data binding; S400: After obtaining the compliance code data of the encryption operation, the primary and foreign keys are reconstructed; S500: Find the corresponding data table and the associated data table of the target database, decrypt the data according to the compliance code encryption and decryption operation, obtain the compliance code plain text, find the data table associated with this table according to the primary and foreign key relationship constructed by the implicit rules when the attribute splitting table is established, so as to obtain the data bound to this compliance code, and complete the data watermark extraction and traceability operation; The S100 includes the following steps: S110: Three new tables are created, including an attribute splitting table, a user level table, and a key table; S120: The attribute splitting table is used to aggregate and split the attributes of each data table that needs to be bound in the database, so that these tables adapt to multiple rules; S130: The user hierarchy table is used to systematically describe the hierarchical relationship of data distribution in this database through a K-Tree structure; S140: The key table is used to describe the name, code, and corresponding key and 0-1 attribute table of the user storing the data; S150: without changing the data relationships among several tables in the database, the primary and foreign keys of the tables are changed, thereby obtaining corresponding primary and foreign keys generated by the self, and corresponding implicit rules are applied thereon as embedded watermark information; The S400 includes the following steps: S410: After obtaining the compliant code data after the encryption operation, store these data separately in a data table in order, and then use the attribute splitting table constructed by itself according to the implicit rules and related algorithms in the first step to reconstruct the primary and foreign keys of the data table that needs to be bound in the original database in the form of the attribute splitting table.

2. A data binding compliance code method according to claim 1, characterized in that: The S300 includes the following steps: S310: Perform an encryption operation on the data using the AES symmetric encryption algorithm; S320: After encrypting the corresponding compliance code to be embedded using AES, it is embedded into the corresponding data table that needs data binding; when using the AES encryption algorithm, 10 rounds of cyclic encryption operations are required. After the round key addition operation is performed on the plaintext at the beginning, the first round of operations is entered, that is, byte replacement, row shift, column confusion, and finally the round key addition. After completing one round, the processed ciphertext is obtained after 10 rounds of cycles are completed in sequence; S330: The decryption operation is the inverse operation of the encryption operation, and the key used for encryption and decryption is the same.

3. A data-bound compliance code system, characterized in that: include: The database reconstruction module is used to reconstruct the structure of the database and establish the attribute split table, user level table and key table; The attribute splitting table is used to summarize and split the attributes of each data table in the database that needs to be bound, so that these tables can adapt to multiple rules; The user hierarchy table is used to systematically describe the hierarchical relationship of data distribution in this database through a K-Tree tree structure; the key table is used to describe the name, code, and corresponding key and 0-1 attribute table of the user of the stored data; Without changing the data relationships among several tables in the database, the primary and foreign keys of the tables are changed to obtain the corresponding primary and foreign keys generated by themselves, and the corresponding implicit rules are applied on them as embedded watermark information; The requirement determination module is used to determine whether the plaintext bytes are multiples of 16 bytes after obtaining the compliance code label data. If it is not a multiple of 16 bytes, the plaintext bytes are padded and encrypted through the encryption algorithm to obtain the ciphertext; The embedding operation module is used to select an encryption algorithm to perform encryption operations on the data and embed it into the corresponding data table that needs data binding; The primary and foreign key reconstruction module is used to reconstruct the primary and foreign keys after obtaining the compliance code data of the encryption operation; after obtaining the compliance code data after the encryption operation, the data is stored separately in a data table in order, and then the attribute splitting table constructed by itself according to the implicit rules and related algorithms in the first step is used to reconstruct the primary and foreign keys of the data table that needs to be bound in the original database in the form of the attribute splitting table; The data extraction and tracing module is used to find the corresponding data tables and related data tables of the target database, decrypt the data according to the compliance code encryption and decryption operations, obtain the compliance code plaintext, and find the data table associated with this table based on the primary and foreign key relationships constructed according to the implicit rules when the attribute splitting table was established, thereby obtaining the data itself bound to this compliance code and completing the extraction and tracing operations of the data watermark.

Images