CN110990408B - Business information collaboration method based on block chain, business system and alliance chain - Google Patents
Business information collaboration method based on block chain, business system and alliance chain Download PDFInfo
- Publication number
- CN110990408B CN110990408B CN201911211636.XA CN201911211636A CN110990408B CN 110990408 B CN110990408 B CN 110990408B CN 201911211636 A CN201911211636 A CN 201911211636A CN 110990408 B CN110990408 B CN 110990408B
- Authority
- CN
- China
- Prior art keywords
- data form
- information
- shared data
- query
- consensus authentication
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- 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
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The application discloses a business information cooperation method based on a block chain, a business system and a alliance chain, wherein the method comprises the following steps: receiving a query request submitted by a user, and extracting stored query information associated with the query request; manufacturing a shared data form; signing the shared data form by using the stored private key, diffusing the shared data form into a alliance chain, verifying the signature of the shared data form by using the public key by a node receiving the shared data form, and adding query information which is stored by the node and is associated with the query request into the shared data form; after all service systems in the alliance chain add the query information into the shared data form, participating in the consensus authentication of the query information in the shared data form; after the consensus authentication is completed, acquiring a complete data form subjected to the consensus authentication; and feeding back query information in the complete data form to the user. The application can realize information resource sharing and data integration between business departments and improve the safety of the business departments.
Description
Technical Field
The present application relates to the field of blockchain technologies, and in particular, to a blockchain-based service information collaboration method, a blockchain-based service system, and a federation chain.
Background
This section is intended to provide a background or context to the embodiments of the application that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
With the rise of the internet, the conventional service system is not capable of meeting the requirements of people. The current business system adopts a centralized mode, which mainly has the following problems:
1. databases among business departments are independent, information resources cannot be shared, an integration interface is lacked, information integration difficulty is high, and complete data cannot be provided for the outside.
2. The data of each business department is stored independently, and the cost of the input hardware and software is high.
3. The security coefficient of the service system is generally easy to be hacked and tampered, and has potential network safety hazard.
4. The data exist among the business departments, the departments are not trusted, and the data types of the different business departments are inconsistent, so that the data are difficult to exchange and share, the user authorization information is difficult to realize real-time sharing and synchronization, and the data island is easy to form.
Disclosure of Invention
In a first aspect, an embodiment of the present application provides a blockchain-based service data collaboration method, for implementing information resource sharing and data integration between service departments, and improving security of a service system, where the method is applied to a service system that receives a user query request in a federation chain, and the method includes:
receiving a query request submitted by a user, and extracting stored query information associated with the query request; creating a shared data form, wherein the shared data form comprises a query request and query information; signing the shared data form by using the stored private key, diffusing the shared data form into a alliance chain, verifying the signature of the shared data form by using the public key by a node receiving the shared data form, and adding query information which is stored by the node and is associated with the query request into the shared data form; after all service systems in the alliance chain add the query information into the shared data form, participating in the consensus authentication of the query information in the shared data form; after the consensus authentication is completed, acquiring a complete data form subjected to the consensus authentication; and feeding back query information in the complete data form to the user.
In a second aspect, an embodiment of the present application provides a blockchain-based service data collaboration method, for implementing information resource sharing and data integration between service departments, and improving security of a service system, where the method is applied to other service systems in a federation chain except for a service system that receives a user query request, where the method includes:
receiving a shared data form diffused by a service system which has added query information to the shared data form, the shared data form comprising a query request and the query information; verifying the signature of the shared data form by using the stored public key; if the verification is passed, the query information which is stored by the user and is associated with the query request is added into a shared data form; after all service systems in the alliance chain add the query information into the shared data form, participating in the consensus authentication of the query information in the shared data form; and after the consensus authentication is completed, acquiring a complete data form subjected to the consensus authentication.
In a third aspect, an embodiment of the present application further provides a service system, configured to implement information resource sharing and data integration between service departments, and improve security of the service system, where the service system includes:
The first communication module is used for receiving a query request submitted by a user and extracting stored query information associated with the query request; the form making module is used for making a shared data form, wherein the shared data form comprises a query request and query information; the first communication module is further configured to utilize the stored private key to sign the shared data form made by the form making module, diffuse the shared data form into the federation chain, so that the node that receives the shared data form verifies the signature of the shared data form by using the public key, and add the query information stored by itself and associated with the query request into the shared data form; the first consensus authentication module is used for participating in the consensus authentication of the query information in the shared data form after all the service systems in the alliance chain add the query information into the shared data form; the first communication module is further used for acquiring a complete data form subjected to the consensus authentication after the first consensus module determines that the consensus authentication is completed; the first communication module is further used for feeding back query information in the complete data form to the user.
In a fourth aspect, an embodiment of the present application further provides a service system, configured to implement information resource sharing and data integration between service departments, and improve security of the service system, where the service system includes:
A second communication module, configured to receive a shared data form diffused by a service system that has added query information to the shared data form, where the shared data form includes a query request and the query information; the signature verification module is used for verifying the signature of the shared data form received by the second communication module by using the stored public key; the information adding module is used for adding the query information stored by the signature verification module and associated with the query request into the shared data form when the signature verification module determines that the verification is passed; the second consensus authentication module is used for participating in the consensus authentication of the query information in the shared data form after all the service systems in the alliance chain add the query information into the shared data form; and the second communication module is also used for acquiring the complete data form after the second consensus module determines that the consensus authentication is completed.
In a fifth aspect, an embodiment of the present application further provides a federation chain, configured to implement information resource sharing and data integration between service departments, and improve security of a service system, where the federation chain includes the service systems according to the third aspect and the fourth aspect.
In the embodiment of the application, the service system is accessed to the alliance chain, and the point-to-point information sharing among a plurality of service departments can be realized by means of the decentralization and the descension of the blockchain, and the sharing flow of cross-platform service information is promoted by realizing one-time sharing, multiple times of use and hastening. Meanwhile, the block chain adopts the decentralization and distributed architecture, so that the problem of a central node is avoided, the risk of the whole network is reduced, in addition, the block chain adopts a private key signature, public key verification and a non-encryption algorithm, a hacker is difficult to crack, and the trust risk of the system is reduced. And the transaction records of the blockchain are transparent and open in the whole network, so that the problem of information asymmetry is solved, and the auditing and supervision are facilitated. In addition, the blockchain technology has good expansibility, information acquisition, updating and exchange are all carried out in one chain, other departments participate in the multi-department information collaboration of cross departments, cross levels and cross platforms conveniently only by adding interfaces.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:
Fig. 1 is a schematic diagram of a service information collaboration system according to an embodiment of the present application;
fig. 2 is a flowchart of a business information collaboration method in an embodiment of the present application;
FIG. 3 is a schematic diagram of a federated chain in accordance with an embodiment of the present application;
FIG. 4 is a schematic diagram of an information interaction scenario between a user and a federation chain in an embodiment of the present application;
FIG. 5 is a flowchart of another business information collaboration method according to an embodiment of the present application;
FIG. 6 is a flowchart of another business information collaboration method according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a service system according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of another service system according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present application and their descriptions herein are for the purpose of explaining the present application, but are not to be construed as limiting the application.
Fig. 1 is a schematic diagram of a service information collaboration system according to an embodiment of the present application. As shown in fig. 1, the system includes a blockchain service layer and a blockchain layer.
The block chain business layer mainly comprises a block chain management module and a block chain business module. The block chain management module mainly provides functions of block chain character information maintenance, block chain character information inquiry and the like. The block chain service module provides functions of data storage, checking, history inquiry and the like.
The blockchain layer includes blockchain interface services (Blockchain information interconnection platform, BIIP), blockchain intelligence contracts, and blockchain network nodes.
The BIIP is a middleware of block chain interaction, and aims to conveniently realize the butt joint and integration of a traditional financial service system and a block chain bottom layer, and a front-end service system calls the BIIP system through different transaction codes.
A blockchain smart contract is a piece of program running on the blockchain that implements specific transaction functions, the code and state of the smart contract are public, and on-chain users can audit the code functions. The intelligent contract language in the alliance chain is Turing-complete and can interact with the data outside the chain. Once deployed on the chain, the smart contract runs all the way and is not tamperable. The smart contracts may be written according to different business scenarios.
The blockchain network node is a base blockchain network built based on Hyperledger Fabric 1.2.
Based on the above architecture, the embodiment of the present application provides a business data collaboration method based on a blockchain, where the method is applied to a business system in a federation chain that receives a user query request, as shown in fig. 2, and the method includes steps 201 to 206 as follows:
Step 201, receiving a query request submitted by a user, and extracting stored query information associated with the query request.
The block chain adopts the characteristics of decentralization, non-tamper property and the like of the block chain, and ensures the joint participation of all nodes. The blockchain has the characteristics of decentralization, time sequence data, programmability, safety and reliability. The strong computing power formed by consensus algorithms such as workload certification of each node of the distributed system is used for resisting external attack, so that the non-falsification of the block chain data is ensured, and the safety and reliability of the data are ensured. The blockchain comprises a public chain, a private chain and a alliance chain, wherein the alliance chain is arranged between the public chain and the private chain and is jointly initiated by a plurality of institutions, and the blockchain has the characteristic of partial decentralization. The embodiment of the application utilizes a coalition chain, and the constructed coalition chain is shown in figure 3.
The process of building a federation chain occurs prior to receiving a query request submitted by a user. When the alliance chain is built, the business system accesses the alliance chain as a node in the alliance chain; the method comprises the steps of achieving an mutual recognition protocol with other nodes in a alliance chain, wherein the mutual recognition protocol comprises common recognition data, shared data and automatic backup data; a certificate authority, CA, certificate issued by a chain of federations is received, as well as a pair of public and private keys.
When the user logs in the service system, the identity information of the user is verified to ensure the legality of the user identity, wherein the identity information comprises account passwords, faces and the like.
Step 202, making a shared data form.
The shared data form comprises a query request and query information.
And 203, signing the shared data form by using the stored private key, diffusing the shared data form into the alliance chain, so that the node receiving the shared data form can verify the signature of the shared data form by using the public key, and adding the query information which is stored by the node and is associated with the query request into the shared data form.
Step 204, after all the service systems in the alliance chain add the query information into the shared data form, participating in the consensus authentication of the query information in the shared data form.
If the business system acquires the accounting right through competition, the business system serves as a master node of the consensus authentication.
Specifically, the process of performing consensus authentication by the master node includes: acquiring a shared data form added with query information through all service systems; judging whether query information added to a shared data form by all service systems is repeated or not, and whether record of the same information is inconsistent or not; if there is duplication, deleting the duplicated information; if the record of the same information is inconsistent, the information recorded in the latest time is determined as correct information according to the time of recording the same information in each service system, other information is error information, and the error information is deleted. If the master node is the last service system which adds the query information into the shared data form in all service systems, the master node can directly acquire the shared data form which is added with the query information through all service systems from the master node; if the master node is not the last service system in all the service systems to add the query information to the shared data form, the master node needs to acquire the shared data form completed by adding the query information from the service system to which the query information is added last.
The process of performing consensus authentication by nodes that are not master nodes includes the cooperation of the master nodes to complete the judgment of correct information and error information.
The consensus authentication is a process of checking query information added by all service systems in a shared data form, and in the process, consensus is achieved on different records of the same information of different service systems, so that the correctness of the query information recorded in the shared data form is ensured. For example, for the same information "working years", the working years of the users are recorded in the a business system as 5 years, the recording time as 2019, 8 months and 10 days, the working years of the users are recorded in the B business system as 3 years, the recording time as 2017, 7 and 6 days, and the recording of the a business system is newer than the recording time of the B business system, after the consensus authentication, the working years of the users are determined to be 5 years, and the recording of the users "working years of 3 years" in the shared data form is deleted. In addition, in the process of the consensus authentication, whether the query information added to the shared data form by the service system is duplicated or not is checked, and if the duplication exists, the duplicated information is deleted. For example, if a plurality of records of 5 years of user operation are added to the shared data form, one record of 5 years of user operation is retained, and the other records are deleted.
In the usual case, the federation chain employs a practical bayer fault tolerance algorithm (Practical Byzantine Fault Tolerance, PBFT) for consensus authentication.
The failed node is called a Bayesian node, and the normal node is a non-Bayesian node. The conclusion that the consensus satisfies 3f+1< = n is reached.
F is the number of failed nodes. Suppose the F node is both a failed node and a rogue node. Then only one more than failed node is required to reach consensus, i.e., f+1+F < = N, F (maximum number of fault tolerant nodes) = N-1/2. It is assumed that the failed node and the offending node are not one. If F fault nodes and F disqualified nodes are found, the fault nodes are removed by the cluster, F fault nodes are left, and the number of the fault nodes is one more than that of the fault nodes, namely F+1+F < = N. F=n-1/3.
The basic algorithm flow is as follows:
the client sends a request to the master node;
the master node broadcasts a request to other slave nodes, and the nodes execute a three-phase consensus flow of the pbft algorithm.
After the node processes the three-stage flow, the node returns a message to the client.
After receiving the same message from f+1 nodes, the client represents that the consensus has been completed.
The three-stage flow of the algorithm core is a Pre-preparation stage, a preparation stage and a commit stage. pre-preparation, receiving or rejecting information broadcast by the master node. After the preparation slave node agrees, the preparation information is sent to other nodes, and the nodes send the preparation information simultaneously, so that the preparation information of different nodes exceeding 2F is received, and the preparation stage is finished. Commit phase: broadcasting the commit message to other nodes, the process may be performed by n nodes, so that the commit message sent by other nodes may be received, when 2f+1 commit messages are received, representing that most nodes enter a commit phase, consensus is reached at this phase, and the nodes will execute the request and write data.
Step 205, when the consensus authentication is completed, a complete data form after the consensus authentication is obtained.
Specifically, when a complete data form subjected to consensus authentication is obtained, the service system judges whether the service system is a master node for the consensus authentication or not; if the self is the master node for the consensus authentication, the complete data form is acquired from the self. If the node is not the master node for the consensus authentication, the complete data form is obtained from the master node for the consensus authentication.
In the embodiment of the application, if the service system is the master node for carrying out the consensus authentication, the service system packages the complete data form subjected to the consensus authentication into blocks and broadcasts the blocks to other nodes in the alliance chain so as to enable the other nodes to synchronously store the complete data form, thereby realizing information sharing among different service departments and ensuring the consistency of the stored information of different service systems. And the other nodes realize the storage of the complete data form by adopting a hash uplink mode for the complete data form.
And 206, feeding back query information in the complete data form to the user.
The query information fed back to the user comprises the related information which the user wants to acquire in all the service systems in the alliance chain, the user does not need to log in each service system one by one to acquire the required information, the user time is saved, the multiparty communication cost is reduced, and the business efficiency is greatly improved.
An information interaction scene of the user and the alliance chain in the application is shown in fig. 4. Referring to fig. 4, a service system A, B, C has access to a federation chain as one of the nodes, and a user submits a query request to the service systems in the federation chain (which service system is not shown in the figure to which the user submits the query request) and receives query information fed back by the service systems, and information flows are transferred between the service systems and the user. The business system counts each data inquiry in the alliance chain, and ensures the traceability of information in the alliance chain.
In the embodiment of the application, the service system is accessed to the alliance chain, and the point-to-point information sharing among a plurality of service departments can be realized by means of the decentralization and the descension of the blockchain, and the sharing flow of cross-platform service information is promoted by realizing one-time sharing, multiple times of use and hastening. Meanwhile, the block chain adopts the decentralization and distributed architecture, so that the problem of a central node is avoided, the risk of the whole network is reduced, in addition, the block chain adopts a private key signature, public key verification and a non-encryption algorithm, a hacker is difficult to crack, and the trust risk of the system is reduced. And the transaction records of the blockchain are transparent and open in the whole network, so that the problem of information asymmetry is solved, and the auditing and supervision are facilitated. In addition, the blockchain technology has good expansibility, information acquisition, updating and exchange are all carried out in one chain, other departments participate in the multi-department information collaboration of cross departments, cross levels and cross platforms conveniently only by adding interfaces.
The embodiment of the application also provides a service data collaboration method based on the block chain, which is applied to other service systems except the service system receiving the user query request in the alliance chain, as shown in fig. 5, and comprises the steps 501 to 505:
step 501, receiving a shared data form that is diffused by a business system that has added query information to the shared data form.
Wherein the shared data form includes a query request and query information.
The shared data forms are sequentially transmitted among all nodes (i.e. service systems) of the alliance chain, after the service system receiving the user query request completes making the shared data forms, the shared data forms are diffused to the next node, the node receiving the shared data forms adds the query information stored by the node corresponding to the query request into the shared data forms, and the new shared data forms continue to be diffused to the next node until all the nodes determine that the query information stored by the node is added into the shared data forms. If the current node determines that the query information corresponding to the query request is not stored, the query information is not added to the shared data form, and the query result which is not queried for the related query information at this time is added to the shared data form. Thus, the business system that has added the query information to the shared data form may be the business system that receives the user query request, or may be other business systems.
The process of building a federation chain occurs prior to receiving a shared data form that is diffused by a business system that has added query information to the shared data form. When the alliance chain is built, each service system accesses the alliance chain as a node in the alliance chain; the method comprises the steps of achieving an mutual recognition protocol with other nodes in a alliance chain, wherein the mutual recognition protocol comprises common recognition data, shared data and automatic backup data; a CA certificate issued by a federation chain is received, along with a pair of public and private keys.
Step 502, verifying the signature of the shared data form by using the stored public key.
Step 503, if the verification is passed, adding the query information stored by the user and associated with the query request into the shared data form.
The business system adds all the query information which is queried by the business system and is associated with the query request into the shared data form.
Step 504, after all the service systems in the alliance chain add the query information into the shared data form, participating in the consensus authentication of the query information in the shared data form.
Participating in consensus authentication of query information in a shared data form, comprising: and judging whether the node is a master node of consensus authentication. If yes, acquiring a shared data form added with query information through all service systems; judging whether query information added to a shared data form by all service systems is repeated or not, and whether record of the same information is inconsistent or not; if there is duplication, deleting the duplicated information; if the record of the same information is inconsistent, the information recorded in the latest time is determined as correct information according to the time of recording the same information in each service system, other information is error information, and the error information is deleted. If not, the cooperative master node completes the judgment of the correct information and the error information.
It should be noted that the primary node qualification is obtained by all nodes in the federation chain through competition. The node competing for the accounting right is a master node for the consensus authentication, and is initiated by the master node, and other nodes participate in the consensus authentication process.
The consensus authentication process ensures that repeated information and error information do not exist in the complete data form, and ensures the correctness of the node storage information.
And 505, after the consensus authentication is completed, acquiring a complete data form subjected to the consensus authentication.
The master node of the consensus authentication has a complete data form, so if the master node is the master node of the consensus authentication, the complete data form is stored; if the node is not the master node for the consensus authentication, the complete data form is obtained from the master node for the consensus authentication. And the master node of the consensus authentication is packaged into blocks and broadcasts to other nodes in the alliance chain, and the other nodes acquire the broadcasted complete data form. Thus, data sharing among the nodes is realized.
In the embodiment of the application, the service system is accessed to the alliance chain, and the point-to-point information sharing among a plurality of service departments can be realized by means of the decentralization and the descension of the blockchain, and the sharing flow of cross-platform service information is promoted by realizing one-time sharing, multiple times of use and hastening. Meanwhile, the block chain adopts the decentralization and distributed architecture, so that the problem of a central node is avoided, the risk of the whole network is reduced, in addition, the block chain adopts a private key signature, public key verification and a non-encryption algorithm, a hacker is difficult to crack, and the trust risk of the system is reduced. And the transaction records of the blockchain are transparent and open in the whole network, so that the problem of information asymmetry is solved, and the auditing and supervision are facilitated. In addition, the blockchain technology has good expansibility, information acquisition, updating and exchange are all carried out in one chain, other departments participate in the multi-department information collaboration of cross departments, cross levels and cross platforms conveniently only by adding interfaces.
The embodiment of the application also provides a service data collaboration method based on the block chain, wherein the service system receiving the user query request is called a first service system, and other service systems in the alliance chain are called a second service system. As shown in fig. 6, the method includes steps 601 to 611:
step 601, the first service system and the second service system together construct a alliance chain and achieve an consensus protocol.
Step 602, a first service system receives a query request submitted by a user.
And 603, the first service system extracts the stored query information associated with the query request, creates a shared data form, and signs the shared data form by using the stored private key.
The shared data form comprises a query request and query information.
Step 604, the first business system diffuses the shared data form into the federation chain.
Step 605, the second business system receives a shared data form that is diffused by the business system that has added query information to the shared data form.
Step 606, the second business system verifies the signature of the shared data form using the stored public key.
Step 607, if the verification is passed, the second service system adds the query information associated with the query request stored by itself to the shared data form.
Step 608, after all the service systems in the alliance chain add the query information into the shared data form, all the service systems participate in the consensus authentication of the query information in the shared data form.
Step 609, all service systems judge whether the service systems are master nodes for consensus authentication or not; if yes, acquiring a shared data form added with query information through all service systems; judging whether query information added to a shared data form by all service systems is repeated or not, and whether record of the same information is inconsistent or not; if there is duplication, deleting the duplicated information; if the record of the same information is inconsistent, determining the information recorded in the latest time as correct information according to the time of recording the same information by each service system, and deleting the error information when other information is error information; if not, the cooperative master node completes the judgment of the correct information and the error information.
And 610, after the consensus authentication is completed, all the service systems acquire a complete data form subjected to the consensus authentication, wherein the complete data form is broadcast to other nodes by a master node of the consensus authentication.
In the embodiment of the application, the service system is accessed to the alliance chain, and the point-to-point information sharing among a plurality of service departments can be realized by means of the decentralization and the descension of the blockchain, and the sharing flow of cross-platform service information is promoted by realizing one-time sharing, multiple times of use and hastening. Meanwhile, the block chain adopts the decentralization and distributed architecture, so that the problem of a central node is avoided, the risk of the whole network is reduced, in addition, the block chain adopts a private key signature, public key verification and a non-encryption algorithm, a hacker is difficult to crack, and the trust risk of the system is reduced. And the transaction records of the blockchain are transparent and open in the whole network, so that the problem of information asymmetry is solved, and the auditing and supervision are facilitated. In addition, the blockchain technology has good expansibility, information acquisition, updating and exchange are all carried out in one chain, other departments participate in the multi-department information collaboration of cross departments, cross levels and cross platforms conveniently only by adding interfaces.
The embodiment of the application also provides a service system, as shown in fig. 7, the service system 700 includes a first communication module 701, a form making module 702 and a first consensus authentication module 703.
The first communication module 701 is configured to receive a query request submitted by a user, and extract stored query information associated with the query request.
The form creation module 702 is configured to create a shared data form, where the shared data form includes a query request and query information.
The first communication module 701 is further configured to utilize the stored private key to sign the shared data form made by the form making module 702, diffuse the shared data form into the federation chain, so that the node that receives the shared data form verifies the signature of the shared data form by using the public key, and add the query information associated with the query request stored by itself into the shared data form.
The first consensus authentication module 703 is configured to participate in consensus authentication of the query information in the shared data form after all the service systems in the federation chain add the query information to the shared data form.
The first communication module 701 is further configured to obtain a complete data form after the first consensus authentication module 703 determines that the consensus authentication is completed.
The first communication module 701 is further configured to feed back query information in the complete data form to the user.
In one implementation of the embodiment of the present application, the service system 701 further includes a first federation link construction module 704, where the first federation link construction module 704 is configured to:
When constructing the alliance chain, accessing the alliance chain as a node in the alliance chain;
the method comprises the steps of achieving an mutual recognition protocol with other nodes in a alliance chain, wherein the mutual recognition protocol comprises common recognition data, shared data and automatic backup data;
a certificate authority, CA, certificate issued by a chain of federations is received, as well as a pair of public and private keys.
In one implementation of the embodiment of the present application, the first consensus authentication module 703 is configured to:
judging whether the node is a master node for consensus authentication or not;
if yes, acquiring a shared data form added with query information through all service systems; judging whether query information added to a shared data form by all service systems is repeated or not, and whether record of the same information is inconsistent or not; if there is duplication, deleting the duplicated information; if the record of the same information is inconsistent, determining the information recorded in the latest time as correct information according to the time of recording the same information by each service system, and deleting the error information when other information is error information;
if not, the cooperative master node completes the judgment of the correct information and the error information.
In one implementation of the embodiment of the present application, the first communication module 701 is configured to:
judging whether the node is a master node for consensus authentication or not;
if the self is the master node for consensus authentication, acquiring a complete data form from the self;
if the node is not the master node for the consensus authentication, the complete data form is obtained from the master node for the consensus authentication.
In one implementation manner of the embodiment of the present application, when the service system is a master node performing consensus authentication, the first communication module 701 is configured to:
and packaging the complete data form subjected to the consensus authentication into blocks, and broadcasting to other nodes in the alliance chain so as to enable the other nodes to synchronously store the complete data form.
In the embodiment of the application, the service system is accessed to the alliance chain, and the point-to-point information sharing among a plurality of service departments can be realized by means of the decentralization and the descension of the blockchain, and the sharing flow of cross-platform service information is promoted by realizing one-time sharing, multiple times of use and hastening. Meanwhile, the block chain adopts the decentralization and distributed architecture, so that the problem of a central node is avoided, the risk of the whole network is reduced, in addition, the block chain adopts a private key signature, public key verification and a non-encryption algorithm, a hacker is difficult to crack, and the trust risk of the system is reduced. And the transaction records of the blockchain are transparent and open in the whole network, so that the problem of information asymmetry is solved, and the auditing and supervision are facilitated. In addition, the blockchain technology has good expansibility, information acquisition, updating and exchange are all carried out in one chain, other departments participate in the multi-department information collaboration of cross departments, cross levels and cross platforms conveniently only by adding interfaces.
The embodiment of the application also provides a service system, as shown in fig. 8, the service system 800 includes a second communication module 801, a signature verification module 802, an information adding module 803 and a second consensus authentication module 804.
The second communication module 801 is configured to receive a shared data form diffused by a service system that has added query information to the shared data form, where the shared data form includes a query request and the query information.
A signature verification module 802, configured to verify the signature of the shared data form received by the second communication module 801 by using the stored public key.
An information adding module 803, configured to add the query information associated with the query request stored by the signature verification module 802 to the shared data form when the signature verification module determines that the signature verification passes.
The second consensus authentication module 804 is configured to participate in the consensus authentication of the query information in the shared data form after all the service systems in the federation chain add the query information to the shared data form.
The second communication module 801 is further configured to obtain a complete data form after the second consensus module 804 determines that the consensus authentication is completed.
In one implementation of the embodiment of the present application, the service system 800 further includes a second federation link construction module 805, where the second federation link construction module 805 is configured to:
When constructing the alliance chain, accessing the alliance chain as a node in the alliance chain;
the method comprises the steps of achieving an mutual recognition protocol with other nodes in a alliance chain, wherein the mutual recognition protocol comprises common recognition data, shared data and automatic backup data;
a CA certificate issued by a federation chain is received, along with a pair of public and private keys.
In one implementation of the embodiment of the present application, the second consensus authentication module 804 is configured to:
judging whether the node is a master node of consensus authentication or not;
if yes, acquiring a shared data form added with query information through all service systems; judging whether query information added to a shared data form by all service systems is repeated or not, and whether record of the same information is inconsistent or not; if there is duplication, deleting the duplicated information; if the record of the same information is inconsistent, determining the information recorded in the latest time as correct information according to the time of recording the same information by each service system, and deleting the error information when other information is error information;
if not, the cooperative master node completes the judgment of the correct information and the error information.
In one implementation of the embodiment of the present application, the second communication module 801 is further configured to:
If the node is the master node of the consensus authentication, storing the complete data form, packaging the complete data form subjected to the consensus authentication into blocks, and broadcasting to other nodes in the alliance chain so as to enable the other nodes to synchronously store the complete data form;
if the node is not the master node for the consensus authentication, the complete data form is obtained from the master node for the consensus authentication.
In the embodiment of the application, the service system is accessed to the alliance chain, and the point-to-point information sharing among a plurality of service departments can be realized by means of the decentralization and the descension of the blockchain, and the sharing flow of cross-platform service information is promoted by realizing one-time sharing, multiple times of use and hastening. Meanwhile, the block chain adopts the decentralization and distributed architecture, so that the problem of a central node is avoided, the risk of the whole network is reduced, in addition, the block chain adopts a private key signature, public key verification and a non-encryption algorithm, a hacker is difficult to crack, and the trust risk of the system is reduced. And the transaction records of the blockchain are transparent and open in the whole network, so that the problem of information asymmetry is solved, and the auditing and supervision are facilitated. In addition, the blockchain technology has good expansibility, information acquisition, updating and exchange are all carried out in one chain, other departments participate in the multi-department information collaboration of cross departments, cross levels and cross platforms conveniently only by adding interfaces.
The present application also provides a federation chain that includes business system 700 and business system 800.
The embodiment of the application also provides a computer device, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor implements any one of the methods of step 201 to step 206, step 501 to step 505 and/or step 601 to step 610 when executing the computer program.
Embodiments of the present application also provide a computer-readable storage medium storing a computer program for executing any one of the methods of steps 201 to 206, 501 to 505, and/or 601 to 610.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may 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, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the application, and is not meant to limit the scope of the application, but to limit the application to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the application are intended to be included within the scope of the application.
Claims (12)
1. A blockchain-based business data collaboration method, wherein the method is applied to a business system in a federated chain that receives user query requests, the method comprising:
receiving a query request submitted by a user, and extracting stored query information associated with the query request;
Creating a shared data form, wherein the shared data form comprises a query request and query information;
signing the shared data form by using the stored private key, diffusing the shared data form into a alliance chain, verifying the signature of the shared data form by using the public key by a node receiving the shared data form, and adding query information which is stored by the node and is associated with the query request into the shared data form;
after all service systems in the alliance chain add the query information into the shared data form, participating in the consensus authentication of the query information in the shared data form;
after the consensus authentication is completed, acquiring a complete data form subjected to the consensus authentication;
the query information in the complete data form is fed back to the user;
the participating in the consensus authentication of the query information in the shared data form comprises the following steps: judging whether the node is a master node for consensus authentication or not; if yes, acquiring a shared data form added with query information through all service systems; judging whether query information added to a shared data form by all service systems is repeated or not, and whether record of the same information is inconsistent or not; if there is duplication, deleting the duplicated information; if the record of the same information is inconsistent, determining the information recorded in the latest time as correct information according to the time of recording the same information by each service system, and deleting the error information when other information is error information; if not, the cooperative master node completes the judgment of the correct information and the error information.
2. The method of claim 1, wherein prior to receiving the user's query request, the method further comprises:
when a alliance chain is built, accessing the alliance chain as a node in the alliance chain;
the method comprises the steps of achieving an mutual recognition protocol with other nodes in a alliance chain, wherein the mutual recognition protocol comprises common recognition data, shared data and automatic backup data;
a certificate authority, CA, certificate issued by a chain of federations is received, as well as a pair of public and private keys.
3. The method according to any one of claims 1 to 2, wherein, when the consensus authentication is completed, obtaining the complete data form comprises:
judging whether the node is a master node for consensus authentication or not;
if the self is the master node for consensus authentication, acquiring a complete data form from the self;
if the node is not the master node for the consensus authentication, the complete data form is obtained from the master node for the consensus authentication.
4. The method according to claim 1, wherein if the master node itself is a master node performing the consensus authentication, the method further comprises, after completing the consensus authentication:
and packaging the complete data form subjected to the consensus authentication into blocks, and broadcasting to other nodes in the alliance chain so as to enable the other nodes to synchronously store the complete data form.
5. A blockchain-based service data collaboration method, wherein the method is applied to other service systems in a federated chain than a service system receiving a user query request, the method comprising:
receiving a shared data form diffused by a service system which has added query information to the shared data form, the shared data form comprising a query request and the query information;
verifying the signature of the shared data form by using the stored public key;
if the verification is passed, the query information which is stored by the user and is associated with the query request is added into a shared data form;
after all service systems in the alliance chain add the query information into the shared data form, participating in the consensus authentication of the query information in the shared data form;
after the consensus authentication is completed, acquiring a complete data form subjected to the consensus authentication;
the participating in the consensus authentication of the query information in the shared data form comprises the following steps: judging whether the node is a master node of consensus authentication or not; if yes, acquiring a shared data form added with query information through all service systems; judging whether query information added to a shared data form by all service systems is repeated or not, and whether record of the same information is inconsistent or not; if there is duplication, deleting the duplicated information; if the record of the same information is inconsistent, determining the information recorded in the latest time as correct information according to the time of recording the same information by each service system, and deleting the error information when other information is error information; if not, the cooperative master node completes the judgment of the correct information and the error information.
6. The method of claim 5, wherein prior to receiving the shared data form diffused by the business system that has added query information to the shared data form, the method further comprises:
when a alliance chain is built, accessing the alliance chain as a node in the alliance chain;
the method comprises the steps of achieving an mutual recognition protocol with other nodes in a alliance chain, wherein the mutual recognition protocol comprises common recognition data, shared data and automatic backup data;
a CA certificate issued by a federation chain is received, along with a pair of public and private keys.
7. The method of claim 6, wherein the obtaining the consensus-authenticated complete data form comprises:
if the node is the master node of the consensus authentication, storing the complete data form, packaging the complete data form subjected to the consensus authentication into blocks, and broadcasting to other nodes in the alliance chain so as to enable the other nodes to synchronously store the complete data form;
if the node is not the master node for the consensus authentication, the complete data form is obtained from the master node for the consensus authentication.
8. A business system, said business system comprising:
the first communication module is used for receiving a query request submitted by a user and extracting stored query information associated with the query request;
The form making module is used for making a shared data form, wherein the shared data form comprises a query request and query information;
the first communication module is further configured to utilize the stored private key to sign the shared data form made by the form making module, diffuse the shared data form into the federation chain, so that the node that receives the shared data form verifies the signature of the shared data form by using the public key, and add the query information stored by itself and associated with the query request into the shared data form;
the first consensus authentication module is used for participating in the consensus authentication of the query information in the shared data form after all the service systems in the alliance chain add the query information into the shared data form; the participating in the consensus authentication of the query information in the shared data form comprises the following steps: judging whether the node is a master node for consensus authentication or not; if yes, acquiring a shared data form added with query information through all service systems; judging whether query information added to a shared data form by all service systems is repeated or not, and whether record of the same information is inconsistent or not; if there is duplication, deleting the duplicated information; if the record of the same information is inconsistent, determining the information recorded in the latest time as correct information according to the time of recording the same information by each service system, and deleting the error information when other information is error information; if not, the cooperative master node completes the judgment of the correct information and the error information;
The first communication module is further used for acquiring a complete data form subjected to consensus authentication after the first consensus authentication module determines that the consensus authentication is completed;
the first communication module is further used for feeding back query information in the complete data form to the user.
9. A business system, said business system comprising:
a second communication module, configured to receive a shared data form diffused by a service system that has added query information to the shared data form, where the shared data form includes a query request and the query information;
the signature verification module is used for verifying the signature of the shared data form received by the second communication module by using the stored public key;
the information adding module is used for adding the query information stored by the signature verification module and associated with the query request into the shared data form when the signature verification module determines that the verification is passed;
the second consensus authentication module is used for participating in the consensus authentication of the query information in the shared data form after all the service systems in the alliance chain add the query information into the shared data form; the participating in the consensus authentication of the query information in the shared data form comprises the following steps: judging whether the node is a master node for consensus authentication or not; if yes, acquiring a shared data form added with query information through all service systems; judging whether query information added to a shared data form by all service systems is repeated or not, and whether record of the same information is inconsistent or not; if there is duplication, deleting the duplicated information; if the record of the same information is inconsistent, determining the information recorded in the latest time as correct information according to the time of recording the same information by each service system, and deleting the error information when other information is error information; if not, the cooperative master node completes the judgment of the correct information and the error information;
And the second communication module is also used for acquiring the complete data form after the second consensus module determines that the consensus authentication is completed.
10. A federation chain comprising the business system of claims 8 and 9.
11. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 7 when executing the computer program.
12. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program for executing the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911211636.XA CN110990408B (en) | 2019-12-02 | 2019-12-02 | Business information collaboration method based on block chain, business system and alliance chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911211636.XA CN110990408B (en) | 2019-12-02 | 2019-12-02 | Business information collaboration method based on block chain, business system and alliance chain |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110990408A CN110990408A (en) | 2020-04-10 |
| CN110990408B true CN110990408B (en) | 2023-09-19 |
Family
ID=70089136
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911211636.XA Active CN110990408B (en) | 2019-12-02 | 2019-12-02 | Business information collaboration method based on block chain, business system and alliance chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110990408B (en) |
Families Citing this family (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111639887A (en) * | 2020-04-13 | 2020-09-08 | 中国铁道科学研究院集团有限公司电子计算技术研究所 | Multi-type joint transport processing method, system and node based on alliance chain |
| CN113839905B (en) * | 2020-06-08 | 2023-05-09 | 中国移动通信有限公司研究院 | Certificate writing and certificate feedback method, accounting node and identity authentication system |
| CN111932250A (en) * | 2020-06-08 | 2020-11-13 | 国网浙江省电力有限公司台州供电公司 | Method for realizing power grid information sharing based on block chain technology |
| CN111698254B (en) * | 2020-06-15 | 2022-11-15 | 中国银行股份有限公司 | Alliance chain Baas platform building method based on sharing organization |
| CN111708820A (en) * | 2020-06-17 | 2020-09-25 | 中国银行股份有限公司 | Travel data query method |
| CN111651783A (en) * | 2020-06-24 | 2020-09-11 | 北京米弘科技有限公司 | Block chain-based network security information sharing method and device |
| CN111835570B (en) * | 2020-07-20 | 2022-11-11 | 中国银行股份有限公司 | Global state persistence decentralized blockchain network node device and working method |
| CN111881486A (en) * | 2020-07-23 | 2020-11-03 | 中国工商银行股份有限公司 | Multi-party data backup method, device and system based on block chain |
| CN112016898A (en) * | 2020-08-31 | 2020-12-01 | 光大科技有限公司 | Block chain-based collaborative office method, device and system |
| CN112287361A (en) * | 2020-09-11 | 2021-01-29 | 杭州鸽子蛋网络科技有限责任公司 | Data governance method, system, electronic device and storage medium |
| CN112235294B (en) * | 2020-10-14 | 2022-07-26 | 南京三眼精灵信息技术有限公司 | Block chain cooperative authority control method and device |
| CN112328605B (en) * | 2020-11-26 | 2024-01-12 | 安徽继远软件有限公司 | Block chain-based power field security data management method and system |
| CN112837023A (en) * | 2020-12-03 | 2021-05-25 | 杭州趣链科技有限公司 | Business collaboration platform, method and device of organization and electronic equipment |
| CN114760325A (en) * | 2020-12-25 | 2022-07-15 | 中移动信息技术有限公司 | Business data processing method, device, storage medium and sharing platform |
| CN112751662B (en) * | 2020-12-29 | 2022-10-25 | 山西特信环宇信息技术有限公司 | Shared chain of cone block chain |
| CN113190618A (en) * | 2021-04-28 | 2021-07-30 | 宁夏中小在线资信服务有限公司 | Enterprise government affair service data storage method based on block chain technology |
| CN114629631B (en) * | 2021-07-21 | 2024-01-09 | 国网河南省电力公司信息通信公司 | Data trusted interaction method and system based on alliance chain and electronic equipment |
| CN113938499A (en) * | 2021-09-29 | 2022-01-14 | 深圳时空云科技有限公司 | Decentralized service method, device and system |
| CN114021172B (en) * | 2021-11-10 | 2022-10-21 | 苏州同济区块链研究院有限公司 | Multi-party joint security calculation method and device based on alliance chain |
| CN115396248B (en) * | 2022-08-31 | 2024-03-15 | 杭州程天科技发展有限公司 | Remote device control method, device, system, electronic device and storage medium |
| CN117056110B (en) * | 2023-08-17 | 2024-02-23 | 北京优特捷信息技术有限公司 | System fault investigation method and device, electronic equipment and storage medium |
| CN117235188B (en) * | 2023-11-15 | 2024-01-30 | 成都三合力通科技有限公司 | Data universe sharing system and method based on alliance computing |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108632292A (en) * | 2018-05-16 | 2018-10-09 | 苏宁易购集团股份有限公司 | Data sharing method based on alliance's chain and system |
| CN108776929A (en) * | 2018-04-02 | 2018-11-09 | 成都云创智融科技有限公司 | Bill processing method, system based on block chain database and readable storage medium storing program for executing |
| CN108848080A (en) * | 2018-06-01 | 2018-11-20 | 深圳崀途科技有限公司 | Data-sharing systems based on the storage verification of alliance's chain |
| CN109189962A (en) * | 2018-08-17 | 2019-01-11 | 福建南威软件有限公司 | A kind of license service realization system based on block chain |
| CN109413174A (en) * | 2018-10-18 | 2019-03-01 | 中国船舶工业系统工程研究院 | A kind of trans-departmental oceanographic data sharing method based on block chain |
| CN109802993A (en) * | 2018-12-13 | 2019-05-24 | 深圳市链联科技有限公司 | A kind of alliance's chain building method based on supply chain ecology |
| CN109831425A (en) * | 2019-01-25 | 2019-05-31 | 中国联合网络通信集团有限公司 | Block chain common recognition method, apparatus, equipment and computer readable storage medium |
| CN109948370A (en) * | 2018-12-29 | 2019-06-28 | 弦子科技(北京)有限公司 | A kind of method for processing business based on block chain, device and electronic equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110365491B (en) * | 2017-03-30 | 2021-03-26 | 腾讯科技（深圳）有限公司 | Service processing method, device, equipment, storage medium and data sharing system |
-
2019
- 2019-12-02 CN CN201911211636.XA patent/CN110990408B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108776929A (en) * | 2018-04-02 | 2018-11-09 | 成都云创智融科技有限公司 | Bill processing method, system based on block chain database and readable storage medium storing program for executing |
| CN108632292A (en) * | 2018-05-16 | 2018-10-09 | 苏宁易购集团股份有限公司 | Data sharing method based on alliance's chain and system |
| CN108848080A (en) * | 2018-06-01 | 2018-11-20 | 深圳崀途科技有限公司 | Data-sharing systems based on the storage verification of alliance's chain |
| CN109189962A (en) * | 2018-08-17 | 2019-01-11 | 福建南威软件有限公司 | A kind of license service realization system based on block chain |
| CN109413174A (en) * | 2018-10-18 | 2019-03-01 | 中国船舶工业系统工程研究院 | A kind of trans-departmental oceanographic data sharing method based on block chain |
| CN109802993A (en) * | 2018-12-13 | 2019-05-24 | 深圳市链联科技有限公司 | A kind of alliance's chain building method based on supply chain ecology |
| CN109948370A (en) * | 2018-12-29 | 2019-06-28 | 弦子科技(北京)有限公司 | A kind of method for processing business based on block chain, device and electronic equipment |
| CN109831425A (en) * | 2019-01-25 | 2019-05-31 | 中国联合网络通信集团有限公司 | Block chain common recognition method, apparatus, equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110990408A (en) | 2020-04-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110990408B (en) | Business information collaboration method based on block chain, business system and alliance chain | |
| CN109447795B (en) | Byzantine consensus method supporting rapid achievement of final confirmation | |
| CN110597911B (en) | Certificate processing method and device for block chain network, electronic equipment and storage medium | |
| CN113395363B (en) | Data processing method, device and equipment based on block chain and storage medium | |
| CN110912707A (en) | Block chain-based digital certificate processing method, device, equipment and storage medium | |
| CN112508566A (en) | Alliance chain-based cross-chain private transaction method and equipment | |
| CN111612619A (en) | Storage sharing platform based on block chain and storage transaction method | |
| CN111221914A (en) | Data exchange sharing tracing method based on block chain | |
| CN113255014B (en) | Data processing method based on block chain and related equipment | |
| CN114240433A (en) | Data processing method and system based on block chain | |
| CN113722722A (en) | Block chain-based high-security-level access control method and system | |
| CN114913013A (en) | House renting transaction system and house renting transaction method based on block chain | |
| CN116827957B (en) | Information processing method, device, equipment and medium based on multi-block chain | |
| CN115865705A (en) | Multi-party federal learning system, method, equipment and medium based on supervision mechanism | |
| KR102294569B1 (en) | Block Chain Management System To Build Block Chain Network | |
| CN117010889A (en) | Data processing method, device, equipment, medium and product | |
| CN112950180A (en) | Community certificate method and system based on alliance chain, electronic device and storage medium | |
| CN116186786A (en) | Block chain-based service processing method and device, electronic equipment and readable medium | |
| CN112968772A (en) | Cross-chain decoupling method and system for block chain data and application of cross-chain decoupling method and system | |
| CN111339189A (en) | Data processing method and device and computer readable storage medium | |
| CN116633699B (en) | Product anti-counterfeiting traceability information trusted processing method and system based on block chain | |
| US11971877B2 (en) | Method, apparatus, device, and storage medium for proposal message processing for blockchain | |
| CN114172661B (en) | Bidirectional cross-link method, system and device for digital asset | |
| CN116760632B (en) | Data processing method, device, equipment and readable storage medium | |
| US20230325833A1 (en) | Blockchain-based data processing method and apparatus, device, storage medium, and program product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |