Supply chain data supervision method and equipment based on block chain

Abstract

The invention is suitable for the technical field of supply chains, and particularly relates to a supply chain data supervision method and equipment based on a block chain, and the method comprises the steps: receiving management requirement information uploaded by a management node; the management requirement information is examined, the management requirement information is sent to all management nodes and enterprise nodes after examination is qualified, delivery determination is carried out, and the management requirement information is subjected to block processing and then uploaded to a block chain; receiving supply chain data uploaded by the enterprise node; sending the supply chain data to all management nodes and carrying out delivery determination, and then blocking the supply chain data and uploading the blocked supply chain data to a block chain; receiving supply chain data verification data uploaded by the management node; and sending the supply chain data verification data to all enterprise nodes and carrying out delivery determination, and then carrying out block processing on the supply chain data verification data and uploading the supply chain data verification data to a block chain. The method can solve the problem that a traditional supply chain data supervision method has a high requirement for the credibility of a supervisor.

Description

Technical Field

[0001] This application belongs to the technical field of supply chain, and particularly relates to a supply chain data supervision method and device based on blockchain. Background Art

[0002] Blockchain technology is a decentralized, immutable, transparent and secure block-chain storage technology. By storing data distributively in all nodes, it realizes the characteristics of decentralization and immutability.

[0003] Traditional supply chain data supervision methods inevitably select a designated supervisor with high authority to supervise supply chain data. As a result, supply chain data needs to be stored on the supervisor and is based on the supply chain data stored on the supervisor, which requires a high level of trust in the supervisor. However, there are few supervisors with a high level of trust, greatly limiting the use of traditional supply chain data supervision methods. Summary of the Invention

[0004] Embodiments of this application provide a supply chain data supervision method and device based on blockchain, which can solve the problem that traditional supply chain data supervision methods need to store supply chain data on the supervisor and are based on the supply chain data stored on the supervisor, requiring a high level of trust in the supervisor and greatly limiting the use of traditional supply chain data supervision methods.

[0005] In a first aspect, embodiments of this application provide a supply chain data supervision method based on blockchain, which is applied to a blockchain supervision system. The blockchain supervision system includes multiple management nodes and enterprise nodes, and the blockchain supervision system runs in a computer network composed of all nodes. The method includes: Receiving management requirement information uploaded by a management node; Reviewing the management requirement information, and after passing the review, sending the management requirement information to all management nodes and enterprise nodes for delivery confirmation, and then blockifying the management requirement information and uploading it to the blockchain; where the delivery confirmation refers to detecting whether the sent information is delivered, and if not, repeating the sending of the corresponding information; Receiving supply chain data uploaded by an enterprise node; where the supply chain data is used to reflect the transaction situation of the enterprise's supply chain, and the supply chain data meets the specification requirements of the management requirement information; Sending the supply chain data to all management nodes for delivery confirmation, and then blockifying the supply chain data and uploading it to the blockchain; Receive the supply chain data verification data uploaded by the management node; wherein, the supply chain data verification data is used to reflect the authenticity of all the supply chain data after the management node verifies all the supply chain data, and the supply chain data verification data meets the specification requirements of the management requirement information; Send the supply chain data verification data to all enterprise nodes and confirm the delivery, and then block the supply chain data verification data and upload it to the blockchain.

[0006] In the technical solution described above in the embodiments of the present application, it has at least the following technical effects: The supply chain data supervision method provided by this application. First, it receives the management requirement information uploaded by the management node. In this step, receiving the management requirement information uploaded by the management node is used to standardize the data uploaded by enterprise nodes and management nodes hereafter, so that the uploaded data will not be stored as different files due to different formats, which is beneficial to solving the problem of storing supply chain data on the supervisor side. Subsequently, it reviews the management requirement information. After passing the review, it sends the management requirement information to all management nodes and enterprise nodes and determines the delivery. Then, it blocks the management requirement information and uploads it to the blockchain. In this step, it notifies the management requirement information to all nodes and generates a block according to the management requirement information and uploads it to the blockchain, which can make the management requirement information tamper-proof and is beneficial to solving the problem of having a high requirement for the trust in the supervisor. Then, it receives the supply chain data uploaded by the enterprise node. In this step, receiving the supply chain data uploaded by the enterprise node is for subsequent verification and data processing of the supply chain data. Then, it sends the supply chain data to all management nodes and determines the delivery. Then, it blocks the supply chain data and uploads it to the blockchain, and uploads the enterprise block to the blockchain. In this step, it sends the supply chain data to the management node and generates an enterprise block and uploads it to the blockchain, which is beneficial to ensuring that the supply chain data cannot be tampered with and facilitating the verification of this supply chain data in the future. Then, it receives the supply chain data verification data uploaded by the management node. In this step, the management node verifies the received supply chain data, and the result after verification is called the supply chain data verification data, which is for subsequent data processing and storage of the supply chain data verification data. Finally, it sends the supply chain data verification data to all enterprise nodes and determines the delivery. Then, it blocks the supply chain data verification data and uploads it to the blockchain. In this step, it notifies the supply chain data verification data to all enterprise nodes and generates a verification block according to the supply chain data verification data and uploads it to the blockchain, which can ensure that the supply chain data verification data is not tampered with and facilitate the verification of this supply chain data verification data in the future. This method proposes management requirement information, supply chain data, and supply chain data verification data to complete the supervision of supply chain data. Subsequently, it generates corresponding blocks for the management requirement information, supply chain data, and supply chain data verification data and uploads them to the blockchain to solve the problem that the traditional supply chain data supervision method needs to store the supply chain data on the supervisor side and takes the supply chain data stored on the supervisor side as the standard, and has a high requirement for the trust in the supervisor.

[0007] In the second aspect, the embodiment of this application provides a supply chain data supervision system. The blockchain supervision system includes multiple management nodes and enterprise nodes. The system includes: A receiving unit, configured to receive the management requirement information uploaded by the management node, receive the supply chain data uploaded by the enterprise node, and receive the supply chain data verification data uploaded by the management node; A review unit, configured to review the management requirement information; A sending unit, configured to send the management requirement information to all management nodes and enterprise nodes and determine delivery, and further configured to send the supply chain data to all management nodes and determine delivery, and further configured to send the supply chain data verification data to all enterprise nodes and determine delivery; A block-forming unit, configured to block the management requirement information and upload it to the blockchain, and further configured to block the supply chain data and upload it to the blockchain, and further configured to block the supply chain data verification data and upload it to the blockchain.

[0008] In a third aspect, an embodiment of the present application provides a supply chain data supervision device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor is characterized in that when the processor executes the computer program, the method described in any item of the first aspect above is implemented.

[0009] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the method described in any item of the first aspect above is implemented.

[0010] In a fifth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a supply chain data supervision device, the supply chain data supervision device is caused to execute the blockchain-based supply chain data supervision method described in any item of the first aspect above.

[0011] It can be understood that the beneficial effects of the second to fifth aspects above can refer to the relevant descriptions in the first aspect above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for use in the embodiments or the description of the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0013] Figure 1 is a schematic flowchart of a blockchain-based supply chain data supervision method provided by an embodiment of the present application; Figure 2 is a schematic communication flowchart between management nodes and enterprise nodes of a blockchain-based supply chain data supervision method provided by an embodiment of the present application; Figure 3 is a schematic structural diagram of a supply chain data supervision system provided by an embodiment of the present application; Figure 4 It is a schematic structural diagram of the supply chain data supervision device provided by an embodiment of the present application. Detailed implementation manners

[0014] In the following description, for the purpose of illustration rather than limitation, specific details such as specific system structures and technologies are presented to thoroughly understand the embodiments of the present application. However, those skilled in the art should understand that the present application can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid unnecessary details from interfering with the description of the present application.

[0015] It should be understood that when used in the specification and appended claims of the present application, the term "comprising" indicates the presence of the described features, wholes, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.

[0016] It should also be understood that the term "and / or" used in the specification and appended claims of the present application refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0017] As used in the specification and appended claims of the present application, the term "if" can be interpreted as "when", "once", "in response to determining", or "in response to detecting" according to the context. Similarly, the phrase "if determined" or "if detecting [the described condition or event]" can be interpreted as meaning "once determined", "in response to determining", "once detecting [the described condition or event]", or "in response to detecting [the described condition or event]" according to the context.

[0018] In addition, in the description of the specification and appended claims of the present application, the terms "first", "second", "third", etc. are only used for distinguishing descriptions and cannot be understood as indicating or implying relative importance.

[0019] The reference to "one embodiment" or "some embodiments" etc. described in the specification of the present application means that a specific feature, structure, or characteristic described in combination with the embodiment is included in one or more embodiments of the present application. Thus, the statements "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "comprising", "including", "having", and their variants all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0020] In the related art, traditional supply chain data supervision methods inevitably select a designated supervisor with high authority to supervise supply chain data. As a result, supply chain data needs to be stored on the supervisor and the supply chain data stored on the supervisor is taken as the standard, which requires a high degree of trust in the supervisor. However, there are few supervisors with a high degree of trust, greatly limiting the use of traditional supply chain data supervision methods.

[0021] To solve the above problems, an embodiment of the present application provides a blockchain-based supply chain data supervision method. In this method, first, management requirement information uploaded by a management node is received. In this step, receiving the management requirement information uploaded by the management node is used to standardize the data uploaded by enterprise nodes and management nodes hereafter, enabling the uploaded data not to be stored as different files due to different formats, which is beneficial to solving the problem of storing supply chain data on the supervisor side. Subsequently, the management requirement information is reviewed. After passing the review, the management requirement information is sent to all management nodes and enterprise nodes for delivery confirmation, and then the management requirement information is blockified and uploaded to the blockchain. In this step, the management requirement information is notified to all nodes, and a block is generated according to the management requirement information and uploaded to the blockchain, which can make the management requirement information tamper-proof and is beneficial to solving the problem of having a high requirement for the trust in the supervisor. Then, supply chain data uploaded by an enterprise node is received. In this step, receiving the supply chain data uploaded by the enterprise node is for subsequent verification and data processing of the supply chain data. Then, the supply chain data is sent to all management nodes for delivery confirmation, and then the supply chain data is blockified and uploaded to the blockchain, and the enterprise block is uploaded to the blockchain. In this step, the supply chain data is sent to the management nodes, and an enterprise block is generated and uploaded to the blockchain, which is beneficial to ensuring that the supply chain data cannot be tampered with and facilitating future verification of this supply chain data. Then, supply chain data verification data uploaded by the management node is received. In this step, the management node verifies the received supply chain data, and the verified result is called supply chain data verification data for subsequent data processing and storage of the supply chain data verification data. Finally, the supply chain data verification data is sent to all enterprise nodes for delivery confirmation, and then the supply chain data verification data is blockified and uploaded to the blockchain. In this step, the supply chain data verification data is notified to all enterprise nodes, and a verification block is generated according to the supply chain data verification data and uploaded to the blockchain, which can ensure that the supply chain data verification data is not tampered with and facilitate future verification of this supply chain data verification data. This method proposes management requirement information, supply chain data, and supply chain data verification data to complete the supervision of supply chain data, and then generates corresponding blocks for the management requirement information, supply chain data, and supply chain data verification data and uploads them to the blockchain to solve the problem that the traditional supply chain data supervision method needs to store the supply chain data on the supervisor side and uses the supply chain data stored on the supervisor side as the standard, resulting in a high requirement for the trust in the supervisor.

[0022] The blockchain-based supply chain data supervision method provided by an embodiment of the present application can be applied to a supply chain data supervision device. At this time, the supply chain data supervision device is the execution subject of the blockchain-based supply chain data supervision method provided by an embodiment of the present application, and the specific type of the supply chain data supervision device is not limited in any way by an embodiment of the present application.

[0023] For example, the supply chain data supervision device may be a mobile phone, a tablet computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a desktop computer, a computer, or a laptop computer.

[0024] To better understand the blockchain-based supply chain data supervision method provided by the embodiments of the present application, the following provides an exemplary introduction to the specific implementation process of the blockchain-based supply chain data supervision method provided by the embodiments of the present application.

[0025] Figure 1 FIG. shows a schematic flowchart of the blockchain-based supply chain data supervision method provided by the embodiments of the present application. The blockchain-based supply chain data supervision method includes: S100, receiving the management requirement information uploaded by the management node.

[0026] It can be understood that the management requirement information may be a text summary plus a format sample of the uploaded data. The text summary is used to describe the data that needs to be included in the uploaded data of the enterprise node or the management node. The format sample of the uploaded data of the enterprise node or the management node is used to indicate the format of the uploaded data and the arrangement order between different types of data. The format sample may be a word document or other types of documents.

[0027] With such a setting, the format of the uploaded data can be unified, which is beneficial to ensuring that the same document content does not obtain completely different hash values due to format problems.

[0028] S200, reviewing the management requirement information, after the review is qualified, sending the management requirement information to all management nodes and enterprise nodes and performing delivery confirmation, and then blockifying the management requirement information and uploading it to the blockchain. Among them, delivery confirmation refers to detecting whether the sent information is delivered. If it is not delivered, the corresponding information is repeatedly sent. The blockchain is stored in the computer network composed of all nodes.

[0029] It can be understood that after obtaining the management requirement information, the management requirement information is first reviewed. The review refers to reviewing the rationality of the management requirement information. Keywords can be added to the review process in advance, and then the keywords are retrieved in the management requirement information. When all types of keywords are included in the management requirement information, the review is qualified. The keywords can be the names of necessary data in the uploaded data of enterprise nodes or management nodes, such as enterprise names and enterprise numbers. Subsequently, the management requirement information is sent to all management nodes and enterprise nodes and delivery confirmation is performed. Information delivery confirmation can be achieved by adding a return signal to the communication protocol. The return signal means that after receiving any information, the receiving party sends a specific signal to the sending party to indicate that the information has been delivered. The specific signal can be an upper-edge trigger signal or a lower-edge trigger signal, etc. When the return signal is not received, the sending party resends the information. Finally, the management requirement information is blockified and uploaded to the blockchain. Blockification means obtaining a special number by performing a digest on the subject information. The obtained special number can uniquely correspond to the subject information. The digest method can be various hash algorithms, such as SHA256, etc. Then, the obtained special number is assembled with some specific data to obtain a block. Such a process is called blockification. The specific data can be the parent hash, timestamp, body hash, etc.

[0030] With such settings, first reviewing the management requirement information can ensure the feasibility of reviewing the management requirement information. Secondly, performing delivery confirmation can prevent packet loss and ensure that nodes can receive the management requirement information. Finally, performing blockification and then uploading to the blockchain can reduce the storage size of the blockchain, and the blockchain can ensure that the management requirement information cannot be tampered with, which is beneficial for future verification of the management requirement information of this version.

[0031] In a possible implementation manner, in step S200, reviewing the management requirement information includes: S210, determining whether there are specifications for supply chain data and supply chain data verification data in the management requirement information. If not, the review is unqualified.

[0032] It can be understood that supply chain data refers to the data of an enterprise's supply chain transactions. The supply chain data can be various documents. Supply chain data verification data refers to the verification result data of the supply chain data. The supply chain data verification data can be a list. First, a computer program can perform a preliminary review of the management requirement information to determine whether there are unique keywords and format samples for supply chain data and supply chain data verification data in the management requirement information. When they exist, the preliminary review by the computer program is passed.

[0033] With such settings, the manual review cost can be reduced.

[0034] S220. If it exists, obtain the number of the first operations on all management nodes. If the number of the first operations is greater than or equal to a preset number, the management requirement information passes the review. Herein, the first operation is an operation by which a user approves the management requirement information on a management node.

[0035] It can be understood that after a preliminary review by a computer program, all management nodes vote on the management requirement information. The first operation refers to an operation of casting an approval vote. Obtaining the number of the first operations on all management nodes is the number of approval votes. When the number of approval votes is greater than or equal to the preset number, it means that the management requirement information passes the review.

[0036] With such a setting, the management requirement information can be successfully reviewed only after being voted on by all management nodes.

[0037] In a possible implementation manner, in step S200, the blockification includes: S230. Obtain a hash value of the information to be blockified to obtain a block body.

[0038] It can be understood that the algorithm for obtaining the hash value can be various hash algorithms, such as SHA256. By performing SHA256 calculation on the entire management requirement information, the block body can be obtained.

[0039] With such a setting, it is not necessary to upload the entire information to be blockified to the blockchain, greatly saving the blockchain storage space.

[0040] S240. Obtain a parent hash. Herein, the parent hash refers to the hash value of the block header of the last block of the blockchain when generating a management block.

[0041] It can be understood that the blockchain is a data structure formed by connecting multiple blocks in a single line. When each block is generated, the last block of the blockchain is called the parent block of the block being generated. By performing SHA256 calculation on the block header of the parent block, the parent hash can be obtained.

[0042] With such a setting, the blocks are cascaded level by level to form a blockchain.

[0043] S250. Obtain a timestamp. Herein, the timestamp is used to reflect the time when the block is created.

[0044] It can be understood that the computer times of all nodes can be counted together, and the median of all times is found, which is the timestamp. A certain number of maximum values and minimum values can also be removed before taking the median to improve the rationality of the timestamp.

[0045] With such a setting, the time when the block is created can be obtained in a decentralized manner.

[0046] S260, calculating the hash value of the block body to obtain the body hash.

[0047] It can be understood that performing SHA256 calculation on the block body means performing SHA256 calculation on the blockized information twice to obtain the body hash.

[0048] With this setting, the block header and block body can be connected, and when the block body is modified, the block header will also be modified.

[0049] S270, fill the parent hash, timestamp and body hash into the predetermined template to obtain a block header.

[0050] It can be understood that the parent hash, timestamp and body hash are substituted into the template to obtain the block header. The template may include a frame header and a frame body. The frame header may be a special sequence to indicate that the signal sent is a block header. The frame body may be the parent hash, timestamp and body hash arranged in a fixed order, with a special sequence between each.

[0051] With this setting, the block header can be obtained quickly and reasonably.

[0052] S280, assemble the block header and the block body into a block.

[0053] It can be understood that a special sequence can be set before the block header and the block body. When the computer reads the sequence, it can distinguish the block header and the block body, and then compose the block header and the block body into blocks in order; after being combined into blocks, the management block is uploaded to the local blockchain supervision system of the operating node, and then the local blockchain supervision system sends the block to the neighboring node through the computer network, and the blockchain supervision system of the neighboring node sends the block to its neighboring node, and so on, the block is sent to all nodes, and the upload of the blockchain is completed.

[0054] With this setup, any information can be segmented.

[0055] S300, receiving supply chain data uploaded by the enterprise node, wherein the supply chain data is used to reflect the transaction status of the enterprise's supply chain, and the supply chain data meets the specification requirements of the management requirement information.

[0056] It can be understood that the supply chain data can be various electronic documents. The format samples of the supply chain data are obtained from the management requirement information to meet the standard requirements of the management requirement information. The supply chain data can include total import data and total export data, and the total import data and total export data are subdivided into detailed different types of import data and export data, and pictures can be posted after each import data and export data.

[0057] Such a setting is conducive to verifying supply chain data.

[0058] S400 sends the supply chain data to all management nodes and determines the delivery. Then, the supply chain data is block-formed and uploaded to the blockchain.

[0059] It can be understood that after the supply chain data is sent to all management nodes, the regulatory party can allocate work offline. Different management nodes are responsible for verifying different supply chain data. And after block-forming the supply chain data and uploading it to the blockchain, since the supply chain data is different from the management requirement information, the block-forming process is not exactly the same. The block-forming of the supply chain data can add some information on the block header based on the block-forming of the management requirement information, such as the version of the management requirement information that the supply chain data conforms to, the number of the enterprise node that uploads the supply chain data, and so on.

[0060] With such a setting, it can be ensured that the supply chain data will not be tampered with, which is beneficial to verifying the supply chain data in the future.

[0061] S500 receives the supply chain data verification data uploaded by the management nodes. Among them, the supply chain data verification data is used to reflect the authenticity of all supply chain data after the management nodes verify all the supply chain data, and the supply chain data verification data meets the specification requirements of the management requirement information.

[0062] It can be understood that the verification process of the supply chain data can be to compare the supply chain data between enterprises. For example, if the supply chain data of the first enterprise indicates that the first enterprise imported the first transaction from the second enterprise, then look in the supply chain data of the second enterprise to find out whether the second enterprise exported the first transaction to the first enterprise. After finding problems through comparison, manually contact the two enterprises with problems to verify and obtain the verification result. After the management nodes complete the verification of the supply chain data, the supply chain data verification data is obtained. The supply chain data verification data can be a list, which can include columns for enterprise names, enterprise numbers, verification results, modification suggestions, and attachments. The columns for enterprise names and enterprise numbers are used to indicate enterprises, the column for verification results is used to indicate the verification results of the supply chain data, the column for modification suggestions is used to indicate the unqualified positions in the supply chain data during verification, and the column for attachments is used to add some attachment materials.

[0063] With such a setting, it is beneficial for enterprises to quickly find the verification results of the supply chain data, as well as how to modify and re-upload the supply chain data.

[0064] S600 sends the supply chain data verification data to all enterprise nodes and determines the delivery. Then, the supply chain data verification data is block-formed and uploaded to the blockchain.

[0065] It can be understood that the supply chain data verification data is sent to all enterprise nodes, and then the supply chain data verification data is block-formed and uploaded to the blockchain. Some important information can be added to the block header during the block-forming process of the supply chain data verification data, such as the verification count and the qualified count. The verification count refers to the number of supply chain data items verified against the supply chain data verification data, and the qualified count refers to the number of qualified items among the verified supply chain data.

[0066] With such a setting, the verification count and the qualified count are conducive to ensuring that all enterprise nodes are verified, and when enterprise nodes re-upload supply chain data, no nodes will be missed.

[0067] Optionally, the method further includes: S710, detecting the first time period and the second time period selected by the management node, and sending the first time period and the second time period to all enterprise nodes and performing delivery determination. Among them, the first time period and the second time period are two different time periods without intersection, and enterprise nodes can upload supply chain data within the first time period and the second time period.

[0068] It can be understood that the first time period and the second time period are two non-intersecting time periods, which are used for enterprise nodes to upload supply chain data, and the time interval between the first time period and the second time period is the time for the management node to verify the supply chain data.

[0069] With such a setting, the data upload times of the management node and the enterprise nodes are arranged more reasonably.

[0070] S720, if an enterprise node fails to upload supply chain data within the first time period or the uploaded supply chain data fails the verification, notify the corresponding enterprise node to resubmit the supply chain data within the second time period. If the supply chain data still fails the verification or is not submitted, deal with the enterprise node corresponding to the supply chain data that fails the verification or is not submitted.

[0071] It can be understood that if an enterprise node fails to upload supply chain data within the first time period or the uploaded supply chain data fails the verification, mark the verification result of the enterprise node in the supply chain data verification data, and then send a notification signal to notify the corresponding enterprise node to resubmit the supply chain data within the second time period. If the supply chain data submitted within the second time period still fails the verification or is not submitted, perform relevant processing. The relevant processing can be fining, notifying to submit again, or kicking out of the supervision system, etc.

[0072] With such a setting, the supervision process becomes more reasonable.

[0073] Optionally, the method further includes: S730 detects the first request, second request, or third request of the management node. Among them, the first request refers to a request to add an enterprise node, the second request refers to a request to delete an enterprise node, and the third request refers to a request to add a management node.

[0074] It can be understood that the blockchain supervision system constantly detects the first request, second request, or third request proposed by the management node. The first request, second request, or third request can be a preset signal (the number of the enterprise node to be deleted is included in the second request). When the blockchain supervision system detects the preset signal, it performs subsequent operations on the first request, second request, or third request.

[0075] With such a setting, due to the reason that blockchain technology has no central point, when a user loses their account or password, they cannot retrieve the account or password by requesting the server (the accounts and passwords of all nodes are stored in the blockchain), and can only create a completely new node. Therefore, the request to add an enterprise node is a necessary function of the blockchain supervision system, which can solve the problem that when a user loses their account or password, they cannot retrieve the account or password by requesting the server; because an enterprise may suspend operations for various reasons, such as going bankrupt, etc., and the number of enterprises in the blockchain supervision system is a key parameter, so the function of deleting an enterprise node is a necessary function of the blockchain supervision system, which can ensure the stable operation of the blockchain supervision system.

[0076] S740, when the first request is detected, a new account and password for an enterprise node are created, and data processing is performed on the account and password of the newly created node to obtain an account block, and then the account block is uploaded to the second blockchain. Among them, the account block refers to a data structure that stores the accounts and passwords of one or more nodes, and the second blockchain is stored on the computer network composed of all nodes.

[0077] It can be understood that when the first request is detected, at this time, the blockchain supervision system creates a new account and password for an enterprise node. The account and password of the enterprise node can be randomly generated or given by the user; after obtaining the account and password of the newly created node, the account and password can be uploaded to the second blockchain. Before uploading to the second blockchain, data processing similar to blockification needs to be performed on the account and password to obtain an account block (it can be simplified based on the blockification operation, such as not requiring a block header, timestamp, etc.), and the password also needs to be encrypted. The encryption process can be to calculate the hash value of the password.

[0078] With such a setting, the function of the blockchain supervision system can be improved.

[0079] In a possible implementation manner, in step S740, performing data processing on the account and password of the newly created node to obtain an account block includes: S741. Hash the password of the newly created node to obtain the password hash value.

[0080] It can be understood that the information uploaded to the second blockchain is stored in all computers of the computer network. If a conventional encryption algorithm is used, the encryption algorithm itself also needs to be uploaded to the second blockchain for the blockchain supervision system to decrypt, and the encryption function cannot be achieved. Therefore, a hash algorithm can be used to hash the password of the node to obtain the password hash value.

[0081] With such a setting, the account security level of the blockchain supervision system can be improved.

[0082] S742. Combine the accounts of all newly created nodes and the corresponding password hash values into N account groups. Here, N is the number of newly created nodes, and an account group includes the account of a newly created node and the corresponding password hash value.

[0083] It can be understood that the blockchain supervision system can create the accounts and passwords of multiple new nodes at one time. The account and password hash value of one node form an account group. When N newly created nodes are created at one time, a total of N account groups are formed.

[0084] With such a setting, storing the account passwords of different nodes separately can improve the speed of the blockchain supervision system to verify the account passwords.

[0085] S743. Obtain the parent hash. Here, the parent hash refers to the hash value of the block header of the last block of the second blockchain when generating a block.

[0086] It can be understood that the parent hash is necessary in the blockchain and can connect different blocks. For other block-forming steps, such as timestamps, block headers, and block bodies, etc., since the account passwords of the blockchain supervision system belong to time-invariant information, a timestamp is not required. Also, since the amount of information of the account passwords is small, the block header step and block body step are not required either.

[0087] With such a setting, the link function between account blocks is realized.

[0088] S744. Combine the N account groups and the parent hash into an account block in a predetermined order.

[0089] It can be understood that a special sequence can be set before the parent hash and the account group respectively. When the computer reads the sequence, it can distinguish the parent hash and the account group, and then combine the parent hash and the N account groups into an account block in order.

[0090] With such a setting, the block-forming steps of the account block can be simplified, and the speed of obtaining the account block can be improved.

[0091] S750. When the second request is detected, obtain the accounts of the corresponding enterprise nodes, add the accounts to the sealed list, and upload the sealed list after blockification to the second blockchain. The sealed list is used to record the accounts of the deleted enterprise nodes.

[0092] It can be understood that when the second request is detected, the blockchain supervision system obtains the accounts of the enterprise nodes to be deleted from the second request, which can be one or more accounts. List the accounts of the enterprise nodes to be deleted into a sealed list, and then upload the sealed list after blockification to the second blockchain (a special sequence can be set before the sealed list for the computer to identify the block storing the sealed list). The blockification step can be the blockification steps of S230 to S280. When an account requests to log in, the blockchain supervision system first reads all the blocks in the second blockchain that store the sealed list, then extracts the complete sealed list, and determines whether the account requesting to log in is in the sealed list. If it is in the sealed list, the login is not allowed.

[0093] With such a setting, the function of the blockchain supervision system can be improved.

[0094] S760. When the third request is detected, generate an account and password for a management node, perform data processing on the newly created node account and password to obtain an account block, and then upload the account block to the second blockchain.

[0095] It can be understood that when the third request is detected, the blockchain supervision system newly creates an account and password for a management node. The account and password of the management node can be randomly generated or given by the user. After obtaining the account and password of the newly created node, the account and password can be uploaded to the second blockchain. Before uploading to the second blockchain, data processing similar to blockification needs to be performed on the account and password to obtain an account block (simplification can be performed on the basis of the blockification operation, such as not requiring a block header, timestamp, etc.), and the password also needs to be encrypted. The encryption process can be to calculate the hash value of the password.

[0096] With such a setting, the function of the blockchain supervision system can be improved.

[0097] Optionally, the method further includes: S810. The management node performs a first verification process on the supply chain data. The first verification process refers to verifying a single supply chain data separately.

[0098] It is understandable that to verify the supply chain data of an enterprise, one can first check the supply chain data of the enterprise alone. For example, check whether the total purchase amount is equal to the sum of all sub-purchase amounts, or check whether the total shipment amount is equal to the sum of all sub-shipment amounts. The total purchase amount and the total shipment amount can be verified through tax information to determine whether the supply chain data provided by the enterprise is self-consistent.

[0099] With such a setting, the supply chain data of an enterprise can be initially verified.

[0100] In a possible implementation, in step S810, the management node performs a first verification process on the supply chain data, including: S811, the management node checks whether the sum of all sub-purchase data in the supply chain data is equal to the total purchase data. Here, the sub-purchase data refers to the purchase amount of a commodity, and the total purchase data refers to the purchase amount of all commodities.

[0101] It is understandable that the management node adds up the amounts of all sub-purchase data in a supply chain data to determine whether it is equal to the amount of the total purchase data. The authenticity of the total purchase data can be verified according to tax information.

[0102] With such a setting, the authenticity of the purchase data in the supply chain data can be checked.

[0103] S812, the management node checks whether the sum of all sub-shipment data in the supply chain data is equal to the total shipment data. Here, the sub-shipment data refers to the shipment amount of a commodity, and the total shipment data refers to the shipment amount of all commodities.

[0104] It is understandable that the management node adds up the amounts of all sub-shipment data in a supply chain data to determine whether it is equal to the amount of the total shipment data. The authenticity of the total shipment data can be verified according to tax information.

[0105] With such a setting, the authenticity of the shipment data in the supply chain data can be checked.

[0106] S813, if the sum of all sub-purchase data in the supply chain data is equal to the total purchase data and the sum of all sub-shipment data in the supply chain data is equal to the total shipment data, then the first verification process is verified as qualified; otherwise, the first verification process is verified as unqualified.

[0107] It is understandable that when the purchase data and the shipment data of a supply chain data are both verified as qualified, the first verification process of the supply chain data is verified as qualified. When other situations occur, such as the purchase data is verified as qualified but the shipment data is verified as unqualified, the shipment data is verified as qualified but the purchase data is verified as unqualified, or both the purchase data and the shipment data are verified as unqualified, then the first verification process of the supply chain data is verified as unqualified.

[0108] With such a setting, the first verification process can initially verify the authenticity and self-consistency of the supply chain data.

[0109] S820. The management node performs a second verification process on the supply chain data. Among them, the second verification process refers to jointly verifying all the supply chain data.

[0110] It can be understood that the method of further verifying the supply chain data is to jointly verify multiple supply chain data to make the sub-shipment data and sub-inbound data correspond one by one, find out the conflicting or non-corresponding transaction records to verify the authenticity of the supply chain data. If the transaction target of the shipment data or inbound data in the supply chain data is not in the blockchain supervision system, the enterprise can be required to provide invoices or other transaction certificates to verify the corresponding transaction records.

[0111] With such a setting, the authenticity of the supply chain data can be further verified.

[0112] In a possible implementation manner, in step S820, the management node performs a second verification process on the supply chain data, including: S821. The management node distributes the supply chain data of all enterprises as decentralized nodes, and uses the transaction records between the supply chain data as connections. Among them, the supply chain data of one enterprise is one node.

[0113] It can be understood that the supply chain data of all enterprises are distributed as nodes in a decentralized manner. Subsequently, the transaction records in the supply chain data are read, and the transaction records between two nodes are used as the lines connecting the two nodes. The "connection" can be that one of the two nodes of the trading parties sends the transaction record to the other node, and after the other node receives the transaction record, it returns 0, 1 or no return value (when the transaction records are aligned, 1 is sent, when they are not aligned, 0 is sent, and when there is no transaction record, there is no return value). According to the return value, it can be known that the status of the line has three states: non-conflicting, conflicting, and unable to connect (non-conflicting means that the transaction records of the two trading parties correspond (that is, 1 is returned), conflicting means that the transaction records of the two trading parties do not correspond (that is, 0 is returned), and unable to connect means that one of the two trading parties has no transaction record (that is, no return value)). Reading the supply chain data of all enterprises completes the connection of the entire transaction network.

[0114] With such a setting, the abnormal transaction records in the supply chain data can be quickly and conveniently found to implement the second verification process of the supply chain data.

[0115] S822. The management node judges one of the supply chain data. If there is no conflict or inability to connect in all the connections of the selected supply chain data, the second verification process of the selected supply chain data is verified to be qualified; otherwise, the second verification process of the selected supply chain data is verified to be unqualified.

[0116] It can be understood that after completing the connection between the supply chain data of all enterprises, the management node can check the supply chain data one by one. When the management node selects a supply chain data, it determines whether there is a conflict or an inability to connect in all the connections of the supply chain data. If so, it means that the second verification process has failed, and then it is deduced to all supply chain data to complete the second verification process for all supply chain data.

[0117] With such an arrangement, the result of the second verification process of a company's supply chain data can be obtained quickly.

[0118] S830, when the first verification process is verified to be qualified and the second verification process is also verified to be qualified, the corresponding supply chain data is verified to be qualified.

[0119] It can be understood that when the supply chain data uploaded by an enterprise passes the first verification process and the second verification process, the corresponding supply chain data verification is qualified.

[0120] With this arrangement, the results of the supply chain data passing through the first verification process and the second verification process are shown.

[0121] S840: When the first verification process is verified to be qualified and the second verification process is verified to be unqualified, a manual verification is performed to determine the verification result of the corresponding supply chain data.

[0122] It is understandable that when the supply chain data uploaded by an enterprise passes the first verification process but fails the second verification process, it means that one or both of the two companies in the transaction have fraud problems. Therefore, manual verification can be carried out and both companies can be required to provide additional transaction evidence to determine the verification results of the corresponding supply chain data.

[0123] This arrangement shows the result that the supply chain data passes the first verification process but fails the second verification process.

[0124] S850, when the first verification process fails the verification, the corresponding supply chain data fails the verification.

[0125] It can be understood that when the first verification process of the supply chain data uploaded by an enterprise fails, then regardless of whether the second verification process is qualified, the supply chain data uploaded by the enterprise will fail the verification.

[0126] This arrangement shows the result that the supply chain data does not pass the first verification process.

[0127] For the communication process between management nodes and enterprise nodes, Figure 2 shows an example of the communication process between a management node and an enterprise node, Figure 2There are a total of n + 1 enterprises in the blockchain supervision system in the example.

[0128] It should be understood that the magnitudes of the sequence numbers of the steps in the above embodiments do not mean the order of execution. The order of execution of each process should be determined according to its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0129] Corresponding to the blockchain-based supply chain data supervision method described in the above embodiments, the embodiments of the present application further provide a supply chain data supervision system, and each module of the system can implement each step of the blockchain-based supply chain data supervision method. Figure 3 The structural block diagram of the supply chain data supervision system provided by the embodiments of the present application is shown. For the sake of convenience of description, only the parts related to the embodiments of the present application are shown.

[0130] Refer to Figure 3 , the system includes: A receiving unit, configured to receive the management requirement information uploaded by the management node, receive the supply chain data uploaded by the enterprise node, and receive the supply chain data verification data uploaded by the management node; A review unit, configured to review the management requirement information; A sending unit, configured to send the management requirement information to all management nodes and enterprise nodes and determine the delivery, and is further configured to send the supply chain data to all management nodes and determine the delivery, and is further configured to send the supply chain data verification data to all enterprise nodes and determine the delivery; A block-forming unit, configured to block the management requirement information and upload it to the blockchain, and is further configured to block the supply chain data and upload it to the blockchain, and is further configured to block the supply chain data verification data and upload it to the blockchain.

[0131] It should be noted that for the information interaction, execution process, etc. between the above units, since they are based on the same concept as the method embodiments of the present application, their specific functions and the technical effects brought about can be specifically referred to in the method embodiment part, and will not be elaborated here.

[0132] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the above division of each functional unit is used as an example. In practical applications, the above functions can be allocated to different functional units as needed, that is, the internal structure of the system can be divided into different functional units or modules to complete all or part of the functions described above. Each functional unit in the embodiment can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. In addition, the specific names of each functional unit are only for the convenience of mutual distinction and do not limit the protection scope of this application. The specific working process of the units in the above system can refer to the corresponding process in the foregoing method embodiment and will not be elaborated here.

[0133] The embodiment of this application also provides a supply chain data supervision device. Figure 4 It is a schematic structural diagram of the supply chain data supervision device provided in an embodiment of this application. As Figure 4 shown, the supply chain data supervision device 4 of this embodiment includes: at least one processor 40 ( Figure 4 only one is shown in the figure), at least one memory 41 ( Figure 4 only one is shown in the figure), and a computer program 42 stored in the at least one memory 41 and operable on the at least one processor 40. When the processor 40 executes the computer program 42, the supply chain data supervision device 4 implements the steps in any of the foregoing method embodiments of the supply chain data supervision method based on blockchain, or enables the supply chain data supervision device 4 to implement the functions of each unit in the foregoing system embodiments.

[0134] Exemplarily, the computer program 42 can be divided into one or more units. The one or more units are stored in the memory 41 and executed by the processor 40 to complete this application. The one or more units can be a series of computer program instruction segments capable of completing specific functions, and these instruction segments are used to describe the execution process of the computer program 42 in the supply chain data supervision device 4.

[0135] The supply chain data supervision device 4 can be a mobile phone, a tablet computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a desktop computer, a computer, or a laptop computer. The supply chain data supervision device 4 may include, but is not limited to, a processor 40 and a memory 41. Those skilled in the art can understand that Figure 4This is only an example of the supply chain data supervision device 4, and does not constitute a limitation on the supply chain data supervision device 4. It may include more or fewer components than those shown in the figure, or combine some components, or different components. For example, it may also include input / output devices, network access devices, buses, etc.

[0136] The processor 40 may be a central processing unit (CPU), and the processor 40 may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0137] In some embodiments, the memory 41 may be an internal storage unit of the supply chain data supervision device 4, such as the hard disk or memory of the supply chain data supervision device 4. In other embodiments, the memory 41 may also be an external storage device of the supply chain data supervision device 4, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc., equipped on the supply chain data supervision device 4. Further, the memory 41 may also include both the internal storage unit and the external storage device of the supply chain data supervision device 4. The memory 41 is used to store an operating system, application programs, a boot loader, data, and other programs, such as the program code of the computer program, etc. The memory 41 may also be used to temporarily store data that has been output or will be output.

[0138] An embodiment of the present application also provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.

[0139] An embodiment of the present application provides a computer program product, and when the computer program product runs on a supply chain data supervision device, the supply chain data supervision device implements the steps in any of the above method embodiments.

[0140] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, to implement all or part of the processes in the above-mentioned embodiment methods of this application, a computer program can be used to instruct relevant hardware to complete. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps of the above-mentioned various method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file or some intermediate forms, etc. The computer-readable medium can at least include: any entity or device that can carry the computer program code to the supply chain data supervision device, recording medium, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electrical carrier signal, telecommunication signal, and software distribution medium. For example, USB flash drive, mobile hard disk, magnetic disk or optical disc, etc.

[0141] In the above embodiments, the descriptions of the various embodiments have their own emphases. For the parts not detailed or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0142] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0143] In the embodiments provided by this application, it should be understood that the disclosed blockchain-based supply chain data supervision method, supply chain data supervision device, and supply chain data supervision equipment can be implemented in other ways. For example, the above-described blockchain-based supply chain data supervision method, supply chain data supervision device, and supply chain data supervision equipment embodiments are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical or other forms.

[0144] The unit described as a separation component may or may not be physically separated. The component shown as a unit may or may not be a physical unit, that is, it may be located in one place or may be distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0145] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included within the protection scope of the present application.

Claims

1. A supply chain data supervision method based on blockchain, characterized in that: Applied to a blockchain supervision system, the blockchain supervision system includes multiple management nodes and enterprise nodes, and the blockchain supervision system runs in a computer network composed of all nodes. The method includes: Receive management requirement information uploaded by the management node; The management requirement information is reviewed, and after passing the review, the management requirement information is sent to all management nodes and enterprise nodes and the delivery is confirmed, and then the management requirement information is block-uploaded to the blockchain; wherein, the delivery confirmation refers to detecting whether the sent information is delivered, and if not, the corresponding information is sent repeatedly, and the blockchain is stored in a computer network composed of all nodes; Receiving supply chain data uploaded by an enterprise node; wherein the supply chain data is used to reflect the transaction status of the enterprise's supply chain, and the supply chain data meets the specification requirements of the management requirement information; Send the supply chain data to all management nodes and confirm the delivery, then block the supply chain data and upload it to the blockchain; Receive supply chain data verification data uploaded by the management node; wherein the supply chain data verification data is used to reflect the authenticity of all the supply chain data after the management node verifies all the supply chain data, and the supply chain data verification data meets the specification requirements of the management requirement information; The supply chain data verification data is sent to all enterprise nodes and the delivery is confirmed, and then the supply chain data verification data is block-ified and uploaded to the blockchain.

2. The supply chain data supervision method as claimed in claim 1, characterized in that: The review of the management requirement information includes: Determine whether the management requirement information contains specifications for the supply chain data and the supply chain data verification data; if not, the review is unqualified; If it exists, the number of first operations on all management nodes is obtained. If the number of first operations is greater than or equal to the preset number, the management requirement information is reviewed and qualified; wherein, the first operation is an operation in which the user agrees to the management requirement information on the management node.

3. The supply chain data supervision method according to claim 1, characterized in that: The block-based approach includes: Obtain the block body by calculating the hash value of the blockized information; Obtaining a parent hash; wherein the parent hash refers to the hash value of the block header of the last block of the blockchain when the block is generated; Obtain a timestamp; wherein the timestamp is used to reflect the time when the block was created; Calculating a hash value for the block body to obtain a body hash; Fill the parent hash, the timestamp and the body hash into a predetermined template to obtain the block header; The block header and the block body are combined into a block.

4. The supply chain data supervision method according to claim 1, characterized in that: The method further comprises: Detecting a first time period and a second time period selected by the management node, and sending the first time period and the second time period to all enterprise nodes and performing delivery confirmation; wherein the first time period and the second time period are two different time periods and have no intersection, and the enterprise nodes can upload the supply chain data within the first time period and the second time period; If the enterprise node fails to upload the supply chain data within the first time period or the uploaded supply chain data fails verification, the corresponding enterprise node is notified to resubmit the supply chain data within the second time period. If the supply chain data still fails verification or is not submitted, the enterprise node corresponding to the supply chain data that fails verification or fails to submit is processed.

5. The supply chain data supervision method according to claim 1, characterized in that: The method further comprises: Detecting a first request, a second request, or a third request of a management node; wherein the first request is a request to add an enterprise node, the second request is a request to delete an enterprise node, and the third request is a request to add a management node; When the first request is detected, a new account and password of an enterprise node are created, and data processing is performed on the account and password of the newly created node to obtain an account block, and then the account block is uploaded to the second blockchain; wherein the account block refers to a data structure storing the account and password of one or more nodes, and the second blockchain is stored on a computer network composed of all nodes; When the second request is detected, the account number of the corresponding enterprise node is obtained, the account number is included in the sealed list, and the sealed list is block-uploaded to the second blockchain; wherein the sealed list is used to record the account number of the deleted enterprise node; When the third request is detected, an account and password for a management node are generated, and data processing is performed on the newly created node account and password to obtain the account block, and then the account block is uploaded to the second blockchain.

6. The supply chain data supervision method according to claim 5, characterized in that: The data processing of the account and password of the newly created node to obtain the account block includes: Calculate the hash value of the password of the newly created node to obtain the password hash value; All accounts of the newly created nodes and the corresponding password hash values ​​are grouped into N account groups; wherein N is the number of newly created nodes, and one account group includes an account of a newly created node and the corresponding password hash value; Obtaining a parent hash; wherein the parent hash refers to the hash value of the block header of the last block of the second blockchain when the block is generated; The N account groups and the parent hash are combined into the account block in a predetermined order.

7. The supply chain data supervision method according to claim 1, characterized in that: After the management node receives the supply chain data, the method further includes: The management node performs a first verification process on the supply chain data; wherein the first verification process refers to verifying a single piece of supply chain data; The management node performs a second verification process on the supply chain data; wherein the second verification process refers to a joint verification of all the supply chain data; When the first verification process is verified to be qualified and the second verification process is also verified to be qualified, the corresponding supply chain data is verified to be qualified; When the first verification process is verified to be qualified and the second verification process is verified to be unqualified, a manual verification is performed to determine the verification result of the corresponding supply chain data; When the first verification process fails the verification, the corresponding supply chain data fails the verification.

8. The supply chain data supervision method according to claim 7, characterized in that: The management node performs a first verification process on the supply chain data, including: The management node checks whether the sum of all sub-purchase data in the supply chain data is equal to the total purchase data; wherein the sub-purchase data refers to the purchase amount of a commodity, and the total purchase data refers to the purchase amount of all commodities; The management node checks whether the sum of all sub-shipment data in the supply chain data is equal to the total shipment data; wherein the sub-shipment data refers to the shipment amount of a commodity, and the total shipment data refers to the shipment amount of all commodities; If the sum of all the sub-purchase data in the supply chain data is equal to the total purchase data, and the sum of all the sub-shipment data in the supply chain data is equal to the total shipment data, then the first verification process is verified to be qualified, otherwise the first verification process is verified to be unqualified.

9. The supply chain data supervision method according to claim 8, characterized in that: The management node performs a second verification process on the supply chain data, including: The management node distributes the supply chain data of all enterprises as decentralized nodes, and uses the transaction records between the supply chain data as connections; wherein the supply chain data of one enterprise is one node; The management node judges one of the supply chain data. If there is no conflict or connection failure in all the connections of the selected supply chain data, the second verification process of the selected supply chain data is verified to be qualified; otherwise, the second verification process of the selected supply chain data is verified to be unqualified.

10. A supply chain data supervision device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 9 is implemented.

Images