Why Latency Matters to Mobile Backhaul - O3b Networks
Why Latency Matters to Mobile Backhaul - O3b Networks
Why Latency Matters to Mobile Backhaul - O3b Networks
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Why</strong> <strong>Latency</strong> <strong>Matters</strong> <strong>to</strong> <strong>Mobile</strong> <strong>Backhaul</strong><br />
Finally, the absolute quality of the voice and latency impact is related <strong>to</strong><br />
the codec selected. Although in any case, higher latency means a decrease<br />
in quality. For <strong>Mobile</strong> backhaul, AMR-12.2 is widely used and corresponds<br />
<strong>to</strong> GSM-EFR codec.<br />
Ie= 0 5 7 10 15 19 19 20 26<br />
ms<br />
G.711 GSM-EFR<br />
G.726<br />
@32 G.729<br />
G.728<br />
@16<br />
~0 94 87<br />
G.723.1<br />
@6.3<br />
G.729A<br />
+VAD<br />
w/2% loss<br />
G.723.1<br />
@5.3<br />
G.723.1<br />
@<br />
6.3+VAD<br />
w/1% loss<br />
GSM-FR<br />
IS-54<br />
G.729A<br />
+VAD<br />
w/4% loss<br />
50 93 86 83 74 67<br />
100 92 87 85 82 77 73 73 72 66<br />
150 90 85 83 80 75 71 71 70 64<br />
200 87 82 80 77 72 68 68 67 61<br />
250 80 75 73 70 65 61 61 60 54<br />
300 74 69 67 64 59 55 55 54 48<br />
350 68 63 61 58 53 49 49 48 42<br />
400 63 58 56 53 48 44 44 43 37<br />
450 59 54 52 49 44 40 40 39 33<br />
Note 1 – R-values in this table have been calculated using the indicated values for Ie and T (T=Ta=Tr/2) along<br />
with the default values from Table 6 for all other parameters.<br />
Note 2 – Unless indicated otherwise, examples do not include packet loss or Voice Activity Detection (VAD).<br />
Note 3 – Blackened cells indicate combinations of delay and codec that are impossible <strong>to</strong> realize.<br />
Figure 15: R rating values for various voice codecs depending on End <strong>to</strong> end delay (ITU G. 108<br />
Annex B)<br />
Annex 2 TCP details and throughput calculation<br />
This annex gives more details on TCP Flow Control and TCP Congestion and<br />
Maximum TCP throughput and TCP transfer duration.<br />
Flow control<br />
Flow control is achieved using a feature called “sliding windows”.<br />
The receiver advertises the amount of data it can accept through time<br />
(generally related <strong>to</strong> buffering capacity). The transmitter is allowed<br />
<strong>to</strong> transmit data up <strong>to</strong> this advertised value until it receives an ACK<br />
message.<br />
www.o3bnetworks.com 17