IP Library › Granted Patent US 12,602,646
Granted Patent B2
US 12,602,646 · App. 17/837,620 · Granted Apr 14, 2026

Systems and methods for controlled data sharing in supply chains

Inventors: Lingyun Hu (Brooklyn, NY); Anand Banik (Rogers, AR); Harika Addagada (Bentonville, AR); Coran J. Coley (Bentonville, AR); Zachary Bell (Rogers, AR); Pushparaj Parab (Bentonville, AR); Haritha Gunawardana (Piscataway, NJ); Weihong Ou (Bentonville, AR)
Assignee: WALMART APOLLO, LLC
G06Q10/0835G06Q10/087G06Q30/04H04L9/50
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,602,646
App. No.
17/837,620
Granted
Apr 14, 2026
Kind
B2
Abstract

Methods and systems for controlled data sharing are provided. A method includes: communicating, as a first node of a supply chain distributed ledger, with a second node and a third node of the ledger, the nodes corresponding to a first entity, a second entity, and a third entity in a supply chain; storing, with a data management module, a hash of a public version of a contract between the first entity and the second entity; replicating the hash of the public version of the contract to the ledger; sharing a private version of the contract between the first and second nodes; storing a hash of a public version of a purchase order between the first entity and the third entity; replicating the hash of the public version of the purchase order to the ledger; and sharing a private version of the purchase order between the first and third nodes.

Claims (50)

1 . A system for controlled data sharing comprising:

a network interface; and

a control circuit coupled to the network interface, the control circuit to:

communicate, as a first node of a supply chain distributed ledger and via the network interface, with a second node and a third node of the supply chain distributed ledger, the nodes corresponding to a first entity, a second entity, and a third entity in a supply chain;

create and store a cryptographic hash of a public version of a first set of data involving the first entity and the second entity at the first node;

replicate the cryptographic hash of the public version of the first set of data to the supply chain distributed ledger, the cryptographic hash of the public version of the first set of data being accessible to all of the three entities;

share a cryptographic hash of a private version of the first set of data between the first and second nodes, the cryptographic hash of the private version of the first set of data being shared peer-to-peer between, and accessible by, only the first and second entities;

create and store a cryptographic hash of a public version of a second set of data involving the first entity and the third entity at the first node;

replicate the cryptographic hash of the public version of the second set of data to the supply chain distributed ledger, the cryptographic hash of the public version of the second set of data being accessible to all of the three entities;

share a cryptographic hash of a private version of the second set of data between the first and third nodes, the cryptographic hash of the private version of the second set of data being shared peer-to-peer, and accessible by, only the first and third entities;

receive an update from a scanning device, the update automatically triggered and transmitted based on scans, by the scanning device, of one or more images of damaged products owned by the first entity and being transported by the second entity;

store, at the first node, the one or more images of the damaged products; and

share, with the second node, the one or more images of the damaged products.

2 . The system of claim 1 , wherein the first entity is a purchaser of products, the second entity is a carrier of the products, and third entity is a supplier of the products.

3 . The system of claim 1 , wherein the first set of data comprises a contract, the public version of the contract including information indicating existence of the contract but not actual contract terms.

4 . The system of claim 1 , wherein the first set of data comprises a contract, the public version of the contract not including at least one of origin, destination, container type, carrier identification data, or carrier rate data.

5 . The system of claim 1 , wherein the second set of data comprises a purchase order, the public version of the purchase order including at least one of product identifier, product name, and product quantity.

6 . The system of claim 1 , wherein the second set of data comprises a purchase order, the public version of the purchase order not including item price data.

7 . The system of claim 1 , wherein the control circuit to:

receive, as the first node of the supply chain distributed ledger and via the network interface, a carrier invoice from the second node, the carrier invoice being shared peer-to-peer between, and accessible by, only the first and second entities.

8 . The system of claim 1 , wherein the control circuit to:

receive, as the first node of the supply chain distributed ledger and via the network interface, a supplier invoice from the third node, the supplier invoice being shared peer-to-peer between, and accessible by, only the first and third entities.

9 . The system of claim 1 , wherein the control circuit to:

share product shipment data from a supplier invoice of the third entity with the second entity to generate a carrier invoice.

10 . The system of claim 1 , wherein the control circuit to:

maintain data integrity and share a third set of data with a fourth entity being a regulatory agency, the third set of data being shared peer-to-peer, and accessible by, only the first and fourth entities.

11 . The system of claim 1 , wherein:

when a plurality of blocks having a same block identifier as each other is received at the first node, the first node verifies the plurality of blocks and temporarily stores the plurality of blocks if they pass verification; and

the first node uses a subsequent block to determine which of the plurality of blocks is a correct or consensus block.

12 . The system of claim 1 , wherein a longest chain of blocks in the supply chain distributed ledger is retrieved following the first node going offline, each new block added since the first node has been offline is verified, and a local copy of the supply chain distributed ledger is updated.

13 . A method for controlled data sharing comprising:

communicating, as a first node of a supply chain distributed ledger and via a network interface, with a second node and a third node of the supply chain distributed ledger, the nodes corresponding to a first entity, a second entity, and a third entity in a supply chain;

creating and storing, by a control circuit, a cryptographic hash of a public version of a first set of data involving the first entity and the second entity at the first node;

replicating, by the control circuit, the cryptographic hash of the public version of the first set of data to the supply chain distributed ledger, the cryptographic hash of the public version of the first set of data being accessible to all of the three entities;

sharing, by the control circuit, a cryptographic hash of a private version of the first set of data between the first and second nodes, the cryptographic hash of the private version of the first set of data being shared peer-to-peer between, and accessible by, only the first and second entities;

creating and storing, by the control circuit, a cryptographic hash of a public version of a second set of data involving the first entity and the third entity at the first node;

replicating, by the control circuit, the cryptographic hash of the public version of the second set of data to the supply chain distributed ledger, the cryptographic hash of the public version of the second set of data being accessible to all of the three entities;

sharing, by the control circuit, a cryptographic hash of a private version of the second set of data between the first and third nodes, the cryptographic hash of the private version of the second set of data being shared peer-to-peer, and accessible by, only the first and third entities;

receiving, by the control circuit, an update from a scanning device, the update automatically triggered and transmitted based on scans, by the scanning device, of one or more images of damaged products owned by the first entity and being transported by the second entity;

storing, at the first node, the one or more images of the damaged products; and

sharing, with the second node, the one or more images of the damaged products.

14 . The method of claim 13 , wherein the first entity is a purchaser of products, the second entity is a carrier of the products, and third entity is a supplier of the products.

15 . The method of claim 13 , wherein the first set of data comprises a contract, the public version of the contract including information indicating existence of the contract but not actual contract terms.

16 . The method of claim 13 , wherein the first set of data comprises a contract, the public version of the contract not including at least one of origin, destination, container type, carrier identification data, or carrier rate data.

17 . The method of claim 13 , wherein the second set of data comprises a purchase order, the public version of the purchase order including at least one of product identifier, product name, and product quantity.

18 . The method of claim 13 , wherein the second set of data comprises a purchase order, the public version of the purchase order not including item price data.

19 . The method of claim 13 , further comprising, by the control circuit:

receiving, as the first node of the supply chain distributed ledger and via the network interface, a carrier invoice from the second node, the carrier invoice being shared peer-to-peer between, and accessible by, only the first and second entities.

20 . The method of claim 13 , further comprising, by the control circuit:

receiving, as the first node of the supply chain distributed ledger and via the network interface, a supplier invoice from the third node, the supplier invoice being shared peer-to-peer between, and accessible by, only the first and third entities.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 10, 2022
From: HU, LINGYUN; BANIK, ANAND; ADDAGADA, HARIKA; COLEY, CORAN J.; BELL, ZACHARY; PARAB, PUSHPARAJ; GUNAWARDANA, HARITHA; OU, WEIHONG
To: WALMART APOLLO, LLC
Reel/Frame 060171/0424 →
Continuity (1)
Related Publication 20230401526A1 · Dec 14, 2023
References Cited (17)
US 8560461B1 · Tian · 2013 [cited by applicant]
US 20190080284A1 · Kim · 2019 [cited by applicant]
US 20210157947A1 · Biazetti · 2021 [cited by examiner]
US 20210209546A1 · Ramachandran · 2021 [cited by applicant]
US 20230401525A1 · Hu · 2023 [cited by applicant]
CN 112035574 · 2020 [cited by applicant]
WO 2021128733 · 2021 [cited by applicant]
WO 2021231408 · 2021 [cited by applicant]
Wan, Paul Kengfai, Lizhen Huang, and Halvor Holtskog. “Blockchain-enabled information sharing within a supply chain: A systematic literature review.” IEEE access 8 (2020): 49645-49656. (Year: 2020). [cited by examiner]
Hussain, Muhammad Tariq; “How Blockchain Based Smart-Contracts Can Improve Invoicing Accuracy”; <https://www.researchgate.net/publication/344575012_HOW_BLOCKCHAIN_BASED_SMART-CONTRACTS_CAN_IMPROVE_INVOICING_ACCURACY>; A… [cited by applicant]
Mearian, Lucas; “Walmart launches ‘world's largest’ blockchain-based freight-and-payment network”; <https://www.computerworld.com/article/3454336/walmart-launches-world-s-largest-blockchain-based-freight-and-payment-net… [cited by applicant]
Amazon; “Amazon Managed Blockchain Hyperledger Fabric Developer Guide”; <https://www.syncids.com/#/app/show=todo&term=154405&filterType=smart>: available at least as early as Mar. 11, 2022; 135 pages. [cited by applicant]
Hyperledger Fabric; “Private data”; <https://hyperledger-fabric.readthedocs.io/en/release-2.2/private-data/private-data.html>; Sep. 20, 2020; 13 pages; retrieved from Internet Archive Wayback Machine <http://web.archive… [cited by applicant]
USPTO; U.S. Appl. No. 17/837,322; Final Rejection mailed Mar. 12, 2024; (pp. 1-20). [cited by applicant]
USPTO; U.S. Appl. No. 17/837,322; Non-Final Rejection mailed Sep. 9, 2024; (pp. 1-17). [cited by applicant]
USPTO; U.S. Appl. No. 17/837,322; Non-Final Rejection mailed Nov. 2, 2023; (14 pages). [cited by applicant]
USPTO; U.S. Appl. No. 17/837,322; Final Rejection mailed Feb. 10, 2025; (pp. 1-18). [cited by applicant]