Consensus-based transport event severity

1. A method, comprising:

receiving, by a hardware-implemented server, primary data related to the transport from a primary device located in an interior of the transport;

receiving, by the hardware-implemented server, secondary data related to the transport from a plurality of secondary devices remote from the transport;

identifying, by the hardware-implemented server, an occurrence of an event associated with the transport based on the primary data and the secondary data;

identifying, by the hardware-implemented server, a severity of the event based on the primary data and on a consensus regarding the secondary data provided by a majority of the plurality of secondary devices being within a certain range corresponding to the severity of the event; and

sending, by the hardware-implemented server, a first notification to the primary device and a second notification containing content that is different than a content of the first notification to the plurality of secondary devices; and

sending, by the hardware-implemented server, an instruction to the transport to autonomously take an action based on the severity of the event.

2. The method of claim 1 , wherein the primary data and the secondary data comprises:

sensor data relating to anomalous behavior of the transport from the plurality of devices.

3. The method of claim 1 , wherein the identifying a severity of the event further comprises:

identifying the consensus when the secondary data provided by a majority of the plurality of secondary devices is within a common range corresponding to the severity of the event.

4. The method of claim 1 , further comprising:

identifying, by the hardware-implemented server, a state of the transport based on data collected by each secondary device, of the plurality of secondary devices, at a particular time,

wherein the state is related to the event, and

wherein a degree of the secondary data relates to the severity of the event.

5. The method of claim 1 , further comprising:

identifying an action to take based on the severity, the action comprising at least one of:

notifying the transport in response to the severity of the event is low;

notifying the plurality of devices in response to the severity of the event is moderate; and

contacting one or more first responders in response to the severity of the event is high.

6. The method of claim 1 , comprising:

creating, by the hardware-implemented server, a blockchain transaction based on a smart contract and one or more of:

the primary data;

the secondary data;

a location of the plurality of secondary devices;

a type of the plurality of secondary devices;

times of receipt of the secondary data;

a type of the severity of the event; and

a type of the action to take; and

storing, by the hardware-implemented server, the blockchain transaction in a blockchain ledger based on a smart contract.

7. A hardware-implemented server, comprising:

a memory storing one or more instructions; and

a processor that when executing the one or more instructions is configured to:

receive primary data related to a transport from a primary device located in an interior of the transport;

receive secondary data related to the transport from a plurality of secondary devices remote from the transport;

identify an occurrence of an event associated with the transport based on the primary data and the secondary data;

identify a severity of the event based on the primary data and on a consensus regarding the secondary data provided by a majority of the plurality of secondary devices being within a certain range corresponding to the severity of the event; and

send a first notification to the primary device and a second notification containing content that is different than a content of the first notification to the plurality of secondary devices; and

sending an instruction to the transport to autonomously take an action based on the severity of the event.

8. The hardware-implemented server of claim 7 , wherein the primary data and the secondary data comprises:

sensor data relating to anomalous behavior of the transport from the plurality of devices.

9. The hardware-implemented server of claim 7 , wherein, when the processor is configured to identify a severity of the event, the processor is further configured to:

identify the consensus when the secondary data provided by a majority of the plurality of secondary devices is within a common range corresponding to the severity of the event.

10. The hardware-implemented server of claim 7 , wherein the processor is further configured to:

identify a state of the transport based on data collected by each secondary device, of the plurality of secondary devices, at a particular time,

wherein the state is related to the event, and

wherein a degree of the secondary data relates to the severity of the event.

11. The hardware-implemented server of claim 7 , wherein the processor is further configured to:

identify an action to take based on the severity, wherein the action comprises at least one of:

notify the transport in response to the severity of the event is low;

notify the plurality of devices in response to the severity of the event is moderate; and

contact one or more first responders in response to the severity of the event is high.

12. The hardware-implemented server of claim 7 , wherein the processor is configured to:

create a blockchain transaction based on a smart contract and one or more of:

the primary data;

the secondary data;

a location of the plurality of secondary devices;

a type of the plurality of secondary devices;

times of receipt of the secondary data;

a type of the severity of the event; and

a type of the action to take; and

store the blockchain transaction in a blockchain ledger based on a smart contract.

13. A non-transitory computer readable medium comprising one or more instructions that when executed by a processor of a server cause the processor to perform:

receiving primary data related to the transport from a primary device located in an interior of the transport;

receiving secondary data related to the transport from a plurality of secondary devices remote from the transport;

identifying an occurrence of an event associated with the transport based on the primary data and the secondary data;

identifying a severity of the event based on the primary data and on a consensus regarding the secondary data provided by a majority of the plurality of secondary devices being within a certain range corresponding to the severity of the event; and

sending a first notification to the primary device and a second notification containing content that is different than a content of the first notification to the plurality of secondary devices; and

sending an instruction to the transport to autonomously take an action based on the severity of the event.

14. The non-transitory computer readable medium of claim 13 , wherein the primary data and the secondary data comprises:

sensor data relating to anomalous behavior of the transport from the plurality of devices, and

wherein the identifying a severity of the event further comprises:

identifying the consensus when the secondary data provided by a majority of the plurality of secondary devices is within a common range corresponding to the severity of the event.

15. The non-transitory computer readable medium of claim 13 , wherein the one or more instructions further causes the processor to perform:

identifying a state of the transport based on data collected by each secondary device, of the plurality of secondary devices, at a particular time,

wherein the state is related to the event, and

wherein a degree of the secondary data relates to the severity of the event.

16. The non-transitory computer readable medium of claim 13 , wherein the one or more instructions further causes the processor to perform:

identifying an action to take based on the severity, the action comprising at least one of:

notifying the transport in response to the severity of the event is low;

notifying the plurality of devices in response to the severity of the event is moderate; and

contacting one or more first responders in response to the severity of the event is high.

17. The non-transitory computer readable medium of claim 13 , wherein the one or more instructions further cause the processor to perform:

creating, by the hardware-implemented server, a blockchain transaction based on a smart contract and one or more of:

the primary data;

the secondary data;

a location of the plurality of secondary devices;

a type of the plurality of secondary devices;

times of receipt of the secondary data;

a type of the severity of the event; and

a type of the action to take; and

storing, by the hardware-implemented server, the blockchain transaction in a blockchain ledger based on a smart contract.