IP Library Granted Patent US 11,631,061
Granted Patent B2
US 11,631,061 · App. 16/940,220 · Granted Apr 18, 2023

Method for creating and maintaining a distributed ledger of vehicle gas consumption and wear and tear information

Inventors: Callum Brook (Piedmont, CA); Theobolt N. Leung (San Francisco, CA)
Assignee: BlueOwl, LLC
G06Q10/20G06F16/2379G06N20/00G06Q40/08H04L9/32
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 11,631,061
App. No.
16/940,220
Filed
Jul 27, 2020
Granted
Apr 18, 2023
Kind
B2
Art Unit
3698
USPC
705/4
Abstract

A distributed ledger operated by a group of network participants according to a set of consensus rules stores vehicle condition data and generated vehicle condition reports, The vehicle condition data may be received directly from a vehicle or an associated mobile device and the vehicle condition report may be accessed by an authorized user.

Claims (34)

1. A validating network node for validating vehicle condition data transactions in a distributed ledger network, the node comprising:

a transceiver configured to exchange distributed ledger data with peer network nodes, the distributed ledger data including transactions having vehicle condition data indicative of a longevity of the vehicle based on at least one selected from a group consisting of wear and tear on the vehicle and fuel efficiency of the vehicle;

a storage media configured to store a copy of a distributed ledger; and

a validator configured to apply a set of consensus rules to the distributed ledger data received from the peer network nodes, wherein the validator is further configured to:

append the distributed ledger data received from the peer network nodes to the copy of the distributed ledger if the distributed ledger data satisfies the set of consensus rules;

disregard the distributed ledger data received from the peer network nodes if the distributed ledger data does not satisfy the set of consensus rules;

execute code in a smart contract configured to generate a vehicle condition report based at least in part upon the vehicle condition data, the vehicle condition report including one or more descriptors indicative of the condition of the vehicle;

generate a solution to solve a cryptographic puzzle based at least in part upon the distributed ledger data received from the peer network nodes;

add the solution to the cryptographic puzzle to the copy of the distributed ledger; and

transmit the copy of the distributed ledger to at least one other participant in the distributed ledger network;

wherein the set of consensus rules comprise a rule on a proof-of-work.

2. The validating network node of claim 1 , wherein the validator is further configured to update a state database associated with the smart contract, the state database including one or more sets of vehicle condition data.

3. The validating network node of claim 2 , wherein the vehicle condition report includes a vehicle condition metric, the vehicle condition metric includes one of an estimated lifetime of the vehicle, an estimated value of the vehicle, and an estimated average fuel consumption of the vehicle.

4. The validating network node of claim 3 , wherein to generate the vehicle condition metric includes to train a machine learning model for generating the vehicle condition metric.

5. The validating network node of claim 2 , wherein the vehicle condition report is generated further based in part upon receiving a payment from a user.

6. The validating network node of claim 2 , wherein the smart contract is a first smart contract, the vehicle condition report is a first vehicle condition report, and wherein the validator is further configured to execute code in one or more additional smart contracts that generates one or more additional vehicle condition reports based at least in part upon the vehicle condition data.

7. The validating network node of claim 6 , wherein the validator is further configured to send a first vehicle condition report to a first user and send a second vehicle condition report to a second user.

8. A device for validating vehicle condition data transactions in a distributed ledger network, the device comprising:

means for transceiving configured to exchange distributed ledger data with peer network nodes, the distributed ledger data including transactions having vehicle condition data indicative of a longevity of the vehicle based on at least one selected from a group consisting of wear and tear on the vehicle and fuel efficiency of the vehicle;

means for storage media configured to store a copy of a distributed ledger; and

means for validating configured to apply a set of consensus rules to the distributed ledger data received from the peer network nodes, wherein the means for validating is further configured to:

append the distributed ledger data received from the peer network nodes to the copy of the distributed ledger if the distributed ledger data satisfies the set of consensus rules;

disregard the distributed ledger data received from the peer network nodes if the distributed ledger data does not satisfy the set of consensus rules;

execute code in a smart contract configured to generate a vehicle condition report based at least in part upon the vehicle condition data, the vehicle condition report including one or more descriptors indicative of the condition of the vehicle;

generate a solution to solve a cryptographic puzzle based at least in part upon the distributed ledger data received from the peer network nodes;

add the solution to the cryptographic puzzle to the copy of the distributed ledger; and

transmit the copy of the distributed ledger to at least one other participant in the distributed ledger network;

wherein the set of consensus rules comprise a rule on a proof-of-work.

9. The device of claim 8 , wherein the means for validating is further configured to update a state database associated with the smart contract, the state database including one or more sets of vehicle condition data.

10. The device of claim 9 , wherein the vehicle condition report includes a vehicle condition metric, the vehicle condition metric includes one of an estimated lifetime of the vehicle, an estimated value of the vehicle, and an estimated average fuel consumption of the vehicle.

11. The device of claim 10 , wherein the means for validating is further configured to train a machine learning model for generating the vehicle condition metric.

12. The device of claim 9 , wherein the vehicle condition report is generated further based in part upon receiving a payment from a user.

13. The device of claim 9 , wherein the smart contract is a first smart contract, the vehicle condition report is a first vehicle condition report, and wherein the means for validating is further configured to execute code in one or more additional smart contracts that generates one or more additional vehicle condition reports based at least in part upon the vehicle condition data.

14. The device of claim 13 , wherein the means for validating is further configured to send a first vehicle condition report to a first user and send a second vehicle condition report to a second user.

Assignments (2)
CHANGE OF NAME Recorded May 29, 2024
From: BLUEOWL, LLC
To: QUANATA, LLC
Reel/Frame 067558/0600 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 28, 2020
From: BROOK, CALLUM; LEUNG, THEOBOLT N.
To: BLUEOWL, LLC
Reel/Frame 053904/0850 →
Continuity (1)
Related Publication 20220292463A1 · Sep 15, 2022