Vehicle data sharing with interested parties

1. A method, comprising:

receiving, at a server, sensor data from one or more sensors disposed on a vehicle;

receiving, at the server, additional sensor data from a computing device operating inside the vehicle;

determining the sensor data and the additional sensor data correspond to the vehicle's operational status;

determining whether one or more of the sensor data and the additional sensor data exceed one or more thresholds; and

when one or more of the sensor data and the additional sensor data exceed the one or more thresholds, providing a value to the vehicle.

2. The method of claim 1 , wherein determining the sensor data and the additional sensor data correspond to the vehicle's operational status further comprises:

determining the sensor data has identified an abnormal movement of the vehicle while the vehicle is being operated;

determining the additional sensor data has identified the abnormal movement of the vehicle;

comparing a time the sensor data was captured and a time the additional sensor data was captured; and

when the time the sensor data was captured and the time the additional sensor data was captured are within a predefined time range of one another, designating the sensor data and the additional sensor data correspond to the vehicle's operational status.

3. The method of claim 1 , wherein determining the sensor data and the additional sensor data correspond to the vehicle's operational status further comprises:

determining the sensor data has identified an abnormal condition of the vehicle while the vehicle is being operated;

determining the additional sensor data has identified the abnormal condition of the vehicle;

comparing a magnitude of the sensor data and a magnitude of the additional sensor data; and

when the magnitude of the sensor data and the magnitude of the additional sensor are within a predefined range of one another, designating the sensor data and the additional sensor data correspond to the vehicle's operational status.

4. The method of claim 1 , wherein the sensor data is one or more of movement data, audio data, and video data; and the additional sensor data is one or more of orientation data, angular velocity date, location, speed, direction.

5. The method of claim 1 , wherein the one or more sensors comprise movement sensors, sonar sensors, accelerometers, temperature sensors, speed sensors, sound sensors, collision sensors, tire pressure sensors, location determination sensors, camera sensors, activity sensors, and biometric sensors.

6. The method of claim 1 , further comprising:

invoking, responsive to the sensor data or the additional sensor data being identified, a smart contract, wherein the smart contract comprises at least a portion of a vehicle profile associated with the vehicle, a sensor data recipient profile, a type of sensor data associated with the vehicle profile and the recipient profile, and the value assigned to the vehicle.

7. The method of claim 6 , wherein responsive to invoking the smart contract, creating a distributed ledger transaction which comprises a record of the sensor data that was shared with one or more data recipients, the value assigned to the vehicle, a date of the distributed ledger transaction, and the distributed ledger transaction being logged in a distributed ledger.

8. A system, comprising:

a vehicle;

a computing device operating inside the vehicle; and

a server configured to

receive sensor data from one or more sensors disposed on the vehicle;

receive additional sensor data from the computing device operating inside the vehicle;

determine the sensor data and the additional sensor data correspond to the vehicle's operational status;

determine whether one or more of the sensor data and the additional sensor data exceed one or more thresholds; and

when one or more of the sensor data and the additional sensor data exceed the one or more thresholds, provide a value to the vehicle.

9. The system of claim 8 , wherein the sensor data and the additional sensor data are determined to correspond to the vehicle's operational status by the server further being configured to

determine the sensor data has identified an abnormal movement of the vehicle while the vehicle is being operated;

determine the additional sensor data has identified the abnormal movement of the vehicle;

compare a time the sensor data was captured and a time the additional sensor data was captured; and

when the time the sensor data was captured and the time the additional sensor data was captured are within a predefined time range of one another, designate the sensor data and the additional sensor data correspond to the vehicle's operational status.

10. The system of claim 8 , wherein the sensor data and the additional sensor data are determined to correspond to the vehicle's operational status by the server further being configured to

determine the sensor data has identified an abnormal condition of the vehicle while the vehicle is being operated;

determine the additional sensor data has identified the abnormal condition of the vehicle;

compare a magnitude of the sensor data and a magnitude of the additional sensor data; and

when the magnitude of the sensor data and the magnitude of the additional sensor are within a predefined range of one another, designate the sensor data and the additional sensor data correspond to the vehicle's operational status.

11. The system of claim 8 , wherein the sensor data is one or more of movement data, audio data, and video data; and the additional sensor data is one or more of orientation data, angular velocity date, location, speed, direction.

12. The system of claim 8 , wherein the one or more sensors comprise movement sensors, sonar sensors, accelerometers, temperature sensors, speed sensors, sound sensors, collision sensors, tire pressure sensors, location determination sensors, camera sensors, activity sensors, and biometric sensors.

13. The system of claim 8 , wherein the server is further configured to

invoke, responsive to the sensor data or the additional sensor data being identified, a smart contract, wherein the smart contract comprises at least a portion of a vehicle profile associated with the vehicle, a sensor data recipient profile, a type of sensor data associated with the vehicle profile and the recipient profile, and the value assigned to the vehicle.

14. The system of claim 13 , wherein responsive to the smart contract being invoked, the server is further configured to create a distributed ledger transaction which comprises a record of the sensor data that was shared with one or more data recipients, the value assigned to the vehicle, a date of the distributed ledger transaction, and the distributed ledger transaction being logged in a distributed ledger.

15. A non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform:

receiving, at a server, sensor data from one or more sensors disposed on a vehicle;

receiving, at the server, additional sensor data from a computing device operating inside the vehicle;

determining the sensor data and the additional sensor data correspond to the vehicle's operational status;

determining whether one or more of the sensor data and the additional sensor data exceed one or more thresholds; and

when one or more of the sensor data and the additional sensor data exceed the one or more thresholds, providing a value to the vehicle.

16. The non-transitory computer readable storage medium of claim 15 , wherein the determining the sensor data and the additional sensor data correspond to the vehicle's operational status further comprises:

determining the sensor data has identified an abnormal movement of the vehicle while the vehicle is being operated;

determining the additional sensor data has identified the abnormal movement of the vehicle;

comparing a time the sensor data was captured and a time the additional sensor data was captured; and

when the time the sensor data was captured and the time the additional sensor data was captured are within a predefined time range of one another, designating the sensor data and the additional sensor data correspond to the vehicle's operational status.

17. The non-transitory computer readable storage medium of claim 15 , wherein determining the sensor data and the additional sensor data correspond to the vehicle's operational status further comprises:

determining the sensor data has identified an abnormal condition of the vehicle while the vehicle is being operated;

determining the additional sensor data has identified the abnormal condition of the vehicle;

comparing a magnitude of the sensor data and a magnitude of the additional sensor data; and

when the magnitude of the sensor data and the magnitude of the additional sensor are within a predefined range of one another, designating the sensor data and the additional sensor data correspond to the vehicle's operational status.

18. The non-transitory computer readable storage medium of claim 15 , wherein the sensor data is one or more of movement data, audio data, and video data; and the additional sensor data is one or more of orientation data, angular velocity date, location, speed, direction.

19. The non-transitory computer readable storage medium of claim 15 , wherein the one or more sensors comprise movement sensors, sonar sensors, accelerometers, temperature sensors, speed sensors, sound sensors, collision sensors, tire pressure sensors, location determination sensors, camera sensors, activity sensors, and biometric sensors.

20. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:

invoking, responsive to the sensor data or the additional sensor data being identified, a smart contract, wherein the smart contract comprises at least a portion of a vehicle profile associated with the vehicle, a sensor data recipient profile, a type of sensor data associated with the vehicle profile and the recipient profile, and the value assigned to the vehicle.