CN115022042A - A compliance code verification method and computer-readable medium for protecting data privacy - Google Patents

Abstract

The invention relates to a compliance code verification method and a computer-readable medium for protecting data privacy. The verification method includes SA: a data receiver obtains an identification code for verification, and the data receiver stores a compliance code as a verification standard ; The compliance code is a multi-factor compliance code, which includes multiple data label codes and message authentication codes as verification factors spliced together; SB: Call the data compliance verification algorithm to decrypt and verify the compliance code and identification code ; SC: Determine whether the compliance verification is passed. If the verification fails, it means that the data has illegal operations; if the verification passes, you can choose to continue the tampering verification. If there is no tampering, the verification is successful. This application is used for further verification to ensure the confidentiality, integrity and compliance of the data.

Description

A compliance code verification method and computer-readable medium for protecting data privacy

technical field

The present application devises the field of computer technology, and specifically designs an efficient compliance code verification method and a computer-readable medium for protecting data privacy.

Background technique

In the data transmission process in the prior art, in order to ensure the security and integrity of the data, it is usually necessary to perform encryption and message digest processing on the data. SM4 is a block cipher standard adopted by the government of the People's Republic of China. In the commercial cryptography system, SM4 is mainly used for data encryption. Its algorithm is public. The block length and key length are both 128 bits. The encryption algorithm and key expansion algorithm both use a 32-round nonlinear iterative structure. The S box used for encryption is Fixed 8-bit input and 8-bit output. SM3 is a cryptographic hash function standard adopted by the government of the People's Republic of China. In the commercial cryptographic system, SM3 is mainly used for digital signature and verification, message authentication code generation and verification, random number generation, etc. Its algorithm is public. According to the State Cryptography Administration, its security and efficiency are better than the SHA-256 algorithm.

When there is no compliance code verification method for transactions with private data in the prior art, how to effectively verify whether the data is compliantly circulated to the enterprise and applied correctly through the network api or access to the compliance verification address. Therefore, problems such as how to perform data compliance verification and tampering verification are problems that those skilled in the art need to solve urgently.

SUMMARY OF THE INVENTION

The purpose of the invention is to overcome the above-mentioned shortcomings in the prior art, and to provide a compliance code verification method and a computer-readable medium that include data circulation compliance verification, data tampering verification, fast verification, and high confidentiality.

In order to achieve the above-mentioned purpose, this invention has the following constitution:

The present application includes a compliance code verification method for protecting data privacy, comprising the steps of:

SA: The data receiver obtains the identification code for verification, and the data receiver stores the compliance code as the verification standard; the compliance code is a multi-factor compliance code, including multiple data label codes and message authentication The code is spliced as a verification factor;

SB: Invoke the data compliance verification algorithm to decrypt and verify the compliance code and identification code;

SC: Determine whether the compliance verification is passed. If the verification fails, it means that the data has illegal operations; if the verification passes, you can choose to continue the tamper verification. If there is no tampering, the verification is successful.

In a preferred compliance code verification method, the step SC specifically includes:

SC: Invoke the data compliance verification algorithm, decrypt and verify each data tag code respectively, if the verification fails, determine that the data has violations corresponding to the data tag encoding; if all data tag encodings are verified, you can choose to continue to step SD;

SD, perform tampering verification, and verify the message verification code. If they are the same, it is determined that there is no tampering, and if they are different, it is determined that there is tampering.

In a preferred compliance code verification method, the compliance code is generated by adding multiple labels to the original data in advance, jointly encoding the label data and the data source identity information, and using HMAC to obtain the code and the abstract of the data. information and splicing encryption to generate compliance codes.

In a preferred compliance code verification method, the step of generating the compliance code includes:

S1, the data source collects raw data;

S2, establish a data dictionary mapping encoding rule table;

S3, the data is divided into batches to generate batch data labels;

S4, selecting a data tag, and splicing the data dictionary mapping code and HMAC value corresponding to the data tag to form the data to be encrypted;

S5, using the national secret SM4 to encrypt the data to be encrypted to obtain the ciphertext;

S6, calling a two-dimensional code generation algorithm to process the ciphertext to generate a compliance code.

In a preferred compliance code verification method, the step S4 specifically includes the steps of:

S4-1, splicing the data to obtain the label code, and splicing the HMAC value obtained after the data is bound to the data source identity and the user identity;

S4-2, splicing data cache tag encoding, splicing the data use deadline information;

S4-3, splicing the data using tag encoding, splicing the value obtained after the data is mapped to the data dictionary using the category information tag;

S4-4, splicing the code of the data transaction label, and splicing the value obtained after performing the data dictionary mapping on the data transaction information label;

S4-5, splicing the data flow to label coding, splicing the HMAC value obtained after performing data dictionary mapping on the batch label and adding the total amount of batch transactions;

S4-6, splicing the HMAC value of the data plaintext.

In a preferred compliance code verification method, the step SC is specifically: calling a data compliance verification algorithm, decrypting and verifying each data tag code respectively, if the verification fails, judging that the data has a violation corresponding to the data tag encoding, specifically includes steps

SC-1, judge whether the data acquisition label code has passed the verification, if the verification fails, it means that the data is illegally acquired;

SC-2, judge whether the data cache label coding has passed the verification, if the verification fails, it means that the data has illegal cache;

SC-3, judge whether the data use label coding has passed the verification, if the verification fails, it means that the data is used illegally;

SC-4, judge whether the data transaction label code has passed the verification, if the verification fails, it means that there is an illegal transaction in the data;

SC-5, judge whether the data flow label code has passed the verification, if the verification fails, it means that the data has been illegally transferred;

If all data label codes are verified and passed, you can choose to continue to step SD;

SD, perform tampering verification, and verify the message verification code. If they are the same, it is determined that there is no tampering, and if they are different, it is determined that there is tampering.

In a preferred compliance code verification method, the HMAC is specifically:

Wherein, opad and ipad are constants, M is the data to be processed, Key1 is the first initial key, and Key2 is the second key.

In a preferred compliance code verification method, the first initial key Key ₁ =SM3(S ₁ ), the S ₁ is generated according to the current time T ₁ and using a random number tool,

The second key Key ₂ =SM3(S ₂ ||Key1), the S ₂ is generated according to the current time T ₂ and using a random number tool.

In a preferred compliance code verification method, the original data includes: the time to which the data belongs, the time when the data is generated, the data source number, the industry number to which the data belongs, the validity period of the data content, the data field number, the data content, the transaction platform code, the transaction Business ID code, data transaction validity period, sales customer ID code, allowable application industry, allowable application scenario, data transaction time, data transaction method, charging type, data field number.

The present application also includes a computer-readable medium having computer-readable instructions stored thereon, the computer-readable instructions being executable by a processor to implement the method for verifying a compliance code for protecting data privacy.

The compliance code verification method for protecting data privacy and the computer-readable medium of the present application are adopted, and the verification method includes SA: the data receiver obtains the identification code for verification, and the data receiver stores the compliance code as the verification standard ; The compliance code is a multi-factor compliance code, including multiple data label codes and message authentication codes as verification factors spliced together; SB: Call the data compliance verification algorithm to decrypt and verify the compliance code and identification code ; SC: Determine whether the compliance verification is passed. If the verification fails, it means that the data has illegal operations; if the verification passes, you can choose to continue the tampering verification. If there is no tampering, the verification is successful. This application is used for further verification to ensure the confidentiality, integrity and compliance of the data.

Description of drawings

Fig. 1 is a preferred step diagram of a compliance code verification method for protecting data privacy;

Figure 2 is a step diagram of compliance code verification and tampering to protect data privacy

Fig. 3 is the preferred step diagram of the preferred HMAC technology;

Fig. 4 is the compliance code generation step of the first preferred embodiment of protecting data privacy;

FIG. 5 is a step of generating a compliance code in the second preferred embodiment of protecting data privacy.

Detailed ways

The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative efforts also fall within the protection scope of the present invention.

The present application includes a compliance code verification method for protecting data privacy, comprising the steps of:

SA: The data receiver obtains the identification code for verification, and the data receiver stores the compliance code as the verification standard; the compliance code is a multi-factor compliance code, including multiple data label codes and message authentication The code is spliced as a verification factor;

SB: Invoke the data compliance verification algorithm to decrypt and verify the compliance code and identification code;

SC: Determine whether the compliance verification is passed. If the verification fails, it means that the data has illegal operations; if the verification passes, you can choose to continue the tamper verification. If there is no tampering, the verification is successful.

In the data transmission process in the prior art, the national secret SM4 is usually used to encrypt the data. The SM4 encryption algorithm is public, the packet length and the key length are both 128 bits, and both the encryption algorithm and the key expansion algorithm use 32 rounds of nonlinear iteration. Structure, the S box used for encryption is a fixed 8-bit input and 8-bit output. For an exemplary technical solution, please refer to the Information Security Technology SM4 Block Cipher issued by the General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China and the Standardization Administration of China. Algorithm" (GB/T 32907-2016), it should be known that the technical solution recorded in the above-mentioned "Information Security Technology SM4 Block Cipher Algorithm" is the prior art of this application, and can be directly applied to the technical solution of this application.

On the basis of the existing ciphertext generated by encrypting the message data with the SM4 encryption algorithm, the present application adds a message verification code generated by further adopting the SM3 hashing algorithm for the message data to judge whether the ciphertext has violated the rules or been violated. Tampered technical solutions.

For the technical solution of the exemplary SM3 hash algorithm, please refer to "Information Security Technology SM3 Cryptographic Hash Algorithm" (GB/T 32905-2016) issued by the General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China and the Standardization Administration of China (GB/T 32905-2016). , the technical solution recorded in the above "Information Security Technology SM3 Cryptographic Hash Algorithm" is the prior art of the present application, and can be directly applied to the technical solution of the present application.

In a preferred embodiment of the present application, the data owner (compliance code generator) generates a compliance code, sends the compliance code to the data receiver and stores it in the data receiver storage unit as a verification standard. For the convenience of distinction, the code obtained by the data receiver for verification is called the identification code. It should be known that when the identification code can be verified by the verification method of the present application, the compliance code is the same as the identification code.

When data transmission is required and there is a need to verify ciphertext, the data receiver submits the verification information to a trusted third verification agency, and decrypts and verifies the compliance code stored in the data receiver by invoking the data compliance verification algorithm.

The compliance code is generated by splicing and encrypting the data tag encoding information and the plaintext data message authentication code, and calling a two-dimensional code generation algorithm.

In a preferred compliance code verification method, the compliance code is generated by adding multiple labels to the original data in advance, jointly encoding the label data and the data source identity information, and using HMAC to obtain the code and the abstract of the data. information and splicing encryption to generate compliance codes.

In a preferred compliance code verification method, the step SC specifically includes:

SC: Invoke the data compliance verification algorithm, decrypt and verify the data label codes respectively. If the verification fails, it is determined that the data has violations corresponding to the data label codes. The violations include illegal acquisition, illegal caching, illegal use, and illegal transactions. and illegal circulation; if all data label codes are verified, you can choose to continue to step SD;

SD, perform tampering verification, and verify the message verification code. If they are the same, it is determined that there is no tampering, and if they are different, it is determined that there is tampering.

In a preferred embodiment, the data compliance code verification algorithm is used to verify the coded information in the compliance code and the ciphertext part of the message authentication code. In a preferred embodiment, the ciphertext part is identified by the original data tag The code is mapped through the data dictionary and the message authentication code of the original data is spliced and generated using SM4 encryption. The specific generation method of the ciphertext part will be described in detail below. This application decrypts the compliance code and compares the encoded information with the information part of the information authentication code. If the comparison is the same, the tampering verification is continued. If the comparison is different, it is directly determined that there is a violation of the data.

In other preferred embodiments, the data receiver stores original data, and the content of the original data is the same as the original data used by the data sender to generate the compliance code. In this embodiment, after obtaining the compliance code (identification code) for verification, the data receiver generates an equivalent compliance code through the stored original data, and invokes the data compliance verification algorithm to verify the newly generated compliance code and Check whether the obtained compliance codes (identification codes) are the same.

In a preferred embodiment, an HMAC function is stored in the data receiver, and the HMAC function is used to form a message authentication code from the processed private data information. The authentication code is stored on the data recipient.

In a preferred embodiment, the HMAC function is specifically:

Wherein, opad and ipad are constants, M is the data to be processed, Key1 is the first initial key, and Key2 is the second key.

The first initial key Key1=SM3 (S ₁ ), the S ₁ is generated according to the current time T ₁ and using a random number tool. The second key Key ₂ =SM3(S ₂ ||Key1), the S ₂ is generated according to the current time T ₂ and using a random number tool.

As shown in Figure 2, the obtained message verification code is tampered with verification. The third verification party first decrypts the ciphertext compliance code and splits it to obtain the message verification code, extracts the original data message verification code, and provides it with the data receiver. If the verification is successful, it means that the data has not been tampered with; if the verification fails, it means that the data has been tampered with.

As shown in FIG. 3 , which is the HMAC processing flow chart of the application, first obtain the value of the first secret key Key1 Key1=SM3 (S ₁ ), and the S ₁ is based on the current time T ₁ and uses a random number generated by the tool. XOR the generated key Key1 with the opad to obtain the _first S1 (this S1 is different from S1), splicing S1 with the data tag encoding information and the information authentication code, and XOR the spliced content with Key2 and the ipad. Or, the second key Key2=SM3 (S ₂ ||Key1), and the S ₂ is generated according to the current time T ₂ and using a random number tool.

The present application also includes a method for generating the above compliance code, as shown in FIG. 4 , the method includes the steps:

S1, the data source collects raw data;

S2, establish a data dictionary mapping encoding rule table;

S3, the data is divided into batches to generate batch data labels;

S4, selecting a data tag, and splicing the data dictionary mapping code and HMAC value corresponding to the data tag to form the data to be encrypted;

S4-1, splicing the data to obtain the label code, and splicing the HMAC value obtained after the data is bound to the data source identity and the user identity;

S4-2, splicing data cache tag encoding, splicing the data use deadline information;

S4-3, splicing the data using tag encoding, splicing the value obtained after the data is mapped to the data dictionary using the category information tag;

S4-4, splicing the code of the data transaction label, and splicing the value obtained after performing the data dictionary mapping on the data transaction information label;

S4-5, splicing the data flow to label coding, splicing the HMAC value obtained after performing data dictionary mapping on the batch label and adding the total amount of batch transactions;

S4-6, splicing the HMAC value of the data plaintext.

S5, using the national secret SM4 to encrypt the data to be encrypted to obtain the ciphertext;

S6, calling a two-dimensional code generation algorithm to process the ciphertext to generate a compliance code.

In a preferred compliance code verification method, the step SC is specifically: calling a data compliance verification algorithm, decrypting and verifying each data tag code respectively, if the verification fails, judging that the data has a violation corresponding to the data tag encoding, specifically includes steps

SC-1, judge whether the data acquisition label code has passed the verification, if the verification fails, it means that the data is illegally acquired;

SC-2, judge whether the data cache label coding has passed the verification, if the verification fails, it means that the data has illegal cache;

SC-3, judge whether the data use label coding has passed the verification, if the verification fails, it means that the data is used illegally;

SC-4, judge whether the data transaction label code has passed the verification, if the verification fails, it means that there is an illegal transaction in the data;

SC-5, judge whether the data flow label code has passed the verification, if the verification fails, it means that the data has been transferred illegally;

Preferably, the steps SC-1 to SC-5 and S4-1 to S4-6 do not represent a specific order, and the steps SC-1 to SC-5 and S4-1 to S4-6 can be performed simultaneously or by setting Execute sequentially.

If all data label codes are verified and passed, you can choose to continue to step SD;

SD, perform tampering verification, and verify the message verification code. If they are the same, it is determined that there is no tampering, and if they are different, it is determined that there is tampering.

In a preferred embodiment, the raw data is obtained from said data source.

The original data includes: the time to which the data belongs, the time when the data is generated, the data source number, the industry number to which the data belongs, the validity period of the data content, the data field number, the data content, the code of the trading platform, the ID code of the dealer, the validity period of the data transaction, and the selling customer. ID code, allowable application industry, allowable application scenario, data transaction time, data transaction method, charging type, data field number.

Preferably, the original data label is obtained by reading the original file, selecting a worksheet as required, and traversing the entire document to read the data in the entire book (the first row is the column name, so choose to skip);

In a preferred embodiment, each piece of transaction data is accompanied by a unique compliance code. That is, the original data is obtained for the data source of each piece of data, and the corresponding compliance code is generated for the original data according to the above-mentioned compliance code generation method.

In practical applications, the data owner (data sender) provides each generated compliance code to the data receiver, and the data receiver stores the compliance code. In other preferred embodiments, the data owner (data sender) provides each generated compliance code and its corresponding original data ciphertext to the data receiver, and the data receiver stores the compliance code and the corresponding Original data ciphertext.

As shown in Figure 5, it is a flow chart of other preferred compliance code generation methods, including step A1 to obtain original data from a data source, A2 to add batch division identifier T, to obtain data source identity information identifier and data reception through HMAC function The message authentication code H _I of the party identity information identifier splicing identifier I, the data use deadline identifier T _s , the data usage identifier U, the data transaction identifier P, and the message of the data flow batch and batch quantity integrity identifier C obtained by the HMAC function Authentication code H _C , A3 performs data dictionary mapping encoding on the above identification, A4 generates the message authentication code H _D of the data content and splices the above encoding information and message authentication code information, A5 uses SM4 encryption to generate the compliance code ciphertext, A6 calls the second The dimensional code generation algorithm generates compliance codes.

The present application also includes a computer-readable medium having computer-readable instructions stored thereon, the computer-readable instructions being executable by a processor to perform the verification method of a compliance code for protecting data privacy.

The processor can perform the following steps for compliance code violation and tamper verification:

SA: The data receiver obtains the multi-factor ciphertext compliance code for verification, and the data receiver stores a multi-factor ciphertext compliance code composed of multiple data tag data dictionary mapping codes and message authentication codes as the verification standard, including the first compliance code, the Multi-factor encryption compliance codes of the second compliance code, the third compliance code, the fourth compliance code, the fifth compliance code and the sixth compliance code;

SB: Invoke the data compliance verification algorithm to decrypt and verify the first compliance code, the second compliance code, the third compliance code, the fourth compliance code, the fifth compliance code, and the sixth compliance code;

SC: Invoke the data compliance verification algorithm, decrypt and verify the data label codes respectively. If the verification fails, it is determined that the data has violations corresponding to the data label codes. The violations include illegal acquisition, illegal caching, illegal use, and illegal transactions. and illegal circulation; if all data label codes are verified, you can choose to continue to step SD;

SD, perform tampering verification, and verify the message verification code. If they are the same, it is determined that there is no tampering, and if they are different, it is determined that there is tampering.

As shown in this application and in the claims, unless the context clearly dictates otherwise, the words "a", "an", "an" and/or "the" are not intended to be specific in the singular and may include the plural. "First" and "Second" are not qualifiers, but are only for explanation and to facilitate the understanding of the technical solution of the invention, and the contents involved in "First" and "Second" can be replaced with each other. Generally speaking, the terms "comprising" and "comprising" only imply that the clearly identified steps and elements are included, and these steps and elements do not constitute an exclusive list, and the method or apparatus may also include other steps or elements.

The components, relative arrangements, functions, values set forth in these embodiments do not limit the scope of the invention unless specifically stated otherwise. Meanwhile, it is obvious that the dimensions of the various parts shown in the accompanying drawings are not drawn according to the actual proportional relationship for convenience of description. Techniques, methods, and devices known to those of ordinary skill in the relevant art will not be described in detail for the time being, but where appropriate, the techniques, methods, and devices should be considered as part of the authorized specification. In all examples shown and discussed herein, any specific value should be construed as illustrative only and not as limiting. Accordingly, other examples of step-by-step embodiments may have different sequences.

The above is an illustration of the present invention and should not be construed as limiting it. Although several exemplary embodiments of the present invention have been described, those skilled in the art will readily appreciate that many modifications can be made to the exemplary embodiments without departing from the technical characteristics of the present invention. Accordingly, all such modifications are intended to be included within the scope of this invention as defined in the claims. It is to be understood that the foregoing descriptions of the invention are not to be considered limited to the particular embodiments disclosed, and that modifications to the disclosed embodiments, as well as other embodiments, are intended to be included within the scope of the appended claims. The invention is defined by the claims and their equivalents.

Claims (10)

1. A compliance code verification method for protecting data privacy is characterized by comprising the following steps:

and SA: a data receiver acquires an identification code for verification, and the data receiver stores a compliance code serving as a verification standard; the compliance code is a multi-factor compliance code and comprises a plurality of data label codes and a message authentication code which are spliced as verification factors;

SB: calling a data compliance verification algorithm to decrypt and verify the compliance code and the identification code;

and (3) SC: judging whether the data pass the compliance verification, and if the compliance verification fails, indicating that the data have illegal operation; if the verification is passed, the tampering verification can be selected to be continuously carried out, and if the tampering does not exist, the verification is successful.

2. The compliance code verification method according to claim 1, wherein the step SC specifically comprises:

SC: calling a data compliance verification algorithm, decrypting and respectively verifying each data label code, and if the verification fails, judging that the data has an illegal behavior corresponding to the data label code; if all the data label codes pass the verification, the step SD can be selected to be continuously executed;

and SD, performing tampering check, checking the message verification code, if the message verification code is the same, judging that no tampering exists, and if the message verification code is different, judging that tampering exists.

3. The method for verifying the compliance code for protecting the data privacy of claim 1, wherein the compliance code is generated by adding a plurality of tags to original data in advance, performing joint encoding on tag data and data source identification information, and generating the compliance code by using HMAC to obtain the encoding and the digest information of the data and splicing and encrypting the encoding and the digest information.

4. The compliance code verification method of claim 3, wherein the compliance code generation step comprises:

s1, collecting original data by a data source;

s2, establishing a data dictionary mapping and encoding rule table;

s3, dividing the data into batches to generate batch data labels;

s4, selecting a data label, and splicing the data dictionary mapping code and the HMAC value corresponding to the data label to form data to be encrypted;

s5, encrypting the data to be encrypted by using the state secret SM4 to obtain a ciphertext;

and S6, calling a two-dimensional code generation algorithm to process the ciphertext to generate a compliance code.

5. The compliance code verification method according to claim 4, wherein the step S4 specifically comprises the steps of,

s4-1, splicing the data to obtain a label code, and splicing the data to obtain an HMAC value after the data is bound by a data source identity and a user identity;

s4-2, splicing data cache label codes, and splicing the data to use deadline information;

s4-3, splicing data, namely encoding the spliced data by using labels, and splicing values obtained after data dictionary mapping is carried out on the spliced data by using category information labels;

s4-4, splicing data transaction label codes, and splicing values obtained after data dictionary mapping is carried out on the data transaction information labels;

s4-5, splicing data flow label codes, and splicing HMAC values obtained after performing data dictionary mapping on the batch labels and adding batch transaction total amount;

and S4-6, splicing the HMAC values of the data cleartext.

6. The method for generating compliance codes for protecting data privacy according to claim 2, 4 or 5, wherein the step SC specifically comprises: calling a data compliance verification algorithm, decrypting and respectively verifying each data label code, and if the verification fails, judging that the data has violation behaviors corresponding to the data label codes, wherein the method specifically comprises the following steps

SC-1, judge whether the label code of data acquisition passes the check, if the check fails, prove that the data has violation to obtain;

SC-2, judge whether the data cache label code passes the check, if the check fails, show that the data has the cache of violation;

SC-3, judge whether the data uses the label code to pass the check, if the check fails, show that the data has illegal use;

SC-4, judge whether the label code of data transaction passes the verification, if the verification fails, show that the data has illegal transaction;

SC-5, judge whether the label code of data flow passes the verification, if the verification fails, show that the data has flow violating;

if all the data label codes pass the verification, the step SD can be selected to be continuously executed;

and SD, performing tampering check, checking the message verification code, if the message verification code is the same, judging that no tampering exists, and if the message verification code is different, judging that tampering exists.

7. The compliance code verification method according to claim 3 or 4, wherein the HMAC is specifically:

the opad and the ipad are constants, M is data to be processed, Key1 is a first initial Key, and Key2 is a second Key.

8. The method of generating compliance codes for protecting data privacy of claim 5 wherein the first primary Key Key is ₁ ＝SM3(S ₁ ) Said S ₁ According to the current time T ₁ And is generated using a random number tool,

the second Key Key ₂ ＝SM3(S ₂ | Key1), S ₂ According to the current time T ₂ And generated using a random number tool.

9. The method of claim 4, wherein the raw data comprises: the data transaction method comprises the following steps of data belonging time, data generation time, data source number, data belonging industry number, data content validity period, data field number, data content, transaction platform code, transaction provider ID code, data transaction validity period, selling customer ID code, permitted application industry, permitted application scene, data transaction time, data transaction mode, charging type and data field number.

10. A computer readable medium having stored thereon computer readable instructions executable by a processor to implement a method of verifying compliance codes for protecting data privacy of any one of claims 1 to 9.

Images