IP Library Granted Patent US 10,740,849
Granted Patent B1
US 10,740,849 · App. 15/910,300 · Granted Aug 11, 2020

Smart contracts for vehicle events

Inventors: William J. Leise (Normal, IL); Jacob J. Alt (Downs, IL); Jaime Skaggs (Chenoa, IL); Eric Bellas (Bloomington, IL); Shawn M. Call (Bloomington, IL); Eric R. Moore (Heyworth, IL); Melinda Teresa Magerkurth (Utica, IL); Vicki King (Bloomington, IL)
Assignee: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
G06Q40/08G06Q10/20G06Q40/00
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 10,740,849
App. No.
15/910,300
Filed
Mar 2, 2018
Granted
Aug 11, 2020
Kind
B1
Examiner
LIU, I JUNG
Art Unit
3697
USPC
705/4
Abstract

Systems and methods are disclosed for interacting with smart contracts stored on a blockchain to control vehicle related activity. The systems and methods may include (1) receiving one or more transactions from one or more computing devices, the transactions associated with a particular vehicle and include a VIN for the vehicle and indicative of at least one of a trigger condition associated with the vehicle; (2) compiling the one or more transactions into a block of transactions; (3) distributing the block to a plurality of validation entities to form a consensus on an update to the distributed ledger; (4) routing the one or more transactions within the block to respective smart contracts associated with the VIN; and/or (5) automatically executing an action the particular smart contract directs should be performed in response to the particular trigger condition.

Claims (48)

1. A computer-implemented method for interacting with a distributed ledger of transactions pertaining to a plurality of smart contracts, the method comprising:

receiving, at one or more processors, one or more transactions from one or more computing devices, the transactions associated with a particular vehicle and include a Vehicle Identification Number (VIN) for the vehicle and indicative of at least one of a trigger condition or a decision condition associated with one or more smart contracts associated with the vehicle;

compiling, by the one or more processors, the one or more transactions into a block of transactions;

distributing, by the one or more processors, the block to a plurality of validation entities to form a consensus on an update to the distributed ledger;

routing, by the one or more processors, the one or more transactions within the block to respective smart contracts associated with the VIN, wherein a particular transaction corresponding to a particular smart contract indicates that a particular trigger condition for the particular smart contract has occurred; and

automatically executing, by the one or more processors, an action the particular smart contract directs should be performed in response to the particular trigger condition, the action determined based upon a decision condition included in a transaction routed to the particular smart contract.

2. The computer-implemented method of claim 1 , wherein the particular trigger condition for the particular smart contract is related to vehicle maintenance, vehicle repair, vehicle financing, vehicle registration, vehicle titling, vehicle ownership, or combinations thereof.

3. The computer-implemented method of claim 1 , wherein the particular trigger condition for the particular smart contract is related to auto insurance.

4. The computer-implemented method of claim 3 , wherein automatically executing the action further comprises:

updating, by the one or more processors, an insurance policy date, an insurance claim date, or updating both.

5. The computer-implemented method of claim 3 , wherein automatically executing the action comprises:

updating, by the one or more processors, a usage-based insurance policy based upon telematics data, or odometer data received from a customer vehicle or mobile device.

6. The computer-implemented method of claim 1 , wherein the particular trigger condition for the particular smart contract is related to vehicle financing.

7. The computer-implemented method of claim 6 , wherein automatically executing the action further comprises:

updating or generating, via the one or more processors, a vehicle lien payoff amount.

8. The computer-implemented method of claim 1 , wherein the particular trigger condition for the particular smart contract is related to auto insurance.

9. The computer-implemented method of claim 8 , wherein automatically executing the action further comprises:

verifying, by the one or more processors, an insurance policy for the vehicle associated with the VIN, the owner of the insurance policy, one or more insurance coverages and limits under the insurance policy, or combinations thereof.

10. The computer-implemented method of claim 1 , wherein the particular trigger condition for the particular smart contract is related to a vehicle manufacturer.

11. The computer-implemented method of claim 10 , wherein automatically executing the action further comprises:

issuing, by the one or more processors, a recall notice from the vehicle manufacturer to the owner of the vehicle associated with the VIN using owner contact information stored in the distributed ledger.

12. A computer-implemented method for interacting with a distributed ledger of transactions pertaining to a plurality of smart contracts, the method comprising:

receiving, at one or more processors, one or more transactions from one or more computing devices, the transactions associated with a particular vehicle and include a Vehicle Identification Number (VIN) for the vehicle and indicative of at least one of a trigger condition or a decision condition associated with one or more smart contracts associated with the vehicle;

verifying, by the one or more processors, validity of the one or more transactions;

compiling, by the one or more processors, the one or more transactions into a block of transactions;

distributing, by the one or more processors, the block to a plurality of validation entities to form a consensus on an update to the distributed ledger;

routing, by the one or more processors, the one or more transactions within the block to respective smart contracts associated with the VIN, wherein a particular transaction corresponding to a particular smart contract indicates that a particular trigger condition for the particular smart contract has occurred; and

automatically executing, by the one or more processors, an action the particular smart contract directs should be performed in response to the particular trigger condition, the action determined based upon a decision condition included in a transaction routed to the particular smart contract.

13. The computer-implemented method of claim 12 , wherein the particular trigger condition for the particular smart contract is related to vehicle maintenance, vehicle repair, vehicle financing, vehicle registration, vehicle titling, vehicle ownership, or combinations thereof.

14. The computer-implemented method of claim 12 , wherein the particular trigger condition for the particular smart contract is related to auto insurance.

15. The computer-implemented method of claim 14 , wherein automatically executing the action further comprises:

updating, by the one or more processors, an insurance policy date, an insurance claim date, or updating both.

16. The computer-implemented method of claim 14 , wherein automatically executing the action comprises:

updating, by the one or more processors, a usage-based insurance policy based upon telematics data, or odometer data received from a customer vehicle or mobile device.

17. A computer system for maintaining a distributed ledger of transactions pertaining to a particular vehicle, the computer system comprising:

one or more processors;

one or more transceivers adapted to communicate with connected vehicle and other computer devices;

a non-transitory program memory coupled to the one or more processors and storing executable instructions that, when executed by the one or more processors, cause the computer system to:

receive one or more transactions from the connected vehicle or other computing devices, the transactions indicative of at least one of a trigger condition or a decision condition associated with one or more smart contracts, identified by Vehicle Identification Number (VIN), governing or associated with the particular vehicle;

compile the one or more transactions into a block of transactions;

distribute the block to a plurality of validation entities to form a consensus on an update to the distributed ledger;

route the plurality of transactions within the block to respective smart contracts, wherein a particular transaction corresponding to a particular smart contract indicates that a trigger condition for the particular smart contract has occurred; and

automatically execute an action the particular smart contract directs should be performed in response to the particular trigger condition, the action determined based upon a decision condition included in a transaction routed to the particular smart contract.

18. The system of claim 17 , wherein the particular trigger condition for the particular smart contract is related to auto insurance.

19. The system of claim 18 , wherein automatically executing the action further comprises:

update an insurance policy date, an insurance claim date, or updating both.

20. The system of claim 18 , wherein automatically executing the action comprises:

updating, by the one or more processors, a usage-based insurance policy based upon telematics data, or odometer data received from a customer vehicle or mobile device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 6, 2018
From: LEISE, WILLIAM J.; ALT, JACOB J.; SKAGGS, JAIME; BELLAS, ERIC; CALL, SHAWN M.; MOORE, ERIC R.; MAGERKURTH, MELINDA TERESA; KING, VICKI
To: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
Reel/Frame 045115/0339 →
Continuity (19)
Provisional Application 62557433 · Sep 12, 2017
Provisional Application 62557415 · Sep 12, 2017
Provisional Application 62557403 · Sep 12, 2017
Provisional Application 62557393 · Sep 12, 2017
Provisional Application 62557359 · Sep 12, 2017
Provisional Application 62557446 · Sep 12, 2017
Provisional Application 62550131 · Aug 25, 2017
Provisional Application 62550224 · Aug 25, 2017
Provisional Application 62550245 · Aug 25, 2017
Provisional Application 62550140 · Aug 25, 2017
Provisional Application 62550172 · Aug 25, 2017
Provisional Application 62550186 · Aug 25, 2017
Provisional Application 62550261 · Aug 25, 2017
Provisional Application 62550197 · Aug 25, 2017
Provisional Application 62501621 · May 4, 2017
Provisional Application 62500977 · May 3, 2017
Provisional Application 62469070 · Mar 9, 2017
Provisional Application 62468092 · Mar 7, 2017
Provisional Application 62466917 · Mar 3, 2017
Cited By (7)
US 12,235,979 US 12,380,232 US 12,386,989 US 12,566,871 US 12,579,580 US 12,579,585 US 12,602,729