Turning now briefly to FIG. 3, a graph 300 illustrating an OTA hourly traffic comparison between CASE 0 and CASE 1 will be described. As shown in the graph 300, CASE 1 smoothens the hourly OTA flow compared to the centralized flow of CASE 0. At the peak hour (hour 7), the OTA size of CASE 1 is nearly half of CASE 0. Thus, it can be seen that the heuristic scheduling algorithm 136 as demonstrated by the results of CASE 1 effectively smoothens the OTA impact on the RAN 108 during busy hours.
Returning to FIG. 1, the illustrated connected car 106 includes a connected car processor 140, a connected car memory 142, a connected car firmware 144, a connected car wireless communications component 146, a connected car operation system 148, and a connected car software application 150. Each of these components will now be described in detail.
