Bounding Mobile Latency from Network Interconnections
TL;DR
A new method is developed to evaluate the latency cost of sending traffic through an exit point on the three largest U.S. MNOs, and shows that geographic optimization saves little latency: the inflation users experience comes from routing and other overhead.
Abstract
Mobile latency is determined by how Mobile Network Operators (MNOs) route traffic: from phones, across the MNO's network to exit points where it enters the public Internet. Exit points are few, and MNOs are quiet about details, but their role prompts us to ask: What is the latency cost of sending traffic through an exit point? We develop a new method to evaluate this question, and demonstrate it on the three largest U.S. MNOs, although in principle it can apply globally. Using new analysis of existing traceroutes, we find that AT&T, T-Mobile, and Verizon funnel nationwide traffic through only 9, 5, and 9 exits, and the geographic detour they incur adds up to 62.1 ms compared to an ideal, direct-path latency. Routing delays also add latency. We show that even assuming speed-of-light paths through the exit points, latency is still up to 46.9 ms more than optimal. To understand if these costs can be overcome, we compare actual to theoretically optimal placements, finding that the latencies of current placements are 18-66% above the population-weighted optimum and 32-72% above the market-share-weighted optimum with the same number of exits. However, we show this gap is small in absolute terms: perfect placement would recover only a few milliseconds of the tens that remain. We show that geographic optimization saves little latency: the inflation users experience comes from routing and other overhead.