WO2021008400A1 - Procédé de traitement de données sur chaîne de blocs, appareil, et support d'informations - Google Patents

Procédé de traitement de données sur chaîne de blocs, appareil, et support d'informations Download PDF

Info

Publication number
WO2021008400A1
WO2021008400A1 PCT/CN2020/100382 CN2020100382W WO2021008400A1 WO 2021008400 A1 WO2021008400 A1 WO 2021008400A1 CN 2020100382 W CN2020100382 W CN 2020100382W WO 2021008400 A1 WO2021008400 A1 WO 2021008400A1
Authority
WO
WIPO (PCT)
Prior art keywords
hotspot
unit
data
updated
data information
Prior art date
Application number
PCT/CN2020/100382
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 WO2021008400A1 publication Critical patent/WO2021008400A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/273—Asynchronous replication or reconciliation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • This application relates to the technical field of financial technology (Fintech), and in particular to blockchain-based data batch processing methods, devices, equipment, and computer-readable storage media.
  • the user can use his payment account to pay the amount of the product to the secured transaction intermediate account.
  • the secured transaction intermediate account will be involved.
  • the secured transaction intermediate account will become a hotspot.
  • Existing hotspot units keep accounts in a synchronous mode, that is, when performing transactions, they need to lock/unlock the hotspot account. This makes a large number of concurrent data processing requests need to be queued up and waited to be processed by the hotspot account, resulting in a large number of concurrent data processing requests being stringed Banking greatly reduces the efficiency of data processing.
  • the main purpose of this application is to propose a block chain-based data batch processing method, device, equipment, and computer-readable storage medium, aiming to solve the technical problem of low data processing efficiency in the existing serial processing method of hotspot units .
  • the data batch processing method includes the following steps:
  • each data recording request unit in the multiple blockchain nodes corresponding to the batch data record After receiving the batch data recording request, determine each data recording request unit in the multiple blockchain nodes corresponding to the batch data record, and determine the hot spot in each data recording request unit according to the preset hot spot configuration table unit;
  • the obtaining the change data information corresponding to the hotspot unit, and synchronize the change data information corresponding to the hotspot unit to the hotspot node to which the hotspot unit belongs, and generate the data to be changed corresponding to each hotspot node The specific steps of the list include:
  • the unsynchronized data in the list of data to be synchronized is fragmented, and the fragmented unsynchronized data is synchronized to the hotspot node to which the corresponding hotspot unit belongs, Generate a list of data to be changed corresponding to each hotspot node.
  • the steps of performing other non-numerical processing operations on each data record request unit based on the list of all changed data after the value is updated, and processing the data records in batches specifically include:
  • the hotspot unit corresponding to each change data information is updated respectively, and the hotspot configuration is updated according to the updated unit value corresponding to each hotspot unit The unit status corresponding to each hotspot unit described in the table.
  • the hotspot unit corresponding to each change data information is updated with a numerical value according to the respective change data information and the unit status of the corresponding hotspot unit, and the updated value corresponding to each hotspot unit is updated.
  • Unit value the step of updating the unit status corresponding to each hotspot unit in the hotspot configuration table specifically includes:
  • Judging whether the hotspot unit to be updated can update the value according to the value to be updated corresponding to the data information to be updated and the value status of the unit;
  • hotspot unit to be updated can perform a value update, lock the hotspot unit to be updated, modify the pending update state of the data information to be updated to the updated state, and perform a numerical value on the hotspot unit to be updated Update and update the unit value status corresponding to the hotspot unit to be updated in the hotspot configuration table.
  • the method further includes:
  • a corresponding transaction failure reminder message is generated according to the hot-spot unit to be updated.
  • each data recording request unit of the multiple blockchain nodes corresponding to the batch data record after receiving the batch data recording request, determine each data recording request unit of the multiple blockchain nodes corresponding to the batch data record, and according to a preset hotspot configuration table, After the step of determining the hotspot unit in each data recording request unit, it also includes:
  • each data recording request unit If the hotspot unit does not exist in each data recording request unit, the corresponding value of each data recording request unit is synchronously updated according to the preset general mode, and other non-numerical processing operations are performed on each data recording request unit To process the data records in batches.
  • the hotspot configuration table acquiring the hotspot unit status corresponding to the hotspot unit, and judging whether the hotspot unit can allow value updating according to the hotspot unit status;
  • hotspot unit allows value updating, execute: obtain the change data information corresponding to the hotspot unit, and synchronize the change data information corresponding to the hotspot unit to the hotspot node to which the hotspot unit belongs to generate each hotspot node Steps corresponding to the list of data to be changed;
  • the hot-spot unit is updated numerically, and other non-hot-spot units in the hot-spot node and other non-hot-spot units in the other non-hot-spot nodes are numerically updated Before the update steps, it also includes:
  • deduplication processing is performed on each change data information in the to-be-changed data list according to the repeated change data information identifier.
  • the present application also provides a block chain-based data batch processing device, which includes:
  • the hotspot unit determination module is used to determine each data record request unit of the multiple blockchain nodes corresponding to the batch data record after receiving the batch data record request, and set the data record request unit in each of the multiple blockchain nodes according to the preset hotspot configuration table. Determine the hotspot unit in the data record request unit;
  • the data list generating module is used to obtain the change data information corresponding to the hotspot unit, and synchronize the change data information corresponding to the hotspot unit to the hotspot node to which the hotspot unit belongs, and generate a list of data to be changed corresponding to each hotspot node ;
  • the unit value update module is used to update the value of the hotspot unit according to the list of data to be changed, and update the values of other non-hotspot units in the hotspot node and other non-hotspot units in other non-hotspot nodes ;
  • the value update processing module is used to perform other non-numerical processing operations on each data record request unit according to the list of all changed data after the value update to process the data records in batches.
  • the data list generating module specifically includes:
  • a synchronization list generating unit configured to obtain the changed data information corresponding to the hotspot unit, and generate a list of data to be synchronized
  • the synchronized data synchronization unit is configured to divide the unsynchronized data in the to-be-synchronized data list into fragments when there is unsynchronized data in the to-be-synchronized data list, and synchronize the fragmented unsynchronized data to the corresponding
  • the hotspot node to which the hotspot unit belongs generates a list of data to be changed corresponding to each hotspot node.
  • the value update processing module specifically includes:
  • the unit status obtaining subunit is used to obtain each change data information in the data list to be changed according to the data list to be changed, and obtain the hotspot unit corresponding to each change data information according to the hotspot configuration table The unit status;
  • the unit value update subunit is used to update the values of the hotspot units corresponding to the respective change data information according to the respective change data information and the unit status of the corresponding hotspot unit, and to update the values according to the updated data corresponding to each hotspot unit
  • the unit value updates the unit status corresponding to each hotspot unit in the hotspot configuration table.
  • the unit value update subunit is further used for:
  • Judging whether the hotspot unit to be updated can update the value according to the value to be updated corresponding to the data information to be updated and the value status of the unit;
  • hotspot unit to be updated can perform a value update, lock the hotspot unit to be updated, modify the pending update state of the data information to be updated to the updated state, and perform a numerical value on the hotspot unit to be updated Update and update the unit value status corresponding to the hotspot unit to be updated in the hotspot configuration table.
  • the block chain-based data batch processing device further includes a modified data deduplication module, and the modified data deduplication module is configured to:
  • deduplication processing is performed on each change data information in the to-be-changed data list according to the repeated change data information identifier.
  • this application also provides a block chain-based data batch processing device.
  • the block chain-based data batch processing device includes: a memory, a processor, and a storage A block chain-based data batch processing program running on the processor, and the block chain-based data batch processing program is executed by the processor to realize the above-mentioned blockchain-based data batch processing method step.
  • the present application also provides a computer-readable storage medium on which a blockchain-based data batch processing program is stored, and the blockchain-based data batch processing program is stored on the computer-readable storage medium.
  • the steps of the block chain-based data batch processing method as described above are realized.
  • this application determines each data record request unit in the multiple blockchain nodes corresponding to the batch data record, and according to the preset hotspot configuration table, in each data record request unit Determine the hotspot unit; obtain the change data information corresponding to the hotspot unit, and synchronize the change data information corresponding to the hotspot unit to the hotspot node to which the hotspot unit belongs, and generate a list of data to be changed corresponding to each hotspot node; State the list of data to be changed, update the values of the hotspot units, and update the values of other non-hotspot units in the hotspot node and other non-hotspot units in other non-hotspot nodes; according to all the changed data after the value update List, perform other non-numerical processing operations on each data record request unit to process the data records in batches.
  • this application processes data recording requests in batches, synchronizes the change data information corresponding to the hotspot unit to the data list to be changed of the hotspot node, synchronously records the changed data information of the hotspot unit, and then performs the hotspot unit according to the list of data to be changed Asynchronous update of changed data values and other non-numerical processing operations.
  • the data processing efficiency of the hotspot unit is improved, the success rate of data modification of the multi-node unit is improved, and the technical problem of low data processing efficiency in the existing serial processing method of the hotspot unit is solved.
  • FIG. 1 is a schematic diagram of a device structure of a hardware operating environment involved in a solution of an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a first embodiment of a data batch processing method based on blockchain in this application.
  • FIG. 1 is a schematic diagram of the device structure of the hardware operating environment involved in the solution of the embodiment of the present application.
  • the block chain-based data batch processing device in the embodiment of the present application may be a PC or a server device, on which a Java virtual machine runs.
  • the block chain-based data batch processing device may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002.
  • the communication bus 1002 is used to implement connection and communication between these components.
  • the user interface 1003 may include a display screen (Display) and an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface.
  • the network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).
  • the memory 1005 can be a high-speed RAM memory or a stable memory (non-volatile memory), such as disk storage.
  • the memory 1005 may also be a storage device independent of the foregoing processor 1001.
  • FIG. 1 does not constitute a limitation on the device, and may include more or fewer components than those shown in the figure, or a combination of certain components, or different component arrangements.
  • the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a data batch processing program based on the blockchain.
  • the network interface 1004 is mainly used to connect to a back-end server and perform data communication with the back-end server;
  • the user interface 1003 is mainly used to connect to a client (user side) and perform data communication with the client;
  • the processor 1001 can be used to call a blockchain-based data batch processing program stored in the memory 1005, and execute the following operations in the blockchain-based data batch processing method.
  • Fig. 2 is a schematic flow chart of the first embodiment of a blockchain-based data batch processing method according to this application.
  • the blockchain-based data batch processing method includes:
  • Step S10 after receiving the batch data recording request, determine each data recording request unit in the multiple blockchain nodes corresponding to the batch data record, and according to the preset hotspot configuration table, in each data recording request unit Determine the hotspot unit;
  • the data recording request is a billing request
  • the data recording request unit is a billing request account
  • the hotspot unit is a hotspot account.
  • the account becomes a hot account.
  • the user can use his payment account to pay the amount of the product to the secured transaction intermediate account.
  • the secured transaction intermediate account will be involved.
  • the secured transaction intermediate account will become a hot account.
  • Hotspot accounts are accounted in a synchronous mode, that is, when transactions are executed, hotspot accounts need to be locked/unlocked, which makes a large number of concurrent transaction requests need to be queued and waited to be processed by hotspot accounts, resulting in a large number of concurrent transaction requests being serialized , Which greatly reduces the efficiency of data processing.
  • batch processing of billing requests is performed, the transaction flow corresponding to the hot account is synchronized to the pending flow list of the hot node, the transaction flow of the hot account is synchronously recorded, and then the hot account is performed according to the pending flow list Asynchronous update of balance and other non-balance processing operations.
  • the hotspot configuration table is preset, including the node routing information to which the hotspot account belongs, the allowed processing type of the hotspot account (debit hotspot, credit hotspot), current control status (judicial, bank control), account balance corresponding to the alert status, and alert Recover account balance threshold, pause status indicator, pause recovery account balance threshold, etc., and synchronize the hotspot configuration table to each node.
  • the allowed processing type of the hotspot account debit hotspot, credit hotspot
  • current control status judicial, bank control
  • account balance corresponding to the alert status and alert Recover account balance threshold, pause status indicator, pause recovery account balance threshold, etc.
  • the bookkeeping transaction request will be sent to the hotspot node, that is, the node to which the hot account belongs; if the two parties involved in the bookkeeping involve multiple nodes, the transaction request will be sent to the non-hotspot node to reduce synchronization Operation, avoid cross-node calls. If both parties to the account involve multiple nodes and both are hot nodes, the transaction is sent to any hot node.
  • the hotspot configuration table is checked to confirm whether there is a hotspot account in each billing request account. And register the transaction elements in the bookkeeping transaction of the hot account, such as the bookkeeping type, borrowing or transferring amount, etc.
  • step S10 it further includes:
  • each data recording request unit If the hotspot unit does not exist in each data recording request unit, the corresponding value of each data recording request unit is synchronously updated according to the preset general mode, and other non-numerical processing operations are performed on each data recording request unit To process the data records in batches.
  • the value is the balance
  • the other non-numerical processing operations are other non-balance processing operations. If there is no hot account in each billing request account, the general mode is processed according to the synchronous real-time balance update, that is, the account balance corresponding to each billing request account and other non-balance processing operations are updated in real time according to the billing request.
  • Step S20 Obtain the changed data information corresponding to the hotspot unit, and synchronize the changed data information corresponding to the hotspot unit to the hotspot node to which the hotspot unit belongs, and generate a list of data to be changed corresponding to each hotspot node;
  • the changed data information is a transaction flow
  • the list of data to be changed is a flow list to be processed. Get the transaction flow corresponding to each hotspot account, synchronize the transaction flow corresponding to each hotspot account in each hotspot node to their respective hotspot node, and add the transaction flow corresponding to all hotspot accounts under each hotspot node to each hotspot
  • step S20 it further includes:
  • the hotspot configuration table acquiring the hotspot unit status corresponding to the hotspot unit, and judging whether the hotspot unit can allow value updating according to the hotspot unit status;
  • step S20 If the hotspot unit allows value updating, perform: step S20;
  • the hotspot unit status is the hotspot account status
  • the value update is the balance update, that is, it is judged whether the hotspot account can conduct transactions.
  • the billing request includes multiple types of billing services.
  • the hotspot accounts are respectively set to: allow debit hotspots, allow credit hotspots, or both lending hotspots.
  • the hotspot configuration table also includes control information such as whether each hotspot account is judicially frozen.
  • the hotspot account status corresponding to the hotspot account is determined according to the hotspot configuration table, such as whether this type of hotspot is allowed, or whether the account of the hotspot account is in a controlled state, etc., to determine whether each hotspot account is allowed to conduct transactions, if If allowed, step S20 is executed to obtain the to-be-processed pipeline corresponding to each hotspot account. If not allowed, a reminder message of transaction failure is generated.
  • Step S30 according to the list of data to be changed, update the value of the hot spot unit, and update the value of other non-hot spot units in the hot spot node and other non-hot spot units in other non-hot spot nodes;
  • the data list to be changed is the pipeline list to be processed, and the other non-hot-spot units are other non-hot-spot accounts.
  • the transaction summary of the hotspot account is performed and the account balance of the hotspot account is updated.
  • the billing status of each hotspot account in the hotspot configuration table is further updated according to the updated account balance of each hotspot account.
  • synchronize the updated hotspot configuration table to all other nodes. As a result, the time difference between the hot account balance update and the corresponding status update is further reduced, so that the balance update and synchronization status change are more timely.
  • Step S40 Perform other non-numerical processing operations on each data record request unit according to the list of all changed data after the value is updated to process the data records in batches.
  • the all changed data list is a complete flow list
  • each data record request unit is each billing request account
  • the batch processing of the data records is the batch completion of the billing request.
  • other non-balance processing operations include inserting, deleting, and modifying multiple records, such as transaction details and accounting parts.
  • the corresponding transaction details and accounting calculations must also be registered, which takes a long time, so the balance is updated Operation and non-balance processing operations are separated to reduce the time difference of balance update, make balance update faster, and state synchronization more accurate.
  • each data recording request unit in the multiple blockchain nodes corresponding to the batch data recording is determined, and according to the preset hotspot configuration table, the data recording request unit Determine the hotspot unit; obtain the change data information corresponding to the hotspot unit, and synchronize the change data information corresponding to the hotspot unit to the hotspot node to which the hotspot unit belongs, and generate a list of data to be changed corresponding to each hotspot node; For the list of data to be changed, update the values of the hotspot units, and update the values of other non-hotspot units in the hotspot node and other non-hotspot units in other non-hotspot nodes; according to all the changes after the value update In the data list, other non-numerical processing operations are performed on each data record request unit to process the data records in batches.
  • this application processes data recording requests in batches, synchronizes the change data information corresponding to the hotspot unit to the data list to be changed of the hotspot node, synchronously records the changed data information of the hotspot unit, and then performs the hotspot unit according to the list of data to be changed Asynchronous update of changed data values and other non-numerical processing operations.
  • the data processing efficiency of the hotspot unit is improved, the success rate of data modification of the multi-node unit is improved, and the technical problem of low data processing efficiency in the existing serial processing method of the hotspot unit is solved.
  • step S20 specifically includes:
  • the unsynchronized data in the list of data to be synchronized is fragmented, and the fragmented unsynchronized data is synchronized to the hotspot node to which the corresponding hotspot unit belongs, Generate a list of data to be changed corresponding to each hotspot node.
  • the list of data to be synchronized is a pipeline to be synchronized
  • the unsynchronized data is an unsynchronized pipeline
  • the list of data to be changed is a pipeline to be processed.
  • the pending pipeline corresponding to each hot account is recorded, and a list of pipelines to be synchronized is generated, including transaction pipelines corresponding to all hot accounts to be synchronized to their own nodes, wherein each pipeline to be synchronized in the pipeline list to be synchronized
  • the initial state is unsynchronized.
  • the hotspot node then localizes the received transaction flow and stores it in the to-be-processed flow table, where the billing node directly calls the service through the message bus to perform flow synchronization and failed synchronization retry.
  • step S30 specifically includes:
  • the hotspot unit corresponding to each change data information is updated respectively, and the hotspot configuration is updated according to the updated unit value corresponding to each hotspot unit The unit status corresponding to each hotspot unit described in the table.
  • each change data information is each transaction flow
  • the unit status of the hotspot unit is the account status of the hotspot account
  • the unit value is the account balance.
  • the hotspot configuration table is used as the basis for checking the accounting type permission and accounting status in the accounting synchronization process. There are three situations that will cause the hotspot account status to change and need to be synchronized:
  • the status change caused by the account balance update that is, after each hotspot account performs the balance update operation, the account status of each hotspot account needs to be updated, such as the account balance value of each hotspot account is lower than the warning threshold, modify the configuration In the early warning state of the table status, the account balance is lower than the deactivation threshold, modify the deactivated state in the configuration table status.
  • the balance is higher than the early warning recovery threshold, and the normal state in the state of the configuration table is modified.
  • the hotspot units corresponding to the respective change data information are respectively updated with values, and according to the updated unit values corresponding to each hotspot unit,
  • the step of updating the unit status corresponding to each hotspot unit in the hotspot configuration table specifically includes:
  • Judging whether the hotspot unit to be updated can update the value according to the value to be updated corresponding to the data information to be updated and the value status of the unit;
  • hotspot unit to be updated can perform a value update, lock the hotspot unit to be updated, modify the pending update state of the data information to be updated to the updated state, and perform a numerical value on the hotspot unit to be updated Update and update the unit value status corresponding to the hotspot unit to be updated in the hotspot configuration table.
  • a corresponding transaction failure reminder message is generated according to the hot-spot unit to be updated.
  • the hotspot account before updating the balance of the hotspot account according to the transaction flow corresponding to each hotspot account, it is necessary to determine whether the hotspot account can perform a transaction operation for the amount corresponding to the transaction flow. Specifically, the transaction flow details in the synchronously recorded transaction flow are sequentially obtained, that is, each transaction flow is sequentially used as the flow to be updated, and the hot accounts corresponding to the transaction flow details are correspondingly processed. The hot account corresponding to the transaction flow details is used as the hot account to be updated corresponding to the brother's to be updated flow.
  • the amount to be updated corresponding to the flow to be updated that is, the transaction amount
  • the account balance status of the hot account to be updated such as a suspended status, a balance warning status, or a normal status (balance sufficient status). It is judged whether the balance of the hot account to be updated can be updated, that is, it is judged whether the amount to be updated is less than the account balance of the hot account to be updated.
  • the balance update operation can be performed, the hotspot account to be updated is locked, and the pending update status of the flow to be updated is changed to already Update the status, update the balance of the hotspot account to be updated, and update the account balance status corresponding to the hotspot account to be updated in the hotspot configuration table. If the amount to be updated is greater than the account balance of the hotspot account to be updated, the balance update operation cannot be performed, and a transaction failure reminder message corresponding to the hotspot account is generated.
  • the method before the step S30, the method further includes:
  • deduplication processing is performed on each change data information in the to-be-changed data list according to the repeated change data information identifier.
  • each change data information identifier is each transaction flow identifier
  • the repeated change data information identifier is a repeated flow identifier
  • each change data information is each transaction flow identifier.
  • each asynchronous task is deduplicated and failed retry processing.
  • asynchronous tasks include balance updates, other non-balance processing operations, etc.
  • each transaction flow identifier in the pending flow list where each transaction The flow corresponds to a unique transaction flow identifier, such as a trading flow number or a trading flow name. It is judged whether there is a repeated flow mark in each transaction flow mark, that is, it is judged whether there are two or more identical transaction flow marks in each transaction flow mark. If there is a repeated flow mark in each transaction flow mark, the repeated flow mark corresponding to the repeated flow mark is de-duplicated, so that each trading flow in the pending flow list is a unique trading flow. In a specific embodiment, when it is detected that the balance update task corresponding to each transaction flow in the pending flow list has failed, the balance update task corresponding to the transaction flow is restarted and executed according to a preset time interval.
  • the present application also provides a block chain-based data batch processing device, which includes:
  • the hotspot unit determination module is used to determine each data record request unit of the multiple blockchain nodes corresponding to the batch data record after receiving the batch data record request, and according to the preset hotspot configuration table, set Determine the hotspot unit in the data record request unit;
  • the data list generating module is used to obtain the change data information corresponding to the hotspot unit, and synchronize the change data information corresponding to the hotspot unit to the hotspot node to which the hotspot unit belongs, and generate a list of data to be changed corresponding to each hotspot node ;
  • the unit value update module is used to update the value of the hotspot unit according to the list of data to be changed, and update the values of other non-hotspot units in the hotspot node and other non-hotspot units in other non-hotspot nodes ;
  • the value update processing module is used to perform other non-numerical processing operations on each data record request unit according to the list of all changed data after the value update to process the data records in batches.
  • the data list generating module specifically includes:
  • a synchronization list generating unit configured to obtain the changed data information corresponding to the hotspot unit, and generate a list of data to be synchronized
  • the synchronized data synchronization unit is configured to divide the unsynchronized data in the to-be-synchronized data list into fragments when there is unsynchronized data in the to-be-synchronized data list, and synchronize the fragmented unsynchronized data to the corresponding
  • the hotspot node to which the hotspot unit belongs generates a list of data to be changed corresponding to each hotspot node.
  • the numerical value update processing module specifically includes:
  • the unit status obtaining subunit is used to obtain each change data information in the data list to be changed according to the data list to be changed, and obtain the hotspot unit corresponding to each change data information according to the hotspot configuration table The unit status;
  • the unit value update subunit is used to update the values of the hotspot units corresponding to the respective change data information according to the respective change data information and the unit status of the corresponding hotspot unit, and to update the values according to the updated data corresponding to each hotspot unit
  • the unit value updates the unit status corresponding to each hotspot unit in the hotspot configuration table.
  • unit value update subunit is also used for:
  • Judging whether the hotspot unit to be updated can update the value according to the value to be updated corresponding to the data information to be updated and the value status of the unit;
  • hotspot unit to be updated can perform a value update, lock the hotspot unit to be updated, modify the pending update state of the data information to be updated to the updated state, and perform a numerical value on the hotspot unit to be updated Update and update the unit value status corresponding to the hotspot unit to be updated in the hotspot configuration table.
  • the block chain-based data batch processing device further includes a modified data deduplication module, and the modified data deduplication module is used for:
  • deduplication processing is performed on each change data information in the to-be-changed data list according to the repeated change data information identifier.
  • the block chain-based data batch processing device further includes a hotspot unit identification module, and the hotspot unit identification module is used for:
  • each data recording request unit If the hotspot unit does not exist in each data recording request unit, the corresponding value of each data recording request unit is synchronously updated according to the preset general mode, and other non-numerical processing operations are performed on each data recording request unit To process the data records in batches.
  • the block chain-based data batch processing device further includes a unit value judgment module, and the unit value judgment module is configured to:
  • the hotspot configuration table acquiring the hotspot unit status corresponding to the hotspot unit, and judging whether the hotspot unit can allow value updating according to the hotspot unit status;
  • hotspot unit allows value updating, execute: obtain the change data information corresponding to the hotspot unit, and synchronize the change data information corresponding to the hotspot unit to the hotspot node to which the hotspot unit belongs to generate each hotspot node Steps corresponding to the list of data to be changed;
  • the application also provides a computer-readable storage medium.
  • the computer-readable storage medium of this application stores a block chain-based data batch processing program, and the block chain-based data batch processing program is executed by a processor to realize the block chain-based data batch processing method as described above A step of.
  • the method implemented when the block chain-based data batch processing program running on the processor is executed can refer to the various embodiments of the block chain-based data batch processing method of this application, which will not be repeated here.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Accounting & Taxation (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Finance (AREA)
  • Computing Systems (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé, un appareil et un dispositif de traitement de données sur chaîne de blocs, et un support d'informations. Le procédé consiste : après réception d'une demande d'enregistrement de données par lots, à déterminer chaque unité de demande d'enregistrement de données dans de multiples nœuds de chaîne de blocs correspondant à un enregistrement de données par lots, et à déterminer une unité de point d'accès dans chaque unité de demande d'enregistrement de données en fonction d'une table de configuration de point d'accès (S10) ; à acquérir des informations de données modifiées correspondant à l'unité de point d'accès, à synchroniser les informations de données modifiées correspondant à l'unité de point d'accès, avec un nœud de point d'accès auquel appartient l'unité de point d'accès, et à générer une liste de données à modifier correspondant à chaque nœud de point d'accès (S20) ; à mettre à jour la valeur de l'unité de point d'accès en fonction de la liste de données à modifier, et à mettre à jour les valeurs d'unités autres que de point d'accès dans le nœud de point d'accès et les valeurs d'unités autres que de point d'accès dans des nœuds autres que de point d'accès (S30) ; et à effectuer d'autres tâches de traitement non numériques sur chaque unité de demande d'enregistrement de données en fonction de toutes les listes de données modifiées ayant été soumises à une mise à jour de valeur, de manière à traiter les enregistrements de données par lots (S40). Le procédé consiste : après réception d'une demande d'enregistrement de données par lots, à déterminer chaque unité de demande d'enregistrement de données dans de multiples nœuds de chaîne de blocs correspondant à un enregistrement de données par lots, et à déterminer une unité de point d'accès dans chaque unité de demande d'enregistrement de données en fonction d'une table de configuration de point d'accès (S10) ; à acquérir des informations de données modifiées correspondant à l'unité de point d'accès, à synchroniser les informations de données modifiées correspondant à l'unité de point d'accès, avec un nœud de point d'accès auquel appartient l'unité de point d'accès, et à générer une liste de données à modifier correspondant à chaque nœud de point d'accès (S20) ; à mettre à jour la valeur de l'unité de point d'accès en fonction de la liste de données à modifier, et à mettre à jour les valeurs d'unités autres que de point d'accès dans le nœud de point d'accès et les valeurs d'unités autres que de point d'accès dans des nœuds autres que de point d'accès (S30) ; et à effectuer d'autres tâches de traitement non numériques sur chaque unité de demande d'enregistrement de données en fonction de toutes les listes de données modifiées ayant été soumises à une mise à jour de valeur, de manière à traiter les enregistrements de données par lots (S40).
PCT/CN2020/100382 2019-07-12 2020-07-06 Procédé de traitement de données sur chaîne de blocs, appareil, et support d'informations WO2021008400A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910633067.1A CN110363663B (zh) 2019-07-12 2019-07-12 基于区块链的数据批量处理方法、装置、设备及存储介质
CN201910633067.1 2019-07-12

Publications (1)

Publication Number Publication Date
WO2021008400A1 true WO2021008400A1 (fr) 2021-01-21

Family

ID=68219354

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/100382 WO2021008400A1 (fr) 2019-07-12 2020-07-06 Procédé de traitement de données sur chaîne de blocs, appareil, et support d'informations

Country Status (2)

Country Link
CN (1) CN110363663B (fr)
WO (1) WO2021008400A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113034254A (zh) * 2021-03-19 2021-06-25 北京字跳网络技术有限公司 数据处理方法、装置和电子设备

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110363663B (zh) * 2019-07-12 2023-08-22 深圳前海微众银行股份有限公司 基于区块链的数据批量处理方法、装置、设备及存储介质
CN111211876B (zh) * 2020-01-02 2021-10-12 支付宝(杭州)信息技术有限公司 发送针对数据请求的应答消息的方法及装置、区块链系统
CN111984733A (zh) * 2020-09-03 2020-11-24 深圳壹账通智能科技有限公司 基于区块链的数据传输方法、装置及存储介质
CN112487010B (zh) * 2020-12-14 2024-02-23 深圳前海微众银行股份有限公司 一种区块链用户数据表更新方法、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107358420A (zh) * 2017-06-09 2017-11-17 北京博晨技术有限公司 用于实现热点账户的区块链系统以及实现热点账户的方法
US20180054491A1 (en) * 2016-08-19 2018-02-22 Ca, Inc. Maintaining distributed state among stateless service clients
CN108492183A (zh) * 2018-03-29 2018-09-04 深圳前海微众银行股份有限公司 区块链的账户交易方法、系统和计算机可读存储介质
CN109040029A (zh) * 2018-07-13 2018-12-18 上海点融信息科技有限责任公司 在区块链中执行事务的方法和装置
CN110363663A (zh) * 2019-07-12 2019-10-22 深圳前海微众银行股份有限公司 基于区块链的数据批量处理方法、装置、设备及存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170132625A1 (en) * 2015-11-05 2017-05-11 Mastercard International Incorporated Method and system for use of a blockchain in a transaction processing network
CN108566420A (zh) * 2018-03-29 2018-09-21 上海点融信息科技有限责任公司 用于区块链的数据处理方法、设备及计算机可读存储介质
CN109446208A (zh) * 2018-09-03 2019-03-08 深圳壹账通智能科技有限公司 一种数据存储方法、计算机可读存储介质及服务器
CN109274752A (zh) * 2018-10-10 2019-01-25 腾讯科技（深圳）有限公司 区块链数据的访问方法及装置、电子设备、存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180054491A1 (en) * 2016-08-19 2018-02-22 Ca, Inc. Maintaining distributed state among stateless service clients
CN107358420A (zh) * 2017-06-09 2017-11-17 北京博晨技术有限公司 用于实现热点账户的区块链系统以及实现热点账户的方法
CN108492183A (zh) * 2018-03-29 2018-09-04 深圳前海微众银行股份有限公司 区块链的账户交易方法、系统和计算机可读存储介质
CN109040029A (zh) * 2018-07-13 2018-12-18 上海点融信息科技有限责任公司 在区块链中执行事务的方法和装置
CN110363663A (zh) * 2019-07-12 2019-10-22 深圳前海微众银行股份有限公司 基于区块链的数据批量处理方法、装置、设备及存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113034254A (zh) * 2021-03-19 2021-06-25 北京字跳网络技术有限公司 数据处理方法、装置和电子设备
CN113034254B (zh) * 2021-03-19 2024-05-14 北京字跳网络技术有限公司 数据处理方法、装置和电子设备

Also Published As

Publication number Publication date
CN110363663A (zh) 2019-10-22
CN110363663B (zh) 2023-08-22

Similar Documents

Publication Publication Date Title
WO2021008400A1 (fr) Procédé de traitement de données sur chaîne de blocs, appareil, et support d'informations
TWI679874B (zh) 跨區塊鏈的認證方法及裝置、電子設備
US11902450B2 (en) Blockchain generation method and system, and related device
TW201943250A (zh) 跨區塊鏈的認證方法及裝置、電子設備
US20190171739A1 (en) Detecting phantom items in distributed replicated database
WO2020134895A1 (fr) Procédé et appareil comptabilité à base de chaîne de blocs, et dispositif électronique
TW201935384A (zh) 資產管理方法及裝置、電子設備
TW201935375A (zh) 資產管理方法及裝置、電子設備
WO2019097322A1 (fr) Optimisation de la réalisation d'une transaction volumineuse sur une chaîne de blocs
CN110569309A (zh) 用于实现区块链的设备、方法、系统以及介质
EP3905172A1 (fr) Procédé et appareil d'annulation de facture fondés sur une chaîne de blocs et dispositif électronique
CN112075062A (zh) 区块链网络中的自动提交交易管理
CN108319617A (zh) 确定数据库主从差异的方法、装置及切换控制方法、装置
WO2020088072A1 (fr) Procédé, appareil et système de traitement de données de basculement
TWI736608B (zh) 便於支付主體擴展的方法和裝置
WO2023207529A1 (fr) Procédé et appareil de traitement de données, dispositif, support et produit
KR20190086301A (ko) 블록 체인을 이용한 분산 데이터베이스 시스템 및 방법
US20230259930A1 (en) Cross-chain transaction processing method and apparatus, electronic device, and storage medium
JP7460348B2 (ja) ブロックチェーンの拡張を可能にするトランザクション処理システムおよび方法
US11881996B2 (en) Input and output for target device communication
CN116366353A (zh) 基于x86平台的业务登录方法、装置、介质及平台
CN107066315B (zh) 业务调用方法及装置
CN110648228A (zh) 一种通过链上数字货币结算的链上资产转移系统和方法
CN107729156B (zh) 一种应用冲突解决方法及装置
TWM617950U (zh) 服務系統

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: 20840163

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: 20840163

Country of ref document: EP

Kind code of ref document: A1