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

Abstract

The invention relates to a compliance code verification method and computer-readable medium for protecting data privacy. The verification method includes SA: the data recipient obtains an identification code for verification, and the data recipient stores a compliance code as a verification standard; the compliance code is a multi-factor compliance code, including multiple data label codes and message authentication codes as verification factors; SB: calling a data compliance verification algorithm to decrypt and verify the compliance code and identification code; SC: judging whether the compliance verification is passed. If the verification fails, it means that there is an illegal operation in the data; 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

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an efficient compliance code verification method and computer-readable medium for protecting data privacy. Background Art

[0002] In the data transmission process of the prior art, in order to ensure the security and integrity of the data, it is usually necessary to encrypt the data and process the message digest. Among them, SM4 is a block cipher standard adopted by the government of the People's Republic of China. In the commercial cryptographic system, SM4 is mainly used for data encryption, and its algorithm is public. The block length and key length are both 128 bits. The encryption algorithm and the key expansion algorithm both use a 32-round nonlinear iterative structure, and the S box used for encryption is a 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 signatures and verification, message authentication code generation and verification, random number generation, etc., and its algorithm is public. According to the State Cryptography Administration, its security and efficiency are better than the SHA-256 algorithm.

[0003] 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 circulated to the enterprise in compliance and correctly applied through the network API or access to the compliance verification address. Therefore, how to conduct data compliance verification and tampering verification and other issues are currently urgent problems that technicians in this field need to solve. Summary of the invention

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

[0005] In order to achieve the above-mentioned purpose, the invention has the following structure:

[0006] This application includes a compliance code verification method for protecting data privacy, including the steps of:

[0007] SA: The data recipient obtains an identification code for verification, and the data recipient stores a compliance code as a verification standard; the compliance code is a multi-factor compliance code, including multiple data tag codes and message authentication codes as verification factors;

[0008] SB: Calling the data compliance verification algorithm to decrypt and verify the compliance code and identification code;

[0009] SC: Determine whether the compliance verification has passed. If the verification fails, it means that there are illegal operations in the data. If the verification passes, you can choose to continue with the tampering verification. If there is no tampering, the verification is successful.

[0010] In the preferred compliance code verification method, the step SC specifically includes:

[0011] SC: Call the data compliance verification algorithm, decrypt and verify each data label code separately. If the verification fails, it is determined that the data has violations corresponding to the data label code; if all data label codes pass the verification, you can choose to continue to step SD;

[0012] SD, performs tampering verification, verifies the message verification code, if they are the same, it is determined that there is no tampering, if they are different, it is determined that there is tampering.

[0013] In the preferred compliance code verification method, the compliance code is generated by pre-adding multiple tags to the original data, jointly encoding the tag data and the data source identity information, using HMAC to obtain the summary information of the code and data and concatenating and encrypting them to generate the compliance code.

[0014] In the preferred compliance code verification method, the compliance code generation step includes:

[0015] S1, data source collects raw data;

[0016] S2, establish a data dictionary mapping encoding rule table;

[0017] S3, dividing the data into batches to generate batch data labels;

[0018] S4, select a data tag, and concatenate the data dictionary mapping code and HMAC value corresponding to the data tag to form the data to be encrypted;

[0019] S5, using the national encryption SM4 to encrypt the data to be encrypted to obtain a ciphertext;

[0020] S6, calling the QR code generation algorithm to process the ciphertext to generate a compliant code.

[0021] In the preferred compliance code verification method, the step S4 specifically includes the steps of:

[0022] S4-1, splicing data to obtain label codes, splicing the HMAC value obtained after binding the data source identity and the user identity of the data;

[0023] S4-2, splicing data cache tag codes and splicing the data usage deadline information;

[0024] S4-3, concatenating data using label coding, concatenating values ​​obtained after data dictionary mapping using category information labels of the data;

[0025] S4-4, splicing data transaction label codes, splicing values ​​obtained after data dictionary mapping of the data transaction information labels;

[0026] S4-5, splicing the data flow label code, splicing the HMAC value obtained after the batch label is mapped to the data dictionary and appending the total amount of batch transactions;

[0027] S4-6, concatenate the HMAC value of the data plaintext.

[0028] In the preferred compliance code verification method, the step SC is specifically: calling the data compliance verification algorithm, decrypting and verifying each data label code respectively, if the verification fails, judging that the data has a violation corresponding to the data label code, specifically including the steps

[0029] SC-1, determine whether the data acquisition tag code has passed the verification. If the verification fails, it means that the data has been obtained illegally;

[0030] SC-2, determine whether the data cache tag code has passed the verification. If the verification fails, it means that the data is illegally cached;

[0031] SC-3, determine whether the data usage label code has passed the verification. If the verification fails, it means that the data has been used in violation of regulations;

[0032] SC-4, determine whether the data transaction tag code has passed the verification. If the verification fails, it means that there is illegal transaction in the data;

[0033] SC-5, determine whether the data flow label code has passed the verification. If the verification fails, it means that the data has been illegally circulated;

[0034] If all data label codes are verified, you can choose to proceed to step SD;

[0035] SD, performs tampering verification, verifies the message verification code, if they are the same, it is determined that there is no tampering, if they are different, it is determined that there is tampering.

[0036] In the preferred compliance code verification method, the HMAC is specifically:

[0037]

[0038] Among them, opad and ipad are constants, M is the data to be processed, Key1 is the first initial key, and Key2 is the second key.

[0039] In the preferred compliance code verification method, the first initial secret key Key1 = SM3 (S1), and the S1 is generated according to the current time T1 using a random number tool.

[0040] The second key Key2=SM3(S2||Key1), wherein S2 is generated according to the current time T2 using a random number tool.

[0041] In the preferred compliance code verification method, the original data includes: data time, data generation time, data source number, data industry number, data content validity period, data field number, data content, trading platform code, trader ID code, data transaction validity period, selling customer ID code, allowed application industry, allowed application scenario, data transaction time, data transaction method, charging type, and data field number.

[0042] The present application also includes a computer-readable medium having computer-readable instructions stored thereon, and the computer-readable instructions can be executed by a processor to implement the method for verifying compliance codes for protecting data privacy.

[0043] The compliance code verification method and computer-readable medium for protecting data privacy of the present application are adopted, and the verification method includes SA: the data recipient obtains the identification code for verification, and the data recipient 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; SB: calling the data compliance verification algorithm to decrypt and verify the compliance code and identification code; SC: judging whether the compliance verification is passed, if the verification fails, it means that there is an illegal operation in the data; 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 A preferred step diagram of a compliance code verification method for protecting data privacy;

[0045] Figure 2 Diagram of steps to verify tampering of compliance codes to protect data privacy

[0046] Figure 3 A preferred step diagram for the preferred HMAC technique;

[0047] Figure 4 A compliance code generation step for the first preferred embodiment to protect data privacy;

[0048] Figure 5 The compliance code generation step of the second preferred embodiment is to protect data privacy. DETAILED DESCRIPTION

[0049] The technical solutions in the embodiments of the present disclosure will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work also fall within the scope of protection of the present invention.

[0050] This application includes a compliance code verification method for protecting data privacy, including the steps of:

[0051] SA: The data recipient obtains an identification code for verification, and the data recipient stores a compliance code as a verification standard; the compliance code is a multi-factor compliance code, including multiple data tag codes and message authentication codes as verification factors;

[0052] SB: Calling the data compliance verification algorithm to decrypt and verify the compliance code and identification code;

[0053] SC: Determine whether the compliance verification has passed. If the verification fails, it means that there are illegal operations in the data. If the verification passes, you can choose to continue with the tampering verification. If there is no tampering, the verification is successful.

[0054] In the data transmission process of the prior art, the national secret SM4 is usually used to encrypt data. The SM4 encryption algorithm is public, and the block length and key length are both 128 bits. The encryption algorithm and the key expansion algorithm both adopt a 32-round nonlinear iterative structure, and the S box used for encryption is a fixed 8-bit input and 8-bit output. For exemplary technical solutions, refer to the "Information Security Technology SM4 Block Cipher Algorithm" (GB / T 32907-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. 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.

[0055] Based on the existing ciphertext generated by encrypting message data through the SM4 encryption algorithm, the present application adds a technical solution in which a message verification code is generated by further using the SM3 hash algorithm on the message data to determine whether the ciphertext has violated regulations or been tampered with.

[0056] The technical solution of the exemplary SM3 hash algorithm can refer to the "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. It should be known that the technical solution recorded in the above-mentioned "Information Security Technology SM3 Cryptographic Hash Algorithm" is the prior art of this application and can be directly applied to the technical solution of this application.

[0057] 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 recipient, and stores it in the data recipient's storage unit as a verification standard. For ease of distinction, the code obtained by the data recipient for verification is called an 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.

[0058] When data transmission is required and there is a need to verify the ciphertext, the data recipient submits the verification information to a trusted third-party verification agency, which decrypts and verifies the compliance code stored in the data recipient by calling the data compliance verification algorithm.

[0059] The compliance code is generated by concatenating and encrypting the data tag encoding information and the plaintext data message authentication code, and then calling a two-dimensional code generation algorithm to generate the code.

[0060] In the preferred compliance code verification method, the compliance code is generated by pre-adding multiple tags to the original data, jointly encoding the tag data and the data source identity information, using HMAC to obtain the summary information of the code and data and concatenating and encrypting them to generate the compliance code.

[0061] In the preferred compliance code verification method, the step SC specifically includes:

[0062] SC: Call the data compliance verification algorithm, decrypt and verify each data label code separately. If the verification fails, it is determined that the data has violations corresponding to the data label code, including illegal acquisition, illegal caching, illegal use, illegal transactions and illegal circulation. If all data label codes pass the verification, you can choose to continue to step SD;

[0063] SD, performs tampering verification, verifies the message verification code, if they are the same, it is determined that there is no tampering, if they are different, it is determined that there is tampering.

[0064] In a preferred embodiment, the data compliance code verification algorithm is used to verify the coded information and message authentication code ciphertext part in the compliance code. In a preferred embodiment, the ciphertext part is generated by the original data tag through data dictionary mapping encoding and taking the message authentication code of the original data and then splicing and 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 coded information and the information part of the message authentication code. If the comparison is the same, the tampering verification will continue. If the comparison is different, it will directly determine that the data has violated the regulations.

[0065] In other preferred embodiments, the data receiving party stores original data, and the content of the original data is the same as the original data used by the data sending party to generate the compliance code. In this embodiment, after the data receiving party obtains the compliance code (identification code) for verification, it generates an equivalent compliance code through the stored original data, and calls the data compliance verification algorithm to verify whether the newly generated compliance code and the obtained compliance code (identification code) are the same.

[0066] In a preferred embodiment, the data receiver stores an HMAC function, which is used to convert the processed private data information into a message authentication code. The authentication code is stored in the data receiver.

[0067] In a preferred embodiment, the HMAC function is specifically:

[0068]

[0069] Among them, opad and ipad are constants, M is the data to be processed, Key1 is the first initial key, and Key2 is the second key.

[0070] The first initial secret key Key1 = SM3 (S1), wherein S1 is generated according to the current time T1 using a random number tool. The second secret key Key2 = SM3 (S2||Key1), wherein S2 is generated according to the current time T2 using a random number tool.

[0071] like Figure 2 As shown, the obtained message authentication code is verified for tampering. The third verification party first decrypts the ciphertext compliance code and splits it to obtain the message authentication code, extracts the message authentication code of the original data, and compares it with the message authentication code provided by the data recipient. 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.

[0072] like Figure 3 As shown, it is the HMAC processing flow chart of the present application. First, the value of the first secret key Key1 is obtained, Key1=SM3(S1), and the S1 is generated according to the current time T1 and using a random number tool. The generated key Key1 is XORed with opad to obtain the first S1 (this S1 is different from S1), S1 is spliced ​​with the data tag encoding information and the information authentication code, and the spliced ​​content is XORed with Key2 and ipad. The second key Key2=SM3(S2||Key1), and the S2 is generated according to the current time T2 and using a random number tool.

[0073] This application also includes a method for generating the above-mentioned compliance code, such as Figure 4 As shown, the method comprises the steps of:

[0074] S1, data source collects raw data;

[0075] S2, establish a data dictionary mapping encoding rule table;

[0076] S3, dividing the data into batches to generate batch data labels;

[0077] S4, select a data tag, and concatenate the data dictionary mapping code and HMAC value corresponding to the data tag to form the data to be encrypted;

[0078] S4-1, splicing data to obtain label codes, splicing the HMAC value obtained after binding the data source identity and the user identity of the data;

[0079] S4-2, splicing data cache tag codes and splicing the data usage deadline information;

[0080] S4-3, concatenating data using label coding, concatenating values ​​obtained after data dictionary mapping using category information labels of the data;

[0081] S4-4, splicing data transaction label codes, splicing values ​​obtained after data dictionary mapping of the data transaction information labels;

[0082] S4-5, splicing the data flow label code, splicing the HMAC value obtained after the batch label is mapped to the data dictionary and appending the total amount of batch transactions;

[0083] S4-6, concatenate the HMAC value of the data plaintext.

[0084] S5, using the national encryption SM4 to encrypt the data to be encrypted to obtain a ciphertext;

[0085] S6, calling the QR code generation algorithm to process the ciphertext to generate a compliant code.

[0086] In the preferred compliance code verification method, the step SC is specifically: calling the data compliance verification algorithm, decrypting and verifying each data label code respectively, if the verification fails, judging that the data has a violation corresponding to the data label code, specifically including the steps

[0087] SC-1, determine whether the data acquisition tag code has passed the verification. If the verification fails, it means that the data has been obtained illegally;

[0088] SC-2, determine whether the data cache tag code has passed the verification. If the verification fails, it means that the data is illegally cached;

[0089] SC-3, determine whether the data usage label code has passed the verification. If the verification fails, it means that the data has been used in violation of regulations;

[0090] SC-4, determine whether the data transaction tag code has passed the verification. If the verification fails, it means that there is illegal transaction in the data;

[0091] SC-5, determine whether the data flow label code has passed the verification. If the verification fails, it means that the data has been illegally circulated;

[0092] Preferably, the steps SC-1 to SC-5, S4-1 to S4-6 do not represent a specific order, and the steps SC-1 to SC-5, S4-1 to S4-6 can be executed simultaneously or in a set order.

[0093] If all data label codes are verified, you can choose to proceed to step SD;

[0094] SD, performs tampering verification, verifies the message verification code, if they are the same, it is determined that there is no tampering, if they are different, it is determined that there is tampering.

[0095] In a preferred embodiment, raw data is obtained from the data source.

[0096] The original data includes: data time, data generation time, data source number, data industry number, data content validity period, data field number, data content, trading platform code, trader ID code, data transaction validity period, selling customer ID code, allowed application industry, allowed application scenario, data transaction time, data transaction method, charging type, and data field number.

[0097] Preferably, the original data labels are obtained by reading the original file, selecting a worksheet as required, and traversing the entire document to read the data therein (the first row is the column name, so it is skipped);

[0098] In a preferred embodiment, each piece of transaction data is accompanied by a unique compliance code, that is, the original data is obtained from the data source of each piece of data, and a corresponding compliance code is generated for the original data according to the above compliance code generation method.

[0099] 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.

[0100] like Figure 5As shown, it is a flowchart of another preferred compliance code generation method, including step A1 to obtain original data from the data source, step A2 to add a batch division identifier T, and to obtain a message authentication code H of the data source identity information identifier and the data recipient identity information identifier splicing identifier I through the HMAC function. I , Data usage deadline mark T s , data usage identifier U, data transaction identifier P, and the message authentication code H of the data flow batch and batch quantity integrity identifier C obtained through the HMAC function C A3 performs data dictionary mapping encoding on the above identifiers, and A4 generates a message authentication code H for the data content. D The above encoding information and message authentication code information are concatenated, A5 uses SM4 encryption to generate a compliance code ciphertext, and A6 calls a QR code generation algorithm to generate a compliance code.

[0101] The present application also includes a computer-readable medium having computer-readable instructions stored thereon, and the computer-readable instructions can be executed by a processor to implement the method for verifying compliance codes for protecting data privacy.

[0102] The processor can perform the following steps to verify compliance code violations and tampering:

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

[0104] SB: calling 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;

[0105] SC: Call the data compliance verification algorithm, decrypt and verify each data label code separately. If the verification fails, it is determined that the data has violations corresponding to the data label code, including illegal acquisition, illegal caching, illegal use, illegal transactions and illegal circulation. If all data label codes pass the verification, you can choose to continue to step SD;

[0106] SD, performs tampering verification, verifies the message verification code, if they are the same, it is determined that there is no tampering, if they are different, it is determined that there is tampering.

[0107] As shown in this application and claims, unless the context clearly indicates an exception, the words "a", "an", "a kind" and / or "the" do not specifically refer to the singular, but may also include the plural. "First" and "second" are not qualifiers, but are only for explanation to facilitate understanding of the technical solution of the invention. The contents involved in "first" and "second" can be interchangeable. Generally speaking, the terms "including" and "comprising" only indicate that the steps and elements that have been clearly identified are included, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0108] Unless otherwise specifically stated, the components, relative arrangements, functions, and numerical values ​​described in these embodiments do not limit the scope of the present invention. At the same time, it is obvious that for ease of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship. The techniques, methods, and equipment known to ordinary technicians in the relevant fields are not described in detail, but where appropriate, the techniques, methods, and equipment should be regarded as part of the authorization specification. In all examples shown and discussed here, any specific values ​​should be interpreted as merely exemplary and not as a limitation. Therefore, other examples of step-by-step embodiments may have different sequences.

[0109] The above is an explanation of the present invention and should not be considered as a limitation thereof. Although several exemplary embodiments of the present invention have been described, it will be readily understood by those skilled in the art that many modifications may be made to the exemplary embodiments without departing from the technical features of the present invention. Therefore, all of these modifications are intended to be included within the scope of the present invention as defined in the claims. It should be understood that the above is an explanation of the present invention and should not be considered as being limited to the specific embodiments disclosed, and modifications to the disclosed embodiments and other embodiments are intended to be included within the scope of the appended claims. The present invention is defined by the claims and their equivalents.

Claims

1. A compliance code verification method for protecting data privacy, characterized in that: Includes steps: SA: The data receiver obtains an identification code for verification, and the data receiver stores a compliance code as a verification standard; the compliance code is generated by adding multiple data tags to the original data in advance, jointly encoding the data tag and the data source identity information, using HMAC to obtain the code and data summary information and splicing and encrypting them to generate the compliance code; the compliance code is a multi-factor compliance code, including multiple data tag codes and message authentication codes as verification factors; SB: Calling the data compliance verification algorithm to decrypt and verify the compliance code and identification code; SC: Call the data compliance verification algorithm, decrypt and verify each data label code separately. If the verification fails, it is determined that the data has a violation corresponding to the data label code; the specific steps include: SC-1, determine whether the data acquisition tag code has passed the verification. If the verification fails, it means that the data has been obtained illegally; SC-2, determine whether the data cache tag code has passed the verification. If the verification fails, it means that the data is illegally cached; SC-3, determine whether the data usage label code has passed the verification. If the verification fails, it means that the data has been used in violation of regulations; SC-4, determine whether the data transaction tag code has passed the verification. If the verification fails, it means that there is illegal transaction in the data; SC-5, determine whether the data flow label code has passed the verification. If the verification fails, it means that the data has been illegally circulated; If all data label codes are verified, you can choose to proceed to step SD; SD, conducts tampering verification, verifies the message authentication code, the third party verifier decrypts the ciphertext compliance code and splits it to obtain the message authentication code, extracts the message authentication code of the original data, and compares it with the message authentication code provided by the data recipient for verification. If they are the same, it is determined that there is no tampering, if they are different, it is determined that there is tampering.

2. The compliance code verification method for protecting data privacy according to claim 1 is characterized in that: The steps of generating the compliance code include: S1, data source collects raw data; S2, establish a data dictionary mapping encoding rule table; S3, dividing the data into batches to generate batch data labels; S4, select a data tag, and concatenate the data dictionary mapping code and HMAC value corresponding to the data tag to form the data to be encrypted; S5, using the national encryption SM4 to encrypt the data to be encrypted to obtain a ciphertext; S6, calling the QR code generation algorithm to process the ciphertext to generate a compliant code.

3. The compliance code verification method for protecting data privacy according to claim 2 is characterized in that: The step S4 specifically includes the steps of: S4-1, splicing data to obtain label codes, splicing the HMAC value obtained after binding the data source identity and the user identity of the data; S4-2, splicing data cache tag encoding, splicing data usage deadline information; S4-3, splicing data using label encoding, splicing uses category information data labels to obtain values ​​after data dictionary mapping; S4-4, splicing data transaction tag encoding, splicing transaction information data tag and obtaining the value after data dictionary mapping; S4-5, concatenate the data flow label encoding, concatenate the batch data label, perform data dictionary mapping, and append the HMAC value obtained after the total batch transaction amount; S4-6, HMAC value of the concatenated data plaintext.

4. The compliance code verification method for protecting data privacy according to claim 1 or 2, characterized in that: The HMAC is specifically: HMAC(Key,M)=SM3(Key1⊕opad||M||Key2⊕ipad), Among them, opad and ipad are constants, M is the data to be processed, Key1 is the first initial key, and Key2 is the second key.

5. The compliance code verification method for protecting data privacy according to claim 4 is characterized in that: The first initial key Key1 = SM3 (S1), wherein S1 is generated according to the current time T1 using a random number tool, The second key Key2=SM3(S2||Key1), wherein S2 is generated according to the current time T2 using a random number tool.

6. The compliance code verification method for protecting data privacy according to claim 2 is characterized in that: The original data includes: data time, data generation time, data source number, data industry number, data content validity period, data field number, data content, trading platform code, trader ID code, data transaction validity period, selling customer ID code, allowed application industry, allowed application scenario, data transaction time, data transaction method, charging type, and data field number.

7. A computer-readable medium having computer-readable instructions stored thereon, wherein the computer-readable instructions can be executed by a processor to implement the compliance code verification method for protecting data privacy as described in any one of claims 1 to 6.

Images