WO2018157778A1 - 写入区块链业务数据的方法和装置及业务子集合确定方法 - Google Patents
写入区块链业务数据的方法和装置及业务子集合确定方法 Download PDFInfo
- Publication number
- WO2018157778A1 WO2018157778A1 PCT/CN2018/077286 CN2018077286W WO2018157778A1 WO 2018157778 A1 WO2018157778 A1 WO 2018157778A1 CN 2018077286 W CN2018077286 W CN 2018077286W WO 2018157778 A1 WO2018157778 A1 WO 2018157778A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- data
- service data
- sub
- level
- Prior art date
Links
Images
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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
-
- 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/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24568—Data stream processing; Continuous queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/22—Microcontrol or microprogram arrangements
- G06F9/28—Enhancement of operational speed, e.g. by using several microcontrol devices operating in parallel
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4812—Task transfer initiation or dispatching by interrupt, e.g. masked
- G06F9/4831—Task transfer initiation or dispatching by interrupt, e.g. masked with variable priority
- G06F9/4837—Task transfer initiation or dispatching by interrupt, e.g. masked with variable priority time dependent
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
- H04L9/0637—Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
Definitions
- the present application relates to the field of computer technologies, and in particular, to a method and apparatus for writing blockchain service data, and a service subset determination method for blockchain service data.
- blockchain technology also known as distributed ledger technology
- distributed ledger technology is favored for its decentralization, transparency, non-tampering, trustworthiness, etc., in smart contracts, securities trading, e-commerce, Internet of Things, social communication, file storage, proof of existence, authentication, equity crowdfunding and many other fields are widely used.
- blockchain technology is a decentralized distributed database technology.
- Each piece of data in the blockchain is broadcast to the blockchain nodes of the entire network, and each node stores the full amount of consistent data.
- Blockchain technology requires that the state of each node be consistent, including the state of the database.
- the order of executing blockchain transactions is ordered, and consistent in each node, each node executes transactions in this order, completing transaction verification, implementation, data entry and so on.
- a timestamp is created, the transaction is written into the transaction pool, and the transaction is sorted according to the timestamp.
- mining the transaction is executed in the order of the transaction timestamp. And update the account information after executing each transaction to the database to update the database account status.
- the embodiments of the present application provide a method and apparatus for writing blockchain service data, aiming at reducing the cost required for improving data processing execution efficiency and improving scalability.
- the embodiment of the present application further provides a service sub-set determining method for blockchain service data, which aims to reasonably divide the service data, thereby reducing the cost required for improving the data processing execution efficiency and improving the scalability.
- a method for writing blockchain service data includes:
- Each of the subsets of services is executed in parallel to write the results of the execution to the blockchain.
- the service sub-group to which the service data belongs is determined according to the service type and/or the data change scope of the service data, and specifically includes:
- performing each of the service sub-collections in parallel includes:
- Each of the service sub-collections is executed in parallel using a multi-thread or machine cluster.
- the method specifically includes:
- the service data included in the service subset is serially executed according to the time sequence corresponding to the time stamp.
- the service sub-group to which the service data belongs is determined according to the service type of the service data, which specifically includes:
- the service data of the same service type is divided into the same service sub-set according to the service type of the service data, and the service data with different service types are divided into different service sub-sets.
- determining the service sub-set to which the service data belongs according to the data change scope of the service data specifically includes:
- the business data in which the data change scope has an intersection is divided into the same service sub-collection, and the service data in which the data change scope is not intersected is divided into different service sub-sets.
- the service data with the data change scope intersected is divided into the same service sub-collection, and the data is changed.
- Business data with no intersections is divided into different business sub-collections, including:
- the first service data is added to the first service subset
- the first service sub-set is any service sub-set of the service sub-set, and the second service sub-set and the first service sub-set are not the same.
- the data change scope of the service sub-set is determined as a union of data change ranges of the service data included in the service sub-set.
- the service data has a corresponding relationship with the timestamp, and the data change range of the service data is traversed, specifically including:
- the traversal is performed according to the timestamp corresponding to the timestamp according to the timestamp of each service data.
- the service sub-group to which the service data belongs is determined according to the service type and the data change scope of the service data, and specifically includes:
- determining the I-level sub-set to which each service data belongs according to the service type of the service data specifically includes:
- the service data with the same service type is divided into the same I-level sub-set, and the service data with different service types are divided into different I-level sub-sets.
- determining the level II sub-collection to which the service data belongs according to the data change range of the service data in the I-level subset specifically includes:
- the service data with the data change scope intersection is divided into the same level II sub-collection, and the service data with no data intersection range is divided into different level II sub-items. set.
- the service data with the data change scope intersecting is divided into the same II.
- the sub-collections are divided into different level II sub-collections by dividing the data of the data change scope without intersection, including:
- the second service data is added to the first level II subset
- the first level I subset is any one of the level I subsets
- the second service data is any one of the first level 1 subsets
- the first The Level II sub-set is any of the Level II subsets of the first Level I subset
- the second Level II subset is different from the first Level II subset.
- the method for writing the blockchain service data acquires a plurality of service data to be executed, and forms a service set to be executed, which is composed of the service data, where the service set is preset.
- the amount of data processing and/or the preset business data time is determined.
- the embodiment of the present application further provides another method for writing blockchain service data, including:
- Each of the first service data is executed in parallel to write the result of the execution to the blockchain.
- the first service data that does not have a transaction dependency relationship is determined according to the data change scope of the service data, and specifically includes:
- the service data that does not intersect with the data change range of any other service data is determined as the first service data that does not have a transaction dependency relationship.
- the embodiment of the present application further provides an apparatus for writing block chain service data, including:
- the service sub-set determining module determines, according to the service type and/or the data change scope of the service data, a service sub-set to which the service data belongs; wherein the service data belonging to different service sub-sets does not have a transaction dependency relationship;
- a data execution module executes each of the subsets of services in parallel to write the results of the execution to the blockchain.
- the embodiment of the present application further provides a method for determining a service subset of a blockchain service data, including: after acquiring service data of a plurality of blockchains to be written, according to the service type of the service data and And or a data change scope, determining a service sub-set to which the service data belongs, so as to execute each of the service sub-sets in parallel, and writing the executed result to the blockchain; wherein, the service data belonging to different service sub-sets does not have Transaction dependencies.
- the service sub-group to which the service data belongs is determined according to the service type and/or the data change scope of the service data, and specifically includes:
- the method specifically includes: performing the service according to the service type of the service data.
- the service data of the same type is divided into the same service sub-collection, and the service data of different service types is divided into different service sub-sets; or
- Determining, according to the data change scope of the service data, the service sub-set to which the service data belongs specifically: dividing, according to the data change scope of the service data, the service data with the data change scope into the same service sub-set, Business data with no data intersections is divided into different business sub-collections.
- the service sub-group to which the service data belongs is determined according to the service type and the data change range of the service data, and specifically includes:
- whether the transaction data has a transaction dependency relationship between the service data may be determined according to the service type of the service data or the data change scope, and then the transaction dependency between the service data may be In the case, business data is divided into different business sub-collections. Since there is no transaction dependency between business data belonging to different business sub-sets, different business sub-sets can be executed in parallel without affecting the consistency of the database state.
- the business data without transaction dependencies is executed in parallel, which not only ensures the consistency of the database state, but also improves the execution efficiency of the data processing without relying on the improvement of the performance of the single machine, so Performance requirements can be reduced, cost savings, and scalability.
- FIG. 1 is a schematic flowchart of a method for writing data of a blockchain service according to an embodiment of the present application
- FIG. 2 is a schematic flowchart of a second blockchain service data writing method in an embodiment of the present application
- FIG. 3 is a schematic flowchart of a method for writing a third blockchain service data in the embodiment of the present application
- FIG. 4 is a schematic diagram of an actual scenario application of a method for writing a blockchain service data according to an embodiment of the present application
- FIG. 5 is a schematic structural diagram of a blockchain service data writing apparatus according to an embodiment of the present application.
- FIG. 1 is a schematic diagram of a method for writing blockchain service data according to an embodiment of the present application, which specifically includes:
- S101 Acquire a plurality of service data to be written into the blockchain.
- S102 Determine, according to the service type and/or the data change scope of the service data, a service sub-set to which the service data belongs; wherein, the service data belonging to the different service sub-sets does not have a transaction dependency relationship;
- the service type or the data change scope of the service data may be used to determine whether the service data has a transaction dependency relationship, and thus may be based on the service data.
- the transaction depends on the situation, the business data is divided into different business sub-sets. Since there is no transaction dependency between the business data belonging to different business sub-sets, different business sub-sets can be executed in parallel without affecting the consistency of the database state.
- the execution efficiency of the data processing can be improved by performing the service data in the service sub-set in parallel, without relying on the improvement of the performance of the single machine, so that the performance requirement of the single machine can be reduced, which is beneficial to saving. Cost, and scalability is better.
- the embodiment may form a service set to be executed that is composed of the service data to be executed.
- This set of services can be determined by a preset data throughput and/or a preset service data time.
- the service data that needs to be executed in the same batch can be determined by preset data processing amount, and the specific value of the preset data processing amount can be determined according to the number of data allowed to be written into the blockchain. For example, assuming that the number of service data allowed to be written into the blockchain is 1000, the preset data processing amount can be set to be less than 1000, for example, 800, to meet the requirement.
- each time the server obtains 800 service data a set of services to be executed is formed for subsequent processing.
- the service set to be executed it is also possible to determine the service data that needs to be executed in the same batch by preset the service data time. For example, if the preset service data time is set to 1 second, the service data executed in the same batch needs to be concurrently generated in 1 second.
- step S103 since the service data has been divided into multiple service sub-sets without transaction dependencies, each service sub-collection can be executed in parallel by means of multi-threading or machine clustering, thereby satisfying the requirements of database state consistency. And can achieve the purpose of improving data execution efficiency. In this way, the data execution efficiency can be improved without relying on the improvement of the performance of the single machine, the performance requirement of the single machine can be reduced, the cost is saved, and the machine clustering method is adopted, and the scalability is better.
- the service sub-assembly including the service data since the business data that is divided into the different service sub-sets does not have the transaction dependency, the business data that is divided into the same service sub-set has the transaction dependency relationship. Therefore, different business sub-sets can be executed in parallel to improve data execution efficiency; and each business data contained in the same business sub-set should be executed serially to ensure consistency of database status, specifically, business data and time stamps. If there is a corresponding relationship, when a certain service sub-set is executed, the service data included in the service sub-collection is serially executed according to the time sequence corresponding to the time stamp. Further, when each piece of business data is executed, it is performed in the order of transaction verification, transaction execution, and data entry, and finally the result of the execution is written into the blockchain.
- the business subset can be determined in a number of different manners as long as the business data having the transaction dependencies can be distinguished from the business data having no transaction dependencies.
- the service sub-set to which the service data belongs may be determined according to the data attribute of the service data, where the data attribute has a correspondence relationship with the service type and/or the data change range of the service data, and the data attribute is used to reflect the service data.
- Transaction dependencies Therefore, by extracting the data attributes from the business data, the business data having the transaction dependency can be divided into the same business sub-collection, and the business data without the transaction dependency is divided into different business sub-sets, thereby realizing different Parallel execution of business subcollections.
- the data attribute may be embodied in the form of an identifier field included in the service data, or may be embodied in the form of feature information carried by the service data.
- the method may determine whether the specified identifier field is included, or extract the feature information of the service data, and further determine whether the feature information satisfies the preset condition.
- the transaction dependency relationship between the service data referred to in the embodiment of the present application may be embodied as the service association existing when the different service data is executed, for example, may be the correlation of the time sequence, the business object or the execution result. For example, if the execution of the business data after the execution time depends on the execution result of the business data after the time, or the execution of the different business data affects the same data state, it can be considered that there is a transaction dependency between the two business data. Relationship, on the contrary, it can be considered that there is no transaction dependency between the two business data.
- the service sub-set can be determined according to the service type of the service data. Specifically, the service data with the same service type can be divided into the same service sub-collection, and the service data with different service types can be divided into different service sub-sets. Since there is no transaction dependency between business data belonging to different business types, the results of data execution will not be affected for different types of business data regardless of the order of execution. According to whether the service types are the same, whether the service sub-sets to which the service data belongs are the same, it is ensured that the service data belonging to different service sub-sets do not have transaction dependencies, so that the parallel processing of the service data between different service sub-sets can be satisfied. It is beneficial to improve the efficiency of data processing.
- a contract-type business (also known as a transaction) will only change the corresponding contract data after execution
- the transfer-type business (also known as a transaction) will change the account amount data of both parties after execution. It can be seen that the order of execution of these two types of transactions has no effect on the results of the execution. Therefore, by dividing two different types of transactions into different service sub-sets, it is guaranteed that there is no transaction dependency between the business data belonging to different business sub-sets, so that each business sub-set can be processed in parallel without affecting the database status. Consistency.
- the scope of data change referred to in this application refers to the object pointed to by the execution of business data.
- the service data with the intersection of the data change scope is divided into the same service sub-collection, and the service data with no data interchange scope is divided into different service sub-sets.
- the service sub-set is determined according to the data change scope of the service data. If the data range affected by the execution of different service data has an intersection, the service data needs to be executed in the order in which the service data occurs, otherwise the result of the data execution may be affected. If the data range affected by the execution of different business data does not intersect, the order of execution of these business data does not affect the result of data processing. Therefore, the service sub-set determined according to the data change scope of the service data can meet the requirement of parallel execution between different service sub-sets, thereby facilitating the improvement of data processing execution efficiency.
- the service data in which the data change scope has an intersection is divided into the same service sub-collection, and the service data in which the data change scope is not intersected is divided into different service sub-sets, which may include:
- the first service data is added to the first service subset
- the first service data set is any service data in the service set, and the first service sub-set is any one of the service sub-sets, and the second service sub-set is different from the first service sub-set.
- step S1021 It is determined whether all the service data in the service set has been traversed, and if so, the process ends; otherwise, step S1022 is performed;
- S1022 Taking any service data TX in the service set; it should be noted that the service data TX can be extracted and generated in the service data that has not been classified into the service sub-set, but if the extracted service data TX has been classified into the service sub- The collection, when the subsequent steps are completed, the service data TX will still be divided into the same business subset, without affecting the achievement of technical purposes;
- step S1025 If the result of the determination in step S1024 is YES, the service data TX is added to the service sub-set TXB.
- step S1026 If the result of the determination in step S1024 is no, a new service subset TXN is created, and the service data TX is added into the service subset TXN.
- the data change scope of the service sub-set needs to be re-calculated, and the data change range of the service data included in the service sub-set can be used as the service.
- the execution object of the contract type business is the contract ID
- the contract ID can be understood as the data change range of the business data.
- the two service data are executed for the same contract ID, it can be understood that there is an intersection of the data change ranges of the two service data, and the two service data should be divided into the same service sub-set, corresponding to the service data.
- the timestamps are determined in the order in which they are executed. If two business data are executed for different contract IDs, it can be understood that there is no intersection of the data change scopes of the two business data, and the contract data corresponding to different contract IDs is changed during execution, so The order of execution has no effect on the result of the execution.
- the two business data can be divided into different business sub-collections and distributed and executed in parallel.
- the execution object of the transfer business is the account of both parties to the transfer, and the account amount data of both parties of the transfer is changed after execution. Therefore, the data change range of the transfer business data can be understood as the account of both transfer parties.
- the business collection contains the following five business data:
- Business Data 1 Account A is transferred to Account B, then the data change range of Business Data 1 can be expressed as (A, B);
- Business Data 2 Account B is transferred to Account A, and the data change range of Business Data 2 can be expressed as (B, A);
- Business Data 3 Account C is transferred to Account E, and the data change range of Business Data 3 can be expressed as (C, E);
- Business data 4 Account F is transferred to account X, then the data change range of business data 4 can be expressed as (F, X);
- Business Data 5 When Account X is transferred to Account E, the data change range of Business Data 5 can be expressed as (X, E).
- the service set including the service data 1 to the service data 5 can be divided into the following service sub-sets:
- Business sub-collection 1 contains business data 1 and business data 2, the data change scope is (A, B);
- Service sub-collection 2 contains business data 3, business data 4, and business data 5, and the data change range is (C, E, F, X).
- the data change scopes involved in the service sub-collection 1 and the service sub-collection 2 do not intersect, and even if the parallel execution does not affect the execution result, the service sub-set 1 and the business sub-set 2 can be executed in parallel to improve effectiveness.
- the data change scopes of the business data 1 and the business data 2 have an intersection (here even the same), and the execution of the two business data may depend on the business data before the execution thereof, so It is necessary to judge the order of execution according to the timestamp corresponding to the two service data, and execute serially in time sequence. The same is true for the service sub-collection 2.
- the service data 4 should be first transferred from the account F to the account X, and then the service data 5 account X is transferred to the account E, and the execution order is not available.
- Parallel it is also not reversed, because it is possible to execute the business data 5 when the account X transfers funds to the account E depends on the transfer of the business data 4 account F to the account X.
- each service data in the service set when traversing the data change range of each service data in the service set, it may be performed by performing step 1022 to take one service data, or according to each service data, as shown in the example of FIG. 2 .
- the timestamp is traversed in the order in which the business data in the business collection occurs.
- the service type and the data change scope may also be combined, and the service sub-set is determined in a hierarchical hierarchical manner. In the specific implementation, it may be divided according to the scope of data change. On this basis, the second division may be performed according to the service type, or vice versa.
- the following is based on the service type, and then the secondary division of the data change scope is taken as an example to illustrate the implementation process of the service sub-collection according to the service type and the data change scope of the service data, which may specifically include:
- step S1027 is performed to determine, according to the service type of the service data, the I-level sub-set to which the service data belongs;
- the second-level sub-set to which each service data belongs is determined, and the second-level sub-set is used as the service sub-set; wherein the second-level sub-set is a subset of the I-level sub-set.
- the first level of the service set is divided according to the service type, and the I-level sub-set to which each service data belongs is determined, which may further include:
- the service data with the same service type is divided into the same I-level sub-collection, and the service data with different service types are divided into different I-level sub-sets.
- the second-level sub-set determined according to the service type can be divided into two levels, and the second-level sub-set obtained through the second-level division is processed as a sub-set of the business in parallel, with a view to Further improve execution efficiency.
- determining the level II sub-set to which each service data belongs according to the data change range of the service data in the I-level subset may include:
- the business data with the data change scope intersection is divided into the same level II sub-collection, and the business data with no data intersection is not divided into different level II sub-sets.
- the level sub-collection may specifically include:
- the first level I subset is any one of the level I subsets
- the second service data is any one of the first level I subsets
- the first level II subset is the first level I. Any of the Level II sub-sets in the set, the second Level II sub-sets are different from the first Level II sub-sets.
- the process of dividing the level II sub-set from the I-level sub-set is similar to the process and principle of dividing the service sub-set from the service set described in item (2), and will not be described here.
- each service sub-set can be executed in parallel, and the execution process of the blockchain service data is completed, so that the execution result is written into the blockchain.
- the service data orchestration module is configured to implement division of service sub-sets.
- the service data execution cluster executes the service data in the different service sub-sets in parallel, and performs the serial execution according to the time stamp corresponding to the service data in the service sub-collection, and then writes the executed result into the blockchain, thereby ensuring the area.
- the consistency of the state of the blockchain database can reduce the cost of improving the efficiency of data processing execution and improve scalability.
- the service data when the service is executed, the service data is sorted according to the timestamp of receiving the service data, and then the serial information is serially executed, and the account information after executing each service data is updated.
- the service data after receiving the service data to be written into the blockchain (that is, the transaction data received by the block link), the service data is classified according to the service type and/or the data change scope to form a service sub-process.
- the collection is such that business data without transaction dependencies is divided into different business sub-sets, and business data with transaction dependencies is divided into the same business sub-set.
- the division of the business data and the determination of the subset of services can be implemented by the business data orchestration module in the example of FIG.
- each service sub-set can be distributed to each computer in the service data execution cluster for data processing, and each computer in the service data execution cluster executes only the assigned service sub-set.
- the business data is processed in accordance with the verification-implementation-entry process, and the results of the execution are written into the blockchain.
- the service data orchestration module and the service data execution cluster may also be combined to be understood as a service execution cluster, which implements the functions of receiving, classifying, distributing, and executing service data, and summarizes the execution results of the service data and writes the area. Blockchain.
- the embodiment of the present application further provides another method for writing blockchain service data, including:
- Each of the first service data is executed in parallel to write the result of the execution to the blockchain.
- the service data that does not intersect with the data change scope of any other service data may be determined as the first one without the transaction dependency according to the data change scope of the service data.
- Business data when determining the first service data, the service data that does not intersect with the data change scope of any other service data may be determined as the first one without the transaction dependency according to the data change scope of the service data.
- the data change range of the business data 3, 4, 6, 8 and any other business data does not intersect, therefore, the order of execution of the several business data does not affect The consistency of the database state, so that the implementation of these business data in parallel, is conducive to improve the efficiency of data processing, thereby reducing the cost of data processing execution efficiency and improving scalability.
- the apparatus for writing blockchain service data provided by the present application may include:
- the obtaining module 101 is configured to obtain a plurality of service data to be written into the blockchain;
- the service sub-set determining module 102 determines, according to the service type of the service data and/or the data change scope, the service sub-set to which the service data belongs; wherein the service data belonging to the different service sub-sets does not have a transaction dependency relationship;
- the data execution module 103 executes the respective service subsets in parallel to write the results of the execution to the blockchain.
- This embodiment is the device corresponding to the method for writing the blockchain service data in the embodiment 1. All the explanations in the embodiment 1 are applicable to the embodiment, and are not described herein again.
- the present application also provides a service sub-set determining method for blockchain service data, according to which the business data is reasonably divided, so that business data without transaction dependencies can be executed in parallel, thereby reducing the efficiency of data processing execution.
- the method includes:
- determining the service sub-set to which the service data belongs according to the service type and/or the data change scope of the service data may include:
- the service sub-set to which the service data belongs is determined; wherein the data attribute has a correspondence relationship with the service type and/or the data change range of the service data, and the data attribute is used to reflect the transaction dependency of the service data.
- determining the service sub-assembly to which the service data belongs according to the service type of the service data may include: dividing the service data with the same service type into the same service sub-set according to the service type of the service data, and the service types are different.
- the business data is divided into different business sub-collections.
- Determining the service sub-set to which the service data belongs according to the data change scope of the service data may specifically include: dividing the service data with the intersection of the data change scope into the same service sub-set according to the data change scope of the service data, and changing the data range Business data without intersections is divided into different business sub-collections.
- the service sub-group to which the service data belongs is determined according to the service type and the data change scope of the service data, and may further specifically include:
- the second-level sub-set to which each service data belongs is determined, and the second-level sub-set is used as the service sub-set; wherein the second-level sub-set is a subset of the I-level sub-set.
- embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
- a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
- processors CPUs
- input/output interfaces network interfaces
- memory volatile and non-volatile memory
- the memory may include non-persistent memory in a computer readable medium, random access memory (R I level subset M), and/or nonvolatile memory, such as read only memory (ROM) or flash memory (fl I level). Subset sh R I level subset M). Memory is an example of a computer readable medium.
- Computer readable media includes both permanent and non-persistent, removable and non-removable media.
- Information storage can be implemented by any method or technology.
- the information can be computer readable instructions, data structures, modules of programs, or other data.
- Examples of computer storage media include, but are not limited to, phase change memory (PR I level subset M), static random access memory (SR I level subset M), dynamic random access memory (DR I level subset M) Other types of random access memory (R I subgroup M), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, read only optical disc only Read memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape storage or other magnetic storage device or any other non-transportable medium that can be used to store access that can be accessed by a computing device. information.
- computer readable media does not include temporary storage computer readable media (tr I level subset nsitory medi I level subsets), such as modulated data signals
- embodiments of the present application can be provided as a method, system, or computer program product.
- the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
- the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Computational Linguistics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mathematical Physics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Description
数据编号 | 业务类型 | 数据变更范围 | 备注 |
1 | 合约类 | ID A | 执行将变更ID A的数据 |
2 | 合约类 | ID A | 执行将变更ID A的数据 |
3 | 合约类 | ID B | 执行将变更ID B的数据 |
4 | 合约类 | ID C | 执行将变更ID C的数据 |
5 | 转账类 | 账户X、账户Y | 执行将变更账户X和账户Y的数据 |
6 | 转账类 | 账户Z、账户D | 执行将变更账户Z和账户D的数据 |
7 | 转账类 | 账户X、账户M | 执行将变更账户X和账户M的数据 |
8 | 转账类 | 账户N、账户L | 执行将变更账户N和账户L的数据 |
Claims (21)
- 一种写入区块链业务数据的方法,其特征在于,包括:获取多个待写入区块链的业务数据;依据所述业务数据的业务类型和/或数据变更范围,确定业务数据归属的业务子集合;其中,属于不同业务子集合的业务数据间不具有交易依赖关系;并行执行各所述业务子集合,以将执行的结果写入所述区块链。
- 按照权利要求1所述方法,其特征在于,依据所述业务数据的业务类型和/或数据变更范围,确定业务数据归属的业务子集合,具体包括:依据所述业务数据的数据属性,确定业务数据归属的业务子集合;其中,所述数据属性与所述业务数据的业务类型和/或数据变更范围具有对应关系,所述数据属性用于反映所述业务数据的交易依赖关系。
- 按照权利要求1所述方法,其特征在于,并行执行各所述业务子集合,具体包括:采用多线程或者机器集群并行执行各所述业务子集合。
- 按照权利要求1所述方法,其特征在于,所述业务数据与时间戳具有对应关系,则执行所述业务子集合时,具体包括:按照所述时间戳对应的时间顺序,串行执行所述业务子集合中包含的业务数据。
- 按照权利要求1所述方法,其特征在于,依据所述业务数据的业务类型,确定业务数据归属的业务子集合,具体包括:依据所述业务数据的业务类型,将所述业务类型相同的业务数据分入相同的业务子集合,将所述业务类型不相同的业务数据分入不同的业务子集合。
- 按照权利要求1所述方法,其特征在于,依据所述业务数据的数据变更范围,确定业务数据归属的业务子集合,具体包括:依据所述业务数据的数据变更范围,将数据变更范围有交集的业务数据分入相同的业务子集合,将数据变更范围无交集的业务数据分入不同的业务子集 合。
- 按照权利要求6所述方法,其特征在于,依据所述业务数据的数据变更范围,将数据变更范围有交集的业务数据分入相同的业务子集合,将数据变更范围无交集的业务数据分入不同的业务子集合,具体包括:遍历所述业务数据的数据变更范围;若第一业务数据的数据变更范围与第一业务子集合的数据变更范围有交集,则将所述第一业务数据添加进所述第一业务子集合;若所述第一业务数据的数据变更范围与第一业务子集合的数据变更范围无交集,则创建一个包含所述第一业务数据的第二业务子集合;其中,所述第一业务数据为任一业务数据,所述第一业务子集合为所述业务子集合中任一业务子集合,所述第二业务子集合与所述第一业务子集合不相同。
- 按照权利要求6或7所述方法,其特征在于,所述业务子集合的数据变更范围,确定为该业务子集合包含的业务数据的数据变更范围的并集。
- 按照权利要求7所述方法,其特征在于,所述业务数据与时间戳具有对应关系,则遍历所述业务数据的数据变更范围,具体包括:依据各业务数据的所述时间戳,按照所述时间戳对应的时间顺序进行遍历。
- 按照权利要求1所述方法,其特征在于,依据所述业务数据的业务类型和数据变更范围,确定业务数据归属的业务子集合,具体包括:依据所述业务数据的业务类型,确定所述业务数据所属的Ⅰ级子集合;依据所述Ⅰ级子集合中业务数据的数据变更范围,确定各业务数据所属的Ⅱ级子集合,以所述Ⅱ级子集合作为所述业务子集合;其中,所述Ⅱ级子集合为所述Ⅰ级子集合的子集。
- 按照权利要求10所述方法,其特征在于,依据所述业务数据的业务类型,确定各业务数据所属的Ⅰ级子集合,具体包括:依据所述业务数据的业务类型,将所述业务类型相同的业务数据分入相同的Ⅰ级子集合,将所述业务类型不相同的业务数据分入不同的Ⅰ级子集合。
- 按照权利要求10所述方法,其特征在于,依据所述Ⅰ级子集合中业务数据的数据变更范围,确定各业务数据所属的Ⅱ级子集合,具体包括:依据所述Ⅰ级子集合中的业务数据的数据变更范围,将数据变更范围有交集的业务数据分入相同的Ⅱ级子集合,将数据变更范围无交集的业务数据分入不同的Ⅱ级子集合。
- 按照权利要求12所述方法,其特征在于,依据所述Ⅰ级子集合中的业务数据的数据变更范围,将数据变更范围有交集的业务数据分入相同的Ⅱ级子集合,将数据变更范围无交集的业务数据分入不同的Ⅱ级子集合,具体包括:遍历第一Ⅰ级子集合中各业务数据的数据变更范围;若第二业务数据的数据变更范围与第一Ⅱ级子集合的数据变更范围有交集,则将所述第二业务数据添加进所述第一Ⅱ级子集合;若所述第二业务数据的数据变更范围与第一Ⅱ级子集合的数据变更范围无交集,则创建一个包含所述第二业务数据的第二Ⅱ级子集合;其中,所述第一Ⅰ级子集合为所述Ⅰ级子集合中任一Ⅰ级子集合,所述第二业务数据为所述第一Ⅰ级子集合中任一业务数据,所述第一Ⅱ级子集合为所述第一Ⅰ级子集合中任一Ⅱ级子集合,所述第二Ⅱ级子集合与所述第一Ⅱ级子集合不相同。
- 按照权利要求1所述方法,其特征在于,获取多个待执行的业务数据,形成由所述业务数据构成的待执行的业务集合,所述业务集合由预设数据处理量和/或预设业务数据时间确定。
- 一种写入区块链业务数据的方法,其特征在于,包括:获取多个待写入区块链的业务数据;依据所述业务数据的数据变更范围,确定不具有交易依赖关系的第一业务数据;其中,所述第一业务数据间不具有交易依赖关系;并行执行各所述第一业务数据,以将执行的结果写入所述区块链。
- 按照权利要求15所述方法,其特征在于,依据所述业务数据的数据变更范围,确定不具有交易依赖关系的第一业务数据,具体包括:依据所述业务数据的数据变更范围,将与其他任一业务数据的数据变更范围无交集的业务数据确定为不具有交易依赖关系的所述第一业务数据。
- 一种写入区块链业务数据的装置,其特征在于,包括:获取模块,获取多个待写入区块链的业务数据;业务子集合确定模块,依据所述业务数据的业务类型和/或数据变更范围,确定业务数据归属的业务子集合;其中,属于不同业务子集合的业务数据间不具有交易依赖关系;数据执行模块,并行执行各所述业务子集合,以将执行的结果写入所述区块链。
- 一种区块链业务数据的业务子集合确定方法,其特征在于,包括:在获取多个待写入区块链的业务数据之后,依据所述业务数据的业务类型和/或数据变更范围,确定业务数据归属的业务子集合,以便并行执行各所述业务子集合,将执行的结果写入所述区块链;其中,属于不同业务子集合的业务数据间不具有交易依赖关系。
- 按照权利要求18所述方法,其特征在于,依据所述业务数据的业务类型和/或数据变更范围,确定业务数据归属的业务子集合,具体包括:依据所述业务数据的数据属性,确定业务数据归属的业务子集合;其中,所述数据属性与所述业务数据的业务类型和/或数据变更范围具有对应关系,所述数据属性用于反映所述业务数据的交易依赖关系。
- 按照权利要求18所述方法,其特征在于,依据所述业务数据的业务类型,确定业务数据归属的业务子集合,具体包括:依据所述业务数据的业务类型,将所述业务类型相同的业务数据分入相同的业务子集合,将所述业务类型不相同的业务数据分入不同的业务子集合;或 者,依据所述业务数据的数据变更范围,确定业务数据归属的业务子集合,具体包括:依据所述业务数据的数据变更范围,将数据变更范围有交集的业务数据分入相同的业务子集合,将数据变更范围无交集的业务数据分入不同的业务子集合。
- 按照权利要求18所述方法,其特征在于,依据所述业务数据的业务类型和数据变更范围,确定业务数据归属的业务子集合,具体包括:依据所述业务数据的业务类型,确定所述业务数据所属的Ⅰ级子集合;依据所述Ⅰ级子集合中业务数据的数据变更范围,确定各业务数据所属的Ⅱ级子集合,以所述Ⅱ级子集合作为所述业务子集合;其中,所述Ⅱ级子集合为所述Ⅰ级子集合的子集。
Priority Applications (15)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
SG11201907212SA SG11201907212SA (en) | 2017-02-28 | 2018-02-26 | Method and apparatus for writing service data into block chain and method for determining service subset |
MX2019009728A MX2019009728A (es) | 2017-02-28 | 2018-02-26 | Metodo y aparato para escribir datos de servicio en cadena de bloques y metodo para determinar un subconjunto de servicio. |
KR1020197023701A KR102103130B1 (ko) | 2017-02-28 | 2018-02-26 | 서비스 데이터를 블록체인에 기입하기 위한 방법 및 장치, 그리고 서비스 하위세트를 결정하기 위한 방법 |
RU2019124224A RU2744585C2 (ru) | 2017-02-28 | 2018-02-26 | Способ и аппаратура для записи служебных данных в цепочку блоков и способ для определения поднабора услуг |
EP18760329.5A EP3561700A4 (en) | 2017-02-28 | 2018-02-26 | METHOD AND DEVICE FOR WRITING SERVICE DATA IN A BLOCKCHAIN AND METHOD FOR DETERMINING A SERVICE SUB-GROUP |
JP2019546907A JP6928104B2 (ja) | 2017-02-28 | 2018-02-26 | ブロック・チェーンにサービス・データを書き込むための方法および装置、ならびにサービス・サブセットを判定するための方法 |
MYPI2019004229A MY197445A (en) | 2017-02-28 | 2018-02-26 | Method and apparatus for writing service data into block chain and method for determining service subset |
CA3054813A CA3054813C (en) | 2017-02-28 | 2018-02-26 | Method and apparatus for writing service data into block chain and method for determining service subset |
BR112019017863-5A BR112019017863A2 (pt) | 2017-02-28 | 2018-02-26 | Método e aparelho para gravar dados de serviço em cadeia de blocos e método para determinar subconjunto de serviços |
AU2018228540A AU2018228540B2 (en) | 2017-02-28 | 2018-02-26 | Method and apparatus for writing service data into block chain and method for determining service subset |
ZA2019/04916A ZA201904916B (en) | 2017-02-28 | 2019-07-26 | Method and apparatus for writing service data into block chain and method for determining service subset |
PH12019501795A PH12019501795A1 (en) | 2017-02-28 | 2019-08-05 | Method and apparatus for writing service data into block chain and method for determining service subset |
US16/535,035 US10642643B2 (en) | 2017-02-28 | 2019-08-07 | Method and apparatus for writing service data into block chain and method for determining service subset |
AU2019101606A AU2019101606A4 (en) | 2017-02-28 | 2019-12-16 | Method and apparatus for writing service data into block chain and method for determining service subset |
US16/745,519 US10664305B1 (en) | 2017-02-28 | 2020-01-17 | Method and apparatus for writing service data into block chain and method for determining service subset |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710116539.7 | 2017-02-28 | ||
CN201710116539.7A CN106980649B (zh) | 2017-02-28 | 2017-02-28 | 写入区块链业务数据的方法和装置及业务子集合确定方法 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/535,035 Continuation US10642643B2 (en) | 2017-02-28 | 2019-08-07 | Method and apparatus for writing service data into block chain and method for determining service subset |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018157778A1 true WO2018157778A1 (zh) | 2018-09-07 |
Family
ID=59339366
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/077286 WO2018157778A1 (zh) | 2017-02-28 | 2018-02-26 | 写入区块链业务数据的方法和装置及业务子集合确定方法 |
Country Status (16)
Country | Link |
---|---|
US (2) | US10642643B2 (zh) |
EP (1) | EP3561700A4 (zh) |
JP (1) | JP6928104B2 (zh) |
KR (1) | KR102103130B1 (zh) |
CN (1) | CN106980649B (zh) |
AU (2) | AU2018228540B2 (zh) |
BR (1) | BR112019017863A2 (zh) |
CA (1) | CA3054813C (zh) |
MX (1) | MX2019009728A (zh) |
MY (1) | MY197445A (zh) |
PH (1) | PH12019501795A1 (zh) |
RU (1) | RU2744585C2 (zh) |
SG (1) | SG11201907212SA (zh) |
TW (1) | TWI660281B (zh) |
WO (1) | WO2018157778A1 (zh) |
ZA (1) | ZA201904916B (zh) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019072303A2 (en) | 2018-12-28 | 2019-04-18 | Alibaba Group Holding Limited | EXECUTING PARALLEL TRANSACTIONS IN A BLOCK CHAINS NETWORK |
CN109766727A (zh) * | 2018-12-25 | 2019-05-17 | 中链科技有限公司 | 智能区块网络构建方法及*** |
EP3545481A4 (en) * | 2018-11-27 | 2020-02-12 | Alibaba Group Holding Limited | SYSTEM AND METHOD FOR IMPROVING THE SECURITY OF AN INTELLIGENT CONTRACT ON A BLOCK CHAIN |
WO2019120332A3 (en) * | 2019-04-12 | 2020-02-13 | Alibaba Group Holding Limited | Performing parallel execution of transactions in a distributed ledger system |
WO2019120334A3 (en) * | 2019-04-12 | 2020-02-13 | Alibaba Group Holding Limited | Performing parallel execution of transactions in a distributed ledger system |
WO2019120333A3 (en) * | 2019-04-12 | 2020-02-13 | Alibaba Group Holding Limited | Performing parallel execution of transactions in a distributed ledger system |
JP2020518880A (ja) * | 2018-12-28 | 2020-06-25 | アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited | スマートコントラクトホワイトリストに基づくブロックチェーンネットワークにおけるトランザクションの並列実行 |
JP2020519983A (ja) * | 2019-03-28 | 2020-07-02 | アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited | 並列処理ブロックチェーントランザクションのためのシステムおよび方法 |
US11138597B2 (en) | 2018-11-27 | 2021-10-05 | Advanced New Technologies Co., Ltd. | System and method for improving security of smart contract on blockchain |
Families Citing this family (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106980649B (zh) | 2017-02-28 | 2020-07-10 | 创新先进技术有限公司 | 写入区块链业务数据的方法和装置及业务子集合确定方法 |
GB201707296D0 (en) * | 2017-05-08 | 2017-06-21 | Nchain Holdings Ltd | Computer-implemented system and method |
CN107423124A (zh) * | 2017-07-27 | 2017-12-01 | 中链科技有限公司 | 一种用于对交易数据进行并行处理的方法 |
CN107729137B (zh) * | 2017-09-04 | 2021-06-22 | 深圳壹账通智能科技有限公司 | 服务器、区块链验签解密的方法及存储介质 |
CN107678865A (zh) * | 2017-09-20 | 2018-02-09 | 中国银行股份有限公司 | 基于交易分组的区块链的验证方法以及*** |
CN107734021B (zh) | 2017-09-30 | 2020-04-07 | 深圳壹账通智能科技有限公司 | 区块链数据上传方法、***、计算机***及存储介质 |
CN107786642B (zh) * | 2017-09-30 | 2020-04-17 | 上海数据交易中心有限公司 | 用于数据流通的区块链构建方法及装置、存储介质、服务器 |
CN107833060B (zh) * | 2017-11-13 | 2020-12-25 | 中国银行股份有限公司 | 一种区块链中智能合约交易的验证方法以及*** |
CN108322309B (zh) * | 2017-12-27 | 2019-10-11 | 北京欧链科技有限公司 | 基于区块链的交易处理方法及装置 |
WO2019127532A1 (zh) * | 2017-12-29 | 2019-07-04 | 深圳前海达闼云端智能科技有限公司 | 基于区块链的众筹信息处理方法、装置、存储介质及电子设备 |
CN110083437A (zh) * | 2018-01-25 | 2019-08-02 | 北京欧链科技有限公司 | 处理区块链事务的方法及装置 |
CN108471510A (zh) * | 2018-01-29 | 2018-08-31 | 东莞理工学院 | 一种基于区块链的视频操作记录保护方法及*** |
CN108564470B (zh) * | 2018-04-17 | 2021-09-28 | 北京天德科技有限公司 | 一种区块链中并行建块的交易分发方法 |
CN108958925B (zh) * | 2018-04-26 | 2023-06-20 | 武汉龙津科技有限公司 | 一种节能的工作量证明方法与*** |
CN108768994B (zh) * | 2018-05-22 | 2021-07-27 | 北京小米移动软件有限公司 | 数据匹配方法、装置及计算机可读存储介质 |
JP7063142B2 (ja) * | 2018-06-25 | 2022-05-09 | 日本電信電話株式会社 | 番号管理システム、番号管理方法および番号管理装置 |
CN109087097B (zh) * | 2018-07-26 | 2020-11-03 | 京东数字科技控股有限公司 | 一种更新链码同一标识的方法和装置 |
CN109191295A (zh) * | 2018-08-15 | 2019-01-11 | 深圳市元征科技股份有限公司 | 一种信息处理方法及其设备 |
CN109325366B (zh) * | 2018-08-22 | 2022-08-12 | 深圳前海微众银行股份有限公司 | 基于联盟链的业务处理方法、设备及计算机可读存储介质 |
US10860659B1 (en) * | 2018-09-06 | 2020-12-08 | Amazon Technologies, Inc. | Distributed verification of digital work product |
TWI698100B (zh) * | 2018-09-18 | 2020-07-01 | 柯賓漢數位金融科技有限公司 | 多區塊鏈產生及整合方法暨區塊鏈系統 |
CN109493211A (zh) * | 2018-09-27 | 2019-03-19 | 深圳壹账通智能科技有限公司 | 基于区块链的信贷数据存储方法、装置、设备及存储介质 |
CN109088722B (zh) * | 2018-10-08 | 2021-10-19 | 深圳投时科技有限公司 | 区块链节点演进方法及区块链节点 |
CN109299195A (zh) * | 2018-10-23 | 2019-02-01 | 杭州能链科技有限公司 | 数据处理方法、装置及存储介质 |
CN111782275B (zh) * | 2018-10-25 | 2024-02-06 | 创新先进技术有限公司 | 基于区块链的交易处理方法及装置、电子设备 |
CN111291018B (zh) * | 2018-12-07 | 2023-06-23 | 北京沃东天骏信息技术有限公司 | 数据管理方法、装置、设备及存储介质 |
JP6763094B2 (ja) * | 2018-12-29 | 2020-09-30 | アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited | 地図アプリケーションのブロックチェーンベースのクラウドソーシング |
WO2019101232A2 (en) * | 2019-03-04 | 2019-05-31 | Alibaba Group Holding Limited | Methods and devices for providing transaction data to blockchain system for processing |
KR102118178B1 (ko) * | 2019-04-24 | 2020-06-02 | 주식회사 데이터젠 | 블록체인을 위한 다중 트랜잭션 병렬 처리 방법 및 시스템 |
CN110209671A (zh) * | 2019-05-17 | 2019-09-06 | 无锡朝阳供应链科技股份有限公司 | 一种分布式账本数据的存取***及其应用 |
CN112001713B (zh) * | 2019-05-27 | 2024-03-29 | 深圳市红砖坊技术有限公司 | 区块链***以及请求处理方法和装置 |
US11126593B2 (en) | 2019-06-15 | 2021-09-21 | Facebook, Inc. | Scalable, secure, efficient, and adaptable distributed digital ledger transaction network |
US11249985B2 (en) * | 2019-06-15 | 2022-02-15 | Facebook, Inc. | Scalable, secure, efficient, and adaptable distributed digital ledger transaction network |
US11405204B2 (en) | 2019-06-15 | 2022-08-02 | Meta Platforms, Inc | Scalable, secure, efficient, and adaptable distributed digital ledger transaction network |
US11249947B2 (en) | 2019-06-15 | 2022-02-15 | Facebook, Inc. | Distributed digital ledger transaction network for flexible, lazy deletion of data stored within an authenticated data structure |
CN114096966A (zh) * | 2019-06-15 | 2022-02-25 | 元平台公司 | 可扩展的、安全的、高效的和适应性强的分布式数字分类账交易网络 |
CN110570311B (zh) * | 2019-09-17 | 2021-05-25 | 北京海益同展信息科技有限公司 | 区块链的共识方法、装置及设备 |
CN110659308B (zh) * | 2019-09-24 | 2020-12-22 | 华润网络(深圳)有限公司 | 一种数据清算处理方法及装置 |
CN110728578A (zh) * | 2019-09-29 | 2020-01-24 | 南京金宁汇科技有限公司 | 区块链交易的并行执行方法、***及存储介质 |
CN110806923B (zh) * | 2019-10-29 | 2023-02-24 | 百度在线网络技术(北京)有限公司 | 一种区块链任务的并行处理方法、装置、电子设备和介质 |
CN111126978B (zh) * | 2019-12-28 | 2023-03-14 | 飞天诚信科技股份有限公司 | 一种区块链上快速处理事务的实现方法及装置 |
US11682095B2 (en) | 2020-02-25 | 2023-06-20 | Mark Coast | Methods and apparatus for performing agricultural transactions |
KR102461553B1 (ko) * | 2020-02-28 | 2022-11-01 | 주식회사 시큐어링크 | 대용량 정보 공유를 위한 계층 블록체인 시스템 |
CN111405037A (zh) * | 2020-03-13 | 2020-07-10 | 杭州复杂美科技有限公司 | 区块同步方法、设备和存储介质 |
KR102315226B1 (ko) * | 2020-03-16 | 2021-10-20 | 이정우 | 규칙 증명 방식의 합의 알고리즘 기반 블록체인 시스템 및 그 방법 |
CN113779016A (zh) * | 2020-07-06 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | 数据管理的方法和装置 |
CN112508574A (zh) * | 2021-02-03 | 2021-03-16 | 北京全息智信科技有限公司 | 一种区块链的并行交易执行方法、装置和电子设备 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150379510A1 (en) * | 2012-07-10 | 2015-12-31 | Stanley Benjamin Smith | Method and system to use a block chain infrastructure and Smart Contracts to monetize data transactions involving changes to data included into a data supply chain. |
CN106330431A (zh) * | 2016-08-29 | 2017-01-11 | 北京瑞卓喜投科技发展有限公司 | 基于区块链技术的数据处理方法、装置及*** |
CN106406896A (zh) * | 2016-09-27 | 2017-02-15 | 北京天德科技有限公司 | 一种并行PipeLine技术的区块链建块方法 |
CN106980649A (zh) * | 2017-02-28 | 2017-07-25 | 阿里巴巴集团控股有限公司 | 写入区块链业务数据的方法和装置及业务子集合确定方法 |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10002019B2 (en) * | 2009-05-11 | 2018-06-19 | International Business Machines Corporation | System and method for assigning a transaction to a serialized execution group based on an execution group limit for parallel processing with other execution groups |
RU2554509C2 (ru) * | 2010-10-06 | 2015-06-27 | Александр Яковлевич Богданов | Система и способ распределенных вычислений |
US8856283B2 (en) * | 2011-06-03 | 2014-10-07 | Apple Inc. | Playlists for real-time or near real-time streaming |
US8688661B2 (en) | 2012-06-15 | 2014-04-01 | International Business Machines Corporation | Transactional processing |
US9553982B2 (en) | 2013-07-06 | 2017-01-24 | Newvoicemedia, Ltd. | System and methods for tamper proof interaction recording and timestamping |
US11126627B2 (en) | 2014-01-14 | 2021-09-21 | Change Healthcare Holdings, Llc | System and method for dynamic transactional data streaming |
EP2961168A1 (en) * | 2014-06-27 | 2015-12-30 | Thomson Licensing | Method and apparatus for predicting image samples for encoding or decoding |
TWI528217B (zh) * | 2014-07-02 | 2016-04-01 | 柯呈翰 | 於線上加上即時檔案動態標籤、加密之系統及方法 |
US9594644B2 (en) | 2014-09-19 | 2017-03-14 | Sybase, Inc. | Converting a serial transaction schedule to a parallel transaction schedule |
US9967334B2 (en) | 2015-03-02 | 2018-05-08 | Dell Products Lp | Computing device configuration and management using a secure decentralized transaction ledger |
US9967333B2 (en) | 2015-03-02 | 2018-05-08 | Dell Products Lp | Deferred configuration or instruction execution using a secure distributed transaction ledger |
US10812274B2 (en) * | 2015-05-07 | 2020-10-20 | Blockstream Corporation | Transferring ledger assets between blockchains via pegged sidechains |
JP6923946B2 (ja) | 2015-12-21 | 2021-08-25 | コチャバ インコーポレイテッドKochava Inc. | 自己規制取引システム、その方法、プログラム、データ処理デバイスシステム、コンピュータ読み取り可能な記憶媒体システム、コンピュータプログラム製品およびコンピュータプログラム製品 |
US10255108B2 (en) | 2016-01-26 | 2019-04-09 | International Business Machines Corporation | Parallel execution of blockchain transactions |
US10108812B2 (en) | 2016-01-28 | 2018-10-23 | Nasdaq, Inc. | Systems and methods for securing and disseminating time sensitive information using a blockchain |
GB2604540B (en) | 2016-02-03 | 2023-01-11 | Luther Systems | System and method for secure management of digital contracts |
AU2017216289A1 (en) | 2016-02-04 | 2018-09-27 | Nasdaq Technology Ab | Systems and methods for storing and sharing transactional data using distributed computer systems |
US10129238B2 (en) | 2016-02-10 | 2018-11-13 | Bank Of America Corporation | System for control of secure access and communication with different process data networks with separate security features |
US10142312B2 (en) | 2016-02-22 | 2018-11-27 | Bank Of America Corporation | System for establishing secure access for users in a process data network |
US20170264428A1 (en) | 2016-03-08 | 2017-09-14 | Manifold Technology, Inc. | Data storage system with blockchain technology |
AU2017240796A1 (en) | 2016-03-31 | 2018-10-25 | Clause, Inc. | System and method for creating and executing data-driven legal contracts |
CN105893042A (zh) * | 2016-03-31 | 2016-08-24 | 北京航空航天大学 | 一种基于区块链的智能合约的实现方法 |
WO2017173271A1 (en) | 2016-04-01 | 2017-10-05 | Jpmorgan Chase Bank, N.A. | Systems and methods for providing data privacy in a private distributed ledger |
GB201607476D0 (en) | 2016-04-29 | 2016-06-15 | Eitc Holdings Ltd | Operating system for blockchain IOT devices |
CN109314635A (zh) | 2016-05-09 | 2019-02-05 | 诺基亚技术有限公司 | 基于区块链的资源管理 |
GB201611698D0 (en) | 2016-07-05 | 2016-08-17 | Eitc Holdings Ltd | Blockchain-implemented control method and system |
WO2018013124A1 (en) | 2016-07-14 | 2018-01-18 | Digital Asset Holdings | Digital asset platform |
CN106682984B (zh) * | 2016-10-27 | 2019-09-10 | 深圳壹账通智能科技有限公司 | 基于区块链的交易事务处理方法及*** |
CN108427601A (zh) * | 2017-02-13 | 2018-08-21 | 北京航空航天大学 | 一种私有链节点的集***易处理方法 |
-
2017
- 2017-02-28 CN CN201710116539.7A patent/CN106980649B/zh active Active
- 2017-11-14 TW TW106139289A patent/TWI660281B/zh active
-
2018
- 2018-02-26 KR KR1020197023701A patent/KR102103130B1/ko active IP Right Grant
- 2018-02-26 BR BR112019017863-5A patent/BR112019017863A2/pt not_active IP Right Cessation
- 2018-02-26 AU AU2018228540A patent/AU2018228540B2/en active Active
- 2018-02-26 WO PCT/CN2018/077286 patent/WO2018157778A1/zh unknown
- 2018-02-26 SG SG11201907212SA patent/SG11201907212SA/en unknown
- 2018-02-26 EP EP18760329.5A patent/EP3561700A4/en not_active Ceased
- 2018-02-26 JP JP2019546907A patent/JP6928104B2/ja active Active
- 2018-02-26 MY MYPI2019004229A patent/MY197445A/en unknown
- 2018-02-26 MX MX2019009728A patent/MX2019009728A/es unknown
- 2018-02-26 RU RU2019124224A patent/RU2744585C2/ru active
- 2018-02-26 CA CA3054813A patent/CA3054813C/en active Active
-
2019
- 2019-07-26 ZA ZA2019/04916A patent/ZA201904916B/en unknown
- 2019-08-05 PH PH12019501795A patent/PH12019501795A1/en unknown
- 2019-08-07 US US16/535,035 patent/US10642643B2/en active Active
- 2019-12-16 AU AU2019101606A patent/AU2019101606A4/en active Active
-
2020
- 2020-01-17 US US16/745,519 patent/US10664305B1/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150379510A1 (en) * | 2012-07-10 | 2015-12-31 | Stanley Benjamin Smith | Method and system to use a block chain infrastructure and Smart Contracts to monetize data transactions involving changes to data included into a data supply chain. |
CN106330431A (zh) * | 2016-08-29 | 2017-01-11 | 北京瑞卓喜投科技发展有限公司 | 基于区块链技术的数据处理方法、装置及*** |
CN106406896A (zh) * | 2016-09-27 | 2017-02-15 | 北京天德科技有限公司 | 一种并行PipeLine技术的区块链建块方法 |
CN106980649A (zh) * | 2017-02-28 | 2017-07-25 | 阿里巴巴集团控股有限公司 | 写入区块链业务数据的方法和装置及业务子集合确定方法 |
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3545481A4 (en) * | 2018-11-27 | 2020-02-12 | Alibaba Group Holding Limited | SYSTEM AND METHOD FOR IMPROVING THE SECURITY OF AN INTELLIGENT CONTRACT ON A BLOCK CHAIN |
US11354727B2 (en) | 2018-11-27 | 2022-06-07 | Advanced New Technologies Co., Ltd. | System and method for improving security of smart contract on blockchain |
US11138597B2 (en) | 2018-11-27 | 2021-10-05 | Advanced New Technologies Co., Ltd. | System and method for improving security of smart contract on blockchain |
CN109766727B (zh) * | 2018-12-25 | 2021-04-06 | 苏州朗润创新知识产权运营有限公司 | 智能区块网络构建方法及*** |
CN109766727A (zh) * | 2018-12-25 | 2019-05-17 | 中链科技有限公司 | 智能区块网络构建方法及*** |
EP3571653A4 (en) * | 2018-12-28 | 2020-04-08 | Alibaba Group Holding Limited | EXECUTING PARALLEL TRANSACTIONS IN A BLOCK CHAIN NETWORK |
US11132676B2 (en) | 2018-12-28 | 2021-09-28 | Advanced New Technologies Co., Ltd. | Parallel execution of transactions in a blockchain network |
US11381573B2 (en) | 2018-12-28 | 2022-07-05 | Advanced New Technologies Co., Ltd. | Parallel execution of transactions in a blockchain network based on smart contract whitelists |
JP2020518880A (ja) * | 2018-12-28 | 2020-06-25 | アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited | スマートコントラクトホワイトリストに基づくブロックチェーンネットワークにおけるトランザクションの並列実行 |
JP7012730B2 (ja) | 2018-12-28 | 2022-01-28 | アドバンスド ニュー テクノロジーズ カンパニー リミテッド | スマートコントラクトホワイトリストに基づくブロックチェーンネットワークにおけるトランザクションの並列実行 |
WO2019072303A2 (en) | 2018-12-28 | 2019-04-18 | Alibaba Group Holding Limited | EXECUTING PARALLEL TRANSACTIONS IN A BLOCK CHAINS NETWORK |
US10911461B2 (en) | 2018-12-28 | 2021-02-02 | Advanced New Technologies Co., Ltd. | Parallel execution of transactions in a blockchain network based on smart contract whitelists |
KR102315473B1 (ko) | 2019-03-28 | 2021-10-21 | 어드밴스드 뉴 테크놀로지스 씨오., 엘티디. | 병렬-처리 블록체인 트랜잭션을 위한 시스템 및 방법 |
KR20200116011A (ko) * | 2019-03-28 | 2020-10-08 | 알리바바 그룹 홀딩 리미티드 | 병렬-처리 블록체인 트랜잭션을 위한 시스템 및 방법 |
JP2020519983A (ja) * | 2019-03-28 | 2020-07-02 | アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited | 並列処理ブロックチェーントランザクションのためのシステムおよび方法 |
US11310032B2 (en) | 2019-03-28 | 2022-04-19 | Advanced New Technologies Co., Ltd. | System and method for parallel-processing blockchain transactions |
US11057217B2 (en) | 2019-04-12 | 2021-07-06 | Advanced New Technologies Co., Ltd. | Performing parallel execution of transactions in a distributed ledger system |
US11082230B2 (en) | 2019-04-12 | 2021-08-03 | Advanced New Technologies Co., Ltd. | Performing parallel execution of transactions in a distributed ledger system |
US11106487B2 (en) | 2019-04-12 | 2021-08-31 | Advanced New Technologies Co., Ltd. | Performing parallel execution of transactions in a distributed ledger system |
WO2019120333A3 (en) * | 2019-04-12 | 2020-02-13 | Alibaba Group Holding Limited | Performing parallel execution of transactions in a distributed ledger system |
WO2019120334A3 (en) * | 2019-04-12 | 2020-02-13 | Alibaba Group Holding Limited | Performing parallel execution of transactions in a distributed ledger system |
US11231957B2 (en) | 2019-04-12 | 2022-01-25 | Alibaba Group Holding Limited | Performing parallel execution of transactions in a distributed ledger system |
WO2019120332A3 (en) * | 2019-04-12 | 2020-02-13 | Alibaba Group Holding Limited | Performing parallel execution of transactions in a distributed ledger system |
CN111095326A (zh) * | 2019-04-12 | 2020-05-01 | 阿里巴巴集团控股有限公司 | 在分布式账本***中进行交易的并行执行 |
CN111095326B (zh) * | 2019-04-12 | 2023-08-22 | 创新先进技术有限公司 | 用于在区块链网络中执行多个交易的方法、***和装置 |
Also Published As
Publication number | Publication date |
---|---|
RU2019124224A3 (zh) | 2021-02-01 |
KR102103130B1 (ko) | 2020-04-22 |
PH12019501795A1 (en) | 2020-03-09 |
TW201833796A (zh) | 2018-09-16 |
CN106980649A (zh) | 2017-07-25 |
MX2019009728A (es) | 2019-10-22 |
RU2744585C2 (ru) | 2021-03-11 |
US20190361731A1 (en) | 2019-11-28 |
AU2018228540A1 (en) | 2019-08-22 |
AU2018228540B2 (en) | 2020-09-03 |
CN106980649B (zh) | 2020-07-10 |
EP3561700A4 (en) | 2020-01-15 |
BR112019017863A2 (pt) | 2020-05-12 |
AU2019101606A4 (en) | 2020-01-23 |
JP6928104B2 (ja) | 2021-09-01 |
MY197445A (en) | 2023-06-19 |
US10664305B1 (en) | 2020-05-26 |
KR20190099087A (ko) | 2019-08-23 |
RU2019124224A (ru) | 2021-02-01 |
EP3561700A1 (en) | 2019-10-30 |
CA3054813A1 (en) | 2018-09-07 |
US10642643B2 (en) | 2020-05-05 |
CA3054813C (en) | 2021-04-20 |
US20200150999A1 (en) | 2020-05-14 |
TWI660281B (zh) | 2019-05-21 |
JP2020509495A (ja) | 2020-03-26 |
ZA201904916B (en) | 2020-08-26 |
SG11201907212SA (en) | 2019-09-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018157778A1 (zh) | 写入区块链业务数据的方法和装置及业务子集合确定方法 | |
WO2018214898A1 (zh) | 一种向区块链***中写入业务数据的方法和装置 | |
CN107392608B (zh) | 基于区块链***的数字资产交易方法及区块链*** | |
Shaikh et al. | Apache spark: A big data processing engine | |
JP2022547956A (ja) | ブロックチェーンデータをインデックスする方法およびブロックチェーンデータを格納する方法 | |
US10997154B2 (en) | Verifiable state machines | |
US20160210313A1 (en) | System for high-throughput handling of transactions in a data-partitioned, distributed, relational database management system | |
CN109977274A (zh) | 一种数据查询和验证方法、***、设备及存储介质 | |
Zhang et al. | A method to predict the performance and storage of executing contract for ethereum consortium-blockchain | |
CN110704438B (zh) | 一种区块链中布隆过滤器的生成方法及装置 | |
US20210311916A1 (en) | Blockchain-based hierarchical data storage | |
CN111724258B (zh) | 基于环形拓扑、依赖图及多版本控制的联盟链交易并发方案的实现方法 | |
WO2021027612A1 (zh) | 一种区块链中的交易执行方法及装置 | |
US10599614B1 (en) | Intersection-based dynamic blocking | |
CN108596824A (zh) | 一种基于gpu优化富元数据管理的方法和*** | |
US20240095241A1 (en) | Data search method and apparatus, and device | |
CN110490724A (zh) | 账户数据的存储方法和装置 | |
CN107832121B (zh) | 一种应用于分布式串行长事务的并发控制方法 | |
CN112817919A (zh) | 数据合并方法、装置及计算机可读存储介质 | |
CN115034794B (zh) | 一种区块链***的节点共识方法及装置 | |
Ma et al. | Key-Based Transaction Reordering: An Optimized Approach for Concurrency Control in Hyperledger Fabric | |
Kaur | Enhanced Bond Energy Algorithm for Vertical Fragmentation of IoT Data in a Fog Environment | |
CN116881361A (zh) | 交易的执行方法、节点和区块链*** | |
Şahin | Locality-aware distributed state partitioning for stream processing systems | |
CN115982126A (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: 18760329 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3054813 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 2018760329 Country of ref document: EP Effective date: 20190723 |
|
ENP | Entry into the national phase |
Ref document number: 20197023701 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2018228540 Country of ref document: AU Date of ref document: 20180226 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2019546907 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112019017863 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112019017863 Country of ref document: BR Kind code of ref document: A2 Effective date: 20190827 |