CN111539706A - Bill operation method and system based on alliance chain - Google Patents
Bill operation method and system based on alliance chain Download PDFInfo
- Publication number
- CN111539706A CN111539706A CN202010290203.4A CN202010290203A CN111539706A CN 111539706 A CN111539706 A CN 111539706A CN 202010290203 A CN202010290203 A CN 202010290203A CN 111539706 A CN111539706 A CN 111539706A
- Authority
- CN
- China
- Prior art keywords
- bill
- alliance
- paid
- node
- nodes
- 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.)
- Pending
Links
Images
Classifications
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/085—Payment architectures involving remote charge determination or related payment systems
- G06Q20/0855—Payment architectures involving remote charge determination or related payment systems involving a third party
Abstract
The specification discloses a bill operation method and system based on a alliance chain, wherein the alliance chain comprises alliance main nodes and a plurality of alliance friend nodes, and the method comprises the following steps: the alliance main node initiates consensus aiming at the bill to be paid in an alliance chain; the alliance nodes which achieve consensus on the bill to be paid formulate a bill payment scheme based on the bill to be paid respectively, and synchronize the formulated bill payment scheme to other nodes of the alliance chain through a consensus mechanism of the alliance chain; accessing a client of an allied node, selecting a target bill payment scheme provided by a target allied node from bill payment schemes formulated by the allied node which agrees with the bill to be paid, and paying the bill to be paid based on the target bill payment scheme; and the client uploads the transaction carrying the payment credential to the alliance chain through the accessed alliance nodes.
Description
Technical Field
The present document relates to the field of computer technologies, and in particular, to a bill operation method and system based on a federation chain.
Background
At present, the bill is centrally provided with a bill inquiry capability by an account-out system, and a user or a merchant inquires and recommends a third-party bill payment platform such as a payment application, a client of xx bank and the like after acquiring the bill.
However, when a plurality of users or merchants inquire bills at the same time, for example, when the bills are inquired at the same time, the pressure of the charge-off system center is very large, and the multi-party inquiry also has the defect of asynchronization due to network message transmission. In addition, for the user or the merchant, the user or the merchant can only receive unilateral recommendation marketing after obtaining the bill, and the user or the merchant has no option for a third-party bill payment platform.
Disclosure of Invention
The embodiment of the specification provides a bill operation method and a bill operation system based on a federation chain, which are used for solving the problems that in the prior art, the pressure of a charge-off center is too large, and a user usually has no option for a third-party payment platform for paying a bill to be paid after receiving the bill to be paid.
In order to solve the above technical problem, the embodiments of the present specification are implemented as follows:
in a first aspect, a method for bill operation based on a federation chain is provided, where the federation chain includes a federation master node and a plurality of federation friend nodes, and the method includes:
the alliance main node initiates consensus aiming at the bill to be paid in an alliance chain;
the alliance nodes which achieve consensus on the bill to be paid formulate a bill payment scheme based on the bill to be paid respectively, and synchronize the formulated bill payment scheme to other nodes of the alliance chain through a consensus mechanism of the alliance chain;
accessing a client of an allied node, selecting a target bill payment scheme provided by a target allied node from bill payment schemes formulated by the allied node which agrees with the bill to be paid, and paying the bill to be paid based on the target bill payment scheme;
and the client uploads the transaction carrying the payment credential to the alliance chain through the accessed alliance nodes, wherein the payment credential is the credential for paying the bill to be paid based on the target bill payment scheme.
In a second aspect, a federation chain-based billing operation system is provided, which includes a federation master node, a plurality of federation friend nodes, and a client, wherein:
the alliance main node initiates consensus aiming at the bill to be paid in an alliance chain;
the alliance nodes which achieve consensus on the bill to be paid formulate a bill payment scheme based on the bill to be paid respectively, and synchronize the formulated bill payment scheme to other nodes of the alliance chain through a consensus mechanism of the alliance chain;
the method comprises the steps that a client side of an alliance node is accessed, a target bill payment scheme provided by the target alliance node is selected from bill payment schemes formulated by alliance nodes which agree with the bill to be paid, the bill to be paid is paid based on the target bill payment scheme, and a transaction carrying payment credentials is uploaded to the alliance chain through the accessed alliance nodes, wherein the payment credentials are the credentials for paying the bill to be paid based on the target bill payment scheme.
The embodiment of the specification can achieve at least the following technical effects by adopting the technical scheme:
the alliance main node initiates consensus aiming at the bill to be paid in the alliance chain; the method comprises the steps that alliance nodes which achieve consensus on bills to be paid formulate bill payment schemes based on the bills to be paid respectively, and synchronize the formulated bill payment schemes to other nodes of a federation chain through a consensus mechanism of the federation chain; the method comprises the steps of accessing a client of an alliance node, selecting a target bill payment scheme provided by the target alliance node from bill payment schemes formulated by the alliance node which agrees with a bill to be paid, paying the bill to be paid based on the target bill payment scheme, uploading a transaction carrying a payment credential to an alliance chain through the accessed alliance node, wherein the payment credential is the credential for paying the bill to be paid based on the target bill payment scheme.
The method comprises the steps that an alliance main node can initiate consensus of bills to be paid in an alliance chain, so that after the multiple alliance nodes in the alliance chain achieve the consensus of the bills to be paid, the bills to be paid are recorded in a newly added block of each node, each alliance node can formulate a bill payment scheme based on the bills to be paid and synchronize the bill payment scheme formulated by the alliance node to other nodes in the alliance chain, and therefore when a user obtains the bill payment scheme formulated by the alliance nodes through a client, the bill payment scheme meeting the actual requirements of the alliance node can be selected to pay the bills to be paid, and when the bills to be paid are inquired before payment, the bills to be paid can be inquired and obtained on the selected target alliance node side. On one hand, the expenditure presentation and checking pressure on the allied master node side is relieved, and on the other hand, various options are provided for the user to pay bills to be paid.
Drawings
The accompanying drawings, which are included to provide a further understanding of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the description serve to explain the specification and not to limit the specification in a non-limiting sense. In the drawings:
fig. 1 is a schematic flowchart of a federation chain-based bill operation method provided in an embodiment of the present specification;
fig. 2 is a schematic diagram of a bill operation method in a federation chain, provided in an embodiment of the present specification, applied in an actual scenario;
fig. 3 is a schematic structural diagram of a federation chain-based billing operation system according to an embodiment of the present specification.
Detailed Description
In order to make the purpose, technical solutions and advantages of this document more clear, the technical solutions of this specification will be clearly and completely described below with reference to specific embodiments of this specification and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of this document, and not all embodiments. All other embodiments obtained by a person skilled in the art without making any inventive step based on the embodiments in this description belong to the protection scope of this document.
The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.
Billing is a form of payment credential for the user, but for some business entities is a resource that pulls traffic and even a portal for subsequent profit. As described in the background art, the current bill is provided with a bill inquiry capability by centralizing an accounting system, and a user or a merchant inquires and recommends a third-party bill payment platform such as a payment application, a client of xx bank and the like after acquiring the bill by self. However, the existing centralized mode of the charge-off system generally causes great charge-off pressure to the charge-off system, and for a user or a bill partner merchant, the user or the merchant can only receive unilateral recommendation and marketing after obtaining a bill, and has no option for a third-party bill payment platform.
The block chain is used as a shared database, and the data or information stored in the block chain has the characteristics of unforgeability, whole-course trace, traceability, public transparency, collective maintenance and the like. Based on the characteristics, the block chain technology lays a solid 'trust' foundation, creates a reliable 'cooperation' mechanism and has wide application prospect. While a federation chain is one of blockchains, which is not as large as a public chain, can provide several organizations or individuals with write permission for blockchains, and is convenient to maintain. Based on the above, in order to solve the problems that the pressure of the billing center is too high and the user usually has no option for the third-party payment platform for paying the bill to be paid after receiving the bill to be paid in the prior art, an embodiment of the present disclosure provides a bill operating method based on a federation chain, where the federation chain includes a federation master node and a plurality of federation friend nodes.
Specifically, after the accounting system corresponding to the alliance owner node generates the bill to be paid, the alliance owner node initiates consensus on the bill to be paid in the alliance chain; the method comprises the steps that alliance nodes which achieve consensus on bills to be paid formulate bill payment schemes based on the bills to be paid respectively, and synchronize the formulated bill payment schemes to other nodes of a federation chain through a consensus mechanism of the federation chain; the method comprises the steps of accessing a client of an alliance node, selecting a target bill payment scheme provided by the target alliance node from bill payment schemes formulated by the alliance node which agrees with a bill to be paid, paying the bill to be paid based on the target bill payment scheme, uploading a transaction carrying a payment credential to an alliance chain through the accessed alliance node, wherein the payment credential is the credential for paying the bill to be paid based on the target bill payment scheme.
The method comprises the steps that an alliance main node can initiate consensus of bills to be paid in an alliance chain, so that after the multiple alliance nodes in the alliance chain achieve the consensus of the bills to be paid, the bills to be paid are recorded in a newly added block of each node, each alliance node can formulate a bill payment scheme based on the bills to be paid and synchronize the bill payment scheme formulated by the alliance node to other nodes in the alliance chain, and therefore when a user obtains the bill payment scheme formulated by the alliance nodes through a client, the bill payment scheme meeting the actual requirements of the alliance node can be selected to pay the bills to be paid, and when the bills to be paid are inquired before payment, the bills to be paid can be inquired and obtained on the selected target alliance node side. On one hand, the expenditure presentation and checking pressure on the allied master node side is relieved, and on the other hand, various options are provided for the user to pay bills to be paid.
Specifically, an implementation flow diagram of a bill operation method based on a federation chain provided by one or more embodiments of the present specification is shown in fig. 1, and includes:
at step 110, the federation master node initiates a consensus on the bill to be paid in the federation chain.
In order to relieve the centralized billing pressure of the billing system, the federation master node in the embodiment of the present specification may be created and maintained by the billing system, and a federation chain is created by the federation master node, a plurality of third-party payment platforms may apply for residing in the federation chain created by the federation master node as federation member nodes in the federation chain, after each bill to be paid is generated by the billing system, the bill to be paid may be synchronized to a plurality of federation member node sides in the federation chain through a consensus mechanism of the federation chain, so that the plurality of federation member nodes agree on the bill to be paid, and after agreeing on the bill to be paid, a block in which the bill to be paid is recorded is generated on each federation chain side.
In this case, when the client user accessing the alliance node wants to inquire the bill to be paid, the client user can inquire not only in the charge-out system, but also in the corresponding alliance chain side through preset interfaces provided by the alliance main node and the alliance node in the alliance chain, so that the pressure of centralized charge-out and charge-checking of the charge-out system is greatly relieved.
Optionally, in order to reduce centralized billing and checking pressure of the billing system, the billing system may synchronize the generated bill to be paid to other nodes in the federation chain through the federation master node according to the consensus mechanism of the federation chain. It should be understood that when the alliance owner node synchronizes the bill to be paid to other nodes in the alliance chain through an agreement mechanism of the alliance chain, firstly, agreement on the bill to be paid needs to be initiated in the alliance chain, and after no less than a specified number of nodes in the alliance chain agree on the bill to be paid, each agreed node generates a block on the side of the corresponding alliance chain, wherein the block records the bill to be paid. Specifically, the federation master node initiates consensus on the bill to be paid in the federation chain, including:
the alliance main node sends the proposal containing the bill to be paid to a plurality of alliance nodes;
the proposed allied nodes are received to carry out consensus on bills to be paid;
if the nodes not less than the specified number in the alliance chain agree with the bill to be paid, the nodes agreeing with the bill to be paid generate a block recording the bill to be paid;
wherein the specified number is 3f +1, and f is the maximum number of abnormal nodes allowed in the federation chain.
Assuming that the number of nodes in the federation chain is 5, and the maximum number of abnormal nodes allowed in the federation chain is 1, the abnormal nodes are nodes which may be down, when a node whose number of nodes in the federation chain is not less than 3f +1 ═ 4 agrees on the bill to be paid, the node whose number of nodes is not less than 4 generates a block recording the bill to be paid.
It should be understood that, because the bill to be paid, which is synchronized to the federation chain by the account-issuing system through the federation master node, passes through the consensus of more than or equal to 3f +1 nodes in the federation chain, the bill to be paid, which is recorded on the federation chain side of the node achieving the consensus on the bill to be paid, has a certain credibility, so that the bill to be paid, which is uploaded to the federation chain, is difficult to be tampered, and the rights and interests of the user corresponding to the bill to be paid are guaranteed.
And 120, the ally-member nodes which agree with the bill to be paid formulate a bill payment scheme based on the bill to be paid respectively, and synchronize the formulated bill payment scheme to other nodes of the alliance chain through an agreement mechanism of the alliance chain.
As described above, in order to guarantee the credibility of the bill to be paid, the number of federate nodes sharing the consensus on the bill to be paid is at least 3f +1 nodes, where f is the maximum number of abnormal nodes allowed in the federation chain. Assuming that f is 1, the number of alliance nodes agreeing to pay bills is 4-1 to 3 (for example, alliance nodes 1 to 3 are included), and the number of alliance master nodes is 1.
First, the allied node 1 to the allied node 3 make a bill payment scheme based on the bill to be paid, respectively, and specifically, the allied node 1 makes a bill payment scheme 1 based on the bill to be paid (i.e., 100 full of payment amount minus two yuan), the allied node 2 makes a bill payment scheme 2 based on the bill to be paid (i.e., 49 full of payment amount minus one yuan), and the allied node 3 makes a bill payment scheme 3 based on the bill to be paid (i.e., 100 full of payment amount gives a two-yuan telephone charge ticket).
Then, the alliance node 1 synchronizes the bill payment scheme 1 to other nodes in the alliance chain through a consensus mechanism, the alliance node 2 synchronizes the bill payment scheme 2 to other nodes in the alliance chain through the consensus mechanism, and the alliance node 3 synchronizes the bill payment scheme 3 to other nodes in the alliance chain through the consensus mechanism.
It should be understood that, because there is a certain competitive relationship between alliance nodes, in order to ensure a certain fairness and prevent a bill payment scheme formulated by a certain alliance node from being hacked by other alliance nodes, in the embodiment of the present specification, an alliance node agreeing to a bill to be paid may encrypt the bill payment scheme formulated by the alliance node after formulating the bill payment scheme based on the bill to be paid, and then synchronize the encrypted bill payment scheme with other nodes in the alliance chain through an agreement mechanism of the alliance chain. Optionally, synchronizing the formulated bill payment scheme to other nodes of the federation chain through the consensus mechanism of the federation chain by the federation member node agreeing with the bill to be paid, including:
encrypting the formulated bill payment scheme by the ally-connected node which agrees with the bill to be paid to obtain the encrypted bill payment scheme;
and synchronizing the encrypted bill payment scheme to other nodes of the alliance chain through an agreement mechanism.
The method comprises the steps that an alliance node which agrees with a bill to be paid encrypts a formulated bill payment scheme, and the formulated bill payment scheme can be encrypted through a private key of the alliance node. For example, the formulated bill payment scheme may be hashed to obtain a hash value, and then the hash value is encrypted by using a private key to obtain an encrypted bill payment scheme. After the client or the alliance master node receives the encrypted bill payment scheme, the client or the alliance master node can decrypt the encrypted bill payment scheme based on the public key matched with the private key of the alliance node to obtain the decrypted bill payment scheme.
Optionally, in order to improve the reliability of the bill payment scheme uploaded into the federation chain, the federation node agreeing on the bill to be paid synchronizes the encrypted bill payment scheme to other nodes of the federation chain through a consensus mechanism, including:
and the alliance nodes which agree with the bill to be paid initiate consensus on the encrypted bill payment scheme in the alliance chain, so that other nodes in the alliance chain agree with the encrypted bill payment scheme, and blocks in which the encrypted bill payment scheme is recorded are respectively generated after the consensus is agreed.
Specifically, after the federate node agreeing with the bill to be paid initiates agreement on the encrypted bill payment scheme in the federation chain, the node of the encrypted bill payment scheme is received, the agreement operation is performed on the encrypted bill payment scheme, and if it is determined that nodes not less than the specified number in the federation chain agree with the encrypted bill payment scheme, the node agreeing with the encrypted bill payment scheme generates a block in which the encrypted bill payment scheme is recorded. Wherein the specified number is 3f +1, and f is the maximum number of abnormal nodes allowed in the federation chain.
And step 130, accessing the client side of the alliance node, selecting a target bill payment scheme provided by the target alliance node from bill payment schemes formulated by the alliance node which agrees with the bill to be paid, and paying the bill to be paid based on the target bill payment scheme.
It should be understood that, in order to facilitate a client user to obtain a bill payment scheme and a bill to be paid provided in a federation chain, the embodiments of the present specification may provide a preset interface for accessing an alliance node and an alliance master node in the federation chain for the client, so that the client may obtain the bill to be paid and a bill payment scheme formulated by a plurality of alliance nodes from an alliance master node side or an alliance master node side of the federation chain based on the preset interface. Optionally, accessing a client of the allied node, and paying the bill to be paid based on the target bill payment scheme includes:
the client acquires a bill to be paid through a preset interface provided by the target allied node;
and the client pays the bill to be paid based on the target bill payment scheme.
And accessing a client of the ally nodes, after obtaining the bill to be paid and the bill payment schemes formulated by the ally nodes through a preset interface provided by the ally nodes, selecting a bill payment scheme meeting the own equity requirement from the bill payment schemes formulated by the ally nodes based on the own equity requirement, and paying the bill to be paid based on the bill payment scheme.
Continuing with the example above, assume that alliance node 1 establishes bill payment scheme 1 based on the bill to be paid (i.e., 100 dollar full of payment), alliance node 2 establishes bill payment scheme 2 based on the bill to be paid (i.e., 49 dollar per full of payment), alliance node 3 establishes bill payment scheme 3 based on the bill to be paid (i.e., 100 dollar bill to pay), and the bill to be paid is 99 dollar in amount.
After seeing the bill to be paid and the three bill payment schemes, the user can select a bill payment scheme which is most suitable for the self demand based on the self demand, and if the bill payment scheme is the bill payment scheme 2, after the user selects the bill payment scheme 2 formulated by the alliance node 2, the user can pay the bill to be paid based on the bill payment scheme 2, namely, the user can complete the payment of the bill to be paid only by paying 99-2 yuan or 97 yuan on a third party payment platform corresponding to the alliance node 3.
And step 140, the client uploads the transaction carrying the payment credential to the alliance chain through the accessed alliance nodes, wherein the payment credential is the credential for paying the bill to be paid based on the target bill payment scheme.
In order to facilitate tracing of the payment record of the client user, obtain the payment credential of the user, and perform a verification operation on the bill to be paid of the user based on the payment credential of the user, in this embodiment, after the client user completes payment of the bill to be paid, the client further uploads the transaction carrying the payment credential to the alliance chain through the accessed alliance node.
Optionally, in order to improve the credibility of the payment credential of the client user and avoid that the payment credential is maliciously tampered, in this embodiment of the present specification, after the client uploads the transaction carrying the payment credential to the federation chain through the accessed federate node, the method further includes:
the alliance main node is used for fishing out the transaction carrying the payment credential from a transaction pool of the alliance chain;
and the ally leader node synchronizes the transaction carrying the payment credentials to a plurality of ally member nodes through a consensus mechanism.
Specifically, the alliance master node may initiate consensus on the transaction carrying the payment credential in an alliance chain, and after determining that no less than a specified number of nodes agree with the transaction carrying the payment credential, the alliance master node may generate a block recording the transaction at each alliance chain side. It should be appreciated that to facilitate determining which alliance node formulated bill payment scheme the client user selected, the payment credentials may also indicate the client user's selection, i.e., indicate that the client user completed payment of the bill to be paid based on which alliance node formulated bill payment scheme.
It should be understood that after the bill to be paid is paid and needs to be verified and sold on the alliance node side, the alliance node synchronizes the transaction carrying the payment credentials into a plurality of alliance nodes through a consensus mechanism, and the method further comprises the following steps:
and the alliance main node performs verification and cancellation operation on the bill to be paid based on the transaction carrying the payment credential.
It should be understood that after the bill to be paid is paid and needs to be verified and sold on the target alliance node side, the alliance master node synchronizes the transaction carrying the payment credentials into a plurality of alliance nodes through a consensus mechanism, and the method further comprises the following steps:
and the target ally node performs the verification and cancellation operation on the bill to be paid according to the transaction carrying the payment credential.
It should be understood that after the client user pays the bill to be paid based on the target bill payment scheme, if the payment amount is posted to the third party payment platform corresponding to the target alliance node, the third party payment platform also needs to settle to the charge-out system corresponding to the alliance main node based on the amount of the bill to be paid.
The method provided by the embodiment of the present specification is described in detail below with reference to a schematic diagram of a federation chain-based bill operation method applied in an actual scene, which is shown in fig. 2. The federation chain shown in fig. 2 includes federation master node 210 and 3 federation nodes 220 (i.e., federation node 1, federation node 2, and federation node 3), and the client interacting with the federation chain is 230, and the interaction flow includes:
s21, the charge-off system sends the generated bill to be paid to the alliance host node through a preset interface;
s22, the alliance main node 210 synchronizes the bill to be paid to alliance nodes 1-3 through an alliance mechanism in an alliance chain, and after no less than 3f +1 nodes in the alliance chain agree with the bill to be paid, the alliance main node and the alliance nodes 1-3 respectively generate blocks recording the bill to be paid on the respective alliance chain side;
s23, the alliance operation system corresponding to the alliance node 3 formulates a bill payment scheme 3 based on the bill to be paid, and synchronizes to the alliance main node and the alliance nodes 1 and 2 through an consensus mechanism in an alliance chain;
s24, the alliance operation system corresponding to the alliance node 2 makes a bill payment scheme 2 based on the bill to be paid, and synchronizes to the alliance main node and the alliance nodes 1 and 3 through an consensus mechanism in an alliance chain;
s25, the alliance operation system corresponding to the alliance node 1 makes a bill payment scheme 1 based on the bill to be paid, and synchronizes to the alliance main node and the alliance nodes 2 and 3 through an consensus mechanism in an alliance chain;
s26, the client user obtains the bill to be paid and the bill payment schemes 1-3 through a preset interface provided by the alliance chain, and selects a target bill payment scheme (assuming to be the bill payment scheme 2) meeting the interest requirement from the bill payment schemes 1-3 based on the bill to be paid;
s27, the client user pays the bill to be paid based on the bill payment scheme 2, and the client uploads the payment credential to the alliance chain;
s28, the alliance main node synchronizes the transaction carrying the payment credential to other nodes in the alliance chain based on a consensus mechanism in the alliance chain, wherein the payment credential is the credential for paying the bill to be paid based on the bill payment scheme 2;
and S29, the ally owner node verifies and sells the bill to be paid based on the payment credential.
By adopting the method provided by the embodiment of the specification, the alliance main node initiates consensus aiming at the bill to be paid in the alliance chain; the method comprises the steps that alliance nodes which achieve consensus on bills to be paid formulate bill payment schemes based on the bills to be paid respectively, and synchronize the formulated bill payment schemes to other nodes of a federation chain through a consensus mechanism of the federation chain; the method comprises the steps of accessing a client of an alliance node, selecting a target bill payment scheme provided by the target alliance node from bill payment schemes formulated by the alliance node which agrees with a bill to be paid, paying the bill to be paid based on the target bill payment scheme, uploading a transaction carrying a payment credential to an alliance chain through the accessed alliance node, wherein the payment credential is the credential for paying the bill to be paid based on the target bill payment scheme.
The method comprises the steps that an alliance main node can initiate consensus of bills to be paid in an alliance chain, so that after the multiple alliance nodes in the alliance chain achieve the consensus of the bills to be paid, the bills to be paid are recorded in a newly added block of each node, each alliance node can formulate a bill payment scheme based on the bills to be paid and synchronize the bill payment scheme formulated by the alliance node to other nodes in the alliance chain, and therefore when a user obtains the bill payment scheme formulated by the alliance nodes through a client, the bill payment scheme meeting the actual requirements of the alliance node can be selected to pay the bills to be paid, and when the bills to be paid are inquired before payment, the bills to be paid can be inquired and obtained on the selected target alliance node side. On one hand, the expenditure presentation and checking pressure on the allied master node side is relieved, and on the other hand, various options are provided for the user to pay bills to be paid.
Fig. 3 is a schematic structural diagram of a bill operation system 300 based on a federation chain according to an embodiment of the present specification. Referring to fig. 3, in one software implementation, a federation chain-based billing operations system 300 may include an alliance node 310, a plurality of alliance nodes 320, and an alliance node-accessing client 330, wherein:
the federation master node 310 initiates a consensus on the bill to be paid in the federation chain;
the client 330 accessing the alliance node selects a target bill payment scheme provided by the target alliance node from bill payment schemes formulated by alliance nodes agreeing on the bill to be paid, pays the bill to be paid based on the target bill payment scheme, and uploads a transaction carrying payment credentials to the alliance chain through the accessed alliance node, wherein the payment credentials are the credentials for paying the bill to be paid based on the target bill payment scheme.
The method comprises the steps that an alliance main node can initiate consensus of bills to be paid in an alliance chain, so that after the multiple alliance nodes in the alliance chain achieve the consensus of the bills to be paid, the bills to be paid are recorded in a newly added block of each node, each alliance node can formulate a bill payment scheme based on the bills to be paid and synchronize the bill payment scheme formulated by the alliance node to other nodes in the alliance chain, and therefore when a user obtains the bill payment scheme formulated by the alliance nodes through a client, the bill payment scheme meeting the actual requirements of the alliance node can be selected to pay the bills to be paid, and when the bills to be paid are inquired before payment, the bills to be paid can be inquired and obtained on the selected target alliance node side. On one hand, the expenditure presentation and checking pressure on the allied master node side is relieved, and on the other hand, various options are provided for the user to pay bills to be paid.
Optionally, in an embodiment, the ally node 320 agreeing on the bill to be paid is configured to:
encrypting the formulated bill payment scheme to obtain an encrypted bill payment scheme;
synchronizing the encrypted bill payment scheme into other nodes of the federation chain through the consensus mechanism.
Optionally, in an embodiment, the ally node 420 agreeing on the bill to be paid is configured to:
initiating consensus on the encrypted bill payment scheme in the federation chain, so that other nodes of the federation chain perform consensus operations on the encrypted bill payment scheme, and generating blocks recorded with the encrypted bill payment scheme after consensus is achieved.
Optionally, in an embodiment, after the client 330 uploads the transaction carrying the payment credential to the federation chain through an accessed alliance node, the alliance node 310 is configured to:
the transaction carrying the payment credential is fished from a transaction pool of the alliance chain;
and synchronizing the transaction carrying the payment credential to the plurality of ally nodes through the consensus mechanism.
Optionally, in an embodiment, after the ally owner node 310 synchronizes the transaction carrying the payment credential to the plurality of ally-member nodes through the consensus mechanism, the ally owner node 310 is further configured to:
and the ally owner node 310 performs a verification operation on the bill to be paid based on the transaction carrying the payment credential.
Optionally, in an embodiment, after the ally owner node 310 synchronizes the transaction carrying the payment credential to the plurality of ally nodes through the consensus mechanism, the target ally node 420 is configured to:
and carrying out verification and cancellation operation on the bill to be paid according to the transaction carrying the payment credential.
Optionally, in an embodiment, the ally owner node 310 is configured to:
sending an offer containing a bill to be paid to the plurality of federate nodes;
the federate node 320 receiving the proposal agrees on the bill to be paid;
if the nodes 320 in the alliance chain with the number not less than the specified number achieve consensus on the bill to be paid, generating a block recorded with the bill to be paid by the alliance nodes achieving consensus on the bill to be paid;
wherein the specified number is 3f +1, and f is the maximum number of abnormal nodes allowed in the federation chain.
Optionally, in an embodiment, the ally-connected node client 430 is accessed to:
acquiring the bill to be paid through a preset interface provided by the target allied node;
paying the bill to be paid based on the target bill payment scheme.
The bill operation system 300 based on the federation chain can implement the method in the embodiment of the method shown in fig. 1 to fig. 2, which specifically refers to the bill operation method based on the federation chain in the embodiment shown in fig. 1 to fig. 2 and is not described again.
In short, the above description is only a preferred embodiment of the present disclosure, and is not intended to limit the scope of the present disclosure. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of the present disclosure should be included in the scope of protection of one or more embodiments of the present disclosure.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
Claims (10)
1. A federation chain-based billing operation method, the federation chain including a federation master node and a plurality of federation friend nodes, the method comprising:
the alliance main node initiates consensus aiming at the bill to be paid in an alliance chain;
the alliance nodes which achieve consensus on the bill to be paid formulate a bill payment scheme based on the bill to be paid respectively, and synchronize the formulated bill payment scheme to other nodes of the alliance chain through a consensus mechanism of the alliance chain;
accessing a client of an allied node, selecting a target bill payment scheme provided by a target allied node from bill payment schemes formulated by the allied node which agrees with the bill to be paid, and paying the bill to be paid based on the target bill payment scheme;
and the client uploads the transaction carrying the payment credential to the alliance chain through the accessed alliance nodes, wherein the payment credential is the credential for paying the bill to be paid based on the target bill payment scheme.
2. The method of claim 1, wherein the federate node agreeing to the bill to be paid, synchronizing the formulated bill payment scheme into other nodes of the federation chain through the consensus mechanism of the federation chain, comprises:
encrypting the formulated bill payment scheme by the ally-member node which agrees with the bill to be paid to obtain an encrypted bill payment scheme;
and synchronizing the encrypted bill payment scheme to other nodes of the alliance chain through the consensus mechanism.
3. The method of claim 2, wherein the federate node agreeing to the bill to be paid, synchronizing the encrypted bill payment scheme to other nodes of the federation chain through the agreement mechanism, comprises:
the method comprises the steps that alliance nodes which agree on the bill to be paid initiate agreement on the encrypted bill payment scheme in the alliance chain, so that other nodes of the alliance chain conduct agreement operation on the encrypted bill payment scheme, and blocks recorded with the encrypted bill payment scheme are respectively generated after agreement is achieved.
4. The method of claim 1, wherein after the client uploads the transaction carrying the payment credential into the federation chain through the accessed federate node, the method further comprises:
the alliance main node is used for fishing the transaction carrying the payment credential from a transaction pool of the alliance chain;
and the ally main node synchronizes the transaction carrying the payment credentials to the plurality of ally nodes through the consensus mechanism.
5. The method of claim 4, the ally-owned node, after synchronizing the transaction carrying the payment credentials into the plurality of ally-owned nodes via the consensus mechanism, further comprising:
and the ally master node performs verification and cancellation operation on the bill to be paid based on the transaction carrying the payment credential.
6. The method of claim 4 or 5, the ally-owned node, after synchronizing the transaction carrying the payment credentials into the plurality of ally-affiliated nodes via the consensus mechanism, further comprising:
and the target ally member node performs verification and cancellation operation on the bill to be paid according to the transaction carrying the payment credential.
7. The method of claim 1, the federation master node initiating consensus for pending bills in a federation chain, comprising:
the federation master node sending an offer to the plurality of federation members nodes containing bills to be paid;
receiving the proposed allied node to agree on the bill to be paid;
if the number of nodes in the alliance chain is not less than the specified number, the nodes reach a consensus on the bill to be paid, and then alliance nodes reaching the consensus on the bill to be paid generate a block recorded with the bill to be paid;
wherein the specified number is 3f +1, and f is the maximum number of abnormal nodes allowed in the federation chain.
8. The method of claim 1, accessing a client of an allied node for paying the bill to be paid based on the target bill payment scheme, comprising:
the client acquires the bill to be paid through a preset interface provided by the target ally node;
and the client pays the bill to be paid based on the target bill payment scheme.
9. A bill operation system based on a alliance chain comprises an alliance main node, a plurality of alliance member nodes and a client, wherein:
the alliance main node initiates consensus aiming at the bill to be paid in an alliance chain;
the alliance nodes which achieve consensus on the bill to be paid formulate a bill payment scheme based on the bill to be paid respectively, and synchronize the formulated bill payment scheme to other nodes of the alliance chain through a consensus mechanism of the alliance chain;
the method comprises the steps that a client side of an alliance node is accessed, a target bill payment scheme provided by the target alliance node is selected from bill payment schemes formulated by alliance nodes which agree with the bill to be paid, the bill to be paid is paid based on the target bill payment scheme, and a transaction carrying payment credentials is uploaded to the alliance chain through the accessed alliance nodes, wherein the payment credentials are the credentials for paying the bill to be paid based on the target bill payment scheme.
10. The system of claim 9, an allied node agreeing on the bill to be paid to:
encrypting the formulated bill payment scheme to obtain an encrypted bill payment scheme;
synchronizing the encrypted bill payment scheme into other nodes of the federation chain through the consensus mechanism.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010290203.4A CN111539706A (en) | 2020-04-14 | 2020-04-14 | Bill operation method and system based on alliance chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010290203.4A CN111539706A (en) | 2020-04-14 | 2020-04-14 | Bill operation method and system based on alliance chain |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111539706A true CN111539706A (en) | 2020-08-14 |
Family
ID=71975253
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010290203.4A Pending CN111539706A (en) | 2020-04-14 | 2020-04-14 | Bill operation method and system based on alliance chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111539706A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112199412A (en) * | 2020-09-15 | 2021-01-08 | 裴俊伟 | Payment bill processing method based on block chain and block chain bill processing system |
| CN113610640A (en) * | 2021-09-30 | 2021-11-05 | 浙江网商银行股份有限公司 | Event wind control method, device, equipment and storage medium based on alliance chain |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106779661A (en) * | 2017-02-15 | 2017-05-31 | 宇龙计算机通信科技(深圳)有限公司 | The system of selection of mobile payment mode and system |
| CN107103461A (en) * | 2017-05-02 | 2017-08-29 | 广州市智专信息科技有限公司 | A kind of method of payment and corresponding portable terminal, POS |
| CN107705113A (en) * | 2017-09-06 | 2018-02-16 | 浙江大学 | A kind of cross-border inter-bank method of payment of block chain based on Baas frameworks and system |
| CN108009805A (en) * | 2017-10-24 | 2018-05-08 | 广东康美通信息服务有限公司 | A kind of payment processing method, storage medium, device and payment route system |
| CN108985731A (en) * | 2018-07-13 | 2018-12-11 | 北京京东金融科技控股有限公司 | Pay method for routing and device |
| CN109067582A (en) * | 2018-08-03 | 2018-12-21 | 腾讯科技（深圳）有限公司 | A kind of data management system, method and device |
| CN109785096A (en) * | 2018-12-21 | 2019-05-21 | 中信百信银行股份有限公司 | Based on block chain and event driven two clear question processing methods |
| CN110570191A (en) * | 2019-08-27 | 2019-12-13 | 北京艾摩瑞策科技有限公司 | Block chain-based e-commerce data processing method and device |
| CN110599181A (en) * | 2019-09-26 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Data processing method, device and equipment based on block chain and storage medium |
| US20200034818A1 (en) * | 2018-07-24 | 2020-01-30 | Source Ltd | System and method for performing cashless transactions between computing devices |
| WO2020032314A1 (en) * | 2018-08-06 | 2020-02-13 | 주식회사 모아플래닛 | System for processing on/off-line multi-payment on basis of multi-wallet using blockchain |
| US20200074437A1 (en) * | 2018-08-31 | 2020-03-05 | Bleu Tech Enterprises, Llc | Long-range decentralized mobile payment network using bluetooth |
-
2020
- 2020-04-14 CN CN202010290203.4A patent/CN111539706A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106779661A (en) * | 2017-02-15 | 2017-05-31 | 宇龙计算机通信科技(深圳)有限公司 | The system of selection of mobile payment mode and system |
| CN107103461A (en) * | 2017-05-02 | 2017-08-29 | 广州市智专信息科技有限公司 | A kind of method of payment and corresponding portable terminal, POS |
| CN107705113A (en) * | 2017-09-06 | 2018-02-16 | 浙江大学 | A kind of cross-border inter-bank method of payment of block chain based on Baas frameworks and system |
| CN108009805A (en) * | 2017-10-24 | 2018-05-08 | 广东康美通信息服务有限公司 | A kind of payment processing method, storage medium, device and payment route system |
| CN108985731A (en) * | 2018-07-13 | 2018-12-11 | 北京京东金融科技控股有限公司 | Pay method for routing and device |
| US20200034818A1 (en) * | 2018-07-24 | 2020-01-30 | Source Ltd | System and method for performing cashless transactions between computing devices |
| CN109067582A (en) * | 2018-08-03 | 2018-12-21 | 腾讯科技（深圳）有限公司 | A kind of data management system, method and device |
| WO2020032314A1 (en) * | 2018-08-06 | 2020-02-13 | 주식회사 모아플래닛 | System for processing on/off-line multi-payment on basis of multi-wallet using blockchain |
| US20200074437A1 (en) * | 2018-08-31 | 2020-03-05 | Bleu Tech Enterprises, Llc | Long-range decentralized mobile payment network using bluetooth |
| CN109785096A (en) * | 2018-12-21 | 2019-05-21 | 中信百信银行股份有限公司 | Based on block chain and event driven two clear question processing methods |
| CN110570191A (en) * | 2019-08-27 | 2019-12-13 | 北京艾摩瑞策科技有限公司 | Block chain-based e-commerce data processing method and device |
| CN110599181A (en) * | 2019-09-26 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Data processing method, device and equipment based on block chain and storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112199412A (en) * | 2020-09-15 | 2021-01-08 | 裴俊伟 | Payment bill processing method based on block chain and block chain bill processing system |
| CN112199412B (en) * | 2020-09-15 | 2021-07-30 | 财智云享(杭州)数据信息技术有限公司 | Payment bill processing method based on block chain and block chain bill processing system |
| CN113610640A (en) * | 2021-09-30 | 2021-11-05 | 浙江网商银行股份有限公司 | Event wind control method, device, equipment and storage medium based on alliance chain |
| CN113610640B (en) * | 2021-09-30 | 2021-12-28 | 浙江网商银行股份有限公司 | Event wind control method, device, equipment and storage medium based on alliance chain |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10552805B2 (en) | Systems and methods for monitoring referrals | |
| US11238447B2 (en) | Blockchain transactions with ring signatures | |
| JP6763094B2 (en) | Blockchain-based crowdsourcing for map applications | |
| TW202008272A (en) | Block-chain transaction method and device, and electronic device | |
| US11258614B2 (en) | Ring signature-based anonymous transaction | |
| US11824971B2 (en) | Peer-to-peer transmission system with a controlled, double-tier cryptographic key structure | |
| US20200160326A1 (en) | System and method for optimizing data writing to a blockchain | |
| US20140046749A1 (en) | Techniques for monetizing anonymized context | |
| CN110020854B (en) | Data evidence storage method and system based on multiple block chain networks | |
| US11582043B2 (en) | Systems, apparatus and methods for backing up and auditing distributed ledger data within a network and securely without using private keys | |
| CN110569281A (en) | Block chain transaction query method and system | |
| CN110020945B (en) | Data reading method and system based on multiple block chain networks | |
| CN110060153B (en) | Data evidence storage method and system based on multiple block chain networks | |
| AU2018241201A1 (en) | Regulation compliant data integration for financial institutions | |
| EP3230912B1 (en) | Method, apparatus, and computer-readable medium for data exchange | |
| CN111340477A (en) | Service processing method and device, electronic equipment and storage medium | |
| CN111539706A (en) | Bill operation method and system based on alliance chain | |
| US9742744B1 (en) | Documents with location attributes for access and storage | |
| US10979410B1 (en) | Systems and methods for utilizing cryptology with virtual ledgers in support of transactions and agreements | |
| CN109409134B (en) | Transaction data monitoring method and device, storage medium and electronic equipment | |
| CN111861462B (en) | Financial product transaction method and device based on blockchain | |
| JP2021514076A (en) | Content provision method and system based on free charge usage right | |
| US20210144219A1 (en) | Service execution methods and apparatuses | |
| US9984243B1 (en) | Documents with location attributes for access and storage | |
| US20220138760A1 (en) | Dynamic Ledger Address Masking |
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 | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40035491 Country of ref document: HK |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200814 |