Business processing method and apparatus based on alliance chain

Abstract

The application provides a business processing method and device based on a consortium chain. The business processing method based on the consortium chain comprises the following steps: receiving a business processing request sent by a user, and determining a business initiation account of the business processing request; in the case that the business initiation account is a first type account, determining account permission information of the business initiation account and a permission valid time interval corresponding to the account permission information; if the business processing request corresponds to business permission information in the account permission information, and a current time point is within the permission valid time interval, executing the business processing request.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a business processing method based on alliance chain. The present application also relates to a business processing device based on alliance chain, a computing device and a computer readable storage medium. BACKGROUND

[0002] With the continuous development of blockchain technology, the blockchain can be divided into three categories: public chain, private chain and alliance chain based on application scenarios and access control degree. Among them, the alliance chain has certain access threshold, that is, only authorized nodes can participate in network consensus.

[0003] In order to limit abnormal business transactions in the alliance chain, the current method is to deploy gateway nodes by the participants of the alliance chain network, and to realize network interaction on the alliance chain through the gateway to shield abnormal business transactions. However, the method of setting up a gateway will increase the complexity of the alliance chain, and cannot effectively solve the problem of abnormal business transactions.

[0004] Therefore, how to efficiently limit abnormal business transactions on the alliance chain has become a technical problem to be solved by those skilled in the art. SUMMARY

[0005] Therefore, the embodiments of the present application provide a business processing method based on alliance chain. The present application also relates to a business processing device based on alliance chain, a computing device and a computer readable storage medium, to solve the problem that abnormal business transactions on the alliance chain affect the actual function of the alliance chain in the prior art.

[0006] According to a first aspect of the embodiments of the present application, a business processing method based on alliance chain is provided, comprising:

[0007] receiving a business processing request sent by a user, and determining a business initiation account of the business processing request;

[0008] if the business initiation account is a first type account, determining account permission information of the business initiation account and a permission effective time interval corresponding to the account permission information;

[0009] if the account permission information contains business permission information corresponding to the business processing request, and the current time point is within the permission effective time interval, executing the business processing request.

[0010] According to a second aspect of the embodiments of the present application, a business processing device based on alliance chain is provided, comprising:

[0011] The receiving module is configured to receive a service processing request sent by a user and determine a service initiation account of the service processing request.

[0012] The determining module is configured to, in a case where the service initiation account is a first type account, determine account permission information of the service initiation account and a permission valid time interval corresponding to the account permission information.

[0013] The executing module is configured to, if the account permission information contains service permission information corresponding to the service processing request and a current time point is within the permission valid time interval, execute the service processing request.

[0014] According to a third aspect of an embodiment of the present application, a computing device is provided, including a memory, a processor, and computer instructions stored in the memory and executable on the processor, and the processor implements the steps of the service processing method based on the alliance chain when executing the computer instructions.

[0015] According to a fourth aspect of an embodiment of the present application, a computer readable storage medium is provided, which stores computer instructions, and the computer instructions implement the steps of the service processing method based on the alliance chain when executed by a processor.

[0016] The service processing method based on the alliance chain provided by the present application receives a service processing request sent by a user and determines a service initiation account of the service processing request; in a case where the service initiation account is a first type account, determines account permission information of the service initiation account and a permission valid time interval corresponding to the account permission information; and if the account permission information contains service permission information corresponding to the service processing request and a current time point is within the permission valid time interval, executes the service processing request.

[0017] An embodiment of the present application realizes the verification of service permission information of a service initiation account and a permission valid time interval corresponding to the service permission information, thereby limiting abnormal business transactions of alliance chain accounts and improving the rationality of service processing on the alliance chain. BRIEF DESCRIPTION OF DRAWINGS

[0018] Figure 1 is a flowchart of a service processing method based on the alliance chain provided by an embodiment of the present application;

[0019] Figure 2 is a processing flowchart of a service processing method based on the alliance chain applied to a leasing business provided by an embodiment of the present application;

[0020] Figure 3 is a structural schematic diagram of a service processing device based on the alliance chain provided by an embodiment of the present application;

[0021] Figure 4 is a structural block diagram of a computing device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0022] In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. However, the present application can be practiced without the specific details, and it is understood that the present application is not limited to the embodiments described herein. In other instances, well-known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present application.

[0023] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of one or more embodiments of the present application. As used in one or more embodiments of the present application and the accompanying claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0024] It will be understood that, although the terms first, second, etc. can be used herein to describe various information, these terms are not intended to denote a temporal sequence, but are used only to distinguish one piece of information from another. For example, without departing from the scope of one or more embodiments of the present application, first can be termed second, and similarly, second can be termed first. Depending on the context, the word "if' as used herein can be interpreted to mean "when" or "in response to determining."

[0025] First, the noun terms related to one or more embodiments of the present application are explained.

[0026] Consortium chain: A blockchain that is only accessible to members of a certain group and limited third parties, and a plurality of pre-selected nodes are designated as accountants inside, and the generation of each block is determined by all pre-selected nodes.

[0027] Proposal: A way of consortium chain governance, through the initiation of a proposal, on-chain voting, reaching community consensus, to achieve the purpose of modifying the parameters of the blockchain network.

[0028] Transaction: In a broad sense, transaction refers to all on-chain activities, including transfer / contract invocation / proposal voting, etc.

[0029] Blockchain can be divided into public chain, consortium chain and private chain in terms of application scenarios and access control degree. Among them, the node access of consortium chain network has a certain threshold, only authorized nodes can participate in network consensus. Early consortium chain does not contain token mechanism, and the blockchain network has no incentive measures for nodes to package transactions. Such architecture leads to insufficient motivation for nodes to package more transactions, therefore, many consortium chains have also introduced incentive mechanisms, that is, a certain token reward is given to the nodes that package transactions and blockchains. The token mechanism in consortium chain introduces new compliance risks, how to limit token transactions between users, prevent value speculation, and return token value to the function of blockchain network itself, become technical problems to be solved.

[0030] The current common solution is that the participants of the consortium chain network deploy their own gateway nodes, and the blockchain nodes are not directly exposed to the outside. Users interact with the blockchain network through the gateway layer, and transactions are shielded in the gateway layer. For the token mechanism under the existing consortium chain network, all on-chain accounts can participate in token circulation without any restrictions, which leads to users privately trading to third-party accounts after obtaining a certain token, affecting the use of consortium chain.

[0031] However, the current solution of limiting token circulation through the gateway layer has certain limitations. Consortium chain network participants belong to different enterprises or institutions, which requires each participant in the network to deploy their own gateway nodes to expose services to the outside, making the topology of the blockchain network more complex. If there is a subsequent requirement for blockchain nodes to be directly exposed to the outside, it cannot meet the requirements.

[0032] The solution of the present application places the management of all account rights on the consortium chain, directly controls the capabilities and rights of on-chain accounts from the source, and does not need to shield transaction actions through a preposed gateway node. Even if the blockchain node is directly exposed to the outside, the user's account has no right to initiate transaction operations through the node.

[0033] In the present application, a business processing method based on a consortium chain is provided. The present application also relates to a business processing device based on a consortium chain, a computing device, and a computer readable storage medium, which are described in detail one by one in the following embodiments.

[0034] Figure 1 A flowchart of a business processing method based on a consortium chain according to an embodiment of the present application is shown, which specifically includes the following steps:

[0035] Step 102: receiving a business processing request sent by a user, and determining a business initiation account of the business processing request.

[0036] In actual application, the consortium chain refers to a blockchain used by multiple organizations; the consortium chain can include multiple consortium nodes, wherein the consortium node refers to a terminal device such as a server in the consortium chain network, and can be used to receive a business processing request sent by a user; each consortium node has a corresponding organization, for example, consortium node 1 on the consortium chain corresponds to an enterprise, consortium node 2 on the consortium chain corresponds to a company, and so on. The business processing request refers to a request sent by a user based on a client configured with a consortium chain account.

[0037] The business initiation account refers to an account that sends a business processing request, wherein the business can be a transaction such as leasing, purchasing, and transferring, which can be processed based on the consortium chain; in actual application, a user can send a business processing request based on a client configured with a consortium chain account, and take the consortium chain account that sends the business processing request as the business initiation account; for example, user A sends a business processing request through a client configured with consortium chain account H, and takes consortium chain account H as the business initiation account; the user initiating the business processing request refers to signing the business content with a consortium chain account private key, and broadcasting the signed message to the target consortium node on the consortium chain, and the target consortium node broadcasts the business content to each consortium node on the consortium chain through the consortium chain network.

[0038] Specifically, the permission verification module in the consortium chain receives a business processing request sent by a user to the consortium chain, and analyzes the business processing request to determine the business initiation account and the business receiving account, specifically, determines the business initiation account and the business receiving account corresponding to the business processing request according to the account included in the business processing request.

[0039] For example, the permission verification module of consortium chain K receives a business processing request sent by user G to the consortium chain; analyzes the business processing request to obtain the consortium chain account identifier, and determines the business initiation account A and the business receiving account B on the consortium chain K based on the consortium chain account identifier.

[0040] By receiving the business processing request and determining the business initiation account based on the business processing request, the permission of the business initiation account can be determined subsequently, and the restriction on the business flow in the consortium chain is realized.

[0041] Step 104: In the case that the business initiation account is a first type account, determining the account permission information of the business initiation account and the permission effective time interval corresponding to the account permission information.

[0042] In actual application, in order to enable different consortium chain accounts in the consortium chain to have different processing permissions, different account types such as a management account type and a normal account type can be set in the consortium chain; the account corresponding to the consortium chain node can be created as a second type account, or the first type account used by the user, and the first type account and the second type account are both consortium chain accounts; whether the consortium chain account needs to be verified in terms of permission can be determined based on the account type.

[0043] The first type account refers to a consortium chain account that needs to be verified in terms of account permission; in actual application, the consortium chain account is configured with an account type, that is, the consortium chain can correspond to a first type account and a second type account; in a case where it is determined that the business initiating account is a first type account, account permission information and a permission valid time interval of the business initiating account can be obtained, for subsequent determination of whether the business initiating account can execute a business request; the account permission information refers to permission information configured for the account, such as account permission information of account A being permission 1, permission 2, and permission 3; the permission valid time interval refers to a time interval in which the account permission information is valid, such as the permission valid time interval being 3:00-5:00 on March 22, so that in a case where the current time point is 4:00 on March 22, the account permission information is in a valid state.

[0044] Specifically, after determining the business initiating account, the account type of the business initiating account is determined; for example, the account type of the business initiating account can be determined through the account identifier of the business initiating account, specifically, the account type can be determined through the account name of the account, the account name of account A being user-234-1, and the account name of account B being user-345-2, so that it can be determined that the account with the suffix "-1", that is, account A, is an account that needs to be verified in terms of permission, and it can be determined that the account with the suffix "-2", that is, account B, is an account that does not need to be verified in terms of permission.

[0045] In a case where it is determined that the business initiating account is an account that needs to be verified in terms of permission, that is, a first type account, the account permission information of the business initiating account and the permission valid time interval corresponding to the account permission information are obtained.

[0046] For example, it is determined that the business initiating account corresponding to the business initiating node is account G; the account type of account G is determined, and in a case where it is determined that account G is a first type account, the account permission information of account G and the permission valid time interval corresponding to the account permission information are obtained.

[0047] By determining the account permission information and the permission valid time interval of the business initiating account in a case where the account type of the business initiating account is determined to be an account type that needs to be verified in terms of permission, the business initiating account can be verified in terms of permission subsequently.

[0048] Step 106: if the account permission information contains the business permission information corresponding to the business processing request, and the current time point is within the permission valid time interval, execute the business processing request.

[0049] The business permission information refers to the permission information corresponding to the business request. For example, if the business processing request is a transfer from the alliance chain account M to the alliance chain account N, the business permission information can be the transfer permission information. By judging whether the account permission information contains the business permission information, it is determined whether the business initiating account has the permission to process the business processing request. For example, if the account permission information is the information reading permission and the transfer permission, and the business permission information corresponding to the business processing request is the transfer permission, it is determined that the business initiating account has the permission to execute the business processing request.

[0050] However, in order to further verify the permission of the account, if it is determined that the account permission information contains the business permission, it is further determined whether the account permission information is within the permission valid time interval.

[0051] The current time point refers to the time point of processing the business processing request. By judging whether the current time point is within the permission valid time interval, it is determined whether the account permission information is valid. For example, if it is determined that the current time point is 3:30, and the permission valid time interval is 2:00-5:00, it is determined that the account permission information of the business initiating account is valid.

[0052] Further, the first organization of the alliance chain refers to one of the organizations joining the alliance chain, such as an enterprise, a trade union, etc. The second organization of the alliance chain refers to one of the organizations joining the alliance chain different from the first organization of the alliance chain, such as an enterprise, a trade union, etc. The first organization of the alliance chain and the second organization of the alliance chain refer to two different organizations having business transactions, for example, the first organization of the alliance chain is enterprise 1, the second organization of the alliance chain is enterprise 2, and there is a business transaction between enterprise 1 and enterprise 2.

[0053] The business initiating account in the first organization of the alliance chain can send a business processing request to the business receiving account in the second organization of the alliance chain, thereby realizing the business transaction between the business initiating account and the business receiving account.

[0054] The business receiving account in the second organization of the alliance chain is determined based on the business processing request. For example, the alliance chain account identifier is carried in the business processing request, and based on the alliance chain account identifier, the business initiating account of the first organization of the alliance chain and the business receiving account of the second organization of the alliance chain can be determined. Through the alliance chain, the alliance chain account corresponding to the first organization of the alliance chain and the alliance chain account corresponding to the second organization of the alliance chain can be realized.

[0055] Specifically, after determining the account permission information of the business initiating account and the permission valid time interval corresponding to the account permission information, it is first determined whether the business permission information corresponding to the business processing request is contained in the account permission information; in the case where it is determined that the business permission information corresponding to the business processing request is contained in the account permission information, the current time point is determined, and it is determined whether the current time point is within the permission valid time interval; if yes, it is determined that the account permission information is currently valid; at this point, it can be determined that the business initiating account has the permission to execute the business processing request, that is, the alliance chain node can execute the business processing request between the business initiating account and the business receiving account.

[0056] It should be noted that, in order to further verify the business permission, in addition to the above-mentioned permission verification of the business initiating account, the permission verification of the business receiving account can also be performed at the same time, specifically whether the business permission information corresponding to the business processing request is contained in the account permission information of the business receiving account, and whether the current time point is within the permission time interval of the business receiving account; in the case where both parties pass the permission verification, it can be determined that the business processing request is executed normally, and if any party fails to pass the permission verification, it is determined that the business processing request fails to execute.

[0057] The above is the case where the business initiating account is a first type account, and the case where the business initiating account is a second type account is described below:

[0058] Specifically, in the case where the business initiating account is a second type account, the business processing request is executed.

[0059] The second type account refers to an alliance chain account that does not need to be subjected to account permission verification, for example, the second type account can be an account containing all execution permissions in the alliance chain or an account containing more permissions; this type of account can be executed without permission verification.

[0060] For example, the second type account is a management account A of a first organization of the alliance chain and a management account B of a second organization of the alliance chain set when the alliance chain is created.

[0061] After determining that the business initiating account passes the permission verification, the account attribute value in the business initiating account needs to be determined, so as to determine whether the business processing request can be executed, specifically, the method for executing the business processing request can include:

[0062] determining the account attribute value of the business initiating account and the business attribute value in the business processing request;

[0063] In the case where the account attribute value is greater than or equal to the business attribute value, the business receiving account is determined based on the business processing request, and the business processing request is executed.

[0064] wherein, the account attribute value refers to a value related to the business initiating account, such as the total number of account businesses, the remaining number of account businesses, and the like; the business attribute value refers to an attribute value contained in the business processing request and required to be met by the business processing request; in the case that the account attribute value is greater than or equal to the business attribute value, it indicates that the account attribute value can meet the execution condition of the business processing request; for example, the business processing request is to transfer 300 from the business initiating account A to the business receiving account B, if the current balance of the business initiating account A is 500, that is, the account attribute value 500 is greater than the business attribute value 300, it is determined that the business processing request can be executed.

[0065] In the case that the account attribute value is greater than or equal to the business attribute value, the business initiating account and the business receiving account can be determined based on the business processing request, and the business processing request can be executed by the alliance nodes in the alliance chain.

[0066] In the case that the account attribute value is less than the business attribute value, it is determined that the business processing request fails to execute.

[0067] For example, the business processing request is to transfer 500 from the business initiating account A to the business receiving account B, if the current balance of the business initiating account A is 100, that is, the account attribute value 100 is less than the business attribute value 500, it is determined that the business processing request fails to execute.

[0068] Further, in the case that the business initiating account does not contain the permission to execute the business processing request, the business initiating account can initiate a permission allocation request to the second type account, requesting the second type account to allocate the required permission to the business initiating account. Specifically, the method can be:

[0069] In the case that the account permission information does not contain the business permission information corresponding to the business processing request, a permission allocation request is sent to the second type account;

[0070] If the second type account does not configure the permission to the business initiating account based on the permission allocation request, it is determined that the business processing request fails to execute.

[0071] wherein, the permission allocation request refers to a request for allocating permission sent to an account with permission allocation capability; after the business initiating account sends the permission allocation request, if the second type account can configure the permission to the alliance chain account after the request, if the request is not passed, it can be determined that the business processing request fails to execute.

[0072] For example, the permission of the consortium chain account A is checked, and it is determined that the consortium chain account A does not contain the transfer permission required by the business processing request. The consortium chain account A can send a permission allocation request to the consortium chain account B of the second account type to request to add the transfer permission to the consortium chain account A. If the consortium chain account B does not pass the permission allocation request, it is determined that the business processing request fails.

[0073] In addition, in the case that the permission valid time interval corresponding to the business permission information does not meet the current time point, a permission valid time adjustment request can also be sent to the consortium chain account of the second type account. Specifically, the method can be:

[0074] In the case that the account permission information contains the business permission information corresponding to the business processing request, and the current time point is not within the permission valid time, a permission valid time adjustment request is sent to the second type account;

[0075] If the second type account does not adjust the permission valid time interval for the business initiation account based on the permission valid time adjustment request, it is determined that the business processing request fails.

[0076] The permission valid time adjustment request is an adjustment request for the permission valid time interval sent to the consortium chain account with the permission valid time interval adjustment capability. After the business initiation account sends the valid time adjustment request, if the second type account passes the request, the permission valid time interval of the consortium chain account can be adjusted. If the request is not passed, it is determined that the business processing request fails.

[0077] For example, the permission of the consortium chain account M is checked, and it is determined that the consortium chain account M contains the transfer permission required by the business processing request, but the current time point is within the permission valid time interval corresponding to the transfer permission. The consortium chain account M can send a permission valid time adjustment request to the second type account N. The permission valid time adjustment request is specifically an adjustment request for the permission valid time interval corresponding to the transfer permission of the consortium chain account M. If the consortium chain account N does not pass the permission valid time adjustment request, it is determined that the business processing request fails.

[0078] In addition to the above, the second type account can be set when the consortium chain is created. Based on actual needs, the first type account can be upgraded to the second type account. The specific upgrading method can include:

[0079] An account upgrade request is received from a voting initiation account. The account upgrade request contains a to-be-upgraded account identifier. The voting initiation account is a second type account, and the to-be-upgraded account corresponding to the to-be-upgraded account identifier is a first type account.

[0080] counting voting information fed back by each second-type account in the alliance chain for the account upgrade request to obtain a voting attribute value;

[0081] upgrading the to-be-upgraded account to a second-type account if the voting attribute value is greater than a voting attribute threshold.

[0082] The account upgrade request refers to a request for upgrading an account type. The account upgrade request contains a to-be-upgraded account identifier, such as an account identifier M corresponding to a first-type account. The voting initiator account refers to an alliance chain account that initiates voting. In actual applications, it can be limited that only second-type accounts can issue account upgrade requests, thereby facilitating the processing of voting matters.

[0083] counting voting information fed back by alliance chain accounts on the alliance chain according to the account upgrade request, wherein the voting information refers to opinion information of the alliance chain accounts for the upgrade proposal, such as agreeing to upgrade or disagreeing to upgrade; the account upgrade request can be synchronized to second-type accounts on the alliance chain, that is, the voting information of the second-type accounts on the alliance chain needs to be counted to obtain a voting result.

[0084] In actual applications, if the number of alliance chain accounts corresponding to the alliance chain can be determined, the voting information fed back by each alliance chain account for the account upgrade request can also be obtained to obtain voting attribute information for determining a voting result.

[0085] The counting of the voting information can determine a voting attribute value, for example, the accounts agreeing to upgrade account for 3 / 4. The voting attribute threshold refers to the minimum value of the voting attribute value. If the voting attribute value is less than or equal to the voting attribute threshold, it is considered that the voting proposal fails. If the voting attribute value is greater than the voting attribute threshold, it is determined that the voting passes, that is, the alliance chain can upgrade the first-type account to the second-type account.

[0086] For example, a voting request is initiated by a second-type account, wherein the voting request contains a voting proposal for upgrading a first-type alliance chain account A. The voting result data table is obtained by counting voting results fed back by each second-type account in the alliance chain based on the voting request. The voting attribute value is calculated based on the voting result data table, for example, the data table contains 3 pieces of voting information agreeing to upgrade and 1 piece of voting information disagreeing to upgrade, and the proportion of accounts agreeing to upgrade is calculated as 3 / 4, that is, the voting attribute value is 3 / 4.

[0087] Before a business initiator account initiates a business processing request, an alliance chain needs to be created based on a demand. The method for creating the alliance chain can include:

[0088] receiving an alliance chain creation request generated based on creation demands of a first organization of the alliance chain and a second organization of the alliance chain;

[0089] create the consortium chain in response to the consortium chain creation request, and configure the consortium chain accounts of the consortium chain first organization and the consortium chain second organization as second-type accounts.

[0090] The creation requirement is a requirement for creating a consortium chain. In actual application, a consortium chain can be established based on the consortium chain creation requirements of multiple organizations. For example, there are more business transactions between enterprise 1 and company 2. In order to facilitate data synchronization, a consortium chain can be created based on the consortium chain creation requirements of enterprise 1 and company 2. The consortium chain creation request refers to a request for creating a consortium chain. The specific process of creating a consortium chain is not limited in the application.

[0091] The consortium chain is created based on the consortium chain creation request, which includes creating a consortium chain node of the consortium chain first organization and creating a consortium chain node of the consortium chain second organization. The consortium chain accounts corresponding to the consortium chain nodes in the consortium chain first organization and the consortium chain second organization can be configured as second-type accounts. For example, the consortium chain accounts of the consortium chain first organization are set as management accounts.

[0092] For example, a consortium chain is created based on the consortium chain creation requirements of enterprise 1 and enterprise 2. The consortium chain accounts of enterprise 1 in the consortium chain are configured as second-type accounts. At this time, enterprise 1 only contains one consortium chain account. The consortium chain accounts added subsequently can be configured as first-type accounts. The first-type accounts can also be upgraded to first-type accounts through on-chain voting. The consortium chain accounts of enterprise 2 in the consortium chain are configured as second-type accounts. At this time, enterprise 2 only contains one consortium chain account. First-type accounts can also be configured subsequently.

[0093] After the creation of the consortium chain, consortium chain accounts can also be created for new organizations in the consortium chain. That is, after the consortium chain is created in response to the consortium chain creation request and the consortium chain accounts of the consortium chain first organization and the consortium chain second organization are configured as second-type accounts, the following steps can also be included:

[0094] receiving a consortium chain joining request of a consortium chain third organization;

[0095] creating a first-type account of the consortium chain third organization in the consortium chain in response to the consortium chain joining request, and upgrading the first-type account to a second-type account.

[0096] Specifically, the third organization of the consortium chain refers to one of the organizations joining the consortium chain different from the first organization of the consortium chain and the second organization of the consortium chain; according to the consortium chain joining request, a first type account is created, and an account upgrade request is initiated by the second type account of the first organization of the consortium chain or the second organization of the consortium chain to upgrade the first type account to a second type account; and then the consortium node of the third organization of the consortium chain is deployed in the consortium chain, and the second type account of the third organization of the consortium chain is added to the consortium chain.

[0097] For example, the consortium chain is created by enterprise 1 and enterprise 2, and after the creation of the consortium chain, enterprise 3 also needs to join the consortium chain, and the consortium chain account of enterprise 3 is created, and the default created account is a first type account; the first type account created by enterprise 1 and enterprise 2 is upgraded to a second type account, and the consortium node corresponding to enterprise 3 is deployed on the consortium chain, and the created second type account is added to the consortium chain.

[0098] In actual application, it can be known from the above steps that the consortium chain account of the third organization of the consortium chain can be a first type account or a second type account, and in the case of the first type account of the consortium chain account, that is, an account containing less permission information or no permission information; after receiving a business processing request, the first type consortium chain account of the third organization of the consortium chain can not be able to execute the business processing request, and therefore a permission allocation request can be sent to the second type account in the consortium chain, and specifically, the method for requesting permission allocation can include:

[0099] receiving a permission allocation request sent by the first type account of the third organization of the consortium chain, wherein the permission allocation request contains a target permission identifier;

[0100] In response to the permission allocation request, the target permission corresponding to the target permission identifier and the permission effective time interval corresponding to the target permission are allocated to the first type account of the third organization of the consortium chain by the second type account.

[0101] The permission allocation request refers to a request for allocating permissions to the first type consortium chain account; the target permission identifier is contained in the permission allocation request, and the permissions allocated by the permission allocation request can be determined based on the target permission identifier.

[0102] The second type account to which the permissions can be allocated in the consortium chain can be determined based on the permission allocation request; or the consortium chain account identifier is contained in the permission allocation request, and the second type consortium chain account to which the permissions can be allocated is directly determined based on the consortium chain account identifier.

[0103] After determining the alliance chain account to which the assignable right belongs, the alliance chain account allocates the target right corresponding to the target right identifier and the right validity time interval corresponding to the target right to the alliance chain account in the alliance chain third organization which initiates the right allocation request.

[0104] For example, after receiving the business processing request, the alliance chain account D of the alliance chain third organization determines that the account right corresponding to the alliance chain account D does not contain the transfer right, and then the alliance chain account D sends a right allocation request to the alliance chain account G which can allocate rights, wherein the right allocation request contains the transfer right identifier; the alliance chain account G allocates the transfer right and the right validity time interval corresponding to the transfer right, i.e., “from March 2 to March 5”, to the alliance chain account D based on the right allocation request.

[0105] In actual application, the account in the alliance chain third organization can also be upgraded, and the specific method can include:

[0106] receiving an account upgrade request sent by a second type account of the alliance chain third organization, and determining a to-be-upgraded account based on the account upgrade request;

[0107] counting the voting information fed back by each second type account in the alliance chain for the account upgrade request to obtain a voting attribute value;

[0108] upgrading the to-be-upgraded account to a second type account in the case where the voting attribute value is greater than a voting attribute threshold.

[0109] Specifically, the account upgrade request can be sent by a second type account in the alliance chain third organization, or an upgrade application can be sent by a first type account in the alliance chain third organization to a second type account, and then the second type account sends an account upgrade request; the to-be-upgraded account is determined according to the account identifier contained in the account upgrade request; the voting attribute value is calculated based on the voting information fed back by the second type account in the alliance chain, and the to-be-upgraded account in the alliance chain third organization is upgraded to a second type account in the case where the voting attribute value is greater than a voting attribute threshold, wherein the to-be-upgraded account is a first type account.

[0110] In addition, the second type account can adjust the right information of the first type alliance chain account in addition to allocating rights to the first type alliance chain account. Specifically, the method can include:

[0111] the second type account receives a right adjustment request, and determines a to-be-adjusted account in the alliance chain based on the right adjustment request;

[0112] adjusting the account right information and / or the right validity time interval of the to-be-adjusted account according to the right adjustment information in the right adjustment request.

[0113] The permission adjustment request refers to a request for adjusting the permission of the alliance chain account; the account to be adjusted refers to an account that needs to be adjusted in permission; and the permission adjustment information refers to adjustment information for adjusting the account to be adjusted.

[0114] The second type of account, i.e., the alliance chain account with permission adjustment capability, after receiving the permission adjustment request, determines the account to be adjusted according to the account identifier in the permission adjustment request; in actual application, a plurality of accounts to be adjusted can be determined in the alliance chain, i.e., the permission adjustment request can contain a plurality of account identifiers; and the determined account to be adjusted is adjusted based on the permission adjustment information parsed in the permission adjustment request, such as closing the permission of each account to be adjusted, modifying the permission of the account to be adjusted, increasing the permission validity time interval, etc.

[0115] For example, after the second type of account A receives the permission adjustment request, the permission adjustment request is parsed to determine the account to be adjusted H and the permission adjustment information; based on the permission adjustment information "close the transfer permission, and increase the validity time of the view permission by 3 hours", the transfer permission of the account to be adjusted H is closed, and the permission validity time interval "3:00 to 5:00" corresponding to the view permission is modified to "3:00 to 8:00".

[0116] The business processing method based on the alliance chain provided in the present application receives a business processing request sent by a user and determines a business initiator account of the business processing request; in the case that the business initiator account is a first type of account, the account permission information of the business initiator account and the permission validity time interval corresponding to the account permission information are determined; if the account permission information contains the business permission information corresponding to the business processing request, and the current time point is within the permission validity time interval, the business processing request is executed. By checking the business permission information of the business initiator account and the permission validity time interval corresponding to the business permission information, the abnormal transactions of the alliance chain accounts are limited, and the rationality of the business processing is improved.

[0117] The following will be described in conjunction with the accompanying Figure 2 The business processing method based on the alliance chain provided in the present application is applied to the leasing business as an example to further illustrate the business processing method based on the alliance chain. Among them, Figure 2 A processing flowchart of a business processing method based on an alliance chain applied to a leasing business is shown, which specifically includes the following steps:

[0118] Step 202: The alliance chain management account G allocates account permissions for the ordinary account A and the ordinary account B based on a permission allocation request.

[0119] Specifically, the management account in the present example is a second type account, i.e., an account that does not need to be verified for permission before executing a service processing request; and the common account is a first type account, i.e., an account that needs to be verified for permission before executing a service processing request.

[0120] The management account G can assign account permissions for the common account A and the common account B based on a permission assignment request, such as assigning the common account A a lease resource assignment permission and a permission validity time interval 3 / 4-3 / 5 for the lease resource assignment permission.

[0121] Step 204: The common account A sends a service processing request.

[0122] Specifically, the service processing request is to assign the common account A a lease resource with a quantity of 300 to the common account B.

[0123] Step 206: Determine whether the common account A is of the common account type, if yes, execute step 208; if no, execute step 210.

[0124] Specifically, the account type can be determined based on the account identifier of the account.

[0125] Step 208: Determine whether the common account A has a service processing permission, if yes, execute step 212; if no, execute step 214.

[0126] Specifically, determine whether the service processing permission corresponding to the service processing request is contained in all account permission information of the common account A, if yes, execute step 212; if no, execute step 214.

[0127] Step 210: Determine that the account type is of the management account type. After executing step 210, continue to execute step 216.

[0128] Step 212: Determine whether the current time point is within the permission validity time interval, if yes, execute step 216; if no, execute step 214.

[0129] Specifically, determine whether the current time point is within the permission validity time interval corresponding to the service processing permission; if yes, execute step 216; if no, execute step 214.

[0130] Step 214: Determine that the service processing request fails.

[0131] Step 216: Determine whether the account attribute value is greater than the lease resource attribute value, if yes, execute step 218; if no, execute step 214.

[0132] Step 218: Determine that the service processing request is executed successfully.

[0133] Specifically, it is determined that the business processing request can be executed by the normal account A and the normal account B, that is, the normal account A can assign the lease resource with a quantity of 300 to the normal account B.

[0134] In addition, in actual application, the normal account B can also assign the lease resource to the normal account A, and the method of verifying the permission of the normal account B is consistent with the method of verifying the permission of the normal account A.

[0135] The business processing method based on the alliance chain applied to the lease business in the embodiment receives a business processing request sent by a user and determines a business initiating account of the business processing request. In a case where the business initiating account is a first type account, account permission information of the business initiating account and a permission valid time interval corresponding to the account permission information are determined. If the account permission information contains business processing permission information corresponding to the business processing request and a current time point is within the permission valid time interval, the business processing request is executed. By verifying the business permission information of the business initiating account and the permission valid time interval corresponding to the business permission information, abnormal business transactions of the alliance chain account are limited, and the rationality of business processing is improved.

[0136] Corresponding to the method embodiment, the application also provides a business processing device based on an alliance chain, Figure 3 A structure schematic diagram of a business processing device based on an alliance chain is shown. Figure 3 As shown in the figure, the device comprises:

[0137] The receiving module 302 is configured to receive a business processing request sent by a user and determine a business initiating account of the business processing request.

[0138] The determining module 304 is configured to, in a case where the business initiating account is a first type account, determine account permission information of the business initiating account and a permission valid time interval corresponding to the account permission information.

[0139] The executing module 306 is configured to, if the account permission information contains business permission information corresponding to the business processing request and a current time point is within the permission valid time interval, execute the business processing request.

[0140] Optionally, the device further comprises an executing submodule configured to:

[0141] execute the business processing request in a case where the business initiating account is a second type account.

[0142] Optionally, the executing module 306 is further configured to:

[0143] determining an account attribute value of the service initiation account and a service attribute value in the service processing request;

[0144] in a case where the account attribute value is greater than or equal to the service attribute value, determining a service receiving account based on the service processing request, and executing the service processing request.

[0145] Optionally, the execution module 306 is further configured to:

[0146] in a case where the account attribute value is less than the service attribute value, determining that the service processing request fails to be executed.

[0147] Optionally, the apparatus further comprises a voting module configured to:

[0148] receiving an account upgrade request issued by a voting initiation account, wherein the account upgrade request contains a to-be-upgraded account identifier, the voting initiation account is a second type account, and the to-be-upgraded account corresponding to the to-be-upgraded account identifier is a first type account;

[0149] counting voting information fed back by each second type account in the alliance chain for the account upgrade request to obtain a voting attribute value;

[0150] in a case where the voting attribute value is greater than a voting attribute threshold value, upgrading the to-be-upgraded account to a second type account.

[0151] Optionally, the apparatus further comprises a creation module configured to:

[0152] receiving an alliance chain creation request generated based on creation requirements of an alliance chain first organization and an alliance chain second organization;

[0153] creating an alliance chain in response to the alliance chain creation request, and configuring alliance chain accounts of the alliance chain first organization and the alliance chain second organization as second type accounts.

[0154] Optionally, the apparatus further comprises an adding module configured to:

[0155] receiving an alliance chain joining request of an alliance chain third organization;

[0156] creating a first type account of the alliance chain third organization in response to the alliance chain joining request, and upgrading the first type account to a second type account.

[0157] Optionally, the apparatus further comprises a permission allocation module configured to:

[0158] receiving a permission allocation request sent by a first type account of an alliance chain third organization, wherein the permission allocation request contains a target permission identifier;

[0159] in response to the permission assignment request, assigning, by the second-type account, the target permission corresponding to the target permission identifier and a permission valid time interval corresponding to the target permission to the first-type account of the third organization of the alliance chain.

[0160] Optionally, the apparatus further comprises an upgrade module configured to:

[0161] receive an account upgrade request sent by a second-type account of a third organization of the alliance chain, and determine a to-be-upgraded account based on the account upgrade request;

[0162] count voting information fed back by each second-type account in the alliance chain for the account upgrade request to obtain a voting attribute value;

[0163] in a case where the voting attribute value is greater than a voting attribute threshold, upgrade the to-be-upgraded account to a second-type account.

[0164] Optionally, the apparatus further comprises a permission adjustment module configured to:

[0165] receive a permission adjustment request by a second-type account, and determine a to-be-adjusted account in the alliance chain based on the permission adjustment request;

[0166] adjust account permission information and / or a permission valid time interval of the to-be-adjusted account according to permission adjustment information in the permission adjustment request.

[0167] Optionally, the apparatus further comprises a permission assignment request module configured to:

[0168] in a case where the account permission information does not contain business permission information corresponding to the business processing request, send a permission assignment request to a second-type account;

[0169] if the second-type account does not configure permission for the business initiation account based on the permission assignment request, determine that the business processing request fails.

[0170] Optionally, the apparatus further comprises a permission valid time adjustment module configured to:

[0171] in a case where the account permission information contains business permission information corresponding to the business processing request and the current time point is not within the permission valid time, send a permission valid time adjustment request to a second-type account;

[0172] if the second-type account does not adjust the permission valid time interval for the business initiation account based on the permission valid time adjustment request, determine that the business processing request fails.

[0173] The business processing device based on the alliance chain of the present application, a receiving module is configured to receive a user sent business processing request, and determine the business initiation account of the business processing request; the determining module is configured to determine the account permission information of the business initiation account and the permission effective time interval corresponding to the account permission information in the case that the business initiation account is a first type account; the executing module is configured to execute the business processing request if the business processing request corresponding business permission information is contained in the account permission information, and the current time point is within the permission effective time interval. By checking the business permission information of the business initiation account and the permission effective time interval corresponding to the business permission information, the abnormal business transactions of the alliance chain account are limited, and the business processing rationality on the alliance chain is improved.

[0174] The above is a schematic scheme of the business processing device based on the alliance chain of the embodiment. It should be noted that the technical scheme of the business processing device based on the alliance chain belongs to the same concept as the technical scheme of the business processing method based on the alliance chain described above, and the details of the technical scheme of the business processing device based on the alliance chain which are not described in detail can be referred to the description of the technical scheme of the business processing method based on the alliance chain.

[0175] Figure 4 The structure block diagram of a computing device 400 according to an embodiment of the present application is shown. The components of the computing device 400 include, but are not limited to, a memory 410 and a processor 420. The processor 420 is connected with the memory 410 through a bus 430, and a database 450 is used to save data.

[0176] The computing device 400 also includes an access device 440, which enables the computing device 400 to communicate via one or more networks 460. Examples of these networks include the public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 440 can include one or more of any type of network interface (e.g., network interface card (NIC)) such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a near-field communication (NFC) interface, and the like, either wired or wireless.

[0177] In an embodiment of the present application, the above-mentioned components of the computing device 400 and other components not shown in the Figure 4 It should be understood that the components of the computing device 400 can be connected to each other through a bus, for example. Figure 4The illustrated computing device architecture diagram is for the purpose of example only and is not intended to limit the scope of the present application. Other components can be added or substituted as desired by those skilled in the art.

[0178] The computing device 400 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. The computing device 400 can also be a mobile or stationary server.

[0179] The processor 420 implements the steps of the alliance chain-based business processing method when executing the computer instructions.

[0180] The above is a schematic scheme of the computing device of the embodiment. It should be noted that the technical scheme of the computing device belongs to the same concept as the technical scheme of the alliance chain-based business processing method described above, and the details of the technical scheme of the computing device that are not described in detail can be referred to the description of the technical scheme of the alliance chain-based business processing method.

[0181] An embodiment of the present application also provides a computer readable storage medium storing computer instructions, which, when executed by a processor, implement the steps of the alliance chain-based business processing method as described above.

[0182] The above is a schematic scheme of the computer readable storage medium of the embodiment. It should be noted that the technical scheme of the storage medium belongs to the same concept as the technical scheme of the alliance chain-based business processing method described above, and the details of the technical scheme of the storage medium that are not described in detail can be referred to the description of the technical scheme of the alliance chain-based business processing method.

[0183] The specific embodiments of the present application are described above. Other embodiments are within the scope of the appended claims. In some cases, acts or steps recited in the claims can be performed in an order other than that recited in the embodiments, and still achieve desirable results. Also, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing can be advantageous.

[0184] The computer readable medium can include any entity or apparatus capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, software distribution medium, etc. It should be noted that the computer readable medium can include appropriate additions or subtractions according to the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.

[0185] It should be noted that for the foregoing method embodiments, the descriptions are expressed as a combination of a series of actions for the sake of simplicity, but those skilled in the art should know that the present application is not limited by the order of the described actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0186] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0187] The preferred embodiments of the present application disclosed above are only used to help explain the present application. The alternative embodiments do not describe all the details and do not limit the present application to the specific embodiments described. Obviously, according to the content of the present application, many modifications and changes can be made. The present application selects and describes these embodiments in order to better explain the principles and practical applications of the present application, so that those skilled in the art can well understand and utilize the present application. The present application is limited by the claims and their entire scope and equivalents.

Claims

1. A business processing method based on a consortium chain, characterized by, The permission verification module applied to the alliance chain comprises: Receiving a business processing request sent by a user, and determining a business initiation account of the business processing request; In the case that the business initiation account is a first type account, determining account permission information of the business initiation account and a permission effective time interval corresponding to the account permission information; If the account permission information contains business permission information corresponding to the business processing request, and the current time point is within the permission effective time interval, the business processing request is executed; The method further comprises: Receiving an alliance chain creation request generated based on creation requirements of an alliance chain first organization and an alliance chain second organization; In response to the alliance chain creation request, creating an alliance chain, and configuring alliance chain accounts of the alliance chain first organization and the alliance chain second organization as second type accounts; After creating the alliance chain in response to the alliance chain creation request and configuring the alliance chain accounts of the alliance chain first organization and the alliance chain second organization as second type accounts, the method further comprises: Receiving an account upgrade request sent by a second type account of an alliance chain third organization, and determining a to-be-upgraded account based on the account upgrade request; Statistics of voting information fed back by each second type account in the alliance chain for the account upgrade request is obtained, and a voting attribute value is obtained; In the case that the voting attribute value is greater than a voting attribute threshold, the to-be-upgraded account is upgraded to a second type account.

2. The method of claim 1, wherein, The method further comprises: In the case that the business initiation account is a second type account, the business processing request is executed.

3. The method of claim 1 or 2, wherein, The execution of the business processing request comprises: Determining an account attribute value of the business initiation account and a business attribute value in the business processing request; In the case that the account attribute value is greater than or equal to the business attribute value, determining a business receiving account based on the business processing request, and executing the business processing request.

4. The method of claim 3, wherein, The method further comprises: In the case that the account attribute value is less than the business attribute value, determining that the business processing request fails.

5. The method of claim 1, wherein, The method further comprises: Receiving an account upgrade request issued by a voting initiation account, wherein the account upgrade request contains a to-be-upgraded account identifier, the voting initiation account is a second type account, and the to-be-upgraded account corresponding to the to-be-upgraded account identifier is a first type account; Statistics of voting information fed back by each second type account in the alliance chain for the account upgrade request is obtained, and a voting attribute value is obtained; In the case that the voting attribute value is greater than a voting attribute threshold, the to-be-upgraded account is upgraded to a second type account.

6. The method of claim 1, wherein, After creating the alliance chain in response to the alliance chain creation request and configuring the alliance chain accounts of the alliance chain first organization and the alliance chain second organization as second type accounts, the method further comprises: Receiving an alliance chain joining request of an alliance chain third organization; In response to the alliance chain joining request, creating a first type account of the alliance chain third organization, and upgrading the first type account to a second type account.

7. The method of claim 6, wherein, In response to the creation of the third organization's account in the consortium chain, the method further comprises: receiving a permission assignment request sent by the first type account of the third organization, wherein the permission assignment request contains a target permission identifier; in response to the permission assignment request, assigning the target permission corresponding to the target permission identifier and a permission validity time interval corresponding to the target permission to the first type account of the third organization by the second type account.

8. The method of claim 1, wherein, In response to the creation of the consortium chain, the method further comprises: the second type account receives a permission adjustment request and determines a to-be-adjusted account in the consortium chain based on the permission adjustment request; adjusting the account permission information and / or the permission validity time interval of the to-be-adjusted account according to the permission adjustment information in the permission adjustment request.

9. The method of claim 2, wherein, The method further comprises: if the business processing request corresponding business permission information is not contained in the account permission information, sending a permission assignment request to the second type account; if the second type account does not configure permissions for the business initiation account based on the permission assignment request, determining that the business processing request fails to execute.

10. The method of claim 2, wherein, The method further comprises: if the business processing request corresponding business permission information is contained in the account permission information, and the current time point is not within the permission validity time, sending a permission validity time adjustment request to the second type account; if the second type account does not adjust the permission validity time interval for the business initiation account based on the permission validity time adjustment request, determining that the business processing request fails to execute. 11.A business processing apparatus based on a consortium chain, characterized by comprising: The method further comprises: a receiving module configured to receive a business processing request sent by a user and determine a business initiation account of the business processing request; a determining module configured to, if the business initiation account is a first type account, determine account permission information of the business initiation account and a permission validity time interval corresponding to the account permission information; an executing module configured to, if the account permission information contains business processing request corresponding business permission information, and the current time point is within the permission validity time interval, execute the business processing request; The device further comprises a creating module configured to: receive a consortium chain creation request generated based on the creation demand of the first organization and the second organization of the consortium chain; in response to the consortium chain creation request, create a consortium chain, and configure the consortium chain accounts of the first organization and the second organization of the consortium chain as second type accounts; The device further comprises an upgrading module configured to: receive an account upgrading request sent by the second type account of the third organization, and determine a to-be-upgraded account based on the account upgrading request; statistically obtain voting attribute values by counting voting information fed back by each second type account in the consortium chain for the account upgrading request; In a case where the voting attribute value is greater than a voting attribute threshold, the to-be-upgraded account is upgraded to a second type account.

12. A computing device comprising a memory, a processor, and computer instructions stored on the memory and executable on the processor, wherein, The processor implements the steps of the method of any one of claims 1-10 when executing the computer instructions.

13. A computer-readable storage medium storing computer instructions, wherein, The computer instructions, when executed by the processor, implement the steps of the method of any one of claims 1-10.

14. A computer program product comprising computer instructions, characterized in that, The computer instructions, when executed by the processor, implement the steps of the method of any one of claims 1-10. The computer instructions, when executed by the processor, implement the steps of the method of any one of claims 1-10.

Images