Data processing method, electronic device, storage medium and program product

Abstract

The invention provides a data processing method, electronic equipment, a readable storage medium and a computer program product. The data processing method comprises the steps of performing data encryption on unencrypted data to obtain encrypted data; performing data separation on the encrypted data to obtain a plurality of encrypted sub-data, each encrypted sub-data corresponding to a service type; acquiring associated data associated with the encrypted sub-data, and generating an intermediate data set which comprises one encrypted sub-data and associated data associated with the encrypted sub-data; and matching a verification task corresponding to the encrypted sub-data, and executing the verification task by adopting the intermediate data set to obtain verified sub-data.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a data processing method, an electronic device, a storage medium, and a program product. Background Art

[0002] With the development of big data technology, data collection, storage, processing and application have become important links in the application of big data in various industries. However, in the data verification link of data processing, there are scenarios where internal personnel directly access the data. When data faces malicious attacks from internal personnel, how to ensure the security and accuracy of the data becomes an important challenge. Summary of the invention

[0003] In order to solve at least one of the above technical problems, the present disclosure provides a data processing method, an electronic device, a storage medium and a program product.

[0004] According to one aspect of the present disclosure, there is provided a data processing method, comprising: Encrypt unencrypted data to obtain encrypted data; separate the encrypted data to obtain multiple encrypted sub-data, each encrypted sub-data corresponding to a business type; obtain associated data associated with the encrypted sub-data, and generate an intermediate data set, the intermediate data set including one encrypted sub-data and the associated data associated with it; and match the verification task corresponding to the encrypted sub-data, and use the intermediate data set to execute the verification task to obtain verified sub-data.

[0005] According to the data processing method of at least one embodiment of the present disclosure, unencrypted data is encrypted to obtain encrypted data, including: obtaining corresponding data access parameters according to the data type of the unencrypted data; matching the data encryption algorithm corresponding to the data access parameters; and encrypting the unencrypted data using the matched data encryption algorithm, and accessing the encrypted data using the data access parameters to obtain the encrypted data.

[0006] According to the data processing method of at least one embodiment of the present disclosure, the encrypted data is separated to obtain multiple encrypted sub-data, each of which corresponds to a business type, including: querying multiple verification tasks corresponding to the encrypted data, each of which is used to verify data of a business type; and separating the encrypted data into multiple encrypted sub-data, each of which corresponds to one verification task.

[0007] According to the data processing method of at least one embodiment of the present disclosure, the associated data associated with the encrypted sub-data is configured as: data that is business-associated with the encrypted sub-data.

[0008] According to the data processing method of at least one embodiment of the present disclosure, matching the verification task corresponding to the encrypted sub-data includes: obtaining the initial verification rules corresponding to the unencrypted data, the initial verification rules including multiple verification tasks, each of the verification tasks being used to verify data having a specific field; and matching the verification tasks corresponding to the same specific field according to the specific field of the encrypted sub-data to obtain the verification tasks corresponding to the encrypted sub-data.

[0009] According to the data processing method of at least one embodiment of the present disclosure, the intermediate data set is used to perform the verification task to obtain verified sub-data, including: using the encrypted sub-data in the intermediate data set to perform the verification task to obtain a first execution result; using the associated data in the intermediate data set to perform the verification task to obtain a second execution result; performing data verification on the first execution result through the second execution result to obtain a verification result; and obtaining a verification mark corresponding to the verification result, and adding the verification mark to the encrypted sub-data to obtain the verified sub-data; wherein the data verification includes at least one of data format verification, data integrity verification, data consistency verification, and rule logic verification.

[0010] According to at least one embodiment of the data processing method of the present disclosure, the method further includes: mapping the verification mark of the verified sub-data to a verification result of the encrypted sub-data.

[0011] According to the data processing method of at least one embodiment of the present disclosure, the number of verified sub-data is multiple, and the verified sub-data has a verification mark, and the verification mark includes an abnormal mark; the data processing method also includes: screening out the verified sub-data with the abnormal mark to obtain abnormal sub-data; obtaining the initial sub-data corresponding to the abnormal sub-data in the unencrypted data; and; in response to a search instruction for an object field, displaying the initial sub-data with the object field and the abnormal sub-data corresponding to the initial sub-data with the object field.

[0012] According to another aspect of the present disclosure, an electronic device is provided, comprising: a memory storing execution instructions; and a processor executing the execution instructions stored in the memory, so that the processor executes the data processing method of any embodiment of the present disclosure.

[0013] According to another aspect of the present disclosure, a readable storage medium is provided, wherein the readable storage medium stores execution instructions, and when the execution instructions are executed by a processor, the execution instructions are used to implement the data processing method of any embodiment of the present disclosure.

[0014] According to another aspect of the present disclosure, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the data processing method of any embodiment of the present disclosure is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings illustrate exemplary embodiments of the present disclosure and together with the description serve to explain the principles of the present disclosure. These drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this specification.

[0016] Figure 1 It is a schematic diagram of an application scenario of a data processing method according to an embodiment of the present invention.

[0017] Figure 2 It is a flowchart of a data processing method according to an embodiment of the present disclosure.

[0018] Figure 3 It is a flowchart of a data processing method according to an embodiment of the present disclosure.

[0019] Figure 4 It is a flowchart of a data processing method according to an embodiment of the present disclosure.

[0020] Figure 5 It is a flowchart of a data processing method according to an embodiment of the present disclosure.

[0021] Figure 6 It is a flowchart of a data processing method according to an embodiment of the present disclosure.

[0022] Figure 7 It is a flowchart of a data processing method according to an embodiment of the present disclosure.

[0023] Figure 8 It is a flowchart of a data processing method according to an embodiment of the present disclosure.

[0024] Fig. 9 It is a schematic block diagram of the structure of a data processing device according to one embodiment of the present disclosure.

[0025] Fig.10 It is a schematic block diagram of the structure of an electronic device equipped with a data processing device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0026] The present disclosure is further described in detail below in conjunction with the accompanying drawings and examples. It is understood that the specific examples described herein are only used to explain the relevant content, rather than to limit the present disclosure. It should also be noted that, for ease of description, only the parts related to the present disclosure are shown in the accompanying drawings.

[0027] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in the present disclosure can be combined with each other. The technical solution of the present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0028] With the development of big data technology, data collection, storage, processing and application have become important links in the application of big data in various industries. However, in the data verification link of data processing, there are scenarios where internal personnel directly access the data. When data faces malicious attacks from internal personnel, how to ensure the security and accuracy of the data becomes an important challenge.

[0029] To this end, the present disclosure proposes a data processing method to solve the above problems.

[0030] Figure 1 The application scenario of the data processing method of one embodiment of the present disclosure is shown. The application scenario is mainly used to verify data on the basis of ensuring data security to prevent malicious attacks or unauthorized use of verified data by internal personnel.

[0031] Figure 1The initial data in is the data to be verified, that is, the unencrypted data, called unencrypted data. First, the unencrypted data is encrypted into encrypted data, and then the encrypted data is separated into multiple encrypted sub-data, and finally each encrypted sub-data is matched with a corresponding verification task for data verification. In this way, on the one hand, encrypting the data before data verification can effectively protect the security of the data; on the other hand, separating the encrypted data into multiple encrypted sub-data for data verification can reduce the amount of data verified in each data verification link, thereby reducing the amount of data accessible to internal personnel, so that even if internal personnel can access the encrypted sub-data, it is difficult to associate it with other encrypted sub-data of the same source, further protecting the security of the data; on the third hand, matching each encrypted sub-data with a corresponding verification task for data verification can configure corresponding verification rules for various types of encrypted sub-data for verification, which can effectively improve the accuracy of the data and the efficiency of verification. In addition, before the encrypted sub-data is verified, the associated data that is business-related to the encrypted sub-data is combined with the encrypted sub-data to form an intermediate data set. The intermediate data set is verified during data verification, so that the data verification can use the upstream and downstream related data of the business scenario where the encrypted sub-data is located to verify the correctness and accuracy of the encrypted sub-data, ensuring the accuracy of the verification result. The verified encrypted sub-data is output as verified sub-data. The correlation between the verified sub-data and the unencrypted data is that the verified sub-data is a state where part of the unencrypted data has been encrypted and has a verification mark. The verification mark represents the data verification result of the verified sub-data and reflects the correctness of the data. The verified sub-data can be directly used for the task requirements within its business scenario scope, or it can be used for the task requirements within its business scenario scope after decryption. That is, the data encryption and data verification process experienced by the verified sub-data does not affect its data utility, and the availability of the data can be guaranteed.

[0032] For the convenience of description and to make the technical solutions of the specific implementation methods of the present disclosure easier to understand, before describing the data processing method implemented in the present disclosure, the technical terms involved in the specific implementation methods of the present disclosure are defined as follows: Data encryption is a technical means of protecting information security by using an encryption algorithm to convert plaintext (readable information) into ciphertext (unreadable information). Data encryption algorithms may include symmetric encryption algorithms, asymmetric encryption algorithms, hybrid encryption algorithms, etc., which are not limited here. Data encryption in the disclosed embodiments may be to encrypt specific fields in the data, so that the specific fields in the encrypted data after encryption may be rendered unreadable. In addition, data encryption in the disclosed embodiments also includes fuzzifying the specific fields in the encrypted data, that is, converting the readable specific fields into other readable fields according to certain conversion rules, so that the user of the data cannot read the specific fields from the encrypted data after encryption, but can read other fields as substitutes to replace the specific fields to achieve their original functions.

[0033] Data Segregation refers to dividing data into different parts or groups based on certain standards or rules. Data separation can be achieved by storing different types of data on different physical devices, or by isolating data on the same storage device through logical partitioning, access control, etc., without limitation here.

[0034] Data ingestion refers to the process of collecting data from various sources and introducing it into data storage systems (such as databases, data warehouses, data lakes, etc.).

[0035] Data cleaning, also known as data cleaning or data purification, refers to the process of preprocessing data to improve data quality. The goal of data cleaning is to identify and correct anomalies, inconsistencies, and missing values ​​in the data, so that the data is more suitable for further analysis or processing.

[0036] Data Verification is the process of checking data to ensure its accuracy, completeness and consistency.

[0037] Figure 2 FIG. 1 is a schematic diagram showing the overall flow of a data processing method M100 according to an embodiment of the present disclosure. Figure 2 The method shown includes steps S110 to S140. The method can be executed by electronic devices such as mobile phones and tablet computers.

[0038] Specifically, Figure 2 The methods shown include: S110: Encrypt the unencrypted data to obtain encrypted data.

[0039] The unencrypted data refers to the data that has not been processed before data processing is performed, and the encrypted data refers to the data obtained by encrypting the unencrypted data.

[0040] S120: Separate the encrypted data to obtain a plurality of encrypted sub-data, each of which corresponds to a service type.

[0041] In one example, the data separation method can be divided according to the business type corresponding to the data. For example, a certain encrypted data is related to the charging business of a certain user. The charging business specifically includes the purchase fee collection business, the service fee collection business and the tax business. The encrypted data includes the purchase fee data, the service fee data and the tax data. In this case, the encrypted data of the user can be separated into three parts: the purchase fee data, the service fee data and the tax data, and three encrypted sub-data are obtained. The three encrypted sub-data can be used independently or independently verified. For example, when verifying the purchase fee data, it is only necessary to retrieve the purchase data, and there is no need to retrieve the encrypted data containing the purchase fee data, the service fee data and the tax data. In this way, in the process of verifying the purchase fee data, the operation authority of the internal personnel responsible for verification can be configured so that the operation authority of the internal personnel is limited to the operation of the purchase fee data during the data verification process, which can effectively prevent the malicious attack and unauthorized use of the service fee data and the tax data by the internal personnel. In this way, compared with the method of retrieving encrypted data containing purchase fee data, service fee data and tax data for data verification when verifying purchase fee data, the method of retrieving purchase fee data separately for data verification can effectively protect data security. The main purpose of data separation is to enable the separated encrypted sub-data to be verified separately and independently, so as to reduce the amount of data that can be manipulated by internal personnel during the verification process and protect data security.

[0042] S130: Acquire associated data associated with the encrypted sub-data, and generate an intermediate data set, the intermediate data set including the encrypted sub-data and the associated data.

[0043] Among them, the associated data is data that has a business association with the encrypted sub-data. Business association means that the application scenarios of the data are associated. For example, the sales-related data of a certain commodity include dispatch data and bill data. The application scenario of the dispatch data is to count the number of orders assigned to the commodity, corresponding to the dispatch business; the application scenario of the bill data is to count the number of bills of the commodity that have been traded and settled, corresponding to the bill business. In the application scenario, for each bill data generated for a bill, there must be dispatch data corresponding to the bill, then the application scenario representing the dispatch data is associated with the application scenario of the bill data, that is, there is a business association between the bill data and the dispatch data. Assuming that the bill data is encrypted sub-data and data verification is required for the bill data, then in the data verification process, it is necessary to verify whether the bill number in the bill data is correct through the dispatch number in the corresponding dispatch data. Therefore, in the case where the bill data is encrypted sub-data, its corresponding dispatch data is the associated data associated with it. For another example, assuming that the bill amount in the bill data is also business-associated with the payment standard of the offline city, in the case where the bill data is encrypted sub-data, the corresponding payment standard data of the offline city is also the associated data associated with it. That is to say, the same encrypted sub-data may correspond to one or more associated data associated with it, depending on the business relevance of the data.

[0044] An intermediate data set is a collection of multiple data, and the multiple data in the intermediate data set include encrypted sub-data and associated data associated with the encrypted sub-data. The intermediate data set can be in the form of a wide table, an intermediate process table, a temporary table, etc., and there is no limitation here.

[0045] In one example, the data encryption, data separation and generation of the intermediate data set in the above steps S110 to S130 are all implemented in the database where the unencrypted data is located, and the data involved in the above process does not provide a query entry. In this way, it is possible to avoid the data involved in the above steps S110 to S130 from being obtained and used, and the data to be verified can be protected from malicious attacks or unauthorized use before the data verification is carried out, so as to effectively protect the security of the data.

[0046] S140, matching the verification task corresponding to the encrypted sub-data, and using the intermediate data set to execute the verification task to obtain the verified sub-data.

[0047] Among them, the verification task refers to a task that uses a certain verification rule or algorithm to verify the correctness of data. For example, in the case where the verification task is a certain verification rule, using the intermediate data set to perform the verification task means applying the defined verification rule to the intermediate data set to check whether the encrypted sub-data in the intermediate data set meets the expected standards, such as by comparing whether the format of the encrypted sub-data is consistent with the format of the associated data to verify whether the encrypted sub-data is consistent, verifying whether the value of the encrypted sub-data falls within the expected value range of the intermediate data set, verifying whether the specific field of the encrypted sub-data is unique in the intermediate data set, and verifying the logical correctness of the encrypted sub-data by comparing whether the format of the encrypted sub-data is consistent with the business logic of the associated data, etc., which are not listed here one by one. For another example, in the case where the verification task is a certain verification algorithm, using the intermediate data set to perform the verification task means processing the intermediate data set through the verification algorithm.

[0048] In one example, a plurality of verification tasks are stored in the rule base, corresponding to different business rules. The encrypted sub-data may correspond to at least one business rule. The verification task corresponding to the encrypted sub-data refers to the verification task corresponding to the same business. For example, a certain encrypted sub-data is dispatch data, and the corresponding business rule is the dispatch business. A certain verification task R1 corresponds to the dispatch business, which is used to verify whether the data related to the dispatch business is correct. Then the dispatch data corresponds to the verification task R1. When the dispatch data becomes encrypted sub-data, the verification task R1 can be matched as the verification task corresponding to the dispatch data.

[0049] Verified sub-data is the data output after the verification task is performed using the intermediate data set. The verified sub-data is basically the same as the encrypted sub-data, except that the verified sub-data has a verification mark, which is used to characterize the verification result of the verified sub-data, and the verification result includes data correctness and data anomaly. The verification mark can be a specific label, a specific field, a specific character, etc. added to the encrypted sub-data, and is not limited here. In other words, although the input item when performing the verification task is the intermediate data set, the purpose of the verification task is to verify the correctness of the encrypted sub-data in the intermediate data set, so the output item of performing the verification task can only include the verified sub-data corresponding to the encrypted sub-data. In other embodiments, the output item of performing the verification task can also include verified associated data corresponding to the associated data, that is, the verification task not only performs data verification on the encrypted sub-data, but also performs data verification on the associated data.

[0050] In one example, a rule engine can be used to perform data verification, by inputting an intermediate data set into the rule engine, executing the verification task in the rule engine, and outputting the verified sub-data by the rule engine. The rule engine is a software system for executing a series of predefined business rules. The rule engine can be a Drools engine, a JESS engine, an OpenRules engine, an Oracle Policy Automation engine, etc., without limitation.

[0051] In summary, the data processing method provided in this embodiment can encrypt and separate the original data, and generate an intermediate data set with the associated data for data verification. During data verification, the separated encrypted sub-data is mapped to the corresponding verification task, so that the operation authority of the internal personnel during data verification is limited to the encrypted sub-data, that is, it is limited to operating a part of the encrypted unencrypted data, which can ensure that the data that the internal personnel can operate is encrypted data, and reduce the amount of data that the internal personnel can operate. Thereby ensuring the data security of the data verification process.

[0052] Regarding step S110, in some embodiments of the present disclosure, it may include: Figure 3 Steps S1101 to S1103 are shown.

[0053] S1101. Obtain corresponding data access parameters according to the data type of the unencrypted data.

[0054] The data type represents the storage and access methods of data. Two data of the same data type have the same storage and access methods. Conversely, if one of the storage methods or access methods of two data is different, the data types of the two data are different.

[0055] Exemplarily, the data type of the unencrypted data may be interface data, Excel table data, MySQL data, etc., which is not limited here.

[0056] Data Ingestion Parameters refer to the various parameters that need to be configured during the data ingestion process to ensure that data can be correctly and efficiently transferred from the data source to the target system. Data of different data types have different access methods, and the corresponding data ingestion parameters are different. That is, each data type corresponds to its own data ingestion parameter.

[0057] S1102. Match the data encryption algorithm corresponding to the data access parameters.

[0058] Among them, each data access parameter corresponds to a data encryption algorithm, and different data access parameters correspond to different data types, that is, each data type corresponds to a data encryption algorithm. When the data access parameters of unencrypted data are available, the unencrypted data is characterized as accessible data. When configuring the data encryption algorithm, if a corresponding data encryption algorithm is configured for each data type, then when a certain data type does not have a corresponding data access parameter and data cannot be transmitted, the data encryption algorithm configured for this type of data is a redundant algorithm. Therefore, when configuring the data encryption algorithm, a corresponding data encryption algorithm is configured for each data access parameter to avoid redundant algorithms.

[0059] S1103: Use the matched data encryption algorithm to encrypt the unencrypted data, and use the data access parameter to access the encrypted data to obtain the encrypted data.

[0060] When the data access parameters corresponding to the unencrypted data can be obtained, on the one hand, it means that the unencrypted data is data that can be transmitted and obtained, and the data encryption algorithm corresponding to the data access parameters can be matched to support data encryption of the data type corresponding to the data access parameters. On the other hand, the data access parameters are used to access the encrypted data encrypted from the unencrypted data.

[0061] In one example, the data encryption algorithm corresponding to MySQL data is the encryption and decryption algorithm of the library table field dimension; the data encryption algorithm for interface data has corresponding signature verification, while retaining a separate encryption and decryption algorithm for specific fields.

[0062] Exemplarily, in one process, assuming that the data type of the unencrypted data is detected to be MySQL data, first query whether there is a data access parameter corresponding to the MySQL data, and if there is a data access parameter corresponding to the MySQL data, obtain the data access parameter corresponding to the MySQL data, and obtain the data encryption algorithm of the data access parameter. The data access parameter corresponding to the MySQL data is used for accessing the unencrypted data, and the data encryption algorithm of the data access parameter is used for data encryption of the unencrypted data.

[0063] In summary, steps S1101 to S1103 can ensure that unencrypted data selects a reasonable data access method and encryption method according to its data type, so as to ensure the data security and accuracy of the data transmission process.

[0064] Regarding step S120, in some embodiments of the present disclosure, it may also include the following Figure 4 Steps S1201 to S1202 are shown.

[0065] S1201. Query multiple verification tasks corresponding to encrypted data, each verification task is used to verify data of a business type.

[0066] The encrypted data is obtained by encrypting the unencrypted data, and the unencrypted data is a series of data in a business scenario. If the business scenario corresponding to the unencrypted data includes multiple business links, and each business link has its own corresponding business rules, then when verifying the unencrypted data, each business rule has its own corresponding verification task.

[0067] For example, the unencrypted data is the fee payment data in a fee payment business scenario of a certain product. The fee payment business scenario of the product includes the deposit payment link, the final payment link, and the service fee payment link. Each of the above business links has its own corresponding business rules. When verifying the unencrypted data, it is necessary to verify the relevant data of the deposit payment link according to the business rules of the deposit payment link, verify the relevant data of the final payment link according to the business rules of the final payment link, and verify the relevant data of the service fee payment link according to the business rules of the service fee payment link. In this way, the data verification of the unencrypted data can be divided into three verification tasks, which are used to verify the relevant data of the deposit payment link, the final payment link, and the service fee payment link.

[0068] In one example, a plurality of verification tasks are stored in the rule base, each verification task corresponds to a business type, and each business type includes at least one business rule. Querying the plurality of verification tasks corresponding to the encrypted data includes obtaining the business rules included in each of the various business types in the business scenario corresponding to the encrypted data, and querying the verification tasks corresponding to each business type, to obtain the plurality of verification tasks corresponding to the encrypted data. Among them, the business scenario of the encrypted data and the business type in the business scenario can be obtained from the access source of the unencrypted data corresponding to the encrypted data. For example, the access source of the unencrypted data corresponding to the encrypted data is the fee payment system, and the business scenario of the fee payment system is the fee payment scenario, including the three business types of the deposit payment link, the final payment link, and the service fee payment link. The above three business types each include corresponding business rules, so that the business rules corresponding to the encrypted data are the business rules included in the three business types of the deposit payment link, the final payment link, and the service fee payment link, so as to query the corresponding verification tasks in the rule base according to the above business rules, and obtain the plurality of verification tasks corresponding to the encrypted data.

[0069] S1202, separating the encrypted data into a plurality of encrypted sub-data, each encrypted sub-data corresponding to a verification task.

[0070] For example, if the encrypted data includes the deposit payment amount, the balance payment amount, and the service fee payment amount, and the multiple verification tasks corresponding to the encrypted data include the deposit verification task, the balance verification task, and the service fee verification task, the encrypted data is separated into three encrypted sub-data: deposit payment data, balance payment data, and service fee payment data. Among them, the deposit payment data includes the deposit payment amount, corresponding to the deposit verification task; the balance payment data includes the balance payment amount, corresponding to the balance verification task; and the service fee payment data includes the service fee payment amount, corresponding to the service fee verification task.

[0071] In summary, steps S1201 to S1202 can separate the encrypted data into a corresponding number of multiple encrypted sub-data according to the number of verification tasks corresponding to the encrypted data, and each encrypted sub-data corresponds to a verification task. In this way, each verification task can be configured to verify the encrypted sub-data in the encrypted data in a customized manner, and only grant it access rights to the encrypted sub-data, thereby ensuring the security and accuracy of data verification.

[0072] In some embodiments of the present disclosure, the associated data associated with the encrypted sub-data is configured as: data that has a business association with the encrypted sub-data. Business association means that the application scenarios of the data are associated.

[0073] For example, the encrypted sub-data includes service fee data generated by a transaction. However, the service fee data generated by a single transaction cannot reflect the correctness of the data. It needs to be compared with the service fee data of other transaction parameters of the same product, and combined with data related to the charging standard of the service fee, the charging time interval, the charging location and other data to verify whether the service fee data generated by a single transaction is correct. Therefore, in step S130, it is necessary to obtain associated data that is business-related to the encrypted sub-data, and generate an intermediate data set for the encrypted sub-data and the associated data, so that the intermediate data set can be used to perform the verification task in the subsequent step S140 to verify whether the encrypted sub-data is correct.

[0074] Regarding step S140, in some embodiments of the present disclosure, it may also include the following Figure 5 Steps S1401 to S1402 are shown.

[0075] S1401. Obtain initial verification rules corresponding to unencrypted data, where the initial verification rules include multiple verification tasks, each of which is used to verify data having a specific field.

[0076] In one example, a rule base stores multiple verification rules, each of which is used to verify data in a business scenario. The initial verification rules corresponding to unencrypted data are used to verify data in the business scenario corresponding to the unencrypted data. When the business scenario corresponding to the unencrypted data includes multiple business links, each of which has its own business rules, the initial verification rules corresponding to the unencrypted data include multiple verification tasks, each of which is used to verify data in a business link. Among them, the data in different business links have different specific fields, that is, each verification task is used to verify data with a specific field.

[0077] S1402. Match the verification task corresponding to the same specific field according to the specific field of the encrypted sub-data to obtain the verification task corresponding to the encrypted sub-data.

[0078] For example, the unencrypted data is dispatch data, including first-hand house dispatch data and second-hand house dispatch data. Among them, "first-hand house" and "second-hand house" are configured as specific fields. There are verification rules for dispatch business in the rule base. The verification rules for dispatch business are the initial verification rules corresponding to the dispatch data. The verification rules for dispatch business include the first verification task and the second verification task. The first verification task is used to verify the data with the "first-hand house" field, and the second verification task is used to verify the data with the "second-hand house" field. After the unencrypted data is processed by data encryption and data separation, two encrypted sub-data are obtained, namely, first-hand house dispatch data and second-hand house dispatch data, wherein the first-hand house dispatch data has the "first-hand house" field, which corresponds to the same specific field as the first verification task, and the verification task corresponding to the first-hand house dispatch data is matched to the first verification task. Similarly, the second-hand house dispatch data has the "second-hand house" field, which corresponds to the same specific field as the second verification task, and the verification task corresponding to the second-hand house dispatch data is matched to the second verification task.

[0079] In summary, step S1401 to step S1402 can map the encrypted sub-data to the corresponding verification task, which can improve the accuracy of data verification and the execution efficiency of the verification task.

[0080] Regarding step S140, in some embodiments of the present disclosure, it may also include the following Figure 6 Steps S1403 to S1406 are shown.

[0081] S1403. Use the encrypted sub-data in the intermediate data set to execute the verification task and obtain a first execution result.

[0082] S1404: Use the associated data in the intermediate data set to execute the verification task and obtain a second execution result.

[0083] S1405. Perform data verification on the first execution result through the second execution result to obtain a verification result.

[0084] Among them, data verification includes at least one of data format verification, data integrity verification, data consistency verification, and rule logic verification. The content of the verification task corresponds to the type of data verification. The verification result is used to characterize whether the data is correct or not.

[0085] For example, in the case where the data verification is data format verification, the verification task is a data format verification task, and the execution result obtained by executing the data format verification task with data indicates whether the data has a specific format. Assuming that the first execution result indicates that the encrypted sub-data has a specific format, and the second execution result indicates that the associated data has a specific format, then the verification result obtained by performing data verification on the first execution result through the second execution result indicates that the data format of the encrypted sub-data is correct, otherwise the data format is abnormal.

[0086] For example, when the data verification is data integrity verification, the verification task is a data integrity verification task, and the execution result obtained by executing the data integrity verification task with data represents the number of required fields in the data. Assuming that the first execution result represents that the encrypted sub-data has a required fields, and the second execution result represents that the associated data has b required fields, and a=b, then the verification result obtained by performing data verification on the first execution result through the second execution result represents that the data integrity of the encrypted sub-data is correct, otherwise the data integrity is abnormal.

[0087] For example, in the case where the data verification is data consistency verification, the verification task is a data consistency verification task, and the execution result obtained by executing the data consistency verification task using the data is the identity identification code of the data. Assuming that the identity identification code of the encrypted sub-data represented by the first execution result is the first ID, and the identity identification code of the associated data represented by the second execution result is the second ID, and the first ID is the same as the second ID, then the verification result obtained by performing data verification on the first execution result through the second execution result represents that the data consistency of the encrypted sub-data is correct, otherwise the data consistency is abnormal.

[0088] For example, when data verification is data logic verification, the verification task is a data logic verification task, and the execution result obtained by executing the data logic verification task with data is the value of the data. Assuming that the encrypted sub-data is dispatch data, and the associated data is bill data, the first execution result represents the value of the encrypted sub-data, and the second execution result represents the value of the associated data, then data verification is to verify whether the first execution result is equal to the second execution result. If they are equal, it means that the dispatch quantity is consistent with the bill quantity, which complies with the business logic. The verification result represents that the data logic is correct, otherwise it is a data logic anomaly.

[0089] S1406. Obtain a verification mark corresponding to the verification result, and add the verification mark to the encrypted sub-data to obtain the verified sub-data.

[0090] Among them, the verification mark is used to indicate whether the data is correct. For example, the verification mark includes a first mark and a second mark, the first mark indicates that the data is correct, and the second mark indicates that the data is abnormal. When the verification result is that the data is correct, corresponding to the first mark, the first mark is added to the encrypted sub-data to obtain the verified sub-data; when the verification result is that the data is abnormal, corresponding to the second mark, the second mark is added to the encrypted sub-data to obtain the verified sub-data. In this way, according to the verification mark of the verified sub-data, it is possible to determine whether the verified sub-data is correct data, so as to intuitively obtain whether the encrypted sub-data is correct data. In addition, by screening the verified sub-data with the first mark, all correct verified sub-data can be screened out, which is convenient for data management.

[0091] Regarding step S140, in some embodiments of the present disclosure, it may also include the following Figure 7 Steps S1403 to S1407 are shown. Steps S1403 to S1406 have been introduced above and will not be described again.

[0092] S1407. Map the verification mark of the verified sub-data to the verification result of the encrypted sub-data.

[0093] In step S1403 to step S1406, the encrypted sub-data is verified, and the output obtained is the verified sub-data. The verified sub-data can be applied to the business scenario where the corresponding encrypted sub-data is applied. For example, a certain encrypted sub-data is a dispatch data of a certain commodity, which is applied to the dispatch quantity statistics of the dispatch business scenario. The verified sub-data obtained after data verification is the dispatch data with a verification mark, and the dispatch data with a verification mark can replace its corresponding encrypted sub-data and be applied to the dispatch quantity statistics of the dispatch business scenario. In other words, there is basically no difference between the encrypted sub-data before verification and the verified sub-data after verification. The main difference is that the verified sub-data has a verification mark, and the verification mark can be screened to selectively filter out correct or abnormal data for application.

[0094] In step S1407, the verification mark of the verified sub-data is mapped to the verification result of the encrypted sub-data, and the verification result is used to characterize the correctness of the encrypted sub-data. In this way, the obtained verification result is convenient for intuitively showing whether the encrypted sub-data is correct data. For example, the verification mark includes a first mark and a second mark, the first mark characterizes that the data is correct, and the second mark characterizes that the data is abnormal. If the verification mark of the verified sub-data is the first mark, the first mark is mapped to the first verification result, characterizing that the encrypted sub-data is correct data; otherwise, if the verification mark of the verified sub-data is the second mark, the second mark is mapped to the second verification result, characterizing that the encrypted sub-data is abnormal data.

[0095] In some embodiments of the present disclosure, the data processing method M100 further includes: Figure 8 Steps S150 to S170 are shown.

[0096] S150, filter out verified sub-data with abnormal marks to obtain abnormal sub-data.

[0097] The abnormal sub-data are verified sub-data with abnormal marks.

[0098] S160: Acquire initial sub-data corresponding to the abnormal sub-data in the unencrypted data.

[0099] The initial sub-data is the part of the data corresponding to the encrypted sub-data in the unencrypted data, and the abnormal sub-data corresponds to the encrypted sub-data before data verification. The initial sub-data corresponding to the abnormal sub-data is the initial sub-data corresponding to the same encrypted sub-data as the abnormal sub-data. In other words, the abnormal sub-data is equivalent to the data whose verification result is abnormal after the initial sub-data is encrypted and verified.

[0100] S170 . In response to a search instruction of the object field, display the initial sub-data having the object field and abnormal sub-data corresponding to the initial sub-data having the object field.

[0101] Among them, the object field is a filter item for filtering data. Displaying the initial sub-data with the object field and the abnormal sub-data corresponding to the initial sub-data with the object field can display the abnormal results in the verification results of the initial sub-data while displaying the initial sub-data with the object field. For example, if the object field entered by the user is "second-hand housing", all initial sub-data containing the field "second-hand housing" will be returned and displayed. If the returned initial sub-data has no corresponding abnormal sub-data, it will be displayed in black font. If the returned initial sub-data has corresponding abnormal sub-data, the initial sub-data will be displayed in black font and its corresponding abnormal sub-data will be displayed in red font. In this way, the abnormal sub-data can be intuitively traced back to the initial sub-data corresponding to it before the data verification.

[0102] Based on any of the above implementations, the present disclosure also provides a data processing device. Fig. 9 is a schematic diagram of a data processing device according to one embodiment of the present disclosure.

[0103] like Fig. 9 As shown, the data processing device includes: The data encryption module 110 is used to encrypt unencrypted data to obtain encrypted data.

[0104] The data separation module 120 is used to separate the encrypted data to obtain a plurality of encrypted sub-data, each of which corresponds to a service type.

[0105] The data association module 130 is used to obtain the associated data associated with the encrypted sub-data and generate an intermediate data set, wherein the intermediate data set includes an encrypted sub-data and the associated data associated with the encrypted sub-data.

[0106] The data verification module 140 is used to match the verification task corresponding to the encrypted sub-data and use the intermediate data set to perform the verification task to obtain the verified sub-data.

[0107] Each of the above modules can be implemented by a computer program module. Fig. 9 The data processing apparatus shown may be implemented based on a computer program module architecture.

[0108] In some embodiments of the present disclosure, the data encryption module 110 is used to obtain corresponding data access parameters according to the data type of unencrypted data; match the data encryption algorithm corresponding to the data access parameters; and use the matched data encryption algorithm to encrypt the unencrypted data, and use the data access parameters to access the encrypted data to obtain encrypted data.

[0109] In some embodiments of the present disclosure, the data separation module 120 is used to query multiple verification tasks corresponding to the encrypted data, each verification task is used to verify data of a business type; and to separate the encrypted data into multiple encrypted sub-data, each encrypted sub-data corresponding to a verification task.

[0110] In some embodiments of the present disclosure, the data verification module 140 is used to obtain initial verification rules corresponding to unencrypted data, where the initial verification rules include multiple verification tasks, each verification task is used to verify data having a specific field; and the verification task corresponding to the same specific field is matched according to the specific field of the encrypted sub-data to obtain the verification task corresponding to the encrypted sub-data.

[0111] In some embodiments of the present disclosure, the data verification module 140 is also used to use the encrypted sub-data in the intermediate data set to perform a verification task to obtain a first execution result; use the associated data in the intermediate data set to perform a verification task to obtain a second execution result; perform data verification on the first execution result through the second execution result to obtain a verification result; and obtain a verification mark corresponding to the verification result, and add a verification mark to the encrypted sub-data to obtain verified sub-data; wherein data verification includes at least one of data format verification, data integrity verification, data consistency verification, and rule logic verification.

[0112] In some embodiments of the present disclosure, the data verification module 140 is further configured to map the verification mark of the verified sub-data to the verification result of the encrypted sub-data.

[0113] In some embodiments of the present disclosure, the data processing device also includes a data display module 150, which is used to screen out verified sub-data with abnormal marks to obtain abnormal sub-data; obtain initial sub-data corresponding to the abnormal sub-data in the unencrypted data; and; in response to a search instruction for an object field, display the initial sub-data with the object field and the abnormal sub-data corresponding to the initial sub-data with the object field.

[0114] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.

[0115] The execution subject of the data processing method in the specific implementation manner of the present disclosure may be an electronic device such as a mobile phone, a tablet computer, or a server.

[0116] Therefore, based on any of the above embodiments, the present disclosure further provides an electronic device, which can execute the data processing method of any of the above embodiments of the present disclosure, and the data processing device of any of the above embodiments can be configured on the electronic device.

[0117] Fig.10 1 is a schematic block diagram of the structure of an electronic device 1000 equipped with a data processing device according to an embodiment of the present disclosure.

[0118] The hardware structure of the electronic device 1000 can be implemented using a bus architecture. The bus architecture can include any number of interconnected buses and bridges, depending on the specific application and overall design constraints of the hardware. The bus 1100 connects various circuits including one or more processors 1200, memory 1300 and / or hardware modules together. The bus 1100 can also connect various other circuits 1400 such as peripherals, voltage regulators, power management circuits, external antennas, etc.

[0119] The bus 1100 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Component (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the figure only uses one connecting line, but does not mean that there is only one bus or one type of bus.

[0120] The present disclosure also provides a readable storage medium, in which a computer program is stored, and the computer program is used to implement the above method when executed by a processor. "Readable storage medium" can be any device that can contain, store, communicate, propagate or transmit a program for use in an instruction execution system, device or equipment or in combination with these instruction execution systems, devices or equipment. More specific examples of readable storage media include the following: an electrical connection portion (electronic device) with one or more wirings, a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and editable read-only memory (EPROM or flash memory), an optical fiber device, and a portable read-only memory (CDROM), etc.

[0121] The present disclosure also provides a computer program product. The method of the present disclosure can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed, the process or function of the present disclosure is executed in whole or in part.

[0122] A computer program or instruction may be stored in a readable storage medium or transmitted from one readable storage medium to another readable storage medium, for example, a computer program or instruction may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The readable storage medium may be any available medium that can be accessed or a data storage device such as a server, data center, etc. that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; it may also be a semiconductor medium, such as a solid state drive. The computer readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0123] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0124] The present disclosure is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0125] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0126] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0127] In the description of this specification, the description with reference to the terms "one embodiment / method", "some embodiments / methods", "example", "specific example", or "some examples" etc. means that the specific features, structures, or characteristics described in conjunction with the embodiment / method or example are included in at least one embodiment / method or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment / method or example. Moreover, the specific features, structures, or characteristics described may be combined in any one or more embodiments / methods or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments / methods or examples described in this specification and features of different embodiments / methods or examples, unless they are contradictory.

[0128] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of the present disclosure, "plurality" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0129] Those skilled in the art should understand that the above embodiments are only for the purpose of clearly illustrating the present disclosure, and are not intended to limit the scope of the present disclosure. For those skilled in the art, other changes or modifications may be made based on the above disclosure, and these changes or modifications are still within the scope of the present disclosure.

Claims

1. A data processing method, characterized in that: include: Encrypting the unencrypted data to obtain encrypted data; Separating the encrypted data to obtain a plurality of encrypted sub-data, each of which corresponds to a service type; Acquire associated data associated with the encrypted sub-data, and generate an intermediate data set, wherein the intermediate data set includes the encrypted sub-data and the associated data associated with the encrypted sub-data; as well as Match the verification task corresponding to the encrypted sub-data, and use the intermediate data set to execute the verification task to obtain the verified sub-data.

2. The data processing method according to claim 1, characterized in that: The unencrypted data is encrypted to obtain encrypted data, including: Acquire corresponding data access parameters according to the data type of the unencrypted data; Matching the data encryption algorithm corresponding to the data access parameter; and The unencrypted data is encrypted using the matched data encryption algorithm, and the encrypted data is accessed using the data access parameter to obtain the encrypted data.

3. The data processing method according to claim 1, characterized in that: The encrypted data is separated to obtain a plurality of encrypted sub-data, each of which corresponds to a service type, including: querying a plurality of verification tasks corresponding to the encrypted data, each of the verification tasks being used to verify data of a business type; and The encrypted data is separated into a plurality of encrypted sub-data, each of which corresponds to one verification task.

4. The data processing method according to claim 1, characterized in that: The associated data associated with the encrypted sub-data is configured as: data that is business-associated with the encrypted sub-data.

5. The data processing method according to claim 1, characterized in that: Matching the verification task corresponding to the encrypted sub-data includes: Acquire an initial verification rule corresponding to the unencrypted data, the initial verification rule comprising a plurality of verification tasks, each of the verification tasks being used to verify data having a specific field; and The verification task corresponding to the encrypted sub-data is obtained by matching the verification task corresponding to the same specific field according to the specific field of the encrypted sub-data.

6. The data processing method according to claim 1, characterized in that: The verification task is performed using the intermediate data set to obtain verified sub-data, including: Using the encrypted sub-data in the intermediate data set to execute the verification task, and obtaining a first execution result; Using the associated data in the intermediate data set to execute the verification task, to obtain a second execution result; Performing data verification on the first execution result using the second execution result to obtain a verification result; and Obtaining a verification mark corresponding to the verification result, and adding the verification mark to the encrypted sub-data to obtain the verified sub-data; Wherein, the data verification includes at least one of data format verification, data integrity verification, data consistency verification, and rule logic verification; Optionally, the data processing method further includes: The verification mark of the verified sub-data is mapped to the verification result of the encrypted sub-data.

7. The data processing method according to claim 1, characterized in that: The number of the verified sub-data is multiple, the verified sub-data has a verification mark, and the verification mark includes an abnormal mark; the data processing method further includes: Screening out the verified sub-data with abnormal marks to obtain abnormal sub-data; Acquiring initial sub-data corresponding to the abnormal sub-data in the unencrypted data; and; In response to a search instruction of an object field, initial sub-data having the object field and the abnormal sub-data corresponding to the initial sub-data having the object field are displayed.

8. An electronic device, characterized in that: include: A memory storing execution instructions; as well as A processor, wherein the processor executes the execution instruction stored in the memory, so that the processor executes the data processing method according to any one of claims 1 to 7.

9. A readable storage medium, characterized in that: The readable storage medium stores execution instructions, which are used to implement the data processing method according to any one of claims 1 to 7 when executed by a processor.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the data processing method according to any one of claims 1 to 7 is implemented.

Images