CN113610640B

CN113610640B - Event wind control method, device, equipment and storage medium based on alliance chain

Info

Publication number: CN113610640B
Application number: CN202111159709.2A
Authority: CN
Inventors: 秦亚恒
Original assignee: Zhejiang eCommerce Bank Co Ltd
Current assignee: Zhejiang eCommerce Bank Co Ltd
Priority date: 2021-09-30
Filing date: 2021-09-30
Publication date: 2021-12-28
Anticipated expiration: 2041-09-30
Also published as: CN113610640A

Abstract

One embodiment of the present specification provides a federation chain-based event wind control method, apparatus, device, and storage medium, where the method includes: the method comprises the steps of obtaining event information of a to-be-wind-controlled event, wherein an event participant of the to-be-wind-controlled event comprises a target member node in a coalition chain, obtaining a wind control contract corresponding to the to-be-wind-controlled event from the coalition chain according to the event information, issuing the wind control contract corresponding to the to-be-wind-controlled event in the coalition chain in advance by the target member node, and performing wind control processing on the to-be-wind-controlled event according to the wind control contract corresponding to the to-be-wind-controlled event.

Description

Event wind control method, device, equipment and storage medium based on alliance chain

Technical Field

The present document relates to the field of blockchain technologies, and in particular, to a method, an apparatus, a device, and a storage medium for event wind control based on a federation chain.

Background

In many business scenarios, it is desirable to wind business events, for example, to assess credit for a user while lending, and to predict future revenue for an enterprise while financing. The traditional off-line wind control mode is difficult to ensure the authenticity of a wind control result, the wind control result is easy to be tampered by illegal molecules, and when a plurality of parties participate in wind control, how the wind control result is approved by each party is one of difficulties.

Disclosure of Invention

One embodiment of the present specification provides an event wind control method based on a federation chain, where the federation chain includes federation master nodes and member nodes. The method is applied to alliance main nodes. The method comprises the following steps: and acquiring event information of the event to be wind-controlled. The event participants for the wind-controlled event include target member nodes in the federation chain. And acquiring a wind control contract corresponding to the event to be wind controlled from the alliance chain according to the event information. And the target member node issues a wind control contract corresponding to the to-be-wind-controlled event in the alliance chain in advance. And carrying out wind control processing on the event to be wind controlled according to the wind control contract corresponding to the event to be wind controlled.

Another embodiment of the present specification provides an event wind control system based on a federation chain, including federation owner nodes and member nodes. And the target member node in the member nodes is used as an event participant of the event to be subjected to wind control to participate in the event to be subjected to wind control. And issuing a wind control contract corresponding to the event to be controlled in the alliance chain. And the ally master node acquires event information of the event to be controlled by wind. And acquiring a wind control contract corresponding to the event to be wind controlled from the alliance chain according to the event information. And carrying out wind control processing on the event to be wind controlled according to the wind control contract corresponding to the event to be wind controlled.

Another embodiment of the present specification provides a federation chain-based event wind control apparatus. The federation chain includes federation master nodes and member nodes. The device is applied to an alliance master node. The device includes: the first acquisition unit acquires event information of a to-be-wind-controlled event. The event participants for the wind-controlled event include target member nodes in the federation chain. And the second acquisition unit is used for acquiring the wind control contract corresponding to the event to be wind controlled from the alliance chain according to the event information. And the target member node issues a wind control contract corresponding to the to-be-wind-controlled event in the alliance chain in advance. And the wind control processing unit is used for carrying out wind control processing on the event to be wind controlled according to the wind control contract corresponding to the event to be wind controlled.

Another embodiment of the present specification provides a federation chain-based event wind control apparatus, including: a processor and a memory arranged to store computer executable instructions. The computer executable instructions, when executed by the processor, cause the processor to implement the steps of the federation chain-based event wind control method described above.

Another embodiment of the present specification provides a storage medium for storing computer-executable instructions. The computer executable instructions, when executed by the processor, cause the processor to implement the steps of the federation chain-based event wind control method described above.

Drawings

In order to more clearly illustrate the technical solutions in one or more embodiments of the present disclosure, the following briefly introduces the drawings that are needed to be used in the embodiments or the prior art descriptions, obviously, the drawings in the following description are only some embodiments described in the present disclosure, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts;

fig. 1 is a schematic application scenario diagram of an event wind control method based on a federation chain according to an embodiment of the present specification;

FIG. 2 is a flowchart illustrating a federation chain-based event wind control method according to an embodiment of the present disclosure;

FIG. 3 is a flowchart illustrating a federation chain-based event wind control method according to yet another embodiment of the present specification;

FIG. 4 is a flowchart illustrating a federation chain-based event wind control method according to yet another embodiment of the present specification;

FIG. 5 is a schematic diagram illustrating an application scenario of a federation chain-based event wind control method according to yet another embodiment of the present specification;

fig. 6 is a functional diagram of an alliance-owner bank node according to an embodiment of the present disclosure;

fig. 7 is a functional schematic diagram of a affiliate node provided in an embodiment of the present disclosure;

FIG. 8 is a functional diagram of a product side of an alliance bank node according to an embodiment of the present disclosure;

FIG. 9 is a block diagram illustrating a federated chain-based event wind control system according to an embodiment of the present disclosure;

FIG. 10 is a block diagram of a federation chain-based event wind control device according to an embodiment of the present disclosure;

fig. 11 is a schematic structural diagram of an event wind control device based on a federation chain according to an embodiment of the present specification.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.

Fig. 1 is a schematic view of an application scenario of an event wind control method based on a federation chain according to an embodiment of the present specification, where the scenario includes a federation chain including a federation master node and a member node, as shown in fig. 1. The union chain-based event wind control method provided in one or more embodiments of the present specification is applied to a union owner node and executed by the union owner node. Specifically, in the scenario of fig. 1, a target member node in the member nodes participates in a to-be-wind-controlled event as an event participant of the to-be-wind-controlled event, and issues a wind-controlled contract corresponding to the to-be-wind-controlled event in a federation chain, and then, an alliance master node obtains event information of the to-be-wind-controlled event, obtains the wind-controlled contract corresponding to the to-be-wind-controlled event from the federation chain according to the event information, and performs wind-controlled processing on the to-be-wind-controlled event according to the wind-controlled contract corresponding to the to-be-wind-controlled event. The method has the advantages that the wind control processing is carried out based on the alliance chain, the accuracy of the wind control result can be guaranteed by utilizing the characteristic that data in the alliance chain cannot be tampered, and the wind control result can be guaranteed to be approved by each member node by utilizing the characteristic that the data in the alliance chain are real and effective under the condition that a plurality of member nodes are used as event participants to participate in a wind control event to be treated.

Corresponding to the scenario in fig. 1, fig. 2 is a schematic flowchart of an event wind control method based on a federation chain according to an embodiment of the present specification, and as shown in fig. 2, the flowchart includes:

step S202, acquiring event information of a to-be-wind-controlled event; the event participants of the events to be subjected to the wind control comprise target member nodes in the alliance chain;

step S204, acquiring a wind control contract corresponding to the event to be wind controlled from the alliance chain according to the event information; a wind control contract corresponding to a to-be-wind-controlled event is issued in advance in a coalition chain by a target member node;

and step S206, carrying out wind control processing on the event to be wind controlled according to the wind control contract corresponding to the event to be wind controlled.

In this embodiment, the wind control processing is performed based on the federation chain, the accuracy of the wind control result can be ensured by using the characteristic that data in the federation chain cannot be tampered, and the wind control result can be ensured to be approved by each member node by using the characteristic that the data in the federation chain is real and effective under the condition that a plurality of member nodes participate in the wind control event to be treated as event participants.

In one embodiment, the to-be-weathered event is a loan application event of a user, the alliance owner node is a service device for providing a loan product end for the user, the alliance owner node is used for providing the loan product end for the user, for example, providing a loan APP for the user, and the user initiates the loan application event through the loan APP provided by the alliance owner node. The loan application event is participated by at least two target member nodes in the member nodes, the at least two target member nodes are service equipment of a financial institution for providing loan funds, and the funds required by the loan application event are provided by the financial institution to which the at least two target member nodes belong.

After the at least two target member nodes negotiate a loan item and determine the respective provided fund proportion, the at least two target member nodes issue a wind control contract for the loan item in the federation chain, and the wind control contract may include wind control rules for the user applying for loan. Therefore, after the user initiates a loan application event aiming at the loan project based on the APP provided by the alliance owner node, the alliance owner node can acquire the event information of the loan application event, extract the project name of the loan project from the event information, further acquire the wind control contract of the loan project from the alliance chain according to the project name, and perform wind control processing on the loan application event according to the wind control contract of the loan project.

Therefore, the event wind control method based on the alliance chain is applied to the loan scene, the wind control processing can be performed on the loan related events participated by multiple parties, the accuracy of the wind control result is ensured by using the characteristic that data in the alliance chain cannot be tampered, and the wind control result is ensured to be approved by each participant by using the characteristic that the data in the alliance chain is real and effective.

In an embodiment, in step S202, the ally leader node obtains event information of the event to be wind controlled, specifically: after a user initiates a to-be-wind-controlled event through a union main node, event information of the to-be-wind-controlled event is obtained, wherein the event information comprises an event name of an associated event associated with the to-be-wind-controlled event. Further, after the user initiates the event to be wind-controlled through the alliance master node, the event information of the event to be wind-controlled is acquired, which may specifically be: and after a user initiates a to-be-wind-controlled event through a user interaction end of the alliance main node, acquiring event information of the to-be-wind-controlled event.

As mentioned above, the federation master node may provide the user with a product end, which is the user interaction end described above. The product side may be a product side of a loan product. After a user initiates a wind control event to be controlled through a product end provided by a union master node, the union master node acquires event information of the wind control event to be controlled, wherein the event information comprises an event name of an associated event related to the wind control event to be controlled. The related event related to the event to be wind-controlled may be an event which causes the event to be wind-controlled, and the event information of the event to be wind-controlled includes an event name of the related event, and also includes information such as an event name of the event to be wind-controlled.

In one embodiment, the ally node provides a product end of a loan product to a user, and the user initiates a loan application event for a loan item based on the product end, where the loan item is the related event, the item name of the loan item is the event name of the related event, and the loan application event is the event to be controlled. In this embodiment, after a user initiates a loan application event for a loan item through a product end, an alliance node obtains event information of the loan application event, where the event information carries a item name of the loan item and an event name of the loan application event. Because the product end (namely the user interaction end) provided by the allied master node is used for initiating the event to be controlled by wind, and the event to be controlled by wind is correlated with the correlated event, the three of the user interaction end, the event to be controlled by wind and the correlated event can be determined to be corresponding to each other.

In the step S204, according to the event information, a wind control contract corresponding to the event to be wind controlled is obtained from the alliance chain. The wind control contracts are pre-published in the federation chain by the target member nodes. The method comprises the following steps: and searching a wind control contract corresponding to the event name of the associated event in the alliance chain to be used as the wind control contract corresponding to the event to be controlled. The method comprises the steps that wind control contracts corresponding to different associated events are stored in a coalition chain in advance, and the wind control contracts corresponding to the different associated events are issued in the coalition chain by corresponding member nodes in the coalition chain as event participants of the associated events.

As previously described, the associated event may be a loan item, and the pending event may be a loan application event for the loan item. When the loan funds involved in the loan program are provided by the financial institution in which the plurality of member nodes are located, the plurality of member nodes are both event participants for the loan program (event participants for the associated event) and event participants for the loan application event (event participants for the event to be moderated).

And for each loan item, the member nodes serving as event participants of the loan item issue the wind control contracts of the loan item in the alliance chain in advance, so that the wind control contracts corresponding to different loan items are stored in the alliance chain in advance, and the wind control contracts corresponding to different loan items are issued in the alliance chain by using the corresponding member nodes in the alliance chain as event participants of the loan item. When the wind control contract of the loan item is stored in the federation chain, the loan item can be stored in the form of a corresponding relation of the item name of the loan item-the wind control contract. Therefore, in step S204, the wind control contract corresponding to the event name of the associated event obtained in step S202 is searched in the federation chain, and is used as the wind control contract corresponding to the event to be wind controlled. Therefore, in the embodiment, for the loan item and the loan application event, the corresponding wind control contracts are the wind control contracts of the loan item, that is, the wind control contracts corresponding to the loan item and the loan application event are the same, and the wind control contracts may include the wind control rules for the user applying the loan.

In the above description, the related events are used as loan items, and the pending events are used as loan application events for the loan items. It should be emphasized here that the relationship between the associated event and the event to be wind-controlled is: the associated event associated with the event to be windcontrolled is the event that caused the event to be windcontrolled. Therefore, on the basis of following the relationship, the association event and the event to be controlled by wind are not limited to the above examples, for example, the association event may also be a business trip event, the event to be controlled by wind may also be a business trip reimbursement event, the association event may also be a purchase event, and the event to be controlled by wind may be a return event after purchase. The wind control contract corresponding to the to-be-wind-controlled event (i.e. the wind control contract of the associated event) may include a plurality of wind control rules for performing risk control on the user. The wind control contract corresponding to the to-be-wind-controlled event is pre-deployed in the alliance chain in the form of an intelligent contract, and the safety and effectiveness of the wind control contract corresponding to the to-be-wind-controlled event can be guaranteed.

After acquiring the wind control contract corresponding to the to-be-wind-controlled event, in step S206, performing wind control processing on the to-be-wind-controlled event according to the wind control contract corresponding to the to-be-wind-controlled event, where the step may specifically be: and executing each wind control rule included in the wind control contract corresponding to the to-be-wind-controlled event so as to perform wind control processing on the to-be-wind-controlled event.

In one embodiment, according to a wind control contract corresponding to a to-be-wind-controlled event, wind control processing is performed on the to-be-wind-controlled event, which specifically includes: and executing a wind control rule in a wind control contract corresponding to the to-be-wind-controlled event, and calling a corresponding wind control contract according to the wind control rule if the wind control rule indicates that other wind control contracts stored in the alliance chain need to be called in the executing process so as to perform wind control processing on the to-be-wind-controlled event.

Specifically, a plurality of wind control rules are recorded in a wind control contract corresponding to a wind control event, after acquiring the wind control contract corresponding to the wind control event, a master node executes each wind control rule in sequence according to an execution sequence marked among the plurality of wind control rules, and in the execution process, if a certain wind control rule indicates that other wind control contracts stored in a federation chain need to be called, the corresponding wind control contract in the federation chain is called according to the wind control rule so as to perform wind control processing on the wind control event. The called corresponding wind control contract can be issued by a member node in the federation chain, and the member node may or may not be a target member node participating in the event to be subjected to wind control.

For example, 3 wind control rules are recorded in a wind control contract corresponding to a to-be-wind-controlled event, which are a user credit wind control rule, a user repayment capacity wind control rule, and a user consumption capacity wind control rule, respectively, and the execution sequence is as follows: the method comprises the steps that a user credit wind control rule, a user repayment capacity wind control rule and a user consumption capacity wind control rule are carried out, when a union master node executes the user repayment capacity wind control rule, the rule is analyzed, it is determined that a wind control contract which is stored in a alliance chain and used for judging the repayment capacity of a user needs to be called is marked in the rule, and the union master node calls the wind control contract which is stored in the alliance chain and used for judging the repayment capacity of the user according to the mark to execute so as to carry out wind control processing on a wind control event. The wind control contract for judging the repayment capability of the user can be issued by a target member node participating in a to-be-wind-controlled event, can be issued by other member nodes in a alliance chain, and can also be issued by an alliance main node.

The foregoing describes a process of acquiring a wind control contract of a to-be-wind-controlled event and performing wind control processing on the to-be-wind-controlled event. It can be known that the wind contract of the to-be-wind event (i.e. the wind contract of the associated event of the to-be-wind event) is issued in the federation chain by the target member node participating in the to-be-wind event (i.e. the member node participating in the associated event). To ensure that a member node joining a federation chain is a true and reliable node, fig. 3 is a schematic flow diagram of an event wind control method based on a federation chain according to another embodiment of the present specification, and as shown in fig. 3, before acquiring event information of an event to be wind controlled, the method further includes:

step S302, acquiring a join request for requesting a join node to apply for joining a alliance chain;

step S304, according to the joining request, a first request event requesting the joining node to join the alliance chain is examined and approved;

and S306, after the first request event is approved, responding to the join request so as to enable the node requesting to join as a member node to join the alliance chain.

In step S302, the federation master node obtains a join request requesting the join node to apply for joining the federation chain. The joining requesting node is any node that wants to join the federation chain, including but not limited to the target member node described above. In step S304, the federation master node approves the first request event requesting the joining node to join the federation chain according to the joining request. And step S306, after confirming that the first request event is approved, the alliance main node responds to the join request so as to enable the join request node to be used as a member node to join the alliance chain.

In step S304, the federation master node approves the first request event requesting the joining node to join the federation chain according to the joining request, specifically: and voting the first request event according to the joining request, and/or sending a voting notification to the joined member nodes in the alliance chain according to the joining request so as to notify the joined member nodes in the alliance chain to vote for the first request event, and determining that the first request event passes the examination and approval when the voting result meets the corresponding preset requirement.

After receiving the join request, the alliance main node determines a first request event for requesting the join node to join the alliance chain. In one case, the ally leader node votes for the first requested event. In another case, the federation master node sends a voting notification to the member nodes that have joined the federation chain, informing the member nodes that have joined the federation chain to vote for the first requested event. In yet another case, the federation master node both votes for the first requested event and notifies member nodes that have joined the federation chain to vote for the first requested event.

When the voting result meets the corresponding preset requirement, for example, when the alliance master node agrees to request the joining node to join the alliance chain, or more than half of the member nodes already joining the alliance chain agree to request the joining node to join the alliance chain, or when the alliance master node and more than half of the member nodes already joining the alliance chain agree to request the joining node to join the alliance chain, the alliance master node determines that the first request event is approved, and responds to the joining request, so that the joining node is requested to join the alliance chain as the member node.

It can be understood that when any node wants to join the federation chain, it needs to vote based on the flow in fig. 3. It can be seen that through the flow in fig. 3, the security of the member node joining the federation chain can be ensured by voting.

As can be known from the foregoing description, a member node joining a federation chain, such as the target member node mentioned above, may issue a wind-control contract in the federation chain for a participating to-be-controlled event, that is, issue a wind-control contract in the federation chain for a participating associated event, and in order to ensure the legitimacy of the wind-control contract issued by the member node, fig. 4 is a flowchart of an event wind-control method based on a federation chain according to a further embodiment of this specification, as shown in fig. 4, before acquiring, according to event information, a wind-control contract corresponding to the to-be-controlled event from the federation chain, the method further includes:

step S402, acquiring a wind control contract release request of a target member node; the request carries a wind control contract corresponding to the event to be wind controlled;

step S404, according to the wind control contract issuing request, a second request event of the target member node requesting to issue the wind control contract corresponding to the wind control event to be issued is examined and approved;

and step S406, after the second request event passes the approval, responding to the wind control contract issuing request so as to issue the wind control contract corresponding to the to-be-controlled event in the alliance chain.

In the step S402, the franchise master node acquires a wind control contract issuing request of the target member node; the request carries a wind control contract corresponding to the event to be wind controlled. The method can be understood that the wind control contract corresponding to the to-be-controlled event is the wind control contract of the associated event associated with the to-be-controlled event. In the step S404, the ally master node determines that the target member node requests to issue the second request event of the wind control contract corresponding to the event to be controlled according to the wind control contract issue request, and approves the second request event. In step S406, after determining that the second request event passes the approval, the federation master node responds to the wind control contract issuing request to issue the wind control contract corresponding to the event to be controlled by wind in the federation chain.

Step S404, according to the wind control contract issuing request, the second request event of the target member node requesting to issue the wind control contract corresponding to the wind control event to be issued is examined and approved, specifically: issuing a request according to a wind control contract, voting a second request event, and/or issuing the request according to the wind control contract, and sending a voting notification to the member nodes added in the alliance chain so as to notify the member nodes added in the alliance chain to vote for the second request event; and when the voting result meets the corresponding preset requirement, determining that the second request event passes the approval.

After receiving the wind control contract issuing request, the alliance main node determines that the target member node requests to issue a second request event of the wind control contract corresponding to the wind control event to be issued. In one case, the ally leader node votes for the second request event. In another case, the federation master node sends a voting notification to the member nodes that have joined the federation chain, informing the member nodes that have joined the federation chain to vote for the second requested event. In yet another case, the federation master node both votes for the second requested event and notifies member nodes that have joined the federation chain to vote for the second requested event.

When the voting result meets the corresponding preset requirement, for example, when the alliance master node agrees with the target member node to issue the wind control contract corresponding to the wind control event to be issued, or when more than half of the member nodes which have joined the alliance chain agree with the target member node to issue the wind control contract corresponding to the wind control event to be issued, or when the alliance master node and more than half of the member nodes which have joined the alliance chain agree with the target member node to issue the wind control contract corresponding to the wind control event to be issued, the alliance master node determines that the second request event is approved, and responds to the wind control contract issuing request, so that the target member node issues the wind control contract corresponding to the wind control event to be issued in the alliance chain.

It can be understood that when any member node issues a wind control contract for any event to be controlled or any associated event, such as a wind control contract for any loan item, it needs to vote based on the flow in fig. 4. The method is the same as the conventional block chain, and after the member node issues the wind control contract, the wind control contract also needs to be identified by each node in the alliance chain, and the process is not repeated. It can be seen that through the flow in fig. 4, the validity of issuing the wind control contract can be ensured by adopting a voting manner.

In this embodiment, the alliance master node has a trusted Execution environment tee (trusted Execution environment). And the ally main node stores the wind control contract corresponding to the to-be-wind-controlled event in the TEE, and executes the wind control processing operation on the to-be-wind-controlled event according to the wind control contract corresponding to the to-be-wind-controlled event in the TEE, so that the safety of the wind control processing is ensured, and the data used in the wind control processing is made to be invisible.

In this embodiment, each member node also has a trusted execution environment TEE, and the member node sends, in the TEE, a join request requesting to join the federation chain and a wind control contract issuance request requesting to issue a wind control contract of a to-be-controlled event, so as to ensure that a process of joining the federation chain and a process of issuing the contract are authentic and trusted.

Fig. 5 is a schematic view of an application scenario of an event wind control method based on a federation chain according to still another embodiment of the present specification, where the scenario is described by taking a financial scenario as an example, as shown in fig. 5, the scenario includes a federation chain, where a federation chain has a federation owner bank node and an affiliate node, the federation owner bank node is the federation owner node, and the affiliate node is the member node. In fig. 5, the ally owner bank node may implement the node deployment in a cloud node or localized deployment manner, and the affiliated entity node may implement the node deployment in a cloud node or localized deployment manner.

Firstly, an alliance chain is established by an alliance owner bank node, the alliance owner bank node is provided with a product end, and the product end can realize functions of user registration, wind control processing, money release and the like. And then, the joint office node sends a joining application to the alliance owner bank node to request to join the alliance chain, and the alliance owner bank node creates a joining application event according to the joining application. And finally, the alliance owner bank node or the alliance organization node which has joined the alliance chain votes for applying for joining the event so as to permit or not permit the alliance organization node to join the alliance chain. In fig. 5, the franchise bank node and the franchise organization node both have TEE environments, establish a federation chain based on the TEE environments, implement wind control, implement that data is available and invisible, and provide a secure and trusted execution environment.

In fig. 5, if a plurality of affiliated enterprise nodes joining a federation chain participate in a related event together as an event participant of the related event, for example, share funds as a fund provider of a loan item, the plurality of affiliated enterprise nodes also participate in a pending event together as an event participant of a pending event associated with the related event, for example, participate in a loan application event for the loan item. Any one or more of the plurality of affiliated nodes may apply for a controlled contract for the loan item issued in the federation chain, the controlled contract also being a controlled contract for the loan application event. The wind control contract can be jointly researched and determined by the nodes of the plurality of joint organizations, and the contract development language is a language with complete graphic flexibility and supports the realization of various wind control logics.

After any one of the plurality of affiliated entity nodes issues a wind control contract for the loan item in the federation chain, the federation master bank node or the affiliated entity node that has joined the federation chain votes for an event that the application issues the wind control contract to permit or not permit issuance. The voting rules can be in various ways such as ally decision, 51% principle, designated member voting, and the like. The ally decision means that the ally permits issuing to be issued. The 51% principle refers to more than half of the nodes in the federation chain granting publishing. The designated member voting refers to that the designated member can vote. The wind control contract can record contract codes, wind control logic description, contract version, effective time and the like.

After issuing the wind control contract, as shown in fig. 5, the franchise main bank node is provided with a product end, the user can apply for loan at the product end, and after applying for loan, the franchise main bank node obtains a corresponding wind control contract from the alliance chain according to the name of the loan item, so that the wind control is performed on the event that the user applies for loan.

Fig. 6 is a functional schematic diagram of an alliance bank node according to an embodiment of the present disclosure, and as shown in fig. 6, in the scenario of fig. 5, the alliance bank node has the following functions: creating a alliance chain, configuring authority which is the authority of a worker configuring alliance main bank nodes, such as whether contract can be checked or not, voting nodes, freezing the behavior of member nodes in the alliance chain, voting contract voting, and applying for a released wind control contract for the member nodes.

Fig. 7 is a functional schematic diagram of an affiliate organization node provided in an embodiment of the present specification, and as shown in fig. 7, in the scenario of fig. 5, the affiliate organization node has the following functions: joining a alliance chain, applying for joining the alliance chain, voting the nodes applying for joining, issuing a wind control contract, voting the wind control contracts issued by other nodes, inquiring the historical issued wind control contracts, and the like.

Fig. 8 is a functional schematic diagram of a product side of an alliance bank node according to an embodiment of the present disclosure, and as shown in fig. 8, in the scenario of fig. 5, the product side of the alliance bank node has the following functions: user registration, registration of a loan user, wind control processing, the wind control processing and the payment when the user applies for loan, and payment for the loan user.

In summary, by the method provided by the above embodiment, the problem of data privacy during interaction between member nodes can be solved by using the block chain based on the trusted execution environment TEE; an open type wind control contract platform is set up on the alliance chain, and the butt joint cost among all member nodes is reduced; the intelligent contract is used for realizing the wind control rule of each member node, and the characteristics of non-tampering, transaction trace, multi-party consensus, safety encryption and the like of the TEE block chain are utilized to ensure the efficiency, safety and cooperation consensus when the multi-party joint wind control is carried out.

An embodiment of the present specification further provides an event wind control system based on a federation chain, and fig. 9 is a schematic structural diagram of the event wind control system based on a federation chain provided in the embodiment of the present specification, and as shown in fig. 9, the system includes federation master nodes and member nodes; a target member node in the member nodes is used as an event participant of a to-be-wind-controlled event to participate in the to-be-wind-controlled event, and a wind-controlled contract corresponding to the to-be-wind-controlled event is issued in the alliance chain; the ally master node acquires event information of a to-be-wind-controlled event, acquires a wind control contract corresponding to the to-be-wind-controlled event from the alliance chain according to the event information, and performs wind control processing on the to-be-wind-controlled event according to the wind control contract corresponding to the to-be-wind-controlled event.

Optionally, the alliance master node obtains event information of the event to be wind-controlled after a user initiates the event to be wind-controlled through the alliance master node; the event information comprises the event name of the associated event related to the event to be ventilated.

Optionally, the alliance owner node obtains the event information of the event to be wind-controlled after a user initiates the event to be wind-controlled through a user interaction end of the alliance owner node.

Optionally, the alliance main node searches a wind control contract corresponding to the event name of the associated event in the alliance chain, and the wind control contract is used as the wind control contract corresponding to the event to be wind controlled; the method comprises the steps that wind control contracts corresponding to different associated events are stored in the alliance chain in advance, and the wind control contracts corresponding to the different associated events are issued in the alliance chain by corresponding member nodes in the alliance chain as event participants of the associated events.

Optionally, the ally master node executes a wind control rule in a wind control contract corresponding to the event to be wind controlled; in the execution process, if the wind control rule indicates that other wind control contracts stored in the union chain need to be called, calling a corresponding wind control contract according to the wind control rule so as to perform wind control processing on the event to be wind controlled.

Optionally, the alliance master node acquires an adding request of a node requesting to add to the alliance chain before acquiring event information of a to-be-wind-controlled event; according to the joining request, a first request event of the node requesting to join the alliance chain is approved; and after the first request event passes the examination and approval, responding the join request so as to enable the node requesting to join to be used as a member node to join the alliance chain.

Optionally, the alliance master node votes for the first request event according to the join request, and/or sends a voting notification to the member nodes joined in the alliance chain according to the join request, so as to notify the member nodes joined in the alliance chain to vote for the first request event; and when the voting result meets the corresponding preset requirement, determining that the first request event passes the approval.

Optionally, the alliance master node obtains a wind control contract issuing request of the target member node before obtaining a wind control contract corresponding to the event to be wind controlled from the alliance chain according to the event information; the request carries a wind control contract corresponding to the event to be wind controlled; according to the wind control contract issuing request, a second request event of the target member node requesting to issue the wind control contract corresponding to the event to be controlled is examined and approved; and after the second request event passes the approval, responding to the wind control contract issuing request to issue the wind control contract corresponding to the event to be subjected to wind control in the alliance chain.

Optionally, the federation master node issues a request according to the wind control contract and votes for the second request event, and/or sends a voting notification to a member node already joined in the federation chain according to the wind control contract issuance request to notify the member node already joined in the federation chain to vote for the second request event; and when the voting result meets the corresponding preset requirement, determining that the second request event passes the approval.

Optionally, the ally master node has a trusted execution environment TEE; and the ally main node stores the wind control contract corresponding to the event to be wind controlled in the TEE, and executes the wind control contract corresponding to the event to be wind controlled in the TEE to perform wind control processing on the event to be wind controlled.

For a detailed explanation of the present system, reference may be made to the aforementioned explanation of the event-related wind control method, which is not repeated here. The event wind control system based on the federation chain in this embodiment can implement each process of the foregoing event wind control method based on the federation chain, and achieve the same function and effect, which is not repeated here.

An embodiment of the present specification further provides an event wind control device based on a federation chain, where the federation chain includes federation master nodes and member nodes; the apparatus is applied to the alliance master node; fig. 10 is a schematic structural diagram of an event wind control device based on a federation chain according to an embodiment of the present specification, where, as shown in fig. 10, the device includes:

a first obtaining unit 1001 for obtaining event information of a to-be-wind-controlled event; the event participants of the events to be subjected to the wind control comprise target member nodes in the alliance chain;

a second obtaining unit 1002, configured to obtain, according to the event information, a wind control contract corresponding to the to-be-wind-controlled event from the federation chain; the target member node issues a wind control contract corresponding to the event to be wind controlled in the alliance chain in advance;

and a wind control processing unit 1003, performing wind control processing on the event to be wind controlled according to the wind control contract corresponding to the event to be wind controlled.

The event wind control device based on the federation chain in this embodiment can implement each process of the foregoing event wind control method based on the federation chain, and achieve the same function and effect, which is not repeated here.

Fig. 11 is a schematic structural diagram of an event wind control device based on a federation chain according to an embodiment of the present specification, and as shown in fig. 11, the event wind control device based on a federation chain may generate a relatively large difference due to different configurations or performances, and may include one or more processors 1501 and a memory 1502, and one or more applications or data may be stored in the memory 1502. The memory 1502 may be, for example, a transient storage or a persistent storage. The application stored in memory 1502 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a federation chain-based event wind control device. Still further, the processor 1501 may be configured to communicate with the memory 1502 and execute a series of computer-executable instructions in the memory 1502 on a federation chain-based event wind control device. A federation chain-based event wind control apparatus may also include one or more power supplies 1503, one or more wired or wireless network interfaces 1504, one or more input-output interfaces 1505, one or more keyboards 1506, and the like.

In a specific embodiment, the event wind control device based on the alliance chain comprises a processor; and a memory arranged to store computer executable instructions that, when executed by the processor, cause the processor to implement:

acquiring event information of a to-be-wind-controlled event; the event participants of the events to be subjected to the wind control comprise target member nodes in the alliance chain;

acquiring a wind control contract corresponding to the event to be wind controlled from the alliance chain according to the event information; the target member node issues a wind control contract corresponding to the event to be wind controlled in the alliance chain in advance;

and carrying out wind control processing on the event to be wind controlled according to the wind control contract corresponding to the event to be wind controlled.

Another embodiment of the present disclosure further provides a storage medium for storing computer-executable instructions, in a specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, or the like, and the storage medium stores computer-executable instructions, which when executed by a processor, enable the processor to implement the following processes:

The storage medium in this embodiment can implement each process of the foregoing federation chain-based event wind control method embodiment, and achieve the same function and effect, which is not repeated here.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

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.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the various elements may be implemented in the same one or more software and/or hardware implementations in implementing one or more embodiments of the present description.

As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.

Embodiments of the present description are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

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.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

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.

The above description is only an example of the present specification and is not intended to limit the present document. Various modifications and changes may occur to the embodiments described herein, as will be apparent to those skilled in the art. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims

1. An event wind control method based on a alliance chain, wherein the alliance chain comprises alliance main nodes and member nodes; the method is applied to the alliance master node; the method comprises the following steps:

acquiring event information of a to-be-wind-controlled event; the event participants of the events to be subjected to the wind control comprise target member nodes in the alliance chain; the event information comprises an event name of an associated event related to the event to be wind-controlled;

carrying out wind control processing on the event to be wind controlled according to a wind control contract corresponding to the event to be wind controlled;

acquiring a wind control contract corresponding to the event to be wind controlled from the alliance chain according to the event information, wherein the acquiring comprises the following steps:

and searching a wind control contract corresponding to the event name of the associated event in the alliance chain to serve as the wind control contract corresponding to the event to be subjected to wind control.

2. The method of claim 1, wherein obtaining event information for an event to be windcontrolled comprises:

and after the user initiates the event to be controlled by wind through the alliance main node, acquiring the event information of the event to be controlled by wind.

3. The method of claim 2, wherein obtaining event information of the event to be wind-controlled after a user initiates the event to be wind-controlled through the alliance master node comprises:

and after a user initiates the event to be wind controlled through the user interaction end of the alliance main node, acquiring the event information of the event to be wind controlled.

4. The method of claim 3, wherein,

the method comprises the steps that wind control contracts corresponding to different associated events are stored in the alliance chain in advance, and the wind control contracts corresponding to the different associated events are issued in the alliance chain by corresponding member nodes in the alliance chain as event participants of the associated events.

5. The method according to claim 1, wherein performing wind control processing on the event to be wind controlled according to the wind control contract corresponding to the event to be wind controlled comprises:

executing a wind control rule in a wind control contract corresponding to the event to be wind controlled;

in the execution process, if the wind control rule indicates that other wind control contracts stored in the union chain need to be called, calling a corresponding wind control contract according to the wind control rule so as to perform wind control processing on the event to be wind controlled.

6. The method of claim 1, wherein prior to obtaining event information for the event to be windaged, further comprising:

acquiring a joining request for requesting a joining node to apply for joining the alliance chain;

according to the joining request, a first request event of the node requesting to join the alliance chain is approved;

and after the first request event passes the examination and approval, responding the join request so as to enable the node requesting to join to be used as a member node to join the alliance chain.

7. The method of claim 6, wherein approving, according to the join request, a first request event for the requesting joining node to request to join the federation chain comprises:

voting the first request event according to the join request, and/or sending a voting notification to member nodes joined in the alliance chain according to the join request so as to notify the member nodes joined in the alliance chain to vote for the first request event;

and when the voting result meets the corresponding preset requirement, determining that the first request event passes the approval.

8. The method according to claim 1, wherein before acquiring, according to the event information, a wind control contract corresponding to the event to be wind controlled from the federation chain, the method further includes:

acquiring a wind control contract issuing request of the target member node; the request carries a wind control contract corresponding to the event to be wind controlled;

according to the wind control contract issuing request, a second request event of the target member node requesting to issue the wind control contract corresponding to the event to be controlled is examined and approved;

and after the second request event passes the approval, responding to the wind control contract issuing request to issue the wind control contract corresponding to the event to be subjected to wind control in the alliance chain.

9. The method of claim 8, wherein approving, according to the wind control contract issuance request, a second request event for which the target member node requests to issue a wind control contract corresponding to the event to be controlled includes:

voting the second request event according to the release request of the wind control contract, and/or sending a voting notification to the member nodes added in the alliance chain according to the release request of the wind control contract so as to notify the member nodes added in the alliance chain to vote for the second request event;

and when the voting result meets the corresponding preset requirement, determining that the second request event passes the approval.

10. The method of claim 1, wherein the ally-owned node has a Trusted Execution Environment (TEE); and the ally main node stores the wind control contract corresponding to the event to be wind controlled in the TEE, and executes the wind control contract corresponding to the event to be wind controlled in the TEE to perform wind control processing on the event to be wind controlled.

11. An event wind control system based on a alliance chain comprises alliance main nodes and member nodes;

a target member node in the member nodes is used as an event participant of a to-be-wind-controlled event to participate in the to-be-wind-controlled event, and a wind-controlled contract corresponding to the to-be-wind-controlled event is issued in the alliance chain;

the ally master node acquires event information of an event to be wind-controlled, wherein the event information comprises an event name of an associated event related to the event to be wind-controlled; acquiring a wind control contract corresponding to the event to be wind controlled from the alliance chain according to the event information, and performing wind control processing on the event to be wind controlled according to the wind control contract corresponding to the event to be wind controlled;

12. The system of claim 11, wherein the affiliate master node,

13. The system of claim 12, wherein the affiliate master node,

14. The system of claim 13, wherein the federation chain has stored in advance wind control contracts corresponding to different associated events, the wind control contracts corresponding to different associated events being issued in the federation chain by respective member nodes in the federation chain as event participants of the associated events.

15. The system of claim 11, wherein the affiliate master node,

16. The system of claim 11, wherein the affiliate master node,

before acquiring event information of a to-be-wind-controlled event, acquiring a join request of a node requesting to join the alliance chain;

17. The system of claim 16, wherein the affiliate master node,

18. The system of claim 11, wherein the affiliate master node,

acquiring a wind control contract issuing request of the target member node before acquiring a wind control contract corresponding to the to-be-wind-controlled event from the alliance chain according to the event information; the request carries a wind control contract corresponding to the event to be wind controlled;

19. The system of claim 18, wherein the affiliate master node,

20. The system of claim 11, wherein the ally-owned node has a Trusted Execution Environment (TEE); and the ally main node stores the wind control contract corresponding to the event to be wind controlled in the TEE, and executes the wind control contract corresponding to the event to be wind controlled in the TEE to perform wind control processing on the event to be wind controlled.

21. An event wind control device based on a alliance chain, wherein the alliance chain comprises alliance main nodes and member nodes; the apparatus is applied to the alliance master node; the device comprises:

the first acquisition unit is used for acquiring event information of a to-be-wind-controlled event; the event participants of the events to be subjected to the wind control comprise target member nodes in the alliance chain; the event information comprises an event name of an associated event related to the event to be wind-controlled;

the second obtaining unit is used for obtaining a wind control contract corresponding to the to-be-wind-controlled event from the alliance chain according to the event information; the target member node issues a wind control contract corresponding to the event to be wind controlled in the alliance chain in advance;

the wind control processing unit is used for carrying out wind control processing on the event to be wind controlled according to a wind control contract corresponding to the event to be wind controlled;

and the second obtaining unit searches a wind control contract corresponding to the event name of the associated event in the alliance chain, and the wind control contract is used as the wind control contract corresponding to the event to be subjected to wind control.

22. A federation chain-based event wind control apparatus comprising: a processor and a memory arranged to store computer executable instructions which, when executed by the processor, cause the processor to carry out the steps of the method of any of claims 1 to 10 above.

23. A storage medium storing computer-executable instructions which, when executed by a processor, cause the processor to carry out the steps of the method of any one of claims 1 to 10.