Automatic data projection of smart contract groups on blockchain
By creating and registering smart contract groups on the blockchain, the problem of inefficient data projection and execution on the distributed ledger is solved, efficient and secure data access and sharing is achieved, and network congestion is reduced.
Patent Information
- Application Number
- CN201980031273.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-05-15
- Filing Date
- 2019-04-17
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2039-04-17
AI Technical Summary
On distributed ledgers (such as blockchain), data projection and smart contract execution have problems such as inefficiency, network congestion and difficulty in data access control, especially in multi-party consensus and data sharing scenarios.
By creating and registering smart contract groups, authorized visitors are allowed to access data records on the blockchain, and optimize data projection and distribution through subscription services and approval processes to ensure atomicity and reduce network congestion.
It improves the efficiency of data projection and distribution, reduces network congestion, ensures the security and consistency of data access, and is suitable for multi-party consensus and data sharing scenarios.
Smart Images

Figure CN112154434B_ABST
Abstract
Description
Technical Field
[0001] The present application relates generally to data projection, and more particularly to performing automated data projection for smart contracts on a distributed ledger, such as a blockchain. Background Art
[0002] A ledger is generally defined as a book of entries in which transactions are recorded. A distributed ledger is a ledger that is replicated in whole or in part to multiple computers. A cryptographic distributed ledger (CDL) may have at least some of the following characteristics: irreversibility (once a transaction is recorded, it cannot be undone), accessibility (any party can access the CDL in whole or in part), chronological and timestamped (all parties know when a transaction was added to the ledger), consensus-based (transactions are added only when generally approved by all parties on the network), and verifiability (all transactions can be cryptographically verified). A blockchain is an example of a CDL. Although the description and drawings herein are described in terms of a blockchain, the present application is equally applicable to any CDL.
[0003] A distributed ledger is a growing list of records that are usually encrypted using cryptographic techniques such as storing cryptographic hashes in relation to other blocks. Blockchain is a common example of a distributed ledger that can be used as a public ledger to store information. Although primarily used for financial transactions, blockchain can store a variety of information related to goods and services (i.e. product, packaging, status, etc.). The decentralized scheme provides authority and trust to a decentralized network and enables its nodes to continuously and sequentially record their transactions on a public "block", thus creating a unique "chain" called a blockchain. Cryptography is used through hash codes to ensure the authentication of the transaction source and remove central intermediaries. Blockchain is a distributed database that maintains a growing list of records in the blockchain, which are protected from tampering and modification due to its immutable properties. Each block contains a timestamp and a link to the previous block. Blockchain can be used to save, track, transfer and verify information. Since blockchain is a distributed system, all peers need to reach a consensus state before a transaction is added to the blockchain ledger.
[0004] Conventionally, in various applications, data records generated by producers are projected onto subsets of their attributes and distributed to different data consumers. For example, for field S1, A data model 'A' record with field 'F' can be projected as R[Si]R|(Si) into n subsets. Each projection R[Si] is consumed independently by a subset of data consumers. Typically, producers and consumers are distributed over a network. Data can be generated at a high speed. Essentially, the application can be viewed as a distributed publish-subscribe system well known to those skilled in the art. A data record 'R' may have various different consumers using different subsets of the record 'R'. Organizing data records according to the expected consumer access operations can provide the best results. Summary of the invention
[0005] An example embodiment may provide a method comprising one or more of identifying data records to be included in a blockchain, creating a set of smart contracts to enable data consumers with access to the blockchain to access the data records, determining that the set of smart contracts has been registered by one or more blockchain peers, and storing the set of smart contracts on the blockchain.
[0006] Another example embodiment may include an apparatus comprising a processor configured to identify a data record to be included in a blockchain, create a set of smart contracts to enable data consumers with access to the blockchain to access the data record, determine that the set of smart contracts has been registered by one or more blockchain peers, and store the set of smart contracts on the blockchain.
[0007] Another example embodiment may provide a non-transitory computer-readable storage medium configured to store instructions that, when executed, cause a processor to perform identifying data records to be included in a blockchain, creating a set of smart contracts to enable data consumers with access to the blockchain to access the data records, determining that the set of smart contracts has been registered by one or more blockchain peers, and storing the set of smart contracts on the blockchain. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings, in which:
[0009] Figure 1A A network diagram illustrating a blockchain data record management configuration according to an example embodiment.
[0010] Figure 1B A network diagram illustrating a blockchain data record management configuration using a set of smart contracts according to an example embodiment.
[0011] Figure 1C A network diagram of a blockchain data record management configuration for inserting data records by a producing peer is shown according to an example embodiment.
[0012] Figure 1D A network diagram illustrating a blockchain data record management configuration for an ordering service for inserting data records by a producing peer, according to an example embodiment.
[0013] Figure 2A An example peer node blockchain architecture configuration for data record management is shown according to an example embodiment.
[0014] Figure 2B An example peer node blockchain configuration is shown according to an example embodiment.
[0015] Figure 3 is a diagram illustrating a permissioned blockchain network according to an example embodiment.
[0016] Figure 4 A system message diagram for performing data record management according to an example embodiment is shown.
[0017] Figure 5 A flow chart illustrating an example method of data record management in a blockchain according to an example embodiment is shown.
[0018] Fig. 6A An example physical infrastructure configured to perform various operations on a blockchain according to one or more operations described herein is shown according to an example embodiment.
[0019] Figure 6B An example smart contract configuration between contracting parties and an intermediary server configured to execute smart contract terms on a blockchain is shown according to an example embodiment.
[0020] Figure 7 An example computer system configured to support one or more example embodiments is shown. DETAILED DESCRIPTION
[0021] It will be readily appreciated that the instant components, as generally described and illustrated in the figures herein, may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of embodiments of at least one of the methods, devices, non-transitory computer-readable media, and systems, as illustrated in the figures, is not intended to limit the scope of the claimed application, but is representative of selected embodiments only.
[0022] The instant features, structures, or characteristics described throughout the specification may be combined in any suitable manner in one or more embodiments. For example, throughout the specification, the use of the phrases "example embodiments," "some embodiments," or other similar language refers to the fact that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment. Therefore, throughout the specification, the appearance of the phrases "example embodiments," "in some embodiments," "in other embodiments," or other similar language does not necessarily refer to the same set of embodiments, and the described features, structures, characteristics may be combined in any suitable manner in one or more embodiments.
[0023] In addition, although the term "message" may have been used in the description of the embodiments, the present application can be applied to many types of network data, such as packets, frames, datagrams, etc. The term "message" also includes packets, frames, datagrams, and any equivalent thereof. In addition, although certain types of messages and signaling may be depicted in exemplary embodiments, they are not limited to specific types of messages, and the present application is not limited to specific types of signaling.
[0024] Example embodiments provide methods, devices, networks, and / or systems that provide projection and distribution of data on a blockchain network. Producers / consumers of data can be peer users of an enterprise blockchain network. Smart contracts can be used to implement data insertion, projection, and distribution. Specifically, for each projection Si, there is a channel Ci with all producing peers (i.e., peers that produce records) and all consuming peers Si (i.e., peers that consume fields corresponding to Si).
[0025] A blockchain is a distributed system that consists of multiple nodes that communicate with each other. Blockchain operating programs (e.g., smart contracts, etc.) called chaincodes save state and ledger data and execute transactions. Some transactions are operations called on chaincodes. Typically, blockchain transactions must be "endorsed" by certain blockchain members, and only endorsed transactions can be submitted to the blockchain and affect the state of the blockchain. Other unendorsed transactions will be ignored. There may be one or more special chaincodes for managing functions and parameters, collectively referred to as system chaincodes.
[0026] A node is a communication entity of a blockchain system. A "node" can perform a logical function in the sense that multiple nodes of different types can run on the same physical server. Nodes are grouped in trust domains and are associated with logical entities that control them in various ways. Nodes can include different types, such as client or submit client nodes, which submit transaction calls to signatories (e.g., peers) and broadcast transaction proposals to ordering services (e.g., ordering nodes). Another type of node is a peer node, which can receive transactions submitted by clients, submit transactions, and maintain a copy of the state and blockchain transaction ledger. Although not required, peers can also play the role of endorsers. Ordering service nodes or orderers are nodes that run communication services for all nodes and implement delivery guarantees, such as broadcasting to every peer node in the system when submitting transactions and modifying the world state of the blockchain, which is another name for the initial blockchain transaction, which usually contains control and setup information.
[0027] The ledger is an ordered, tamper-proof record of all state transitions of the blockchain. State transitions can be caused by chaincode invocations (i.e., transactions) submitted by participating parties (e.g., client nodes, ordering nodes, endorser nodes, peer nodes, etc.). A transaction may result in a set of asset key-value pairs being submitted to the ledger as one or more operands (e.g., create, update, delete, etc.). The ledger includes a blockchain (also called a chain) that is used to store immutable, sequential records in blocks. The ledger also includes a state database that is used to maintain the current state of the blockchain. There is typically one ledger per channel. Each peer node maintains a copy of the ledger for each channel it belongs to.
[0028] A chain is a transaction log that is structured as hash-linked blocks, and each block contains a sequence of N transactions, where N is equal to or greater than one. The block header includes the hash of the transactions in that block, as well as the hash of the previous block header. In this way, all transactions on the ledger can be ordered and cryptographically linked together. Therefore, it is impossible to tamper with the ledger data without breaking the hash links. The hash of the most recently added blockchain block represents every transaction that occurred previously on the chain, ensuring that all peer nodes are in a consistent and trusted state. The chain can be stored on the peer node file system (i.e., local, attached storage, cloud, etc.), effectively supporting the append-only nature of blockchain workloads.
[0029] The current state of the immutable ledger represents the latest values for all keys included in the chained transaction log. Because the current state represents the latest key values known to the channel, it is sometimes referred to as the world state. Chaincode invocations execute transactions against the current state data of the ledger. In order for these chaincode interactions to be efficient, the latest values of the keys can be stored in a state database. The state database may be just an indexed view of the chain's transaction log, so it can be regenerated from the chain at any time. The state database can be automatically restored (or generated on demand) at peer startup and before accepting transactions.
[0030] Multiple smart contracts can be created and assigned to certain portions of a data record "R" that are different or the same for each smart contract. For example, separate smart contracts corresponding to separate channels and certain subsets of fields of a data record "R" are created and shared with a group of data consumers. Two different smart contracts will correspond to two different subsets of data fields, or there will be redundancy between certain smart contracts identifying the same portions of a data record "R".
[0031] Figure 1A A network diagram of a blockchain data record management configuration according to an example embodiment is shown. In this configuration 100A, a record "R" 102 is identified by a data management application running on each peer node of the blockchain. The application identifies the record R and computes a projection R[Si] for each "i", such as R[S1] 104, R[S2] 106, and R[S3] 108. A transaction "proposal" is a call for smart contract execution sent from the application to an endorsing peer. Proposals P1-110, P2-112, and P3-114 are sent to the endorsement process by peer 116, and endorsed proposals 118, 122, and 124 are forwarded to the ordering service 126 for blockchain commitment. The peer simulates the smart contract execution to produce a subsequent set of changes to the ledger (i.e., a read / write set), which are called endorsed transaction proposals 118-124 and sent back to the application. If the peer accepts the submission on its ledger, the application sends the approved transaction proposal 118-124 to the ordering service 126, which adds the transaction to a blockchain block that may contain other transactions.
[0032] A channel is a set of blockchain peers that share a distributed ledger corresponding to the channel and accessible only to its peers. A channel may have several smart contracts instantiated that modify the shared ledger. Each channel maintains a separate transaction blockchain by its peers. A call proposal is the same as a smart contract transaction proposal. It is also possible to execute a smart contract to only query the ledger without changing its state, which would be a query proposal that is executed only by the peer and provides the result of its local ledger to the calling application.
[0033] Figure 1B A network diagram of a blockchain data record management configuration using a set of smart contracts according to an example embodiment is shown. Figure 1B , configuration 100B includes record R 102, where projections R[S1] 104 to R[S3] 108 are processed by a group call proposal [P] 132, which is approved by peer 116 to create an approved group call proposal P 134. A group call is a "group" of combined executions of multiple "smart contracts" on the same data record. The group call proposal is sent by the application to the approving peer, which simulates the execution of all the constituent smart contracts and generates approved transaction proposals, which are combined into an approved group call proposal. The group call proposal is received by the application and then sent to the subscription service 126. Since different approved transaction proposals in the approved group call proposal can correspond to different channels, they are assigned to their respective channel's blocks. This involves decomposing the approved group call proposal into approved transaction proposals and reorganizing the approved transaction proposals into channel-specific blocks corresponding to different peers.
[0034] Figure 1C A network diagram of a blockchain data record management configuration for inserting data records by a production peer is shown according to an example embodiment. Figure 1C , example configuration 100C provides for the insertion of records by the producing peer. If an approved group call proposal "P" 142 is received and decomposed 144, the result is multiple separate approved proposals P1 148 to P3 152. The ordering service 150 decomposes the approved group call proposal into smart contract-level approved proposals. For each peer (producer and consumer), the ordering service sends the appropriate re-aggregation of the approved smart contract proposals as a commit transaction to the blockchain. This approach provides atomicity of group call operations until the dispatch operation performed by the ordering service 150. For example, the individual transactions of the smart contracts that make up the smart contract group are approved by the peers and dispatched by the ordering service, otherwise, no smart contract / transaction will be dispatched. This approach reduces the amount of network congestion caused by bundling in group call proposals.
[0035] Figure 1D A network diagram illustrating a blockchain data record management configuration for an ordering service for inserting data records by a producing peer according to an example embodiment. Figure 1D, configuration 100D provides for each producing peer to register its group with the ordering / endorsement service. The registration can provide a "group ID" 169 for each smart contract 164, 166, and 168 in the group, a record field 162 with the smart contract ID in the group, and a projection specific to the producing peer. This information is validated during the registration process. Group call proposals created by a peer include the group ID and the data record to be inserted. The endorsement service uses the group's registration information to endorse the proposal. This code exists at the endorsement policy level and is not part of any smart contract. The endorsed proposal includes the group ID and read / write sets for each smart contract in the group. The reaggregated transaction created by the ordering service for the peer includes the relevant read / write sets.
[0036] In the above about Figure 1D In the described use case, the base smart contract is used to compute and store its own ledger as a projection of the same data input record onto a subset of its fields. The term "projection" provides that smart contracts "1", "2" and "3" are projections. The constituent smart contracts, the set of fields of the input data record and the group ID used for identification provide a group of smart contracts. This information is registered with the peer and the ordering service. The application simply sends its input data record and group ID to the peer as part of its group call proposal group. The peer uses the group ID to determine the group of smart contracts to execute on the input data record to generate an approved group call proposal.
[0037] These examples provide producers with the ability to define a group of smart contracts that are independent of each other. The group receives a subset of the same data records as input and treats a "call" as a combined proposal or a single group call based on multiple members in the group. This approach improves communication efficiency by eliminating network congestion.
[0038] In a specific example of a medical data sharing network, hospitals are producers of medical data, while related service (e.g., insurance, medical drug research) entities are consumers of the data. The medical data produced by the producer can be in the form of a per-patient record with fields corresponding to the patient's identity as well as various test results. These records are intended to be shared with consumers after appropriate filtering and projection in accordance with privacy and / or contractual policies. Blockchain implementations can provide an efficient and powerful solution for medical data sharing by implementing a group smart contract approach. Hospitals are producing peers, while federated service entities are consuming peers. Smart contract channels will be deployed for each desired data projection, along with appropriately defined and registered smart contract groups on the network.
[0039] Figure 2A A blockchain architecture configuration 200 is shown according to an example embodiment. Figure 2A, the blockchain architecture 200 may include certain blockchain elements, such as a set of blockchain nodes 202. The blockchain nodes 202 may include one or more nodes 204-210 (four nodes are described by way of example only). These nodes participate in many activities, such as blockchain transaction addition and verification processes (consensus). One or more of the blockchain nodes 204-210 may endorse transactions and may provide ordering services for all blockchain nodes in the architecture 200. The blockchain node may initiate a blockchain authentication and attempt to write to the blockchain immutable ledger stored in the blockchain layer 216, a copy of which may also be stored on the underlying physical infrastructure 214. The blockchain configuration may include one or more applications 224 that are linked to an application programming interface (API) 222 to access and execute stored program / application code 220 (e.g., chain code, smart contracts, etc.), which may be created based on the custom configuration sought by the participants and may maintain its own state, control its own assets, and receive external information. It may be deployed as a transaction and installed on all blockchain nodes 204-210 by attaching it to the distributed ledger.
[0040] The blockchain foundation or platform 212 may include various layers of blockchain data, services (e.g., cryptographic trust services, virtual execution environments, etc.), and supporting physical computer infrastructure that can be used to receive and store new transactions and provide access to auditors seeking to access data entries. The blockchain layer 216 may expose an interface that provides access to the virtual execution environment necessary to process program code and use the physical infrastructure 214. Cryptographic trust services 218 may be used to verify transactions such as asset exchange transactions and keep information private.
[0041] Figure 2A The blockchain architecture configuration may process and execute program / application code 220 via one or more interfaces exposed by the blockchain platform 212 and the services provided. The code 220 may control blockchain assets. For example, the code 220 may store and transmit data and may be executed by nodes 204-210 in the form of smart contracts and associated chain codes with conditions or other code elements subject to execution conditions. As a non-limiting example, a smart contract may be created to execute reminders, updates, and / or other notifications subject to such changes, updates, etc. The smart contract itself may be used to identify rules related to authorization and access requirements and ledger usage.
[0042] In chaincode, smart contracts can be created by high-level applications and programming languages and then written into blocks in the blockchain. Smart contracts can include executable code that is registered, stored, and / or replicated to a blockchain (e.g., a distributed network of blockchain peers). A transaction is the execution of smart contract code that can be executed in response to the satisfaction of a condition associated with a smart contract. The execution of a smart contract can trigger trusted modifications to the state of a digital blockchain ledger. Modifications to the blockchain ledger caused by the execution of a smart contract can be automatically replicated throughout the distributed network of blockchain peers through one or more consensus protocols.
[0043] Smart contracts can write data to the blockchain in the format of key-value pairs. In addition, smart contract code can read values stored in the blockchain and use them in application operations. Smart contract code can write the output of various logical operations to the blockchain. The code can be used to create temporary data structures in a virtual machine or other computing platform. The data written to the blockchain can be public and / or can be encrypted and maintained as private. Temporary data used / generated by smart contracts is kept in memory by the provided execution environment and deleted once the data is identified as required by the blockchain.
[0044] A chaincode may include a code interpretation of a smart contract with additional features. As described herein, a chaincode may be a program code deployed on a computing network, wherein chaincode validators execute and validate the chaincode together in a consensus process. The chaincode receives the hash and retrieves from the blockchain a hash associated with a data template created using a previously stored feature extractor. If the hash value of the hashed identifier matches the hash value created from the stored identifier template data, the chaincode sends the authorization key to the requested service. The chaincode may write data associated with cryptographic details to the blockchain. Figure 2A In one example, certain subsets of data records are identified as potential data sets 226 for group call proposals, which can optimize network performance and provide optimal access to various different parties. Different smart contracts 228 can be defined to represent different parts of the data records. The smart contract set can be set as a set of smart contracts 228 that are identified and recognized by one or more blockchain peer nodes 201.
[0045] Figure 2B An example of a transaction flow 250 between nodes of a blockchain according to an example embodiment is shown. Figure 2B, a transaction flow may include a transaction proposal 291 sent by an application client node 260 to an endorsing peer node 281. The endorsing peer 281 may verify the client signature and execute the chaincode function to initiate the transaction. The output may include a chaincode result, a set of key / value versions read in the chaincode (read set), and a set of key / values written in the chaincode (write set). If approved, a proposal response 292 is sent back to the client 260 along with the endorsement signature. The client 260 assembles the endorsement into a transaction payload 293 and broadcasts it to the ordering service node 284. The ordering service node 284 then delivers the ordered transaction as a block to all peers 281-283 on the channel. Each peer 281-283 may validate the transaction before committing to the blockchain. For example, a peer may check the endorsement policy to ensure that the correct assignment of the specified peer has signed the result and verified the signature against the transaction payload 293.
[0046] Reference again Figure 2B , the client node 260 initiates a transaction 291 by constructing a request and sending it to the peer node 281 as the approved issuer. The client 260 may include an application utilizing a supported software development kit (SDK) such as NODE, JAVA, PYTHON, etc., which utilizes the available API to generate a transaction proposal. The proposal is a request to invoke a chaincode function so that data can be read and / or written to the ledger (i.e., write a new key-value pair for an asset). The SDK can act as a shim to package the transaction proposal into an appropriate architectural format (e.g., protocol buffers over remote procedure calls (RPCs)) and generate a unique signature for the transaction proposal using the client's cryptographic credentials.
[0047] In response, the endorsing peer node 281 can verify that (a) the transaction proposal is formatted correctly; (b) the transaction has not been submitted in the past (replay attack protection); (c) the signature is valid; and (d) the submitter (client 260 in this example) is properly authorized to perform the proposed operation on the channel. The endorsing peer node 281 can input the transaction proposal as a parameter to the invoked chaincode function. The chaincode is then executed against the current state database to generate a transaction result, which includes a response value, a read set, and a write set. However, no updates have been made to the ledger at this time. In 292, the set of values, along with the endorsing peer node 281 signature, is passed back to the SDK of client 260 as a proposal response 292, which parses the payload for application consumption.
[0048] In response, the client 260 application checks / verifies the endorsed peer signature and compares the proposal response to determine if the proposal responses are the same. If the chaincode only queries the ledger, the application will check the query response and typically will not submit the transaction to the ordering node service 284. If the client application intends to submit the transaction item to the ordering node service 284 to update the ledger, the application determines whether the specified endorsement policy has been met before submission (i.e., all peer nodes required for the transaction endorse the transaction). Here, the client may include only one of the multiple parties to the transaction. In this case, each client may have its own endorsement node, and each endorsement node is required to endorse the transaction. The architecture is such that even if the application chooses not to check the response or forward unapproved transactions, the endorsement policy will still be enforced by the peers and maintained during the submission verification phase.
[0049] After successful checks, in step 293, client 260 assembles the endorsements into a transaction and broadcasts the transaction proposal and response within a transaction message to ordering node 284. The transaction may contain a read / write set, an endorsing peer signature, and a channel ID. Ordering node 284 does not need to examine the entire contents of a transaction in order to perform its operations, instead, ordering node 284 may simply receive transactions from all channels in the network, sort them chronologically by channel, and create a transaction block for each channel.
[0050] The block of transactions is passed from the ordering node 284 to all peer nodes 281-283 on the channel. Transactions within the block are validated 294 to ensure that any endorsement policies are satisfied and that the ledger state of the read set variables has not changed since the transaction execution generated the read set. The transactions in the block are marked as valid or invalid. In addition, in step 295, each peer node 281-283 appends the block to the channel chain and, for each valid transaction, commits the write set to the current state database. An event is emitted to notify the client application that the transaction (call) has been immutably attached to the chain and whether the transaction is valid or invalid.
[0051] Figure 3An example of a permissioned blockchain network 300 is shown, featuring a distributed, decentralized, peer-to-peer architecture and a certificate authority 318 that manages user roles and permissions. In this example, a blockchain user 302 can submit a transaction to a permissioned blockchain network 310. In this example, the transaction can be a deployment, call, or query, and can be issued through a client application utilizing an SDK, directly through a REST API, etc. A trusted business network can provide access to a regulator system 314 such as an auditor (e.g., the Securities Commission in the U.S. stock market). At the same time, the blockchain network operator system of node 312 manages member permissions, such as registering the regulator system 310 as an "auditor" and registering the blockchain user 302 as a "client." Auditors may be limited to querying the ledger, while clients may be authorized to deploy, call, and query certain types of chaincodes.
[0052] The blockchain developer system 316 writes chaincode and client applications. The blockchain developer system 316 can deploy chaincode directly to the network through a REST interface. In order to include credentials from a traditional data source 330 in the chaincode, the developer system 316 can use an out-of-band connection to access the data. In this example, a blockchain user 302 connects to the network through a peer node 308. Before conducting any transactions, the peer node 308 retrieves the user's registration and transaction certificates from the certificate authority 318. In some cases, blockchain users must have these certificates in order to conduct transactions on the permissioned blockchain network 310. At the same time, users trying to drive the chaincode may be required to verify their credentials on the traditional data source 330. To confirm the user's authorization, the chaincode can use an out-of-band connection to the data through a traditional processing platform 320.
[0053] Figure 4 A system message diagram for performing data record management according to an example embodiment is shown. Figure 4 , a system configuration 400 provides a set of blockchain peers 410, an ordering service 420 for managing blockchain transactions, and a blockchain 430. In one example, a peer may receive a data record proposal 412 for a data record and approve 414 the data record proposal, which will be represented by a set of smart contracts in the blockchain. The approved proposal may be forwarded 416 to the ordering service 420, where the proposal may be decomposed 418 into individual smart contract-level blockchain transactions, which are reaggregated 422 into transaction blocks for submission to the blockchain 430. The transaction blocks are forwarded 424 to the blockchain and submitted 426.
[0054] Figure 5 A flowchart of an example method of data record management in a blockchain according to an example embodiment is shown. Figure 5, method 500 includes identifying a data record to be included in a blockchain 512, creating a set of smart contracts to enable data consumers with access to the blockchain to access the data record 514, determining that the smart contract group has been registered by one or more blockchain peers 516, and storing the smart contract group on the blockchain 518. The method may also include assigning different portions of the data record to the smart contract group so that each smart contract in the smart contract group is assigned a different portion of the data record. The method may further include: identifying a group call transaction proposal including a plurality of smart contract-level data record access proposals associated with the data record; endorsing the group call transaction proposal by one or more blockchain peers; and sending the group call transaction proposal to a subscription service, decomposing the endorsed group call transaction proposal into a plurality of individually endorsed smart contracts, transmitting a plurality of endorsed transactions corresponding to the one or more blockchain peers from the subscription service as blockchain transactions to be submitted to the blockchain, and performing registration of one or more groups with the subscription service, the registration including a group identifier, a record field, and a smart contract identifier corresponding to the smart contract group.
[0055] Fig. 6A An example physical infrastructure configured to perform various operations on a blockchain according to one or more example operating methods according to example embodiments is shown. Fig. 6A , the example configuration 600 includes a physical infrastructure 610 with a blockchain 620 and a smart contract 640, which can perform any operation steps 612 included in any example embodiment. Steps / operations 612 may include one or more steps described or depicted in one or more flow charts and / or logic diagrams. These steps may represent output or written information written or read from one or more smart contracts 640 and / or blockchains 620 residing on the physical infrastructure 610 of the computer system configuration. Data may be output from the executed smart contracts 640 and / or blockchains 620. The physical infrastructure 610 may include one or more computers, servers, processors, memories, and / or wireless communication devices.
[0056] Figure 6B An example smart contract configuration between contracting parties and an intermediary server configured to enforce smart contract terms on a blockchain is shown according to an example embodiment. Figure 6B, configuration 650 may represent a communication session, an asset transfer session, or a process or procedure driven by a smart contract 640 that explicitly identifies one or more user devices 652 and / or 656. The execution, operation, and results of the smart contract execution may be managed by a server 654. The contents of the smart contract 640 may require digital signatures by one or more of the entities 652 and 656 that are parties to the smart contract transaction. The results of the smart contract execution may be written to the blockchain as a blockchain transaction.
[0057] The above embodiments may be implemented in hardware, in a computer program executed by a processor, in firmware, or in a combination thereof. The computer program may be embodied on a computer-readable medium such as a storage medium. For example, the computer program may reside in a random access memory ("RAM"), a flash memory, a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM"), an electrically erasable programmable read-only memory ("EEPROM"), a register, a hard disk, a removable disk, a compact disk read-only memory ("CD-ROM"), or any other form of storage medium known in the art.
[0058] An exemplary storage medium may be coupled to a processor such that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium may be integrated with the processor. The processor and the storage medium may reside in an application specific integrated circuit ("ASIC"). In an alternative, the processor and the storage medium may reside as discrete components. For example, Figure 7 An example computer system architecture 700 is shown, which may represent or be integrated in any of the above-described components, among others.
[0059] Figure 7 It is not intended to imply any limitation on the scope of use or functionality of the application embodiments described herein. Regardless, computing node 700 is capable of being implemented and / or performing any of the functionality set forth above.
[0060] In computing node 700, there is a computer system / server 702, which can operate with numerous other general or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and / or configurations that may be suitable for use with computer system / server 702 include, but are not limited to, personal computer systems, server computer systems, thin clients, fat clients, manual handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments including any of the above systems or devices, and the like.
[0061] Computer system / server 702 may be described in the general context of computer system executable instructions (e.g., program modules) executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, etc. that perform specific tasks or implement specific abstract data types. Computer system / server 702 may be practiced in a distributed cloud computing environment where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in local and remote computer system storage media including memory storage devices.
[0062] like Figure 7 As shown, a computer system / server 702 in a cloud computing node 700 is shown in the form of a general-purpose computing device. Components of the computer system / server 702 may include, but are not limited to, one or more processors or processing units 704, a system memory 706, and a bus that couples various system components including the system memory 706 to the processor 704.
[0063] The bus represents any one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example and not limitation, such architectures include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.
[0064] Computer system / server 702 generally includes various computer system readable media. Such media can be any available media accessible to computer system / server 702, and it includes volatile and non-volatile media, removable and non-removable media. In one embodiment, system memory 706 implements the flow charts of other figures. System memory 706 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 710 and / or cache memory 712. Computer system / server 702 can further include other removable / non-removable, volatile / non-volatile computer system storage media. As an example only, a storage system 714 can be provided for reading and writing non-removable non-volatile magnetic media (not shown and generally referred to as "hard drive"). Although not shown, a disk drive for reading and writing from a removable non-volatile disk (such as a "floppy disk") and an optical disk drive for reading or writing from a removable non-volatile optical disk (CD-ROM, DVD-ROM or other optical media or the like) can be provided. In this case, each can be connected to the bus through one or more data medium interfaces. As will be further depicted and described below, memory 706 may include at least one program product having a set (eg, at least one) of program modules configured to perform the functions of various embodiments of the present application.
[0065] A program / utility 716 having a set (at least one) of program modules 718 may be stored in the memory 706, as well as an operating system, one or more application programs, other program modules, and program data, by way of example and not limitation. Each of the operating system, one or more application programs, other program modules, and program data, or some combination thereof, may include an implementation of a networking environment. The program modules 718 generally perform the functions and / or methods of various embodiments of the present application as described herein.
[0066] As will be appreciated by those skilled in the art, aspects of the present application may be embodied as a system, method or computer program product. Therefore, aspects of the present application may take the following forms: a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.) or an embodiment combining software and hardware aspects, which may generally all be referred to as "circuit", "module" or "system" in this article. In addition, aspects of the present application may take the form of a computer program product, which is embodied in one or more computer-readable media, and the medium has a computer-readable program code embodied therein.
[0067] The computer system / server 702 may also communicate with one or more external devices 720 (e.g., keyboard, pointing device, display 722, etc.), with one or more devices that enable a user to interact with the computer system / server 702; with and / or any device that enables the computer system / server 702 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may occur via I / O interface 724. However, the computer system / server 702 may still communicate with one or more networks (such as a local area network (LAN), a general wide area network (WAN), and / or a public network (e.g., the Internet)) through a network adapter 726. As shown, the network adapter 726 communicates with other components of the computer system / server 702 via a bus. It should be understood that, although not shown, other hardware and / or software components may be used in conjunction with the computer system / server 702. Examples include, but are not limited to, microcode, device drivers, redundant processing units, external disk drives, arrays, RAID systems, tape drives, and data archive storage systems.
[0068] Although illustrated in the drawings and described in the foregoing specific embodiments, at least one exemplary embodiment of the system, method and non-transitory computer-readable medium, it should be understood that the present application is not limited to the disclosed embodiments, but can be many rearrangements, modifications and replacements as set forth and defined in the appended claims. For example, the capabilities of the systems of the various drawings can be performed by one or more of the modules or components described herein or in a distributed architecture, and can include a transmitter, a receiver or a pair of both. For example, all or part of the functions performed by each module can be performed by one or more of these modules. In addition, the functions described herein can be performed at various times inside or outside the module or component and in relation to various events. Moreover, the information sent between various modules can be sent between each module via at least one of the following: data network, Internet, voice network, Internet protocol network, wireless device, wired device and / or through multiple protocols. Moreover, the message sent or received by any module can be sent or received directly and / or via one or more other modules.
[0069] Those skilled in the art will appreciate that a "system" may be embodied as a personal computer, server, console, personal digital assistant (PDA), cell phone, tablet computing device, smart phone, or any other suitable computing device or combination of devices. Presenting the above functions as being performed by a "system" is not intended to limit the scope of the present application in any way, but is intended to provide an example of many embodiments. In fact, the methods, systems, and apparatus disclosed herein may be implemented in local and distributed forms consistent with computing technology.
[0070] It should be noted that some of the system features described in this specification have been presented as modules in order to more specifically emphasize their implementation independence. For example, a module can be implemented as a hardware circuit that includes a custom very large scale integrated circuit (VLSI) circuit or gate array, an off-the-shelf semiconductor (e.g., logic chip, transistor), or other discrete components. A module can also be implemented in a programmable hardware device such as a field programmable gate array, programmable array logic, a programmable logic device, a graphics processing unit, etc.
[0071] Modules may also be implemented, at least in part, with software for execution by various types of processors. The identified executable code units may, for example, include one or more physical or logical blocks of computer instructions, which may, for example, be organized as objects, processes, or functions. However, the executable files of the identified modules need not be physically located together, but may include different instructions stored in different locations, which, when logically combined together, include the modules and achieve the purpose of the modules. In addition, modules may be stored on a computer-readable medium, which may be, for example, a hard drive, a flash memory device, a random access memory (RAM), a magnetic tape, or any other such medium for storing data.
[0072] In fact, the module of executable code can be a single instruction, or multiple instructions, and can even be distributed across multiple different code segments, between different programs, and multiple storage devices. Similarly, in this article, operating data can be identified and shown in the module, and can be embodied in any suitable form and can be organized in any suitable type of data structure. The operating data can be collected as a single data set, or can be distributed in different locations including different storage devices, and can exist at least partially only as electronic signals on a system or network.
[0073] It will be easily understood that the components of the present application can be arranged and designed in a variety of different configurations as generally described and shown in the drawings herein. Therefore, the detailed description of the embodiments is not intended to limit the scope of the claimed application, but only represents the selected embodiments of the present application.
[0074] Those skilled in the art will readily appreciate that the above content may be practiced with steps in a different order and / or with hardware elements in a configuration different from that disclosed. Therefore, although the present application has been described based on these preferred embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative configurations will be apparent.
[0075] Although preferred embodiments of the present application have been described, it should be understood that the described embodiments are merely illustrative and that the scope of the present application is limited solely by the appended claims when considering all equivalents and scopes thereof (e.g., protocols, hardware devices, software platforms, etc.).
Claims
1. A method, include: Receiving, by an ordering service in a blockchain network, a group approval proposal approved by peer nodes among a plurality of peer nodes included in the blockchain network, the group approval proposal comprising a plurality of blockchain transactions, wherein the group approval proposal is represented by a plurality of smart contracts in the blockchain network; Decomposing, by an ordering service, the plurality of blockchain transactions included in the group endorsement proposal into separate smart contract-level blockchain transactions; re-aggregating the decomposed smart contract-level blockchain transactions into blockchain transaction blocks by the ordering service; and The blockchain transaction block is forwarded to the blockchain ledger by the ordering service.
2. The method according to claim 1, in, Each of the multiple smart contracts corresponds to a different field in the data record.
3. The method according to claim 1, further comprising: include: Based on the channel assigned to the smart contract executed to generate the approved blockchain transaction, the approved blockchain transaction is assigned to the corresponding block.
4. The method according to claim 1, further comprising: include: Submitting the blockchain transaction block to the blockchain ledger.
5. The method according to claim 1, further comprising: include: The subscription service registration group identifier, the record fields and the smart contract identifiers corresponding to the multiple smart contracts.
6. A device, include: Processor, configured as: Receiving, by an ordering service in a blockchain network, a group approval proposal approved by peer nodes among a plurality of peer nodes included in the blockchain network, the group approval proposal comprising a plurality of blockchain transactions, wherein the group approval proposal is represented by a plurality of smart contracts in the blockchain network; Decomposing, by an ordering service, the plurality of blockchain transactions included in the group endorsement proposal into separate smart contract-level blockchain transactions; re-aggregating the decomposed smart contract-level blockchain transactions into blockchain transaction blocks by the ordering service; and The blockchain transaction block is forwarded to the blockchain ledger by the ordering service.
7. The device as claimed in claim 6, in, Each of the multiple smart contracts corresponds to a different field in the data record.
8. The device as claimed in claim 6, in, The processor is further configured to: Based on the channel assigned to the smart contract executed to generate the approved blockchain transaction, the approved blockchain transaction is assigned to the corresponding block.
9. The device as claimed in claim 6, in, The processor is further configured to: Submitting the blockchain transaction block to the blockchain ledger.
10. The device according to claim 6, in, The processor is further configured to: A registration group identifier, record fields, and smart contract identifiers corresponding to the multiple smart contracts.
11. A non-transitory computer-readable storage medium configured to store instructions that, when executed, cause a processor to: receiving, by an ordering service in a blockchain network, a group approval proposal approved by peer nodes among a plurality of peer nodes included in the blockchain network, the group approval proposal including a plurality of blockchain transactions, in, The group approval proposal is represented by a plurality of smart contracts in the blockchain network; Decomposing, by an ordering service, the plurality of blockchain transactions included in the group endorsement proposal into separate smart contract-level blockchain transactions; The ordering service reaggregates the decomposed smart contract-level blockchain transactions into blockchain transaction blocks; as well as The blockchain transaction block is forwarded to the blockchain ledger by the ordering service.
12. The non-transitory computer-readable storage medium of claim 11, in, Each of the multiple smart contracts corresponds to a different field in the data record.
13. The non-transitory computer-readable storage medium of claim 11, in, The processor is further configured to perform: Based on the channel assigned to the smart contract executed to generate the approved blockchain transaction, the approved blockchain transaction is assigned to the corresponding block.
14. The non-transitory computer-readable storage medium of claim 11, in, The processor is further configured to perform: Submitting the blockchain transaction block to the blockchain ledger.
15. The non-transitory computer-readable storage medium of claim 11, in, The processor is further configured to perform: A registration group identifier, record fields, and smart contract identifiers corresponding to the multiple smart contracts.
