CN109688012A - A kind of method of alliance's chain node hot standby switch - Google Patents
A kind of method of alliance's chain node hot standby switch Download PDFInfo
- Publication number
- CN109688012A CN109688012A CN201811639905.8A CN201811639905A CN109688012A CN 109688012 A CN109688012 A CN 109688012A CN 201811639905 A CN201811639905 A CN 201811639905A CN 109688012 A CN109688012 A CN 109688012A
- Authority
- CN
- China
- Prior art keywords
- node
- common recognition
- candidate nodes
- nodes
- network
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0889—Techniques to speed-up the configuration process
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
- H04L9/3268—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]
Abstract
The invention discloses a kind of methods of alliance's chain node hot standby switch.The step of node hot standby switch specifically: both candidate nodes and common recognition node establish connection；Its network configuration and its common recognition routing table information are sent to both candidate nodes and backed up by common recognition node in real time；Both candidate nodes carry out fault detection to common recognition node, decide whether the process for triggering node upgrading replacement；Upgrade to common recognition node on both candidate nodes line, according to the network configuration of backup go connection block chain network common recognition node, while by itself common recognition state initialization to know together node delay machine when state, complete to replace with this.This method participates in the alliance's block chain network formed by multiple mechanisms, the common recognition node of mechanism is abnormal delay machine, under the premise of not introducing manual operation, it is automatically performed on both candidate nodes line and upgrades to common recognition node, it ensure that on the basis of not influencing block chain network common recognition efficiency, avoid node of knowing together in mechanism and Single Point of Faliure occurs.
Description
Technical field
The present invention relates to the block chain CA certificate system of decentralization more particularly to a kind of alliance's chain node hot standby switch
Method.
Background technique
With popularizing for block chain technology, people gradually recognize that it can bring safe and reliable, simplified stream for traditional industries
The advantages that journey, save the cost and enhancing are trusted, can make up that multiparty collaboration brings low efficiency, at high cost, operational risk is big etc. lacks
Point, so by the favor for needing multi-party reciprocity cooperative enterprise.Since multiparty collaboration generally requires stringent authentication and specially
The access of door, quasi- licensing scheme out, therefore alliance's block chain also becomes their main selection.
In alliance's block chain, by other enterprises, there is Byzantium's behavior and is influenced in node in order to prevent, enterprise development
Service application transaction be often sent to oneself deployment node up handle.At present in alliance's block chain, if some
There is hardware error in server where abnormal delay machine or node occurs in the node of mechanism, although for there is the area of certain fault-tolerance
For block chain network will not because of this node delay machine and be affected, but for enterprise, need with most fast speed
Go recovery nodes service.At present frequently with restoration methods have following two:
By the relevant configuration before running node starting under computer room operation maintenance personnel line, node is restarted, is set if it is storage
The raw fatal error of preparation leads to loss of data, needs to be related to the synchronous block chain network data of new node.
The backup that data and service are done using multiple common recognition nodes, when a common recognition node occurs abnormal, upper layer
Using switching service node after perception.
Both the above method all has some disadvantages, and first method may result in section due to introducing manual operation
Point service can not restore for a long time, this is extremely disadvantageous for the intelligent contract application being in communication with each other with it.In addition, if complete
Network data amount is very big, and the synchronous the time it takes of node data is difficult to estimate, will lead to node and is in temporarily unavailable state.The
Although two kinds of methods have the advantages that fast quick-recovery, however, to ensure that the fairness for ballot of knowing together between enterprise, all participation enterprises
Industry must all dispose equivalent amount common recognition node, and the increase for number of nodes of knowing together will generate strong influence to common recognition efficiency.
Summary of the invention
In view of the deficiencies of the prior art, it is an object of the present invention to provide a kind of methods of alliance's chain node hot standby switch, make
Upgrade to common recognition node on non-authentication nodal line, complete permission upgrading and replacement, realizes under the premise of not influencing to know together efficiency,
Upgrading the spent time on line is second grade.
The purpose of the present invention is achieved through the following technical solutions: a kind of method of alliance's chain node hot standby switch,
Include the following steps:
(1) both candidate nodes network configuration: both candidate nodes are substantially a special accounting nodes, hold third party under line
ECert the and RCert certificate that authentication center issues；Both candidate nodes before being initiated, need to specify in its network profile
It is the both candidate nodes of which common recognition node；
(2) both candidate nodes and common recognition node establish connection: both candidate nodes establish connection request to common recognition node initiation, in object
Reason connection is established after completion, starts to carry out both sides' authentication, if authentication does not pass through, connects foundation failure；If body
Part certification passes through, and node confirmation opposite end of knowing together is its both candidate nodes, then does Backup label to it and be put into candidate list
In；
(3) both candidate nodes back up common recognition meshed network configuration: establishing in the connection of both candidate nodes and common recognition node
After completion, the common recognition each network connection information of node is changed, and is notified that both candidate nodes are updated backup；Backup
Data include: other common recognition address of node link informations in block chain network, with the accounting nodes that are connected of node of knowing together
The candidate list of address link information, node of knowing together.Wherein, accounting nodes include both candidate nodes, because both candidate nodes are special
Accounting nodes；
(4) both candidate nodes to common recognition node carry out fault detection: both candidate nodes using the mechanism of keepalive+ time-out come
Judge whether common recognition node survives, replacement operation is upgraded to decide whether to trigger node with this；It is arranged according to both candidate nodes in candidate
Priority is replaced to determine to upgrade in position in table, only when the both candidate nodes for coming front fail, subsequent candidate
Node just can trigger upgrading replacement；
(5) both candidate nodes disconnect existing network connection: being abnormal when by the determining common recognition node such as heartbeat, fault detection
After delay machine, the automatic upgrading replacement operation of both candidate nodes is triggered；This is the first step that both candidate nodes carry out upgrading replacement；
(6) both candidate nodes more new line online network configuration file: both candidate nodes read the network profile of backup, more new line
Upper network configuration information, the basis established as step (8) network connection；
(7) register and start common recognition service: after starting common recognition service, this node just has the function of common recognition ballot
Can, but other nodes also not with common recognition network establish connection；
(8) both candidate nodes are built a consensus network connection: both candidate nodes update the identity information of oneself, are matched according to latest network
Confidence, which is ceased to the initiation of other nodes, establishes connection request, these nodes include other common recognition nodes being connected originally with common recognition node
And accounting nodes, it connects the same step of establishment process (2).
Further, in the step (1), we determine that node possesses different permissions according to the difference of certificate,
Hold ECert and show that node has the permission of access block chain network, holds RCert and show that node possesses the power for participating in common recognition ballot
Limit；Common recognition node holds ECert and RCert；Accounting nodes hold ECert；Both candidate nodes hold ECert and RCert, still
RCert is only used as a backup to exist, and before node carries out identity upgrading, it does not have any effect；In addition, a candidate section
Point can only specify a common recognition node to go to obtain network of relation link information；
Further, in the step (2), a common recognition node can establish connection with its multiple both candidate nodes.
Further, in the step (3), both candidate nodes are by the network configuration information persistence received in backup net
In network configuration file, it will not influence the network of oneself on the current line of both candidate nodes and configure, only done when both candidate nodes are triggered
When upgrading replacement, the network profile that the network profile on line can be just backed up is replaced, and completes to rise in node
After grade replacement, the network profile of backup is just deleted.
Further, in the step (4), the heartbeat that keepalive is used to do both candidate nodes between node of knowing together is examined
It surveys, judges whether common recognition node survives；What timeout mechanism was mainly used to judge currently to hit carries out the both candidate nodes of upgrading replacement
Whether fail, if both candidate nodes fail, candidate list is also required to be updated, by the both candidate nodes of failure from candidate list
It removes.
Further, in the step (5), both candidate nodes are substantially a special accounting nodes, it may be with
One or more common recognition node establishes connection, therefore needs first to disconnect itself and other common recognition nodes before upgrading on making line
Connection.
Further, in the step (8), the process due to establishing connection needs to carry out authentication, candidate
Node must update the identity information of oneself first before beginning setting up connection, these identity informations need and specified common recognition node
It corresponds, in the present system predominantly hostname information, after guaranteeing node upgrading replacement, node unique identification is kept not
Become, in this way, for know together network other nodes for, just look like only some common recognition node briefly disconnected, net
Network connection, which has occurred, replaces.After completing identity information update, both candidate nodes are configured according to latest network to other nodes
It initiates the connection.
The beneficial effects of the present invention are: the present invention is applied in the block chain network under alliance's chain background, ensure that not
Influence block chain network common recognition efficiency carries out hot standby cut to node of knowing together in mechanism under the premise of not introducing manual operation automatically
It changes, avoids node of knowing together in mechanism and Single Point of Faliure occurs.For traditional block chain, on the one hand, with the operation of block chain, area
The data volume of block chain will be increasing, when critical failure, which occurs, for node of knowing together leads to loss of data, starts a new section
The synchronous whole network data the time it takes of point be it is unpredictable, may cause can not handle transaction in the node short time.It is another
Aspect, BFT class algorithm know together when number of nodes reaches certain amount efficiency decline, it is clear that increase know together node by way of
Nor solving the best approach of node Single Point of Faliure.And it is proposed that alliance's chain node hot standby switch method then solve this
One problem, so that common recognition node failure, which restores the consumed time, only needs second grade.
Detailed description of the invention
Fig. 1 is that node establishes connection journey figure；
Fig. 2 is common recognition node connection status figure；
Fig. 3 is connection status figure after both candidate nodes upgrading replacement；
Specific embodiment
Below according to the drawings and specific embodiments the present invention is described in detail, the objects and effects of the present invention will become brighter
It is aobvious.
A kind of method of alliance's chain node hot standby switch, includes the following steps:
(1) both candidate nodes network configuration: both candidate nodes are substantially a special accounting nodes, hold third party under line
ECert the and RCert certificate that authentication center issues；Both candidate nodes before being initiated, need to specify in its network profile
It is the both candidate nodes of which common recognition node；
(2) both candidate nodes and common recognition node establish connection: both candidate nodes establish connection request to common recognition node initiation, in object
Reason connection is established after completion, starts to carry out both sides' authentication, if authentication does not pass through, connects foundation failure；If body
Part certification passes through, and node confirmation opposite end of knowing together is its both candidate nodes, then does Backup label to it and be put into candidate list
In；
(3) both candidate nodes back up common recognition meshed network configuration: establishing in the connection of both candidate nodes and common recognition node
After completion, the common recognition each network connection information of node is changed, and is notified that both candidate nodes are updated backup；Backup
Data include: other common recognition address of node link informations in block chain network, with the accounting nodes that are connected of node of knowing together
The candidate list of address link information, node of knowing together.Wherein, accounting nodes include both candidate nodes, because both candidate nodes are special
Accounting nodes；
(4) both candidate nodes to common recognition node carry out fault detection: both candidate nodes using the mechanism of keepalive+ time-out come
Judge whether common recognition node survives, replacement operation is upgraded to decide whether to trigger node with this；It is arranged according to both candidate nodes in candidate
Priority is replaced to determine to upgrade in position in table, only when the both candidate nodes for coming front fail, subsequent candidate
Node just can trigger upgrading replacement；
(5) both candidate nodes disconnect existing network connection: being abnormal when by the determining common recognition node such as heartbeat, fault detection
After delay machine, the automatic upgrading replacement operation of both candidate nodes is triggered；This is the first step that both candidate nodes carry out upgrading replacement；
(6) both candidate nodes more new line online network configuration file: both candidate nodes read the network profile of backup, more new line
Upper network configuration information, the basis established as step (8) network connection；
(7) register and start common recognition service: after starting common recognition service, this node just has the function of common recognition ballot
Can, but other nodes also not with common recognition network establish connection；
(8) both candidate nodes are built a consensus network connection: both candidate nodes update the identity information of oneself, are matched according to latest network
Confidence, which is ceased to the initiation of other nodes, establishes connection request, these nodes include other common recognition nodes being connected originally with common recognition node
And accounting nodes, it connects the same step of establishment process (2).
Further, in the step (1), we determine that node possesses different permissions according to the difference of certificate,
Hold ECert and show that node has the permission of access block chain network, holds RCert and show that node possesses the power for participating in common recognition ballot
Limit；Common recognition node holds ECert and RCert；Accounting nodes hold ECert；Both candidate nodes hold ECert and RCert, still
RCert is only used as a backup to exist, and before node carries out identity upgrading, it does not have any effect；In addition, a candidate section
Point can only specify a common recognition node to go to obtain network of relation link information；
Further, in the step (2), a common recognition node can establish connection with its multiple both candidate nodes.
As shown in Figure 1, for the node 1 that connection is established in request, firstly, establishing the request of connection, 2 sound of node to the initiation of node 2
After answering connection request, node 1 and node 2 just establish transport layer encryption connection, can start further authentication and
Key agreement.Whether node 1 is by oneself ECert, RCert and be that the authentication informations such as CVP are sent to node 2.Node 2
After receiving message, firstly, the ECert of verifying node 1, if ECert authentication failed, disconnects；If ECert is verified
And there is RCert in authentication information, illustrate that peer node is a VP node, RCert certificate legitimacy is verified, if tested
Card failure then disconnects, and then two nodes generate a pair of of shared key if the verification passes, can start to carry out safe encryption
Communication；If ECert is verified and does not have RCert in authentication information, illustrate that peer node is a NVP node,
If it is a CVP, makes marks to it and be orderly put into candidate list, similarly generates a pair of of shared key, it can be with
Start to carry out safe coded communication.
Further, in the step (3), CVP matches the network configuration information persistence received in backup network
It sets in file, will not influence the network of oneself on the current line of CVP and configure, only when CVP, which is triggered, does upgrading replacement,
The network profile that network profile on line can be just backed up is replaced, after node completes upgrading replacement, backup
Network profile just be deleted.
Further, in the step (4), the heartbeat that keepalive is used to do both candidate nodes between node of knowing together is examined
It surveys, judges whether common recognition node survives；What timeout mechanism was mainly used to judge currently to hit carries out the both candidate nodes of upgrading replacement
Whether fail, if both candidate nodes fail, candidate list is also required to be updated, by the both candidate nodes of failure from candidate list
It removes.
It is likely to occur various faults situation, we illustrate the processing mode of system under each fault condition by taking Fig. 2 as an example.
The VP0 is connected with two common NVP and two CVP at present as seen from the figure, sequentially stores in the candidate list of VP0 maintenance
The information of CVP-1 and CVP-2, the sequencing of candidate list decides is triggered upgrading by for whom when VP0 cancel closedown.
One: VP0 exception delay machine of scene
After VP0 exception delay machine, the connection of it and NVP-1, NVP-2, CVP-1 and CVP-2 are disconnected.At this point, being arranged from candidate
Table is it is found that it is more than after a certain period of time, to carry out upgrading replacement at once that CVP-1 loses in discovery VP0 heartbeat.Although CVP-2 is in heartbeat
It has also discovered the exception of VP0 during detection, but due to oneself not being candidate list first place, upgrading will not be triggered,
But the case where waiting CVP-1 completion upgrading replacement, VP0 and CVP-1 while abnormal delay machine will be discussed hereinafter.
Two: CVP-1 exception delay machine of scene
VP0 remains normal work under this scene, so the process of upgrading replacement will not occur.However at this point, by
It has been shut down in CVP-1, the first place of VP0 candidate list is no longer valid, at this time if still remain the information of failure for VP0
For be very unfavorable.Therefore, after VP0 has found that CVP-1 is shut down, CVP-1 is deleted from candidate list, while will be newest
Network connection information is sent to other CVP.
Scene three: VP0 and CVP-1 while delay machine
Since shutting down occur in VP0 and the first both candidate nodes CVP-1, therefore, it is necessary to other CVP to upgrade replacement VP0.
We provide a configurable time-out time for system, so that the both candidate nodes of non-first place all can't detect in time-out time
New verifying node there are when, then it is assumed that node upgrades replacement process and time-out occurs, and next bit both candidate nodes is needed to do upgrading
Replacement, the both candidate nodes being hit update the candidate list of oneself before doing upgrading replacement, delete the candidate section of known failure
Point information.
Under these three scenes, it is as shown in Figure 3 that both candidate nodes upgrade replaced network connection state.
Further, in the step 5), CVP is substantially a NVP, it may establish with multiple VP and connect,
Therefore need first to disconnect the connection of itself and other VP nodes before upgrading on making line.
Further, in the step 8), the process due to establishing connection needs to carry out authentication, and CVP exists
Must update oneself identity information before beginning setting up connection first, these identity informations need and VP0 one-to-one correspondence, are at this
It is mainly hostname information in system, after guaranteeing node upgrading replacement, node unique identification is remained unchanged, in this way, for common recognition
For other nodes of network, just look like only VP0 briefly disconnected, network connection has occurred and replaces.It completes
After identity information updates, CVP is configured to other nodes according to latest network and is initiated the connection.
Claims (7)
1. a kind of method of alliance's chain node hot standby switch, which comprises the steps of:
(1) both candidate nodes network configuration: both candidate nodes are substantially a special accounting nodes, hold Third Party Authentication under line
ECert the and RCert certificate that center is issued；Both candidate nodes before being initiated, need to specify it to be in its network profile
The both candidate nodes of which common recognition node.
(2) both candidate nodes and common recognition node establish connection: both candidate nodes establish connection request to common recognition node initiation, connect in physics
After connecing foundation completion, start to carry out both sides' authentication, if authentication does not pass through, connects foundation failure；If identity is recognized
Card passes through, and node confirmation opposite end of knowing together is its both candidate nodes, then does Backup label to it and be put into candidate list.
(3) both candidate nodes back up common recognition meshed network configuration: establishing and complete in the connection of both candidate nodes and common recognition node
After, the common recognition each network connection information of node changes, and is notified that both candidate nodes are updated backup；The data of backup
It include: other common recognition address of node link informations in block chain network, the address of accounting nodes being connected with node of knowing together
The candidate list of link information, node of knowing together.Wherein, accounting nodes include both candidate nodes, because both candidate nodes are special notes
Account node.
(4) both candidate nodes carry out fault detection to common recognition node: both candidate nodes are judged using the mechanism of keepalive+ time-out
Whether common recognition node survives, and upgrades replacement operation with this to decide whether to trigger node；According to both candidate nodes in candidate list
Position come determine upgrading replacement priority, only when come front both candidate nodes fail when, subsequent both candidate nodes
It just can trigger upgrading replacement.
(5) both candidate nodes disconnect existing network connection: being abnormal when by the determining common recognition node of the methods of heartbeat, fault detection
After delay machine, the automatic upgrading replacement operation of both candidate nodes is triggered；This is the first step that both candidate nodes carry out upgrading replacement.
(6) both candidate nodes more new line online network configuration file: both candidate nodes read the network profile of backup, the online of more new line
Network configuration information, the basis established as step (8) network connection.
(7) register and start common recognition service: after starting common recognition service, this node just has the function of common recognition ballot,
But other nodes also not with common recognition network establish connection.
(8) both candidate nodes are built a consensus network connection: both candidate nodes update the identity information of oneself, match confidence according to latest network
It ceases to the initiation of other nodes and establishes connection request, these nodes include other common recognition nodes being connected originally with common recognition node and note
Account node connects the same step of establishment process (2).
2. a kind of method of alliance's chain node hot standby switch as described in claim 1, which is characterized in that the step (1)
In, we determine that node possesses different permissions according to the difference of certificate, hold ECert and show that node has access block link network
The permission of network holds RCert and shows that node possesses the permission for participating in common recognition ballot；Common recognition node holds ECert and RCert；Note
Account node holds ECert；Both candidate nodes hold ECert and RCert, but RCert is only used as a backup to exist, node into
Before the upgrading of row identity, it does not have any effect；In addition, a both candidate nodes can only specify a common recognition node to go to obtain correlation
Network connection information.
3. a kind of method of alliance's chain node hot standby switch as described in claim 1, which is characterized in that the step (2)
In, a common recognition node can establish connection with its multiple both candidate nodes.
4. a kind of method of alliance's chain node hot standby switch as described in claim 1, which is characterized in that the step (3)
In, the network configuration information persistence received in backup network configuration file, will not influence both candidate nodes by both candidate nodes
The network of oneself configures on line at present, the network configuration only when both candidate nodes, which are triggered, does upgrading replacement, on line
The network profile that file can be just backed up is replaced, after node completes upgrading replacement, the network profile of backup
Just it is deleted.
5. a kind of method of alliance's chain node hot standby switch as described in claim 1, which is characterized in that the step (4)
In, keepalive is used to do the heartbeat detection between both candidate nodes and node of knowing together, and judges whether common recognition node survives；Overtime machine
Make whether the both candidate nodes for carrying out upgrading replacement for being mainly used to judge currently to hit fail, it is candidate if both candidate nodes fail
List is also required to be updated, and the both candidate nodes of failure are removed from candidate list.
6. a kind of method of alliance's chain node hot standby switch as described in claim 1, which is characterized in that the step (5)
In, both candidate nodes are substantially a special accounting nodes, it may establish with one or more common recognition node and connect, because
This needs first to disconnect the connection of itself and other common recognition nodes before upgrading on making line.
7. a kind of method of alliance's chain node hot standby switch as described in claim 1, which is characterized in that the step (8)
In, the process due to establishing connection needs to carry out authentication, both candidate nodes before beginning setting up connection first more
The newly identity information of oneself, these identity informations need and specify common recognition node one-to-one correspondence, are mainly in the present system
Hostname information, after guaranteeing node upgrading replacement, node unique identification is remained unchanged, in this way, other for common recognition network
For node, just look like only some common recognition node briefly disconnected, network connection has occurred and replaces.Complete body
After part information update, both candidate nodes are configured to other nodes according to latest network and are initiated the connection.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811639905.8A CN109688012B (en) | 2018-12-29 | 2018-12-29 | Method for hot standby switching of alliance link nodes |
| PCT/CN2019/103671 WO2020134152A1 (en) | 2018-12-29 | 2019-08-30 | Consortium blockchain node hot-standby switching method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811639905.8A CN109688012B (en) | 2018-12-29 | 2018-12-29 | Method for hot standby switching of alliance link nodes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109688012A true CN109688012A (en) | 2019-04-26 |
| CN109688012B CN109688012B (en) | 2020-07-17 |
Family
ID=66190354
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811639905.8A Active CN109688012B (en) | 2018-12-29 | 2018-12-29 | Method for hot standby switching of alliance link nodes |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109688012B (en) |
| WO (1) | WO2020134152A1 (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110351133A (en) * | 2019-06-28 | 2019-10-18 | 阿里巴巴集团控股有限公司 | Method and device for the host node hand-off process in block catenary system |
| CN110430087A (en) * | 2019-09-16 | 2019-11-08 | 上海保险交易所股份有限公司 | The architecture design and realization of block chain heat upgrading |
| CN110572287A (en) * | 2019-09-05 | 2019-12-13 | 腾讯科技（深圳）有限公司 | data disaster tolerance method and device, computer equipment and storage medium |
| CN111104282A (en) * | 2019-11-26 | 2020-05-05 | 众安信息技术服务有限公司 | Node processing method and device based on block chain |
| CN111277645A (en) * | 2020-01-16 | 2020-06-12 | 深圳市网心科技有限公司 | Hot switching method for main and standby nodes, block chain system, block chain node and medium |
| WO2020134152A1 (en) * | 2018-12-29 | 2020-07-02 | 杭州趣链科技有限公司 | Consortium blockchain node hot-standby switching method |
| CN111654393A (en) * | 2020-05-20 | 2020-09-11 | 中国工商银行股份有限公司 | Block chain networking method and system |
| CN111767347A (en) * | 2020-07-27 | 2020-10-13 | 腾讯科技（深圳）有限公司 | Switching method and device of consensus algorithm, node equipment and storage medium |
| WO2020224237A1 (en) * | 2019-05-06 | 2020-11-12 | 深圳壹账通智能科技有限公司 | Blockchain consensus method, apparatus, device and storage medium |
| CN112511338A (en) * | 2020-11-09 | 2021-03-16 | 迅鳐成都科技有限公司 | Block chain consensus network dynamic recovery method, electronic device, system and medium |
| CN112511337A (en) * | 2020-11-09 | 2021-03-16 | 迅鳐成都科技有限公司 | Block chain consensus network self-recovery method, electronic device, system and storage medium |
| US11128522B2 (en) | 2019-06-28 | 2021-09-21 | Advanced New Technologies Co., Ltd. | Changing a master node in a blockchain system |
| CN113472566A (en) * | 2021-06-11 | 2021-10-01 | 北京市大数据中心 | Status monitoring method of union block chain and master node status monitoring system |
| CN113761063A (en) * | 2021-08-26 | 2021-12-07 | 浙商银行股份有限公司 | Block chain migration method and equipment without shutdown and storage medium |
| WO2022048357A1 (en) * | 2020-09-03 | 2022-03-10 | 深圳壹账通智能科技有限公司 | Transaction endorsement method and apparatus, and storage medium |
| US11496558B2 (en) | 2020-01-29 | 2022-11-08 | Hewlett Packard Enterprise Development Lp | Peer-to-peer blockchain fabric management mechanism |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107171829A (en) * | 2017-04-24 | 2017-09-15 | 杭州趣链科技有限公司 | A kind of dynamic node management method for algorithm realization of being known together based on BFT |
| CN107426157A (en) * | 2017-04-21 | 2017-12-01 | 杭州趣链科技有限公司 | A kind of alliance's chain authority control method based on digital certificate and ca authentication system |
| CN107995197A (en) * | 2017-12-04 | 2018-05-04 | 中国电子科技集团公司第三十研究所 | A kind of method for realizing across management domain identity and authority information is shared |
| CN108134706A (en) * | 2018-01-02 | 2018-06-08 | 中国工商银行股份有限公司 | Block chain high-availability system mostly living, computer equipment and method |
| CN108769150A (en) * | 2018-05-14 | 2018-11-06 | 百度在线网络技术（北京）有限公司 | Data processing method, device, clustered node and the storage medium of block chain network |
| CN109426952A (en) * | 2017-08-22 | 2019-03-05 | 汇链丰(北京)科技有限公司 | A kind of block chain framework |
| US20190147190A1 (en) * | 2016-11-19 | 2019-05-16 | Gustavo Manuel Damil Marin | System and method for interaction object management in a blockchain environment |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3639536A2 (en) * | 2016-12-30 | 2020-04-22 | INTEL Corporation | Naming and blockchain recording for the internet of things |
| CN108667614B (en) * | 2018-04-19 | 2021-02-02 | 上海分布信息科技有限公司 | Byzantine fault-tolerant method and implementation system thereof |
| CN108665271A (en) * | 2018-05-02 | 2018-10-16 | 百度在线网络技术（北京）有限公司 | Block chain data processing method, device, equipment and storage medium |
| CN109688012B (en) * | 2018-12-29 | 2020-07-17 | 杭州趣链科技有限公司 | Method for hot standby switching of alliance link nodes |
-
2018
- 2018-12-29 CN CN201811639905.8A patent/CN109688012B/en active Active
-
2019
- 2019-08-30 WO PCT/CN2019/103671 patent/WO2020134152A1/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190147190A1 (en) * | 2016-11-19 | 2019-05-16 | Gustavo Manuel Damil Marin | System and method for interaction object management in a blockchain environment |
| CN107426157A (en) * | 2017-04-21 | 2017-12-01 | 杭州趣链科技有限公司 | A kind of alliance's chain authority control method based on digital certificate and ca authentication system |
| CN107171829A (en) * | 2017-04-24 | 2017-09-15 | 杭州趣链科技有限公司 | A kind of dynamic node management method for algorithm realization of being known together based on BFT |
| CN109426952A (en) * | 2017-08-22 | 2019-03-05 | 汇链丰(北京)科技有限公司 | A kind of block chain framework |
| CN107995197A (en) * | 2017-12-04 | 2018-05-04 | 中国电子科技集团公司第三十研究所 | A kind of method for realizing across management domain identity and authority information is shared |
| CN108134706A (en) * | 2018-01-02 | 2018-06-08 | 中国工商银行股份有限公司 | Block chain high-availability system mostly living, computer equipment and method |
| CN108769150A (en) * | 2018-05-14 | 2018-11-06 | 百度在线网络技术（北京）有限公司 | Data processing method, device, clustered node and the storage medium of block chain network |
Non-Patent Citations (1)
| Title |
|---|
| 袁勇等: "区块链共识算法的发展现状与展望", 《自动化学报》 * |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020134152A1 (en) * | 2018-12-29 | 2020-07-02 | 杭州趣链科技有限公司 | Consortium blockchain node hot-standby switching method |
| WO2020224237A1 (en) * | 2019-05-06 | 2020-11-12 | 深圳壹账通智能科技有限公司 | Blockchain consensus method, apparatus, device and storage medium |
| CN110351133A (en) * | 2019-06-28 | 2019-10-18 | 阿里巴巴集团控股有限公司 | Method and device for the host node hand-off process in block catenary system |
| US11128522B2 (en) | 2019-06-28 | 2021-09-21 | Advanced New Technologies Co., Ltd. | Changing a master node in a blockchain system |
| CN110351133B (en) * | 2019-06-28 | 2021-09-17 | 创新先进技术有限公司 | Method and device for main node switching processing in block chain system |
| CN110572287A (en) * | 2019-09-05 | 2019-12-13 | 腾讯科技（深圳）有限公司 | data disaster tolerance method and device, computer equipment and storage medium |
| CN110572287B (en) * | 2019-09-05 | 2022-03-18 | 腾讯科技（深圳）有限公司 | Data disaster tolerance method and device, computer equipment and storage medium |
| CN110430087B (en) * | 2019-09-16 | 2022-04-05 | 上海保险交易所股份有限公司 | Block chain hot upgrade architecture design and implementation |
| CN110430087A (en) * | 2019-09-16 | 2019-11-08 | 上海保险交易所股份有限公司 | The architecture design and realization of block chain heat upgrading |
| CN111104282A (en) * | 2019-11-26 | 2020-05-05 | 众安信息技术服务有限公司 | Node processing method and device based on block chain |
| CN111104282B (en) * | 2019-11-26 | 2024-01-16 | 众安信息技术服务有限公司 | Node processing method and device based on block chain |
| CN111277645B (en) * | 2020-01-16 | 2023-02-10 | 深圳市迅雷网络技术有限公司 | Hot switching method for main and standby nodes, block chain system, block chain node and medium |
| CN111277645A (en) * | 2020-01-16 | 2020-06-12 | 深圳市网心科技有限公司 | Hot switching method for main and standby nodes, block chain system, block chain node and medium |
| US11496558B2 (en) | 2020-01-29 | 2022-11-08 | Hewlett Packard Enterprise Development Lp | Peer-to-peer blockchain fabric management mechanism |
| CN111654393B (en) * | 2020-05-20 | 2023-01-06 | 中国工商银行股份有限公司 | Block chain networking method and system |
| CN111654393A (en) * | 2020-05-20 | 2020-09-11 | 中国工商银行股份有限公司 | Block chain networking method and system |
| CN111767347B (en) * | 2020-07-27 | 2021-09-10 | 腾讯科技（深圳）有限公司 | Switching method and device of consensus algorithm, node equipment and storage medium |
| CN111767347A (en) * | 2020-07-27 | 2020-10-13 | 腾讯科技（深圳）有限公司 | Switching method and device of consensus algorithm, node equipment and storage medium |
| WO2022048357A1 (en) * | 2020-09-03 | 2022-03-10 | 深圳壹账通智能科技有限公司 | Transaction endorsement method and apparatus, and storage medium |
| CN112511337A (en) * | 2020-11-09 | 2021-03-16 | 迅鳐成都科技有限公司 | Block chain consensus network self-recovery method, electronic device, system and storage medium |
| CN112511337B (en) * | 2020-11-09 | 2023-03-14 | 迅鳐成都科技有限公司 | Block chain consensus network self-recovery method, electronic device, system and storage medium |
| CN112511338A (en) * | 2020-11-09 | 2021-03-16 | 迅鳐成都科技有限公司 | Block chain consensus network dynamic recovery method, electronic device, system and medium |
| CN113472566A (en) * | 2021-06-11 | 2021-10-01 | 北京市大数据中心 | Status monitoring method of union block chain and master node status monitoring system |
| CN113761063A (en) * | 2021-08-26 | 2021-12-07 | 浙商银行股份有限公司 | Block chain migration method and equipment without shutdown and storage medium |
| CN113761063B (en) * | 2021-08-26 | 2024-04-16 | 浙商银行股份有限公司 | Non-stop blockchain migration method, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020134152A1 (en) | 2020-07-02 |
| CN109688012B (en) | 2020-07-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109688012A (en) | A kind of method of alliance's chain node hot standby switch | |
| US11809291B2 (en) | Method and apparatus for redundancy in active-active cluster system | |
| CN107040594A (en) | The method and device of license block chain node access based on PBFT | |
| US20100174807A1 (en) | System and method for providing configuration synchronicity | |
| CN110784495B (en) | Block chain-based discovery and configuration information management method for big data cluster system | |
| CN100397803C (en) | N+1 duplicates data real-time synchronising method | |
| CN107105032A (en) | node device operation method and node device | |
| CN105933407B (en) | method and system for realizing high availability of Redis cluster | |
| US7730029B2 (en) | System and method of fault tolerant reconciliation for control card redundancy | |
| CN107124305B (en) | Node device operation method and node device | |
| CN108846745B (en) | Block chain transaction processing auxiliary system, block chain data processing system and method | |
| CN107919977A (en) | A kind of on-line rapid estimation of the distributed consensus system based on Paxos agreements, the method and apparatus of online capacity reducing | |
| WO2018113543A1 (en) | Management method, system, and device for master and standby databases | |
| CN113409145A (en) | Cross-block-chain transaction synchronization method and device | |
| CN113965578A (en) | Method, device, equipment and storage medium for electing master node in cluster | |
| US20230004465A1 (en) | Distributed database system and data disaster backup drilling method | |
| CN105323271B (en) | Cloud computing system and processing method and device thereof | |
| CN111338767B (en) | PostgreSQL master-slave database automatic switching system and method | |
| CN103780433B (en) | Self-healing type virtual resource configuration management data architecture | |
| US10756975B2 (en) | Multiple site rolling upgrade protocol | |
| CN111338848B (en) | Failure application copy processing method and device, computer equipment and storage medium | |
| CN108038782B (en) | Security system for securities trading and security verification method for securities trading | |
| Jehl et al. | Asynchronous reconfiguration for Paxos state machines | |
| CN112667449B (en) | Cluster management method and device | |
| KR102294048B1 (en) | Method and system for replicating blockchain application service |
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 |