Satellite Channel Emulation¶
This is the Wiki page for the SCS 2014/2015 project #1. It deals with DVB-S2 and its novel ACM feature.
Table Of Contents¶
- Lab Setup
- Information Sources
Why ACM is necessary.
Block diagram of ACM functionality.
A little bit of history.
Features vs DVB-S.
Coding and modulation schemes.
Test Setup Section:
Modem configuration, ethernet bridge. Explain as in manual (both modems on same subnet, etc...)
Introduction Link Emulation system
Network diagram of full setup
Single diagram for each modem and associated client PC
Full settings for modems (ACM mode as well as CCM mode)
Table with IPs
Task 1, Status: DONE
Task 2, Status: TODO
SubTask 1, Status: URGENT
Satellite systems based on the DVB-S standard are inevitably forced to adhere to fixed MODCOD parameters, that is, a fixed coding rate and modulation scheme. This in turn leaves the designer with no choice other than to dimension the system for the worst-case propagation conditions in order to have link-closure and meet availability, coverage and performance requirements.
This approach has the disadvantage that high margins in the carrier-to-noise-and-interference ratios (CNIRs) occur in the majority of cases when propagation conditions allow for it. In the case of broadcasting services, where we have a multitude of users spread over very large areas, this waste of power cannot be easily avoided. However, in point-to-point links if a return channel is present it is possible to report channel state conditions and exploit its temporal variations by adapting the code rate and modulation scheme being used so as to best match the CNIR. This way a fixed link is avoided and considerable improvements in system capacity are obtained with better utilization of power resources.
The DVB-S2 standard introduces adaptive coding and modulation (ACM) enabling better use of transponder resources when high carrier-to-noise-plus-interference ratios occur due to favorable propagation conditions. ACM allows for different coding rates and modulation schemes to be used and dynamically changed on a frame-by-frame basis.
(Similar to fig12 in ETSI-TR.102376)