# US 2021/0264526 A1 · Distributed ledger system for use with vehicle sensor data and usage based systems

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0264526 A1
- Document ID: US20210264526A1
- Status: Published application
- Kind: A1
- Application number: 15/870,292
- Filed: 2018-01-12
- Published: 2021-08-26
- Earliest claimed: 2017-05-02
- Assignees: State Farm Mutual Automobile Insurance Company
- Applicants: State Farm Mutual Automobile Insurance Company
- Inventors: Ronny S. Bryant; Stacie A. McCullough; Mitchell J. Hill; Jacob J. Alt; Jaime Skaggs; Shawn M. Call; Eric Bellas; Vick King; Melinda Teresa Magerkurth
- Web page: https://patentgrep.com/patent/US20210264526A1

## CPC

- G06Q 40/084: {by insurance claims processing}
- B60W 50/00: Details of control systems for road vehicle drive control not related to the control of a particular sub-unit {, e.g. process diagnostic or vehicle driver interfaces}
- G06F 16/182: Distributed file systems
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06Q 10/10: Office automation; Time management
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 30/0283: Price estimation or determination
- G06Q 30/0623: {by investigating goods or services}
- G06Q 40/08: Insurance
- G06Q 50/163: Real estate management
- G07C 5/008: {communicating information to a remotely located station (transmission systems for measured values G08C)}
- G07C 5/0808: {Diagnosing performance data (testing of vehicles G01M17/00; testing of electrical installation on vehicles G01R31/005)}
- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/32: including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials}
- H04L 12/2803: {Home automation networks}
- H04L 67/1061: using node-based peer discovery mechanisms (static access to replicated servers H04L67/1006; service discovery H04L67/51)
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04W 4/40: for vehicles, e.g. vehicle-to-pedestrians [V2P]
- B60W 2756/10: Involving external transmission of data to or from the vehicle
- G06F 16/903: Querying (for retrieval from the web G06F16/953)
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2012/2847: {characterised by the type of home appliance used}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- B60W: CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G07C: TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Systems and methods are disclosed with respect to using a distributed ledger for use with vehicle sensor data and usage based systems. These usage based systems may be opt-in programs wherein a driver volunteers to install one or more vehicle sensors configured to monitor various characteristics associated with a vehicle (e.g., speed, acceleration, cornering, braking, path, etc.) that are utilized to develop a profile including information quantifying, for example, a driver's habits. Advantageously for the driver, such a profile can be utilized to reward safe drivers with lower insurance rates, including lower usage-based insurance rates.

## Claims

### Claim 1

A computer-implemented method for managing a usage based insurance profile, the method comprising:
implementing a plurality of servers, each of the plurality of servers maintaining a copy of a distributed ledger, the plurality of servers including a vehicle-based server;
collecting, at the vehicle-based server, sensor data from one or more vehicle sensors or mobile device sensors;
generating, at the vehicle-based server, a transaction record including the collected sensor data;
validating the transaction record including the collected sensor data, including:
(i) causing the vehicle-based server to propose the transaction record to one or more other servers from the plurality of servers;
(ii) performing, via the plurality of servers, a consensus analysis of the transaction record utilizing a consensus mechanism; and
(iii) when the consensus analysis indicates that the plurality of servers have formed a consensus, storing the proposed transaction record at the distributed ledger by storing the transaction record to each copy of the distributed ledger at the plurality of servers;
updating a usage-based insurance (UBI) profile based upon an analysis of a plurality of transaction records stored at the distributed ledger, the plurality of transaction records including the proposed transaction record; and
calculating an insurance premium for the driver based upon the UBI profile.

### Claim 2 (depends on 1)

The method of claim 1, wherein storing the proposed transaction record at the distributed ledger comprises: storing the transaction to a block.

### Claim 3 (depends on 2)

The method of claim 2, wherein performing the consensus analysis comprises generating a hash value for the transaction, and utilizing the hash value for the transaction to generate a hash value for the block.

### Claim 4 (depends on 1)

The method of claim 1, wherein the consensus mechanism is: a proof of work mechanism, a proof of stake mechanism, or a proof of activity mechanism.

### Claim 5 (depends on 1)

The method of claim 1, wherein the consensus mechanism is: a proof of burn mechanism, a proof of capacity mechanism, or a proof of elapsed time mechanism.

### Claim 6 (depends on 1)

The method of claim 1, wherein the transaction record includes data representing: an identity of the insured person and an identity of the vehicle.

### Claim 7 (depends on 1)

The method of claim 1, wherein the one or more vehicle sensors include one or more of the following: a GPS receiver, an accelerometer, a heading indicator, a gyroscope, a braking sensor, and a steering wheel sensor.

### Claim 8 (depends on 1)

The method of claim 1, wherein the sensor data is or includes: (i) telematics data collected via one or more vehicles or mobile devices; (ii) autonomous vehicle data collected via one or more autonomous vehicles, wherein the autonomous vehicle data includes radar data, image data, or telematics data; (iii) smart infrastructure data collected by smart infrastructure, wherein the smart infrastructure data includes speed data or image data; (iv) data indicating an amount of mileage an autonomous vehicle has been driven or operated; and/or (v) data indicating an amount of time an autonomous vehicle has been driven or operated.

### Claim 9 (depends on 7)

The method of claim 7, wherein the transaction record includes data representing one or more of: acceleration, braking, speed, and a path of movement.

### Claim 10 (depends on 1)

The method of claim 1, further comprising publishing the UBI to a user interface of a mobile device accessible by the driver.

### Claim 11 (depends on 1)

The method of claim 1, further comprising publishing the UBI to a user interface installed in the vehicle.

### Claim 12

A system for tracking loss histories, the system comprising:
a plurality of servers maintaining a distributed ledger, the plurality of servers including a vehicle-based server that:
(i) collects sensor data from vehicle sensors or mobile device sensors that track the position and movement of the vehicle;
(ii) generates a transaction record including the collected sensor data; and
(iii) proposes the transaction record to one or more other servers from the plurality of servers;
wherein the plurality of servers are configured to: (i) facilitate validating the transaction record including the collected sensor data, wherein the plurality of servers: (a) perform a consensus analysis of the proposed transaction record utilizing a consensus mechanism; (b) store the transaction record at the distributed ledger when the consensus analysis indicates that the plurality of servers have formed a consensus by storing the transaction record to each copy of the distributed ledger at the plurality of servers; (ii) create a usage-based insurance (UBI) profile based upon an analysis of a plurality of transaction records stored at the distributed ledger, the plurality of transaction records including the proposed transaction record; and (iii) calculate an insurance premium for the driver based upon the UBI profile.

### Claim 13 (depends on 12)

The system of claim 12, wherein storing the proposed transaction record at the distributed ledger comprises: storing the transaction to a block.

### Claim 14 (depends on 13)

The system of claim 13, wherein performing the consensus analysis comprises generating a hash value for the transaction, and utilizing the hash value for the transaction to generate a hash value for the block.

### Claim 15 (depends on 12)

The system of claim 12, wherein the consensus mechanism is: a proof of work mechanism, a proof of stake mechanism, or a proof of activity mechanism.

### Claim 16 (depends on 12)

The system of claim 12, wherein the consensus mechanism is: a proof of burn mechanism, a proof of capacity mechanism, or a proof of elapsed time mechanism.

### Claim 17 (depends on 12)

The system of claim 12, wherein the transaction record includes data representing: an identity of the insured person and an identity of the vehicle.

### Claim 18 (depends on 12)

The system of claim 12, wherein the one or more vehicle sensors include one or more of the following: a GPS receiver, an accelerometer, a heading indicator, a gyroscope, a braking sensor, and a steering wheel sensor.

### Claim 19 (depends on 1)

The method of claim 1, wherein the sensor data is or includes: (i) telematics data collected via one or more vehicles or mobile devices; (ii) autonomous vehicle data collected via one or more autonomous vehicles, wherein the autonomous vehicle data includes radar data, image data, or telematics data; (iii) smart infrastructure data collected by smart infrastructure, wherein the smart infrastructure data includes speed data or image data; (iv) data indicating an amount of mileage an autonomous vehicle has been driven or operated; and/or (v) data indicating an amount of time an autonomous vehicle has been driven or operated.

### Claim 20 (depends on 18)

The system of claim 18, wherein the transaction record includes data representing one or more of: acceleration, braking, speed, and a path of movement.
