Data processing method and device, equipment and medium

Abstract

The embodiment of the invention discloses a data processing method and device, equipment and a medium. The method comprises the steps of obtaining current update data and a corresponding current update field, and determining a current entity type of a current entity class where the current update field is located based on a preset target encryption relation tree; if the current entity type is a semi-configuration type, determining whether fuzzy matching exists in the current update field; if yes, determining an update shadow field of the current update field, and determining update standby data of the current update data; obtaining encrypted update data based on a preset basic encryption mode, and obtaining encrypted standby data based on the target encryption relation tree; and storing the encrypted update data and the encrypted standby data into a current data table corresponding to the current entity class in a database. The security of the data in the database is improved, and the requirement of personalized data encryption storage is met.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of data processing technology, and in particular, to a data processing method, device, equipment and medium. Background Art

[0002] Digital systems are becoming more and more important for modern offices, but there is a risk of information data leakage in the database due to the lack of digital system security protection. Therefore, it is crucial to improve the data security in the database. Summary of the invention

[0003] The present invention provides a data processing method, device, equipment and medium to improve the security of data in a database.

[0004] According to one aspect of the present invention, there is provided a data processing method, comprising:

[0005] Acquire current update data and corresponding current update fields, and determine the current entity type of the current entity class where the current update field is located based on a preset target encryption relationship tree; wherein the target encryption relationship tree is determined based on the data to be encrypted determined from the candidate entity class and / or the candidate processing method, and a preset configuration type determination strategy;

[0006] If the current entity type is a semi-configured type, determining whether there is a fuzzy match in the current update field;

[0007] If it exists, determining the updated shadow field of the current updated field, and determining the updated standby data of the current updated data;

[0008] Encrypting the current update data under the current update field based on a preset basic encryption method to obtain encrypted update data, and encrypting the update standby data under the update shadow field based on the target encryption relationship tree to obtain encrypted standby data;

[0009] The encrypted update data and the encrypted standby data are stored in a current data table corresponding to the current entity class in a database.

[0010] According to another aspect of the present invention, there is provided a data processing device, comprising:

[0011] A current entity type determination module, used to obtain current update data and corresponding current update fields, and determine the current entity type of the current entity class where the current update field is located based on a preset target encryption relationship tree; wherein the target encryption relationship tree is determined based on the data to be encrypted determined from the candidate entity class and / or the candidate processing method, and a preset configuration type determination strategy;

[0012] A fuzzy matching judgment module, used to determine whether there is a fuzzy match in the current update field if the current entity type is a semi-configuration type;

[0013] A shadow field determination module, configured to determine an updated shadow field of the current updated field, if any, and to determine updated standby data of the current updated data;

[0014] A data encryption module, configured to encrypt the current update data under the current update field based on a preset basic encryption method to obtain encrypted update data, and to encrypt the update standby data under the update shadow field based on the target encryption relationship tree to obtain encrypted standby data;

[0015] The data storage module is used to store the encrypted update data and the encrypted standby data in a current data table corresponding to the current entity class in a database.

[0016] According to another aspect of the present invention, there is provided an electronic device, comprising:

[0017] one or more processors;

[0018] A memory for storing one or more programs;

[0019] When one or more programs are executed by one or more processors, the one or more processors can execute any data processing method provided by the embodiments of the present invention.

[0020] According to another aspect of the present invention, a computer-readable storage medium is provided, which stores computer instructions, and the computer instructions are used to enable a processor to implement any data processing method provided by the embodiments of the present invention when executed.

[0021] An embodiment of the present invention provides a data processing solution, which obtains current update data and corresponding current update fields, and determines the current entity type of the current entity class where the current update field is located based on a preset target encryption relationship tree; wherein the target encryption relationship tree is determined based on the data to be encrypted determined from the candidate entity class and / or the candidate processing method, and a preset configuration type determination strategy; if the current entity type is a semi-configuration type, it is determined whether there is a fuzzy match in the current update field; if so, the update shadow field of the current update field is determined, and the update standby data of the current update data is determined; based on a preset basic encryption method, the current update data under the current update field is encrypted to obtain encrypted update data, and based on the target encryption relationship tree, the update standby data under the update shadow field is encrypted to obtain encrypted standby data; the encrypted update data and the encrypted standby data are stored in the current data table corresponding to the current entity class in the database. The above scheme introduces a target encrypted relationship tree. When the current entity class is a semi-configured type, it determines the updated shadow field of the current updated field and the updated backup data of the current updated data. It uses a preset basic encryption method to encrypt the current updated data under the current updated field. At the same time, it uses the target encrypted relationship tree to encrypt the updated backup data under the updated shadow field. This achieves encrypted storage of the current updated data under the current updated field and customized encrypted storage of the backup data under the shadow field without changing the original code, thereby improving the security of data in the database and meeting the needs of personalized data encryption storage.

[0022] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 is a flow chart of a data processing method provided by Embodiment 1 of the present invention;

[0025] Figure 2 is a flow chart of a data processing method provided by Embodiment 2 of the present invention;

[0026] Figure 3 is a structural diagram of a data processing device provided by Embodiment 4 of the present invention;

[0027] Figure 4 It is a structural schematic diagram of an electronic device for implementing a data processing method provided in Embodiment 5 of the present invention. DETAILED DESCRIPTION

[0028] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0029] Embodiment 1

[0030] Figure 1 It is a flow chart of a data processing method provided in the first embodiment of the present invention. This embodiment can be applied to the case of encrypting data stored in a database. The method can be executed by a data processing device, which can be implemented in software and / or hardware and can be configured in an electronic device that carries the data processing function.

[0031] See also Figure 1 The data processing method shown comprises:

[0032] S110, obtaining current update data and corresponding current update fields, and determining the current entity type of the current entity class where the current update field is located based on a preset target encrypted relationship tree.

[0033] The current update data refers to the data that needs to be added or modified in the database at the current moment. The current update field can be used to store the current update data. Exemplarily, the current update field can be a name, and the current update data can be a specific value of the name, such as Ab12.

[0034] Among them, the target encrypted relationship tree can be used to record the entity classes, methods and fields that need to be encrypted in the program, the corresponding encryption methods, and the configuration types of the entity classes. The aforementioned program can be understood as a business program for data storage, query and modification services between the application system and the database. The current entity class refers to the reference entity class associated with the current update field recorded in the target encrypted relationship tree. The current entity type refers to the configuration type of the entity class where the current update field recorded in the target encrypted relationship tree is located.

[0035] Exemplarily, the target encryption relationship tree is determined based on the data to be encrypted determined from the candidate entity class and / or the candidate processing method, and the preset configuration type determination strategy. Among them, the candidate entity class refers to the entity class preset in the program. The candidate processing method refers to the method preset in the program. The data to be encrypted refers to the data that needs to be encrypted in the program. Exemplarily, the data to be encrypted may include the entity class to be encrypted and / or the processing method to be encrypted.

[0036] Specifically, the current update data and the current update field are obtained, and the reference entity class associated with the current update field in the target encrypted relationship tree is used as the current entity class, and the reference configuration type marked by the current entity class is used as the current entity type.

[0037] S120: If the current entity type is a semi-configured type, determine whether there is a fuzzy match in the current update field.

[0038] Among them, the semi-configured type refers to the type that can be configured with a custom encryption method. Fuzzy matching refers to similar matching. For example, if the current update field is a name, judging whether there is a fuzzy match means matching through the part of the value corresponding to the name, that is, if the value corresponding to the name is Ab12, fuzzy matching means matching through Ab.

[0039] S130. If it exists, determine the update shadow field of the current update field, and determine the update standby data of the current update data.

[0040] Among them, the update shadow field refers to the spare field of the current update field. It should be noted that the update shadow field and the current update field can be the same or different, and the embodiment of the present invention does not specifically limit this. It should be noted that a preset distinguisher can be added to the update shadow field to distinguish the update shadow field from the current update field, so as to facilitate the removal of the update shadow field after subsequent use. The embodiment of the present invention does not impose any limitation on the preset distinguisher, which can be set by the technician according to experience or needs. For example, if the current update field is a name, the update shadow field can be name a. Update spare data refers to data that is exactly the same as the current update data.

[0041] Specifically, if a fuzzy match exists in the current update field, an update shadow field of the current update field is added, and the current update data is copied to obtain updated standby data.

[0042] S140. Encrypt the current update data under the current update field based on a preset basic encryption method to obtain encrypted update data, and encrypt the update standby data under the update shadow field based on a target encryption relationship tree to obtain encrypted standby data.

[0043] The preset basic encryption method refers to a preset method for encrypting the data under the current update field. The encrypted update data refers to the data obtained by encrypting the current update data based on the preset basic encryption method. The encrypted standby data refers to the encrypted standby data obtained by encrypting the update standby data based on the target encryption method in the target encryption relationship tree.

[0044] Specifically, based on the preset basic encryption method, the current update data under the current update field is encrypted to obtain encrypted update data; based on the target encryption method in the target encryption relationship tree, the update standby data under the update shadow field is encrypted to obtain encrypted standby data.

[0045] In an optional embodiment, based on the target encryption relationship tree, the updated standby data under the update shadow field is encrypted to obtain encrypted standby data, including: determining the target encryption method of the current updated data from the target encryption relationship tree, and encrypting the updated standby data under the update shadow field according to the target encryption method to obtain encrypted standby data.

[0046] The target encryption method refers to a method for performing custom encryption on the data under the current update field marked in the target encryption relationship tree.

[0047] Specifically, the candidate encryption method marked at the current update field in the target encryption relationship tree is used as the target encryption method, and the update standby data under the update shadow field is encrypted according to the target encryption method to obtain encrypted standby data.

[0048] It can be understood that by determining the target encryption method from the target encryption relationship tree, and encrypting the updated backup data under the updated shadow field based on the target encryption method, the encrypted backup data is obtained, thereby achieving personalized encryption of the data without changing the original program code, thereby meeting the needs of personalized encrypted storage of data.

[0049] It should be noted that the preset basic encryption method refers to a method of encrypting the current update data under the current update field that is pre-configured during the program design process; the target encryption method refers to a method of customizing the encryption of the current update data under the current update field that is marked in the target encryption relationship tree based on business needs.

[0050] S150. Store the encrypted update data and the encrypted standby data in the current data table corresponding to the current entity class in the database.

[0051] The database can be used for data storage, data query and data update. The embodiment of the present invention does not specifically limit the type of database, which can be set by technicians based on experience. The current data table refers to the data table corresponding to the current entity class in the database.

[0052] In an optional embodiment, storing encrypted update data and encrypted backup data in a current data table corresponding to a current entity class in a database includes: determining the current data table corresponding to the current entity class in the database; storing the encrypted update data under the corresponding update primary field in the current data table, and storing the encrypted backup data under the corresponding shadow primary field in the current data table.

[0053] Among them, the update main field refers to the field in the current data table that is the same as the current update field. The shadow main field refers to the field in the current data table that is the same as the update shadow field. It should be noted that the shadow main field is the shadow field of the update main field.

[0054] It can be understood that the encrypted update data is stored under the updated main field of the current data table, and the encrypted backup data is stored under the corresponding shadow main field in the current data table. This realizes the storage of the encrypted backup data obtained by custom encryption in the database without changing the original encrypted update data, thereby improving the convenience of subsequent use of data in the database.

[0055] An embodiment of the present invention provides a data processing solution, which obtains current update data and corresponding current update fields, and determines the current entity type of the current entity class where the current update field is located based on a preset target encryption relationship tree; wherein the target encryption relationship tree is determined based on the data to be encrypted determined from the candidate entity class and / or the candidate processing method, and a preset configuration type determination strategy; if the current entity type is a semi-configuration type, it is determined whether there is a fuzzy match in the current update field; if so, the update shadow field of the current update field is determined, and the update standby data of the current update data is determined; based on a preset basic encryption method, the current update data under the current update field is encrypted to obtain encrypted update data, and based on the target encryption relationship tree, the update standby data under the update shadow field is encrypted to obtain encrypted standby data; the encrypted update data and the encrypted standby data are stored in the current data table corresponding to the current entity class in the database. The above scheme introduces a target encrypted relationship tree. When the current entity class is a semi-configured type, it determines the updated shadow field of the current updated field and the updated backup data of the current updated data. It uses a preset basic encryption method to encrypt the current updated data under the current updated field. At the same time, it uses the target encrypted relationship tree to encrypt the updated backup data under the updated shadow field. This achieves encrypted storage of the current updated data under the current updated field and customized encrypted storage of the backup data under the shadow field without changing the original code, thereby improving the security of data in the database and meeting the needs of personalized data encryption storage.

[0056] Based on the above technical solution, the method also includes: if the current entity type is a full configuration type, encrypting the current update data based on a preset basic encryption method to obtain encrypted update data; storing the encrypted update data in the corresponding update main field in the current data table.

[0057] The full configuration type is a type that prohibits custom encryption method configuration.

[0058] Specifically, if the current entity type is a full configuration type, the current update data is directly encrypted based on a preset basic encryption method to obtain encrypted update data; the encrypted update data is stored in the corresponding update main field in the current data table.

[0059] It can be understood that, in the case of the full configuration type, the current update data is directly encrypted based on the preset basic encryption method, the encrypted update data is obtained and stored in the database, which improves the applicability of data encryption storage.

[0060] Based on the above technical solution, the method also includes: obtaining the current query data and the current query field, and determining the query entity type of the query entity class where the current query field is located based on a preset target encrypted relationship tree; if the query entity type is a semi-configured type, determining the query shadow field of the current query field, and determining the query backup data of the current query data; obtaining the current query result from the database based on the query backup data under the query shadow field.

[0061] Among them, the current query data refers to the data that needs to be retrieved in the database at the current moment. The current query field can be used to store the current query data. The query entity class refers to the reference entity class associated with the current query field recorded in the target encrypted relationship tree. The query entity type refers to the configuration type of the entity class where the current query field recorded in the target encrypted relationship tree is located.

[0062] The query shadow field refers to the backup field of the current query field. The query backup data refers to the data that is exactly the same as the current query data. The current query result refers to the result obtained based on the current query data.

[0063] It can be understood that by determining whether the query entity type is a semi-configuration type based on the target encrypted relationship tree, if so, a query shadow field is added to the current query field, and the current query data is copied to obtain query backup data. According to the query backup data under the query shadow field, the current query result is obtained from the database, thereby achieving the acquisition of the current query result from the database without changing the current query data and the current query field, thereby improving the accuracy of the current query data and the current query field.

[0064] Embodiment 2

[0065] Figure 2 It is a flow chart of a data processing method provided in the second embodiment of the present invention. Based on the above embodiments, this embodiment further adds the operation of "determining the candidate processing method associated with the service class to be processed, and based on the candidate processing method, determining the candidate entity class under the service class to be processed; determining the data to be encrypted from the candidate entity class and / or the candidate processing method according to business needs, and building a candidate encryption relationship tree according to the data to be encrypted; determining the reference configuration type of the reference entity class according to the reference fields, reference processing methods, and preset configuration type determination strategies under each reference entity class in the candidate encryption relationship tree; wherein the configuration type determination strategy includes an integer field determination strategy, a time field determination strategy, and a fuzzy matching determination strategy; updating the candidate encryption relationship tree according to the reference configuration type of each reference entity class to obtain a target encryption relationship tree" to improve the construction mechanism of the target encryption relationship tree. It should be noted that for the parts not described in detail in the embodiments of the present invention, please refer to the descriptions of other embodiments.

[0066] S210: Determine candidate processing methods associated with the service class to be processed, and based on the candidate processing methods, determine candidate entity classes under the service class to be processed.

[0067] The service class to be processed refers to a service class that can be used to construct a target encrypted relationship tree. The candidate processing method refers to a method associated with the service class to be processed. The candidate entity class refers to an entity class associated with the service class to be processed.

[0068] In an optional embodiment, candidate processing methods associated with the service class to be processed are determined, and based on the candidate processing methods, candidate entity classes under the service class to be processed are determined, including: obtaining the class path of the service class to be processed, and determining the candidate processing methods associated with the service class to be processed based on the class path; generating a method call relationship tree based on the candidate processing methods, and determining the candidate entity classes under the service class to be processed based on the method call relationship tree.

[0069] The class path can be used to locate the path of the file of the service class to be processed. The method call relationship tree can be used to record the call relationship between the candidate processing methods.

[0070] Specifically, by obtaining the class path of the service class to be processed, reading the content of the class path, and performing code decompilation, after the decompilation is completed, all candidate processing methods of the service class to be processed are extracted, and the code of the storage layer is called according to the content of the candidate processing method to form a method call relationship tree, and the candidate entity class associated with the orm framework is inferred according to the method call relationship tree.

[0071] It can be understood that by determining candidate processing methods based on the class path of the service class to be processed, generating a method call relationship tree, and determining candidate entity classes based on the method call relationship tree, the comprehensiveness of the determined candidate processing methods and candidate entity classes is improved, avoiding omissions.

[0072] S220: Determine the data to be encrypted from the candidate entity classes and / or candidate processing methods according to business requirements, and construct a candidate encryption relationship tree according to the data to be encrypted.

[0073] The business demand refers to the demand of the user to call the database through the application system. The data to be encrypted refers to the data that needs to be encrypted in the program. Exemplarily, the data to be encrypted may include the entity class to be encrypted and / or the encryption processing method to be encrypted.

[0074] The candidate encryption relationship tree can be used to record entity classes, methods and fields that need to be encrypted in the program, as well as the corresponding candidate encryption methods.

[0075] In an optional embodiment, if the data to be encrypted includes an entity class to be encrypted and a processing method to be encrypted, a candidate encryption relationship tree is constructed based on the data to be encrypted, including: taking the entity class to be encrypted as a reference actual entity class, and taking the candidate processing methods and candidate fields under the reference actual entity class as reference processing methods and reference fields under the reference actual entity class; taking the candidate entity class corresponding to the processing method to be encrypted as a reference virtual entity class for the processing method to be encrypted, and taking the processing method to be encrypted as a reference processing method under the reference virtual entity class, and taking the candidate field corresponding to the processing method to be encrypted as a reference field under the reference virtual entity class; constructing an initial encryption relationship tree based on the reference actual entity class, the reference processing method and reference field under the reference actual entity class, the reference virtual entity class, and the reference processing method and reference field under the reference virtual entity class; and marking each node in the initial encryption relationship tree with the candidate encryption method according to business needs to obtain a candidate encryption relationship tree.

[0076] The entity class to be encrypted refers to a candidate entity class that needs to be encrypted, and the processing method to be encrypted refers to a candidate processing method that needs to be encrypted.

[0077] Among them, referring to the actual entity class can represent directly encrypting the candidate entity class. Referring to the virtual entity class can represent encrypting at least one candidate processing method or candidate field under the candidate entity class. It should be noted that for the determined entity class to be encrypted, the representation is to encrypt all candidate processing methods and candidate fields under the entity class to be encrypted. At this time, the entity class to be encrypted is directly used as the reference actual entity class; for the determined processing method to be encrypted, the representation is to encrypt a certain candidate processing method. At this time, it is necessary to upgrade the scope and use the candidate entity class where the processing method to be encrypted is located as the reference virtual entity class.

[0078] The reference processing method refers to a candidate processing method that needs to be encrypted. The reference field refers to a candidate field that needs to be encrypted. The candidate field refers to a field that is preset in the program.

[0079] The initial encrypted relationship tree can be used to record entity classes, methods, and fields that need to be encrypted in the program. The candidate encryption method refers to the method for encrypting the entity classes, methods, and fields in the initial encrypted relationship tree. The embodiment of the present invention does not impose any restrictions on the setting of the candidate encryption method, which can be set by technicians based on experience or needs.

[0080] Specifically, an initial encrypted relationship tree is constructed based on the service class to be processed, the reference actual entity class, the reference processing method and reference field under the reference actual entity class, the reference virtual entity class, and the reference processing method and reference field under the reference virtual entity class.

[0081] It can be understood that by determining the reference actual entity class, the reference virtual entity class, and the corresponding reference processing method and reference field according to the entity class to be encrypted and the encryption processing method to be encrypted, and then constructing the initial encryption relationship tree, and then updating the initial encryption relationship tree by marking the candidate encryption method to obtain the candidate encryption relationship tree, thereby improving the accuracy of the constructed candidate encryption relationship tree.

[0082] S230: Determine the reference configuration type of the reference entity class according to the reference fields, reference processing methods, and preset configuration type determination strategies under each reference entity class in the candidate encrypted relationship tree.

[0083] The reference entity class refers to a candidate entity class that needs to be encrypted. Exemplarily, the reference entity class may include a reference actual entity class and / or a reference virtual entity class. The configuration type determination strategy may be used to determine the reference configuration type of each reference entity class in the candidate encryption relationship tree. The reference configuration type refers to the configuration type of the reference entity class.

[0084] Exemplarily, the configuration type determination strategy includes an integer field determination strategy, a time field determination strategy, and a fuzzy match determination strategy. Among them, the integer field determination strategy can be used to determine the corresponding reference configuration type according to the integer field under the reference entity class. The time field determination strategy can be used to determine the corresponding reference configuration type according to the time field under the reference entity class. The fuzzy match determination strategy can be used to determine the corresponding reference configuration type according to whether there is a fuzzy match under the reference entity class.

[0085] Optionally, the reference configuration type of the reference entity class is determined according to the configuration type determination strategy, including: for any reference entity class, judging whether there is a calculation function call for the reference field whose field type is an integer under the reference entity class, and if so, the reference configuration type of the reference entity class is characterized as a semi-configuration type. For example, if the integer reference field under the reference entity class is a name, judging whether there is a call to a calculation function such as statistics, size comparison, etc.; if so, the reference configuration type of the reference entity class is characterized as a semi-configuration type.

[0086] Or optionally, according to the configuration type determination strategy, the reference configuration type of the reference entity class is determined, including: for any reference entity class, judging whether there is an interval comparison of the reference field of the time field under the reference entity class, if so, then the reference configuration type of the reference entity class is characterized as a semi-configuration type. For example, if any reference field under the reference entity class is the production date, then judging whether there is an interval comparison greater than a certain time or less than a certain time, if so, then the reference configuration type of the reference entity class is characterized as a semi-configuration type.

[0087] Or optionally, a strategy is determined according to the configuration type to determine the reference configuration type of the reference entity class, including: for any reference entity class, judging whether there is a fuzzy match in the reference field under the reference entity class, and if so, the reference configuration type of the reference entity class is characterized as a semi-configuration type.

[0088] Or optionally, a strategy is determined according to the configuration type to determine the reference configuration type of the reference entity class, including: for any reference entity class, if there is no calculation function call for the reference field whose field type is an integer under the reference entity class, there is no interval comparison for the reference field that is a time field under the reference entity class, and there is no fuzzy match for the reference field under the reference entity class, then the reference entity class is characterized as a full configuration type.

[0089] S240. Update the candidate encrypted relationship tree according to the reference configuration type of each reference entity class to obtain a target encrypted relationship tree.

[0090] Specifically, the reference configuration type of each reference entity class in the candidate encrypted relationship tree is marked to obtain the target encrypted relationship tree.

[0091] It should be noted that each node in the target encrypted relationship tree is a service class to be processed, a reference entity class, a reference field and a reference processing method, and is marked with the corresponding candidate processing method and reference configuration type.

[0092] S250: Acquire current update data and corresponding current update fields, and determine the current entity type of the current entity class where the current update field is located based on a preset target encrypted relationship tree.

[0093] The target encryption relationship tree is determined based on the data to be encrypted determined from the candidate entity classes and / or candidate processing methods, and a preset configuration type determination strategy.

[0094] S260: If the current entity type is a semi-configured type, determine whether there is a fuzzy match in the current update field.

[0095] S270. If it exists, determine the update shadow field of the current update field, and determine the update standby data of the current update data.

[0096] S280. Encrypt the current update data under the current update field based on a preset basic encryption method to obtain encrypted update data, and encrypt the update standby data under the update shadow field based on the target encryption relationship tree to obtain encrypted standby data.

[0097] S290. Store the encrypted update data and the encrypted standby data in the current data table corresponding to the current entity class in the database.

[0098] An embodiment of the present invention provides a data processing solution, which determines the candidate processing method associated with the service class to be processed by adding, and based on the candidate processing method, determines the candidate entity class under the service class to be processed; according to business needs, determines the data to be encrypted from the candidate entity class and / or the candidate processing method, and constructs a candidate encryption relationship tree based on the data to be encrypted; determines the reference configuration type of the reference entity class according to the reference fields, reference processing methods, and preset configuration type determination strategies under each reference entity class in the candidate encryption relationship tree; wherein the configuration type determination strategy includes an integer field determination strategy, a time field determination strategy, and a fuzzy matching determination strategy; according to the reference configuration type of each reference entity class, updates the candidate encryption relationship tree to obtain a target encryption relationship tree operation, thereby improving the construction mechanism of the target encryption relationship tree. The above scheme determines the associated candidate processing methods and candidate entity classes based on the service class to be processed, and then determines the data to be encrypted from the candidate processing methods and candidate entity classes, and then constructs a candidate encryption relationship tree based on the data to be encrypted, thereby improving the comprehensiveness of the constructed candidate encryption relationship tree; at the same time, the strategy is determined according to the configuration type, and the candidate encryption relationship tree is updated to obtain the target encryption relationship tree, thereby supplementing the candidate encryption relationship tree and improving the comprehensiveness of the target encryption relationship tree.

[0099] Embodiment 3

[0100] The embodiment of the present invention provides an optional example based on the above embodiment. It should be noted that for the part not described in detail in the embodiment of the present invention, reference can be made to the description of other embodiments.

[0101] While digital systems bring convenience to daily office work, if digital systems lack security protection, there is a great risk of leakage of information data generated by digital systems. From the perspective of digital systems alone, the conventional practice is to store and encrypt data in the database. For some data, the encrypted data cannot be fuzzy matched, which affects the convenience of the business.

[0102] Exemplarily, by obtaining the class path of the service class to be processed, reading the content of the class path, and performing code decompilation, after the decompilation is completed, all candidate processing methods of the service class to be processed are extracted, and the code of the storage layer is called according to the content of the candidate processing method to form a method call relationship tree, and the candidate entity class associated with the orm framework is inferred according to the method call relationship tree, triggering the definition mechanism of the entity class, and after the definition is completed, the child node of the associated reference entity class is inserted into the root node of the service class to be processed, and the corresponding reference configuration type is marked. If it is a reference virtual entity class, determine whether the associated child node type is a method or a field. If it is a field, point-to-point judgment of the field and configuration type determination strategy is defined. If it is a method, according to the point-to-point extraction method content, it is processed according to the method logic of the service class.

[0103] For example, in the application system, construct the @JM annotation to annotate the candidate encryption methods. The annotation can specify the encryption method. When the technical personnel are developing business functions, they annotate the entity class or method according to the importance of the business demand data. At the same time, build the spring preprocessor. After the system is compiled and started, when spring is started, the spring preprocessor is automatically triggered to run; by scanning all the @JM annotated entity classes and methods in the current system, the metadata information of the annotated target object (that is, the data to be encrypted) is extracted and stored in the encrypted temporary storage. Listen to the startup event of the spring container. When the spring container is started, establish the target encryption relationship tree (JMT), iterate the encrypted temporary storage, and perform hierarchical processing on the metadata information of each encrypted annotated target object.

[0104] The spring preprocessor can be used to parse the marked candidate encryption methods. The encryption temporary storage can be used to store the class name of the entity class to be encrypted, the encryption processing method to be encrypted and the class name of the corresponding candidate entity class.

[0105] Exemplarily, firstly, the encrypted temporary storage is iterated, each encrypted annotation object is obtained, and the objects annotated in the class are extracted, and the type of the effect class is defined to determine whether the class is an entity class or a service class. If the field of the class contains the @Field annotation, and each field has a clear get / set method, it is determined to be an entity class; if the class name contains Service or dao, and the field of the class has a large number of @Resource and @Autowired, it is defined as a service class; after the determination is completed, the class name is inserted into the initial encrypted relationship tree as the root node, and the inserted content is: refer to the class name of the actual entity class, and the type is the real root. Iterate the encrypted temporary storage, obtain each encrypted annotation object, and extract the objects annotated in the class method and class field, and at the same time upgrade the scope, provide the effect class name (that is, refer to the class name of the virtual entity class), create a virtual root in the initial encrypted relationship tree, the root name is the class name, the type is the virtual root, and the annotated method and field are inserted. Further, each node in the initial encrypted relationship tree is annotated with a candidate encryption method to obtain a candidate encrypted relationship tree.

[0106] Exemplarily, the class name of the reference entity class is obtained from the candidate encrypted relationship tree, and the target framework that the current program depends on is determined; the orm framework configuration file corresponding to the reference entity class is determined according to the target framework, and the relationship of the to-be-processed service class corresponding to the reference entity class calling the target framework is determined to determine whether at least one of the following situations occurs: a field type of integer is called, and a calculation function is called; an interval comparison is performed on the time field; there is a fuzzy match; if at least one of the above situations exists, the corresponding reference entity class is marked as a semi-configuration type; if none of the above situations exists, the corresponding reference entity class is marked as a full configuration type, and the target encrypted relationship tree is obtained.

[0107] Exemplarily, after obtaining the target encrypted relationship tree, an interceptor of the orm framework is added to intercept the addition, modification, and query operations, and the following processing is performed:

[0108] Specifically, for addition and modification: according to the modified current entity class, search in the target encrypted relationship tree to determine whether the current entity class being operated is a full configuration type or a semi-configuration type. If it is a full configuration type, make an instance deep copy of the added data (copy the current updated data to obtain the updated standby data), encrypt all the copied data, and replace the instance object intercepted by the ORM to perform addition and modification operations; if it is a semi-configuration type, make an instance deep copy of the added data. For the current entity class of the semi-configuration type, check in the target encrypted relationship tree whether the current updated field of the current entity class has a fuzzy match. If so, the current entity class needs to be bytecode enhanced, and a shadow field of the fuzzy field is added (that is, an updated shadow field of the current updated field is added). At the same time, by obtaining the table structure of the current data table corresponding to the current entity class, detect whether there is a shadow field in the table structure. If not created, after the creation is completed, firstly perform word segmentation on the updated standby data of the updated shadow field, encrypt and splice each word, set it to the updated shadow field, encrypt the current updated data under the current updated field, and replace the instance object intercepted by the orm to perform addition and modification operations.

[0109] Specifically, for query operations, it is mainly determined whether the current query field is set to the current query data and whether it is a semi-configured type. If this is the case, the parameter object (i.e., the current query data) needs to be deeply copied (i.e., the current query data is copied to obtain the query backup data), and byte enhancement is performed to add a query shadow field, copy the value of the current query field to the query shadow field (i.e., set the query backup data to the query shadow field), and change the query orm (Object-Relational Mapping, programming framework) framework's sql (Structured Query Language) main field (i.e., the current query field) to replace it with the query shadow field; after the query is completed, the returned data (i.e., the current query result) is decrypted and the query shadow field is removed.

[0110] Embodiment 4

[0111] Figure 3 The fourth embodiment of the present invention provides a structural diagram of a data processing device. This embodiment is applicable to the case where data stored in a database is encrypted. The method can be executed by a data processing device, which can be implemented in software and / or hardware and can be configured in an electronic device that carries a data processing function.

[0112] like Figure 3 As shown, the device includes: a current entity type determination module 310, a fuzzy matching judgment module 320, a shadow field determination module 330, a data encryption module 340 and a data storage module 350. Among them,

[0113] The current entity type determination module 310 is used to obtain the current update data and the corresponding current update field, and determine the current entity type of the current entity class where the current update field is located based on a preset target encryption relationship tree; wherein the target encryption relationship tree is determined based on the data to be encrypted determined from the candidate entity class and / or the candidate processing method, and a preset configuration type determination strategy;

[0114] A fuzzy matching judgment module 320 is used to determine whether there is a fuzzy match in the current update field if the current entity type is a semi-configuration type;

[0115] A shadow field determination module 330, configured to determine an updated shadow field of the current updated field, if any, and to determine updated standby data of the current updated data;

[0116] The data encryption module 340 is used to encrypt the current update data under the current update field based on a preset basic encryption method to obtain encrypted update data, and to encrypt the update standby data under the update shadow field based on the target encryption relationship tree to obtain encrypted standby data;

[0117] The data storage module 350 is used to store the encrypted update data and the encrypted standby data in a current data table corresponding to the current entity class in a database.

[0118] An embodiment of the present invention provides a data processing solution, which obtains current update data and corresponding current update fields, and determines the current entity type of the current entity class where the current update field is located based on a preset target encryption relationship tree; wherein the target encryption relationship tree is determined based on the data to be encrypted determined from the candidate entity class and / or the candidate processing method, and a preset configuration type determination strategy; if the current entity type is a semi-configuration type, it is determined whether there is a fuzzy match in the current update field; if so, the update shadow field of the current update field is determined, and the update standby data of the current update data is determined; based on a preset basic encryption method, the current update data under the current update field is encrypted to obtain encrypted update data, and based on the target encryption relationship tree, the update standby data under the update shadow field is encrypted to obtain encrypted standby data; the encrypted update data and the encrypted standby data are stored in the current data table corresponding to the current entity class in the database. The above scheme introduces a target encrypted relationship tree. When the current entity class is a semi-configured type, it determines the updated shadow field of the current updated field and the updated backup data of the current updated data. It uses a preset basic encryption method to encrypt the current updated data under the current updated field. At the same time, it uses the target encrypted relationship tree to encrypt the updated backup data under the updated shadow field. This achieves encrypted storage of the current updated data under the current updated field and customized encrypted storage of the backup data under the shadow field without changing the original code, thereby improving the security of data in the database and meeting the needs of personalized data encryption storage.

[0119] Optionally, the target encrypted relationship tree is determined based on the following means:

[0120] A candidate entity class determination module, used to determine a candidate processing method associated with a service class to be processed, and based on the candidate processing method, determine a candidate entity class under the service class to be processed;

[0121] A candidate tree determination module, used to determine the data to be encrypted from the candidate entity classes and / or the candidate processing methods according to business requirements, and to construct a candidate encryption relationship tree according to the data to be encrypted;

[0122] A configuration type determination module, used to determine the reference configuration type of the reference entity class according to the reference fields, reference processing methods, and preset configuration type determination strategies under each reference entity class in the candidate encrypted relationship tree; wherein the configuration type determination strategy includes an integer field determination strategy, a time field determination strategy, and a fuzzy matching determination strategy;

[0123] The target tree determination module is used to update the candidate encrypted relationship tree according to the reference configuration type of each reference entity class to obtain a target encrypted relationship tree.

[0124] Optionally, if the data to be encrypted includes an entity class to be encrypted and a processing method to be encrypted, the candidate tree construction module is specifically used to:

[0125] The entity class to be encrypted is used as a reference actual entity class, and the candidate processing methods and candidate fields under the reference actual entity class are used as reference processing methods and reference fields under the reference actual entity class;

[0126] The candidate entity class corresponding to the to-be-encrypted processing method is used as a reference virtual entity class of the to-be-encrypted processing method, the to-be-encrypted processing method is used as a reference processing method under the reference virtual entity class, and the candidate field corresponding to the to-be-encrypted processing method is used as a reference field under the reference virtual entity class;

[0127] Constructing an initial encrypted relationship tree according to the reference actual entity class, the reference processing method and the reference field under the reference actual entity class, the reference virtual entity class, and the reference processing method and the reference field under the reference virtual entity class;

[0128] According to business requirements, each node in the initial encryption relationship tree is marked with a candidate encryption method to obtain a candidate encryption relationship tree.

[0129] Optionally, the candidate entity class determination module is specifically used to:

[0130] Obtaining a class path of a service class to be processed, and determining a candidate processing method associated with the service class to be processed according to the class path;

[0131] A method call relationship tree is generated according to the candidate processing methods, and a candidate entity class under the to-be-processed service class is determined according to the method call relationship tree.

[0132] Optionally, the data encryption module 340 includes:

[0133] an encrypted standby data determining unit, configured to determine a target encryption mode of the current update data from the target encryption relationship tree, and encrypt the update standby data under the update shadow field according to the target encryption mode to obtain encrypted standby data;

[0134] Accordingly, the data storage module 350 includes:

[0135] A current data table determination unit, used to determine the current data table corresponding to the current entity class in the database;

[0136] The data storage unit is used to store the encrypted update data in the corresponding update main field in the current data table, and store the encrypted standby data in the corresponding shadow main field in the current data table.

[0137] Optionally, the device further comprises:

[0138] An encrypted update data determination module, configured to encrypt the current update data based on a preset basic encryption method to obtain encrypted update data if the current entity type is a full configuration type;

[0139] The main field storage module is used to store the encrypted update data in the corresponding update main field in the current data table.

[0140] Optionally, the device further comprises:

[0141] A query entity type determination module, used to obtain current query data and current query fields, and determine the query entity type of the query entity class where the current query field is located based on a preset target encrypted relationship tree;

[0142] A query standby data determination module, configured to determine a query shadow field of the current query field and determine query standby data of the current query data if the query entity type is a semi-configuration type;

[0143] The current query result determination module is used to obtain the current query result from the database according to the query backup data under the query shadow field.

[0144] The data processing device provided in the embodiment of the present invention can execute the data processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing each data processing method.

[0145] In the technical solution of the present invention, the collection, storage, use, processing, transmission, provision and disclosure of current update data, current update fields, configuration type determination strategies and preset basic encryption methods, etc., all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0146] Embodiment 5

[0147] Figure 4 It is a structural schematic diagram of an electronic device for implementing a data processing method provided in Embodiment 5 of the present invention.

[0148] The electronic device 410 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the invention described and / or claimed herein.

[0149] like Figure 4 As shown, the electronic device 410 includes at least one processor 411, and a memory connected to the at least one processor 411 in communication, such as a read-only memory (ROM) 412, a random access memory (RAM) 413, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 411 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 412 or the computer program loaded from the storage unit 418 to the random access memory (RAM) 413. In the RAM 413, various programs and data required for the operation of the electronic device 410 can also be stored. The processor 411, the ROM 412, and the RAM 413 are connected to each other via a bus 414. An input / output (I / O) interface 415 is also connected to the bus 414.

[0150] Multiple components in the electronic device 410 are connected to the I / O interface 415, including: an input unit 416, such as a keyboard, a mouse, etc.; an output unit 417, such as various types of displays, speakers, etc.; a storage unit 418, such as a disk, an optical disk, etc.; and a communication unit 419, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 419 allows the electronic device 410 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0151] The processor 411 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 411 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 411 performs the various methods and processes described above, such as a data processing method.

[0152] In some embodiments, the data processing method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 418. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 410 via the ROM 412 and / or the communication unit 419. When the computer program is loaded into the RAM 413 and executed by the processor 411, one or more steps of the data processing method described above may be performed. Alternatively, in other embodiments, the processor 411 may be configured to perform the data processing method in any other appropriate manner (e.g., by means of firmware).

[0153] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0154] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0155] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0156] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0157] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0158] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0159] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0160] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A data processing method, characterized in that: include: Acquire current update data and corresponding current update fields, and determine the current entity type of the current entity class where the current update field is located based on a preset target encryption relationship tree; wherein the target encryption relationship tree is determined based on the data to be encrypted determined from the candidate entity class and / or the candidate processing method, and a preset configuration type determination strategy; If the current entity type is a semi-configured type, determining whether there is a fuzzy match in the current update field; If it exists, determining the updated shadow field of the current updated field, and determining the updated standby data of the current updated data; Encrypting the current update data under the current update field based on a preset basic encryption method to obtain encrypted update data, and encrypting the update standby data under the update shadow field based on the target encryption relationship tree to obtain encrypted standby data; The encrypted update data and the encrypted standby data are stored in a current data table corresponding to the current entity class in a database.

2. The method according to claim 1, characterized in that The target encryption relationship tree is determined based on the following method: Determine a candidate processing method associated with the service class to be processed, and based on the candidate processing method, determine a candidate entity class under the service class to be processed; According to business requirements, determine the data to be encrypted from the candidate entity classes and / or the candidate processing methods, and construct a candidate encryption relationship tree according to the data to be encrypted; Determine the reference configuration type of the reference entity class according to the reference fields, reference processing methods, and preset configuration type determination strategies under each reference entity class in the candidate encrypted relationship tree; wherein the configuration type determination strategy includes an integer field determination strategy, a time field determination strategy, and a fuzzy matching determination strategy; According to the reference configuration type of each reference entity class, the candidate encrypted relationship tree is updated to obtain a target encrypted relationship tree.

3. The method according to claim 2, characterized in that If the data to be encrypted includes an entity class to be encrypted and a processing method to be encrypted, then the step of constructing a candidate encryption relationship tree according to the data to be encrypted includes: The entity class to be encrypted is used as a reference actual entity class, and the candidate processing methods and candidate fields under the reference actual entity class are used as reference processing methods and reference fields under the reference actual entity class; The candidate entity class corresponding to the to-be-encrypted processing method is used as a reference virtual entity class of the to-be-encrypted processing method, the to-be-encrypted processing method is used as a reference processing method under the reference virtual entity class, and the candidate field corresponding to the to-be-encrypted processing method is used as a reference field under the reference virtual entity class; Constructing an initial encrypted relationship tree according to the reference actual entity class, the reference processing method and the reference field under the reference actual entity class, the reference virtual entity class, and the reference processing method and the reference field under the reference virtual entity class; According to business requirements, each node in the initial encryption relationship tree is marked with a candidate encryption method to obtain a candidate encryption relationship tree.

4. The method according to claim 2, characterized in that The step of determining a candidate processing method associated with the service class to be processed, and determining a candidate entity class under the service class to be processed based on the candidate processing method, includes: Obtaining a class path of a service class to be processed, and determining a candidate processing method associated with the service class to be processed according to the class path; A method call relationship tree is generated according to the candidate processing methods, and a candidate entity class under the service class to be processed is determined according to the method call relationship tree.

5. The method according to claim 1, characterized in that: The step of encrypting the updated standby data under the updated shadow field based on the target encrypted relationship tree to obtain the encrypted standby data includes: Determine the target encryption mode of the current update data from the target encryption relationship tree, and encrypt the update standby data under the update shadow field according to the target encryption mode to obtain encrypted standby data; Correspondingly, storing the encrypted update data and the encrypted standby data in a current data table corresponding to the current entity class in the database includes: Determine the current data table corresponding to the current entity class in the database; The encrypted update data is stored in the corresponding update main field in the current data table, and the encrypted standby data is stored in the corresponding shadow main field in the current data table.

6. The method according to claim 5, characterized in that The method further comprises: If the current entity type is a full configuration type, encrypting the current update data based on a preset basic encryption method to obtain encrypted update data; The encrypted update data is stored in the corresponding update main field in the current data table.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Acquire current query data and current query fields, and determine the query entity type of the query entity class where the current query field is located based on a preset target encrypted relationship tree; If the query entity type is a semi-configuration type, determining a query shadow field of the current query field, and determining query standby data of the current query data; The current query result is obtained from the database according to the query standby data under the query shadow field.

8. A data processing device, characterized in that: include: A current entity type determination module, used to obtain current update data and corresponding current update fields, and determine the current entity type of the current entity class where the current update field is located based on a preset target encryption relationship tree; wherein the target encryption relationship tree is determined based on the data to be encrypted determined from the candidate entity class and / or the candidate processing method, and a preset configuration type determination strategy; A fuzzy matching judgment module, used to determine whether there is a fuzzy match in the current update field if the current entity type is a semi-configuration type; A shadow field determination module, configured to determine an updated shadow field of the current updated field, if any, and to determine updated standby data of the current updated data; A data encryption module, configured to encrypt the current update data under the current update field based on a preset basic encryption method to obtain encrypted update data, and to encrypt the update standby data under the update shadow field based on the target encryption relationship tree to obtain encrypted standby data; The data storage module is used to store the encrypted update data and the encrypted standby data in a current data table corresponding to the current entity class in a database.

9. An electronic device, characterized in that: include: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement a data processing method as described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, a data processing method as described in any one of claims 1 to 7 is implemented.

Images