Provisioning of external functionality to transports

1. A method, comprising:

receiving, at a transport, a key and data associated with an upcoming event from a server,

verifying, by the transport, the data associated with the upcoming event based on current data acquired by the transport;

responsive to the verification, receiving, at the transport, functionality configured to address the upcoming event; and

unlocking the functionality on the transport by the key;

wherein the key is modified by the transport, based on an agreement with the server, and the functionality is received at the transport, based on the modified key and data related to the event that is occurring.

2. The method of claim 1 , wherein the verifying comprises sending, by the transport, data as the event begins to occur, from sensors associated with the transport.

3. The method of claim 1 , comprising sending, by the transport, the modified key and the data related to the event that is occurring, from sensors associated with the transport.

4. The method of claim 1 , comprising

receiving, at the transport, the functionality based on the data received from the sensors associated with the transport, responsive to a verification of the modified key based on the key at the server.

5. The method of claim 1 , comprising confirming the upcoming event associated with the key based on transport sensors' or ECU readings.

6. The method of claim 1 , further comprising modifying the key based on an agreement with the server, wherein the agreement constitutes a blockchain consensus at least between a peer represented by the transport and the server.

7. The method of claim 6 , further comprising executing a smart contract to record the modified key on a blockchain responsive to the blockchain consensus.

8. A system, comprising:

a processor of a transport;

a memory on which are stored machine readable instructions that when executed by the processor, cause the processor to:

receive a key and data associated with an upcoming event from a server,

verify the data associated with the upcoming event based on current data acquired by the processor of the transport;

responsive to the verification, receive functionality configured to address the upcoming event; and

unlock the functionality on the transport by the key;

wherein the key is modified by the transport, based on an agreement with the server, and the functionality is received at the transport, based on the modified key and data related to the event that occurs.

9. The system of claim 8 , wherein the verification comprises data that is sent as the event begins to occur, from sensors associated with the transport.

10. The system of claim 8 , wherein the instructions further cause the processor to send the modified key and data related to the event that occurs, from sensors associated with the transport.

11. The system of claim 8 , wherein the instructions further cause the processor to receive the functionality based on the data received from the sensors associated with the transport, responsive to a verification of the modified key based on the key at the server.

12. The system of claim 8 , wherein the instructions further cause the processor to confirm the upcoming event associated with the key based on transport sensors' or ECU readings.

13. The system of claim 8 , wherein the instructions further cause the processor to modify the key based on an agreement with the server, wherein the agreement constitutes a blockchain consensus at least between a peer represented by the transport and the server.

14. The system of claim 13 , wherein the instructions further cause the processor to execute a smart contract to record the key on a blockchain responsive to the blockchain consensus.

15. A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform:

receiving a key and data associated with an upcoming event from a server;

verifying the data associated with the upcoming event based on current data acquired by a transport;

responsive to a verification, receiving functionality configured to address the upcoming event; and

unlocking the functionality on the transport by the key

wherein the key is modified by the transport, based on an agreement with the server, and the functionality is received at the transport, based on the modified key and data related to the event that is occurring.

16. The non-transitory computer readable medium of claim 15 , wherein the verifying comprises sending data as the event begins to occur from sensors associated with the transport.

17. The non-transitory computer readable medium of claim 15 , further comprising instructions, that when read by a processor, cause the processor to send the modified key and the data related to the event that is occurring from sensors associated with the transport.

18. The non-transitory computer readable medium of claim 15 , further comprising instructions, that when read by a processor, cause the processor to receive the functionality based on the data received from the sensors associated with the transport, responsive to a verification of the modified key based on the key at the server.

19. The non-transitory computer readable medium of claim 15 , further comprising instructions, that when read by a processor, cause the processor to modify the key based on an agreement with the server, wherein the agreement constitutes a blockchain consensus at least between a peer represented by the transport and the server.

20. The non-transitory computer readable medium of claim 19 , further comprising instructions, that when read by a processor, cause the processor to execute a smart contract to record the key on a blockchain responsive to the blockchain consensus.