Asset full life cycle management method based on alliance chain

Abstract

The invention relates to an alliance chain-based asset full life cycle management method, which comprises the following steps of: generating application information based on a commercial behavior demand through an enterprise side, encrypting the generated application information of the commercial behavior demand and sending the encrypted application information to each server side on an alliance chain; then, each server side decrypts the received encrypted application information of the commercial behavior demand, part of the server sides generate a first secret key of each server side based on the decrypted information, and the first secret key is sent back to the enterprise side; the enterprise side screens the received multiple first secret keys and selects a proper server side, and then the enterprise side encrypts the screened server side information and sends the encrypted information to each server side which is not selected; and each unselected server side sends the evaluation of the selected server side to the enterprise side, and the enterprise side performs evaluation based on the received evaluation.

Description

Technical Field

[0001] The present application relates to the field of asset management technology, and in particular to an asset full life cycle management method based on an alliance chain. Background Art

[0002] The consortium chain is only for members of a specific group and limited third parties. It internally designates multiple pre-selected nodes as bookkeepers. The generation of each block is jointly determined by all pre-selected nodes. Other access nodes can participate in transactions, but do not ask about the bookkeeping process. Other third parties can perform limited queries through the open API of the blockchain. In order to obtain better performance, the consortium chain has certain requirements for the configuration and network environment of consensus or verification nodes. With the access mechanism, transaction performance can be improved more easily and some problems caused by uneven participants can be avoided.

[0003] At present, enterprises generate a large number of asset or capital transactions in the course of their frequent business activities. In this process, each transaction needs to be recorded and managed, which wastes a lot of time and energy, resulting in high costs and low efficiency for enterprises in asset management. Summary of the invention

[0004] Based on this, it is necessary to provide an asset life cycle management method based on an alliance chain to address the problem that traditional enterprises need to record and manage every transaction in the process of asset management, which will waste a lot of time and energy, resulting in high costs and low efficiency in asset management.

[0005] This application provides an asset life cycle management method based on alliance chain, including:

[0006] The enterprise side generates an asset decision application information;

[0007] Send asset decision application information to each server;

[0008] The enterprise determines whether it has received at least one first secret key sent by the server;

[0009] If at least one first secret key sent by a server is received, the locally stored server public key is retrieved to decrypt each first secret key one by one to obtain a first decryption result;

[0010] Select a server as the hit server based on the result of the first decryption;

[0011] The enterprise's private key is retrieved to sign the first secret key of the hit server, and the second secret key is generated and sent to each server, so as to further enable each missed server to evaluate the hit server;

[0012] The enterprise side determines whether the on-chain conditions are met based on the evaluation of the hit server by all the missed servers;

[0013] If the on-chain conditions are met, the target Key is generated;

[0014] The enterprise package the target key and contract information and upload them to the alliance chain.

[0015] Further, after the server determines the docking asset decision application, the server that determines the docking asset decision application performs the following steps:

[0016] The server retrieves the private key stored locally to sign the asset decision application information, generates a first signature and sends the first signature back to the enterprise; the server is defined as the hit server.

[0017] Furthermore, after each missed server receives the second secret key, each missed server performs the following steps:

[0018] Extract the enterprise-side public key stored locally on the server that missed the target, and decrypt it to obtain the result of the second decryption;

[0019] When the missed server recognizes the hit server, the missed server retrieves the locally stored private key of the missed server to sign the second decryption result, obtains a second signature, and sends the second signature to the enterprise end.

[0020] Furthermore, the enterprise generates an asset decision application information and sends the asset decision application information to each service end, including:

[0021] The enterprise side generates a first random number, a second random number and a third random number;

[0022] All servers except the enterprise side in the alliance chain are regarded as receiving ends. The enterprise side generates the asset decision application information corresponding to each server side according to Formula 1;

[0023] N k =[s1 111 +H(id i )+t1+t2+s2+s3] Formula 1;

[0024] Among them, N k is the asset decision application information of the server with serial number K; s1 is the first random number, 111 is the type of asset decision application; s1 111 The encrypted result of the type of asset decision application for the first random number; id i It is the identity of the enterprise side; H(id i) is the hash value obtained by hashing the identity identifier of the enterprise; t1 is the starting time of the asset decision application initiated by the enterprise; t2 is the end time of the asset decision application initiated by the enterprise; s2 is the second random number; s3 is the third random number.

[0025] Furthermore, the method of retrieving the locally stored private key to sign the asset decision application information, generating a first secret key and sending the first secret key back to the enterprise end includes:

[0026] The server determines that the server that connects to the asset decision application retrieves the private key stored locally, signs the asset decision application information according to Formula 2, and obtains the first secret key corresponding to the enterprise end;

[0027] G k =[H(N k )] vk Formula 2;

[0028] Among them, G k is the first secret key of the server with serial number k; N k The service information of the service provided by the server with serial number K; H(N k ) is the hash obtained by hashing the asset decision application information of the server with serial number K; vk is the private key of the server with serial number K.

[0029] Furthermore, the service information of the service provided by the server includes one or more of service type information, service agreed start time, and service agreed end time.

[0030] Furthermore, the enterprise determines whether the chaining conditions are met based on the evaluation of the hit server by all the missed servers, including:

[0031] The threshold for the number of first signatures created by the enterprise side;

[0032] Count the number of all first signatures obtained;

[0033] Determine whether the number of all first signatures obtained is greater than or equal to a first signature number threshold;

[0034] If the number of all first signatures obtained is greater than or equal to the first signature number threshold, it is determined that the evaluations generated by all missed servers on the hit server meet the on-chain conditions;

[0035] If the number of all first signatures obtained is less than the first signature number threshold, it is determined that the evaluations generated by all missed servers on the hit server do not meet the on-chain conditions.

[0036] Further, when the missed server recognizes the hit server, the missed server retrieves the private key of the missed server stored locally to sign the second decryption result, obtains a second signature, and sends the second signature to the enterprise end, including:

[0037] The missed server retrieves the private key of the missed server stored locally, signs the second decryption result according to Formula 3, and obtains a second signature;

[0038] W k =[H(id y +id n +T+t4)] Formula 3;

[0039] Among them, W k The second signature of the server with sequence number k that missed the target; id y The ID of the server that hits the server; id n is the ID of the current missed server; T is the evaluation time of the missed server on the hit server; t4 is the fourth random number.

[0040] Furthermore, if the on-chain conditions are met, the target Key is generated, including:

[0041] The enterprise client obtains all second signatures;

[0042] Retrieve the public key of each missed server, decrypt each second signature, and obtain the ID of the missed server corresponding to each second signature;

[0043] Aggregate the hit server ID and all second signatures to get the key.

[0044] Furthermore, the method of retrieving the public key of each missed server, decrypting each second signature, and obtaining the ID of the missed server corresponding to each second signature includes:

[0045] Retrieve the public key of each missed server, decrypt each second signature, and determine whether each second signature is successfully decrypted;

[0046] If so, the ID of the server that hits the key and all the second signatures will be aggregated to get the key.

[0047] If not, terminate the subsequent steps and return to send the asset decision application information to each server.

[0048] The present application relates to an asset life cycle management method based on a consortium chain, in which an application information based on business behavior requirements is generated by the enterprise side, and the generated application information of the business behavior requirements is encrypted and sent to each server on the consortium chain, and then each server will decrypt the received encrypted application information of the business behavior requirements, and some servers will generate the first secret key of each server based on the decrypted information, and send the first secret key back to the enterprise side, and the enterprise side will screen the received multiple first secret keys and select the appropriate server, and then the enterprise side will encrypt the screened server information and send the encrypted information to each unselected server, and each unselected server will send the evaluation of the selected server to the enterprise side, and the enterprise side will evaluate based on the received evaluation. Only when the received evaluation meets the evaluation requirements will it generate a target Key, and then package the target Key and contract information and upload them to the consortium chain. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 A flowchart of an asset life cycle management method based on a consortium chain provided in accordance with an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0051] like Figure 1 As shown, in one embodiment of the present application, the asset life cycle management method based on the alliance chain includes the following S100 to S900:

[0052] S100, the enterprise generates an asset decision application information.

[0053] Specifically, an asset decision application refers to a demand generated by the enterprise in actual business activities, which may include a demand application for the sale of products produced by the enterprise, an application for maintenance of equipment used by the enterprise, and so on.

[0054] S200, sending asset decision application information to each server.

[0055] S300, the enterprise determines whether it has received a first secret key sent by at least one server.

[0056] S400: If at least one first secret key sent by a server is received, the locally stored server public key is retrieved to decrypt each first secret key one by one to obtain a first decryption result.

[0057] S500: Select a server as a hit server based on the result of the first decryption.

[0058] Specifically, the hit service end refers to other enterprises on the alliance chain, and the enterprise can provide corresponding business behaviors for the asset decision application submitted by the enterprise end, and the business behavior can be purchasing behavior, equipment maintenance, etc.

[0059] S600, retrieve the enterprise's private key to sign the first secret key of the hit server, generate a second secret key and send it to each server, so as to further enable each missed server to evaluate the hit server.

[0060] S700, the enterprise determines whether the chaining conditions are met based on the evaluation of the hit server by all the missed servers.

[0061] S800: If the uplink conditions are met, the target Key is generated.

[0062] S900, the enterprise package the target key and contract information and upload them to the alliance chain.

[0063] Specifically, it should be noted that each client in the alliance chain (the client can be any enterprise end or any server end) has a private key and a public key. At the same time, the local storage of each client includes a private key of the client and the public keys of all clients except the client itself.

[0064] In this embodiment, an application information based on the business behavior demand is generated by the enterprise side, and the generated application information of the business behavior demand is encrypted and sent to each server on the alliance chain. Then each server will decrypt the received encrypted application information of the business behavior demand. Some servers will generate the first secret key of each server based on the decrypted information, and send the first secret key back to the enterprise side. The enterprise side will screen the multiple first secret keys received and select the appropriate server. Then the enterprise side will encrypt the screened server information and send the encrypted information to each unselected server. Each unselected server will send the evaluation of the selected server to the enterprise side. The enterprise side will evaluate based on the received evaluation. Only when the received evaluation meets the evaluation requirements will it generate a target Key, and then package the target Key and contract information and upload them to the alliance chain.

[0065] In one embodiment of the present application, after the server determines the docking asset decision application, the server that determines the docking asset decision application executes the following step S501:

[0066] S501 The server retrieves the private key stored locally to sign the asset decision application information, generates a first signature and sends the first signature back to the enterprise; the server is defined as the hit server.

[0067] In this embodiment, the server signs the asset decision application information with the private key stored locally, thereby generating a first signature, and the server sends the first signature to the enterprise end. This server is defined as a hit server.

[0068] In one embodiment of the present application, after each missed server receives the second key, each missed server performs the following steps S601 to S602:

[0069] S601, extracting the enterprise-side public key stored locally on the server that was not hit for decryption to obtain a second decryption result.

[0070] S602, when the missed server recognizes the hit server, the missed server retrieves the private key of the missed server stored locally to sign the second decryption result, obtains a second signature, and sends the second signature to the enterprise end.

[0071] In this embodiment, the second secret key is decrypted by first extracting the public key of the enterprise side stored locally on the missed server side, and then the second decryption result is obtained. The missed server side performs information analysis on the obtained second decryption result. When the missed server side approves the second decryption result, the missed server side will retrieve the private key of the missed server side stored locally to sign the second decryption result to generate a second signature, and then the missed server side sends the second signature back to the enterprise side.

[0072] In one embodiment of the present application, the enterprise generates an asset decision application information, including the following S100 to S102:

[0073] S101, the enterprise generates a first random number, a second random number and a third random number.

[0074] S102, taking all the servers except the enterprise in the alliance chain as receiving terminals, the enterprise generates asset decision application information corresponding to each server according to Formula 1;

[0075] N k =[s1 111 +H(id i )+t1+t2+s2+s3] Formula 1;

[0076] Among them, N kis the asset decision application information of the server with serial number K; s1 is the first random number, 111 is the type of asset decision application; s1 111 The encrypted result of the type of asset decision application for the first random number; id i It is the identity of the enterprise side; H(id i ) is the hash value obtained by hashing the identity identifier of the enterprise; t1 is the starting time of the asset decision application initiated by the enterprise; t2 is the end time of the asset decision application initiated by the enterprise; s2 is the second random number; s3 is the third random number.

[0077] Specifically, the type of asset decision application can be maintenance type, purchase type, sale type, etc.

[0078] In this embodiment, a first random number, a second random number and a third random number are generated by the enterprise side, wherein the first random number is encrypted using the type of asset decision application to obtain an encrypted result, and then the identity identifier of the enterprise side is hashed to obtain a hash value, and the start time and end time of the asset decision application initiated by the enterprise side are accumulated to obtain the asset decision application information received by the server side with serial number K.

[0079] In one embodiment of the present application, the server retrieves the private key stored locally to sign the asset decision application information, generates a first signature and sends the first signature back to the enterprise end, including the following S501a:

[0080] S501a, the server determines that the server that connects to the asset decision application retrieves the private key stored locally, signs the asset decision application information according to formula 2, and obtains the first secret key corresponding to the enterprise end;

[0081] G k =[H(N k )] vk Formula 2;

[0082] Among them, G k is the first secret key of the server with serial number k; N k The service information of the service provided by the server with serial number K; H(N k ) is the hash obtained by hashing the asset decision application information of the server with serial number K; vk is the private key of the server with serial number K.

[0083] In this embodiment, the service information of the service provided by the server is hashed to obtain a hash value, and then the server retrieves the locally stored private key of the server to sign the obtained hash value to generate a first signature.

[0084] In one embodiment of the present application, the service information of the service provided by the server includes one or more of service type information, service agreed start time, and service agreed end time.

[0085] In one embodiment of the present application, the enterprise end determines whether the chaining condition is met based on the evaluation of the hit server end by all the missed server ends, including S701 to S705:

[0086] S701, the enterprise creates a first signature quantity threshold.

[0087] S702: Count the number of all first signatures obtained.

[0088] S703: Determine whether the number of all acquired first signatures is greater than or equal to a first signature number threshold.

[0089] S704: If the number of all first signatures obtained is greater than or equal to the first signature number threshold, it is determined that the evaluations generated by all missed servers on the hit server meet the on-chain conditions.

[0090] S705: If the number of all first signatures obtained is less than the first signature number threshold, it is determined that the evaluations generated by all missed servers on the hit server do not meet the on-chain conditions.

[0091] In this embodiment, a first signature quantity threshold is first created by the enterprise side, and then the enterprise side counts the number of first signatures received. The enterprise side compares the number of first signatures received with the created first signature quantity threshold. Only when the number of first signatures received is greater than the created first signature quantity threshold, the enterprise side will determine that the asset decision application is qualified.

[0092] In one embodiment of the present application, when the missed server recognizes the hit server, the missed server retrieves the private key of the missed server stored locally to sign the second decryption result, obtains a second signature, and sends the second signature to the enterprise end, including S602a:

[0093] S602a, the missed server retrieves the private key of the missed server stored locally, signs the second decryption result according to Formula 3, and obtains a second signature;

[0094] W k =[H(id y +id n +T+t4)] Formula 3;

[0095] Among them, W k The second signature of the server with sequence number k that missed the target; id yThe ID of the server that hits the server; id n is the ID of the current missed server; T is the evaluation time of the missed server on the hit server; t4 is the fourth random number.

[0096] In this embodiment, when the missed server approves the result of the second decryption, the missed server needs to retrieve the locally stored private key of the missed server to sign the second decryption result. The signing process is to accumulate the ID of the hit server, the ID of the current missed server, the evaluation time of the missed server on the hit server, and the fourth random number, and then hash the accumulated result to obtain the hash value which is the second signature.

[0097] In one embodiment of the present application, if the uplink condition is met, a target Key is generated, including the following S801 to S900:

[0098] S801, the enterprise client obtains all second signatures.

[0099] S802, retrieve the public key of each missed server, decrypt each second signature, and obtain the ID of the missed server corresponding to each second signature.

[0100] S803, aggregate the hit server ID and all second signatures to obtain a key.

[0101] In this embodiment, the corresponding second signature sent by each missed server is first decrypted using the public key of each missed server to obtain the ID of the missed server corresponding to each second signature, and then the ID of the hit server and all the second signatures are aggregated to generate the target Key.

[0102] In one embodiment of the present application, the method of retrieving the public key of each missed server, decrypting each second signature, and obtaining the ID of the missed server corresponding to each second signature includes the following S802a to S802c:

[0103] S802a, retrieve the public key of each missed server, decrypt each second signature, and determine whether each second signature is successfully decrypted.

[0104] S802b: If yes, then perform the subsequent aggregation of the hit server ID and all second signatures to obtain the key.

[0105] S802c, if not, terminate the subsequent steps and return to send the asset decision application information to each server.

[0106] In this embodiment, the public key of each missed server stored locally is retrieved through the enterprise end to decrypt the second signature uploaded by each missed server. If the public key of each missed server can be decrypted successfully, the subsequent steps can be executed. If the public key of any missed server fails to decrypt, the asset decision application information is returned and sent to each server.

[0107] The technical features of the above-described embodiments may be arbitrarily combined, and the execution order of the method steps is not limited. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0108] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for asset life cycle management based on alliance chain, characterized in that: The asset life cycle management method based on the alliance chain includes: The enterprise side generates an asset decision application information; Send asset decision application information to each server; The enterprise determines whether it has received at least one first secret key sent by the server; If at least one first secret key sent by a server is received, the locally stored server public key is retrieved to decrypt each first secret key one by one to obtain a first decryption result; Select a server as the hit server based on the result of the first decryption; The enterprise's private key is retrieved to sign the first secret key of the hit server, and the second secret key is generated and sent to each server, so as to further enable each missed server to evaluate the hit server; The enterprise side determines whether the on-chain conditions are met based on the evaluation of the hit server by all the missed servers; If the on-chain conditions are met, the target Key is generated; The enterprise package the target key and contract information and upload them to the alliance chain.

2. The asset life cycle management method based on alliance chain according to claim 1 is characterized in that: After the server determines the docking asset decision application, the server that determines the docking asset decision application performs the following steps: The server retrieves the private key stored locally to sign the asset decision application information, generates a first signature and sends the first signature back to the enterprise; the server is defined as the hit server.

3. The asset life cycle management method based on alliance chain according to claim 2 is characterized in that: After each missed server receives the second secret key, each missed server performs the following steps: Extract the enterprise-side public key stored locally on the server that missed the target, and decrypt it to obtain the result of the second decryption; When the missed server recognizes the hit server, the missed server retrieves the locally stored private key of the missed server to sign the second decryption result, obtains a second signature, and sends the second signature to the enterprise end.

4. The asset life cycle management method based on alliance chain according to claim 3 is characterized in that: The enterprise end generates an asset decision application information and sends the asset decision application information to each service end, including: The enterprise side generates a first random number, a second random number and a third random number; All servers except the enterprise side in the alliance chain are regarded as receiving ends. The enterprise side generates the asset decision application information corresponding to each server side according to Formula 1; N k ＝ [ s1 111 +H(id i )+t 1 +t 2 +s2+s3 ] Formula 1; Wherein, Nk is the asset decision application information of the server with serial number K; s1 is the first random number, and 111 is the type of asset decision application; s 1111 is the result of encrypting the first random number using the type of asset decision application; id i is the identity identifier of the enterprise; H(idi) is the hash value obtained by hashing the identity identifier of the enterprise; t1 is the starting time of the asset decision application initiated by the enterprise; t2 is the end time of the asset decision application initiated by the enterprise; s2 is the second random number; s3 is the third random number.

5. The asset life cycle management method based on alliance chain according to claim 4 is characterized in that: The method of retrieving the locally stored private key to sign the asset decision application information, generating the first secret key and sending the first secret key back to the enterprise end includes: The server determines that the server that connects to the asset decision application retrieves the private key stored locally, signs the asset decision application information according to Formula 2, and obtains the first secret key corresponding to the enterprise end; G k ＝ [ H(N k ) ]vk Formula 2; Among them, Gk is the first secret key of the server with serial number k; Nk is the service information of the service provided by the server with serial number K; H(Nk) is the hash obtained by hashing the asset decision application information of the server with serial number K; vk is the private key of the server with serial number K.

6. The asset life cycle management method based on alliance chain according to claim 5 is characterized in that: The service information of the service provided by the server includes one or more of service type information, service agreed start time, and service agreed end time.

7. The asset life cycle management method based on alliance chain according to claim 6 is characterized in that: The enterprise determines whether the chaining conditions are met based on the evaluation of the hit server by all the missed servers, including: The threshold for the number of first signatures created by the enterprise side; Count the number of all first signatures obtained; Determine whether the number of all first signatures obtained is greater than or equal to a first signature number threshold; If the number of all first signatures obtained is greater than or equal to the first signature number threshold, it is determined that the evaluations generated by all missed servers on the hit server meet the on-chain conditions; If the number of all first signatures obtained is less than the first signature number threshold, it is determined that the evaluations generated by all missed servers on the hit server do not meet the on-chain conditions.

8. The asset life cycle management method based on alliance chain according to claim 7 is characterized in that: When the missed server recognizes the hit server, the missed server retrieves the private key of the missed server stored locally to sign the second decryption result, obtains a second signature, and sends the second signature to the enterprise end, including: The missed server retrieves the private key of the missed server stored locally, signs the second decryption result according to Formula 3, and obtains a second signature; W k ＝ [ H(id y +id n +T+t4) ] Formula 3; Among them, Wk is the second signature of the missed server with serial number k; idy is the ID of the hit server; idn is the ID of the current missed server; T is the evaluation time of the missed server on the hit server; t4 is the fourth random number.

9. The asset life cycle management method based on alliance chain according to claim 8 is characterized in that: If the on-chain conditions are met, the target Key is generated, including: The enterprise client obtains all second signatures; Retrieve the public key of each missed server, decrypt each second signature, and obtain the ID of the missed server corresponding to each second signature; Aggregate the hit server ID and all second signatures to get the key.

10. The asset life cycle management method based on alliance chain according to claim 9 is characterized in that: The method of retrieving the public key of each missed server, decrypting each second signature, and obtaining the ID of the missed server corresponding to each second signature includes: Retrieve the public key of each missed server, decrypt each second signature, and determine whether each second signature is successfully decrypted; If so, the ID of the server that hits the key and all the second signatures will be aggregated to get the key. If not, terminate the subsequent steps and return to send the asset decision application information to each server.

Images