Surrogate vehicle OTA update through V2X

1. A first vehicle, comprising:

a wireless transceiver; and

a processor programmed to

responsive to encountering a second vehicle, update a frequency list maintained and establish a wireless connection to the second vehicle via the wireless transceiver and obtain a vehicle identification of the second vehicle,

identify a software update for a controller of the second vehicle using the vehicle identification, wherein the software update is incompatible with the first vehicle,

calculate a probability to encounter the second vehicle using the updated frequency list,

responsive to the probability being greater than a predefined threshold and responsive to connecting to a predefined wireless network, download the software update into a local storage, and

responsive to reencountering the second vehicle, reconnect to the second vehicle via the wireless transceiver and transmit the software update to the second vehicle.

2. The first vehicle of claim 1 , wherein the processor is further programmed to:

responsive to receiving a driving instruction directing the first vehicle to get closer to the second vehicle, perform a driving maneuver using the driving instruction.

3. The first vehicle of claim 1 , wherein the processor is further programmed to:

maintain the frequency list recording encounter information each time the vehicle encounters the second vehicle, wherein the encounter information includes location, time and duration of encounters.

4. The first vehicle of claim 1 , wherein the processor is further programmed to:

sharing the frequency list with another vehicle associated with a user of the vehicle.

5. The first vehicle of claim 1 , wherein the processor is further programmed to:

responsive to reconnecting to the second vehicle, verify a current software version for the controller of the second vehicle.

6. The first vehicle of claim 5 , wherein the processor is further programmed to:

responsive to verifying the software update is of a newer version, send a request to transmit software to the second vehicle; and

responsive to receiving an acceptance of the request, transmit the software update to the second vehicle.

7. The first vehicle of claim 1 , wherein the processor is further programmed to:

responsive to receiving a download instruction from a server, download the software update for the second vehicle, wherein the download instruction include information identifying a version of the software update to download and the second vehicle as a potential recipient vehicle.

8. The first vehicle of claim 1 , wherein the processor is further programmed to:

responsive to connecting to a third vehicle for the first time, verify if the software update is compatible with a controller of the third vehicle; and

responsive to verifying the software is compatible with the controller of the third vehicle, wirelessly transmit the software update to the third vehicle.

9. The first vehicle of claim 1 , wherein the processor is further programmed to:

responsive to connecting a fourth vehicle which indicates an availability of a second software update, verify if the second software update is compatible and newer than a current version of software for a controller of the vehicle; and

responsive to a successful verification, send an accept message indicative intent to receive to second software update to the fourth vehicle.

10. A method for a vehicle operating as a donor vehicle, comprising:

responsive to encountering a recipient vehicle,

establishing a wireless connection to the recipient vehicle via a wireless transceiver,

obtaining a vehicle identification of the recipient vehicle, and

updating a frequency list to record encounter information of the recipient vehicle, wherein the encounter information includes location, time and duration of the encounter;

identifying a software update for a controller of the recipient vehicle using the vehicle identification, wherein the software update is incompatible with any controller of the donor vehicle;

calculating a probability to reencounter the recipient vehicle using the frequency list;

responsive to the probability being greater than a predefined threshold and to connecting to a predefined network, downloading the software update into a local storage; and

responsive to reencountering the recipient vehicle, reestablishing the wireless connection and transmitting the software to the recipient vehicle via the wireless connection.

11. The method of claim 10 , further comprising:

responsive to receiving a driving instruction directing the donor vehicle to get closer to the recipient vehicle, performing a driving maneuver using the driving instruction.

12. The method of claim 10 , further comprising:

responsive to receiving a download instruction from a server, downloading the software update for the recipient vehicle, wherein the download instruction include information identifying a version of the software update to download and an identity of the recipient vehicle.

13. The method of claim 10 , further comprising:

sharing the frequency list with another vehicle associated with a user of the donor vehicle.

14. The method of claim 10 , further comprising:

responsive to reestablishing the wireless connection with the recipient vehicle, verifying a current software version for the controller of the recipient vehicle; and

responsive to verifying the software update is of a newer version, starts to transmit the software update to the recipient vehicle.

15. A non-transitory computer-readable medium, comprising instructions, when executed by a processor of a vehicle, made the vehicle to:

responsive to encountering a recipient vehicle,

establish a wireless connection to the recipient vehicle via a wireless transceiver,

obtain a current software version for a controller of the recipient vehicle, and

update a frequency list to record encounter information of the recipient vehicle, wherein the encounter information includes location, time and duration of the encounter;

identify a software update for a controller of the recipient vehicle using the current software version;

calculate a probability to reencounter the recipient vehicle using the frequency list;

responsive to the probability being greater than a predefined threshold and the vehicle connecting to a predefined network, download the software update into a local storage, wherein the software update is incompatible with any controller of the vehicle; and

responsive to reencountering the recipient vehicle, reestablish the wireless connection and transmit the software to the recipient vehicle via the wireless connection.

16. The non-transitory computer-readable medium of claim 15 , further comprising instructions, when executed by a processor of a vehicle, made the vehicle to:

responsive to receiving a driving instruction directing the vehicle to get closer to the recipient vehicle, perform a driving maneuver using the driving instruction.

17. The non-transitory computer-readable medium of claim 16 , further comprising instructions, when executed by a processor of a vehicle, made the vehicle to:

responsive to receiving a download instruction from a server, download the software update for the recipient vehicle, wherein the download instruction include information identifying the version of the software update to download and an identity of the recipient vehicle.

18. The non-transitory computer-readable medium of claim 15 , further comprising instructions, when executed by a processor of a vehicle, made the vehicle to:

responsive to connecting to a second recipient vehicle for the first time, verify if the software update is compatible with a controller of the second recipient vehicle; and

responsive to verifying the software is compatible with the controller of the second recipient vehicle, wirelessly transmit the software update to the second recipient vehicle.

19. The non-transitory computer-readable medium of claim 15 , further comprising instructions, when executed by a processor of a vehicle, made the vehicle to:

responsive to connecting a donor vehicle which indicates an availability of a second software update, verify if the second software update is compatible and newer than a current version of software for a controller of the vehicle; and

responsive to a successful verification, send an accept message indicative intent to receive to second software update to the donor vehicle.