Comtech EF Data CDM-425, Installation And Operation Manual

Page: 691 / 744

CDM-425 Advanced Satellite Modem
Revision 0
Appendix K K–11 MN-CDM-425
Table K-2. VersaFEC Implementation of ACM – 100 ksymbols/sec Example Case
ModCod Modulation Code Rate Spectral efficiency,
bps/Hz
Bit rate (throughput)
Minimum Latency,
In milliseconds
00 BPSK 0.488 0.49 49 kbps 34
01 QPSK 0.533 1.07 107 kbps 32
02 QPSK 0.631 1.26 126 kbps 30
03 QPSK 0.706 1.41 141 kbps 28
04 QPSK 0.803 1.61 161 kbps 26
05 8-QAM 0.642 1.93 193 kbps 30
06 8-QAM 0.711 2.13 213 kbps 28
07 8-QAM 0.780 2.34 234 kbps 27
08 16-QAM 0.731 2.93 293 kbps 27
09 16-QAM 0.780 3.12 312 kbps 26
10 16-QAM 0.829 3.32 332 kbps 25
11 16-QAM 0.853 3.41 341 kbps 25
OVERALL SYSTEM LATENCY = Worst-case ModCod (ModCod0)
Latency = 34 milliseconds, NOT INCLUDING WAN BUFFER OR SATELLITE PATH
By way of comparison, consider the same 100 ksymbols/second rate, but this time using DVB-S2. It
becomes clear that there is an unintended penalty (besides demodulator complexity) to having a
constant number of bits per block. Each time the ModCod is lowered and the throughput is reduced,
the latency grows accordingly due to the block size being related to data rate, not symbol rate.
Remembering that, for the ACM case, the system latency is equal to the latency of the worst-case
ModCod, DVB-S2 shows a severe penalty. For 16k short blocks, this calculates to be 329
milliseconds (+ WAN Buffer delay)
versus 34 milliseconds (+ WAN Buffer delay) for VersaFEC
ACM. For 64k block DVB-S2, the core latency is 4 times higher. Assuming a WAN Buffer of 20
milliseconds:
•
Latency for 64k block DVB-S2 ACM at 100 ksps = 1336 milliseconds
•
Latency for 16k block DVB-S2 ACM at 100 ksps = 349 milliseconds
•
Latency for VersaFEC ACM at 100 ksps = 54 milliseconds
For the example shown, the latency for a 16k block DVB-S2 ACM scheme is
approximately 7 times higher than VersaFEC ACM.
The latency for a 64k block DVB-S2 ACM scheme is approximately 25 times
higher than VersaFEC ACM.