IP Library Granted Patent US 12,430,463
Granted Patent B1
US 12,430,463 · App. 18/100,544 · Granted Sep 30, 2025

Token-based digital private data exchange systems, methods, and apparatus

Inventors: Nicholas J. Witchey (Laguna Hills, CA); Patrick Soon-Shiong (Los Angeles, CA)
Assignee: Nant Holdings IP, LLC
G06F21/6245H04L9/008G06F2221/2141
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,430,463
App. No.
18/100,544
Granted
Sep 30, 2025
Kind
B1
Abstract

Systems, apparatus, and methods of managing access to private data via tokens are disclosed. The disclosed techniques provide for constructing digital tokens that represent a right-to-access private data where the tokens can be managed as individual objects. Further, such digital access tokens (DATs) can be recorded on a notarized ledger, a blockchain for example. Additionally, the rights-to-access can be embodied as a non-fungible token (NFT), which could further include support for establishing homomorphic encryption workspaces in which private data can be accessed or manipulated without exposing the private data.

Claims (46)

1. A computer-based data escrow system comprising:

at least one computer-readable, non-transitory memory storing software instructions;

at least one private database storing private data records associated with an authorized computing device having an authorization identifier, wherein the private data records comprise field-value entries; and

at least one processor coupled with the at least one memory and that executes the software instructions and thereby performs operations of:

receiving, over a network, a request of a first computing device other than the authorized computing device for at least some of the private data records, the request including a requested field of interest from at least one field from the at least some of the private data records;

storing, upon a determination based on the authorization identifier that the first computing device is authorized to access the at least some of the private data records, at least one value corresponding to the requested field of interest from the at least some of the private data records in a private data escrow that is separate from the private data records;

generating, in the at least one memory, a data access token (DAT) as a non-fungible token (NFT) responsive to the request, the DAT NFT comprising at least a data access token identifier, a token owner identifier representing the first computing device as an owner of the DAT NFT but not of the at least some of the private data records, and a data access activation protocol (DAAP) executable to access at least one value in the private data escrow;

recording the DAT NFT on a corresponding notarized ledger operating as a record-keeping system, wherein the DAT NFT is accessible by the first computing device;

authenticating the first computing device and validating the first computing device based on at least the data access token identifier and the token owner identifier; and

in accordance with authenticating the first computing device, validating the first computing device, and an execution of the DAAP within the DAT NFT:

sending instructions to a second computing device operated by a second entity thereby enabling the second computing device to interact with the at least one value of the at least one field of interest via the private data escrow, the at least one value of the at least one field of interest being unavailable for interaction to the second computing device via the at least some of the private data records.

2. The system of claim 1 , wherein the private data escrow is separate from the second computing device; and

wherein the authorized computing device includes at least one of the following: a data owner, a government, a corporation, an authentication server, and a device.

3. The system of claim 1 , wherein the authorization identifier comprises at least one of the following: a name, a universally unique identifier (UUID), a globally unique identifier (GUID), a hash, and a token.

4. The system of claim 1 , wherein the token owner identifier comprises at least one of the following: a name, a universally unique identifier (UUID), a globally unique identifier (GUID), a hash, an address associated with the notarized ledger, and a token.

5. The system of claim 1 , wherein the DAT NFT further comprises an authentication key of the authorized computing device and a data access key of the owner of the DAT NFT.

6. The system of claim 1 , wherein the DAT NFT comprises a pointer to off-ledger data.

7. The system of claim 1 , wherein the DAT NFT is a member of a multi-token set.

8. The system of claim 1 , wherein the DAT NFT comprises a bearer token.

9. The system of claim 1 , wherein the DAT NFT comprises a non-transferable token.

10. The system of claim 1 , wherein the DAAP provides exclusive access to the at least some of the private data records for the owner of the DAT NFT.

11. The system of claim 1 , wherein the DAAP includes a homomorphic context.

12. The system of claim 11 , wherein the homomorphic context configures the second computing device to interact with the at least one value of the at least one field of interest via a homomorphic workspace external to the second computing device.

13. The system of claim 12 , wherein the homomorphic workspace is external to the at least one memory and the at least one private database.

14. The system of claim 1 , wherein the DAAP comprises serialized instructions targeting execution on at least the second computing device.

15. The system of claim 1 , wherein the DAAP is stored in an encrypted format and includes encoded information that the second computing device uses to interact with the at least one value.

16. The system of claim 1 , wherein the DAAP comprises a smart contract.

17. The system of claim 1 , wherein the DAAP comprises data access restriction criteria restricting data access of the owner of the DAT NFT to the at least some of the private data records.

18. The system of claim 17 , wherein at least one criterion of the data access restriction criteria is based on an access counter.

19. The system of claim 17 , wherein at least one criterion of the data access restriction criteria is based on time.

20. The system of claim 17 , wherein at least one criterion of the data access restriction criteria is based on a location of the second computing device.

21. The system of claim 17 , wherein at least one criterion of the data access restriction criteria comprises at least one token termination criterion.

22. The system of claim 1 , wherein the DAAP comprises a data access application program interface (API).

23. The system of claim 1 , wherein the DAT NFT comprises a for-fee token.

24. The system of claim 23 , wherein the DAT NFT is generated upon the authorized computing device receiving a fee from the owner of the DAT NFT.

25. The system of claim 1 , wherein the operations further include causing at least some of the private data to be escrowed in the private data escrow in a private data store off the notarized ledger.

26. The system of claim 25 , wherein the DAT NFT represents the private data escrow.

27. The system of claim 1 , wherein the operations further include updating an SNMP MIB based on a transaction associated with DAT NFT and associated with the notarized ledger.

28. The system of claim 27 , wherein the operations further including causing a dashboard to render the updated SNMP MIB associated with the notarized ledger DAT NFT transaction.

29. The system of claim 1 , wherein the operations further comprise:

receiving a request to change ownership of the DAT NFT to the second entity;

recording an update to the DAT NFT on the corresponding notarized ledger, the update indicating that the second entity is a new owner of the DAT NFT and recorded without providing access to the private data records to the second entity;

receiving, from a computing device operated by the second entity, an access request that includes the field of interest; and

enabling, upon authentication and validation of the new owner and according to another execution of the DAAP within the DAT NFT, the computing device operated by the second entity to interact with the at least one value of the at least one field of interest via the private data escrow.

30. The system of claim 1 , wherein the operations further comprise:

recording an update to the DAT NFT on the corresponding notarized ledger, the update associated with using the DAT NFT to access the at least one field of interest via the private data escrow.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 24, 2023
From: WITCHEY, NICHOLAS J.
To: NANTWORKS, LLC
Reel/Frame 062802/0691 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 24, 2023
From: SOON-SHIONG, PATRICK
To: NANT HOLDINGS IP, LLC
Reel/Frame 062802/0711 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 24, 2023
From: NANTWORKS, LLC
To: NANT HOLDINGS IP, LLC
Reel/Frame 062802/0718 →
Continuity (2)
Continuation In Part 17590291 · Feb 1, 2022
Provisional Application 63302484 · Jan 24, 2022
References Cited (80)
US 8752203B2 · Reinertsen · 2014 [cited by examiner]
US 10540654B1 · James · 2020 [cited by examiner]
US 11025598B1 · Laghaeian · 2021 [cited by examiner]
US 11062006B2 · Maxwell · 2021 [cited by examiner]
US 11070378B1 · Griffin · 2021 [cited by examiner]
US 11200569B1 · James · 2021 [cited by examiner]
US 11210383B2 · Witchey et al. · 2021 [cited by applicant]
US 11263630B2 · Brown · 2022 [cited by examiner]
US 11308487B1 · Foster · 2022 [cited by examiner]
US 11392717B1 · Friedlander · 2022 [cited by examiner]
US 11429969B1 · Alt · 2022 [cited by examiner]
US 11455417B2 · Yang · 2022 [cited by examiner]
US 11836690B1 · Stroke · 2023 [cited by examiner]
US 12277554B1 · James · 2025 [cited by examiner]
US 20130340093A1 · Reinertsen · 2013 [cited by examiner]
US 20160300078A1 · Wooldridge · 2016 [cited by examiner]
US 20170223005A1 · Birgisson · 2017 [cited by examiner]
US 20200160320A1 · Williams · 2020 [cited by examiner]
US 20200201967A1 · Maxwell · 2020 [cited by examiner]
US 20200286076A1 · Zhu · 2020 [cited by examiner]
US 20200374129A1 · Dilles · 2020 [cited by examiner]
US 20210012326A1 · Maxwell Zelocchi · 2021 [cited by examiner]
US 20210097508A1 · Papanikolas · 2021 [cited by examiner]
US 20210217002A1 · Basu · 2021 [cited by examiner]
US 20210232707A1 · Wilson · 2021 [cited by examiner]
US 20210258169A1 · Basu · 2021 [cited by examiner]
US 20210304200A1 · Doney · 2021 [cited by examiner]
US 20220029815A1 · Basu · 2022 [cited by examiner]
US 20220239662A1 · Conkle · 2022 [cited by examiner]
US 20220292496A1 · Yan · 2022 [cited by examiner]
US 20220309540A1 · Blaikie, III · 2022 [cited by examiner]
US 20220309542A1 · Blaikie, III · 2022 [cited by examiner]
US 20230036439A1 · Olson · 2023 [cited by examiner]
US 20230075767A1 · Bradley · 2023 [cited by examiner]
US 20230135947A1 · Barhudarian · 2023 [cited by examiner]
US 20230241543A1 · Nguyen · 2023 [cited by examiner]
US 20230421543A1 · Doney · 2023 [cited by examiner]
US 20240086876A1 · Stroke · 2024 [cited by examiner]
CA 2949449 · 2015 [cited by applicant]
EP 3408987B1 · 2019 [cited by applicant]
EP 3832975A1 · 2021 [cited by applicant]
EP 3851984A1 · 2021 [cited by applicant]
WO WO0108352A1 · 2001 [cited by examiner]
WO WO2013059794A1 · 2013 [cited by examiner]
WO 2017042375A1 · 2017 [cited by applicant]
WO 2017042400A1 · 2017 [cited by applicant]
WO WO2020051365A1 · 2020 [cited by examiner]
WO 2020146667A1 · 2020 [cited by applicant]
WO 2021102116A1 · 2021 [cited by applicant]
WO WO2021255425A1 · 2021 [cited by examiner]
⋅ Loïc Lesavre et al. “Blockchain Networks: Token Design and Management Overview.” (Feb. 2021). Retrieved online May 18, 2025. https://nvlpubs.nist.gov/nistpubs/ir/2021/NIST.IR.8301.pdf (Year: 2021). [cited by examiner]
⋅ Mark Soelman. “Permissioned Blockchains: A Comparative Study a Deep Dive into Hyperledger Fabric and Hyperledger Besu.” (Jun. 2021). Retrieved online May 18, 2025. https://fse.studenttheses.ub.rug.nl/25270/1/Final%20S… [cited by examiner]
⋅ European Parliament. “Blockchain and the General Data Protection Regulation Can distributed ledgers be squared with European data protection law?” (Jul. 2019). Retrieved online May 18, 2025. https://www.europarl.europ… [cited by examiner]
U.S. Appl. No. 17/590,291, “Final Office Action,” dated Apr. 12, 2024, 37 pages. [cited by applicant]
U.S. Appl. No. 17/590,291, “Non-Final Office Action,” dated Dec. 11, 2023, 27 pages. [cited by applicant]
U.S. Appl. No. 17/590,291, “Final Office Action,” dated Jun. 14, 2023, 20 pages. [cited by applicant]
U.S. Appl. No. 17/590,291, “Non-Final Office Action,” dated Mar. 29, 2023, 17 pages. [cited by applicant]
“How Scientists Are Embracing NFTs,” Jun. 18, 2021, Nature.com, 11 pages. [cited by applicant]
Howard, “Where is my art stored when it's released through Foundation? An IPFS primer,” Aug. 30, 2021, intercom.help, 3 pages. [cited by applicant]
Sergeenkov, “How to Mint an NFT,” published May 12, 2021, coinmarketcap.com, 10 pages. [cited by applicant]
“Token Program,” Oct. 11, 2021, Solana Program Library Docs, spl.solana.com, 25 pages. [cited by applicant]
Cvllr, “Solidity Tutorial: all about Addresses,” Aug. 1, 2019, jeancvllr.medium.com, 27 pages. [cited by applicant]
“Tutorial: mint and transfer your own ERC-721 (NFT) tokens,” Oct. 12, 2021, docs.secondstate.io, 10 pages. [cited by applicant]
Wilhelm, “Bring on the low-cost NFTs,” Nov. 3, 2021, techcrunch.com, 9 pages. [cited by applicant]
“Layer2 Rollups,” Dec. 3, 2021, ethereum.org, 11 pages. [cited by applicant]
Vogelsteller, et al., “EIP-20: Token Standard,” Aug. 27, 2021, eip.ethereum.org, 4 pages. [cited by applicant]
Reitweβner, et al., “EIP-165: Standard Interface Detection,” Aug. 30, 2021, eips.ethereum.org, 8 pages. [cited by applicant]
Entriken, et al., “EIP-721: ERC-721 Non-Fungible Token Standard,” Aug. 4, 2021, eips.ethereum.org, 14 pages. [cited by applicant]
Lockyer, et al., “EIP-998: ERC-998 Composable Non-Fungible Token Standard,” Oct. 13, 2021, eips.ethereum.org, 35 pages. [cited by applicant]
Radomski, et al., “EIP-1155: ERC-1155 Multi Token Standard,” Aug. 4, 2021, eips.ethereum.org,22 pages. [cited by applicant]
“Smart Contract Languages,” Aug. 4, 2021, ethereum.org, 10 pages. [cited by applicant]
Gorantala, et al., “A General Purpose Transpiler for Fully Homomorphic Encryption,” [email protected], Jun. 4, 2021, 10 pages. [cited by applicant]
“Introduction to Smart Contracts,” Aug. 30, 2021, ethereum.org, 6 pages. [cited by applicant]
Jones, et al., “JSON Web Token (JWT),” Internet Engineering Task Force (IETF), Standards Track, May 2015, 30 pages. [cited by applicant]
“Security Requirements for Cryptographic Modules,” National Institute of Standards and Technology,FIPS Pub 140-2, May 25, 2001, 69 pages. [cited by applicant]
Jones, et al., “The OAuth 2.0 Authorization Framework: Bearer Token Usage,” Standards Track, Oct. 2012, 18 pages. [cited by applicant]
“Distributed Monitoring with OpenNMS,” OpenNMS, 14 pages. [cited by applicant]
Polyakov, et al., “Palisade Lattice Cryptography Library User Manual (v1.11.4),” Aug. 20, 2021, 53 pages. [cited by applicant]
Oracles, “What is an Oracle,” Jul. 9, 2021, ethereum.org, 9 pages. [cited by applicant]
U.S. Appl. No. 17/590,291, “Non-Final Office Action,” dated Apr. 21, 2025, 38 pages. [cited by applicant]
Cited By (2)
US 12,481,746 US 12,500,891