Blockchain-based Digital Warehouse Receipt Management Method, Device, and Electronic Equipment

Abstract

An embodiment of the present application provides a digital warehouse receipt management method, device, and electronic device based on a blockchain. The method includes: receiving a first call transaction sent by a fund provider after a warehouse receipt pledge application is initiated by a cargo owner; in response to the first call transaction, generating a digital warehouse receipt inventory data module and determining whether the pledged goods of the digital warehouse receipt are consistent with the goods inventory data; if so, generating a property right information module for the goods corresponding to the digital warehouse receipt and determining whether the ownership of the pledged goods is clear; if so, further determining whether the pledged goods corresponding to the pledged goods actually exist based on the offline Internet of Things device corresponding to the digital warehouse receipt; if so, modifying the status of the digital warehouse receipt pledged goods stored in the blockchain to the pledged status, so that when the fund provider determines that the digital warehouse receipt is modified to the pledged status, the goods corresponding to the digital warehouse receipt are used as pledges to provide financing to the cargo owner.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of Internet technologies, and in particular, to a digital warehouse receipt management method, device, and electronic device based on a blockchain. Background Art

[0002] Blockchain technology, also known as distributed ledger technology, is a new technology in which several computing devices jointly participate in "recording accounts" and jointly maintain a complete distributed database. Due to the characteristics of blockchain technology such as decentralization, openness and transparency, each computing device can participate in database records, and data synchronization can be quickly performed between computing devices, blockchain technology has been widely applied in many fields. Summary of the Invention

[0003] A digital warehouse receipt management method, device, and electronic device based on a blockchain provided by the embodiments of this specification:

[0004] According to a first aspect of the embodiments of this specification, a digital warehouse receipt management method based on a blockchain is provided. Digital warehouse receipts are stored in the blockchain. The digital warehouse receipt is an asset certificate corresponding to goods generated after the goods owner stores the goods in the warehouse keeper and initiates a pledge application. The method includes:

[0005] Receiving a first call transaction sent by a fund provider after the goods owner initiates a warehouse receipt pledge application; wherein, the first call transaction includes a digital warehouse receipt pledge goods module generated by the goods owner's pledge application;

[0006] In response to the first call transaction, invoking the warehouse receipt authenticity verification logic declared in the smart contract published on the blockchain, generating a digital warehouse receipt inventory data module, and determining whether the pledged goods of the digital warehouse receipt are consistent with the goods inventory data;

[0007] If so, invoking the management logic declared in the blockchain smart contract, generating a goods ownership information module for the goods corresponding to the digital warehouse receipt, and determining whether the ownership of the pledged goods is clear;

[0008] If so, further determining whether the pledged goods corresponding to the digital warehouse receipt actually exist based on the offline Internet of Things device corresponding to the digital warehouse receipt;

[0009] If so, invoking the status modification logic declared in the smart contract to modify the goods status of the digital warehouse receipt stored in the blockchain to the pledged status, so that when the fund provider determines that the pledged goods in the digital warehouse receipt are modified to the pledged status, the goods corresponding to the digital warehouse receipt are used as pledges to provide financing to the goods owner.

[0010] Optionally, determining whether the pledged goods of the digital warehouse receipt are consistent with the goods inventory data includes:

[0011] Obtaining the goods inventory data corresponding to the shipper party that is stored on the chain by the warehouse keeper's warehouse management system through the API interface;

[0012] Obtaining the goods information for the pledge application to the financier party that is stored on the chain by the shipper party;

[0013] Verifying and validating the goods information for the pledge application with the goods inventory data to determine that the pledged goods of the digital warehouse receipt are truly consistent with the goods inventory data.

[0014] Optionally, determining whether the goods corresponding to the digital warehouse receipt actually exist based on the offline Internet of Things device corresponding to the digital warehouse receipt includes:

[0015] Determining the storage space location corresponding to the digital warehouse receipt stored on the blockchain, and sending the communication parameters of the offline Internet of Things device associated with the storage space location to the financier party; so that the financier party establishes a connection with the offline Internet of Things device based on the communication parameters, and determines whether the goods are located in the storage space managed by the warehouse keeper based on the monitoring data transmitted by the offline Internet of Things device.

[0016] Optionally, the method further includes:

[0017] When it is determined that the digital warehouse receipt is stored on the blockchain, obtaining the goods status corresponding to the digital warehouse receipt. If the goods status corresponding to the digital warehouse receipt is pledged, returning a digital warehouse receipt exception notice to the financier party so that the financier party suspends the pledge of the goods corresponding to the digital warehouse receipt.

[0018] Optionally, the method further includes:

[0019] Receiving a second call transaction sent by the warehouse keeper; where the second call transaction includes the warehouse keeper of the goods and the goods of the shipper party;

[0020] In response to the second call transaction, when the shipper party initiates a goods pledge application to the financier party, invoking the digital warehouse receipt inventory data generation logic declared in the smart contract to generate a to-do event for the goods corresponding to the warehouse keeper. After the warehouse keeper obtains the to-do event in the blockchain, automatically submitting the goods inventory data to the smart contract through the API interface; the smart contract summarizes the inventory data and generates an inventory data module for the digital warehouse receipt corresponding to the goods and updates and stores the digital warehouse receipt to the blockchain.

[0021] Optionally, the method further includes:

[0022] Receive the third call transaction sent by the consignor party, where the third call transaction includes a proof document representing the ownership of the goods submitted by the consignor party of the goods;

[0023] In response to the third call transaction, call the digital warehouse receipt goods right information module generation logic declared in the smart contract, generate the goods information module of the digital warehouse receipt after depositing the proof document on the blockchain, and update and deposit the digital warehouse receipt to the blockchain.

[0024] Optionally, the method further includes:

[0025] Receive the fourth call transaction sent by the warehousing party after the pledged goods of the consignor party are out of storage; where the fourth call transaction includes the out-of-storage data of the goods;

[0026] In response to the fourth call transaction, call the out-of-storage logic declared in the smart contract, after the fund party approves the out-of-storage, deposit the out-of-storage data on the blockchain, update the inventory data module of the digital warehouse receipt corresponding to the goods, and update and deposit the digital warehouse receipt to the blockchain.

[0027] Optionally, the method further includes:

[0028] Receive the fifth call transaction sent by the quality inspection party after inspecting the pledged goods; where the fifth call transaction includes the quality inspection information of the pledged goods;

[0029] In response to the fifth call transaction, call the digital warehouse receipt pledged goods generation logic declared in the smart contract, deposit the quality inspection information on the blockchain, update the pledged goods module of the digital warehouse receipt, and update and deposit the digital warehouse receipt to the blockchain.

[0030] Optionally, the method further includes:

[0031] Receive the sixth call transaction sent by the warehousing party; where the sixth call transaction includes the inventory data of the warehousing party for the pledged goods;

[0032] In response to the sixth call transaction, call the digital warehouse receipt inventory data generation logic declared in the smart contract, update the digital warehouse receipt inventory data module based on the inventory data of the pledged goods, and determine whether the data is consistent with the quantity of the pledged goods;

[0033] If the quantity of the pledged goods in the digital warehouse receipt is inconsistent with the inventory data after the inventory data is updated, send an alarm to the fund party.

[0034] Optionally, the method further includes:

[0035] Receive the seventh invocation transaction sent by the warehousing party; wherein, the seventh invocation transaction includes monitoring data related to the goods collected by offline Internet of Things devices;

[0036] In response to the seventh transfer transaction, invoke the management logic declared in the smart contract, and determine whether there are potential safety hazards for the pledged goods corresponding to the digital warehouse receipt based on the monitoring data;

[0037] When there are potential safety hazards for the pledged goods, send an alarm to the fund provider.

[0038] Optionally, the offline Internet of Things device includes an environmental sensor, and the monitoring data includes environmental data of the warehousing space collected by the environmental sensor;

[0039] The determining whether there are potential safety hazards for the pledged goods based on the monitoring data includes:

[0040] Judge whether the environmental data reaches the dangerous condition; if it reaches, determine whether there are potential safety hazards for the goods.

[0041] Optionally, the environmental data includes at least one of temperature, humidity, dust concentration, and concentration of dangerous gases.

[0042] According to the second aspect of the embodiments of the present specification, a digital warehouse receipt management device based on a blockchain is provided. The digital warehouse receipt is stored in the blockchain. The digital warehouse receipt is an asset certificate corresponding to the goods generated after the goods owner stores the goods in the warehousing party and initiates a pledge application. The device includes:

[0043] A receiving unit that receives a first invocation transaction sent by a fund provider after the goods owner initiates a warehouse receipt pledge application; wherein, the first invocation transaction includes a digital warehouse receipt pledged goods module generated by the goods owner's pledge application;

[0044] A response unit that, in response to the first invocation transaction, invokes the warehouse receipt verification logic declared in the smart contract published on the blockchain, generates a digital warehouse receipt inventory data module, and determines whether the pledged acquisition and inventory data of the digital warehouse receipt are consistent;

[0045] A judgment unit that, if so, invokes the management logic declared in the blockchain smart contract, generates a goods ownership information module for the goods corresponding to the digital warehouse receipt, and judges whether the ownership of the pledged goods is clear;

[0046] A determination unit that, if so, further determines whether the pledged goods corresponding to the digital warehouse receipt actually exist based on the offline Internet of Things device corresponding to the digital warehouse receipt;

[0047] The management unit, if so, invokes the state modification logic declared in the smart contract to modify the goods status of the digital warehouse receipt stored in the blockchain to the pledged status, so that when the financier determines that the pledged goods in the digital warehouse receipt are modified to the pledged status, the goods corresponding to the digital warehouse receipt are used as collateral to provide financing to the goods owner party.

[0048] According to the third aspect of the embodiments of the present specification, an electronic device is provided, including:

[0049] A processor;

[0050] A memory for storing instructions executable by the processor;

[0051] Wherein, the processor is configured to perform any of the above blockchain-based digital warehouse receipt management methods.

[0052] In the above technical solutions, the goods corresponding to the digital warehouse receipt are monitored in real time based on the offline Internet of Things devices carried by the warehousing party, and the goods status is maintained based on the smart contract corresponding to the digital warehouse receipt deployed on the blockchain; on the one hand, the circulation efficiency and information transparency of the digital warehouse receipt are improved; on the other hand, the potential safety hazards in each business link related to the digital warehouse receipt are reduced, and a reliable guarantee is provided for the transfer of rights and interests in the process of warehouse receipt pledge. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 is a networking schematic diagram of a digital warehouse receipt management system built based on a blockchain network provided by an embodiment of the present specification;

[0054] Figure 2 is a flowchart of a method for managing warehouse receipt data based on blockchain provided by an embodiment of the present specification;

[0055] Figure 3 is a structural schematic diagram of an electronic device provided by an embodiment of the present specification;

[0056] Figure 4 is a block diagram of a warehouse receipt data management device provided by an embodiment of the present specification. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0057] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present specification. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present specification as detailed in the appended claims.

[0058] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a", "the", and "said" used in this specification and the appended claims are also intended to include the plural forms unless the context clearly dictates otherwise. It should 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.

[0059] It should be understood that although the terms first, second, etc. may be used in this specification to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to a determination".

[0060] For the convenience of understanding, the basic concepts related to blockchain are briefly introduced here first.

[0061] The blockchain described in this specification may specifically include a private chain, a public chain, a consortium chain, etc., which are not particularly limited in this specification. The node devices in the blockchain can be added without limitation, and each node device can synchronize a system time to ensure the timeliness of the execution of smart contracts.

[0062] It should be noted that the transaction (Transaction) described in this specification refers to a piece of data created through the client of the blockchain and finally published to the data storage system of the blockchain.

[0063] Transactions in the blockchain generally have a distinction between a narrow sense and a broad sense. A narrow-sense transaction refers to a value transfer issued by a user to the blockchain; for example, in the traditional Bitcoin blockchain network, a transaction can be a transfer initiated by a user in the blockchain. A broad-sense transaction refers to a piece of business data with a business intention issued by a user to the blockchain; for example, an operator can build a consortium chain based on actual business needs and deploy some other types of online services unrelated to value transfer (such as, broadly divided into query services, call services, etc.) on the consortium chain, and in such a consortium chain, a transaction can be a business message or business request with a business intention issued by a user in the consortium chain.

[0064] The above-mentioned client can include any type of upper-layer application that uses the underlying business data stored in the blockchain as data support to implement specific business functions.

[0065] Please refer to Figure 1 ,Figure 1 This is a network diagram of a digital warehouse receipt management system based on blockchain shown in this specification.

[0066] In the network environment as Figure 1 shown, it may include client-side computing devices 101, a server-side 102, and at least one blockchain system; for example, blockchain systems 103, 104, and 105.

[0067] In one implementation, the client-side computing device 101 may include various different types of client-side computing devices; for example, the client-side terminal devices may include, such as, PC terminal devices, mobile terminal devices, Internet of Things devices, and other forms of intelligent devices with certain computing capabilities, and so on.

[0068] In one implementation, at least some of the computing devices in the client-side terminal device 101 may be coupled to the server-side 102 through various communication networks; for example, Figure 1 the device 3 shown in is coupled to the server-side 102.

[0069] It is not difficult to understand that some of the terminal devices in the client-side terminal device 101 may not be coupled to the server-side 102, but directly coupled to the blockchain system as blockchain nodes through various communication networks; for example, Figure 1 the device 4 shown in can be coupled to the blockchain system as a blockchain node.

[0070] Among them, the above communication network may include wired and / or wireless communication networks; for example, it may be a local area network (LAN), wide area network (WAN), Internet, or a combination thereof implemented based on a wired access network or wireless access network (such as a mobile cellular network) provided by an operator.

[0071] In one implementation, the client-side computing device 101 may further include one or more user-side servers; for example, Figure 1 the device 5 shown in. At least some of the computing devices in the client-side terminal device 101 may be coupled to the user-side server, and the user-side server may be further coupled to the above server-side 102; for example, Figure 1 the devices 1 and 2 shown in are coupled to the device 5, and the device 5 is further coupled to the server-side 102.

[0072] In one implementation, the above user-side server may be implemented by a service entity that has built a user account system; the above service entity may include an operating entity of a service carrier that provides various online and / or offline services to users;

[0073] Among them, the above service carriers may include service carriers in the form of software or in the form of hardware.

[0074] In one implementation, the above service carriers may include various client software that provides online Internet services; for example, websites, web pages, APPs, etc. Among them, when the client software is an APP, the APP may specifically be a Decentralized Application (DAPP) to cooperate with the blockchain system.

[0075] In one implementation, the above service carriers may also include various intelligent devices deployed offline that can provide offline services.

[0076] Correspondingly, the above operation entities may include the operators corresponding to the above service carriers; for example, the above operation entities may include individuals, organizations, companies, and enterprises that operate and manage the above service carriers, and so on.

[0077] In one implementation, the server side 102 may also be coupled to one or more blockchain systems through various communication networks; for example, Figure 1 the server side 102 shown in may be respectively coupled to the blockchain system 103, the blockchain system 104, and the blockchain system 105, and so on.

[0078] In one implementation, each blockchain system may maintain one or more blockchains (for example, public blockchains, private blockchains, consortium blockchains, etc.), and include multiple blockchain nodes for hosting the above one or more blockchains; for example, as Figure 1 the blockchain nodes 1, blockchain node 2, blockchain node 3, blockchain node 4, blockchain node i, etc. shown in may jointly host one or more blockchains. Cross-chain data access may also be performed between the blockchains included in each blockchain system and between each blockchain system.

[0079] In one implementation, the blockchain nodes may include full nodes and light nodes. The full nodes may download all the blockchain transactions included in each block in the blockchain in full, and may perform consensus verification on the blockchain transactions included in each blockchain according to the blockchain consensus algorithm carried.

[0080] The light nodes may not download the complete blockchain, but may only download the block header data of each block in the blockchain, and use the data included in the block header as the verification root to verify the authenticity of the blockchain transactions. The light nodes may rely on the full nodes to access more functions of the blockchain.

[0081] For example,Figure 1 Each blockchain node in the blockchain system 103 shown can be a full node; and Figure 1 the device 4 directly coupled to the blockchain system shown can be a light node and attach to each full node in the blockchain system 103.

[0082] In one implementation, a blockchain node can be a physical device or a virtual device implemented in a server or a server cluster; for example, the blockchain node device can be a physical host in a server cluster or a virtual machine created after virtualizing the hardware resources carried by a server or a server cluster based on virtualization technology. Each blockchain node can be coupled together through various types of communication methods (such as TCP / IP) to form a network to carry one or more blockchains.

[0083] In one implementation, the server side 102 can include a BaaS platform (also referred to as BaaS cloud) for providing blockchain as a service (BaaS). The BaaS platform can provide simple, easy-to-use, one-click deployable, quickly verifiable, and flexibly customizable blockchain services to the client-side computing devices coupled to the BaaS platform by providing pre-written software for activities occurring on the blockchain (such as subscriptions and notifications, user authentication, database management, and remote updates), thereby accelerating the development, testing, and launch of blockchain business applications and facilitating the implementation of blockchain commercial application scenarios in various industries.

[0084] For example, in one example, the BaaS platform can provide software such as an MQ (Message Queue) service; the client-side computing device coupled to the BaaS platform can subscribe to the contract events generated on a blockchain deployed on a certain blockchain in the blockchain system coupled to the BaaS platform after the smart contract is triggered and executed; and the BaaS platform can listen to the events generated on the blockchain after the smart contract is triggered and executed, and then add the contract events to the message queue in the form of notification messages based on the software related to the MQ service, so that the client-side computing device subscribing to the message queue can obtain notifications related to the above contract events.

[0085] In one implementation, the BaaS platform can also provide enterprise-level platform services based on blockchain technology to help enterprise-level customers build a secure and stable blockchain environment and easily manage the deployment, operation, maintenance, and development of the blockchain.

[0086] For example, in one example, the BaaS platform can implement rich security policies and multi-tenant isolation environments based on cloud technology, provide advanced security protection based on chip encryption technology, and provide end-to-end high-availability services that can be quickly scaled without interruption based on highly reliable data storage;

[0087] In another example, enhanced management functions can also be provided to help customers build an enterprise-level blockchain network environment; and, local support can also be provided for standard blockchain applications and data, supporting mainstream open-source blockchain technologies such as Hyperledger Fabric and Enterprise Ethereum - Quorum to build an open and inclusive technology ecosystem.

[0088] The following combines Figure 2 to introduce an embodiment of the method for managing digital warehouse receipts based on blockchain in this specification. The method includes:

[0089] Step 210: Receive a first call transaction sent by the fund provider after the warehouse receipt pledge application is initiated by the cargo owner. Among them, the first call transaction includes a digital warehouse receipt pledge goods module generated by the cargo owner's pledge application;

[0090] Step 220: In response to the first call transaction, call the warehouse receipt authenticity verification logic declared in the smart contract published on the blockchain, generate a digital warehouse receipt inventory data module, and determine whether the pledged goods of the digital warehouse receipt are consistent with the goods inventory data;

[0091] Step 230: If so, call the management logic declared in the blockchain smart contract, generate a goods ownership information module for the goods corresponding to the digital warehouse receipt, and determine whether the ownership of the pledged goods is clear;

[0092] Step 240: If so, further determine whether the pledged goods corresponding to the digital warehouse receipt actually exist based on the offline Internet of Things devices corresponding to the digital warehouse receipt;

[0093] Step 250: If so, call the status modification logic declared in the smart contract to modify the goods status of the digital warehouse receipt stored on the blockchain to the pledged status, so that when the fund provider determines that the pledged goods in the digital warehouse receipt are modified to the pledged status, the goods corresponding to the digital warehouse receipt are used as pledges to provide financing to the cargo owner.

[0094] This embodiment can be applied to the Figure 1 digital warehouse receipt management system shown above. For example, the blockchain can include a blockchain network constructed with blockchain nodes such as fund providers, cargo owners, warehousing parties, and quality inspection parties.

[0095] For another example, the capital provider, the goods owner, the warehouser, and the quality inspector can be coupled to the server 102, and the server 102 can send the transactions among the capital provider, the goods owner, the warehouser, and the quality inspector to the blockchain. In this way, in terms of the system architecture, there is no need to transform the existing APP. Based on the existing client-server architecture, relevant functions can be realized by connecting the server to the blockchain.

[0096] In this specification, the above digital warehouse receipt may refer to an asset certificate corresponding to the goods generated after the goods owner stores the goods in the warehouser and initiates a pledge application. And the digital warehouse receipt is generated and stored on the blockchain.

[0097] The following embodiments are used to introduce how the digital warehouse receipt stored on the blockchain is generated:

[0098] In an illustrated embodiment, the digital warehouse receipt can be generated after the goods owner actively applies to the blockchain. Specifically:

[0099] After the goods of the goods owner are stored in the warehouser and a pledge application is initiated, the goods owner can actively send a third call transaction to the blockchain;

[0100] The node device of the blockchain receives the third call transaction sent by the goods owner; wherein, the third call transaction includes the proof documents submitted by the goods owner representing the ownership of the goods;

[0101] In response to the third call transaction, the digital warehouse receipt goods right information module generation logic declared in the smart contract is called to generate the goods information module of the digital warehouse receipt after the proof documents are stored on the blockchain, and the digital warehouse receipt is updated and stored on the blockchain.

[0102] Through this embodiment, the blockchain can, in response to the requirement of the goods owner to actively apply for generating a digital warehouse receipt, generate and store a unique digital warehouse receipt corresponding to the goods after obtaining the proof documents submitted by the goods owner representing the ownership of the goods. Since the data in the blockchain has the characteristic of being immutable, the digital warehouse receipt cannot be modified after being stored, which can ensure the security and reliability of the digital warehouse receipt corresponding to the goods.

[0103] In an illustrated embodiment, the digital warehouse receipt can be automatically generated by the blockchain after the warehouser stores the inbound data on the blockchain after the goods are warehoused. Specifically:

[0104] After the warehouser receives the goods, it needs to register the inbound. After the warehouser completes the inbound, it can send the inbound data of the goods to the blockchain after carrying it in the second call transaction;

[0105] The node device of the blockchain receives a second call transaction sent by the warehouser after the goods stored for the consignor are warehoused; wherein, the second call transaction includes information on the goods of the warehouser and the consignor.

[0106] In response to the second call transaction, when the consignor initiates a goods pledge application to the financier, the digital warehouse receipt inventory data generation logic declared in the smart contract is called to generate a to-do event for the corresponding goods of the warehouser. The to-do event is the aforementioned contract event and will not be elaborated here.

[0107] After obtaining the to-do event in the blockchain, the warehouser can automatically submit the inventory data of the goods (such as the name, quantity, specifications, etc. of the goods) to the smart contract through the API interface.

[0108] Then, the smart contract summarizes the inventory data, generates an inventory data module for the corresponding digital warehouse receipt of the goods, and updates and stores the digital warehouse receipt in the blockchain. Through this embodiment, the blockchain can not only store and prove the warehousing data of the goods to ensure the real data when the goods are stored in the warehouser, but also generate and store and prove a unique digital warehouse receipt corresponding to the goods to ensure the security and reliability of the digital warehouse receipt.

[0109] In actual warehousing, there is also a management link for the goods out of the warehouse to update the stored goods data. Specifically:

[0110] When the goods pledged by the consignor are out of the warehouse, the warehouser can initiate a fourth call transaction.

[0111] The node device of the blockchain receives the fourth call transaction sent by the warehouser after the goods pledged by the consignor are out of the warehouse; wherein, the fourth call transaction includes the out-of-warehouse data of the goods.

[0112] In response to the fourth call transaction, the out-of-warehouse logic declared in the smart contract is called. After the financier approves the out-of-warehouse, the out-of-warehouse data is stored and proved in the blockchain, and the inventory data module of the digital warehouse receipt corresponding to the goods is updated, and the digital warehouse receipt is updated and stored in the blockchain.

[0113] Through this embodiment, the blockchain can store and prove the out-of-warehouse record of each pledged goods and update the digital warehouse receipt corresponding to the goods in real time.

[0114] In actual warehousing, there is also a quality inspection link for the goods in the warehouse, that is, the quality inspection party needs to conduct quality inspection on the goods in the warehouse to avoid storing problematic goods. Similarly, the quality inspection information can also be stored and proved on the chain. Specifically:

[0115] After the quality inspection party conducts quality inspection on the goods in storage, it can send the quality inspection information to the blockchain after the fifth call transaction;

[0116] The node device of the blockchain receives the fifth call transaction sent by the quality inspection party after conducting quality inspection on the goods in storage; wherein, the fifth call transaction includes the quality inspection information of the goods in storage;

[0117] In response to the fifth call transaction, the digital warehouse receipt pledged goods generation logic declared in the smart contract is called to deposit the quality inspection information into the blockchain, update the pledged goods module of the digital warehouse receipt, and update and deposit the digital warehouse receipt to the blockchain;

[0118] Through this embodiment, the blockchain can not only deposit the quality inspection information of the goods in storage to ensure the safety of the goods, but also make the deposited digital warehouse receipt effective, so that the goods owner can perform other business operations based on the effective digital warehouse receipt, such as warehouse receipt pledge.

[0119] After introducing the embodiments of the generation and effectiveness of the digital warehouse receipt, the foregoing steps 210 to 250 will be further introduced:

[0120] Step 210: Receive the first call transaction sent by the fund provider after the goods owner initiates a warehouse receipt pledge application; wherein, the first call transaction includes the digital warehouse receipt pledged goods module generated by the goods owner's pledge application.

[0121] In implementation, the goods owner can use the goods stored in the warehouse keeper as collateral to apply for a certain amount of financing from the fund provider. And the fund provider can use the blockchain to determine whether the pledged goods are actually and completely stored in the warehouse keeper. Specifically, the fund provider can send the digital warehouse receipt corresponding to the goods pledged by the goods owner to the blockchain after the first call transaction.

[0122] Step 220: In response to the first call transaction, call the warehouse receipt authenticity verification logic declared in the smart contract published on the blockchain to generate a digital warehouse receipt inventory data module, and determine whether the pledged goods of the digital warehouse receipt are consistent with the goods inventory data.

[0123] In one embodiment, when the fund provider uses the blockchain to determine the pledged goods, it is first necessary to determine whether the digital warehouse receipt corresponding to the pledged goods is true. For example, query whether the same digital warehouse receipt is deposited in the blockchain; if not, it means the digital warehouse receipt is false, and then the pledge can be directly terminated. If so, it means the digital warehouse receipt is true and subsequent judgments can be made.

[0124] In an illustrated embodiment, the determination of whether the pledged goods of the digital warehouse receipt are consistent with the goods inventory data includes:

[0125] Obtain the cargo inventory data corresponding to the cargo owner party where the warehousing party's warehousing management system stores evidence on the chain through the API interface;

[0126] Obtain the cargo information for which the cargo owner party applies for pledge to the fund party and stores evidence on the chain;

[0127] Verify and check the cargo information for the pledge application against the cargo inventory data to determine that the pledged cargo of the digital warehouse receipt is truly consistent with the cargo inventory data.

[0128] In this example, by querying the cargo inventory data stored in the chain by the warehousing party's warehousing management system, and then verifying and checking it against the cargo information for which the cargo owner party applies for pledge to the fund party and stores evidence on the chain; it is used to verify that the pledged cargo information under the digital warehouse receipt is truly consistent with the cargo inventory data.

[0129] Step 230: If so (the pledged cargo information under the digital warehouse receipt is truly consistent with the cargo inventory data), call the management logic declared in the blockchain smart contract to generate the property right information module for the cargo corresponding to the digital warehouse receipt, and determine whether the ownership of the pledged cargo is clear.

[0130] As in the embodiment of the second call transaction described above, the blockchain stores the proof documents representing the ownership of the goods submitted by the cargo owner party. Therefore, it is possible to determine whether the ownership of the pledged cargo is clear through the proof documents stored in the blockchain.

[0131] In an illustrated embodiment, it is also possible to obtain again from the cargo owner party the proof documents representing the ownership of the goods to prove that the ownership of the pledged cargo belongs to the cargo owner party.

[0132] By determining the ownership of the pledged cargo, ownership disputes over the pledged cargo are avoided.

[0133] Step 240: If so (the ownership of the pledged cargo is clear), further determine whether the pledged cargo corresponding to the digital warehouse receipt truly exists based on the offline Internet of Things device corresponding to the digital warehouse receipt.

[0134] Among them, the offline Internet of Things (IOT) devices specifically refer to the process of collecting various objects that need to be monitored, connected, and interacted with in real-time or non-real-time through various sensing hardware, such as various monitoring cameras, information sensors, radio frequency identifiers, global positioning systems, infrared sensors, laser scanners, and other devices, in combination with relevant technologies. Collect various required information such as images, sounds, lights, heat, electricity, mechanics, chemistry, biology, and location, and through various possible network accesses, realize the connection between things and things, and between things and people, and realize the intelligent perception, identification, and management of items and processes. The Internet of Things is an information carrier based on the Internet, traditional telecommunications networks, etc. The Internet of Things can enable all ordinary physical objects that can be independently addressed to form an interconnected network.

[0135] In this embodiment, combining the offline Internet of Things devices with the blockchain can empower the blockchain to perceive information and data in the real offline environment, so that the blockchain can make reasonable judgments, processing, etc. intelligently with the data in the real environment collected by the offline Internet of Things devices.

[0136] Among them, in step 240, determining whether the pledged goods corresponding to the digital warehouse receipt actually exist based on the offline Internet of Things devices corresponding to the digital warehouse may include:

[0137] Determine the storage space location in the blockchain that is certified to correspond to the digital warehouse receipt, and send the communication parameters of the offline Internet of Things device associated with the storage space location to the fund provider; so that the fund provider can establish a connection with the offline Internet of Things device based on the communication parameters, and determine whether the goods are located in the storage space managed by the storage provider based on the monitoring data transmitted by the offline Internet of Things device.

[0138] In this embodiment, after the smart contract determines that there is a pledged digital warehouse receipt in the blockchain, it can further obtain the storage space location in the blockchain where the goods corresponding to the digital warehouse receipt are stored, the offline Internet of Things device associated with the storage space location, and the communication parameters of the offline Internet of Things device.

[0139] Among them, the storage space location may refer to the storage location in the warehouse. Usually, the location where the goods are stored after being put into the warehouse will be recorded for convenient subsequent outbound.

[0140] In addition, the storage provider can install Internet of Things devices in the warehouse to monitor the goods or other information in the warehouse in real-time.

[0141] Generally, since a single Internet of Things device may not be able to collect information on all locations in the entire warehouse, multiple Internet of Things devices need to be installed to cover all areas of the warehouse. Thus, for the incoming goods, it is also necessary to associate the Internet of Things devices that can collect the monitoring data of the goods. In some embodiments, multiple Internet of Things devices can be associated with the goods.

[0142] It should be noted that the above information such as the storage space location, offline Internet of Things device, communication parameters, etc. can be part of the incoming storage data stored when the goods are warehoused. Of course, if the storage space location of the goods changes during the warehousing process (inventory transfer is quite common in actual warehousing), then it is also necessary to upload the changed storage space location of the goods, the offline Internet of Things device corresponding to this storage space location, and the communication parameters corresponding to this offline Internet of Things device for storage. These information can be stored as the storage records of the goods during the warehousing process on the blockchain. Thus, the storage history of the goods in the warehouse can be traced.

[0143] Among them, the communication parameters can refer to the link parameters for an external party to remotely connect to the offline Internet of Things device or the remote server corresponding to the offline Internet of Things device, such as the destination IP address, destination port number, communication protocol, digital certificate, etc.

[0144] After obtaining the communication parameters, the fund provider can establish a connection with the offline Internet of Things device based on the communication parameters to obtain the monitoring data transmitted by the offline Internet of Things device. Taking a surveillance camera as an example, the fund provider can visually determine whether the goods in the warehouse are the pledged goods by viewing the surveillance video.

[0145] Since the monitoring data truly reflects the real situation of the pledged goods in the warehouse, it can be used to judge whether the pledged goods are consistent with the goods stored in the warehouse.

[0146] If they are inconsistent, then the fund provider can terminate the pledge.

[0147] Step 250: If it is (the pledged goods actually exist), call the state modification logic declared in the smart contract to modify the goods status of the digital warehouse receipt stored in the blockchain to the pledged status, so that when the fund provider determines that the pledged goods in the digital warehouse receipt are modified to the pledged status, the goods corresponding to the digital warehouse receipt are used as collateral to provide financing to the shipper.

[0148] If the fund provider determines that the pledged goods are consistent with the goods stored in the warehouse, it means that the goods pledged by the shipper are valid, and the goods stored in the warehouse can be used as collateral to obtain financing. And the smart contract of the blockchain will modify the goods status of the digital warehouse receipt stored in the blockchain to the pledged status.

[0149] To avoid duplicate pledges of warehouse receipts, the method may further include:

[0150] When it is determined that the digital warehouse receipt is stored in the blockchain, obtain the cargo status corresponding to the digital warehouse receipt. If the cargo status is pledged, return the digital warehouse receipt exception notice to the financier so that the financier can suspend the pledge of the digital warehouse receipt.

[0151] Through the above embodiments, the goods corresponding to the digital warehouse receipt are monitored in real time based on the offline Internet of Things devices carried by the warehouser, and the status of the warehouse receipt is maintained based on the smart contract corresponding to the digital warehouse receipt deployed on the blockchain. On the one hand, the transfer efficiency and information transparency of the digital warehouse receipt are improved; on the other hand, the potential safety hazards in each business link related to the digital warehouse receipt are reduced, and a reliable guarantee is provided for the transfer of rights and interests in the process of warehouse receipt pledge.

[0152] In an exemplary embodiment, the blockchain may also provide a prompt service for cargo anomalies to each participating party.

[0153] In one implementation, the method may further include:

[0154] Receive a fifth call transaction sent by the warehouser; wherein the fifth call transaction includes the inventory data of the pledged goods by the warehouser.

[0155] In response to the sixth transfer transaction, call the digital warehouse receipt inventory data generation logic declared in the smart contract, update the digital warehouse receipt inventory data module based on the inventory data of the pledged goods, and determine whether the inventory data is consistent with the quantity of the pledged goods.

[0156] If they are inconsistent, send an alarm to the financier.

[0157] In this embodiment, the blockchain can be docked with the inventory management system of the warehouser to synchronize the inventory data in the database of the inventory management system in real time or non-real time. Usually, the warehouser needs to regularly check the pledged goods in the warehouse to determine whether the goods inventory data is consistent with the actual quantity of the pledged goods.

[0158] In this specification, the blockchain can determine whether the quantity of the pledged goods is consistent based on the inventory data of the warehouser.

[0159] If they are inconsistent, it means that there are anomalies in the pledged goods, and then an alarm can be sent to the financier so that the financier can handle it in time to avoid greater losses.

[0160] In another implementation, the method may further include:

[0161] Receive the seventh call transaction sent by the warehousing party; wherein, the seventh call transaction includes monitoring data related to the goods collected by offline Internet of Things devices;

[0162] In response to the seventh transfer transaction, invoke the management logic declared in the smart contract, and determine whether there are potential safety hazards for the pledged goods corresponding to the digital warehouse receipt based on the monitoring data;

[0163] When there are potential safety hazards for the pledged goods, send an alarm to the financier.

[0164] In this embodiment, the offline Internet of Things device includes an environmental sensor, and the monitoring data includes environmental data of the warehousing space collected by the environmental sensor;

[0165] The determination of whether there are potential safety hazards for the pledged goods based on the monitoring data includes:

[0166] Judge whether the environmental data reaches dangerous conditions; if it reaches (for example, when the monitored environmental data is greater than the preset environmental threshold), determine whether there are potential safety hazards for the pledged goods. Wherein, the environmental data includes at least one of temperature, humidity, dust concentration, and concentration of dangerous gases.

[0167] In this specification, environmental sensing hardware can be distributed and set in the warehousing space managed by the warehousing party. These environmental sensing hardware are used to monitor the environmental data in the warehousing space in real time, and report the monitored environmental data to the warehousing party, which is then stored on the blockchain for certification.

[0168] The blockchain can determine whether there are potential safety hazards for the pledged goods corresponding to the digital warehouse receipt based on the environmental data, and when there are potential safety hazards, send an alarm to the financier and / or the warehousing party, so that the financier and / or the warehousing party can handle it in time to avoid greater losses.

[0169] Corresponding to the foregoing embodiment of the method for managing digital warehouse receipts based on blockchain, this specification also provides an embodiment of a device for managing digital warehouse receipts based on blockchain. The device embodiment can be implemented by software, or by hardware or a combination of software and hardware. Taking software implementation as an example, as a logically meaningful device, it is formed by the processor of the device where it is located reading the corresponding computer service program instructions in the non-volatile memory into the memory for operation. From the hardware level, as Figure 3 shown, it is a hardware structure diagram of the device where the digital warehouse receipt management device based on blockchain in this specification is located. In addition to Figure 3 the shown processor, network interface, memory, and non-volatile memory, the device where the embodiment is located usually also includes other hardware according to the actual functions of managing digital warehouse receipts based on blockchain, which will not be elaborated here.

[0170] Please refer to Figure 4 , which is a module diagram of a blockchain-based digital warehouse receipt management device provided in an embodiment of this specification. The device corresponds to Figure 2 the embodiment shown. In the blockchain, digital warehouse receipts are stored. The digital warehouse receipt is an asset certificate corresponding to the goods generated after the shipper stores the goods with the warehouser and initiates a pledge application. The device includes:

[0171] A receiving unit 510, which receives a first call transaction sent by the financier after the shipper initiates a warehouse receipt pledge application; wherein, the first call transaction includes a digital warehouse receipt pledged goods module generated by the shipper's pledge application;

[0172] A response unit 520, in response to the first call transaction, calls the warehouse receipt verification logic declared in the smart contract published on the blockchain, generates a digital warehouse receipt inventory data module, and determines whether the pledged acquisition and inventory data of the digital warehouse receipt are consistent;

[0173] A judgment unit 530, if so, calls the management logic declared in the blockchain smart contract, generates a property right information module of the goods corresponding to the digital warehouse receipt, and judges whether the ownership of the pledged goods is clear;

[0174] A determination unit 540, if so, further determines whether the pledged goods corresponding to the digital warehouse receipt actually exist based on the offline Internet of Things device corresponding to the digital warehouse receipt;

[0175] A management unit 550, if so, calls the status modification logic declared in the smart contract, and modifies the goods status of the digital warehouse receipt stored in the blockchain to the pledged status, so that when the financier determines that the pledged goods in the digital warehouse receipt are modified to the pledged status, the goods corresponding to the digital warehouse receipt are used as pledges to provide financing to the shipper.

[0176] Optionally, in the response unit 520, determining whether the pledged goods of the digital warehouse receipt are consistent with the goods inventory data includes:

[0177] Obtaining the goods inventory data corresponding to the shipper stored on the chain by the warehouser's warehousing management system through the API interface;

[0178] Obtaining the goods information of the shipper's pledge application stored on the chain to the financier;

[0179] Performing verification and validation on the goods information of the pledge application and the goods inventory data to determine that the pledged goods of the digital warehouse receipt are truly consistent with the goods inventory data.

[0180] Optionally, in the determining unit 540, determining whether the goods corresponding to the digital warehouse receipt actually exist based on the offline Internet of Things device corresponding to the digital warehouse receipt includes:

[0181] Determine the storage space location corresponding to the digital warehouse receipt stored in the blockchain, and send the communication parameters of the offline Internet of Things device associated with the storage space location to the financier; so that the financier establishes a connection with the offline Internet of Things device based on the communication parameters, and determines whether the goods are located in the storage space managed by the warehouse keeper based on the monitoring data transmitted by the offline Internet of Things device.

[0182] Optionally, the device further includes:

[0183] An exception notification subunit, when it is determined that the digital warehouse receipt is stored in the blockchain, obtain the goods status corresponding to the digital warehouse receipt. If the goods status corresponding to the digital warehouse receipt is pledged, return a digital warehouse receipt exception notification to the financier, so that the financier suspends the pledge of the goods corresponding to the digital warehouse receipt.

[0184] Optionally, the device further includes:

[0185] A second call processing subunit, which receives a second call transaction sent by the warehouse keeper; wherein, the second call transaction includes the warehouse keeper of the goods and the goods of the goods owner; in response to the second call transaction, when the goods owner initiates a goods pledge application to the financier, call the digital warehouse receipt inventory data generation logic declared in the smart contract to generate a to-do event for the goods corresponding to the warehouse keeper. After the warehouse keeper obtains the to-do event in the blockchain, automatically submit the inventory data of the goods to the smart contract through the API interface; the smart contract summarizes the inventory data, generates an inventory data module for the digital warehouse receipt corresponding to the goods, and updates and stores the digital warehouse receipt to the blockchain.

[0186] Optionally, the device further includes:

[0187] A third call processing subunit, which receives a third call transaction sent by the goods owner, wherein the third call transaction includes a proof document representing the ownership of the goods submitted by the goods owner; in response to the third call transaction, call the digital warehouse receipt goods right information module generation logic declared in the smart contract, generate a goods information module for the digital warehouse receipt after storing the proof document in the blockchain, and update and store the digital warehouse receipt to the blockchain.

[0188] Optionally, the device further includes:

[0189] The fourth call processing subunit receives the fourth call transaction sent by the warehousing party after the pledged goods of the consignor are out of storage; wherein, the fourth call transaction includes the out-of-storage data of the goods; in response to the fourth call transaction, it calls the out-of-storage logic declared in the smart contract, and after the fund party approves the out-of-storage, stores the out-of-storage data on the blockchain, updates the inventory data module of the digital warehouse receipt corresponding to the goods, and updates and stores the digital warehouse receipt on the blockchain.

[0190] Optionally, the device further includes:

[0191] The fifth call processing subunit receives the fifth call transaction sent by the quality inspection party after inspecting the pledged goods; wherein, the fifth call transaction includes the quality inspection information of the pledged goods; in response to the fifth call transaction, it calls the logic for generating pledged goods of the digital warehouse receipt declared in the smart contract, stores the quality inspection information on the blockchain, updates the pledged goods module of the digital warehouse receipt, and updates and stores the digital warehouse receipt on the blockchain.

[0192] Optionally, the device further includes:

[0193] The sixth call processing subunit receives the sixth call transaction sent by the warehousing party; wherein, the sixth call transaction includes the inventory data of the warehousing party for the pledged goods; in response to the sixth call transaction, it calls the logic for generating inventory data of the digital warehouse receipt declared in the smart contract, updates the inventory data module of the digital warehouse receipt based on the inventory data of the pledged goods, and determines whether the data is consistent with the quantity of the pledged goods; if the quantity of the pledged goods in the digital warehouse receipt is inconsistent with the inventory data after the inventory data is updated, an alarm is sent to the fund party.

[0194] Optionally, the device further includes:

[0195] The seventh call processing subunit receives the seventh call transaction sent by the warehousing party; wherein, the seventh call transaction includes the monitoring data related to the goods collected by the offline Internet of Things device; in response to the seventh call transaction, it calls the management logic declared in the smart contract, and determines whether there are potential safety hazards for the pledged goods of the digital warehouse receipt based on the monitoring data; when there are potential safety hazards for the goods, an alarm is sent to the fund party.

[0196] Optionally, the offline Internet of Things device includes an environmental sensor, and the monitoring data includes the environmental data of the warehousing space collected by the environmental sensor;

[0197] Determining whether there are potential safety hazards for the goods based on the monitoring data includes:

[0198] Judging whether the environmental data reaches the dangerous condition; if it reaches, determining whether there are potential safety hazards for the goods.

[0199] Optionally, the environmental data includes at least one of temperature, humidity, dust concentration, and hazardous gas concentration.

[0200] The systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, and the specific form of the computer can be a personal computer, laptop computer, cellular phone, camera phone, smart phone, personal digital assistant, media player, navigation device, email transceiver, game console, tablet computer, wearable device, or a combination of any several of these devices.

[0201] For the specific implementation processes of the functions and roles of each unit in the above device, please refer to the implementation processes of the corresponding steps in the above method for details, which will not be elaborated here. For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can refer to the partial descriptions of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this specification. Those of ordinary skill in the art can understand and implement it without creative efforts.

[0202] In the embodiments of the above electronic device, it should be understood that the processor can be a central processing unit (English: Central Processing Unit, abbreviated: CPU), and can also be other general-purpose processors, digital signal processors (English: Digital Signal Processor, abbreviated: DSP), application specific integrated circuits (English: Application Specific Integrated Circuit, abbreviated: ASIC), etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc., and the aforementioned memory can be a read-only memory (English: read-only memory, abbreviated: ROM), random access memory (English: random access memory, abbreviated: RAM), flash memory, hard disk, or solid-state drive. The steps of the method disclosed in combination with the embodiments of the present application can be directly implemented by the execution of the hardware processor, or implemented by the combination of hardware and software modules in the processor.

[0203] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the embodiment of the electronic device, since it is basically similar to the method embodiment, the description is relatively simple, and reference can be made to the corresponding part of the method embodiment for the relevant content.

[0204] After considering the specification and practicing the invention disclosed herein, those skilled in the art will readily conceive of other embodiments of this specification. This specification is intended to cover any variations, uses, or adaptations of this specification, which follow the general principles of this specification and include common general knowledge or conventional technical means in the technical field not disclosed in this specification. The specification and the embodiments are only regarded as exemplary, and the true scope and spirit of this specification are pointed out by the following claims.

[0205] It should be understood that this specification is not limited to the exact structures already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of this specification is only limited by the appended claims.

Claims

1. A blockchain-based digital warehouse receipt management method, characterized in that, The blockchain stores digital warehouse receipts and supporting documents. The digital warehouse receipt is an asset certificate corresponding to the goods generated after the goods owner stores the goods with the warehouser and initiates a pledge application. The supporting document is a document submitted by the goods owner representing the ownership of the goods. The method includes: Receiving a first call transaction sent by the fund provider after the goods owner initiates a warehouse receipt pledge application. The first call transaction includes a digital warehouse receipt pledge goods module generated from the goods owner's pledge application. In response to the first call transaction, invoking the warehouse receipt authenticity verification logic declared in the smart contract published on the blockchain, generating a digital warehouse receipt inventory data module, and determining whether the pledged goods of the digital warehouse receipt are consistent with the goods inventory data. If so, invoking the management logic declared in the blockchain smart contract, generating a goods ownership information module for the goods corresponding to the digital warehouse receipt, and determining whether the ownership of the pledged goods is clear through the supporting document stored on the blockchain. If so, determining the storage space location on the blockchain corresponding to the digital warehouse receipt, and sending the communication parameters of the offline Internet of Things device associated with the storage space location to the fund provider, so that the fund provider can establish a connection with the offline Internet of Things device based on the communication parameters, and determine whether the goods are located in the storage space managed by the warehouser based on the monitoring data transmitted by the offline Internet of Things device. If so, invoking the status modification logic declared in the smart contract to modify the goods status of the digital warehouse receipt stored on the blockchain to the pledged status, so that when the fund provider determines that the pledged goods in the digital warehouse receipt are modified to the pledged status, the goods corresponding to the digital warehouse receipt are used as collateral to provide financing to the goods owner.

2. The method according to claim 1, characterized in that, The determination of whether the pledged goods of the digital warehouse receipt are consistent with the goods inventory data includes: Obtaining the goods inventory data corresponding to the goods owner stored on the blockchain by the warehouser's warehouse management system through the API interface. Obtaining the goods information of the goods owner's pledge application stored on the blockchain. Performing authenticity verification on the goods information of the pledge application and the goods inventory data to determine that the pledged goods of the digital warehouse receipt are truly consistent with the goods inventory data.

3. The method according to claim 1, characterized in that The method further includes: When it is determined that the digital warehouse receipt is stored on the blockchain, obtaining the goods status corresponding to the digital warehouse receipt. If the goods status corresponding to the digital warehouse receipt is pledged, returning a digital warehouse receipt exception notice to the fund provider, so that the fund provider can suspend the pledge of the goods corresponding to the digital warehouse receipt.

4. The method according to claim 1, wherein The method further includes: Receiving a second call transaction sent by the warehouser. The second call transaction includes the warehouser of the goods and the goods of the goods owner. In response to the second call transaction, when the cargo owner initiates a cargo pledge application to the capital provider, the digital warehouse receipt inventory data generation logic declared in the smart contract is called to generate a to-do event for the corresponding goods of the warehouser. After the warehouser obtains the to-do event in the blockchain, the inventory data of the goods is automatically submitted to the smart contract through the API interface; the smart contract summarizes the inventory data, generates an inventory data module for the corresponding digital warehouse receipt of the goods, and updates and stores the digital warehouse receipt in the blockchain.

5. The method according to claim 1, characterized in that, The method further includes: Receiving a third call transaction sent by the cargo owner, where the third call transaction includes a proof document submitted by the cargo owner of the goods representing the ownership of the goods; In response to the third call transaction, calling the digital warehouse receipt ownership information module generation logic declared in the smart contract, generating a goods information module for the digital warehouse receipt after storing the proof document in the blockchain, and updating and storing the digital warehouse receipt in the blockchain.

6. The method according to claim 1, wherein The method further includes: Receiving a fourth call transaction sent by the warehouser after the pledged goods of the cargo owner are out of storage; where the fourth call transaction includes the out-of-storage data of the goods; In response to the fourth call transaction, calling the out-of-storage logic declared in the smart contract, after the capital provider approves the out-of-storage, storing the out-of-storage data in the blockchain, and updating the inventory data module corresponding to the digital warehouse receipt of the goods, and updating and storing the digital warehouse receipt in the blockchain.

7. The method according to claim 1, characterized in that The method further includes: Receiving a fifth call transaction sent by the quality inspection party after inspecting the pledged goods; where the fifth call transaction includes the quality inspection information of the pledged goods; In response to the fifth call transaction, calling the digital warehouse receipt pledged goods generation logic declared in the smart contract, storing the quality inspection information in the blockchain, updating the pledged goods module of the digital warehouse receipt, and updating and storing the digital warehouse receipt in the blockchain.

8. The method according to claim 1, wherein The method further includes: Receiving a sixth call transaction sent by the warehouser; where the sixth call transaction includes the inventory data of the warehouser for the pledged goods; In response to the sixth call transaction, calling the digital warehouse receipt inventory data generation logic declared in the smart contract, updating the digital warehouse receipt inventory data module based on the inventory data of the pledged goods, and determining whether the data is consistent with the quantity of the pledged goods; If the quantity of the pledged goods in the digital warehouse receipt is inconsistent with the inventory data after the inventory data is updated, an alarm is sent to the capital provider.

9. The method according to claim 1, characterized in that, The method further includes: Receiving a seventh call transaction sent by the warehouser; where the seventh call transaction includes the monitoring data related to the goods collected by the offline Internet of Things device; In response to the seventh call transaction, calling the management logic declared in the smart contract, and determining whether there are potential safety hazards for the pledged goods in the digital warehouse receipt based on the monitoring data; When there are potential safety hazards for the pledged goods, an alarm is sent to the capital provider.

10. The method according to claim 9, wherein The offline Internet of Things device includes an environmental sensor, and the monitoring data includes the environmental data of the storage space collected by the environmental sensor; Determining whether there are potential safety hazards for the pledged goods based on the monitoring data includes: Determine whether the environmental data reaches a dangerous condition; If so, determine whether there are potential safety hazards for the pledged goods.

11. A digital warehouse receipt management device based on blockchain, characterized in that, The digital warehouse receipt and supporting documents are stored on the blockchain. The digital warehouse receipt is an asset certificate corresponding to the goods generated after the shipper stores the goods with the warehouser and initiates a pledge application. The supporting document is a document submitted by the shipper representing the ownership of the goods. The device includes: A receiving unit that receives a first call transaction sent by the financier after the shipper initiates a warehouse receipt pledge application. The first call transaction includes a digital warehouse receipt pledge goods module generated from the shipper's pledge application. A response unit that, in response to the first call transaction, invokes the warehouse receipt authenticity verification logic declared in the smart contract published on the blockchain, generates a digital warehouse receipt inventory data module, and determines whether the pledge acquisition and inventory data of the digital warehouse receipt are consistent. A judgment unit that, if so, invokes the management logic declared in the blockchain smart contract, generates a goods ownership information module for the goods corresponding to the digital warehouse receipt, and determines whether the ownership of the pledged goods is clear through the supporting documents stored on the blockchain. A determination unit that, if so, determines the storage space location corresponding to the digital warehouse receipt stored on the blockchain, and sends the communication parameters of the offline IoT device associated with the storage space location to the financier; so that the financier can establish a connection with the offline IoT device based on the communication parameters, and determine whether the goods are located in the storage space managed by the warehouser based on the monitoring data transmitted by the offline IoT device. A management unit that, if so, invokes the status modification logic declared in the smart contract to modify the goods status of the digital warehouse receipt stored on the blockchain to the pledged status, so that when the financier determines that the pledged goods in the digital warehouse receipt are modified to the pledged status, the goods corresponding to the digital warehouse receipt are used as collateral to provide financing to the shipper.

12. An electronic device, characterized in that, Includes: A processor; A memory for storing instructions executable by the processor; Wherein, the processor is configured to perform the method according to any one of the above claims 1-10.

Images