WO2021174882A1 - Procédé et appareil de vérification de données, dispositif informatique et support d'enregistrement lisible - Google Patents

Procédé et appareil de vérification de données, dispositif informatique et support d'enregistrement lisible Download PDF

Info

Publication number
WO2021174882A1
WO2021174882A1 PCT/CN2020/125114 CN2020125114W WO2021174882A1 WO 2021174882 A1 WO2021174882 A1 WO 2021174882A1 CN 2020125114 W CN2020125114 W CN 2020125114W WO 2021174882 A1 WO2021174882 A1 WO 2021174882A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
user
service
key value
hash
Prior art date
Application number
PCT/CN2020/125114
Other languages
English (en)
Chinese (zh)
Inventor
何自兴
张德顺
张汉文
张煜清
冯宇
冯玉娜
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2021174882A1 publication Critical patent/WO2021174882A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/13—File access structures, e.g. distributed indices
    • G06F16/137—Hash-based
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/14—Details of searching files based on file metadata
    • G06F16/148—File search processing
    • G06F16/152—File search processing using file content signatures, e.g. hash values
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/182—Distributed file systems

Definitions

  • This application relates to the field of cloud service technology, and in particular to a data fragment verification method, device, computer equipment, and readable storage medium, which use a hash code generated by the hash technology of the blockchain.
  • Data interaction is generated between the distributed client terminal and the centralized server, such as virtual currency transaction scenarios such as transactions, financial management, financial management, etc., and data synchronization is finally completed.
  • virtual currency transaction scenarios such as transactions, financial management, financial management, etc.
  • data synchronization is finally completed.
  • the client terminal The financial information stored in the centralized server should be consistent with the financial information stored in the centralized server.
  • the centralized server may have synchronization failures when synchronizing data with the distributed clients, and the synchronized data obtained after the synchronization failure is often still stored in the user.
  • the data between the distributed client and the centralized server is different, and it is difficult to be identified.
  • the current approach is to extract the user data in the distributed client and enter it into the database of the centralized server, and store the user data in the database. Compare with service data one by one.
  • the inventor realized that the comparison process of this approach will not only call a large amount of resources of the centralized server, but also that the comparison process will be very slow due to the huge amount of data; and because the comparison process is in the database Therefore, the client cannot call other information in the database of the centralized server during the execution of the comparison operation, which greatly reduces the efficiency of data interaction and calling between the client and the server.
  • the purpose of this application is to provide a data slice verification method, device, computer equipment, and readable storage medium, which are used to solve the problem that the comparison process in the prior art will be very slow, and the user cannot perform the comparison operation. Calling other information in the database of the centralized server during execution greatly reduces the efficiency of data interaction and calling between the client and the server.
  • this application provides a data fragment verification method for verifying the synchronized data between a distributed client and a centralized server, including:
  • a verification process is performed to verify the user target data and the service target data to identify abnormal data therein.
  • this application also provides a data fragment verification device, including:
  • the data acquisition module is used to acquire the user data of the distributed client and the service data of the centralized server;
  • the fragmentation service module is used to execute the fragmentation process to separately fragment the user data and service data, and aggregate user data elements that contain the same user hash code in the user data to obtain user fragmentation data, and Summarize the service data elements that contain the same service hash code in the service data to obtain service fragment data; wherein, the user data element is the smallest unit that constitutes the user data, and the service data element constitutes the service The smallest unit of data;
  • the target recognition module is used to call a distributed system containing at least one computing server to execute parallel processes to obtain user hash codes and service hash codes with the same value from user fragment data and service fragment data, as well as User target data and service target data corresponding to the user hash code and the service hash code;
  • the verification service module is used to perform a verification process to verify the user target data and the service target data to identify abnormal data therein.
  • this application also provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and running on the processor.
  • the processor of the computer device executes the computer program.
  • Data fragment verification method, the data fragment verification method includes:
  • a verification process is performed to verify the user target data and the service target data to identify abnormal data therein.
  • the present application also provides a computer-readable storage medium, the readable storage medium stores a computer program, and the computer program stored in the readable storage medium is executed by a processor to realize data slicing Verification methods, data fragment verification methods include:
  • a verification process is performed to verify the user target data and the service target data to identify abnormal data therein.
  • the data fragment verification method, device, computer equipment, and readable storage medium provided in this application avoid data verification in the database of the centralized server by obtaining user data on the distributed user side and service data of the centralized server.
  • the server needs to consume a lot of resources for data verification, and cannot provide data call services for the user end, which leads to the problem of reduced efficiency of data interaction and call between the user end and the server.
  • the user data and service data are fragmented by executing the fragmentation process, which helps to improve the efficiency of data verification; the parallel process executed by the distributed system helps to improve the identification efficiency of the user target data and user service data; by distribution
  • Each computing server in the system separately performs a verification process on the user target data and service target data it obtains, which not only improves the technical effect of data verification efficiency, but also calls an external distributed system to verify the user target data and service target data.
  • the verification avoids occupying the memory and computing power of the centralized server, thereby avoiding the problem that the current client cannot call other information in the database of the centralized server during the execution of the comparison operation, which greatly improves the client The efficiency of data interaction and invocation with the server.
  • FIG. 1 is a flowchart of Embodiment 1 of a method for verifying data fragments according to this application;
  • FIG. 2 is a schematic diagram of the environmental application of the data fragment verification method in the second embodiment of the data fragment verification method of this application;
  • FIG. 5 is a flowchart of the parallel process in the second embodiment of the data fragment verification method of the present application.
  • FIG. 6 is a flowchart of the verification process in the second embodiment of the data fragment verification method of the present application.
  • FIG. 7 is a flowchart of determining whether the target file corresponding to the user key value is consistent with the target file corresponding to the service key value in the second embodiment of the data fragment verification method of the present application;
  • FIG. 8 is a schematic diagram of program modules of Embodiment 3 of the data fragment verification device of this application.
  • FIG. 9 is a schematic diagram of the hardware structure of the computer device in the fourth embodiment of the computer device of this application.
  • a data fragment verification method of this embodiment is used to verify the synchronized data between a distributed client and a centralized server, including:
  • S101 Obtain user data of a distributed client and service data of a centralized server.
  • S104 Perform a fragmentation process to separately fragment the user data and service data, summarize user data elements that contain the same user hash code in the user data to obtain user fragmentation data, and summarize the service data
  • the service data elements containing the same service hash code in the service data element obtain the service fragment data; wherein, the user data element is the smallest unit that constitutes the user data, and the service data element is the smallest unit that constitutes the service data.
  • S106 Invoke a distributed system including at least one computing server to execute a parallel process to obtain user hash codes and service hash codes with the same value from the user slice data and service slice data, and to obtain the same value as the user hash code.
  • the user target data and service target data corresponding to the Greek code and the service hash code.
  • S107 Perform a verification process to verify the user target data and the service target data to identify abnormal data therein.
  • the user data of the distributed client side and the service data of the centralized server are obtained to avoid data verification in the database of the centralized server, which causes the server to consume a large amount of resources for data verification.
  • the inability to provide data call services for the user end leads to the problem of reduced efficiency of data interaction and call between the user end and the server.
  • data interaction is generated between the distributed client and the centralized server, such as virtual currency transaction scenarios such as transactions, financial management, and wealth management, and data synchronization is finally completed, such as: after the virtual currency transaction ,
  • the financial information stored in the user terminal such as user data in this application
  • the financial information stored in the centralized server such as service data in this application
  • a distributed client purchases a fund worth 1 million in a centralized server (such as fund company B) (the data interaction), and the distribution is synchronized through the data
  • the financial information of "investor A purchased a fund worth 1 million in fund company B" is stored in the distributed client terminal and the centralized server, respectively, as the user data of the distributed client terminal and the service data of the centralized server.
  • the user data is the synchronization data stored in the distributed user terminal after the data interaction process and the data synchronization is completed; the service data is the data synchronization data after the data interaction process is completed , The synchronized data stored in the centralized server.
  • the user data and service data are sharded by executing the sharding process to facilitate the use of the computing servers in the distributed system to obtain the sharded data, which helps to improve the efficiency of data verification; the parallel process is executed through the distributed system to Obtain user hash codes and service hash codes with the same value, and obtain user target data and service target data corresponding to the user hash codes and service hash codes, respectively, so as to improve the performance of the user target data and user service data.
  • each computing server in the distributed system performs a verification process on the user target data and service target data obtained by each computing server to identify the abnormal data, which not only achieves the technical effect of improving the efficiency of data verification, but also calls external
  • the distributed system checks the user target data and the service target data to avoid occupying the memory and computing power of the centralized server, thereby avoiding the current user’s inability to call the centralized server during the execution of the comparison operation.
  • the problem of other information in the database greatly improves the efficiency of data interaction and invocation between the client and the server.
  • the user hash code in this embodiment is a hash code obtained by performing a hash operation on the user key value key of the data obtained by the first hash algorithm in the hashmap method;
  • the service The hash code is a hash code obtained by performing a hash operation on the obtained service key value key through the first hash algorithm in the hashmap method. Since the hash operation on the key by the hash algorithm belongs to the prior art, the hash algorithm and its operation principle are not described here.
  • This embodiment is a specific application scenario of the foregoing Embodiment 1. Through this embodiment, the method provided by this application can be described more clearly and specifically.
  • Fig. 2 schematically shows an environmental application diagram of the data fragment verification method according to the second embodiment of the present application.
  • the authentication server 2 where the data fragment verification method is located is connected to the distributed client 3, the centralized server 4, and the distributed system 5 via a network; the server 2 may pass through one or more networks
  • the network may include various network devices, such as routers, switches, multiplexers, hubs, modems, bridges, repeaters, firewalls, proxy devices, and/or the like.
  • the network may include physical links, such as coaxial cable links, twisted pair cable links, optical fiber links, combinations thereof, and/or the like.
  • the network may include wireless links, such as cellular links, satellite links, Wi-Fi links, and/or the like;
  • the client terminal in the distributed client terminal 3 may be a smart phone or a tablet computer that stores user data , notebook computers, desktop computers, and other computer equipment,
  • the centralized server may be a server or a server system cluster storing service data, and the computing server in the distributed system may be a service system pre-stored with a check process.
  • FIG. 3 is a specific method flowchart of a data fragment verification method provided by an embodiment of the present application. The method specifically includes steps S201 to S208.
  • S201 Obtain user data of a distributed client and service data of a centralized server.
  • data interaction is generated between the distributed client and the centralized server, such as virtual currency transaction scenarios such as transactions, financial management, wealth management, etc.
  • data synchronization is finally completed, such as: after the virtual currency transaction,
  • the financial information stored in the user terminal (such as user data in this application) and the financial information stored in the centralized server (such as service data in this application) should be consistent.
  • a distributed client such as investor A purchases a fund worth 1 million in a centralized server (such as fund company B) (the data interaction), and the distribution is synchronized through the data
  • the financial information of "investor A purchased a fund worth 1 million in fund company B" is stored in the distributed client terminal and the centralized server, respectively, as the user data of the distributed client terminal and the service data of the centralized server.
  • the user data is the synchronization data stored in the distributed user terminal after the data interaction process and the data synchronization is completed;
  • the service data is the data synchronization data after the data interaction process is completed ,
  • the synchronized data stored in the centralized server.
  • the acquired user data and service data may be a fund change table.
  • the server needs to consume a lot of resources for data verification, and cannot provide data call services for the user end, resulting in a reduction in the efficiency of data interaction and call between the user end and the server
  • the user data of the distributed user terminal and the service data of the centralized server are obtained to avoid the above problems.
  • the user key value is a user invalid key value and stored in a preset abnormal database, and the user invalid key value is deleted from the user data.
  • user data is usually stored in the form of key-value pairs in the distributed user terminal, where the user key-value is the key of the key-value pair, and the target file is the key-value pair. Therefore, for a user key value (that is: key) without a target file (value), the user key value is invalid.
  • the formation of this user key value must be an abnormal operation in the distributed client.
  • the user key value is the invalid user key value and stored in the preset exception database, so as to remind the administrator of the occurrence of the abnormality, by deleting the invalid user key value from the user data,
  • the user key value in the user data can be sequentially identified through the polling mechanism, and the user key value corresponding to the user key value can be retrieved.
  • the target file if the target file can be retrieved, it means that the user key has a corresponding target file; if the target file cannot be retrieved, it means that the user key does not have a corresponding target file.
  • S203 Verify whether the service key value in the service data has a corresponding target file.
  • the service key value is a service invalid key value and stored in a preset exception database, and the service invalid key value is deleted from the service data.
  • service data is usually stored in the form of key-value pairs in a centralized server. Therefore, for a service key value (ie: key) without a target file (value), the service key value is Invalid, the formation of this service key must be an abnormal operation in the centralized server. Therefore, the service key is set to the invalid service key and stored in the preset exception database to facilitate reminder management In the event of abnormal occurrence, the invalid service key value is deleted from the service data to ensure that all information in the service data used for verification is valid.
  • S204 Perform a fragmentation process to separately fragment the user data and service data, summarize user data elements that contain the same hash code in the user data to obtain user fragmentation data, and summarize the service data
  • Service data elements containing the same hash code obtain service fragment data; wherein, the user data element is the smallest unit that constitutes the user data, and the service data element is the smallest unit that constitutes the service data.
  • this step divides the user data and service data by executing the fragmentation process, so that each computing server in the distributed system can obtain the fragmented data separately, which helps to improve the efficiency of data checking.
  • the user data is fragmented by using the hash consistency fragmentation rule to obtain at least one user fragmentation data
  • the user fragmentation data is entered into the preset user record table, and the hash is used.
  • the consistent fragmentation rule fragments the service data to obtain at least one service fragmentation data.
  • the fragmentation process includes:
  • S41 Obtain a user hash table of user data and a service hash table of service data; wherein, the user hash table reflects the storage location of each user data element in the user data in the distributed user terminal, so The service hash table reflects the storage location of each service data element in the service data in the centralized server.
  • the user hash table and service hash table namely: hashmap
  • hashmap is a data structure that stores user data in an array, and each user data element or service data element will be key-
  • the form of value pair is stored as an entry in the user hash table or service hash table, and the entry is the smallest unit of data in the hash table, where Entry is a key value stored in the hashmap
  • the right unit module is a data structure that stores user data in an array, and each user data element or service data element will be key-
  • the form of value pair is stored as an entry in the user hash table or service hash table, and the entry is the smallest unit of data in the hash table, where Entry is a key value stored in the hashmap The right unit module.
  • S42 Identify the hash bucket corresponding to the hash code in the user hash table, extract the user data elements in the hash bucket and summarize the user segment data; and identify the hash code in the service hash table
  • the corresponding hash bucket extracts and summarizes the service data elements in the hash bucket to obtain service fragment data.
  • the get function in the hashmap is used to obtain the hash code hashcode in the user hash table and the service hash table, where hashcode is the hash bucket number that stores the user data element and the service data element.
  • hashcode is the hash bucket number that stores the user data element and the service data element.
  • the user data elements stored in the same hash bucket are aggregated to form user fragmentation data
  • the service data elements stored in the same hash bucket are aggregated to form service fragmentation data, so that user fragmentation data and service fragmentation data can be based on the hash bucket.
  • the Greek codes correspond to each other, so that the user segment data and the service segment data of the same hash code can be compared through the parallel execution of the verification process, so as to improve the efficiency of data verification.
  • S205 Enter the user segment data into a preset user record table, and load the user status tag on the user segment data in the user record table; and enter the service segment data into the preset user record table. In the service record table, and load the service status label on the service fragment data in the service record table.
  • this step is to set the user record table and the service record table, and load the user shard data
  • the status tag may include: checked, unchecked, and checked, to clarify the current status of each piece of data, so as to prevent the distributed system from obtaining the checked and checked user pieces Fragmentation of data and service data improves the execution efficiency of data verification operations.
  • S206 Invoke a distributed system including at least one computing server to execute a parallel process to obtain user hash codes and service hash codes with the same value from the user slice data and service slice data, and the same value as the user hash code.
  • the user target data and service target data corresponding to the Greek code and the service hash code.
  • a parallel process is executed through a distributed system to obtain user hash codes and service hash codes with the same value, and obtain user target data and service target data corresponding to the user hash codes and service hash codes, respectively, to Improve the identification efficiency of the user target data and user service data.
  • the parallel process includes:
  • S61 Invoke the computing server in the distributed system, identify the content as the user status label to be verified and obtain user segment data corresponding to the user status label, and identify the content as the service status label to be verified, and obtain the The service fragment data corresponding to the service status tag.
  • S62 Identify the user hash code and the service hash code with the same value in the user fragment data and the service fragment data, and replace the user fragment data and service corresponding to the user hash code and the service hash code respectively.
  • Fragmented data set as user target data and service target data;
  • S63 Modify the user status label of the user segment data acquired by the computer server to be verified, and modify the service status label of the service segment data acquired by the computer server to be verified to avoid other calculations in the distributed system
  • the server obtains the user segment data and the service segment data.
  • the user status label and service status label are editable.
  • edit the content of the user status label and service status label so that they are “To be checked” is changed to "Checking in progress.”
  • S207 Perform a verification process to verify the user target data and the service target data to identify abnormal data therein.
  • the abnormality of the user target data and the service target data is identified through the verification process, so as to identify the abnormal data therein, and achieve the technical effect of improving the efficiency of data verification.
  • the verification process includes:
  • S71 Extract user key values and service key values with consistent values from the user target data and service target data, and determine whether the target file corresponding to the user key value is consistent with the target file corresponding to the service key value;
  • S75 Extract a service key value that does not exist in the user target data from the service target data, and set the service key value and its target file as service unilateral data.
  • user target data includes “data A, data B, and data C”
  • service target data includes “data A, data B, and data D”.
  • S76 Summarize the non-matching data, user unilateral data, and service unilateral data to obtain abnormal data.
  • construct a first abnormal hash table for storing the non-matching data construct a second abnormal hash table for users to store the user unilateral data, delete the service key value in the service unilateral data, and construct The third abnormal hash table used to store the unilateral data of the service, summarize the first abnormal hash table, the second abnormal hash table, and the third abnormal hash table to obtain abnormal data, and save the abnormal data To the abnormal database.
  • the non-matching data, user unilateral data, and service unilateral data are hashed through the hashmap algorithm to obtain an abnormal hash table. Since the hashmap algorithm and hash processing belong to the prior art, and the technical problem to be solved by this application is how to identify abnormal data and store it, the technical principles of the hashmap algorithm and hash processing are not repeated here.
  • the non-matching data after aggregating the non-matching data, user unilateral data, and service unilateral data to obtain abnormal data, it further includes:
  • the corresponding summary information is obtained based on the abnormal data.
  • the summary information is obtained by hashing the abnormal data, for example, obtained by the sha256s algorithm.
  • Uploading summary information to the blockchain can ensure its security and fairness and transparency to users.
  • the user equipment can download the summary information from the blockchain to verify whether the abnormal data has been tampered with.
  • the blockchain referred to in this example is a new application mode of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm.
  • Blockchain essentially a decentralized database, is a series of data blocks associated with cryptographic methods. Each data block contains a batch of network transaction information for verification. The validity of the information (anti-counterfeiting) and the generation of the next block.
  • the blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.
  • the step of judging whether the target file corresponding to the user key value is consistent with the target file corresponding to the service key value includes:
  • S71-1 Calculate the user key value and the service key value by using the preset first hash algorithm to obtain the user hash code and the service hash code.
  • the user hash code is a hash code obtained by performing a hash operation on the user key value key of the obtained data through the first hash algorithm in the hashmap method; the service hash code is obtained through a hashmap The first hash algorithm in the method performs a hash operation on the obtained service key value key to obtain a hash code hashcode.
  • S71-2 Determine whether the user hash code and the service hash code are consistent.
  • the user location code uses the second hash algorithm of the hashmap to perform a hash operation on the user hash code hashcode and the length of the target file value corresponding to the user key value key to obtain an array subscript;
  • the service location code uses the second hash algorithm of the hashmap to perform a hash operation on the service hash code hashcode and the length of the target file value corresponding to the service key value key to obtain an array subscript.
  • S71-5 Determine whether the user location code and the service location code are consistent according to the obtained user location code and service location code.
  • the user status label and service status label are editable.
  • edit the content of the user status label and service status label so that they are “Checking” is changed to "Checked.”
  • the user hash code and the service hash code are obtained by comparing the key in the user fragment data and the service fragment data, and compare them, and then obtain the user location code according to the user hash code and the service hash code It is compared with the service location code, so that the verification process does not need to compare the user fragment data and the service fragment data one by one, and the verification result can be obtained accurately, which improves the efficiency of data verification.
  • this step saves the abnormal data in the abnormal data table.
  • the first abnormal hash table, the second abnormal hash table, and the first abnormal hash table are stored in the abnormal data table.
  • Three abnormal hash tables are sent and stored in the preset abnormal database.
  • a data fragment verification device 1 of this embodiment includes:
  • the data acquisition module 11 is used to acquire the user data of the distributed client and the service data of the centralized server;
  • the fragmentation service module 14 is configured to execute the fragmentation process to separately fragment the user data and service data, and summarize user data elements that contain the same user hash code in the user data to obtain user fragmentation data, And summarizing the service data elements that contain the same service hash code in the service data to obtain the service fragment data; wherein, the user data element is the smallest unit that constitutes the user data, and the service data element constitutes the The smallest unit of service data;
  • the target recognition module 16 is used to call a distributed system including at least one computing server to execute parallel processes to obtain user hash codes and service hash codes with the same value from user fragment data and service fragment data, and User target data and service target data corresponding to the user hash code and the service hash code;
  • the verification service module 17 is used to perform a verification process to verify the user target data and the service target data to identify abnormal data therein.
  • the data fragment verification device 1 further includes:
  • the user verification module 12 is used to verify whether the user key value in the user data has a corresponding target file; if it is, the user key value is retained; if not, it is determined that the user key value is an invalid user key value And save it in a preset abnormal database, and delete the invalid key value of the user from the user data.
  • the data fragment verification device 1 further includes:
  • the service verification module 13 is used to verify whether the service key value in the service data has a corresponding target file; if it is, the service key value is retained; if not, it is determined that the service key value is an invalid service key value And save it in a preset abnormal database, and delete the service invalid key value from the service data.
  • the data fragment verification device 1 further includes:
  • the status tag module 15 is used to enter the user segment data into a preset user record table, and load the user status tag on the user segment data in the user record table; and segment the service The data is entered into the preset service record table, and the service status label is loaded on the service fragment data in the service record table.
  • the data fragment verification device 1 further includes:
  • the abnormality saving module 18 is used for saving abnormal data in a preset abnormal data table.
  • This technical solution is applied to the field of cloud computing technology for cloud services, by performing a sharding process on the acquired user data and service data, and calling a distributed system containing at least one computing server to execute parallel processes, so as to develop distributed systems.
  • Cluster calculations are performed to obtain user hash codes and service hash codes with the same value, as well as user target data and service target data corresponding to the user hash codes and service hash codes, and finally perform a verification process to identify abnormal data.
  • the present application also provides a computer device 6.
  • the components of the data slice verification device 1 in the third embodiment can be dispersed in different computer devices.
  • the computer device 6 can be a smart phone or a tablet that executes the program.
  • the computer device in this embodiment at least includes but is not limited to: a memory 61 and a processor 62 that can be communicatively connected to each other through a system bus, as shown in FIG. 9. It should be pointed out that FIG. 9 only shows a computer device with components, but it should be understood that it is not required to implement all the components shown, and more or fewer components may be implemented instead.
  • the memory 61 (ie, readable storage medium) includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), Read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disk, optical disk, etc.
  • the memory 61 may be an internal storage unit of a computer device, such as a hard disk or a memory of the computer device.
  • the memory 61 may also be an external storage device of the computer device, for example, a plug-in hard disk equipped on the computer device, a smart memory card (Smart Media Card, SMC), and a Secure Digital (SD) Card, Flash Card, etc.
  • the memory 61 may also include both the internal storage unit of the computer device and its external storage device.
  • the memory 61 is generally used to store an operating system and various application software installed in a computer device, such as the program code of the data slice verification device in the third embodiment, and so on.
  • the memory 61 may also be used to temporarily store various types of data that have been output or will be output.
  • the processor 62 may be a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments.
  • the processor 62 is generally used to control the overall operation of the computer equipment.
  • the processor 62 is configured to run the program code or process data stored in the memory 61, for example, to run a data fragmentation verification device, to implement the data fragmentation verification methods of the first embodiment and the second embodiment.
  • the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium may be volatile or non-volatile.
  • Such as flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read only memory (ROM), electrically erasable and programmable memory Read memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disks, optical disks, servers, App application malls, etc. have computer programs stored thereon, and corresponding functions are realized when the programs are executed by the processor 62.
  • the computer-readable storage medium of this embodiment is used to store a data slicing verification device, and when executed by the processor 62, the data slicing verification method of the first embodiment and the second embodiment is implemented.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Quality & Reliability (AREA)
  • Mathematical Physics (AREA)
  • Library & Information Science (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne le domaine technique des services en nuage, et concerne un procédé de vérification de fragment de données, un appareil, un dispositif informatique et un support d'enregistrement lisible, le procédé comprenant les étapes consistant à : obtenir des données d'utilisateur et des données de service; exécuter un processus de fragmentation pour effectuer une fragmentation sur les données d'utilisateur et les données de service pour obtenir des données d'utilisateur et des données de service; exécuter des processus parallèles pour obtenir un code de hachage d'utilisateur et un code de hachage de service ayant la même valeur, et des données cibles d'utilisateur et des données cibles de service correspondant au code de hachage d'utilisateur et au code de hachage de service; exécuter un processus de vérification pour vérifier les données cibles d'utilisateur et les données cibles de service de façon à identifier des données anormales. La présente invention permet non seulement d'améliorer l'effet technique de l'efficacité de vérification de données, mais aussi d'économiser la mémoire et la puissance de calcul de serveurs centralisés, ce qui permet d'éviter le problème selon lequel un terminal utilisateur courant ne peut pas appeler d'autres informations dans une base de données d'un serveur centralisé pendant l'exécution d'une opération de comparaison, ce qui permet d'améliorer significativement l'efficacité de l'interaction de données et l'invocation entre le terminal utilisateur et le serveur.
PCT/CN2020/125114 2020-09-02 2020-10-30 Procédé et appareil de vérification de données, dispositif informatique et support d'enregistrement lisible WO2021174882A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010908571.0A CN112052141B (zh) 2020-09-02 2020-09-02 数据分片校验方法、装置、计算机设备及可读存储介质
CN202010908571.0 2020-09-02

Publications (1)

Publication Number Publication Date
WO2021174882A1 true WO2021174882A1 (fr) 2021-09-10

Family

ID=73608215

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/125114 WO2021174882A1 (fr) 2020-09-02 2020-10-30 Procédé et appareil de vérification de données, dispositif informatique et support d'enregistrement lisible

Country Status (2)

Country Link
CN (1) CN112052141B (fr)
WO (1) WO2021174882A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114205139A (zh) * 2021-12-09 2022-03-18 中国电信股份有限公司 算力资源管理方法、节点、系统和存储介质
CN115242774A (zh) * 2022-06-24 2022-10-25 浪潮通信技术有限公司 边缘计算网关配置传输方法及装置
CN116094844A (zh) * 2023-04-10 2023-05-09 蓝象智联(杭州)科技有限公司 一种用于多方安全计算的地址核对方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010142111A1 (fr) * 2009-06-09 2010-12-16 中兴通讯股份有限公司 Méthode et appareil de vérification et synchronisation de blocs de données dans un système de fichiers distribués
CN102638578A (zh) * 2012-03-29 2012-08-15 深圳市高正软件有限公司 一种基于移动设备的数据同步方法及系统
CN104780211A (zh) * 2015-04-13 2015-07-15 努比亚技术有限公司 数据同步方法和装置
CN110413441A (zh) * 2019-06-18 2019-11-05 平安科技（深圳）有限公司 主备存储卷同步数据校验方法、装置、设备及存储介质
CN111506578A (zh) * 2020-04-17 2020-08-07 深圳前海微众银行股份有限公司 业务数据的校验方法、装置、设备及存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107154945A (zh) * 2017-05-31 2017-09-12 中南大学 一种基于纠删码的多云碎片化安全存储方法及系统
US10877962B2 (en) * 2017-08-11 2020-12-29 International Business Machines Corporation Deferred update of database hashcode in blockchain
CN109492436A (zh) * 2018-11-29 2019-03-19 深圳市网心科技有限公司 一种文件校验方法及相关装置
CN109816481A (zh) * 2019-01-04 2019-05-28 平安科技（深圳）有限公司 账单处理方法、装置及计算机可读存储介质
CN110149373B (zh) * 2019-04-28 2022-01-07 平安科技（深圳）有限公司 基于点对点网络的数据存储方法、装置、介质及服务器
CN110300173A (zh) * 2019-06-28 2019-10-01 杭州复杂美科技有限公司 去中心化数据存储方法、验证方法、设备和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010142111A1 (fr) * 2009-06-09 2010-12-16 中兴通讯股份有限公司 Méthode et appareil de vérification et synchronisation de blocs de données dans un système de fichiers distribués
CN102638578A (zh) * 2012-03-29 2012-08-15 深圳市高正软件有限公司 一种基于移动设备的数据同步方法及系统
CN104780211A (zh) * 2015-04-13 2015-07-15 努比亚技术有限公司 数据同步方法和装置
CN110413441A (zh) * 2019-06-18 2019-11-05 平安科技（深圳）有限公司 主备存储卷同步数据校验方法、装置、设备及存储介质
CN111506578A (zh) * 2020-04-17 2020-08-07 深圳前海微众银行股份有限公司 业务数据的校验方法、装置、设备及存储介质

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114205139A (zh) * 2021-12-09 2022-03-18 中国电信股份有限公司 算力资源管理方法、节点、系统和存储介质
CN115242774A (zh) * 2022-06-24 2022-10-25 浪潮通信技术有限公司 边缘计算网关配置传输方法及装置
CN116094844A (zh) * 2023-04-10 2023-05-09 蓝象智联(杭州)科技有限公司 一种用于多方安全计算的地址核对方法

Also Published As

Publication number Publication date
CN112052141A (zh) 2020-12-08
CN112052141B (zh) 2022-04-01

Similar Documents

Publication Publication Date Title
EP3776208B1 (fr) Autocorrection d'exécution pour registres de chaîne de blocs
CN109831487B (zh) 分片文件验证方法及终端设备
US11671262B2 (en) Asynchronously determining relational data integrity using cryptographic data structures
US11593029B1 (en) Identifying a parent event associated with child error states
US11563560B2 (en) Blockchain-based data evidence storage method and apparatus
US11243839B1 (en) Audit file generation in a dispersed storage network
WO2020224235A1 (fr) Procédé et appareil de transactions entre chaînes, dispositif, et support de stockage
WO2021174882A1 (fr) Procédé et appareil de vérification de données, dispositif informatique et support d'enregistrement lisible
CN111641563B (zh) 基于分布式场景的流量自适应方法与系统
CN112511316B (zh) 单点登录接入方法、装置、计算机设备及可读存储介质
WO2020224100A1 (fr) Système, procédé, et appareil de traitement de fichier de configuration de chaîne de blocs, et support d'informations
US20180121669A1 (en) Extended security scrutiny of data access requests in a dispersed storage network
CN111722946A (zh) 分布式事务处理方法、装置、计算机设备及可读存储介质
WO2019061667A1 (fr) Appareil électronique, procédé et système de traitement de données, et support de stockage lisible par ordinateur
CN111698227B (zh) 信息同步管理方法、装置、计算机系统及可读存储介质
CN112052256A (zh) 多版本请求返回方法、装置、计算机设备及可读存储介质
CN114925044A (zh) 基于云存储的数据同步方法、装置、设备及存储介质
CN113420050A (zh) 数据查询管理方法、装置、计算机设备及可读存储介质
CN116136844A (zh) 实体标识信息的生成方法、装置、介质及电子设备
CN115630409B (zh) 一种数据的存储控制方法及装置
CN113434505B (zh) 交易信息属性检索方法、装置、计算机设备及存储介质
CN112019350B (zh) 区块链的区块验证方法及装置
CN114650252B (zh) 基于企业服务总线的路由方法、装置及计算机设备
US20240354192A1 (en) Storage Network with Audit Records Aggregation and Methods for Use Therewith
US20240154945A1 (en) System and method for third party service integration into a browser client application

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20923295

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20923295

Country of ref document: EP

Kind code of ref document: A1