Management of transport software updates
An example operation may include one or more of receiving a software update at a transport of a subset of transports, validating the software update based on one or more of: a period of time when the software update is in use, and a number of utilizations of the software update by the subset of the transports, propagating the software update based on the validating, to a further subset of transports, wherein the further subset of the transports is larger than the subset of the transports.
1. A method, comprising:
identifying, by a master transport, that a first transport and a second transport are within a determined distance of one another; and
sending, by the master transport, an instruction to the first transport to send a first portion of a software update to the second transport to create a complete software update at the second transport; and
sending, by the master transport, an instruction to the second transport to send the complete software update to the first transport.
2. The method of claim 1 , further comprising:
performing, by at least one of the first transport and the second transport, an operation to validate the complete software update based on a period of time that the complete software update is used by the at least one of the first transport or the second transport.
3. The method of claim 2 , further comprising:
in response to successfully validating the complete software update, propagating, by the at least one of the first transport and the second transport, the complete software update to another transport.
4. The method of claim 2 , wherein the performing of the operation to validate the complete software update further comprises:
performing, by the least one of the first transport and the second transport, a first operation to validate the complete software update in a first environment; and
in response to successfully validating the complete software update in the first environment, the method further comprises:
performing, by the least one of the first transport and the second transport, a second operation to validate the complete software update in a second environment that is different than the first environment.
5. The method of claim 2 , further comprising:
in response to a failure in validating the complete software update:
alerting any transport having the complete software update of the failure; and
reverting the any transport to a previous software update.
6. The method of claim 1 , wherein the master transport, the first transport, and the second transport are nodes in a blockchain network.
7. The method of claim 6 , comprising:
executing a smart contract of the blockchain network to validate the complete software update and to propagate the complete software update through a plurality of the transports.
8. A system, comprising:
a master transport comprising a processor that, when executing one or more instructions stored in an associated memory, is configured to:
identify that a first transport and a second transport are within a determined distance of one another; and
send an instruction to the first transport to send a first portion of a software update to the second transport to create a complete software update at the second transport; and
send an instruction to the second transport to send the complete software update to the first transport.
9. The system of claim 8 , wherein at least one of the first transport and the second transport are configured to:
perform an operation to validate the complete software update based on a period of time that the complete software update is used by the at least one of the first transport or the second transport.
10. The system of claim 9 , wherein the at least one of the first transport and the second transport is further configured to:
in response to a successful validation of the complete software update, propagate the complete software update to another transport.
11. The system of claim 9 , wherein when the at least one of the first transport and the second transport is configured to perform the operation to validate the complete software update, the at least one of the first transport and the second transport is further configured to:
perform a first operation to validate the complete software update in a first environment; and
in response to a successful validation of the complete software update in the first environment, the at least one of the first transport and the second transport is further configured to:
perform a second operation to validate the complete software update in a second environment that is different than the first environment.
12. The system of claim 9 , wherein in response to a failure to validate the complete software update, one or more of the processor and the least one of the first transport and the second transport is further configured to:
alert any transport having the complete software update of the failure; and
revert the any transport to a previous software update.
13. The system of claim 8 , wherein the master transport, the first transport, and the second transport are nodes in a blockchain network.
14. The system of claim 13 , wherein the least one of the first transport and the second transport are further configured to:
execute a smart contract of the blockchain network to validate the complete software update and to propagate the complete software update through a plurality of the transports.
15. A non-transitory computer-readable medium comprising one or more instructions that, when executed by one or more processors, cause the one or more processors to perform:
identifying, by a master transport, that a first transport and a second transport are within a determined distance of one another; and
sending, by the master transport, an instruction to the first transport to send a first portion of a software update to the second transport to create a complete software update at the second transport; and
sending, by the master transport, an instruction to the second transport to send the complete software update to the first transport.
16. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the one or more processors to perform:
executing, by at least one of the first transport and the second transport, an operation to validate the complete software update based on a period of time that the complete software update is used by the at least one of the first transport or the second transport.
17. The non-transitory computer-readable medium of claim 16 , wherein the executing the operation to validate the complete software update further comprises:
performing, by the least one of the first transport and the second transport, a first operation to validate the complete software update in a first environment; and
in response to successfully validating the complete software update in the first environment, the method further comprises:
performing, by the least one of the first transport and the second transport, a second operation to validate the complete software update in a second environment that is different than the first environment.
18. The non-transitory computer-readable medium of claim 16 , wherein the one or more instructions further cause the processor to perform:
in response to a failure in validating the complete software update:
alerting any transport having the complete software update of the failure; and
reverting the any transport to a previous software update.
19. The non-transitory computer-readable medium of claim 15 , wherein the master transport, the first transport, and the second transport are nodes in a blockchain network.
20. The non-transitory computer-readable medium of claim 19 , wherein the one or more instructions further cause the one or more processors to perform:
executing execute a smart contract of the blockchain network to validate the complete software update and to propagate the complete software update through a plurality of the transports.