CN113159682B - Electronic warehouse information alliance chain system - Google Patents
Electronic warehouse information alliance chain system Download PDFInfo
- Publication number
- CN113159682B CN113159682B CN202110435743.1A CN202110435743A CN113159682B CN 113159682 B CN113159682 B CN 113159682B CN 202110435743 A CN202110435743 A CN 202110435743A CN 113159682 B CN113159682 B CN 113159682B
- Authority
- CN
- China
- Prior art keywords
- user
- bill
- transaction
- warehouse
- alliance chain
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
- G06Q10/0875—Itemisation or classification of parts, supplies or services, e.g. bill of materials
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06315—Needs-based resource requirements planning or analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Marketing (AREA)
- Development Economics (AREA)
- Finance (AREA)
- Game Theory and Decision Science (AREA)
- Educational Administration (AREA)
- Computer Security & Cryptography (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses an electronic bill of goods information alliance chain system, which comprises an IOT terminal, a bill of goods system and an alliance chain system; the IOT terminal is used for a user to initiate a bill operation request to the bill system; the warehouse receipt system is used for constructing a corresponding on-chain transaction request sending alliance chain system after receiving a warehouse receipt operation request of a user; after receiving the on-chain transaction request, the alliance chain system executes corresponding transaction operation. The invention can enable the user to execute on the alliance chain aiming at the operation of the bill, thereby enabling the data change of the bill to be trace-free and unmodified and providing a trust environment for the execution of the operation business of the bill.
Description
Technical Field
The invention belongs to the technical field of alliance chain systems, and particularly relates to an electronic warehouse information alliance chain system.
Background
The electronic warehouse bill is a certificate for picking up the warehouse articles, which is paid by a warehouse custodian to a supplier (stock person) after the warehouse custodian receives the warehouse articles. The electronic warehouse bill can be used as a certificate of the collected warehouses and a certificate of the extracted warehouses, and can be used for transferring ownership of goods under the electronic warehouse bill or for quality improvement through endorsements.
Electronic warehouse bill is a certificate which is frequently used in the real estate mortgage financing industry, but in recent years, the problem of repeated mortgages is continuously generated.
The common knowledge mechanism and information in the block chain technology are not tamper-proof, so that the problems can be effectively solved. There is currently no specific technical solution for applying blockchain technology to electronic warehouse transactions and mortgages.
Disclosure of Invention
The technical problem to be solved by the invention is to provide an electronic bill information alliance chain system aiming at the defects in the prior art, which can enable a user to execute on an alliance chain aiming at the operation of a bill, so that the change of the data of the bill is trace-free and unmodified, and a trust environment is provided for the execution of the bill operation service.
In order to solve the technical problems, the invention adopts the following technical scheme: an electronic bill of lading information alliance chain system comprises an IOT terminal, a bill of lading system and an alliance chain system;
the IOT terminal is used for a user to initiate a bill operation request to the bill system;
the warehouse receipt system is used for constructing a corresponding on-chain transaction request sending alliance chain system after receiving a warehouse receipt operation request of a user;
after receiving the on-chain transaction request, the alliance chain system executes corresponding transaction operation.
The electronic bill information alliance chain system, wherein the bill operation request comprises a bill account opening request, and the bill system executes the following steps after receiving the bill account opening request:
the warehouse bill system signs the user information text provided by the IOT terminal through a digital signature algorithm to obtain a signature value;
writing the signature value into an on-chain transaction request, and sending the on-chain transaction request into a user service processing channel of the alliance chain system;
the alliance chain system constructs a digital identity DID as a unique identifier of a user on a chain according to the on-chain transaction request;
the alliance chain system creates a contract container UserCreating and builds a GRPC contract calling interface; the GRPC calling interface is used for transmitting the message into a contract container UserCreating;
the contract container UserCreating calls a contract chain code execution request CreateNewAccount callback function in the container, stores the newly built user digital identity DID in a local on-chain database, and returns a user digital identity DID creation success result through a GRPC call interface new message;
broadcasting the transaction registered by the user in the user service processing channel by the alliance chain system, and waiting for all endorsement nodes to verify the transaction and returning a verification result;
after the number of returned verification results reaches a threshold value; and creating an account number on the chain for the user, distributing two public and private key pairs of the user, encrypting the public and private key pairs under the ID name of the user on the chain, generating a key and a private key file, and allowing the user to download the key file after the user verifies the identity.
The electronic warehouse information alliance chain system, the alliance chain system builds digital identity DID for the user through the DID building function, comprises the following steps:
calculating a hash value hash1 for the public key by using a hash algorithm;
taking the first 20 bytes of the hash1 as a hash2;
adding DID role type bytes in front of the hash2 to obtain a hash3;
hash algorithm hash 4=sha-256 (hash 3) is used, and a hash value is calculated by the hash3 to obtain hash4;
combining the first 4 bytes of the hash4 with the hash3 to generate a hash5;
and encoding the hash5 by using a base64 encoding method to obtain the user DID.
The electronic bill information alliance chain system, wherein the bill operation request comprises a bill transaction request, and the bill system executes the following steps after receiving the bill transaction request:
the bill system builds on-chain transaction data according to the bill transaction request, and sends the bill transaction request and the on-chain transaction data to the alliance chain system;
the alliance chain system constructs a transaction according to the warehouse bill transaction request and the transaction data on the chain;
the warehouse system initiates an aggregate signature proposal Q to the alliance chain system, and after the aggregate signature proposal Q is signed, the transaction is in an executable state.
When the transaction is in an executable state, the electronic bill information alliance chain system informs a user through the IOT terminal, and when the user confirms to execute the transaction at the IOT terminal, the alliance chain system executes the transaction.
The electronic warehouse information alliance chain system performs the following steps after receiving the aggregate signature proposal Q:
the federation chain analyzes the content of the aggregated signature proposal Q, analyzes the participant nodes U1, U2..
One of the participant nodes Ui generates a public key pki=ski×g according to its own private key Ski, wherein G is a base point on an elliptic encryption curve (secp 256-k1 elliptic encryption curve), and broadcasts the public key Pki to the other participant nodes;
all the participant nodes calculate a public key list l=hash (pk1..pkn);
the method comprises the steps that a random number Ki is selected by a participant node Ui, ri=Ki G is calculated, and the random number Ri is broadcasted to other participant nodes;
the participant node Ui aggregates the random number r=r1+ & gt Rn;
the party node Ui calculates an aggregation public key p=hash (L, pk 1) ×pk1+,. Hash (L, pkn) ×pkn;
the participant node Ui computes the signature si=ki+hash (P, R, m) and broadcasts Si: wherein m is transaction message body as abstract parameter content;
each of the other participant nodes calculates an aggregate signature s=s1+s2+ & gt.+ Sn, and the signature information (R, S) is the final signature result;
each party node verifies whether the elliptic encryption curve exists or not according to m, the public key list L and signature information (R, S), and deduces the S point: s x g= r+hash (P, R, m) x P; if yes, signature verification is successful, the aggregate signature proposal Q is passed, and the transaction is stored in a local database by each participant node; if not, the signature verification fails, the on-chain state database is not processed, and the alliance chain block historical database is updated.
Compared with the prior art, the invention has the following advantages: by setting the bill system, the user can perform bill operation through the IOT terminal, and the specific bill operation is performed on the alliance chain each time, so that a good trust environment is provided for each party user involved in the bill operation service.
The technical scheme of the invention is further described in detail through the drawings and the embodiments.
Drawings
Fig. 1 is a system block diagram of the present invention.
Fig. 2 is a system operation diagram of the present invention.
Fig. 3 is a schematic diagram of an aggregate signature proposal of the present invention.
Detailed Description
As shown in fig. 1 and 2, an electronic bill of information alliance chain system includes an IOT terminal, a bill of information system, and an alliance chain system.
The IOT terminal communicates with the billing system, which communicates with the coalition chain system.
The alliance chain system is composed of an ordering service node, an account book management node, a consensus node and a certificate management node.
The IOT terminal is configured with a bill opening function, a bill demand function, a bill transaction transfer function, a bill mortgage function, a bill picking function and/or a bill history inquiry function.
In this embodiment, when the IOT terminal executes the function of opening an account in a warehouse, the method includes the following steps:
a01, the IOT terminal collects user information and uploads the user information to a warehouse bill system for auditing; the user information includes, but is not limited to, face recognition information, fingerprint recognition information, user's corporate legal information, user's business information business license, user's corporate credit information, user's corporate risk information;
step A02, after the user information is checked and checked, the warehouse bill system sends a notification result to the user, for example, the user is notified in a short message or mail mode, and a risk agreement is sent to the user, and after the user signs, the signed risk agreement can be uploaded through the IOT terminal;
a03, the IOT terminal sends the signed risk agreement uploaded by the user to a warehouse bill system for checking again;
step A04, after the risk agreement is checked and approved by the warehouse bill system, serializing the text of the risk agreement, signing by ECDSA (elliptic curve digital signature algorithm), and taking the encrypted string as an information abstract m; and then a set of random numbers k, k E [1, n-1 ] in the value domain are generated]The method comprises the steps of carrying out a first treatment on the surface of the Selecting a base point G on the elliptic curve, and obtaining a point KG= (X1, Y1) coordinate by a point multiplication method; calculating r=x 1mod n where n is k maximum boundary +1; r is a non-zero integer; encrypting the information abstract: calculating a message digest content hash e=sha-256 (m); finally, s value s=k is calculated -1 (e+pk x r) mod n, where PK is the private key held by the policy administrator and s is a non-zero value.
Step A05, obtaining a signature pair (r, s) through the last step, sending a signature value into a user transaction operation request and sending the user transaction operation request to a user creation service processing channel on a alliance chain system;
step A06, after the alliance chain system receives the user registration transaction request, a digital identity DID is constructed for the user through a DID construction function to serve as a unique identifier of the user on the chain;
step A07, a alliance chain system creates a contract container UserCreating;
step A08, constructing GRPC contract calling request, { method: createNewAccount, account_name: userDID, endorsement: peer1, peer2, peer 3..PeerN } and transmitting the message into contract container UserCreating through GRPC calling interface, contract container calling contract chain code in container to execute the request CreateNewAccount callback function, and storing new user result in local chain database, and returning successful result through GRPC new message;
step A09, broadcasting the user registration transaction in a user service processing channel by the alliance chain system, and waiting for all endorsement nodes to verify the user registration transaction to return;
and step A10, after all endorsement nodes verify that the user register transaction returns, or after the endorsement nodes reaching the set number verify that the user register transaction returns, creating an on-chain account for the user, distributing two public and private key pairs of the user, encrypting the public and private key pairs under the on-chain user ID name to generate a key and a private key file, and allowing the user to download the key file after the user verifies the identity. Specifically, after the user short message verification code is passed, the user code scanning downloading key file is provided through the IOT terminal.
It should be noted that, in step a06, the federation chain system constructs a digital identity DID for the user through the DID construction function, including the following steps:
step 1), calculating a hash value hash1 for a public key by using a hash algorithm;
step 2), taking the first 20 bytes of the hash1 as a hash2;
step 3), adding DID role type bytes (such as common users, admin users and the like) in front of the hash2 to obtain a hash3;
step 4), hash algorithm hash 4=sha-256 (hash 3) is used to calculate a hash value of hash3 to obtain hash4;
step 5), combining the first 4 bytes of the hash4 with the hash3 to generate a hash5;
step 6), encoding the hash5 by using a base64 encoding method to obtain the user DID.
In this embodiment, when the IOT terminal executes the warehouse order requirement function, the method includes the following steps:
b01, an IOT terminal constructs an online bill transaction demand form, and a user selects a bill ID, the number of the bill and a unit bill price for transaction purchase through the bill transaction demand form;
step B02, the IOT terminal obtains the payment amount of the warehouse purchased by the user; specifically, the IOT terminal generates a cash register, and the user can pay the amount by scanning the cash register;
step B03, the warehouse system receives the payment amount, and calculates the amount to generate a corresponding amount TOKEN; locking the TOKEN STATE in the warehouse transaction demand form, and waiting for the user to initiate purchase;
step B04, executing a preset contract by the IOT terminal to send an anonymous transaction Request: the anonymous transaction information comprises { user DID, transaction warehouse ID, warehouse number, transaction TOKEN number, transaction deadline, transaction fee TOKEN };
step B05, the bill system receives an anonymous transaction request through a RESTFUL SDK interface, a bill demand processing module of the bill system carries out form making, and the made form is submitted and released in a bill demand page of the IOT terminal and a transaction market module of the bill system; at this time, the buyer user selects the bill transaction through the transaction market, or the bill transaction system matches the bill of the buyer user through matching transaction, and the bill transaction flow is triggered.
In this embodiment, when the IOT terminal executes the bill transaction function, the method includes the following steps:
step C01, sending the issued warehouse bill transaction requirements of all users which can be checked by the user to the user through the IOT terminal;
step C02, the IOT terminal obtains the bill to be purchased selected by the user, and obtains the payment amount of the bill selected for transaction purchase by the user according to the real-time bill quotation IOT terminal; specifically, the IOT terminal generates a cash register, and the user can pay the amount by scanning the cash register;
and C03, calculating an equal amount TOKEN score by the warehouse bill system according to the payment amount actually paid by the user, and carrying out warehouse bill transaction user pairing according to a matching principle, wherein the pairing basis is as follows:
d=a when a is less than or equal to C; (if the previous bid price in the warehouse is higher than or equal to the bid price, then bid price = latest bid price)
When B is more than or equal to C, D=B; (the price of the price before the warehouse is lower than or equal to the price of the price, then the price of the price = price of the price
When B < C < a, d=c; (the price of the previous price in the warehouse is between the selling price and the buying price, then the latest price = the price of the previous price)
Step C04, matching to a proper warehouse sales user after matching is completed, and transmitting the matching result back to the IOT terminal of the purchasing user and the IOT terminal of the sales user through RESTFUL API; then entering the next step;
step C05, after locally verifying that TOKEN is more than or equal to the price under the purchase user name, initiating a transaction request and sending the transaction request to a warehouse bill system, otherwise, prompting the purchase user and the selling user to re-operate and confirm whether the transaction is performed;
step C06, after the bill system receives the transaction request, constructing transaction data { bill original user DID, bill transaction user DID on the chain, transferring the bill number, the price TOKEN, the transaction procedure TOKEN }, and then transmitting the transaction request to the alliance chain system through RESTFUL SDK;
step C07, the alliance chain system constructs transaction { transaction ID, user DID1, transaction data { { { warehouse original user DID, warehouse transaction user DID, assigned warehouse singular number, assigned price TOKEN, transaction procedure TOKEN1}, transaction TOKEN2, transaction user DID2}, transaction node signature 1};
as shown in fig. 3, step C08, the warehouse system initiates an aggregate signature proposal { proposal: transfer DID 1to DID2, warehouse receipt ID, warehouse receipt counts, TOKEN }, to the federation chain system, which requires that the transaction be agreed and authorized by at least three parties signing of trusted nodes in the federation, and the transaction can be initiated to the federation chain system, otherwise the transaction is withdrawn; after the proposal is initiated, the user waits for the authorization approval of the multiparty mechanism offline and waits for the operation warehouse bill transaction;
it should be noted that, the endorsement node of the alliance chain system may be constituted by a bill transaction mechanism, a notarization node of a transaction notarization department, a supervision mechanism, a bank, and the like. After each mechanism node receives the on-chain proposal request, when the three-party mechanism grants the proposal on the warehouse system, the signature of the transaction is aggregated into the signature of the mechanism node, and the transaction is updated and broadcasted;
after the aggregate signatures of all endorsement nodes are completed, the transaction is executed locally and stored on a local database. Otherwise, the transaction execution fails, the on-chain state database is not processed, and only the alliance chain system block historical database is updated;
it should be noted that, after receiving the aggregated signature proposal Q, the federation chain system executes the following steps:
the federation chain analyzes the content of the aggregated signature proposal Q, analyzes the participant nodes U1, U2..
One of the participant nodes Ui generates a public key pki=ski×g according to its own private key Ski, wherein G is a base point on an elliptic encryption curve (secp 256-k1 elliptic encryption curve), and broadcasts the public key Pki to the other participant nodes;
all the participant nodes calculate a public key list l=hash (pk1..pkn);
the method comprises the steps that a random number Ki is selected by a participant node Ui, ri=Ki G is calculated, and the random number Ri is broadcasted to other participant nodes;
the participant node Ui aggregates the random number r=r1+ & gt Rn;
the party node Ui calculates an aggregation public key p=hash (L, pk 1) ×pk1+,. Hash (L, pkn) ×pkn;
the participant node Ui computes the signature si=ki+hash (P, R, m) and broadcasts Si;
each of the other participant nodes calculates an aggregate signature s=s1+s2+ & gt.+ Sn, and the signature information (R, S) is the final signature result;
each party node verifies whether the elliptic encryption curve exists or not according to m, the public key list L and signature information (R, S), and deduces the S point: s x g= r+hash (P, R, m) x P; if yes, signature verification is successful, the aggregate signature proposal Q is passed, and the transaction is stored in a local database by each participant node; if not, the signature verification fails, the on-chain state database is not processed, and the alliance chain block historical database is updated.
Step C09, when the three-party signature agrees and authorizes, the bill transaction state of the user is switched from the waiting state to the transactable state by the bill transaction system; after the user selects to initiate transaction in a tradable state, entering the next step;
step C10, a transaction module of a warehouse system constructs an on-chain transaction request { transaction ID, user DID1, transaction data { { { warehouse original user DID, warehouse transaction user DID, assigned warehouse singular number, assigned price TOKEN, transaction procedure TOKEN1}, transaction TOKEN2, transaction user DID2}, transaction node signature 1, aggregate signature { node signature 1, node signature 2, node signature 3} }, and broadcasts to a alliance chain system;
the other endorsement nodes of the alliance chain system receive the request and add own signature on the transaction basis according to the endorsement policy, namely: { { bin original user DID, bin transaction user DID, assigned bin singular, assigned price TOKEN, transaction procedure TOKEN1}, transaction TOKEN2, transaction user DID2}, transaction node signature 1, aggregate signature { node signature 1, node signature 2, node signature 3}, { { bin original user DID, bin transaction user DID, assigned bin singular, assigned price TOKEN, transaction procedure TOKEN1}, transaction TOKEN2, transaction user DID2}, transaction node signature 2.
After the 2/3 nodes of the endorsement node on the chain pass the consensus, TOKEN of the transaction user DID1 will be transferred to the account name of the transaction user DID2 by the federation chain system restul API by calling the transaction contract of the bin list, the user DID1 is added with a { hold bin list, bin list number, goods ID } information, while its corresponding TOKEN and procedure TOKEN are deducted, while TOKEN under the name of DID2 is increased, the bin list under the name of DID2 is transferred to the record under the name of DID1, while 5% of the transaction procedure fee is charged to DID1 according to the number of TOKEN to be transferred. This bin record for DID2 is appended to the { sell bin list } for DID2 record, while the hold bin list for DID2 is deducted by the corresponding bin ID.
After the transaction is completed, the warehouse bill system makes the transaction which is completed into an electronic bill, and returns the electronic bill to the IOT terminals of the users of both sides of the transaction through REST API SDK for the users to download.
In this embodiment, when the IOT terminal executes the bill transaction transfer function, the method includes the following steps:
step D01, obtaining the DID number of the assigned user input by the assignment user at the IOT terminal and { item ID, item number, item unit price };
step D02, the warehouse system searches the DID number of the assigned user, if the DID number exists, the next step is carried out, and if the DID number does not exist, the transaction failure is returned;
step D03, executing step C10, wherein the step C is executed without deducting the hand TOKEN.
After the transaction is completed, the warehouse bill system makes the transaction which is completed into an electronic bill, and returns the electronic bill to the IOT terminals of the users of both sides of the transaction through REST API SDK for the users to download.
It should be noted that, the transaction transfer belongs to the directed bill transfer transaction among the DID users, and is mainly responsible for being cooperatively completed by the bill transfer module. The transfer of the brands involves TOKEN transfer and branding ownership transfer for the user, unlike the branding trading market, which pertains to both user and user-oriented trading, and therefore does not deduct additional fees.
In this embodiment, when the IOT terminal executes the warehouse list mortgage function, the method includes the following steps:
e01, acquiring { item IDs, item numbers and item unit prices } which are held by a warehouse bill mortgage user when the IOT terminal initiates a loan financing application;
e02, after the check (manual check) of the warehouse bill system is passed, sending a sign 'warehouse bill mortgage loan agreement' needing to be signed to a user on line by an IOT terminal; after encrypting the agreement and signing by ECDSA, the warehouse system initiates a transaction to the alliance chain system, stores the transaction in the chain storage under the DID name of the user, broadcasts and agrees with the full chain endorsement node and confirms;
e03, returning to the IOT terminal after transaction confirmation, and changing the mortgage state of the front-end user from the to-be-checked state to the mortgage-possible state; after submitting the mortgage confirmation, the user can wait for the bank to pay;
and E04, after the bank paying is finished, the bank system informs a bill system through a short message and/or a mail, and the bill system constructs a transaction contract anonymous transaction Request: the anonymous transaction information includes { user DID, mortgage ticket ID, number of tickets, ticket TOKEN, redemption deadline, transaction fee TOKEN }; initiating an aggregate signature proposal by a warehouse bill system, waiting for all endorsement nodes to pass and signing the aggregate signature proposal;
e05, agreeing to aggregate signature proposal execution and broadcasting transaction after all endorsement nodes receive and aggregate the self signatures into transaction signatures; after the aggregated signature proposal is completed, the alliance chain system updates the state data of the user DID, adds the mortgage state information of the user in the record, namely, the mortgage is successful, and associates the hash value of the transaction in the record;
and E06, the alliance chain system transfers the consignment right to the bank ID name by calling the consignment mortgage contract.
After the mortgage is successful, the transaction hash and the transaction result are returned to the bill system, and the bill system short message and/or mail is used for notifying the user of the bill due redemption time, if the user does not release the mortgage and returns the collateral deposit for a long time, the bill system can update the state of the constructed bill, and the user's mortgage releasing operation is frozen; the short message is sent to inform the bank that the bill of goods is in an out-of-date state, and the bank can determine whether to initiate the bill of goods picking process according to the short message.
In this embodiment, when the IOT terminal executes the warehouse bill picking function, the method includes the following steps:
step F01, acquiring { item ID, item number }, to be mentioned, provided by a user initiating a bill of goods picking at an IOT terminal;
step F02, confirming the bin number by a bin bill system and inquiring the bin number of a bin management library of a background of the alliance chain system by the bin bill system, and inputting a user ID, a goods ID and the number of goods by initiating a bin management state updating transaction to the alliance chain system;
the alliance chain system calls the goods-picking contract to decrement the goods-picking amount under the user name, starts the expiration time-out processing contract and returns the result and the time-out contract ID to the warehouse system. The transaction system informs the IOT terminal to print and issue a delivery bill of lading through a RESTUL API SDK interface, and informs a user of carrying out lading to a specified warehouse before the deadline through a short message mail;
in practice, the pick-up process has been done before expiration: the IOT terminal scans the two-dimension code of the bill of lading, executes expiration transaction, transmits in user ID and the STATUS of the delivered goods, and the contract updates the STATUS of the user bill of lading to [ not mortgage ], registers the time of the bill of lading and updates to the alliance chain system; expiration of the non-pick-up process: automatically triggering the contract to automatically roll back after expiration, updating the user warehouse receipt status, re-rolling the user goods-lifting asset back to the record of the alliance chain system, registering the user status as not being picked up and updated to the alliance chain system, and starting a short message and a mail to inform the user to initiate the goods-lifting process again.
In this embodiment, when the IOT terminal executes the warehouse entry query function, the method includes the following steps: the user can initiate self-service bill inquiry on the bill system, and the bill system returns bill information to the IOT terminal by calling the interface API stored on the back end chain of the alliance chain system.
The bin list information is as follows:
(subsequent)
(subsequent)
The foregoing description is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and any simple modification, variation and equivalent structural changes made to the above embodiment according to the technical substance of the present invention still fall within the scope of the technical solution of the present invention.
Claims (5)
1. An electronic warehouse information alliance chain system, which is characterized in that: the system comprises an IOT terminal, a warehouse system and a alliance chain system;
the IOT terminal is used for a user to initiate a bill operation request to the bill system;
the warehouse receipt system is used for constructing a corresponding on-chain transaction request sending alliance chain system after receiving a warehouse receipt operation request of a user;
after receiving the on-chain transaction request, the alliance chain system executes corresponding transaction operation;
the IOT terminal is configured with a bill opening function, a bill demand function, a bill transaction transfer function, a bill mortgage function, a bill picking function and/or a bill history inquiry function;
when the IOT terminal executes the warehouse receipt opening function, the method comprises the following steps:
a01, the IOT terminal collects user information and uploads the user information to a warehouse bill system for auditing; the user information includes, but is not limited to, face recognition information, fingerprint recognition information, user's corporate legal information, user's business information business license, user's corporate credit information, user's corporate risk information;
step A02, after the user information is checked and checked, the warehouse bill system sends a notification result to the user, notifies the user in a short message or mail mode, and sends a risk agreement to the user, and after the user signs, the signed risk agreement can be uploaded through the IOT terminal;
a03, the IOT terminal sends the signed risk agreement uploaded by the user to a warehouse bill system for checking again;
step A04, after the risk agreement is checked and approved by the warehouse bill system, serializing the text of the risk agreement, signing by ECDSA (elliptic curve digital signature algorithm), and taking the encrypted string as an information abstract m; and then a set of random numbers k, k E [1, n-1 ] in the value domain are generated]The method comprises the steps of carrying out a first treatment on the surface of the Selecting a base point G on the elliptic curve, and obtaining a point KG= (X1, Y1) coordinate by a point multiplication method; calculating r=x1 mod n, where n is the k maximum boundary +1; r is a non-zero integer; encrypting the information abstract: calculating a message digest content hash e=sha-256 (m); finally, s value s=k is calculated -1 (e+pk x r) mod n, where PK is the private key held by the policy administrator and s is a non-zero value;
step A05, obtaining a signature pair (r, s) through the last step, sending a signature value into a user transaction operation request and sending the user transaction operation request to a user creation service processing channel on a alliance chain system;
step A06, after the alliance chain system receives the user registration transaction request, a digital identity DID is constructed for the user through a DID construction function to serve as a unique identifier of the user on the chain;
step A07, a alliance chain system creates a contract container UserCreating;
step A08, constructing GRPC contract calling request, { method: createNewAccount, account_name: userDID, endorsement: peer1, peer2, peer 3..PeerN } and transmitting the message into contract container UserCreating through GRPC calling interface, contract container calling contract chain code in container to execute the request CreateNewAccount callback function, and storing new user result in local chain database, and returning successful result through GRPC new message;
step A09, broadcasting the user registration transaction in a user service processing channel by the alliance chain system, and waiting for all endorsement nodes to verify the user registration transaction to return;
and step A10, after all endorsement nodes verify that the user register transaction returns, or after the endorsement nodes reaching the set number verify that the user register transaction returns, creating an on-chain account for the user, distributing two public and private key pairs of the user, encrypting the public and private key pairs under the on-chain user ID name to generate a key and a private key file, and allowing the user to download the key file after the user verifies the identity.
2. An electronic warehouse information alliance chain system according to claim 1, wherein:
the alliance chain system constructs a digital identity DID for a user through a DID construction function, comprising the following steps:
calculating a hash value hash1 for the public key by using a hash algorithm;
taking the first 20 bytes of the hash1 as a hash2;
adding DID role type bytes in front of the hash2 to obtain a hash3;
hash algorithm hash 4=sha-256 (hash 3) is used, and a hash value is calculated by the hash3 to obtain hash4;
combining the first 4 bytes of the hash4 with the hash3 to generate a hash5;
and encoding the hash5 by using a base64 encoding method to obtain the user DID.
3. An electronic warehouse information alliance chain system according to claim 1, wherein: the bill handling request includes a bill transaction request, and the bill system performs the following steps after receiving the bill transaction request:
the bill system builds on-chain transaction data according to the bill transaction request, and sends the bill transaction request and the on-chain transaction data to the alliance chain system;
the alliance chain system constructs a transaction according to the warehouse bill transaction request and the transaction data on the chain;
the warehouse system initiates an aggregate signature proposal Q to the alliance chain system, and after the aggregate signature proposal Q is signed, the transaction is in an executable state.
4. An electronic warehouse information alliance chain system according to claim 3, wherein: and when the transaction is in an executable state, the warehouse system informs a user through the IOT terminal, and after the user confirms to execute the transaction at the IOT terminal, the alliance chain system executes the transaction.
5. An electronic warehouse information alliance chain system according to claim 4, wherein: after receiving the aggregate signature proposal Q, the alliance chain system executes the following steps:
the federation chain analyzes the content of the aggregated signature proposal Q, analyzes the participant nodes U1, U2..
One of the participant nodes Ui generates a public key pki=ski×g according to its own private key Ski, wherein G is a base point on the elliptic encryption curve, and the public key Pki is broadcasted to the other participant nodes;
all the participant nodes calculate a public key list l=hash (pk1..pkn);
the method comprises the steps that a random number Ki is selected by a participant node Ui, ri=Ki G is calculated, and the random number Ri is broadcasted to other participant nodes;
the participant node Ui aggregates the random number r=r1+ & gt Rn;
the party node Ui calculates an aggregation public key p=hash (L, pk 1) ×pk1+,. Hash (L, pkn) ×pkn;
the participant node Ui computes the signature si=ki+hash (P, R, m) and broadcasts Si;
each of the other participant nodes calculates an aggregate signature s=s1+s2+ & gt.+ Sn, and the signature information (R, S) is the final signature result;
each party node verifies whether the elliptic encryption curve exists or not according to m, the public key list L and signature information (R, S), and deduces the S point: s x g= r+hash (P, R, m) x P; if so, the signature verification is successful and the aggregate signature proposal Q is passed, the transaction being stored by each participant node in a local database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110435743.1A CN113159682B (en) | 2021-04-22 | 2021-04-22 | Electronic warehouse information alliance chain system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110435743.1A CN113159682B (en) | 2021-04-22 | 2021-04-22 | Electronic warehouse information alliance chain system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113159682A CN113159682A (en) | 2021-07-23 |
| CN113159682B true CN113159682B (en) | 2023-05-05 |
Family
ID=76869721
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110435743.1A Active CN113159682B (en) | 2021-04-22 | 2021-04-22 | Electronic warehouse information alliance chain system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113159682B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114511325B (en) * | 2022-04-19 | 2022-07-15 | 北京思特奇信息技术股份有限公司 | Block chain-based emergency transaction method and system |
| CN114581243B (en) * | 2022-05-09 | 2022-09-23 | 南京金宁汇科技有限公司 | Asynchronous callback processing method and system for multi-channel transaction certificate |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109858908A (en) * | 2019-01-09 | 2019-06-07 | 暨南大学 | Alliance's chain building method, method of commerce and distributed supply chain system |
| CN112131228A (en) * | 2020-09-29 | 2020-12-25 | 上海卓钢链科技有限公司 | FABRIC-based alliance chain system convenient for data retrieval |
| CN112214502A (en) * | 2020-08-28 | 2021-01-12 | 迅鳐成都科技有限公司 | User contract deployment method, device, system and storage medium of alliance chain |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109727133A (en) * | 2018-12-29 | 2019-05-07 | 杭州趣链科技有限公司 | A kind of electronics warehouse receipt transaction system and method based on block chain |
| CN109639714B (en) * | 2019-01-02 | 2021-06-15 | 浙江师范大学 | Internet of things identity registration and verification method based on block chain |
| CN109936569B (en) * | 2019-02-21 | 2021-05-28 | 领信智链(北京)科技有限公司 | Decentralized digital identity login management system based on Ether house block chain |
| CN110322246A (en) * | 2019-07-09 | 2019-10-11 | 深圳市网心科技有限公司 | A kind of optimization method and relevant device of block chain Transaction Information |
| CN111553792A (en) * | 2020-03-24 | 2020-08-18 | 平安科技（深圳）有限公司 | Data verification method and device based on block chain |
-
2021
- 2021-04-22 CN CN202110435743.1A patent/CN113159682B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109858908A (en) * | 2019-01-09 | 2019-06-07 | 暨南大学 | Alliance's chain building method, method of commerce and distributed supply chain system |
| CN112214502A (en) * | 2020-08-28 | 2021-01-12 | 迅鳐成都科技有限公司 | User contract deployment method, device, system and storage medium of alliance chain |
| CN112131228A (en) * | 2020-09-29 | 2020-12-25 | 上海卓钢链科技有限公司 | FABRIC-based alliance chain system convenient for data retrieval |
Non-Patent Citations (1)
| Title |
|---|
| 基于区块链的可信仓单系统设计;周元健等;《信息网络安全》(第第6期期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113159682A (en) | 2021-07-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11250507B2 (en) | Trusted tokenized transactions in a blockchain system | |
| US20220156738A1 (en) | Methods and systems of using a cryptocurrency system to manage payments and payment alternatives | |
| CN106982205B (en) | Block chain-based digital asset processing method and device | |
| CN105373955B (en) | Digital asset processing method and device based on multiple signatures | |
| CN103413389B (en) | Based on bank account to non-banking account management and method of payment | |
| CN106952094A (en) | Electronic bill management method and device | |
| US20190311343A1 (en) | Point of sale system network with distributed ownership record database | |
| US20140089117A1 (en) | Secure Escrow Transaction System | |
| CN113159682B (en) | Electronic warehouse information alliance chain system | |
| EP3918505A2 (en) | Point-to-point distributed decentralized system | |
| JP6457391B2 (en) | Method and system for distributing data streams | |
| CN104021492A (en) | On-line purchasing method for protecting secretes of customer and system thereof | |
| CN112163954B (en) | Transaction method and device based on block chain | |
| WO2019227345A1 (en) | Method and system for managing maintenance and repair plant and data management server | |
| CN112513904B (en) | Digital asset transaction control method, device, terminal equipment and storage medium | |
| US20020174075A1 (en) | System & method for on-line payment | |
| US20210133701A1 (en) | Proxied cross-ledger authentication | |
| CN111311277B (en) | Bill processing method and device based on block chain network and related equipment | |
| KR102329779B1 (en) | System for investing contents using crypto-currency based on blockchain and method thereof | |
| CN115564414A (en) | Digital currency double-off-line transaction method and system | |
| US7257554B1 (en) | Anonymous purchases while allowing verifiable identities for refunds returned along the paths taken to make the purchases | |
| CN112651727B (en) | On-site shopping payment replacing method, acquirer server and system | |
| KR101045241B1 (en) | System and method for authenticating seller using credit card system | |
| CN114298698A (en) | Transaction settlement method and device | |
| KR102398641B1 (en) | System for providing card payment agent service and method performing thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |