Scheduling software updates for connected cars with limited availability

Secure over-the-air software updates in connected vehicles: A survey

“…These two issues also exist in the case where home EV chargers are used. From a security perspective, we, as well as other authors [6], do not recommended to hinge on the awareness and experience, or lack thereof, of average users to maintain their Wi-Fi access points, wildly common to have guessable passwords and open configurations [41]. Finally, as in cellular OTA updates, downloading through Wi-Fi access points exhausts the backhaul network resources, since the number of connections is linear to the number of Wi-Fi access points, which are roughly as numerous as vehicles.…”

“…Due to the limited cellular Physical Resource Blocks (PRB), shared by mobiles too, cellular networks only scale (with a reasonable interference) to almost 20 car simultaneous zonal downloads. As a consequence of these reasons, a major update (> 1GB) may take one week to complete [3], [6]. Last but not least, cellular-based downloads exhaust the telecommunication network resources since the number of vehicle-to-server connections is linear to the number of vehicles.…”

“…In fact, in a real-world scenario this result is expected to be even worse due to the network congestion and interference from multiple vehicles in close proximity degrading the link quality [4], [6].…”

“…In search for a convenient solution, we realized another facet to this problem, characterized by the centralization of updates on the OEM's repositories at daily peak hours. The experiments in [4], [6] pointed out that the interference caused by simultaneous vehicle updates in a zone at peak hours can reach the bandwidth limit of a telecommunication cell unit with less than 20 vehicles. In addition, the connection's quality deteriorates significantly for the vehicles and other (mobile) users.…”