US-12627486-B2 - Non-fungible token (NFT) vehicle information

Abstract

Methods and systems are described herein for transferring control of vehicle information. A transfer system may be used to facilitate the transfer. The system may receive a first request for transferring an association of a vehicle from a first user to a second user. The transfer system may generate a first blockchain operation for transferring control of the cryptographic token from a first to second cryptography-based storage application associated with the first user and second user, respectively, wherein the first blockchain operation comprises the second address associated with the second cryptography-based storage application. The system may transmit the first blockchain operation for transferring control of the cryptographic token to the second cryptography-based storage application. In response to receiving an indication of successful blockchain operation from a blockchain node, the system may transmit a command to update first user identification data stored at a link.

Inventors

• Russell DANNA
• Landon M. NEHMER
• Michael Garner

Assignees

• CAPITAL ONE SERVICES, LLC

Dates

Publication Date

20260512

Application Date

20230227

Claims (18)

1. 1 . A system for transferring control of vehicle information, the system comprising: one or more processors and one or more non-transitory computer-readable storage media storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving, from a user device, a first request for generating a non-fungible token that associates a vehicle and a first user, wherein the first request comprises (1) vehicle identification data, (2) first user identification data, and (3) a first address of a first cryptography-based storage application corresponding to the first user; storing the first user identification data at a remote computing device, wherein the storing generates a link to the first user identification data stored at the remote computing device; generating a first blockchain operation for generating the non-fungible token, wherein generating the first blockchain operation comprises: encrypting a uniform resource identifier, corresponding to the link, into an encrypted payload; and inserting the encrypted payload into the non-fungible token, wherein the non-fungible token is controlled by the first cryptography-based storage application; receiving, from the user device, a second request for transferring an association of the vehicle from the first user to a second user, wherein the second request comprises (1) an identifier of the non-fungible token, (2) second user data, and (3) a second address of a second cryptography-based storage application associated with the second user; generating a second blockchain operation for transferring control of the non-fungible token from the first cryptography-based storage application to the second cryptography-based storage application, wherein the second blockchain operation comprises the second address associated with the second cryptography-based storage application; transmitting, to the user device, the second blockchain operation for transferring control of the non-fungible token to the second cryptography-based storage application; and in response to receiving an indication of successful blockchain operation from a blockchain node, transmitting, to the remote computing device, a command to update user identification data accessible via the link, wherein the command to update includes second user identification data.
2. 2 . The system of claim 1 , wherein encrypting the uniform resource identifier comprises encrypting the uniform resource identifier into the encrypted payload using a key associated with the first cryptography-based storage application.
3. 3 . The system of claim 2 , wherein the instructions cause the one or more processors to perform operations comprising: receiving, from a second device associated with the second cryptography-based storage application, an access request for accessing the first user identification data, wherein the access request comprises the identifier of the non-fungible token; retrieve, based on the identifier of the non-fungible token in the access request, the encrypted payload associated with the non-fungible token; generating and transmitting, to the user device associated with the first cryptography-based storage application, a decryption request for decrypting the encrypted payload for accessing the first user identification data; and receiving, from the second device, a second indication of successful transfer of the first user identification data between the second device and the user device.
4. 4 . The system of claim 1 , wherein the instructions cause the one or more processors to perform operations comprising: receiving, from a third device associated with a third cryptography-based storage application, a third request for transferring control of the non-fungible token to a fourth cryptography-based storage application associated with a fourth device, wherein the third cryptography-based storage application does not have control of the non-fungible token; generating and transmitting, to the blockchain node, a second blockchain operation request for determining an address of a cryptography-based storage application having control of the non-fungible token; determining the address of the cryptography-based storage application having control of the non-fungible token; determining, using the address of the third cryptography-based storage application, a device identifier for the third device; and transmitting, to the third device, a blockchain operation request for transferring control of the non-fungible token to the fourth cryptography-based storage application.
5. 5 . A method comprising: receiving a prior request for generating a cryptographic token that associates a vehicle and a first user, wherein the prior request comprises (1) vehicle identification data, (2) first user identification data, and (3) a first address of a first cryptography-based storage application corresponding to the first user; storing the first user identification data at a remote computing system; generating a prior blockchain operation for generating the cryptographic token, wherein generating the prior blockchain operation comprises: encrypting a uniform resource identifier, corresponds to a link to the first user identification data stored at the remote computing system, into an encrypted payload; and inserting the encrypted payload into the cryptographic token, wherein the cryptographic token is controlled by the first cryptography-based storage application; receiving, from a user device, a first request for transferring an association of the vehicle from the first user to a second user, wherein the first request comprises (1) an identifier of the cryptographic token that associates the vehicle and the first user, (2) second user data, and (3) a second address of a second cryptography-based storage application associated with the second user, generating a first blockchain operation for transferring control of the cryptographic token from the first cryptography-based storage application associated with the first user to the second cryptography-based storage application associated with the second user, wherein the first blockchain operation comprises the second address associated with the second cryptography-based storage application; transmitting, to the user device, the first blockchain operation for transferring control of the cryptographic token to the second cryptography-based storage application; and in response to receiving an indication of successful blockchain operation from a blockchain node, transmitting, to the remote computing system, a command to update user identification data accessible via the link, wherein the command to update includes second user identification data.
6. 6 . The method of claim 5 , wherein encrypting the uniform resource identifier comprises encrypting the uniform resource identifier into the encrypted payload using a first key associated with the first cryptography-based storage application.
7. 7 . The method of claim 6 , further comprising: receiving, from a second device associated with the second cryptography-based storage application, an access request for accessing the first user identification data, wherein the access request comprises the identifier of the cryptographic token; retrieve, based on the identifier of the cryptographic token in the access request, the encrypted payload associated with the cryptographic token; generating and transmitting, to the user device associated with the first cryptography-based storage application, a decryption request for decrypting the encrypted payload for accessing the first user identification data; and receiving, from the second device, a second indication of successful transfer of first user identification information between the second device and the user device.
8. 8 . The method of claim 6 , wherein the command causes a second device associated with the second user to perform: transmitting a request to the user device for decrypting the encrypted payload to obtain the uniform resource identifier; receiving, from the user device, the uniform resource identifier; encrypting the uniform resource identifier using a second key associated with the second cryptography-based storage application to obtain a second encrypted payload; and inserting, into the cryptographic token, the second encrypted payload.
9. 9 . The method of claim 5 , further comprising: receiving, from a third device associated with a third cryptography-based storage application, a third request for transferring control of the cryptographic token to a fourth cryptography-based storage application associated with a fourth device, wherein the third cryptography-based storage application does not have control of the cryptographic token; generating and transmitting, to the blockchain node, a third blockchain operation for determining an address of a cryptography-based storage application having control of the cryptographic token; determining the address of the cryptography-based storage application having control of the cryptographic token; determining, using the address of the cryptography-based storage application having control, a device identifier for a fifth device associated with the cryptography-based storage application having control; and transmitting, to the fifth device, a fourth blockchain operation for transferring control of the cryptographic token to the fourth cryptography-based storage application.
10. 10 . The method of claim 5 , further comprising: inserting, into the cryptographic token, metadata indicating digital title of the vehicle; and transmitting, to the remote computing system, a second command to access and update the first user identification data stored at the uniform resource identifier by adding the metadata indicating digital title of the vehicle.
11. 11 . The method of claim 5 , further comprising: inserting, into the cryptographic token, metadata indicating physical title of the vehicle identification data; and transmitting, to the remote computing system, a second command to access and update the first user identification data stored at the uniform resource identifier by adding the metadata indicating physical title of the vehicle identification data.
12. 12 . One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising: receiving a prior request for generating a cryptographic token that associates a vehicle and a first user, wherein the prior request comprises (1) vehicle identification data, (2) first user identification data, and (3) a first address of a first cryptography-based storage application corresponding to the first user; storing the first user identification data at a remote computing system; generating a prior blockchain operation for generating the cryptographic token, wherein generating the prior blockchain operation comprises: encrypting a uniform resource identifier, corresponds to a link to the first user identification data stored at the remote computing system, into an encrypted payload; and inserting the encrypted payload into the cryptographic token, wherein the cryptographic token is controlled by the first cryptography-based storage application; receiving, from a user device, a first request for transferring an association of the vehicle from the first user to a second user, wherein the first request comprises (1) an identifier of the cryptographic token that associates the vehicle and the first user, (2) second user data, and (3) a second address of a second cryptography-based storage application associated with the second user; generating a first blockchain operation for transferring control of the cryptographic token from the first cryptography-based storage application associated with the first user to the second cryptography-based storage application associated with the second user, wherein the first blockchain operation comprises the second address associated with the second cryptography-based storage application; transmitting, to the user device, the first blockchain operation for transferring control of the cryptographic token to the second cryptography-based storage application; and in response to receiving an indication of successful blockchain operation from a blockchain node, transmitting, to the remote computing system, a command to update user identification data accessible via the link, wherein the command to update includes second user identification data.
13. 13 . The one or more non-transitory computer-readable media of claim 12 , wherein encrypting the uniform resource identifier comprises encrypting the uniform resource identifier into the encrypted payload using a first key associated with the first cryptography-based storage application.
14. 14 . The one or more non-transitory computer-readable media of claim 13 , wherein the instructions cause the one or more processors to perform operations comprising: receiving, from a second device associated with the second cryptography-based storage application, an access request for accessing the first user identification data, wherein the access request comprises the identifier of the cryptographic token; retrieving, based on the identifier of the cryptographic token in the access request, the encrypted payload associated with the cryptographic token; generating and transmitting, to the user device associated with the first cryptography-based storage application, a decryption request for decrypting the encrypted payload for accessing the first user identification data; and receiving, from the second device, a second indication of successful transfer of first user identification information between the second device and the user device.
15. 15 . The one or more non-transitory computer-readable media of claim 13 , wherein the command causes a second device associated with the second user to perform: transmitting a request to the user device for decrypting the encrypted payload to obtain the uniform resource identifier; receiving, from the user device, the uniform resource identifier; encrypting the uniform resource identifier using a second key associated with the second cryptography-based storage application to obtain a second encrypted payload; and inserting, into the cryptographic token, the second encrypted payload.
16. 16 . The one or more non-transitory computer-readable media of claim 12 , wherein the instructions cause the one or more processors to perform operations further comprising: receiving, from a third device associated with a third cryptography-based storage application, a third request for transferring control of the cryptographic token to a fourth cryptography-based storage application associated with a fourth device, wherein the third cryptography-based storage application does not have control of the cryptographic token; generating and transmitting, to the blockchain node, a third blockchain operation for determining an address of a cryptography-based storage application having control of the cryptographic token; determining the address of the cryptography-based storage application having control of the cryptographic token; determining, using the address of the cryptography-based storage application having control, a device identifier for a fifth device associated with the cryptography-based storage application having control; and transmitting, to the fifth device, a fourth blockchain operation for transferring control of the cryptographic token to the fourth cryptography-based storage application.
17. 17 . The one or more non-transitory computer-readable media of claim 12 , wherein the instructions cause the one or more processors to perform operations further comprising: inserting, into the cryptographic token, metadata indicating a digital title of vehicle; and transmitting, to the remote computing system, a second command to access and update the first user identification data stored at the uniform resource identifier by adding the metadata indicating the digital title of the vehicle.
18. 18 . The one or more non-transitory computer-readable media of claim 12 , wherein the instructions cause the one or more processors to perform operations further comprising: inserting, into the cryptographic token, metadata indicating a physical title of the vehicle; and transmitting, to the remote computing system, a second command to access and update the first user identification data stored at the uniform resource identifier by adding the metadata indicating the physical title of the vehicle.

Description

BACKGROUND Transfer of title, such as vehicle title, is completed by performing multiple transactions between multiple parties. To ensure that only the appropriate parties are completing the transfer, each of these parties typically takes part in a complex process requiring physical authentication, such as by a notary, by providing multiple forms of identification at a third party (e.g., Department of Motor Vehicles (DMV)), and/or the like. For example, even in the simple case of transferring a vehicle title, the transferring party must first release ownership of the vehicle by signing a physical title and subsequently provide the signed title to the person to whom the vehicle is transferred to (e.g., via mail or physical transaction). The person to whom the vehicle is transferred to must then provide the signed title to the DMV (e.g., by mail or physical transaction), and the state may subsequently issue a new registration and title showing ownership of the vehicle. In some cases, the transfer process may require additional forms to be filled out making the process even more painful. Accordingly, a mechanism is desired that would enable individuals or entities to transfer a title to an item (e.g., a vehicle) and for institutions to maintain data regarding such transfers without the need for multiple physical transactions and physical authentication between several parties. SUMMARY One mechanism to enable both users and institutions to transfer vehicle titles may use blockchain technology and, in particular, cryptographic tokens (e.g., non-fungible tokens, also known as NFTs). Therefore, methods and systems are described herein for transferring vehicle titles (or other types of titles) of users using cryptographic tokens (e.g., NFTs). The cryptographic tokens may represent a title of a vehicle and may enable a user to access information regarding the vehicle. For example, the cryptographic token may include an encrypted payload storing a resource identifier (e.g., uniform resource identifier (URI)) identifying information associated with the vehicle (e.g., details regarding the car, previous owner(s), current status, past owner(s), etc.). Control of the cryptographic token by a cryptographic address associated with a user may indicate that the user owns the vehicle (e.g., controls the title). A transfer system may be used to perform operations described herein. The cryptographic tokens may be used by the transfer system as described below. The transfer system may receive a request from a user device (e.g., a user device associated with the user who owns or otherwise uses the vehicle) for transferring an association (e.g., ownership) of a vehicle to a second user (e.g., a new owner of the vehicle). The request may include an identifier of the cryptographic token that associates the vehicle and the first user. For example, the request may include an identifier of a NFT described above. In addition, as described above, the identified cryptographic token may be associated with an encrypted payload that stores a resource identifier (e.g., uniform resource identifier (URI)) identifying information associated with the vehicle. The request may further include second user data (e.g., identification information of the second user, etc.) and a second address of a second cryptography-based storage application associated with the second user. In response to the request, the system may generate a blockchain operation for transferring control of the cryptographic token from a first cryptography-based storage application associated with the first user to the second cryptography-based storage application identified in the request. In some embodiments, transfer of control may be between two cryptographic addresses. The transfer system may transmit, to the user device, the blockchain operation for transferring control of the cryptographic token to the second cryptography-based storage application. Once the system receives an indication that the blockchain operation was successful (e.g., the cryptographic token is controlled by the second cryptography-based storage application of the second user), the system may transmit, to a remote computing device, a command to update first user identification data stored at a link (e.g., the resource identifier). The command to update the first identification data may include second user identification data. In this way, the cryptographic token may include an encrypted reference (i.e., the encrypted payload storing the URI) to information corresponding to the new owner (e.g., the second user). To use the cryptographic token as described above, the transfer system may first cause the cryptographic token to be generated. The transfer system may receive a request from a first user's device (or from another suitable device such as a device associated with a manufacturer or distributor) for generating a cryptographic token (e.g., NFT). The request may include vehicle identification data, first