Supply chain data sharing method and system

Abstract

The invention is suitable for the technical field of data sharing, and particularly relates to a supply chain data sharing method and system.The method comprises the steps that providers of supply chain data are determined, the providers comprise a dominator and collaborators, the supply chain data of the collaborators are obtained, segmentation and packaging are carried out, an object package and a quantity package are obtained, and the object package and the quantity package are sent to a server; utilizing a preset numbering rule to configure a unique identifier of each piece of supply chain data, and establishing a corresponding relationship among the unique identifier, the object packet and the quantity packet; and storing the object packet and the quantity packet in different dominators respectively. According to the method, the target data is subjected to hash, and the target data can be pushed to the collaborator after verification, so that the security of the supply chain data in the storage and sharing process is ensured while the supply chain data is normally called, the management efficiency of the enterprise supply chain data is greatly improved, and the user experience is improved. And the digital and intelligent development of the supply chain is promoted.

Description

Technical Field

[0001] The present invention relates to the technical field of data sharing, and in particular to a supply chain data sharing method and system. Background Art

[0002] Supply chain data refers to various information and data related to supply chain management. These data cover the entire process from raw material procurement to final product delivery, including inventory levels, order status, transportation information, supplier and customer data, production plans, logistics information and sales data. Supply chain data reflects the operational information of the entire enterprise. Complete supply chain data can make the enterprise's production and sales process more coordinated and improve the work efficiency of staff.

[0003] However, some existing smaller enterprises are usually unable to establish a dedicated supply chain data management system due to limited resources. This leads to the dispersion of supply chain data. When staff need to obtain data, a lot of docking work is required. There is a lack of unified storage and management methods. If the data is managed by a third party, it is difficult to ensure data security. Therefore, "how to provide a supply chain data security management solution for small-scale enterprises" is the technical problem that the present invention needs to solve. Summary of the Invention

[0004] The purpose of the present invention is to provide a supply chain data sharing method and system to solve the problem raised in the above background technology of "how to provide a supply chain data security management solution for small-scale enterprises".

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] A supply chain data sharing method, comprising:

[0007] Identify the providers of supply chain data, including the leader and collaborators, obtain the collaborators' supply chain data, segment and package it into object packages and quantity packages, configure a unique identifier for each piece of supply chain data using a preset numbering rule, and establish a correspondence between the unique identifier, object package, and quantity package;

[0008] The object package and quantity package are stored in different leaders respectively, a hash function is selected to hash the object package and quantity package to obtain a hash value, which is defined as a tag value, and the tag value is sent to all leaders in parallel, and a synchronous update mechanism is embedded;

[0009] Configure the user account of each collaborator, and define the sharing scope of the user account in each leader, and copy the tag value to the sharing scope;

[0010] After receiving the sharing request uploaded by the provider, the supply chain data corresponding to the sharing request is traversed and defined as the target data. The corresponding unique identifier is extracted, and the supply chain data is hashed based on the corresponding relationship to determine whether the hash value is the same as the tag value. If so, the sharing permission of the target data is opened. If not, the target data is pushed to the collaborator and the target data is restored.

[0011] Furthermore, the steps of determining the providers of the supply chain data, wherein the providers include: a leader and a collaborator, obtaining the supply chain data of the collaborator, and performing segmentation and packaging include:

[0012] Selecting sensitive data from the supply chain data, locating the storage locations of the sensitive data, object packages, and quantity packages, and making adjustments;

[0013] A query table is constructed, wherein the query table at least includes: a supply chain data item, a storage location item, and a unique identifier item.

[0014] Furthermore, the steps of dividing and packaging to obtain object packages and quantity packages include:

[0015] Dividing the supply chain data into object classes and quantity classes, and packaging them to obtain object packages and quantity packages;

[0016] An authentication mechanism is embedded into the object package and the quantity package.

[0017] Furthermore, the step of storing the object package and the quantity package in different leaders respectively, selecting a hash function, hashing the object package and the quantity package to obtain a hash value, and defining the hash value as a tag value includes:

[0018] Selecting a redundant node from the provider to dynamically back up the supply data;

[0019] A label is generated using the tag value, and the label is inserted into the corresponding redundant node.

[0020] Furthermore, the steps of configuring the user account of each collaborator, defining a shared scope of the user account in each leader, and copying the tag value to the shared scope include:

[0021] Obtaining permission types, where the permission types include at least: read, write, and modify, determining the supply chain data corresponding to the sharing scope, and establishing a mapping between the user account, permission type, and sharing scope;

[0022] The authority to adjust the mapping is opened to the leader.

[0023] Furthermore, the synchronous update mechanism is: when it is monitored that the supply chain data in the leader has changed, the changed supply chain data is hashed using a hash function, and the tag value is updated using the obtained hash value.

[0024] Furthermore, the step of hashing the supply chain data and determining whether the obtained hash value is the same as the tag value includes:

[0025] Integrate a timestamp into the tag value, integrate the timestamp, tag value and supply chain data to generate a version, and record version changes based on the synchronous update mechanism;

[0026] A version backtracking mechanism is created using the version changes.

[0027] Furthermore, a configuration module is configured to determine the providers of supply chain data, wherein the providers include: a leader and a collaborator, obtain the supply chain data of the collaborator, segment and package it into object packages and quantity packages, configure a unique identifier for each supply chain data using a preset numbering rule, and establish a correspondence between the unique identifier, the object package, and the quantity package;

[0028] an embedding module, configured to store the object package and quantity package in different leaders respectively, select a hash function, hash the object package and quantity package to obtain a hash value, define the hash value as a tag value, distribute the tag value to all leaders in parallel, and embed a synchronous update mechanism;

[0029] A copy module is used to configure the user account of each collaborator, and define the sharing range of the user account in each leader, and copy the tag value into the sharing range;

[0030] The recovery module is used to traverse the supply chain data corresponding to the sharing request after receiving the sharing request uploaded by the provider, define it as the target data, extract the corresponding unique identifier, hash the supply chain data through the corresponding relationship, and determine whether the obtained hash value is the same as the tag value. If so, the sharing permission of the target data is opened; if not, the target data is pushed to the collaborator and the target data is restored.

[0031] Furthermore, the configuration module includes:

[0032] an adjustment unit, configured to select sensitive data from the supply chain data, locate the storage locations of the sensitive data, object packages, and quantity packages, and make adjustments;

[0033] A construction unit, configured to construct a query table, wherein the query table comprises at least: a supply chain data item, a storage location item, and a unique identifier item;

[0034] a segmentation unit, configured to segment the supply chain data into object classes and quantity classes, and package the data into object packages and quantity packages;

[0035] The verification unit is used to embed an identity authentication mechanism into the object package and the quantity package.

[0036] Furthermore, the embedded module includes:

[0037] A backup unit, configured to select a redundant node from the provider and dynamically back up the supply data;

[0038] The inserting unit is configured to generate a label using the tag value and insert the label into the corresponding redundant node.

[0039] Compared with the prior art, the present invention has the following beneficial effects:

[0040] By determining the provider, the present invention can centrally manage the supply chain data and improve the management efficiency of the supply chain data. By dividing and packaging the supply chain data and storing it in different leaders, the privacy of the provider can be guaranteed, and the supply chain data can be prevented from being tampered with during the storage process. By selecting a hash function, the efficiency of calling the supply chain data can be greatly improved, and the changes in the supply chain data can be recorded to provide a data basis for enterprise decision-making. By creating and using accounts, data sharing between providers and leaders can be achieved, and by defining the sharing scope, sensitive information can be protected, data security can be enhanced, and the risk of data sharing can be reduced. By hashing the target data, the target data can be pushed to the collaborator after verification, thereby ensuring the security of the supply chain data while performing normal calls on the supply chain data, greatly improving the management efficiency of the enterprise supply chain data, and promoting the digitalization and intelligent development of the supply chain. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention.

[0042] Figure 1 This is a flowchart of the supply chain data sharing method provided by an embodiment of the present invention.

[0043] Figure 2 This is a block diagram of the first sub-process of the supply chain data sharing method provided in an embodiment of the present invention.

[0044] Figure 3 This is a block diagram of the second sub-process of the supply chain data sharing method provided in an embodiment of the present invention.

[0045] Figure 4 This is a block diagram of the third sub-process of the supply chain data sharing method provided in an embodiment of the present invention.

[0046] Figure 5 This is a block diagram of the fourth sub-process of the supply chain data sharing method provided in an embodiment of the present invention.

[0047] Figure 6 This is a block diagram of the supply chain data sharing system provided by an embodiment of the present invention.

[0048] Figure 7 This is a block diagram of the configuration module in the supply chain data sharing system provided by an embodiment of the present invention.

[0049] Figure 8 This is a block diagram of the composition of the embedded modules in the supply chain data sharing system provided by an embodiment of the present invention.

[0050] Figure 9 This is a block diagram of the composition of the replication module in the supply chain data sharing system provided by an embodiment of the present invention.

[0051] Figure 10 This is a block diagram of the composition of the recovery module in the supply chain data sharing system provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0053] In Example 1, Figure 1 The implementation process of the supply chain data sharing method provided by an embodiment of the present invention is shown and described in detail below:

[0054] S100: Determine the providers of supply chain data, where the providers include: leaders and collaborators, obtain the supply chain data of the collaborators, and split and package them to obtain object packages and quantity packages. Use preset numbering rules to configure a unique identifier for each supply chain data, and establish a corresponding relationship between the unique identifier, object package and quantity package.

[0055] Find out the providers, which are manufacturers, enterprises and companies that need to manage supply chain data. The providers are divided into two parts. The first part is that they have their own supply chain data management system (leader). Since there may be data sharing needs between enterprises using the system, the system may also transmit supply chain data to enterprises. Therefore, they are also considered to be the party providing data and included in the provider; the second part is smaller enterprises (collaborators), which generally obtain and process supply chain data through manual recording; find out the supply chain data of collaborators, split the supply chain data, and package it after splitting. The splitting is to split the supply chain data so that it can be stored in different locations to avoid single-point storage and improve data security, while the packaging of the supply chain data is to ensure the integrity of the data.

[0056] For example, the existing supply chain data: "Supplier name: XXX Company, Nanjing, Jiangsu Province, Supply category: Plastic casing, Annual production capacity: 5 million pieces"; the supply chain data is segmented and packaged to obtain object package 1: supplier name, object package 2: supply category, object package 3: annual production capacity, quantity package 1: XXX Company, Nanjing, Jiangsu Province, quantity package 2: plastic casing, quantity package 35 million pieces.

[0057] According to the numbering rules, each object package and quantity package is numbered, and the obtained number is defined as a unique identifier. The numbering rules are pre-established by professionals. It should be noted that in the above example, the unique identifiers of object package 1 and quantity package 1 are the same, the unique identifiers of object package 2 and quantity package 2 are the same, and so on.

[0058] In this embodiment, the collaborator stores the supply chain data in two leaders and realizes the sharing of supply chain data between the leader and the collaborator by using accounts; in addition, when it is necessary to query the supply chain data of other collaborators, all quantity packages or object packages can be directly retrieved.

[0059] S200: The object package and quantity package are stored in different leaders respectively, a hash function is selected, the object package and quantity package are hashed to obtain a hash value, and the hash value is defined as a tag value, the tag value is sent to all leaders in parallel, and a synchronous update mechanism is embedded.

[0060] Randomly select two leaders from the providers, store the object package in one of the leaders, and store the quantity package in the other leader; use SHA-256, MD5 or a custom hash function to hash the object package and quantity package, and define the resulting hash value as the tag value; the advantage of hashing the quantity package and object package is that it can promptly detect whether the supply chain data has been tampered with during the storage process. At the same time, through hashing, the corresponding relationship between the object package and the quantity package can also be established; a synchronous update mechanism centered on the tag value is constructed, where the synchronous update mechanism is: when the object package and quantity package change, the tag value is updated at the same time.

[0061] S300: configuring a user account for each collaborator, defining a sharing range of the user account in each leader, and copying the tag value into the sharing range.

[0062] In the supply chain management system of the leader, an account is configured for each collaborator. Through this account, the collaborator can not only retrieve the supply chain data stored in the leader, but also share the supply chain data with the leader after verification and obtain the supply chain data of other companies. Of course, this process requires both parties of data interaction to provide clear authorization. At this time, the leader is equivalent to a third-party platform, establishing a data sharing channel between the two collaborators, but for any collaborator, it only interacts with the leader. Before sharing, the sharing scope of the leader or collaborator is defined, and the tag value corresponding to the supply chain data within the sharing scope is determined. By setting the tag value, it can quickly identify whether the supply chain data within the sharing scope has changed.

[0063] S400: After receiving the sharing request uploaded by the provider, traverse the supply chain data corresponding to the sharing request and define it as the target data, extract the corresponding unique identifier, hash the supply chain data through the corresponding relationship, and determine whether the hash value is the same as the tag value. If so, open the sharing permission of the target data. If not, push the target data to the collaborator and restore the target data.

[0064] In the technical solution of the present invention, data interaction may actually occur between the leaders. For example, when the supply chain data of two collaborators are stored in different leaders, and the two collaborators have reached a data sharing agreement, the collaborator interacts with the leader that stores its data, and the leader that stores its data interacts with another leader to obtain the supply chain data of another collaborator stored in the other leader.

[0065] When a provider (who may be the leader or a collaborator) needs to query the supply chain data of other providers, the supply chain data that needs to be queried is defined as the target data, and the unique identifier corresponding to the target data is found. The retrieved supply chain data is hashed using the unique identifier to determine whether the hash value is the same as the tag value. If they are the same, it means that the supply chain data has not been tampered with during the storage process. At this time, the sharing permission of the target data is opened to the provider so that it can query and call the target data. On the contrary, if the hash value is different from the tag value, it means that the supply chain data has been tampered with. The collaborator corresponding to the target data is found, and the collaborator restores the target data based on the corresponding relationship.

[0066] Continuing to elaborate on the example in S100, when a provider needs to inquire about the annual production capacity of plastic casings of XXX Company in Nanjing, Jiangsu Province, the annual production capacity is defined as the target data, and the corresponding quantity package is found through the unique identifier of the object package corresponding to the target data. The quantity package and the object package are hashed to determine whether the obtained hash value is the same as the tag value.

[0067] In Example 2, Figure 2 The implementation process of the supply chain data sharing method provided by an embodiment of the present invention is shown. The following details the steps of determining the providers of supply chain data, where the providers include: a leader and a collaborator, obtaining the supply chain data of the collaborator, and performing segmentation and packaging, as follows:

[0068] S101: Select sensitive data from the supply chain data, locate the storage locations of the sensitive data, object packages, and quantity packages, and make adjustments.

[0069] Sensitive data is selected from the collaborator's supply chain data, and the object package and quantity package corresponding to the sensitive data are stored in the collaborator's preset storage location, where the preset storage location can be a local device or a mobile device.

[0070] S102: Construct a query table, wherein the query table at least includes: a supply chain data item, a storage location item, and a unique identifier item.

[0071] Construct a query table, which includes: object package items, quantity package items, storage location items, etc. By constructing the query table, the storage location of the supply chain data can be quickly located, improving retrieval efficiency.

[0072] In Example 3, Figure 2 The implementation process of the supply chain data sharing method provided by an embodiment of the present invention is shown. The steps of splitting and packaging to obtain object packages and quantity packages are described in detail below:

[0073] S103: Divide the supply chain data into object classes and quantity classes, and package them to obtain object packages and quantity packages.

[0074] As mentioned above, all supply chain data are divided into object classes and quantity classes, and after packaging, object packages and quantity packages are obtained.

[0075] S104: Embed an identity authentication mechanism into the object package and quantity package.

[0076] An authentication mechanism is embedded in the object package and quantity package, where the authentication mechanism is: the provider can directly query the data in the object package or quantity package, but when it needs to query the data in another package, its identity needs to be verified.

[0077] For example, a provider wants to query all manufacturers that can provide plastic casings. At this time, the provider can directly retrieve all public object packages and quantity packages to find all manufacturers that can provide plastic casings. However, if the provider needs to view the specific quantity, that is, the corresponding quantity package, its identity needs to be verified.

[0078] In Example 4, Figure 3 The implementation process of the supply chain data sharing method provided by an embodiment of the present invention is shown. The following details the steps of storing the object package and quantity package in different leaders, selecting a hash function, hashing the object package and quantity package, obtaining a hash value, and defining it as a tag value.

[0079] S201: Select a redundant node from the provider and dynamically back up the supply data.

[0080] The collaborator's supply chain data is divided into object packages or quantity packages, and stored in two leaders respectively; redundant nodes are found, which are leaders other than the two leaders mentioned above, and the redundant nodes are used to dynamically back up the collaborator's supply chain data; for example, the object package of a collaborator is stored in leader A, and the quantity package is stored in leader B, and then leader C is selected, and C is used to back up the quantity package and object package.

[0081] It should be noted that the leader C is a higher-level concept, which may actually include multiple leaders for backing up data and ensuring data security. Of course, a special leader C can also be equipped to back up data. In this case, the security management module of the leader C must be more sophisticated because it backs up a large amount of data and can easily become a target of attack. Of course, the function of the leader C is backup, and it can also encrypt the supply chain data, and the encryption key is determined by the party being backed up.

[0082] S202: Generate a label using the tag value, and insert the label into the corresponding redundant node.

[0083] When using redundant nodes to back up quantity packages and object packages, the corresponding tag values ​​should also be backed up at the same time; in other words, insert labels generated by tag values ​​into redundant nodes, and when the quantity packages and object packages in the redundant nodes change, the tag values ​​in the labels are updated at the same time.

[0084] In Example 5, Figure 4 The implementation process of the supply chain data sharing method provided by an embodiment of the present invention is shown. The following details the steps of configuring the user account of each collaborator, defining the user account sharing range in each leader, and copying the tag value to the sharing range.

[0085] S301: Obtain permission types, where the permission types include at least: read, write and modify, determine the supply chain data corresponding to the sharing scope, and establish a mapping between the user account, permission type and sharing scope.

[0086] After determining the sharing scope of supply chain data, establish a mapping between each user account and the sharing scope and permission type. By building the mapping, not only can the access rights of different user accounts to supply chain data be precisely controlled, but the sharing scope and access rights can also be dynamically adjusted.

[0087] S302: Opening the mapping adjustment authority to the leader.

[0088] In actual operation, since the supply chain data of the collaborators are also stored in the supply chain data management system of the leader, the leader can adjust the permission type of the collaborators. For example, collaborator A stores supply chain data A in the supply chain data management system of leaders B and C. However, there must be other supply chain data in this supply chain data management system. Therefore, the permission type for sharing other supply chain data should be determined by the leader.

[0089] In Example 6, the synchronous update mechanism in S200 is: when it is monitored that the supply chain data in the leader has changed, the changed supply chain data is hashed using a hash function, and the tag value is updated using the obtained hash value.

[0090] When supply chain data is called or modified, a hash function is used to hash the called or modified supply chain data, and the original tag value is replaced based on the generated hash value. The advantage of this is that the irreversible nature of the hash value can be used to quickly record changes in the supply chain data so that the supply chain data can be tracked and managed.

[0091] In Example 7, Figure 5 The implementation process of the supply chain data sharing method provided by an embodiment of the present invention is shown. The following details the steps of hashing the supply chain data and determining whether the obtained hash value is the same as the tag value.

[0092] S401: Integrate a timestamp into the tag value, integrate the timestamp, tag value and supply chain data, generate a version, and record version changes based on the synchronous update mechanism.

[0093] As mentioned above, when the tag value is updated, a timestamp is added to the tag value, the update time of the tag value is recorded, the supply chain data corresponding to the tag value is used as the version content, and the timestamp and tag value are used as version attributes to generate a version; when the tag value is updated, a new version is generated, and while recording the version changes, the historical version is retained.

[0094] S402: Using the version change, create a version backtracking mechanism.

[0095] The version backtracking mechanism is: every time the version changes, a unique version number is generated and the version number is used to retrieve the version.

[0096] Figure 6 The following is a structural block diagram of a supply chain data sharing method and system according to an embodiment of the present invention. The supply chain data sharing system 1 includes:

[0097] Configuration module 11 is used to determine the providers of supply chain data, including the leader and collaborators, obtain the collaborators' supply chain data, segment and package it into object packages and quantity packages, configure a unique identifier for each piece of supply chain data using a preset numbering rule, and establish a correspondence between the unique identifier, object package, and quantity package;

[0098] An embedding module 12 is configured to store the object package and quantity package in different leaders respectively, select a hash function, hash the object package and quantity package to obtain a hash value, define the hash value as a tag value, distribute the tag value to all leaders in parallel, and embed a synchronous update mechanism;

[0099] The copy module 13 is used to configure the user account of each collaborator, and define the sharing range of the user account in each leader, and copy the tag value into the sharing range;

[0100] The recovery module 14 is used to traverse the supply chain data corresponding to the sharing request after receiving the sharing request uploaded by the leader, define it as the target data, extract the corresponding unique identifier, hash the supply chain data through the corresponding relationship, and determine whether the obtained hash value is the same as the tag value. If so, open the sharing permission of the target data; if not, push the target data to the collaborator and restore the target data.

[0101] Figure 7 The following is a structural diagram of the supply chain data sharing system provided by an embodiment of the present invention. The configuration module 11 includes:

[0102] An adjustment unit 111 is configured to select sensitive data from the supply chain data, locate the storage locations of the sensitive data, object packages, and quantity packages, and perform adjustments;

[0103] A construction unit 112 is configured to construct a query table, wherein the query table includes at least: a supply chain data item, a storage location item, and a unique identifier item;

[0104] A segmentation unit 113 is used to segment the supply chain data into object classes and quantity classes, and package them to obtain object packages and quantity packages;

[0105] The verification unit 114 is configured to embed an identity authentication mechanism into the object package and the quantity package.

[0106] Figure 8 The following is a structural block diagram of the supply chain data sharing system provided by an embodiment of the present invention. The embedded module 12 includes:

[0107] The backup unit 121 is used to select redundant nodes from the provider and divide them into several partitions to dynamically back up the supply data;

[0108] The inserting unit 122 is configured to generate a label using the tag value and insert the label into the corresponding partition.

[0109] Figure 9 The structure diagram of the supply chain data sharing system provided by an embodiment of the present invention is shown. The replication module 13 includes:

[0110] A mapping unit 131 is configured to obtain permission types, wherein the permission types include at least: read, write, and modify, determine the supply chain data corresponding to the sharing scope, and establish a mapping between the user account, permission type, and sharing scope;

[0111] The opening unit 132 is configured to open the mapping adjustment authority to the leader.

[0112] Figure 10 The following is a structural block diagram of the supply chain data sharing system provided by an embodiment of the present invention. The recovery module 14 includes:

[0113] A recording unit 141 is configured to integrate a timestamp into the tag value, integrate the timestamp, tag value, and supply chain data, generate a version, and record version changes based on the synchronous update mechanism;

[0114] The creating unit 142 is configured to create a version backtracking mechanism using the version change.

[0115] The configuration module 11 is mainly used to complete step S100, the embedding module 12 is mainly used to complete step S200, the copy module 13 is mainly used to complete step S300, and the recovery module 14 is mainly used to complete step S400;

[0116] The adjustment unit 111 is mainly used to complete step S101, the construction unit 112 is mainly used to complete step S102, the segmentation unit 113 is mainly used to complete step S103, and the verification unit 114 is mainly used to complete step S104;

[0117] The backup unit 121 is mainly used to complete step S201, and the insertion unit 122 is mainly used to complete step S202;

[0118] The mapping unit 131 is mainly used to complete step S301, and the opening unit 132 is mainly used to complete step S302;

[0119] The recording unit 141 is mainly used to complete step S401, and the creating unit 142 is mainly used to complete step S402.

[0120] The above are only preferred embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention description and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A supply chain data sharing method, characterized in that: The method comprises: Identify the providers of supply chain data, including the leader and collaborators, obtain the collaborators' supply chain data, segment and package it into object packages and quantity packages, configure a unique identifier for each piece of supply chain data using a preset numbering rule, and establish a correspondence between the unique identifier, object package, and quantity package; The object package and quantity package are stored in different leaders respectively, a hash function is selected to hash the object package and quantity package to obtain a hash value, which is defined as a tag value, and the tag value is sent to all leaders in parallel, and a synchronous update mechanism is embedded; Configure the user account of each collaborator, define the sharing range of the user account in each leader, and copy the tag value into the sharing range; After receiving the sharing request uploaded by the provider, the supply chain data corresponding to the sharing request is traversed and defined as the target data. The corresponding unique identifier is extracted, and the supply chain data is hashed based on the corresponding relationship to determine whether the hash value is the same as the tag value. If so, the sharing permission of the target data is opened. If not, the target data is pushed to the collaborator and the target data is restored.

2. The supply chain data sharing method according to claim 1, characterized in that: The steps of determining the providers of the supply chain data, wherein the providers include: a leader and a collaborator, obtaining the supply chain data of the collaborator, and performing segmentation and packaging include: Selecting sensitive data from the supply chain data, locating storage locations of the sensitive data, object packages, and quantity packages, and adjusting the storage locations; A query table is constructed, wherein the query table at least includes: a supply chain data item, a storage location item, and a unique identifier item.

3. The supply chain data sharing method according to claim 2, characterized in that: The steps of dividing and packaging to obtain the object package and quantity package include: Dividing the supply chain data into object classes and quantity classes, and packaging them to obtain object packages and quantity packages; An authentication mechanism is embedded into the object package and the quantity package.

4. The supply chain data sharing method according to claim 1, characterized in that: The steps of storing the object package and the quantity package in different leaders, selecting a hash function, hashing the object package and the quantity package, obtaining a hash value, and defining the hash value as a tag value include: Selecting a redundant node from the provider to dynamically back up the supply data; A label is generated using the tag value, and the label is inserted into the corresponding redundant node.

5. The supply chain data sharing method according to claim 1, characterized in that: The steps of configuring the user account of each collaborator, defining the user account sharing range in each leader, and copying the tag value to the sharing range include: Obtaining permission types, where the permission types include at least: read, write, and modify, determining the supply chain data corresponding to the sharing scope, and establishing a mapping between the user account, permission type, and sharing scope; The authority to adjust the mapping is opened to the leader.

6. The supply chain data sharing method according to claim 1, characterized in that: The synchronous update mechanism is: when it is monitored that the supply chain data in the leader has changed, the changed supply chain data is hashed using a hash function, and the tag value is updated using the obtained hash value.

7. The supply chain data sharing method according to claim 1, characterized in that: The step of hashing the supply chain data and determining whether the obtained hash value is the same as the tag value includes: Integrate a timestamp into the tag value, integrate the timestamp, tag value and supply chain data to generate a version, and record version changes based on the synchronous update mechanism; A version backtracking mechanism is created using the version changes.

8. A supply chain data sharing system, characterized in that: The system comprises: A configuration module is used to determine the providers of supply chain data, including the leader and collaborators, obtain the collaborators' supply chain data, segment and package it into object packages and quantity packages, configure a unique identifier for each piece of supply chain data using a preset numbering rule, and establish a correspondence between the unique identifier, the object package, and the quantity package; an embedding module, configured to store the object package and quantity package in different leaders respectively, select a hash function, hash the object package and quantity package to obtain a hash value, define the hash value as a tag value, distribute the tag value to all leaders in parallel, and embed a synchronous update mechanism; A copy module is used to configure the user account of each collaborator, and define the sharing range of the user account in each leader, and copy the tag value into the sharing range; The recovery module is used to traverse the supply chain data corresponding to the sharing request after receiving the sharing request uploaded by the provider, define it as the target data, extract the corresponding unique identifier, hash the supply chain data through the corresponding relationship, and determine whether the obtained hash value is the same as the tag value. If so, the sharing permission of the target data is opened; if not, the target data is pushed to the collaborator and the target data is restored.

9. The supply chain data sharing system according to claim 8, characterized in that: The configuration module includes: an adjustment unit, configured to select sensitive data from the supply chain data, locate the storage locations of the sensitive data, object packages, and quantity packages, and make adjustments; A construction unit, configured to construct a query table, wherein the query table comprises at least: a supply chain data item, a storage location item, and a unique identifier item; a segmentation unit, configured to segment the supply chain data into object classes and quantity classes, and package the data into object packages and quantity packages; The verification unit is used to embed an identity authentication mechanism into the object package and the quantity package.

10. The supply chain data sharing system according to claim 8, characterized in that: The embedded module includes: A backup unit, configured to select a redundant node from the provider and dynamically back up the supply data; The inserting unit is configured to generate a label using the tag value and insert the label into the corresponding redundant node.

Images